Jump to content
  • Advertisement
Sign in to follow this  
jdub

SlimDX and the Visual Studio Graphics Debugger

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

I am trying to debug my code in the graphics diagnostics tool provided with Visual Studio 2012.  However, I am noticing that the order in which D3D function calls are made according to the Graphics Events List tab is different than the order in which I call them (or at least call their wrappers) in my code.  For example, in my initialization code, I start by creating a device and swap chain, then create a viewport, and then create a render target with corrosponding RenderTargetView.  However, in the Graphics Events List tab, it records that D3D11CreateDeviceAndSwapChain() is called first, and then my Vertex Shader is created immediately afterwards.  The render target and viewport are not listed as being created until much further down in the list of events.

 

What gives?  Why does SlimDX do this as opposed to creating things in the order in which I specify them?  

Share this post


Link to post
Share on other sites
Advertisement

This has nothing to do with SlimDX directly.  It's possibly Direct 3D or your video driver that's reordering the commands.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!