Driver Workflow Design #54653

New Issue

Joshua Leung · 2018-04-16T13:03:48+02:00

Joshua Leung commented

2018-04-16 13:03:48 +02:00

For Blender 2.8, we want to improve the workflow for adding drivers. Here's how:

When the user right-clicks on a property and adds a driver, we display a non-modal, persistent Add Driver floating popup.
While open, all of Blender remains responsive, and the user can select any object in the scene.

Optionally, users can then set a multiply and offset value, and add additional driver inputs. They can also click the Open Driver Editor button to open a Drivers window,

Users can also use the ID type picker to select from a list of Object and property ID's. They can also, using the eyedropper, directly select an object in the 3D View, or in the Outliner. When users select an object, they are presented with a basic list of commonly used properties, like so:

If the user has closed this window and wants to get it back, they can right-click on the property being driven and
select Edit Driver, like so:

For Blender 2.8, we want to improve the workflow for adding drivers. Here's how: - When the user right-clicks on a property and adds a driver, we display a non-modal, persistent Add Driver floating popup. - While open, all of Blender remains responsive, and the user can select any object in the scene. # From the popup, users can select a property to use as as a driver. No other steps are needed. ![Screen Shot 2018-05-16 at 19.24.15.png](https://archive.blender.org/developer/F3376242/Screen_Shot_2018-05-16_at_19.24.15.png) Optionally, users can then set a multiply and offset value, and add additional driver inputs. They can also click the Open Driver Editor button to open a Drivers window, Users can also use the ID type picker to select from a list of Object and property ID's. They can also, using the eyedropper, directly select an object in the 3D View, or in the Outliner. When users select an object, they are presented with a basic list of commonly used properties, like so: ![Screen Shot 2018-05-16 at 19.34.02.png](https://archive.blender.org/developer/F3376299/Screen_Shot_2018-05-16_at_19.34.02.png) If the user has closed this window and wants to get it back, they can right-click on the property being driven and select Edit Driver, like so: ![Screen Shot 2018-05-16 at 19.08.59.png](https://archive.blender.org/developer/F3376245/Screen_Shot_2018-05-16_at_19.08.59.png)

Joshua Leung self-assigned this 2018-04-16 13:03:48 +02:00

Joshua Leung commented

2018-04-16 13:03:48 +02:00

Added subscriber: @JoshuaLeung

Joshua Leung commented

2018-05-04 11:28:52 +02:00

Added subscribers: @WilliamReynish, @pablovazquez

msalv commented

2018-05-04 13:47:51 +02:00

Added subscriber: @moisessalvador

Joshua Leung was unassigned by William Reynish

2018-05-16 17:47:48 +02:00

William Reynish self-assigned this 2018-05-16 17:47:48 +02:00

Luciano Muñoz Sessarego commented

2018-05-16 19:01:20 +02:00

Added subscriber: @LucianoMunoz

Jorge Vásquez Pérez commented

2018-05-16 19:50:21 +02:00

Added subscriber: @yorch

Jorge Vásquez Pérez commented

2018-05-16 19:50:21 +02:00

Sounds like an definite improvement to the current workflow which it has to be said is a little cumbersome.
I question I have is, will it be possible to also use the eye-dropper to select objects directly in the outliner ?

Sounds like an definite improvement to the current workflow which it has to be said is a little cumbersome. I question I have is, will it be possible to also use the eye-dropper to select objects directly in the outliner ?

Dimitri Bastos commented

2018-05-16 21:04:33 +02:00

Added subscriber: @DimitriBastos

Dimitri Bastos commented

2018-05-16 21:04:33 +02:00

This is a much needed improvement. The currect workflow is way to clicky and uses a lot of space due to the graph editor interface.

William Reynish commented

2018-05-16 21:06:42 +02:00

Yes, it will be possible to select objects in the outliner too.

KiJeon commented

2018-05-17 10:03:13 +02:00

Added subscriber: @0o00o0oo

KiJeon commented

2018-05-17 10:03:13 +02:00

YES, much needed. I actively avoid drivers because they're so cumbersome to setup. I'm really curious about what "Open Driver Editor" will open.

Few questions:

Will the Add/Edit Driver will also include the ability to modify expression in the popup window? Or maybe that's the plan with the "Open Driver Editor"?
As an example, After Effects provides such a quick and easy access to expressions (basically their drivers system), I use the feature quite frequently, which is opposite my behavior in Blender. Example here: https://vimeo.com/94981235#t=1m32s.
After Effect's ability to quickly pick-whip desired targets into expression being written is really useful. In Blender, maybe the eyedropper could do the trick? And maybe auto generate variable names by default.
Could expanding expression capabilities be a target in 2.8? Such as being able to define variables, using self's base value, logical operators, etc.

YES, much needed. I actively avoid drivers because they're so cumbersome to setup. I'm really curious about what "Open Driver Editor" will open. Few questions: 1) Will the Add/Edit Driver will also include the ability to modify expression in the popup window? Or maybe that's the plan with the "Open Driver Editor"? As an example, After Effects provides such a quick and easy access to expressions (basically their drivers system), I use the feature quite frequently, which is opposite my behavior in Blender. Example here: https://vimeo.com/94981235#t=1m32s. 2) After Effect's ability to quickly pick-whip desired targets into expression being written is really useful. In Blender, maybe the eyedropper could do the trick? And maybe auto generate variable names by default. 3) Could expanding expression capabilities be a target in 2.8? Such as being able to define variables, using self's base value, logical operators, etc.

