Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.2.3f1
2023.1.0a26
Issue ID
UUM-24684
Regression
No
Mesh Collider error is thrown when transitioning from Scene to Scene in Play Mode
How to reproduce:
1. Open the user-attached “TestProject2” project
2. Open the “Empty” Scene
3. Enter Play Mode
4. Open the Console window
Expected result: Scenes transition without issues
Actual result: An error is thrown
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.3f1, 2023.1.0a26
Reproduced on: macOS Ventura 13.1 (Intel), macOS Darwin 12.5.1 (Intel), Windows 11
Notes:
- Reproducible in Builds
- Full Error message: “This Mesh Collider is attached to GameObject at path 'Scn12_jianmo_longmu06_01_LOD1/Roof_05_ruined_white.005' with Mesh 'Scn12_jianmo_longmu06_Roof_05_ruined_white.005' as child of a non-uniform scale hierarchy, in Scene 'SampleScene'. Change the hierarchy scale to uniform, or mark the mesh read/write in order to be usable with the given transform.”
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:
The error message is legit. Some scale configurations do require the read/write access because the physics engine would have to bake that scaling and for that it requires the geometry access.