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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Add comment