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
- 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