# VkPhysicalDeviceMaintenance10FeaturesKHR(3) Manual Page

## Name

VkPhysicalDeviceMaintenance10FeaturesKHR - Structure describing whether the implementation supports maintenance10 functionality

Loading… please wait.

## C Specification

The `VkPhysicalDeviceMaintenance10FeaturesKHR` structure is defined as:

    // Provided by VK_KHR_maintenance10
    typedef struct VkPhysicalDeviceMaintenance10FeaturesKHR {
        VkStructureType    sType;
        void*              pNext;
        VkBool32           maintenance10;
    } VkPhysicalDeviceMaintenance10FeaturesKHR;

## Members

This structure describes the following feature:

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

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

- `maintenance10` indicates that the implementation supports the following:

  - New image format feature bits that indicate support for copying depth or stencil aspects using non-graphics queue families

  - If vkCmdSetSampleMaskEXT is called with `pSampleMask` set to `NULL`, it is treated as if the mask has all bits set to `1`.

  - Add vkCmdEndRendering2KHR as an extensible version of vkCmdEndRendering

  - Add input attachment information to dynamic rendering

  - Require that vertex inputs follow sRGB encoding when those formats are used, instead of being underspecified.

  - Add a query to determine if sRGB images are resolved in nonlinear or linear space by default

  - Add an optional feature to allow applications to override the default sRGB resolve behavior

  - Add resolve mode and depth-stencil resolve support to `vkCmdResolveImage2` to bring it in-line with render pass attachment resolves

## Description

If the `VkPhysicalDeviceMaintenance10FeaturesKHR` 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 `VkPhysicalDeviceMaintenance10FeaturesKHR`, 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-VkPhysicalDeviceMaintenance10FeaturesKHR-sType-sType
  `sType` must be `VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MAINTENANCE_10_FEATURES_KHR`

## See Also

VK_KHR_maintenance10, 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-2025 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0