Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0b4
2020.1.0a1
Issue ID
1186858
Regression
Yes
[2D] CompositeCollider2D doesn't generate correct shape when Geometry Type set to Polygon
How to reproduce:
1. Open the attached 'TilemapCompositeColliderBug.zip' project
2. Select 'Composite' GameObject in the Hierarchy
3. Observe 'Composite' GameObject in the Scene View
Expected result: CompositeCollider2D is generated for all GameObject's children
Actual result: CompositeCollider2D is not generated for some of GameObject's children sides
Reproducible with: 2019.3.0b4, 2019.3.0b5, 2020.1.0a6
Not reproducible with: 2017.4.32f1, 2018.4.10f1, 2019.2.7f1, 2019.3.0b3
Note: not only a visual bug CompositeCollider2D functionality is also affected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment