Page MenuHome

Image Texture unpredictable behavior in Workbench renderer when duplicating node
Confirmed, NormalPublicBUG

Description

System Information
Operating system: Linux-4.18.0-25-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116

Blender Version
Broken: version: 2.83 (sub 6), branch: master, commit date: 2020-03-03 18:38, hash: rB31aefdeec5a6

Short description of error
Duplicating an Image Texture node causes the displayed image texture to go all white in Workbench renderer

Exact steps for others to reproduce the error

see attached .blend demo

  • fresh blender start, delete cube
  • switch to workbench renderer
  • enable Import Images as Plane, import test image (attached)
  • go in to shader editor
  • select image texture, duplicate it
  • remove image selection from the image texture node, observe that texture in viewport goes all white
  • behavior is unpredictable when selecting different nodes

Demo video:

Source image:

.blend file:

Event Timeline

I can confirm.
I'm not sure which criteria Workbenck uses to choose the texture node. (I imagined it would be the last selected texture).

Manual informs that he chooses the active texture:
https://docs.blender.org/manual/en/latest/render/workbench/color.html#color

If this is the case, it seems that defining the active texture is somewhat unpredictable.

@Jeroen Bakker (jbakker), bug, known issue or works as designed?

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.Fri, Mar 13, 8:45 PM
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".

I analyzed the code and this is really a bug involving depsgraph and "Copy and Write".