Example,
>ngfx --exe /usr/bin/vkcube --activity "Frame Debugger" --wait-hotkey --verbose
Parsed general options:
hostname --> localhost
ssh-user -->
ssh-pwd -->
ssh-port --> 22
exe --> /usr/bin/vkcube
dir -->
args -->
env -->
project -->
output-dir --> /home/carlo/Documents/NVIDIA Nsight Graphics
activity --> Frame Debugger
platform --> Linux (x86_64)
verbose --> 1
Launching process...
Preparing to launch...
Launched process: vkcube (pid: 2485446)
/usr/bin/vkcube
Attempting to automatically connect...
Searching for attachable process 2485446 on local socket...
Launch process exited. Searching for attachable child processes...
Searching for attachable process 2485446 on local socket...
Failed to connect. The target process may have exited.
Launching process... Failed
Exiting...
Running result: 1
As vkcube doesn’t print anything, this isn’t very insight full (pun intended).
But, by running my own application we find that running an executable from within nsight sees a completely different list of extensions:
Normally my application reports:
Available instance extensions:{ "VK_KHR_device_group_creation", "VK_KHR_display", "VK_KHR_external_fence_capabilities", "VK_KHR_external_memory_capabilities", "VK_KHR_external_semaphore_capabilities", "VK_KHR_get_display_properties2", "VK_KHR_get_physical_device_properties2", "VK_KHR_get_surface_capabilities2", "VK_KHR_surface", "VK_KHR_surface_protected_capabilities", "VK_KHR_wayland_surface", "VK_KHR_xcb_surface", "VK_KHR_xlib_surface", "VK_EXT_acquire_xlib_display", "VK_EXT_debug_report", "VK_EXT_debug_utils", "VK_EXT_direct_mode_display", "VK_EXT_display_surface_counter", "VK_KHR_portability_enumeration" }
but when run from ngfx I get:
Available instance extensions:{ "VK_EXT_debug_report", "VK_EXT_debug_utils", "VK_KHR_portability_enumeration", "VK_EXT_tooling_info" }
making it not even capable to draw to a surface.
How can I fix this?
PS This is on Arch linux, using NVIDIA_Nsight_Graphics_2022.2.1.22100.run