[Kovarex] [2.0.10] "Read stopped train" signal gets used by "Send to train" in circuit condition interrupts
Posted: Fri Oct 25, 2024 9:58 pm
Hi,
There seems to be an unexpected conflict with trying to use both "Read stopped train" and "Send to train" functions in the Train stop, combined with circuit-triggered interrupts in trains.
A minimal setup is a track, a train stop with "Read stopped train" ([T] from now on) and "Send to train" enabled, a pole connected by a circuit wire to the train stop, a train with one stop, being the stop it's at, and an circuit condition interrupt that sends a train to a stop named, for example, "{SWC} Pickup", where {SWC} is the "Signal parameter" wildcard rich text.
Once the train's wait condition expires, it seems like the [T] bounces back into the Train Stop and immediately into the train, if there is no other signal present. In the video demonstration attached, you can see it happening - during the wait condition, the [T] signal is visible on the power pole/display panel. Once the wait condition runs out, train immediately gets scheduled a station with [T] substituting the interrupt.
This does not sound like a bug per se, as [T] is a signal like any other, but it does sound like a conflict of available options. I would expect Train Stop to ignore the signal it has created itself, be it [T] or "Read train count" ([C]). The issue could be worked around by using a condition such as "Station is not full" condition in the interrupt, but this may not be desirable, if, for example, I plan to use another interrupt to handle that. Maybe a "Destination available", as an opposite of the "Destination full or no path" condition, could be a solution?
Thanks in advance for taking a look.
There seems to be an unexpected conflict with trying to use both "Read stopped train" and "Send to train" functions in the Train stop, combined with circuit-triggered interrupts in trains.
A minimal setup is a track, a train stop with "Read stopped train" ([T] from now on) and "Send to train" enabled, a pole connected by a circuit wire to the train stop, a train with one stop, being the stop it's at, and an circuit condition interrupt that sends a train to a stop named, for example, "{SWC} Pickup", where {SWC} is the "Signal parameter" wildcard rich text.
Once the train's wait condition expires, it seems like the [T] bounces back into the Train Stop and immediately into the train, if there is no other signal present. In the video demonstration attached, you can see it happening - during the wait condition, the [T] signal is visible on the power pole/display panel. Once the wait condition runs out, train immediately gets scheduled a station with [T] substituting the interrupt.
This does not sound like a bug per se, as [T] is a signal like any other, but it does sound like a conflict of available options. I would expect Train Stop to ignore the signal it has created itself, be it [T] or "Read train count" ([C]). The issue could be worked around by using a condition such as "Station is not full" condition in the interrupt, but this may not be desirable, if, for example, I plan to use another interrupt to handle that. Maybe a "Destination available", as an opposite of the "Destination full or no path" condition, could be a solution?
Thanks in advance for taking a look.