← All guides

Frame generation and upscaling: when to use them

June 11, 2025 · 4 min read

Most players leave 15–30% of their performance on the table. Below is the exact order we tune systems on the bench, what each change buys you, and how to verify it instead of trusting placebo.

Lock your GPU control panel

Driver-level settings override in-game ones, so a misconfigured control panel quietly caps your game. We standardise these on every build.

Low Latency Mode set to Ultra (NVIDIA) or Anti-Lag (AMD) shaves real input delay when you're GPU-bound.

  • Power management → Prefer maximum performance
  • Low Latency Mode → Ultra (or Radeon Anti-Lag On)
  • Texture filtering → Performance / High performance
  • Disable in-game V-Sync; cap FPS just under your refresh instead

Cap your frame rate (yes, really)

Capping is the most counter-intuitive win here. A stable 237 FPS feels better than a spiky 400 because the frame-time graph flattens out.

For a 240Hz panel, cap around 234–237 FPS. On 144Hz, target ~141. Use the in-game limiter first, then the driver as a backstop.

Verify it actually worked

Never trust the average FPS number alone. Watch 1% and 0.1% lows and frame-time consistency — that's what 'smooth' really means.

Run the same replay or aim-trainer routine before and after, capture with a frame-time overlay, and only keep changes that flatten the graph.

  • Benchmark the same scene before/after
  • Track 1% lows, not just average FPS
  • Watch the frame-time line — flatter is better
  • Change one thing at a time so you know what moved the needle
// The TL;DR
  • Power management → Prefer maximum performance
  • Cap your frame rate (yes, really)
  • Benchmark the same scene before/after
#dlss#frame gen

Skip the manual work

Bravo applies every tweak in this guide — and hundreds more — in one click, fully reversible. Tuned per game, per rig.

See the tweak packs →