I can't say I've ever slept my system while running a game, but this really sounds like you're just trying to make excuses for the crash.This is graphics driver specific. We've had bugs with this before, and it's all about how the graphics driver restores things. On the laptops/desktops I've tried it's worked fine. Only way I could get it to crash was by updating the graphics card driver, and then - even Visual Studio crashed!
If you went to sleep playing Call Of Duty (or other big game), do they crash when it wakes up?
Understood.We do treat it like a defect, but the problem is if we cannot replicate it here then it is very difficult to fix... We have had this issue before and it was always a graphics driver issue (crash deep in the driver) then driver update fixes it.
Without the ability to replicate it here our hands are basically tied - you may consider it how you want, but our experience with this is OpenGL drivers not restoring from sleep correctly.
Thanks, I will give that a try this evening.Out of interest can you test using the software driver that we supply and put your system to sleep and see if GMS2 survives... to do this go to your installation directory and copy the opengl32.dll from the mesa directory to the main directory and restart GMS2 (you should be able to tell from Help -> About box as it should mention MESA in the Graphics Vendor line) ... once you have tested remember to delete (or move back) the opengl32.dll or it will be using the software driver all the time.
Russell
Blocking the system from sleeping is an idea... it's workaround rather than a fix, and not a good one. For a couple of reasons:We might be able to tell the system not to sleep while we're running (like a video).... unlike a normal desktop app (which uses standard windows GUI elements), we are like a game that draws everything its self in a graphics context (which is why I was wondering if you ever had the same issue with a game).
Can you get any support from Microsoft, or Nvidia, or ATI?As Russ has said, so far it's always been the graphics driver that's been to blame - or windows itself.
OK but what does a driver upgrade have to do with my problem?When doing a driver upgrade, I was debugging the IDE, and the debugger itself (VisualStudio) crashed due to he graphics driver update. The OS will be resetting and throwing lots away during that, and it makes it impossible to debug, let alone see what odd state a program is in mid-execution when it happens. Obviously, you wouldn't update a graphics driver while playing a game, and if you did....you wouldn't be shocked if it crashed. Although we are a tool, we are in a similar boat.
Fair enough.That said.... if we can get a reproducible, non-driver related crash we can look at, we'll try and fix it - or at the very least, exit gracefully.
I cannot update the GFX driver with photoshop open without it crashing, but I can sleep the PC fine.Also...Photoshop I believe can suffer from the same issue, as it uses OpenGL for lots of rendering as well, and if drivers go "funny" on them they will crash too. (i.e. if you update a driver while running PS)
Yeah... you need to be able to close the lid on a laptop and have it sleep. This is one of the ways we were testing and it was working fine here.Can you get any support from Microsoft, or Nvidia, or ATI?
- If I'm on battery power, my system needs to go to sleep/hibernate when it's low on power, or when my power saving settings say it should.
OK but what does a driver upgrade have to do with my problem?
If I was upgrading the graphics driver, then sure, I'd expect there might well be problems with application stability. What does that have to do with the system going to sleep?
Fair enough.
Ah, thanks for explaining that. I hope you guys can figure out a way to make it work.A driver update does the same as a sleep (more or less). The graphics card context is reset and restored, so the program has an old context that is totally invalid for all the views, textures, primitives, surfaces etc. You are basically having to reload everything and start again. But...if I could detect that, I'd force a save and quit so at least it's clean.