Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


#ActualAlessio1989

Posted 25 June 2013 - 12:10 PM

Ok, just tweaking, looking and stuff. 

 

And it finally ran! (... in debug mode happy.png ) 

 

But black...

 

So I ran PIX, and found out that the full screen quad was being rendered, with color. So looking over the code again, the stencils weren't being restored properly.

 

But I guess the next goal is to make it run in Release Mode, but for now, I'm just going to play around a bit.

 

Just one question: Can Directx 11 with c++ corrupt the system, or cause BSOD, even if the system is healthy?

 

Thanks for your help! wink.png

The code itself shouldn't cause BSOD or other "enjoyable" Windows hangs and crashes... 

Any crashes/hangs/BSOD/nuclear disaster/celin dion song/zombie pandemic/etc. caused by a direct3d application are related with the quality of the video drivers only; with the introduction of WDDM (since Vista), most of problems appear as driver crashes with reset to desktop (or just with some seconds of hangs without the application crash if you are lucky)...


#1Alessio1989

Posted 25 June 2013 - 12:10 PM

Ok, just tweaking, looking and stuff. 

 

And it finally ran! (... in debug mode happy.png ) 

 

But black...

 

So I ran PIX, and found out that the full screen quad was being rendered, with color. So looking over the code again, the stencils weren't being restored properly.

 

But I guess the next goal is to make it run in Release Mode, but for now, I'm just going to play around a bit.

 

Just one question: Can Directx 11 with c++ corrupt the system, or cause BSOD, even if the system is healthy?

 

Thanks for your help! wink.png

The code itself shouldn't cause BSOD or other "enjoyable" Windows hangs and crashes... 

Any crashes/hangs/BSOD/nuclear disaster/celin dion song/zombie pandemic/etc. caused by a direct3d application are related with the quality of the video drivers only; and with the introduction of WDDM (since Vista), most of problems appear as driver crashes with reset to desktop (or just with some seconds of hangs without the application crash if you are lucky)...


PARTNERS