Drivers do not work in node groups. #46587

New Issue

Philip Holzmann · 2015-10-24T18:03:06+02:00

Philip Holzmann commented

2015-10-24 18:03:06 +02:00

System Information
Windows 7 64 bit with 64 bit Blender

Blender Version
Broken: 2.76.2 fbca69c

Short description of error
Drivers do not work, when they are inside a node group.
(Didn't test it outside the compositor.)

Exact steps for others to reproduce the error
bug.blend
The value node on the top left (labeled "#frame") has a driver which takes the current frame number.
The group node below contains a value node also has a driver, and should output the current frame number. But this does NOT work.

So you can see it, if you render, the output of the group node is displayed on the left; the output of the (ungrouped) value node is displayed on the right.

**System Information** Windows 7 64 bit with 64 bit Blender **Blender Version** Broken: 2.76.2 fbca69c **Short description of error** Drivers do not work, when they are inside a node group. (Didn't test it outside the compositor.) **Exact steps for others to reproduce the error** [bug.blend](https://archive.blender.org/developer/F247154/bug.blend) The value node on the top left (labeled "#frame") has a driver which takes the current frame number. The group node below contains a value node also has a driver, and should output the current frame number. But this does NOT work. So you can see it, if you render, the output of the group node is displayed on the left; the output of the (ungrouped) value node is displayed on the right.

Philip Holzmann commented

2015-10-24 18:03:06 +02:00

Changed status to: 'Open'

Philip Holzmann commented

2015-10-24 18:03:06 +02:00

Added subscriber: @Foaly

Sergey Sharybin commented

2015-10-27 19:22:57 +01:00

Added subscriber: @Sergey

Sergey Sharybin self-assigned this 2015-10-27 19:22:57 +01:00

Sergey Sharybin commented

2015-10-27 19:22:57 +01:00

This is something which can't really work in the old depsgraph but something i would expect to work in the new one. Need to have some closer look tho.

blender-admin commented

2015-11-06 14:36:22 +01:00

This issue was referenced by 97c8619b42

This issue was referenced by 97c8619b421b979dc4b05ed0959e90de532813ba

Sergey Sharybin commented

2015-11-06 14:37:54 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2015-11-06 14:37:54 +01:00

Mr. Burns commented

2016-01-20 11:36:41 +01:00

Added subscriber: @mrburns

Mr. Burns commented

2016-01-20 11:36:41 +01:00

Hi,

the problem still exists!
I have the x value of a blur node driven by the Z location of the default cube. This works.
But if I put the blur node into a group then it does not work anymore, the x value is always zero.

My Blender version is 2.76b, Date 2015-11-03- 10:56, Hash f337fea.
I use the Windows 64 bit version

Best regards,

Mr. Burns

Hi, the problem still exists! I have the x value of a blur node driven by the Z location of the default cube. This works. But if I put the blur node into a group then it does not work anymore, the x value is always zero. My Blender version is 2.76b, Date 2015-11-03- 10:56, Hash f337fea. I use the Windows 64 bit version Best regards, Mr. Burns

Mr. Burns commented

2016-01-20 11:58:17 +01:00

Hi,

I also tested with version 2.76 Date 2016-01-20 00:43 hash bda0820, but still the same. The Z location of the cube is 2.15.
The blur node inside group does not update the x value. It shows 3.
The blur node out of group does it correctly. It shows 2.
(both use same driver)

Hi, I also tested with version 2.76 Date 2016-01-20 00:43 hash bda0820, but still the same. The Z location of the cube is 2.15. The blur node inside group does not update the x value. It shows 3. The blur node out of group does it correctly. It shows 2. (both use same driver) ![Driver_inside_group_not_working.jpg](https://archive.blender.org/developer/F275303/Driver_inside_group_not_working.jpg)

Sergey Sharybin commented

2016-01-25 10:04:47 +01:00

If this doesn't work after switching to the new dependency graph, then please make a new bug report including all the details and .blend file demonstrating the problem.

Julian Eisel commented

2016-01-25 10:23:21 +01:00

Added subscriber: @JulianEisel

Julian Eisel commented

2016-01-25 10:23:21 +01:00

@mrburns, you need to explicitly enable the new dependency graph by launching Blender from the command line with the --enable-new-depsgraph argument.

@mrburns, you need to explicitly enable the new dependency graph by launching Blender from the command line with the `--enable-new-depsgraph` argument.

Lukas Remis commented

2018-06-17 21:42:52 +02:00

Added subscriber: @lukas.remis

Lukas Remis commented

2018-06-17 21:42:52 +02:00

Changed status from 'Resolved' to: 'Open'

Lukas Remis reopened this issue

2018-06-17 21:42:52 +02:00

Lukas Remis commented

2018-06-17 21:42:52 +02:00

This bug is still present in 2.79b (Mac version)drivers_error.blend.
Attaching test file. I try to drive some values inside a group with the input value from the group node.

Tried starting Blender with --enable-new-depsgraph - still drivers do not work in node groups.

This bug is still present in 2.79b (Mac version)[drivers_error.blend](https://archive.blender.org/developer/F3727634/drivers_error.blend). Attaching test file. I try to drive some values inside a group with the input value from the group node. Tried starting Blender with --enable-new-depsgraph - still drivers do not work in node groups.

Sergey Sharybin commented

2018-10-29 16:36:51 +01:00

Please make a simple file where it's clear which exact drivers do not work. If it's possible top reproduce with one driver, that'd be way more clear to understand desired behavior.

In this example some of the drivers are actually set to constant values, and some other drivers are trying to drive nodes of same node tree. Note that this should probably work, but chained drivers are not yet supported (as in, node_a drivers node_b and node_b drives node_c of the same tree).

Please make a simple file where it's clear which exact drivers do not work. If it's possible top reproduce with one driver, that'd be way more clear to understand desired behavior. In this example some of the drivers are actually set to constant values, and some other drivers are trying to drive nodes of same node tree. Note that this should probably work, but chained drivers are not yet supported (as in, node_a drivers node_b and node_b drives node_c of the same tree).

Philipp Oeser commented

2018-11-09 11:12:08 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2018-11-09 11:12:08 +01:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2018-11-09 11:12:08 +01:00

Philipp Oeser commented

2018-11-09 11:12:08 +01:00

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

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 do not work in node groups. #46587