WARDOGS best settings: what the requirements, the patch notes and the developer actually say about performance, DLSS, shadows, voice and input

The Steam listing states the target for each spec in its 'Additional Notes'. Minimum — Intel Core i5 8600 / AMD Ryzen 5 3500, 16 GB RAM, GTX 1660 / Radeon RX 590, Windows 10, 50 GB — targets '1080p Low @ 60fps (Upscaled)'. Recommended — Core i7 12700K / Ryzen 7 5700X, 16 GB, RTX 3070 / RX 6700 XT, Windows 11 — targets '1440p Medium @ 70fps+ (Native) or 4k Medium @ 60fps+ (Upscaled)'. Note the word 'Upscaled' on the minimum: BULKHEAD expects a GTX 1660 to hit 60 fps at 1080p only with an upscaler on.

So the first setting decision is the preset that matches your card: Low with upscaling on a 1660-class GPU, Medium at native 1440p on a 3070-class one. Everything below those presets is unmeasured territory.

The July 2026 'Level Design & Performance' devlog: 'Performance has been a priority for the entire team since day one… We've continuously optimised WARDOGS across a wide range of hardware. Graphics options let you tune the experience to YOUR PC.' The February FAQ explains the engine: 'Our custom WAR DYNAMICS FRAMEWORK enhances UE5 to handle high-density 100-player All Out Warfare!… we're heavily conscious of performance & input latency being a major factor in the feel of the game.'

Two things follow for settings. It is Unreal Engine 5, so the usual UE5 costs apply — shadows and global illumination are the expensive items, which is consistent with the changelog spending three lines on shadows. And the studio treats input latency as a feature, which is the argument against frame generation for competitive play; the changelog made that a toggle you can flip without restarting.

From 'Performance and stability' in the 9 September changelog, verbatim where it matters:

'DLSS Frame Generation can now be turned off without restarting, and the render target pool is configurable.' 'Reduced shadow cache refreshes, which cuts hitching when you take control of a character.' 'Shadow quality is now clamped to Low on high benchmark scores rather than being switched off entirely.' 'Fixed two crash paths in the frame generation pipeline.' 'GPU crash reports now carry more detail.' 'Removed a legacy graphics dependency.' 'Dropped items no longer affect navigation, which claws back a little performance.'

The shadow line is the interesting one: it says the game runs a benchmark, and that on very fast machines it was previously turning shadows off; now it floors them at Low. So if shadows look flat on a high-end PC, that is the auto-benchmark, and raising the setting by hand is the fix. The DLSS line says Frame Generation was a restart-gated toggle and is not any more — relevant because FG adds latency, which the studio itself flags as central to feel.

One practical reading of that list: the two settings BULKHEAD chose to make live-toggleable or auto-clamped — frame generation and shadows — are the two it considers most likely to be wrong for a given machine.

The Steam description promises that 'the world around you reacts to your presence' — 'Destroy apartment blocks with rocket launchers or tear your way through towns in heavily armoured tanks' — and the February FAQ describes the engine work as handling 'high-density 100-player All Out Warfare'. Those two facts are why the minimum spec is a 1660 with upscaling rather than a 1660 native: destruction and a hundred networked players are CPU and memory costs that graphics sliders do not touch. The changelog's 'Reduced shadow cache refreshes, which cuts hitching when you take control of a character' is a spawn-time stutter fix, and 'Dropped items no longer affect navigation' is a CPU saving; neither is a setting.

The devlog's line that 'playtesters consistently tell us how surprised they are at how well it already performs' is a claim, not a measurement, and the Season 1 changelog fixing 'a crash caused by network calls scheduled off the game thread' shows the network side was still being stabilised the day before launch. For the practical question — what preset — the honest answer stays the Steam table: Low upscaled on minimum hardware, Medium native on recommended, and the FG toggle as the one live lever the developer has drawn attention to.

Patch 0.11 says 'More GPU crashes addressed'; the changelog before it fixed 'two crash paths in the frame generation pipeline', a crash 'caused by network calls scheduled off the game thread', a crash 'when closing a chatbox entry tooltip', 'a crash involving buildables' and 'a crash when firing a weapon whose owner had left'. If you crashed in the beta, most of those are gone. If you still crash with Frame Generation on, the FG toggle is the setting to try first — it is the one component the studio has fixed crash paths in twice.

Crashes that settings will not fix: the anti-cheat 'error 1147405308 Access Denied' and the 'WD-L004' error that Steam community guides address by title, and the login/queue failures of launch day that the hotfix handled. The crashing page in the Early Access hub covers those separately.

Proximity voice is always on and squad voice is separate. The changelog: 'Fixed voice cutting out permanently after a failed join. Stale channel rejoins, push to talk targeting and re-login all recover properly now. Improved voice reliability under load, and added a visible communication status.' So there is a push-to-talk mode with a target (proximity or squad), a status indicator, and the launch build no longer requires a restart to recover voice after a bad join.

The quiet-microphone issue is real enough to have a trending Steam guide — 'WARDOGS – Low Microphone Volume / Mic Being Quiet Fix' — and a Russian-language one about voice not working over VPN. The official material does not document a mic-gain setting; if yours is quiet, the community guide is the resource, and Windows-level microphone boost is the usual UE5 workaround. We do not print steps we cannot source.

The one place the settings menu is documented by name is a player-written Steam forum FAQ (Grundy, 3 September 2026), which lists under Settings → Controls: Rotary Vehicle Mouse Control, Helicopter Mouse Swipe Left/Right and Up/Down, Invert Y Axis – Air Vehicle, Invert Y Axis – Infantry, Freelook on by Default, and the Flight Assists master switch with Stability Assist and Auto-Hover Assist. It also documents that the Delete key clears a binding, that some bindings are 'globally exclusive' across infantry and vehicles, and that spacebar carries a hidden helicopter weapon function. The helicopter page has the whole list.

BULKHEAD's pre-order post describes its '10 Reasons NOT to Buy' devlog as covering 'local VoIP and gamepad support', and the changelog says 'Helicopter input damping now applies to every input device' and fixed 'a DPI issue affecting tank aiming'. Those are the only official statements on input. The Steam listing carried no controller-support badge on 13 September. Search interest — 'best controller settings', 'joystick support', 'hotas' — outruns what is documented, so: gamepads are acknowledged by the developer, helicopters have damping on all devices, and nothing else is confirmed.

For mouse users, the tank DPI fix matters: if turret aim felt inconsistent between desktop and in-vehicle in the beta, that was a bug, not a setting.

Anti-cheat is now a documented setting-adjacent fact: the Steam store lists 'Uses Kernel Level Anti-Cheat: Elytra' with a required third-party EULA. A kernel driver that refuses to load — the forum thread 'The anti-cheat service refused the game executable' — is the failure mode the crashing page covers.

Windows only. BULKHEAD to GamingOnLinux, 5 September: 'We do not officially support Linux and we cannot commit to having support for launch. We are still working on Official Linux Proton compatibility.' No Mac. Consoles in 2028 per the launch trailer post. The changelog names DLSS Frame Generation, which implies DLSS upscaling; no source names FSR or XeSS, so we cannot confirm AMD or Intel upscalers even though the minimum spec includes an RX 590 and the target says 'Upscaled'.

Also unpublished: a field-of-view range, HDR support, ultrawide behaviour, and a settings-by-setting frame-time cost. The Steam Early Access Q&A promises that 'our ongoing priority will always be improving balance, performance, and stability'; the settings menu will change, and this page is dated so you can tell when it lags.