Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a10
2018.4
2019.3
2019.3.14f1
2020.1
2020.2
Issue ID
1249347
Regression
Yes
Mesh/Mesh and Box/Mesh Collider collisions call wrong events when a very small Mesh is used
How to reproduce:
1. Open user's attached project
2. Open "SampleScene" scene
3. Enter Play Mode
4. Observe the Game view
Expected result: Mesh/Box and Mesh/Mesh Collider collisions are detected accurately, Mesh colors stay solid (OnTriggerEnter)
Actual result: Mesh/Box and Mesh/Mesh Collider collisions are not detected accurately, Mesh colors are flickering (Alternating between OnTriggerEnter and OnTriggerExit)
Reproducible with: 2018.3.0a10, 2018.4.40f1, 2019.3.16f1, 2020.1.0b13, 2020.2.0a15
Not reproducible with: 2017.4.40f1, 2018.3.0a4
Could not test with: 2018.3.0a5 - 2018.3.0a9 (Collisions are not detected at all, OnTriggerEnter event is not called)
Note:
- The issue is not reproducible with Box/Box Collider collisions
- The issue is not reproducible with built-in 3D objects
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note:
Penetration of colliders in this scene are quite small compared to the contact offset. It's recommended to scale the scene up.