Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
6
Found in
2019.4.23f1
2020.2.2f1
2021.1.0a7
Issue ID
1319133
Regression
Yes
Wintermute::Geometry::Verify errors are spammed when baking a Mesh with Mesh Compression set to Medium/High
How to reproduce:
1. Open the user's attached "BakingWithCompression.zip" project
2. Open the "SampleScene" Scene
3. Open the Lighting Tab (Window -> Rendering -> Lighting)
4. Press the "Generate Lighting" button in the Lighting Tab
Expected result: Baking is successful without any errors
Actual result: Baking time keeps increasing and "Wintermute::Geometry::Verify" errors are spammed in the Console log
Reproducible with: 2020.2.2f1, 2020.3.1f1, 2021.1.0f1, 2021.2.0a10
Not reproducible with: 2019.4.22f1, 2020.2.1f1
-
Thunderik
Jun 04, 2021 06:52
My team gets this in 2020.3.10f1
-
Dobrynia
Mar 30, 2021 07:09
Hello! a similar problem, only the error "Wintermute::Geometry::Verify" does not appear in the logs, and the process does not stop even after the remark is stopped. After that, you can close Unity only through the Windows Task Manager.
The same situation occurs when MESH COMPRESSION is disabled.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a15
Resolution Note (fix version 2021.1):
Fixed in 2021.1.5f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.6f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.25f1