[BUG] 1.01.106 - Crash when using 16q Anti-Aliasing

Here are the details - when I patched the game today to 1.01.106, my game would not launch.  I'd see the demigod splash screen and then the game would crash.  I get a pop up saying unable to start.  Unable to create Direct3d.  Please ensure system has current video drivers.  Then I see an unhandled exception popup (screenshot sent to support). 

If I delete game.prefs, I can get the game to launch normally again.  BUT, when I change anti-aliasing settings back to 16Q, the screen goes gray and it just stays gray (no crash).  Eventually, I control+alt+delete and kill the program.  When I run it again, I get the crash described above.  So, something appears to have changed with this new build that impacts this.  I have never encountered this issue before and my settings have been the same since I purchased some time ago.  I tested all other graphical settings and the only one impacted by this is 16Q, so I can still play without issue. 

All relevant info is being forwarded to SD support.  Here are the last few lines of code from my demigodlog file. 

warning: Key action not found debug_toggle_log_window for key F9
warning: GAL Exception: file : c:\Work\forge\main\code\src\libs\gpggal\DeviceD3D9.cpp(1510)
         error: Ran out of memory
warning: GAL Exception: file : c:\Work\forge\main\code\src\libs\gpggal\DeviceD3D9.cpp(189)
         error: unable to create device

 I'm not running anything out of the ordinary, have over a gig of video memory (gtx 260) and have 4 gigs of ram in my pc.  I uninstalled and reinstalled the game and I have the latest drivers.  And, I have not had any memory issues before. 

1,064 views 2 replies
Reply #1 Top

I checked with a few people in chat.  None of them have been able to reproduce the issue using similar setups and settings. 

Reply #2 Top

This is a strange one, but so far appears to be related to my specific setup (as no one else seems to have the same issue).  I restarted a few times and now this is resolved... perhaps something due to Windows 7's current handling of memory or a driver issue with current nvidia.  Anyway, this can probably be closed out.