Search Issue Tracker
Fixed
Fixed in 2020.3.38f1, 2021.3.9f1, 2022.1.12f1, 2022.2.0b4, 2023.1.0a1
Votes
24
Found in
2019.4.40f1
2020.3.35f1
2021.3.5f1
2022.1.5f1
2022.2.0a17
2023.1.0a1
Issue ID
UUM-6271
Regression
No
Physics overlap queries are not consistent when used against convex Mesh Colliders with a very small scale
Reproduction steps:
1. Open the attached 'ComputePenetrationTesting' project
2. Open the 'SampleScene'
3. Enter the Play mode
4. Observe the Console, note that collision is detected
5. While in Play mode, in the Scene View move the movingTestObject slightly inside the staticTestObject
6. Observe the Console
Expected result: the collision is always detected when the movingTestObject overlaps the staticTestObject
Actual result: the collision is not always detected when objects overlap
Reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2
Comments (1)
-
Santa
Aug 25, 2022 14:09
This bug is NOT totally fixed.
It was combined with other bug and second part of it is still a bug.
I've submitted it here:
'New Incident created: IN-14809 - Physics overlap with convex Mesh __STILL__ don't work'
unity3d.atlassian.net/servicedesk/customer/portal/2/IN-14809Previously it was here:
https://fogbugz.unity3d.com/default.asp?1385191_r7rsvj2flo90mb4fPlease keep it open!
24 votes is difficult to collect again.
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Resolution Note (fix version 2022.2.0b4):
Fixed in 2022.2.0b4
Resolution Note (fix version 2022.1.12f1):
Fixed in 2022.1.13f1
Resolution Note (fix version 2020.3.38f1):
Fixed in 2020.3.38f1