# DX11 D3DCompileFromFile

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

## Recommended Posts

Hello!

I am stuck on tutorial 4 on this website: http://www.braynzarsoft.net/index.php?p=D3D11BD#still

Theese two lines are messing everything up for me:

hResult = D3DCompileFromFile(L"C:\\Users\\Dawood\\Documents\\Visual Studio 2013\\Projects\\Direct3D\\Direct3D\\Effects.fx", NULL, D3D_COMPILE_STANDARD_FILE_INCLUDE, NULL, "vs_5_0", 0, 0, &VS_Buffer, NULL);

hResult = D3DCompileFromFile(L"C:\\Users\\Dawood\\Documents\\Visual Studio 2013\\Projects\\Direct3D\\Direct3D\\Effects.fx", NULL, D3D_COMPILE_STANDARD_FILE_INCLUDE, NULL, "ps_5_0", 0, 0, &PS_Buffer, NULL);

I am not using the exact same code as he is using so please notice that. I have included my Effects.fx file in the project and also placed it where my .cpp and .h files are located for the project. I have also changed the properties->HLSL Compiler->General and there I changed the "shader type" to Effect (/fx) and the "shader model" to Shader Model 5 (/5_0)

I can't understand why this isn't working. The issue is that our VS_Buffer and PS_Buffer is still pointing to NULL after this line of code is done and the result of hResult is some weird numbers like "0x8876086c" and not "S_OK"

He has written the following lines just to save you some time in your search but I am not using that stuff since msdn doesn't recommend it anymore.

hr = D3DX11CompileFromFile(L"Effects.fx", 0, 0, "VS", "vs_4_0", 0, 0, 0, &VS_Buffer, 0, 0);
hr = D3DX11CompileFromFile(L"Effects.fx", 0, 0, "PS", "ps_4_0", 0, 0, 0, &PS_Buffer, 0, 0);

I have already tried changing the vs_5_0 to vs_4_0 but that is not the issue here.

Regards!

Edited by dawoodr

##### Share on other sites

the result of hResult is some weird numbers like "0x8876086c"

That's called an error code. 0x8876086c is the informative error "Invalid Call."

So.. you need to check each parameter for validity.

Do you have debug output enabled? You should be able to get more informative info from that. Or, add the error msgs blob parameter and get the error description from that.

- Is the file path correct?

- If you have "#include some-file" in your shader file, can they be found?

- Are VS_ and PS_BUFFER ID3DBlob* objects? I know, if they aren't, it shouldn't compile.

- Have you tried specifying the entry points explicitly?

- Try setting the shader flags to D3DCOMPILE_ENABLE_STRICTNESS | D3DCOMPILE_DEBUG.

I changed ... the "shader model" to Shader Model 5 (/5_0)

Is that supported? Do you have code in the fx file that needs 5_0? [shrug]

Edited by Buckeye

##### Share on other sites

http://msdn.microsoft.com/en-us/library/windows/desktop/hh446872%28v=vs.85%29.aspx

The last parameter is an ID3DBlob that will receive error messages that occur during the compilation.  Instead of setting it to NULL, I recommend that you actually use it; you can then use it's GetBufferPointer member to access those error messages and find out what went wrong.  Cast it to the appropriate char * or string type and print them, or whatever; e.g:

if (pErrorBlob) {OutputDebugString ((LPCTSTR) pErrorBlob->GetBufferPointer ()); pErrorBlob->Release ();}

##### Share on other sites

Ok, I created on ID3DBlob* pErrorBlob, I assume that was what you wanted me to do and just placed it instead of NULL.
The pErrorBlob showed the following message: + 0x01485510 <Information not available, no symbols loaded for D3DCompiler_47.dll> ID3D10Blob *

Also what do you mean by this "- Have you tried specifying the entry points explicitly?" I am a beginner so I don't know what you mean really

##### Share on other sites

I don't know how much this will help but perhaps It will so I am just pasting this

'Direct3D.exe' (Win32): Loaded 'C:\Users\Dawood\Documents\Visual Studio 2013\Projects\Direct3D\Debug\Direct3D.exe'. Symbols loaded.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Program Files (x86)\Norton Internet Security\NortonData\21.0.0.100\Definitions\BASHDefs\20140912.003\UMEngx86.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\d3d11.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\D3DCompiler_47.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcr120d.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dxgi.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptsp.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcryptprimitives.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\uxtheme.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\combase.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\dwmapi.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nvinit.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\nvinit.dll'
The thread 0xf3c has exited with code 0 (0x0).
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\igd10iumd32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\shlwapi.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\bcrypt.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ncrypt.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntasn1.dll'. Cannot find or open the PDB file.
'Direct3D.exe' (Win32): Loaded 'C:\Windows\SysWOW64\igdusc32.dll'. Cannot find or open the PDB file.

