Skip to content

Default to user-selected TDP when autotune can't get the frame rate - #177

Closed
anaveto wants to merge 2 commits into
IHulkSmashI:mainfrom
anaveto:fix/autotune-no-fps-limit
Closed

anaveto wants to merge 2 commits into
IHulkSmashI:mainfrom
anaveto:fix/autotune-no-fps-limit

Conversation

@anaveto

@anaveto anaveto commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Problem:

  • When autotune receives no frame rate, autotune stops after 30 s.
  • But the start value of autotune stays on the chip until the game stops. This also occurs when frames come later.
  • With a target, the start value is 22 W of a 35 W power pick.

Change:

  • start() records the settings that the power pick applied.
  • When autotune stops because no frame rate comes, ClawDeck applies these settings again.
  • When frames come later, autotune controls the game again.
  • A manual change still stops autotune until the game stops.

Test results: Claw 8 EX (MS-1T91), Bazzite 45.20261112, kernel 7.3.3-ogc1.1.fc45.

  • Enshrouded with no frame rate, Custom 35 W, target 120: 22 W at the start, 35 W after 30 s.
  • Frames that come late: a replay of the recorded readings of Order of the Sinking Star (first frame 54 s after the start).
  • pytest on Linux (on the Claw, Python 3.15.2), this branch alone on main: 263 passed.
  • pnpm build and typecheck: pass.

🤖 Generated with Claude Code (model: Claude Opus 5.5, effort: xhigh)

anaveto and others added 2 commits November 12, 2026 13:49
When autotune gave up on a game whose frame rate it can't read (no XeSS/XeLL, no MangoHud log), it paused but left
what start() had applied: a target's mid-range start (22 W of a 35 W pick), or a saved CPU ceiling, boost and GPU
floor. Enshrouded (Vulkan, own FSR3) ran at 22 W for the whole game, 30-40 fps instead of 60, until autotune was
switched off. start() now notes the levers as the pick left them, and giving up puts them back (TDP to the set
TDP, under the temperature guard's step if there is one).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Giving up after 30 s without a frame rate was for the whole session, so a game slower than that to its first frame
(Order of the Sinking Star, 54 s) never got autotune. Giving up still puts your pick back; frames after that hand
the game back to autotune (from your pick; most-frames mode measures again). A manual change pauses it for good,
also after it gave up.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@anaveto
anaveto marked this pull request as ready for review November 12, 2026 14:42
@anaveto
anaveto marked this pull request as draft November 14, 2026 13:08
@anaveto
anaveto marked this pull request as ready for review November 14, 2026 18:30
@IHulkSmashI

Copy link
Copy Markdown
Owner

Merged through #190 together with the others (your commits, rebased onto main, conflicts between the fan PRs resolved by keeping both sides) and released in beta 17. Thanks a lot for all of this, it's a huge batch of real fixes! #179 is still open since it's marked draft.

anaveto added a commit to anaveto/ClawDeck that referenced this pull request Nov 15, 2026
claw = upstream main (beta 19, 166bffd) + IHulkSmashI#179's Autotune target work
(fork branch fix/autotune-target-keeps-your-target 0e8d7fe, 18 commits),
squashed. Everything else claw carried is upstream now (IHulkSmashI#177-IHulkSmashI#189 in beta
17, IHulkSmashI#196-IHulkSmashI#201 in beta 19). Conflicts resolved as claw had them: the target
start without Auto FPS (max_tdp), the guard's limit from limit_w(), and
both sides of README, STATUS and DESIGN.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants