Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.4f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-133628
Regression
No
PhysicsRaycaster ray length is incorrect when casting from rotated Camera
How to reproduce:
1. Open the attached “IN-131605“ project
2. Enter Play mode
3. In Game view, hover the mouse pointer over the “Cube1” GameObject on the right
4. Observe the console, note the 3 different outputs for “Cube1“
5. In Game view, hover the mouse pointer over the “Cube” GameObject on the left
6. Observe the console, note the amount of outputs for “Cube“
Actual result: The “Cube“ GameObject is only detected by Physics.Raycast
Expected result: The “Cube“ GameObject is detected by all active Raycasts
Reproducible with: 2023.1.0a1, 6000.0.66f1, 6000.3.6f1, 6000.4.0b5, 6000.5.0a5
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment