Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0005515Dwarf FortressWorld Generation -- Generalpublic2012-02-29 18:082014-08-04 15:01
phishstrangler75 
Footkerchief 
immediatecrashalways
resolvedduplicate 
WindowsWindows 76.1.7601.2.1.0.7
0.34.04 
 
0005515: Game crashes on acceptance of newly generated world
When I generate a new world, the game immediately crashes on accepting the world. I had 0.34.01 before, and I did not have this problem.
Tried with multiple different parameters, including different world sizes and history lengths. It crashes the same way every time, making the game completely unplayable, as a world cannot be generated.
Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
No tags attached.
duplicate of 0005283resolved Toady One Crash upon accepting/saving a generated world when old-version saves are present 
Issue History
2012-02-29 18:08phishstrangler75New Issue
2012-02-29 18:25krenshalaNote Added: 0020930
2012-02-29 20:19FootkerchiefNote Added: 0020935
2012-02-29 20:19FootkerchiefTag Attached: AWAITING UPDATE
2012-02-29 20:19FootkerchiefRelationship addedduplicate of 0005283
2012-02-29 20:20FootkerchiefNote Edited: 0020935bug_revision_view_page.php?bugnote_id=0020935#r7785
2014-01-20 19:36FootkerchiefStatusnew => resolved
2014-01-20 19:36FootkerchiefResolutionopen => duplicate
2014-01-20 19:36FootkerchiefAssigned To => Footkerchief
2014-08-04 15:01FootkerchiefTag Detached: AWAITING UPDATE

Notes
(0020930)
krenshala   
2012-02-29 18:25   
I do not see the same problem with vanilla 0.34.04 for linux.

phishstrangler75, You might try redownloading, just on the off chance it was a corrupted download. I would have expected that to break the zip file not just world gen, but if nothing else it rules out that kind of corruption as the problem.
(0020935)
Footkerchief   
2012-02-29 20:19   
(edited on: 2012-02-29 20:20)
Are you sure you aren't using 0.34.03 instead? Because this sounds exactly like the bug that 0.34.04 was released in order to fix: 0005283. The releases were only separated by about 14 hours.