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
- [WebRequest] Missing CURLOPT_SEEKFUNCTION causes "curl error 26" on POST retry with reused connections
- Summary tab is selected but its content is not displayed when pressing Ctrl/Cmd+A in the Project Auditor window
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b16