Skip to content

Cap screensaver ttfx at 30fps by default - #13631

Open
AnPod wants to merge 1 commit into
omacom:quattrofrom
AnPod:cursor/fix-screensaver-fps-e0d3
Open

AnPod wants to merge 1 commit into
omacom:quattrofrom
AnPod:cursor/fix-screensaver-fps-e0d3

Conversation

@AnPod

@AnPod AnPod commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes #13279

Hardcoded 120fps screensaver pinned a CPU core on older laptops.

Change

  • Default screensaver frame rate to 30fps
  • Allow OMARCHY_SCREENSAVER_FRAME_RATE to override

Test plan

  • Start the screensaver; CPU/fan should stay calm vs the previous 120fps default

Hardcoded 120fps pinned a CPU core on older laptops; allow OMARCHY_SCREENSAVER_FRAME_RATE to override.

Co-authored-by: AnPod <AnPod@users.noreply.github.com>
@jandrusk

jandrusk commented Oct 7, 2026

Copy link
Copy Markdown

This overlaps two older open PRs for the same knob: #8556 adds an override for the screensaver frame rate (with a manual entry), and #8695 caps it at the panel's refresh rate. Only one of these approaches should land, so it's worth comparing them.

One thing to check before changing the default: TTE effects advance per frame, so dropping from 120 to 30 fps should make each effect play roughly 4x slower, not just smoother or rougher. That's a visible change to the screensaver, so it's a product call more than a bug fix. A refresh-rate cap (#8695), or a lower default plus an override (this PR or #8556), trade that differently. Also, OMARCHY_SCREENSAVER_FRAME_RATE only takes effect if it's in the Hyprland/uwsm session environment, which deserves a line in the manual if it stays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Screensaver (ttfx 120fps fullscreen) causes sustained high CPU, heat and fan noise

4 participants