Search Issue Tracker
Fixed in 2021.1
Fix In Review for 2020.2
Fixed in 2019.4, 2020.1
A part of the PolygonCollider2D's shape is getting removed when the PolygonCollider2D's points are too close
How to reproduce:
1. Open the user's attached "PolygonCollider2D_RemovedShapes_2019.4.9.zip" project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. Press the "Pause" button after entering Play Mode
5. Press the "Step" button until the balls touch the PolygonCollider2D shapes (See "1274172_repro.mp4")
Expected result: Both ball GameObjects hit the PolygonCollider2D shape without going through
Actual result: The left ball GameObject goes through the PolygonCollider2D shape's top vertex (Part of the PolygonCollider2D shape is getting removed)
Reproducible with: 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
Could not test with: 2018.4.27f1 (The PolygonCollider2D shape is not visible when downgrading the project)
- The issue is not reproducible if the PolygonCollider2D Component's Offset property is slightly increased (Now it's 0 on both X and Y axis)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Can't select sRGB color format for Render Texture on HDRP project
- Built player takes multiple seconds to shut down
- Wireframe flicker and quad shaped artifacts on terrain trees using Mac Metal.
- Spamming error: `GLSL: Shader cannot be patched for instancing.` When enabling terrain Draw Instanced option in desktop OpenGL.
- [Mono, Debugger] VS 2019 debugger detaches when the Trace.TraceInformation is called with a specific string