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
- Shadow cascades and lights flicker when using Shadowmap Sampling
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
Resolution Note:
Heya, I've submitted a documentation bug with regards to this issue. As direction is expected to be normalized.
Cheers,
AlexRvn