Page MenuHome
Create Task
Maniphest T38286

Muting a node in Cycles erases automation data
Closed, DuplicatePublic
Actions

Description

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.blend567 KBDownload

Event Timeline

Seth L. (quantumanomaly) created this task.Jan 19 2014, 1:37 PM
Seth L. (quantumanomaly) raised the priority of this task from to 90.
Seth L. (quantumanomaly) updated the task description. (Show Details)
Seth L. (quantumanomaly) added a project: BF Blender.
Seth L. (quantumanomaly) edited a custom field.
Seth L. (quantumanomaly) added a subscriber: Seth L. (quantumanomaly).
Seth L. (quantumanomaly) added a comment.Jan 19 2014, 2:53 PM

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 (mont29) changed the task status from Unknown Status to Duplicate.Jan 19 2014, 3:10 PM

✘ Merged into T38221.