Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2019.4
2019.4.9f1
2020.2
Issue ID
1274172
Regression
No
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)
Note:
- 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.
Latest issues
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Add comment