ATC-pie user guide: Difference between revisions

Jump to navigation Jump to search
v1.9.0
(v1.8.7)
(v1.9.0)
 
Line 106: Line 106:


=== Voice radio ===
=== Voice radio ===
In solo sessions, voice radio interaction is simulated through speech recognition of instructions and read-back synthesis. Use the {{key press|Ctrl}} key to PTT.  
In solo sessions, radio interaction is simulated through speech recognition of instructions and read-back synthesis. Use the {{key press|Ctrl}} key to PTT.  


In FlightGear and FSD 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. To monitor frequencies without attending them, a trick is to set their volume to "soft" to tell them apart.
In FlightGear and FSD 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. 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 a separate voice communication program for radio. In this case, try making the same {{key press|Ctrl}} key the PTT to preserve other features such as RDF for receiving stations in FG sessions, or the ''PTT turns off notification sounds'' option recommended if not wearing a headset.
Note: Except for solo sessions, you may always use a separate voice communication program for radio. 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 ===
=== CPDLC ===
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 {{key press|Alt}} key with a double-click on a strip or radar contact opens the current or latest dialogue for the selected callsign.
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 {{key press|Alt}} 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 {{key press|Alt}} key with a mouse gesture (also see ''Mouse gestures'' in the quick reference):
Each active CPDLC dialogue window allows to manually compose formatted or free text message elements. But the most frequent and convenient way of creating message elements is to combine the {{key press|Alt}} key with (also see ''Mouse gestures'' in the quick reference):
* click-and-drag vectoring gesture to send a heading, altitude/FL or speed instruction (see [[#Vectors|section on vectors]]);
* a click-and-drag vectoring gesture to send a heading, altitude/FL or speed instruction (see [[#Vectors|section on vectors]]);
* strip drop on an ATC to initiate a CPDLC authority transfer or to send the aircraft a "contact" instruction;
* a strip drop on an ATC to initiate a CPDLC authority transfer or to send the aircraft a "contact" instruction;
* "OK" button click in the instruction panel to send the corresponding formatted instruction.
* an instruction panel "OK" button click to send the corresponding formatted instruction if applicable.


Created message elements are appended to the message buffer in the connection dialogue window until you send the message manually. The other party must then acknowledge it before it times out.
Created message elements are appended to the message buffer in the connection dialogue window until you send the message manually. The other party must then acknowledge it before it times out.
Line 125: Line 125:
Although voice communications should be encouraged for realism whenever possible, ATC-pie has a powerful text chat system for keyboard interaction with pilots in network sessions. In FlightGear sessions, all messages from within at least 100 NM and up to the radar range are visible in the chat. In FSD sessions, whose protocol simulates text frequencies, ATC-pie tunes the chat to the "publicised frequency" in the radio panel.
Although voice communications should be encouraged for realism whenever possible, ATC-pie has a powerful text chat system for keyboard interaction with pilots in network sessions. In FlightGear sessions, all messages from within at least 100 NM and up to the radar range are visible in the chat. In FSD sessions, whose protocol simulates text frequencies, ATC-pie tunes the chat to the "publicised frequency" in the radio panel.


'''Text aliases''' are dollar-prefixed words that ATC-pie tries to replace with context-dependant values when sent. For example, <code>$metar</code> expands to the current primary station weather. This allows to send/save formatted messages like "Current weather is $metar" instead of copy-pasting a weather look-up for every such message.
'''Text aliases''' are dollar-prefixed words that ATC-pie can replace with context-dependant values when sent. For example, <code>$metar</code> expands to the current primary station weather, which allows to send formatted messages like "Current weather is $metar" instead of copy-pasting a weather look-up for every such message. There is a list of predefined aliases, whose replacements depend on the environment, local configuration or current selection. All other aliases are expected to find their replacement in one of the following sources, checked in order (see ''Text aliases'' tab in quick reference for more information):
 
* general notepad (editable in any session, regardless of location);
Predefined aliases such as <code>$metar</code> take values that are specified by the program and may depend on the local environment (weather, declination, airport elevation...), on your configuration (transition altitude, runways in use...) or on the current selection (QDM to airport, assigned route...). They are all listed with their meaning in the "quick reference", ''Text aliases'' section.
* location notepad (saved for this airport or centre);
 
* strip comments (value applies to single aircraft contact).
All other aliases will be considered custom, in other words expected to take a value specified by you, on either of the following levels:
* world (value saved for replacement anywhere that the program will be opened), in the general notes (notepad dock);
* location (saved for this airport or centre), in the local notes;
* single aircraft contact (by selected strip), in the strip comments.
 
Here is how ATC-pie decides what to do with a text alias of the form <code>$foo</code> in a sent message:
# If it is one of the predefined list, the specified substitution is performed. If not, it is a custom alias and we carry on to the next step.
# Look for a line beginning with <code>foo=</code> in the general notes. If one is found, the alias is replaced with what follows the '<code>=</code>' character.
# Look for a line beginning with <code>foo=</code> in the local notes. If one is found, the alias is replaced with what follows the '<code>=</code>' character.
# If a strip is part of the current selection, search likewise in its comment field and substitute if the search succeeds.
# Substitution is unsuccessful. ATC-pie will open an edit box so that you can review your message before sending it.


Moreover, ATC-pie strips everything up to the first '''pipe character''' (<code>|</code>) in the message if any, before it is processed and sent. You may test this by sending "stripped part|sent part" and observe that only the "sent part" makes it to the message contents. You can therefore make your life easier with piped shortcuts in your preset message list. They will pop up like any other message in the filtered menu as you type. For example, the following preset message enables something like a dot-command for sending a bearing to your base airport in a few key strokes:
Moreover, ATC-pie strips everything up to the first '''pipe character''' (<code>|</code>) in the message if any, before it is processed and sent. You may test this by sending "stripped part|sent part" and observe that only the "sent part" makes it to the message contents. You can therefore make your life easier with piped shortcuts in your preset message list. They will pop up like any other message in the filtered menu as you type. For example, the following preset message enables something like a dot-command for sending a bearing to your base airport in a few key strokes:
Line 262: Line 251:
* Controlling the traffic is done in the same way as in solo sessions without voice, i.e. using the click&drag vector and taxi tools and the instruction dock. The only difference is that you control the selected aircraft directly, regardless of your strip links and details. You therefore do not need a strip and a correctly filled callsign to instruct a pilot, though it is a good idea to have one if you want your vectors registered and drawn on the radar. The traffic creation dialog offers to create a linked strip with every new aircraft.
* Controlling the traffic is done in the same way as in solo sessions without voice, i.e. using the click&drag vector and taxi tools and the instruction dock. The only difference is that you control the selected aircraft directly, regardless of your strip links and details. You therefore do not need a strip and a correctly filled callsign to instruct a pilot, though it is a good idea to have one if you want your vectors registered and drawn on the radar. The traffic creation dialog offers to create a linked strip with every new aircraft.
* You may pause the whole simulation, or freeze each aircraft individually. Frozen aircraft will result in stationary flights on the student's radar.
* You may pause the whole simulation, or freeze each aircraft individually. Frozen aircraft will result in stationary flights on the student's radar.
* The ATC text chat system allows to chat to the student directly as the teacher, and to simulate private ATC conversations with the student (select callsign to interact as).
* The ATC text messaging system allows to simulate ATC conversations with the student (select callsign to interact as), or interact with the student directly as the teacher.
* To exchange strips, drop them on "Student" and select whom the strip should appear from on the student's side. Note that for your convenience in further control of the traffic, teacher strips do not disappear on handovers;
* To exchange strips, drop them on "Student" and select whom the strip should appear from on the student's side. Note that for your convenience in further control of the traffic, teacher strips do not disappear on handovers;
* CPDLC is supported, the dialogue windows reflecting the change of perspective (ACFT instead of ATC) and the {{key press|Alt}} key combinations generating requests rather than instructions.
* CPDLC is supported, the dialogue windows reflecting the change of perspective (ACFT instead of ATC) and the {{key press|Alt}} key combinations generating requests rather than instructions.


[[Category:ATC-pie]]
[[Category:ATC-pie]]
270

edits

Navigation menu