Field manual

Can your PC run it?

The official spec table hides its biggest caveat in the footnotes: both tiers target only 1080p / 60 fps, and both assume upscaling is on. Check your hardware against the two official anchors below — no third tier invented.

30-second self-check

Your GPU vs the official anchors

Your CPU vs the official anchors

RAM

Verdicts only compare your picks against the two official tiers published on Steam — nothing is extrapolated. Also required either way: 64-bit Windows 10/11, DirectX 12, 30 GB storage, broadband (online-only game).

The official table (Steam store page)

	Minimum	Recommended
OS	Windows 10 64-bit	Windows 11 64-bit
CPU	Intel i5-10600K / AMD Ryzen 5 3600X	Intel i5-12600K / AMD Ryzen 5 7600X
RAM	16 GB	16 GB
GPU	Nvidia RTX 2060 Super / AMD RX 6600 XT	Nvidia RTX 3060 Ti / AMD RX 6900 XT
DirectX / Storage	12 / 30 GB	12 / 30 GB
Official target	1080p/60 — TSR 71% or DLSS Ultra Performance	1080p/60 High — TSR 100% or DLSS Balanced

Copied verbatim from the official Steam store page, Aug 8, 2026.

What "minimum" really means

At minimum spec the 1080p/60 target assumes DLSS Ultra Performance — internally the game renders far below 1080p. Even the recommended tier promises 60 fps only at 1080p with upscaling. If you play at 1440p/4K or want high refresh, treat the recommended row as your floor, not your goal.

What the beta showed: 100-player servers hit the CPU

This is a UE5 game where a full server means 100 live humans plus helicopters, boats and tunnels — and the May open beta's performance megathread (102 replies) ran well below what the spec table implies: an RTX 4060 Ti + i5-11600K reported ~60 fps on low in full servers, and a 3080 Ti + i7-12700K saw 55–70 fps on low with only 50–70% GPU usage — the classic signature of being CPU/engine-bound in mass fights. Press coverage echoed the beta's performance complaints. Two honest caveats: the devs said some beta video settings were bugged, and the beta also shipped a 60 Hz refresh-rate lock in the config that made everything feel worse than raw fps. Team17's own pre-launch blog says over 300 bugs were fixed and performance/stability improved across the board since that beta.

Official launch-week performance notes (Team17 blogs, Aug 12–16):

AMD GPU instability is a known issue at launch (driver-related). Temporary workarounds Team17 suggests: add -dx12 -USEALLAVAILABLECORES -malloc=system to your Steam launch options (or -dx11 -USEALLAVAILABLECORES -malloc=system if that doesn't help), set in-game graphics to High, and disable the in-game overlay in AMD Software: Adrenalin Edition. Update (Aug 16): Hotfix 1 is confirmed live as of Aug 16, 2026 10:00 UTC and includes further AMD GPU stability improvements per Team17's official notes. Team17 hasn't said whether the manual launch-option workaround above is now redundant, so we're leaving it up until a player confirms it's no longer needed — and we're still seeing scattered fresh AMD crash reports as of Aug 17, so treat this as improved, not necessarily solved. One concrete post-Hotfix-1 example: an RX 7600 owner reported a GPU crash dump on launch with every boot-option combination tried (default, -dx12, and -dx11 all crashed), and a second player replied confirming the same failure on their own system (Aug 16 report thread) — so the launch-option workaround isn't a guaranteed fix for everyone. A second AMD symptom also outlasted the hotfix: white texture flickering/ghosting on the ground, reported at launch on a 7800 XT (a separate Aug 14 report described the same symptom but its GPU model was garbled by a typo, so we're not citing that one as a specific model), and still happening to a 9070 owner roughly six hours after Hotfix 1 shipped; another player in the same thread says disabling the in-game overlay in AMD Software: Adrenalin Edition fixed it for them (flickering report thread, active Aug 14–17).
FSR is not available at launch. FSR 4.1 is implemented but still being tested; it's coming in a future update.
The dedicated NVIDIA Game Ready Driver was delayed at NVIDIA's end — expected "early next week" as of Aug 14. Use your latest existing driver in the meantime.
If you played the Crossplay Playtest on PC, Team17 recommends resetting your video settings to default so they recalibrate correctly for the launch build.

Post-hotfix crash cluster (community reports, Aug 18): a fast-growing "Crashing after hotfixes" thread (29 replies in its first day) collects at least 11 different players reporting crashes that began after the hotfixes — mid-match crash-to-desktop, black screen with no display signal, or freezing on the loading screen — and notably on both vendors: NVIDIA (RTX 5070, 5070 Ti, 5080) and AMD (RX 9070 XT, 7900 XTX). Posters explicitly report that updating drivers and clearing the shader cache did not help; one player mentioned the -dx11 launch option helping them, but that's a single uncorroborated report. In a separate thread, two players posted UE5 crash logs showing the same EXCEPTION_ACCESS_VIOLATION error. Team17's pinned Aug 17 "Server Stability Update" confirms they're aware of new post-Hotfix-1 crash reports and investigating (details on our server status page); the Aug 18 Patch 1.2 preview promises broad stability fixes but names no specific client-crash fix yet.

Sources: official Steam store page · official "Known Issues, Launch Time & More" blog (Aug 12) · official "Important Launch Info" blog (Aug 14) · official "Dev Comms Thread & Launch Updates" (live-updated thread, checked Aug 17)

Last verified Aug 19, 2026 ~04:30 UTC — added the post-hotfix crash cluster: "Crashing after hotfixes" thread (29 replies, 11+ independent reporters across NVIDIA RTX 50-series and AMD RX 9070 XT / 7900 XTX, driver updates and shader-cache clears reported ineffective) plus a separate thread with two matching UE5 EXCEPTION_ACCESS_VIOLATION crash logs; both threads re-checked against source this round. Prior round (Aug 18 ~04:25 UTC) verified the 7800 XT / 9070 white-flicker reports and AMD-overlay workaround word-for-word against thread 631219091886124248. Spec table from Steam Aug 8; Hotfix 1 confirmed live Aug 16 10:00 UTC.