View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008717 | Dwarf Fortress | Technical -- Saving/Loading | public | 2015-01-10 07:02 | 2015-01-10 12:51 |
| Reporter | latias1290 | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | N/A |
| Status | resolved | Resolution | no change required | ||
| Platform | Multi-session PC | OS | Windows | OS Version | 7 |
| Product Version | 0.40.24 | ||||
| Summary | 0008717: PC takes forever to finish saving, forcequitting during this stage irrevocably corrupts save | ||||
| Description | I recently had a class drop out because of a sick teacher at school. I decided to grab an empty seat in the computer room and start up a new fort. (I did this in 40.19.) In this version, it takes the PC ages to save, specifically when it says "Finishing..." Because of the fact that I was already running late for the next class, and that probably nothing critically important was happening during that stage, I decided to forcequit DF and log off. Now, my save is unplayable. IIRC crashes during the "Loading world information" state, or at least after the raws are loaded, and before the game began. I have [COMPRESSED_SAVES:OFF] and [AUTOSAVE:SEASONAL] in init.txt, and no other modifications. (Ironically I forgot to set [AUTOBACKUP:YES], making recovery hopeless.) Now, it is well-known that forcequitting during saving is a very good way to lose your save, but it actually was stuck for so long that I thought it froze already. I can't post the world right now because it's Saturday, but I think I can post it the next time I get the chance to access my docs, which is probably monday. | ||||
| Steps To Reproduce | 1. Try to save world. 2. Wait until it says "Finishing..." 3. Force-quit DF. 4. Try to reload the save. | ||||
| Additional Information | The PCs on my school use multiple sessions on one console. This means that on a single PC, up to 6 sessions each with their own screen, mouse, and keyboard can be running. I'm not sure if that may be (partially) causing it but it is possible, although only one other person was logged in on the PC at the time. Another thing is that I had [COMPRESSED_SAVES:ON] initially and later switched to [COMPRESSED_SAVES:OFF]. IIRC it was not so slow before I turned it off. Lastly, I remember seeing old threads on the forums where someone had their save corrupted, and after examination it turned out that many, many unit-###.dat files were gone. (I experienced the same thing after copying a fort over to some other PC, back in 34.11.) I did not have particularly few unit.dat files but only one site-###.dat file. These corruptions MAY be related. | ||||
| Tags | No tags attached. | ||||
|
|
Force-quitting DF during a save is all but guaranteed to break your saved game, so NEVER EVER DO IT! |
|
|
It seems likely that your school's computer setup prevents the game from saving properly. If you can reproduce the "takes forever" on a normal PC, please reopen this report. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-01-10 07:02 | latias1290 | New Issue | |
| 2015-01-10 08:47 | Quietust | Note Added: 0031844 | |
| 2015-01-10 12:51 |
|
Note Added: 0031859 | |
| 2015-01-10 12:51 |
|
Status | new => resolved |
| 2015-01-10 12:51 |
|
Resolution | open => no change required |
| 2015-01-10 12:51 |
|
Assigned To | => user6 |
