Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0004163Dwarf FortressWorld Generation -- Generalpublic2011-03-08 04:102012-03-06 08:01
normalmajorhave not tried
PCWindows 7 x64SP1
0004163: World gen doing crazy things with cavern placement.
I just genned a new large region and upon choosing an embark site I found a LONG major river. I was curious to see how wide it would be at the mouth so I attempted to embark there, causing an instant crash. I tried a few more times with different embark square shapes to the same effect. Figuring it might have to do with the river size I attempted to embark a little bit further upstream which succeeded, however, the first thing I see is an eerie glowing pit that my river is draining into, with various cavern layers extending to the surface over one side of the map and two big spires of slade extending far higher than ground level. FPS is near zero due to the entire major river draining into the misplaced crevices. What should be cavern layers are also covered in generic grass where the sky is visible. Magma and water are generating at the sides of the map where the seas should be and falling into space.
I have no idea, I think I got (un)lucky.
Save: http://dffd.wimbli.com/file.php?id=3929 [^]
cavern, crash, worldgen
duplicate of 0005077resolved Toady One Browsing world gen map causes corrupted feature files 
Issue History
2011-03-08 04:10btbtbtbtNew Issue
2011-03-08 04:50btbtbtbtTag Attached: cavern
2011-03-08 04:50btbtbtbtTag Attached: worldgen
2011-03-08 04:50btbtbtbtTag Attached: crash
2011-12-25 06:59FootkerchiefRelationship addedchild of 0000051
2012-02-20 13:10LacNote Added: 0020283
2012-02-20 13:10LacNote Edited: 0020283bug_revision_view_page.php?bugnote_id=0020283#r7575
2012-02-28 09:27FootkerchiefRelationship addedduplicate of 0005077
2012-02-28 09:27FootkerchiefStatusnew => resolved
2012-02-28 09:27FootkerchiefResolutionopen => duplicate
2012-02-28 09:27FootkerchiefAssigned To => Footkerchief
2012-03-06 08:01FootkerchiefRelationship deletedchild of 0000051

2012-02-20 13:10   
See Lightning4's comment 0005077:0020165 which refers to this bug.