Search Issue Tracker
By Design
By Design in 2020.3.X
Votes
0
Found in
2020.3.45f1
Issue ID
UUM-27602
Regression
No
Convex mesh collider is rendered incorrectly when using default FBX import scaling
How to reproduce:
1. Download and open the attached project
2. Import the attached FBX file to the project
3. Select the FBX asset, add a mesh collider and set the "convex" checkbox to true
Expected outcome: The collider fits the whole model
Actual outcome: The collider does not rendered correctly or fill the whole model
Workaround: set the FBX import scaling to 100
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
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:
This behavior is expected. The size of the mesh is at the mesh collider's calculation boundary, which would not yield accurate result. A useful workaround could be to upscale in the import settings and then downscale the same amount in the game object transform.
Resolution Note (2020.3.X):
This behavior is expected. The size of the mesh is at the mesh collider's calculation boundary, which would not yield accurate result. A useful workaround could be to upscale in the import settings and then downscale the same amount in the game object transform.