265
edits
ATC-pie user guide: Difference between revisions
Jump to navigation
Jump to search
v1.8.6
Mickybadia (talk | contribs) (v1.8.5) |
Mickybadia (talk | contribs) (v1.8.6) |
||
| 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 | Other ways to learn the program are: | ||
* the online [https://www.youtube.com/playlist?list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb video tutorial]; | * to watch 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...); | * to read the in-app ''Quick reference'' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions...); | ||
* a skilled teacher | * to connect with a skilled teacher as a student (personal training); | ||
* to [[#Solo_sessions|train solo]]! | * to [[#Solo_sessions|train solo]]! | ||
== Flight strips == | == Flight strips == | ||
Whether dematerialised or on | Whether electronic (dematerialised) or on paper, printed automatically or filled by hand, the '''flight progress strip''' is the essential piece of air and ground traffic control. Every aircraft in contact is represented by a unique strip on the ATC workbench, and every strip represents a unique contact, present or expected. This ensures that no aircraft is ever forgotten about. Strip positioning and updating then enable to monitor the aircraft's status, sequence number, position, intentions, etc. | ||
=== Strip details and linking === | === Strip details and linking === | ||
A click on the "new strip" tool bar button (shortcut {{key press|F2}}) 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. | [[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]] | ||
A click on the "new strip" tool bar button (shortcut {{key press|F2}}) 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. callsign, type of aircraft, destination, etc. Double-clicking on an existing strip allows to edit the filled details. | |||
If providing radar service, strips should be '''linked''' to identified contacts to inform the radar display with the filled details and enable joint selection. To link a strip to a radar contact, select one and middle-click on the other. Conflicts between the strip details and the values squawked by the linked transponder contact are reported: the strip displays a "!!XPDR" warning and the strip dialog labels the conflicting details. | If providing radar service, strips should be '''linked''' to identified contacts to inform the radar display with the filled details, e.g. assigned altitude, and enable joint selection. To link a strip to a radar contact, select one and middle-click on the other. Conflicts between the strip details and the values squawked by the linked transponder contact are reported: the strip displays a "!!XPDR" warning and the strip dialog labels the conflicting details. | ||
A strip can also be linked to a filed flight plan (FPL). This will make radar and strip display fall back on filed information for missing details. The strip dialog also shows the mismatching information between the two, though this is rather common because the strip typically gets updated as the flight progresses. | A strip can also be linked to a filed flight plan (FPL). This will make radar and strip display fall back on filed information for missing details. The strip dialog also shows the mismatching information between the two, though this is rather common because the strip typically gets updated as the flight progresses. | ||
| Line 22: | Line 23: | ||
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 {{key press|Shift}}+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. | 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 {{key press|Shift}}+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 {{key press|F2}} and type the spoken callsign. You should then soon figure out if, | For fast and efficient service, every initial contact by a pilot should basically make you hit {{key press|F2}} and type the spoken callsign. You should then soon figure out if: | ||
* a flight plan is | * you already have a strip for that contact, e.g. it was automatically printed earlier, or handed over by a colleague: a "!!dup" warning appears next to the input field; | ||
* a | * a flight plan is filed whose details can be linked immediately: a number of candidate FPLs is displayed on a button in the bottom row, which you can click on to select the matching FPL; | ||
* a FPL must be filed, e.g. IFR departure not filed by lazy pilot: click on the "new FPL" button in the bottom row to open a fresh FPL detail sheet on save (FPL will be created and linked if saved). | |||
=== Strip placeholders === | === Strip placeholders === | ||
| Line 43: | Line 43: | ||
* a '''strip shelf''' (flat button at the bottom of loose and racked strip panels), which clears the strip from your workbench and stores it as shelved. | * a '''strip shelf''' (flat button at the bottom of loose and racked strip panels), which clears the strip from your workbench and stores it as shelved. | ||
== Vectors, routes and separation | == Vectors, routes and separation == | ||
ATC-pie can register and analyse issued vectors and routes to: | ATC-pie can register and analyse issued vectors and routes to: | ||
| Line 66: | Line 66: | ||
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 ( | * each recognised navpoint token (radio navigation beacon, 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); | ||
* if ambiguous (navpoint names are not all unique around the world), a waypoint is | * if ambiguous (navpoint names are not all unique around the world), a waypoint is the nearest homonym to the point beginning the leg; | ||
* other tokens are kept as route leg specifications to the following waypoint | * other tokens are kept as route leg specifications to the following waypoint, e.g. airways between fixes. | ||
[[File:ATC-pie-screenshot-routeDrawing.png|thumbnail|Assigned routes are drawn as dashed lines on the radar scope when linked to contacts]] | [[File:ATC-pie-screenshot-routeDrawing.png|thumbnail|Assigned routes are drawn as dashed lines on the radar scope when linked to contacts]] | ||
| 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 | '''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. | ||
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. | |||
All other aliases will be considered custom, in other words to take | 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 (saved for replacement anywhere that the program will be opened), in the general notes (notepad dock); | * 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; | * location (saved for this airport or centre), in the local notes; | ||
* single aircraft contact (by selected strip), in the strip comments. | * single aircraft contact (by selected strip), in the strip comments. | ||
| Line 166: | Line 166: | ||
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. 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. | 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. | ||
=== ATC text chat === | === ATC text chat === | ||