vkCmdBeginCustomResolveEXT - Begins a shader resolve operation

Description

Following this call, any resolveImageView with resolveMode set to RESOLVE_MODE_CUSTOM_BIT_EXT will be written by outputs which would otherwise have written to the imageView image until the end of the current render pass instance.

Following this call, the fragment area may be reduced to (1,1) if a fragment density map is attached. If this occurs, reads of input attachments mapped to a color, depth, or stencil attachment return the value for the original larger fragment containing the smaller fragment. Reads of input attachments not mapped to a color, depth, or stencil attachment use the new fragment area.

Because the content of any depth/stencil resolve attachment as well as any color resolve attachment is undefined at the beginning of a resolve operation, any depth testing, stencil testing, or blending operation which sources these undefined values also has undefined result value.

During a custom resolve pass, multiple fragment invocations writing to the same (x, y, layer, view, sample) coordinate, i.e. overdraw, will produce undefined behavior.

Implementations are allowed to implement custom resolve attachment writes through other mechanisms than framebuffer attachment writes, which would normally obey rules of rasterization order.

Valid Usage

• The current render pass instance must have been started or resumed by cmdBeginRendering in this commandBuffer

• cmdBeginCustomResolveEXT must not have already been recorded in the current render pass instance
• The current render pass instance must have specified RENDERING_CUSTOM_RESOLVE_BIT_EXT
• The current render pass instance must not have specified RENDERING_SUSPENDING_BIT

Valid Usage (Implicit)

• commandBuffer must be a valid CommandBuffer handle

• If pBeginCustomResolveInfo is not NULL, pBeginCustomResolveInfo must be a valid pointer to a valid BeginCustomResolveInfoEXT structure
• commandBuffer must be in the recording state
• The CommandPool that commandBuffer was allocated from must support QUEUE_GRAPHICS_BIT operations
• This command must only be called inside of a render pass instance
• This command must not be called between suspended render pass instances
• This command must only be called outside of a video coding scope

Host Synchronization

• Host access to commandBuffer must be externally synchronized

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

Command Properties

'

Conditional Rendering

vkCmdBeginCustomResolveEXT is affected by conditional rendering

See Also

VK_EXT_custom_resolve, VK_KHR_dynamic_rendering, VK_VERSION_1_3, BeginCustomResolveInfoEXT, CommandBuffer

VkBeginCustomResolveInfoEXT - Structure specifying shader resolve information

Valid Usage (Implicit)

See Also

VK_EXT_custom_resolve, VK_KHR_dynamic_rendering, VK_VERSION_1_3, StructureType, cmdBeginCustomResolveEXT

VkPhysicalDeviceCustomResolveFeaturesEXT - Structure indicating support for shader resolves

Members

This structure describes the following feature:

Description

If the PhysicalDeviceCustomResolveFeaturesEXT structure is included in the pNext chain of the PhysicalDeviceFeatures2 structure passed to getPhysicalDeviceFeatures2, it is filled in to indicate whether each corresponding feature is supported. If the application wishes to use a Device with any features described by PhysicalDeviceCustomResolveFeaturesEXT, it must add an instance of the structure, with the desired feature members set to TRUE, to the pNext chain of DeviceCreateInfo when creating the Device.

Valid Usage (Implicit)

See Also

VK_EXT_custom_resolve, Bool32, StructureType

VkCustomResolveCreateInfoEXT - Structure specifying format info for custom resolves

Description

If the pNext chain includes this structure for one of:

• a GraphicsPipelineCreateInfo for a pipeline created without a RenderPass
• a CommandBufferInheritanceInfo for a secondary command buffer within a render pass instance begun with cmdBeginRendering.

it specifies the formats used in custom resolves within the same render pass. It also specifies that the corresponding object will be used in a render pass which contains a custom resolve operation.

If the pNext chain includes this structure for a ShaderCreateInfoEXT for a fragment shader object, it only specifies that the fragment shader will be used in a custom resolve operation.

If a graphics pipeline is created with a valid RenderPass, parameters of this structure are ignored.

If customResolve is FALSE, the pipeline can only be used outside the custom resolve section. If customResolve is TRUE, the pipeline can only be used inside the custom resolve section.

When a dynamic render pass instance contains a custom resolve operation and the dynamicRenderingUnusedAttachments feature is not enabled , all pipelines used to draw in such render pass must include this structure and have identical format information in it. When a dynamic render pass does not contain a custom resolve operation and the dynamicRenderingUnusedAttachments feature is not enabled , all pipelines used to draw in such render pass must not include this structure.

If the dynamicRenderingUnusedAttachments feature is enabled, then when this structure is not included in the pNext chain for GraphicsPipelineCreateInfo, customResolve is FALSE, colorAttachmentCount is 0, and depthAttachmentFormat and stencilAttachmentFormat are FORMAT_UNDEFINED.

If depthAttachmentFormat, stencilAttachmentFormat, or any element of pColorAttachmentFormats is FORMAT_UNDEFINED, it indicates that the corresponding attachment is unused within the resolve portion of the render pass. Valid formats indicate that an attachment can be used - but it is still valid to set the attachment to NULL when beginning rendering.

When passed as a pNext member to a ShaderCreateInfoEXT struct for use with fragment density maps, the colorAttachmentCount, pColorAttachmentFormats, depthAttachmentFormat, and stencilAttachmentFormat members of this struct are ignored. When not passed as a pNext member, customResolve is FALSE.

Valid Usage

• colorAttachmentCount must be less than or equal to maxColorAttachments

• If depthAttachmentFormat is not FORMAT_UNDEFINED, it must be a format that includes a depth component
• If depthAttachmentFormat is not FORMAT_UNDEFINED, it must be a format with potential format features that include FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT
• If any element of pColorAttachmentFormats is not FORMAT_UNDEFINED, it must be a format with potential format features that include FORMAT_FEATURE_COLOR_ATTACHMENT_BIT , or FORMAT_FEATURE_2_LINEAR_COLOR_ATTACHMENT_BIT_NV if the linearColorAttachment feature is enabled
• If stencilAttachmentFormat is not FORMAT_UNDEFINED, it must be a format that includes a stencil aspect
• If stencilAttachmentFormat is not FORMAT_UNDEFINED, it must be a format with potential format features that include FORMAT_FEATURE_DEPTH_STENCIL_ATTACHMENT_BIT
• If depthAttachmentFormat is not FORMAT_UNDEFINED and stencilAttachmentFormat is not FORMAT_UNDEFINED, depthAttachmentFormat must equal stencilAttachmentFormat

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_CUSTOM_RESOLVE_CREATE_INFO_EXT

See Also

VK_EXT_custom_resolve, VK_KHR_dynamic_rendering, VK_VERSION_1_3, Bool32, Format, StructureType