#include <RenderAttachmentLayout.h>
|
static void | Reflect (ReflectContext *context) |
|
|
uint32_t | m_attachmentCount = 0 |
| Number of total attachments in the list.
|
|
AZStd::array< Format, Limits::Pipeline::RenderAttachmentCountMax > | m_attachmentFormats = { {} } |
| List with all attachments (renderAttachments, resolveAttachments and depth/stencil attachment).
|
|
uint32_t | m_subpassCount = 0 |
| Number of subpasses.
|
|
AZStd::array< SubpassRenderAttachmentLayout, Limits::Pipeline::SubpassCountMax > | m_subpassLayouts |
| List with the layout of each subpass.
|
|
A RenderAttachmentLayout consist of a description of one or more subpasses. Each subpass is a collection of render targets, subpass inputs and depth stencil attachments. Each subpass corresponds to a phase in the rendering of a Pipeline. Subpass outputs can be read by other subpasses as inputs. A RenderAttachmentLayout may be implemented by the platform using native functionality, achieving a performance gain for that specific platform. On other platforms, it may be emulated to achieve the same result but without the performance benefits. For example, Vulkan supports the concept of subpass natively.
The documentation for this class was generated from the following file:
- Gems/Atom/RHI/Code/Include/Atom/RHI.Reflect/RenderAttachmentLayout.h