Page 1 of 1

Make rail signal placement less janky/unintuitive

Posted: Sat Nov 02, 2024 5:21 am
by Theikkru
I tried to signal some of the new half-curve rails, but it did not work as expected:
rail.png
rail.png (1.42 MiB) Viewed 292 times
I was about to post it as a bug, but found that it had already been reported...and marked not a bug. Apparently, you can figure out what's going on if you turn on the rail collision debug overlay:
collision.png
collision.png (1.39 MiB) Viewed 292 times
I was eventually able to understand what was going on, but, after some consideration, it's still horribly janky and unintuitive, and we really shouldn't have to open a debug overlay to figure out how to signal things.

I propose, then, the following two ways to mitigate confusion:
A. Trim the collision boxes so they don't overlap so jankily:
boxed.png
boxed.png (1.32 MiB) Viewed 292 times
B. Change the graphics/UI so that they more accurately indicate where blocks will be divided:
lined.png
lined.png (1.36 MiB) Viewed 292 times
doodad.png
doodad.png (1.17 MiB) Viewed 292 times

Re: Make rail signal placement less janky/unintuitive

Posted: Sun Nov 03, 2024 5:34 am
by Theikkru
After thinking about it some more, I'd like to pose a question:
Is there some reason there must be exactly one collision box for each rail segment?
From a player perspective, everything would be far more straightforward, and a lot more positions on curves would become valid signal locations, if the signals could bisect rail segment collision boxes wherever they are placed:
bisection.png
bisection.png (286.96 KiB) Viewed 245 times