ATC-pie user guide: Difference between revisions

A click on the "new strip" tool bar button (shortcut <code>F2</code>) or double-click on an empty strip rack or bay space will open a dialog to fill flight details on a fresh blank strip, e.g. destination, type of aircraft, etc. Double-clicking on an existing strip allows to edit the filled details.

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 <code>Shift</code>+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.

For fast and efficient service, every initial contact by a pilot should basically make you hit <code>F2</code> and type the spoken callsign. You should then soon figure out if, for example:

* holding <code>Shift</code>, click and drag vertically for altitude/FL vectors;

* holding <code>Shift</code>, click and drag horizontally for speed instructions;

* holding <code>Shift</code>, double-click on the radar target to clear registered vecors from the linked strip.

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 <code>Ctrl</code> keyboard 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. If you monitor frequencies that you are not servicing, a trick is to set their volume to "soft" to tell them apart.

When [[CPDLC]] is serviced (location setting), aircraft can establish a data link from their cockpit for a direct text communication channel supplementing the radio frequency. You can monitor connections from the CPDLC dock and open a window for each active or terminated connection in the CPDLC history. Combining the <code>Alt</code> key with a double-click on a strip or radar contact opens the current or latest dialogue for the selected callsign.

Each active CPDLC dialogue window allows to manually compose preformatted or free text message elements. But the most frequent and convenient way of creating message elements is to combine the <code>Alt</code> key with a mouse gesture (also see ''Mouse gestures'' in the quick reference):

* You create new traffic holding <code>Shift</code> down with a right click-and-drag on the radar specifying the position and face heading. A dialog pops up and allows you to choose a callsign (one is initially generated), altitude and other details. If near a ground route node, a parking position or runway, you can create it on the ground, ready to taxi or for departure (NB: parking overrides position/heading input).

* CPDLC is supported, the dialogue windows reflecting the change of perspective (ACFT instead of ATC) and the <code>Alt</code> key combinations generating requests rather than instructions.