DSplayer

This month's patch included some changes to the HARM that were not included in the changelog. Now, a HARM upon target loss will attempt to hit the last known INS position of the target while attempting to search for the signal. The HARM is not laser pinpoint accurate in INS, but can still get close enough to kill the targets as is in your case. I will note that if you were to make the radars stop emitting even earlier in flight, the miss area would increase further. In previous patches (like the June patch), the HARM after target loss basically didn't fallback to its INS and continued the last command it had before target loss. That behavior was not correct. There are also some other HARM changes like I said, but they're slightly unrelated to this specific case.

Do you have any mods installed?

The LITENING TGP we have right now has unrealistically good lossless digital zoom which it should not have. The ATP implementation, however, does have the digital zoom limitations. Otherwise, I feel like the ATP is pretty easy to use, but the HOTAS commands are not the exact same as the LITENING's and I would suggest reading the manual chapter on the ATP to become fully acquainted with the system and how it works.

BAP-100 and BAP-120 are defined in CoreMods/aircraft/AircraftWeaponPack/common_bombs.lua

I would have to test it out again but I believe it does still work with the latest DCS version. If not, I'll have to update it.

What's the mission you're attempting this Mach 2 run in? The weather/atmospheric conditions do play a part in the maximum speed that you can achieve. I'm able to achieve Mach 2+ in level flight at 38000ft with a standard day.

You have Captive AIM-9Ms on the wingtip stations (1A and 8A) but live AIM-9Ms on 1B and 8B. When you first selected AIM-9s, it fired since it fired from 8B (which had a live AIM-9M), then it stepped to 1A after you shot 8B's missile but 1A has a CAP-9M. Then you switched to Sparrow then back to AIM-9s but it then stepped to 8A then you stepped back to 1A.

Perhaps it would be good to write a bug report on that issue of it underperforming in-game since the values I used are pulled from the lua definitions.

In the first track ("magic 1 vs 9J no tracking.trk") the Magic 1 loses track because the target moves such that it isn't rear aspect anymore. The AIM-9J tracks because it has better side aspect performance than the Magic 1 (max trackable aspect of ~103 degrees vs ~63 degrees off tail respectively). I personally don't know what's being demonstrated in the second track ("no flare rear close magic 1.trk") but if it's the target aspect thing, I would expect it to be the same as the first track.

Please provide a short SP track of the situation you're encountering. The Magic 1 last had a change in May of 2024.

Try uninstalling them and seeing if this occurs still. It sounds like a mod conflict of some kind that's causing this issue to occur.

Do you have any mods installed?

They're talking about using Loft delivery mode with the LABS and not the WRCS AGM-45 mode.

Module developers, even ED, can't just manifest something out of nowhere. The F-35 that is in service today doesn't even have HARM or AARGM integrated yet. With absolutely no information to work on unlike other instances, ED can't just make the largest assumptions to put the HARM or AARGM on our F-35.

Provide a source for HARM integration into the F-35 with symbology and how it works, thanks.