Search Issue Tracker
Fixed in 2019.2
Fixed in 2018.4, 2019.1
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.
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
- Aspect Ratio Fitter's "Fit In Parent" Aspect Mode causes scene to update indefinitely
- DragAndDrop state is not cleanup after a drag
- [SRP] Shadow culling ignores Lens Shift setting on Camera
- Output Texture's RGB values are slightly different from the source PNG image when using Texture2D.EncodeToPNG function
- [Android] Accessing any class/instance member with an "AggressiveInlining" attribute will cause a crash
Resolution Note (fix version 2019.2):
Fixed in 2019.2.0a11 backported to 2018.4.3f1