- Welcome to Bitsum Community Forum.
Development (period)
Recent posts
#11
Process Lasso / Re: [Suggestion] Process Lasso...
Last post by Coldblackice - Today at 08:39:33 AMI realize I'm beating a dead horse, but there's real opportunity for PL to level-up its userbase here. I continue seeing pleas from users all across Discords/forums/YT comments for help setting up PL to help improve their games via configuring of affinity/X3D-CCD.
The AMD X3D userbase has overall been fairly small until now, however, following Intel's recent CPU snafu, I've been seeing droves of users both jumping ship to AMD-X3D, and being recommended to jump ship when ready for their next build.
For PL's sake, I'd highly suggest rolling out some degree of this ability in whatever form sooner rather than later, even if unpolished, because:
If PL can quickly elbow its way ahead of Microsoft here, it can become the de facto solution for a new herd of many users, solidifying itself not only as the go-to "Gamer" software, but also extend itself as part of the automatic all-around setup/routines of many PC builders and owners, going beyond the task of mere game performance alone.
However, once Microsoft (with AMD) polishes the Game-Bar/OS functionality, it'll more than likely get deemed "good enough" by a majority of users, who won't care enough to be bothered tweaking it, nor will more technically apt users feel it necessary to push users toward third-party solutions like PL for handling this.
My suggestion:
A PL "Gamer" mode, which detects if the user is a gamer based on the presence of Steam/Epic/Bnet clients (most of all, Steam), and presents a popup/modal asking the user if they'd like to enable "Gamer"-mode, even if merely cloning Performance-mode.
This then makes tweaks and affinity configuring based on the user's CPU maker/model, either scraping Steam/.VDFs/registry for their installed games, or watches for child processes spawned by Steam/SteamService, applying the optimal affinity configuration necessary. (When a PL-configured game exits, PL could optionally pop a Y/N box asking the user how the game performed, utilizing that telemetry)
The "Gamer mode" popup/modal could even include a simple GIF that animates a simple visual of what's happening (obviously at a very simplistic, high-level bird's eye view). Despite coming to the realization that many (most?) gamers just aren't interested in learning the underlying mechanics such as this, I think even non-technically apt users would appreciate an animated diagram showing them the CPU and before/after of their game being on an optimal or non-optimal CCD). PL would then handle all the backend configuring of this, and the user would feel good knowing that they're now the wiser as to how this works.
And lastly, I'm only recommending this for PL's sake, as I don't need automation like this, and am in the outlier minority "freak" that likes having access to lower-level nitty-gritty configuring like this
The AMD X3D userbase has overall been fairly small until now, however, following Intel's recent CPU snafu, I've been seeing droves of users both jumping ship to AMD-X3D, and being recommended to jump ship when ready for their next build.
For PL's sake, I'd highly suggest rolling out some degree of this ability in whatever form sooner rather than later, even if unpolished, because:
- Loads of users have been doing new AMD PC builds following the "Abandon-Intel" movement (as far as home user/gamerbase-wise), as well as new back-to-school PC sales
- AMD recently announced their upcoming 9000-series X3D CPUs which will release in a couple months
- AMD's 5000- and 7000-series X3D CPUs have subsequently gotten their retail prices cut in lieu of this, sparking a wave of many new buyers
- Microsoft continues working on their "Game Bar" utility, and working with AMD to adapt it (and OS overall) with respect to CCD handling and management, affinity, configuring, etc., to do so automatically and invisibly without the user even being made aware of such
If PL can quickly elbow its way ahead of Microsoft here, it can become the de facto solution for a new herd of many users, solidifying itself not only as the go-to "Gamer" software, but also extend itself as part of the automatic all-around setup/routines of many PC builders and owners, going beyond the task of mere game performance alone.
However, once Microsoft (with AMD) polishes the Game-Bar/OS functionality, it'll more than likely get deemed "good enough" by a majority of users, who won't care enough to be bothered tweaking it, nor will more technically apt users feel it necessary to push users toward third-party solutions like PL for handling this.
My suggestion:
A PL "Gamer" mode, which detects if the user is a gamer based on the presence of Steam/Epic/Bnet clients (most of all, Steam), and presents a popup/modal asking the user if they'd like to enable "Gamer"-mode, even if merely cloning Performance-mode.
This then makes tweaks and affinity configuring based on the user's CPU maker/model, either scraping Steam/.VDFs/registry for their installed games, or watches for child processes spawned by Steam/SteamService, applying the optimal affinity configuration necessary. (When a PL-configured game exits, PL could optionally pop a Y/N box asking the user how the game performed, utilizing that telemetry)
The "Gamer mode" popup/modal could even include a simple GIF that animates a simple visual of what's happening (obviously at a very simplistic, high-level bird's eye view). Despite coming to the realization that many (most?) gamers just aren't interested in learning the underlying mechanics such as this, I think even non-technically apt users would appreciate an animated diagram showing them the CPU and before/after of their game being on an optimal or non-optimal CCD). PL would then handle all the backend configuring of this, and the user would feel good knowing that they're now the wiser as to how this works.
And lastly, I'm only recommending this for PL's sake, as I don't need automation like this, and am in the outlier minority "freak" that likes having access to lower-level nitty-gritty configuring like this
#12
Process Lasso / 14.3.0.58 - Performance Mode e...
Last post by ranko - Today at 05:09:36 AMHi,
I think I reported this already in the past (months or year ago).
I have Balanced as default/initial energy profile.
Idle saver is enabled.
So usually the system switches between balanced and energy saving.
Ultimate Performance I choosed for special application (Cubase, Games, Macrium Reflect).
Sometimes I want the system to be performant regardless of which application is choosed or not, then I right-click to the PL icon and enable "Performance mode enabled".
I have a Desktop Gadget, which shows me the enery setting (Highest, Balanced, Energy Saving).
If I choose Performance mode and Ultimate kicks in, then the Gadget shows no status, because at that time Ultimate didn't exist. So there I can see quickly if there is something wrong.
And after some time something goes wrong. I see balanced activated although performance mode is still enabled.
Could you try to nail this down and fix it? That would be great.
Otherwise / usually it works very fine.
Here my config.
[Administration]
Version=6100200
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfForeground=true
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
DoNotAdjustAffinityIfCustomized=true
OocDisableCoreParkingWhileIn=false
UseEfficiencyMode=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=10
PerProcessUsageBeforeRestraint=5
TimeOverQuotaBeforeRestraint=900
PerProcessUsageForRestore=2
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
ChangeTrayIconOnRestraint=true
OocExclusions=cubase12.exe,cubase13.exe,musicbee.exe,nms.exe,picasa3.exe,wavelabpro11.exe,wavelabpro12.exe
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowCPUCoreUtilGraphs=true
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
ShowPowerProfile=true
GraphShowTooltips=true
ShowCPUUtilityAsPrimary=true
[Advanced]
AutomaticUpdate=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
[Sampling]
SamplingEnabled=false
SamplingIntervalSeconds=900
SamplingOutputPath=
SamplingIncludePattern=
SamplingExcludePattern=
[Performance]
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
IsConfigWritable=true
ForcedMode=false
IgnoreProblematicProcesses=false
IgnoreSuspendedProcesses=false
SetTimerResolutionAtStartup=0
[ForegroundBoosting]
BoostForegroundProcess=false
ForegroundBoostPriorityClass=0x8000
BoostOnlyNormal=true
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=true
[Logging]
LogDisable=false
IncludeCommandLines=false
LogSmartTrim=true
LogCPULimiter=true
LogEfficiencyMode=true
LogGroupExtender=true
LogCPUSets=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
SmartTrimClearFileCache=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimExclusions=latmon.exe,cubase12.exe,cubase13.exe,wavelabpro11.exe,wavelabpro12.exe,musicbee.exe,eac.exe,freefilesync_x64.exe,vortex.exe,bg3_dx11.exe,cyberpunk2077.exe,nms.exe,x4.exe
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
NamedAffinities=
DefaultPriorities=
DefaultIOPriorities=
DefaultMemoryPriorities=
ThreadPriorityBoosts=
DefaultAffinitiesEx=reflectbin.exe,0,2-15
CPUSets=
KeepRunningProcesses=
[ProcessAllowances]
EfficiencyMode=
[ProcessDefaults]
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
ProhibitInternetExplorerExceptWhenAny=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Ultimative Leistung
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=bg3_dx11.exe,cubase12.exe,cyberpunk2077.exe,eac.exe,freefilesync_x64.exe,latmon.exe,reflectbin.exe,vortex.exe,wavelabpro11.exe,x4.exe,cubase13.exe,starcitizen.exe,s-gear.exe,wavelabpro12.exe,digikam.exe,resolve.exe,photomove 2.exe,dupeguru-win64.exe,luminar neo.exe,photoshopelementsorganizer.exe,premiereelementseditor.exe,picasa3.exe
[PowerManagement]
StartWithPowerPlan=Ausbalanciert
Display=
PC=
[ProcessDefaults]
DefaultPowerSchemes=b1-win64-shipping.exe;ultimative leistung,picasa3.exe;ultimative leistung,nms.exe;ultimative leistung,premiereelementseditor.exe;ultimative leistung,photoshopelementsorganizer.exe;ultimative leistung,luminar neo.exe;ultimative leistung,dupeguru-win64.exe;ultimative leistung,photomove 2.exe;ultimative leistung,resolve.exe;ultimative leistung,digikam.exe;ultimative leistung,wavelabpro12.exe;ultimative leistung,bg3_dx11.exe;ultimative leistung,cubase12.exe;ultimative leistung,cyberpunk2077.exe;ultimative leistung,eac.exe;ultimative leistung,freefilesync_x64.exe;ultimative leistung,latmon.exe;ultimative leistung,reflectbin.exe;ultimative leistung,vortex.exe;ultimative leistung,wavelabpro11.exe;ultimative leistung,x4.exe;ultimative leistung,cubase13.exe;ultimative leistung,starcitizen.exe;ultimative leistung,es2-win64-shipping.exe;ultimative leistung
[PowerSaver]
PowerSaver_IdleTime=15
EnergySaverEnabled=true
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_TargetGUID=Energiesparmodus
PowerSaver_Exclusions=
I think I reported this already in the past (months or year ago).
I have Balanced as default/initial energy profile.
Idle saver is enabled.
So usually the system switches between balanced and energy saving.
Ultimate Performance I choosed for special application (Cubase, Games, Macrium Reflect).
Sometimes I want the system to be performant regardless of which application is choosed or not, then I right-click to the PL icon and enable "Performance mode enabled".
I have a Desktop Gadget, which shows me the enery setting (Highest, Balanced, Energy Saving).
If I choose Performance mode and Ultimate kicks in, then the Gadget shows no status, because at that time Ultimate didn't exist. So there I can see quickly if there is something wrong.
And after some time something goes wrong. I see balanced activated although performance mode is still enabled.
Could you try to nail this down and fix it? That would be great.
Otherwise / usually it works very fine.
Here my config.
[Administration]
Version=6100200
ConfigPasswordMD5=
[OutOfControlProcessRestraint]
OocOn=true
ExcludeChildrenOfForeground=true
DisableProBalanceWhenSysIdle=false
ProBalanceDropOneRandomCore=false
DoNotAdjustAffinityIfCustomized=true
OocDisableCoreParkingWhileIn=false
UseEfficiencyMode=false
DisableProBalanceIfSysIdleThisManyMS=30000
TotalProcessorUsageBeforeRestraint=10
PerProcessUsageBeforeRestraint=5
TimeOverQuotaBeforeRestraint=900
PerProcessUsageForRestore=2
PlayOnRestraint=C:\WINDOWS\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\WINDOWS\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=4200
MaximumTimeOfRestraint=0
TameOnlyNormal=true
LowerToIdleInsteadOfBelowNormal=false
ExcludeServices=true
PlaySoundOnRestraint=false
PlaySoundOnRestore=false
RestrainByAffinity=false
RestraintAffinity=
ExcludeForegroundProcesses2=true
DoNotLowerPriorityClass=false
LowerIOPriorityDuringRestraint=false
MatchExclusionsByPathnameToo=false
ChangeTrayIconOnRestraint=true
OocExclusions=cubase12.exe,cubase13.exe,musicbee.exe,nms.exe,picasa3.exe,wavelabpro11.exe,wavelabpro12.exe
OocHardCodedExclusionOverrides=
[GUI]
ClearLogAtExit=false
ShowCPUCoreUtilGraphs=true
ShowGraphLegend=true
ShowGraphCPU=true
ShowGraphResponsiveness=true
ShowGraphMemoryLoad=true
ShowGraphProBalanceEvents=true
ShowGraphSelectedProcessesCPUHistory=true
ProBalanceCountersOnGraph=true
ShowGraphLicenseName=true
ShowPowerProfile=true
GraphShowTooltips=true
ShowCPUUtilityAsPrimary=true
[Advanced]
AutomaticUpdate=false
[Performance]
DefaultsLevel=327942
GracefulWaitTimeInMs=5000
UpdateSpeedGUI=1000
UpdateSpeedCore=1000
[Sampling]
SamplingEnabled=false
SamplingIntervalSeconds=900
SamplingOutputPath=
SamplingIncludePattern=
SamplingExcludePattern=
[Performance]
ManageOnlyCurrentUser=false
ExitOnCloseWindow=false
SoundsOff=true
IsConfigWritable=true
ForcedMode=false
IgnoreProblematicProcesses=false
IgnoreSuspendedProcesses=false
SetTimerResolutionAtStartup=0
[ForegroundBoosting]
BoostForegroundProcess=false
ForegroundBoostPriorityClass=0x8000
BoostOnlyNormal=true
ForegroundBoostExclusions=
[SystemTrayIcon]
UseStaticIcon=false
ShowResponsivnessInTrayInsteadOfProcessorUsage=true
[Logging]
LogDisable=false
IncludeCommandLines=false
LogSmartTrim=true
LogCPULimiter=true
LogEfficiencyMode=true
LogGroupExtender=true
LogCPUSets=true
LogProBalanceParkingChanges=true
LogProcessExecutions=false
LogProcessTerminations=false
LogProcessesDisallowed=true
LogDefaultPriorityAdjustments=true
LogDefaultAffinityAdjustments=true
LogProBalanceBegin=true
LogProBalanceEnd=true
LogInstanceLimitTerminations=true
LogPowerProfileChanges=true
[MemoryManagement]
SmartTrimIsEnabled=true
SmartTrimWorkingSetTrims=false
SmartTrimClearStandbyList=false
SmartTrimClearFileCache=false
ClearStandbyFreeRAMThresholdMB=1024
ClearStandbyOnlyInPerfMode=true
SmartTrimExclusions=latmon.exe,cubase12.exe,cubase13.exe,wavelabpro11.exe,wavelabpro12.exe,musicbee.exe,eac.exe,freefilesync_x64.exe,vortex.exe,bg3_dx11.exe,cyberpunk2077.exe,nms.exe,x4.exe
SmartTrimAutoMinimumRAMLoad=65
MinimumProcessWSSInMb=196
SmartTrimIntervalMins=15
[SysTrayBalloons]
EnableSystemTrayNotification=false
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=false
[ProcessAllowances]
ApplyInstanceCountLimitsToAllUsers=false
AllowedProcesses=
DisallowedProcesses=
InstanceLimitedProcesses=
InstanceManagedCPUAffinities=
ProcessThrottles=
OneTimeProcessThrottles=
CPULimitRules=
[ProcessDefaults]
NamedAffinities=
DefaultPriorities=
DefaultIOPriorities=
DefaultMemoryPriorities=
ThreadPriorityBoosts=
DefaultAffinitiesEx=reflectbin.exe,0,2-15
CPUSets=
KeepRunningProcesses=
[ProcessAllowances]
EfficiencyMode=
[ProcessDefaults]
MatchWildcardsToPathnames=true
MatchOnCommandLine=false
[AdvancedRules]
DivideCPUPercentThresholdsBySystemCPUCount=false
ProcessorGroupExtended=
ProhibitInternetExplorerExceptWhenAny=
WatchdogRules2=
[GamingMode]
GamingModeEnabled=false
GamingChangePowerPlan=true
TargetPowerPlan=Ultimative Leistung
GamingModeEngageForSteam=true
AutomaticGamingModeProcessPaths=bg3_dx11.exe,cubase12.exe,cyberpunk2077.exe,eac.exe,freefilesync_x64.exe,latmon.exe,reflectbin.exe,vortex.exe,wavelabpro11.exe,x4.exe,cubase13.exe,starcitizen.exe,s-gear.exe,wavelabpro12.exe,digikam.exe,resolve.exe,photomove 2.exe,dupeguru-win64.exe,luminar neo.exe,photoshopelementsorganizer.exe,premiereelementseditor.exe,picasa3.exe
[PowerManagement]
StartWithPowerPlan=Ausbalanciert
Display=
PC=
[ProcessDefaults]
DefaultPowerSchemes=b1-win64-shipping.exe;ultimative leistung,picasa3.exe;ultimative leistung,nms.exe;ultimative leistung,premiereelementseditor.exe;ultimative leistung,photoshopelementsorganizer.exe;ultimative leistung,luminar neo.exe;ultimative leistung,dupeguru-win64.exe;ultimative leistung,photomove 2.exe;ultimative leistung,resolve.exe;ultimative leistung,digikam.exe;ultimative leistung,wavelabpro12.exe;ultimative leistung,bg3_dx11.exe;ultimative leistung,cubase12.exe;ultimative leistung,cyberpunk2077.exe;ultimative leistung,eac.exe;ultimative leistung,freefilesync_x64.exe;ultimative leistung,latmon.exe;ultimative leistung,reflectbin.exe;ultimative leistung,vortex.exe;ultimative leistung,wavelabpro11.exe;ultimative leistung,x4.exe;ultimative leistung,cubase13.exe;ultimative leistung,starcitizen.exe;ultimative leistung,es2-win64-shipping.exe;ultimative leistung
[PowerSaver]
PowerSaver_IdleTime=15
EnergySaverEnabled=true
EnergySaverForceActivePowerProfile=false
EnergySaverUpPowerProfileName=
EnergySaverEvents=true
DisableEnergySaverDuringGamingMode=true
PowerSaver_TargetGUID=Energiesparmodus
PowerSaver_Exclusions=
#13
Process Lasso / Bitsum Highest Performance - s...
Last post by ranko - Today at 04:43:43 AMHi,
I used the tool QuickCPU to compare Energy Profiles and had some interesting findings
https://coderbag.com/product/quickcpu?fw=upd
1. When comparing "Highest Performance" (hope I got the name right, have german localization) with "Ultimate Performance" (activated with powercfg command), then you will notice surprisingly that there is no difference when running on AC (Plugged In) only for DC (battery).
In the tool select "power settings" and then "compare power plans".
As "Ultimate Performance" is from the product Windows for Workstations I would have expected some interesting settings which bring you even higher performance than Highest Performance but if you take a look, the changed values "in red" are only in the column for DC (battery).
Disappointing, so good old "Highest Performance" seems to be well enough.
2. Then I compared "Highest Performance" with "Bitsums Highest Performance".
Could you kindly add these changes when running plugged (AC Power).
309dce9b-bef4-4119-9921-a851fb12f0f4 Stop Diashow, good for saving some CPU cycles, especially when recording (DAW, Cubase, ...)
Thanks.
I used the tool QuickCPU to compare Energy Profiles and had some interesting findings
https://coderbag.com/product/quickcpu?fw=upd
1. When comparing "Highest Performance" (hope I got the name right, have german localization) with "Ultimate Performance" (activated with powercfg command), then you will notice surprisingly that there is no difference when running on AC (Plugged In) only for DC (battery).
In the tool select "power settings" and then "compare power plans".
As "Ultimate Performance" is from the product Windows for Workstations I would have expected some interesting settings which bring you even higher performance than Highest Performance but if you take a look, the changed values "in red" are only in the column for DC (battery).
Disappointing, so good old "Highest Performance" seems to be well enough.
2. Then I compared "Highest Performance" with "Bitsums Highest Performance".
Could you kindly add these changes when running plugged (AC Power).
309dce9b-bef4-4119-9921-a851fb12f0f4 Stop Diashow, good for saving some CPU cycles, especially when recording (DAW, Cubase, ...)
Thanks.
#14
Process Lasso / Re: Auto Log Rotation
Last post by Trever Willms - August 29, 2024, 12:48:27 AMThe auto-rotate function still works normally and can detect specific errors.
#15
Process Lasso / Re: 24H2 7950X3D CPU Set Probl...
Last post by Procha - August 28, 2024, 02:03:15 PMOk thanks. It does this in every game I tried, so I think It's Windows issue.
#16
Process Lasso / Re: 24H2 7950X3D CPU Set Probl...
Last post by Jeremy Collake - August 28, 2024, 01:43:44 PMWow! As of now, I don't have an explanation. It's possible that 24H2 changed CPU Sets behavior and/or that specific game has an incompatibility. We will monitor for any similar reports and run some tests to see if we can elucidate the change.
#17
Process Lasso / 24H2 7950X3D CPU Set Problems
Last post by Procha - August 28, 2024, 10:17:07 AMHello. So I upgraded my Windows 11 to 24H2 build 26120 and since then whenever I apply CPU Sets to any game to limit it to X3D CCD0, my CCD0 usage goes to 100% and my game freezes indefinitely, but if I don't set any CPU Sets the game runs fine. Any help with this? Before I upgraded there were not any problems like this. Thanks
#18
General / Re: Power plan switching, Park...
Last post by mattskiiau - August 27, 2024, 11:23:47 PMThanks Jeremy,
I've been able to figure it out. Setting freq to 1% via PCP allowed balance profile to down clock correctly. For some reason 5% wasn't lowering it for some reason.
Happy with the setup now, thanks!
I've been able to figure it out. Setting freq to 1% via PCP allowed balance profile to down clock correctly. For some reason 5% wasn't lowering it for some reason.
Happy with the setup now, thanks!
#19
Process Lasso / Re: 24h2 Ryzen performance lif...
Last post by pixelcowboy - August 27, 2024, 01:28:13 PMThanks!
#20
General / Re: Power plan switching, Park...
Last post by Jeremy Collake - August 27, 2024, 07:22:58 AMUse Process Lasso's IdleSaver or ParkControl's Dynamic Boost, but don't use both. If you try to use both, Dynamic Boost will be disabled.
They do the same thing and detect idle the same way.
Process Lasso doesn't directly affect CPU downclocking. That is controlled by the power plan attributes. If your target idle power plan is configured as desired, it should be working. If you continue to encounter that, we can try to ferret out what you're seeing.
They do the same thing and detect idle the same way.
Process Lasso doesn't directly affect CPU downclocking. That is controlled by the power plan attributes. If your target idle power plan is configured as desired, it should be working. If you continue to encounter that, we can try to ferret out what you're seeing.