Search Issue Tracker
Third Party Issue
Third Party Issue in 2022.2.X
Votes
2
Found in
2020.3.46f1
2021.3.21f1
2022.2.13f1
Issue ID
UUM-32283
Regression
No
GameObject ignores collisions when more than 99 Capsule Colliders are present in a single collision spot
Reproduction steps:
1. Open the attached project “ColliderProject”
2. Open the “Assets/TestPhysicsBug.unity” scene
3. Enter the Play Mode
4. In the Hierarchy Window, select the “TestController” GameObject
5. In the Inspector Window, click the “Start test” button in the attached Test Controller Script Component
6. Observe the movement of the “TestController” GameObject in the Scene View
Expected result: The TestController GameObject moves for a bit and stops (i.e does not fall)
Actual result: The TestController GameObject moves a bit and falls ignoring the “Terrain” GameObject Mest Collider
Reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.0a18, 2022.2.13f1
Not Reproducible with: 2023.1.0a1, 2023.1.0b10, 2023.2.0a8
Reproducible on: Intel macOS 13.2.1
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
This issue is a limitation in PhysX. Unfortunately, it happens deep in the SDK and it's uneasy to provide a helpful message indicating that this has actually happened.
https://github.com/NVIDIAGameWorks/PhysX/blob/a2c0428acab643e60618c681b501e86f7fd558cc/physx/source/physxcharacterkinematic/src/CctCharacterControllerCallbacks.cpp#L955
Resolution Note (2022.2.X):
This issue is a limitation in PhysX. Unfortunately, it happens deep in the SDK and it's uneasy to provide a helpful message indicating that this has actually happened.
https://github.com/NVIDIAGameWorks/PhysX/blob/a2c0428acab643e60618c681b501e86f7fd558cc/physx/source/physxcharacterkinematic/src/CctCharacterControllerCallbacks.cpp#L955