Some WARDOGS players are using Nvidia Profile Inspector, a free tool for editing graphics driver settings, to make foliage render thinner so they can spot people hiding in it. A post on r/WarDogs asking Bulkhead to "Ban Nvidia Inspector" went up on 26 September and had passed 1,600 upvotes by the 30th. A developer reply on the thread reportedly said only "Thanks for showing this, we will speak to Nvidia." Bulkhead's rules do not name the tool, and that is not the same as it being allowed.
| What it is | A third-party editor for Nvidia driver profiles |
| What players say it does in WARDOGS | Thins out foliage so hidden players show |
| Named in Bulkhead's rules? | No |
| Covered by them anyway? | Plausibly, as exploiting unintended behaviour |
| Developer response | "We will speak to Nvidia" (reported) |
| Fixed? | Not in Update 0.1.2 |
What the trick actually is
Nvidia Profile Inspector edits the per-game profiles inside Nvidia's driver, including dozens of settings the Nvidia app never shows you. Most of what people use it for is harmless: capping frame rate, forcing V-sync, overriding DLSS versions. The original post put the problem plainly: players are using it to change GPU settings "not shown in game" and "shooting through crazy thick foliage."
The most detailed reply on the thread, from a player who says the trick is common in other mil-sim games, describes the recipe: an extreme positive LOD bias, which makes the driver draw lower-detail versions of models and textures sooner, combined with forced transparency supersampling. Together they strip the dense leaf layers that grass and bushes are built from. We have not tested it, and we are not going to publish the values. The effect players describe is enough: cover that hides you on normal settings does not hide you from them.
A separate complaint on the same thread is about shadows, which some players turn off in the game's config file rather than through the driver. That is a different fix and a different argument.
What Bulkhead has said
Very little. The only developer response found is the reply surfaced on the subreddit's developer-comment list: "Thanks for showing this, we will speak to Nvidia." We could not confirm who at the studio posted it. Nothing has been announced since, and the Update 0.1.2 notes on 30 September, which were mostly about exploits, do not mention it.
Speaking to Nvidia makes sense. The trick lives in the driver, not in WARDOGS, so the cleanest fix is a driver profile that locks those settings for the game, or a game-side change that ignores them. Neither has been promised.
Can it get you banned?
Nobody has been banned for it that we know of, and Bulkhead's rules do not name it. But three lines in them give the studio room:
- The Security & Enforcement page says the anti-cheat looks for attempts "to reveal information that shouldn't be known."
- The same page bans "Deliberately exploiting bugs, glitches or unintended behaviour for advantage."
- The EULA defines cheating as including a list of specific things and "any other conduct that we determine, in our sole discretion" to be cheating.
Seeing players through foliage that is meant to hide them is information the game is not supposed to give you, gained through behaviour nobody intended. Whether Bulkhead treats it that way is its call, and it has said the anti-cheat monitors applications running on your machine. Using Inspector for a frame cap is not what anyone is complaining about. Using it to thin out foliage is the part to leave alone. What gets you banned in WARDOGS →
Why it matters more in WARDOGS
Concealment is worth more here than in most shooters. Loadouts cost real in-game cash that persists between matches, recon players earn by spotting, and a sniper in a bush is a legitimate build. If one player's bush is see-through to another player's settings, that is money moving from one to the other for no reason the game intended. It sits alongside a genuine bug with the same effect, the infrared rangefinder showing players through walls, which Team17 says is under investigation.
What we still don't know
- Whether Bulkhead will ban for it, or fix it in the game or the driver instead.
- Who posted the "we will speak to Nvidia" reply, and whether Nvidia has responded.
- Whether AMD's driver tools allow the same trick. Nobody on the thread has said.
- How widespread it is. One upvoted post and a pile of angry comments is a signal, not a count.
