-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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 does not detect the other body. #76227
Comments
Here's a close-up of what happens: godot.windows.editor.dev.x86_64_L8yZzOpcZh.mp4The left sprite is moving faster, so once it collides with the right one, they stick together from now on. But for whatever reason |
Changing time_scale in my project is not a solution, I have to use a time_scale = 0.4 for detection to occur. |
Fixes happen based on availability of contributors and detection of the cause |
I am aware of that, which is why I say that I "hope". |
I think it is related with: #43743 |
I'm not sure if they are related. In this one the speed is low, it even collides with the other body and the area is being invaded in each frame but still, the detection is not registered. |
Godot version
v3.6.beta1.official [632a544]
System information
w10 64
Issue description
Problem:
The area2D of the "Player" node does not detect the body of the enemy.
To fix it make the collisionshape assigned to the area2D even bigger (currently it is 17x17) but this is not fixed, I mean you will have to make the area bigger even if the movement speeds of the nodes change.
I mean, the size of the area will be tied to the movement speeds of the nodes somehow.
So how is this understood? What size should I put in the area if it can become too big? I cannot be assigning different sizes to the area2D depending on the speed of the nodes.
Steps to reproduce
Just play the project and you'll see that when the "Enemy" node reaches the "Player" node then you don't get the body name written to the output.
Minimal reproduction project
testCuerposKinematic.zip
The text was updated successfully, but these errors were encountered: