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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2019.2):
Fixed in 2019.2.0a11 backported to 2018.4.3f1