Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.2f1
Issue ID
1086087
Regression
No
Collision event delayed when using OnCollisionEnter2d
Steps to reproduce:
1. Open attached project
2. Open any issued scenes (01IssueCollision2d)
3. Click the Play button and wait for a while, it pauses automatically
4. Press the Step button several times
Expected result: As soon as "Sphere" GameObject collides with "Cube" GameObject Unity should register a collision.
Actual result: As collision happens one frame passes, and only then Unity registers a collision.
Note: If you set "Sphere" RigidBody Collision Detection setting to "Continuous", then Unity detects a collision on the first frame. This issue does not occur on OnTriggerEnter2D.
Reproduced in 2017.4.12f1, 2018.1.9f2, 2018.2.11f1, 2018.3.0b5, 2019.1.0a4
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #904813