vkCmdBeginCustomResolveEXT

To begin resolving attachments using render pass draws, call:

void vkCmdBeginCustomResolveEXT(
    VkCommandBuffer commandBuffer,
    const VkBeginCustomResolveInfoEXT* pBeginCustomResolveInfo);

pub fn cmd_begin_custom_resolve_ext(
    command_buffer: vk::CommandBuffer,
    p_begin_custom_resolve_info: *const vk::BeginCustomResolveInfoEXT,
);

• commandBuffer is the command buffer in which to record the command.
• pBeginCustomResolveInfo is an optional struct with which to extend functionality.

Following this call, any resolveImageView with resolveMode set to VK_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.

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.