Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.4.X, 2019.1.X
Votes
15
Found in
2018.3.0a5
2018.3.7f1
2019.2.0a1
Issue ID
1136868
Regression
Yes
Raycasts hit the second layer of the Mesh Collider when the first layer is thin
How to reproduce:
1. Open the "SampleScene" Scene in the attached "v2018.3.7test.zip" Project
2. Select "TestMesh" and click on the helmet Collar on the side where the helmet screen is
3. Move the Camera to see where the Raycast hit
Expected Behavior: The Raycast hits helmet screen
Actual Behavior: The Raycast hits helmet collar which is behind one thin helmet screen
Reproducible with: 2018.3.0a5, 2018.3.9f1, 2019.1.0b7, 2019.2.0a8
Not reproducible with: 2018.3.0a4
Note: Could not check with 2017.4 because of C# Environment version 6.0 the MeshCollider.Raycast cannot take the "out" parameter.
Comments (1)
-
smithjohns402
Jun 10, 2024 05:34
You've encountered a bug in Unity where a Raycast is hitting the wrong object, hitting the "helmet collar" instead of the intended "helmet screen." This issue appears in versions 2018.3.0a5 through 2019.2.0a8 but not in version 2018.3.0a4. Report it to Unity's bug tracker for investigation.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Resolution Note (fix version 2019.2):
Fixed in 2019.2.0a11 backported to 2018.4.3f1