Getting multiple system console error traces on Animation Drivers that appear to be functional #98525

New Issue

Keith Boshoff · 2022-05-31T22:49:51+02:00

Keith Boshoff commented

2022-05-31 22:49:51 +02:00

Blender 3.3 (2022/05/31)

Short description

--------------------------------------------------------------------
Failed to add relation "RNA Target -> Driver"
Could not find op_from: RnaPathKey(id: OBshadow_rig, prop: 'Warp')

Trace:

Depth    Type                     Name
-----    ----                     ----
1        Object                   shadow_rig_obj

To demonstrate that the driver is actually working, in the Armature Data's Custom Properties there should be a Warp slider, slide that and the bone will transform weirdly (the weird transformation is functioning as intended).

If I'm reading the trace correctly it's looking for 'Warp' on the shadow_rig object, which is incorrect, the drivre is referencing 'Warp' on the shadow_rig data (data path is "data['Warp']"), and doing so correctly if you see the driver working.

I also get these errors on some Rigify rigs made from custom metarigs.

I have a feeling that the trace is being triggered incorrectly.

Steps to Reproduce
This rig uses drivers generated by a script if that matters.

Open Window > Toggle System Console
Select the visible rig
Tab into Edit Mode
Tab back to Object Mode
System console will have a few traces
Weird Driver Traces.blend

Blender 3.3 (2022/05/31) **Short description** ``` -------------------------------------------------------------------- Failed to add relation "RNA Target -> Driver" Could not find op_from: RnaPathKey(id: OBshadow_rig, prop: 'Warp') Trace: Depth Type Name ----- ---- ---- 1 Object shadow_rig_obj ``` To demonstrate that the driver is actually working, in the Armature Data's Custom Properties there should be a Warp slider, slide that and the bone will transform weirdly (the weird transformation is functioning as intended). If I'm reading the trace correctly it's looking for 'Warp' on the shadow_rig object, which is incorrect, the drivre is referencing 'Warp' on the shadow_rig data (data path is "data['Warp']"), and doing so correctly if you see the driver working. I also get these errors on some Rigify rigs made from custom metarigs. I have a feeling that the trace is being triggered incorrectly. **Steps to Reproduce** This rig uses drivers generated by a script if that matters. - Open Window > Toggle System Console - Select the visible rig - Tab into Edit Mode - Tab back to Object Mode - System console will have a few traces [Weird Driver Traces.blend](https://archive.blender.org/developer/F13125427/Weird_Driver_Traces.blend)

Keith Boshoff commented

2022-05-31 22:49:51 +02:00

Added subscriber: @Wahooney

Pratik Borhade commented

2022-06-01 06:06:47 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Pratik Borhade commented

2022-06-01 06:06:54 +02:00

Added subscriber: @PratikPB2123

Lukas Tönne commented

2022-06-24 14:35:30 +02:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2022-06-24 14:35:30 +02:00

DepsgraphNodeBuilder::build_driver_id_property adds the operation node in the Object datablock, but the RNA path points to the Armature datablock. This case is described in a comment here:
https://developer.blender.org/diffusion/B/browse/master/source/blender/depsgraph/intern/builder/deg_builder_relations.cc$1714-1737

      /* It is possible that RNA path points to a property of a different ID than the target_id:

     * for example, paths like "data" on Object, "camera" on Scene.

...

`DepsgraphNodeBuilder::build_driver_id_property` adds the operation node in the `Object` datablock, but the RNA path points to the `Armature` datablock. This case is described in a comment here: https://developer.blender.org/diffusion/B/browse/master/source/blender/depsgraph/intern/builder/deg_builder_relations.cc$1714-1737 ``` /* It is possible that RNA path points to a property of a different ID than the target_id: ``` * for example, paths like "data" on Object, "camera" on Scene. ``` ...

blender-admin commented

2022-06-29 18:03:46 +02:00

This issue was referenced by 2f729bc111

This issue was referenced by 2f729bc1117cddd809a8545ae7f4dd424e689dbc

Alexander Gavrilov commented

2022-08-31 18:01:03 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Alexander Gavrilov closed this issue

2022-08-31 18:01:03 +02:00

Alexander Gavrilov self-assigned this 2022-08-31 18:01:03 +02:00

R. C. Randolph referenced this issue

2023-07-01 00:01:12 +02:00