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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment