Skip to content
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

Are things after the updater-refactoring actually still compatible with fixed_update_timer? #94

Open
johannesugb opened this issue Mar 15, 2021 · 0 comments
Labels
bug Something isn't working question Further information is requested

Comments

@johannesugb
Copy link
Member

During the updater-refactoring, several framework-internal things have changed. Among others, imgui_manager's internal structure has changed and some code got moved from its render() to its update().

With the varying_update_timer, the order of update/render-invocations is well defined and has always a 1:1 ratio:

update();
render();
update();
render();
update();
render();

With fixed_update_timer, there is no fixed order or relation between the two. update() can be configured to run e.g. 60 times a second (i.e. fixed update rate of 60Hz), and render() is invoked as often as possible. E.g. like follows:

update();
render();
update();
update();
render();
update();
update();
render();
render();
render();
render();
update();
render();
@johannesugb johannesugb added bug Something isn't working question Further information is requested labels Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Development

No branches or pull requests

1 participant