Search Issue Tracker
Fixed
Fixed in 2021.3.53f1, 2022.3.61f1, 6000.0.48f1, 6000.1.0b14, 6000.2.0a8
Votes
0
Found in
2021.3.49f1
2022.3.59f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99022
Regression
No
Normal maps are rendered differently in Sprite Editor when compared to the Inspector Preview
How to reproduce:
1. Open the “NormalMap_Bug.zip“ project
2. Open the Window > 2D > Sprite Editor window
3. Select the “Assets/HappyHarvest/Art/Interior/Fireplace/Sprites/Fireplace_base/Sprite_Fireplace_normal.png“ normal map texture
4. Observe the Inspector preview and the Sprite Editor window
Expected result: The images are the same
Actual result: The images are different
Reproducible in: 2022.3.59f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Reprdouced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Sometimes, the icon for the “Sprite_Fireplace_normal.png“ texture at the top of the Inspector also shows up as the one in the Sprite Editor
- It seems that the blue color is transformed into alpha
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 6000.2.0a8):
Fix for this issue is available on Unity 6000.2.0a8 and above
Resolution Note (fix version 6000.1.0b14):
Fix for this issue is available on Unity 6000.1.0b14 and above
Resolution Note (fix version 6000.0.48f1):
Fix for this issue is available on Unity 6000.0.48f1 and above
Resolution Note (fix version 2022.3.61f1):
Fix for this issue is available on Unity 2022.3.61f1 and above
Resolution Note (fix version 2021.3.53f1):
Fix for this issue is available on Unity 2021.3.53f1 and above