VkPipelineCreateFlags2CreateInfo 0 flags
Opened this issue · 4 comments
There's a validation error about 0 flags being passed with VkPipelineCreateFlags2CreateInfo.
It doesn't cause any problems in practice but it's a bit ugly.
err: VUID-VkPipelineCreateFlags2CreateInfo-flags-requiredbitmask:
err: vkCreateComputePipelines(): pCreateInfos[0].pNext.flags is zero.
err: The Vulkan spec states: flags must not be 0 (https://docs.vulkan.org/spec/latest/chapters/pipelines.html#VUID-VkPipelineCreateFlags2CreateInfo-flags-requiredbitmask)
err: VUID-VkPipelineCreateFlags2CreateInfo-flags-requiredbitmask:
err: vkCreateComputePipelines(): pCreateInfos[0].pNext.flags is zero.
err: The Vulkan spec states: flags must not be 0 (https://docs.vulkan.org/spec/latest/chapters/pipelines.html#VUID-VkPipelineCreateFlags2CreateInfo-flags-requiredbitmask)
i don't understand that VU, what flag are we missing?
If this is just a generic rule that requires us to not pass the structure at all unless any flags are active, then that smells like a spec bug and a massive usability issue.
I think we mustn't add VkPipelineCreateFlags2CreateInfo to the pNext chain if flags is 0.
That is... exceptionally stupid and annoying.
Agreed, stupid pointless rule.