Mystery solved. Thanks @gigatank3000.bsky.social for the tip!

It definitely wasn't steam traffic (over roughly the same period), which is noisy but mostly flat. So I assume something external?

(Showing wireframe) I initially made the system with 10m squares as the basis, but that way to big for realistically scaled roads. 5m squares is better. But I may use 10m for runways and <5m for paths and such.

Ish 😅

More glorious programmer art. Reminds me of a spider web. 🕸️

Wish I had it back when I started on procedural buildings. It would have saved so many headaches! At least I will have it in the future when I improve them.

I've actually had this for a while, but I finally figured out how to turn it into a standalone script today. This means I can easily attach it to any object with a mesh, like even this built-in unity sphere. But it's mainly useful for procedural meshes.

I haven't done the lane extension/intersection yet, but I did get my sorting issue figured out to correctly determine neighbors.

bsky.app/profile/joet...

Going to need some additional tessellation to make them terrain conforming like the splines though. Alternatively I could force terrain under intersections to always be flat, but that seems less flexible, and I think it should be doable.

Works with different sizes of roads too.

Ahhhh! Love this write up, thank you! This is similar to what I was already doing, but the extending the lanes beyond the intersection idea was not on my radar yet. I will definitely give it a shot and let you know how it goes.

As for the UVs, I'm not actually sampling a texture there. It's vertex colors as data channels, and a shader to turn them into road markings/curbs etc. Theory is that I can use it to procedurally alter the markings in code. No idea if this is smart but I'm trying it (allergic to textures I guess)!