msalv commented

2018-05-17 10:10:27 +02:00

Removed subscriber: @moisessalvador

zebus3d commented

2018-05-17 14:07:08 +02:00

Added subscriber: @zebus3dream

Juan Gea commented

2018-05-17 18:45:09 +02:00

Added subscriber: @juang3d

William Reynish commented

2018-05-17 22:55:39 +02:00

Re. expressions, we discussed this during the design session. We may revisit it.

With this design, we wanted to strike a balance, where this interface remains lightweight and quick to use, while the full Drivers Editor remains as an area for full control.

We initially considered expressions more of a 'deep' feature, but perhaps we can find a way to include it here, as long as it doesn't take up too much space or is too cumbersome to use.

Re. expressions, we discussed this during the design session. We may revisit it. With this design, we wanted to strike a balance, where this interface remains lightweight and quick to use, while the full Drivers Editor remains as an area for full control. We initially considered expressions more of a 'deep' feature, but perhaps we can find a way to include it here, as long as it doesn't take up too much space or is too cumbersome to use.

Luciano Muñoz Sessarego commented

2018-05-18 15:13:25 +02:00

|
|

data

In #54653#503598, @WilliamReynish wrote:
Re. expressions, we discussed this during the design session. We may revisit it.

With this design, we wanted to strike a balance, where this interface remains lightweight and quick to use, while the full Drivers Editor remains as an area for full control.

We initially considered expressions more of a 'deep' feature, but perhaps we can find a way to include it here, as long as it doesn't take up too much space or is too cumbersome to use.

cant you just write expressions in a property by using the "#" and just writing it there?

| | | data | | | -- | -- | > In #54653#503598, @WilliamReynish wrote: > Re. expressions, we discussed this during the design session. We may revisit it. > > With this design, we wanted to strike a balance, where this interface remains lightweight and quick to use, while the full Drivers Editor remains as an area for full control. > > We initially considered expressions more of a 'deep' feature, but perhaps we can find a way to include it here, as long as it doesn't take up too much space or is too cumbersome to use. cant you just write expressions in a property by using the "#" and just writing it there?

William Reynish commented

2018-05-18 15:33:58 +02:00

Yes, we discussed that actually. It's just that currently, the properties don't work like that. When you hit return, the result is applied, and you can't 'edit' the expression, as you'd want to do. But maybe we can make it work that way.

Dimitri Bastos commented

2018-05-18 19:25:48 +02:00

Would be possible to create a "bigger" box for expressions? It's a little difficult to handle a big expression by a one line entry box/form.

Joshua Leung commented

2018-05-18 19:29:30 +02:00

@DimitriBastos In most cases, you really shouldn't need a very large space at all (though it's true that the current space may be a bit small). Really, if you aren't going in putting massive `bpy.data.blah["blah_name"].propname" paths everywhere (which you really, really, really shouldn't be doing), you shouldn't be running into any problems in general for most expressions :)

KiJeon commented

2018-05-18 19:56:15 +02:00

Not sure for the scope of this task, but I agree, Blender should allow for a more robust expression system.

After Effects is a good model for this. Being able to easily write multi-line expressions defining variables and logical operators really helps settings up dynamic scenes. I use expressions every chance I get.
In Blender, it's the opposite. It's really a hassle to setup drivers/expressions, I avoid doing that if at all possible.

Not sure for the scope of this task, but I agree, Blender should allow for a more robust expression system. After Effects is a good model for this. Being able to easily write multi-line expressions defining variables and logical operators really helps settings up dynamic scenes. I use expressions every chance I get. In Blender, it's the opposite. It's really a hassle to setup drivers/expressions, I avoid doing that if at all possible.

Lucas Boutrot commented

2018-05-23 15:09:42 +02:00

Added subscriber: @thornydre

Lucas Boutrot commented

2018-05-23 15:09:42 +02:00

Would it be possible to have a preview of the curve of the function if we create a driver using Python ?

zebus3d commented

2018-07-17 14:49:49 +02:00

Removed subscriber: @zebus3dream

Luciano Muñoz Sessarego commented

2018-08-13 11:35:28 +02:00

would be nice to in that same panel be able to tell it to make it the standard 0.0 to 1.1, curve or the inverted :)
also this is very related but not exclusive, in 2.77 the pinning of the properties doesnt seem to work correctly, which is what really messes up the current driver creation workflow, if that gets fixed, then this will be even more powerful!

would be nice to in that same panel be able to tell it to make it the standard 0.0 to 1.1, curve or the inverted :) also this is very related but not exclusive, in 2.77 the pinning of the properties doesnt seem to work correctly, which is what really messes up the current driver creation workflow, if that gets fixed, then this will be even more powerful!

Duarte Farrajota Ramos commented

2018-11-19 15:54:59 +01:00

Added subscriber: @DuarteRamos

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Driver Workflow Design #54653

From the popup, users can select a property to use as as a driver. No other steps are needed.