As can be seen here, the DASS format MFD does not display incoming missiles in the cockpit, which effectively makes all the MAWS changes the EFT got during this update worthless if you fly in sim without the in-game RWR overlay. I have a short clip and will be making a bug report for this critical missing feature.
One thing I need to test quickly first is that maybe its due to the ranges involved, since the DASS format is permanently locked at 40NMi (good for irl, not so good for in-game), so maybe the missile range was too short to have it show up at all, but I’m pretty sure thats not the case and gaijin has just once again forgotten to model stuff in the EFT’s cockpit properly…
As a sidenote, tho it likely wouldn’t be accurate to IRL (at least afaik), the ability to downscale the DASS display range would be nice… 40NMi (~74km) is massive, and makes it ludicrously hard to figure out where threats are when within ~15nmi, which is when the vast majority of WT engagements occur.
The 40NMi likely wouldn’t be an issue irl either since the HMD would presumably be displaying all friendly and hostile targets real time locations, alongside missiles using the data from all available sensors, but seeing as that’s not the case in-game, its a bit more of a significant problem for situational awareness…
I have some clips of the radar in action and they’re likely to just about make you throw up ngl. Too big for the forums tho, I’ll see if I can send it on discord.
Edit: couldnt send them on discord, so here’s 1/4 for an example:
CAPTOR-L(iability) spends more time tracking thin air then enemy jets when using TWS, and this is with a relatively slow jet, flying towards me, in a predictable pattern. I’d hazard a guess at saying if you arent using STT vs an actual player, you might as well just not use the radar at all. Otherwise, have fun trying to not get your missiles notched when the radar is by default pointing the AMRAAM’s seeker at the chaff instead of the enemy jet…