Weird reaction in body_entered signal

:information_source: Attention Topic was automatically imported from the old Question2Answer platform.
:bust_in_silhouette: Asked By gfnekro

Sorry if this question is too noobie, but I’ve been scratching my head for hours and can not find a solution.
I have a player that shoots bullets. The bullets are RigidBody2D and are shooted with the left button of the mouse. The fire rate is 0.2.
I have some trees that are RigidBody2D.
I use the “body_entered(body)” signal in the bullet to watch for collisions. When I detect one, I play an explosion and delete the bullet (“queue_free”).
I use the “body_entered(body)” signal in the trees to see what hit it. If it’s a bullet, it takes damage. If the damage is enough, it’s eliminated (“queue_free”).
The player need three hits to kill the tree.
If the player is very near the tree, everything works as expected: the three bullets detect the collsion, the three explosion animations are played and the bullets dissapear. The tree detects the hits, it’s life goes down and with the third hit, dies and dissappears.
But if the player is far from the trees, things go wrong. The bullets detect the tree, the explosions are played and the bullet dissapear, but the tree detects far less collisions that bullets shot. The tree detection rate goes down with the distance. If the player is on the opposite corner of the tree, the tree detects only one bullet from 8 or 9 shooted.
I have “Contact Monitor” ON and “Contacts Reported” on 100 for the bullets and the trees.
Any ideas?
it’s frame rate related? Shouldn’t I be using signals?

I have a video showing the problem. If someone can tell me how to share it (if It’s allowed and possible), please tell me.