Search Issue Tracker
Won't Fix
Votes
1
Found in
6000.0.58f1
6000.2.1f1
6000.3.0a3
Issue ID
UUM-125344
Regression
No
Raycasts travel an incorrect distance when a non-normalized Direction vector is provided to RaycastCommand
How to reproduce:
1. Open attached project "IN-118474"
2. Open "ExampleScene"
3. Enter Play Mode
4. Observe Scene View
Expected result: Only the first RaycastCommand example hits a cube
Actual result: Every RaycastCommand example except for the last hits a cube
Reproducible with: 2023.1.0a3, 6000.0.58f2, 6000.2.1f1, 6000.3.0a3
Could not test with: 6000.0.59f1, 6000.0.61f1, 6000.2.10f1, 6000.3.0b8, 6000.4.0a3 (due to UUM-123124)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Workaround: normalizing the Direction value results in Raycasts traveling the expected length
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
Heya, I've submitted a documentation bug with regards to this issue. As direction is expected to be normalized.
Cheers,
AlexRvn