Sign in to follow this  
Atemu

D3D11CreateDevice failed

Recommended Posts

Atemu    263

Hello,

 

I have a huge problem. I can't run my program in Debug, I use the D3D11_CREATE_DEVICE_DEBUG when I want to initialize DX 11. However, it works in Release mode. I tried toreinstall the DirectX SDK but it's not successfull sad.png

Yesterday everything was working fine and not today sad.png

 

The source code that initialize DX 11:

UINT createDeviceFlags = 0;
#if defined(DEBUG) || defined(_DEBUG)  
    createDeviceFlags |= D3D11_CREATE_DEVICE_DEBUG;
#endif

D3D_FEATURE_LEVEL featureLevel;
HRESULT hr = D3D11CreateDevice(
		0,                 // default adapter
		md3dDriverType,
		0,                 // no software device
		createDeviceFlags, 
		0, 0,              // default feature level array
		D3D11_SDK_VERSION,
		&md3dDevice,
		&featureLevel,
		&md3dImmediateContext);

if( FAILED(hr) )
{
	MessageBox(0, L"D3D11CreateDevice Failed.", 0, 0);
	DXTrace( __FILE__, __LINE__, hr, DXGetErrorDescription(hr), FALSE );
	return false;
}

These are the information I get:

First-chance exception at 0x7751c41f in SpinningCube.exe: Microsoft C++ exception: _com_error at memory location 0x0031ec88..
An undetermined error occurred hr=E_FAIL (0x80004005)

Thanks in advance !

Share this post


Link to post
Share on other sites
Atemu    263

I'm getting the same problem as well. I think it has something to do with the update yesterday.

