Render discrepancies between packed and unpacked normal maps #52688

New Issue

Marco · 2017-09-09T10:34:03+02:00

Marco commented

2017-09-09 10:34:03 +02:00

System Information
Windows 10, Nvidia GT620

Blender Version
Broken: 2.75, 2.78c, 2.79rc2
Worked: (optional)

Short description of error
Normal maps render differently when they are packed in the scene from when they are unpacked

Exact steps for others to reproduce the error
packed_unpacked_nrm.blend

1.Unpack files
2.render
3.pack files
4.render on a different slot
5.compare differences

**System Information** Windows 10, Nvidia GT620 **Blender Version** Broken: 2.75, 2.78c, 2.79rc2 Worked: (optional) **Short description of error** Normal maps render differently when they are packed in the scene from when they are unpacked **Exact steps for others to reproduce the error** [packed_unpacked_nrm.blend](https://archive.blender.org/developer/F783900/packed_unpacked_nrm.blend) 1.Unpack files 2.render 3.pack files 4.render on a different slot 5.compare differences

Marco commented

2017-09-09 10:34:03 +02:00

Changed status to: 'Open'

Marco commented

2017-09-09 10:34:03 +02:00

Added subscriber: @Pie_Negro

Sergey Sharybin commented

2017-09-11 09:59:03 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2017-09-11 09:59:03 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2017-09-11 09:59:03 +02:00

Sergey Sharybin self-assigned this 2017-09-11 09:59:03 +02:00

Sergey Sharybin commented

2017-09-11 09:59:03 +02:00

The issue is caused by Cycles attempting to do color management on its side. This color management only works for non-packed images, for packed ones Cycles is fully relying on Blender side color management. This means, currently to make things render correct you need to both select No-color data in the Image Texture node AND select input colorspace of image itself as Non-color.

This is confusing, but not currently considered a bug: unifying color space management is a known TODO to happen in context of Cycles+Blender.

Thanks for the report, but closing it now.

The issue is caused by Cycles attempting to do color management on its side. This color management only works for non-packed images, for packed ones Cycles is fully relying on Blender side color management. This means, currently to make things render correct you need to both select No-color data in the Image Texture node AND select input colorspace of image itself as Non-color. This is confusing, but not currently considered a bug: unifying color space management is a known TODO to happen in context of Cycles+Blender. Thanks for the report, but closing it now.

Marco commented

2017-09-12 14:42:31 +02:00

Understood. Thank you so much, Sergei!

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

Render discrepancies between packed and unpacked normal maps #52688