Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Jeoshua]

Somehow, running the game in compatability mode fixed the problem.

AHA!!!

Windows Vista, I presume.

[BigD145]

If you have a multi core CPU, try putting DF on just one core. ctrl+alt+del, processes, right click, set affinity...

[Mazonas]

Windows Vista, I presume.

Ye gods, no.  Win 7.

[ral]

Did you try rebooting just in case system memory got corrupted or something?

[kaenneth]

I would guess it's because DF doesn't always initialize it's memory. Like Glass having Undefined values ( http://www.bay12games.com/dwarves/mantisbt/view.php?id=3071 ) and military orders persisting between games ( http://www.bay12games.com/dwarves/mantisbt/view.php?id=1056 )  there is probably memory being used during worldgen, filled with effectivly random numbers that is being used for uninitialized variables in the new embark, causing crashes.

Windows (generally*) only gives processes zero'd out memory, so the crash won't occur if you exit DF after worldgen, then re-embark. Using that memory as a pointer will cause an access violation (crash), as a string will give an empty string "", while using it as an number gives zero, which is why glass weapon traps (usually) dealt zero damage. I presume Linux/Mac's do the same.

* There are test/debug tools that fill memory with values like '0xDEADBEEF' which makes diagnosing such crashes easier. When I get home I may try running DF under some verification tools, and file bugs as needed (UI framework software API testing is my day job.)