Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
0
Found in
2018.3.4f1
Issue ID
1123489
Regression
No
Unity editor crashes on WorldContactFilter2D::ShouldCollide when trying to destroy tile player is colliding with
How to reproduce:
1. Open attached "repro_1123489" project
2. Open scene "Sector Omega.unity"
3. While you entering the Game mode hold "D" key on your keyboard.
4. Exit the Game mode and Repeat step three.
- observe the crash (usually takes 3 - 5 tries to reproduce)
Reproducible with: 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Was not able to test: 2017.4.x
Workaround:
Attach a composite collider to the tilemap gameObject and have the tilemap collider attached to the composite collider
Fix verified in: 2018.3.8f1, 2019.1.0b5, 2019.2.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Add comment