migrating pre-4.0 rigs loses Rig Layers information #105168

Closed
opened 2024-02-07 22:29:30 +01:00 by James Tomkinson · 8 comments

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:

cap1.png

Bone Collections have a very undescriptive list

Bone collections.png compare to generating a new rig in 4.0

bone collections 4.png.

Is there some migration workflow or tool to not lose this feature on older rigs?

**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](https://blender.stackexchange.com/q/311410/111042) 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: ![cap1.png](/attachments/8af5a807-2a4d-4e81-9d14-a156fdd6f946) Bone Collections have a very undescriptive list ![Bone collections.png](/attachments/f2846839-56ce-488a-b724-4a0b2c9d755a) compare to generating a new rig in 4.0 ![bone collections 4.png](/attachments/27ebfe8e-cea9-4be8-bc56-737531003a74). Is there some migration workflow or tool to not lose this feature on older rigs?
James Tomkinson added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2024-02-07 22:29:30 +01:00
Member

Hi, thanks for the report. Guess you would require to update metarig to "bone collections" first, then need to regenerate rig: image

Hi, thanks for the report. Guess you would require to update metarig to "bone collections" first, then need to regenerate rig: [image](/attachments/dc246304-e571-4dfd-829b-da945984d433)
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-02-08 11:04:04 +01:00

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?

Screenshot 2024-02-11 124646.png

> Hi, thanks for the report. Guess you would require to update metarig to "bone collections" first, then need to regenerate rig: [image](/attachments/dc246304-e571-4dfd-829b-da945984d433) > why don't I have a Rigify panel for my rigs? ![Screenshot 2024-02-11 124646.png](/attachments/601f54e3-76fd-432f-8c45-50d029acedeb)
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-02-11 18:48:46 +01:00

Closed this issue by mistake

Closed this issue by mistake
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2024-02-11 18:49:15 +01:00
Member

Select meta-rig instead.
BTW this was added in 5ec3aa7d9d

Select meta-rig instead. BTW this was added in 5ec3aa7d9d5643a4f179c417285d7edba38b632c
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-02-12 12:36:27 +01:00

Hi, thanks for the report. Guess you would require to update metarig to "bone collections" first, then need to regenerate rig: image

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.

> Hi, thanks for the report. Guess you would require to update metarig to "bone collections" first, then need to regenerate rig: [image](/attachments/dc246304-e571-4dfd-829b-da945984d433) > 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](/attachments/918f3f65-ef5f-4ea9-a777-a6a8e34048a1) I still don't see the upgrade nor any Rigify panel.
Member

Most of my files are like the attached: only the main rig

Not sure how to proceed in such case (without the meta-rig or the actual bones) cc @angavrilov
In case of rigify migration.blend, select metarig_3.6.2 then you will get an option "update metarig" in object data properties panel.

> Most of my files are like the attached: only the main rig Not sure how to proceed in such case (without the meta-rig or the actual bones) cc @angavrilov In case of `rigify migration.blend`, select `metarig_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.

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.

It is unfortunate that at least DAZ import add-on does not create such a rig.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-02-16 18:21:36 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#105168
No description provided.