Hmm… it might. This doc is from Flame as well, so not sure, unless there is some context I dont know about. But that’ll be an @Flame2512 question for tomorrow
I see.
My friend does much more dogfighting than I do, so it is probably just skill difference.
Is there a comparison between EFT and Rafale, or J-10A?
I would like to see that.
Thank you.
Okay, just found something a tad interesting, and I have no idea if this needs bug reporting or not.
When you have Litening III pod equipped, you can still view the PIRATE feed. In both the Harrier Gr7 and GR4 the Tpod overrides the inbuilt camera and you cannot access it.
@Gunjob Does this need a bug report or do you think this is intended?
Partly true. The MiG-29’s IRST is tuned correctly for non-afterburning targets (15 km detection for a side on MiG-21 at full dry thrust).
The main problem that all IRST’s (and IR missiles) share is that afterburners do not provide nearly the increase in heat signature that they should.
Another problem is that a couple of IRST’s are simply not tuned properly. Su-27 is a major example. The manual provides that it can detect a Mach 2 afterburning MiG-25 from 90-100 km HEAD ON. 14 km for a head on non-afterburning target on the deck and 50 km for rear aspect.
What do we have in game? A cap of 30 km (can’t lock anything past that). One of the hottest planes in the game, the F-14, is detected from like 10-11 km with no afterburner head on. IRL test was done with Su-15 with around 14 km detection range, so if you take a comparable aircraft, the J-8B, you will get measly 4 km. Locking a side on target in a match, the most I was able to get was around 20-25 km, for a supersonic F-15 on afterburner. Nowhere near the performance we should have.
The 30 km cap was “fixed”. Nothing really changed, however. The IRST is technically capped only at 100 km, but the range gates are still at 30 km, so we are stuck with that.
Currently, both the Eurofighter and the Rafale IRST have the same exact problem. Both are technically capable of more, but are capped at 30 km.
If they don’t change anything, these seemingly advanced IRST systems will all be barely any better than the one on the MiG-29.
Ridiculous
Not a huge loss, they’re utter trash in-game anyways, and borderline useless.
Truly a bruh moment.
@MythicPi have you tried toggling the engine off and on again when on the runway, the start-up sounds awesome.
I dont use the dev, i tend to wait for the live server, since i dont bug report anymore, happy to hear it sounds nice tho!
Thank you for the reply.
The thing that I find interesting is that the only bug reports that you have decided to link to are ones that show that it is underperforming. What about the bug reports that show that it is overperforming? Don’t you think that it being off of the claimed time-to-climb by 30 seconds to be a bit optimistic?
The idea that these two turbofans share similar thrust curves is entirely absurd. The idea that thrust does not drop off until 2.2 mach is also absurd. What is this source?
Additionally, the “full AB thrust” indicates 30k lb-f when nearly every source indicates 20,200 lb-f uninstalled. Installed thrust losses would not amount to 5,000 lb-f per engine and 30,000 lb-f is far too high for a single engine. So what is it saying? Complete nonsense.
The same can be said for the Rafale’s M88, which produces 16,900 lb-f uninstalled. Installed thrust would be less, not more. This chart states 25k lb-f, which if combined would be short nearly 9k lb-f and we know that intake losses would not amount to 3,500 lb-f per engine. It is also clearly far too much thrust to be discussing the performance of a single engine. Make believe data.
Do you know what targets under which conditions this is for? I don’t think we will be able to report anything, unless we can give them the target plane, altitude, speed, power, and aspect.
The only reports i’ve seen so far are the ones ive seen linked in this thread, the German Typoon bug list or ones i’ve seen Flame submit via his profile
In fact, after a quick look through the bug reports for it on the website, I dont see any bug reports to nerf it . Heck, just found this one yet to be passed:
https://community.gaijin.net/issues/p/warthunder/i/75Meg57oyRDW
There is a report regarding overperforming acceleration which was closed as not a bug with the dev comment of:
The current FM of the Typhoon on dev server has not yet been configured correctly. As such, its performance is not accurate or representative at this time.
Now what changes this will entail will remain to be seen, but given the FGR4 and F-2000 dont even have the right names for the engines, im not surprised.
Now I do reckon the acceleration on reheat is too high, but not dramatically so.
Again, it states “under 2:30” not “it takes 2:30”. The time to climb should probably should have been around 2:10-2:15 I reckon, so thats only a marginal decrease in RoC needed.
This is the reason I am withholding my bug report for supercruise, unless someone beats me to it. I may be busy the following week or two.
As far as I am aware, Gunjob and Flame have given the Devs every scrap of Primary source data they have and the devs just havent finished implementing them yet. I doubt you’ll have much to report with wise to that and besides, Flame has already started to report it underperforming
https://community.gaijin.net/issues/p/warthunder/i/uM50xadDrBYA
The British and Italian Typhoon’s engines seem to have the name of the engine used on the Tornado. But I don’t know if the British and Italian Typhoon perform differently because of it.
Maybe the afterburning thrust is too high, but I don’t see anything substantial that needs to be changed in that regard.
I think its just a naming issue as well. As for thrust. I think AB might need dropping slightly but not by much, 5-10% tops and then dry thrust increasing
I see.
Someone reported that the Rafale’s empty weight is incorrect (heavier by approximately 900 kilograms ingame). So might be interesting to see how it performs in relation to the Eurofighter after both aircraft have been changed.