Notifications
Clear all
Topic starter
27/06/2026 9:16 pm
Benchmark screenshots are easy to post and hard to trust. If you want your results to be useful, include the method.
Minimum information for game benchmarks
- Game version.
- Preset and any manual overrides.
- Resolution and scaling mode.
- DLSS, FSR, XeSS, frame generation, and ray tracing status.
- Driver version.
- CPU, GPU, RAM, and whether the run was repeated.
For retro benchmarks, also include
- Operating system.
- API path where relevant.
- Patch level.
- Whether the run is period-correct or deliberately cross-era for comparison.
Report more than one number when possible
- Average FPS is not enough when frame pacing is the real issue.
- If you can, include 1% low or frame-time behavior and note the capture tool.
What weakens a result
- No settings list.
- No driver version.
- Thermals not stabilized.
- Background tasks changing from run to run.
- Claiming a win without matching image quality or workload.
Good methodology does not need to be complicated. It just needs to be repeatable and honest.