Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
0
Found in
2021.3.1f1
Issue ID
1425289
Regression
No
CustomCollider2D does not update properly after call to SetCustomShape(s)
Steps to reproduce:
1. Unzip and load the attached project "CC2D.Zip".
2. Open the "SampleScene".
3. Ensure that "Gizmos" are turned on in the "Game" view and selec tthe "TestCollider2D GameObject so you can see the collider gizmo.
4. Press Play, the "Circle" GameObject will fall down.
Expected result: Falling collider stops on the highest box.
Actual result: Falling collider doesn't stop on the highest box but stops on the one below it.
Reproducible with: 2021.3.1f1, 2022.1.0b16, 2022.2.0a12
NOTE: CustomCollider2D was introduced in 2021.3. This issue has been there since the start.
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
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Infinite inertial tensor rotation values are not discarded (both AB and RB)
Resolution Note (fix version 2022.2):
https://forum.unity.com/threads/customcollider2d-setcustomshape.1276481
Fix for this issue will be available on Unity 2022.2.0a15 and above
Resolution Note (fix version 2022.1):
https://forum.unity.com/threads/customcollider2d-setcustomshape.1276481
Fix for this issue is available on Unity 2022.1.2f1 and above
Resolution Note (fix version 2021.3):
https://forum.unity.com/threads/customcollider2d-setcustomshape.1276481
Fix for this issue is available on Unity 2021.3.4f1 and above