We measured this on mid and high-end rigs and only kept the tweaks that moved 1% lows, not just the average FPS counter. Here's what survived testing.
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
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.
- ✓Benchmark the same scene before/after
- ✓Cap your frame rate (yes, really)
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 →