That means that the engine temperatures ( white / yellow / orange / red) are triggered at lower temperatures the longer the game lasts. So even with just 100% or lower throttle you will get a flashing red a 83° C.
If it’s a bug and not a historical issue, then yes.
Otherwise no.
This is a bug and was reported as such.
Similarly how the Leclerc’s UFP shows 3 plates yet only models 2 in the damage model, a bug and that was accepted as such.
You clearly don’t know the difference between game bugs and historical issues.
The standards for bugs have never changed.
This is not a historical report.
Saying “This was overheating a few months ago and now it doesn’t.” is a bug report, not a historical report.
Unless you have evidence of a changelog intentionally changing the FW190 to never overheat, it’s a bug.
And again, what kinda bug is this? Someone, without any evidence to back it up, FEELS that the Fw 190 As ran too cold (even though this nerf also affected 190 Ds)?
They did overheat before, just took a while. The person who made that bug report did not attach any evidence that this wasn’t the case in real life, so chances are this might have been an ahistorical nerf.
On top of all that, you’re not even right to begin with. Nowhere in the bug report did it say they overheated before and now they didn’t.
Again, if “I feel like this shouldn’t be the case” is enough for a bug report, then I got plenty of “bugs” to report.
Same on basically any side, even today reports are often exaggerated, like the nuclear plants of a certain country starting with i that according to someone was completely destroyed only IAEA said they can restart in a month.
However regardless they are sources and nothing as of RN seem to contradict the FW190s flying with full power for an extended period of time. Also how else will we know if we weren’t in the cockpit?
Well hegseth did do a report on this but same could be said about claims in most modern day combat. Also it is partially hard to know what you destroyed vs what you damaged or just got a ‘hit’ since u aren’t in WT. Like how german combat report sighted way too many T-34s in 1941 when in reality half of them were KVs and other stuff.
gaijin making any excuse to give German prop players the worst experience known to man while simultainously buffing every other nation and ignoring bug reports
The “Tank battle of Prokorovka” myth is one of the most used examples about truth and reality. Several decades the USSR claimed that they had killed hundreds of German tanks in this battle. Current status is that the Germans lost 5 or 6 tanks - whilst they scored ~ 200 tank kills. A 40:1 K/D.
I was actually referring to combat reports described in memoirs. So combat reports based on actual experiences - not war propaganda.
As a side note: There is nothing wrong with being patriotic - but it is obvious that you have never flown a 190 in wt or that you are able to contribute to the topic “engine nerf”.
So as they are accepted amongst historians - they have to be valid for gaijin too. Otherwise this whole “historical accuracy” claim by gaijin is worthless. Oh - we were there before…
Something similar has been happening to the P-51. Flying them, after a few minutes and not even using WEP, there comes a point where the temperature rises to the point where you can no longer fly at 100%, having to go down to 97, 95 and then to 92% to avoid breaking the engine. I don’t know what it’s like in the FW-190, but in the P-51 it’s clear that it’s because they don’t model the radiator air intake opening well.
The verification and scrutiny was conducted by the developer. The report was passed, as if did indeed highlight an issue that needed to be reviewed. A developer then reviewed the report, cross checking with our information and sources on the aircraft and came to the conclusion answered within the report.
Sadly historical fixes cannot be reverted based on “demands” because you disagree with the outcome.
If you have legimate information or evidence from testing the aircraft that shows somethings incorrectly been modeled, you are free to make a report. In this case, as mentioned above, the developers reviewed this report and did indeed find an issue based on known information.