Skip to content

Fix ROOT/FK subtree propagation in shared Mechanics runtime; prove Motion→LBS consequence - #372

Merged
merynz merged 4 commits into
mainfrom
integrate/mechanics-root-subtree-runtime-20261107
Nov 6, 2026
Merged

merynz merged 4 commits into
mainfrom
integrate/mechanics-root-subtree-runtime-20261107

Conversation

@merynz

@merynz merynz commented Nov 6, 2026

Copy link
Copy Markdown
Owner

Product runtime behavior, following #365 and #368

Audited exact source: isolated existing Mechanics solver fix from #353 commit a9f3efd225eed7d08e418c2ebfd303da3b0cb613; source blob 6b08101d4beab65e9261253b10c023d31c266251 identical, not a new solver. The previous direct ROOT/FK behavior moved only targeted joints, leaving descendant bones unmoved.

This bounded 4-file PR brings proper declared-root/subtree propagation, child-FK precedence (regardless of control list order) and hard errors on invalid parent graphs into the mainline solver already used by Motion V2 and CanonicalMechanics. It adds independent behavioral tests that flow through actual CanonicalMesh v1 → CanonicalRig v2 → CanonicalSkin v2 → CanonicalMechanics v1 → qualified CanonicalMotion v2 sampling → solve → full LBS deformation.

Dedicated CI runs original V6 solver/Motion/Mechanics/CAS worker regressions as well as new positive/negative source-independent tests; must also pass broad mainline, platform/go and native/CAA checks before review/merge.

No trained-model, source-truth, 60fps, UI, Graphics, 6D grip, ProductRevision, .rss or unseen claims. No unrelated #353 multigoal runtime imported. This is a real mechanical runtime correctness fix, not product admission. Follow-up: source-bound interactive live runtime and Graphics/native consumer tests.

@merynz
merynz marked this pull request as ready for review November 6, 2026 23:02
@merynz
merynz merged commit 93374ff into main Nov 6, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant