VKing Posted January 7, 2023 Share Posted January 7, 2023 (edited) If the HARM is fired in PB (or EOM in the F-16), the expected behaviour is that the HARM will loft and turn towards the selected steerpoint or target point, then dive towards the target area and start looking for a radar of the selected type to home in on. What appears to be happening, is that the HARM seeker activates immediately upon launch. If it doesn't see a radar, or if the radar is active the entire time the HARM is in flight, it will fly the correct flight path. However, if the radar turns off at any point during the flight, the missile will go dumb and forget its target position, and glide straight past it. In the first two tracks, which is the same scenario in the F-16 and F-18, to show there is no issue with a particular aircraft, there is one SA-6 radar at steerpoint 2. First one HARM is fired against a non-existent SA-2, and one against the SA-6. When the first HARM is about to strike the SA-6, a third is fired, also against the SA-6. Observe that the first two missiles loft and dive towards the target area as expected, even though there is no SA-2 radar for the first missile to spot. The third missile fails to initiate its dive, and as such will completely miss the target area. In the third track, the radar respawns (placeholder for a radar deactivating and reactivating), and since the second HARM does not follow the correct flight path, it misses the second radar since it is outside of the HARM's FOV when it activates. The fourth track demonstrates that the HARM seeker activates far too early. Even in EOM mode, which is supposedly the most restrictive in terms of precision required of the target location, the missile turns to seek onto a radar more than 20 nmi away from its given target position. HARM_EOM_Tracking_bug_F-18.trk HARM_EOM_Tracking_bug_F-16.trk HARM_EOM_Tracking_bug_F-16_radar-reactivates.trk HARM_EOM_Tracking_bug_F-16_activation-range.trk Edited March 25, 2023 by VKing 5 Link to comment Share on other sites More sharing options...
VKing Posted January 25, 2023 Author Share Posted January 25, 2023 Same behaviour in 2.8.2.35632. 2 Link to comment Share on other sites More sharing options...
al531246 Posted January 27, 2023 Share Posted January 27, 2023 Reported since April of 2022. According to ED's EW expert this is how the weapon functions IRL. Comical... 3 Intel i5-8600k | EVGA RTX 3070 | Windows 10 | 32GB RAM @3600 MHz | 500 GB Samsung 850 SSD Link to comment Share on other sites More sharing options...
VKing Posted January 27, 2023 Author Share Posted January 27, 2023 I can believe that's how the weapon is supposed to work after the sensor turns on. You would like the missile to continue towards the target if it turns on again, but this is contingent on the missile being close enough that it's actually flying at the target instead of still lofting. The problem seems to be that the sensor turns on almost immediately upon launch instead of when it reaches the target area it's supposed to search in. So instead of looking at a small area for a specific radar, it searches basically half the map. 4 Link to comment Share on other sites More sharing options...
VKing Posted March 25, 2023 Author Share Posted March 25, 2023 Issue still present in OB 2.8.3.38090, both ST and MT. Link to comment Share on other sites More sharing options...
VKing Posted April 18, 2023 Author Share Posted April 18, 2023 (edited) Another track, recorded with 2.8.4.38947 MT. This shows four HARMs fired at four different SAMs, but when the SAMs activate, all four HARMs turn to the same radar, leaving three of the four SAM sites unengaged. Edit: Second track with F-18. This time two radars got hit because they activated later and one of the HARMs spotted one radar while the three others went for another. HARM_EOM_Tracking_bug_F-16_InadvertentFocusFire.trk HARM_EOM_Tracking_bug_F-18_InadvertentFocusFire.trk HARM_bug_earlyactivation.webm Edited April 18, 2023 by VKing 4 Link to comment Share on other sites More sharing options...
VKing Posted September 21, 2023 Author Share Posted September 21, 2023 (edited) Retest on MT 2.8.8.43704 HARM_EOM_Tracking_bug_F-16_MT-2.8.8.43704.trk Edited September 21, 2023 by VKing Fixed track Link to comment Share on other sites More sharing options...
Flappie Posted October 28, 2023 Share Posted October 28, 2023 Thanks for the tracks. This was reported earlier. (reported for both F-16 and F/A-18) --- Link to comment Share on other sites More sharing options...
Recommended Posts