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 Usages context menu and panel doesn't show resources accessed via ResourceDescriptorHeap indexing (bindless) #3278

Open
kylawl opened this issue Mar 19, 2024 · 1 comment
Labels
Feature An improvement or feature Unresolved Waiting for a fix or implementation

Comments

@kylawl
Copy link

kylawl commented Mar 19, 2024

Description

Resource Usage in frame and Used: context menu do not display usages resulting from bindless access.

Steps to reproduce

  1. Select a draw or dispatch which uses ResourceDescriptorHeap indexing
  2. Right click on a ResourceDescriptorHeap indexed resource.
  3. Note: the Used context menu will only contain usages where the resource was bound and other non-bindless work like barriers
  4. Select Open in Resource Inspector, the same subset of usages as the context menu is only visible there.

Environment

  • RenderDoc version: v1.31
  • Operating System: Windows 10.0.19045 Build 19045
  • Graphics API: D3D12

Thanks Baldur!

@baldurk
Copy link
Owner

baldurk commented Mar 19, 2024

Yes the resource usage is tracked via what bindings are used on the CPU, so in the case of bindless access (which means mostly any access via a large arrayed binding in the shader) rather than reporting every binding as used everywhere, they are reported as used nowhere.

It's not clear if it's technically feasible to track accesses that are only possible to account for on the GPU.

@baldurk baldurk added Feature An improvement or feature Unresolved Waiting for a fix or implementation labels Mar 19, 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