Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profiling category not set for the various Vulkan functions #61

Open
myblindy opened this issue Jun 5, 2020 · 1 comment
Open

Profiling category not set for the various Vulkan functions #61

myblindy opened this issue Jun 5, 2020 · 1 comment

Comments

@myblindy
Copy link

myblindy commented Jun 5, 2020

I'm referring to the new category column for profiling events introduced in VS 2019:
image

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?

@FacticiusVir
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants