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
- [GTK] Root graph gets dirty when viewing a dirty subgraph
- HDR Gradient Editor window closes when undoing changes in Sample Gradient node with Ctrl+Z
- Global Settings Asset “Open Project Settings > Graphics …” text overflows the button bounds when Inspector is narrow
- The “x” button to delete the input for the Source project is inconsistent and only appears when hovered and creating a new Template
- The “Next” button is not greyed out and still active when creating a new Template in the Hub and the Source project was selected but then something was searched with no options
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.