Changing image path in Image Texture node resets color space #74284

New Issue

Ludvik Koutny · 2020-02-28T11:13:08+01:00

Ludvik Koutny commented

2020-02-28 11:13:08 +01:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7
Worked: (optional)

Short description of error
When changing image file path in Image Texture node, Color Space is always reset to sRGB even if it was changed by user. This can cause problems if for example users wants to quickly swap a normal map for a new one, and doesn't notice color space has spontaneously changed back to sRGB. It can be especially destructive if it's not noticed immediately, but after a long rendering session for example.

Exact steps for others to reproduce the error

Create a new Image Texture node in the shader editor
Click the folder icon to open file browser and load any image
Switch color space from sRGB to Non-Color
Click the folder icon to open file browser again and load another image
Result: Color Space setting of the image textures reverts back to sRGB without warning
Expected: Color Space setting remains unchanged

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `77d23b0bd7` Worked: (optional) **Short description of error** When changing image file path in Image Texture node, Color Space is always reset to sRGB even if it was changed by user. This can cause problems if for example users wants to quickly swap a normal map for a new one, and doesn't notice color space has spontaneously changed back to sRGB. It can be especially destructive if it's not noticed immediately, but after a long rendering session for example. **Exact steps for others to reproduce the error** - Create a new Image Texture node in the shader editor - Click the folder icon to open file browser and load any image - Switch color space from sRGB to Non-Color - Click the folder icon to open file browser again and load another image Result: Color Space setting of the image textures reverts back to sRGB without warning Expected: Color Space setting remains unchanged

Ludvik Koutny commented

2020-02-28 11:13:08 +01:00

Added subscriber: @Rawalanche

Philipp Oeser commented

2020-02-28 15:05:46 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-02-28 15:05:46 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Philipp Oeser closed this issue

2020-02-28 15:05:46 +01:00

Philipp Oeser self-assigned this 2020-02-28 15:05:46 +01:00

Philipp Oeser commented

2020-02-28 15:05:46 +01:00

This is the same as #70688, #69244, #66985, #68047, but was not considered a bug.

This changed in 7ad802cf3a.

Opening a new image from the Image Texture node will trigger automatic colorspace detection.
As a workaround, you can load another image from the sidebar in the Shader Editor or the Image Editor (or python), doing it from there will not trigger this detection.

This has pros and cons, but it is working as intended and not a bug.
Will have to close, thx for the report anyways!

This is the same as #70688, #69244, #66985, #68047, but was not considered a bug. This changed in 7ad802cf3a. Opening a new image from the Image Texture node will trigger automatic colorspace detection. As a workaround, you can load another image from the sidebar in the Shader Editor or the Image Editor (or python), doing it from there will not trigger this detection. This has pros and cons, but it is working as intended and not a bug. Will have to close, thx for the report anyways!

Ludvik Koutny commented

2020-02-28 16:15:15 +01:00

In #74284#882173, @lichtwerk wrote:
This is the same as #70688, #69244, #66985, #68047, but was not considered a bug.

This changed in 7ad802cf3a.

Opening a new image from the Image Texture node will trigger automatic colorspace detection.
As a workaround, you can load another image from the sidebar in the Shader Editor or the Image Editor (or python), doing it from there will not trigger this detection.

This has pros and cons, but it is working as intended and not a bug.
Will have to close, thx for the report anyways!

Okay, but non the less, this has caused me and other people I know tons of damage already. There is really no colorspace detection going on at all. Regardless of the image type, it will always end up being sRGB.

> In #74284#882173, @lichtwerk wrote: > This is the same as #70688, #69244, #66985, #68047, but was not considered a bug. > > This changed in 7ad802cf3a. > > Opening a new image from the Image Texture node will trigger automatic colorspace detection. > As a workaround, you can load another image from the sidebar in the Shader Editor or the Image Editor (or python), doing it from there will not trigger this detection. > > This has pros and cons, but it is working as intended and not a bug. > Will have to close, thx for the report anyways! Okay, but non the less, this has caused me and other people I know tons of damage already. There is really no colorspace detection going on at all. Regardless of the image type, it will always end up being sRGB.

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

Changing image path in Image Texture node resets color space #74284