nx_bvhmotion.nx

nx_bvhmotion.nx -- BVH MOTION CAPTURE CENSUS (thin CLI over nx_bvh_lib). NAMING (deliberate, do not "fix" to nx_bvh): nx_bvh.nx is a BOUNDING VOLUME HIERARCHY for the slicer. The collision is real and it already cost a false capability reading -- a grep for "bvh" reported this format as ALREADY SUPPORTED when nothing of the kind existed. *A NAME IS NOT A CAPABILITY. WHY: measured 2026-08-07 against vrstormlab.com/dancexr/play (their served bytes): the LW build ingests VMD + BVH motion. BVH is the universal interchange, and unlike VMD its corpus has a commercially-clean tier -- which matters because our banked license truth says the SMPL/AMASS academic stack is non-commercial even for TRAINING. PROVEN ON REAL THIRD-PARTY DATA 2026-08-07 (not only on a fixture I authored): test_mocapbank.bvh 19 joints / 60 chan / 455 frames -> 27,300 values = 455*60 EXACT test_freebvh.bvh 55 joints / 168 chan / 69 frames -> 11,592 values = 69*168 EXACT Both channel sums also reconcile independently (6 + 18*3 = 60; 6 + 54*3 = 168). usage: nx_bvhmotion info <file.bvh> joints, channels, frames, frame time, derived fps nx_bvhmotion joints <file.bvh> joint tree: index, parent, nchan, offset xyz, name nx_bvhmotion dump <file.bvh> [n] first n motion rows nx_bvhmotion --kat selftest: 7 teeth, 3 of them anti-vacuity exit 0 ok | 2 unreadable | 3 usage | 4 REFUSED | 1 selftest RED license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0