migrating pre-4.0 rigs loses Rig Layers information #105168
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#105168
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.33
Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash:
9be62e85b727
Worked: 3.6.2
Addon Information
Name: Rigify (0, 6, 9)
Author: Nathan Vegdahl, Lucio Rossi, Ivan Cappiello, Alexander Gavrilov
Short description of error
[Please fill out a short description of the error here]
Exact steps for others to reproduce the error
As stated in this stackexchange question, the replacement of armature.layers (removed) with armature.collections (new) appears to lose information and not be able to draw the Rigify Layers panel in the UI as in previous versions:
Bone Collections have a very undescriptive list
compare to generating a new rig in 4.0
.
Is there some migration workflow or tool to not lose this feature on older rigs?
Hi, thanks for the report. Guess you would require to update metarig to "bone collections" first, then need to regenerate rig: image
why don't I have a Rigify panel for my rigs?
Closed this issue by mistake
Select meta-rig instead.
BTW this was added in
5ec3aa7d9d
Perhaps my "example" file had another (meta) rig. Most of my files are like the attached: only the main rig that contains both FK and IK bones, in layers. Rigged.blend I still don't see the upgrade nor any Rigify panel.
Not sure how to proceed in such case (without the meta-rig or the actual bones) cc @angavrilov
In case of
rigify migration.blend
, selectmetarig_3.6.2
then you will get an option "update metarig" in object data properties panel.Upgrade is only implemented for metarigs, because 1) the intended workflow is to keep them around for updates, and 2) updating a generated rig would require parsing and patching the text of the python script datablock. So, in any case, this is a feature request and not a bug.
It is unfortunate that at least DAZ import add-on does not create such a rig.