Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2018.4
2019.4
2020.3
2020.3.1f1
2021.1
2021.2
Issue ID
1339454
Regression
No
Character Controller Closest Point returns incorrect position when the Center is offsetted
Reproduction steps:
1. Open the attached "CharacterControllerClosestPoint.zip" project
2. Open the "SampleScene" Scene
3. In the Hierarchy, select the "Capsules" GameObject
4. In the Scene View, compare the drawn Gizmos (opaque and wireframe spheres) around the Capsule Collider (Capsule_Col) and the Character Controller (Capsule_CC)
Expected result: Closest points (wireframe spheres) from locations (opaque spheres) are correct for both Colliders (Capsule Collider and Character Controller)
Actual result: Capsule Collider (Capsule_Col) closest points (wireframe spheres) are correct but the Character Controller (Capsule_CC) closest points (wireframe spheres) are visibly incorrect
Reproducible with: 2018.4.35f1, 2019.4.28f1, 2020.3.11f1, 2021.1.10f1, 2021.2.0a19
Note: Even when the Character Controller (Capsule_CC) Center is zeroed the closest point results slightly differ from a Capsule Collider (Capsule_Col) of the same height and radius
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2022.1):
Fixed in: 2021.2.0a21