Chain bones are getting incorrect names. #141

New Issue

Thalia-Solari · 2024-05-10T00:25:14+02:00

Thalia-Solari commented

2024-05-10 00:25:14 +02:00

System Information
Operating system:
Windows-10-10.0.19045-SP0 64 Bits

Blender Version:
4.1.1, branch: blender-v4.1-release, commit: 2024-04-15

CloudRig Version:
(2, 0, 0)

Short description of error

In the provided blend, metarig bones Bone_3.L and Bone_4.L are not getting the correct names, instead being generated as Bone_4.L and Bone_6.L respectively. The naming schemes for intersections are also funkier than usual.

I think this has something to do with the way Tip Controls are being generated.

Exact steps for others to reproduce the error
Based on the default human metarig or a simplified attached .blend file.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Blender Version: 4.1.1, branch: blender-v4.1-release, commit: 2024-04-15 CloudRig Version: (2, 0, 0) **Short description of error** In the provided blend, metarig bones Bone_3.L and Bone_4.L are not getting the correct names, instead being generated as Bone_4.L and Bone_6.L respectively. The naming schemes for intersections are also funkier than usual. I think this has something to do with the way Tip Controls are being generated. **Exact steps for others to reproduce the error** Based on the default human metarig or a simplified attached .blend file.

cloudrig chain naming weirdness.blend

596 KiB

Demeter Dzadik commented

2024-05-23 16:23:28 +02:00

Thanks for the report.

I think the best solution here may be to document this as a limitation; The code assumes that bones with incrementing names are always chains. That assumption allows avoiding marking tip controls as "TIP" and instead just incrementing the name, which I think is simpler and less confusing. It's a bit of a shame about this side-effect, but for the moment I feel like just embracing it.

I added a mention of this to the Troubleshooting page for now.

Thanks for the report. I think the best solution here may be to document this as a limitation; The code assumes that bones with incrementing names are always chains. That assumption allows avoiding marking tip controls as "TIP" and instead just incrementing the name, which I think is simpler and less confusing. It's a bit of a shame about this side-effect, but for the moment I feel like just embracing it. I added a mention of this to the [Troubleshooting](https://projects.blender.org/Mets/CloudRig/wiki/Troubleshooting#naming) page for now.

Demeter Dzadik closed this issue

2024-05-23 16:23:29 +02:00

Sign in to join this conversation.