Quick ad hoc MWS test against radar and IR threats.
Threat 1: R-77-1, launch 82km, detected by RWR and not by MWS. evaded at ~4km
Threat 2: R-73, launch 6km, not detected. evaded at ~3.5km
Threat 3: R-73, launch 4km, detected by MWS at 3.5km, evaded at 2.5km
Threat 4: R-77-1, launch 4.5km, detected by RWR, and by MWS at 3.5km. Not evaded.
It is HUGELY underperforming by the looks of things. 3.5km is also a seriously concerning value, as this is not nearly enough time to evade any AAM. SAMs (e.g ADATS in test drive) seem to be detected at a more reasonable distance (7-8km?) but still far too low.
In dogfight tests against Su-30SM I also had erroneous warnings while the enemy was flaring… which doesn’t quite line up with the “Radar MAW”. Confirmed that they were not using any chaff for the entire engagement.
They’ve done… something? It doesn’t seem to have changed much though and may be worse in places for now. I’ve also taken a quick look at the datamines and there seems to be a GTM section, a surfacesearch section and a surfacetrack section so it seems we might be getting something.
This should be pretty helpful for effeciency, but most interested to see if Priority Track is planned for this update as well as any improvements for the radar actually detecting things
It’s not listed as fixed on the report site, while the MAW bugs are, so i’m not too sure.
On the other hand, we do have this “TWS+” which may involve provisions for priority track.
Yeah, given the fact the TWS in medium mode cant keep track of the mig-15s doing a lazy turn in test flight, the EFTs radar has got a LOOOOOONG way to go yet
If i’m being entirely honest, it’s worse than in live right now, which suggests they tried to do something. On live it can (somewhat) track the 15s in testflight, but in dev it simply fails. It drifts off target for seemingly no reason and loses tracks on straight flying threats.
Positives are we know they’ve tried to do something and there’s a clear differentiation between modern and older radars now, which means we can have high hopes (in severe moderation) that it may be fixed before live.
I expected a working Radar by now its been over 2 months.
we go on the dev and see they have changed the scan pattern and the Radar is still struggling to track.
We aren’t asking for something new and revolutionary here.
Most likely they got a “number twist” on the RCS part of the MAW which is currently set to 1.0 m² for the 20 km range. Should be 0.1 m² instead and 11 km for 0.01 m² targets like MANPADS.
With the current settings it detects enemy Air-to-Air missiles only at ridiculously short ranges of a few kilometers and MANPADs at even less.
Yeah but even then there’s still something wrong, either missiles have rcs modeled wrong or the sensor itself is modelled wrong, 1.0 m² at 20km is still 0.01 m² at a little over 7km.
Could be wrong here now but wouldn’t the MAW have to use unrealistically low frequencies (for the given antenna size), like S- to X-Band to have that bad of a resultion at the given distance?
True, so something other fishy is going on currently…
There literally ain’t any information from what i saw, maybe this image could be a source if we consider every ring to be 25km, that missile is being tracked at 25km+. Also there should be evidence that the maws should be able to track planes or else how could the iris-t do a 180 to kill enemy planes and missiles, which apparently was stated in a presentation.
MAW tracking planes was already mentioned to the devs which they shot down as it would be extremly OP to have an all around AESA in game which would be able to track all fighter size targets (and FFI them) at up to 44 km in real time while also being able to lock onto and fire missiles at them.
