Why this matters
Most upgrade decisions fail because players compare only average FPS. This page adds 1% lows, 0.1% lows, headroom to target FPS, and bottleneck direction.
Best practices
- Run the same setup at 1080p, 1440p, and 4K to expose whether CPU or GPU limits first.
- Use average FPS together with 1% and 0.1% lows before deciding a setting is stable.
- Treat this output as directional and verify final settings with in-game benchmark or frame-time capture.
Use Cases
- Check if your current build can hit 144 or 240 FPS before changing hardware.
- Compare ray tracing and upscaling tradeoffs for the same game and resolution.
- Estimate whether your setup is CPU-bound or GPU-bound in different FPS targets.
Frequently Asked Questions
Is this the same as an in-game benchmark?
No. This is a directional FPS model for fast scenario planning. Use it to narrow options, then validate final choices with real benchmark runs.
Why can real FPS differ from this estimate?
Driver versions, map density, shader compilation, memory tuning, thermal throttling, and patch changes can all shift real performance.
How should I interpret 1% and 0.1% lows?
Average FPS tells throughput, while 1% and 0.1% lows reflect frame-time stability. If lows are far below average, gameplay can still feel inconsistent.
Does bottleneck direction change by resolution?
Yes. Lower resolutions often increase CPU pressure, while higher resolutions usually shift load to the GPU. Compare multiple resolutions to confirm.
Can I share this exact scenario with teammates?
Yes. Use Share Scenario to copy a URL with your current game profile, hardware scores, and graphics settings.