vkAllocateCommandBuffers - Allocate command buffers from an existing command pool

Parameters

• Device is the logical device that owns the command pool.

• pAllocateInfo is a pointer to a CommandBufferAllocateInfo structure describing parameters of the allocation.
• pCommandBuffers is a pointer to an array of CommandBuffer handles in which the resulting command buffer objects are returned. The array must be at least the length specified by the commandBufferCount member of pAllocateInfo. Each allocated command buffer begins in the initial state.

Description

allocateCommandBuffers can be used to create multiple command buffers. If the creation of any of those command buffers fails, the implementation must destroy all successfully created command buffer objects from this command, set all entries of the pCommandBuffers array to NULL and return the error.

When command buffers are first allocated, they are in the initial state.

Valid Usage (Implicit)

• Device must be a valid Device handle

• pAllocateInfo must be a valid pointer to a valid CommandBufferAllocateInfo structure
• pCommandBuffers must be a valid pointer to an array of pAllocateInfo::commandBufferCount CommandBuffer handles
• The value referenced by pAllocateInfo::commandBufferCount must be greater than 0

Host Synchronization

• Host access to pAllocateInfo::commandPool must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

CommandBuffer, CommandBufferAllocateInfo, Device

A safe wrapper for allocateCommandBuffers and freeCommandBuffers using bracket

The allocated value must not be returned from the provided computation

vkFreeCommandBuffers - Free command buffers

Parameters

• Device is the logical device that owns the command pool.

• CommandPool is the command pool from which the command buffers were allocated.
• commandBufferCount is the length of the pCommandBuffers array.
• pCommandBuffers is a pointer to an array of handles of command buffers to free.

Description

Any primary command buffer that is in the recording or executable state and has any element of pCommandBuffers recorded into it, becomes invalid.

Valid Usage

• All elements of pCommandBuffers must not be in the pending state

• pCommandBuffers must be a valid pointer to an array of commandBufferCount CommandBuffer handles, each element of which must either be a valid handle or NULL

Valid Usage (Implicit)

• Device must be a valid Device handle

• CommandPool must be a valid CommandPool handle
• commandBufferCount must be greater than 0
• CommandPool must have been created, allocated, or retrieved from Device
• Each element of pCommandBuffers that is a valid handle must have been created, allocated, or retrieved from CommandPool

Host Synchronization

• Host access to CommandPool must be externally synchronized

• Host access to each member of pCommandBuffers must be externally synchronized

See Also

CommandBuffer, CommandPool, Device

vkBeginCommandBuffer - Start recording a command buffer

Parameters

• CommandBuffer is the handle of the command buffer which is to be put in the recording state.

• pBeginInfo points to a CommandBufferBeginInfo structure defining additional information about how the command buffer begins recording.

Valid Usage

• CommandBuffer must not be in the recording or pending state

• If CommandBuffer was allocated from a CommandPool which did not have the COMMAND_POOL_CREATE_RESET_COMMAND_BUFFER_BIT flag set, CommandBuffer must be in the initial state
• If CommandBuffer is a secondary command buffer, the pInheritanceInfo member of pBeginInfo must be a valid CommandBufferInheritanceInfo structure
• If CommandBuffer is a secondary command buffer and either the occlusionQueryEnable member of the pInheritanceInfo member of pBeginInfo is FALSE, or the precise occlusion queries feature is not enabled, the queryFlags member of the pInheritanceInfo member pBeginInfo must not contain QUERY_CONTROL_PRECISE_BIT
• If CommandBuffer is a primary command buffer, then pBeginInfo->flags must not set both the COMMAND_BUFFER_USAGE_ONE_TIME_SUBMIT_BIT and the COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT flags

Valid Usage (Implicit)

• CommandBuffer must be a valid CommandBuffer handle

• pBeginInfo must be a valid pointer to a valid CommandBufferBeginInfo structure

Host Synchronization

• Host access to CommandBuffer must be externally synchronized

• Host access to the CommandPool that CommandBuffer was allocated from must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

CommandBuffer, CommandBufferBeginInfo

A safe wrapper for beginCommandBuffer and endCommandBuffer using bracket_

The allocated value must not be returned from the provided computation

vkEndCommandBuffer - Finish recording a command buffer

Parameters

• CommandBuffer is the command buffer to complete recording.

Description

If there was an error during recording, the application will be notified by an unsuccessful return code returned by endCommandBuffer. If the application wishes to further use the command buffer, the command buffer must be reset. The command buffer must have been in the recording state, and is moved to the executable state.

Valid Usage

• CommandBuffer must be in the recording state.

• If CommandBuffer is a primary command buffer, there must not be an active render pass instance
• All queries made active during the recording of CommandBuffer must have been made inactive
• Conditional rendering must not be active
• If CommandBuffer is a secondary command buffer, there must not be an outstanding cmdBeginDebugUtilsLabelEXT command recorded to CommandBuffer that has not previously been ended by a call to cmdEndDebugUtilsLabelEXT.
• If CommandBuffer is a secondary command buffer, there must not be an outstanding cmdDebugMarkerBeginEXT command recorded to CommandBuffer that has not previously been ended by a call to cmdDebugMarkerEndEXT.

Valid Usage (Implicit)

• CommandBuffer must be a valid CommandBuffer handle

Host Synchronization

• Host access to CommandBuffer must be externally synchronized

• Host access to the CommandPool that CommandBuffer was allocated from must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

CommandBuffer

vkResetCommandBuffer - Reset a command buffer to the initial state

Parameters

• CommandBuffer is the command buffer to reset. The command buffer can be in any state other than pending, and is moved into the initial state.

• Flags is a bitmask of CommandBufferResetFlagBits controlling the reset operation.

Description

Any primary command buffer that is in the recording or executable state and has CommandBuffer recorded into it, becomes invalid.

Valid Usage

• CommandBuffer must not be in the pending state

• CommandBuffer must have been allocated from a pool that was created with the COMMAND_POOL_CREATE_RESET_COMMAND_BUFFER_BIT

Valid Usage (Implicit)

• CommandBuffer must be a valid CommandBuffer handle

• Flags must be a valid combination of CommandBufferResetFlagBits values

Host Synchronization

• Host access to CommandBuffer must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

CommandBuffer, CommandBufferResetFlags

VkCommandBufferAllocateInfo - Structure specifying the allocation parameters for command buffer object

Valid Usage (Implicit)

See Also

CommandBufferLevel, CommandPool, StructureType, allocateCommandBuffers

VkCommandBufferInheritanceInfo - Structure specifying command buffer inheritance info

Valid Usage

• If the inherited queries feature is not enabled, occlusionQueryEnable must be FALSE

• If the inherited queries feature is enabled, queryFlags must be a valid combination of QueryControlFlagBits values
• If the inherited queries feature is not enabled, queryFlags must be 0
• If the pipeline statistics queries feature is enabled, pipelineStatistics must be a valid combination of QueryPipelineStatisticFlagBits values
• If the pipeline statistics queries feature is not enabled, pipelineStatistics must be 0

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_COMMAND_BUFFER_INHERITANCE_INFO

• Each pNext member of any structure (including this one) in the pNext chain must be either NULL or a pointer to a valid instance of CommandBufferInheritanceConditionalRenderingInfoEXT or CommandBufferInheritanceRenderPassTransformInfoQCOM
• The sType value of each struct in the pNext chain must be unique
• Both of Framebuffer, and RenderPass that are valid handles of non-ignored parameters must have been created, allocated, or retrieved from the same Device

See Also

Bool32, CommandBufferBeginInfo, Framebuffer, QueryControlFlags, QueryPipelineStatisticFlags, RenderPass, StructureType

VkCommandBufferBeginInfo - Structure specifying a command buffer begin operation

Valid Usage

• If Flags contains COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BIT, the RenderPass member of pInheritanceInfo must be a valid RenderPass

• If Flags contains COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BIT, the subpass member of pInheritanceInfo must be a valid subpass index within the RenderPass member of pInheritanceInfo
• If Flags contains COMMAND_BUFFER_USAGE_RENDER_PASS_CONTINUE_BIT, the Framebuffer member of pInheritanceInfo must be either NULL_HANDLE, or a valid Framebuffer that is compatible with the RenderPass member of pInheritanceInfo

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_COMMAND_BUFFER_BEGIN_INFO

• pNext must be NULL or a pointer to a valid instance of DeviceGroupCommandBufferBeginInfo
• The sType value of each struct in the pNext chain must be unique
• Flags must be a valid combination of CommandBufferUsageFlagBits values

See Also

CommandBufferInheritanceInfo, CommandBufferUsageFlags, StructureType, beginCommandBuffer