Not really. Early version maybe, but if anything Rafale holds some advantages like A2G load and range. In most other aspects they are damn close in performance
1 Like
Range is largely irrelevant to WT, and although the Rafale can carry more a2g what would they even have that is good enough for them to leverage that payload
This week and otherwise next week we have the start of the new devblog season.
In ARB, Id consider pretty equal, though the Rafale will be able to get away with running less internal fuel
in GRB, the Rafale will hold the advantage, especially if we are limited to SAL-only Brimstone 2s for our AGMs
in ASB… Its gunna be close. Range does have an impact in that gamemode, though both can super-cruise.
Something else to consider withwise to the range argument though. Hopefully they add bigger maps sooner rather than later.
1 Like
Of course, I’m mostly just here assuming based on the leaks I’ve seen so far. However my theory for how it went is something along the lines of:
- Thailand idea planned for Japan at the beginning of the year or maybe even sooner, F-5E FCU added to test player reception
- Ground subtree conceptualized, including more ASEAN nations (Indonesia, Singapore) following the trend of multi-national subtrees
- More work done on that since the initial leak in summer
- Sudden demand for a Chinese subtree becomes clear, likely around the time of the BVVD interview
- Idea of moving ASEAN assets to China conceptualized as a way to get such a subtree faster than Gaijin initially planned
- Leopard 2A4 addition planned to test reception, while new found “holes” left by the removed ASEAN nations are filled with simple C&P aircraft Thailand operated, like the F-5A.
This would obviously suggest the squadron 2A4 is canned, since player reception was clear with the leak.
Now the question is what that means going forward.
With Thailand going to Japan that basically ruins a standalone ASEAN tree and Singapore and Indonesia very much shouldn’t go to China so they will likely be added to part of a multi-nation subtree for Japan again.
Probably it’ll be just ASEAN Founders, not all of them though, since the suggestion for that was popular, and it leaves ASEAN nations like Cambodia, Laos and Myanmar to be Chinese subtrees Gaijin wants, alongside Bangladesh, Pakistan, North Korea.
But this is really just my idealized hope, there is a lot Gaijin could do wrong, even if I may stay hopeful they won’t.
5 Likes
It sucks, teamkilling happens , i get it. Especially iff friendly kills, but multiple times the radar has listed a friendly as an enemiy in my case, it happens . And now you got harriers in both sides of the battle in most battles. Which makes visual ID harder if they dont get close enough. I rarely team kill in higher tier with iff now , its a god send. But game is borked sometimes.
I think thats also a good idea , to learn iff on radar, but not all planes have it . I ran into a guy the other day that dodnt realize the symbolgy was different in PD and SRC mode after he team killed me twice in a row. Lol well he killed me 3 times but im pretty sure he got auto kicked after
I think what catches people out the most, is that not every aircraft has IFF, nor does every radar mode for aircraft that do have IFF. (they could with making the tooltip in the hanger more clear about which modes do and do not have IFF)
There use to be a bug as well, with switching between a radar mode without IFF to a mode with IFF and it not updating. But most often its in things like F-4S where im confident its because the person has no idea what IFF is.
As for Harriers on both teams… At some brackets yes. In this one. Nope. It was a 10.0-11.0 lobby. AV-8S would have been in the bracket below and the AV-8B+ would have been in the bracket above. The ONLY harriers in game had to be the SHar and so friendly. (unless someone had been insane enough to bring a 9.7 to fight 11.0s, which they hadnt)
It is exactly that, which could be demonstrated in a tutorial
Its funny cause whenever i get teamkilled in sim its either mid dogfight , or coming back to base to rearm , both are situations which give the teamcmaye ample time to see whos the bad guy. I also was unaware of that bug but it makes so much more sence now for issues i had in the past. I was usually awitching radar modes trying to get a lock and what not.
Yeah, MP definitely isn’t what it used to be.
Even if you do everything right, and send it into the dirt, it feels very common to get fragged by the splash.
These E/I’s are launching with such insane velocity, and from so high up, that the AoA these AMRAAM’s come from are damn near unotchable, unchaffable, and un-MP-able lol.
1 Like
Yeah, similar for me too. And yeah, use to catch me out all the time in the FGR2.
(I also think people have this expectation that the missile will either go for the target it was fired at or self-destruct and quite often i was taken out by a missile that swapped targets. It seemed like in the last ban wave, a lot of people were TKing like mad because they were spamming missile without thinking about proximity to teammates )
cant it bring the pgm? arent those more or less equal to kh38?
Typhoon? No
ePaveways / Paveway
Brimstones 2
Spear 3 & EW
Storm Shadow
ALARM
BL755
Not really. They’re way more clunky, and make a huge ploom of smoke all the way to target.
As I understand it, the Alpha Jet(TH) was the one which was expected to appear in update " Alpha Strike ", the FCU was an unexpected detour. But we already know that gaijin needs at minimum six months to prepare a vehicle, and often takes longer - sometimes several years pass between a vehicle being ready and it being added.
Even if the FCU had been planned to come alone in Feb, it would’ve been decided to develop it in the middle of 2023 at the latest. Since we have now seen the AV-8S, F-5A(TH), and F-5T SCU in the files, it credits the leaks towards the likelihood of a Thai subbranch ( at the least ) having been the plan; the aircraft planned to compose a TH subtree probably started their development process together, more than a year ago. Developing multiple vehicles to appear together would take longer than the 6mo minimum that 's been mentioned for individual ones, logically.
Since until recently our leakers understanding of the plans w/ ASEAN was that it would introduced as part of Thailand, under Japan, it would follow that their leaked ground vehicles, plus any of their other kinds of vehicles yet to be seen, have been in development for a similar or the same timeframe as the Thai ones: more than a year.
The thing is, it really wasn’t. And the players who even know abt the leak ( us on the forum, and some small scattergroups on social media ) are still a very small group inside of those who interact w/ the game outside of playing it, which is itself only a tiny fraction of the playerbase total size.
We have no way of knowing if the leak or reaction to the leak could’ve been a factor in the singapore Leopard 's non-appearance. Not even if it was a factor.
Making predictions as if it was, while we still don’t have much concrete information on what ** is planned** for the update in a few weeks ( in comparison to what might be, based on partial evidence ) compared to what we had for the last two, could mislead us to miss critical information should it appear in the time being.
3 Likes
Yes, the point being the people that did see it didn’t react exactly very positive, especially those from the respective countries.
Of course, that was just my interpretation of the leaks I’ve seen on the forum and otherwise. It is never guaranteed, best we can hope is they do what is best for the game and its players.
2 Likes
I can confirm this. The reddit forum for example conpletely believes gaijin’s lie that the leak was fake and ASEAN was never planned for china.
5 Likes
Id say this thursday the earliest
Edit spelling
Highest Leopard 2A4s in-game currently are the Canadian Leopard 2A4M and the Leopard 2PL I think.
Unless I missed one
2PL would be higher though if it got its actual best round (unless Gaijin fixed it then idk)
Also not sure if the 2A4M was supposed to have it’s armour fixed