ThePentiumGuy
Senior Contributor
Here's something that has helped me a lot!
Normally, on any error in directX, it would give you an InvalidCallException, or possibly now and then a DeviceLostException.
In order to aid developers, Microsoft has created something called Debug mode, where errors are much more clear.
Go to Control Panel, and click DirectX. In the Direct3D tab, be sure you set it to Debug mode and move the 'Debug Ouput' slider all the way.
The only disadvantage towards this is that you will see a slight reduction in speed, but you will gain a significant accelleration in programming your application
. Less cryptic errors.
Helped a lot to me. Not even kidding at all.
Please see DrunkenHyena's Site for more information
Sticky anyone?
-The Pentium Guy
Normally, on any error in directX, it would give you an InvalidCallException, or possibly now and then a DeviceLostException.
In order to aid developers, Microsoft has created something called Debug mode, where errors are much more clear.
Go to Control Panel, and click DirectX. In the Direct3D tab, be sure you set it to Debug mode and move the 'Debug Ouput' slider all the way.
The only disadvantage towards this is that you will see a slight reduction in speed, but you will gain a significant accelleration in programming your application
. Less cryptic errors.Helped a lot to me. Not even kidding at all.
Please see DrunkenHyena's Site for more information
Sticky anyone?
-The Pentium Guy