Rigging: joints, constraints, IK, skinning, blend shapes, deformers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- computer-graphics
Research direction
This is a tracking issue, not a code change. Start by reading .project-docs/parity.md (the Rigging section) and the pinned reference in #5 to see what is currently claimed. The work is to split each checklist item (joints, constraints, IK/FK, skinning, blend shapes, deformers) into its own child issue with a sourced workflow list. Done means those child issues exist and each follows the feature gates.
Written by the indexing model from the issue text.
Description
Problem
Not implemented.
Current behavior
.project-docs/parity.md (Rigging): not implemented.
Expected behavior
Staged rigging. Quick Rig reference: https://help.autodesk.com/cloudhelp/2026/ENU/Maya-CharacterAnimation/files/GUID-DC29C982-D04F-4C20-9DBA-4BBB33E027EF.htm .
Checklist:
- Joints and skeletons
- Constraints
- IK/FK
- Skinning and weight editing
- Blend shapes
- Deformers
Acceptance criteria
- Each checklist item is split into its own issue before work starts, with a sourced workflow list.
- Every child follows the feature gates: visibly unsupported until done, MCP coverage with schemas, Editor protocol tests and docs, native visual check.
- No percentage or parity claim until the pinned reference (#5) and the audited inventory exist.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 2
- Avg merge
- 2h 28m
- Merged PRs (30d)
- 76
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cristim/AztecCraft
-
area/viewport type/chore
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cristim/AztecCraft#186 ·
Maintainers usually reply within 1 day
-
area/infra type/chore
Difficulty 1/5 Under an hour Newbie friendliness 94/100
cristim/AztecCraft#181 ·
Maintainers usually reply within 1 day
-
area/modeling type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cristim/AztecCraft#176 ·
Maintainers usually reply within 1 day
-
area/modeling type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cristim/AztecCraft#175 ·
Maintainers usually reply within 1 day
-
area/ui-parity type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cristim/AztecCraft#172 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cristim/AztecCraft
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#4023 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nautechsystems/nautilus_trader#5365 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
IntersectMBO/developer-experience#347 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
registrystack/registry-stack#2168 ·
Maintainers usually reply within 1 day
-
bug crate: 3d help wanted triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kornia/kornia-rs#1203 · 1 comment ·
Maintainers usually reply within 1 day