EpisodeRecon3d

A controlled 3D reconstruction view, shaped like the other Episode* components: pass a scene (geometry + its per-frame tracks) plus time/duration and it animates — meshes move along their 6-DoF transform tracks, deforming meshes get new vertices per frame, and the motion trail is the future: the next second of each path, running out exactly when the clip does. Orbit with the mouse. This is the same scene the platform's annotation viewer renders for recon3d datasets; the example below loads a real exported scene (a ruler + a toy with MANO hand meshes) from its glTF binary.

Data in

Geometry comes from a glTF / GLB file; everything per-frame comes from the dataset as separate tracks. The glTF node name is the join key — a transform3d track named ruler (or ruler_pose, poses[ruler]) drives the node named ruler.

import { EpisodeRecon3d, loadGltf, type Scene3dInput } from '@dreamlake/viz/episode-recon-3d'

const meshes = await loadGltf(url, 'glb')       // nodes: ruler, toy, left_hand, …
const scene: Scene3dInput = {
  meshes,
  transforms: [],    // { name, timestamps, values (rows×7), layout }
  vertexTracks: [],  // { name, count, fps?, vertexCount, at(i) } — deforming meshes
  pointTracks: [],   // animated 3D point sets (21 points draw a hand skeleton)
  upVector: null,    // gravity in the data's frame → upright grid
}
<EpisodeRecon3d scene={scene} time={t} duration={clipSeconds} />

pointTrackFromPose3d(name, payload) turns a pose3d read into a point track.

Props

In a .dreamrc, the recon3d view wraps this — geometry and tracks bind the mesh3d / transform3d / vertices3d / pose3d tracks and the shared cursor drives time.