reported LOST Cue Displaying Incorrectly/Early 2.7.12

MARLAN_ · April 28, 2022

I was asked to make a new thread regarding this issue:

The LOST Cue in the F/A-18C should be displayed when:

a) Missile Launched outside of R_max

b) Target Maneuvers outside of R_maxpost launch -- If the target maneuvers back within the kinematic capabilities of the missile during TOF the dynamic TTG cueing will return.

c) Dynamic TTG cueing has reached a count of 0 and the radar is still tracking a target.

The purpose of the LOST cue is to inform the pilot when it is highly unlikely his missile will impact his target, typically unless the target under attack maneuvers back into the incoming missile. Because the LOST cue removes your Dynamic TTG cueing (TTA/TTG) if it is displayed incorrectly it can be disorientating for the experienced pilot and totally confusing for the inexperienced pilot who will now believe his missile is unlikely to intercept.

It is hard to test all of this piece-by-piece but it does appear ED has got this mostly correct which is awesome, thanks to the team for implementing this feature.

The issue currently is that the LOST cue is displayed despite the missile having enough energy to impact the target. It's not even close with the following Tacview & Track file showing an impact at Mach 2.21 with the target under attack at Mach 0.76.

If needed I can provide proof to one of the ED CMs, but it does appear ED is modeling this correctly already, albeit with a math error somewhere in the DCS code causing this issue.

EDIT: To add: The MC displayed LOST at 043232Z with the AMRAAM at Mach 2.75 with 12NM to go with the target under attack in HOT aspect. The target had not maneuvered at all yet.