Dobbie93

@NineLine can your SMEs confirm that the implementation changed between M3 and M4.2+? Because M3 is pretty clear that the radar remains locked to the hmd until otherwise told once cued, and whilst I know defence organisations make some weird decisions, making it harder for the aircraft designed to be a dogfighter to get a lock whilst in a dogfight makes no sense even for them. Thanks

Looking at the MLU_M3 document, the following is stated: "Slaving FCR ACM BORE without a TOI (FCR Not Locked On) When ACM BORE is selected and TMS-forward is held, the radar is slaved to the HMCS Aiming Cross LOS in a non-radiating state. The FCR ACM BORE ellipse is displayed on the HMCS at the FCR LOS. The radar is commanded to radiate when TMS-forward is released (Figure 6-33). The radar automatically attempts to acquire a target in the ACM BORE ellipse when TMS-forward is released. The FCR is slaved to the HMCS LOS until one of the following occur: 1. The radar acquires a target. 2. The radar transitions out of ACM BORE mode. 3. TMS-right with TGP tracking an A-A target. 4. The radar stops communicating on the Mux. 5. The HMCS LOS becomes invalid. 6. The HMCS stops communicating on the Mux. 7. A TMS-aft occurs. Note that if the HMCS LOS is moved past the FCR gimbal limits, the avionic system continues to try to slave the FCR LOS to the HMCS LOS even though the FCR gimbal limits have been reached." Current implementation appears to respect the first paragraph but ignores the second paragraph on the following page (pages 76+77)