War Thunder News

War Thunder devs apologise for using picture of Challenger shuttle disaster in artwork promoting latest update

The developers of multiplayer aerial combat sim War Thunder have apologised after a picture of the real-life Space Shuttle Challenger disaster, which killed seven crew members when it exploded just 73 seconds after launch in 1986, was used in artwork promoting the game’s recent Seek & Destroy update.

War Thunder by Gaijin Entertainment is a large-scale military simulation with an emphasis on realism, and the game's known for one thing in particular: a community that just cannot stop itself from leaking classified military documents to win forum arguments about virtual tanks. Well, that and having game footage used (without the studio's knowledge) in the background of Russian propaganda clips...
Read more.

War Thunder dev apologizes for using image of Challenger tragedy

War Thunder developer Gaijin Entertainment has apologized for accidentally using footage from the 1986 Challenger disaster in a piece of key art. The maker of the military combat game just dropped the new 'Seek and Destroy' update filled with new vehicles, quality-of-life changes, and fixes, but one piece of promotional art directly lifts the smoke and contrails left behind after the tragic space shuttle explosion.

Read the rest of the story...

Screenshot Competition – Seek & Destroy!

Welcome to the 125th War Thunder Steam Screenshot Competition!

We loved seeing the screenshots you captured and submitted last week! Many of you were anxiously waiting for the major update to arrive. Well, wait no more, it is here! Which new feature do you like the most? The three most popular and three selected by us will get 300 GE. See the winners down below!

[h2]Let’s begin the 125th edition of our competition![/h2]

Create a stunning screenshot and submit it on the War Thunder Steam Community Hub with the tag #WTscreen125. You have time until the 28th of June to submit your screenshot.

After that date, 6 winners will be selected (3 of which will be the highest rated by the community and 3 selected by our judges), each of which receive a reward of 300GE.

[h3]Terms:[/h3]

Your screenshot must feature a new vehicle or map introduced in the major update Seek and Destroy.
You must add the #WTscreen125 tag (title cannot have any other text in it).
Artists may only win by popular vote once per four screenshot competitions.

Screenshots need to be compliant with the War Thunder rules.
You need to be the author of the screenshot.
Screenshot needs to be new. You cannot use those which have previously been published or used in other competitions.
We will only accept raw screenshots from the game. You cannot use any editing software nor any other visual enhancements (like Nvidia Ansel filters).
You can use filters and settings built into War Thunder.
You can use the replay functionality built into War Thunder.
Rewards will be delivered to the author's account within 14 working days.

[h2]And now, time for the winners of the competition’s 124th edition – Summer Gathering![/h2]

[h3]Winners selected via community votes:[/h3]
https://steamcommunity.com/sharedfiles/filedetails/?id=3269653085
https://steamcommunity.com/sharedfiles/filedetails/?id=3268099158
https://steamcommunity.com/sharedfiles/filedetails/?id=3268132645

[h3]Winners selected by our judges:[/h3]
https://steamcommunity.com/sharedfiles/filedetails/?id=3271154764
https://steamcommunity.com/sharedfiles/filedetails/?id=3268417094
https://steamcommunity.com/sharedfiles/filedetails/?id=3270666548

Each winner will get 300GE! Congratulations and see you next week!

Update 2.37.0.20

[h2]Aircraft[/h2]

