I downloaded the new Nsight build today (22.214.171.12421, I think I was on 126.96.36.19968) and suddenly VK_EXT_debug_marker no longer works to let me name resources.
When I try to vkCreateDevice with VK_EXT_debug_marker in the requested device extension list, it succeeds but I get the following debug report:
“vkCreateDevice extension VK_EXT_debug_marker not available for devices associated with ICD C:\WINDOWS\system32.\nvoglv64.dll”
And upon looking at resources or memory pools in Nsight they no longer have names. It definitely worked in the previous build.
I can still call vkDeviceGetProcAddr with “vkDebugMarkerSetObjectTagEXT” and get a non-null result, calling that function just seems to be a no-op.
Renderdoc’s VK_EXT_debug_marker still seems to function alright.
Any ways I can fix this?
Nsight 5.2 build 188.8.131.5221
GeForce GTX 760
Windows 10 Pro x64
VS 2015 Update 3
GeForce driver: 378.92