War Thunder tank shot diagnosis: use Protection Analysis when a hit underperforms

Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Private browser-local worksheet · no live game connection

Crew investment and shot-evidence checklist

This worksheet stores your entries only in the current page session. It does not connect to War Thunder, read your account, access a replay, or save/upload your notes. It provides a checklist, not an armor calculator, crew recommendation engine, or battle prediction.

Vehicle / crew slot (your note)Mode (for your own context)Repeated crew problem

Skill / question to revisit

Your notes: no vehicle entered · Ground Realistic

Confirm the assigned vehicle uses a human loader rather than an autoloader.
Check the current Weapon Reloading tooltip and identify which loader role the vehicle panel lists.
Compare the displayed reload with a damaged-module/crew state before spending; damage may be the actual cause.
Write down the intended vehicle, lineup and mode so the slot investment matches how you play it.

0 of 4 checks marked

Mark a step only after you have checked it in the client. This tool cannot confirm a skill purchase is worthwhile or determine why a shot behaved a certain way.

No account, API, analytics, replay reader, or persistent browser storage is used. External links on this page are separate from these local inputs.

1. Save the encounter details before opening the Hangar

Record both vehicles, the exact shell type, approximate range, and where the shot landed. Use the battle replay/hit information if available; do not substitute a different shell because it has a similar name.
Note whether the result was no penetration, an apparent penetration with little effect, a ricochet, or an uncertain hit. Keep those cases separate.
Record the patch/client date and game mode. A damage-model update, different range, or different target variant can change the comparison.
If the shot was from a different platform or mode than the analysis setup, label the mismatch instead of treating it as a controlled reproduction.

2. Set up a comparable Protection Analysis case

In the Hangar, select or inspect the target ground vehicle and open its Armor / Protection Analysis view.
Choose the firing vehicle and the same shell family/variant used in the encounter; set the observed range rather than leaving an unexamined default.
Aim at the approximate impact point and reproduce the incoming direction/strike angle as closely as the tool allows. The historical feature description says the analysis uses the selected vehicle, shell, range, cursor point, and view direction.
Read the penetration/protection result and predicted internal modules or crew together. A penetration indicator alone does not promise the same post-penetration outcome in a live battle.
If useful for the vehicle and patch, inspect the current ballistic or armor-penetration curve/comparison UI; Gaijin described curves at different ranges in its June 2026 development update.

3. Interpret the mismatch without inventing a weak spot

Analysis compared with the encounter	Next investigation	Do not conclude
Analysis predicts no penetration	Check exact shell, range, impact point, angle, and whether an outer track/screen/part altered the path.	‘This tank is immune’ from one shot or one angle.
Analysis predicts penetration but limited internal effect	Inspect the predicted path, modules, crew placement, shell type/fuze behavior, and the selected point.	‘It should have one-shot’ without a vehicle-specific damage path.
Analysis result differs from the hit information/replay	Check vehicle variant, patch, range estimate, impact direction, lag/desync, and whether the shot actually connected.	That the analysis reproduces a networked battle frame-for-frame.
Only the edges of a tested region behave differently	Use several nearby aim points and compare the displayed prediction; treat borders as transition areas.	A single cursor color as an unconditional guarantee in every battle.
Prediction is inconsistent after a patch	Recheck the current changelog and repeat with the updated client’s current model.	Old screenshots as current armor truth.

4. Change one variable per test

A useful comparison is a short, controlled matrix rather than a search for a universal weak spot. Keep target and shot point fixed while changing ammunition; then keep shell fixed while changing range; then vary angle or point. Capture the in-tool settings and result for your own notes. Do not combine a new shell, range, point, and target orientation in one comparison, or you will not know what changed the output.

Test pass	Hold constant	Change only
Ammunition	Target, range, aim point, direction	Shell type/variant
Range	Target, shell, aim point, direction	Distance
Impact geometry	Target, shell, range	Point and/or direction—one at a time
Patch check	All settings	Client version/date; repeat after relevant damage-model change

5. Use the result as practice, not a battle guarantee

Protection Analysis is valuable because it applies the game’s modeled armor interaction without spending a live shell, but it cannot guarantee the exact online shot you saw. The server may resolve a different impact point or timing than the client view suggests, and the damage model can be updated. For a repeatable issue, save a replay or screenshot, list target, shooter, shell, mode, range, patch, and analysis setup, then compare again after the next relevant changelog entry.

Before you play

I matched the vehicle, role, mode and current patch before using a reference.
I used current in-game tooltips/analysis rather than a universal meta claim.
I separated offline analysis from live match outcomes.

Frequently asked questions

Does this guide prove a vehicle or shell will work in a live match?

No. Vehicle, shell, range, angle, server behavior and patch can affect outcomes; use the current in-game analysis for the stated case.

Sources & revision notes

Editorial revision: November 6, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

War Thunder official changelog — Protection Analysis feature description (Official)
Gaijin/Wiki source for the stated mechanic. Check the current vehicle, mode and client build; this guide does not assert a live match outcome.
Official War Thunder Wiki — using armor and modifications to improve survivability (Official)
Gaijin/Wiki source for the stated mechanic. Check the current vehicle, mode and client build; this guide does not assert a live match outcome.
Gaijin development news — ballistic comparison and range curves in Protection Analysis (June 3, 2026) (Official)
Gaijin/Wiki source for the stated mechanic. Check the current vehicle, mode and client build; this guide does not assert a live match outcome.
War Thunder official changelog — current patches (Official)
Gaijin/Wiki source for the stated mechanic. Check the current vehicle, mode and client build; this guide does not assert a live match outcome.
Steam discussion — Protection Analysis announced (historical feature context) (Community)
External player-generated discussion; may describe a different vehicle, mode, ammunition or patch. Not official mechanics authority or GamerWin testing.
Steam update feedback thread — user reports about Protection Analysis / hit analysis (2024) (Community)
External player-generated discussion; may describe a different vehicle, mode, ammunition or patch. Not official mechanics authority or GamerWin testing.

What changed in this revision

November 6, 2026: first publication, organized current official/Wiki sources into role- and case-specific checks; no match or armor result was tested.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.