nickos86 Posted October 31, 2022 Share Posted October 31, 2022 I guess I'm doing something wrong or missing something. When I designate a GM/GMT target with the FCR, I need to press the TGT. It changes to OA1 then OA2 and back to TGT. Only when it come back to TGT the TGP will slave to the designated point. Is there a way to slave the TGP without cycling through TGT>OA1>OA2>TGT? Link to comment Share on other sites More sharing options...
104th_Crunch Posted October 31, 2022 Share Posted October 31, 2022 Simply press TMS Right Link to comment Share on other sites More sharing options...
nickos86 Posted October 31, 2022 Author Share Posted October 31, 2022 It's basically the same. TMS Right cycle TGT>OA1>OA2>TGT and then the TGP slaves to the FCR designation. It won't slave on the first TGT press/TMP Right. Link to comment Share on other sites More sharing options...
RuskyV Posted November 2, 2022 Share Posted November 2, 2022 CZ or cursor zero button on the TGP should remove any slew errors, you don’t have to have the pod as the sensor of interest for the button to function. give it a go and see if that works. Link to comment Share on other sites More sharing options...
nickos86 Posted November 2, 2022 Author Share Posted November 2, 2022 12 hours ago, RuskyV said: CZ or cursor zero button on the TGP should remove any slew errors, you don’t have to have the pod as the sensor of interest for the button to function. give it a go and see if that works. It's not. Honestly, I would expect the TGP to automatically slave to the FCR target that now became the SPI... But only TGT>OA1>OA2>TGT works 1 Link to comment Share on other sites More sharing options...
Lima29 Posted November 2, 2022 Share Posted November 2, 2022 I’m sure this is a bug that has been mentioned a few times before. Im sure it’s been said that it should slave to the SPI in GM/GMT but it isn’t at the moment, the work-around being that you have to cycle the targeting point as you are doing at the moment. 1 1 Link to comment Share on other sites More sharing options...
=617= Evil Posted November 4, 2022 Share Posted November 4, 2022 (edited) Another way to get it to slave right away is to set a Markpoint with the FCR. It'll automatically slew the pod just like it does for steerpoints. Bonus: You can use IFF IN long press to share the info via Datalink with your flight. Edited November 5, 2022 by =617= Evil 1 Link to comment Share on other sites More sharing options...
Falconeer Posted November 5, 2022 Share Posted November 5, 2022 On 11/2/2022 at 10:40 PM, Lima29 said: I’m sure this is a bug that has been mentioned a few times before. Im sure it’s been said that it should slave to the SPI in GM/GMT but it isn’t at the moment, the work-around being that you have to cycle the targeting point as you are doing at the moment. i agree, the tgt is always looking at a SPI. So by designating a ground target in said GM or GMT, the TGP should slave to that point Planes: Choppers: Maps: Flaming Cliffs 3 Black Shark 2 Syria A-10C Tank killer 2 Black Shark 3 Persian Gulf F/A18C Hornet AH-64 Apache Mariana's F-16C Viper F-15E Strike Eagle Mirage 2000C AJS-37 Viggen JF-17 Thunder F-14 Tomcat Link to comment Share on other sites More sharing options...
Furiz Posted November 6, 2022 Share Posted November 6, 2022 On 10/31/2022 at 4:05 PM, nickos86 said: TMS Right cycle TGT>OA1>OA2>TGT That's not true, TMS Right = AREA Track Link to comment Share on other sites More sharing options...
Tholozor Posted November 6, 2022 Share Posted November 6, 2022 29 minutes ago, Furiz said: That's not true, TMS Right = AREA Track I believe he meant TMS Right with FCR as SOI. 1 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/ Link to comment Share on other sites More sharing options...
falconzx Posted November 7, 2022 Share Posted November 7, 2022 Any ETA from ED guys about a fix on this? Link to comment Share on other sites More sharing options...
104th_Crunch Posted November 7, 2022 Share Posted November 7, 2022 17 hours ago, falconzx said: Any ETA from ED guys about a fix on this? What is the issue? Link to comment Share on other sites More sharing options...
falconzx Posted November 7, 2022 Share Posted November 7, 2022 SPI not consistent and synced automatically between FCR and LITENING. Link to comment Share on other sites More sharing options...
TEOMOOSE Posted November 9, 2022 Share Posted November 9, 2022 This should be reported in the bug reports section. Hopefully it would get some attention. Link to comment Share on other sites More sharing options...
Lima29 Posted November 9, 2022 Share Posted November 9, 2022 (edited) 5 hours ago, TEOMOOSE said: This should be reported in the bug reports section. Hopefully it would get some attention. It has been already, a couple times I think. It’s a few pages back - about 4 or 5 maybe. Edited November 9, 2022 by Lima29 Link to comment Share on other sites More sharing options...
falconzx Posted November 11, 2022 Share Posted November 11, 2022 (edited) it's not only about the FCR to TGP's SPI sync, but IMHO all the SPI system needs a check in many situations and cases. For example: few days ago in 2.8 I noticed that with a loadout A/A+AGM88+HTS+TGP (a classic one for F-16C), my TGP wasn't able to move SPI, or at least in my HSD the SPI symbology was STUCK, probably because of the presence of HAD, but even turning it off via pylon switch i didn't solve this, and going in NAV neither. Now i don't have time to make report, tracks and so on about this specific case (if someone can please do it). Edited November 11, 2022 by falconzx Link to comment Share on other sites More sharing options...
_SteelFalcon_ Posted November 11, 2022 Share Posted November 11, 2022 1 hour ago, falconzx said: it's not only about the FCR to TGP's SPI sync, but IMHO all the SPI system needs a check in many situations and cases. For example: few days ago in 2.8 I noticed that with a loadout A/A+AGM88+HTS+TGP (a classic one for F-16C), my TGP wasn't able to move SPI, or at least in my HSD the SPI symbology was STUCK, probably because of the presence of HAD, but even turning it off via pylon switch i didn't solve this, and going in NAV neither. Now i don't have time to make report, tracks and so on about this specific case (if someone can please do it). yup, can be recreated. and it doesnt matter if you have the HTS equipped or not. it's simply the HARM. if HARM is the selected weapon, stuff's weird. 1 Link to comment Share on other sites More sharing options...
Recommended Posts