[CHECKING] Discrepancy between HUD TGT and SA TGT

[Swift.]

When you move the FLIR from a WPGSD and create a new TGT, the SA/HSI and HUD both show different TGTs:

 

1. Have a FLIR loaded

2. Slave FLIR to WP on the ground

3. Slew FLIR to a new area

4. TDC Depress to set new TGT

5. TGT diamond on HUD moves

6. TGT diamond on SA/HSI page doesn't move

 

The Jet now has two separate TGTs, which I assume would be an issue (Which one does a TOO Jdam take, or any auto bombing for example)

[Santi871]

thanks, I'll look into this

[maxTRX]

When you move the FLIR from a WPGSD and create a new TGT, the SA/HSI and HUD both show different TGTs:

 

1. Have a FLIR loaded

2. Slave FLIR to WP on the ground

3. Slew FLIR to a new area

4. TDC Depress to set new TGT

5. TGT diamond on HUD moves

6. TGT diamond on SA/HSI page doesn't move

 

The Jet now has two separate TGTs, which I assume would be an issue (Which one does a TOO Jdam take, or any auto bombing for example)

 

Just tried it. If I designate a target with the Tpod (not co-located with any wpt) all indicators point to it. Without undesignating current target and pressing WPDSG for any wpt, all sensors shift to my new tgt.

If I designate a wpt first, all sensors point to it also but... like you noticed, slewing away from the wpt/tgt and re-designating a new tgt only HUD and FLIR followed. No problems if you un-designate first.

 

I had JSOW loaded and it followed the FLIR designation. Good catch!

Edited March 22, 2020 by Gripes323

[Santi871]

Reported, thanks. FLIR and HUD designations are showing a couple of missing features that do work with nav designations (WPDSG). That is, when a FLIR/HUD designation is performed, the designation diamond symbol does not show in the HSI/SA, and TGT steering is not selected in those either. It should work the same way as with a nav designation so I've reported that.

Edited March 23, 2020 by Santi871

[Swift.]

Top stuff, thanks Santi