You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Load attached scenario. Use cheat to switch to red company (Bilbo transport)
Start train number two. Now, as breakdowns are off, it is "safe" to use ignore signals on train 1, as it won't catch the second train before it gets to "safe" place before the station (where it is protected by another signal). Press "ignore signals" on train 1. Train 1 should ignore the signal and continue, but instead it just jumps one or two squares and stops because "waiting for free path". Each further click on ignore signals will cause it just to jump further one or two squares, instead of the train to ignore that ordinary red signal and continue to next signal (expected behavior, as seen in 0.6 and earlier)
You are hitting the feature that causes trains not to crash all the time when reworking a junction. The train is a PBS junction so each tile it checks whether the next tile is still reserved, which adds a kind of invisible signal to each tile (which in this case is red).
If you do not want the section to be PBS then don't add PBS signals directly to that track section.
If that is feature then it does not work properly. I tried re-creating a simpler version of the layout, also with one PBS signal leading to the section of the track (attached) - I tried to create a small scale layout of the track where I observed the weird behavior. Start train 1, then tell train 2 to ignore signals. Now it works the way I expect it to work ... second train follows the first.
I think that in this case, ignore signals should continue ignoring signals till the train hit first signal or station in its path. While this "waiting feature" is useful when redoing junctions, it is pain in the ass if you want to use ignore signals to move trains from some place.
bilbo opened the ticket and wrote:
Attachments
Reported version: 0.7.0
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/2891
The text was updated successfully, but these errors were encountered: