Overwatch 2 Season 5: A Grim Doctrine Best Settings (2026)

Season 5: A Grim Doctrine dropped with new hero reworks, map tweaks, and rendering changes that shifted performance on most GPUs. The patch altered shadow LOD behavior and VRAM allocation — cards that previously cruised at 200+ FPS on ultra are now hitting 140-160 with the same settings. Competitive players on 240Hz+ displays need every frame, and the out-of-box presets still waste GPU headroom on visual elements that don't matter mid-fight.

This guide covers GPU-specific settings for Season 5 builds, confirmed on RTX 40-series, RTX 50-series, and Radeon RX 9000 hardware. We'll walk through the exact toggles that reclaim 60-90 FPS without touching visual clarity on enemy silhouettes or ability VFX — the two things that actually affect gameplay. If you want a hardware-matched playbook that auto-adjusts for your exact GPU and target refresh rate, run a free playbook at BetterFPS after reading the manual tweaks below.

What Season 5 Changed Under the Hood

The Season 5 patch changed how Overwatch 2 handles dynamic resolution scaling and model detail falloff at range. Blizzard added higher-res hero skins for the new mythic cosmetics, which forced the engine to keep more geometry in VRAM even when zoomed out. On GPUs with 8GB VRAM or less, this triggers mid-match texture streaming stalls — brief 1-2% lows that feel like micro-stutters during team fights. Cards with 12GB+ handle it fine, but the average frame rate still dropped 8-12% across the board compared to Season 4 on identical settings.

The shadow system now uses a different cascade resolution at medium and high — previously, medium was a clean step down from high, but now medium renders at near-high quality with only a 5-7 FPS cost instead of the old 15 FPS. High and ultra shadows are now nearly identical in visual fidelity but ultra costs an extra 18-22 FPS on most modern GPUs. That's the single biggest free gain in Season 5: dropping shadows from ultra to high or medium reclaims 20-25 FPS with no competitive disadvantage.

Tested GPU Benchmarks (Season 5 Patch)

VRLA Tech measured Season 5 performance on the new patch build across common GPUs. All tests used the Practice Range benchmark run (consistent bot movement, no network variance) at ultra preset, then optimized settings. These numbers represent the ceiling — real competitive matches run 10-15% lower due to ability spam and player density.

• RTX 5090 at 4K ultra: 228 FPS — tested by VRLA Tech. Optimized settings push this to 285+ FPS, but you hit CPU limits above 300 FPS even on a Ryzen 9800X3D.
• RTX 5090 at 1440p ultra: 385 FPS — tested by VRLA Tech. The 5090 is overkill for 1440p Overwatch unless you're driving a 500Hz display.
• RTX 4090 at 1440p ultra: 302 FPS — tested by VRLA Tech. Still the best pure-gaming GPU before the 5090, handles 360Hz monitors with headroom.
• RTX 4070 SUPER at 1440p ultra: 178 FPS — tested by VRLA Tech. Optimized settings hit 240+ FPS, making it a solid 240Hz pairing.
• RTX 4070 at 1440p ultra: 142 FPS — tested by VRLA Tech. Just barely misses 144Hz on ultra; optimized settings lock 165-180 FPS easily.
• RTX 4070 SUPER at 4K ultra: 104 FPS — tested by VRLA Tech. 4K Overwatch is uncommon in competitive, but if you run it, drop to high preset for 144 FPS stable.
• RTX 4070 at 1080p ultra: 202 FPS — tested by VRLA Tech. Strong 240Hz entry-level option; optimized settings clear 280 FPS.

If you're on an RTX 4070 or 4070 SUPER and chasing 240Hz, ultra preset won't cut it — you need the optimized layer. Cards below the 4070 (RTX 4060 Ti, RX 7700 XT) need aggressive low-medium presets at 1440p or will drop below 144 FPS in 5v5 team fights. The Overwatch 2 best settings guide covers legacy GPU tuning for older hardware.

Competitive Settings Breakdown (Season 5)

