KhronosGroup / KhronosGroup/Vulkan-Docs
vkBeginCommandBuffer valid usage inconsistency
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
In [Command Buffer Lifecycle](https://docs.vulkan.org/spec/latest/chapters/cmdbuffers.html#commandbuffers-lifecycle):
> Command buffers allocated from a command pool created with [VK_COMMAND_POOL_CREATE_RESET_COMMAND_BUFFER_BIT](https://docs.vulkan.org/spec/latest/chapters/cmdbuffers.html#VkCommandPoolCreateFlagBits) in the invalid, recording, or executable state **can** also be transitioned to the recording state by [vkBeginCommandBuffer](https://docs.vulkan.org/spec/latest/chapters/cmdbuffers.html#vkBeginCommandBuffer).
But in [Valid Usage](https://docs.vulkan.org/spec/latest/chapters/cmdbuffers.html#VUID-vkBeginCommandBuffer-commandBuffer-00049):
> commandBuffer **must** not be in the[ recording or pending state](https://docs.vulkan.org/spec/latest/chapters/cmdbuffers.html#commandbuffers-lifecycle)
First one says it's fine to restart recording in the recording state, but the second one forbids it.
Contributor guide
Assessment
This issue has not been assessed yet.