A compact camera domain.
45 × 256 × 192 is 8.44 MiB after image decoding. Expanding camera axes or adding a clock multiplies the sample budget. This deliberately small example covers −60° to +60° azimuth and 15° to 65° elevation.
A camera becomes a small lattice.
Drag in two directions. Every step selects one of 45 real baked views. The coarse sampling is the subject of this study.
OFFICIAL RIVE · NO LIVE 3DDrag in both directions · arrow keys also work
9 × 5 VIEW SAMPLES
Two inputs. One stored pose.
Horizontal dragging chooses azimuth. Vertical dragging chooses elevation. The gold ticks inside the Rive drawing carry the same two keyed values.
A live camera would project geometry. Here, the browser only maps the two controls to a Rive animation frame. Between samples the view deliberately holds, making the storage tradeoff visible.
Loading the ordinary Rive drawing…
Download ordinary .riv45 images · 256 × 192 each
What is actually baked.
The views come from the neighboring retained-volume / baked-receiver study. Its glass shading and finite hourglass reconstruction become ordinary embedded images. The Rive file holds those images, visibility keys and two vector ticks. No geometry, shader or transport solver runs in playback.
The other choice stays live.
The transport-bake Suite retains the medium paths and receiver field, so its camera can move continuously. This specimen deliberately gives up that freedom to use an unchanged official Rive runtime. It is a browser-authored export study, not a claim that this page runs the native desktop backend.