265
edits
ATC-pie user guide: Difference between revisions
Jump to navigation
Jump to search
v1.8.1
Mickybadia (talk | contribs) (v1.8.0) |
Mickybadia (talk | contribs) (v1.8.1) |
||
| Line 209: | Line 209: | ||
"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); | ||
* voice land lines (direct phone calls); | |||
* CPDLC authority transfers; | * CPDLC authority transfers; | ||
* ''who-has'' requests, to query the system and know who is claiming contact/control of callsigns; | * ''who-has'' requests, to query the system and know who is claiming contact/control of callsigns; | ||
* ATC text chat, to exchange messages between connected ATCs | * ATC text chat, to exchange messages between connected ATCs. | ||
=== Strip exchange === | === Strip exchange === | ||
[[File:ATC-pie-screenshot-receivedStrip.png|thumbnail|Example of a strip received from "GND"]] | [[File:ATC-pie-screenshot-receivedStrip.png|thumbnail|Example of a strip received from "GND"]] | ||
To hand a strip over, drag it and drop it on the recipient in the list of connected controllers. Received strips appear on their collecting rack (if defined), with an identification of the sender which disappears as soon as the strip is clicked on. They may link automatically to identified radar contacts, according to the auto-link configuration (general settings). Double-click on the rack name to add an ATC callsign from which to collect strips. | To hand a strip over, drag it and drop it on the recipient in the list of connected controllers (''ATC coordination'' dock). Received strips appear on their collecting rack (if defined), with an identification of the sender which disappears as soon as the strip is clicked on. They may link automatically to identified radar contacts, according to the auto-link configuration (general settings). Double-click on the rack name to add an ATC callsign from which to collect strips. | ||
See [https://www.youtube.com/watch?v=oQIud-cAlT4 tutorial video 6] for a presentation of the feature. | See [https://www.youtube.com/watch?v=oQIud-cAlT4 tutorial video 6] for a presentation of the feature. | ||
=== Voice land lines === | |||
Land lines allow to call and talk to other ATCs directly from the ''ATC coordination'' dock. Each land 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. Opening an incoming call puts you on the phone with the caller. In other words, if both parties have a line open, they are in direct communication (no PTT). | |||
You can only talk to one ATC at a time but may place multiple outgoing calls. Opening (answering) an incoming call while already in another call drops the current line, which you can pick back up as long as the other party holds it open ("still incoming"). If a call you placed is answered while you are in another call, the former switches to show as incoming without interrupting the one in progress. Conversely, 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 === | |||
The ATC text messaging system allows to talk to other ATCs in channels that are separate from the public one read by pilots. It offers '''private channels''' simulating one-to-one landline conversations, and a '''general ATC chat room''' in network sessions, readable by all connected ATCs. Note however that ATC-pie features a direct voice (phone) land line switching system for a lot more realistic coordination between human ATCs! | |||
'''Note on interoperability''': While only ATC-pie integrates ATC-side text chat in its interface, other users can join the same channel with an 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. | |||
=== FlightGear sessions and compatibility with OpenRadar === | === FlightGear sessions and compatibility with OpenRadar === | ||
| Line 277: | Line 288: | ||
# An [[OpenStreetMap]] option will take you to the free online map server, centred on your radar centre position. For a quick and dirty start (e.g. for access to coastlines, borders and rivers) you can screenshot the map and use it as a background. | # An [[OpenStreetMap]] option will take you to the free online map server, centred on your radar centre position. For a quick and dirty start (e.g. for access to coastlines, borders and rivers) you can screenshot the map and use it as a background. | ||
== Communications == | == Communications with aircraft == | ||
The features described in this section | The features described in this section apply to multi-player sessions only (excluding voice radio in FSD). In solo sessions, voice radio interaction is dealt with through speech recognition of instructions and read-back synthesis (see above). | ||
=== | === Voice radio === | ||
'''Multiple radios''' can be opened and tuned in at once, and you can talk on either one by holding the PTT mouse button down for the chosen radio box. The <code>left-Ctrl</code> keyboard key will also let you PTT on selected frequencies. You can transmit on several at once, for example to service GND+TWR frequencies in view of splitting them seemlessly again if a controller is expected soon to fill one of the two positions. Tick the ''Kbd PTT'' option in the radio boxes of the frequencies to merge. Your keyboard PTT key will then transmit on them all simultaneously. Note that while you will be broadcasting on, and hearing incoming transmissions from, all frequencies, pilots will not be hearing each other across frequencies. | '''Multiple radios''' can be opened and tuned in at once, and you can talk on either one by holding the PTT mouse button down for the chosen radio box. The <code>left-Ctrl</code> keyboard key will also let you PTT on selected frequencies. You can transmit on several at once, for example to service GND+TWR frequencies in view of splitting them seemlessly again if a controller is expected soon to fill one of the two positions. Tick the ''Kbd PTT'' option in the radio boxes of the frequencies to merge. Your keyboard PTT key will then transmit on them all simultaneously. Note that while you will be broadcasting on, and hearing incoming transmissions from, all frequencies, pilots will not be hearing each other across frequencies. | ||
| Line 289: | Line 300: | ||
=== Radio text chat === | === Radio text chat === | ||
ATC-pie has a powerful text chat system for those who use the keyboard extensively to interact with pilots in network sessions, although voice communications should be encouraged for realism whenever possible. | ATC-pie has a powerful text chat system for those who use the keyboard extensively to interact with pilots in network sessions, although voice communications should be encouraged for realism whenever possible. In FlightGear sessions, all messages are visible between range. FSD simulates text frequencies; ATC-pie tunes to the "publicised frequency" in the radio panel. | ||
First, '''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 write and save formatted messages instead of repeating chunks of a recurrent format. For instance, anybody will enjoy the comfort of sending "Current weather is $metar" instead of copy-pasting a weather look-up for every such message. | First, '''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 write and save formatted messages instead of repeating chunks of a recurrent format. For instance, anybody will enjoy the comfort of sending "Current weather is $metar" instead of copy-pasting a weather look-up for every such message. | ||
| Line 311: | Line 322: | ||
Lastly, if a troll or angry user is polluting your session with undesired messages, add their callsign to the '''senders blacklist'''. All messages from the user will then be filtered out from the message pane. You can view and clear this list at any time. | Lastly, if a troll or angry user is polluting your session with undesired messages, add their callsign to the '''senders blacklist'''. All messages from the user will then be filtered out from the message pane. You can view and clear this list at any time. | ||
== Teacher & student connections (ATC tutoring) == | == Teacher & student connections (ATC tutoring) == | ||