Skip to content

Vulkan Descriptor Buffer (VK_EXT_descriptor_buffer) support #2880

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

Open
kyamant opened this issue Mar 11, 2023 · 4 comments
Open

Vulkan Descriptor Buffer (VK_EXT_descriptor_buffer) support #2880

kyamant opened this issue Mar 11, 2023 · 4 comments
Labels
Feature An improvement or feature Unresolved Waiting for a fix or implementation

Comments

@kyamant
Copy link

kyamant commented Mar 11, 2023

Description

VK_EXT_descriptor_buffer extension enhances the Vulkan (descriptor) api drastically and I would like to be able to use it together with RenderDoc.

Environment

  • RenderDoc version: 1.25
  • Operating System: Windows 10 Pro
  • Graphics API: Vulkan 1.3.236.0
@baldurk baldurk added Feature An improvement or feature Unresolved Waiting for a fix or implementation labels Mar 13, 2023
@d3-denis-zaporozhets
Copy link

Any news on adding support for this extension?

@theagentd
Copy link

I could really use support for this in RenderDoc too. Descriptor buffers are amazing for reducing the overhead of descriptor set management. The lack of support for them in RenderDoc is pretty much the only thing holding me back from making a permanent move over to descriptor buffers.

@all500234765
Copy link

Same here. Intel GPA is practically useless in terms of debugging bindless resources on either API, nsight graphics is only for NV, PIX doesn't support Vulkan and then most common and the only vendor agnostic debugger we has for vulkan - RenderDoc doesn't support descriptor_buffer extension.
That's real bummer for me right now

@nihalkenkre
Copy link

Need this. Has work started on this ? On the blogs they mention that debugging and profiling support would take a while. Why would it take longer than others. The extension docs mention that the API / usage is simplified since under the hood it was really just memory being allocated and updated, which is now being exposed to the developer.

Is it that the exposure of previously black boxed operations, would make it a tedious task to debug ? I am curious to know.

Cheers, and great work on RenderDoc until now!

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

6 participants