Exception thrown (in debug pane) when exiting fullscreen

DividedByZero · 2015-10-21T11:25:01

Hi guys,I get the following errors in the debug pane in my DirectX 11 based application, which only show up on exit.This only happens in full screen mode.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067AA20.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067B63C.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067B898.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067BA50.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067AA20.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067B63C.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067B898.Exception thrown at 0x74DB3E28 in DirectX11.exe: Microsoft C++ exception: _com_error at memory location 0x0067BA50.Windowed mode has no errors at all.The only difference in my code (for either mode) is the following; swapChainDesc.Windowed = true; // or false So, I am at a loss as to why this issue may be happening.I read that if you are in full screen mode you need to do the following before clean up. But this doesn't seem to have an effect on the problem. d3dSwapChain->SetFullscreenState(FALSE, NULL); Any ideas would be awesome

Graphics and GPU Programming Programming

Started by DividedByZero October 18, 2015 05:30 AM

15 comments, last by vinterberg 8 years, 6 months ago

DividedByZero

1,261

Author

October 20, 2015 06:42 AM

Unfortunately its not in the clean up. I got my program to quit out to windows right after the device and swapchain are created. Obviously this causes a leak, which VS reports. But, I am still getting the exceptions and still only in fullscreen mode.

I did read recently that hard coding the refresh rate isn't a good thing and will cause exceptions in FS mode. Even though my display says it is 60hz, it might really be 59.95hz or something. So, I'll throw in some proper auto-detection and report back

vinterberg

1,268

October 20, 2015 04:31 PM

It seems like you forget to set SwapEffect, thus it defaults to 0 which is DXGI_SWAP_EFFECT_DISCARD.

This flag is valid for a swap chain with more than one back buffer, although, applications only have read and write access to buffer 0.

And you only got 1 backbuffer ("swapChainDesc.BufferCount = 1;") ..

Maybe this is the cause?

.:vinterberg:.

DividedByZero

1,261

Author

October 20, 2015 10:29 PM

It seems like you forget to set SwapEffect, thus it defaults to 0 which is DXGI_SWAP_EFFECT_DISCARD.

How can you tell that from what I have posted? DXGI_SWAP_EFFECT_DISCARD is a Present() parameter.

The exceptions happen at the 'create device' stage. Even though create device reports that all went well.

DividedByZero

1,261

Author

October 20, 2015 11:18 PM

I added code to correctly query the refresh rate and it is in fact 59.978 Hz.

I have corrected the swapchain creation process to detect the users refresh rate rather than to hard code it. So, that side of things is more robust.

However the exceptions still remain. I'll keep plugging away until this is sorted