##### Share on other sites

Perhaps this can help

- &VS_Buffer 0x00e2bee0 {0x00000000 <NULL>} ID3D10Blob * *
- 0x00000000 <NULL> ID3D10Blob *
- IUnknown <struct at NULL> IUnknown
__vfptr <Unable to read memory> void * *

##### Share on other sites

First: It appears the code you're working with is for Direct3D 11, and you're using ID3D10Blob. If so, use ID3DBlob.

You should have something like:

// ID3DBlob VS_BUFFER; // NO! VS_BUFFER must be a pointer to a blob.
ID3DBlob *VS_BUFFER = NULL;
ID3DBlob *errMsg = NULL;
DWORD dwShaderFlags = D3DCOMPILE_ENABLE_STRICTNESS | D3DCOMPILE_DEBUG;

hr = D3DCompileFromFile( filename, NULL, D3D_COMPILE_STANDARD_FILE_INCLUDE, "your-entry-point", "vs_4_0", dwShaderFlags, NULL, &VS_BUFFER, &errMsg );
if( FAILED(hr) )
{
if( NULL != errMsg )
{
OutputErrorMessage( (char*)errMsg->GetBufferPointer() );
errMsg->Release();
return some-error;
}
// .. output the error condition for the user
ReportErrorCondition(hr);
}
if( NULL != errMsg ) errMsg->Release(); // ensure cleanup

Edited by Buckeye

##### Share on other sites

What do you mean by "your-entry-point"? What should I put there?

##### Share on other sites

That parameter is the entry point for the vertex shader in your shader file.

If, for instance, your shader file has:

