Rigify: add option to parent all deform bones according to metarig #104644
No reviewers
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#104644
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Leslie-Leigh/blender-addons:rigify_parent"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR wants to add an option to rigify which, if toggled, parent all deform bones in generated rig according to metarig's original bone hierarchy.
Motivation
Currently, rigs generated by rigify are not game-friendly.
In this video, the author compared rigify vs auto rig pro, and given rigify only
C
score on exporting to game engine.Some users even post the solution to strike the problem. This series video shares how to achieve a game-ready rig. The idea is, manually add some rig and constraint them to follow the deforming bones generated by rigify.
In my opinion, one of the problems is the deforming bones' hierarchy is sometimes totally different from metarig's one.
For example, for a basic human meta-rig sample provided by rigify, it has a clear bone hierarchy:
During generation, rigify generates lots of helper bones (mch, ctl...). These bones sure are not suitable for directly exporting to game engine. Usually, users export the finally rig with a "deforming bones only" option (which as I know, are supported both by glTF and FBX exporter). Then the result model should contain bones prefixing with "DEF-", let's look at these bones:
As you can see, the hierarchy is not organized in an expected way. For example:
DEF-pelvis.L/R
is not child ofroot
orDEF-spine
;DEF-arm.L/R
is not a child ofDEF-shoulder.L/R
...So, even we export using "deforming bones only", we still cannot get an ideal hierarchy.
This PR here wants to strike this problem.
As I observed, almost each
DEF-
deforming bone has at least a copy-transform constraint. So, in theory, it doesn't matter if it wasn't under some bones. So, in this PR, I:Added a "parent all deform bones" boolean generation option.
If the option is true, parent each rig chain to parent chain's deforming bone instead of helper bones. For example, for a
basic.limb
rig which is a child rig of abasic.spine
rig:Gets its "rig parent bone", which for example is
ORG-spine.01
in the parentbasic.spine
rig.Attempt to find the corresponding deforming bone of
ORG-spine.01
, if everything goes fine, the result should beDEF-spine.01
.Parent the head deforming bone of the
basic.limb
rig underDEF-spine.01
.I have tried the modification with the builtin horse meta-rig, the result rig looks like this:
Checkout
From your project repository, check out a new branch and test the changes.