About P2P performance and about P2P in general

[arthuro555]

@Gruk

Is that a guess or something you noticed?

Nah this is something that obviously will lead to desynchronization, because the behavior of a key press depends on variables that are client specific, like TimeDelta, and high variability variables, like the current velocity of the object. Since frame rate differs and the network is always slow and irregular, meaning it will always arrive at different moments a bit later on every client.

@Gruk

The data loss setting is here to avoid desynchronization, I believe.

Data loss is to avoid data losses, not help with desynchronization. All that it does is, when turned in “no data loss mode”, when receiving an event twice in the same frame, the other will be queued for being handled next frame. In data loss, only the last event trigger is kept, which is useful when sending for example a position, where older ones doesn’t matter, only the current one does.

---

I think that take of mine is still pretty to the point:

[solved]Sync entity positions over P2P

That’s the host-client pattern The “host” client handles most of the game logic, and the clients are being shown the current state of the game held by the host. To be able to have multiple enemies, you can do something like this: Whenever the host creates a new enemy, you’ll want to generate a new UID (Unique IDentifier) for that entity. You can do it easily with the UUID extension. Ask all the instances to create that object and use an object variable to remember which ID belon…