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

Handle giving time input to egui correctly #226

Merged
merged 1 commit into from
Dec 11, 2023

Conversation

TheRawMeatball
Copy link
Contributor

The predicted_dt should be based on the target framerate and not depend on frame-to-frame fluctuations. Instead, we can pass total elapsed time instead to let egui handle things correctly.

The predicted_dt should be based on the target framerate and not depend on frame-to-frame fluctuations. Instead, we can pass total elapsed time instead to let egui handle things correctly.
@mvlabat
Copy link
Owner

mvlabat commented Dec 11, 2023

Hi, apologies for the delay, and thanks for the fix!

@mvlabat mvlabat merged commit e4461a4 into mvlabat:main Dec 11, 2023
19 checks passed
Schmarni-Dev pushed a commit to Schmarni-Dev/bevy_egui that referenced this pull request Dec 23, 2023
The predicted_dt should be based on the target framerate and not depend on frame-to-frame fluctuations. Instead, we can pass total elapsed time instead to let egui handle things correctly.
Schmarni-Dev pushed a commit to Schmarni-Dev/bevy_egui that referenced this pull request Dec 23, 2023
The predicted_dt should be based on the target framerate and not depend on frame-to-frame fluctuations. Instead, we can pass total elapsed time instead to let egui handle things correctly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants