Error when trying to setup validation layers while following the official khronos tutorials

learingvulkan · July 5, 2024, 9:49am

Hi I am trying to follow the Khrnonos tutorals but I am not able to set up validation layers below I am attaching the errors:

validation layers: loader_add_layer_properties: 'layers' tag not supported until file version 1.0.1, but C:\Windows\System32\DriverStore\FileRepository\nvlti.inf_amd64_3979ce41b5d87a81\nv-vk64.json is reporting version 1
validation layers: windows_get_device_registry_files: GUID for 4 is not SoftwareComponent skipping
validation layers: windows_get_device_registry_files: GUID for 5 is not SoftwareComponent skipping
validation layers: Searching for ICD drivers named .\amdvlk64.dll
validation layers: Searching for ICD drivers named .\nvoglv64.dll
validation layers: Loading layer library C:\VulkanSDK\1.3.283.0\Bin\.\VkLayer_khronos_validation.dll
validation layers: Loading layer library C:\Windows\System32\DriverStore\FileRepository\nvlti.inf_amd64_3979ce41b5d87a81\.\nvoglv64.dll
validation layers: Loading layer library C:\Windows\System32\DriverStore\FileRepository\u0391129.inf_amd64_7a819ad751ab7622\B390488\.\amdvlk64.dll
validation layers: loader_add_layer_properties: 'layers' tag not supported until file version 1.0.1, but C:\Windows\System32\DriverStore\FileRepository\nvlti.inf_amd64_3979ce41b5d87a81\nv-vk64.json is reporting version 1
validation layers: windows_get_device_registry_files: GUID for 4 is not SoftwareComponent skipping
validation layers: windows_get_device_registry_files: GUID for 5 is not SoftwareComponent skipping
validation layers: Searching for ICD drivers named .\amdvlk64.dll
validation layers: Searching for ICD drivers named .\nvoglv64.dll
validation layers: Loading layer library C:\VulkanSDK\1.3.283.0\Bin\.\VkLayer_khronos_validation.dll
validation layers: Loading layer library C:\Windows\System32\DriverStore\FileRepository\nvlti.inf_amd64_3979ce41b5d87a81\.\nvoglv64.dll
validation layers: Loading layer library C:\Windows\System32\DriverStore\FileRepository\u0391129.inf_amd64_7a819ad751ab7622\B390488\.\amdvlk64.dll
failed to setup debug messenger!

Edit: Using the official code of Khronos tuts the error remains.

Thank you!

aria · July 10, 2024, 6:18pm

Hi,
I have similar errors (the first one specifically) and tried everything I can find online to fix it, but nothing works. I tried reinstalling Vulkan and NVIDIA drivers, added environment variables, messed with the registry, all to no avail.

validation layer: loader_add_layer_properties: 'layers' tag not supported until file version 1.0.1, but C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\nv-vk64.json is reporting version 1
validation layer: Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
validation layer: Searching for ICD drivers named .\amdvlk64.dll
validation layer: Searching for ICD drivers named .\nvoglv64.dll
validation layer: loader_get_json: Failed to open JSON file C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\nv - vk64.json
validation layer: loader_get_json: Failed to open JSON file C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\nv - vk64.json
validation layer: Loading layer library F:\Programming\VulkanSDK\1.3.283.0\Bin\.\VkLayer_khronos_validation.dll
validation layer: Loading layer library C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\.\nvoglv64.dll
validation layer: Loading layer library C:\Windows\System32\DriverStore\FileRepository\u0403811.inf_amd64_52448c34fb47b343\B403843\.\amdvlk64.dll
validation layer: Unloading layer library C:\Windows\System32\DriverStore\FileRepository\u0403811.inf_amd64_52448c34fb47b343\B403843\.\amdvlk64.dll
validation layer: Unloading layer library C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5714f0dca6485379\.\nvoglv64.dll
validation layer: Unloading layer library F:\Programming\VulkanSDK\1.3.283.0\Bin\.\VkLayer_khronos_validation.dll

F:\Programming\LearningVulkan\DrawingTriangle\x64\Debug\DrawingTriangle.exe (process 16104) exited with code 0.

Any help would be greatly appreciated!
Thanks

alan88w · July 22, 2024, 2:18am

I had the same issue when following the Vulkan Tutorials. Still run and Window does open but just these message.

