Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2019.4
2019.4.16f1
2020.2
2021.1
2021.2
Issue ID
1318366
Regression
No
"This MeshCollider requires the mesh to be marked as readable" error does not give enough information to find GameObject
Reproduction steps:
1. Open attached project "MeshMessage.zip" and scene "SampleScene"
2. Build and Run Windows Development Build
3. In Build, click on the "XXXXX" button and observe Console Log
Expected result: Errors display full path to the GameObject in question or something similar that would help to identify the exact GameObject.
Actual result: "This MeshCollider (GameObject: 'mesh' Mesh:'mesh') requires the mesh to be marked as readable in order to be usable with the given transform"
Reproducible with: 2019.4.21f1, 2020.2.7f1, 2021.1.10b1, 2021.2.0a7
Could not test with: 2018.4.32f1 (errors when building)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a10
Resolution Note (fix version 2021.1):
Fixed in 2021.1.2f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.4f1