Page MenuHome

Node Editor: value stuck after setting a keyframe and clearing clearframes again
Closed, ResolvedPublic


System Information
Operating system: Windows 10
Graphics card: Nvidia GTX 1070

Blender Version
Broken: 2.80 Beta, 893fa598319e, blender2.7, 2019-02-24
Worked: 2.79

When adding the vector mapping to an image texture using the Ctrl-T shortcut from node wrangler, the mapping node added doesn't not behave like mapping nodes added with Shift-A.
Update (@Philipp Oeser (lichtwerk) ): this is apparently unrelated to NodeWrangler, but instead can be reproduced by setting a keyframe on a node on clearing keyframes again...

Left click the X scale and drag down to select the Y and Z values. Type a new number and press Enter.

Expected: All 3 values should be updated with the new value, as they are in a Shift-A added vector mapping node.

Actual: Only the first value gets updated.

Event Timeline

I cannot reproduce that. It works as expected here.

I have attached a Blend file demonstrating the bug. These nodes were copied over from another Blender 2.8 Beta project, and I can't figure out how to reproduce it in a new Blender file.

Wow, that's interesting.
So with your file I am able to reprocuce it. I would guess that somehow the Mapping nodes in your blendfile are broken.
I opened a new file with factory settings, no Node Wrangler, and appended the material "Mineral.001" from your blendfile. When I assign that material to the default cube the Mapping nodes show the same behavior as you described.
Speaking of weird behaviors:
On the Mapping node 'Mapping.008', the bottom one, I cannot even change the mapping type. Clicking on 'Vector', 'Normal' or 'Texture' does nothing.
I am not sure if that bounts as a general bug, or if somehow just the nodes in your material are broken, or if there is some other weirdness is going on.
Because with a new file I cannot reproduce this behavior, with and without Node Wrangler.

Jacques Lucke (JacquesLucke) triaged this task as Confirmed, Medium priority.

No idea what is happening there. Checking...

Issue seems to be that there is (borked) animation data on the nodetree.

All is fine again if you call something like:['Mineral.001'].node_tree.animation_data_clear()

The way to reproduce this (at least thats how I can reproduce this) is to set a keyframe on anything on the node, then clear the keyframe again.
Now we still have animation data on the node but no associated action.
This seems to be 'normal' behavior (its the same for e.g. object translations -- and doesnt cause an issue there), but somewhat turns out to be problematic on nodes...

I would actually suggest to open a new report on this [since this apparently has nothing to do with NodeWrangler].
This can be reproduced with any node without the addon installed, see

I can also imagine there is already a report for this, since this "value-is-stuck-after-setting-clearing-keyframes" sounds very familiar...
@Jacques Lucke (JacquesLucke) , @Sebastian Parborg (zeddb) , does this ring a bell [in regards to: do we have similar reports?]

Philipp Oeser (lichtwerk) renamed this task from Node Wrangler: Ctrl-T Vector Mapping Node Broken to Node Editor: value stuck after setting a keyframe and clearing clearframes again.Mar 4 2019, 2:05 PM

Found a report that is closely related: T60900

Vyacheslav (hitrpr) added a comment.EditedMar 5 2019, 11:58 AM

Oh, here it is!

So bug happens when user try to adjust driven values, then delete drivers. But I still can`t reproduce.

Also it happen when driven node copied and drivers deleted authomatically (is it a bug or intended?)

Another bit of info. If i add driver, it starts to move but interminent

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