Rongor Posted Friday at 11:06 PM Posted Friday at 11:06 PM (edited) page 308 claims the SPI would be placed on a hooked symbol This is not the case and it would annoyingly affect a current SPI if it was. Edited 15 hours ago by Rongor 1
Yurgon Posted Friday at 11:35 PM Posted Friday at 11:35 PM 18 minutes ago, Rongor said: This is not the case and it would annoyingly affect a current SPI if it was. Agreed, partly. In the marked sentence, it should be named "Hookship symbol" instead of "SPI symbol", or rather: "Hookship or SPI symbol". If the TAD is set as SPI Generator ("TAD" is shown in the lower left corner of the HUD, which otherwise defaults to STPT), hooking TAD objects will make them SPI. There's no way to make the TAD SPI Generator without it having anything hooked, and unhooking a TAD object will also un-SPI the TAD and revert the SPI Generator to STPT (if the TAD was SPI Generator). When TAD is set as SPI Generator, hooking a TAD object will not just hook it, but will also set it as SPI. To put it yet another way, one TAD object can be hooked without it being the SPI, but when the TAD is SPI, then the hooked TAD object will also be the SPI.
Rongor Posted Friday at 11:57 PM Author Posted Friday at 11:57 PM (edited) 30 minutes ago, Yurgon said: Agreed, partly. In the marked sentence, it should be named "Hookship symbol" instead of "SPI symbol", or rather: "Hookship or SPI symbol". If the TAD is set as SPI Generator ("TAD" is shown in the lower left corner of the HUD, which otherwise defaults to STPT), hooking TAD objects will make them SPI. There's no way to make the TAD SPI Generator without it having anything hooked, and unhooking a TAD object will also un-SPI the TAD and revert the SPI Generator to STPT (if the TAD was SPI Generator). When TAD is set as SPI Generator, hooking a TAD object will not just hook it, but will also set it as SPI. To put it yet another way, one TAD object can be hooked without it being the SPI, but when the TAD is SPI, then the hooked TAD object will also be the SPI. Not on my end. Even with TAD as SOI, hooking any object won't make it SPI. The reason for this is hooking being performed by DMS up short. Only DMS up long would set the SPI at that currently hooked object. The green part is correct though. Edited Saturday at 12:07 AM by Rongor
Yurgon Posted Saturday at 03:04 AM Posted Saturday at 03:04 AM (edited) 3 hours ago, Rongor said: Not on my end. Even with TAD as SOI, hooking any object won't make it SPI. Read carefully. I never said it did. I said, once the TAD is set as SPI Generator, hooking a TAD object will make that object SPI. I'd suggest to, in this order... put the TGP into into AG Slave all to SPI make TAD SOI; hook a TAD object make the TAD SPI observe the TGP slewing to the hooked TAD object; observe the "wedding cake" SPI symbol hook another TAD object Would you expect the TGP to slew over to the newly hooked TAD object in step 6 and the "wedding cake" to move to that same symbol, even though the "Make SPI" HOTAS command wasn't issued again? Edited Saturday at 03:15 AM by Yurgon Changed response because I misread one "SOI" for "SPI"
Rongor Posted Saturday at 09:34 AM Author Posted Saturday at 09:34 AM (edited) 6 hours ago, Yurgon said: Read carefully. I never said it did. I said, once the TAD is set as SPI Generator, hooking a TAD object will make that object SPI. I'd suggest to, in this order... put the TGP into into AG Slave all to SPI make TAD SOI; hook a TAD object make the TAD SPI observe the TGP slewing to the hooked TAD object; observe the "wedding cake" SPI symbol hook another TAD object Would you expect the TGP to slew over to the newly hooked TAD object in step 6 and the "wedding cake" to move to that same symbol, even though the "Make SPI" HOTAS command wasn't issued again? Exactly. You are focusing on a situation in which the current SPI has been designated by a hooked TAD object already. Which the manual also seems to expect: It's actually claiming "Hook Mode (TAG: OWN, BULL, or CURS), rotary OSB 18. This OSB function is only displayed when you have hooked a TAD symbol with the cursor", which is worded problematically, as you really don't have to have a hooked TAD symbol for the Hook mode to display on OSB18, you only need to move the TAD cursor over any TAD object, regardless hooked or not. SPI'ing is neither a requirement for hooking nor is the manual addressing the SPI status at this point. The problem isn't the manual mentioning how the SPI will move from one hooked object to the next if it has been designated on an initial hooked object. The issue is the manual providing this info at a point where the reader expects to learn what happens when an object gets hooked. The optional prior SPI'ing is left out in this explanation, while actually being a precondition for the claim the manual is making. So either the "SPI is moved over the hooked object" should be dropped from the text entirely, or it should be added further down as an optional use case for when the pilot has designated the current SPI by any hooked object. Designating a SPI by the TAD isn't required to hook anything. Only precondition for hooking is setting TAD as SOI. The manual doesn't mention this requirement. Instead it claims hooking would place the SPI over the hooked object. Which is not the case. So it shouldn't be mentioned this way in the first introductory paragraph as if it was. Edited Saturday at 09:44 AM by Rongor
Yurgon Posted Saturday at 01:28 PM Posted Saturday at 01:28 PM (edited) 3 hours ago, Rongor said: You are focusing on a situation in which the current SPI has been designated by a hooked TAD object already I don't see how we disagree on anything here. Where the manual mentions the SPI, it is lacking the precondition of making the TAD SPI Generator in the first place. However, if the TAD was already set as SPI Generator at this stage, both the Hookship symbol and the SPI symbol would be updated when another TAD object is hooked. So the manual isn't entirely wrong, it's just inaccurate by omission right now and fails to cover a) the use case of moving the TAD cursor over a TAD object without hooking and b) the use case of the TAD not generating the SPI. So how about this? Quote Hook Mode (TAG: OWN, BULL, or CURS), rotary OSB 18. This OSB function is only displayed when the cursor hovers above a TAD symbol, or when you have hooked a TAD symbol with the cursor. TAD symbols can include the SPI, TGP diamond, waypoint/steerpoint, flight members, EPLRS transmitters, or bullseye. When a symbol is hooked, the Hookship symbol is placed over it and a dashed, yellow line leads from the Hookship symbol to the rotary selection. If the TAD is set to generate the SPI, the hooked symbol will also show the SPI symbol. For comparison, the original: Quote Hook Mode (TAG: OWN, BULL, or CURS), rotary OSB 18. This OSB function is only displayed when you have hooked a TAD symbol with the cursor. TAD symbols can include the SPI, TGP diamond, waypoint/steerpoint, or bullseye. When a symbol is hooked, the SPI symbol is placed over it and a dashed, yellow line leads from the SPI symbol to the rotary selection. Edited Saturday at 01:30 PM by Yurgon
Rongor Posted 15 hours ago Author Posted 15 hours ago (edited) On 1/18/2025 at 2:28 PM, Yurgon said: Hook Mode (TAG: OWN, BULL, or CURS), rotary OSB 18. This OSB function is only displayed when the cursor hovers above a TAD symbol, or when you have hooked a TAD symbol with the cursor. TAD symbols can include the SPI, TGP diamond, waypoint/steerpoint, flight members, EPLRS transmitters, or bullseye. When a symbol is hooked, the Hookship symbol is placed over it and a dashed, yellow line leads from the Hookship symbol to the rotary selection. If the TAD is set to generate the SPI, the hooked symbol will also show the SPI symbol. Much better. Lending your suggestions, how about this: Quote Hook Mode (TAG: OWN, BULL, or CURS), rotary OSB 18. This OSB function is only displayed when the cursor hovers above a TAD symbol which can be hooked, or when you already have hooked a TAD symbol. Hooking allows you to readout bearings and ranges between symbols and cursor locations on the TAD and also can provide visual cues on the HUD (see Fig. 283+284). It also enables you to slave your SPI onto TAD symbols, so you can use their locations to slave other sensors on them. TAD symbols can include the SPI, wingmen's broadcasted SPI, TGP diamond, waypoint/steerpoint, flight members, EPLRS transmitters, or bullseye. A TAD symbol is hooked with the cursor and DMS FWD SHORT. When a symbol is hooked, the Hookship symbol is placed over it and a dashed, yellow line leads from the Hookship symbol to the rotary selection. Designating the TAD as SPI by DMS FWD LONG while a symbol is hooked, will place the SPI symbol over the hooked symbol. Hooking another TAD symbol by hovering the cursor over it and pressing DMS FWD SHORT will drop the hook from the current symbol and move it to the new one. In case the SPI had been designated on the TAD, the SPI will move to that new hook as well. Hooking is cancelled by DMS AFT SHORT. In case the SPI had been designated on the TAD, the SPI will then return to the current steerpoint. Of course this version is longer, Though I think it could be worth it, as it pretty much contains everything especially a new player might need to understand the whole concept at once. Edited 15 hours ago by Rongor 1
Yurgon Posted 12 hours ago Posted 12 hours ago 1 hour ago, Rongor said: Lending your suggestions, how about this: Excellent, sounds really good! Except that "DMS" should be "TMS" This would give us (with a few more minor changes): Quote Hook Mode (TAG: OWN, BULL, or CURS), rotary OSB 18. This OSB function is only displayed when the cursor hovers above a TAD symbol that can be hooked, or when a TAD symbol is already hooked. Hooking allows you to read bearings and ranges between symbols and cursor locations on the TAD and also can provide visual cues on the HUD (see chapter HookShip HUD Symbols). Hooking TAD symbols is performed with the TMS Forward Short HOTAS command (Hook) with the TAD as SOI. TAD symbols can include the SPI, SADL members' broadcasted SPI, TGP diamond, waypoints, SADL members, EPLRS transmitters, bullseye and others. When a TAD symbol is hooked, the Hookship symbol is placed over it and a dashed, yellow line leads from the Hookship symbol to the rotary selection. Designating the TAD as SPI Generator with the TMS Forward Long HOTAS command (Make SPI) while a symbol is hooked will place the SPI symbol over the hooked symbol. Hooking another TAD symbol by hovering the cursor over it and pressing the TMS Forward Short HOTAS command will drop the hook from the current symbol and move it to the new one. In case the SPI had been designated on the TAD, the SPI will move to that new hook as well. Hooking is cancelled by the TMS Aft Short HOTAS command (Un-hook). In case the SPI had been designated on the TAD, the SPI will revert to the current steerpoint. What do you think? And: if I'm not mistaken, this chapter is identical for the legacy A-10C and the new A-10C II modules, and the above text should be applicable to both modules, right?
Recommended Posts