Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.2f1
2023.1.0b21
2023.2.0a19
2023.3.0a3
6000.0.0b11
Issue ID
UUM-40466
Regression
No
“hitInfo.point” returned values are slightly off when using “Physics.Raycast”
How to reproduce:
1. Open the user’s attached “RaycastDrift.zip” project
2. In the Hierarchy window, select the “Tee1” GameObject
3. In the Inspector window, press the “Snap To Ground” button
4. Observe the position values in the “Transform” Component
Expected result: values don’t change
Actual result: values changes
Reproducible with: 1.0.0-exp.4 (2021.3.27f1), 1.1.3 (2022.3.2f1, 2023.1.0f1), 2.0.0-pre.3 (2023.2.0a19)
Reproduced on: macOS 13.2.1 (Intel)
Note: after repeating the 3rd step several times, the values don’t change
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:
After review we have elected not to address this issue at this time.