While making progress in understanding the sim, I am confused by the TAD hook function and decided to look it up in the manual, which is even more confusing.

The manual (p. 309 in v1.1.1.1) states for OSB 18:
OWN HOOK: hook line from ownship symbol to SPI weddding cake
HOOK BULL: hook line from SPI wedding cake to bullseye
HOOK CURS: hook line from SPI wedding to cursor

However, the corresponding image (Figure 227) for OWN HOOK shows a line drawn from ownship symbol to bullseye/cursor which happen to be at the same place in that image. As opposed to a line from ownship symbol to SPI wedding cake, as described in the description of OWN HOOK. What's up with that?

Can't remember 1.1.1.1. But from 1.2.2.x newest version, image shows it correct. I just checked in the sim to verify.

In the image the bullseye has been selected, as the text under the image says.
which means the "OWN-HOOK" shows as supposed to "From OWNSHIP to HOOK/Selected symbol (selected Bullseye)".

You can also see waypoint 1 as highlighted, which is also selected as SPI (wedding cake)

Should Be at least for newest version:
HOOK -> OWN: Hook line from Hooked/selected symbol to OWNSHIP
OWN -> HOOK: hook line from ownship symbol to hooked/Selected symbol

HOOK -> BULL: hook line from Hook/Selected Symbol to bullseye
BULL -> HOOK: Hool line from bullseye to hooked/selected symbol

HOOK -> CURS: hook line from hooked/selected symbol to cursor
CURS -> HOOK: Hook line from cursor to hooked/selected symbol

BULL -> CURS: Hook line from bullseye to cursor
CURS -> BULL: Hook line from cursor to bullseye

Yes thanks got it Runibl! Why does the manual have to make such a big issue out of explaining a line originating from A, pointing to B and vice versa. That and the whole drama about the TAD background map.

The word "hook" just means to select an object with the TAD. That's the vocabulary to distinguish it from lock, track, etc. from other sensors.

So the dotted line option isn't the hook, it just may use the hook for an end point of the line.

The Hook feature is useful for sending SPIs to others in your Group ID. I don't use it often so some of my comment may be off.

When I have designated a SPI, I can broadcast it to everyone with DMS Left Long. If I change my SPI to a different target/designation, then the broadcasted SPI follows.

OTOH, when I have an SPI, I can Hook another A-10C in my Group by moving the TAD cursor over the top of the other a/c's purple circle and pressing LMFD OSB18. Do it right and the other guy will get a message and can Wilco to accept the SPI or Cantco to ignore it.

If the other Client accepts the 'Hook' then the received SPI should be a red triangle on their TAD. The best part is that this indicator doesn't go away when I change my SPI to something different. I can send many SPIs to the other A-10Cs and each one will be recorded onto their TAD.

I do not know how a red triangle on a TAD can be cleared once it is accepted.

I don't know what would happen if I tried to Hook an A-10C that is not in my Group.

WC

Should be as simple as hooking the triangle and clicking "OSB7" (CNC). That should remove it.


Not much different than hooking one that is in your group. Different information on the TAD, otherwise the same I believe. Sending info should also work.

You can send a tasking to any suitable participant (all A-10C are fine) of the datalink by selecting any TAD object (doesn't have to be SPI), then the recipient TAD object, and pressing the OSB next to send.

Its very handy Hooking the wingman as it gives you HUD directions to the wingmans location. Now if only we could do that to the tanker for night missions.

I love to hook my lead _as_ wingman. Having a pseudo radar tie to your flight member is great.

Tanker's pretty good if you have the TACAN address. I think all the KC-135s in DCS support range and heading via TACAN. The trouble is often knowing the address.

AA TACAN is great, seeing a little dot appear ahead meaning you've tracked down the tanker is great