VKRENDERPASSBEGININF(3)

NAME
VkRenderPassBeginInfo - Structure specifying render pass begin info

C SPECIFICATION

The VkRenderPassBeginInfo structure is defined as:

    typedef struct VkRenderPassBeginInfo {
        VkStructureType        sType;
        const void*            pNext;
        VkRenderPass           renderPass;
        VkFramebuffer          framebuffer;
        VkRect2D               renderArea;
        uint32_t               clearValueCount;
        const VkClearValue*    pClearValues;
    } VkRenderPassBeginInfo;

MEMBERS

    • sType is the type of this structure.

    • pNext is NULL or a pointer to an extension-specific structure.

    • renderPass is the render pass to begin an instance of.

    • framebuffer is the framebuffer containing the attachments that are used with the render pass.

    • renderArea is the render area that is affected by the render pass instance, and is described in more detail below.

    • clearValueCount is the number of elements in pClearValues.

    • pClearValues is an array of VkClearValue structures that contains clear values for each attachment, if the attachment uses a loadOp value of VK_ATTACHMENT_LOAD_OP_CLEAR or if the attachment has a depth/stencil format and uses a stencilLoadOp value of VK_ATTACHMENT_LOAD_OP_CLEAR. The array is indexed by attachment number. Only elements corresponding to cleared attachments are used. Other elements of pClearValues are ignored.

DESCRIPTION

renderArea is the render area that is affected by the render pass instance. The effects of attachment load, store and resolve operations are restricted to the pixels whose x and y coordinates fall within the render area on all attachments. The render area extends to all layers of framebuffer. The application must ensure (using scissor if necessary) that all rendering is contained within the render area, otherwise the pixels outside of the render area become undefined and shader side effects may occur for fragments outside the render area. The render area must be contained within the framebuffer dimensions.

    Note

    There may be a performance cost for using a render area smaller than the framebuffer, unless it matches the render area granularity for the render pass.

Valid Usage

    • clearValueCount must be greater than the largest attachment index in renderPass that specifies a loadOp (or stencilLoadOp, if the attachment has a depth/stencil format) of VK_ATTACHMENT_LOAD_OP_CLEAR
Valid Usage (Implicit)

    • sType must be VK_STRUCTURE_TYPE_RENDER_PASS_BEGIN_INFO

    • pNext must be NULL

    • renderPass must be a valid VkRenderPass handle

    • framebuffer must be a valid VkFramebuffer handle

    • If clearValueCount is not 0, pClearValues must be a pointer to an array of clearValueCount valid VkClearValue unions

    • Both of framebuffer, and renderPass must have been created, allocated, or retrieved from the same VkDevice

SEE ALSO

VkClearValue, VkFramebuffer, VkRect2D, VkRenderPass, VkStructureType, vkCmdBeginRenderPass

DOCUMENT NOTES

For more information, see the Vulkan Specification at URL

https://www.khronos.org/registry/vulkan/specs/1.0/xhtml/vkspec.html#VkRenderPassBeginInfo

This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification,not directly.

COPYRIGHT

Copyright (c) 2014-2016 Khronos Group. This work is licensed under a Creative Commons Attribution 4.0 International License.

AUTHOR

Khronos Group
    Author.