Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b3
Issue ID
877599
Regression
Yes
Enabling and Disabling Collider2D in the same frame while colliding with other colliders usually results in crash
To reproduce:
1. Open attached project "zombiesNew.zip"
2. Open and Play "Test" scene.
3. Unity will crash.
Reproducible: 5.6.0b4
Not reproducible: 5.4.1f1, 5.5.1f1, 5.6.05b, 2017.1.0a5
Workaround:
wait at least 1 frame before setting Collider2D to enabled, after it was disabled.
It also gives these errors:
Assertion failed on expression: 'contactState == Collision2D::ContactStay'
Assertion failed on expression: 'colliderItr != m_Collisions.end ()'
Assertion failed on expression: 'collision.m_ContactCount >= 0'
Fixed in: 5.6.05b (no errors, no crash)
Comments (2)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
M0rph3v5
Apr 02, 2017 11:55
In my case it's enabling and disabling 'simulated' in one frame btw.
M0rph3v5
Apr 02, 2017 11:51
This is still a problem! In Unity 5.6.0f3.