Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Area2D entered/exit signals more than 1 frame late with KinematicBody #53099

Open
Tracked by #45334
MaxLap opened this issue Sep 26, 2021 · 0 comments
Open
Tracked by #45334

Area2D entered/exit signals more than 1 frame late with KinematicBody #53099

MaxLap opened this issue Sep 26, 2021 · 0 comments

Comments

@MaxLap
Copy link
Contributor

MaxLap commented 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

GodotArea2DDelay

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 and body_exited signals are received, the textbox is set to "Entered" or "Exited".

Minimal reproduction project

BugArea2DDelay.zip

@Calinou 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants