That’s why I asked why the EFT doesn’t have variable scan speed. The Su30 has a variable scan speed from my understanding because it’s mixed ESA/mechanical.
It’s also interesting to see that not only the EFT in full ESA sector but also the rafale (and probably others but I don’t know them) have worse ESCAN speed than the medium width scan pattern of the SU30 which, iirc, is already a mix of mechanical and ESA.
Never passed by a TM tho…
I like his suggestion of adding broken lines however.
Then, they could give slightly more realistic scan speed to the different modes of the EFT by given variable speed depending on the mode, the speed being the average of ESA + mech speed, just like what I assume they did on the su30. That would not make the radar mechanic much more complicated than it currently is
Primary sources are clearly marketing lies…there is no way the ECRS performs better than a soviet radar from 20 years ago
I’m now 99% sure the AIM-9M locks onto a ghost-target. Had a match where I tried to lock onto an F/A-18C at 9 km from behind while it was constantly flaring. Aquired a lock, fired the missile (yeah no chance it would catch it at this distance but anyway) and it just turned left downward into the ground. Tried to lock-on again with another missile, it locked solid but the lock drifted left downward (like the first missile flew before). Relocked, again drifted left downward for multiple seconds with a solid lock onto nothing. This is way too reproducable to be coincidence and the lock-drift before firing and the missile direction after firing is identical.
If this happens in flight when the target is flaring (not flaring while locking still on rail) and seeker shutoff should be triggered that would explain everything.
The thing is, there is no need to make things up, we have a primary video of scan speed, that matches written documents.
Isn’t it possible that it tracked a flare for a second and when it lost it it continued turning in IOG ?
Not saying it’s a normal behavior, but I don’t remember IR having much issues with ghost targets.
I sometimes have bugs with any IR missile where I’d have a lock on someone and just as I fire my missile the lock freezes in the air, so my missile locks absolutely nothing and fly straight, but I’ve never seen IR missiles going for actual ghost targets.
Sensor view shows constantly “TRK” (no IOG ever mentioned) while the seeker cone effectively stays on the target plane while the missile turns away sharply (as if the distance to target is way shorter). So either sensor view is lying or the hop from plane to flare in the given timeframe is used for IOG-data. Anyway it shouldn’t use the flare as a reference point for IOG data at all.
The discussion about realistic scan speed is that according to gunjob :
So simply giving an average mech + esa scan speed in the whole pattern considered seems like an okay solution to this problem.
And add an extra limit to where targets aren’t continuously updated to model would also make a better distinction between full ESA and hybrid radars
No, Gunjob is responding to removal of TWS ESA when the target is away from radar ESA fov, that is if EF radar is looking max left, and the target is max right.
When it came to scan speed, developers “needed more sources”
Scan speed
Ah ok fair enough.
I still stand by the fact that approximating hybrid scan speed by giving only the average of the combined speed is sufficient without complicating the mechanic too much, which is what the devs seem to think because that’s how they implemented the (obviously much superior) Russian radars
Edit : obviously that average depends on the actual mode, if in narrow scan with only ESA, then you should have access to 100% of the ESA speed
Which is what we’ve got for all modes, even those that are just pure ESA.
Should be 190 for the 200x15 but the 90x30, 60x30 and I can’t remember the narrow mode, but those 3 should be 560+
Gaijin has all set to 190.
There are no complications when it comes to changing scan speeds, I did that myself
It is as much as changing 1(!) numerical value
Yes, I didn’t see your proposition, that’s basically what I was also thinking about.
Didn’t say it was complicated either, my initial question is why gaijin hadn’t done it for the EFT when they can do it for the SU30 just fine :/
Ok I thought the 190 was the pure mech speed, not the combined ESA + mech at 200x15 width, hence the confusion in my comments
Something something russian bias ;)
Idk, devs seem to belive that is is not possible to do it that fast at 571 degree/s, while at the same time we had things like Pantsir that for a long while wore astonishing 72000 degree/s, and even now boasts with 3600 degree/s.
Im fairly certain its a estimated figure for a combined ESA + Mech speed at least. But I could be wrong
Related question, anyone know why its 200x15 and not 200x30, on the grounds that its just any mode, being rapidly moved back and forth by the repositioner (as far as I am aware) and therefore it could and probably would be one of the larger volume modes like the 90x30 or 60x30?
Why to grind flare really hard? Any keybind to remove this CCRP that make me unable to drop my bomb because my radar keeps slaving my IRST.