The International Simutrans Forum

Simutrans Extended => Simutrans-Extended bug reports => Simutrans-Extended development => Simutrans-Extended closed bug reports => Topic started by: Jando on July 03, 2017, 11:25:25 AM

Title: Wrong travel time in station's detail window
Post by: Jando on July 03, 2017, 11:25:25 AM
Occasionally I see wrong travel times in a station's detail window. Sadly I do not know what causes this (but will check that more often from now on). Once the wrong times are in there they seem to be permanently wrong - although that wrong value can vary a little bit over time.

A screenshot showing such a wrong travel time is here: http://files.simutrans.com/index.php/s/Kae2P8bn0qcZNKM
The saved game to this screenshot is here: http://files.simutrans.com/index.php/s/kqoWKPBkwopyL6f

The last entry in the detail window of that station shows travel time to St. Peter Wetwell as far too long (correct time is less than half the value shown). However, it is not always the last entry that can show wrong travel time, there can be wrong times on other entries as well.

I don't know whether that wrong travel time is used to calculate other values that would be wrong as well then. I don't know if related, but I see wrong info in line management, the capacity and the departures graphs. If unrelated please advise whether I should file a separate bug report for the graphs in line management. Thanks!
Title: Re: Wrong travel time in station's detail window
Post by: DrSuperGood on July 04, 2017, 07:36:09 AM
I remember such an issue back on the old server game. A travel time of 20 hours was being reported as high as 129 hours.
Title: Re: Wrong travel time in station's detail window
Post by: jamespetts on July 05, 2017, 11:43:37 PM
Thank you for the report. I think that I have managed to fix this, which occurred when the last entry in a schedule was a waypoint. Would you be able to re-test with to-morrow's nightly version? I should be most grateful.
Title: Re: Wrong travel time in station's detail window
Post by: Jando on July 07, 2017, 04:00:51 PM
Thank you, James, I have not yet seen other wrong travel times, thus I assume it's fixed. :)