Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
Issue ID
1321303
Regression
No
MeshCollider fails to be added when added through Script in Player
Reproduction steps:
1. Open User Attached Project
2. Open Assets\Scenes\SampleScene
3. Press Play
4. Click on the Board on the Table
5. Exit Play
6. Build and Run the Game
7. Click on the Board on the Table
Expected result: The Board is destroyed when clicked in both the Player and the Editor
Actual result: The Board is not destroyed in the Player, because a MeshCollider fails to be added
Reproducible with: 2019.4.24f1, 2020.3.4f1, 2021.1.2f1, 2021.2.0a12
Could not test with: 2018.4 (Project breaks)
Notes: Not a WebGL issue, reproduces in Desktop Player as well
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note:
The CollisionMeshData creation fails because the Board on the Table is statically batched in Player. Excluding the GameObject from static batching and checking the "Read/Write" checkbox in the Model Import Settings > Model fixes the issue.