Bones with prefixed 'DEF-' problem. #106

New Issue

2023-07-12T04:16:15+02:00

ZAQraven commented

2023-07-12 04:16:15 +02:00

(Migrated from gitlab.com)

System Information
Operating system: Linux-6.3.12-200.fc38.x86_64-x86_64-with-glibc2.37 64 Bits

Blender Version
3.6.0, branch: blender-v3.6-release, commit: 2023-06-27

CloudRig Version: (0, 0, 9) (2023-07-11 03:58)

Having problems with bone with prefixed 'DEF-'

To reproduce:

Create single bone
Enter pose mode, and rename the bone with prefixed 'DEF-'
Set rig type to cloud_copy
Generate CloudRig
The result, the generated bone's deform checkbox was disabled (not deformed).

The bone's deform checkbox by default is enabled. But when generated, it was not deformed. It could be there's a bug while generating the rig.

Here's the log on the terminal:

Warning: addon-module bone_selection_sets found module but without '__addon_enabled__' field, possible name collision from file: '/home/zaqraven/Blender-3.6/3.6/scripts/addons/bone_selection_sets.py

**System Information** Operating system: Linux-6.3.12-200.fc38.x86_64-x86_64-with-glibc2.37 64 Bits **Blender Version** 3.6.0, branch: blender-v3.6-release, commit: [2023-06-27](https://developer.blender.org/rBc7fc78b81ecb) **CloudRig Version**: (0, 0, 9) (2023-07-11 03:58) *************************************** Having problems with bone with prefixed 'DEF-' To reproduce: 1. Create single bone 2. Enter pose mode, and rename the bone with prefixed 'DEF-' 3. Set rig type to cloud_copy 4. Generate CloudRig 5. The result, the generated bone's deform checkbox was disabled (not deformed). ![image](/uploads/1befcc36ef1ebe409706d1baf5421822/image.png) The bone's deform checkbox by default is enabled. But when generated, it was not deformed. It could be there's a bug while generating the rig. Here's the log on the terminal: <pre>Warning: addon-module bone_selection_sets found module but without '__addon_enabled__' field, possible name collision from file: '/home/zaqraven/Blender-3.6/3.6/scripts/addons/bone_selection_sets.py</pre>

ZAQraven commented

2023-07-12 04:17:45 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 04:20:42 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 04:35:10 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 04:35:49 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 04:36:43 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 04:38:10 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 06:11:54 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 06:12:10 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 17:33:34 +02:00

(Migrated from gitlab.com)

changed the description

ZAQraven commented

2023-07-12 17:45:49 +02:00

(Migrated from gitlab.com)

I already made a workaround. I check the box of 'Create Deform' and the copy one will be an ORG-xxx. Will remain open if there is a way to fix this bug.

ZAQraven commented

2023-07-17 15:58:33 +02:00

(Migrated from gitlab.com)

changed the description

Mets3D commented

2023-08-02 18:16:09 +02:00

(Migrated from gitlab.com)

So, this is not really a bug, but I admit there is a lack of documentation on what's exactly going on here. I tried to address this by adding a new Naming section to the wiki, where we can collect problematic naming conventions that might pop up over time.

In theory, any bone prefix or set of prefixes that CloudRig might use, is illegal, because it could wreak havoc in the code, which sometimes relies on strings to keep track of bones.

So the DEF- prefix is reserved for use by CloudRig's generation process, and users aren't really allowed to name bones that way, unless it's a cloud_tweak situation.

Thanks for the report.

So, this is not really a bug, but I admit there is a lack of documentation on what's exactly going on here. I tried to address this by adding a new [Naming](https://gitlab.com/blender/CloudRig/-/wikis/Troubleshooting#naming) section to the wiki, where we can collect problematic naming conventions that might pop up over time. In theory, any bone prefix or set of prefixes that CloudRig might use, is illegal, because it could wreak havoc in the code, which sometimes relies on strings to keep track of bones. So the DEF- prefix is reserved for use by CloudRig's generation process, and users aren't really allowed to name bones that way, unless it's a cloud_tweak situation. Thanks for the report.

Sign in to join this conversation.