Search Issue Tracker
Fixed
Fixed in 6000.5.0a7
Votes
1
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
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Fixed an issue where the raycast computation did not account for camera orientation, and fixes ray lengths that were previously wrong.
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed an issue where the raycast computation did not account for camera orientation, and fixes ray lengths that were previously wrong.