|Anonymous | Login | Signup for a new account||2023-02-08 01:36 PST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0010735||Dwarf Fortress||Miscellaneous Crashes||public||2018-04-29 22:01||2018-05-06 10:39|
|Target Version||Fixed in Version|
|Summary||0010735: Game crashes a few minutes after the save (returning raid)|
|Description||Unavoidable crash. Cause unknown.|
|Steps To Reproduce||Waiting a minute or two will suffice.|
|Additional Information||http://dffd.bay12games.com/file.php?id=13716 [^] My save.|
|Tags||0.44.09, crash, Fortress Mode|
|No mods were in use. Completely vanilla. Didn't even change init settings or add a texture pack. Most recent game version with a save made a few days ago on the current version. I'm rather attached to the fort and am afraid I can't make heads or tails of the errorlog https://pastebin.com/VyPD7UH4 [^] other than it seems to really be having trouble with buckets. Any advice on how to make my save playable again would be great.|
edited on: 2018-04-30 02:03
You've made two error reports that are very similar. Is 0010734 really another report for the same issue?
While I couldn't see any indications, it may well be another case of a crash as squads sent out on a raid return. A raid is in progress in the save, and it's a known issue that DF sometimes crash when squad return from raids. However, the other case I've looked at had some of the squad members actually enter the map before it crashed.
edited on: 2018-04-30 08:55
It is a duplicate. Sorry about that. I had expected a place to link my save file in the report form and realized after I clicked the submit button that it never asked for one. So I created a second one including the save file.
So uh. Anyway to un bug my save?
I've invested over a week into this file and was really enjoying how it was coming along. I wouldn't have saved after starting a raid if I'd known about this problem.
edited on: 2018-04-30 10:38
I have a theory: if it IS the pillaging, and some of the squad members returned in the other save, but not on mine: What if one soldier in particular bugged out and crashed the game, and it broke as soon as that one tried to enter the map? In my case it might have crashed beforehand because the very first one who tried to come back is the one who did it.
I think I found a way to resolve it. Or at least render the save useable again. Retiring and unretiring my fortress gave me my military back. They immediately set off to do the mission I had previously assigned them again. I cancelled it before they left the map. This had a few side effects, like my caged ettin suddenly being free in the cage stockpile (And confused, for some reason), as well as undesignating every project I'd ordered the dwarves to build that wasn't done yet. But the save is playable now. Will see if it still crashes later. Of course this doesn't fix the bug, but it's a workaround for anyone in my situation.
Your best bet is probably to wait and hope Toady manages to find and fix the problem (if it is the raid one, which is likely). Toady's latest dev report said he'd fix a few bugs as the last things before the next release, and crash bugs are at the top of the priority list.
The other crash save I've looked at crashed 4-5 times as I tried to figure out exactly where it crashed, and then suddenly all raiders returned, so there might be a small chance the raid crash condition isn't triggered. Thus, the alternative to waiting is to just bang your head against the wall and hope you'll suddenly break through (of course, you could also take the opportunity to top up of a bit of that elusive "Real Life" thing).
edited on: 2018-04-30 12:15
Retiring and unretiring the fortress fixed it. In the sense that it caused the entire mission to reset to "units have not yet left the map" and gave me everyone i sent out on the raid back. This had all the expected side effects of retiring a fortress. So there's a few setbacks. But I got my fortress back at least. now I just need to wait for these hooligans to move all the furnature back where it belongs...
Waiting to see if it still crashes. If it does, obviously, it was some other problem.
v0.44.10: Looks like this was a raid duplicate equipment crash (0010369). From errorlog.txt:
Duplicate inventory removed: ðsteel right gauntletð from Fikod Udilunƒl, Hammer Lord
Duplicate inventory removed: ðsteel low bootð from Fikod Udilunƒl, Hammer Lord
|2018-04-29 22:01||randomoddguy||New Issue|
|2018-04-29 22:10||randomoddguy||Note Added: 0038220|
|2018-04-29 22:11||randomoddguy||Issue Monitored: randomoddguy|
|2018-04-29 22:23||randomoddguy||Tag Attached: 0.44.09|
|2018-04-29 22:23||randomoddguy||Tag Attached: crash|
|2018-04-29 22:23||randomoddguy||Tag Attached: Fortress Mode|
|2018-04-29 22:23||randomoddguy||Tag Attached: unplayable|
|2018-04-30 01:55||PatrikLundell||Note Added: 0038222|
|2018-04-30 02:03||PatrikLundell||Note Edited: 0038222||View Revisions|
|2018-04-30 07:33||lethosor||Tag Detached: unplayable|
|2018-04-30 07:35||lethosor||Relationship added||has duplicate 0010734|
|2018-04-30 08:52||randomoddguy||Note Added: 0038226|
|2018-04-30 08:55||randomoddguy||Note Edited: 0038226||View Revisions|
|2018-04-30 09:53||randomoddguy||Note Added: 0038227|
|2018-04-30 10:38||randomoddguy||Note Edited: 0038227||View Revisions|
|2018-04-30 12:04||PatrikLundell||Note Added: 0038228|
|2018-04-30 12:14||randomoddguy||Note Added: 0038229|
|2018-04-30 12:15||randomoddguy||Note Edited: 0038229||View Revisions|
|2018-05-01 07:45||Loci||Relationship added||child of 0010369|
|2018-05-06 10:38||Loci||Note Added: 0038262|
|2018-05-06 10:38||Loci||Relationship replaced||duplicate of 0010369|
|2018-05-06 10:38||Loci||Status||new => resolved|
|2018-05-06 10:38||Loci||Resolution||open => duplicate|
|2018-05-06 10:38||Loci||Assigned To||=> Loci|
|2018-05-06 10:39||Loci||Summary||Game crashes a few minutes after the save => Game crashes a few minutes after the save (returning raid)|
|Copyright © 2000 - 2010 MantisBT Group|