Page MenuHome

Wrong colors with some float TIFF files
Closed, ArchivedPublic


System Information
Operating system: Windows 10 Pro 10.0.17134 Build 17134
Graphics card: Nvidia 660 GTX

Blender Version
Broken: 2.80 (sub 35), branch: blender2.8, commit date: 2018-11-30 00:46, hash: 4c31bed6b46, type: Release
Previous versions (2.79 and earlier) are broken too in similar ways.

Short description of error
Some float TIFF files get rendered in wrong colors in eevee or cycles. Even though the image looks correct in the image viewer, it will show wrong colors in the render. But i mainly tested normal maps, so the report will be about normal maps.

Here are some example outputs which compare the original float TIFF image with a version externally converted to integer. The image is applied as normal map, both versions of the normal map look the same in any external program or even the blender image viewer, but they render differently. Left uses the original image and right uses the converted image:

DescriptionExample output
Rendered in eevee
Rendered in cycles, but files are not packed into the blend file
Rendered in cycles, but files are packed into the blend file

I'm not sure yet, but it seems it doesn't happen with all float RGB TIFF images. I could only reproduce it with normal maps i have here. Some float RGB TIFF images for the base color didn't show any huge color differences in the output.

Exact steps for others to reproduce the error
Here is a blend file from which the above examples where created from. For some reason it makes a difference for cycles if the images are packed into the blend file, so you may unpack or repack the two textures to test. To reproduce the behaviour, just open the file in blender 2.8 and display the viewport as LookDev or Rendered.



Event Timeline

Brecht Van Lommel (brecht) closed this task as Archived.
Brecht Van Lommel (brecht) claimed this task.

It's a color space issue, Cycles and EEVEE use different settings and this will be fixed as part of T54659: Move and share Eevee / Cycles render settings.

The solution for now is to set the image to Non-Color Data both in the node and in the image editor.

David Vogel (Dadido3) added a comment.EditedDec 3 2018, 6:08 PM

This issue has nothing to do with differences between cycles or eevee. It's not an issue between the two render engines, but rather an issue that sort of affects both equally.

I noticed it before eevee was a thing. In older blender versions normal maps were shown incorrect in the preview like i've shown above, but they rendered correctly in cycles so i didn't care much. But now with eevee they render incorrect, too. And by trying to narrow down the problem i also noticed that the same problem happens in cycles, but only if the images are packed into the blend file.

It has something to do with the way TIFF images are handled, and it happens especially with normal map images. Perhaps those images contain a color profile or some other information that is wrongly or not used by blender. I don't know much about how blender handles the data, but i'm sure it's not an issue that only lies between cycles or eevee.

Alone the fact that cycles produces different results if images are packed into the blend file or not, shows that there is something wrong in how blender handles the float TIFF image data. I hope this issue gets reopened.

Edit: Ok, declaring that image as Non-Color Data in the image editor too seems to fix it. So as long as it gets fixed with the other bug, it doesn't need to be reopened.

Thanks for the solution.

When images are packed, Cycles loads them through Blender like EEVEE. So it's the same issue.

Sergey (koloved) triaged this task as Confirmed, Low priority.Mar 14 2019, 2:02 AM

this bug still exists, why is it closed? =(

Sergey (koloved) reopened this task as Open.Mar 14 2019, 2:03 AM

Because T54659 already exits to handle this.