“Create a rendering pipeline flowchart for a desktop deferred physically based renderer: update camera, transforms, and materials; perform frustum and occlusion culling; render a directional shadow map and opaque geometry to a G-buffer; build tiled light lists; run deferred PBR lighting; forward-render transparent objects; apply temporal anti-aliasing, bloom, color grading, tone mapping, UI compositing, and present the frame.”
Die dahinterstehenden Entscheidungen verstehen.
Off-screen and occluded geometry is removed before expensive passes.
Opaque surface attributes are recorded once for deferred lighting.
Light lists limit lighting calculations to relevant screen regions.
Transparent objects are drawn after deferred opaque lighting in a forward pass.
Use this for a desktop or console renderer with physically based materials and a large opaque scene. It is not intended for a mobile power-saving or ray-tracing pipeline.
Häufige Fragen
Why use a G-buffer?
It stores opaque surface data so lighting can be calculated later without rerasterizing geometry.
Why render transparency forward?
Transparent surfaces need ordered blending and do not fit the usual deferred composition path.
What does tone mapping do?
It maps high-dynamic-range lighting values into the displayable output range.