Node Editor: value stuck after setting a keyframe and clearing clearframes again #61963

New Issue

Addison · 2019-02-26T04:37:43+01:00

Addison commented

2019-02-26 04:37:43 +01:00

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

Blender Version
Broken: 2.80 Beta, 893fa59831, 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 (@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.

**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 (@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.

Addison commented

2019-02-26 04:37:43 +01:00

Added subscriber: @seaside98-4

blender-admin commented

2019-02-26 04:37:43 +01:00

#62206 was marked as duplicate of this issue

Sebastian Koenig commented

2019-02-26 08:43:15 +01:00

Added subscriber: @sebastian_k

Sebastian Koenig commented

2019-02-26 08:43:15 +01:00

I cannot reproduce that. It works as expected here.

Addison commented

2019-02-27 03:37:21 +01:00

Bug.blend
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.

[Bug.blend](https://archive.blender.org/developer/F6720707/Bug.blend) 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.

Sebastian Koenig commented

2019-02-27 09:02:05 +01:00

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.

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 commented

2019-02-27 13:57:07 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-02-27 13:57:07 +01:00

No idea what is happening there. Checking...

Philipp Oeser commented

2019-03-04 14:04:28 +01:00

Added subscribers: @ZedDB, @lichtwerk

Philipp Oeser commented

2019-03-04 14:04:28 +01:00

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

All is fine again if you call something like:

bpy.data.materials['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
T61963_example.blend

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

Issue seems to be that there is (borked) animation data on the nodetree. All is fine again if you call something like: ``` bpy.data.materials['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 [T61963_example.blend](https://archive.blender.org/developer/F6759482/T61963_example.blend) I can also imagine there is already a report for this, since this "value-is-stuck-after-setting-clearing-keyframes" sounds very familiar... @JacquesLucke , @ZedDB , does this ring a bell [in regards to: do we have similar reports?]

Philipp Oeser changed title from ~~Node Wrangler: Ctrl-T Vector Mapping Node Broken~~ to Node Editor: value stuck after setting a keyframe and clearing clearframes again

2019-03-04 14:05:45 +01:00

Philipp Oeser commented

2019-03-04 15:06:12 +01:00

Found a report that is closely related: #60900

Brecht Van Lommel was assigned by Philipp Oeser

2019-03-04 15:19:26 +01:00

Philipp Oeser commented

2019-03-04 15:19:26 +01:00

Added subscriber: @brecht

Philipp Oeser commented

2019-03-04 15:19:26 +01:00

since @brecht did 83f8f44791, assigning to him...

since @brecht did 83f8f44791, assigning to him...

Brecht Van Lommel commented

2019-03-05 11:47:52 +01:00

Added subscriber: @Vyach

Vyacheslav Kobozev commented

2019-03-05 11:58:14 +01:00

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?)

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?)

Vyacheslav Kobozev commented

2019-03-05 12:16:40 +01:00

Another bit of info. If i add driver, it starts to move but interminent
2019-03-05_14-14-18.mp4

Another bit of info. If i add driver, it starts to move but interminent [2019-03-05_14-14-18.mp4](https://archive.blender.org/developer/F6765557/2019-03-05_14-14-18.mp4)

blender-admin commented

2019-03-08 14:59:33 +01:00

This issue was referenced by 89fa6a7a06

This issue was referenced by 89fa6a7a063e74604c14aedef9b88599249e3a29

Brecht Van Lommel commented

2019-03-08 15:16:33 +01:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-03-08 15:16:33 +01:00

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

Node Editor: value stuck after setting a keyframe and clearing clearframes again #61963