Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.3.0a5
2018.2.2f1
Issue ID
1077869
Regression
Yes
Mesh Optimization is disabled on meshes with more than 30000 vertices
To reproduce:
1. Open the QA's attached project
2. Select the FBX model in the Assets folder and enable Mesh Optimization
3. Open the "Test" scene and take a look at the Stats in the Game window
Expected result: The mesh is noticeably optimized 899K -> 144K verts (749K verts change)
Actual result: The mesh is hardly optimized 899K -> 893K verts (6K verts change)
Reproduced with: 2017.3.0a5, 2017.4.11f1, 2018.1.9f1, 2018.2.7f1, 2018.3.0a11
Not reproduced with: 5.6.6f2, 2017.3.0a4
Regression started in 2017.3.0a5
Fixed in 2019.1.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment