Image Texture Node UI resets Color Space #70688

New Issue

Conrad Dueck · 2019-10-10T02:22:38+02:00

Conrad Dueck commented

2019-10-10 02:22:38 +02:00

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: fb46d273f8
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.

**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: `fb46d273f8` 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.

Conrad Dueck commented

2019-10-10 02:22:38 +02:00

Added subscriber: @ConradDueck

Philipp Oeser commented

2019-10-10 10:01:10 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-10-10 10:01:10 +02:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2019-10-10 10:01:10 +02:00

Philipp Oeser self-assigned this 2019-10-10 10:01:10 +02:00

Philipp Oeser commented

2019-10-10 10:01:10 +02:00

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 7ad802cf3a. [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.

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 7ad802cf3a. [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.

Conrad Dueck commented

2019-10-10 20:31:25 +02:00

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?

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?

Philipp Oeser commented

2019-10-10 20:49:48 +02:00

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 #69244, #66985, #68047, but was not considered a bug.

see also https://wiki.blender.org/wiki/Reference/Not_a_bug

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 #69244, #66985, #68047, but was not considered a bug. see also https://wiki.blender.org/wiki/Reference/Not_a_bug

Conrad Dueck commented

2019-11-01 18:40:25 +01:00

If I repath to a new image using the sidebar, or in the other places I mentioned, or via python, Blender doesn't force a color space change. Also, just because Blender CAN do something, it should still be optional for me to allow it to do that thing. Is it possible to provide an image example where "Non-color" is not supported and "sRGB" is?

Samuel Gariépy commented

2021-12-13 16:07:54 +01:00

Added subscriber: @sgariepy.3d

Samuel Gariépy commented

2021-12-13 16:11:12 +01:00

Removed subscriber: @sgariepy.3d

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

Image Texture Node UI resets Color Space #70688