So after abit of test flying… now maybe it’s because they’re slow moving Mig-15s, but is anyone else finding the track while scan barely works - its seem to be incredibly easy to notch out of TWS, and the radar just seems to be forgetting what its looking at, so I’m struggling to get a kill with the aim-120s at even 15-20km
The Gripen C doesnt seem to be struggling with this at all
One one hand, I am happy they did so. On the other hand, I am bitter that the Su-27 has been here for a year now, yet its IRST is still nowhere near what it should be. I was really looking forward to sneaking around and picking off targets with 27ETs, yet instead we got a copy-paste IRST of the 29 on release, with constant updates that would fix a bug and introduce another.
Maybe the EFT and Rafale getting added will finally be enough for them to notice and fix bugs with it, but by this time the window for the prime of that kind of gameplay is kind of gone.
But hey, this is finally a reason for me to go past tier 5 in UK.
Wow, nice rushed patch, still WIP
Eurofighter spaded with two aim9 still doesnt accelerate in a 90° climb… TWR is >1,1 in interceptor loadout…
worst patch in the last two years
I can do cartwheels like a cartoon, launch AIM-9M or AIM-120 mid dogfight, and recover without any signs of departure
Yeah the radar feels a bit disappointing, don’t know what they changed since the dev server but the Foxhunter is definitely better still in TWS scan rate and volume.
had the same issue too, even on the smaller and faster scan it would drop/forget targets super easily even in a head-on ~25km out
I made this bug report agian bc it seems like it isnt getting noticed.
https://community.gaijin.net/issues/p/warthunder/i/XBUVLodmckWy
If you want to read more about the EJ200 and why its designed how it is, you can read about that here: https://web.archive.org/web/20140520001842/http://ftp.rta.nato.int/public//PubFullText/RTO/MP/RTO-MP-008///$MP-008-02.pdf
Additionally: I remeber you saying (maybe in the other EF thread), that the Convergent-Divergent-Nozzle wasn’t optimal for supercruise/supersonic. In contrast to that, the source (and everything else I found about that) states that this C-D-Nozzle was chosen because of its supersonic capability in enhancing the endurance by 25% and reducing the tail air drag of the EF opposed to other nozzle designs.
I think it’s because they’re slow moving mig15. I had the same issue while testing the Rafale in the test drive. The TWS struggle to keep them updated, and Rafale’s scan rate is easily two time faster than the EFT.
IIRC the test drive Mig15 keep a constant speed of 500km/h.
How is the radar? Is it fixed… is it quick like it is everywhere written when talked about its scan speed? Or its just LAZY copy paste of blue vixen.
This looks a lot like a copypasta of the Gripen radar. Let’s play a game? I’ll send you 2 gifs of the radar in action, and you’ll guess which is Typhoon and which is Gripen?
You joking right??? That thing should be capable of combining AG/AA modes with good refresh speeds.
Are gaijin devs on drugs again?
No A/G. At all
Would explain how they came up with thrust/intake losses of 13,5% dry (6118 kgf uninstalled, 5390 kgf installed) and 11% wet (9177 kgf uninstalled, 8260 kgf installed) for the engine.
The convergent-divergent is great for supersonic afterburning performance but is actually inferior to the other designs for supercruise in particular. The most optimal is a design similar to the F-22’s.
This is a good document, thank you. Now we can see that the two documents align quite well and it is explicit that the EJ200 was described in my previous post.
It is clear, the EJ200 is not well optimized for supercruise. If it were better optimized, the bypass ratio would be smaller. The pressure ratios and temp limits would be retained, but there would be heavier focus on dry thrust and this would require a lower T3 temp, higher SOT, and inferior TSFC during afterburner operation to achieve the same afterburning thrust capability. They simply had hard requirements to enhance the SFC during dry operation as well as during afterburner. They simply could not meet subsonic cruise SFC requirements and supersonic re-heat SFC performance without the larger bypass ratio and within the temperature limitations.
It is this bug (go up the chain of replies a bit for more details).
There is a typo in radar’s config file (only on the Captor-M with Pirate, for some reason) that sets the time it takes to clear a target that the radar has not updated to only 4 seconds. So every time you have a TWS target that the radar was not able to update in 4 seconds, it just clears that contact off of the scope. It also centers the scan area if you have have target cycling turned on (you don’t manually move the pipper).
Which likely means it cannot see helis in TWS mode :(
Where is Typhoon’s radar and where is Gripen’s? No joking
Gripen radar is pretty mid too, dont even use TWS with the R-Darter as it always loses track and just misses.
