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
- UI Toolkit Slider value defaults to min value when the initial value is set in the UXML file
- The Player hangs when unloading a scene using the UnloadUnusedAssets() method
- [iOS] Too many texture parameters error is thrown when running on devices that support the number of parameters
- [MacOS] Trying to pick a Colour from full-screen window breaks Colour Picker Tool functionality
- WebGL Player hangs on first frame when "Autoconnect Profiler" is enabled and large amount of Profiler data is buffered before the first frame
Resolution Note (fix version 2019.1):
Fixed in: 2019.3.0a7