The F119 has lower T3 and higher SOT aiding dry thrust. The excess dry thrust pushes a draggier airframe to 1.7+ mach supercruise. This is aided heavily by the lower bypass ratio. If it was only a few percent better it would not have such raw performance benefit.
I was under the impression the convergent-divergent nozzle of the Eurofighter is not fully variable and that was one of the upgrades that set apart the TVC nozzle upgrade theorized for it.
But hey… they told ut that radar is WIP… SURPRISE, its same S**t as it was on dev.
It’s frustrating they couldnt get the Radar right, im prepared to give them some time to rectify it.
How does it fly or play are we all still just dead to the F-15E Spamraam?
Is the maws working?
It turns well, but the acceleration is about half of what it was on the dev
Why even have the dev server, its like they treat it as an opinion poll.
Russian and US mains whining about Typhoon. We had better nerf it…
Least if it tanks we might get the double amraam pylons…
Acceleration when the dev server closed was pretty much correct.
So its right on the live sever then?
I’ll test it at some point. But it feels about the same as it did on dev.
The TWS bug is annoying. But what else is majorly wrong with the radar? The scan speed isn’t great but as I’ve been saying for months there’s no information on that so we’d be hard pressed to fix it.
I was a bit hasty with half of that, yes.
Do I understand correctly that the RWR is now fully spherical?
Its a copy and paste from the Gripen, it should be a unique modelled Radar with its excentricities otherwise whats the point?
May aswell give every new jet the same Radar
Yes
600 Pure rofl
Reported it, should be 1250w.
BTW, that TWS bug is still here (don’t know if it is coming in todays micropatches, but thought I would let you know):
Oh, and do you have the British/Italian EFT yet (or maybe test drive). I am not close to any of them, can you test this IRST bug, please?
This bug is also still a thing
[DEV] EF-2000: Enemies not Displayed on TWS HUD in Sim Battles // Gaijin.net // Issues
Is the cockpit RWR display bugged? I remember it looking different on dev.
In game CAPTOR_M is an improved version of the Blue Vixen in game (the Gripen’s radar being a Blue Vixen C&P).
The ECR-90 (the original name for CAPTOR-M) in real life was a scaled up (larger / more powerful) and improved Blue Vixen, you could apparently trace every component of ECR-90 back to a corresponding component in Blue Vixen. The overall design and architecture of the radars are very similar:
ECR-90 had improved radar processing for stuff like NCTR and better ECCM, but it is to be expected that where the stats of CAPTOR-M are unknown Gaijin will fall back to using Blue Vixen stats, because of how similar the radars are in many respects.
ah yes its now a microwave oven
Update on this, @Gunjob:
It is not just uk_captor_m_pirate that is affected, but also fr_thales_rbe2 (and su_v_004 to some extent).
A bit of speculation that might be helpful:
Seems like the some of the ESA code was taken from V004 to be used on RBE2, but it was accidentally used on Captor-M with Pirate (mechanically scanned and the regular Captor-M does not have this).
V004’s scan rate permits to have such a short clear time, more or less (not in wide scan, it is too slow for that, so there it faces the same problems as the other radars above). However, Captor and RBE take longer to complete their scans, so 4 seconds is too short for them to update a track file, resulting in that track file being cleared. It is likely that the ESA code was taken from V004 and then worked upon, but they forgot to change that value.
Edit/Update: This should now not apply to RBE2, as it is now (or very soon) constantly updating targets. It also did not apply to V004, as that one already had that ability, so I was wrong about this issue affecting V004 (it only affected Captor-M Pirate and RBE2).
