The left model is how it should work.
- 10-22-2024, 00-37-06.png (1.33 MiB) Viewed 741 times
- 10-22-2024, 00-40-51.png (1.26 MiB) Viewed 741 times
[2.0.8] Nearby rail blocks are considered one
[2.0.8] Nearby rail blocks are considered one
On the right model the signals attach to the same coordinate, which makes the magenta and bottom aqua tracks cross themselves, which shouldn't be possible in this configuration. Ideally, only the magenta one should cross, while the bottom blue should be 2 different tracks.
The left model is how it should work.
The left model is how it should work.
Re: [2.0.8] Nearby rail blocks are considered the as one
Some of the signal spots on the new curved rails are actually some distance from the block break points they control. This can be really powerful in tightly-packed junctions, but has some side effects as you discovered.
My mods: Multiple Unit Train Control, Smart Artillery Wagons
Maintainer of Vehicle Wagon 2, Cargo Ships, Honk
Maintainer of Vehicle Wagon 2, Cargo Ships, Honk
Re: [2.0.8] Nearby rail blocks are considered the as one
In this case they aren't very far apart. Less than half a rail (1 tile) as I see it. It just happens to be half a rail in an unhelpful direction.
Re: [2.0.8] Nearby rail blocks are considered the as one
(Excuse my poor drawing) Here's approximately how the blocks behave:
The rail joint for both is on the same coordinate, so it thinks that the aqua track is crossing itself.
- 10-22-2024, 09-23-12.png (4.9 KiB) Viewed 647 times
Re: [2.0.8] Nearby rail blocks are considered the as one
If two trains both drive on the cyan rails until their nose is at the rail block division, will they visually collide? Will their collision boxes overlap?
Re: [2.0.8] Nearby rail blocks are considered one
Thanks for the report. This is Not a bug.
When 2 rails pieces overlap each other then they are forced to be in the same rail block. In this case both rails above the junction overlap each other and both rails in below the junction overlap each other but they do not overlap top-bottom so this is what you get.
show-rail-segment-collision-boxes debug layer:
When 2 rails pieces overlap each other then they are forced to be in the same rail block. In this case both rails above the junction overlap each other and both rails in below the junction overlap each other but they do not overlap top-bottom so this is what you get.
show-rail-segment-collision-boxes debug layer:
- 10-27-2024, 21-43-00.png (339.43 KiB) Viewed 466 times
Re: [2.0.8] Nearby rail blocks are considered one
I find this really unintuitive behaviour:boskid wrote: ↑Sun Oct 27, 2024 8:44 pm Thanks for the report. This is Not a bug.
When 2 rails pieces overlap each other then they are forced to be in the same rail block. In this case both rails above the junction overlap each other and both rails in below the junction overlap each other but they do not overlap top-bottom so this is what you get.
show-rail-segment-collision-boxes debug layer:
10-27-2024, 21-43-00.png
viewtopic.php?f=47&t=119501
Maybe dont allow signal placement in these cases? They dont do what you expert anyways.
Re: [2.0.8] Nearby rail blocks are considered one
Yea, with new rails the signals can be confusing in some places and sometimes they don't split the track