I also installed the update yesterday :(

Share this post


Link to post
Share on other sites
Seabolt    781

You've got to be kidding me. Now in order to debug shaders I need to use the Graphics Diagnostic tool that requires you to buy Visual Studios. That's ridiculous.

Share this post


Link to post
Share on other sites
Atemu    263

You've got to be kidding me. Now in order to debug shaders I need to use the Graphics Diagnostic tool that requires you to buy Visual Studios. That's ridiculous.

No, that's Microsoft...

Edited by Atemu

Share this post


Link to post
Share on other sites
Atemu    263

Solution found for the D3D11_CREATE_DEVICE_DEBUG flag:

For developers currently working on applications in Microsoft Visual Studio 2010 or earlier using theD3D11_CREATE_DEVICE_DEBUG flag, be aware that calls to D3D11CreateDevice will fail. This is because the D3D11.1 runtime now requires D3D11_1SDKLayers.dll instead of D3D11SDKLayers.dll. To get this new DLL (D3D11_1SDKLayers.dll), install the Windows 8 SDK, Visual Studio 2012, or the Visual Studio 2012 remote debugging tools. See the Debug Layer documentation for more info. You can download Visual Studio 2012 remote debugging tools from either of these links:

Share this post


Link to post
Share on other sites
blueshogun96    2264

Forgive me if I missed something, but does this require you to have the professional edition of Visual Studio 2012?  What about the express edition?  If the former is true, then that's really unfortunate for the large number of indie game devs that can't afford it.  No disrespect to Microsoft, but wow, that doesn't sound like it will go down very well with Windows devs, and maybe increase the piracy rate for their professional IDE.  And people complain about Apple...

 

Shogun.

 

EDIT: Okay, it does require the paid version.  So, what is Microsoft thinking?  That only the big time professional devs can debug their games? \/_\/ 

Edited by blueshogun96

Share this post


Link to post
Share on other sites
Flimflam    665

Microsoft's decisions lately have generally left me feeling disappointed... They look eager to rid themselves of "freeloading" developers despite their products being a positive thing for the platform. I knew the moment Microsoft tried to get rid of the proper Express editions where we were heading. 

Share this post


Link to post
Share on other sites
Hodgman    51220

 If the former is true, then that's really unfortunate for the large number of indie game devs that can't afford it.

Yeah that's really disappointing.

If you're strapped for cash, you can actually buy a professional version of an older VS version such as 2008 for very cheap, but the latest version always costs a kidney!

Share this post


Link to post
Share on other sites
Aqua Costa    3691

It seems that Microsoft is determined on making the lives of indie developers/students a lot harder... First they stop supporting XNA and now this, I'm pretty sure developing for the next XBox will be close to impossible for indies, let's hope the PS4 will be more indie friendly.

 

I'm just glad my University provides Visual Studio 2012 Ultimate licenses for free to all students.

Share this post


Link to post
Share on other sites
thezbuffer    706

MJP wasn't at the summit this year.  But the rest of us gave the feedback to them that the VS tools provided need to be in the free version (and also not hidden under the C++ parts of Visual Studio). They did seem to hear the message but I have no idea how fast they can react even if they agree with it.

Share this post


Link to post
Share on other sites
NiteLordz    808

I have tried nSIght and GPU PerfStudio 2.0 as well as Pix.  Each application crashes upon startup now.  They worked fine prior to the update that we are discussing.  Does nSight or any of the other applications run for anyone who has done the update? if so, have you done anything besides installing the Windows 8 SDK.

 

I am using windows 7 and visual studio 2010

 

thanks much

Share this post


Link to post
Share on other sites
blueshogun96    2264

 If the former is true, then that's really unfortunate for the large number of indie game devs that can't afford it.

Yeah that's really disappointing.

If you're strapped for cash, you can actually buy a professional version of an older VS version such as 2008 for very cheap, but the latest version always costs a kidney!

 

Really?  I thought that it required you to have VS 2012 professional edition.  Maybe I didn't read it right.  In that case, I'm good because I have 2010 professional.  I got it as a gift from Microsoft about a year or two ago.

 

Shogun.

Share this post


Link to post
Share on other sites
Cthuga    132

Does Microsoft announced earlier that this kind of update would take place ? Or it was described only in update ?

 

In my opinion this is critical hit for game creativity ( Indie Games ) written on DirectX. That's really sad

 

______________________________________________________________________________________________________________

 

Geek Message Blog

The steps I take to make a dream come true:

 

http://geekmessage.wordpress.com

Edited by Cthuga

Share this post


Link to post
Share on other sites
Jason Z    6434

 

 If the former is true, then that's really unfortunate for the large number of indie game devs that can't afford it.

Yeah that's really disappointing.

If you're strapped for cash, you can actually buy a professional version of an older VS version such as 2008 for very cheap, but the latest version always costs a kidney!

 

Really?  I thought that it required you to have VS 2012 professional edition.  Maybe I didn't read it right.  In that case, I'm good because I have 2010 professional.  I got it as a gift from Microsoft about a year or two ago.

 

Shogun.

 

He is just referring to the price of the SKU, not the functionality of the graphics debugger.  The graphics debugger is currently only available in the Pro or better version of VS2012.

 

Does Microsoft announced earlier that this kind of update would take place ? Or it was described only in update ?

 

In my opinion this is critical hit for game creativity ( Indie Games ) written on DirectX. That's really sad

 

______________________________________________________________________________________________________________

 

Geek Message Blog

The steps I take to make a dream come true:

 

http://geekmessage.wordpress.com

 

There were some hints about this (there are some links in the following blog post that would indicate this was coming...) but I don't think it was fully understood just how much of a problem this is going to be.  A bunch of the MVPs (myself included) are lobbying to get the graphics debugger put into the express edition, but there is no word on if or when that might happen.  Let's keep our fingers crossed, and if you have access to someone at Microsoft, please make a comment or send an email to indicate the necessity of this update!

Share this post


Link to post
Share on other sites
NiteLordz    808

I just uninstalled the KB "update" that killed PIX.  I was gave nSight a whirl, but it was very slow, and crashed on me continously.  Within 10 minutes of starting the uninstall, and rebooting and launching PIX, i was able to fix my pixel shader, and now i can move on.

 

 

woot woot

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this