You changed one keybind. Now your variable zoom either does nothing or swaps weapons instead. You’re not alone. The WARDOGS variable zoom bug appears the moment you reassign the “Cycle Scope Distance” binding. The in-game menu doesn’t clean up the old assignments, and two hidden entries in your config file—ScopeZoomDecrease and ScopeZoomIncrease—get corrupted. Here’s the surgical fix that takes thirty seconds and leaves every other setting intact.
Why Most “Fix This” Guides Waste Your Time
You’ll find advice like “reset all keybinds” or “verify game files.” Those work, but they’re sledgehammers. Resetting keybinds nukes every custom binding you built. Verifying game files does nothing because the problem lives in your personal config, not the game’s installation. The real culprit is the file GameUserSettings.ini. The game stores custom keybinding data inside a section that the settings UI does not properly manage. When you bind a key to cycle scope distance, it often overwrites or conflicts with the zoom increase/decrease lines behind the scenes. The result: your scope zoom key suddenly fires a different action.
You need to go straight to the source and delete exactly two lines.
The Exact WARDOGS File You Need to Edit
Open File Explorer. Paste this into the address bar and press Enter:
“`
%localappdata%WarDogsSavedConfigWindowsNoEditorGameUserSettings.ini
“`
That path assumes you installed the game through Steam. If you changed your Windows user folder name, adjust accordingly. The file is plain text. Right-click it, open with Notepad (or any text editor). Make sure the game is completely closed—Steam too, if possible—otherwise the game will overwrite your changes on exit.
Press Ctrl+F and search for CustomKeybindingscodecodecodecode. You’ll land on a line that starts with that word. Below it, a few lines later, look for:
“`
ScopeZoomDecrease=(…)
ScopeZoomIncrease=(…)
“`
The exact parenthesis content depends on what key you bound. It might look like ScopeZoomDecrease=(Key=MouseWheelUp)codecodecodecode or ScopeZoomDecrease=(Key=Numpad1)codecodecodecode. Delete both entire lines. Do not delete any other line unless you’re sure. The CustomKeybindings section can have many entries; only remove these two scope zoom lines.
Save the file. Launch WARDOGS. Test your variable zoom immediately—it should work as intended. If the bug persists, you might have a second instance of the same entries further down. Search again to be thorough. Very rarely, the game regenerates the lines on launch. If that happens, repeat the edit and then right-click the file → Properties → check Read-only. This prevents the game from overwriting your edit. Downside: any in-game setting changes (graphics, audio) will not save while read-only is enabled. Set it back to read-write once you confirm the zoom works, then re-edit if the bug returns.
Comparison: Three Ways to Fix the Scope Zoom Bug
Not every player wants to edit config files. Here are the options side by side. Choose based on your tolerance for collateral damage.
| Method | What It Affects | Time (approx.) | Reliability for This Bug |
|---|---|---|---|
| Delete ScopeZoom lines in .ini | Only the two scope zoom bindings | 30 seconds | Near 100% if lines exist |
| Reset all keybinds in-game via Settings → Controls → Reset | Every custom binding, movement, weapon, vehicle | 2 minutes + re-bind time | 100% (resets everything) |
Delete entire WindowsNoEditorcodecodecodecode folder |
All settings: graphics, audio, keybinds, window position | 1 minute + full re-configuration | 100% (but you rebuild from scratch) |
The .ini edit is the only precision approach. The other two fix the bug but cost you your entire control setup. If you have dozens of custom bindings, the .ini edit is your only sane choice.
What If You Can’t Find the Lines?
The bug only manifests if you have actually changed the “Cycle Scope Distance” keybind at least once. If you never touched that setting, you won’t see ScopeZoomDecrease/Increase in your .ini. In that case, your variable zoom is broken for a different reason—maybe a game version bug or corrupted shader cache. Try the standard launch fixes first: restart PC, verify files, run Steam as admin.
If you did change the keybind and the lines are missing, search for “CustomKeybindings” again and look more carefully. The lines might be buried inside a long single-line block. Some versions of the game cram all custom keybindings into one line without newlines. Use Notepad++ or any editor with word wrap to spot them.
Preventing the Bug From Returning
Avoid touching the “Cycle Scope Distance” keybind entirely. Leave it on its default (usually unbound or mouse wheel). Instead, use the game’s separate “Zoom In” and “Zoom Out” bindings for variable scopes—those don’t trigger this bug. If you absolutely must rebind distance cycling, after you make the change in the menu, immediately open GameUserSettings.ini and check for stray scope zoom entries. Delete them before launching the game. One minute of prevention saves you a crash course in config editing later.
A Note on the Upcoming Patch
Bulkhead has acknowledged this bug in community discussions but hasn’t committed to a fix timeline. The early access schedule is tight. Until they address it, the .ini edit remains the only reliable workaround. If a future update changes how keybindings are stored, this guide will become obsolete—but for now, it’s the difference between a working scope and a frustrating weapon swap during a firefight.
The fix is tiny. The payoff is huge. Do it once, and you’ll never rage-quit over a zoom bind again.
