No "Feels Smoother"

Real Results

Every session produces before/after benchmarks. These are real numbers from real sessions — average FPS, 1% lows, and frametime data captured with CapFrameX.

📊

Results being added

This page will be populated with real before/after benchmark data from completed sessions. Screenshots of CapFrameX comparisons and client feedback will appear here as sessions are completed.

Got questions? Email us

How results are captured

Every session uses the same methodology so results are comparable and honest:

1

Baseline capture first

Before any changes, we run CapFrameX during a real in-game scenario — not a synthetic benchmark. We capture average FPS, 1% lows, 0.1% lows, and frametime graph.

2

Identical scenario after

After optimisation, the same in-game scenario is replayed as closely as possible and captured with the same tool. Same map, same area, same conditions.

3

Side-by-side comparison

CapFrameX's comparison view puts both runs side by side. You can see the frametime graph, avg, and percentiles clearly. No interpretation needed — the numbers speak.

What the numbers mean

Average FPS

How many frames per second your GPU is pushing on average. Higher is better — but it's not the whole story.

1% Lows

The FPS you're getting during the worst 1% of frames. This is what "stutter" feels like. A bad 1% low relative to avg FPS means inconsistency.

Frametime

How long each individual frame takes to render (in ms). A flat frametime graph = smooth. Spikes = perceived stutter even if avg FPS looks fine.

Input latency

The delay between your mouse/keyboard input and it appearing on screen. Affected by frame caps, Reflex, driver settings, and VRR strategy.

Want results like these on your PC?

Start with the free estimator to see your likely gains, or book a session directly.