Volux Docs

Frontend Behavior

What runs for visitors — events, physics, audio, cameras, and responsive bands on the public page.

Publishing hands the page to the public frontend. None of the interactive behavior runs while you edit — the editor only authors the settings — so this page is the contract for what starts moving once a visitor loads the page.

The published page with the live scene
The published page with the live scene

What comes alive

The page mounts one runtime per browser page, and it drives everything interactive:

  • Events — object and element triggers (click, hover, key, scroll, collision, distance, and more) run through a single event engine. The editor never fires them, so verify interactions on the rendered page, not in the viewport.
  • Physics — the simulation steps on the public page only, on a deterministic fixed clock. A scene whose physics are disabled simply skips it.
  • Audio — speakers play through the page's audio context, subject to browser autoplay rules (below).
  • DOM element behavior — linked page elements can carry states and triggers of their own; the frontend watches and drives them with one page-level driver, no per-element listeners.

Events for visitors

Objects use the same trigger set the editor's add menu offers: mouse up, down, press, and hover; key up, down, and press; start (page load); screen resize; distance; state change; collision; and drag and drop. Condition triggers — distance, state change, collision, screen resize, and drag and drop — carry Then and Else action lists, and the press and hover triggers can auto-reverse when the interaction disengages.

Page elements (the HTML around your scenes) get a smaller trigger set: click, hover, and scroll. Element events drive the same action system — transitions, links, camera switches, timeline clips.

Clicks pass through

The frontend listens to the page without ever blocking it: it never swallows or stops a native click. A button under your scene still receives its own clicks, and an object click can double-deliver to both the mesh and the element beneath it — by design.

Physics runs the fixed clock

When a scene's physics are enabled, the simulation starts on the visitor's page — the editor never simulates. The scene's playback window decides when: autoplay releases the bodies after a delay, or manual holds them until an event fires. Per object, participation follows its enable setting and visibility — a hidden object sits out of the simulation.

The engine steps deterministically at 60 Hz — the same settings produce the same motion. The physics engine itself ships as a lazy-loaded chunk, so pages without physics never download it.

Audio and autoplay policies

Browsers refuse sound until the visitor interacts with the page. A speaker set to autoplay arms a first-gesture unlock: the first click, tap, or keypress anywhere on the page resumes audio and starts the speaker. Autoplaying speakers that were interrupted resume from there.

Silent until the first gesture

If your page autoplays audio, visitors see it start only after they click, tap, or press a key — that is the browser's rule, not a Volux setting. Drive audio with a click or hover event if you want guaranteed sound.

Cameras per device

Each scene renders through its default camera, and the default is a per-breakpoint setting: you can frame one camera for desktop and another for mobile, and visitors on each width see their band's framing. The frontend resolves the visitor's viewport width against the document's breakpoint definitions and picks the matching default.

A Switch Camera event action changes what the visitor sees for that page view. The switch lasts for the visit — reload the page and the default camera returns. A scene still pinned to the editor's personal free-nav camera (legacy data with no real camera) is skipped rather than rendered.

For the authored controls — orbit limits, damping, lock-to-view — see Cameras.

Responsive bands on the page

The same band logic you author with in the editor runs on the page: the frontend detects the visitor's viewport width, resolves the active breakpoint, and every per-band setting — camera defaults, scene containers, physics windows, element states — follows. Resizing the browser window re-resolves the band live.

Next

Last updated on

On this page