FS#6046 - Signals: train gets stuck when placing multiple signals over it
Attached to Project:
OpenTTD
Opened by Grzegorz Duczyński (adf88) - Sunday, 15 June 2014, 10:00 GMT
Last edited by andythenorth (andythenorth) - Thursday, 31 August 2017, 07:04 GMT
Opened by Grzegorz Duczyński (adf88) - Sunday, 15 June 2014, 10:00 GMT
Last edited by andythenorth (andythenorth) - Thursday, 31 August 2017, 07:04 GMT
|
Details1. Run a train on a track
2. By performing a single mouse drag-drop, build many one-way signals in a way that: - signals are faced against the train - at least two signals are placed over the train 3. The train gets stuck Kind of signals doesn't matter, the only requirement is that they are non-passable by the train from the side it is coming. Could be related to FS#6039. |
This task depends upon
grep reverse_at openttd.cfg
reverse_at_signals = false
This problem is really annoying and destructive sometimes. It happens quite frequently when you are placing signals on occupied tracks. Short stretches are not a problem, but with longer stretches (ctrl+drag) it is easy to miss that some train stopped. You are finding this out when it's too late (a traffic jam).
Changing 'reverse_at_signals' is not always an option (multiplayer). Besides, current behaviour is not "elegant" ('reverse_at_signals' is just a workaround).
Also 'reverse_at_signals' has other side effects that you may not want to have (reversing it's optional for a reason).