Drivers on bone custom properties can get update delays #32495

New Issue

Nathan Vegdahl · 2012-09-05T01:34:16+02:00

Nathan Vegdahl commented

2012-09-05 01:34:16 +02:00

%%%In a specific useful circumstance, drivers on the custom properties of bones can create the infamous single-frame delay.

This bug occurs when you have 3 or more bones, which we'll call A, B, and C.

A property (custom or not) on bone A is driven by a custom property on bone B. Then that custom property is driven by another custom property on bone C. Thus, indirectly, the custom property on bone C affects bone A. When changing or animating the custom property on bone C, an update delay is introduced between it and the corresponding property on bone A.

A file is attached that illustrates this in the simplest case.

Because the dependencies are only between bones, which Blender can otherwise handle fine (e.g. with constraints), and is not within a single bone, it seems like this ought to be something that Blender can handle. It is useful to be able to do this when trying to construct multiple complex drivers that share some components, and which you would like to maintain in the future.

If this isn't something that can be fixed under the current depgraph, suggestions on how to work around this limitation are welcome.%%%

%%%In a specific useful circumstance, drivers on the custom properties of bones can create the infamous single-frame delay. This bug occurs when you have 3 or more bones, which we'll call A, B, and C. A property (custom or not) on bone A is driven by a custom property on bone B. Then that custom property is driven by another custom property on bone C. Thus, indirectly, the custom property on bone C affects bone A. When changing or animating the custom property on bone C, an update delay is introduced between it and the corresponding property on bone A. A file is attached that illustrates this in the simplest case. Because the dependencies are only between bones, which Blender can otherwise handle fine (e.g. with constraints), and is not within a single bone, it seems like this ought to be something that Blender can handle. It is useful to be able to do this when trying to construct multiple complex drivers that share some components, and which you would like to maintain in the future. If this isn't something that can be fixed under the current depgraph, suggestions on how to work around this limitation are welcome.%%%

Nathan Vegdahl commented

2012-09-05 01:34:16 +02:00

Changed status to: 'Open'

Ton Roosendaal commented

2012-10-19 18:50:38 +02:00

%%%Hey Nathan!

I'm back to Blender :) first cleaning the tracker, do some finger exercises with bugfixng, but the depsgraph is definitely on the agenda now.
The issue has been extensively noted in the todo for wiki though. Will add your report, and close this for future reference.

http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Animation%%%

%%%Hey Nathan! I'm back to Blender :) first cleaning the tracker, do some finger exercises with bugfixng, but the depsgraph is definitely on the agenda now. The issue has been extensively noted in the todo for wiki though. Will add your report, and close this for future reference. http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Animation%%%

Ton Roosendaal commented

2012-10-19 18:50:39 +02:00

Changed status from 'Open' to: 'Archived'

Ton Roosendaal closed this issue

2012-10-19 18:50:39 +02: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

Drivers on bone custom properties can get update delays #32495