Views, coordinate spaces, and temporal state¶
A RenderView supplies the camera, content extent, and view-specific state. Preserve independent identity for simultaneous cameras. Camera motion, a camera cut, or extent changes must reach the graph and its history owners using the actual view contract.
Coordinate conventions¶
The ordinary basis is right-handed with world +Y up and view -Z forward. Positive view distance is the negative of view-space Z.
Matrices apply to column vectors. Compose clip-from-view with view-from-world in that order. Affine translation is the last column.
Built-in perspective uses reverse-Z with zero-to-one depth and an infinite far plane. Near maps to 1, and infinity approaches the depth clear value of 0. Orthographic projection uses finite planes.
Canonical projection supplies the raster-facing Y flip. Screen UV starts at the top left. Avoid adding a second flip in an ordinary pass.
Construct GPU positions relative to the camera before converting far-away world coordinates to floats. Projection distances and ordinary lighting distances use metres. Angles in the camera projection are radians.
Temporal state¶
Frame-local motion uses current minus previous unjittered screen UV. A provider may adapt the sign and units as part of its own API. Camera jitter is in internal content-resolution pixels. Use the previous submitted view and resource state that actually owns the history, applying cut and extent invalidation where required.
Anti-aliasing, reflection reconstruction, and progressive reference accumulation are separate history consumers. Reflection denoising can advance even when image TAA is disabled. A fixed-camera progressive mean is invalid after material or lighting changes unless the consumer resets it. Finite real-time history deliberately rejects or downweights disocclusions and cannot be interpreted as an unbiased progressive reference.
For the relationships between internal, output, and window extents see Resolution domains and upscaling.