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.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [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
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?