[kovarex] [0.17.52]Closed signal with path reserved through not reading change in colour state (Repost from 0.49)

[reduke]

Re-posting below as bug was not fixed as reported in: viewtopic.php?f=11&t=72111

Doesn't happen in .48, started in .49, still broken in .50-.52

If a train reserves a path through, but does not start passing, a signal that is subsequently closed via the circuit network before the train finishes passing, then it will not read any new colour states, ie the change in state from amber to red (the amber state stops being red correctly, but red doesn't start).

If the same train reserves a path through and starts (but does not finish) passing the signal before it closes, the red light is read correctly.

Prior to .49, it would keep reading it's colour and changes in colour until the train had finished passing.

[kovarex]

I'm sorry but I don't understand. Passing a signal is a one time action, it doesn't have beginning and ending, it just happens and it is done.

I tried to several things and it seems consistent.

The reading is:

• Nothing when reserved by circuit network
• Red signal when train is inside or closed
• Yellow when reserved
• Green when open.

Even the tooltip says so, so it is supposed to behave like that.

[reduke]

Has this behaviour changed intentionally since .49? Prior to this, when a reserved signal was closed by the circuit network (after the reservation was made), it would still read the reserved state, and the transition to the red state - it would only stop reading when the signal went back to green.

The tooltip doesn't even read correctly for the current behaviour - when closed by the circuit network, it continues to read the current state if yellow or red, but not green, it just does not record any *new* state changes.