Float might cause desync over time. about godot-rollback-cs

[Carbone13]

Hey there, I suggest reading my last comment on your PR, it explains the situation well.
Also I'm working on a 100% deterministic physics. It still need more functionalities but once coupled with this repo, it could give good result.
About the second solution it can be something to implement, I mean if people don't want it they may just turn it off. The good point is that such logic is already implemented at the end of the sync manager, it's only comparing state and crying if they don't match and the send logic is not abstracted to the Network Adaptor, but that's not a big amount of work tbh 🙂

[FireBrandMint]

Okay, now i read it.

[FireBrandMint]

Oh that's right, now i'm reading it, you're talking about RemotEstateMismatch, thank you for you patience,

[Carbone13]

Yes exactly, now the logic need to be determined, if we discover a mismatch we need a strong logic to determine which one is right

[FireBrandMint]

Maybe just say "if it's the client then your state is wrong and you must resimulate" then?

[Carbone13]

Yes but as this is 100% p2p their is no clear server, but well most of the game will implement a "group/game master" guy, so it should not be a problem 🙂

[Carbone13]

As long as everyone end up in the same state, that's all we want 😅

[FireBrandMint]

Yeah, that sounds very good,

[FireBrandMint]

Just leaving this here, there's a problem with sending the world state: if the player changed input and the server sends them the state before the input gets rolled back without the input, that could cause a desync, the "strong logic" you talked about really matters.