Existing gsplats mesh to update
New splat data
Optionaloptions: { preserveOrdering?: boolean }
preserveOrdering: keep the existing aSortedIndex
permutation on the SAME-SIZE (in-place) branch instead of resetting
it to identity (same-node same-count recommit — the commit path
decides; see commit-gsplats-geometry.ts). Ignored on the rebuild
branch: fresh geometries are zero-filled, not identity, so the
identity write is structurally required there.
true when the geometry+texture pair was swapped for a
fresh one (splat-count change) — the caller must then evict
Three's cached RenderObject (see invalidate-render-object.ts);
false for the in-place texture rewrite.
Update an existing gsplats mesh with new data.
Same splat count: rewrites the existing splat texture's backing store in place. Count change: swaps in a FRESH geometry+texture pair and disposes the old one (never rebinds new storage onto a rendered geometry — see the rebuild branch below).