• Advertisement
Sign in to follow this  

DX11 How to enable MSAA in DirectX 11

This topic is 1824 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts



I remember that it was quite easy to turn it on in DirectX 9.0, but unfortunately I can't make it working with DX11. The MSDN says:



"The settings of the MultisampleEnable and AntialiasedLineEnable members apply only to multisample antialiasing (MSAA) render targets (that is, render targets with sample counts greater than 1)."


therefore we can deduce that we have to change appropriate properties in the rasterizer (MultisampleEnable and AntialiasedLineEnable) and increase the SampleDesc.Count value for a render target, so my changes are like this:


main render target:


D3D11_TEXTURE2D_DESC _depthBufferDesc;
ZeroMemory( &_depthBufferDesc, sizeof( D3D11_TEXTURE2D_DESC ) );
_depthBufferDesc.Width = uScreenWidth;
_depthBufferDesc.Height = uScreenHeight;
_depthBufferDesc.MipLevels = 1;
_depthBufferDesc.ArraySize = 1;
_depthBufferDesc.Format = DXGI_FORMAT_D24_UNORM_S8_UINT;
_depthBufferDesc.SampleDesc.Count = 2; // increased value to 2
_depthBufferDesc.SampleDesc.Quality = 0;
_depthBufferDesc.Usage = D3D11_USAGE_DEFAULT;
_depthBufferDesc.BindFlags = D3D11_BIND_DEPTH_STENCIL;
_depthBufferDesc.CPUAccessFlags = 0;
_depthBufferDesc.MiscFlags = 0;

_result = m_device->CreateTexture2D( &_depthBufferDesc, NULL, &m_depthStencilBuffer );
if( FAILED( _result ) ) {
return false;




D3D11_RASTERIZER_DESC _rasterDesc;
_rasterDesc.AntialiasedLineEnable = true; // changed to true
_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 = true; // changed to true
_rasterDesc.ScissorEnable = false;
_rasterDesc.SlopeScaledDepthBias = 0.0f;

_result = m_device->CreateRasterizerState( &_rasterDesc, &m_rasterState );
if( FAILED( _result ) ) {
return false;


however it fails while creating depth stencil view:


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 = m_device->CreateDepthStencilView( m_depthStencilBuffer, &_depthStencilViewDesc, &m_depthStencilView );
if( FAILED( _result ) ) {
return false;


why? I tried to increase the Count value in the swap chain but then I have just black screen and nothing more.


Thank you for some help.

Share this post

Link to post
Share on other sites
The sample count and quality of the render target/swap chain and the depth stencil view have to be the same.
Can you post the render target/swap chain texture desc?

Is the D3D debug layer printing any warning or error message?


Also make sure that your GPU supports that sample count/quality pair.
Use ID3D11Device::CheckMultisampleQualityLevels Method to check support. Edited by TiagoCosta

Share this post

Link to post
Share on other sites

Thank you for your interest.


The sample count and quality of the render target/swap chain and the depth stencil view have to be the same.


Ok, I have changed it in swap chain to 2 as well, but it still fails.


Can you post the render target/swap chain texture desc?

render target is already posted, isn't it? (it is_depthBufferDesc, right?), the swap chain is:


ZeroMemory( &_swapChainDesc, sizeof( DXGI_SWAP_CHAIN_DESC ) );
_swapChainDesc.BufferCount = 1;
_swapChainDesc.BufferDesc.Width = uScreenWidth;
_swapChainDesc.BufferDesc.Height = uScreenHeight;
_swapChainDesc.BufferDesc.Format = DXGI_FORMAT_R8G8B8A8_UNORM;
_swapChainDesc.BufferDesc.RefreshRate.Numerator = 0;
_swapChainDesc.BufferDesc.RefreshRate.Denominator = 1;
_swapChainDesc.OutputWindow = hWnd;
_swapChainDesc.SampleDesc.Count = 2; // changed to 2
_swapChainDesc.SampleDesc.Quality = 0;
if( isFullscreen )
_swapChainDesc.Windowed = false;
_swapChainDesc.Windowed = true;

_result = D3D11CreateDeviceAndSwapChain( NULL,
        NULL, NULL, NULL, 0, 
        &m_deviceContext );



Is the D3D debug layer printing any warning or error message?


I am getting "_com_error at memory location" in the output in VS2012



Also make sure that your GPU supports that sample count/quality pair.
Use ID3D11Device::CheckMultisampleQualityLevels Method to check support.


I have GF 8800GT and I can't believe it doesn't support MSAA 2x, altough I have used the method like this:


_result = m_device->CheckMultisampleQualityLevels( DXGI_FORMAT_R8G8B8A8_UNORM, 2, &a );


and the result is S_OK.

Share this post

Link to post
Share on other sites
the "a" variable has value 1.

Sorry for the second post, but editing a post with some codes is kinda broken.


Ok I finally made this working.

the value 1 in "a" means that it handles only "0" quality level (from what I have read over the Internet), I tried giving there 4 and it returned me 17 (so 0 to 16 quality?) in the variable a. So I set the sample count to 4 and quality to 1.

furthermore I had to change in depth stencil view the value D3D11_DSV_DIMENSION_TEXTURE2D to D3D11_DSV_DIMENSION_TEXTURE2DMS. Edited by jajcek

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By AxeGuywithanAxe
      I wanted to see how others are currently handling descriptor heap updates and management.
      I've read a few articles and there tends to be three major strategies :
      1 ) You split up descriptor heaps per shader stage ( i.e one for vertex shader , pixel , hull, etc)
      2) You have one descriptor heap for an entire pipeline
      3) You split up descriptor heaps for update each update frequency (i.e EResourceSet_PerInstance , EResourceSet_PerPass , EResourceSet_PerMaterial, etc)
      The benefits of the first two approaches is that it makes it easier to port current code, and descriptor / resource descriptor management and updating tends to be easier to manage, but it seems to be not as efficient.
      The benefits of the third approach seems to be that it's the most efficient because you only manage and update objects when they change.
    • By evelyn4you
      until now i use typical vertexshader approach for skinning with a Constantbuffer containing the transform matrix for the bones and an the vertexbuffer containing bone index and bone weight.
      Now i have implemented realtime environment  probe cubemaping so i have to render my scene from many point of views and the time for skinning takes too long because it is recalculated for every side of the cubemap.
      For Info i am working on Win7 an therefore use one Shadermodel 5.0 not 5.x that have more options, or is there a way to use 5.x in Win 7
      My Graphic Card is Directx 12 compatible NVidia GTX 960
      the member turanszkij has posted a good for me understandable compute shader. ( for Info: in his engine he uses an optimized version of it )
      Now my questions
       is it possible to feed the compute shader with my orignial vertexbuffer or do i have to copy it in several ByteAdressBuffers as implemented in the following code ?
        the same question is about the constant buffer of the matrixes
       my more urgent question is how do i feed my normal pipeline with the result of the compute Shader which are 2 RWByteAddressBuffers that contain position an normal
      for example i could use 2 vertexbuffer bindings
      1 containing only the uv coordinates
      2.containing position and normal
      How do i copy from the RWByteAddressBuffers to the vertexbuffer ?
      (Code from turanszkij )
      Here is my shader implementation for skinning a mesh in a compute shader:
      1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 struct Bone { float4x4 pose; }; StructuredBuffer<Bone> boneBuffer;   ByteAddressBuffer vertexBuffer_POS; // T-Pose pos ByteAddressBuffer vertexBuffer_NOR; // T-Pose normal ByteAddressBuffer vertexBuffer_WEI; // bone weights ByteAddressBuffer vertexBuffer_BON; // bone indices   RWByteAddressBuffer streamoutBuffer_POS; // skinned pos RWByteAddressBuffer streamoutBuffer_NOR; // skinned normal RWByteAddressBuffer streamoutBuffer_PRE; // previous frame skinned pos   inline void Skinning(inout float4 pos, inout float4 nor, in float4 inBon, in float4 inWei) {  float4 p = 0, pp = 0;  float3 n = 0;  float4x4 m;  float3x3 m3;  float weisum = 0;   // force loop to reduce register pressure  // though this way we can not interleave TEX - ALU operations  [loop]  for (uint i = 0; ((i &lt; 4) &amp;&amp; (weisum&lt;1.0f)); ++i)  {  m = boneBuffer[(uint)inBon].pose;  m3 = (float3x3)m;   p += mul(float4(pos.xyz, 1), m)*inWei;  n += mul(nor.xyz, m3)*inWei;   weisum += inWei;  }   bool w = any(inWei);  pos.xyz = w ? p.xyz : pos.xyz;  nor.xyz = w ? n : nor.xyz; }   [numthreads(1024, 1, 1)] void main( uint3 DTid : SV_DispatchThreadID ) {  const uint fetchAddress = DTid.x * 16; // stride is 16 bytes for each vertex buffer now...   uint4 pos_u = vertexBuffer_POS.Load4(fetchAddress);  uint4 nor_u = vertexBuffer_NOR.Load4(fetchAddress);  uint4 wei_u = vertexBuffer_WEI.Load4(fetchAddress);  uint4 bon_u = vertexBuffer_BON.Load4(fetchAddress);   float4 pos = asfloat(pos_u);  float4 nor = asfloat(nor_u);  float4 wei = asfloat(wei_u);  float4 bon = asfloat(bon_u);   Skinning(pos, nor, bon, wei);   pos_u = asuint(pos);  nor_u = asuint(nor);   // copy prev frame current pos to current frame prev pos streamoutBuffer_PRE.Store4(fetchAddress, streamoutBuffer_POS.Load4(fetchAddress)); // write out skinned props:  streamoutBuffer_POS.Store4(fetchAddress, pos_u);  streamoutBuffer_NOR.Store4(fetchAddress, nor_u); }  
    • By mister345
      Hi, can someone please explain why this is giving an assertion EyePosition!=0 exception?
      _lightBufferVS->viewMatrix = DirectX::XMMatrixLookAtLH(XMLoadFloat3(&_lightBufferVS->position), XMLoadFloat3(&_lookAt), XMLoadFloat3(&up));
      It looks like DirectX doesnt want the 2nd parameter to be a zero vector in the assertion, but I passed in a zero vector with this exact same code in another program and it ran just fine. (Here is the version of the code that worked - note XMLoadFloat3(&m_lookAt) parameter value is (0,0,0) at runtime - I debugged it - but it throws no exceptions.
          m_viewMatrix = DirectX::XMMatrixLookAtLH(XMLoadFloat3(&m_position), XMLoadFloat3(&m_lookAt), XMLoadFloat3(&up)); Here is the repo for the broken code (See LightClass) https://github.com/mister51213/DirectX11Engine/blob/master/DirectX11Engine/LightClass.cpp
      and here is the repo with the alternative version of the code that is working with a value of (0,0,0) for the second parameter.
    • By mister345
      Hi, can somebody please tell me in clear simple steps how to debug and step through an hlsl shader file?
      I already did Debug > Start Graphics Debugging > then captured some frames from Visual Studio and
      double clicked on the frame to open it, but no idea where to go from there.
      I've been searching for hours and there's no information on this, not even on the Microsoft Website!
      They say "open the  Graphics Pixel History window" but there is no such window!
      Then they say, in the "Pipeline Stages choose Start Debugging"  but the Start Debugging option is nowhere to be found in the whole interface.
      Also, how do I even open the hlsl file that I want to set a break point in from inside the Graphics Debugger?
      All I want to do is set a break point in a specific hlsl file, step thru it, and see the data, but this is so unbelievably complicated
      and Microsoft's instructions are horrible! Somebody please, please help.

    • By mister345
      I finally ported Rastertek's tutorial # 42 on soft shadows and blur shading. This tutorial has a ton of really useful effects and there's no working version anywhere online.
      Unfortunately it just draws a black screen. Not sure what's causing it. I'm guessing the camera or ortho matrix transforms are wrong, light directions, or maybe texture resources not being properly initialized.  I didnt change any of the variables though, only upgraded all types and functions DirectX3DVector3 to XMFLOAT3, and used DirectXTK for texture loading. If anyone is willing to take a look at what might be causing the black screen, maybe something pops out to you, let me know, thanks.
      Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.
  • Advertisement