ATC-pie user guide: Difference between revisions

Jump to navigation Jump to search

ATC-pie user guide (view source)

Revision as of 15:34, 29 November 2025

206 bytes removed ,  29 November
Version 1.9.2
(v1.9.0)
(Version 1.9.2)
 
Line 3: Line 3:
This article is a guide to the air traffic control simulation program [[ATC-pie]], describing some of its major features. A more exhaustive list can be found in the main article. For download and installation help, refer to the [[ATC-pie installation guide]]. For support and troubleshooting, the [[ATC-pie FAQ]] might get you an answer first. Otherwise kindly ask on the dedicated FlightGear sub-forum so that the discussion is public.
This article is a guide to the air traffic control simulation program [[ATC-pie]], describing some of its major features. A more exhaustive list can be found in the main article. For download and installation help, refer to the [[ATC-pie installation guide]]. For support and troubleshooting, the [[ATC-pie FAQ]] might get you an answer first. Otherwise kindly ask on the dedicated FlightGear sub-forum so that the discussion is public.


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


== Flight strips ==
== Flight strips ==
Line 60: Line 60:
See [https://www.youtube.com/watch?v=BvA3MRlGJjU video 5] of the tutorial for more on vectoring, and check the quick reference ''display conventions'' to interpret the lines and colours of the course and vector graphics around radar contacts.
See [https://www.youtube.com/watch?v=BvA3MRlGJjU video 5] of the tutorial for more on vectoring, and check the quick reference ''display conventions'' to interpret the lines and colours of the course and vector graphics around radar contacts.


NB: In network sessions, an appropriate text chat instruction is suggested for every mouse vectoring action. This allows you to send it easily, for example to pilots whose communications are limited to text chat.
NB: In network sessions, an appropriate text radio instruction is suggested for every mouse vectoring action. This allows you to send it easily to pilots whose communications are limited to text.


=== Routes ===
=== Routes ===
Line 122: Line 122:
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.


=== Radio text chat ===
=== Text radio ===
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 messaging 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 displayed. In FSD sessions, whose protocol simulates text frequencies, ATC-pie tunes the text radio to the "publicised frequency" in the radio panel.


'''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):
'''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):
Line 142: Line 142:
* CPDLC authority transfers;
* CPDLC authority transfers;
* ''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 with other ATCs (except in solo sessions).
* ATC text messaging, to exchange text messages with other ATCs (except in solo sessions).


=== Strip exchange ===
=== Strip exchange ===
Line 153: Line 153:


=== 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 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).
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, and closing an active call hangs up the active line, but you can pick it back up as long as the other party holds it open.


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. An incoming call you answer which turns to "placed" (outgoing only) instead of "in progress" means that the other party is 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 already in a call, the answered call switches to show as incoming without interrupting the one in progress. On your side, an incoming call you answer which turns to "placed" (outgoing only) instead of "in progress" means that the other party is already on the phone and is now seeing an incoming call from you. Opening (answering) an incoming call while already in a call yourself drops the current line.


=== ATC text chat ===
=== ATC text messaging ===
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 talk with other ATCs in channels outside of the "text radio" visible to pilots. It offers private channels for one-to-one conversations, and a public ATC chat room in network sessions, readable by all connected ATCs. Text alias substitution works here too.


'''Note on interoperability in FG sessions''': While only ATC-pie integrates ATC text chat in its interface, other users can interact with a regular IRC client connected to <code>mpirc.flightgear.org</code>, with their FlightGear network callsign as IRC nickname, and joining the set IRC channel. 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.
'''Note on interoperability in FG sessions''': While only ATC-pie integrates ATC text messaging in its interface, other users can interact with a regular IRC client connected to <code>mpirc.flightgear.org</code>, with their FlightGear network callsign as IRC nickname, and joining the set IRC channel. They will be able to send and receive public and private messages and talk with everybody, at the only cost of ignoring the system messages that will sometimes appear on their side.


== Solo sessions ==
== Solo sessions ==
Line 223: Line 223:
[[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 {{key press|Ctrl}} 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 options 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);
Line 243: Line 243:
== Teacher & student connections (ATC tutoring) ==
== Teacher & student connections (ATC tutoring) ==


This session type is made to bring an ATC student and a teacher together for tutorial sessions. To '''set up a session''', the student must connect to the teacher, so make sure the teacher's session is running first. Only one student can connect to a teacher at a time. The teacher creates and manipulates traffic for the student to work with, controls the weather and decides on the ATC neighbours. Strip exchange and ATC text chat is possible, either between both parties ("offline" exchanges) or between the student and the virtual ATCs (in-sim coordination). All exchanges are monitored by the teacher, and transparent to the student. The teacher can also snapshot traffic position situations to recall them later.
This session type is made to bring an ATC student and a teacher together for tutorial sessions. To '''set up a session''', the student must connect to the teacher, so make sure the teacher's session is running first. Only one student can connect to a teacher at a time. The teacher creates and manipulates traffic for the student to work with, controls the weather and decides on the ATC neighbours. The student can exchange strips and text messages with virtual ATCs (monitored/simulated by the teacher). The teacher can also snapshot traffic position situations to recall them later.


In '''teacher sessions''':
In '''teacher sessions''':
Line 250: Line 250:
* Traffic is initially created in an "unspawned" state (radar contact marked "+"), in other words visible to you but not to the student. This allows you to set its transponder or get it into a certain state before spawning it into the student's world.
* Traffic is initially created in an "unspawned" state (radar contact marked "+"), in other words visible to you but not to the student. This allows you to set its transponder or get it into a certain state before spawning it into the student's world.
* 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.
* 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.
* 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 send a strip to the student, drop it on the callsign of the ATC whom it should appear sent 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]]
Mickybadia
274

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/143090"

Navigation menu