Search Issue Tracker
By Design
Votes
1
Found in
2020.3.36f1
2021.3.5f1
2022.1.8f1
2022.2.0a18
2023.1.0a2
Issue ID
UUM-7714
Regression
No
Physics objects trip and/or jump when colliding with other colliders
How to reproduce:
1. Open the user-attached “Physics Tripping Bug.zip” project
2. Open the “SampleScene” Scene (Assets/Scenes)
3. Enter Play Mode
Expected result: Both cubes slide smoothly along the planes
Actual result: “Cube 2” starts jumping at random intervals on the Plane with multiple Colliders
Reproducible with: 2020.3.36f1, 2021.3.5f1, 2022.1.8f1, 2022.2.0a18, 2023.1.0a2
Note:
- Not reproducible on a new project
Comments (1)
-
atomicjoe
Jun 30, 2022 16:35
What do you mean by "Not reproducible on a new project" ?
I was having this issue in all my project and decided to make a repro project just for the bug report, so it definitively reproduces on new projects.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This common physics simulation issue is sometimes referred to as the “internal edge conflict”. The issue occurs because contacts where the tiles meet can be generated with normals that are not perpendicular to the shared plane.
Two most common solutions to this issue are using contact modification API to discard malformed contacts or to merge the mesh/box colliders into one single mesh.