# DX11 Directx11 return code definition

## Recommended Posts

senpegasus    228
I'm using windows 8 with DirectX11 to create a desktop application.

The function D3D11CreateDeviceAndSwapChain has several possible return codes as described here.

Although I can check for many of them, the ones starting with D3DERR_, like D3DERR_INVALIDCALL are not defined.

Googling a bit I found out they should be defined in D3DX11core.h, which is not included in the sdk.

Am I missing something?

##### Share on other sites
NightCreature83    5002

If you include d3d11.h that should be enough as that should include all of what you need, you might need to include dxgi.h as well.

##### Share on other sites
senpegasus    228

I'm including the following, but it still can't find the definition.

#include <dxgi.h>
#include <d3dcommon.h>
#include <d3d11_1.h>
#include <d3dcompiler.h>


##### Share on other sites
Norman Barrows    7179
just use #include <d3dx11.h> (or 11_1 if there is such a thing)

this may not get you the compiler though. it does gets you a DXGI device context, so it seems to include DXGI.

D3DERR_INVALIDCALL is defined in D3DX11core.h:

#define D3DERR_INVALIDCALL MAKE_D3DHRESULT(2156)

note that this is from the june 2010 sdk version of directx 11, not the win8 sdk version of dx11. there may be an 11.0 vs 11.1 version thing going on between them. Edited by Norman Barrows

##### Share on other sites
senpegasus    228

I searched the whole "windows kits\8.0\include" directory but the only definition of D3DERR_INVALIDCALL is inside d3d9helper.h.

Apparently the problem is just that the documentation is not updated about the fact that they dropped the error codes that begin with D3DERR_.

Inside winerror.h I could find all the definitions for dxgi, d3d10 and d3d11 errors, but they are named and defined differently, for example:

//
// DXGI error codes
//

//
// MessageId: DXGI_ERROR_INVALID_CALL
//
// MessageText:
//
// The application made a call that is invalid. Either the parameters of the call or the state of some object was incorrect.
// Enable the D3D debug layer in order to see details via debug messages.
//
#define DXGI_ERROR_INVALID_CALL          _HRESULT_TYPEDEF_(0x887A0001L)


where _HRESULT_TYPEDEF_ is just

#define _HRESULT_TYPEDEF_(_sc) ((HRESULT)_sc)


##### Share on other sites
Norman Barrows    7179

Apparently the problem is just that the documentation is not updated about the fact that they dropped the error codes that begin with D3DERR_.

i suspected something like this.

was there a specific directx 11.1 routine that said it returned d3derr_invalid call? no, cause you were using create dev & swap chain, just like i was a few days ago myself. so you were just trying to trap and process the documented return codes, eh?   too bad their docs suck.

as soon as i saw that create dev and swap chain returned s_ok instead of d3d_ok, i realized dx11 error codes are a whole new ballgame.

they apparently have both the june 2010 and win 8 docs posted on msdn, identical info. apparently true for june 2010 sdk, and not for win8 sdk. you may want to "send a comment to microsoft about this document".

##### Share on other sites
senpegasus    228

Yes, I was getting some errors so I wanted to catch all the possible return codes.

I sent a mail, hopefully they will update the documentation.

## 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!

• 15
• 13
• 15
• 10
• 18