DSplayer

No. In all my experience within the new patch, both single player and multiplayer, it is NOT the ECMs on any aircraft causing the root problem. You can force AIM-120s to absolutely miss without much effort with the ECM turned off.

Just so you guys know what and why.

ED is planning on at least addressing the issue. Now it’s a matter of how they’re going to do it.

The AI F-14 currently doesn't employ the AIM-54 in the way that pilots do and therefore they're not a good indicator to the range of the 54 or how effective it is. It's going to be overhauled soon btw. For long range kills in real life, the figures you're going to generally get are from test figures since the figures for combat kills are basically all Iranian and its super hard to get any really credible info outside of the knowledge of the kill itself. An article on The Aviation Geek Club states that during a test firing of the AIM-54, it shot down a drone from a distance of 120 miles (Source). So I'd say if the AIM-54 was able to hit a target at that sort of distance, it sure could hit a fighter sized target at 40+ nm. In terms of DCS, the AIM-54 is really hampered by the old API and the ease that the AWG-9 can lose tracks (notching, etc.) but it can easily get long range kills if you really get high and launch at a high speed. During a comp match, I was able to score a ~72nm kill on another F-14 while I was RIOing. The range will probably be increased with the new API comes out and makes the missile more efficient with speed management. Just tell him to git gud.

Here's a track file of me just turning around and the missile doesn't even attempt to keep tracking me in both the OB and the Stable along with respective Tacviews. 120Trashed.trk 120TrashedbutStable.trk 120Trashed.acmi 120TrashedbutStabe.acmi

It's a pretty big problem tbh if that's the case. It makes the AIM-120 really hard to justify using when it just gets defeated so easily. It has definitely made an extreme change in how people play in the comp scene since you can just push super aggressively since you know their missile will not hit you. I would personally maybe like the changes to be rolled back or at least the issue be identified and then fixed in a hotfix but I don't know if that would happen.

Okay. Is there another factor that is causing missiles to simply get trashed after going cold or barely notching? There also seems to be a lack of reliability in otherwise high Pk shots in comparison to 2.7.6.

I've been having the exact same issues with the SD-10 and the AIM-120C with this new patch in terms of reliability. Plus they're acting the same with that Datalink/INS guidance thing. Maybe it's a placebo.

I would like Jester to immediately IFF targets that you have STT'd no matter what. The delay between him actually IFFing the target and marking it as hostile is long enough that in high intensity situations, friendly fire incidents can occur. I know that Jester verbally says if something is a friendly or hostile but it'll call out targets that are hostile as friendly sometimes if they're flying a Bluefor aircraft.

From what I could gather, it's the 120 API (AIM-120 + SD-10) that go changed with the new INS+Datalink guidance, notch filter "improvements", and the new physical seeker limitations. Notching just got worse with all these "improvements".

Jester spotting stuff is a bit inconsistent. Sometimes he's able to spot tanks and ground vehicles that are very hard to see but other times he can miss an entire moving oil tanker that is directly in the FOV. I would also like Jester to be able to use Point track instead of just Area track. Slight suggestion for the future: Jester LANTIRN A/A Mode. Would like to see it be used to spot aircraft and point track them.

Yeah it's absolutely insane. When I was reading up on the changes when they first got announced, I thought it would do the complete opposite and make the AIM-120 super hard to defeat. There is clearly something wrong that made the missile complete crap to use. Sparrows are more reliable than 120s atm.

In me and my squadron's current experience with the new patch, the new AIM-120 API (which should apply to all AIM-120 variants and the SD-10) made the missiles extremely easy to defeat. Is this intended or was this a unintended side effect of the new realistic modelling of the seeker head? Guidance on targets that are going cold or beaming have gone out the window and basically made this missile a medium range paperweight. What do you guys think?

Lol... I know you're reguler player on GS. Why don't you just observe inside its tacview and count how many AIM-54 fired by player that actually hit. Because 90% of the people on the server get their AWG-9's notched and lose the missile or the old missile API decides to do drastic high G turns like it's always done. If you actually know what the limitations of the radar and missiles, you can make the AIM-54 do its job effectively. Anyway, HB has said themselves that the AI is currently bugged in AIM-54 employment and they will overhaul it later.

Nope. That’s the AI F-14’s AIM-54 employment problem. Problem with the AI and not the 54. Player fired 54s are fine. Player and AI AIM-120s are not.

Ah that's understandable then! I kinda have to start circling my target area since I usually get to it first before the pod starts showing up "NOT READY"

Jester doesn't turn on the LANTIRN pod immediately when switching to A/G after taking off. Or it takes 10 years for the LANTIRN to be operational after takeoff.

I absolutely love the new TID cursor antenna elevation limits! I no longer have to have my calculator next to me using the formulas that Karon made.

Maybe 2 weeks is closer than it seems.

It kinda becomes an expensive Sparrow in PD-STT with the AIM-54As and AIM-54C currently. Idk if it might change with the AIM-54C going active on its own implementation but we'll have to wait on that. This is only PD-STT btw and not P-STT. For all the AIM-54 variants currently, no. The AIM-54C will go active on its own in the future though. If the target is within 10 miles yes. But currently in my testing and experience, it feels like the ACM cover up actually causes missiles to not go active on a target within 10 miles 8/10 of the launches I do. Yes and no. This doesn't have a range limitation of 10nms. In DCS it's similar to P-STT (without the hard locking bit since you can use it in TWS) in which it will go active on the target after a predeterminate amount of time and distance. Technically yes. It will go active on the target after a predeterminate amount of time and distance which means that it will fly straight until 10 or so miles and do an abrupt turn to meet the target. This is down to limitations of DCS. Hope this should answer your questions.

Oof that's true!

HB said they’re going to remove the ability for mods like Pilot LANTIRN to work after the implementation of Jester LANTIRN.

Aww it’s all recorded in the F-14A. Was hoping to get a sneak peak of the new F-14B EIGT.

Bug: AIM-54 will launch within 10 miles and not track with the ACM cover up. Can I reproduce it 100%: Yes If not 100%, how often out of 10: 8/10 How to reproduce/description: Method 1: Step 1: Lift ACM cover (regardless of radar lock status) Step 2: Fire AIM-54 Result: The AIM-54 will not track the target even if target was launched near the ADL and hot off the rail which will result in the loss of a missile. My assumption is that it takes perhaps a couple of seconds before the missile starts deciding the track any targets within an FOV which is why sometimes you will get a kill but not others. DCS Version: 2.7.6.13436 Open Beta System Specs: i7-8700k GTX 1080 Ti 32GB RAM SSD Samsung 1TB 860 EVO OS: Win10 Peripherals: Joystick: Saitek X56 Throttle: Logitech X56 Headtracker: TrackIR + TrackClipPro Mission File: See attached. Track: Check attached. Video/ Screenshots: https://streamable.com/jc6d7z (Singleplayer Custom Mission using the ACMTest Mission) https://streamable.com/q43oa2 (On the GS Server) https://streamable.com/7okgfh (Singleplayer Custom Mission using the AIM54RadarTest2 Mission) Mods: Quaggles Custom Keybinds ACMTest1.trk ACMTest.miz AIM54RadarTest2.miz

This means that extrapolated targets cannot get un-X’d out correct?