Old bone collections stuck in UI

[J4ke6599]

Basically when I redid my scene and wanted to import the same UI to the new scene, I forgot to delete the bone collections of the old armature from the UI.

The new armature has the same collections and bones as in the old UI, but when I delete them from the UI, it deletes the actual collections from the armature, starting with the first one on the list, but the collections remain in the UI. Also assigning the bones to them is totally bugged and creating new collections doesn't add them to the UI collections list. It's also showing some old collections that don't exist anymore and I can't remove them as it removes wrong collections.

Just wondering if there is a way to wipe the old stuff completely from the UI.

[J4ke6599]

Ah never mind about the collection add part, I didn't realize that you can make new bone collections within the UI, but still, the collection is showing old and missing ones and new collections aren't added to the list, only in the armature object data properties tab. Also, outside of the UI edit view, hiding and showing the collections does nothing.

[Mustard2]

Uhm, do you have a screenshot of the issue? Because I'm not sure I understood what's happening

[Mustard2]

I pushed a new version, since there was an issue with the armature panel. Maybe it might fix also your issue, please let me know. :)

[J4ke6599]

Hey, the issue still persists. Also any new bone collections aren't even added to the UI for some reason. And I can't delete the ones added to the UI, it'll just remove them from the whole armature, but the collections remain in the UI.

[Mustard2]

Hey, the issue still persists. Also any new bone collections aren't even added to the UI for some reason. And I can't delete the ones added to the UI, it'll just remove them from the whole armature, but the collections remain in the UI.

Please send me the blend file without textures, so I check what went wrong in the data structure of the armature.

[Mustard2]

Closing this as there was no new message. If the issue persists, please open a new one here. :)

[J4ke6599]

Hey, sorry for not responding earlier. I've been fixing some dependency issues (unrelated to this issue) and noticed that there are two instances of the armature my figure uses. Let's call the main armature A and the one the UI uses B.

If I select any bone in pose mode, there should a white dot visible on the collection that bone belongs to, both on the armature properties tab and on the UI. Well, on armature A, nothing changes. When I in the Armature Object Data Properties tab switch the Armature Data from A to B, it switches the skeleton to the one that appears in the UI and I can select bones freely. Also, it appears the option to hide and unhide bone collections affects armature B and not the main armature A.

Is it supposed to create a duplicate? Because I have a bunch of bone collections attached to A and I probably can't transfer them to B because I suspect it also changes the actual bones that might not exist on the UI version of the armature. Also Blender turns really laggy when I switch the data collection from A to B. (Edit: Well, by the looks of it, even just switching the data collection deletes custom objects off the bones of the main armature).

I'm also guessing that any custom properties I linked to the UI are also linked to the duplicate armature B.