You gotta see it from their perspective, is this something Smin knows the answer to, and if he does, is he allowed to say?
And if he doesn’t know, is it important enough to warrant chasing a dev for an answer? It could also be that there simply isn’t time to do this?
Maybe because those silly questions are very easy to answer
I agree decompression is an important issue, but again, Smin is not a dev. He probably doesn’t know. In all likelihood, the best he can say is “wait for official news”.
It may feel like that, but I almost guarantee that’s not the intent. I believe Smin is trying his best.
My advice would be to be persistent but polite. Maybe try again some other time of day. You will get an answer eventually.
But there’s genuinely no point to add f16v to tech tree, maybe as a event squadron or premium, but for tech tree there is a USAF equivalent which is what should be added to tt.
As for F-16 block 60 it could go between f16c blk50 and f16c PoBIT (BLK 70 equivalent) or come as sqv/event/prem
I’m not against F-16V come to US just not as a tech tree or if it is tt, then foldered. The USAF does not operate F-16V, HOWEVER, we have upgraded some of our F-16C to f16v standard with an even better EW suite on top of that
That would be much better fit for the United States air tree than like a ROCAF F-16V
They could have called the F-4F Peace Rhine and Tornado F.3 AOP by their names, yet they didn’t, so there’s not much reason to believe it’d be any different here.
Fair enough, if the V does come it should be a folder under than PoBIT so the main tt one is USAF but anyone who specifically wants the V can get it for half the RP
Your bets. Will GJ fix Gripen’s MFD before live or not? https://community.gaijin.net/issues/p/warthunder/i/HCdLLG0Ts9D6 @Gunjob сan you push this somewhere towards the bug reporting moderators? Just to see the answer “yes, we saw it. Maybe we’ll fix it” or “no, no proof, goodbye”