[kovarex] [for 0.16] [0.12.26] Train stops at signal while path is free.

[DutchJer]

Hi, I was streaming today, and i noticed that my train just stopped at a railsignal, the next blocks were completely free. It happend to me earlier. I dont have any ideas about what is happening, but ill drop my highlight here.

http://www.twitch.tv/dutchjer/v/54630687

[sillyfly]

This happens quite a lot, but I'm not sure if it will be considered a bug.

What I think is happening is the block was taken, so the train decided it would need to stop there, and slowed down. By the time it got to the signal the block was already free, but the train was already programmed to stop.

It is required for trains to take this into account in advance, as it takes time to decelerate and stop. Theoretically a train could re-accelerate the moment the signal changes state (or at least recalculate if it indeed needs to stop), but I think this is not done due to optimization considerations.

[HanziQ]

This is a known issue, the train decides to stop, because the block was occupied, but doesn't notice, that it can continue, because the other train left. I will visit this with my train fixes/refactoring.

[DutchJer]

Nice, Okay thanks Hanziq, keep up the good work <3

[Loewchen]

See here as well: viewtopic.php?f=7&t=32591
Edit: Maybe same cause but not the same issue.

[kovarex]

I believe, that this was fix a long time ago.