Sign in to follow this  

DX11 DirectX11 Depth Buffer Problem (solved)

Recommended Posts

Hello everyone,
I have this problem with my depth buffer and all the solutions from the countless other threads with this problem do not seem to work for me.


I use the same code as shown here: [url=""]http://www.rastertek.../dx11tut03.html[/url]

[i]Global Variables:[/i]
extern ID3D11Device* pDevice;
extern ID3D11DeviceContext* pDevCon;
extern ID3D11RenderTargetView* pRenderTargetView;
extern ID3D11DepthStencilState* pDepthStencilState;
extern ID3D11DepthStencilView* pDepthStencilView;
extern ID3D11Texture2D* pDepthStencilBuffer;
extern ID3D11RasterizerState* pRasterState;

[i]Direct3D initialisation:[/i]
HRESULT result;

D3D11_TEXTURE2D_DESC depthBufferDesc;
depthBufferDesc.Width = Width;
depthBufferDesc.Height = Height;
depthBufferDesc.MipLevels = 1;
depthBufferDesc.ArraySize = 1;
depthBufferDesc.Format = DXGI_FORMAT_D24_UNORM_S8_UINT;
depthBufferDesc.SampleDesc.Count = 1;
depthBufferDesc.SampleDesc.Quality = 0;
depthBufferDesc.Usage = D3D11_USAGE_DEFAULT;
depthBufferDesc.BindFlags = D3D11_BIND_DEPTH_STENCIL;
depthBufferDesc.CPUAccessFlags = 0;
depthBufferDesc.MiscFlags = 0;

result = pDevice->CreateTexture2D(&depthBufferDesc, NULL, &pDepthStencilBuffer);

MessageBox(NULL, L"Error1", L"Error", MB_OK | MB_ICONERROR);

D3D11_DEPTH_STENCIL_DESC depthStencilDesc;
ZeroMemory(&depthStencilDesc, sizeof(D3D11_DEPTH_STENCIL_DESC));
// Depth test parameters
depthStencilDesc.DepthEnable = true;
depthStencilDesc.DepthWriteMask = D3D11_DEPTH_WRITE_MASK_ALL;
depthStencilDesc.DepthFunc = D3D11_COMPARISON_LESS;
// Stencil test parameters
depthStencilDesc.StencilEnable = true;
depthStencilDesc.StencilReadMask = 0xFF;
depthStencilDesc.StencilWriteMask = 0xFF;
// Stencil operations if pixel is front-facing
depthStencilDesc.FrontFace.StencilFailOp = D3D11_STENCIL_OP_KEEP;
depthStencilDesc.FrontFace.StencilDepthFailOp = D3D11_STENCIL_OP_INCR;
depthStencilDesc.FrontFace.StencilPassOp = D3D11_STENCIL_OP_KEEP;
depthStencilDesc.FrontFace.StencilFunc = D3D11_COMPARISON_ALWAYS;
// Stencil operations if pixel is back-facing.
depthStencilDesc.BackFace.StencilFailOp = D3D11_STENCIL_OP_KEEP;
depthStencilDesc.BackFace.StencilDepthFailOp = D3D11_STENCIL_OP_DECR;
depthStencilDesc.BackFace.StencilPassOp = D3D11_STENCIL_OP_KEEP;
depthStencilDesc.BackFace.StencilFunc = D3D11_COMPARISON_ALWAYS;

result = pDevice->CreateDepthStencilState(&depthStencilDesc, &pDepthStencilState);
pDevCon->OMSetDepthStencilState(pDepthStencilState, 1);

MessageBox(NULL, L"Error2", L"Error", MB_OK | MB_ICONERROR);

D3D11_DEPTH_STENCIL_VIEW_DESC depthStencilViewDesc;
ZeroMemory(&depthStencilViewDesc, sizeof(D3D11_DEPTH_STENCIL_VIEW_DESC));
depthStencilViewDesc.Format = DXGI_FORMAT_D24_UNORM_S8_UINT;
depthStencilViewDesc.ViewDimension = D3D11_DSV_DIMENSION_TEXTURE2D;
depthStencilViewDesc.Texture2D.MipSlice = 0;
result = pDevice->CreateDepthStencilView(pDepthStencilBuffer, &depthStencilViewDesc, &pDepthStencilView);
pDevCon->OMSetRenderTargets(1, &pRenderTargetView, pDepthStencilView);

MessageBox(NULL, L"Error3", L"Error", MB_OK | MB_ICONERROR);

rasterDesc.AntialiasedLineEnable = false;
rasterDesc.CullMode = D3D11_CULL_BACK;
rasterDesc.DepthBias = 0;
rasterDesc.DepthBiasClamp = 0.0f;
rasterDesc.DepthClipEnable = true;
rasterDesc.FillMode = D3D11_FILL_SOLID;
rasterDesc.FrontCounterClockwise = false;
rasterDesc.MultisampleEnable = false;
rasterDesc.ScissorEnable = false;
rasterDesc.SlopeScaledDepthBias = 0.0f;

result = pDevice->CreateRasterizerState(&rasterDesc, &pRasterState);

MessageBox(NULL, L"Error4", L"Error", MB_OK | MB_ICONERROR);

D3D11_VIEWPORT viewport;
ZeroMemory(&viewport, sizeof(D3D11_VIEWPORT));
viewport.TopLeftX = 0;
viewport.TopLeftY = 0;
viewport.Width = Width;
viewport.Height = Height;
viewport.MinDepth = 0.0f;
viewport.MaxDepth = 1.0f;

pDevCon->RSSetViewports(1, &viewport);

[i]Camera Code:[/i]
m_pV3Pos = &Position;
m_pV3LookAt = &LookAt;
m_pV3View = (D3DXVECTOR3*)malloc(sizeof(D3DXVECTOR3));
m_pV3Up = (D3DXVECTOR3*)malloc(sizeof(D3DXVECTOR3));
*m_pV3View = *m_pV3Pos - *m_pV3LookAt;
D3DXVec3Normalize(m_pV3View, m_pV3View);
D3DXVec3Cross(m_pV3Up, &D3DXVECTOR3(0,1,0), m_pV3View);
D3DXVec3Cross(m_pV3Up, m_pV3View, m_pV3Up);
m_pMatView = (D3DXMATRIX*)malloc(sizeof(D3DXMATRIX));
m_pMatProj = (D3DXMATRIX*)malloc(sizeof(D3DXMATRIX));

D3DXVec3Normalize(m_pV3Up, m_pV3Up);
D3DXMatrixLookAtLH(m_pMatView, m_pV3Pos, m_pV3LookAt, m_pV3Up);
D3DXMatrixPerspectiveFovLH(m_pMatProj, FOV, (float)Width/Height, 1.0f, 1000.0f);

[i]Draw Code:[/i]
D3DXCOLOR bgColor( 0, 0.2f, 0.4f, 1.0f );
pDevCon->ClearRenderTargetView(pRenderTargetView, bgColor);
pDevCon->ClearDepthStencilView(pDepthStencilView, D3D11_CLEAR_DEPTH|D3D11_CLEAR_STENCIL, 1.0f, 0);
pSwapChain->Present(0, 0);

I realy have no ideas left so if anyone could help me with this issue I would be most grateful [img][/img] Edited by Rudi Media

Share this post

Link to post
Share on other sites
Wow D3D11 looks alot different than D3D9 o.O. In the link you gave, he didnt use the flag '[b]D3D11_CLEAR_STENCIL[/b]', maybe take that out and try again.

Draw Code:
D3DXCOLOR bgColor( 0, 0.2f, 0.4f, 1.0f );
pDevCon->ClearRenderTargetView(pRenderTargetView, bgColor);
pDevCon->ClearDepthStencilView(pDepthStencilView, D3D11_CLEAR_DEPTH| D3D11_CLEAR_STENCIL, 1.0f, 0);
pSwapChain->Present(0, 0);
[/code] Edited by Muzzy A

Share this post

Link to post
Share on other sites
[color=#000000]pDevCon[/color][color=#666600]->[/color][color=#660066]OMSetDepthStencilState[/color][color=#666600]([/color][color=#000000]pDepthStencilState[/color][color=#666600],[/color][color=#000000] [/color][color=#006666]1[/color][color=#666600]);[/color]

[color=#000000] [/color][color=#660066]MessageBox[/color][color=#666600]([/color][color=#000000]NULL[/color][color=#666600],[/color][color=#000000] L[/color][color=#008800]"Error2"[/color][color=#666600],[/color][color=#000000] L[/color][color=#008800]"Error"[/color][color=#666600],[/color][color=#000000] MB_OK [/color][color=#666600]|[/color][color=#000000] MB_ICONERROR[/color][color=#666600]);[/color]

Your error handling code at least doens't work as it should. You don't seems to update your result variable.
Also, enable d3d debugging to see any error messages in the debug window.

Otherwise, it seems that you z-buffer doesn't work as intended. As if it wasn't bound or z-testing is disabled.

You can also disable stencil testing at this point since you don't use it.

Best regards!

Share this post

Link to post
Share on other sites
Well [b]OMSetDepthStencilState[/b] doesn't return a [b]HRESULT[/b] value, which is why I don't update my result variable at this place.
Regarding d3d debugging I have actually no experience at all. I'm currently using the VS11 beta and heard that such a feature is already built-in but it seems like you're only able to use it if you have Windows 8 installed. Is there any other way to debug your d3d applications?

Share this post

Link to post
Share on other sites
Go to the DirectX control panel (it should be findable by just typing "DirectX Control Panel" in your Start menu) and enable debugging from there.

One potential problem however that I can see is that you're creating and setting your depth testing state before you create your depth/stencil view - maybe try doing it after instead and see what happens?

Share this post

Link to post
Share on other sites

Other things to verify:

- by any chance, are you using a multisampled back buffer? if so, AFAIK, the depth buffer has to be multisampled too
- depth buffer resolution has to be same as back buffer resolution

- Enable the d3d debug as instructed earlier (works on Win7 too). If there is that kind of problem, it should be able to tell you about it.


Share this post

Link to post
Share on other sites
[quote name='kauna' timestamp='1335874932' post='4936398']
- by any chance, are you using a multisampled back buffer? if so, AFAIK, the depth buffer has to be multisampled too

Hey thank you that was my problem [img][/img]

Share this post

Link to post
Share on other sites

glad to be able to help. I got the idea from looking your screenshot which seemed to be multisampled :)

Best regards!

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  

  • Partner Spotlight

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By evelyn4you
      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
      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 )
      vertexshader.setConstantbuffer ( buffer_A,  slot_A )
      perform drawcall       ( buffer_A is used )

      SetVertexShader ( VS_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!
    • By Reitano
      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:
 = device.Map(page.buffer)
          Alloc(size, initData)
              memcpy( + page.start, initData, size)
          Alloc(size, initData)
              memcpy( + 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  Feel free to adapt it in your engine and please let me know if you spot any mistakes
      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