-
-
Notifications
You must be signed in to change notification settings - Fork 51
feat: PredictiveSynchronizer #533
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
base: main
Are you sure you want to change the base?
Conversation
| func _run_prediction_tick(tick: int) -> void: | ||
| for node in _nodes: | ||
| var is_fresh := _freshness_store.is_fresh(node, tick) | ||
| node._predict_tick(NetworkTime.ticktime, tick, is_fresh) |
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.
I'm considering using _rollback_tick() here too.
pros: consistency, code doesn't need to be touched to go from RBS to PredictiveSynchronizer
cons: might be confusing? + might not work well with mixed / nested setups
Thoughts?
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.
I'd much prefer it be called _rollback_tick also but it does leave the door wide open to unintended side effects.
Can I guard against a double call by checking is_simulated maybe?
TODO:
Closes #374