mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 13:02:03 +00:00
[GH-ISSUE #102] FPS Limiting in sway #68
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#68
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dhofer on GitHub (Aug 26, 2024).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/102
Wolf currently sets the environment variable GAMESCOPE_REFRESH to maxFPS from the Moonlight client.
To have something similar in the new default sway setup we could set DXVK_FRAME_RATE to the same value. This would allow automatic FPS limiting in DXVK and recent versions of VKD3D.
@ABeltramo commented on GitHub (Sep 2, 2024):
Just found out also https://github.com/milaq/libstrangle which might be worth a shot
@miroth commented on GitHub (Feb 22, 2026):
On local gaming, I use mangohud to limit the fps.
Since mangohud is already installed on the steam container, this may also be a viable option for you.
As far as I can see, a new and bare mangohud config is created on every startup. But you can overwrite the env variable when starting a steam game.
Just enter something like this into the game start: