ATC-pie user guide: Difference between revisions

Jump to navigation Jump to search
v1.8.5
(+ Template:Key press)
(v1.8.5)
Line 4: Line 4:


Other sources to learn the program are:
Other sources to learn the program are:
* the [https://www.youtube.com/playlist?list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb online] '''video tutorial''';
* the online [https://www.youtube.com/playlist?list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb video tutorial];
* the in-app '''quick reference''' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions...);
* the in-app ''Quick reference'' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions...);
* a skilled '''teacher''' to connect to as a student (personal training);
* a skilled teacher to connect to as a student (personal training);
* to '''train solo'''!
* to [[#Solo_sessions|train solo]]!


== Flight strips ==
== Flight strips ==
Line 64: Line 64:
=== Routes ===
=== Routes ===
[[File:ATC-pie-screenshot-routeDetailsView.png|thumbnail|Route details dialog with world path drawn, available when both end airfields are recognised]]
[[File:ATC-pie-screenshot-routeDetailsView.png|thumbnail|Route details dialog with world path drawn, available when both end airfields are recognised]]
A '''route''' is analysed for every strip with recognised departure and destination airports (entry fields both turned green), as follows:
A route is analysed for every strip with recognised departure and destination airports (entry fields both turned green), as follows:
* route tokens are whitespace-separated;
* route tokens are whitespace-separated;
* each recognised navpoint token (world navigation aid, airfield, fix, RNAV point) creates a ''waypoint'' on the path to destination, and a route ''leg'' from the previous point (a final leg connects the last point to the destination airport);
* each recognised navpoint token (world navigation aid, airfield, fix, RNAV point) creates a ''waypoint'' on the path to destination, and a route ''leg'' from the previous point (a final leg connects the last point to the destination airport);
Line 85: Line 85:
=== Conflicts and anticipation ===
=== Conflicts and anticipation ===
[[File:ATC-pie-screenshot-routeConflictDetection.png|thumbnail|Route conflict depiction]]
[[File:ATC-pie-screenshot-routeConflictDetection.png|thumbnail|Route conflict depiction]]
ATC-pie features a '''conflict prediction system''', which can be activated or turned off from the ''Options'' menu. It uses route and vector assignments to anticipate and alert you of path conflicts so you can take action and prevent separation losses.
ATC-pie features a conflict prediction system, which can be activated or turned off from the ''Options'' menu. It uses route and vector assignments to anticipate and alert you of path conflicts so you can take action and prevent separation losses.


When looking for conflicts, a horizontal (ground projection) path is considered for aircraft with a linked strip and an assigned route or heading. An aircraft is assumed to follow its route, unless a heading vector is given in which case it is assumed to be flying the assigned straight course. When the projections of two aircraft intersect, a conflict is anticipated if the respective intervals between the current and assigned altitudes overlap. When an aircraft's altitude is unknown, the assigned altitude will be assumed. If an altitude assignment is missing, a ''possible'' conflict is reported.
When looking for conflicts, a horizontal (ground projection) path is considered for aircraft with a linked strip and an assigned route or heading. An aircraft is assumed to follow its route, unless a heading vector is given in which case it is assumed to be flying the assigned straight course. When the projections of two aircraft intersect, a conflict is anticipated if the respective intervals between the current and assigned altitudes overlap. When an aircraft's altitude is unknown, the assigned altitude will be assumed. If an altitude assignment is missing, a ''possible'' conflict is reported.
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.
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 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}} 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.
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.


