|
I extended StateSyncronizer so it can apply state from current peer instead of _last_received_state from host So i tried to do it this way, every step is on non host peer:
For some reason it's jumpy, any other approaches i can use? or maybe i'm doing something wrong in this one |
Answered by
albertok
Feb 12, 2025
Replies: 1 comment 2 replies
|
StateSyncronizer might not be the best fit if client side prediction is needed. The local processing will be out of sync with the server one and result in the jumpiness you're seeing. RollbackSynchronizer and its prediction features will likely work better. You'll just need to make the AI drive inputs. |
2 replies
Answer selected by
xand00
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
StateSyncronizer might not be the best fit if client side prediction is needed. The local processing will be out of sync with the server one and result in the jumpiness you're seeing.
RollbackSynchronizer and its prediction features will likely work better. You'll just need to make the AI drive inputs.