VkPhysicalDeviceDataGraphFeaturesARM(3)

# VkPhysicalDeviceDataGraphFeaturesARM(3) Manual Page

## Name

VkPhysicalDeviceDataGraphFeaturesARM - Structure describing features to control data graph pipelines

Loading… please wait.

## C Specification

The `VkPhysicalDeviceDataGraphFeaturesARM` structure is defined as:

    // Provided by VK_ARM_data_graph
    typedef struct VkPhysicalDeviceDataGraphFeaturesARM {
        VkStructureType    sType;
        void*              pNext;
        VkBool32           dataGraph;
        VkBool32           dataGraphUpdateAfterBind;
        VkBool32           dataGraphSpecializationConstants;
        VkBool32           dataGraphDescriptorBuffer;
        VkBool32           dataGraphShaderModule;
    } VkPhysicalDeviceDataGraphFeaturesARM;

## Members

- `sType` is a VkStructureType value identifying this structure.

- `pNext` is `NULL` or a pointer to a structure extending this structure.

- `dataGraph` specifies whether data graph pipelines can be used.

- `dataGraphUpdateAfterBind` specifies whether data graph pipelines can be created with a VkPipelineLayout that uses one or more VkDescriptorSetLayout objects created with the VK_DESCRIPTOR_SET_LAYOUT_CREATE_UPDATE_AFTER_BIND_POOL_BIT bit set.

- `dataGraphSpecializationConstants` specifies whether data graph pipelines can be created from shader modules that use specialization constants.

- `dataGraphDescriptorBuffer` specifies whether data graph pipelines can use descriptor buffers.

- `dataGraphShaderModule` specifies whether data graph pipelines can be created from a shader module.

## Description

If the `VkPhysicalDeviceDataGraphFeaturesARM` structure is included in the `pNext` chain of the VkPhysicalDeviceFeatures2 structure passed to vkGetPhysicalDeviceFeatures2, it is filled in to indicate whether each corresponding feature is supported. If the application wishes to use a VkDevice with any features described by `VkPhysicalDeviceDataGraphFeaturesARM`, it must add an instance of the structure, with the desired feature members set to VK_TRUE, to the `pNext` chain of VkDeviceCreateInfo when creating the VkDevice.

Valid Usage (Implicit)

- VUID-VkPhysicalDeviceDataGraphFeaturesARM-sType-sType
  `sType` must be VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_DATA_GRAPH_FEATURES_ARM

## See Also

VK_ARM_data_graph, VkBool32, VkStructureType

## 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