The '''''PTT turns off sounds''''' option is recommended if you do not wear a headset. It will avoid picking up GUI sound notifications with your microphone while transmitting.
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 ===
=== CPDLC ===
Line 150: Line 150:
"ATC coordination" refers to the following:
"ATC coordination" refers to the following:
* strip exchange, i.e. sending and receiving strips (handovers);
* strip exchange, i.e. sending and receiving strips (handovers);
* ATC phone lines, for private voice calls (only in FlightGear and FSD sessions);
* ATC phone lines, for private voice calls (except in solo sessions);
* CPDLC authority transfers (not available in FSD sessions);
* CPDLC authority transfers (except in FSD sessions);
* ''who-has'' requests, to query ATCs about who is claiming control of callsigns;
* ''who-has'' requests, to query ATCs about who is claiming control of callsigns;
* ATC text chat, to exchange text messages between ATCs (not available in solo sessions).
* ATC text chat, to exchange text messages between ATCs (except in solo sessions).


=== Strip exchange ===
=== Strip exchange ===
Line 164: Line 164:


=== ATC phone lines ===
=== ATC phone lines ===
Phone lines allow to call and talk to other ATCs directly from the ''ATC coordination'' dock. Each line has an outgoing state that you control, toggling between open and closed with a double-click on its phone icon. Opening a line places a call to the connected ATC, showing as "incoming" on their side. When two parties have their line open to one another, they are in direct communication (no PTT). In other words, opening an incoming call puts you on the phone with the caller. Closing a call hangs up the active line, but you can pick it back up as long as the other party holds it open ("still incoming" for you).
Phone lines allow to call and talk to other ATCs directly from the ''ATC coordination'' dock. Each line has an outgoing state that you control, toggling between open and closed with a double-click on its phone icon. Opening a line places a call to the connected ATC, showing as "incoming" on their side. When two parties have their line open to one another, they are in direct communication (no push-to-talk). In other words, opening an incoming call puts you on the phone with the caller. Closing a call hangs up the active line, but you can pick it back up as long as the other party holds it open ("still incoming" for you).


You can only talk to one ATC at a time but may place multiple outgoing calls. If a call you placed is answered while you are in another call, the answered call switches to show as incoming without interrupting the one in progress. Conversely, opening (answering) an incoming call while already in another call drops the current line. If an incoming call you answer turns to "placed" (outgoing only) instead of "in progress", the other party was already on the phone and is now seeing an incoming call from you.
You can only talk to one ATC at a time but may place multiple outgoing calls. If a call you placed is answered while you are in another call, the answered call switches to show as incoming without interrupting the one in progress. Conversely, opening (answering) an incoming call while already in another call drops the current line. If an incoming call you answer turns to "placed" (outgoing only) instead of "in progress", the other party was already on the phone and is now seeing an incoming call from you.


=== ATC text chat ===
=== ATC text chat ===
The ATC text messaging system allows to chat with other ATCs in channels that are separate from the "radio text chat" read by pilots. It offers '''private channels''' for one-to-one conversations, and a '''general ATC chat room''' in network sessions, readable by all connected ATCs.
The ATC text messaging system allows to chat with other ATCs in channels that are separate from the "radio text chat" read by pilots. It offers private channels for one-to-one conversations, and a general ATC chat room in network sessions, readable by all connected ATCs.


'''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.
'''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.
Line 234: Line 234:
[[File:ATC-pie-screenshot-taxiInstructionTool.png|thumbnail|Click&drag taxi instruction tool at OMDB ground]]
[[File:ATC-pie-screenshot-taxiInstructionTool.png|thumbnail|Click&drag taxi instruction tool at OMDB ground]]
Instructions are given through different means:
Instructions are given through different means:
* provided the speech recognition modules are installed, you can turn on voice instructions from the solo simulation settings dialog and instruct aircraft through your microphone, using the <code>Ctrl</code> key as push-to-talk and standard phraseology (see the quick reference tab about it);
* provided the speech recognition modules are installed, you can turn on voice instructions from the solo simulation settings dialog and instruct aircraft through your microphone, using the {{key press|Ctrl}} key as push-to-talk and standard phraseology (see the quick reference tab about it);
* if voice instructions are turned off:
* if voice instructions are turned off:
** mouse vector assignments issue the corresponding instructions (see section on vectors above);
** mouse vector assignments issue the corresponding instructions (see section on vectors above);
265

edits

Navigation menu