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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Add comment