I have been playing my giant railworld for a while now, and I needed to move some rails around. When attempting to deconstruct a specific section of rail, the game crashed. It did this consistently three times. I didn't test with any adjacent sections of rail so I'm not sure if it is related to something in this specific area or not.
Dropbox link to relevant files: https://www.dropbox.com/sh/64jqwltcubua ... ilg5a?dl=0
In that folder is the save, the two most recent log files for this event occurring, and a few pictures of where this is in my map that is causing the crash. And yes, my save is 63 megs because the world is huge.
I'm not sure what other information is needed but will update if more data is requested!
Edit:
On further inspection it appears to be a problem associated with the rail signals and lights. Whenever I attempt to remove the lights, signal, or cables between the two, the game crashes, but only on this blueprint. Attempting to remove any of those three from the horizontal/vertical sections works just fine without crashing. Perhaps it has something to do with train signals and circuit network interaction when the signal has been placed on a diagonal section of track?
There's another identical placement of the same blueprint just below this, and while the cables are visible on that one it also crashes the game when I attempt to make any modifications to the signal, lights, or specific circuit network.
0.14.5 - Crash on Deconstruction
-
- Burner Inserter
- Posts: 14
- Joined: Tue Jul 19, 2016 6:46 am
- Contact:
Re: 0.14.5 - Crash on Deconstruction
Should be this one: viewtopic.php?f=11&t=32034.
-
- Burner Inserter
- Posts: 14
- Joined: Tue Jul 19, 2016 6:46 am
- Contact:
Re: 0.14.5 - Crash on Deconstruction
Yeah, that looks to be the same issue. My initial guess was that it had something to do with diagonal rails as well.
Reading that thread it appears that it was "fixed" in 0.14.4, in that the problem won't generate again afterward but any current saves with the issue will always have them, is that correct? I've put 350+ hours into my map so far and really don't want to restart it just for this one problem. :/
Reading that thread it appears that it was "fixed" in 0.14.4, in that the problem won't generate again afterward but any current saves with the issue will always have them, is that correct? I've put 350+ hours into my map so far and really don't want to restart it just for this one problem. :/