Search Issue Tracker
Fixed in 5.8.0
Votes
0
Found in [Package]
1.1.10-preview
Issue ID
1154804
Regression
No
[HDRP] Edges become pixelated on dark-colored GameObjects when SMAA is applied on the Post Processing Layer Component
How to reproduce:
1. Open the "scene" Scene in the attached "case_1154804.zip" Unity project (link in the edit below)
2. Select the "Cube" GameObject
3. In the Inspector tab, expand the GameObject Material and change its "Base Color + Opacity" to a darker value
4. Observe the edges of the "Cube" GameObject in the Game tab
Expected result: GameObjects retain anti-aliasing
Actual result: GameObject edges become pixelated past a certain brightness threshold
Reproducible with: 2018.4.1f1, 2019.1.4f1, 2019.2.0b4, 2019.3.0a2
Note: SMAA is discontinued in HDRP versions 5.3.1-preview and later. Package introduced in Unity 2018.1. Not reproducible on versions 2018.3.0a2 and earlier due to errors preventing rendering in Game view. Not reproducible on package versions 1.1.8 and earlier due to errors preventing rendering in Game view. Not reproducible on versions 2019.3.0a3 and 2019.3.0a4 due to SMAA being absent on available HDRP versions.
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 5.8.0):
The bug is fixed in HDRP versions 5.8.0 and later on Unity versions 2019.1.