Search Issue Tracker
Fixed in 5.1.4
Votes
0
Found in [Package]
2.0.0-preview.4
Issue ID
1284920
Regression
Yes
Polygon Collider 2D generates a Collider near a single vertex when a GameObject has a Sprite Shape Controller and 3 vertices
How to reproduce:
1. Open the user's attached "SpriteShapeCollisionBug" project
2. Open the "SampleScene" Scene
3. In Hierarchy select the "New SpriteShapeController (1)" GameObject
4. In the Inspector enable the Collider editor in the Polygon Collider 2D Component
Expected results: The Collider is the same shape as the GameObject
Actual results: The Collider is at the bottom left corner of the GameObject and is very small
Reproducible with: 2.0.0-preview.4 (2019.3.0a11), 3.0.14 (2019.4.13f1), 4.1.4 (2020.1.10f1), 5.0.2 (2020.2.0b8, 2021.1.0a3)
Not reproducible with: 1.0.14-preview.2 (2018.4.28f1, 2019.3.0a11)
Notes:
- Only happens if Sprite Shape Controller uses a Profile which is using a Sprite with Pixels Per Unit set to 7 or higher
- Moving any vertex to the opposite side will fix the issue and the Collider will be generated properly
- The issue is reversed in 2D Sprite Shape 4.1.0 and newer compared to 2D Sprite Shape 4.0.3 and older. If a Collider is generated correctly in 2D Sprite Shape 4.0.3 the same GameObject will have incorrectly generated Collider in 4.1.0 and newer (moving the vertex to the opposite side to fix the Collider in one version will break it in the other)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment