Real-time process CPU usage, add Windows Game Mode controls, dark title bar and improved logger#84
Real-time process CPU usage, add Windows Game Mode controls, dark title bar and improved logger#84RegentScar wants to merge 7 commits intoSimonvBez:mainfrom
Conversation
Replaces average CPU usage with real-time measurement in the process list. Pause process CPU usage updates, core usage updates and sorting updates when the window is hidden (in System-Tray).
- Add a CheckBox to the processes window for toggling Game Mode directly from the app - Allow disabling Game Mode through the GameModeWarning popup - Clear and reapply all active masks when Windows Game Mode is enabled/disabled - Add periodic polling to detect external Game Mode changes Allows quick switching for games that cause issues with CPU Set Setter without needing to close the app
Reduces log clutter when processes have the same name, like Discord or browsers
|
Howdy! First off thank you for your work again. It's been really busy for me, and will be for some more time. I think it's gonna be at least 2 weeks sadly until I can properly do a review, but I will get to it! |
|
No worries, I will also be quite busy for the next few weeks, so take your time. I changed it to show the real-time CPU usage because this also shows processes that only spike occasionally, which would be missed with the 30s average. This way, they can be set to only use cores that handle background tasks, which can make games run more smoothly. If someone is searching for a specific process, they can still find it by pressing Ctrl to pause the sorting or using the search bar. I see your point behind the average approach, but in my testing, paused games always showed up at the top even when minimized because their CPU is still significantly higher than Windows processes or other apps like browsers or Discord. Changing it to the real-time approach also enabled me to pause the process CPU usage updates when CPUSetSetter is closed to the system tray, which reduces CPU usage while it is not actively used. If you still prefer the averaged approach after testing, we can still revert it to the 30s average. |
2 participants
Some changes I think make the user experience better:
Feel free to make changes where necessary.