Search Issue Tracker
Duplicate
Votes
0
Found in
2019.3.6f1
Issue ID
1229712
Regression
No
Mesh Collider Cooking Options does not reset to default without re-adding Mesh Collider component
How to reproduce:
1. Open the attached project "1229712 - 2019.3.6f1.zip"
2. Open the "Test" Scene
3. Uncheck one of the Cooking Options of GameObject's "Custom mesh - modified" Mesh Collider component
4. Check previously unchecked Cooking Option of GameObject's "Custom mesh - modified" Mesh Collider component
5. Build and Run the project
Expected result: in step 4 - Mesh Collider Cooking Options are set to "Everything" (same as default), hence, in step 5 the collision is working (without mesh read/write enabled (as per documentation))
Actual result: in step 4 - Mesh Collider Cooking Options are set to "Everything" (not same as default), hence, in step 5 the collision is not working (without mesh read/write enabled)
Reproducible with: 2019.3.6f1
Not reproducible with: 2020.2.0a4, 2020.1.0b3, 2019.3.7f1, 2019.3.5f1, 2018.4.19f1, 2017.4.37f1
Workaround: removing and re-adding Mesh Collider component solves the issue
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
- [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
This is a duplicate of issue #1215857