Vulkan - VK_EXT_debug_marker missing after new 5.2 build update?
I downloaded the new Nsight build today (5.2.0.16321, I think I was on 5.2.0.16268) 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? Versions: Nsight 5.2 build 5.2.0.16321 GeForce GTX 760 Windows 10 Pro x64 VS 2015 Update 3 GeForce driver: 378.92
I downloaded the new Nsight build today (5.2.0.16321, I think I was on 5.2.0.16268) 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?

Versions:
Nsight 5.2 build 5.2.0.16321
GeForce GTX 760
Windows 10 Pro x64
VS 2015 Update 3
GeForce driver: 378.92

#1
Posted 03/30/2017 08:04 PM   
Hi shilbert, Thanks for your feedback. Can we have your sample to do some local repro? That will help us identify the issue quickly. Thanks, Letitia
Hi shilbert,

Thanks for your feedback.
Can we have your sample to do some local repro? That will help us identify the issue quickly.

Thanks,
Letitia

#2
Posted 03/31/2017 08:53 AM   
Hello Letitia, https://www.dropbox.com/s/5f85jmv1m9tusyz/VulkanSample-Debug.zip?dl=0 This contains the debug EXE and enough assets/DLLs to run. The exe has to be run with the working directory set to the directory it is in. Let me know if you need source. This is an x64/Debug build from VS2015.
Hello Letitia,


https://www.dropbox.com/s/5f85jmv1m9tusyz/VulkanSample-Debug.zip?dl=0


This contains the debug EXE and enough assets/DLLs to run. The exe has to be run with the working directory set to the directory it is in. Let me know if you need source.

This is an x64/Debug build from VS2015.

#3
Posted 03/31/2017 02:00 PM   
Hi shilbert, Thanks for your information. An internal bug is created for tracking the issue. Thanks, Letitia
Hi shilbert,

Thanks for your information.
An internal bug is created for tracking the issue.

Thanks,
Letitia

#4
Posted 04/05/2017 06:01 AM   
Hi shilbert, The issue is fixed in Nsight 5.3 build which is coming, please wait for the Nsight 5.3 build. Regard to the error message "vkCreateDevice extension VK_EXT_debug_marker not available for devices associated with ICD C:\WINDOWS\system32\.\nvoglv64.dll", it's unrelated to this issue. Regards, Letitita
Hi shilbert,

The issue is fixed in Nsight 5.3 build which is coming, please wait for the Nsight 5.3 build.
Regard to the error message "vkCreateDevice extension VK_EXT_debug_marker not available for devices associated with ICD C:\WINDOWS\system32\.\nvoglv64.dll", it's unrelated to this issue.

Regards,
Letitita

#5
Posted 04/11/2017 06:30 AM   
Okay, awesome! Thank you for looking into it!
Okay, awesome! Thank you for looking into it!

#6
Posted 04/11/2017 07:44 AM   
Scroll To Top

Add Reply