Rendering & presentation
The WebGPU renderer, its presentation boundary, and the path from scene data to a frame.
9 documents · 54 sectionsECS presentation
packages/presentation consumes an independent EntityStore journal cursor and produces version-2 presentation messages.
Presentation protocol
The owned WebGPU renderer now consumes a render-only scene through present(message).
Render graph
The production WebGPU renderer now encodes its shadow, scene and postprocessing passes from a compiled texture graph.
Observatory & capabilities
The development player now places its owned WebGPU renderer in a dedicated worker when worker WebGPU and canvas transfer are available.
Render visibility
The WebGPU backend rejects primitive bounds outside each pass's frustum before submitting instance batches.
Shader activation
The WebGPU renderer accepts a complete trusted scene/post WGSL pair through replaceShaders.
Adaptive quality
Open Menu → Settings → Visual quality.
Graphics recovery
An unexpected WebGPU device loss now pauses the player's input and audio, releases pointer capture, and shows “Rekindling the light.” The simulation worker, room connection, authority…
Visible portals
Authored gateways can show one upright rectangular window per place, with up to two destination views in a chain during shared play.