Overwatch 2 competitive settings prioritize three things: stable frame times above your refresh rate, clear enemy visibility, and ability VFX clarity. Everything else is negotiable. Here's the exact config that top-500 players and OWL teams converged on after Season 5 dropped, tested across RTX 40/50 and RX 9000 hardware.

Graphics Quality

• Render Scale: 100% (native). Don't touch this unless you're desperate — anything below 100% blurs enemy outlines and makes tracking harder. Dynamic render scale should stay OFF; it introduces frame time variance that feels worse than a lower locked frame rate.
• Texture Quality: High. Season 5 skins use more VRAM, but high textures still fit in 8GB cards. Ultra adds 2-3 GB VRAM usage for hero close-ups you never see in first-person. Epic is 12GB+ only.
• Texture Filtering: Epic - 16x. Costs 1-2 FPS but sharpens distant geometry. If you're on an 8GB card and seeing stutter, drop to Ultra - 8x.
• Model Detail: High. This controls hero polycount at range. Ultra costs 12-15 FPS and only affects replays and PotG cams. Medium starts to flatten facial features, which doesn't matter functionally but looks noticeably worse. High is the sweet spot.
• Effects Detail: Medium. This is the second-biggest FPS gain after shadows. Medium keeps ability VFX clear (Zarya bubbles, Ana sleep darts, Immortality field radius) but culls particle flourishes on environmental effects and duplicate explosion sprites. Ultra effects cost 18-22 FPS in team fights and add visual clutter that obscures actual threats.
• Lighting Quality: Medium. High and ultra lighting add real-time bounce light on hero models, which looks great in spawn room screenshots and costs 10-14 FPS in actual matches. Medium is static baked lighting — perfectly clear, no competitive disadvantage.
• Shadows: Medium or High. Ultra shadows are 20+ FPS for near-zero visual gain in Season 5. Medium is clean and costs almost nothing. High splits the difference at 5-7 FPS if you want slightly softer edges on shadow cascades. Low shadows are muddy and make floor-geometry read harder (Lijiang Garden bridges, Ilios Well edges).
• Refraction Quality: Low. Refraction is the shimmery heat-wave effect on barriers and some ults. It looks cool, costs 8-10 FPS, provides zero competitive info. Set it to low.

Advanced Settings

• Local Fog Detail: Low. Fog is atmospheric only — it doesn't indicate ability zones or hide enemies. Low fog costs nothing and clears sightlines slightly on maps like Eichenwalde finale.
• Dynamic Reflections: Off. Real-time reflections on shiny floors and barriers cost 6-9 FPS and provide zero gameplay info. Screen-space reflections are baked at medium quality regardless, so you still see basic reflection shapes — dynamic just adds real-time accuracy you don't need mid-fight.
• Local Reflections: Off. Same logic as dynamic. These are the close-up reflections on hero armor and weapon skins. Looks great in highlight intros, costs FPS, doesn't help you win.
• Ambient Occlusion: Off. AO darkens contact shadows between objects (corners, crevices). In theory it helps depth perception; in practice it costs 7-9 FPS and Overwatch's art style is so bold and color-coded that you don't need subtle shadow cues to read geometry. Turn it off.
• Anti-Aliasing: SMAA Medium or High. SMAA is fast post-process AA — medium costs 3-4 FPS, high costs 6-7 FPS, and both clean up jaggies well enough at 1440p+. At 1080p, SMAA High is worth it. Don't use FXAA or Off; jagged edges make tracking harder. Filmic SMAA T2X is the ultra preset — it's the best AA but costs 12-14 FPS and only matters if you're screenshot-hunting.
• Reduce Buffering: On. This is the instant input-lag win. On = 1 frame of render queue, Off = 3 frames. The cost is 2-4 FPS and occasional micro-stutter if your FPS is wildly unstable, but competitive players always run it On. If you see stutter with it On, your FPS is too variable — lock a frame cap.
• NVIDIA Reflex (NVIDIA GPUs only): Enabled or Enabled + Boost. Reflex cuts input latency by 10-15ms on compatible GPUs (GTX 1660 and newer). Boost pushes GPU clocks higher at the cost of 5-8% more power draw and heat. If your GPU is cool and you're not power-limited, use Boost. Reflex is off by default in Season 5 — turn it on.

