View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008615 | Dwarf Fortress | Technical -- Saving/Loading | public | 2014-12-10 13:10 | 2015-03-25 12:36 |
Reporter | Huntthetroll | Assigned To | |||
Priority | normal | Severity | crash | Reproducibility | always |
Status | resolved | Resolution | no change required | ||
Platform | MSI GT70 laptop | OS | Microsoft Windows | OS Version | Windows 8 64-bit |
Product Version | 0.40.19 | ||||
Summary | 0008615: Fortress crashes on save after killing a dragon | ||||
Description | My fortress was attacked by a dragon. The dragon's fiery breath ignited a forest fire that burned most of the embark area. I saved and quit my game halfway through the attack. The next day, I continued the game and my dwarves managed to kill the dragon. However, after the dragon died, I found that I could not save my game again, because Dwarf Fortress would crash at the start of the save process each time I tried to save. | ||||
Steps To Reproduce | Download the save: http://dffd.wimbli.com/file.php?id=10217 Load region 2 (Ishlummuthkat). Try saving it. You shouldn't have any problems doing so. You will see a dragon outside the fortress (and many trees on fire). Station marksdwarves at the top of the central tower and lure the dragon over so they can kill it. Then try to save the game again. Dwarf Fortress will crash. | ||||
Tags | No tags attached. | ||||
|
Windows error logs indicate that the fatal exception occurred in MSVCR100.dll. I am running Dwarf Fortress as part of the Dwarf Fortress 40_19 Starter Pack r2. |
|
This crash no longer occurs in DF 40.24, which I am using as part of PeridexisErrant's Starter Pack 40_24 r3. |
|
It occurs to me that the crash might have happened as a result of the forest fire that the dragon started, which permanently altered the local topography. In particular, the slopes along the sides of various murky pools all disappeared, possibly as a result of cave-ins caused by burning tree roots. |
|
Thanks for the update. It is possible it was related to 0002017. |
Date Modified | Username | Field | Change |
---|---|---|---|
2014-12-10 13:10 | Huntthetroll | New Issue | |
2014-12-10 13:14 | Huntthetroll | Note Added: 0031314 | |
2015-02-02 10:50 | Huntthetroll | Note Added: 0032120 | |
2015-02-03 08:44 | Huntthetroll | Note Added: 0032131 | |
2015-03-25 12:36 |
|
Note Added: 0032419 | |
2015-03-25 12:36 |
|
Status | new => resolved |
2015-03-25 12:36 |
|
Resolution | open => no change required |
2015-03-25 12:36 |
|
Assigned To | => user11 |