[0.17.66] Rail signals for reserved blocks change to circuit-closed state when train re-paths
Posted: Sat Aug 24, 2019 8:22 am
If the close condition of a rail signal becomes true while the block is reserved (not occupied), and the train that reserved those blocks re-paths, the rail signal will change to the circuit-closed state.
This can lead to trains stopping instantly, and inconsistent circuit output behavior (assuming 74862 isn't also a bug).
Trains are running on nuclear fuel, and the game was running at half speed using the editor tool while recording.
How to reproduce:
The lamp in the top example should stay on as long as the train has reserved, or occupies, the middle block.
The train in the bottom example should move without stopping.
What happens:
Top example:
This can lead to trains stopping instantly, and inconsistent circuit output behavior (assuming 74862 isn't also a bug).
- Rail_signal_circuit_close_on_repath_bug.gif (2.2 MiB) Viewed 1846 times
How to reproduce:
- Build the attached blueprint.
- Fuel trains with nuclear fuel and set to automatic.
- Turn on the constant combinator at Start.
The lamp in the top example should stay on as long as the train has reserved, or occupies, the middle block.
The train in the bottom example should move without stopping.
What happens:
Top example:
- Train reserves the middle block.
- Topmost rail signal becomes red, and its closed condition becomes true.
- Lamp turns on.
- Train stop point hits red rail signal, causing train to repath.
- Topmost rail signal switches to circuit-closed state, and stops outputting a circuit signal.
- Lamp turns off, even though nothing has changed about the state of the middle block.
- Train reserves the middle block.
- Left rail signal becomes yellow, and its closed condition becomes true.
- Train stop point hits red rail signal, causing train to repath.
- Left rail signal switches to circuit-closed state.
- Train instantly stops at Left rail signal.