How FrameForecast estimates FPS.

FrameForecast is designed to show where a number came from, not just output a convincing-looking FPS figure.

1. Direct benchmark records

If the dataset contains the exact game, GPU, CPU, resolution and preset combination, FrameForecast uses the stored benchmark data and weights multiple records by sample count.

2. Nearest-match modelling

If an exact record is missing, the engine finds nearby benchmarks for the same game, normalizes them for relative GPU/CPU performance, resolution and preset, and combines the strongest matches.

3. Confidence

Confidence reflects whether the configuration is a direct match, how close the supporting records are and how much sample coverage is available. It is not a guarantee of real-world accuracy.

4. Why real PCs differ

Drivers, game patches, memory speed, cooling, power limits, background processes, map/scene complexity and benchmark methodology can all change measured FPS. For that reason, FrameForecast should present ranges and 1% lows rather than imply a single number is universal.