Sign in to follow this  
w00key

DX11 [DX11] Exiting fullscreen problem

Recommended Posts

Hello all, I'm new here but a long time lurker and used to trawling the forum search for snippets to solve past problems.

I'm getting a weird issue when exiting from full screen (alt-enter) or from triggered key presses. The problem is that the window area is blank or just not updating the frame image. (its temperamental)
If I return to full screen it starts rendering again with any of my keyboard inputs having updated the view.

It's a simple app which renders a mesh from vertexbuffer using a simple shader.

This issue only happens when I don't have D3D10_CREATE_DEVICE_SINGLETHREADED flag or when I don't render my mesh at all.

Render
[code]void Game::render()
{
//if(!paused_)
//{
ID3D11DeviceContext* context = dx_.getContext();


float ClearColor[4] = { 0.0f, 0.125f, 0.3f, 1.0f }; //red,green,blue,alpha
BOOL fs;
dx_.getSwapChain()->GetFullscreenState(&fs,nullptr);
if(fs)
ClearColor[1] = 1.0f;
if(hit_)
ClearColor[2] = 1.0f;


context->ClearRenderTargetView( dx_.getRenderTarget(), ClearColor );
context->ClearDepthStencilView( dx_.getDepthStencilView(), D3D11_CLEAR_DEPTH, 1.0f, 0 );
CB_FrameChanges cb;
cb.view = XMMatrixTranspose(camera_.getView());
XMVECTOR det;
cb.worldInverse = XMMatrixTranspose(XMMatrixInverse(&det,camera_.getWorld()));
dx_.getContext()->UpdateSubresource(cb_FrameChanges_, 0, nullptr, &cb, 0, 0);

mesh_.setToContext(context);
context->VSSetConstantBuffers( 0, 1, &cb_NeverChanges_ );
context->VSSetConstantBuffers( 1, 1, &cb_ResizeChanges_ );
context->VSSetConstantBuffers( 2, 1, &cb_FrameChanges_ );

context->PSSetConstantBuffers( 0, 1, &cb_NeverChanges_ );
context->PSSetConstantBuffers( 1, 1, &cb_ResizeChanges_ );
context->PSSetConstantBuffers( 2, 1, &cb_FrameChanges_ );
context->VSSetShader( vertexShader_, nullptr, 0 );
context->PSSetShader( pixelShader_, nullptr, 0 );
context->Draw(mesh_.getVertexTotal(), 0);


HRESULT hr = dx_.getSwapChain()->Present(0,0);
if(FAILED(hr))
OutputDebugStringA("Failed to present.\n");
//}}[/code]

WndProc
[code]LRESULT CALLBACK wndProc( HWND hWnd, UINT msg, WPARAM wParam, LPARAM lParam )
{
if(msg == WM_PAINT)
{
PAINTSTRUCT ps;
BeginPaint( hWnd, &ps );
EndPaint( hWnd, &ps );
}
else if(msg == WM_DESTROY )
{
PostQuitMessage(0);
}
else if(msg == WM_SIZE)
{
Game* game = (Game*) GetWindowLongPtr(hWnd, GWL_USERDATA);
RECT rc;
GetClientRect(hWnd, &rc );
const int width = rc.right - rc.left;
const int height = rc.bottom - rc.top;
game->resize(width,height);
}
else if(msg == WM_GETMINMAXINFO)
{
((MINMAXINFO*)lParam)->ptMinTrackSize.x = 50;
((MINMAXINFO*)lParam)->ptMinTrackSize.y = 50;

}
else if(msg == WM_NCCREATE)
{
LPCREATESTRUCT cs = (LPCREATESTRUCT) lParam;
SetWindowLongPtr(hWnd, GWL_USERDATA, (long) cs->lpCreateParams);
return DefWindowProc( hWnd, msg, wParam, lParam );
}
else
return DefWindowProc( hWnd, msg, wParam, lParam );
return 0;}[/code]

WM_SIZE calls my resize function
[code] bool prevFullscreen = fullscreen_;
BOOL fullscreen = 0;
if(FAILED(swapChain_->GetFullscreenState(&fullscreen, nullptr)))
OutputDebugStringA("Failed to get fullscreen state.\n");
fullscreen_ = (fullscreen > 0);
//only resize if new height/width are different to current and they both aren't 0
if((height != height_ || width != width_) && (width != 0 && height != 0 ) && (fullscreen_ != prevFullscreen))
{
OutputDebugStringA("Going to resize buffers.\n");
DXGI_SWAP_CHAIN_DESC swapChainDesc;

width_ = width;
height_ = height;

context_->OMSetRenderTargets(0, 0, 0);



swapChain_->GetDesc(&swapChainDesc);
swapChainDesc.Windowed = !fullscreen;
swapChainDesc.Flags = 0;
if(fullscreen_)
swapChainDesc.Flags = DXGI_SWAP_CHAIN_FLAG_ALLOW_MODE_SWITCH;

//Release renderTarget, depth stencil view, etc

depthStencilView_->Release();
renderTarget_->Release();
if(FAILED(swapChain_->ResizeBuffers(swapChainDesc.BufferCount,width,height, swapChainDesc.BufferDesc.Format ,swapChainDesc.Flags)))
{
MessageBox( NULL, "Failed to resize buffers.", "DirectX Error", MB_OK );
return false;
}
//recreate everything that was released
if(!createRenderTarget())
return false;
if(!createDepthStencils(width,height))
return false;


context_->OMSetRenderTargets( 1, &renderTarget_, depthStencilView_);
D3D11_VIEWPORT vp; //Should be a member of dx!
vp.Width = (float)width;
vp.Height = (float)height;
vp.MinDepth = 0.0f;
vp.MaxDepth = 1.0f;
vp.TopLeftX = 0;
vp.TopLeftY = 0;
context_->RSSetViewports( 1, &vp );
}
return true;}[/code]

