War Thunder background
Update 2.37.0.178

Ground vehicles

  • A bug that caused the button for launching a UAV to change to the button for deploying a UGV activation, causing a tank to spawn has been fixed. (Report).
  • A bug that caused shells replenished on a capture point to be damaged if they were lost in an ammo rack fire has been fixed.
  • A synchronization bug that caused the destroyed reactive armor to appear functional for the player who has spawned in after the destruction of said armor has been fixed.
  • A synchronization bug that caused the player to be visually shooting for other players if the player was holding down the firing key with a broken down autoloader has been fixed.

Aircraft

  • Now when landing on an enemy aircraft carrier, a player will surrender just like it happens when landing on an airfield.

Interface

  • Following the Roadmap: A notification of when a reported player got banned has been added.
  • A bug that caused the reloading values for the top crew in the X-ray view to not display or display wrongly for ground vehicles with multiple cannons has been fixed. (Report).
  • A bug that caused the reloading values for the top crew in X-ray view of some ships to not reflect the actual values has been fixed.
  • A bug that prevented the research window from closing if after researching all vehicles a player had some extra research points left has been fixed.
  • A bug that caused the icon-tooltip informing about the possibility to remove a vehicle from the crew slot just by dragging it to not fit into the “Remove from the preset” button, located in the “Change vehicle” menu 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.