Home Dashboard Directory Help
Search

Visual Studio 2012 Graphics Debugger Creates extra Objects During Capture by MWassmer42


Status: 

Closed
 as Deferred Help for as Deferred


4
0
Sign in
to vote
Type: Bug
ID: 775831
Opened: 1/4/2013 11:55:39 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I've been wanting to use the Graphics Event List to do some analysis on redundant API calls in our scenes and to just get a sense of what all is actually going on. In my capture I noticed a ton of Device::CreateX calls (CreateTexture2D, CreateVertexShader, CreatePixelShader, etc) that we are not actually making.

I've confirmed that these are generated by the VSGraphicsHelper.dll during the capturing process just by sticking some breakpoints in the d3d11.dll and checking the callstack.

I don't really have a problem with the GraphicsHelper doing this per-se, but I would like the option to hide all calls that the Graphics Debugger inserts so I can analyze what we are doing exactly. It looks like there's already special handling for these calls, because they do not have a callstack, where all the user calls do.
Details
Sign in to post a comment.
Posted by Microsoft on 1/18/2013 at 11:16 AM
Hi MWassmer42,

Thanks for the feedback! It is true that we do make calls in order to prep the frame that has been captured. However, all of those calls will have had to be made at some point during the application's execution. To differentiate those calls from the calls that were made just for the captured frame, the event list identifies the events with a "clock" icon. See http://msdn.microsoft.com/en-us/library/vstudio/hh873200.aspx.

That being we are interpreting your feedback as a suggestion to be able to filter these calls out altogether to make it easier to navigate and understand the event list. We have added this suggestion to our backlog.

Thanks again for your feedback,
Jim Griesmer
Visual Studio GPU & Graphics
Posted by Microsoft on 1/6/2013 at 9:38 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/4/2013 at 12:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.