-
-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(client_core): 🐛 Cap prediction to avoid head and controllers flying off #2635
Conversation
I would like some feedback on the min/max/step of the setting |
Ready |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I've honestly lost track of changing what where would cause a protocol break, so if you think that aspect's fine then it's good
Sometimes it's not so straightforward to identify and sometimes it could be controversial. In this case the changes are unilateral on the client and don't have any consequence on the server side. the setting is on the server side but with our mechanisms of session extrapolation it doesn't become a breaking change. |
…ng off (#2635) * fix(client_core): 🐛 Cap prediction to avoid head and controllers flying off * Add Max prediction setting
…ng off (#2635) * fix(client_core): 🐛 Cap prediction to avoid head and controllers flying off * Add Max prediction setting
@omfatimh38 Would you mind explaining to me what you're doing? |
No description provided.