Bay 12 Games Forum

having the same problem with phoebus and forceredraw is not an option as it makes the game crash more often.
as you explained the problem, maybe it can be fixed in a future update of the basegame.

would it be possible to only force redraw for when the viewport is moved?
so it wouldn't have to redraw each and every frame, but only the moment it has to draw new tiles anyway.

https://unity3d.com/unity/system-requirements

Since I've stopped releasing 32bit builds, the minimum windows version is probably XP SP2 x64, but nobody in their right mind uses that.

I still want to be able to play my games and NOT give Micro$oft even a cent for a new OS and if i switched to Linux, i'd lose most games. if someone had given me Win7 for free, i'd use that now.
Biggest problem is that without "support" (eg. all MS-files are inaccessible) i can't even install video drivers when i have to reinstall winXP. so even if i would get hands on a WinXP SP2 x64 copy, i couldn't use it.
but enough of the rambling, it won't change my situation and i don't intend to mislead your topic.
I'll have to wait until my new hardware and the win7 copy from a friend arrives. Then i can finally see DF in 3D

Does the game crash randomly when you interact directly with it, or regardless of whether or not you're interacting with it?

when i used 43.03-r04 LNP, it crashed randomly, but that meant also sometimes when i pressed keys too fast in sequence like b-w-l or b-C-w. deactivating multilevel only reduced the frequency of the crashes, but didn't get rid of it.

now with the 43.03-r07 LNP, it only crashed when switching to other windows frequently. although i haven't played that much with that version yet, it didn't crash for like 4 hours yesterday.

Posting from my Windows 8.1 box. Isn't it just Windows XP that only goes up to DirectX 9?

i got dX10 running here on XP.
in some games even dX11 works on XP, but most don't.

"Doing too many things" won't crash DF, unless those things include behavior that triggers crashes. (Yeah, that sounds silly, but what I mean is that parts of DF that are stable, e.g. calculating liquid flows, won't become unstable when calculating lots of things, particularly because DF's simulation is single-threaded.)

Memory is a more likely issue - if you're using DF 0.43.04 or earlier on Windows, it's limited to 2 GB of memory by default, which people have hit with large worlds/forts/etc.. You should check on DF's memory usage and see if it's approaching that limit. (The limit with a LAA-patched version of DF on Windows, or vanilla DF on other platforms, would be around 4 GB, although it could be a bit closer to 3 GB depending on certain things that I fail to remember.)

well, then it will be the memory on a small world and maximum 3x3 embarks.
i only got 3GB for my whole system and my OS uses roughly 700MB by itself.
if i open the browser to look at the wiki, it's another 200MB.
so for DF there's at maximum 2GB available.

My dwarven world lies dormant as it crashes too often to actually play and other games currently distract me more.

Why wait?  A new release of DF doesn't magically make the current Starter pack any worse!

64bit appears to have a number of small performance improvements, but nothing truly major.  Avoiding the occasional crash due to memory exhaustion is probably more important, and of course the usual new-release-bugfixes are always great.

Yeah, my seemingly random crashes most likely are the result of memory exhaustion.
I only got 3GB DDR3 and even 2x2 embarks crash after some time without any remarkable event as trigger.
also flat embark areas tend to be more stable than those with hills.
if i were better at building cisterns etc. i'd even embark without a river.
other than that, in your lates release, the launcher wouldn't start, so i went back to the 43.04.r03.