Home › Best Settings
WARDOGS Best Settings — FPS, Graphics & Requirements
Season 1 Early Access · menu names are build- and driver-sensitive
There is no honest universal preset for WARDOGS — a CPU-limited machine in a 100-player fight behaves nothing like a GPU-limited machine at 4K. What works: official targets as the baseline, a repeatable test, and one setting group changed at a time. That's this guide.
Official PC Requirements
| Minimum | Recommended | |
|---|---|---|
| Target | 1080p Low · 60 fps (upscaling) | 1440p Medium · 70+ fps native / 4K Medium 60+ fps (upscaling) |
| GPU | GTX 1660 / RX 590 class | RTX 3070 / RX 6700 XT class |
| Memory | 16 GB | 16 GB |
| Storage | 50 GB | 50 GB |
Potato Mode and Overkill Mode
BULKHEAD's official performance devlog introduces Potato Mode for lower-end hardware, Overkill Mode for high-end systems, and a 60+ FPS minimum development target. These are official concepts — but not a per-PC guarantee:
- Potato Mode: your starting point on older GPUs, not your finish line. Still test readability — an image too soft to see distant movement costs more than the frames save.
- Overkill Mode: for screenshots and systems with proven headroom. Maximum settings are not automatically competitive settings.
Competitive Settings Priorities
- Frame-time consistency over average FPS. A stable 60 beats a spiky 90 when the building collapses — that's when fights are decided.
- If GPU-limited: reduce resolution scale/upscaling quality carefully → shadows → effects → post-processing. Don't gut textures and view distance first — they're your information.
- Visibility is a setting. Very low effects reduce clutter, but over-softened upscaling hides distant players. Judge settings by whether you can read movement at the ranges you fight.
- Disable motion blur and film-style effects if they hurt target tracking. FOV: pick a value you can aim with consistently, not the maximum number.
How to Test Properly
- Update GPU drivers, restart, close overlays (keep voice chat if that's your real setup).
- Test in a populated Control Zone — vehicles, smoke, destruction and construction all in view. An empty training field proves nothing about match performance.
- Watch for hitches, input delay and worst sustained moments — not the peak number while standing still.
- Change one group of settings at a time; repeat the same kind of fight before judging.
CPU, GPU or Network?
| Symptom | Likely Cause | Fix |
|---|---|---|
| Lowering resolution → big FPS gain | GPU-limited | Resolution scale, shadows, effects |
| Resolution changes little; busy fights still drop | CPU / simulation-limited | Close background apps; check clocks & temps |
| Rubber-banding, delayed hits, FPS fine | Network | Wired connection; check official server status posts |
FAQ
- What settings for a GTX 1660?
- Start at Steam's minimum target: 1080p Low with upscaling, 60 fps. Verify in a crowded objective, then climb one group at a time.
- Does Potato Mode guarantee 60 fps?
- No — it's an official low-end mode, but hardware, scene and build conditions still decide. Test it in real fights.
- Should an RTX 3070 use Overkill Mode?
- Not by default. The official recommended target for that class is Medium. Try Overkill only with proven stable headroom.
- Why is FPS fine at spawn but bad in battle?
- Large fights add players, vehicles, effects, destruction and construction. Benchmark the busy zone, not the safe area.
Sources: official Steam requirements table, BULKHEAD's performance devlog (Potato/Overkill modes, 60+ fps target), Season 1 benchmark walkthroughs. Results are per-system.