Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2019.2.X
Votes
0
Found in
2019.1.3f1
2019.2.0b1
2019.3.0a1
Issue ID
1156794
Regression
Yes
Colliders are not merged when using CompositeCollider2D
Steps to reproduce:
1. Open a new Unity project
2. Make a new gameObject with CompositeCollider2D component
3. Give it 2 child objects, with BoxCollider2D with Used By Composite checked
4. Make sure that one child is at position (0,0,0) while other is at (1,0,0)
5. Select parent gameObject and inspect Scene view
Expected result: Colliders are merged
Actual result: Colliders are not merged (green line in between them)
Reproducible with: 2019.1.3f1, 2019.1.5f1, 2019.2.0b1, 2019.2.0b5, 2019.3.0a4
Not reproducible: 2018.4.1f1, 2019.1.2f1, 2019.2.0a14
Add comment
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
Resolution Note (fix version 2019.1):
Fixed in: 2019.3.0a7