You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calinou
changed the title
Area2D entered/exit signals more than 1 frame late
Area2D entered/exit signals more than 1 frame late with KinematicBody
Sep 26, 2021
Godot version
3.3.3
System information
Windows 10, Nvidia MX250, GLES3
Issue description
I know that for technical reasons, Area2D is supposed to be a frame late. However, in my testing, it appears to be 2 frames late
Steps to reproduce
Just run the provided reproduction project. Make sure you have the "Debug > Visible Collision Shapes" set to ON.
This project sets
Engine.iterations_per_second = 1
to make the visualization easier.Everything happens in _physics_process / the signals.
The tall area collision is the Area2D. The small one is a KinematicBody2D which a constant velocity that just does a move_and_slide.
When the
body_entered
andbody_exited
signals are received, the textbox is set to "Entered" or "Exited".Minimal reproduction project
BugArea2DDelay.zip
The text was updated successfully, but these errors were encountered: