Search Issue Tracker
Won't Fix
Votes
0
Found in
4.3.2f1
Issue ID
585859
Regression
No
Collision issues when using 2D box colliders
Steps to reproduce :
- import the project attached
- press play
- move the character around and notice that the character will be stuck between two tiles
Explanation :
These are known as "Ghost vertices" and are common when you assume that collision vertices that are side-by-side shouldn't cause a collision when in-fact they can due to precision issues etc.
This is explained really well here as well as offering a few solutions:
http://www.iforce2d.net/b2dtut/ghost-vertices
The most notable of solutions is to use the edge-collider which provides a contiguous set of edges which don't suffer from this problem as Box2D understands that the vertices are part of a continuous surface.
Comments (3)
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
Gugaru
May 21, 2017 18:38
This should be fixed, notball 2d games are the solutions acceptable for. This may cause me to move to construct, which is a shame, because I love everything else about unity.
skirners1
Mar 25, 2016 10:53
Please fix :-D
Deep Azure
May 20, 2015 00:11
Why was this not fixed?