Luxar Viewer API Documentation - v2026.9.22
    Preparing search index...

    Minimal shape for stampLadderComplete: every leaf mesh's userData carries a live reference to the loader that produced its data (written at node creation by the node factory / create-*-node helpers), which is how the stamp reads ladder state with zero extra plumbing.

    interface LadderStampable {
        loader?: unknown;
        committedLadderComplete?: boolean;
        committedEnergyFraction?: number;
        committedLODCount?: number;
    }
    Index
    loader?: unknown
    committedLadderComplete?: boolean
    committedEnergyFraction?: number

    Cumulative energy fraction e(k) of the COMMITTED ladder prefix — how much of the ladder's total self-energy is on screen (from the progressive loaders' committedEnergyFraction, sourced from the build-time lod_stats.energy_fraction_cum stamps). 1 for non-progressive (complete single-set) leaves; ABSENT on unstamped (legacy) datasets — the display gate falls back to count crossover then.

    committedLODCount?: number

    Ladder rungs actually ON SCREEN — the loader's cursor as of the commit that put this geometry there, not its cursor now.

    The two diverge exactly when it matters. updateView advances the cursor as each rung ARRIVES, so a pass whose commit fails or is superseded leaves the loader reporting rungs the viewer never drew. On the hosted Laniakea demo the monitor read "LOD 7/7 ~100%" for basins that were rendering a coarse prefix and had stopped refining — the panel was reporting the loader's intent while the screen showed something else, which is how the failure stayed invisible (#2426).