We measured this on mid and high-end rigs running CS2 and only kept the tweaks that moved 1% lows, not just the average FPS counter. Here's what survived testing.
Cap your frame rate (yes, really)
An uncapped frame rate sounds faster but produces uneven frame times and extra latency. A cap a few frames below your refresh rate keeps pacing tight.
For a 240Hz panel in CS2, cap around 234–237 FPS. On 144Hz, target ~141. Use the in-game limiter first, then the driver as a backstop.
Lock your GPU control panel
Driver-level settings override in-game ones, so a misconfigured control panel quietly caps CS2. 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
Verify it actually worked
Never trust the average FPS number alone. Watch 1% and 0.1% lows and frame-time consistency in CS2 — 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)
- ✓Power management → Prefer maximum performance
- ✓Benchmark the same scene before/after
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 →