Closed tycho closed 1 month ago
thanks for reporting this, was able to easily reproduce
the core issue is the vk.xml
is depends="VK_VERSION_1_2,VK_KHR_timeline_semaphore"
but changing it to depends="VK_KHR_timeline_semaphore,VK_VERSION_1_2"
fixes it... I assume this is just because things were always in that order and this one flipped it and the VVL never caught it... will get a fix in quick
Environment:
Describe the Issue
If creating a Vulkan device with a VK 1.1 instance with
VK_NV_low_latency2
enabled, it complains:Expected behavior
The extension is documented as requiring Vulkan 1.2 or
VK_KHR_timeline_semaphore
:https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VK_NV_low_latency2.html
It seems like it should be sufficient to pass validation when using it in a VK 1.1 context where
VK_KHR_timeline_semaphore
is enabled.Valid Usage ID
VUID-vkCreateDevice-ppEnabledExtensionNames-01387
forVK_NV_low_latency2