Although in this case I think some numbers where miscommunicated to the devs so nothing with ill intentions on their end
Oh, no… Another admin replaced “accepted” with “not a bug”
I think I’m going a little crazy :(
Dev updated again I think
Whats your version?
Is it 2.42.0.23?
yes
Then its allready old…
well I suppose that makes up for no AIM120 on the inner pylons, it weird they denied that but are adding the double rack.
They might be, there is a lot in the files that never sees the light of day
Can someone explain me recent FM changes?
It’s crazy how they have gone from people dealing with reports to deciding that they are now the leading expert on military weapons, directly going against official documentation because they ‘‘think’’ and ‘’ believe’’ that something can’t be a certain way like with the Stingers.
And they weren’t good at the former to begin with.
MANPADs 2.0
I wouldn’t be surprised if it’s our beloved trikzzter under the disguise.
I wouldn’t be surprised if they changed it to “Bug reporting manager X” because of him.
Oh, that’s 100% why it happened. He was doxxed if you remember. I mean doxxing is no joke and a really bad thing, but I totally see why everyone was THIS mad at him.
Also guys. I think the only thing we should fight for rn is FM and engine performance. Because unlike anything else engine performance and flight model would remain the same throughout every other model of Typhoon we will get in the future
Radar as well. Currently its definetly a placeholder.
Don’t they use 1m^2 range? And from what I could find captor M does have that range. Scan might need tweaking though
Its pretty much a 1 for 1 C&P of Blue Vixen at the moment. Its underperforming quite a bit, especially in scan rate. Its suppose to have a scan rate that can achieve some of the same functionality only found with e-scan radars.
PIRATE is also underperforming a lot.
How much is the EFT underperforming now in terms of maneuverability?
ITR and STR?