Page MenuHome
Create Task
Maniphest T66979

Can not set one image node to non-color without changing it for every node using that image
Closed, ArchivedPublic
Actions

Description

System Information
Operating system: Linux-4.4.0-151-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.26

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-15 09:24, hash: rB576963d7c1e4
Worked: 2.79, and 2.80 until a while ago

Short description of error
Often you want to load an image texture and use it both as input for color, as well as roughness or bump.
Previously it was possible to just duplicate the image node, set the second node to non-color and it would work as expected.
Now if you use the same image data-block, setting the colorspace will always set the colorspace for all instances of that image.
I know this is also kind of expected, but also breaks many older shaders.

Exact steps for others to reproduce the error
Open this blendfile and try to change the colorspace of just one image node to non-color.

image_colorspace.blend425 KBDownload

Related Objects

Event Timeline

Sebastian Koenig (sebastian_k) created this task.Jul 15 2019, 12:04 PM
Philipp Oeser (lichtwerk) added a subscriber: Philipp Oeser (lichtwerk).Jul 15 2019, 12:20 PM

This was an intentional change, see rB7ad802cf3ae5

This change breaks compatibility for cases where multiple image texture nodes
were using the same image with different color space node settings. However it
gives more predictable behavior for baking and texture painting if save, load
and image editing operations have a single color space to handle.

My workaround:

  • create a new image
  • change it from "Generated" to "Single Image"
  • paste filepath from the "other" image
  • change to colorspace of your liking...

Guess we have to close this one...

Philipp Oeser (lichtwerk) changed the task status from Unknown Status to Archived.Jul 15 2019, 12:21 PM
Philipp Oeser (lichtwerk) claimed this task.
Sebastian Koenig (sebastian_k) added a comment.Jul 15 2019, 12:30 PM

ok, thanks.
Btw: even easier workaround: Duplicate the node, make single user. :)

Philipp Oeser (lichtwerk) added a comment.Jul 15 2019, 12:51 PM
In T66979#722446, @Sebastian Koenig (sebastian_k) wrote:

ok, thanks.
Btw: even easier workaround: Duplicate the node, make single user. :)

True! :)

Philipp Oeser (lichtwerk) mentioned this in T66985: Texture color space in shader editor resets every time i import textures.Jul 15 2019, 1:44 PM
Philipp Oeser (lichtwerk) mentioned this in T68047: Found a bug during shading process.Aug 1 2019, 12:49 PM
Philipp Oeser (lichtwerk) mentioned this in T68182: Color Data for Image Texture Nodes.Aug 6 2019, 11:31 AM
Philipp Oeser (lichtwerk) merged a task: T68182: Color Data for Image Texture Nodes.
Philipp Oeser (lichtwerk) added subscribers: Dan Balderson (DannyLee89), Wo!262 (wo262).
Philipp Oeser (lichtwerk) mentioned this in T71153: Color space configuration of copies of image texture nodes is not independent..Oct 28 2019, 10:23 AM
Philipp Oeser (lichtwerk) merged a task: T71153: Color space configuration of copies of image texture nodes is not independent..
Philipp Oeser (lichtwerk) added a subscriber: Anant Rao Kandikuppa (AntBlender2).
Philipp Oeser (lichtwerk) mentioned this in T73341: Wrong Texture Color Space assigned when opening 2.79 into 2.8x.Jan 23 2020, 2:04 PM