Search Issue Tracker
Fixed
Votes
0
Found in
2017.4
2017.4.1f1
2018.4
2019.2
2019.3
Issue ID
1211371
Regression
No
Raycast fails to hit Collider when aimed from certain distances and angles
How to reproduce:
1. Open attached project "Case_1211371" and load SampleScene
2. Press Play
3. Click "A" and observe the Console
Expected result: a ray pointing at a plane will register hitting it from a large distance
Actual result: raycast fails to detect hitting it
Reproducible in: 2017.4.36f1, 2018.4.15f1, 2019.2.18f1, 2019.3.0a8
Not reproducible in: 2019.3.0a9, 2019.3.0f5, 2020.1.0a19
Notes: In the provided project, the ray is hitting the plane at an angle of 26.27355 from the collider's normal and with a distance of 1004.58. Also reproduces with a distance of 1005.58, but not with 1003.58 or 1006.58
Comments (1)
-
Vincenzo
Mar 22, 2020 09:15
We need a backport to 2018.4 LTS.
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 2019.3.0a8