Page MenuHome

Image Texture Node UI resets Color Space
Closed, ArchivedPublic


System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11

Blender Version
Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-09 19:48, hash: rBfb46d273f885
Worked: (optional)

Short description of error
Image Texture Node UI resets Color Space while manually updating image path or using the sidebar does not.

Exact steps for others to reproduce the error
Open Blender
With the default Cube object selected, add a new material to it.
Open the Shader Editor to see the material node network.
Add an Image Texture node.
Use the node UI browse button to navigate to any image.
Set the Color Space to "Non-Color" (or "Linear" or anything other than sRGB)
Use the node UI browse button to change the image being loaded.
Watch the Color Space reset to "sRGB"
Change the Color Space setting again to something other than sRGB
Now go to the sidebar of the Shader Editor and use the browse button in the Properties section to select a different image.
Color Space remain as it was set.
Now manually replace the path string in the sidebar Properties section to load a different image.
Color Space remain as it was set.

This can be replicated in the 2.80 release build and the 2.81 daily build (as reported here)
I cannot find the same nodeUI<->sidebarUI relationship in 2.78 or 2.79, but both versions do NOT change the color space setting when using the node UI to update the image file.



Event Timeline

Philipp Oeser (lichtwerk) claimed this task.

I think this is not a bug.

  • If you use the node UI browse button, this will open up a new Image datablock, and on opening up a new datablock the colorspace will be determined automatically.
  • If you just change the filepath property of an existing image datablock [sidebar Shader Editor / sidebar Image Editor - Image properties], the colorspace will be kept.

This changed in rB7ad802cf3ae5. [so 2.78 and 2.79 were both having the colorspace setting on the ImageTextureNode - they were not using the colorspace setting of the Image datablock]

It has pros and cons, one might argue that if we do automatic colorspace detection for opening a new image datablock, we should also do this when just changing the filepath on an existing image datablock, but on the other hand this would make it tedious if you want to keep your custom choosen colorspace setting when just wanting to change the image source for an existing datablock.

Will close as not-a-bug, but feel free to comment again if issues persist.

Thanks for your response, Philipp, but I don't understand.

None of the other parameters reset themselves, only the Color Space setting.

For example, Texture Interpolation and Mapping Method and Bound Condition.....all hold their setting.

I stand by the bug report. It's at best inconsistent, but certainly not expected behavior.

Do I need to submit another bug report?

The other settings you mention dont neccessarily depend on the type of new image you are loading, whereas the colorspace can be guessed/determined automatically, thats why blender does that for you.

This has been reported before, see T69244, T66985, T68047, but was not considered a bug.

see also