Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b5
Issue ID
1089473
Regression
No
Collision event delayed when using OnCollisionEnter, OnTriggerEnter
Steps to reproduce:
1. Open attached project
2. Open any issued scenes (02IssueCollision3d, 04IssueTrigger3d)
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: Setting "Sphere" Collision detection to "Continous" does not fix the issue.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
This is by design in PhysX. All the collisions are reported one frame later than they physically occur.