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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment