Skip to content

[FR] Allow resource names for additional resource types #16

@zdobersek

Description

@zdobersek

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.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions