Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.3.0b4
Issue ID
1191583
Regression
No
Custom asset's mesh is distorted and has too many vertices when using Mesh.CombineMesh() to combine submeshes
1. Open the attached '2019.3.0b4.zip' project and load 'New Scene' scene
2. Enter Play mode
3. In the Hierarchy window select 'NewMesh'
4. In the Inspector window double click on Mesh's field value 'NewMesh'
5. Observe the Inspector window
Expected result: new mesh has 32995 vertices and is not distorted
Actual result: new mesh has 180631 vertices and is distorted
Reproducible with: 2017.4.33f1, 2018.4.11f1, 2019.1.0a1, 2019.1.0a2
Not reproducible with: 2019.1.0a3, 2019.1.14f1, 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Reproduced only with the provided custom asset
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- XR Ray Interactor Cone Cast doesn't match Gizmo in Scene View when Cone Cast Angle is higher than 10 degrees
- [XR] LODs switch between high and low poly when Objects are near the center of the screen and switch when near the periphery vision
- Crash when trying to force Shader to interpret 1/30 as a floating point operation
- Terrain is flickering when adjusting "Compatibility Mode" and "Use Rendering Layers" Settings
- Isometric tiles are flickering and overlapping each other when entering Play Mode with Tilemap Renderer mode set to "Chunk"
Add comment