KhronosGroup / Vulkan-Samples

One stop solution for all Vulkan samples
Apache License 2.0
4.33k stars 648 forks source link

Validation error due to missing extension on cross-vendor OpenCL interop sample #949

Closed SaschaWillems closed 6 months ago

SaschaWillems commented 8 months ago

The cross-vendor OpenCL interop sample shows a validation error due to a missing ext at startup:

[error] [framework\core\instance.cpp:50] -579609649 - VUID-VkPhysicalDeviceProperties2-pNext-pNext: Validation Error: [ VUID-VkPhysicalDeviceProperties2-pNext-pNext ] Object 0: handle = 0x1f870ad53d0, type = VK_OBJECT_TYPE_INSTANCE; | MessageID = 0xdd73dbcf | vkGetPhysicalDeviceProperties2KHR(): pProperties->pNext includes a pointer to a VkStructureType (VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_ID_PROPERTIES), but its parent extension VK_KHR_external_fence_capabilities has not been enabled. The Vulkan spec states: Each pNext member of any structure (including this one) in the pNext chain must be either NULL or a pointer to a valid struct for extending VkPhysicalDeviceProperties2 (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkPhysicalDeviceProperties2-pNext-pNext)

That error wasn't present when I wrote the sample, so it probably was added with a more recent layer version. I'll take a look at this.