Overwatch 2 refreshed the original with an engine update focused on larger maps and better lighting, while maintaining excellent optimization. The shift to a 5v5 format slightly reduced the visual clutter, helping with frame rate stability. NVIDIA Reflex is essential for reducing latency, supported on GTX 900 series and up. While minimum specs are low, competitive play at 144Hz+ requires a reasonably modern CPU (Intel Skylake / Ryzen Zen 1 or newer) to handle the fast-paced physics and game state updates.
Actual FPS may vary based on RAM speed, background processes, and other system factors
Performance Report
At 1080p, frame rates range from 15 to 31 FPS depending on quality settings. At 1440p, frame rates range from 8 to 23 FPS. At 4K, frame rates range from 5 to 15 FPS.
The GeForce GTS 160M is 64% below minimum GPU requirement for Overwatch 2. The Ryzen 7 7800X3D is 278% above the recommended CPU (Core i7-4770).
The GeForce GTS 160M sets the FPS ceiling at all 1080p settings, all 1440p settings, all 4k settings, while the Ryzen 7 7800X3D still has additional frame-generation headroom.
Approximated average price on current market:
Combo price: $414. At 1080p Ultra, this combo delivers 15 FPS, equivalent to 0.04 FPS per dollar.
| Resolution | Low | Medium | High | Ultra |
|---|---|---|---|---|
| 1080p | 0.075 fps/$ | 0.058 fps/$ | 0.048 fps/$ | 0.036 fps/$ |
| 1440p | 0.056 fps/$ | 0.043 fps/$ | 0.027 fps/$ | 0.019 fps/$ |
| 4k | 0.036 fps/$ | 0.029 fps/$ | 0.017 fps/$ | 0.012 fps/$ |
* Table values represent FPS per Dollar (higher is better)
This section is based on estimated CPU/GPU FPS ceilings, not utilization percentages.
At 1440p high, the GeForce GTS 160M sets the ceiling at about 11 FPS, while the Ryzen 7 7800X3D has headroom up to 500 FPS. In this scenario, the GPU limits the CPU potential by 98% (FPS gap: 489 FPS). Overall distribution: GPU limits 12/12 cells, CPU limits 0/12, balanced 0/12.
Your GeForce GTS 160M is the limiting side in the heaviest mismatch. This means part of the Ryzen 7 7800X3D frame-generation potential remains unused in those settings.
| Resolution | Low | Medium | High | Ultra |
|---|---|---|---|---|
| 1080p (Full HD) | GPU Limits CPU 95% | GPU Limits CPU 96% | GPU Limits CPU 96% | GPU Limits CPU 97% |
| 1440p (2K QHD) | GPU Limits CPU 96% | GPU Limits CPU 97% | GPU Limits CPU 98% | GPU Limits CPU 98% |
| 4K (Ultra HD) | GPU Limits CPU 96% | GPU Limits CPU 96% | GPU Limits CPU 98% | GPU Limits CPU 98% |
We estimate the maximum FPS the processor can sustain and the maximum FPS the graphics card can sustain in each setting, then compare those limits directly.
Limit Factor formula: (stronger - weaker) / stronger. Example: if CPU ceiling is 200 FPS and GPU ceiling is 140 FPS, then GPU limits CPU by 30%.
CPU Limits GPU means the processor ceiling is lower. GPU Limits CPU means the graphics ceiling is lower. Balanced means the FPS ceilings are close enough that the gap is negligible.
A component can still be the FPS limiter without reaching 100% utilization. The displayed percentages are derived from FPS ceilings, not generic utilization heuristics.
| Resolution | Low | Medium | High | Ultra |
|---|---|---|---|---|
| 1080p (Full HD) | CPU11% - 27% <> GPU94% - 100% <> | CPU11% - 27% <> GPU93% - 100% <> | CPU11% - 27% <> GPU93% - 100% <> | CPU11% - 24% <> GPU93% - 100% <> |
| 1440p (2K QHD) | CPU8% - 24% <> GPU92% - 100% <> | CPU8% - 24% <> GPU91% - 100% <> | CPU8% - 24% <> GPU91% - 100% <> | CPU8% - 21% <> GPU92% - 100% <> |
| 4K (Ultra HD) | CPU9% - 28% <> GPU92% - 100% <> | CPU9% - 28% <> GPU91% - 100% <> | CPU9% - 28% <> GPU91% - 100% <> | CPU10% - 26% <> GPU92% - 100% <> |
The Ryzen 7 7800X3D + GeForce GTS 160M pairing runs this title with CPU utilization between 8% and 28% and GPU utilization between 91% and 100%. Ryzen 7 7800X3D keeps significant headroom across presets, while GeForce GTS 160M carries most of the graphics load at heavier visual settings. As resolution scales, average GPU load rises from 96% at 1080p to 96% at 4K, while CPU averages move from 19% to 18%.
From a utilization perspective, this is a GPU-heavy load profile. At 1080p (Full HD) Low, the GeForce GTS 160M averages 97% usage (94-100%), while the Ryzen 7 7800X3D stays at 19% (11-27%). This shows the graphics pipeline is carrying most of the workload, but utilization alone does not define the FPS limiter.
At 1080p, averages sit around CPU 19% and GPU 96%. At 1440p, that shifts to CPU 16% and GPU 96%, and at 4K it reaches CPU 18% and GPU 96%. This shows that workload scaling is limited, which can indicate engine-side constraints.
1080p (Full HD) Medium is the most balanced preset based on this dataset. It runs around CPU 19% (11-27%) and GPU 96% (93-100%), which keeps GeForce GTS 160M well utilized without constant max-out behavior while Ryzen 7 7800X3D remains stable for consistent frame delivery.
Upgrade priority should be the GPU. The GeForce GTS 160M reaches 97% average load at 1080p (Full HD) Low while the Ryzen 7 7800X3D still has headroom, so a faster graphics card would deliver the largest uplift.
Understanding Hardware Utilization: These percentages represent how much of your component's maximum processing power is actively being used during gameplay. They describe hardware load, but they do not directly tell you which component sets the FPS ceiling.
Important: a CPU or GPU can still be the FPS limiter without reaching 100% utilization. Two processors can both show 40% usage and still deliver very different frame rates, depending on per-core speed, cache, engine threading, driver overhead, and frame preparation efficiency.
Data generated by our Machine Learning engine trained on real-world benchmarks. Shows the approximate average utilization at each setting.
See how your processor and graphics card compare against the game official minimum and recommended system specs. The placement of your hardware is calculated using relative synthetic performance scores to help you gauge overall playability.
Your hardware is below minimum requirements. GPU is the limiting factor (64% below minimum). Expect performance issues. Low settings recommended.
+278%vsrecommended
-93%vsrecommended
+1988%vsminimum
-64%vsminimum
The Ryzen 7 7800X3D and GeForce GTS 160M will struggle to run Overwatch 2 at smooth framerates. At 1080p Ultra, you can expect around 15 FPS which is classified as "struggling". Consider lowering settings or upgrading your hardware.
This CPU + GPU combo costs approximately $414 ($384 CPU (Rank #212 Value) + $30 GPU). Since the GPU is the main limiting factor, investing in a stronger GPU will improve your framerates and overall value. For example, upgrading to the GeForce GTX 1080 SLI (móvel) (Rank #2 for value) could deliver noticeably better performance.
For Overwatch 2, upgrading the GPU would give you the most noticeable improvement. The GeForce GTS 160M is the limiting factor here, while the Ryzen 7 7800X3D still has spare capacity. A more powerful GPU would unlock higher FPS, especially at higher resolutions and quality presets. GPU-limited at: 1080p low, 1080p medium, 1080p high, 1080p ultra, 1440p low, 1440p medium, 1440p high, 1440p ultra, 4k low, 4k medium, 4k high, 4k ultra.
Overwatch 2 does not currently support Frame Generation technologies like DLSS 3 or FSR 3. Your performance is based entirely on native rendering. If the game adds support in a future update, newer GPUs will benefit the most.
Overwatch 2 requires at minimum a Core i3-560 (CPU) and GeForce GTX 600 series (GPU) with 6 GB RAM and 50 GB storage. For the recommended experience, you need a Core i7-4770 and GeForce GTX 1060 with 8 GB RAM. Your hardware falls below the minimum requirements for this game, which may result in poor performance.
These Overwatch 2 FPS results are not arbitrary numbers. They come from calculations informed by thousands of real gaming benchmarks, and the typical accuracy range is around 10% to 15%. That makes them far more useful than generic FPS calculators that simply invent values without a benchmark foundation. Actual in-game performance can still vary with drivers, updates, RAM configuration, cooling, and the exact scene being rendered.
Performance estimates are based on synthetic benchmarks and hardware capabilities.
Results may vary based on drivers, OS, and background processes.
