t→t+1
Documentation

Editor

Canvas

The central editor surface renders the current simulation and keeps its runtime controls in context.

Renderer selection

The canvas selects its renderer from config.renderer.type. It can also present baked video, static images and plots, audio, text, or JSON output returned by non-interactive engines.

three
Interactive 3D rendering with cameras, lighting, environments, shadows, and post-processing.
canvas2d
Direct 2D rendering for compact scenes, diagrams, and lightweight simulations.
webgpu
GPU-oriented rendering for compatible simulations and browsers.
html
Simulation-owned HTML rendered inside a sandboxed iframe with the tplus1 bridge.

Canvas layers

  1. 01Simulation renderer or output view
  2. 02Presentation panels, annotations, and analytics
  3. 03Simulation audio
  4. 04Runtime HUD and parameter controller
  5. 05Transport, quality, and fullscreen controls

Live behavior

Worker state updates the canvas while the simulation runs. Camera and keyboard input are forwarded to the runtime, authored overlays read from live globals, and renderer or worker errors appear over the surface without hiding the editor.