You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RMV userdata tokens can specify debugging-purpose names for specific resources, making for a better experience when examining resources through GUI. These tokens can be generated through object-naming entrypoints in the VK_EXT_debug_marker and VK_EXT_debug_utils extensions, but they could also be used to associate internal resources with some descriptive name.
RMV userdata tokens can specify debugging-purpose names for specific resources, making for a better experience when examining resources through GUI. These tokens can be generated through object-naming entrypoints in the
VK_EXT_debug_marker
andVK_EXT_debug_utils
extensions, but they could also be used to associate internal resources with some descriptive name.The problem at the moment is in the RMV application the name-carrying userdata tokens are only applied to resources of three types: buffers, images and heaps. This filter is applied here:
https://github.com/GPUOpen-Tools/radeon_memory_visualizer/blob/master/source/backend/rmt_resource_userdata.cpp#L330
The naming functionality is great, but it would be perfect it could be applied to resources of any type.
The text was updated successfully, but these errors were encountered: