Using another property to control the animation

Most time-based recipes can run from the frame. An input-driven recipe needs a value to respond to.

Clock-driven or input-driven?

A blink can run because time advances. A remap, threshold or controller response needs a source property. The input is not the object you want to animate: it is the value that tells the recipe what to do.

SOURCEThe value you read

For example, a custom property on a controller object.

RECIPEThe response you choose

Map, clamp, threshold or reshape that source.

DESTINATIONThe property you change

For example, a light's power or a door's angle.

Choose the property to read

Select an input-driven template available in your edition.
Use its input-source controls to identify the source object/datablock and property.
Set a meaningful source range; a factor from 0 to 1 is not the same as a distance in metres.
Choose a separate destination and apply.
Change the source value to test the response. A stationary source normally produces a stationary output.

Driver Espresso and Premium include input-driven recipes. The current Lite catalogue does not require external driver-variable inputs.

Avoid circular dependencies

Do not make a property depend on itself, directly or through another driven property. Keep a clear direction from controller to result. If Blender reports a dependency cycle, remove the cycle rather than adding more update calls.