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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment