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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment