This loadout has given me some success on the Harrier GR1
and i’ve done this quite often on the Typhoon, at least when Aim-9M use to work.
and especially before the twin AMRAAM. 1 AMRAAM for 2x Aim-9Ms was a worth while trade, these days… I prefer the 2 extra AMRAAMs over the 2 extra 9Ms, but Ive got the loadout made just in case
I did similar with the F-18C took half AMRAAM and half 9M’s
I noticed this too when using AIM-9M, AAM-3 and PL8B, it’s weird.
Even had a AAM-3 get one flared rear aspect.
Aim9Ms dont like to use their IRCCM
Worth noting the update rate is the same for all volumes, detection is quicker in smaller volumes but that’s just a product of the volume being smaller but once a target is detected, ESA updates start and the update rate is the same.
I assume no changes planned to revert the ESA area scanrate back to what it was (571°/s) instead of the mechanical scanrate (~200°/s) for all volumes?
And while we have you here: Could please take a look at this report? Just a graphical inconvenience but it just looks strange: Community Bug Reporting System
Ah, thank you for the correction.
The detection with the mode I use is very fast, it can consistently track the entire furball, and also save you from ambushes.
As I mentioned previously, no. Not without some more evidence, which I have been trying to track down.
This evening sure.
Is this a common occurrence for you? Was the video from a replay or recorded live in the match?
I never had anything like that happen to me
I have had this happen to me multiple times since the major update. Along with the Aim-9M just switching to target a flare like it was a 9L (Sean posted a good clip of this yesterday and i’ve had this too (clip)). Between the 2 issues, i’ve got like a 90% failure rate and have taken to ripple firing missile to ensure at least one hits.
The video is from the replay, but matches exactly what I saw in the actual match (AMD Relive keeps disabling itself for some reason)
This is another example from just after the update dropped
and @kensai16 created a report for it doing this 2 months ago
https://community.gaijin.net/issues/p/warthunder/i/bT0XeTXyaQ3X
Is it just with track suspension IR missiles that you have those issues?
I only had similar stuff happen with the derby and r-darter where the seeker goes dumb and drifts away from the target for no reason but happens maybe 15% of the time at most. (You know the thread).
With other fox 3s I don’t have that issue, at least I never noticed it, and with IR missiles I never had that.
I havent observed this exact behaviour with AMRAAM yet and I havent played anything with any other IR Missiles since the major update.
I might have had something similar happen with AMRAAM earlier actually, but totally forgot to log it
So you are saying that 9Ms will randomly turn away 90% of the time?
I’ve played a lot of matches in the last days while carrying 9Ms and no issues here.
Is that happening in every aspect? Or mostly rear? I don’t usually launch 9Ms from rear aspect since they are easily flared like that. Only when someone overshoots me or something like that at very short ranges. So maybe I need to experiment them at rear aspect more
@Morvran in this clip I dont think any issue is present. The flankers have an easier time flaring off track suspension missiles because they flare upwards.
So even in side aspect, where track suspension is harder to defeat, with the flanker by naturally turning into the missile and flaring you are putting the flares right between the seeker and the engines.
With most nato jets that would be a easy kill since they flare downwards and the seeker would not even notice them unless the target turned away instead.
Ive had it side and rear aspect and its common enough that I rarely switch to 9Ms at the moment.
Its a seperate issue. Though no less annoying.
The expected behaviour for seeker shutoff would be for the missile to see the flare, switch the seeker off and then continue to the targets last known position on IOG. Instead the missile appears to be actively re-targeting the flare and turning towards it, as if the seeker shutoff never happened, which defeats the entire point of it being an IRCCM missile with seeker shutoff. You might as well just equip Aim-9Ls
Probably because it was at very short range and the seeker couldn’t find the jet so it went for flares after doing suspension between those flares.
Yesterday I flared 3 aim9m in a row at around 1km away from rear aspect.
Overload the seeker, move a bit and avoid keeping afterburner so the seeker decides to follow the flares after suspending tracking. Works like clockwork
Ive had this happen with 3-4km shots too.
It feels like the seeker shutoff is incredibly tempromental
It can be done at distance but you have to flare more and move more to avoid the IOG seeker relocking you
No, this is not what im explaining. Im talking about the target flaring and the missile just retargetting a flare and turning towards it instantly, Like I had fired an Aim-9L and not an Aim-9M. Quite often with the first flare
Ok I see what you mean. Yes that sometimes happens. 9Ms being single flared at distance or switching lock to a missile fired by the target.
I would need to take a look at those in the replays to see if I suspect of any issue. But I never bothered. Next time I’ll take a look.
