Search Issue Tracker
By Design
Votes
0
Found in
2020.3.45f1
2021.3.20f1
2022.2.9f1
2023.1.0b6
2023.2.0a4
Issue ID
UUM-29135
Regression
No
Raycast prints false values when hitting a GameObject located at 0 on the Y-axis
Reproduction steps:
1. Open the attached “Predictkey.zip“ project
2. Open “Main Scene” scene
3. Enter Play mode and double-click in Game view
4. Observe “GetY” value in Console window
Expected result: “GetY” value (i.e. 0) is the same as Y-axis value of Plane GameObject Position (i.e. 0)
Actual result: “GetY” value (i.e. 0) is not the same as Y-axis value of Plane GameObject Position (i.e. -5.677426E-18)
Reproducible with: 2020.3.45f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b6, 2023.2.0a4
Reproduced on: macOS Monterey 12.6 (Intel), Windows 11 (by the reporter)
Note: Couldn’t test builds due to compilation errors in the user’s scripts required for reproduction
Comments (1)
-
DMark05
Mar 07, 2023 09:57
I agree that something like that would be tolerable, but the value I get is not within that range, but actually something like 9 or -5.
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
- [VFX Graph] ArcCone Direction computation is wrong in Base Mode
- [Android] [Galaxy Tab] A singular Pen touch logs a Pen touch event and a singular finger touch event when logged using "VisualElement.RegisterCallback" with "Pointer(Up/Down)Event"
- Crash on D3D12DescriptorCache::Deallocate or vkGetInstanceProcAddr when loading RenderDoc in a specific Scene
- [HDRP] Lit material preview is rendered incorrectly with a mask map
- The "LerpWhiteTo" missing function displays an error when the Shadows.hlsl shader is included in a Shader file
Resolution Note:
When working with floating point numbers a little bit of inaccuracy is expected. Getting ±5.677426E-18 instead of an absolute 0 from a complex calculation is well within the tolerated error (which is roughly ±1e-5).