Jump to content
  • Advertisement
Sign in to follow this  
XXOXX123456

VS2012 GPU Debugging

This topic is 2077 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

It seems that since VS2011 ,the GPU debugger shipped in VS became supported.

 

After spending some time doing window updating,My win7 can eventually run the debugger

 

but i have no idea how to debug GPU pipeline in VS2012.....

 

Anyone has done this before?HELP..!!

 

the msdn have some guide but it was too brief for me to configure correctly....and get started...forgive me = =

Share this post


Link to post
Share on other sites
Advertisement

What exactly is giving you the problem? When do you become lost?

 

Are you using a paid edition of Visual Studio (Pro, Premium, or Ultimate), or the free express edition?

Share this post


Link to post
Share on other sites

What exactly is giving you the problem? When do you become lost?

 

Are you using a paid edition of Visual Studio (Pro, Premium, or Ultimate), or the free express edition?

VS2012 Ultimate,free for 30 days, if the debugger is powerful i'll buy it but i don't even know how to use it= =

Share this post


Link to post
Share on other sites
eh alright,i think.i have figured it out...alt+f5 to start debigging with graphic pipeline viewer, you can look into the pipeline stage like IA,VS,PS,GS,OM etc.press printscreen at program running time can start an graphic log,which marked down a D3D events list. hope this can help me and others..

Share this post


Link to post
Share on other sites

Yes, that's right. You have to start Graphics Diagnostics by pressing alt+F5, or by choosing Graphics -> Start Diagnostics from the Debug menu. From there, capture frames of your application by pressing the Capture button on the Graphics Menubar, or by pressing Print Screen on your keyboard. There's also an API which you can use inside your program's source code to cause a frame capture (as long as the app is running under Graphics Diagnostics) which can be useful when there's an intermittent rendering problem that's hard to catch manually, but whose instigating circumstances are known.

 

From there, the guides in the MSDN documentation should be helpful, but if you have any questions post them here at GameDev if you like. I'm actually the writer of the MSDN documentation for Graphics Diagnostics, so I monitor the forums here for such questions. Also, there are several other knowledgeable folks here who often are able to answer before me.

 

Finally just a heads up for the thread (I know you're doing desktop development)--for Windows Store apps (Windows 8-style), Graphics Diagnostics is free in Visual Studio 2013 Express for Windows. However, you still need a paid version to use it with Windows Desktop apps (Windows 7-style).

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.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!