WIP: Decouple game and ui frame rates #100
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is some work in progress towards decoupling the frame rate of the ui and the game simulation, and also with the goal of getting rid of the monstrosity half-singleton with function-level statics that is the current
SpeedController
.It is still unfinished, single player mostly works but I haven't tested network or replays.
Still, I hope this can serve as a foundation to discuss and design what we want to achieve.
Some observations:
std::this_thread::yield()
, but that seems to generate still 100% CPU on linux.Thoughs?