
System Requirements
- For PC
- For MAC
- For Linux
Minimum
- OS: Windows 10 (64 bit)
- Processor: Dual-Core 2.2 GHz
- Memory: 4GB
- Video Card: DirectX 11 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
Recommended
- 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
Minimum
- 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
Recommended
- 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
Minimum
- 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
Recommended
- 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
Update 2.45.1.61

Aircraft
- A bug that caused holding down the “Fire flares” control to block the use of the “Fire chaff” control and vice versa has been fixed.
- A bug that caused the point of interest to disappear when setting it through the Optical Seeker View has been fixed.
- Seeker FoV reduction for AAM IR seekers now happens after locking onto the target and not after launch. (Report).
- A bug where “Reset Radar/IRST direction to boresight” did not function correctly on radars with a vertically asymmetric scan area has been fixed. (Repоrt).
Ground Vehicles
- A bug that caused tank turrets to rotate backwards if the game stayed minimized for a long time while moving in battle has been fixed. (Report).
Sound
- A bug that caused the player in an aircraft to sometimes hear ground vehicles regardless of the distance has been fixed. (Report).
- A bug that caused the nuke siren to sometimes start playing much later after the nuke-carrying aircraft spawned in has been fixed. (Report).
Matchmaking
- The rules for calculating the average Battle Rating in Air Arcade Battles have been simplified. Previously, the rounding of the rating could depend on the number of aircraft in the crewslots when a player used fewer than three aircraft. For more details on matchmaking based on average Battle Rating, please check out the article on the Wiki.
Locations and Missions
- Japan — a bug that caused the building in the E6/E7 grid squares (on capture point C in “Domination”) to sometimes disappear has been fixed.
Interface
- The notification about enabled radar cyclic target switching is no longer displayed on the input from the “Horizontal Radar/IRST target cue control axis”. (Report).
- A bug that caused the nicknames of some players in replays to change to the nickname of the player who was watching the replay 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.