Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005284Dwarf FortressDwarf Mode -- Embark/Setuppublic2012-02-18 18:352012-02-21 06:49
Assigned ToFootkerchief 
PlatformAMD x4 840, Geforce 7025 ChipsetOSWindows 7OS Version6.1.7601
Product Version0.34.02 
Target VersionFixed in Version 
Summary0005284: Crash on Embark
DescriptionAny region/world I create is bugged in 34.02.
Pheobus Installed 34.02: [^]
Vanilla 34.02: [^]

I have had a few successful embarks with 34.01...however in 34.02 I was able to embark only at the first region/first site/first embark. It was a test embark to see if this version worked better. Every embark on any generated world since then has failed in version 34.02. In 34.01 it was HIGHLY site dependent. Speculation: if there was not enough elevation variance or too little then the site would be non-embark-able.
Steps To ReproduceGenerate World
Select Site
TagsNo tags attached.
Attached Files

- Relationships
duplicate of 0000136new When embarking on large area, DF hits 2GB memory limit and crashes 
related to 0005223resolvedFootkerchief Crash when embarking 

-  Notes
Logical2u (manager)
2012-02-18 19:55
edited on: 2012-02-18 19:55

Have you tried this without using/installing Phoebus, that is, on a clean 34.02 install?

Mak0 (reporter)
2012-02-18 22:00

Yes, to my knowledge "Vanilla" means unedited/unmodded/clean install. I have already uploaded one of the many regions I created in a clean 34.02 install.

However I have found the main cause(s) of it in 34.02. The crash is dependent on region location, elevation(and variation of)**, and most importantly region size. Anything above 11x11 site area size is a 100% instant crash at embark. My computer should be able to handle above 11x11 easily, however. I get great frame-rates at 10x10, and 11x11; if it successfully embarks. The game runs without a hitch after a successful embark. No problems saving or re-loading yet.

**Completely flat areas are usually insta-crash. Very high elevations are usually insta-crash. Both cases regardless of site-size.
Footkerchief (manager)
2012-02-19 08:11

What happens to your memory usage as you embark? Does it reach 2 GB?
Mak0 (reporter)
2012-02-20 22:29
edited on: 2012-02-20 22:38

No it does not reach 2GB, it gets close to 2GB, around ~1959000 K and crashes.

Footkerchief (manager)
2012-02-21 06:49
edited on: 2012-02-21 06:50

Getting close to 2 GB is good enough to make this a duplicate of 0000136, especially if you're embarking on 11x11 sites. For sites with high elevation variance, you might be getting 0002713.

- Issue History
Date Modified Username Field Change
2012-02-18 18:35 Mak0 New Issue
2012-02-18 19:54 Logical2u Relationship added related to 0005223
2012-02-18 19:55 Logical2u Note Added: 0020081
2012-02-18 19:55 Logical2u Note Edited: 0020081 View Revisions
2012-02-18 22:00 Mak0 Note Added: 0020090
2012-02-19 08:11 Footkerchief Note Added: 0020126
2012-02-20 22:29 Mak0 Note Added: 0020327
2012-02-20 22:38 Mak0 Note Edited: 0020327 View Revisions
2012-02-21 06:49 Footkerchief Note Added: 0020364
2012-02-21 06:49 Footkerchief Relationship added duplicate of 0000136
2012-02-21 06:49 Footkerchief Status new => resolved
2012-02-21 06:49 Footkerchief Resolution open => duplicate
2012-02-21 06:49 Footkerchief Assigned To => Footkerchief
2012-02-21 06:50 Footkerchief Note Edited: 0020364 View Revisions

Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker