Namespace Apogee.Rendering.Graph¶
Classes¶
The graph, compiled: which passes run, in what order, what is allocated, and the barriers in front of each pass.
One image transition the planner put in front of a pass (or at the end): a rectangle of mips and layers going from one state to another.
What a pass declares while the graph is built: how it uses each image and buffer. The graph derives culling, lifetimes and barriers from this. Every image method takes an optional
What the planner decided about one pass.
One frame's rendering as a graph. Passes declare how they use images and buffers;
The graph is inconsistent: a pass reads something nothing writes, uses a resource two incompatible ways, or has mismatched attachments.
The images and buffers graphs allocate, kept between frames so that a steady-state frame allocates nothing. There is one set per frame in flight (a resource is only reused by the frame slot that used it before, once the GPU has finished with it), and one that goes unused for a while is freed.
Structs¶
A graph image: a transient one the graph allocates, or an imported one (the window's image, a persistent texture). Valid for one graph.
What a pass's execute callback gets: the command recorder and its resources.
An image as a pass sees it while it runs.
A rectangle of an image's subresources: some mip levels of some array layers (six per cube). A pass that declares one of these uses only that part of the image, and the graph tracks and transitions the parts
separately. A count of