You just got lit up from 600 meters by a tank you never saw, sitting in a bush a settings guide swore would hide you. That guide is five years out of date. Gaijin equalized how far vegetation and cover render across every graphics preset back in 2021, and War Thunder’s detection system has run on crew skill and player behavior ever since — not on how low you’ve dragged your terrain slider. Then in 2025 the game added ray tracing, path-traced lighting, and full upscaling support, which shifted the FPS-versus-clarity trade-off all over again.
This guide skips the recycled slider list. It explains, with Gaijin’s own patch notes and dev blogs as the source, exactly which settings still affect who spots whom first, which ones are dead placebo left over from a patched exploit, and how the answer changes between ground battles and air battles — plus the concrete FPS cost of the three sliders that matter most.
The Foliage Myth Gaijin Killed in 2021
Every “best War Thunder settings” list on the first page of Google tells you the same thing: drop shadow quality to minimum, kill terrain and foliage detail, and you’ll spot tanks hiding in bushes that other players can’t. That advice used to work. It stopped working in September 2021.
Before that patch, players running Ultra Low Quality graphics genuinely saw fewer distant bushes and trees than players on higher presets, which meant an ULQ player could see a target sitting in cover a max-settings player couldn’t see at all. It was a real, documented exploit, and it’s why the advice spread so widely in the first place. Then Gaijin shipped “It’s Fixed №21,” which states plainly: “Objects in War Thunder, such as trees or houses, now have a similar rendering distance for all graphics presets.” Vegetation, buildings, and cover now render at the same distance no matter what you’ve got your quality slider set to.
That’s five years of patches ago, and most guides recommending “low terrain quality to reveal hidden targets” haven’t been updated since. Chase that exploit today and you’re not spotting anything — you’re just running an uglier game for nothing.
What Actually Decides Who Sees Whom First
If graphics presets don’t control who’s hidden anymore, something else does — and Gaijin’s own devblog on the 1.53 visibility overhaul spells it out. On the ground, detection range is a crew-skill stat, not a settings value: a fresh, untrained crew spots a stationary, hidden enemy vehicle at roughly 500-750 meters, and a fully trained crew detects at two to three times that range. Sitting still in cover with a maxed-out crew genuinely works. But the moment you move, rotate a turret, or fire — even a single machine-gun burst — you immediately de-mask yourself and become visible from far beyond that range, regardless of what your terrain or shadow settings are doing. Open your own killcam next time you get lit up from a bush and check the timing: it lines up with your gun traversing or firing almost every time, not the moment you loaded into the match.
Air battles run on a completely different problem. On a 1080p monitor, an aircraft four kilometers out is roughly four pixels wide and less than a pixel tall — that’s not a foliage-rendering issue, it’s a screen-resolution and anti-aliasing issue. Gaijin’s fix for this wasn’t a “reveal enemies” slider either; it was an 8-16x increase in image dynamic range so you can actually read glint and orientation off a barely-there dot. This is why ground and air battles need completely different settings priorities, which most guides never separate.
Ground Battle Settings: What Still Genuinely Matters
Since render distance is a solved, equalized problem, most of your ground-battle graphics settings are now pure FPS levers with zero spotting cost — except the two that still do something real.
| Setting | Old belief | Current reality | Recommended value |
|---|---|---|---|
| Terrain / Object Quality | Lower = see through more cover | Render distance equalized since 2021 — no spotting effect | Low/Medium for free FPS |
| Shadow Quality | Minimum “reveals hidden targets” | Never tied to visibility — always an FPS setting | Low/Minimum for FPS only |
| Grass in Sights | N/A | Genuinely current and legitimate — strips grass only inside the zoomed sniper/scope view | Off |
| Effects Quality | N/A | Fewer particle emitters and no per-explosion dynamic lighting — real help seeing through your own smoke and dust mid-fight | Low/Medium |
| Anisotropic Filtering | N/A | Near-zero FPS cost, keeps distant camouflage patterns legible instead of blurring into mush | 16x, always |
The one genuinely useful spotting lever on this list is Effects Quality, and it’s not about hiding anyone — it’s about your own view. High Effects Quality means every explosion, muzzle flash, and track kicks up dense, lingering dust and smoke that can bury a target that’s sitting in plain sight. Turning it down doesn’t uncover camouflaged enemies; it stops your own barrage from blinding you.
Air Battle Settings: Legibility Over Cover
None of the ground-battle “cover” logic applies in the air, because there’s no bush to hide behind at 4km — there’s just a handful of pixels you either can resolve into a shape or can’t. Render resolution matters more here than any single quality slider: don’t run a downscaled resolution to chase frames in an air-heavy mode, because you’re directly shrinking the number of pixels a distant contact gets to exist on.
Anti-aliasing is the setting that decides whether that distant dot resolves into a recognizable silhouette or dissolves into shimmer. TAA is the sweet spot for most setups — it smooths those pixel-thin edges for roughly a 3% FPS cost. Full 4x SSAA looks sharper still but costs three to four times the GPU fragment work for the difference, which is a bad trade unless you’re already well above your monitor’s refresh rate. If you’re on an RTX card, DLAA (DLSS run at native resolution purely for anti-aliasing) is worth trying instead — it’s part of the frame-generation and upscaling suite Gaijin added with the 2025 Leviathans update, alongside AMD FSR and Intel XeSS support.
Cloud Quality is the other air-specific setting worth watching: flattening it to save frames also flattens the sky’s contrast and depth cues, and pilots commonly report an easier time picking a silhouette out from a more detailed sky — so unless you’re truly frame-starved, keeping it at Medium or above is the safer default in any mode where air spotting matters. Ray tracing and the new Path Traced Global Illumination, on the other hand, are cosmetic lighting upgrades — better color and no light-leaking artifacts — with no spotting benefit at all. Skip them if you’re chasing frame rate; turn them on if you’re chasing screenshots.
FPS Impact Table: The Big Three
Community benchmark testing (not Gaijin’s own published numbers, so treat these as directional rather than guaranteed on your exact rig) puts real percentages on the three settings that move the needle most.
| Setting | FPS cost at High | What lowering it actually changes |
|---|---|---|
| Terrain Quality | ~6% at High vs. lower presets | Tessellation and material-blending detail only — no spotting effect since 2021 |
| Effects Quality | 4-8% saved dropping High to Medium in busy fights | Fewer particle emitters and dynamic lighting per explosion — also clears your own sightline |
| Anti-Aliasing | TAA ~3%; 4x SSAA up to 3-4x the GPU cost of TAA | TAA is the efficient default; SSAA only pays off with GPU headroom to spare |
If you only change three things today, community testing suggests the biggest single wins are setting render resolution to 100% of native, switching anti-aliasing to TAA, and dropping shadow quality to Medium — reported gains in the neighborhood of 70, 55, and 16 frames respectively on the systems tested, though your mileage will vary by GPU. For general FPS optimization that applies beyond just War Thunder, our complete PC settings guide covers the driver- and OS-level side of this.
Priority by Player Type
| Player type | Priority | What to actually do |
|---|---|---|
| New player | Get it running smoothly without tuning 20 sliders | Turn V-Sync off, Anisotropic Filtering to 16x, leave everything else on the default preset for your GPU tier |
| Casual player | Efficient wins, minimal fiddling | Run the three “free wins” above once, ignore ray tracing entirely |
| Hardcore / optimiser | Min-max by the mode you actually play | Ground-heavy: drop Effects and Terrain Quality further, they cost nothing now. Air-heavy: push Anti-Aliasing to TAA/DLAA and keep Cloud Quality up, then trim Terrain/Effects instead |
| Handheld / low-end | Battery life and stable frame times | Gaijin’s own benchmark on an MSI Claw-class handheld: Movie preset plus Medium ray tracing holds 70-90 FPS — a rare case where the developer’s own tested baseline beats guesswork |
If you also play a long-running live-service title like World of Warcraft, the instinct to chase every slider instead of the two or three that matter is the same trap — our Best WoW Settings guide hits the identical pattern from a completely different engine.
FAQ
Does turning down graphics settings still hide me in bushes?
No. Object and vegetation render distance were equalized across every graphics preset in September 2021. If a guide tells you otherwise, it’s repeating pre-2021 folklore. What actually hides you today is standing still with a trained crew and not firing — a behavior and crew-skill mechanic, not a slider.
Is DLSS/FSR frame generation worth using in competitive matches?
Depends what you’re bottlenecked by. Frame generation interpolates extra frames instead of rendering them, adding a sliver of latency even with Reflex or Anti-Lag 2 offsetting part of it — a real cost when snap-aiming a barrel or leading a deflection shot rewards raw input response. GPU-bound and just want smoother visuals? Fair trade. Chasing the tightest aim feel? Leave it off.
Should I run Direct3D 11 or 12?
Direct3D 11 is still the safer default for raw frame-rate stability. Direct3D 12 is the one that unlocks the 2025 ray-tracing and PTGI feature set, so the right choice depends on whether you actually want those visuals or you just want frames — “12 is newer” isn’t a reason on its own.
Why does my FPS still tank in dense city maps even on low settings?
Terrain Quality isn’t the bottleneck there — Effects Quality and particle density are. City maps stack multiple simultaneous explosion, smoke, and dust emitters in a small space, and that’s exactly the load Effects Quality controls. Dropping Terrain further won’t touch it; dropping Effects will.
Key Takeaways
Spotting stopped being a graphics-settings problem in 2021 and became a crew-skill and behavior problem instead — sit still with a trained crew, or get de-masked the instant you move or fire, regardless of your terrain slider. What’s left for your settings menu is a straightforward FPS-versus-legibility trade that splits by battle type: ground battles reward dropping Effects Quality for your own clarity, air battles reward protecting anti-aliasing and cloud detail for a target that’s only a few pixels wide.
Five-minute version: Anisotropic Filtering 16x, native render resolution, Anti-Aliasing to TAA, Shadow Quality Low, then split Terrain and Effects Quality by whether you’re mostly ground or air this session. Verified against War Thunder’s live settings menu and Gaijin’s 2021 and 2025 developer posts — engine updates ship often enough that slider names can shift, so cross-check your own settings screen if something’s moved.
Sources
- “It’s fixed! №21” — War Thunder official news, warthunder.com (cited above)
- “[Development] Visibility in 1.53 explained” — War Thunder official devblog (cited above)
- “[Development] Graphics Improvements in the Leviathans Update!” — War Thunder official devblog (cited above)
- Steam Community Guide — War Thunder: Best Settings for FPS & Visual Clarity
- TargetFPS — War Thunder Best Graphics Settings 2026
- GameHelper — War Thunder Best Ground Forces Settings for FPS & Visibility (2026) (URL unreachable at publish time, cited above)
- Reality Remake Gaming — Best War Thunder Settings for Spotting Enemies and Performance
- Steam Community discussion — historical foliage-rendering reports (cited above)
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.