Skip to main content
Blender

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • $\begingroup$ I've run a few quick tests by setting up two Image Texture nodes fed by the same image and passing through a Vector Subtract node. By varying each of the Image Texture Color Space settings this can be used to compare the different modes. Initial tests seem to indicate that 'Raw' and 'Non-color' are identical but each of the others produce different output. I can't find any up to date documentation but I'd be very interested to learn the differences between these modes. $\endgroup$ Commented Jul 24, 2019 at 6:10
  • $\begingroup$ You can find some informations in the (updated) 2.80 manual about Color Management $\endgroup$ Commented Jul 24, 2019 at 7:53
  • $\begingroup$ @RichSedman I just have noticed when using .exr environment texture it automatically uses Linear type color space, Raw has same as well as non color while sRGB is a lot lot darker and others are making colors appear a lot different or would be mostly black, Using Linear ACES has some cool effect on env, I don't know what maybe oversaturation it is hard to tell because env was whole 'gray' vibe, it is some old industrial hall. $\endgroup$ Commented Jul 26, 2019 at 19:24
  • $\begingroup$ It’s not “oversaturation”, but a broken transform. That ACES transform isn’t ACES, and needs to be removed. It’s confusing garbage at this point. The TL;DR is use the select box to inform the software how your buffer / file encoding is encoded. If it isn’t encoded as per the selection, don’t use it. $\endgroup$ Commented Jul 27, 2019 at 16:37