Search Issue Tracker
By Design
Votes
0
Found in
2017.4.3f1
2018.2.6f1
Issue ID
1082109
Regression
Yes
Incorrect distance is returned when using EventSystem.RaycastAll
To reproduce:
1. Open project
2. Play 'TestScene'
3. Open console
4. Notice that raycast distance is 0.8 when the expected distance is 1.1
Reproduced: 2017.4.3f1, 2017.4.11f1, 2018.1.9f2, 2018.2.8f1, 2018.3.0b1
Not reproducible: 2017.3.2f1, 2017.4.2f2
BY DESIGN: the distance is calculated from the near clipping plane of the camera and not the camera object. This provides a more correct calculation based on the frustum of the camera. It is expected that the distance will be the distance to object from camera minus the distance for the near clipping plane.
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (2018.3.X):
the distance is calculated from the near clipping plane of the camera and not the camera object. This provides a more correct calculation based on the frustum of the camera. It is expected that the distance will be the distance to object from camera minus the distance for the near clipping plane