Tetra Posted October 25, 2023 Posted October 25, 2023 I think I know the answer to this already, but just wanted to be absolutley sure. Am I correct in assuming that there is no way of having the TGP slave to a SPI created by the HMCS ? VIS and DTOS mode weapons will slave automatically, but the TGP cannot be slaved to the SPI without going through the route of: using the HMCS to create a mark point -> assigning that markpoint as active steerpoint -> slaving the TGP to the newly active steerpoint. Thanks for any help! My Mods: Radar Warning Receiver Audio Expansion G-Breath Sound Mod
ED Team Solution Raptor9 Posted October 25, 2023 ED Team Solution Posted October 25, 2023 (edited) The TGP will always point toward the SPI. By moving the SPI, you are moving the TGP. In VIS and DTOS, you are placing the SPI on the ground using the TD Box. When you are in a pre-planned sub-mode like CCRP or LADD, the SPI is always at the current steerpoint, plus any cursor slews. By making a markpoint the current steerpoint, you are moving the SPI to the markpoint location which will then slew the TGP with the SPI, taking into account cursor slews. EDIT: Note that in CCIP or STRF, the SPI is placed at the weapon impact point at the CCIP/STRF pipper, and the TGP points to that location. Edited October 25, 2023 by Raptor9 1 2 Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
Vortex225 Posted October 26, 2023 Posted October 26, 2023 (edited) 3 hours ago, Raptor9 said: The TGP will always point toward the SPI. By moving the SPI, you are moving the TGP. In VIS and DTOS, you are placing the SPI on the ground using the TD Box. When you are in a pre-planned sub-mode like CCRP or LADD, the SPI is always at the current steerpoint, plus any cursor slews. By making a markpoint the current steerpoint, you are moving the SPI to the markpoint location which will then slew the TGP with the SPI, taking into account cursor slews. EDIT: Note that in CCIP or STRF, the SPI is placed at the weapon impact point at the CCIP/STRF pipper, and the TGP points to that location. I'm not the OP, but this is a good description. Thanks, Raptor9. On the subject of markpoints via HMCS, was the behavior changed in the Viper for 2.9? I noticed in my testing last night that after slaving the the markpoint cue to the HMCS, it would save the markpoint to the location my helmet was looking at when pressing TMS forward the second time--not the location it was ground-stabalized to on the first TMS press. I only noticed this because my TGP wound up looking somewhere entirely different than planned. I intend to submit a bug report soon with track file, but ran out of time to test last night. Thanks. Edited October 26, 2023 by Vortex225 1
Tetra Posted October 26, 2023 Author Posted October 26, 2023 (edited) 4 hours ago, Raptor9 said: The TGP will always point toward the SPI. By moving the SPI, you are moving the TGP. In VIS and DTOS, you are placing the SPI on the ground using the TD Box. When you are in a pre-planned sub-mode like CCRP or LADD, the SPI is always at the current steerpoint, plus any cursor slews. By making a markpoint the current steerpoint, you are moving the SPI to the markpoint location which will then slew the TGP with the SPI, taking into account cursor slews. EDIT: Note that in CCIP or STRF, the SPI is placed at the weapon impact point at the CCIP/STRF pipper, and the TGP points to that location. 45 minutes ago, Vortex225 said: I'm not the OP, but this is a good description. Thanks, Raptor9. On the subject of markpoints via HMCS, was the behavior changed in the Viper for 2.9? I noticed in my testing last night that after slaving the the markpoint cue to the HMCS, it would save the markpoint to the location my helmet was looking at when pressing TMS forward the second time--not the location it was ground-stabalized to on the first TMS press. I only noticed this because my TGP wound up looking somewhere entirely different than planned. I intend to submit a bug report soon with track file, but ran out of time to test last night. Thanks. Thanks, Raptor, that makes a lot of sense, much appreciated! Also Vortex, I was encountering the same today too, have been following the manual/youtube/kneeboard procedures on this and was unable to mimic having to press TMS to ground stabilize, was also having some issues being able to then refine the HMCS SPI point with the RDR cursor slew as well, seem unable to slew inside the HMCS sights, however, I'm also relatively new to the F-16 so I could well be doing something wrong my end. Edited October 26, 2023 by Tetra 1 My Mods: Radar Warning Receiver Audio Expansion G-Breath Sound Mod
VKing Posted October 27, 2023 Posted October 27, 2023 On 10/26/2023 at 4:34 AM, Vortex225 said: On the subject of markpoints via HMCS, was the behavior changed in the Viper for 2.9? I noticed in my testing last night that after slaving the the markpoint cue to the HMCS, it would save the markpoint to the location my helmet was looking at when pressing TMS forward the second time--not the location it was ground-stabalized to on the first TMS press. I only noticed this because my TGP wound up looking somewhere entirely different than planned. I intend to submit a bug report soon with track file, but ran out of time to test last night. Thanks. This is the same behaviour as before (or at least I believe it's currently correct). It starts HUD/HMCS-stabilized, then the first TMS up action changes to ground-stabilized where you can slew it around to fine-tune it, then the second TMS up action saves the markpoint.
Vortex225 Posted October 27, 2023 Posted October 27, 2023 (edited) 11 hours ago, VKing said: This is the same behaviour as before (or at least I believe it's currently correct). It starts HUD/HMCS-stabilized, then the first TMS up action changes to ground-stabilized where you can slew it around to fine-tune it, then the second TMS up action saves the markpoint. Indeed, but this is not the behavior I observed with the penultimate version. I regret I haven't had time to test the hotfix version or create a track file, but I hope to do that tonight. Take your description (which is the correct behavior as far as I know), but now consider that the markpoint is not saved where the markpoint symbol is located & ground stabilized the moment you press TMS Up (short) the second time. Instead, it saved it to where your HMD was centered at that moment. That's what I was observing. Edited October 27, 2023 by Vortex225 1
VKing Posted October 28, 2023 Posted October 28, 2023 10 hours ago, Vortex225 said: Instead, it saved it to where your HMD was centered at that moment. That's what I was observing. I missed this part. That is indeed a bug.
itn Posted October 28, 2023 Posted October 28, 2023 In addition to the bug with second TMS up, the steering indications are bugged on HUD after designating with DTOS. Steerpoints and steering indications are "moved" on HUD but not in HSD. Didn't test weapons (e.g. how does CCRP work in this situation..). I put in a bug report with track to the bug report subforum. Admins may merge these threads if they so wish.
Vortex225 Posted October 31, 2023 Posted October 31, 2023 On 10/28/2023 at 3:28 AM, VKing said: I missed this part. That is indeed a bug. Just following up to say I haven't noticed this particular issue with markpoints since the hotfix; it seems to have been fixed with the hotfix. Nevertheless, I'm having trouble with steerpoints in VIS and DTOS modes and I'm working through the troubleshooting in another thread.
SickSidewinder9 Posted November 7, 2023 Posted November 7, 2023 Something is up with the TGP. In AA or NAV mode it still points at the last location you had it pointing to in AG, so if you don't TMS down before changing modes, it shows a steerpoint where the TGP is pointing, not where it is. Also in AA mode, it try to point at the steerpoint. I'll try getting a track going.
Recommended Posts