The International Simutrans Forum

Simutrans Extended => Simutrans-Extended bug reports => Simutrans-Extended development => Simutrans-Extended closed bug reports => Topic started by: freddyhayward on January 19, 2020, 08:34:07 AM

Title: [BUG]: Line/schedule clears when editing schedule in depot on high-latency games
Post by: freddyhayward on January 19, 2020, 08:34:07 AM
steps to reproduce:
begin server game with server_frames_ahead set to some arbitrarily high value, for example 64
connect with client
build depot and stops
create new line
create new convoy in depot
assign vehicle to line, then immediately click "Schedule"

resulting behaviour:
the schedule window reads "no line selected"
closing the schedule window will revert the convoy to "no schedule set"
Title: Re: [BUG]: Line/schedule clears when editing schedule in depot on high-latency games
Post by: freddyhayward on January 21, 2020, 01:39:41 AM
I created a pull request that appears to fix this, however since the change replaces 10 lines of code with a single line of code, I would recommend checking it thoroughly before merging it.

EDIT: The patch currently causes a separate crash, so should not yet be merged.
EDIT 2: I believe that crash has now been fixed.
Title: Re: [BUG]: Line/schedule clears when editing schedule in depot on high-latency games
Post by: Sirius on February 13, 2020, 12:50:50 PM
Has this been incorporated?
If so, please always comment it in the forums as I will move items from the bugreport list to the changelog when they are incorporated. Watching git commuit history and searching for the refered thread is too complicated in that workflow.
Title: Re: [BUG]: Line/schedule clears when editing schedule in depot on high-latency games
Post by: freddyhayward on February 13, 2020, 08:23:34 PM
Yes, that was merged here: https://github.com/jamespetts/simutrans-extended/pull/126. I'll do this in future.
Title: Re: [BUG]: Line/schedule clears when editing schedule in depot on high-latency games
Post by: jamespetts on February 14, 2020, 10:47:12 AM
My apologies for not noting that this had been incorporated; now moved to the solved bug reports section.