Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.3.X
Votes
0
Found in
2020.2.0a5
2020.3
2020.3.21f1
2021.2
2022.1
Issue ID
1378322
Regression
No
Lighting is incorrect when Sprite Atlas uses secondary Texture Normal Maps in Linear Color Space
How to reproduce:
1. Open the user's attached project
2. Go to File -> Build Settings -> Player Settings
3. Under the "Other Settings" tab, in the Rendering section, set Color Space to Linear
4. Go to the Game view
5. Press the Play button and observe the lighting in the Game view
6. Repeat steps 2-3 and set Color Space to Gamma
7. Repeat steps 4-5
Expected result: the lighting doesn't change orientation when in Play mode, and the orientation of the lighting is the same in both Linear and Gamma Color Space
Actual result: the lighting changes to incorrect orientation in Linear Color Space when entering Play mode
Reproducible with: 2020.2.0a5, 2020.3.24f1, 2021.2.6f1, 2022.1.0b2
Not reproducible with: 2019.4.33f1, 2020.2.0a4
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.2):
Fix for this issue available on Unity 2022.2.0a4 and above
Resolution Note (fix version 2021.3):
Fix for this issue available on Unity 2021.3.4f1
Resolution Note (fix version 2020.3):
Fix for this issue will be available on Unity 2020.3.35f1 and above