![War Thunder background](https://warthunder.com/i/bg-fon/site_theme_seek_and_destroy_desert_warrior.webp?v=9e186acf)
- For PC
- For MAC
- For Linux
- OS: Windows 7 SP1/8/10 (64 bit)
- Processor: Dual-Core 2.2 GHz
- Memory: 4GB
- Video Card: DirectX 10.1 level video card: AMD Radeon 77XX / NVIDIA GeForce GTX 660. The minimum supported resolution for the game is 720p.
- Network: Broadband Internet connection
- Hard Drive: 17 GB
- OS: Windows 10/11 (64 bit)
- Processor: Intel Core i5 or Ryzen 5 3600 and better
- Memory: 16 GB and more
- Video Card: DirectX 11 level video card or higher and drivers: Nvidia GeForce 1060 and higher, Radeon RX 570 and higher
- Network: Broadband Internet connection
- Hard Drive: 95 GB
- OS: Mac OS Big Sur 11.0 or newer
- Processor: Core i5, minimum 2.2GHz (Intel Xeon is not supported)
- Memory: 6 GB
- Video Card: Intel Iris Pro 5200 (Mac), or analog from AMD/Nvidia for Mac. Minimum supported resolution for the game is 720p with Metal support.
- Network: Broadband Internet connection
- Hard Drive: 17 GB
- OS: Mac OS Big Sur 11.0 or newer
- Processor: Core i7 (Intel Xeon is not supported)
- Memory: 8 GB
- Video Card: Radeon Vega II or higher with Metal support.
- Network: Broadband Internet connection
- Hard Drive: 95 GB
- OS: Most modern 64bit Linux distributions
- Processor: Dual-Core 2.4 GHz
- Memory: 4 GB
- Video Card: NVIDIA 660 with latest proprietary drivers (not older than 6 months) / similar AMD with latest proprietary drivers (not older than 6 months; the minimum supported resolution for the game is 720p) with Vulkan support.
- Network: Broadband Internet connection
- Hard Drive: 17 GB
- OS: Ubuntu 20.04 64bit
- Processor: Intel Core i7
- Memory: 16 GB
- Video Card: NVIDIA 1060 with latest proprietary drivers (not older than 6 months) / similar AMD (Radeon RX 570) with latest proprietary drivers (not older than 6 months) with Vulkan support.
- Network: Broadband Internet connection
- Hard Drive: 95 GB
![](https://staticfiles.warthunder.com/upload/image/0_Artwork_940/Ground/PLZ83_940_31f8693da1279cc76a9af65059c8b5ed.jpg)
In this update we have solved a complex problem with damage to bases and due to that damage multipliers for bases have been corrected for some weapons.
Which bugs have been fixed?
- Missing multiplier for the long-term fire of napalm bombs has been fixed. Prior to the fix fire damage was 13 times lower than it should have been. Now fire from napalm bombs deals serious damage to bases again. (Report).
- Due to the lack of armor of the bases the damage of bombs and rockets that have less than 25 mm pen (approximate thickness of base armor) was 1.7 to 20 times higher than it should have been.(Report).
- A bug that caused the reward multiplier for base bombing to be higher than it should have been for pods with bombs and rockets has been fixed. Prior to the fix the amount of weaponry in the pod was not taken into account.
- A bug that caused the reward multiplier for base bombing to be higher than it should have been for presets with large amounts of low-caliber bombs and rockets has been fixed. Prior to the fix the reward was calculated from the combined explosive mass of the weaponry, not from the sum of damage of said weaponry.
- The reward multiplier mechanic for base bombing has been expanded to affect rockets, as many rocket weapon presets are equivalent to or even outperform bomb presets.
These changes are improvements to the Bomber repair costs and bombing reward adjustment and are intended to equalize the reward for bases for different secondary weapons. These fixes are not related to the changes in rewards for base bombings which we planned to bring up for discussion which we mentioned on the release of separate BRs for aircraft for different modes.
Aircraft
- Su-25T, Su-39 — a bug that caused the permitted launch zone indication to not account for roll angle has been fixed.
- Su-22M4 (Germany) — a bug that caused the BR to change in ground battles has been fixed. The BR has been changed to the correct one — 11.0.
- The weaponry tracking camera now turns off automatically after the explosion of tracked weaponry. (Report).
Ground Vehicles
- A bug that caused the replenishment progress to continue decreasing even after it reached “zero”, which allowed some vehicles to replenish their ammo faster than they should by driving away from the point and back into it has been fixed. (Report).
- A bug that caused glow from overheating to not disappear on destroyed vehicles has been fixed.
- Object 279 — a bug that made it possible to penetrate the hull between the exhaust grids and hull roof using low-caliber guns has been fixed.
- PLZ83-130, PLZ83 — a bug that caused the low-caliber HE shells to be able to penetrate the armor when hitting the box near the driver has been fixed.
- A bug that caused the debuff on the turret traverse speed to persist after the healing of the crew has been fixed.
Naval Vessels
- A bug that caused depth charges with a set fuze timer to fall through the naval vessel and to not explode until reaching the seabed has been fixed. It also led to a lack of damage to tnaval vessels from direct hits. (Report).
- USS Flagstaff — a bug that caused target tracking to not work when the 40-mm gun was installed has been fixed. (Report).
- Bernau — detailed missile characteristics are now displayed in battle when hovering over the icon in the action bar.
Interface
- A bug that caused the nickname of the message author in the chat to be displayed incorrectly in some Custom Battles sessions when joining a battle after it has started has been fixed. (Report).
Please, note that the following points from this changelog have been removed as some changes were reverted and will be reintroduced in one of the coming updates.
- Churchill VII, Churchill Crocodile — a bug that prevented track marks from affecting the depth of snow on winter maps has been fixed.
- A bug that caused the use of marker target track to not always select the target which was being looked at and instead aim the camera to the previously selected target has been fixed
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.