The current answer
Use the official hardware tier as a starting point: minimum targets 1080p Low at 60 FPS upscaled; recommended targets 1440p Medium at 70+ FPS native or 4K Medium at 60+ FPS upscaled. These are developer targets, not results measured on this site. Start with a baseline, change one setting at a time and keep only improvements you can repeat in a comparable match.
- Minimum GPU
- GTX 1660 / RX 590
- Recommended GPU
- RTX 3070 / RX 6700 XT
- Memory
- 16 GB
- Storage
- 50 GB
PC requirements
Minimum and recommended performance targets
Match both the CPU and GPU tier before choosing a starting target. A faster GPU alone does not make a minimum-tier CPU equivalent to the recommended system. Read the full storage, operating-system and hardware checklist on the system requirements page.
The launch build can change graphics options and performance. The table gives official hardware targets; it is not a measured preset for every map, server or PC.
| Tier | CPU | GPU | OS | Target |
|---|---|---|---|---|
| Minimum | i5-8600 / Ryzen 5 3500 | GTX 1660 / RX 590 | Windows 10 | 1080p Low, 60 FPS upscaled |
| Recommended | i7-12700K / Ryzen 7 5700X | RTX 3070 / RX 6700 XT | Windows 11 | 1440p Medium 70+ native or 4K Medium 60+ upscaled |
- Check the full system requirements Compare your CPU, GPU, memory and storage before changing graphics.
First comparison
Save a baseline before changing graphics
Steam can distinguish generated frames from the base game frame rate when the relevant data is available. Record those separately: a larger displayed FPS number does not by itself show that input response or frame pacing improved. If your monitor cannot report 1% lows, leave that field unmeasured rather than guessing it.
- Write down your game build, CPU, GPU, RAM, graphics driver, display resolution and current preset. Photograph or capture the existing options so you can restore them.
- In Steam, open Settings → In Game and enable the Performance Overlay. Choose a readable level of detail and place it away from the aiming area. Available metrics vary by system; a missing metric is not a zero reading.
- Start with the closest official hardware target. Where the current game menu offers upscaling, record its actual mode separately from output resolution; do not assume that a target labelled “upscaled” specifies one particular DLSS or FSR version.
- Once a playable build is available, use a short repeatable route with both an open view and a busy fight. Keep the map, route, duration and approximate match population comparable. A quiet menu or empty firing range is not your multiplayer result.
- Run the baseline, change one graphics option or one preset step, then repeat. Repeat the original setup once more before attributing a small difference to the setting; another explosion, vehicle or group of players can change the result.
- Keep the change only if movement stays readable and the improvement repeats. If it does not, restore the baseline before trying a different setting. Test infantry, vehicle control and UI readability again after settling on graphics.
Performance comparison
Choose the next test from the symptom
Use the same route and build for each comparison. The observations below narrow a problem; none identifies its cause on its own. A disconnect or authentication message belongs in connection troubleshooting rather than a graphics preset test.
| What you notice | Check first | Small next test | What would count as useful |
|---|---|---|---|
| FPS is low in most scenes | Output resolution, GPU load and current upscaling mode | Lower resolution or one available upscaling quality step; keep other settings fixed | A repeatable improvement without losing target or text clarity |
| FPS drops mainly in busy fights | CPU/GPU load, match population and the same route | Compare the original setup with one lower available graphics preset | Better frame pacing in another similarly busy pass, not just an empty view |
| Short freezes while turning or changing equipment | Frame-rate graph and available system/video-memory readings | Close an unnecessary background program, then repeat before changing textures | Fewer repeatable hitches; avoid claiming a memory fault from a single spike |
| Average FPS looks fine but mouse movement feels uneven | Frame pacing, base versus generated FPS, current frame limit and sync options | Keep graphics fixed and compare one available frame-limit or sync option | More consistent response without unacceptable tearing or uneven pacing |
| Players jump position or actions arrive late | Whether the local frame-rate graph also drops; any displayed connection warning | Check another available server under similar load before treating it as a GPU issue | The symptom changes with the connection while local rendering remains comparable |
| The game exits or displays an error | Exact message, build and whether it happens at startup, loading or in a match | Follow the matching troubleshooting branch; retain the error text | A reproducible cause or supported next step, not a claimed FPS fix |
- Separate crashes and connection errors Start from the stage where play stops, not a generic graphics fix.
Input and clarity
Tune FOV, sensitivity and audio as separate tasks
There is no verified universal FOV, sensitivity, upscaler mode or footstep-volume preset for the Early Access build in this guide. The useful choice is a configuration you can control and repeat on your own display and input device. Use only the controls present in your current menu.
For FOV, start from the current default, then compare one small change at the same position. Check whether a distant target is still easy to identify, whether nearby movement remains visible and whether the view is comfortable. Recheck FPS with the wider view; do not choose a value purely because another player uses it.
For mouse sensitivity, keep DPI and FOV fixed while changing the in-game slider. Pick a fixed object, turn away by the same amount and return to it several times. Repeated overshoot is a reason to try a lower value; difficulty turning far enough is a reason to try a higher one. Test aimed movement separately if your current build has an ADS control. Do not copy another game’s number as a conversion.
For audio, confirm that Windows and the game use the intended headphones or speakers. Test left/right direction with the same repeatable sound before changing several sliders. Keep voice communication understandable alongside game sound; increasing overall volume is not proof that footsteps or distance cues became clearer.
Check controls again when switching from infantry to helicopters or a gamepad. Keep a separate record of those changes so a vehicle-control problem does not lead you to retune mouse aim unnecessarily.
Continue with hardware and input setup
- System requirements Compare the Windows PC specification tiers, identify your hardware, and understand the resolution and frame-rate targets before changing graphics settings.
- Controller support Set up a gamepad for the tasks you actually need: infantry movement, inventory, communication and vehicles. Keep a keyboard available during the pre-release builds.
- HOTAS setup Build a usable flight layout around four controls, then test device detection, neutral positions and the transition back to infantry.
- Steam Deck Start with SteamOS compatibility, then check controls, readable menus and real match performance. An older Beta video does not certify the launch build.
- Troubleshooting Start with the point where play stops. Entitlement, installation, server availability, controls and performance need different checks.
Direct answers
Frequently asked questions
What are the best settings for WARDOGS?
Start from the official target closest to your CPU and GPU, record the baseline and compare one change in a similar real match. This guide does not claim a tested Early Access preset; the useful result is stable, readable play on your own hardware.
How do I display FPS and system load?
In the Steam client, open Settings → In Game and enable the Performance Overlay. Choose the detail level you need. Some measurements depend on your system, and generated FPS should be recorded separately from the base game rate when both are shown.
Should I lower everything if WARDOGS stutters?
First compare the frame-rate graph, available memory readings and the scene where the hitch happens. Change one available setting or close one unnecessary background program, then repeat. Lowering every option at once makes it harder to learn what actually helped.
What FOV or mouse sensitivity should I use?
No single number is verified for all players here. Keep DPI fixed, begin at the current default and adjust one control at a time. Check distant target clarity, comfortable turning and repeated overshoot before keeping a change.
Which DLSS or FSR mode is best?
The official targets distinguish native and upscaled output but do not define one universal upscaler preset. Check the modes your current game menu and GPU actually offer, then compare output clarity and frame pacing at the same resolution.
How much RAM does WARDOGS need?
Steam lists 16 GB for both minimum and recommended specifications. That is a requirement, not a claim that every other running program can share that memory without affecting play.
How much storage does WARDOGS need?
Steam lists 50 GB of available storage. Required free space is not necessarily the exact download size.