Search Issue Tracker
Won't Fix
Votes
0
Found in
3.5.0f5
Issue ID
443969
Regression
No
Collisions are detected one frame later than they occur.
To reproduce
1. Open the scene "TriggerTest".
2. Press play and pause the game immediately.
4. Press the advance frame button until the frame where the sphere is intersecting the cube. Notice OnTriggerEnter has not been called.
5. Press the advance frame again and notice it now says "enter" in the console.
6. Continue advancing the frame until the sphere exits the cube. Notice OnTriggerExit has not been called.
7. Advance the frame again and notice it now says "exit" even though the sphere stopped intersecting the cube on the previous frame.
Expected result: 'OnTriggerEnter' is calles as soon as the sphere enters the cube
Actual result: 'OnTriggerEnter' is called on frame later than the collision occurs.
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
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
- [Editor] Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
Add comment