I've added a fair bit of debug stuff since this problem has been bugging me. I essentially
release renderTarget, release depthStencilView
resizeBuffers and recreate the released bits.

I'm running it with the debug flag and get no warnings. I've run it with PIX and grabbed a frame when it was blank and it showed all device/swapchains etc as alive and showed me the render frame. It's just not appearing on the window.

If anyone can shed some light on this weird behaviour or offer insights I'd appreciate it.

Also need any more information I'll be happy to provide.

Extra info
win7 64bit, app is win32
dx sdk June 2010

Share this post


Link to post
Share on other sites
Not sure if it fixes your problem, but you really should pass on messages to DefWindowProc unless you can safely return. You have to look the messages up in MSDN to see if this is the case.

In general, you always should pass messages on to DefWindowProc unless you explicitely don't have to for overriding default behaviour.

Share this post


Link to post
Share on other sites
[quote name='Endurion' timestamp='1298305818' post='4777076']
Not sure if it fixes your problem, but you really should pass on messages to DefWindowProc unless you can safely return. You have to look the messages up in MSDN to see if this is the case.

In general, you always should pass messages on to DefWindowProc unless you explicitely don't have to for overriding default behaviour.
[/quote]

Yeah its been changing a lot the past few days with various debugging ideas, swapped it back to your suggestion but the overall problem remains. (Thanks for the fast reply!)

Share this post


Link to post
Share on other sites
You might try presenting (not drawing to, just presenting) the backbuffer in your WM_PAINT handler after you validate the update region. EDIT: be sure to check for a valid device before you do that, as WM_PAINT will likely get called at least once before you have DX setup.

Share this post


Link to post
Share on other sites
[quote name='Buckeye' timestamp='1298306652' post='4777090']
You might try presenting (not drawing to, just presenting) the backbuffer in your WM_PAINT handler after you validate the update region. EDIT: be sure to check for a valid device before you do that, as WM_PAINT will likely get called at least once before you have DX setup.
[/quote]

I tried your suggestion, quickly made a function that simply called Present after EndPaint, this keeps the windowed app from drawing always when dragging resize but the main weird issue remains.

Share this post


Link to post
Share on other sites
I've been reading the msdn docs regarding DXGI fullscreen swapping and the best practises.


