Node values visually reset when changed #60900

New Issue

msalv · 2019-01-26T21:34:59+01:00

msalv commented

2019-01-26 21:34:59 +01:00

System Information
Operating system: Windows 10 64 bit
Graphics card: Nvidia 1060 6gb

Blender Version
Broken: blender-2.80.0-git.1b6da95ccb11-windows64

Short description of error

Under certain circumstances, changing the value of a node snaps back to the previous value, although this is just the UI, the actual value has changed but it doesn't update in the UI. It only applies to nodes not plugged to the Material output, or to a tree that eventually plugs to the Material output

Exact steps for others to reproduce the error
I know of two ways to trigger this bug

1: Add a material, and add a node. Make sure to not connect it to the Material Output node. Insert a keyframe on a value of the node, press play and stop the animation, and delete the keyframe of the node value. Now all the values of all the nodes (that aren't plugged to the Material output) will reset when you try to drag the sliders or type in them
2: Any new node you insert from the add menu will behave fine. Plug any of the other nodes that you know have the bug on the material output. That node will update, but the rest of the nodes will bug, including the new ones

Apart from plugging the nodes to the output or a tree connected to the output, another way of working around this is to change the name of the node in the N sidebar

You can use this blend file to play with it. The bug gets saved on the file
bugreport8.blend

**System Information** Operating system: Windows 10 64 bit Graphics card: Nvidia 1060 6gb **Blender Version** Broken: blender-2.80.0-git.1b6da95ccb11-windows64 **Short description of error** ![ezgif.com-video-to-gif.gif](https://archive.blender.org/developer/F6414026/ezgif.com-video-to-gif.gif) Under certain circumstances, changing the value of a node snaps back to the previous value, although this is just the UI, the actual value has changed but it doesn't update in the UI. It only applies to nodes not plugged to the Material output, or to a tree that eventually plugs to the Material output **Exact steps for others to reproduce the error** I know of two ways to trigger this bug 1: Add a material, and add a node. Make sure to not connect it to the Material Output node. Insert a keyframe on a value of the node, press play and stop the animation, and delete the keyframe of the node value. Now all the values of all the nodes (that aren't plugged to the Material output) will reset when you try to drag the sliders or type in them 2: Any new node you insert from the add menu will behave fine. Plug any of the other nodes that you know have the bug on the material output. That node will update, but the rest of the nodes will bug, including the new ones Apart from plugging the nodes to the output or a tree connected to the output, another way of working around this is to change the name of the node in the N sidebar You can use this blend file to play with it. The bug gets saved on the file [bugreport8.blend](https://archive.blender.org/developer/F6414091/bugreport8.blend)

msalv commented

2019-01-26 21:34:59 +01:00

Added subscriber: @moisessalvador

Philipp Oeser commented

2019-01-28 09:51:16 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-01-28 09:51:16 +01:00

might be related to studio/blender-studio#59495

Ulysse Martin commented

2019-02-13 12:18:44 +01:00

Added subscriber: @you.le

Ulysse Martin commented

2019-02-13 12:18:44 +01:00

I can reproduce this bug.
Here is another test file: keyshading.blend

I don't know how to "fix" it but I noticed that we can sliders are not reseted applying one of these patches:

1 -> commenting something in node_draw.c : p.diff
2 -> changing something in deg_eval_copy_on_write.cc :
p2.diff

I can reproduce this bug. Here is another test file: [keyshading.blend](https://archive.blender.org/developer/F6598746/keyshading.blend) I don't know how to "fix" it but I noticed that we can sliders are not reseted applying one of these patches: 1 -> commenting something in node_draw.c : [p.diff](https://archive.blender.org/developer/F6598765/p.diff) 2 -> changing something in deg_eval_copy_on_write.cc : [p2.diff](https://archive.blender.org/developer/F6598774/p2.diff)

Brecht Van Lommel was assigned by Philipp Oeser

2019-03-04 15:20:04 +01:00

Philipp Oeser commented

2019-03-04 15:20:04 +01:00

Added subscriber: @brecht

Philipp Oeser commented

2019-03-04 15:20:04 +01:00

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

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

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 values visually reset when changed #60900