← RIVX brochureChoosing what the export retains

What stays editable after export?

RIVX can deliver a baked appearance or keep scene data in a player. This small browser study makes that choice visible: scrub an actual .riv bake, change a live material, then orbit the retained scene.

Light position drives every pane. Roughness and IOR affect the two live shaders; the portable bake keeps its authored materials. Only the retained pane accepts camera movement.

01

Portable .riv

Official Rive WebGL2 runtime

Loading the real .riv…

25 light poses in five named material regions. Scalable vector accents accompany finite-resolution image layers. The camera is fixed.

Download the actual .riv ↓
02

Host-rendered lighting

Custom WebGL2 + official Rive vectors

Preparing shader…

The host evaluates the same scene continuously. Light, roughness and glass IOR stay editable; this pane keeps the baked camera for comparison.

The browser owns this shader; it is not packaged in the downloaded .riv.

03

Retained scene

Analytic RIVX study + official Rive vectors
Drag to orbit · ← → keys

Preparing retained scene…

Move around the sphere: visibility and the refracted floor are recalculated. The vector contour follows the same camera.

Dedicated study schema; not a universal native .rivx loader.

The export decides which edits survive. The first pane owns an authored light timeline. The other two retain a renderer; the third also exposes its camera. These are choices made by this study, not limits of GPU Canvas.

Inside these outputs · retained data and approximations
The connection to RIVX

Scene → lighting → marks

  1. Keep scene identities. Spheres, floor and wall are separate regions in the portable bake.
  2. Choose what to evaluate later. The host retains a compact shader and scene parameters for live light, material and camera changes.
  3. Deliver ordinary Rive content. The bake contains image layers and keyed vector marks. The live panes place ordinary Rive contours over host-rendered pixels.

This is a controlled browser explanation of the export boundary. Its dedicated scene schema is not a loader for arbitrary native RIVX projects. Interaction needs no GPU-to-CPU pixel readback; the offline bake utility uses readback to create its images.

What the files actually contain
OutputRetained data
glass-light.riv25 raster light poses, five named image regions, 171 vector marks and authored keys. Fixed camera and baked materials.
Host-rendered paneA WebGL2 renderer, analytic scene and ordinary Rive vector overlay. Live lighting and materials.
Retained scene paneThe same renderer plus an editable camera. Visibility and refraction are evaluated for the new view.

Glass uses Schlick Fresnel, Beer tint, two sphere refractions and one reflected ray. The caustic is a shaped artistic lobe; there is no photon estimate or multiple-bounce GI here.

Compare the actual GPU Canvas and host export pairs →