-
Notifications
You must be signed in to change notification settings - Fork 19
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
FPS limit in build selection #13
Comments
mweber15
added a commit
to mweber15/PathOfBuilding-SimpleGraphic
that referenced
this issue
Mar 15, 2021
As reported in issue PathOfBuildingCommunity#13, PoB tends to use significant CPU and GPU resources while in the foreground. This change exposes a foreground frame rate limit that can be configured via a CVar (vid_fgfps) that defaults to a 30 FPS limit and allows a 5-120 FPS range. A setting of 30 feels responsive and reduces the resource usage by a modest amount. CPU usage hovers around 4% on my 16-core system with this change, as opposed to 6% usage with the current build. Similarly, GPU usage hovers around 18-20% with the 30 FPS limit and around 25-28% with the current build. There may be a better place to situate the sleep that is introduced for this, but this seemed like a reasonable place for someone who is not very familiar with this code. I also removed the reference to tiff.lib in the Debug configuration since that is unused and not a vcpkg dependency.
I think this can be closed now as complete? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Please add an FPS limit to build selection, I use a global rtts one but if it's turned off this happens https://i.imgur.com/ANqKy0t.png . In the build viewer itself it drops to 60 so I assume it's limited there. Probably not a big deal but there we go.
The program while focused is also still too demanding over 10-15% cpu/gpu usage on a 2070super/3600. I assume the program core makes this unfixable but be aware that it's still a thing.
BR
The text was updated successfully, but these errors were encountered: