Guide

How FPS is estimated

The six-step model behind the FPS Calculator: what the estimate is, what it is anchored to, and how far it can move. Written so you can check it.

In short

The FPS Calculator estimates frame rates from measured performance in RDR2, Cyberpunk 2077 and GTA V, scaled by GPU tier and CPU factor, adjusted for preset and upscalers, and presented as a band of ±15% — never as a single number. At launch, the model re-validates against real GTA 6 performance.

Published July 24, 2026 · Updated July 24, 2026 · Last verified November 17, 2026

The six-step model

  1. 1. Anchor to measured games. Start from frame rates measured in RDR2, Cyberpunk 2077 and GTA V at equivalent presets. These are the closest released analogues to GTA 6's RAGE engine workload, and every number in the model traces to a published benchmark.
  2. 2. Scale by GPU tier. Apply the tier delta: the measured performance ratio between the card the benchmark used and the card being estimated. Tier deltas come from TechPowerUp and Hardware Unboxed datasets, not from vendor marketing.
  3. 3. Apply the CPU factor. At 1080p the CPU is often the limiter; at 4K it rarely is. A scaling factor, derived from the same benchmarks at different resolutions, adjusts the estimate for the CPU tier and the resolution together.
  4. 4. Adjust for preset. Low, Medium, High and Ultra are not equal steps. Each preset carries a measured cost from the anchoring games, applied as a multiplier rather than a guess.
  5. 5. Account for upscalers and ray tracing. DLSS, FSR and ray tracing each carry a fixed, stated cost or gain, calibrated against RDR2 captures. The estimate shows the setting it assumed, so a mismatch is visible.
  6. 6. Present a band, not a point. The result is an average FPS and a 1% low, each as a range with a ±15% band. A single-point number would be a claim; the band is the honest form of the estimate.

Calibration: what the estimate is anchored to

The anchoring datasets are RDR2, Cyberpunk 2077 and GTA V at equivalent presets, with tier deltas from TechPowerUp and Hardware Unboxed. VRAM allocation captures from RDR2 calibrate the memory side of the estimate. Every input the model uses is listed on the methodology page, with its error band.

What the model cannot do yet: it cannot predict GTA 6's exact engine behaviour, its draw-call load in the densest parts of Vice City, or how Rockstar's day-one patch will change performance. Those are the reasons the band exists.

Limits of the estimate

  • The band is ±15% on the mean. A card estimated at 60 FPS could land anywhere from 51 to 69.
  • 1% lows are harder to estimate than averages and carry the same band.
  • Driver releases with a known GTA V or RDR2 impact trigger a re-run of the tier deltas.
  • At launch, the model re-validates against real GTA 6 performance and the band tightens or the model is corrected.

Try the FPS Calculator →

FPS estimation, answered

Ranges, anchoring games, upscalers and launch re-validation.

  • Why is the estimate a range, not a single number?

    Because GTA 6 is not out yet. The estimate is anchored to measured behaviour in RDR2, Cyberpunk 2077 and GTA V, and the ±15% band is the variance in those datasets. A single number would imply a precision the model does not have.

  • Which games is the estimate anchored to?

    RDR2, Cyberpunk 2077 and GTA V, at equivalent presets. They are the closest released analogues to the RAGE-engine workload GTA 6 will run, and the anchoring datasets are named in the methodology page.

  • How accurate will this be at launch?

    The band is ±15% on the mean. At launch the model re-validates against real GTA 6 performance and the band tightens or the model is corrected, with the change dated in the FPS Calculator changelog.

  • Does it account for DLSS or FSR?

    Yes. Upscalers and ray tracing each carry a stated cost or gain, calibrated against RDR2 captures. The calculator shows the setting it assumed, so a mismatch between your setup and the assumption is visible.

  • What about 1% lows?

    The calculator reports an average and a 1% low, each as a range. The 1% low is the number that decides whether a game feels smooth, and it is the harder one to estimate, which is why it carries the same ±15% band.