Failed to collect GPU Trace with WebGPU on chrome

Developer Tools Nsight Graphics
1

Failed to collect GPU trace with error followed:

ID,,Origin,Source,Message
1,,Target,GPU Trace,Multiple GPU usage detected - collected data may not be complete.
2,,Host,NVIDIA Nsight Graphics,No data source is available - make sure the application is using a supported API

chrome startup args:
--no-sandbox --disable-gpu-watchdog --disable-features=RendererCodeIntegrity --disable-direct-composition --gpu-startup-dialog --enable-dawn-features=emit_hlsl_debug_symbols,disable_symbol_renaming

When force Angle backend to d3d11on12 will unable to rendering, Dawn(webgpu implement on chrome) default backend on windows is d3d12

Pix on windows works fine meanwhile.

Is there anything missed to collect webgpu gpu trace?

2

Hi xyn0410,

Thank you for using Nsight Graphics and providing your feedback. Let me do some summary about Nsight Graphics’ support of WebGPU/Chrome at current status:

  • Windows
    – The backend for WebGPU in Chrome is D3D11
    – Nsight/Frame Debugger supports D3D11, but doesn’t work on WebGPU/Chrome since it uses some unsupported (by Nsight Graphics) D3D11 interface
    – Nsight/GPUTrace doesn’t support D3D11
  • Linux
    – The backend for WebGPU in Chrome is Vulkan
    – Nsight/Frame Debugger and GPUTrace support Vulkan, and they should work well on WebGPU/Chrome/Vulkan. Please note, you need to enable the Vulkan backend explicitly.

Thanks
An

5

WebGPU on windows does not use ANGLE, it uses DAWN. The default backend for DAWN on windows is D3D12 and it use d3d12 render pass.
Chrome GPU report attached, you can see more detail.
about-gpu-2024-06-26T11-34-23-523Z.txt (55.6 KB)

Thanks.

6

Hi @AYan，
I have checked that WebGPU on Chrome is D3D12。Nsight needs d3d feature level >= 12.0 ？