[2.0.73] rail signal build conflict not highlighted
Posted: Wed May 20, 2026 9:29 pm
[2.0.73] rail signal forced overbuild conflict not highlighted
Note: this is not an antialiasing issue. This depends on build-order (or similar; I did not test further).
I have a train grid blueprint; the common grid places two normal rail signals, the overlay extension replaces it with rail chain signals.
Both are symmetric structures, the rail signals get replaced at both ends, so one would expect the red collision markers to be shown on both ends when using the remote view.
Issue:
One of the ends show both markers, but the other end only 1x of the 2x collisions. If the blueprint is rotated by 180° at the same zoomlevel and viewport position, so the error appears on the other end.
See this video and screenshot:
Blueprints of the base grid and the overlay:
Using the remote view for placing larger rail grid structures is preferable, since this allows more adjacent context to fit on the screen without superfluous details. Train grid blueprints can get so large that don't fit in a zoomed-in screen; the border areas (which are relevant for grind snapping) are only visible when zoomed out.
Therefore I would expect build conflicts of rails signals to be reliably shown in the remote view.
Missing these collision markers is problematic because one can accidentally/unknowingly misplace signals (ie. replacing chain signals with normal signals) that can easily lead to increased travel times and possibly deadlocks.
Note: this is not an antialiasing issue. This depends on build-order (or similar; I did not test further).
- The same structure built twice (one after another) at the same location shows different behaviour.
- One of the structures shows wrong behaviour at all possible orientations and locations.
I have a train grid blueprint; the common grid places two normal rail signals, the overlay extension replaces it with rail chain signals.
Both are symmetric structures, the rail signals get replaced at both ends, so one would expect the red collision markers to be shown on both ends when using the remote view.
Issue:
One of the ends show both markers, but the other end only 1x of the 2x collisions. If the blueprint is rotated by 180° at the same zoomlevel and viewport position, so the error appears on the other end.
See this video and screenshot:
- signal-overbuild-not-shown.png (21.17 KiB) Viewed 110 times
Blueprints of the base grid and the overlay:
Using the remote view for placing larger rail grid structures is preferable, since this allows more adjacent context to fit on the screen without superfluous details. Train grid blueprints can get so large that don't fit in a zoomed-in screen; the border areas (which are relevant for grind snapping) are only visible when zoomed out.
Therefore I would expect build conflicts of rails signals to be reliably shown in the remote view.
Missing these collision markers is problematic because one can accidentally/unknowingly misplace signals (ie. replacing chain signals with normal signals) that can easily lead to increased travel times and possibly deadlocks.