fk bones cannot correctly name DEF bone #179

New Issue

ziyang-liu · 2024-11-21T14:39:51+01:00

ziyang-liu commented

2024-11-21 14:39:51 +01:00

System Information
Operating system:windows11

Blender Version: 4.3
CloudRig Version: 2.1.15

Exact steps to reproduce the error

When creating multiple new fk bones cannot correctly name DEF bone, resulting in confusion when brushing weights.

Based on the human metarig or a minimal .blend file.

CC @Mets

**System Information** Operating system:windows11 Blender Version: 4.3 CloudRig Version: 2.1.15 **Exact steps to reproduce the error** When creating multiple new fk bones cannot correctly name DEF bone, resulting in confusion when brushing weights. Based on the human metarig or a minimal .blend file. CC @Mets

The def bone cannot be properly named.blend

2.9 MiB

ziyang-liu added the

bug

label 2024-11-21 14:39:51 +01:00

Demeter Dzadik commented

2024-11-21 14:55:35 +01:00

You can't expect to name every bone in your rig "Bone" and have a procedural system not run into name conflicts. This is mentioned in the Troubleshooting->Naming section in the docs:

For all Chain component types, incrementing bone names should always correspond to parent/child relationships. For example, "Bone2" must be the child of "Bone1". Bones that are named like this should not be siblings, or unrelated to each other.

So, I advise you name your bones like so:

You can't expect to name every bone in your rig "Bone" and have a procedural system not run into name conflicts. This is mentioned in the [Troubleshooting->Naming](https://studio.blender.org/tools/addons/cloudrig/troubleshooting#naming) section in the docs: > For all Chain component types, incrementing bone names should always correspond to parent/child relationships. For example, "Bone2" must be the child of "Bone1". Bones that are named like this should not be siblings, or unrelated to each other. So, I advise you name your bones like so: ![image](/attachments/f16ae3ad-b74a-404f-8502-b91a782f2d6b)

image.png

66 KiB

Demeter Dzadik closed this issue

2024-11-21 14:55:36 +01:00

Sign in to join this conversation.