Bone parent relations lost after generating rig with game.basic_raw_copy

[gor-rot]

Hello, I’m creating a manual rig using the game.basic_raw_copy type in the metarig. However, after generating it, all the bones using game.basic_raw_copy end up in a flat hierarchy and lose their parent relationships and the Parent field in the Relations panel is empty.

I tried using the Relink Constraints option to force the bones to connect to their intended parents, but it still doesn’t work.

[Arminando]

Hi!
I created a branch for this fix. Can you test it and see if it fixes the issue?
https://github.com/Arminando/GameRig/tree/raw_copy-parenting-fix

[gor-rot]

Hello, I’ve tested it, and the game.basic.raw_copy issue is fixed. However, I noticed another issue, when I use a bone with a different rig type (such as game.basic.super_copy) as a child of a bone using game.basic.raw_copy, it inherits the same problem that game.basic.raw_copy previously had.
In contrast, when a game.basic.raw_copy bone is a child of game.basic.super_copy, the relationship remains consistent with the metarig.

I also found that an extra root bone is generated in the hierarchy even though I have already added one in the metarig. This is different from Rigify’s built-in types when I manually create a root bone in the metarig, the generated rig replaces it rather than adding an additional root bone.

[Arminando]

Hi!
Thanks for the detailed feedback, great stuff!
I pushed another update to the same branch. I am hoping it fixes all parenting issues, but probably not the root. Let me know what you find.

[gor-rot]

Hello, I’ve tested it and noticed that the DEF bones generated using the game.basic.super_copy type are not placed under the DEF hierarchy as expected. Instead, they remain in the metarig hierarchy. I’ve also attached my Blender file in this link in case it helps with debugging. Thank you for the quick update and for looking into this.

[gor-rot]

Hi, I want to let you know that you were right all along. The issue was my mistake! I had set a bone with the rig type game.basic.super_copy as a child of a bone with the rig type game.basic.raw_copy that did not use the "DEF-" prefix. This caused the hierarchy to be incorrect.

The latest fix you provided has no issues and works perfectly. Thank you very much for your hard work.