Collision is broken when disabled after pausing

[Stovehead]

Tested versions

• Reproducible in v4.2.1.stable.official [b09f793] and 4.0.stable.official [92bee43].

System information

Godot v4.2.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; 31.0.101.4575) - 13th Gen Intel(R) Core(TM) i7-1360P (16 Threads)

Issue description

If a game is paused while 2 CollisionBoxes are overlapped, then unpaused, and one of them is disabled, the other one will fail to recognize this, and it will believe that it is colliding with the other CollisionBox as long as they both exist.

Steps to reproduce

Run the program. There are two timer nodes. When the first one, the one under the root Node2D node runs, it will briefly pause the game. When the other one runs, it will disable one of the Area2D's collision and print "disable". The other Area2D is continually printing get_overlapping_areas(). It will not ever change, even after the collision is disabled. If the pausing functionality is disabled, it works as expected.

Minimal reproduction project (MRP)

PauseBug2.zip

[Sauermann]

Related to #60577, which describes a similar problem in 3.x.

[AThousandShips]

Can you test with 4.3-dev2, might be fixed by:

• Clear monitoring in Area* when its space changes to invalid #81809

Sounds very similar to:

• Disabling process of PhysicsBody2D and containing Area2D on same frame will make area register body as entered forever #76219

[Stovehead]

I tried it in 4.3-dev2, and it has a different issue instead. After the pause, the Area2D fails to recognize the overlapping area, even if it is not disabled.

[AThousandShips]

So then the original issue is solved, the other needs to be evaluated if it is a bug or not

I'd say to close this an open a new report for that issue as it's separate and different 🙂

[Stovehead]

Good call.