[kovarex] [0.17.47] Chain Rail signals display issue

[leitk]

When a chain rail signal is set up ahead of a regular signal that is controlled by circuit, the display of the rail signal gets locked in the wrong setting.
It seems like the signal will still direct traffic correctly however.

Attached is a save file, turn the CC on to set the regular signal to red, if it was green, the chain signal will stay green, but will block the oncoming train.
If it was red, turn it off, and the chain signal will stay red, but will not block the oncoming train.

This is only a display issue, the train does the expected behavior at the chain signal (stop or not).

This was recently introduced (.46 or .47 I would guess), as I noticed this on a 'safe train' setup I had built recently.


(updated save file has no mods)

[leitk]

Thank you Loewchen for politely pointing me at making better bug reports.

[Sonora]

It seems like the signal will still direct traffic correctly however.

But the chain signal reports that it is red to any circuit networks attached to it; so if your wait conditions rely on it telling the truth, things will be broken .

Another example; once the chain signal flips red it stays red even when downstream is green:

secondFlipIncorrect.PNG (808.74 KiB) Viewed 2975 times

Interestingly, inserting a new downstream chain signal causes it to update back to the correct state:

corrected.PNG (524.09 KiB) Viewed 2975 times

Of course, the next time they go red they will both get stuck in that state. Manually removing either chain signal causes the other to update to the correct state.

In my save this bug is present in 0.17.46 and 0.17.47 but not in 0.17.45.

(edited to add additional version information)

[Gentil]

hello, I have the same problem as leitk

[kovarex]

Thanks for the report, it is now fixed for the next release.