ATC-pie installation guide
| The FlightGear forum has a
subforum related to: ATC-Pie support & development
ATC-pie is free and open source, and programmed in Python3 for Qt5. It is therefore system-independant, but requires Python3 and the PyQt5 library to run. The exact dependencies and required versions are listed in the
README file packed in the download. Once they are installed, it runs straight away without any compiling to do (make, etc.).
There are essentially two ways of downloading ATC-pie: one is to download a tarball to extract locally; the other is to clone the Git repository.
Downloading the tarball:
- get the latest stable version from the project page;
- extract the files to the directory of your choice.
To clone the Git repository:
git clone git://git.code.sf.net/p/atc-pie/code ATC-pie
More to install?
I say again: the above clone/download alone is not enough: both Python3 and PyQt5 must be installed too. Please read the
README file for extra notes on installation.
At this point with the dependencies installed, you have a working program. But further software pieces can be installed to enable more of its features. Depending on how you mean to use ATC-pie, they can be recommended for more realism but they are not required, and can be installed later.
For a 3D tower view in any airport session, FlightGear must be available, with the appropriate aircraft models and scenery data. Note that it can run on a separate machine, as explained in the user guide.
To enhance solo sessions:
- with voice instruction recognition by the AI aircraft, install PocketSphinx;
- with speech synthesis of AI pilots' radio messages, install pyttsx.
To enhance multi-player sessions (FlightGear and FSD) with an integrated voice land line (telephone) switchboard and enable serious coordination between human ATCs, install PyMumble.
To enhance FlightGear sessions:
- with CPDLC and full ATC coordination including unlimited strip exchange and text messaging, install the Python IRC library;
- with voice radio simulation, install the FGCom-Mumble plugin (requires a Mumble>=1.4 client) or the older standalone FGCom executable client (note that both variants cannot be used simultaneously).
Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you must do is run a Python3 interpreter on the
ATC-pie.py file from the downloaded directory.
Two program modes
On program start, a welcome launcher window should open, from which you may start a session in either airport (AD) or centre (CTR) mode, i.e. respectively with or without a base airfield.
The airport mode is for ATC positions like approach or tower control. In this mode, ATC-pie places the radar at the chosen base airfield, depicts its tarmac and runways, and enables features like tower viewing and runway selection.
The centre mode is designed for en-route control centre simulation. It disables all airport-specific features, and allows to place the radar anywhere on Earth. When selecting this mode:
- The location code is 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.
SBBSfor the Brasilia FIR in central Brazil or
LFFFfor the Paris region in France.
- The radar position field specifies the point on which to centre the radar. For example,
LFPO>090,15will centre the radar on a point 15 NM to the East of Orly airport. Click on the help button for a summary of valid point specification formats, or read the Point specification section in the quick reference for more detail.
Command line arguments
You may bypass the launcher and start directly at a given location with the following command, using an ICAO code for an airport or a previously defined CTR location code:
Besides, the following command line options are available:
|Option||Effect and argument specification||Default|
|--map-range=range||Only valid with a location code argument. Defines 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 does not affect radar range, which can still be greater or lower (and be changed within sessions).'||100 in AD mode; 300 in CTR mode|
|--views-send-from=port||Sets the local UDP port number to bind for sending FGMS packets to views. This includes all tower and additional views, but does not affect the FGMS connection port, chosen on session start.||5009|
Things you will want to do when running ATC-pie for the first time.
- For network sessions (FGMS and FSD), give yourself a "social name" so that others recognise you when using any of the ATC coordination/exchange features.
- To use the internal tower viewing system, make sure you have the right paths set for your FlightGear installation.
- The integrated FGCom radio system is recommended for FlightGear network sessions. Select the variant to use from in the system settings, check the FGCom tab and try an FGCom configuration test from the System menu. If you have problems, search for "FGCom" in the ATC-pie FAQ.
If you intend to operate often at a given location, it is sensible to:
- download the latest airport data file from the X-plane gateway and place it in
- review/fill the various fields in the location set-up dialog (a message pops up on the first time at a location, inviting you to open it), e.g. radar/communication equipment, and airport runway capabilities (necessary for more realisitc aircraft intentions in solo simulation);
- build an elevation map, especially for solo and teacher sessions;
- if using the radar, consider creating/importing background pictures (terrain maps, procedure charts...);
- configure strip racks and bays to fit the environment and service provided, they will be saved for future runs;
- pin your preferred navpoints so that they are restored on every run.
For more detailed and advanced configuration options, check the
- wind will be randomised at start, but will be forced to blow in a favourable direction if at least one active runway is selected before start;
- traffic is spawned with intentions according to the solo simulation configuration options (
F11), so it is preferable to configure them before starting the session to avoid undesired traffic at start.
FlightGear network session:
- callsigns for ATCs in FlightGear are expected to start with the ICAO code of the controlled airport or sector, and end with a hint on the provided service (twr, gnd, ctr...), e.g. "KORDgnd" (note that FGMS restricts callsign length to 7 characters);
- before choosing your callsign, make sure it is not already in use;
- you can connect more than one ATC-pie instance from the same computer, but must use different ports.