Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b8
Issue ID
639564
Regression
Yes
Disabled mesh collider registers to Raycasts
The scene contains a GameObject1 -> Gameobject2 -> Cube hiearchy. Gameobject2 is disabled (And thus, Cube is also disabled). Cube has a Mesh collider generated upon Start(). A Raycast is sent, and it hits the generated Mesh.
To reproduce:
1. Open attached project
2. Open TestRayV2 scene
3. Enter play mode
4. Click in the middle of the game window
Expected result: no collision
Actual result: Collision
Note: After clicking you'll notice that the hierarchy focuses on the disabled collider. That's the script, upon click it sends a raycast and selects the gameobject with which it colliders.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Add comment