https://youtu.be/ylGqDSXw5v0
The video shows it all. Attached is my game file.
[2.0.47] Not able to place rail signals on track segment.
-
- Burner Inserter
- Posts: 5
- Joined: Sun Jun 19, 2022 1:26 pm
- Contact:
[2.0.47] Not able to place rail signals on track segment.
- Attachments
-
- fulgora start2.zip
- (5.38 MiB) Downloaded 20 times
Re: [2.0.47] Not able to place rail signals on track segment.
Hm... That is really interesting corner case. I see exactly where this issue comes from and it may be slightly annoying to fix in a reliable way.
Core of the issue starts at [gps=236.8,-74.4,fulgora]:
This visualisation for placing signals on the left or right side is a "best guess" heuristic which tries to find signals on the left and right side of the rail before deciding which signal spots to show. This logic looks for presence of signals next to current segment and couple of junctions away (to be more precise: up to 5 junctions away). Situation from the picture above is exactly where the "5 junctions away" extends in that case, and the logic sees signal on the left (because it is more south than the corresponding arrows on the left line) but this logic does not see the signal on the right (because it is more north than the corresponding arrow on the right line).
This basically boils down to this - one of the signals is too far and this logic assumes there are only signals on one side and only proposes to build those signals on the corresponding side:
Core of the issue starts at [gps=236.8,-74.4,fulgora]:
This visualisation for placing signals on the left or right side is a "best guess" heuristic which tries to find signals on the left and right side of the rail before deciding which signal spots to show. This logic looks for presence of signals next to current segment and couple of junctions away (to be more precise: up to 5 junctions away). Situation from the picture above is exactly where the "5 junctions away" extends in that case, and the logic sees signal on the left (because it is more south than the corresponding arrows on the left line) but this logic does not see the signal on the right (because it is more north than the corresponding arrow on the right line).
This basically boils down to this - one of the signals is too far and this logic assumes there are only signals on one side and only proposes to build those signals on the corresponding side: