You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 15, 2022. It is now read-only.
One core is always used 100% by the program. This needs to be fixed.
The reason is that it was running at an unbounded frame rate. Enabling vsync fixes the issue, but also adds a lot of input lag. This brings CPU utilization down from ~150% to ~30% on my laptop. It can and should be close to zero percent when the user is not interacting with the app, but I'm going to wait for Bevy's official GUI before I do anything like that.
Here are a couple of related issues in the Bevy repo:
I'm leaving this issue open as the CPU usage could still be regarded as extreme (considering it should be close to zero) to track progress towards solving these issues in Bevy.
The text was updated successfully, but these errors were encountered:
One core is always used 100% by the program. This needs to be fixed.
The reason is that it was running at an unbounded frame rate. Enabling vsync fixes the issue, but also adds a lot of input lag. This brings CPU utilization down from ~150% to ~30% on my laptop. It can and should be close to zero percent when the user is not interacting with the app, but I'm going to wait for Bevy's official GUI before I do anything like that.
Here are a couple of related issues in the Bevy repo:
I'm leaving this issue open as the CPU usage could still be regarded as extreme (considering it should be close to zero) to track progress towards solving these issues in Bevy.
The text was updated successfully, but these errors were encountered: