We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are currently not using VMA's gpu memory dump and visualization feature.
Vulkan Memory Allocator has a feature where you can assign internal debug names to resources (memory allocations) and then you can dump the gpu memory as JSON using vmaBuildStatsString. This can then be used to make an image as visualization of gpu memory using VMA's GpuMemDumpVis python script.
Don't mix this VMA naming system up with resource names in Vulkan validation layers.
None, as we should visualize our memory usage.
All of the code.
All operating systems.
none
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem?
We are currently not using VMA's gpu memory dump and visualization feature.
Description
Vulkan Memory Allocator has a feature where you can assign internal debug names to resources (memory allocations) and then you can dump the gpu memory as JSON using vmaBuildStatsString. This can then be used to make an image as visualization of gpu memory using VMA's GpuMemDumpVis python script.
Don't mix this VMA naming system up with resource names in Vulkan validation layers.
Alternatives
None, as we should visualize our memory usage.
Affected Code
All of the code.
Operating System
All operating systems.
Additional Context
none
The text was updated successfully, but these errors were encountered: