You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm referring to the new category column for profiling events introduced in VS 2019:
With no additional markup, the profiler has no idea that these calls are actually Graphics calls (though it is apparently guessing for some of them). Is there a way to mark the functions that send (and especially wait for) graphics card events as Graphics for this list?
The text was updated successfully, but these errors were encountered:
I've not looked at these before, so I'm not sure how these would be specified - I notice the calls marked as Graphics are those that will require communication with the GPU (Queue Present/Queue Submit, Wait for Fences) while the others are typically constrained to the driver (e.g. Command Buffer calls). Let me do some digging and I'll see if I can add category decorators/attributes.
I'm referring to the new category column for profiling events introduced in VS 2019:
![image](https://user-images.githubusercontent.com/541998/83912551-0a3f0500-a73c-11ea-9e82-f33a8529b7ad.png)
With no additional markup, the profiler has no idea that these calls are actually
Graphics
calls (though it is apparently guessing for some of them). Is there a way to mark the functions that send (and especially wait for) graphics card events as Graphics for this list?The text was updated successfully, but these errors were encountered: