vkUpdateIndirectExecutionSetPipelineEXT(3)

# vkUpdateIndirectExecutionSetPipelineEXT(3) Manual Page

## Name

vkUpdateIndirectExecutionSetPipelineEXT - Update the contents of an indirect execution set

Loading… please wait.

## C Specification

Pipeline elements in an Indirect Execution Set can be updated by calling:

    // Provided by VK_EXT_device_generated_commands
    void vkUpdateIndirectExecutionSetPipelineEXT(
        VkDevice                                    device,
        VkIndirectExecutionSetEXT                   indirectExecutionSet,
        uint32_t                                    executionSetWriteCount,
        const VkWriteIndirectExecutionSetPipelineEXT* pExecutionSetWrites);

## Parameters

- `device` is the logical device that owns the indirect execution set.

- `indirectExecutionSet` is the indirect execution set being updated.

- `executionSetWriteCount` is the number of elements in the `pExecutionSetWrites` array.

- `pExecutionSetWrites` is a pointer to an array of VkWriteIndirectExecutionSetPipelineEXT structures describing the elements to update.

## Description

Valid Usage

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-indirectExecutionSet-11035
  `indirectExecutionSet` must have been created with type VK_INDIRECT_EXECUTION_SET_INFO_TYPE_PIPELINES_EXT

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-executionSetWriteCount-11037
  `executionSetWriteCount` must be less than or equal to `VkIndirectExecutionSetPipelineInfoEXT`::`maxPipelineCount`

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-pExecutionSetWrites-11042
  Each element in the `pExecutionSetWrites` array must have a unique `VkWriteIndirectExecutionSetPipelineEXT`::`index`

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-None-11038
  Each member of the Indirect Execution Set referenced by the update command must not be in use by the device

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-initialPipeline-11324
  If `initialPipeline` was created without VK_PIPELINE_CREATE_2_DESCRIPTOR_HEAP_BIT_EXT, each pipeline in `pExecutionSetWrites` must also have been created without VK_PIPELINE_CREATE_2_DESCRIPTOR_HEAP_BIT_EXT

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-initialPipeline-11325
  If `initialPipeline` was created with VK_PIPELINE_CREATE_2_DESCRIPTOR_HEAP_BIT_EXT, each pipeline in `pExecutionSetWrites` must also have been created with VK_PIPELINE_CREATE_2_DESCRIPTOR_HEAP_BIT_EXT

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-None-11039
  If `initialPipeline` was created without VK_PIPELINE_CREATE_2_DESCRIPTOR_HEAP_BIT_EXT, the layout of each pipeline in `pExecutionSetWrites` must be compatible with the `initialPipeline` used to create the Indirect Execution Set

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-None-11040
  Each pipeline in the Indirect Execution Set must have identically defined static and dynamic state values to the `initialPipeline` used to create the Indirect Execution Set

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-initialPipeline-11147
  Each pipeline in the Indirect Execution Set must have identically defined fragment outputs interface to the `initialPipeline` used to create the Indirect Execution Set

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-initialPipeline-11152
  Each pipeline in the Indirect Execution Set must match the `initialPipeline` used to create the Indirect Execution Set in its included shader stages

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-initialPipeline-11098
  Each pipeline in the Indirect Execution Set must match the `initialPipeline` used to create the Indirect Execution Set in its use of `FragDepth`

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-initialPipeline-11086
  Each pipeline in the Indirect Execution Set must match the `initialPipeline` used to create the Indirect Execution Set in its use of `SampleMask`

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-initialPipeline-11085
  Each pipeline in the Indirect Execution Set must match the `initialPipeline` used to create the Indirect Execution Set in its use of `StencilExportEXT`

Valid Usage (Implicit)

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-device-parameter
  `device` must be a valid VkDevice handle

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-indirectExecutionSet-parameter
  `indirectExecutionSet` must be a valid VkIndirectExecutionSetEXT handle

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-pExecutionSetWrites-parameter
  `pExecutionSetWrites` must be a valid pointer to an array of `executionSetWriteCount` valid VkWriteIndirectExecutionSetPipelineEXT structures

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-executionSetWriteCount-arraylength
  `executionSetWriteCount` must be greater than `0`

- VUID-vkUpdateIndirectExecutionSetPipelineEXT-indirectExecutionSet-parent
  `indirectExecutionSet` must have been created, allocated, or retrieved from `device`

Host Synchronization

- Host access to `indirectExecutionSet` must be externally synchronized

## See Also

VK_EXT_device_generated_commands, VkDevice, VkIndirectExecutionSetEXT, VkWriteIndirectExecutionSetPipelineEXT

## Document Notes

For more information, see the Vulkan Specification.

This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.

## Copyright

Copyright 2014-2026 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0