Driver's target field doesn't update on Bone rename #29822

New Issue

Pablo Vazquez · 2012-01-07T20:22:03+01:00

Pablo Vazquez commented

2012-01-07 20:22:03 +01:00

%%%Trying to find out why my driver didn't work, it seems that I've first assigned the driver's target bone (choosing from the ID menu in the Ob/Bone field in Drivers panel, in Graph/Drivers Editor), but renamed this bone afterwards. The driver target field still had the old bone name, didn't update when I renamed the bone, hence not working (without displaying an error or at least the field being red).

It does work on Object rename (e.g. changing the name of the Armature object works, just doesn't work on bone rename).

I'm using current SVN.

Cheers!%%%

%%%Trying to find out why my driver didn't work, it seems that I've first assigned the driver's target bone (choosing from the ID menu in the Ob/Bone field in Drivers panel, in Graph/Drivers Editor), but renamed this bone afterwards. The driver target field still had the old bone name, didn't update when I renamed the bone, hence not working (without displaying an error or at least the field being red). It does work on Object rename (e.g. changing the name of the Armature object works, just doesn't work on bone rename). I'm using current SVN. Cheers!%%%

Pablo Vazquez commented

2012-01-07 20:22:03 +01:00

Changed status to: 'Open'

Joshua Leung commented

2012-01-08 12:43:42 +01:00

%%%Test file needed.%%%

Pablo Vazquez commented

2012-01-09 03:41:56 +01:00

%%%Sorry Ali, attached a file

Well, it might just be a bad flag somewhere, because in a clean file the field becomes red when the bone is not found.

But if you still want to look into this:

Move the selected bone, the lamp's energy changes.
Rename the bone, the driver's target field is still gray, I could even save the file with a different bone name, reload, the field would still be gray.

Weird fact, if you remove any of the other bones in the armature (I moved them to the back), the field turns red, working properly.

I thought it was a general case, but it might be some weird setup, perhaps not even worth looking into.
Cheers!%%%

%%%Sorry Ali, attached a file Well, it might just be a bad flag somewhere, because in a clean file the field becomes red when the bone is not found. But if you still want to look into this: - Move the selected bone, the lamp's energy changes. - Rename the bone, the driver's target field is still gray, I could even save the file with a different bone name, reload, the field would still be gray. Weird fact, if you remove any of the other bones in the armature (I moved them to the back), the field turns red, working properly. I thought it was a general case, but it might be some weird setup, perhaps not even worth looking into. Cheers!%%%

Joshua Leung commented

2012-01-09 10:47:35 +01:00

%%%Ah... probably this is because the bone rename function only calls the animdata fixit on object-based animation. Let's see...%%%

Joshua Leung commented

2012-01-22 05:12:16 +01:00

%%%Fixed in svn.%%%

Joshua Leung commented

2012-01-22 05:12:17 +01:00

Changed status from 'Open' to: 'Resolved'

Joshua Leung closed this issue

2012-01-22 05:12:17 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Driver's target field doesn't update on Bone rename #29822