How should I cap FPS with lsfg-vk frame generation?

November 21, 2026 3 answers
Asked by P6meterRoute+Olive

I want a game to run at 60 native FPS and use 2x frame generation for roughly 120 FPS output. Should I set the cap to 60 or 120? MangoHUD shows 60, but I can't tell whether that's counting generated frames.

Answers

Respawn!Rinse

For that target, the number you want to control is the native frame rate: 60 FPS before 2x generation. But a cap set to 60 only does that if the limiter is acting on the game's native frames. The number to enter depends on where the limiter sits relative to frame generation.

If the cap is applied to the final output instead, a 120 FPS cap may be the relevant setting. Don't assume the same MangoHUD setting works the same way across lsfg-vk versions.

Reply to this answer
speedrunKeycap_8F

The MangoHUD reading alone doesn't settle it. A 60 FPS display could be counting native frames while generated frames are added later, or it could indicate that the output is capped at 60. The counter and the limiter don't necessarily observe the same point in the pipeline.

To check, compare frame generation off and on with the same scene and cap. Use a separate output-side frame counter or capture method if available, and check whether it sees roughly twice the native rate. Also check that the display is actually running at 120 Hz or higher. Visual smoothness can be a clue, but it isn't a reliable frame count.

P14airBlock+Mango:

And roughly 120 is the goal, not a guarantee. If the native rate drops below 60, 2x generation won't produce a steady 120 from those frames.

Reply to this answer
Pixel+Pajamas

If the game has its own frame limiter, try setting that to 60 and comparing the result with frame generation on and off. That's a straightforward way to target the game's native rate, though you'll still need an output-side measurement to verify what reaches the display.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions