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
- “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 (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