correct-as-is May 18 OB: LMC does not hold position after lase

[LorenLuke]

Previous behavior would have the LMC hold relatively still after being turned on after being provided a viable laser range by engaging and disengaging the LRFD, then engaging the LMC, and the LMC would compensate for the motion of the aircraft.

This behavior no longer occurs. The LMC can still be used to point at a target and versus a moving target, but it no longer seems to stabilize with regards to the motion of the Apache.

AH-64 LMC.trk

[Raptor9]

The previous behavior of the LMC, in that it would ground stabilize when engaged, was not accurate. The current behavior is more accurate; the CPG is required to manually adjust the slew rates to compensate for linear motion.

[LorenLuke]

36 minutes ago, Raptor9 said:

The previous behavior of the LMC, in that it would ground stabilize when engaged, was not accurate. The current behavior is more accurate; the CPG is required to manually adjust the slew rates to compensate for linear motion.

So, to confirm I'm understanding this, realistically it doesn't stabilize to some point <X> distance away wherever it's pointing, with X being a valid laser distance acquired before engaging the LMC?

[Raptor9]

2 hours ago, LorenLuke said:

So, to confirm I'm understanding this, realistically it doesn't stabilize to some point <X> distance away wherever it's pointing, with X being a valid laser distance acquired before engaging the LMC?

Correct. Engaging LMC shouldn't change any existing slew rates. The only time LMC should affect the slew rate of the TADS without user input is if the range is updated to a different value. When the range value changes, the existing angular slew rate being maintained by LMC is adjusted to maintain the same angular velocity at the new range value.

LMC shouldn't perform any stabilization onto a point, it should simply maintain TADS angular rates independent of the aircraft angular rates.