A strange problem with KinematicBody2D's colliding body.

[dbsGen]

I write a little demo to show this problem.
https://github.com/dbsGen/CollidingTest
In the demo, I make a mark at the colliding position, and some time the KinematicBody2D's colliding position is different with others.

[akien-mga]

Maybe related to #2097.

[reduz]

I don't understand this much.. but it seems related to tree processing order to me.. nothing out of the ordinary

[dbsGen]

The KinematicBody2D and Area2D using same CollisionShape. But some time they are not be detecteded at same time.

[akien-mga]

Is this still reproducible in the current master branch?

[MarianoGnu]

Kinematic body has a skin parameter, this means it's collision shape is a little bigger and not detected by other bodies. I had problems because of this to make a falling platform because i could'n detect collision with player. I had to test a movement on every frame to workaround this

[eon-s]

Still happens in 2.1.4 and master.

Project for 3:
CollidingTestv3.zip

Sounds pretty much similar to #11879.

[Anutrix]

Can you tell us how to understand the test project?
What do black crosses mean?
@dbsGen

[eon-s]

Setting sync to physics option on the animated Kinematic bodies seem to fix the problem on latest stable.

[tavurth]

In the videos attached we can see the latest state in Godot version:

Running on a:

In the first video we can see an occasional black cross, representing a mismatched collision with the sibling KinematicBodies.

Gif

Imgur
https://i.imgur.com/oIqLbkx.mp4

After enabling sync-to-physics on the bodies the black crosses disappear, representing the fact that each KB is now in sync with it's siblings.

Gif

Imgur
https://i.imgur.com/xYLGcSR.mp4

[tavurth]

Hope that's helpful, I'm glad this at least has a fix now

[tavurth]

@akien-mga I'm not sure of the status of this now, can this be marked as completed?

[madmiraal]

Closing as fixed.