VP_KHR_roadmap_2026 causes validation errors

[awesomekyle]

This seems to be a bug in the profile spec itself rather than the Vulkan-Profiles library, though I'm not sure if this or Vulkan-Headers is the canonical source of the profiles.

The VP_KHR_roadmap_2026 profile includes VK_KHR_surface_maintenance1, VK_KHR_present_id2 and VK_KHR_present_wait2, all of which require VK_KHR_get_surface_capabilities2 which isn't included in vulkanextensionrequirements_roadmap2026. When run with the Vulkan validation layer, it shows this error:

Validation Error: [ VUID-vkCreateInstance-ppEnabledExtensionNames-01388 ] | MessageID = 0xe5e52180
vkCreateInstance(): pCreateInfo->ppEnabledExtensionNames[2] Missing extension required by the instance extension VK_KHR_surface_maintenance1: VK_KHR_get_surface_capabilities2.
The Vulkan spec states: All required extensions for each extension in the VkInstanceCreateInfo::ppEnabledExtensionNames list must also be present in that list (https://docs.vulkan.org/spec/latest/chapters/initialization.html#VUID-vkCreateInstance-ppEnabledExtensionNames-01388)

Adding VK_KHR_get_surface_capabilities2 to vulkanextensionrequirements_roadmap2026 eliminates the error.

Additionally, pushDescriptor in vulkan14requirements_roadmap2026:features:VkPhysicalDeviceVulkan14Features needs to be true due to VK_KHR_push_descriptor being enabled in vulkanextensionrequirements_roadmap2024:

Validation Error: [ VUID-VkDeviceCreateInfo-ppEnabledExtensionNames-10858 ] | MessageID = 0x6ea7cdc3
vkCreateDevice(): VK_KHR_push_descriptor is enabled but VkPhysicalDeviceVulkan14Features::pushDescriptor is not VK_TRUE.
The Vulkan spec states: If ppEnabledExtensionNames contains "VK_KHR_push_descriptor" and the pNext chain includes a VkPhysicalDeviceVulkan14Features structure, then VkPhysicalDeviceVulkan14Features::pushDescriptor must be VK_TRUE (https://docs.vulkan.org/spec/latest/chapters/devsandqueues.html#VUID-VkDeviceCreateInfo-ppEnabledExtensionNames-10858)
Objects: 1
    [0] VkPhysicalDevice 0x5555561dfb50

[christophe-lunarg]

Thanks for the details report, we are working on a fix.

[christophe-lunarg]

If you want a fix now, you can used the profile file in KhronosGroup/Vulkan-Profiles#851

It has been agreed by the Vulkan working group and will be available in a upcoming Vulkan Header, I guess Header 344.