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.
Its a known bug
https://community.gaijin.net/issues/p/warthunder/i/Vm8AVkoBoCDF
Pls support my bug report about tws datalink
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?
Some work at high altitudes as well. It depends on the model.
Ray Tracing was working perfectly for me since it was added on my 7800xt, why would you turn it off for AMD?
I hope that the graphics options in DX12 do not max out after restarting.
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.
Hope the bug with low resolution texture of other jets on DirectX12 will be fixed soon (or it just me lucky)
Is dx12 stable enough to play now?
Hard to say. After today’s update had some serious issues, like random drop to 5fps (from 60-ish) plus aforementioned texture issue.
But then again, it could be just me for I run the game in high settings on decent (but nothing too crazy) set up
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.
will they add a shader Pre-loading for DX12 soon?
Could someone please tell me the “time frame” these statistics on the new “Player Profile” represent. I have never played any vehicles except Aircraft since the Beta Days. And so then I havent played in ground battles, I have not played in anything BUT airplanes.
And so in Arcade Air, I have approx. 7500 or so airkills. In Air RB I have approx 2798 or so without looking.
However, My Player Profile says 2000 airkills in Air RB and around 375 in Air Arcade. I also have the “Ace” tag which means I have had to had 10,000 airkills in WarThunder. So the numbers on the Player Profile do not add up.
If you go to the “Statistics Tab” they are the correct totals. Why doesnt the new Player Profile reflect those numbers?
Is the Player Profile representing a certain TIME FRAME? If so, what is it? Because, I cannot think of any time Ive been playing Warthunder that my statistics have been close to what is represented.
Where and when are these numbers being pulled from? I do not like the new Player Profile, because it certainly doesnt represent my actual statistics. What is the time frame they are using?, the last 5 years, last 2 years?
Same here, random game engine plunges from normal 90-110FPS to 1FPS when entering a match.
No rhyme nor reason to it, deleting cache/compiled shaders have no effect.
GRRR
“DX12: Observed an critical error while recovering from a previous critical error” this happens multiple times per day since DX12 WT is out… Do i even need to send the report?
AMD QUESTION
Is there any timeline in place on getting the ray tracing fixed or are players with amd just waiting aimlessly? Not even a general time frame seems kinda weird.
Game now crashed because of DX12 3 times in 2 hours…