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

Resource inspector should show pipeline usage in frame #3310

Open
w-pearson opened this issue May 13, 2024 · 0 comments
Open

Resource inspector should show pipeline usage in frame #3310

w-pearson opened this issue May 13, 2024 · 0 comments
Labels
Feature An improvement or feature Unresolved Waiting for a fix or implementation

Comments

@w-pearson
Copy link
Contributor

w-pearson commented May 13, 2024

Description

While investigating #3307, I ended up knowing a pipeline ID without knowing where it was used. I was able to find the pipeline in renderdoc's resource inspector, and the "related resources" section let me go from the pipeline library to the complete graphics pipeline. However, for both the pipeline library and the complete graphics pipeline, the "usage in frame" section is completely empty. This initially confused me into thinking the pipeline wasn't actually in use in the frame.

I don't think that's going to be a scenario anyone else will run into, but having seen that I think that it would be useful to have pipelines show up on "usage in frame". The main use-case for that would be finding other uses of a pipeline in the same frame once you've seen one. It would also be useful to do this with individual shaders, although the related resources section already allows finding pipelines that use specific shaders. This is already possible for vertex and index buffers, so I don't think it would be too difficult to implement.

Environment

  • RenderDoc version: v1.32, and various development builds
  • Operating System: Windows 10
  • Graphics API: Vulkan
@baldurk baldurk added Feature An improvement or feature Unresolved Waiting for a fix or implementation labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature An improvement or feature Unresolved Waiting for a fix or implementation
Projects
None yet
Development

No branches or pull requests

2 participants