[url="http://msdn.microsoft.com/en-us/library/ee417025(v=vs.85).aspx"]Msdn link[/url]

Could my issue be due to DXGI hanging on waiting for the message to go?

I'm not using any of my own threading code within the apps but the app is still responsive (it just isn't drawn on the window).

I know its responsive because swapping back to fullscreen shows the update to the mesh position.

[code]int WINAPI wWinMain( HINSTANCE hInst, HINSTANCE hPrevInst, LPWSTR lpCmdLine, int nCmdShow )
{
Game game;
HWND hWnd;

LRESULT CALLBACK wndProc( HWND, UINT, WPARAM, LPARAM );
bool setup(HINSTANCE hInst, HWND &hWnd, RECT rc, Game* game);

RECT rc = { 0, 0, 1024, 768 };
if(!setup(hInst,hWnd,rc, &game))
PostQuitMessage(0);
if(!game.setup(hWnd))
{
MessageBox( NULL, "Failed to setup stage", "Rob's Error", MB_OK );
PostQuitMessage(0);
}
ShowWindow(hWnd, nCmdShow );

MSG msg = {0};
while( WM_QUIT != msg.message )
{
if( PeekMessage( &msg, NULL, 0U, 0U, PM_REMOVE ) != 0)
{
game.getInput()->handle(&msg);
TranslateMessage( &msg );
DispatchMessage( &msg );
}
else
{
game.run();
}
}
return (int)msg.wParam;
}[/code]

I've added my message pump loop if that helps.

getInput()->handle just grabs all the keys pressed/mouse moved using VK_Keys it's also responsive even though the window is blank.

game.run() -> updates camera from the handled input and also runs render();




Share this post


Link to post
Share on other sites
On the June 2010 sdk I can get the same weirdness using alt-enter on tutorial 7. (the tutorial doesn't resize buffers and will trigger the warning)

However my friend using Radeon HD 5750 has no problems, so I got the latest driver package for my nvidia gtx 460 but the problem remains.

Ok, I quickly changed my shader to use one set of constant buffers and set them just before render like tutorial 6 and the problem disappears. No idea why multiple constant buffers is causing weird issues.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
      627694
    • Total Posts
      2978671
  • Similar Content

    • By evelyn4you
      hi,
      i have read very much about the binding of a constantbuffer to a shader but something is still unclear to me.
      e.g. when performing :   vertexshader.setConstantbuffer ( buffer,  slot )
       is the buffer bound
      a.  to the VertexShaderStage
      or
      b. to the VertexShader that is currently set as the active VertexShader
      Is it possible to bind a constantBuffer to a VertexShader e.g. VS_A and keep this binding even after the active VertexShader has changed ?
      I mean i want to bind constantbuffer_A  to VS_A, an Constantbuffer_B to VS_B  and  only use updateSubresource without using setConstantBuffer command every time.

      Look at this example:
      SetVertexShader ( VS_A )
      updateSubresource(buffer_A)
      vertexshader.setConstantbuffer ( buffer_A,  slot_A )
      perform drawcall       ( buffer_A is used )

      SetVertexShader ( VS_B )
      updateSubresource(buffer_B)
      vertexshader.setConstantbuffer ( buffer_B,  slot_A )
      perform drawcall   ( buffer_B is used )
      SetVertexShader ( VS_A )
      perform drawcall   (now which buffer is used ??? )
       
      I ask this question because i have made a custom render engine an want to optimize to
      the minimum  updateSubresource, and setConstantbuffer  calls
       
       
       
       
       
    • By noodleBowl
      I got a quick question about buffers when it comes to DirectX 11. If I bind a buffer using a command like:
      IASetVertexBuffers IASetIndexBuffer VSSetConstantBuffers PSSetConstantBuffers  and then later on I update that bound buffer's data using commands like Map/Unmap or any of the other update commands.
      Do I need to rebind the buffer again in order for my update to take effect? If I dont rebind is that really bad as in I get a performance hit? My thought process behind this is that if the buffer is already bound why do I need to rebind it? I'm using that same buffer it is just different data
       
    • By Rockmover
      I am really stuck with something that should be very simple in DirectX 11. 
      1. I can draw lines using a PC (position, colored) vertices and a simple shader just fine.
      2. I can draw 3D triangles using PCN (position, colored, normal) vertices just fine (even transparency and SpecularBlinnPhong shaders).
       
      However, if I'm using my 3D shader, and I want to draw my PC lines in the same scene how can I do that?
       
      If I change my lines to PCN and pass them to the 3D shader with my triangles, then the lighting screws them all up.  I only want the lighting for the 3D triangles, but no SpecularBlinnPhong/Lighting for the lines (just PC). 
      I am sure this is because if I change the lines to PNC there is not really a correct "normal" for the lines.  
      I assume I somehow need to draw the 3D triangles using one shader, and then "switch" to another shader and draw the lines?  But I have no clue how to use two different shaders in the same scene.  And then are the lines just drawn on top of the triangles, or vice versa (maybe draw order dependent)?  
      I must be missing something really basic, so if anyone can just point me in the right direction (or link to an example showing the implementation of multiple shaders) that would be REALLY appreciated.
       
      I'm also more than happy to post my simple test code if that helps as well!
       
      THANKS SO MUCH IN ADVANCE!!!
    • By Reitano
      Hi,
      I am writing a linear allocator of per-frame constants using the DirectX 11.1 API. My plan is to replace the traditional constant allocation strategy, where most of the work is done by the driver behind my back, with a manual one inspired by the DirectX 12 and Vulkan APIs.
      In brief, the allocator maintains a list of 64K pages, each page owns a constant buffer managed as a ring buffer. Each page has a history of the N previous frames. At the beginning of a new frame, the allocator retires the frames that have been processed by the GPU and frees up the corresponding space in each page. I use DirectX 11 queries for detecting when a frame is complete and the ID3D11DeviceContext1::VS/PSSetConstantBuffers1 methods for binding constant buffers with an offset.
      The new allocator appears to be working but I am not 100% confident it is actually correct. In particular:
      1) it relies on queries which I am not too familiar with. Are they 100% reliable ?
      2) it maps/unmaps the constant buffer of each page at the beginning of a new frame and then writes the mapped memory as the frame is built. In pseudo code:
      BeginFrame:
          page.data = device.Map(page.buffer)
          device.Unmap(page.buffer)
      RenderFrame
          Alloc(size, initData)
              ...
              memcpy(page.data + page.start, initData, size)
          Alloc(size, initData)
              ...
              memcpy(page.data + page.start, initData, size)
      (Note: calling Unmap at the end of a frame prevents binding the mapped constant buffers and triggers an error in the debug layer)
      Is this valid ? 
      3) I don't fully understand how many frames I should keep in the history. My intuition says it should be equal to the maximum latency reported by IDXGIDevice1::GetMaximumFrameLatency, which is 3 on my machine. But, this value works fine in an unit test while on a more complex demo I need to manually set it to 5, otherwise the allocator starts overwriting previous frames that have not completed yet. Shouldn't the swap chain Present method block the CPU in this case ?
      4) Should I expect this approach to be more efficient than the one managed by the driver ? I don't have meaningful profile data yet.
      Is anybody familiar with the approach described above and can answer my questions and discuss the pros and cons of this technique based on his experience ? 
      For reference, I've uploaded the (WIP) allocator code at https://paste.ofcode.org/Bq98ujP6zaAuKyjv4X7HSv.  Feel free to adapt it in your engine and please let me know if you spot any mistakes
      Thanks
      Stefano Lanza
       
    • By Matt Barr
      Hey all. I've been working with compute shaders lately, and was hoping to build out some libraries to reuse code. As a prerequisite for my current project, I needed to sort a big array of data in my compute shader, so I was going to implement quicksort as a library function. My implementation was going to use an inout array to apply the changes to the referenced array.

      I spent half the day yesterday debugging in visual studio before I realized that the solution, while it worked INSIDE the function, reverted to the original state after returning from the function.

      My hack fix was just to inline the code, but this is not a great solution for the future.  Any ideas? I've considered just returning an array of ints that represents the sorted indices.
  • Popular Now