Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.1.0a7
Issue ID
1294670
Regression
No
[Encoding/compression] Lightmap compression artifacts when Build Target = Android, Lightmap Encoding = Low
As shown in attached android-lm-artifacts.png, regular lightmaps (i.e. not directional) show compression artifacts when Build Target = Android, Lightmap Encoding = Low.
Tested on Unity 2021.1.0a7.
Steps to reproduce:
1) Make sure to have Android support installed.
2) Open attached project.
3) Open SampleScene.
4) Observe that there is no lightmap artifacts.
5) Select Android as build target.
6) Observe that there's now lightmap artifacts.
Expected: No or barely visible compression artifacts.
Actual: Clearly visible compression artifacts.
Note that the behavior is slightly different depending on whether Color Space = Gamma or Linear. If Color Space is Gamma then Unity chooses the ETC1 format. If Color Space is Linear then ETC2 is chosen. However, regardless of Color Space, the same artifacts still show up which is arguably somewhat surprising given how Unity says it the two cases use different compression formats.
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
Add comment