update when?
when all the bugs are ready
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
That’s an issue, not an issme.
Why do you specifically want f16v as US end of line f16 anyway?
A better question is why are you so vehemently against it?
Need the F-16z surely to be the end of line. Unless the US adds more letters to the alphabet so they can make more F-16 variants :D
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
F35 replace F-16C, but F-16Z will replace F-35
The F-16V is more unique than the F-16C, and I dislike “early” and "late’ names.
They could call it F-16 PoBIT or F-16C PoBIT
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
Because Magic 2 is good enough and there’s nothing there after MICA-IR (for now)
Peace Rhine is the F-4F late in game and it wasnt upgrade or vehicle name but the name of the program. They werent called like that in service
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”
Ayeeee nice!!
but then weren’t the F4Fs still called F4F after the ICE program?