If you're not tied to a tilemap you could do the roads with a few crafted overlapping sprites placed in a grid.

Honestly, I considered something like that...such as manipulating the sprite mesh. (Something I've toyed with only a little bit in times prior. So it would take some work...)

The grid/tilemap option seemed best because it's consistent and easier to place the tiles once I have got them all drawn out. But if I could have even more variety in the road pieces? OH HECK, YEAH... But for now, optimization seemed best. I'm not out to make another Need For Speed: Most Wanted or Burnout Paradise open-world city...just something more simple (and still open-world).

Here's the filler pieces (on the right) I think you need...

With your help, I successfully got just the right set of pieces. Two more than I thought I would need, but it's virtually perfect for my purposes! Thank you for your help!

Here's the filler pieces (on the right) I think you need, along with all their rotations and variations, if this is what you're looking for (example on the left). It's missing all the main turns and corners though, but I think you can figure those out yourself.

Basically have attachment points for road pieces at each tile in thirds as shown on the bottom, and have all the variations needed for inside and outside road connections.

I think you just nailed it! I'll let you know if that's the answer I'm looking for.

THANK YOU!

With just straight and 90 degree turns and intersections I figure you’d need 18 unique tiles (or 6? if you eliminate the mirrored and rotated versions)

[remainder of quote truncated for ease of reading]

Interesting! I will try to apply that method.

And, agreed, there's going to be a LOT of pieces. (I can use the rotate tool inside the tilemap drawing in the layout, so that'll minimize tiles.)

I definitely planned on limiting intersection types. Right now, I just want to figure out the best way to transition from a 90° turn into a 45° straight and make the 45° straight repeatable before going back to a turn that resolves back to a vertical or horizontal straight. (Easy, right? LOL)

I am grateful for your help as always!

I can't help directly, but on the Kenney.nl site is a "Racing Pack Asset" with road tiles with 45° roads, turns, curved roads etc.

May be it is helpful for you to see how others have done it. Asset is free and CC0.

Thank you! And I love Kenney's work. I actually have that very asset pack. Unfortunately, two problems with his work:

1. The angled roads are 26° and not 45°.

2. Those same angled roads don't transition from curved into angled (and back). They go from horizontal to horizontal (or vertical to vertical).

Thank you again for the suggestion, though!

I am attempting to develop a diverse set of road pieces for a tilemap in my game.

The straight vertical and horizontal pieces are easy and done.

The full 90° turns are also relatively easy and done.

What I need help with is to draw 45° straight roads using the same width as the normal roads and connecting them to and from curved roads (which would just be the 90° roads cut in half).

What I'm having trouble with is the positioning of the road pieces within the tilemap grid that (1) uses as few pieces as needed and (2) can be repeated as long as needed.

Anyone with experience in drawing tilemap roads would be a great help.

Thank you.

R0J0hound - Thank you, as always!

Finally getting some time to check this out.

My main concern was how the Wheel object would "snap" to a different angle upon click or de-click. (Although, fine-tuning the actual turning behavior of the wheel in relationship to the X-drag factor of the Touch is also nice, but that's kind of a secondary issue presently.)

I'm going to check out your examples now and get back to you if I have any other issues.

You're a great help every time! GOD BLESS!

WHAT I AM TRYING TO DO

On the mobile screen, I want to have a steering wheel object that the Player will touch and then drag along the X-axis, which will, in turn (heh heh..."turn"...okay, I'll stop), the Wheel. As you can see in the screenshot, I'm using Lerp and Unlerp to accomplish this.

Regardless of where the initial Touch is at on the screen, dragging left or right from that point should rotate the Wheel accordingly. For the most part, this works...

THE PROBLEM

When I click on the Wheel, it "snaps" to an angle rather than remaining at the angle it was "at rest". Because I store the initial Touch.AbsoluteX value to an instance variable in the Wheel, and the rotation of the Wheel is based upon how far the Touch is dragged from that same initial X value, it doesn't make sense why the Wheel snaps to any other angle simply from an initial Touch.

This problem is repeated upon Touch End. The Wheel does not Tween/rotate to the desired angle when I release the Touch. Instead, it snaps to a different angle.

WHAT I NEED

I'm hoping that along with a possible solution, someone might help me to better understand the Touch behavior because I do not use it very often at all. There are particulars I'm definitely not familiar with concerning Touch devices (that seems obvious to me). Or maybe it's just the way Construct 3 handles these things. I don't know.

I will keep working at this and trying different things, but I would be grateful for some insight.

Thank you.

I have a single instance of a tilemap object with all the road-themed tiles in place.

From those tiles on the tilemap instance, I want to select only specific tiles and then randomly select one of those tiles.

What would be an efficient way to do that?

This is an issue I've been dealing with for years...ever since the C2 days.

Across two laptops and using both the built-in touchpad and an external mouse (several different types), at least half of the time (lately, as much as 90%), when I click on an object while holding down CTRL and drag to make a copy of that object, upon release of the mouse button, the image editor invariably will open. I do not double-click.

I have tried every variation I can think of to prevent this or figure out what's causing it. Such as...

- Releasing CTRL at least a second before releasing the mouse button.

- Releasing the mouse button before CTRL.

- Lingering the mouse at the destination in the layout for a moment before releasing anything.

I don't know how to replicate this outright other than to keep using the shortcut and maybe (but almost always) it will happen again.

I could use some input/insight from someone who is more technically-minded than I am with C3 and/or hardware. Before I submit this as a bug, I wanted to get some feedback first.

R0J0hound Nothing in the file?? Odd. I set it so anyone with the link can view it.

In any case, the example you just posted is basically the same setup as what I have as well.

I tested something further...

I opened the Instant Hit Laser example in the C3 example browser.

Naturally, the use of Ray Cast intersection works...on the two Rock sprites. I added a new sprite but the laser object (via Ray Cast) doesn't detect the new sprite I added. It goes right through.

But then I noticed something JUST NOW... SOLID BEHAVIOR!!!

For some reason, Solid behavior is the key! I removed the Solid behavior from the Rock sprite objects in the example and the laser went straight through, just like my sprite that I added. I went back to my project and added Solid behavior to my Wall object and it worked!! The global variable I was testing with also changed to "1" to confirm the Ray Cast intersection.

PROBLEM SOLVED!

Again, thank you for your time in trying to help me sort through this!

I'll keep on saying it every time: you are a blessing and I'm glad you're part of this community. I've learned a lot from you over the years.