Documentation
    Preparing search index...

    Interface SceneRenderPass

    A pass the graph can drive itself: one renderer.render call (§63, §64).

    The three fields are R-4's render arguments minus the interpolation record, which belongs to the frame rather than to the pass and is therefore supplied by RenderGraph.execute. Clear policy is not here — it lives on each Viewport (clearColor, §48), which is also what makes a compositing pass expressible: a view with no clearColor draws over what an earlier pass left in the same surface.

    interface SceneRenderPass {
        kind?: "scene";
        root: Node;
        target?: RenderTarget | null;
        views: readonly Viewport[];
    }
    Index
    kind? root target? views
    kind?: "scene"

    Present and "scene", or absent — this is the default form. The discriminant exists so CustomRenderPass can be told apart without a structural guess.

    root: Node

    Subtree to draw; usually the Scene (§64 builds a list from any root).

    target?: RenderTarget | null

    Off-screen surface to draw into (R-4), or absent/null for the backend's default drawing buffer. A pass with no target is a screen pass; §63's "Final Composite" is the usual one.

    views: readonly Viewport[]

    Views to draw it through, in order (§48) — this is §63's "viewport-specific pipelines" at this tier: two passes over the same root with different views are two pipelines.

    Settings
    Member Visibility

    On This Page
    Properties