Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0f3
Issue ID
906431
Regression
No
Object bumps into a corner of a PolygonCollider2D if there is a diagonal line collider
To reproduce:
1. Open attached Unity project "PolygonCollider2D Diagonal Test.zip"
1. Play "test" scene.
2. Hold horizontal input axis keys to move the box
3. Move to the corner of the letter "O"
Expected result: https://gfycat.com/VeneratedAdolescentGrayling
Actual result: https://gfycat.com/GlamorousEcstaticJumpingbean
Reproduced on: 5.5.0f3, 5.6.0f3, 2017.1.0b1, 5.6.0p3
Note: the bug only occurs if the player is moving very slowly at the time of contact with the corner of the letter "O" (increasing the timescale variable
in "PlayerController" script will eliminate the bug)
--
Multiple polygons whether they be separate colliders or the multiple convex polygons that PolygonCollider2D produces do not create a continuous surface and the physics system handles contacts with each polygon separately. This can lead to "catching" corners. Increasing the contact offset can help with this sometimes but not always. Only the EdgeCollider2D or the CompositeCollider2D (using Outline geometry) can produce continuous surfaces.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment