Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.30f1
2021.2
2022.1
2022.2
Issue ID
1409554
Regression
No
Custom surface shaders using emissive Standard lighting does not match Unity Standard shader without the [Gamma] tag
Reproduction steps:
1. Download and open the attached "StandardEmissiveRequiresGammaTag.zip" project
2. Open the "main" scene
3. Observe the Game view
Expected result: "Custom Standard Simple" materials look identical to "Custom Standard Simple [Gamma]" materials
Actual result: "Custom Standard Simple" materials are brighter than the "Custom Standard Simple [Gamma]" materials
Reproducible with: 2019.4.36f1, 2020.3.31f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a7
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:
The provided surface shader is different than Standard.shader because it has [HDR] on the _EmissionColor property.
Adding [HDR] sets the color property to be in linear space by default unless the [Gamma] tag is added in which case it will then go back to being sRGB.