Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
0
Found in
2017.1.0b4
2017.3.0f2
Issue ID
977687
Regression
Yes
Changing the parent of an object with a collider component to a Composite Collider 2D object causes an Assertion failed error
Steps to reproduce:
1. Open attached “ColliderParent.zip” Unity project
2. Open scene “Example”
3. Enter Play mode
4. Click the red button in Game window
Expected results:
No error appears
Actual results:
Assertion failed error appears after object parent was changed to an object with CompositeCollider2D
Reproduced in: 2018.1.0a7, 2017.3.0f2,, 2017.2.1f1,, 2017.1.2p4, 2017.1.0b4, 5.6.4p4, 5.6.2f1, 5.6.1f1, 5.6.0p3
Didn’t reproduce in: 2017.1.0b3, 5.6.0p2, 5.6.0f1, 5.6.0a1
Regression introduced in: 2017.1.0b4, 5.6.0p3
Error:
Assertion failed: Assertion failed on expression: 'm_CompositeCollider == NULL'
UnityEngine.EventSystems.EventSystem:Update()
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Add comment