A bug that caused countermeasures used in Ground Battles to be missing or issued in single quantities has been fixed. (Report).
Mirage 2000C-S5, Mirage 2000-5F — a bug that caused only 2 chaff out of 48 to be available for release has been fixed.
F-105D, F-100F, A32A — a bug that caused the countermeasure pods to release chaff just once has been fixed.
JA37D, JAS39A — a bug that caused the amount of countermeasures present in battle to mismatch the selected amount has been fixed.
Mirage F1C-200 — a bug that caused the amount of countermeasures in the selection window to be higher than the actual amount has been fixed.
Incorrect behavior of the BAFG-230 / 460 bomb acting as a tail fin retarded bomb has been fixed.
Harrier GR.7 — a bug that caused the BOL pods to not carry any countermeasures has been fixed. (Report).
Harrier GR.7 — a bug that caused presets with the AIM-9L + BOL to be locked unless the AIM-9M modification had been researched has been fixed.
JAS39 (all variants) — the incorrect sequence of firing countermeasures and the lack of display in battle of the additonal 12 countermeasures built into the wing pylon for the JAS39C variant has been fixed.
A bug that caused the firing of countermeasures in series to not function has been fixed. (Report).
F-4F KWS LV — AIM-9L/I missile icons have been fixed. A bug that caused the belt selection for the 20 mm cannon to not appear in the modifications window has been fixed. (Report).
MiG-29SMT — the number of missile data link channels in the radar has been increased from 2 to 4. (Report).
JAS39C, Sea Harrier FA 2 — the number of missile data link channels in the radar has been increased from 2 to 4. (Report).
Mirage 2000-5F — the number of missile data link channels in the radar has been increased from 2 to 4. (Report).
Tornado F.3 Late — the number of missile data link channels in the radar has been increased from 2 to 4. (Report).
Fokker G.IA (France) — moments of inertia have been corrected. The operation of control surfaces has been corrected (deflection angles have been changed).
A bug that caused knocked-out gunners to fire has been fixed.

[h2]Ground Vehicles[/h2]

Strv 103 (all variants) — a bug that caused the tank to lose the ability to move when the driver was knocked out has been fixed. (Report).
Namer 30 — a bug that led to the fatal detonation of the external ammunition for the gun has been fixed. A bug where the gun did not jam when overheated has been fixed.
Challenger 3 TD — engine power has been reduced from 1500 HP to 1200 HP. (Report). (This was a missing point in the Seek & Destroy major changelog, the changelog has also been updated).

[h2]Naval Vessels[/h2]

VLT-2 — a bug where the ability to perform survivability actions was disabled due to the lack of crew has been fixed. (Report).
In the controls settings, the description of the seeker lock control has been corrected. (Report).
A bug which caused the belt-fed of clip-fed guns of some ships (for example, MTB-422, R-301, Thunderbolt (PT-556)) to not reload after spending a single belt or clip has been fixed. (Report).

[h2]Interface[/h2]

For vehicles available on the Marketplace, the “Find on Marketplace” button is now replaced with “Consume coupon” button in the tech tree, vehicle preview, and wishlist if the player has the coupon with this vehicle in their inventory.
A bug that caused aircraft with only chaff to have an indication of a number of flares to be displayed in the battle has been fixed.
A bug where selecting a weapon preset without countermeasures on some aircraft lead to the display of countermeasure “belts” in the modification window has been fixed.

[h2]Sound[/h2]
The following sound changes have been reverted back to how they were before the Seek & Destroy major update due to feedback surrounding them, and some will be reworked:

The changes to ground vehicle crew voices, and the clarity and audability of commands, in particular due to the echo when viewed from the gunner.
All explosion sounds due to the updated nature of the sound.
The sounds of artillery shells falling due to the annoying nature of the sound.
All long-range shots from ground vehicle cannons due to their monotony and “dull” sound.
The M61 Vulcan and GAU12 mutli-barrel guns, we realise the updated sound was not seen as an improvement.
The volume levels of all sounds, there are no changes now compared to what they were before the update.

[h2]Other[/h2]

A bug that caused Squadron Activity points to not be given has been fixed. (Report).

Patch notes reflect only key changes, meaning they may not include a complete list of all improvements made. Additionally, War Thunder is constantly being updated and some changes may not require an update. Changes reflected in patch notes are formed by taking reactions and requests of the community from the bug reporting service, forums and other official platforms into account. Bug fixes and changes are implemented in order of importance, for example a game-breaking bug will be worked on and implemented sooner.