Page 1 of 1

[kovarex] [0.17.54] Crashed when dragging a train station in the locomotive schedule GUI.

Posted: Thu Jul 04, 2019 4:32 pm
by Temozarela
Summary
The game crashed when dragging a train station in the locomotive schedule GUI.

Steps:
1. Open the locomotive GUI.
2. Drag a station around the list.

Result:
The game crashes.

Expected Result:
I expected the station to be moved in the schedule.

Additional Notes:
The crash occurred with both newly added stations and existing stations in the schedule.

Reproduction Rate:
10/10 - 100%

Video:
Crash with new station in list: https://www.dropbox.com/s/rw37rjc3nzdfq ... 2.mp4?dl=0
Crash with existing station in list: https://www.dropbox.com/s/mcgtu58jnrxje ... 1.mp4?dl=0

Save File:
https://www.dropbox.com/s/xlmdgllqhvhki ... 2.zip?dl=0

Re: [0.17.54] Crashed when dragging a train station in the locomotive schedule GUI.

Posted: Thu Jul 04, 2019 4:52 pm
by Temozarela
Update:
I was able to reproduce the crash in Sandbox mode with no mods.

Video:
https://www.dropbox.com/s/4i51jq312wgrt ... 3.mp4?dl=0

Re: [0.17.54] Crashed when dragging a train station in the locomotive schedule GUI.

Posted: Sat Jul 06, 2019 8:37 pm
by FlyHigh
Same thing happened to me. CTD whenever a station is dragged on the train schedule.
The old method of adding and deleting still works though.

Re: [0.17.54] Crashed when dragging a train station in the locomotive schedule GUI.

Posted: Mon Jul 08, 2019 3:48 pm
by Smokey
First Post. It would be a bug.

I have this exact same issue. It seems to have appeared in 0.17.54.
Could not have come at a more inconvenient time. :)
factorio-previous.log
(10.38 KiB) Downloaded 162 times
factorio-dump-previous.dmp
(708.19 KiB) Downloaded 138 times

Smokey

Re: [0.17.54] Crashed when dragging a train station in the locomotive schedule GUI.

Posted: Tue Jul 09, 2019 4:56 am
by 3hose
I'm also having this issue

Re: [kovarex] [0.17.54] Crashed when dragging a train station in the locomotive schedule GUI.

Posted: Wed Jul 10, 2019 2:54 pm
by kovarex
Thanks for the report, it is fixed for the next version now.