Enabling physics stops movement of one object, not another

First, I have two test objects (Player_Test and Enemy_Test) I am working with and have added an event that, if the objects are not colliding, have them use a pathfinding move event to move toward each other. This bit works as intended.

When turning on the physics2.0 behavior for both objects (with the only modification setting gravity to 0) the first object behaves as expected, moving towards the second object. It properly collides with the second object as well.

For some reason, the second object no longer moves at all with the physics behavior enabled, though.

They are essentially the same object with different sprites, behaviors are copy-pasted and identical and all the same parameters besides the .png, and I cannot figure out why one is behaving differently to the other.

For additional context, simply removing physics behavior from the second object makes it move towards the first again, as expected - while the first is still moving with physics enabled. Of course, this removes the desired collision physics since the second no longer has physics enabled.

Removing the collision detection and keeping the Move action still results in Object 1 moving and Object 2 not - except it pushes the second off frame instead of stopping shortly after impact.

I have reversed event order/logic placement of Object 1 and 2, but Object 1 always moves and Object 2 does not.

Any help would be appreciated.

  • Screen attached of events.
  • Default settings for Pathfinding and Physics on the two objects, excepting setting gravity to 0.

If you’re not using gravity then Physics objects require the physics actions to move. They have the atom icons. Normal force actions as well as most behaviors don’t work with the physics behavior. It has to do with the way forces are applied. Not all behaviors are compatible with each other.

https://wiki.gdevelop.io/gdevelop5/behaviors/physics2/#movement

Thanks! I wonder why one object works and the other doesn’t when using the pathfinding move event, since they are identical otherwise.

I’ll stop using pathfinding and exclusively use physics.

I’ve seen this happen before. I don’t know the technical reason other than they use different methods.