Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b1
Issue ID
861587
Regression
No
Physics.CapsuleCastNonAlloc returns incorrect RaycastHit point and distance on hit
To reproduce:
1.Download and open attached project
2.Open "CapsuleCastTest" scene
3.Enter Play mode
4.Check the console for outputted log
Expected result: Log showing exact point in world space where and how far was the hit object.
Actual result: Log showing that object was hit at (0.0, 0.0, 0.0) with distance 0.
Reproduced with: 5.6.0b3, 5.6.0b1, 5.5.0p4, 5.4.4f1, 5.3.7p2
Notes: Move the Cube(9) object to coordinates X: 12.34, Y: 0.6 , Z: 15.33 in world space and then hit play. Notice that now log outputs correct information.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment