[2.0.66] Trains cannot read circuit conditions for inturrupts when in "No path" state
Posted: Fri Sep 19, 2025 1:01 am
What I did:
- Create a rail network with stations A, B, C.
- Send a signal to station A (Will be used in the interrupt condition)
- Set the train limit for B as 0
- Create another station B (same station name) that is in a separate rail network that does not have a train limit.
- Create a train on the first network with a schedule like attached image
- Send train to A
What Happened:
Train gets stuck in no path state at A, trying to path to path to B and cannot read the circuit condition at A to trigger its interrupt.
What I expected:
Train should go to C since the interrupt conditions are met. The train limit tooltip for A indicates that the train is still at the station so it should still be able to read the circuit connection.
Other comments:
If the inaccessible station B is removed, and train is sent to A again, then it works because the train instead goes into a destination full state, which allows it to read the circuit connection and trigger the interrupt. This is very unintuitive behaviour, since stations on another rail network can impact your trains behaviour. Also since "Destination full or no path" is a single interrupt condition implies that they would behave in a consistent way when they actually differ in that only one of those cases still can read the circuit connection at the current station.
Would also be nice if there was a way to see the signals that the train can see, not just the station. I believe my explanation for the bug is correct from testing, but its hard to tell since you can't actually see if the train is receiving the signal from the station.
- Create a rail network with stations A, B, C.
- Send a signal to station A (Will be used in the interrupt condition)
- Set the train limit for B as 0
- Create another station B (same station name) that is in a separate rail network that does not have a train limit.
- Create a train on the first network with a schedule like attached image
- {EE2BE754-29CC-4A5F-BC04-401A149E8AD6}.png (72.26 KiB) Viewed 104 times
What Happened:
Train gets stuck in no path state at A, trying to path to path to B and cannot read the circuit condition at A to trigger its interrupt.
What I expected:
Train should go to C since the interrupt conditions are met. The train limit tooltip for A indicates that the train is still at the station so it should still be able to read the circuit connection.
- {33D14478-BFEC-4BE7-8EFB-ED14EBEB50A9}.png (282.14 KiB) Viewed 104 times
If the inaccessible station B is removed, and train is sent to A again, then it works because the train instead goes into a destination full state, which allows it to read the circuit connection and trigger the interrupt. This is very unintuitive behaviour, since stations on another rail network can impact your trains behaviour. Also since "Destination full or no path" is a single interrupt condition implies that they would behave in a consistent way when they actually differ in that only one of those cases still can read the circuit connection at the current station.
Would also be nice if there was a way to see the signals that the train can see, not just the station. I believe my explanation for the bug is correct from testing, but its hard to tell since you can't actually see if the train is receiving the signal from the station.