Muting a node in Cycles erases automation data #38286

New Issue

Seth L. · 2014-01-19T13:37:37+01:00

Seth L. commented

2014-01-19 13:37:37 +01:00

System Information
Observed on Mac OS X 10.6 and Mac OS X 10.8

Blender Version
Broken: (2.69 .0 r60991)
Worked: (never worked as far as I know)

Short description of error
Muting a node in Cycles destroys any automation on the node.

Exact steps for others to reproduce the error

Create a material in Cycles, add some nodes
Automate a parameter of a node
Mute that node (M key while selected)
Unmute it (M key again) and find your automation is lost

The .blend I'm attaching demonstrates it easily. It's all set up and ready to try.
NodeAutomationBug.blend

**System Information** Observed on Mac OS X 10.6 and Mac OS X 10.8 **Blender Version** Broken: (2.69 .0 r60991) Worked: (never worked as far as I know) **Short description of error** Muting a node in Cycles destroys any automation on the node. **Exact steps for others to reproduce the error** 1. Create a material in Cycles, add some nodes 2. Automate a parameter of a node 3. Mute that node (M key while selected) 4. Unmute it (M key again) and find your automation is lost The .blend I'm attaching demonstrates it easily. It's all set up and ready to try. [NodeAutomationBug.blend](https://archive.blender.org/developer/F70658/NodeAutomationBug.blend)

Seth L. commented

2014-01-19 13:37:37 +01:00

Changed status to: 'Open'

Seth L. commented

2014-01-19 13:37:37 +01:00

Added subscriber: @quantumanomaly

Seth L. commented

2014-01-19 14:53:51 +01:00

Update: I have found that the same bug occurs when using Blender Internal. It is not specific to Cycles.
This came as a bit of a surprise to me as Blender Internal is not new.
In any case, it appears not to be a problem with the render engine but rather the automation system or the node system.

**Update:** I have found that the same bug occurs when using Blender Internal. It is not specific to Cycles. This came as a bit of a surprise to me as Blender Internal is not new. In any case, it appears *not* to be a problem with the render engine but rather the automation system or the node system.

Bastien Montagne commented

2014-01-19 15:10:02 +01:00

Changed status from 'Open' to: 'Duplicate'

Bastien Montagne closed this issue

2014-01-19 15:10:02 +01:00

Bastien Montagne commented

2014-01-19 15:10:02 +01:00

✘ Merged into #38221.

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

Muting a node in Cycles erases automation data #38286