WARDOGS performance problems do not all come from the same setting. Poor enemy visibility can be caused by lighting and post-processing, heavy input can come from frame delivery or mouse options, and stutter can remain even after the average FPS looks healthy. This WARDOGS settings guide uses the final Beta 02 menu, including its open-beta phase, as its practical baseline and separates graphics tuning, visibility, input, and troubleshooting instead of treating every problem as a reason to select Potato.
The most useful starting point is a Custom profile with native resolution when possible, VSync disabled, a Quality upscaler only when the GPU needs it, Mesh Detail at Medium or High, View Distance at High, Global Illumination disabled for the performance profile, Shadows at Low, and unnecessary camera effects disabled. That is a starting profile, not an FPS guarantee. WARDOGS enters Early Access on September 10, 2026, so Beta 02 option names and performance behavior should be checked again after the Early Access build replaces the playtest client.
Test Build and Hardware
The settings below are tied to the September 3-6, 2026 Beta 02 build. The test began as Closed Beta 02 on September 3 and was opened to everyone on September 5 until it ended at 08:00 UTC on September 6. BULKHEAD's official Steam page lists Early Access for September 10 and also publishes unusually specific performance targets. Those official targets are a better hardware sanity check than comparing your PC with a random screenshot from a quiet firing range.
Beta 02 was a scale test, and the Early Access build can change shaders, presets, driver behavior, hidden quality values, and individual menu entries. Treat the exact Beta 02 menu as a verified pre-launch snapshot rather than a permanent settings list. The existing WARDOGS game overview covers the larger game structure if you need context for why 100-player Control Zone fights create a different load from an empty practice area.
The official hardware targets are useful because they state resolution, quality, and whether upscaling is part of the target:
| Tier | CPU | GPU | Memory | Official Target |
|---|---|---|---|---|
| Minimum | Intel Core i5-8600 or Ryzen 5 3500 | GTX 1660 or RX 590 | 16 GB | 1080p Low at 60 FPS, upscaled |
| Recommended | Intel Core i7-12700K or Ryzen 7 5700X | RTX 3070 or RX 6700 XT | 16 GB | 1440p Medium at 70+ FPS native |
| Recommended 4K path | Intel Core i7-12700K or Ryzen 7 5700X | RTX 3070 or RX 6700 XT | 16 GB | 4K Medium at 60+ FPS, upscaled |
The minimum target already assumes upscaling, which matters when diagnosing a weaker GPU. If a GTX 1660 class system is being tested at native 1440p, the comparison is outside the published minimum target before any individual slider is changed. The same logic works in reverse: a high-end GPU that still hitches at every building entrance may have a frame-time, streaming, driver, or build-specific problem rather than a simple lack of rendering power.
Graphics Options
Beta 02 exposed enough individual controls to tune WARDOGS without relying on the all-or-nothing presets. Observed Display controls included Display Mode, Resolution, Brightness, Sharpness, Frame Limit, VSync, NVIDIA Reflex, Main Menu FPS Limit, Anti-Aliasing Method, and upscaler mode. The Quality page included Mesh Detail, View Distance, Shading, Global Illumination, Shadows, Reflections, Effects, Particle Spawn Rate, Post-Processing, Motion Blur, Depth of Field, Lens Flare, Bloom, World and Character texture quality, Texture Effects, Texture Streaming, and Texture Filtering.
BULKHEAD has said in its Level Design and Performance devlog that performance has been a priority across a wide range of hardware and that players can tune the graphics to their PC. The developer has not published a final Early Access table declaring one ideal value for every option, so the profiles below are editorial starting points built from the Beta 02 menu, the official hardware targets, and repeated player feedback.
For upscaling, Beta 02 captures consistently show NVIDIA DLSS and AMD FSR paths. Player reports also reference XeSS on supported systems. Frame Generation was available on at least some compatible RTX setups, but its availability was hardware and configuration dependent during testing. One beta report from an RTX 4080 owner found Frame Generation grayed out until the in-game FPS limit was disabled. That is useful troubleshooting evidence, but it is not a guarantee that the Early Access menu will behave identically.
Use the following profiles as controlled starting points rather than permanent commandments:
| Setting | Balanced Visual and Performance | Competitive Visibility | Why Change It |
|---|---|---|---|
| Resolution | Native | Native | Preserves distant target clarity; use an upscaler before cutting panel resolution aggressively |
| VSync | Off unless tearing is a problem | Off | Avoids an extra synchronization step when low input latency is the priority |
| NVIDIA Reflex | Enabled when available | Enabled when available | Use the in-game latency option on supported NVIDIA hardware |
| Upscaling | Native or Quality | Quality, then Balanced only if needed | Quality mode is the safer first compromise for image clarity |
| Frame Generation | Test only after the base frame rate is stable | Off for baseline testing | Generated frames can improve smoothness but do not remove base render latency |
| Mesh Detail | High | Medium or High | Players repeatedly report better foliage and geometry readability above the lowest values |
| View Distance | High | High | Long-range identification matters on large Control Zones |
| Shading | Medium | Medium | Keeps scene definition without making it the first performance sacrifice |
| Global Illumination | On if the GPU has headroom | Off | Large visual difference and a common performance and visibility tradeoff in Beta 02 |
| Shadows | Medium | Low | Low is a stronger compromise than Potato if you still want the scene to look coherent |
| Reflections | Medium | Low | Usually less useful to target acquisition than mesh and view distance |
| Effects | Medium or High | Medium | Keeps destruction and combat readable without maximizing every effect |
| Particle Spawn Rate | Medium | Low | Reduces visual density during explosions and busy fights |
| Post-Processing | Medium | Low | A practical place to reduce cosmetic image processing |
| Motion Blur | Off | Off | Keeps fast camera movement clearer |
| Depth of Field | Off or preference | Off | Avoids intentional blur when scanning distant targets |
| Lens Flare | Off or preference | Off | Reduces bright-screen clutter |
| Bloom | Low or preference | Off | Controls glow around bright surfaces without affecting geometry |
| World and Character Textures | High if VRAM is stable | Medium or High | Lower textures for VRAM pressure, not automatically for every FPS problem |
| Texture Streaming | Default or Medium | Medium, lower only when testing streaming pressure | Changing it blindly may not fix a hitch that is unrelated to asset streaming |
If your goal is the best visual-to-performance ratio rather than the most stripped competitive image, start from the Balanced column and lower Global Illumination, Shadows, Reflections, and Post-Processing one at a time. Do not immediately cut Mesh Detail, View Distance, and every texture option together, because you will not know which change actually helped. Players who want someone to review whether a problem is technical or gameplay-related can use WARDOGS coaching alongside their own settings tests, but the article's profiles are designed to be usable without outside help.
Get any Wardogs service from ExpCarry: raids, dungeons, PvP, leveling, gold, farming, coaching, and custom orders.
Visibility
Visibility is the most controversial part of WARDOGS graphics tuning because the lowest settings can change how easy it is to read enemies, windows, foliage, and dark interiors. The strongest Beta 02 community pattern is not simply "everything low." Players repeatedly recommend keeping Mesh Detail at Medium or High and View Distance high, while lowering lighting and post-processing that darken or clutter the scene.
Global Illumination is the clearest example. With it enabled, interiors and indirect lighting look much more natural. With it disabled, several Beta 02 players reported both better performance and brighter sightlines into buildings. A separate debate formed around Potato Shadows because the setting can make interiors and outdoor cover much easier to read. For a normal balanced setup, Low Shadows are a better starting point than Potato. Potato remains a fallback for weak hardware or an intentionally maximum-visibility profile, but it sacrifices a large amount of visual quality.
The Beta 02 graphics settings discussion contains useful player measurements, but these results are not interchangeable benchmarks. Different locations, player counts, vehicles, upscalers, and background loads can move the result significantly. Numerical examples are included only where the player supplied enough hardware and test context to make the number meaningful:
| Reported Hardware | Reported Test Setup | Reported Result | What It Actually Tells You |
|---|---|---|---|
| RX 7900 XTX, Ryzen 9 7950X3D | 4K, FSR Performance, High except Mesh Detail and Post-Processing at Medium | About 100-135 FPS depending on location, players, vehicles, driving, and flying | Busy match conditions can move performance widely even without changing the preset |
| RTX 2080 Super, Ryzen 7 5700X3D, 32 GB RAM | 1440p, player-described DLSS medium, Shadows Low, other settings mostly Potato | 60-80 FPS; the same player reported roughly 10 FPS less when moving Shadows from Potato to Low | Shadow quality can matter on that specific older GPU, but the 10 FPS change is not a universal promise |
| RX 9070 XT, Ryzen 7 9800X3D, 32 GB RAM | Firing Range, High settings, FSR Quality, Shadows and Reflections Low, no Frame Generation | 150-180 FPS while flying in the firing range | Useful as a controlled high-end practice-area result, not as a prediction for a full 100-player match |
| RTX 4080 Super, Ryzen 7 9800X3D | 1440p ultrawide, maximum settings, no upscaling, 2x Frame Generation, firing range | About 140 FPS | Shows that Frame Generation can operate in the beta on supported hardware, but the result includes generated frames and a light test environment |
For actual visibility, disable Motion Blur and Depth of Field first because they intentionally soften information during movement or focus changes. Keep View Distance high while you still have enough performance. Mesh Detail is worth testing at Medium before Low because multiple players specifically reported that the lowest geometry settings made foliage and tree-line readability worse rather than better.
Brightness and Sharpness should be calibrated on your own display instead of copied from a competitor's exact number. Raise brightness only until dark interiors remain readable without washing out exterior contrast. Increase sharpness only until distant edges become easier to resolve; excessive sharpening can add halos and shimmering. FOV is also personal: a wider value reveals more peripheral space but makes distant enemies occupy fewer pixels. Lock your FOV before serious aim testing so the visual scale does not keep changing.
If you are trying to decide whether a visibility problem comes from settings or positioning, playing alongside an experienced teammate through WARDOGS Hire a Pro can make comparisons easier during live matches. It should not replace controlled testing: use the firing range first, then validate the same visibility profile in a real Control Zone.
Input and Audio
Input troubleshooting starts by separating mouse configuration from frame delivery. If the mouse feels heavy only when the frame rate collapses, fix performance first. If the camera response feels inconsistent at a stable frame time, inspect the control settings. Beta 02 exposed Mouse Acceleration, Sensitivity Scaling Mode, Monitor Matching Distance, Sensitivity Scaling Transition Type, infantry inversion, vehicle-specific controls, and dedicated rotary vehicle bindings.
For a predictable infantry baseline, set Mouse Acceleration to 0, keep sensitivity scaling consistent across hip fire and ADS, and choose one sensitivity you can reproduce instead of copying another player's DPI number. Relative scaling and a stable ADS multiplier are sensible starting points, but there is no universal "best" sensitivity. Record your current value before changing it, then test one adjustment at a time against the same target distance.
For display latency, disable VSync for the first test and enable NVIDIA Reflex when the menu and GPU support it. A stable frame cap can feel better than an uncapped frame rate that constantly swings, so do not assume Unlimited is automatically faster in practice. Test both with the same scene and watch frame time, not only the FPS counter.
Frame Generation deserves its own caution. Beta players with supported RTX hardware successfully used it, but community feedback on aiming latency is split. Some players reported no noticeable problem at a high base frame rate, while others said mouse response became less direct. For competitive troubleshooting, turn Frame Generation off first, establish your real rendered baseline, and only then test it as a smoothness option. If the base frame rate is already unstable, generated frames can make the counter look better without solving the underlying hitch.
For audio, Beta 02 menu captures showed a 3D Spatial Audio option, background sound behavior, and separate volume groups. Enable spatial audio if it produces clear directional cues on your headset, reduce music enough that vehicles, gunfire, and movement are not masked, and keep effects audible. Do not copy an exact effects-volume percentage from another setup because headphones, operating-system volume, and audio interfaces differ. Test direction by having a teammate move around you in a repeatable location.
Beta 02 menu captures and player reports also showed HOTAS-oriented controls and dedicated rotary-vehicle bindings in the test client. Some helicopter players described control as delayed or heavy even after checking their inputs. That is a player observation, not a confirmed menu bug or a setting with a guaranteed fix, and it should not be treated as a promise of final HOTAS compatibility for every device. If aircraft feels slow while infantry input is clean, test the same device in the firing range, verify the rotary vehicle bindings and assists, and avoid changing infantry sensitivity to compensate for aircraft behavior.
Stutter Checklist
WARDOGS stuttering needs a different checklist from low average FPS. A machine can show a high frame counter and still produce camera hitches, asset-loading pauses, or severe one-percent lows. Beta reports include everything from building-entry hitches to systems that ran smoothly for part of a session and then started freezing during vehicles or combat, so one generic "lower graphics" answer is not enough.
- Restart the game and the PC after a driver change. Several beta users reported behavior changing after a clean restart. Do this before stacking multiple speculative fixes.
- Install a current GPU driver. If the game warns about the driver, resolve that first. Record the driver version in your benchmark notes so a later update can be compared fairly.
- Verify the Steam installation. A corrupted or incomplete file is a different problem from a GPU bottleneck.
- Confirm the dedicated GPU is being used. This is especially important on laptops and systems with integrated graphics.
- Keep the game on an SSD when possible. One Beta 02 player reporting extreme pauses during vehicles and combat later confirmed the game was installed on a hard drive. That does not prove storage was the only cause, but an HDD adds an avoidable variable in a large streaming game.
- Check VRAM pressure before lowering everything. A beta laptop report with an RTX 3070 8 GB described crashes after VRAM exhaustion even on very low settings. Lower World and Character textures and Texture Streaming specifically when memory pressure is visible.
- Disable unnecessary overlays, capture tools, browser video, and background GPU workloads. Re-test before making more in-game changes.
- Use a stable frame cap as a test. If the average is high but frame time is uneven, cap below the unstable peak and see whether pacing improves.
- Separate network problems from render stutter. Rubber-banding, delayed hit registration, and players teleporting are not fixed by lowering Shadows. Beta 02 was explicitly used to stress scale-sensitive systems, as shown in the official WARDOGS beta announcements.
- Do not treat an Easy Anti-Cheat theory as confirmed. Steam confirms WARDOGS uses kernel-level Easy Anti-Cheat, and one player suspected it after system-wide stutter, but that report does not establish EAC as the cause. Avoid deleting anti-cheat files, replacing DLLs, or installing unknown optimizer packs.
- Re-test problem locations. If the same building entrance hitches every run while average FPS does not drop, record that behavior separately. A repeatable location-specific hitch can be a game-build issue rather than a quality setting problem.
Change only one troubleshooting variable between runs. If you update the driver, switch the upscaler, lower textures, disable overlays, and move the game to another drive at the same time, you may fix the problem but learn nothing about the cause. A clean diagnosis is more valuable than a random list of twenty tweaks.
Benchmark Method
A useful WARDOGS benchmark must be repeatable and must separate a quiet synthetic route from real large-scale combat. Average FPS alone is not enough. Record average FPS, one-percent low if your monitoring tool supports it, and a frame-time graph or at least the timing and frequency of visible hitches. Do not publish a percentage gain unless you can reproduce it on the same hardware and route.
- Record the environment. Write down WARDOGS build, date, CPU, GPU, RAM, storage type, GPU driver, monitor resolution, Display Mode, FOV, frame cap, VSync, Reflex, upscaler mode, and Frame Generation state.
- Build a baseline. Use the same Custom preset every time. Do not rely on Auto Detect because a later driver or build can choose different hidden values.
- Warm the test scene. Run the firing-range route once without recording. This reduces the chance that the first pass is being compared with a later pass that has already loaded more assets.
- Run three controlled passes. Use the same starting point, camera turns, sprint path, scope check, and vehicle segment when available. Keep each pass the same length. Take the median result rather than selecting the fastest pass.
- Change one setting. Examples: Global Illumination On to Off, Shadows Medium to Low, DLSS Quality to Balanced, or Textures High to Medium. Do not change an entire preset.
- Repeat the three-pass test. Record average FPS, one-percent low, and the largest recurring frame-time spike. If the result is within normal run-to-run variation, call the setting neutral on that system rather than claiming a gain.
- Validate in a real Control Zone. Play a busy five-minute segment around active infantry, vehicles, destruction, and smoke. The firing range is valuable for repeatability, but it does not reproduce a 100-player battle.
- Test latency separately. Compare Frame Generation Off and On, VSync Off and On only if needed for tearing, and capped versus uncapped FPS. Judge mouse response as well as the number on the counter.
- Keep evidence with the claim. If you write that a setting gained 12 percent, save the before and after runs, exact settings, driver, hardware, resolution, and build. Without those conditions, write that the setting "may improve performance" instead.
This method also explains why community FPS numbers can disagree without either player being wrong. One person may be flying in a quiet practice map, another may be inside a packed Control Zone, one may count generated frames, and another may be measuring native rendering. A WARDOGS FPS settings comparison becomes useful only when the test conditions travel with the result.
Conclusion
The safest WARDOGS best settings baseline is not Potato across the board. Keep native resolution when possible, use Quality upscaling when the GPU needs help, preserve Mesh Detail and View Distance for target readability, lower Global Illumination and Shadows before destroying every geometry and texture option, and disable camera effects that add blur or glare. For players who want the game to remain attractive, Low Shadows with medium lighting-related options is a better compromise than a fully stripped competitive preset. For maximum visibility, Global Illumination Off, Shadows Low or Potato, low post-processing, and disabled Motion Blur and Depth of Field are the main Beta 02 choices to test.
For stutter and input delay, stop tuning by feel after every death. Establish a fixed firing-range baseline, change one setting, repeat the route three times, then validate in a real Control Zone. Keep Frame Generation out of the first latency test, separate network symptoms from frame-time problems, and attach hardware, resolution, build, and exact settings to every numerical FPS claim. Early Access begins on September 10, 2026, so the first Early Access task is to re-check the menu and rerun the same benchmark instead of assuming Beta 02 behavior is permanent.
