Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.2.X, 2020.3.X, 2021.1.X
Votes
2
Found in
2020.2.0a7
2020.2.1f1
2021.1
Issue ID
1302233
Regression
Yes
Some Meshes have zero Vertices after upgrading/downgrading the project
Reproduction steps:
1. Open attached "case_1302233.zip" and Scenes/office scene
2. In the Hierarchy window, select Test/appartment layout/floor_wood
3. Observe the Scene view and Inspector
Expected result: Mesh is rendered
Actual result: Mesh is not rendered
Reproducible with: 2020.2.0a7, 2020.2.2f1, 2021.2.0b2
Not reproducible with: 2018.4.30f1, 2019.4.18f1, 2020.2.0a5
Notes: Issue is not reproducible when Mesh is newly imported to the Project
-
lmartellmc
Apr 09, 2021 23:12
Can't vote, but please fold this fix into 2020.3 LTS as it's stopping us from doing a critical upgrade!
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
- Shadows flickering when a Mesh's Cast Shadows are set to Shadows Only and Camera is moving with Spotlight
- AudioMixer exposed parameters cause assertions when hidden and prevent the drop-down from functioning
- Package Manager/My Assets: 401 Response code trying to download a paid asset store package
- TrailRenderer.SetPosition will log a Index out of bounds error when index is in bounds of the positionCount property
- [URP] Graphics.DrawMeshInstancedIndirect rendering correctly after clicking an another application/refreshing Assets
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0b8
Resolution Note (fix version 2020.3):
Fixed in 2020.2.7f1
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.7f1