Search Issue Tracker
By Design
Votes
0
Found in
5.3.5f1
Issue ID
806527
Regression
No
Raycasting to and from a Character Controller doesn't hit intended target
Steps to reproduce:
1. Open my attached project inside "case_806527 Raycastproblem" file.
2. Select "Test Broken - Camera too high" scene.
3. Press play button in toolbar.
--- There are two raycasts. One comes from "FPCamera" object and another from "Capsule" object which is always directed into "FPCamera" object.
4. Open console.
--- "Capsule" object Raycast should hit "FPSController" object (because "FPCamera" object is inside of "FPSController" object) and show it on console window but it doesn't.
5. Press play button again.
6. Select "Test Works - Camera lower" scene.
7. Press play button in toolbar.
--- "FPCamera" camera object in this scene is 0.05 lower in Y axis than in previous scene.
8. Open console.
--- "Capsule" object Raycast hits "FPController" object and now console shows this detection.
Reproduced in: 5.4.0b23, 5.3.5p3, 5.3.1f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment