1. War Thunder
  2. News
  3. Update 2.45.1.50

Update 2.45.1.50



[h2]Aircraft[/h2]

  • Tornado GR.4 — a bug where text keys were displayed on the HUD in the cockpit when selecting AIM-9 missiles and BOL countermeasures has been fixed. (Report).
  • F/A-18C Early — a bug where target acquisition of any target by the targeting pod prevented seeker activation of AIM-7P missiles has been fixed. (Report).

[h2]Ground Vehicles[/h2]

  • A bug that led to desynchronization of the position of moving ground vehicles has been fixed. (Report).
  • The following changes will, among other things, result in the sound on ground vehicles becoming more consistent, stable and predictable overall, in particular, it should no longer be the case that ground vehicles at distances of up to 215 meters, which are behind obstacles, do not make engine and track sounds:

    • The principle of absolute detection of enemies in ground vehicles has been changed. The "absolute detection" parameter no longer depends on the level of the vehicle crew's "Keen Vision" skill and is equal to the value that was previously the maximum for a fully upgraded “Ace” crew — 215 meters (for vehicles with the "Improved Optics" modification, this parameter is 280 meters). This parameter is responsible for the range at which information about enemy vehicles is transmitted by the server to the client, regardless of whether the player sees the vehicle or whether the terrain or objects in the location interfere with this. The change has been made for transparency — despite the fact that the parameter was described in the crew's “Keen Vision” parameters, its presence, its impact on the game, and connection with sound in cases where the vehicle is out of direct line of sight were not obvious.
    • A bug where the sound of the engine and tracks of a scouted target might sound from greater distances than the engine and tracks of a target detected in other ways has been fixed.
    • The theoretical radius of audibility of the engine and tracks of ground vehicles has been reduced from 400 to 215 meters. In fact, this did not noticeably affect audibility in combat since previously, due to volume settings, vehicles further than 215 meters could only be heard in ideal conditions (in silence) along the line of sight, while behind obstacles, vehicles could be heard at a distance of more than 215 meters only due to a bug with the increased range of sound playback for scouted targets.
    • These changes, among other things, will lead to the fact that now information about enemy ground vehicles will appear on the client either at a distance at which the sounds of the engine and tracks are just beginning to be played (with minimum volume), or even at a greater distance (in the case of vehicles with the "Improved Optics" modification), which will eliminate abruptly appearing sounds of engines and tracks of ground vehicles.
    • The ranges of the sounds of gun shots have not undergone any changes and are still always reproduced if the shot occurred within a radius of 2 kilometers.
    • A bug where enemy engine sound could disappear behind obstacles, leaving only the sound of the tracks, has been fixed.



[h2]Naval Vessels[/h2]

  • A bug that caused the turrets to not adjust fire to the crosshair in Naval Arcade Battles and instead fire at the same location on the enemy ship has been fixed. (Report).
  • A bug that caused modules in the X-ray on coastal fleet vessels to sometimes disappear in test sail has been fixed. (Report).


[h2]Sounds[/h2]


  • The volume of sound of a critical angle of attack has been reduced for all modifications of the F/A-18, as it could have been too frequent, hence annoying.


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.