Vulkan.Extensions.VK_EXT_subpass_merge_feedback

VkRenderPassCreationControlEXT - Control about the creation of render pass or subpass

Description

If a RenderPassCreationControlEXT structure is included in the pNext chain of RenderPassCreateInfo2 and its value of disallowMerging is TRUE, the implementation will disable subpass merging for the entire render pass. If a RenderPassCreationControlEXT structure is included in the pNext chain of SubpassDescription2 and its value of disallowMerging is TRUE, the implementation will disable merging the described subpass with previous subpasses in the render pass.

Structure Chaining

Extends the structures

• RenderPassCreateInfo2

• SubpassDescription2

See Also

VK_EXT_subpass_merge_feedback, Bool32, RenderPassCreateInfo2, StructureType, SubpassDescription2, createRenderPass2

VkRenderPassCreationFeedbackInfoEXT - Feedback about the creation of a render pass

See Also

VK_EXT_subpass_merge_feedback, RenderPassCreationFeedbackCreateInfoEXT

VkRenderPassCreationFeedbackCreateInfoEXT - Request feedback about the creation of render pass

Structure Chaining

Extends the structure

• RenderPassCreateInfo2

See Also

VK_EXT_subpass_merge_feedback, RenderPassCreateInfo2, RenderPassCreationControlEXT, RenderPassCreationFeedbackInfoEXT, StructureType, createRenderPass2

VkRenderPassSubpassFeedbackInfoEXT - Feedback about the creation of subpass

See Also

VK_EXT_subpass_merge_feedback, RenderPassSubpassFeedbackCreateInfoEXT, SubpassMergeStatusEXT

VkRenderPassSubpassFeedbackCreateInfoEXT - Request for feedback about the creation of subpass

Structure Chaining

Extends the structure

• SubpassDescription2

See Also

VK_EXT_subpass_merge_feedback, RenderPassCreateInfo2, RenderPassCreationControlEXT, RenderPassSubpassFeedbackInfoEXT, StructureType, SubpassDescription2, createRenderPass2

VkPhysicalDeviceSubpassMergeFeedbackFeaturesEXT - Structure describing whether subpass merging feedback can be supported by the implementation

Members

This structure describes the following feature:

Description

If the PhysicalDeviceSubpassMergeFeedbackFeaturesEXT 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 PhysicalDeviceSubpassMergeFeedbackFeaturesEXT, 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.

Structure Chaining

Extends the structures

• DeviceCreateInfo

• PhysicalDeviceFeatures2

See Also

VK_EXT_subpass_merge_feedback, Bool32, StructureType

VkSubpassMergeStatusEXT - Specify a subpass merging status

Description

• SUBPASS_MERGE_STATUS_MERGED_EXT specifies that the subpass is merged with a previous subpass.

• SUBPASS_MERGE_STATUS_DISALLOWED_EXT specifies that the subpass is not merged because merging was disabled using RenderPassCreationControlEXT. If the render pass does not allow subpass merging, then all subpass statuses are set to this value. If a subpass description does not allow subpass merging, then only that subpass’s status is set to this value.

• SUBPASS_MERGE_STATUS_NOT_MERGED_SIDE_EFFECTS_EXT specifies that the subpass is not merged because it contains side effects.

• SUBPASS_MERGE_STATUS_NOT_MERGED_SAMPLES_MISMATCH_EXT specifies that the subpass is not merged because sample count is not compatible with the previous subpass.

• SUBPASS_MERGE_STATUS_NOT_MERGED_VIEWS_MISMATCH_EXT specifies that the subpass is not merged because view masks do not match with previous subpass.

• SUBPASS_MERGE_STATUS_NOT_MERGED_ALIASING_EXT specifies that the subpass is not merged because of attachments aliasing between them.

• SUBPASS_MERGE_STATUS_NOT_MERGED_DEPENDENCIES_EXT specifies that the subpass is not merged because subpass dependencies do not allow merging.

• SUBPASS_MERGE_STATUS_NOT_MERGED_INCOMPATIBLE_INPUT_ATTACHMENT_EXT specifies that the subpass is not merged because input attachment is not a color attachment from previous subpass or the formats are incompatible.

• SUBPASS_MERGE_STATUS_NOT_MERGED_TOO_MANY_ATTACHMENTS_EXT specifies that the subpass is not merged because of too many attachments.

• SUBPASS_MERGE_STATUS_NOT_MERGED_INSUFFICIENT_STORAGE_EXT specifies that the subpass is not merged because of insufficient memory.

• SUBPASS_MERGE_STATUS_NOT_MERGED_DEPTH_STENCIL_COUNT_EXT specifies that the subpass is not merged because of too many depth/stencil attachments.

• SUBPASS_MERGE_STATUS_NOT_MERGED_RESOLVE_ATTACHMENT_REUSE_EXT specifies that the subpass is not merged because a resolve attachment is reused as an input attachment in a subsequent subpass.

• SUBPASS_MERGE_STATUS_NOT_MERGED_SINGLE_SUBPASS_EXT specifies that the subpass is not merged because the render pass has only one subpass.

• SUBPASS_MERGE_STATUS_NOT_MERGED_UNSPECIFIED_EXT specifies that the subpass is not merged for unspecified reasons. Implementations should return this value when no other SubpassMergeStatusEXT value is appropriate.

See Also

VK_EXT_subpass_merge_feedback, RenderPassSubpassFeedbackInfoEXT