Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
1
Found in
2021.2
2021.2.0b6
2022.1
Issue ID
1357902
Regression
Yes
Optimize Mesh Data setting can make UV data corrupted in the player
How to reproduce:
1. Open user attached project "TEST 2.zip"
2. In the menu bar, click on File>Build And Run
3. When the application launches, observe materials of the GameObjects around
Expected result: Materials of the GameObjects are rendered the same as in the Editor
Actual result: Materials of the GameObjects are rendered with the lightmap on it
Reproducible with: 2021.2.0b6, 2021.2.0b8, 2022.1.0a6
Not reproducible with: 2020.3.16f1, 2021.1.17f1
Can't reproduce with: 2019.4.30f1 - Can't build because of errors in the Console
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 2021.2):
Fixed in: 2021.2.0b16