Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.3.0b1
2017.3.0f3
Issue ID
994586
Regression
Yes
HDR camera introduces pixel artifacts in a light-mapped scene
How to reproduce:
1. Load tester-submitted project
2. Open "Title Screen.unity" scene
3. Rotate the camera and stop when the white spot remains on the screen
Expected result: No white spots and black pixels appear
Actual result: When positioning camera in very peculiar angles white spots with black pixels appear
Notes:
- Main camera must have HDR allowed
- The scene must contain baked lighting (it doesn't matter whether the lightmaps are directional or non-directional)
- White spots are produced by Post-Processing stack plugin bloom effect (white spot is produced due to bloom effect being unable to determine the luminosity of the black pixel in the center of the spot)
- Black pixel persists through Unity scene grid (Editor view - possibly incorrect Z-Buffer pixel generated)
- Lightmap quality doesn't seem to affect artifacts
- Reproduces with both Directional and Non-Directional light maps
- Enlighten light mapper reproduces the issue too, but it's harder catch it
Reproducible with - 2017.3.0b1, 2017.3.1p1, 2018.1.0b8, 2018.2.0a1
Not reproducible with - 5.6.5p2, 2017.1.3p1, 2017.2.1p4, 2017.3.0a7
Comments (1)
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
aftokinito
May 16, 2018 10:30
Still present to this day and REALLY annoying.