owner_predicted example allow client cheating ?

Hello ! I'm new to bevy, and first time using a networking crate with it. I was trying out the examples, but stumbled on weird behavior, which might be a problem with more than just with the example ? This is done with the example untouched.

I have two screens, a 240hz and a secondary 60hz, I guess It's because the example use Update and not FixedUpdate, but I didn't manage to fix it.

When I have both of the server and client window on the SAME screen, it works well. But when I have one on the second slower screen, movement becomes weird:

if the server is on the slower screen, the client box speed will be multiplied, like it will, for both side (but jittering visually on client) go a lot faster than the normal speed. The server box is slower than normal, so the inverse here.
if the client is on the slower screen the client box is move reallyyyy slow. Client side, it's constantly roll backing a lot. The server box is moving normally, it seems.

Video recording showing both behavior: https://streamable.com/pmuxfr

Also, I was wondering, nothing to do with that i guess, but why is client -> server movement latency is really fast, but server to client much slower where the client will see some jitter ? (we can see it in the video at the start when both on same screen)

thanks !

Bendzae / bevy_replicon_snap

owner_predicted example allow client cheating ? #14