Hi,

Recently I've been having some issues while working with DirectX and I'm curious about some error handling.

	hr = D3DX11CompileFromFile("Effects.fx", 0, 0, "VS", "vs_4_0", 0, 0, 0, &VS_Buffer, 0, 0);
	hr = D3DX11CompileFromFile("Effects.fx", 0, 0, "PS", "ps_4_0", 0, 0, 0, &PS_Buffer, 0, 0);
	hr = D3DX11CompileFromFile("Effects.fx", 0, 0, "D2D_PS", "ps_4_0", 0, 0, 0, &D2D_PS_Buffer, 0, 0);
	//Create the Shader Objects
	hr = d3d11Device->CreateVertexShader(VS_Buffer->GetBufferPointer(), VS_Buffer->GetBufferSize(), NULL, &VS);
	hr = d3d11Device->CreatePixelShader(PS_Buffer->GetBufferPointer(), PS_Buffer->GetBufferSize(), NULL, &PS);
	hr = d3d11Device->CreatePixelShader(D2D_PS_Buffer->GetBufferPointer(), D2D_PS_Buffer->GetBufferSize(), NULL, &D2D_PS);

For example above ^ I'm having an issue with the "D2D_PS" lines from the CompileFromFile and the CreatePixelShader, but when the error comes up it just points to the line and comes up with an error like

"Unhandled exception at 0x772815de in DX16UP.exe: 0xC0000005: Access violation reading location 0x00000000."

So I'm just curious if I can put something after the "hr = " lines to do some error handling. I did have some code that was

if(FAILED(hr))
{
   MessageBox(NULL, DXGetErrorDesction(?)(hr),
      TEXT("Message"), MB_OK);
   return 0;
}

The "DXGetError" isn't really what I had but I can't seem to find it at the moment but you get the idea.

EDIT: I'm starting to think this should be in the DirectX section instead of the beginners. Could someone move this?

ID3D10Blob* pErrorBlob = NULL;
if (FAILED(D3DX11CompileFromFile("Effects.fx", 0, 0, "VS", "vs_4_0", 0, 0, 0, &VS_Buffer, &pErrorBlob, 0)))
{   
   char* pErrors_mb = static_cast<char*>(pErrorBlob->GetBufferPointer());   
   wchar_t pErrors_w[512];   
   mbstowcs(pErrors_w, pErrors_mb, 512);   
   MessageBox(NULL, pErrors_w, L"Error", MB_OK);   
   return 0;
}

Okay thanks!

On a side note, why would you want to precompile shader code? ( MSDN Link I believe that's what you were referencing )

One reason to precompile that i can think of is that it hides the actual source hlsl code from the end user, if that makes any sense. Also, it's more efficient since the application doesn't have to compile the same code over and over at every launch.

But these reasons doesn't really apply when actually developing the shaders, where fiddling with fxc.exe every 5 minutes would probably just slow things down. Visual Studio 2012 solves this whole thing however by including an internal hlsl compiler.

Also, i've no idea why, but most of the D3DX-library has just recently been deprecated by microsoft with the release of windows 8. The math part has been moved to another library called DirectXMath (http://msdn.microsoft.com/en-us/library/windows/desktop/hh437833(v=vs.85).aspx), but i'm not sure what will happen to the other stuff (such as the compile shader function, and not to mention the helper functions for loading texture resources).