nx_gsplatbind.nx

nx_gsplatbind.nx -- ★THE HYBRID: OUTSIDE SPLAT, INSIDE PARAMETRIC MESH (operator 2026-07-27, "do the outside splat the inside the same as gnm google"). This is the mid-2026 industry architecture and it resolves the 3DGS-vs-poly-mesh question without choosing: a low-resolution parametric mesh acts as the DRIVING CAGE, and millions of Gaussians are anchored to its triangles. When the rig deforms the cage, the splat cloud is carried with it. You get the animation, physics, collision and EDITABILITY of a mesh with the photorealism of splats -- and, decisively for this program, the mesh keeps the INTERIOR that a splat cloud cannot have at all. ★WHY THE MESH MUST STAY THE SOURCE OF TRUTH HERE: every load-bearing claim of the twin program -- layered bone/muscle/fascia, surgical prediction, joint limits, self-penetration, centre-of-mass -- needs structured solid geometry. Splats are an APPEARANCE representation with no inside. So the binding is deliberately one-directional: the mesh drives, the splats follow, never the reverse. ★THE BINDING (GaussianAvatars-class): each Gaussian is stored in the LOCAL FRAME of its triangle -- barycentric position within the face, a signed offset along the face normal, and a scale expressed as a RATIO of the face's own size. Rebuilding from a deformed triangle then reproduces the splat in the deformed configuration for free, at any pose, with no re-fit. ⚠DECLARED LIMIT: nx_gsplat v0 Gaussians are ISOTROPIC {x,y,z,scale,r,g,b,opacity} -- there is no orientation term, so this binding carries POSITION and SIZE but has no rotation to carry. When anisotropic covariance lands (nx_gsplat's own named next rung), the binding MUST also rotate each Gaussian into the triangle's frame, and a splat that translates without rotating is the classic bug -- highlights that slide across a turning surface. T4 is written now so that rung has a tooth waiting. nx_gsplatbind selftest license_tier: ORIGINAL expect_exit: 0 No hw writes (Rule 26).