Event markers working in Frame Debugger but not in GPU Trace

Developer Tools Nsight Graphics
1

Hi,
I’m trying to profile our project using NSight 2025.2 Pro, but the GPU Trace profile shows all commands/queues etc as “vkCommandBufferSubmit” etc. rather than using marker names.

image
image603×124 4.45 KB

However, the same project shows the correct names when the Frame Debugger is run.
image
image600×114 3.13 KB

Is there some extra config needed to get the event markers to work in the trace?

2

Hi klumaster,

Thank you for using Nsight Graphics and providing your feedback. We are sorry for any inconvenience you have encountered.

It’s weird that you can’t see the perf markers in GPUTrace view, I have tried Nsight 2025.2 in my local machine with the bundled vk_raytrace sample, and it looks OK here. Could you just scroll down a little bit and you will see something like below.

image
image1810×495 32.9 KB

Thanks
An

3

Hi AYan,
Strangely, I don’t seem to have that line in the interface:

image
image430×952 21.1 KB

The line is there when I capture vk_raytrace, so I would assume there is something we’re doing wrong in our app, however our API guy is stumped because what he’s doing does seem to be correct for the frame debugger.

4

Hi klumaster,

Based on the screenshot, your app is using two Grfx API, hence you can see two rows for D3D12 and Vulkan. I am not sure whether it’s the key here, but is that possible to disable one?

Is that possible to share a simple example that would allow us to reproduce the issue? This will help us in investigating and resolving the problem more efficiently.

Thanks
An

5

Hi AYan,
I’ve spoken to our API guy, he’ll probably join this thread shortly. Unfortunately it wouldn’t be easy to turn off either GFX API, as the Vulkan one does all the work and the D3D12 one does the present.
Thanks
Ben

6

which Vulkan API are you using to provide the markers?

7

Hi there,
We’re using vkSetDebugUtilsObjectNameEXT to set the labels.
However, it turns out this was user error on my part, a typo in my config meant that I wasn’t forcing the label marking for VkObjects, Command Buffer sections and Queues to be turned on. We’re not certain why the labels DID appear for frame captures, but that’s far less of a worry for me :)
Thank you for your time
Ben

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.