Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2018.1.0b7
Issue ID
1002396
Regression
No
CharacterController.ClosestPoint return value is not based on the collider's shape
Steps to reproduce:
1. Open user attached project
2. Load Assets/CharacterControllerScene.unity scene
3. Start Play mode
4. Translate the "Point" GameObject (color yellow)
5. Observe the new position of the "Result" GameObject does not follow along the surface of the capsule
6. Assign the "Capsule" GameObject's Capsule Collider to the "Collider" field of "Test Behaviour" and translate the "Point" GameObject
7. Notice that the red capsule follows along the surface right now
Expected behavior: CharacterController.ClosestPoint return points should be based on the collider's shape
Reproduced in: 2018.2.0a1, 2018.1.0b8, 2017.3.1p1, 2017.2.1p4, 2017.1.3p1
Fixed in: 2018.2.0a8, 2018.1.5f1, 2017.4.9f1
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