Search Issue Tracker
Fixed
Fixed in 2022.2.13f1, 2023.1.0b10, 2023.2.0a8
Votes
0
Found in
2020.3.44f1
2021.3.18f1
2022.2.5f1
2023.1.0b2
2023.2.0a3
Issue ID
UUM-28561
Regression
No
Physics2D.OverlapPoint does not work when GO with the "CompositeCollider2D" component has overlapping children
Reproduction steps:
1. Open the attached “Test Project” project
2. Open “Scenes/2D” Scene
3. Enter Play mode
4. Press on “Failed → 2” GameObject in the Game view
Expected result: “Physics2D.OverlapPoint” prints in the console: “Failed collider detected at point (0.18, 2.11)”
Actual result: “Physics2D.OverlapPoint” prints in the console: “no collider detected at point (0.18, 2.11)”
Reproducible with: 2020.3.44f1, 2021.3.18f1, 2022.2.5f1, 2023.1.0b2, 2023.2.0a3
Reproducible on: Windows 10
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
- [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
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
Resolution Note (fix version 2023.2.0a8):
Fix for this issue will be available on Unity 2023.2.0a8 and above
Resolution Note (fix version 2023.1.0b10):
Fix for this issue is available on Unity 2023.1.0b10 and above
Note that in the fixed Unity version, users will need to regenerate the CompositeCollider2D geometry by changing any property on it, deactivating/activating or adding/removing a collider using it. This is required because the CompositeCollider2D, unlike other colliders, stores the previously generated geometry meaning that any changes to how that geometry is produced, doesn't immediately affect what it currently has stored.
This applies to any fixes/changes to the CompositeCollider2D and not simply this fix.
Resolution Note (fix version 2022.2.13f1):
Fix for this issue is available on Unity 2022.2.13f1 and above
Note that in the fixed Unity version, users will need to regenerate the CompositeCollider2D geometry by changing any property on it, deactivating/activating or adding/removing a collider using it. This is required because the CompositeCollider2D, unlike other colliders, stores the previously generated geometry meaning that any changes to how that geometry is produced, doesn't immediately affect what it currently has stored.
This applies to any fixes/changes to the CompositeCollider2D and not simply this fix.