Profiling wgpu app with Nsight Graphics.

[GeneralGDA]

I'm trying to profile a WGPU application on Windows using Nsight Graphics — I have a mobile GeForce 3070 graphics card. The WGPU's backend is Vulkan.

According to the WGPU source code, debug information in shaders is enabled by passing the wgpu::InstanceFlags::DEBUG flag to the descriptor of the wgpu::Instance::new function. This information is needed by Nsight to build flame graphs and perform top-down function analysis.

However, when analyzing the profile, Nsight says "Some shaders are missing required debug info to show nested calls within the Flame Graph. 3 shaders are missing function info. See the User Guide for information." 3 is exactly number of my shaders, used during a frame.

Could you please tell me if I'm doing something wrong? Or is the problem on the WGPU side with how it configures shader compilation?

[JMS55]

I'm fairly certain wgpu is bugged, I've never gotten it to work either.

[GeneralGDA]

Actually the Nsight is able to "see" the compute shader code and even shows the hotspots in the SPIR-V code, produced from it. But some info still lacking.