# DX11 [SharpDX] Understanding DX11 blend states

## Recommended Posts

cephalo    739

In dx9, the blend state was fairly simple. In dx11, it's a lot more complicated and I'm having trouble understanding how I need to have it set. I have a small app that is supposed to draw several instances of tessellated bezier triangles, and even though I have the pixel shader set to just paint one color, I'm not seeing that color on my screen at all. I've looked at my app with PIX (I use VS 2012 Express so it's my only debugging option for now.) and my vertex buffers seem to be doing what they are supposed to.

Right now I'm wondering about the blend state because I don't fully understand it. Here is how I have it set in my render method:

            RenderTargetBlendDescription rendBlendDesc = new RenderTargetBlendDescription();
rendBlendDesc.SourceAlphaBlend = BlendOption.One;
rendBlendDesc.DestinationAlphaBlend = BlendOption.Zero;
rendBlendDesc.SourceBlend = BlendOption.One;
rendBlendDesc.DestinationBlend = BlendOption.Zero;

BlendStateDescription blendDesc = new BlendStateDescription();
blendDesc.AlphaToCoverageEnable = false;
blendDesc.IndependentBlendEnable = false;
blendDesc.RenderTarget[0] = rendBlendDesc;

BlendState blendState = new BlendState(Game.GraphicsDevice, blendDesc);
Game.GraphicsDevice.ImmediateContext.OutputMerger.SetBlendState(blendState);



Do you see anything here that would prevent drawing from being visible?

##### Share on other sites
MJP    19755

Your blend state will result in the pixel shader value being written to the render target(s), and completely overwriting any existing contents of the render target. This is pretty standard for rendering without any blending. If you're not seeing your primitives, then the problem is probably somewhere else.

I would recommend enabling device debug messages if you haven't already, and checking for any warning or messages. Pass the "Debug" flag when creating your device to specify that you want messages, and then enable native debugging for your project. You should then get messages in your debugger output window. If you're using an express version of VS or you don't want to turn on native debugging, you can use a program like DebugView to view the native debugger output stream.

##### Share on other sites
cephalo    739

I used to use DebugView for my dx9 stuff and it was very useful. This time though I'm not seeing any warnings in the DebugView window even though I have created my device with the debug option. Does dx11 have a messaging level like dx9 had? I haven't used DebugView for a couple of years, and I can't remember all the steps necessary to capture messages from my app.

##### Share on other sites
hunpro    1537

Do you see the triangles without this blending turned on?
If not, then 2 quick tips: forgot to transpose the viewprojection matrix, or forgot to set some constant buffer to the proper shaders. At least those are my main 2 sources of pain nowadays.

You can turn on dx debug in sdk->utilities->Directx control panel, if you haven't already. I got some usefull info about not setting the proper patch type for my hull shader, which made the driver reset, so it can be usefull,but not a magic bullet.

##### Share on other sites
MJP    19755

I used to use DebugView for my dx9 stuff and it was very useful. This time though I'm not seeing any warnings in the DebugView window even though I have created my device with the debug option. Does dx11 have a messaging level like dx9 had? I haven't used DebugView for a couple of years, and I can't remember all the steps necessary to capture messages from my app.

There's not really a "message level" anymore. There's functionality to filter out certain warnings/errors using the ID3D11InfoQueue interface, but by default you get all possible warnings and errors.

If you're not getting any messages, then it's possible you're not causing any errors or warnings. To find out for sure, you could try to deliberately cause an error by passing an incorrect parameter to a function, or something like that.

##### Share on other sites
AlexandreMutel    1105

You will be able to see D3D11 messages directly from the output window if you check "Enable native code debugging" in the Project Properties/Debug tab (you need to use the debugger to see the messages) otherwise DebugView is still an option.

##### Share on other sites
cephalo    739

Thanks everyone, of course things are made worse by the fact that I have to stick with express version of VS for now. Very hard to learn dx11 with express.

##### Share on other sites
cephalo    739

You will be able to see D3D11 messages directly from the output window if you check "Enable native code debugging" in the Project Properties/Debug tab (you need to use the debugger to see the messages) otherwise DebugView is still an option.

Oh my gosh! This is working with express! Somebody told me it wouldn't. Now I have about 100 pages of warnings to examine. Thanks!

##### Share on other sites

You may find it useful to have the debugger break on those warnings, in which case take a look at http://blogs.msdn.com/b/chuckw/archive/2012/11/30/direct3d-sdk-debug-layer-tricks.aspx

I'm not sure how easy it would be to interface with that API from C# though, as the SharpDX implementation looks incomplete.

##### Share on other sites
AlexandreMutel    1105

I'm not sure how easy it would be to interface with that API from C# though, as the SharpDX implementation looks incomplete.

It is not incomplete, the class is marked as "partial" so the other part of the code is generated at built time by the DirectX C++ to C# code generator used in SharpDX.

Edit: Though there are here some NotImplementedException for GetStorageFilter/GetRetrievalFilter, will have to double check :D

Edited by xoofx

## Create an account

Register a new account

• ### Similar Content

• By isu diss
I'm trying to code Rayleigh part of Nishita's model (Display Method of the Sky Color Taking into Account Multiple Scattering). I get black screen no colors. Can anyone find the issue for me?

• By Endurion
I have a gaming framework with an renderer interface. Those support DX8, DX9 and latest, DX11. Both DX8 and DX9 use fixed function pipeline, while DX11 obviously uses shaders. I've got most of the parts working fine, as in I can switch renderers and notice almost no difference. The most advanced features are 2 directional lights with a single texture
My last problem is lighting; albeit there's documentation on the D3D lighting model I still can't get the behaviour right. My mistake shows most prominently in the dark side opposite the lights. I'm pretty sure the ambient calculation is off, but that one's supposed to be the most simple one and should be hard to get wrong.
Interestingly I've been searching high and low, and have yet to find a resource that shows how to build a HLSL shader where diffuse, ambient and specular are used together with material properties. I've got various shaders for all the variations I'm supporting. I stepped through the shader with the graphics debugger, but the calculation seems to do what I want. I'm just not sure the formula is correct.
This one should suffice though, it's doing two directional lights, texture modulated with vertex color and a normal. Maybe someone can spot one (or more mistakes). And yes, this is in the vertex shader and I'm aware lighting will be as "bad" as in fixed function; that's my goal currently.
• By Mercesa
Hey folks. So I'm having this problem in which if my camera is close to a surface, the SSAO pass suddenly spikes up to around taking 16 milliseconds.
When still looking towards the same surface, but less close. The framerate resolves itself and becomes regular again.
This happens with ANY surface of my model, I am a bit clueless in regards to what could cause this. Any ideas?
In attached image: y axis is time in ms, x axis is current frame. The dips in SSAO milliseconds are when I moved away from the surface, the peaks happen when I am very close to the surface.

Edit: So I've done some more in-depth profiling with Nvidia nsight. So these are the facts from my results
Count of command buffers goes from 4 (far away from surface) to ~20(close to surface).
The command buffer duration in % goes from around ~30% to ~99%
Sometimes the CPU duration takes up to 0.03 to 0.016 milliseconds per frame while comparatively usually it takes around 0.002 milliseconds.
I am using a vertex shader which generates my full-screen quad and afterwards I do my SSAO calculations in my pixel shader, could this be a GPU driver bug? I'm a bit lost myself. It seems there could be a CPU/GPU resource stall. But why would the amount of command buffers be variable depending on distance from a surface?

Edit n2: Any resolution above 720p starts to have this issue, and I am fairly certain my SSAO is not that performance heavy it would crap itself at a bit higher resolutions.

• In DirectX 11 we have a 24 bit integer depth + 8bit stencil format for depth-stencil resources ( DXGI_FORMAT_D24_UNORM_S8_UINT ). However, in an AMD GPU documentation for consoles I have seen they mentioned, that internally this format is implemented as a 64 bit resource with 32 bits for depth (but just truncated for 24 bits) and 32 bits for stencil (truncated to 8 bits). AMD recommends using a 32 bit floating point depth buffer instead with 8 bit stencil which is this format: DXGI_FORMAT_D32_FLOAT_S8X24_UINT.
Does anyone know why this is? What is the usual way of doing this, just follow the recommendation and use a 64 bit depthstencil? Are there performance considerations or is it just recommended to not waste memory? What about Nvidia and Intel, is using a 24 bit depthbuffer relevant on their hardware?
Cheers!

• By gsc
Hi! I am trying to implement simple SSAO postprocess. The main source of my knowledge on this topic is that awesome tutorial.
But unfortunately something doesn't work... And after a few long hours I need some help. Here is my hlsl shader:
float3 randVec = _noise * 2.0f - 1.0f; // noise: vec: {[0;1], [0;1], 0} float3 tangent = normalize(randVec - normalVS * dot(randVec, normalVS)); float3 bitangent = cross(tangent, normalVS); float3x3 TBN = float3x3(tangent, bitangent, normalVS); float occlusion = 0.0; for (int i = 0; i < kernelSize; ++i) { float3 samplePos = samples[i].xyz; // samples: {[-1;1], [-1;1], [0;1]} samplePos = mul(samplePos, TBN); samplePos = positionVS.xyz + samplePos * ssaoRadius; float4 offset = float4(samplePos, 1.0f); offset = mul(offset, projectionMatrix); offset.xy /= offset.w; offset.y = -offset.y; offset.xy = offset.xy * 0.5f + 0.5f; float sampleDepth = tex_4.Sample(textureSampler, offset.xy).a; sampleDepth = vsPosFromDepth(sampleDepth, offset.xy).z; const float threshold = 0.025f; float rangeCheck = abs(positionVS.z - sampleDepth) < ssaoRadius ? 1.0 : 0.0; occlusion += (sampleDepth <= samplePos.z + threshold ? 1.0 : 0.0) * rangeCheck; } occlusion = saturate(1 - (occlusion / kernelSize)); And current result: http://imgur.com/UX2X1fc
I will really appreciate for any advice!

• 9
• 24
• 16
• 19
• 10