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
- “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
Resolution Note:
This is by design in PhysX. All the collisions are reported one frame later than they physically occur.