[kovarex] [0.16.41] vanilla trains can creep forward with no path

[Zanostra]

I encountered a situation in which trains can creep forward when they have no path available.
In the past there was a problem like this already, but it's in the resolved section.
I commented on it, but I don't know if someone is looking into it because it's in the resolved section.
It's in this topic viewtopic.php?f=11&t=58092

[AreYouScared]

I too have had this issue. Can post video later. Seemed to only happen when train was on a curve

[kovarex]

I tried to reproduce it based on the previous example again with no success.

[mulark]

I have reproduced this behavior in 0.16.51

Here is a save which exhibits the issue:

[invisus]

version [ 16.38 ]

I just came across this bug, and searched the forum if it was known, but I found it in resolved bugs.
Just made a video where it is visible.
The trains creep forward and are still using fuel.

https://www.youtube.com/watch?v=qSZ3egwU-ng

I tested it a little bit extra, and they don't creep ( nor use fuel ) when you put them in manual mode and then in automatic mode again.
They do creep if you place the rail segment so they can go to destination and delete it again to create a 'no path', BUT only if they had enough time to start moving.
By creating and deleting the rail segment to fast, they will not creep.
It doesn't matter if you build/delete the rails by hand, construction bots or bullets.

Yeah! I was able to reproduce it just like in the video here!

Simple loop track, a few signals, two stops, scheduled to hit each stop until 1 sec inactivity. Then pull a piece of rail between train and next stop.

Train begins to "No Path" and every 2-3 seconds, the train creeps forward 1px or so. Barely perceivable, especially given it's relatively slow paced. It doesn't seem completely periodic (certainly not in step with "No Path"), in that the interval between 1px jumps seems to vary slightly. I can upload my save too if needed.

Edit: v0.16.51

[Rseding91]

I fixed this during some unrelated thing I was working on a month or so ago.

So, it's fixed for 0.17.