[CORRECT AS IS] HARM SP does not automatically update to the highest threat

[Harker]

The HARM in SP mode should automatically update and lock the highest threat emitter, according to the RWR. Right now, it does not, requiring the pilot to press RESET in order to select the new highest threat. The pilot shouldn't have to press reset to lock the new highest threat, if the RAID/FLIR FOV button wasn't previously used to cycle targets.

 

This makes SP mode much less reliable and useful and renders the future Pullback mode effectively useless, since it's supposed to enable a HARM launch against a radar that's actively guiding a weapon against you.

 

In my test, I placed two SA-15 units (A, B) spaced apart, with A closer to me. Initially, the SP mode had A locked, but after I passed it and headed towards B, the HARM remained locked to A, even though B was at this point locking and firing on me (clearly being the new highest threat). Only after pressing the RESET button on the HARM SP page, the HARM locked to B, switching to the new highest threat emitter.

 

 

Open Beta 2.5.5.41371, PG map. Track attached.

F-18_HARM SP does not auto-update highest threat.trk

[BIGNEWY]

Hi Harker,

 

From the DCS Hornet manual page 191

 

Threat Selection and HUD Indications

If there is more than one lethal or critical SAM or AAA threat detected, pressing and releasing the HARM Sequence button on the throttle allows the player to cycle through them. Pressing push button 15 RESET on the SP mode HARM format page, the highest threat will be selected or by pressing the cage/uncage switch on the throttle.

 

Seems to be working for me as the manual suggests with hitting reset or uncage it will automatically select the highest threat.

[Harker]

Hi Harker,

 

From the DCS Hornet manual page 191

 

 

 

Seems to be working for me as the manual suggests with hitting reset or uncage it will automatically select the highest threat.

Thanks for the reply. I'm not saying that it doesn't work correctly according to the manual, it's a matter of the implementation itself.

 

The missile should continuously evaluate the RWR data, update its highest threat and select it by default, if there hasn't been prior pilot input. If that doesn't happen, the missile will not be able to be correctly employed in Pullback mode in the future, since Pullback mode overrides the current master mode and places the HARM "under the pickle", requiring only the press of the pickle button to fire against the highest threat.

 

Although, come to think of it, I didn't read anywhere that the missile should default to the highest threat after SP mode has been selected manually. It might still do it under the hood, until the pilot enters SP mode manually, which is what I did during my testing. Possibly to prevent the HARM switching targets by itself while the pilot monitors the situation.

 

I'll test again later today, but if it updates to the highest threat with the HARM un-boxed (simply checked by starting with the HARM boxed and in SP, then unboxing and then boxing again later), it means that it works correctly under the hood and there should be no problem for the Pullback mode.

[NineLine]

Let us know if you have a source that counters how it works as well, if need be, PM it to me if you are worried about 1.16.

 

Thanks.

 

Thanks for the reply. I'm not saying that it doesn't work correctly according to the manual, it's a matter of the implementation itself.

 

The missile should continuously evaluate the RWR data, update its highest threat and select it by default, if there hasn't been prior pilot input. If that doesn't happen, the missile will not be able to be correctly employed in Pullback mode in the future, since Pullback mode overrides the current master mode and places the HARM "under the pickle", requiring only the press of the pickle button to fire against the highest threat.

 

Although, come to think of it, I didn't read anywhere that the missile should default to the highest threat after SP mode has been selected manually. It might still do it under the hood, until the pilot enters SP mode manually, which is what I did during my testing. Possibly to prevent the HARM switching targets by itself while the pilot monitors the situation.

 

I'll test again later today, but if it updates to the highest threat with the HARM un-boxed (simply checked by starting with the HARM boxed and in SP, then unboxing and then boxing again later), it means that it works correctly under the hood and there should be no problem for the Pullback mode.

[Harker]

Works correctly indeed

 

False alarm! I tested and if HARM is unboxed, the seeker will successfully have locked to the current highest threat, after HARM is boxed again, meaning that the evaluation I was talking about is indeed taking place in the background. So I'd say it works correctly. :thumbup:

 

My sources were public, freely available online. I was looking at SP mode in relevance to Pullback mode (it's an extension of SP). For Pullback mode to work correctly, the criterion would be for SP to continuously update to the current highest threat.

 

What I failed to consider initially is that the actual criterion is for the update to happen ONCE SP is entered from any other master mode, which it does. It was my own extrapolation to assume that SP should update continuously, but indeed, there is no reference that says this should be the case while SP mode remains selected.

 

As a side-note, the Cage/Uncage button does not reset to the highest threat, I'll make a separate post about that.

[NineLine]

Thanks!