A bug that caused the radio altimeter to show incorrect values at altitudes above 15,000 meters has been fixed. (Report).
Graphics
The maximum intensity of the visual effect of afterburners now depends on the degree of damage to the engine. The more damage to the engine, the less pronounced the effect becomes.
Excessively bright reflections on cockpit instruments with Ray Tracing enabled have been fixed.
A bug where 100% motion blur was always applied to aircraft debris, even when the game was paused has been fixed.
A bug where it was possible to enable the Ray Tracing option in the graphics settings with an AMD graphics card even though AMD RT is not supported yet has been fixed. We are working on expanding Ray Tracing support and in the future it will additionally be available on AMD graphics cards.
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.
How is this possible? The module costs 13000, and a completely different module was selected for research. Yet, for the second match in a row, the game tells me that Mk.13/18 is being researched, even though it’s already researched.
I noticed that the F-104 in the Italien TT accelerates a bit faster now and you can drop bombs above Mach 1, while the F-20A got this capability removed and if “feels” like they made some changes to the flight model too.
A detailed changelog would be welcome, especially per vehicle.
No, my case is different. The battle ended, I unlocked the module with Mk.13, invested free points into the PGM module, and started the next battle. After that, it told me that the research points went into Mk.13, which had already been researched and purchased by that time.
The f20a and others lost their ability to drop the napalm above Mach 1 with the last major update
Wonder why they’ve reverted that for only the 104s taf and not others so far?
Several questions. When are they going to fix the engine sound? Since this last update, when you are stopped with the tank, you can hear the engine sound as if the driver was pressing the accelerator all the time. And when are they going to fix the Variable sync problem? It has been several years since it appeared in the options, in an update it disappeared and has not come back. And when are they going to fix the vsync problem in general? Since the last major update, after each patch I have to restart the game for vsync to work.
Less premium tanks and more fixing the errors, which have been accumulating for years.
I think it has more to do with the name of the metric rather than the means. The metric in 3rd person HUD displayes the distance from the aircraft to terrain vertically below it, which IRL is measured using a radio altimeter. Hence, we have it known as radar altitude.
I would like them to keep that option available as it is now, simply because of all the other metrics we have irrespective of the properties of means of measurement (we have Mach readings on all aircraft, we have fuel readings on all aircraft, even those that do not irl, barometric altitide always works perfectly, etc.)
Might be a nice touch to have the restriction by altitude for radar altimiters in the cockpit HUD, however.
