Coole28 Posted August 21, 2022 Posted August 21, 2022 Is there a way to slave the TPOD to a SPI created via locking a target in GMT? Hitting CZ seems to slave the TPOD to the steerpoint rather than the SPI. This is opposite of the behavior when you designate a SPI with the HTS, in which CZ slaves the TPOD to said SPI. I can visually confirm the SPI is being created by the radar, I get a weapon solution on the target and everything. Maybe I’m bad at reading but I can’t find anything in the guide relating to this. Any help would be appreciated.
skywalker22 Posted August 21, 2022 Posted August 21, 2022 You can create a MarkPoint for your SPI - over the HUD, overfly,... (they are actually steerpoints from number 26 to 30) and keep overwriting them. When you then want use it so the TGP points to, just select the one you want from steerpoints.
Ignition Posted August 21, 2022 Posted August 21, 2022 TMS aft + TMS right if I'm not mistaken, you don't need to create a mark.
Coole28 Posted August 21, 2022 Author Posted August 21, 2022 2 hours ago, Ignition said: TMS aft + TMS right if I'm not mistaken, you don't need to create a mark. TMS aft/down is target reject, all it does is unlock the designated GMT lock. 2 hours ago, skywalker22 said: You can create a MarkPoint for your SPI - over the HUD, overfly,... (they are actually steerpoints from number 26 to 30) and keep overwriting them. When you then want use it so the TGP points to, just select the one you want from steerpoints. This is what I have been doing as a workaround in the past, but it is overly cumbersome and illogical. The workload aught be as simple as lock target with GMT to create SPI, slave TPOD to SPI, then switch to TPOD as SOI/SPI designator once you have visual with the TPOD. Thats how SPI logic works it is in every other plane, but maybe F-16 is different IRL. I’ve said it before, but damn the F-16 is the least user friendly plane out there. 1
Crptalk Posted August 21, 2022 Posted August 21, 2022 4 hours ago, Coole28 said: Maybe I’m bad at reading but I can’t find anything in the guide relating to this. Any help would be appreciated. Because it's a bug/WIP. TGP should always be slaved to SPI. 2 2
Ignition Posted August 21, 2022 Posted August 21, 2022 3 hours ago, Coole28 said: TMS aft/down is target reject, all it does is unlock the designated GMT lock. TMS Right, FCR SOI 1
Solution GrEaSeLiTeNiN Posted August 22, 2022 Solution Posted August 22, 2022 (edited) Yep TMS right on AG FCR SOI for TGT/OA1/OA2 or press AG FCR OSB 10 (Sighting Option Selector, Chuck's Guide pg 221) "TGT". Edited August 22, 2022 by GrEaSeLiTeNiN 2 AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
Frederf Posted August 22, 2022 Posted August 22, 2022 TGP should always break track and follow FCR when SOI (and slewed IIRC). The "jiggle the sighting point" workaround is a workaround. SPI handling is automatic in the F-16 and with rare exception follows the SOI'd sensor. 1
Coole28 Posted August 22, 2022 Author Posted August 22, 2022 Thanks for the responses all. TMS Right/TGT on the FCR more or less works. It doesn’t continuously update though, I.E. the TPOD will just slew to where the FCR was designating at the time of hitting TMS Right. Still not exactly slaving to the SPI, but easier than creating a markpoint. I’m guessing the TPOD following the FCR as Frederf says is either bugged/WIP. It works fine with slaving TPOD to HTS at least, which I use a lot. 1
Recommended Posts