Target FPS and Frame Caps

Overwatch 2 runs on a hybrid tick-rate system: server updates are 60Hz in competitive, but your client sends inputs at your frame rate. Higher FPS = lower input lag and smoother tracking, even above your monitor refresh rate. The competitive standard is 240 FPS minimum, 300+ FPS ideal. If you can't hold 240 FPS stable, cap at your refresh rate +20-30 FPS (so 165Hz monitor = 190 FPS cap) to prevent frame time spikes that feel like stutters.

Set your frame cap in-game: Options → Video → Frame Rate → Custom, then enter your target. Don't use Display-Based or Unlimited. Display-Based locks to your refresh rate exactly, which causes tearing if you drop a single frame. Unlimited lets your GPU spike to 600+ FPS in spawn and tanks to 180 in fights — the variance feels awful. A stable custom cap 20-30 FPS above your refresh gives you input-lag benefits of high FPS without wild frame-time swings.

On RTX 40/50 series cards, enable NVIDIA Reflex and set your cap just above your monitor refresh — Reflex dynamically manages frame pacing to minimize latency even with a cap. On AMD RX 9000, use Radeon Anti-Lag 2 (same concept) but set your cap slightly higher since Anti-Lag 2 is less aggressive than Reflex. Intel Arc B-series users should rely on manual capping; Arc doesn't have a Reflex equivalent yet.

CPU Bottleneck Check (Season 5 Specific)

Season 5 increased CPU load slightly due to new hero ability calculations (reworked Orisa, Sombra hack changes). If your GPU usage sits below 90% and your FPS isn't moving when you change graphics settings, check per-core CPU usage — not the aggregate percentage in Task Manager. Overwatch 2 is heavily bound by 2-3 cores; a 16-core CPU can show 12% total utilization while one core is pinned at 99% and bottlenecking you. Open Task Manager → Performance → CPU → right-click the graph → Change graph to → Logical processors. If any single core is locked near 100%, you're CPU-limited.

The most common CPU bottleneck in 2026 Overwatch is trying to hit 360+ FPS on older Ryzen 5000 or Intel 12th-gen chips. The game engine has a frame-rate ceiling around 400-450 FPS even on a Ryzen 9800X3D at 1080p low settings, and anything above 300 FPS is almost purely single-core frequency dependent. If you're on a Ryzen 7 5800X or Core i7-12700K and stuck at 240-280 FPS no matter what GPU you have, that's expected — you need a Ryzen 9800X3D or Core Ultra 9 285K to push higher. For 240Hz gaming, those older CPUs are still fine.

Hardware-Specific Playbooks

The settings above are universal starting points, but the optimal config shifts based on your exact GPU, target FPS, and resolution. An RTX 4070 chasing 240 FPS at 1440p needs different texture/shadow balance than an RX 7800 XT targeting 165 FPS, and manual tuning takes hours of A/B testing per patch. BetterFPS generates a hardware-matched playbook for your specific GPU and goal — it's free for your first playbook, and if you subscribe to Patch Watch ($4.99/mo), it auto-regenerates every time Blizzard pushes a major patch or NVIDIA/AMD drops new drivers that change performance profiles.

The free playbook gives you the exact in-game settings panel values (no guessing on sliders), config file tweaks for hidden options, and Windows/driver settings that affect Overwatch specifically (like shader cache behavior and GPU scheduling). If you run multiple games, Patch Watch covers every supported title — when Season 6 drops or Game Ready Driver 5xx.xx changes Overwatch behavior, your playbook updates automatically. That's the entire point of BetterFPS: settings that stay current without you hunting Reddit threads every patch.

For players who want the deep layer — overclocking, memory timing tweaks, .cfg edits, streamer dual-PC passthrough configs — Performance Pro ($9.99/mo) adds that on top of the core settings. Most Overwatch players don't need it; the free + Patch Watch combo is the sweet spot unless you're a top-500 grinder optimizing every millisecond. Check the pricing page for the full breakdown.

Frequently asked questions