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

    Function invalidateCommittedDataStamp

    • Drop ONLY the no-op memoization stamp, keeping the elementIdMap sibling.

      For the caller that is forcing a re-process of geometry which REMAINS on the GPU and pickable — rendering/depth-sort-coordinator.ts's blending-mode switch, which clears the stamp purely so the memoized-concat fast path cannot skip re-projection. The buffers are untouched, so the map still describes them exactly; dropping it would make every hover in the (async) window before the reprocess commits fall back to the raw slot — the silently-wrong label this map exists to prevent. The next real commit rewrites both in lockstep.

      Parameters

      • obj: Object3D

      Returns void