I'm trying to run a game at a 30 fps base rate with 2x frame generation. Should I use the SteamOS slider, the game's limiter, or a launch option instead?
Which frame cap should I use with lsfg-vk on SteamOS?
Answers
For a DirectX 12 game using VKD3D-Proton, one option is to try VKD3D_CONFIG=frame_rate_limit=30 lsfg-vk %command% in the launch options. The idea is to limit the base frames at the translation layer rather than relying on the SteamOS compositor cap.
Set the display to 60 Hz for a 30 fps base with 2x generation, turn off the game's own cap and VSync, and test with the SteamOS frame limit disabled. Allow tearing if you're following that setup. If your lsfg-vk setup has a base rate setting, match it to the launch option.
Reply to this answer
I wouldn't assume the SteamOS slider is unusable in every game. It caps at the compositor, and the reported tradeoff is a steady frame-time graph with more noticeable input lag. Try camera movement with and without it and see whether the difference bothers you.
Reply to this answer
The case for the translation-layer cap is mostly about CPU behavior. The source test reported CPU spikes and higher power draw with some game and lsfg-vk limiters, which it attributed to busy waiting. It reported steadier CPU usage with the VKD3D cap.
That's a useful thing to check, not proof that every internal limiter behaves the same way. Compare power draw, frame pacing and input feel in the game you're actually playing.
Reply to this answer
Check which graphics API the game uses before changing launch options. The VKD3D setting is for the DirectX 12 translation path. For an older DirectX 9 or 11 game using DXVK, the suggested alternative is DXVK_FRAME_RATE=30.
Reply to this answer
Add your answer
Answers are reviewed before publication.
campfireQueue:
For a 28 fps base, the same idea would pair it with a 56 Hz display setting, if that's available on your device.