Custom Power Limits not working.

[paulusgi]

Hi, I tested the 3 different power modes Silent, Balanced and Performance and the "Apply Power Limits" checkbox do nothing.

Whatever I set on the sliders the power consumption doesn't variate. Each power plan have their own limits but can't be changed.

I have an Idea about why is this happening but not sure: In armory crate when I want to modify PPT I have to set The "Manual" power profile. ¿Maybe with Silent, Balanced or Turbo my system don't allow the app the change the power limits?
I really don't know.

Tested with: Cinebench R23 and HWInfo64.
Laptop: Asus Rog Strix G513RM 2022 (Ryzen 7 6800H + RTX3060).
G-Helper Version 0.50
Under latest BIOS v327

[seerge]

@paulusgi can you post log from %appdata%/ghelper , it should mention if PPT settings are accepted by bios or not

[seerge]

@paulusgi , ok, that's surprising .... but explains why it works in armoury (there is no way to set them separately.

TUF laptops on intel CPU had opposite issue, setting FANs were breaking PPTs (if they were not applied).

I can hardcode that for your model (models?) app will force custom fan curves ? will that be a solutuion?

[seerge]

@paulusgi do custom fan curves without custom PPTs work on your laptop?

[paulusgi]

@paulusgi , ok, that's surprising .... but explains why it works in armoury (there is no way to set them separately.

TUF laptops on intel CPU had opposite issue, setting FANs were breaking PPTs (if they were not applied).

I can hardcode that for your model (models?) app will force custom fan curves ? will that be a solution?

@seerge
Yes it will be a solution, BUT the order is important. I mean if I activate custom power limits first and then I activate custom fan curves nothing happens and the ppt values are not set. So I must apply the custom fan curves first and then apply the custom power limits to make them properly work.

And about the fan curves without PPTs yes they work without the PPTs values.

[paulusgi]

In short:

• Apply custom fan curves ONLY (NO ppts checkbox marked) = Custom fan curve works
• 1.Apply custom fan curves -> 2. Apply custom PPTs = Both will work if applied in that order (1->2).
• Apply custom PPTs without fan curves or apply custom curves after applying ppts = ONLY custom fan curves will work (PPTs will NOT)

[seerge]

GHelper.zip
Can you try this build ? app will run fan-curve command before PPTs (unless "real" custom fan curve is applied)

[paulusgi]

@seerge okey did it. The app performs exactly as the 0.51. When I only apply the custom power profile nothing happens. The custom fan curve are not activated when "Apply Power Limits" are selected. :S So for me is exactly the same app.
EDIT
SORRY, after 5 minuts the PPTs values as been applied without the "Apply Custom Fan Curve" checked.

[paulusgi]

@paulusgi clear, thanks - try this one, it should work even when you delete config GHelper.zip

(problem was in applying a fan curve that didn't exist before you edited it at least somehow, now it will save it as soon as it opened for the first time)

@seerge YES! It works perfectly without having to modify the graphical fan curve or selecting the "Apply Custom Fan Curve" checkbox.
Now the software will properly apply the PPTs on laptops like mine or similar :D
Thank you so much for your patience.

[seerge]

@paulusgi great, the only problem is that Platform PPT probably affects CPU limit and CPU slider does nothing ?

[paulusgi]

@paulusgi great, the only problem is that Platform PPT probably affects CPU limit and CPU slider does nothing ?

@seerge
Exactly the CPU slieder does nothing. And the Platform slieder affects 2 things: the STAPM_LIMIT and the PPT_LIMIT_SLOW.

[seerge]

@paulusgi that's expected based on weird DSL implementation in your case

Current app logic is to check if B0 endpoint exists (it's a second slider) and if so - show it
Otherwise show only one A0 slider (if it also exists)

Problem that your BIOS reports both A0 and B0 to exist ... :) the only fix would be hardcoding your model number again (which i'm not a big fan of), so I will probably keep it as is for now.

I have pushed fixes as part of 0.52 https://github.com/seerge/g-helper/releases/tag/v0.52 and closing this as "solved" for now.

Thanks for help!

[paulusgi]

Its more than enough so... big thanks again now it works perfect. <3 ^_^