Invalid Driver : error message improvement #113948

New Issue

shannon zachow · 2023-10-19T20:32:16+02:00

shannon zachow commented

2023-10-19 20:32:16 +02:00

System Information
Operating system: N/A
Graphics card: N/A

Blender Version
Broken: 3.6, 4.0

Short description of error
This is not a bug. It is a request for improvement.

Error message for "Invalid Driver" does not contain the name of the data-block that contains/references the invalid drivers.

Please modify "invalid drivers" error message to include the name of the data-block which holds the invalid drivers.

Exact steps for others to reproduce the error
see attached test047_invalidDriver.blend for example.

....................

Armature: "Armature.Original"
Custom Property in Armature: "handScale"
Bone: "Hand"
has drivers to use Custom Property as scale of bone "Hand"

....................

make a copy of 1st armature for surgery: "Armature.Copy"
separate hand-bones to a 3rd armature: "Armature.Hand"
(...so that you can swap in different hands and hand-rigs,
with "Child Of" bone-constraint...)

....................

as soon as you separate the hand-bones (which have drivers),
the console will start displaying error messages like the following:

WARN (bke.anim_sys): source/blender/blenkernel/intern/anim_sys.cc:4203 BKE_animsys_eval_driver: invalid driver - pose.bones["Hand.L"].scale[0]

error message references bone name(s),
but does NOT reference which data-block contains the invalid drivers.

When you "Separate Bones",
drivers are copied to the new armature "Armature.Hand",
but they are not deleted from the source-armature "Armature.Copy",
because blender can't know that you want them gone.

Drivers in the source-armature "Armature.Copy" are now invalid,
because they reference bones which no longer exist in source-armature.

If the Error Message told you which data-block (armature)
contained the invalid drivers,
then you can just
+ Select (data-block) armature.
+ In Drivers_Editor:
right-click context-menu >> Delete Invalid Drivers

But if you don't know the data-block source of error-messages,
then you might spend months trying to figure out what's wrong
with the (valid) drivers in the separated armature ("Armature.Hand")
that contains the bones that are referenced in the error message.
(... true story)

....................

==> Please modify "invalid drivers" error message to include the name
of the data-block which holds the invalid drivers.

....................
....................

room for improvement #2 :

with one of these armatures selected:
look in Drivers_Editor right-panel:
field "Prop" (for input variable property path data-block type)
Why is it extra-squashed to the right?
(blank space between label "Prop:" & start of drop-down type-menu,
so that field containing name of data-block is extra obscured...)

....................

Thanks for blender! :D

**System Information** Operating system: N/A Graphics card: N/A **Blender Version** Broken: 3.6, 4.0 **Short description of error** This is not a bug. It is a request for improvement. Error message for "Invalid Driver" does not contain the name of the data-block that contains/references the invalid drivers. Please modify "invalid drivers" error message to include the name of the data-block which holds the invalid drivers. **Exact steps for others to reproduce the error** see attached test047_invalidDriver.blend for example. .................... Armature: "Armature.Original" Custom Property in Armature: "handScale" Bone: "Hand" has drivers to use Custom Property as scale of bone "Hand" .................... 1. make a copy of 1st armature for surgery: "Armature.Copy" 2. separate hand-bones to a 3rd armature: "Armature.Hand" (...so that you can swap in different hands and hand-rigs, with "Child Of" bone-constraint...) .................... as soon as you separate the hand-bones (which have drivers), the console will start displaying error messages like the following: WARN (bke.anim_sys): source/blender/blenkernel/intern/anim_sys.cc:4203 BKE_animsys_eval_driver: invalid driver - pose.bones["Hand.L"].scale[0] error message references bone name(s), but does NOT reference which data-block contains the invalid drivers. When you "Separate Bones", drivers are copied to the new armature "Armature.Hand", but they are not deleted from the source-armature "Armature.Copy", because blender can't know that you want them gone. Drivers in the source-armature "Armature.Copy" are now invalid, because they reference bones which no longer exist in source-armature. If the Error Message told you which data-block (armature) contained the invalid drivers, then you can just + Select (data-block) armature. + In Drivers_Editor: right-click context-menu >> Delete Invalid Drivers But if you don't know the data-block source of error-messages, then you might spend months trying to figure out what's wrong with the (valid) drivers in the separated armature ("Armature.Hand") that contains the bones that are referenced in the error message. (... true story) .................... ==> Please modify "invalid drivers" error message to include the name of the data-block which holds the invalid drivers. .................... .................... room for improvement #2 : with one of these armatures selected: look in Drivers_Editor right-panel: field "Prop" (for input variable property path data-block type) Why is it extra-squashed to the right? (blank space between label "Prop:" & start of drop-down type-menu, so that field containing name of data-block is extra obscured...) .................... Thanks for blender! :D

test047_invalidDriver.blend

742 KiB

shannon zachow added the

labels 2023-10-19 20:32:16 +02:00

Iliya Katushenock commented

2023-10-19 20:37:21 +02:00

Thanks for the report, but please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Thanks for the report, but please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Iliya Katushenock closed this issue

2023-10-19 20:37:23 +02:00

Blender Bot added

and removed

labels 2023-10-19 20:37:24 +02:00

shannon zachow commented

2023-10-19 20:43:12 +02:00

it's not a feature request.
it is a description of the deficiency of the current formulation of one sprintf() statement.