PS_INPUT MyVertexShader( VS_INPUT input )
{
...


then that parameter would be "MyVertexShader" - i.e., D3DCompileFromFile(..., "MyVertexShader", "vs_4_0", ...)

##### Share on other sites

Hmm, I think that was it, now it is atleast working, however nothing is being drawn :(

Thanks alot for the help!

• 9
• 16
• 9
• 13
• 41
• ### Similar Content

• By chiffre
Introduction:
In general my questions pertain to the differences between floating- and fixed-point data. Additionally I would like to understand when it can be advantageous to prefer fixed-point representation over floating-point representation in the context of vertex data and how the hardware deals with the different data-types. I believe I should be able to reduce the amount of data (bytes) necessary per vertex by choosing the most opportune representations for my vertex attributes. Thanks ahead of time if you, the reader, are considering the effort of reading this and helping me.
I found an old topic that shows this is possible in principal, but I am not sure I understand what the pitfalls are when using fixed-point representation and whether there are any hardware-based performance advantages/disadvantages.
(TLDR at bottom)
The Actual Post:
To my understanding HLSL/D3D11 offers not just the traditional floating point model in half-,single-, and double-precision, but also the fixed-point model in form of signed/unsigned normalized integers in 8-,10-,16-,24-, and 32-bit variants. Both models offer a finite sequence of "grid-points". The obvious difference between the two models is that the fixed-point model offers a constant spacing between values in the normalized range of [0,1] or [-1,1], while the floating point model allows for smaller "deltas" as you get closer to 0, and larger "deltas" the further you are away from 0.
To add some context, let me define a struct as an example:
struct VertexData { float[3] position; //3x32-bits float[2] texCoord; //2x32-bits float[3] normals; //3x32-bits } //Total of 32 bytes Every vertex gets a position, a coordinate on my texture, and a normal to do some light calculations. In this case we have 8x32=256bits per vertex. Since the texture coordinates lie in the interval [0,1] and the normal vector components are in the interval [-1,1] it would seem useful to use normalized representation as suggested in the topic linked at the top of the post. The texture coordinates might as well be represented in a fixed-point model, because it seems most useful to be able to sample the texture in a uniform manner, as the pixels don't get any "denser" as we get closer to 0. In other words the "delta" does not need to become any smaller as the texture coordinates approach (0,0). A similar argument can be made for the normal-vector, as a normal vector should be normalized anyway, and we want as many points as possible on the sphere around (0,0,0) with a radius of 1, and we don't care about precision around the origin. Even if we have large textures such as 4k by 4k (or the maximum allowed by D3D11, 16k by 16k) we only need as many grid-points on one axis, as there are pixels on one axis. An unsigned normalized 14 bit integer would be ideal, but because it is both unsupported and impractical, we will stick to an unsigned normalized 16 bit integer. The same type should take care of the normal vector coordinates, and might even be a bit overkill.
struct VertexData { float[3] position; //3x32-bits uint16_t[2] texCoord; //2x16bits uint16_t[3] normals; //3x16bits } //Total of 22 bytes Seems like a good start, and we might even be able to take it further, but before we pursue that path, here is my first question: can the GPU even work with the data in this format, or is all I have accomplished minimizing CPU-side RAM usage? Does the GPU have to convert the texture coordinates back to a floating-point model when I hand them over to the sampler in my pixel shader? I have looked up the data types for HLSL and I am not sure I even comprehend how to declare the vertex input type in HLSL. Would the following work?
struct VertexInputType { float3 pos; //this one is obvious unorm half2 tex; //half corresponds to a 16-bit float, so I assume this is wrong, but this the only 16-bit type I found on the linked MSDN site snorm half3 normal; //same as above } I assume this is possible somehow, as I have found input element formats such as: DXGI_FORMAT_R16G16B16A16_SNORM and DXGI_FORMAT_R16G16B16A16_UNORM (also available with a different number of components, as well as different component lengths). I might have to avoid 3-component vectors because there is no 3-component 16-bit input element format, but that is the least of my worries. The next question would be: what happens with my normals if I try to do lighting calculations with them in such a normalized-fixed-point format? Is there no issue as long as I take care not to mix floating- and fixed-point data? Or would that work as well? In general this gives rise to the question: how does the GPU handle fixed-point arithmetic? Is it the same as integer-arithmetic, and/or is it faster/slower than floating-point arithmetic?
Assuming that we still have a valid and useful VertexData format, how far could I take this while remaining on the sensible side of what could be called optimization? Theoretically I could use the an input element format such as DXGI_FORMAT_R10G10B10A2_UNORM to pack my normal coordinates into a 10-bit fixed-point format, and my verticies (in object space) might even be representable in a 16-bit unsigned normalized fixed-point format. That way I could end up with something like the following struct:
struct VertexData { uint16_t[3] pos; //3x16bits uint16_t[2] texCoord; //2x16bits uint32_t packedNormals; //10+10+10+2bits } //Total of 14 bytes Could I use a vertex structure like this without too much performance-loss on the GPU-side? If the GPU has to execute some sort of unpacking algorithm in the background I might as well let it be. In the end I have a functioning deferred renderer, but I would like to reduce the memory footprint of the huge amount of vertecies involved in rendering my landscape.
TLDR: I have a lot of vertices that I need to render and I want to reduce the RAM-usage without introducing crazy compression/decompression algorithms to the CPU or GPU. I am hoping to find a solution by involving fixed-point data-types, but I am not exactly sure how how that would work.
• By cozzie
Hi all,
I was wondering it it matters in which order you draw 2D and 3D items, looking at the BeginDraw/EndDraw calls on a D2D rendertarget.
The order in which you do the actual draw calls is clear, 3D first then 2D, means the 2D (DrawText in this case) is in front of the 3D scene.
The question is mainly about when to call the BeginDraw and EndDraw.
Note that I'm drawing D2D stuff through a DXGI surface linked to the 3D RT.
Option 1:
A - Begin frame, clear D3D RT
B - Draw 3D
C - BeginDraw D2D RT
D - Draw 2D
E - EndDraw D2D RT
F - Present
Option 2:
A - Begin frame, clear D3D RT + BeginDraw D2D RT
B - Draw 3D
C - Draw 2D
D - EndDraw D2D RT
E- Present
Would there be a difference (performance/issue?) in using option 2? (versus 1)
Any input is appreciated.

• Do you know any papers that cover custom data structures like lists or binary trees implemented in hlsl without CUDA that work perfectly fine no matter how many threads try to use them at any given time?
• By cozzie
Hi all,
Last week I noticed that when I run my test application(s) in Renderdoc, it crashes when it enable my code that uses D2D/DirectWrite. In Visual Studio no issues occur (debug or release), but when I run the same executable in Renderdoc, it crashes somehow (assert of D2D rendertarget or without any information). Before I spend hours on debugging/ figuring it out, does someone have experience with this symptom and/or know if Renderdoc has known issues with D2D? (if so, that would be bad news for debugging my application in the future );
I can also post some more information on what happens, code and which code commented out, eliminates the problems (when running in RenderDoc).
Any input is appreciated.

• Hi Guys,
I understand how to create input layouts etc... But I am wondering is it at all possible to derive an input layout from a shader and create the input layout directly from this? (Rather than manually specifying the input layout format?)
Thanks in advance :)