Validation Layer : loader_add_layer_properties: 'layers' tag not supported until file version 1.0.1, but C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_5542d7b83d2efdd5\nv-vk64.json is reporting version 1
Validation Layer : windows_get_device_registry_files: GUID for 2 is not SoftwareComponent skipping
Validation Layer : windows_get_device_registry_files: GUID for 5 is not SoftwareComponent skipping
Validation Layer : Searching for ICD drivers named .\nvoglv64.dll
Validation Layer : Searching for ICD drivers named .\igvk64.dll
Validation Layer : Loading layer library C:\ExternalTools\Vulkan\1.3.283.0\Bin\.\VkLayer_khronos_validation.dll
Validation Layer : Loading layer library C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_5542d7b83d2efdd5\.\nvoglv64.dll
VUID-VkDebugUtilsMessengerCreateInfoEXT-sType-sType(ERROR / SPEC): msgNum: -1593518324 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-sType-sType ] | MessageID = 0xa104d70c | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->sType must be VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT. The Vulkan spec states: sType must be VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-sType-sType)
    Objects: 0
VUID_Undefined(ERROR / SPEC): msgNum: 2044605652 - Validation Error: [ VUID_Undefined ] | MessageID = 0x79de34d4 | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->pNext must be NULL. This error is based on the Valid Usage documentation for version 283 of the Vulkan header.  It is possible that you are using a struct from a private extension or an extension that was added to a later version of the Vulkan header, in which case the use of pCreateInfo->pNext is undefined and may not work correctly with validation enabled
    Objects: 0
VUID-VkDebugUtilsMessengerCreateInfoEXT-flags-zerobitmask(ERROR / SPEC): msgNum: -1887787987 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-flags-zerobitmask ] | MessageID = 0x8f7aa42d | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->flags is 3435973836, but must be 0. The Vulkan spec states: flags must be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-flags-zerobitmask)
    Objects: 0
VUID-VkDebugUtilsMessengerCreateInfoEXT-messageSeverity-parameter(ERROR / SPEC): msgNum: 1928579345 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-messageSeverity-parameter ] | MessageID = 0x72f3c911 | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->messageSeverity contains flag bits (0xcccccccc) which are not recognized members of VkDebugUtilsMessageSeverityFlagBitsEXT. The Vulkan spec states: messageSeverity must be a valid combination of VkDebugUtilsMessageSeverityFlagBitsEXT values (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-messageSeverity-parameter)
    Objects: 0
VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter(ERROR / SPEC): msgNum: -553000032 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter ] | MessageID = 0xdf09e3a0 | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->messageType contains flag bits (0xcccccccc) which are not recognized members of VkDebugUtilsMessageTypeFlagBitsEXT. The Vulkan spec states: messageType must be a valid combination of VkDebugUtilsMessageTypeFlagBitsEXT values (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter)
    Objects: 0

Any idea ?

alan88w · July 22, 2024, 2:19am

I had the same problem, though the window did open:

Validation Layer : loader_add_layer_properties: 'layers' tag not supported until file version 1.0.1, but C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_5542d7b83d2efdd5\nv-vk64.json is reporting version 1
Validation Layer : windows_get_device_registry_files: GUID for 2 is not SoftwareComponent skipping
Validation Layer : windows_get_device_registry_files: GUID for 5 is not SoftwareComponent skipping
Validation Layer : Searching for ICD drivers named .\nvoglv64.dll
Validation Layer : Searching for ICD drivers named .\igvk64.dll
Validation Layer : Loading layer library C:\ExternalTools\Vulkan\1.3.283.0\Bin\.\VkLayer_khronos_validation.dll
Validation Layer : Loading layer library C:\WINDOWS\System32\DriverStore\FileRepository\nvdmwi.inf_amd64_5542d7b83d2efdd5\.\nvoglv64.dll
VUID-VkDebugUtilsMessengerCreateInfoEXT-sType-sType(ERROR / SPEC): msgNum: -1593518324 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-sType-sType ] | MessageID = 0xa104d70c | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->sType must be VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT. The Vulkan spec states: sType must be VK_STRUCTURE_TYPE_DEBUG_UTILS_MESSENGER_CREATE_INFO_EXT (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-sType-sType)
    Objects: 0
VUID_Undefined(ERROR / SPEC): msgNum: 2044605652 - Validation Error: [ VUID_Undefined ] | MessageID = 0x79de34d4 | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->pNext must be NULL. This error is based on the Valid Usage documentation for version 283 of the Vulkan header.  It is possible that you are using a struct from a private extension or an extension that was added to a later version of the Vulkan header, in which case the use of pCreateInfo->pNext is undefined and may not work correctly with validation enabled
    Objects: 0
VUID-VkDebugUtilsMessengerCreateInfoEXT-flags-zerobitmask(ERROR / SPEC): msgNum: -1887787987 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-flags-zerobitmask ] | MessageID = 0x8f7aa42d | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->flags is 3435973836, but must be 0. The Vulkan spec states: flags must be 0 (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-flags-zerobitmask)
    Objects: 0
VUID-VkDebugUtilsMessengerCreateInfoEXT-messageSeverity-parameter(ERROR / SPEC): msgNum: 1928579345 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-messageSeverity-parameter ] | MessageID = 0x72f3c911 | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->messageSeverity contains flag bits (0xcccccccc) which are not recognized members of VkDebugUtilsMessageSeverityFlagBitsEXT. The Vulkan spec states: messageSeverity must be a valid combination of VkDebugUtilsMessageSeverityFlagBitsEXT values (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-messageSeverity-parameter)
    Objects: 0
VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter(ERROR / SPEC): msgNum: -553000032 - Validation Error: [ VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter ] | MessageID = 0xdf09e3a0 | vkCreateDebugUtilsMessengerEXT(): pCreateInfo->messageType contains flag bits (0xcccccccc) which are not recognized members of VkDebugUtilsMessageTypeFlagBitsEXT. The Vulkan spec states: messageType must be a valid combination of VkDebugUtilsMessageTypeFlagBitsEXT values (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkDebugUtilsMessengerCreateInfoEXT-messageType-parameter)
    Objects: 0

Levmur · July 30, 2024, 2:42pm

Same.
Reinstalling Vulkan SDK and updating NVIDIA drivers, adding environment variables, messing with the registry - useless.

I searched paths that Vulkan can’t find and discovered that all these path would be valid if not the last folder "." path there. I tried to add folder with that name but apparentely you can’t create such folder in Windows.

Also these errors occurs during process of instance creation

Any help would be nice because i can’t take these strange issues anymore, it feels like my PC is cursed or smth like this

validation layer: loader_get_json: Failed to open JSON file C:\Program Files (x86)\Epic Games\Launcher\Portal\Extras\Overlay\EOSOverlayVkLayer-Win32.json
validation layer: loader_get_json: Failed to open JSON file C:\Program Files (x86)\Epic Games\Launcher\Portal\Extras\Overlay\EOSOverlayVkLayer-Win32.json
validation layer: loader_get_json: Failed to open JSON file C:\Program Files (x86)\Epic Games\Launcher\Portal\Extras\Overlay\EOSOverlayVkLayer-Win64.json
validation layer: loader_get_json: Failed to open JSON file C:\Program Files (x86)\Epic Games\Launcher\Portal\Extras\Overlay\EOSOverlayVkLayer-Win64.json
validation layer: windows_get_device_registry_files: GUID for 3 is not SoftwareComponent skipping
validation layer: Searching for ICD drivers named .\nvoglv64.dll
validation layer: Layer VK_LAYER_Twitch_Overlay uses API version 1.1 which is older than the application specified API version of 1.3. May cause issues.
validation layer: Loading layer library C:\VulkanSDK\1.3.283.0\Bin\.\VkLayer_khronos_validation.dll
validation layer: Loading layer library C:\Program Files\Common Files\Twitch\Studio\Versions\0.117.8825.41942\.\TwitchNativeOverlay64.dll
validation layer: Loading layer library C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1196b342b24df5d1\.\nvoglv64.dll

Levmur · August 8, 2024, 3:36pm

Ok, right now i got rid of these errors through following this guide → Vulkan Initialization Code - Vulkan Guide (yeap i can’t send link here cool anyway you guys and gals will find it either way i believe in you )
Probably “vkBootstrap” library that initializes things for you (with which you initialize Vulkan in mentioned above guide) somehow doing it more correctly, although i couldn’t right now figure, how exactly

Also if you will have validation error when following this tutorial - it appears that having multiple SDK versions can muddle some OS variables and your code will try to get pointers to layers from different versions of SDK. That solves with deleting ALL SDK versions, reloading PC, and than downloading only one SDK version and them reloading PC again.

Also there is some more junk that can make some nasty errors or conflicts that can be checked with “vkdiag” tool from some random GitHub page that i still can’t include here

I guess that’s all, exactly cause of error is undefined, but it kindaaa solved so i guess i finally can breathe again for 4 hours untill i will get another one crashing my whole project error

system · February 7, 2025, 3:37pm

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