Page MenuHome

Mapping node values get stuck after setting a keyframe
Closed, ResolvedPublicBUG

Description

System Information
Operating system: Windows 7
Graphics card: GTX 480

Blender Version
Broken: 2.80 (sub 43), branch: blender2.7, commit date: 2019-02-01 01:46, hash: 552b2287db86

Short description of error
If a keyframe is set on a value in the mapping node in the shader editor, you can no longer change any values in this node, or any other mapping nodes. Issue persists after removing the keyframes.
Exact steps for others to reproduce the error

  1. Open default file
  2. Open Shader Editor
  3. Add Mapping Node
  4. Set keyframe to any of the properties (e.g. Rotation)
  5. Try to adjust the values in the node

Edit: File with bugged mapping node, even after removing keyframe

Event Timeline

rndmnm created this task.Feb 1 2019, 9:39 PM
Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.

@Brecht Van Lommel (brecht) I'm unsure who to assign this to so I'll assign you as you are the only member of the node editor module.

@rndmnm, please always attach .blend files, even if the steps seems trivial. Helps a lot following the bugs and saves a lot of time while troubleshooting.

rndmnm updated the task description. (Show Details)Feb 4 2019, 2:19 PM

@Sergey Sharybin (sergey) Ok, will keep that in mind.

There's the same problem with other nodes e.g. "value" node. New value seems to be correctly inserted under the hood, but displayed value is stuck. When you copy the keyframed node, the copy will not have keyframes, but the displayed value also stays the same.


Brecht Van Lommel (brecht) raised the priority of this task from 50 to High.Mar 8 2019, 2:14 PM