DX9 fullscreen alt-tab issue [solved - ish]

Damocles · 2010-06-16T03:34:32

I'm having a hell of a problem here...My game, when you alt-tab away (from fullscreen) then alt-tab back, goes screwy. The screen doesn't return to a fullscreen display. Instead, it shows the game window as a thin-bordered black-filled window only, fitting to the screen resolution. The game then receives no updates other than keyboard input (mouse input seems to be ignored) and I have no choice but to quit out.This problem only happens on Vista/W7 - on XP it restores just fine. I tried disabling aero/visual themes, etc, but that's not the issue.Under the DX9 debug spew, there's this:Direct3D9: :Window 000609d6 is on top of us!!Direct3D9: :Window 000609d6 is on top of us!!Direct3D9: :Window 000609d6 is on top of us!!Direct3D9: :Window 000609d6 is on top of us!!Direct3D9: :WM_SYSKEYUP: wParam=00000009 lParam=a00f0001Direct3D9: :Hot key pressed, switching away from appDirect3D9: :Window 000609d6 is on top of us!!Direct3D9: :WM_ACTIVATEAPP: BEGIN Deactivating app pid=0000093c, tid=000012ecDirect3D9: :DoneExclusiveModeDirect3D9: :INACTIVE: 0000093c: Restoring original mode (1440x900x22x75) at adapter index 0Direct3D9: :Window 000609d6 is on top of us!!Direct3D9: :WM_DISPLAYCHANGE: 1440x900x32Direct3D9: :*** Active state changingDirect3D9: :WM_ACTIVATEAPP: DONE Deactivating app pid=0000093c, tid=000012ecDirect3D9: (ERROR) :Lost due to display uniqueness changeThis comes about when I first alt-tab away from the app, and the debug runtimes will break here, on the call to TextCooperativeLevel. The app has handled the lost device, and entered a loop where it checks the coop level every 1/2 second waiting for the time to reset, except it fails. The coop level return value is then D3DERR_DEVICENOTRESET, but resetting the device after this results in the black window mentioned above.Googling around I see a lot of people have hit the "Lost due to display uniqueness change" DX9 error, but I haven't seen any solutions. There's a lot of talk about an NVidia driver bug, but my test HW is ATI.I've checked my lost device code carefully, all state blocks are freed and there's no problem with a reset when running in windowed mode or when making a fullscreen resolution change, only when tabbing away from a fullscreen app.Anyone have any ideas what the cause might be?[Edited by - Damocles on June 16, 2010 3:35:21 AM]

Graphics and GPU Programming Programming

Started by Damocles June 15, 2010 08:17 AM

9 comments, last by Damocles 13 years, 11 months ago

Damocles

133

Author

June 16, 2010 03:34 AM

I found it, or at least I found a way around it...

I added a 0.75 second delay between the call to device->Reset and when it started drawing. It seems the problem lay in the app trying to draw a little bit too soon, and the device wasn't quite ready.

This is odd, because at the very start of my update loop is a cooplevel test to ensure I don't try and draw on a device that's not ok, but that test was returning ok. Very strange, but by giving it a small window to get it's shit together, it now resumes normally. Very strange, but I'm not about to go digging around any further now it's working, for fear of breaking it again :)

------------------------------------------[New Delta Games] | [Sliders]

DX9 fullscreen alt-tab issue [solved - ish]

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

DX9 fullscreen alt-tab issue [solved - ish]

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines