Using multiplayer synchronizer on nodes propertie create a severe lag on steam (spacewar), around 1 to 4 seconds of lags, while there is no lag with local multiplayer simulated with hamachi , around less than a second of lag.
The lag doesn't append with RPC functions. only with data passed throught the node MultiplayerSynchronizer.
Lag using multiplayer synchronizer #29
The peer itself can't even know if its a synchronizer or a rpc - we just pass bytes around. I would expect to see RPCs affected as well.
After some test we found out that there is indeed no lag difference between RPC and multiplayer synchronizer, but the project suffer low lag without using steam (Enetmultiplayerpeer) in local (simulated with Hamachi) (no noticeable ping) and there is a lot more lag with steam (around 2 seconds).
Also there is no lag with Steam.sendP2PPacket, tested with voice (discord and the game had no difference).
Empty project doesn't have any lag difference between Steam and Enetmultiplayerpeer.
That's pretty weird. Is that empty project also using the Synchronizers? Though I guess that shouldn't matter at all, right?
we tested alll the same condition with the same gd script
Well, I do not have enough networking experience to unravel this one. Haha.
That makes sense then. Though I don't know I'd start messing around with outdated client files.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?