Skip to content
← All errors

Rangefinder sees through walls

WARDOGS infrared rangefinder shows players through walls

Published Updated Data as of Season 3 · 12 Nov 2026

This one is not your machine

A rendering bug in the infrared rangefinder that highlights players and buildables through walls and terrain. Reports cluster on older Nvidia GTX cards (1050, 1070, 1080 Ti) on low settings, and some mention XeSS or anti-aliasing off. Team17 passed it to the developers and Update 0.1.2 did not fix it. On 2 October Bulkhead disabled IR rangefinders in the vendor until Season 02 for being too overpowered. They came back in Season 2 on batteries, and Season 3 (12 November) removes them from the vendor again until a redesign. Using it on purpose counts as exploiting a bug, which Bulkhead's rules say can get you banned.

Check whether WARDOGS is down right now →

What you see

Looking through the infrared (thermal) rangefinder, usually zoomed out, you can see enemy players and buildables highlighted through buildings and terrain across the map. Friends using the same item do not see it.

Also reported as: rangefinder wallhack · thermal rangefinder bug · infrared rangefinder see through walls · IRF wallhack · thermal wallhack

What to do instead

The cause is not on your machine, so reinstalling and verifying will not reach it. These are the things that actually help while it lasts.

  1. 01 If it happens to you, stop using the infrared rangefinder

    Confirmed

    Bulkhead's Security and Enforcement page lists "Deliberately exploiting bugs, glitches or unintended behaviour for advantage" among the things that get accounts suspended or banned. Seeing it once is not abuse; carrying on using it is. Switch to the regular rangefinder or monocular. From Season 3 you cannot buy a new infrared one, and Bulkhead has not said whether ones already bought still work.

  2. 02 Report it with your GPU and settings

    Confirmed

    Post in the Report a Problem board on the WARDOGS Steam hub with your graphics card, driver version, upscaler (DLSS, FSR or XeSS), anti-aliasing setting and a screenshot. Team17 support has been adding each report to its file for the developers, and the hardware detail is what is narrowing it down.

  3. 03 Try a different upscaler or anti-aliasing setting

    Unconfirmed

    The first report blamed XeSS; another player saw it with anti-aliasing off. Nobody has confirmed a setting that stops it, so treat this as worth a try rather than a fix.

  4. 04 If you are being spotted through walls, report the player

    Confirmed

    Use the in-game report. You cannot tell from the receiving end whether someone has this bug or a real cheat, and reports are what Bulkhead says tells its detection where to look.

Did this fix it for you?

Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.

No comments yet. Be the first to say whether this worked.

This is a bug, not a cheat, but from the other end it looks exactly like one. The infrared rangefinder is the thermal version of the Recon role's rangefinder: it highlights warm targets so you can mark them for your team. For some players it highlights them through everything. One described zooming all the way out and seeing "enemies all the way across the map inside of their base through buildings and terrain."

Who gets it

The pattern in the reports is hardware. Players on a GTX 1050, 1070 and 1080 Ti have it, several on low settings, while a player on an RTX 5080 does not and a friend on a GTX card does. One report ties it to XeSS, another to having anti-aliasing turned off, and one player noticed it depends on which way you look and how far you zoom. The GTX 10 series stopped getting new Nvidia drivers earlier this year, which may be part of it. None of that is confirmed as the cause.

Is it being fixed?

Team17 support has answered every report since 22 September by adding it to the file for the developers. On 27 September it said "We understand how significant it is if the range finder unintentionally provides visibility through buildings and terrain." No fix date has been given, and Update 0.1.2 on 30 September does not mention it. Players on the thread are asking for the item to be pulled until it is fixed.

On 2 October Bulkhead did pull it. The balance hotfix disables IR rangefinders in the vendor until Season 02, rolling out as servers restart across regions over the following 12 hours. When they return they will need batteries. Bulkhead's stated reason is that they are too overpowered, and the post does not mention this bug. "Disabled in the vendor" means nobody can buy a new one. Whether infrared rangefinders players already own stop working is not stated. Nothing says the rendering bug itself is fixed, and the same day's security and stability hotfix published no notes.

The item came back in Season 2 on 15 October, running on batteries that last about 80 seconds of use, at $3,200 instead of $1,200. The Season 2 notes did not say the rendering bug was fixed.

Season 3 removes it from the vendor again on 12 November. Bulkhead's notes give the same kind of reason as in October: it was used in almost every match, and the Season 2 battery nerf "didn't curb how powerful it is". It stays off the vendor until Bulkhead is happy with a redesign. The notes do not mention the through-walls bug, and they do not say whether infrared rangefinders players already hold still work.

Why it matters more than most bugs

WARDOGS is built around information: marking, spotting and knowing where the enemy is are how teams win the zone. A bug that gives one player a full view of the map is a balance problem as much as a graphics one, and it lands in the middle of a wider row about players forcing graphics driver settings to see through foliage. Nvidia Inspector and the foliage row → · What gets you banned →

If your rangefinder simply will not zoom, that is a different bug: scope zoom not working.

If that did not do it