Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
6000.0.0b11
Issue ID
UUM-52688
Regression
No
Mesh Collider stops working and throws an error "doesn’t have Read/Write enabled" in the Development Console when in the Player
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Build And Run the project (File > Build And Run)
3. Observe the Player
Expected result: “Sphere” GameObject does not fall through the “__CM__Body” GameObject
Actual result: “Sphere” GameObject falls through the “__CM__Body” GameObject and there is an error in the Development Console
Reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproducible on: macOS Ventura 13.6 (M1 Max)
Not reproducible on: No other environment tested
Note:
- Mesh Collider works and there are no errors in the Development Console on 2021.3.31f1 when Cooking Option Everything is selected, but doesn’t work with other Cooking Options selected
- Full Development Console error “This Mesh Collider is attached to GameObject at path '__CM__Body' with Mesh '__CM__Body' in Scene 'MainScene' but doesn't have Read/Write enabled. Only colliders that have default cooking options, are not scaled non-uniformly, and their meshes are not marked dirty can leave this disabled.”
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
After review we have elected not to address this issue at this time.