Wrong Texture Color Space assigned when opening 2.79 into 2.8x #73341

New Issue

Marco G · 2020-01-23T11:53:24+01:00

Marco G commented

2020-01-23 11:53:24 +01:00

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

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d4
Worked: 2.79

Short description of error
Texture Color Space is messed up when opening 2.79 file in Blender 2.8x

Exact steps for others to reproduce the error
Open the attached blend file in 2.79 or older, the wlanut material appears ok.
Instead, when opening the same file in 2.81a (or even 2.82beta), the Color Space of the texture has changed into Non Color, thus messing up my files.

Look at the screenshots--

Happens randomly here, I cannot work this way since it's impossible to check every shader when opening older blend files with tens of materials.280-texture-color-space.blend

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: `f1aa4d18d4` Worked: 2.79 **Short description of error** Texture Color Space is messed up when opening 2.79 file in Blender 2.8x **Exact steps for others to reproduce the error** Open the attached blend file in 2.79 or older, the wlanut material appears ok. Instead, when opening the same file in 2.81a (or even 2.82beta), the Color Space of the texture has changed into Non Color, thus messing up my files. - Look at the screenshots-- Happens randomly here, I cannot work this way since it's impossible to check every shader when opening older blend files with tens of materials.[280-texture-color-space.blend](https://archive.blender.org/developer/F8296752/280-texture-color-space.blend) ![279-texture-color-space.jpg](https://archive.blender.org/developer/F8296749/279-texture-color-space.jpg) ![280-texture-color-space.jpg](https://archive.blender.org/developer/F8296750/280-texture-color-space.jpg)

Marco G commented

2020-01-23 11:53:24 +01:00

Added subscriber: @marcog

Marco G commented

2020-01-23 12:08:26 +01:00

Investigated a bit, it appears that 2.8x cannot assign 2 different Color Space for the same texture, while 2.79 could.

For example in the blend attached i had two nodes with the same wood texture, but with different settings each one:

Linear for color of the material
Non Color for bump

Now when opening with Blender 2.8x it does assign one of the two Color Spaces to each of the texture nodes, thus messing up my base color. (it assigned Non-Color for both)

Any fix possible? It's a huge obstacle for my 2.79 files migration to 2.8x

Investigated a bit, it appears that 2.8x cannot assign 2 different Color Space for the same texture, while 2.79 could. For example in the blend attached i had two nodes with the same wood texture, but with different settings each one: - Linear for color of the material - Non Color for bump Now when opening with Blender 2.8x it does assign one of the two Color Spaces to each of the texture nodes, thus messing up my base color. (it assigned Non-Color for both) Any fix possible? It's a huge obstacle for my 2.79 files migration to 2.8x

Philipp Oeser commented

2020-01-23 14:04:26 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-23 14:04:26 +01:00

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

Philipp Oeser closed this issue

2020-01-23 14:04:26 +01:00

Philipp Oeser self-assigned this 2020-01-23 14:04:26 +01:00

Philipp Oeser commented

2020-01-23 14:04:26 +01:00

This has its roots in 7ad802cf3a

Cycles now uses the color space on the image datablock

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.

It has caused confusion numerous times #69244, #66985, #68047, #66979. but was not considered a bug.
So it is a know thing, all you can do I think is to have two separate image datablocks pointing to the same path on disk (just duplicate the Image Texture Node and make the image datablock single user), that way you can still set the Color Space separately.

Afraid we have to close this, thx for the report anyways!

This has its roots in 7ad802cf3a > Cycles now uses the color space on the image datablock > 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. It has caused confusion numerous times #69244, #66985, #68047, #66979. but was not considered a bug. So it is a know thing, all you can do I think is to have two separate image datablocks pointing to the same path on disk (just duplicate the Image Texture Node and make the image datablock single user), that way you can still set the Color Space separately. Afraid we have to close this, thx for the report anyways!

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

Wrong Texture Color Space assigned when opening 2.79 into 2.8x #73341