265
edits
ATC-pie user guide: Difference between revisions
no edit summary
Mickybadia (talk | contribs) (New release: r8) |
Mickybadia (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
This article is a guide to help one download and run '''[[ATC-pie]]'''. It describes some of its major features and lists a few tips. Other sources to learn the program are: | This article is a guide to help one download and run '''[[ATC-pie]]'''. It describes some of its major features and lists a few tips. Other sources to learn the program are: | ||
* the ''' | * the '''[https://www.youtube.com/playlist?list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb online video tutorial]''' on ''YouTube''; | ||
* the in-app '''quick reference''' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions, etc.). | * the in-app '''quick reference''' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions, etc.). | ||
| Line 31: | Line 31: | ||
ATC-pie's '''centre mode''' is designed for en-route control centre simulation (CTR). It disables all airport-specific features, and allows to place the radar anywhere on Earth. To start this mode and define a new position, run the command: | ATC-pie's '''centre mode''' is designed for en-route control centre simulation (CTR). It disables all airport-specific features, and allows to place the radar anywhere on Earth. To start this mode and define a new position, run the command: | ||
: <code>./ATC-pie.py --ctr=code radar_position</code> | : <code>./ATC-pie.py --ctr=code radar_position</code> | ||
The ''radar_position'' argument specifies the point on which to centre the radar, for example given as world coordinates (see down <code>resources/bg-img/Notice</code> for full point syntax description; look out for any character to escape from shell). Replace ''code'' by a designator of your choice (excluding airport codes), under which to save your location-specific settings. A good idea is to use ICAO airspace designations, e.g. "SBBS" for the | The ''radar_position'' argument specifies the point on which to centre the radar, for example given as world coordinates (see down <code>resources/bg-img/Notice</code> for full point syntax description; look out for any character to escape from shell). Replace ''code'' by a designator of your choice (excluding airport codes), under which to save your location-specific settings. A good idea is to use ICAO airspace designations, e.g. "SBBS" for the Brasilia FIR in central Brazil. Subsequent runs at the same location will then be enabled without the second argument, and with the even more direct command: | ||
: <code>./ATC-pie.py code</code> | : <code>./ATC-pie.py code</code> | ||
| Line 38: | Line 38: | ||
! Option || Effect and argument specification || Default | ! Option || Effect and argument specification || Default | ||
|- | |- | ||
| --ctr=''code'' || Start in CTR mode at given location code (see above). Anonymous argument sets/resets the radar position for this location. || (none) | | --ctr=''code'' || Start in CTR mode at given location code (see above). Anonymous argument sets/resets the radar position for this location if given. || (none) | ||
|- | |- | ||
| --map-range=''range'' || Define the distance in NM from the radar centre up to which the map will be drawn and navpoints listed in the navigator (accepted values are 20..500). This is a different setting to the radar range configurable in the game settings. || 100 | | --map-range=''range'' || Define the distance in NM from the radar centre up to which the map will be drawn and navpoints listed in the navigator (accepted values are 20..500). This is a different setting to the radar range configurable in the game settings. || 100 | ||
| Line 147: | Line 147: | ||
|} | |} | ||
'''Vectors''' are given by means of the vectoring assignment tool | '''Vectors''' are given by means of the vectoring assignment tool: click&drag on radar contact for heading; add SHIFT for altitude/FL and speed (see [https://www.youtube.com/watch?v=BvA3MRlGJjU video 5] of the tutorial). '''Other instructions''' (''line up and wait'', ''clear to land'', etc.) can be sent from the instruction dock. Pull it up from the ''View'' menu if it is not visible. Instructions are issued to the callsign entered in the top field, which should fill automatically on aircraft or strip selection if the callsign is known. | ||
Things you can train for: | Things you can train for: | ||
| Line 153: | Line 153: | ||
* towering a single runway, optimising its use: select TWR position and an equal balance of departures and arrivals; | * towering a single runway, optimising its use: select TWR position and an equal balance of departures and arrivals; | ||
* change of runways (e.g. irl after wind direction change): start with APP+TWR and select a runway for arrivals at least, play for a while and go back to the dialog to change for the opposite runway; | * change of runways (e.g. irl after wind direction change): start with APP+TWR and select a runway for arrivals at least, play for a while and go back to the dialog to change for the opposite runway; | ||
* CTR mode with a low ceiling to increase the number of conflicts to resolve; | |||
* etc. | * etc. | ||
| Line 191: | Line 192: | ||
* pie-to-pie handovers: strip detail preserved, whether present or absent. | * pie-to-pie handovers: strip detail preserved, whether present or absent. | ||
In practice, in ATC-pie, a strip can be handed over by dropping it on the chosen ATC in the list of connected controllers in range. Received strips appear unlinked on the reserved rack, with an identification of the sender which disappears as soon as the strip is clicked on. | In practice, in ATC-pie, a strip can be handed over by dropping it on the chosen ATC in the list of connected controllers in range. Received strips appear unlinked on the reserved rack, with an identification of the sender which disappears as soon as the strip is clicked on. For a full presentation about the feature, check [https://www.youtube.com/watch?v=oQIud-cAlT4 tutorial video 6]. | ||
=== Background images === | === Background images === | ||
| Line 254: | Line 255: | ||
== FAQ == | == FAQ == | ||
Questions frequently asked (at least twice) about the program: | Questions frequently asked (at least twice) about the program: | ||
| Line 271: | Line 271: | ||
The strip exchange feature allows you to hand over strips to ATCs who are connected to the same server and within 180 NM from your position. The public server currently open for general multi-player use is <code>http://h2281805.stratoserver.net/FgFpServer</code>. To hand over a strip, drag it from its rack and drop it on the chosen callsign in the ATC handover list. Publicise your frequency so that ATCs around know what to tell pilots for them to contact you! | The strip exchange feature allows you to hand over strips to ATCs who are connected to the same server and within 180 NM from your position. The public server currently open for general multi-player use is <code>http://h2281805.stratoserver.net/FgFpServer</code>. To hand over a strip, drag it from its rack and drop it on the chosen callsign in the ATC handover list. Publicise your frequency so that ATCs around know what to tell pilots for them to contact you! | ||
'''Q: What nickname should I use for the strip exchange server? Where to | '''Q: What nickname should I use for the strip exchange server? Where to create an account?''' | ||
This feature is not linked to any | This feature is not linked to any identification process; just choose any name you would like to be recognised by. It will appear in a tooltip over your callsign in the handover list of ATCs who will connect near enough to see you. In a sense, this feature is more social than technical, but makes sense as typical ATC callsigns remain mostly anonymous over MP. Use this field so that other players can identify you. | ||
'''Q: Can I draw SID and STAR procedures on the radar?''' | '''Q: Can I draw SID and STAR procedures on the radar?''' | ||
| Line 283: | Line 283: | ||
This question seems asked quite a lot more than it sounds relevant to a real controller's task. Say you could click around the interface and "assign" a STAR to an inbound aircraft; what would the effect be after that? Should this be important to you, you can always freely comment your strips with the information you want to save. But the realistic wishes in relation to this question are already addressed otherwise: | This question seems asked quite a lot more than it sounds relevant to a real controller's task. Say you could click around the interface and "assign" a STAR to an inbound aircraft; what would the effect be after that? Should this be important to you, you can always freely comment your strips with the information you want to save. But the realistic wishes in relation to this question are already addressed otherwise: | ||
* Planning routes | * Planning routes | ||
*: Published standard departure and arrival procedures (SIDs and STARs) are very often | *: Published standard departure and arrival procedures (SIDs and STARs) are very often referred to in planned routes, which are assigned prior to departure. Hopefully pulled straight from an existing flight plan, such route is written on the initial flight strip, modified as the flight progresses and passed along with handovers. Like any piece of route specification, you can specify that a SID or STAR is to be followed in the strip route field, e.g. "SID FUBAR en route stuff DUMMY STAR". This will even be recognised by ATC-pie and accounted for in the second line of the radar contact info box when appropriate (see feature note on routing). | ||
* Reference for easy text chat communications | * Reference for easy text chat communications | ||
*: When such route is parsed on the selected strip, text aliases <code>$wpsid</code> and <code>$wpstar</code> will respectively be replaced with the first and last en-route waypoints if the "SID"/"STAR" keywords are present and placed correctly. With the example route above, <code>$wpsid</code> will turn into "FUBAR" and <code>$wpstar</code> into "DUMMY". Now if you specifically want to assign a full published procedure name to a contact, e.g. FUBAR4E, and use it in text chat messages without typing it, include a line "sid=FUBAR4E" in your strip comments. It will pop up with the strip mouse-over tooltip, and create a custom <code>$sid</code> alias that will automatically be filled in your sent messages when that strip is selected. | *: When such route is parsed on the selected strip, text aliases <code>$wpsid</code> and <code>$wpstar</code> will respectively be replaced with the first and last en-route waypoints if the "SID"/"STAR" keywords are present and placed correctly. With the example route above, <code>$wpsid</code> will turn into "FUBAR" and <code>$wpstar</code> into "DUMMY". Now if you specifically want to assign a full published procedure name to a contact, e.g. FUBAR4E, and use it in text chat messages without typing it, include a line "sid=FUBAR4E" in your strip comments. It will pop up with the strip mouse-over tooltip, and create a custom <code>$sid</code> alias that will automatically be filled in your sent messages when that strip is selected. | ||