ATC-pie user guide: Difference between revisions

If providing radar service, strips should be '''linked''' to identified contacts to inform the radar display with the filled details, e.g. assigned altitude, and enable joint selection. To link a strip to a radar contact, select one and middle-click on the other. Conflicts between the strip details and the values squawked by the linked transponder contact are reported: the strip displays a "!!XPDR" warning and the strip dialog labels the conflicting details.

A strip can also be linked to a filed flight plan (FPL). This will make radar and strip display fall back on filed information for missing details. The strip dialog also shows the mismatching information between the two, though this is rather common because the strip typically gets updated as the flight progresses.

All together, a selection can involve up to three linked elements: strip, radar contact, flight plan. You can pull details from linked elements to strips (strip panel bottom menu), and push strip details to their linked flight plan if necessary (strip dialog bottom tick box). Unlinking is possible with {{key press|Shift}}+middle-click. If you use linking carefully, auto-fill options are available from the general settings, to fill blank strip details with newly-linked information.

* you already have a strip for that contact, e.g. it was automatically printed earlier, or handed over by a colleague: a "!!dup" warning appears next to the input field;

* a flight plan is filed whose details can be linked immediately: a number of candidate FPLs is displayed on a button in the bottom row, which you can click on to select the matching FPL;

* a FPL must be filed, e.g. IFR departure not filed by lazy pilot: click on the "new FPL" button in the bottom row to open a fresh FPL detail sheet on save (FPL will be created and linked if saved).

* an ATC callsign in the ATC panel to initiate a handover;

* a '''strip shelf''' (flat button at the bottom of loose and racked strip panels), which clears the strip from your workbench and stores it as shelved.

In FlightGear network sessions, multiple radios can be opened and tuned in simultaneously. You can transmit on either one by holding down the PTT button of the chosen radio, or on a selected set (''Kbd PTT'' boxes ticked) using the {{key press|Ctrl}} key. This lets you PTT on multiple frequencies at once (merged frequencies), for example to service GND+TWR frequencies in view of splitting them seemlessly again later. Note that while you will be broadcasting on, and hearing incoming transmissions from, all frequencies, pilots will not be hearing each other across frequencies. To monitor frequencies without attending them, a trick is to set their volume to "soft" to tell them apart.

Note: Except for solo sessions, you may always use an external voice communication program like [[Mumble]] for radio. It is even necessary in FSD sessions, which do not integrate radio natively. In this case, try making the same {{key press|Ctrl}} key the PTT to preserve other features such as RDF for receiving stations, or the ''PTT turns off notification sounds'' option recommended if not wearing a headset.

* CPDLC authority transfers (except in FSD sessions);

* ATC text chat, to exchange text messages between ATCs (except in solo sessions).

'''Note on interoperability in FG sessions''': While only ATC-pie integrates ATC text chat in its interface, other users can join the same channel with a regular IRC client. They will be able to send and receive public and private messages and chat with everybody, at the only cost of ignoring the system messages that will sometimes appear on their side. For best results, they should use their FlightGear network callsign as their IRC nickname.