Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.2.4f1
Issue ID
1089297
Regression
No
Mesh assets that have a serialization version of 6 don't import properly from Unity 2017.4 to 2018
Steps to reproduce:
1. Create a new project in 2017.4
2. Import user attached TestMeshSerializedVersion6.asset
3. Check the imported file in one of the reproduced versions
4. Observe the broken quad mesh
Expected result: Mesh assets that have a serialization version of 6 should import properly from Unity 2017.4 to 2018
Does not reprudce anymore in: 2019.1.0a13, 2019.1.0a8
Reproduced in: 2019.1.0a7, 2019.1.0a1, 2018.3.1f1, 2018.2.20f1, 2018.2.0b3
Fixed in: 2019.1.0a8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment