What this FPS calculator does
I built this as a benchmark lookup. Its 197 measured rows across seven games stay inside two separately identified datasets:
- 192 CPU-and-GPU scaling rows from TechSpot’s Ryzen 7 9800X3D versus Ryzen 5 7600X review. Those rows cover four games, two CPUs, four GPUs, three resolutions, and two presets per game.
- Five first-party 4K rows from my ASUS ROG Astral RTX 5080 OC benchmark dataset. Those rows cover Cyberpunk 2077, Alan Wake 2, and Black Myth: Wukong on one recorded test system.
Pick a setup that was tested, and the page returns the average FPS and 1% low from that exact row. It does not combine the two providers, scale a 1440p result into 4K, substitute a nearby GPU, or fill a missing setting with an estimate — and each result separates the benchmark test date from the source’s publication date, so a TechSpot row whose test date was not stated says it is unspecified.
How to use it
- Pick the dataset first. This fixes the provider, test system, and source boundary.
- Choose the game, CPU, GPU, resolution, and preset from the remaining supported values.
- Read the average and 1% low together with the test date, scene, settings, and source link.
- Use Copy result link to keep that exact six-key selection. Reset returns to a supported default measurement.
The menus narrow after each choice. An unsupported shared link clears the form and shows no FPS. Choose Reset to load the supported default, then select a measured setup.
Why the dataset selector matters
Benchmark numbers inherit the reviewer’s whole method. A different scene, patch, driver, memory kit, CPU power policy, warm-up path, or run length can change the result even when the game, CPU, and GPU names match, so provider separation keeps each number attached to the system and method that produced it.
TechSpot’s results link to the review and original chart. The TechFuelHQ rows use the first-party dataset’s CC BY 4.0 license, which does not cover the TechSpot rows.
Settings are stated, off, or unspecified
The result card does not turn missing documentation into an on/off claim. It uses three different ideas:
- Specified on or specified off means the source explicitly establishes that state.
- Specified means the source names a mode such as DLSS Quality, native resolution, Native TAA, or 100% render scale.
- Unspecified by source means the available source record does not establish the setting. It does not mean disabled.
This distinction matters most for frame generation, ray tracing, and upscaling because a blank chart label is not enough evidence that a feature was off.
The measured scope
The current catalog has seven games: Rainbow Six Siege X, Kingdom Come: Deliverance II, Marvel Rivals, Warhammer 40,000: Space Marine 2, Cyberpunk 2077, Alan Wake 2, and Black Myth: Wukong. Each menu narrows to the hardware and settings present in its dataset.
Unsupported hardware gets no universal FPS range. Find a benchmark that tests the same game version and settings, or measure the scene on your own system; the CPU and GPU benchmark lookup can compare separate component indexes, but it cannot supply game FPS. If your measured result is much lower than a matching benchmark, work through the low GPU usage checks before treating a component swap as the answer.
Bounded formula experiment
Before choosing exact lookup as the public behavior, I tested one pre-specified formula inside the TechSpot grid. For each chart, the formula predicted a lower-CPU/lower-GPU cell as the smaller of its CPU anchor and GPU anchor; across 24 charts it held out three target CPU×GPU cells per chart for 72 average-FPS and 72 1%-low comparisons, while each target GPU remained present in the separate higher-CPU anchor.
| Metric | Median absolute relative error | 90th percentile | Maximum | Within 10% | Within 15% | Within 20% |
|---|---|---|---|---|---|---|
| Average FPS | 0.00% | 2.44% | 10.44% | 98.61% | 100% | 100% |
| 1% low FPS | 0.60% | 3.02% | 17.07% | 98.61% | 98.61% | 100% |
The full 72-row validation table retains each prediction, actual value, signed error, absolute error, and source key. This was a bounded formula experiment on one provider’s two-CPU, four-GPU grid; it neither tests lookup accuracy nor supplies a confidence interval, and it provides no evidence that the formula works for another game, scene, provider, CPU, GPU, or setting. The public calculator therefore uses a measured row when one exists and returns no number otherwise.
Compare with your PC
Average FPS summarizes throughput. The 1% low helps expose slower frames that the average can hide. Compare both within the same source method; neither number guarantees what your own system will produce or describes every moment of gameplay.
Match the game version and scene first. Then match the preset, resolution, render scale, upscaler, ray tracing, frame generation, CPU, GPU, and test conditions. If the source marks a field unspecified, leave it unknown instead of assuming a setting.
The catalog records source dates and chart hashes so the transcription can be checked against the captured originals; the public page includes the structured numeric facts and citations, but not the third-party chart images.