Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.1.0b4
Issue ID
909260
Regression
No
Library and ProjectSettings cause Mesh vertex positions go wrong
The generated MeshCollider vertex positions are wrong in Repo project. But exporting the assets and import to new project or delete Library and ProjectSettings folder, the vertex positions are correct.
Step:
1. Open the repo scene in Repo project
2. Click on the rock object
3. Observe the MeshCollider
4. Optional. Remove the Library and ProjectSettings folder and repeat 1-3 again.
Expected Result:
The vertices of the MeshCollider are tightly stick with the rock object vertices.
Actual Result:
The vertices of the MeshCollider are moved outward by a certain value.
Please see attached image.
Note:
Removing Library together with ProjectSettings folder will fix this problem.
Regression is checked with opening the Repo project with the following versions:
Reproduced in : 2017.1.0b4, 2017.1.0b3, 2017.1.0b2, 2017.1.0b1, 5.6.0p4
(Cannot test with 5.5 since shader error)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Does not reproduce with 2019.3.0a3