Reply To: Linking and overwriting Blender 3.0

[Wayne Dixon]

Hi @michimussato,
Yeah, they seem to be changing this constantly.    Let me see if I can clear up some of your questions (if not all)

The different names for ‘making’ overrides all point to the same operator.  I don’t know why there are the 2 versions.  I have tested both, and they are the same, so maybe it’s just so it’s easy to find.

As for the greyed out property – that is also to do with overrides, however, the issue doesn’t reside in the linking side of things.  It’s in the rig file.  The version you have was created before a property existed, so it’s set to False when loaded into newer versions of Blender.   (it’s interesting that you can set that value with python! – I bet that’s isn’t meant to be allowed but you hit it with a hammer to solve your issue)

There is a new version of this rig coming very soon but I think you’ll get a kick out of fixing it yourself.

Here’s a script for you to run on the rig file.  (not your animation file).

Select the armature object then run this code from the text editor.

import bpy
rig = bpy.context.active_object
bones = [bone for bone in rig.pose.bones]
for bone in bones:
    for key in sorted(bone.keys()):
        if key not in '_RNA_UI':
            bone.property_overridable_library_set(f'["{key}"]', True)

Then save your file.  And the UI should work as expected in your anim file.

What does the script do?
Loops through all the custom properties on the active object (it’s expecting an armature though so it will error out if you don’t have that as the active object)

Then it check the “make Library Overridable” boolean to True.

(I thought I did that already for the multiball…but obviously not)
Either way, it’s getting updated in the next couple of weeks when the new version of the course comes out.

Hope that clears things up.
If not just poke me again.