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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is by design in PhysX. All the collisions are reported one frame later than they physically occur.