FigPucker

MULTI THREAD PREVIEW 2.8.4.39731 The last update has come with numerous issues in PvP multiplayer including phantom data link contacts and severe rubber banding. Numerous other players have concomitantly observed the same phenomena.

Aware of the ECM warmup period, and the test has been well timed to ensure that the jammer is warmed up and emitting before the F/A-18C was destroyed. Arguing over definitions of the word "activate" has no bearing on the test results.

"aKsHUaLlY" You're wrong. ECM was activated immediately after AIM-7 launch, warmed up over the next few seconds, and was emitting by the time the F/A-18C was destroyed. OP has effectively demonstrated that the AIM-7 has reverted to HOJ, even though it was not launched in such a mode.

Condensed TacView just showing the engagement attached. AIM-7FSUPERMISSILE.zip.acmi

Good job with the RADAR improvements. When can we expect some implementation of ECM effects on the AN/AWG-9?

Thanks Al. The HARM does indeed use an INS - though the exact mechanism and CEP of said inertial guidance remains classified. ED Team - I have demonstrated the INS in action by firing a HARM in EOM mode. In EOM mode, the HARM uses inertial guidance to fly towards the designated steerpoint and search for the specified emitter. If the emitter is silent, as it was in this test, it will use inertial guidance to fly to the designated steerpoint. In this case the steerpoint was placed on the same location as the silent Tor. You can see that both HARMS landed within a few hundred meters of the target after having flown ~25nm, a CEP of ~200 metres and not 5-16nm! I have attached a graph of this EOM shot. Unlike the shots where the HARM loses guidance, you can observe that the missile is being maneuvered by its inertial guidance system. To be clear, the bug that needs to be addressed is that the missile, when fired upon a target that goes silent midflight, fails to switch to inertial guidance. It is perplexing that this bug report has required such exhaustive evidence and explanation, when the physics and missile behaviour obviously demonstrate that this is not working properly. I would appreciate if Wags could take a look at this and have it addressed. server-20220405-144905.trk Tacview-20220405-145014-DCS-base attack_one sam.zip.acmi

In this track you can see the harm flies 16nm away from the target when the RADAR is shut down. You can see that the HARM flies ballistically and makes no attempt to navigate intertially to the last known target position. server-20220404-221823.trk Tacview-20220405-012834-DCS.zip.acmi

An INS that uses dead reckoning would use dead reckoning to navigate to the last known target position, not one 5nm away. As you can see on the graphs, the missile's guidance simply diminishes to nothing after the RADAR is lost, and the missile flies off ballistically. Yuu can see this by the fact that missile goes to 1G and nil turn rate. With a simple INS, the missile would not go ballistic and would have a dynamic G-load and turn rate. Please have your weapons devs review the updated track files that better demonstrate this problem.

This cannot be the case. I have performed another two tests that allow you more time to see that the missile goes ballistic after the RADAR goes silent. In this graph you can see that, when the RADAR is silenced, G-force drops precipitously to 1G and that turn rate flat-lines to almost 0 degrees/second, demonstrating that the HARM is ballistic and in unguided flight. Watching the tacview file attached, you can see that both missiles are losing any guidance commands and are going ballistic within seconds of RADAR silence. This is especially evident when you see that the missiles land up to 5nm away from the target! For the second test, we had the RADAR blink on and off. In this test the missile once again resumed 1G (ballistic) flight upon RADAR silence. We then turned the RADAR back on, resulting in the HARM reacquiring and pulling 18G! This results in a DCS where IADS scripts and player-controlled SAMs render HARMs impotent. Tacview-RADAR-Blinking.zip.acmi Tacview-RADAR_off_terminal_atk.zip.acmi server-20220404-222714.trk server-20220404-222253.trk

In the attached track file, I launch two HARMs, targeted via the HTS, at a Tor (SA-15) that is being controlled directly by my friend. When the missiles entered the terminal portion of their attack (7-10 seconds before impact), he would turn off his RADAR. To be clear, only one Tor turned on then off. We performed this mission to test whether HARMs fired from the F-16 in HAD will intertially guide onto an emitter if it turns silent. Instead of flying via INS to the last known target position, as real HARMs do, we found that they simply fly off ballistically. This is a well known and critical capability for the HARM - it's bizarre that it has been omitted and, unfortunate that it will likely go unresolved for a long time. Bignewy or Nineline, please see what you can do about this. Track file attached for your convenience: server-20220404-222714.trk server-20220404-222253.trk