Hi all,
I followed the user guide and used all forum answers I could find to make chrome run with nsight.
The minimal configuration I found that would work was
--disable-gpu-watchdog --no-sandbox
With the angle backend set to OpenGL.
However I keep getting this error when capturing (In the Frame Debugger. I intended to use the profiler but I’m on a GTX 1070 / Intel 530 machine, and I can’t use another one).
The following incompatibilities were seen during capture: (11.4s ago) glGetInternalformatSampleivNV, (10.5s ago) wglDXRegisterObjectNV (Unsupported DX object type; only 2D D3D11 textures are currently supported)
Is there anything I’m doing wrong ?
I made sure chrome is using the correct gpu, both in windows and in the nvidia control panel.
The following incompatibilities were seen during capture: (11.4s ago) glGetInternalformatSampleivNV, (10.5s ago) wglDXRegisterObjectNV (Unsupported DX object type; only 2D D3D11 textures are currently supported)
This means the Chrome is using some D3D backend and it will do some OGL and D3D interop and these API calls are not supported by Nsight.
You can try to change the backend to Vulkan:
Access chrome://flags/#enable-vulkan
Change the Default to Enabled
Relaunch Chrome to make it works
Use the same cmd line to launch your WebGL page.
I use this cmd (just for example): --no-sandbox --disable-gpu-watchdog --disable-features=RendererCodeIntegrity --gpu-startup-dialog --use-angle=gl http://SOME-WEBGL-URL
Use --use-angle=vulkan should also work
After launch with Nsight Graphics, you will still get The following incompatibilities were seen during capture: (XX.Xs ago) glGetInternalformatSampleivNV, but wglDXRegisterObjectNV will gone.
Just accept the incompatibilities and try the frame debug. Actually, if you keep the Default backend, accept the incompatibilities, you still can do some part of frame debug.