Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.1f1
Issue ID
835703
Regression
No
Setting "sharedMesh" in disabled "Mesh Collider", turns collider on even if component remains disabled
Steps to reproduce:
1. Open attached project
2. Open scene named "bug"
3. Start play mode
-Mesh Collider is disabled, yet RayCast still returns true(inspect console view).
Actual result: Setting "sharedMesh" in disabled "Mesh Collider", turns collider on even if component remains disabled.
Expected result: "Mesh Collider" should not be detected by ray cast when it's turned off.
Reproduced on: 5.5.0b5, 5.4.1f1, 5.3.6p5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment