Cycles rendering, packed images render differently from unpacked #44643

New Issue

MasterOfCode1986 · 2015-05-09T15:23:01+02:00

MasterOfCode1986 commented

2015-05-09 15:23:01 +02:00

System Information
Windows 64 bit, NVIDIA 750M Blender Version: 2.74.5 eb81153
also confirmed on:
Linux 64-bit, CPU rendering, Blender Version: 2.74 b50c6e3

Blender Version
Broken: Blender Version: 2.74.5 eb81153 , also Blender Version: 2.74 b50c6e3

Short description of error
If textures get packed into the .blend file, they get distorted in a way that the uv seams become visible (although the textures itself do not have seams). This is especially noticable with normal maps.

Exact steps for others to reproduce the error
I have provided an example .blend as well as example textures. Download the .blend and the textures seperately. First, make sure, you have "automatically pack in .blend" (under File > External Data) unchecked. In the shader, connect the normal map (texture node, set to Non-Color-Data) with the glossy shader, using a normal map node. Now save your file and render or use render preview. The texture won't show seams.

Then check "automatically pack into .blend". Blender will tell you that it has packed one file - the normal map. Now render. You will see that the texture has gotten seams where the seams were set for unwrapping. You can use the linked color map to make this more visible. Please use an HDRI for lighting to view the error better.

Test .blend file: blender_bug_test.blend
Normal map:
Color map:

**System Information** Windows 64 bit, NVIDIA 750M Blender Version: 2.74.5 eb81153 also confirmed on: Linux 64-bit, CPU rendering, Blender Version: 2.74 b50c6e3 **Blender Version** Broken: Blender Version: 2.74.5 eb81153 , also Blender Version: 2.74 b50c6e3 **Short description of error** If textures get packed into the .blend file, they get distorted in a way that the uv seams become visible (although the textures itself do not have seams). This is especially noticable with normal maps. **Exact steps for others to reproduce the error** I have provided an example .blend as well as example textures. Download the .blend and the textures seperately. First, make sure, you have "automatically pack in .blend" (under File > External Data) unchecked. In the shader, connect the normal map (texture node, set to Non-Color-Data) with the glossy shader, using a normal map node. Now save your file and render or use render preview. The texture won't show seams. Then check "automatically pack into .blend". Blender will tell you that it has packed one file - the normal map. Now render. You will see that the texture has gotten seams where the seams were set for unwrapping. You can use the linked color map to make this more visible. Please use an HDRI for lighting to view the error better. Test .blend file: [blender_bug_test.blend](https://archive.blender.org/developer/F171863/blender_bug_test.blend) Normal map: ![Material_Normal_OpenGL.png](https://archive.blender.org/developer/F171864/Material_Normal_OpenGL.png) Color map: ![Material_Base_Color.png](https://archive.blender.org/developer/F171866/Material_Base_Color.png)

MasterOfCode1986 commented

2015-05-09 15:23:01 +02:00

Changed status to: 'Open'

MasterOfCode1986 commented

2015-05-09 15:23:01 +02:00

Added subscriber: @sharazam

blender-admin commented

2015-05-09 15:23:01 +02:00

#53902 was marked as duplicate of this issue

Sergey Sharybin was assigned by Bastien Montagne

2015-05-09 16:46:59 +02:00

Bastien Montagne commented

2015-05-09 16:46:59 +02:00

Added subscribers: @ThomasDinges, @MartijnBerger, @mont29

Brecht Van Lommel commented

2015-05-10 17:52:33 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2015-05-10 17:52:33 +02:00

You can set the color space to "Linear" instead of "sRGB" for the normal map image in the image editor to solve this.

Sergey Sharybin commented

2015-05-11 12:46:42 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2015-05-11 12:46:42 +02:00

Sergey Sharybin commented

2015-05-11 12:46:42 +02:00

Currently packed images are following color management rules from blender while non-packed images uses kinda simplified color management implemented in Cycles. This causes Color Space from the node to be ignored for packed images.

We could try making it so packed images are also aware of color management settings in the node, but that'd make color pipeline even more obscure. Proper way would be to implement same CM pipeline in Cycles, so it all becomes consistent in all areas of blender. This is already in our TODO list tho.

So thanks for the report, but improving this situation is already on the list, and meanwhile just use Image datablock CM settings if they're packed.

Currently packed images are following color management rules from blender while non-packed images uses kinda simplified color management implemented in Cycles. This causes Color Space from the node to be ignored for packed images. We could try making it so packed images are also aware of color management settings in the node, but that'd make color pipeline even more obscure. Proper way would be to implement same CM pipeline in Cycles, so it all becomes consistent in all areas of blender. This is already in our TODO list tho. So thanks for the report, but improving this situation is already on the list, and meanwhile just use Image datablock CM settings if they're packed.

Brecht Van Lommel commented

2018-01-26 08:21:32 +01:00

Added subscribers: @Renderbicks, @lichtwerk, @SteffenD

Michael Klein commented

2018-09-12 08:21:59 +02:00

Just a reminder: This bug still exist in the latest builds.

Michael Klein commented

2018-09-12 08:34:13 +02:00

I found the issue. In Data-Blocks the Color Space Settings of the non-color textures is set to sRGB. Setting them to Non-Color will fix the issue.

I found the issue. In Data-Blocks the Color Space Settings of the non-color textures is set to sRGB. Setting them to Non-Color will fix the issue. ![180912_Packed_Non-Color_Images_Issue.png](https://archive.blender.org/developer/F4673210/180912_Packed_Non-Color_Images_Issue.png)

Michael Klein commented

2018-09-12 08:40:06 +02:00

Here's the scene with the issue. The original non-packed scene renders fine. In the node-tree the textures "apple_roughness.png" and "apple_normal.png" are set to "non-color". But when packed the "Color Space Setting" in the "Data-Blocks" is set to sRGB. Setting to "Non-Color" will fix the issue.

Conclusion: The "Color Space Setting" must be set to the color space of the texture nodes.

RB180125_BugReport_2.79.0-9b32248.zip

Here's the scene with the issue. The original non-packed scene renders fine. In the node-tree the textures "apple_roughness.png" and "apple_normal.png" are set to "non-color". But when packed the "Color Space Setting" in the "Data-Blocks" is set to sRGB. Setting to "Non-Color" will fix the issue. Conclusion: The "Color Space Setting" must be set to the color space of the texture nodes. [RB180125_BugReport_2.79.0-9b32248.zip](https://archive.blender.org/developer/F4673232/RB180125_BugReport_2.79.0-9b32248.zip)

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

Cycles rendering, packed images render differently from unpacked #44643