Search Issue Tracker
Fixed in 5.6.0
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.
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset