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