Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: Fullscreen to Windows change and game disappears.  (Read 413 times)

Lando242

  • Bay Watcher
    • View Profile
Fullscreen to Windows change and game disappears.
« on: April 10, 2008, 11:45:00 pm »

While playing DF on Windows XP in fortress mode (and of course having not saved in a little over a year ingame) I hit F11 to look up some info on the wiki only to find that the game had not windowed itself and was not listed on the task bar. I had changed between full and windowed mode many times during the session up until that point without issue. A quick look in the task manager showed that is was NO-LONGER listed in the applications tab but was still eating 300 megs of RAM and half my CPU cycles (listening to the CPU fan was enough to know that) in the processes tab. The game was simply gone in any usable sense, alt-tab couldn't find it, the task manager couldn't find it and opening up another instance of the game had no effect. So about 4 hours worth of gameplay gone, bummer, good thing the week end is coming up.

While playing the only thing I noticed that was odd was my first wave of immigrants didn't show up until about mid summer of my second year between my second and third caravan, nothing else strange. I used Regional Prospector when creating the map (but had restored from a save since) and had been running Dwarf Foreman 0.3.8b at the time of the crash. I just updated my video card drivers 3 days ago, have all the latest XP updates and outside of Azureus, Opera Avast Virus scanner and the other apps mention nothing else was running. Anyone know how to keep it from happening again?

[ April 11, 2008: Message edited by: Lando242 ]

[ April 11, 2008: Message edited by: Lando242 ]

Logged

Tayrin

  • Bay Watcher
    • View Profile
Re: Fullscreen to Windows change and game disappears.
« Reply #1 on: April 11, 2008, 12:40:00 pm »

Wow, so it wasn't just me. I had the exact same issue you describe, and I posted about it here. I never found a way to solve the problem, unfortunately, but it hasn't happened in a while, so maybe it's fixed now.

I did reinstall a few drivers for my motherboard and such in the meantime, but I'm not sure if that had anything to do with it.

Logged