Search Issue Tracker
By Design
Votes
0
Found in
2019.3.0a9
2020.1.0a15
Issue ID
1204810
Regression
Yes
FBX without convex collider throws PhysX convex meshes error after it's loaded from Asset Bundle
How to reproduce:
1. Open the "ConvexErrors.zip" project
2. Open the "SampleScene" scene
3. Assets > Build AssetBundles
4. Enter Play Mode
5. Press "AB Instantiation"
Actual result: "Failed to create Convex Mesh from source mesh "CA_rock_01"" error gets thrown.
Expected result: No errors are thrown.
Reproducible with: 2020.1.0a17, 2019.3.0f3, 2019.3.0a9, 2017.4.35f1.
Regression introduced in: 2019.3.0a9.
Not reproducible with: 2019.3.0a8, 2019.2.16f1, 2018.4.14f1.
Notes:
- In 2020.1.0a17 warning is thrown instead of 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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Meshes that have complex features resulting in hulls over 255 vertices need to be simplified before used. With Unity 2019.3, we would still allow using the partial mesh that was cooked by Quickhull, but that convex will obviously not be accurate. Simplifying the input mesh in any DCC tool is recommended.
The errors are caused without instantiating the object because collision data is pre-baked for all the meshes in the bundle once it's loaded.