Troubles with using NSight Graphics remote debugging

Developer Tools Nsight Graphics
1

Hi. I wanted to try out the new shader debugger feature in NSight Graphics, but I was struggling getting it to work.

Here’s an example project for reference, it’s one of Bevy’s examples GitHub - Andrewp2/wgpu_nsight_test

I have my main (linux ubuntu) desktop act as the target, and my laptop (linux ubuntu) act as the host.

The laptop runs this command in NSight WGPU_DEBUG=1; BEVY_ASSET_ROOT="/home/andrew-peterson/code/debug_test"; WGPU_BACKEND="vulkan";DISPLAY=":1"

The behavior I see is that the target does run the application, but the host hangs on “Searching for attachable processes on 192.168.1.36:49152-49215…”

sudo ss -tunlp does not show any process listening on any port in 49152 to 49215.

2

It seems that other activities don’t work either. Trying to launch the GPU Trace Profiler leads to

"Missing local file: /home/andrew-peterson/nvidia/NVIDIA-Nsight-Graphics-2024.2/target/linux-desktop-nomad-x64/GPUTraceVulkanLayer/vulkansc/implicit_layer.d/VK_LAYER_NV_GPU_Trace_release_public_2024_2_0.json

Missing required file. Re-installing the product may fix this issue"

I’m not sure why it says this, to install I ran the .run file just a few days ago, and then I launch it by doing sudo ./ngfx-ui in the “/home/andrew-peterson/nvidia/NVIDIA-Nsight-Graphics-2024.2/host/linux-desktop-nomad-x64” directory.

3

Ok I tried using the KhronosGroup Vulkan-Samples instead and it’s still not working, with the same issue. I suppose then it’s likely to be some issue with the setup?

running

Application Executable: /home/andrew-peterson/code/Vulkan-Samples/build/linux/app/bin/Release/x86_64/vulkan_samples

Working Directory: /home/andrew-peterson/code/Vulkan-Samples

Command Line Arguments: sample hello_triangle

Environment: DISPLAY=“:1”

4

I should add also that I can SSH from my host to my target successfully, and generate C++ capture seems to work just fine. The Shader Debugger is not working, however.

5

Updating drivers to version 555.58.02 did not help

6

Tried updating to the beta version of the driver 560, did not help

7

Ok I finally got something to attach by launching on the target, and then attaching on the host and updating all my drivers to 560.

8

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