Difference between revisions of "ATC-pie user guide"

From FlightGear wiki
Jump to navigation Jump to search
Line 40: Line 40:
| --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)
| --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 in AD mode; 300 in CTR mode
| --tower-view-external=''host'' || Avoid running an internal FlightGear process for tower viewing, and specify a host on which a viewer is running. This may still be "localhost". || (none, start internal process)
| --tower-view-external=''host'' || Avoid running an internal FlightGear process for tower viewing, and specify a host on which a viewer is running. This may still be "localhost". || (none, start internal process)

Revision as of 09:54, 21 February 2016

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 online video tutorial on YouTube;
  • the in-app quick reference available from the Help menu (summary of mouse/keyboard gestures, display conventions, etc.).

Anyone motivated to write a full user guide is obviously welcome to contact the developer, or improve this article.

Getting ATC-pie to run


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. The latter requires Git, but will keep you in sync with updates more easily. Your choice. In either case, you will have no compiling to do (make, etc.), but do make sure you have the few dependencies installed, listed in the README file (Python3 + bindings to Qt5).

Downloading the tarball:

  1. get the latest stable version from the project page;
  2. extract the files to the directory of your choice.

To clone the repository:

git clone git://git.code.sf.net/p/atc-pie/code ATC-pie

When a new release is announced and if you have cloned the repository, you can update your software with a single command from the downloaded directory:

git pull

Starting the program

Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you need is to run a Python3 interpreter on the ATC-pie.py file in the top-level directory. You may start the program in either airport or centre mode, i.e. respectively with or without a base airfield.

The airport mode is typically used 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 use configuration. To start the airport mode from a system terminal, say with base airfield ICAO, the command to run is:

./ATC-pie.py ICAO

If no ICAO code is given, good old KSFO will be chosen as default.

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.py --ctr=code radar_position

The radar_position argument specifies the point on which to centre the radar, for example given as world coordinates (see down resources/bg-img/Notice 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:

./ATC-pie.py code

Additional command line options are available:

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 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 in AD mode; 300 in CTR mode
--tower-view-external=host Avoid running an internal FlightGear process for tower viewing, and specify a host on which a viewer is running. This may still be "localhost". (none, start internal process)
--tower-view-ports=udp,telnet Specify the tower view ports to send/connect to. These can be the same (UDP and TCP on same port), and are used whether the viewer process is internal (child) or external (local or remote). 5010,5010
--add-view=host:port Register an additional FlightGear instance to forward MP and solo game packets to. This option can be repeated. (none)
--views-send-from=port Change 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 multi-player connection ports, chosen on MP connect. 5009
--fgcom-server=address Set the server used by internal FGCom radio boxes. fgcom.flightgear.org
--fgcom-ports=list-spec Specify a comma-separated list of port numbers for internally started radio boxes. The first one becomes reserved for echo test and ATIS recording while every other port will allow for an additional radio box in the game. Alternatively, enter a string of the form reserved+nboxes as a shortcut for a contiguous range of nboxes+1 ports. 16665+4 (port 16665 reserved, plus 16666 through 16669 for up to 4 radio boxes)

Running for the first time

A few things you will want to do when running ATC-pie for the first time:

  • If you intend to use the radio like you should in multi-player games, check the FGCom version setting in the System menu, and try an echo test. Read the resources/fgcom/Notice file if you have problems hearing yourself, and check the FAQ section in this article.
  • In the same menu, if you want to use the tower viewing system and not bother making it external (see feature note below), make sure you have the right paths set for your FlightGear installation.
  • Set up the important location-specific settings like airport runway parameters, especially ILS capability if you will be playing solo often at the same location.

Note for multi-player games: callsigns for ATCs are typically 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...). Before choosing your callsign on MP connect, make sure it is not already in use, and note that FGMS restricts callsign length to 7 characters. :-(

Feature notes

This section describes a few major features. A more exhaustive list can be found in the main article.

Routing and conflict warnings

ATC-pie analyses routes and assigned vectors to assist traffic management and anticipate path conflicts between controlled aircraft. This feature is essential in centre mode.

Route details dialog with world path drawn, available when both end airfields are recognised

A route is parsed for every strip with recognised departure and destination airports (entry fields both turned green), as follows:

  • route tokens are whitespace-separated;
  • each recognised navpoint token (world navigation aid, 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 always the nearest homonym to the point beginning the leg;
  • other tokens are kept as route leg specifications to the following waypoint (allows for airway or procedure names for example).
Assigned routes can be drawn as dotted lines on the radar scope when linked to contacts

Parsed routes on flight plans and strips are viewable in a route dialog, showing leg details and the geodesic paths on a world map. Also, when a route is parsed and linked to a radar contact, ATC-pie works out its current leg based on distance to destination, and:

  • the route to go is drawn as a dotted line on the radar scope (according to scope "show" options);
  • details of the current leg are displayed in the selection info pane, and the route dialog enabled for full route viewing;
  • the strip shows only the remainder of the route for this contact;
  • the info box contains the next waypoint and the heading leading the aircraft to it on a great circle, unless:
    • the current route leg is the first, and the keyword "SID" appears in its specification: "SID wp" is displayed, where wp is the first waypoint on the route;
    • the current route leg is the last, and the keyword "STAR" appears in its specification: "STAR wp" is displayed, where wp is the last en-route waypoint.

If no route can be interpreted (missing or unidentified DEP or ARR), info boxes will show the strip destination detail (ARR) if it is filled, possibly with a heading if it is recognised.

Separation rings, coloured when a conflict is detected and involving the aircraft (see table)
Route conflict depiction

ATC-pie also features a conflict prediction system, which can be activated or turned off from the Options menu. It uses route and vector assignments to anticipate and alert you of path conflicts so you can take action and prevent separation losses.

When looking for conflicts, a horizontal (ground projection) path is considered for every aircraft with a linked strip and a parsed route or an assigned heading vector. An aircraft is assumed to follow its route, unless a heading vector is given in which case it is assumed to be flying the assigned straight course. Path conflicts occur when horizontal paths intersect and the intervals between respective current and assigned altitudes overlap. When no altitude is assigned, the interval is one around the current altitude. When an aircraft's altitude is unknown, any assigned altitude will be considered instead.

Another possible alarm is the separation incident, a serious ATC mistake which calls for immediate action. The table below summarises the different levels of conflicts, ranked in decreasing order of emergency.

Conflict warnings in ATC-pie
Alarm Shown on scope (default colours) Meaning
Separation incident Bright red intersecting circles Separation loss between aircraft
Path conflict Red circles and paths Anticipated paths and altitudes are intersecting
Possible path conflict Yellow circles, red paths Ground projection of paths are conflicting but not all altitudes are known

Solo training mode

In solo games, you control virtual IFR planes via the instruction interface, receiving and handing over strips to virtual ATCs depending on your position and aircraft's intentions. ATC-pie allows to train in different situations:

  • as an en-route controller (CTR) if started in centre mode;
  • or in airport mode, where three combinable positions are available:
    • tower (TWR), controlling runways and immediate surroundings;
    • departure (DEP), bringing departing traffic to their exit point;
    • approach (APP), vectoring arrivals onto final.

When playing CTR, your task is to transit the aircraft across your airspace, always ensuring separation, and to hand each of them over to the most appropriate neighbouring centre North, South, East or West of your sector. You can specify local navpoints in the location settings so that the system includes them as turning points in the randomised aircraft's routes. In airport mode, traffic is either inbound or outbound. Assuming APP, inbound aircraft must be sequenced and vectored into tower range for handover, unless you are in the TWR position as well. Each inbound aircraft either requests ILS (you must clear them for ILS approach), or visual (they require vectors until they report the expected runway is in sight). Playing TWR, you must clear them to land and hand them over to ground control (GND) once they have vacated the runway. If landing cannot take place (too high, not cleared, etc.), aircraft will climb back up for go-around. Tower also manages outbound traffic, which appears ready holding short of runways. After take-off, hand over your strips to departure control, unless you are assuming DEP yourself. When doing DEP, you must hand outbound aircraft over to the en-route centre (CTR) once they are high enough and close to their exit point if specified.

Handover pane when playing solo in airport mode, assuming all three available positions
Handovers with virtual ATCs in airport mode
Departure strips Arrival strips
Assuming positions Receive from Hand over to Receive from Hand over to

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 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:

  • approach in dense traffic: select APP position only and increase traffic density;
  • 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;
  • CTR mode with a low ceiling to increase the number of conflicts to resolve;
  • etc.

Tower viewing

Tower viewing, following a departing aircraft

This feature allows you to overlook your airport and the connected (MP) or simulated (solo) traffic, like a controller from a tower viewpoint. It uses the tower position specified in the source data if any, otherwise defaults to somewhere over the airport to allow towering all available airports. It is disabled in CTR mode.

There are two ways of activating a tower view. You may let ATC-pie start its own suitably configured FlightGear process, or have it connect to an external viewer, manually set up and accepting connections. The latter way takes a little more effort but allows to run FlightGear on a different machine and thereby relieve your session from the CPU load a local instance induces. If you are going for that, start ATC-pie with --tower-view-external and check the --tower-view-ports and --views-send-from command line options in the table above to set it up correctly.

Running internally only requires FlightGear installed on your computer. A basic installation is enough, but:

  • not all aircraft will be drawn properly if you do not have the corresponding models installed—it is up to you to add models or create substitution links (in your FlightGear root directory or in resources/fg-aircraft according to the Notice file), or be happy with the default blue and yellow glider that will stand for any missing model;
  • more importantly, you will need the scenery for your airport if you want anything exciting to see (and not sea!)—go to this page or use TerraSync to download it to your computer, and add it to your FlightGear root directory or set the right scenery directory in the System menu (ATC-pie will pass it on to FlightGear and save your setting).

In either case, once activated from the View menu, the tower view controller pane is enabled and you can turn to runway points, follow selected aircraft, etc. Additionally, use right click and drag directly on the view to look around, and you may use the x/X keys to change the zoom level from the view window (this is direct FlightGear input).

You can also connect additional viewers to your session, for example placed around your airport for exciting camera footage of challenging landings. You will not be able to control those viewers from ATC-pie like the tower viewer, but you will be able to activate/stop the connection with a switch in the application View menu. To do so, append an option --add-view=XXX:YYY to your ATC-pie command for every additional FlightGear viewer started on host XXX with options --multiplay=out,TTT,HHH,PPP and --multiplay=in,TTT,,YYY. In these options:

  • HHH is the host on which ATC-pie is running (same value for all viewers);
  • PPP is the default 5009, or the chosen port number if ATC-pie is started with --views-send-from (same value for all viewers);
  • TTT is the network polling frequency (100 is common practice; change as desired if you know what you are doing);
  • YYY is the port number used by the viewer for FGMS packet reception.

Multi-player strip exchange (handovers) and OpenRadar interoperability

Example of a strip received from "DEL"

The handover feature in ATC-pie is based on OpenRadar's exchange server to enable ATC coordination between users of both software programs. However, it is to note that their philosophies differ in several ways:

  • OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip;
  • OpenRadar's concept of handover is based on a shared notion of aircraft ownership, whereas ATC-pie allows any controller to pull out a strip, write any callsign and link it to a radar contact;
  • in the OpenRadar philosophy, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring OpenRadar users to see the handover complete, whereas ATC-pie considers that a strip sent through the hand-over pipe is gone and should land directly on a receiver's rack at the other end, without anybody else necessarily to know.

For most interactions to work while still respecting both philosophies as much as possible, the following principles were chosen:

  • ATC-pie users can only hand over strips that are linked to a radar contact (no lone strip can be sent);
  • aircraft under ATC-pie control are not shown as "owned" to OpenRadar users;
  • handovers from ATC-pie will fail if an OpenRadar user in range is claiming ownership;
  • when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally.

Callsign exchange policy:

  • O-R to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail properly;
  • ATC-pie to O-R: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
  • 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. For a full presentation about the feature, check tutorial video 6.

Background images

Pixmap image example with a topographic map shot around LIMW (Aosta, Italy)
Hand drawing example with procedures for LSGG (Geneva, Switzerland)

Background images allow to decorate radar scopes with all sorts of maps and useful information about the airspace, terrain or procedures.

There are two ways to add images to the radar background. One is to import pixmap files, which may contain transparency. The other is to write a text drawing specification file to draw coloured lines and label points. This allows to import anything from the most complex coloured height map to the the most schematic airspace outline. All images are positioned with lat/lon coordinates or navpoint names in radar range. The resources/bg-img/Notice file explains how to import and draw background images.

For example, you can map out SID/STAR routes with one image per published chart, named by procedure and associated runways to make in-game selection easy. If you want more than schematic line plots of the procedures, the best way is certainly to draw the images yourself with good enough resolution, e.g. with Gimp. Superimpose a layer on top of a real map canvas, or over a screenshot of your ATC-pie radar with pinned navaids as landmarks. If you have proper to-scale documentation, it is worth trying the command below (requires ImageMagick) to turn the white background of a ready published chart into transparency, and checking if the rendered images are acceptable and zoom-resistant enough.

convert -transparent white input-file.png output-file.png

Use the image positioning helper tool in the System menu if you want to adjust image corners visually rather than programmatically. All visible pixmap images will be moved simultaneously, so you can work with several at a time if you need to. On dialog box close, a file is generated in the output folder for you to open and copy/edit, or use as a direct substitution.


Here are a few tips to help you navigate and use the program.

Interface and information display

The Options menu is divided in two sections. Items above the separator are unsaved session options, which go back to their default setting on restart. Under the separator are the saved settings, which come in two flavours:

  • location-specific (under a single submenu): saved and restored when started at the same location again, e.g. runway ILS capabilities for an airport, main METAR station;
  • global settings (all other entries): saved and restored regardless of location or game mode, e.g. preset text chat messages.

You can customise the radar colours by editing the colour codes in the settings/colours.ini file generated on first run.

Heading displays are mostly magnetic so they can be read out to pilots. The only exceptions perhaps are the navigator and handover list tooltips, for easier human identification on the scope. All directions are geodesic.

The transition level displayed in the weather analysis is the lowest flight level that is still above the transition altitude. This does not mean the lowest to be expected in ATC clearances, which may be higher, for more vertical separation on either side of the transition layer or due to coordination with neighbouring zones and fields.

The grouped tick marks along the localiser line (when shown) indicate best altitudes AMSL for final approach along the defined flight path angle: every mark in a group is 1,000 ft.

Radio and text communications

Several 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 left-Ctrl 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.

Say you are TWR coordinating with GND at your airport, and you want to monitor both radio frequencies while you are only in charge of TWR. To set this up, start your radio box on TWR frequency and turn on a second one to monitor GND. Tick "Kbd PTT" only for TWR so that you only transmit to your frequency and don't interfere with the other, and set the volume to "soft" on the latter so that you can tell the radio you are hearing the messages from, and know if it is for you to answer.

The PTT turns off sounds option is recommended for those of you who do not wear headsets, as it will avoid GUI sound notifications being picked up by your microphone while transmitting on frequencies.

For more efficient text chat, text aliases are available and allowed in both instant and preset chat messages, e.g. $wind, $qnh... When the containing message is sent, they automatically expand to the current context-dependant value. Custom aliases can be used, whose replacement will be searched for in the general and local notes (your notepads) and in the selected strip comments. This allows for variable text by controller, by location (AD or CTR) and by radar contact. Have a look at the Quick reference available from the Help menu, Text aliases section. Unsuccessful replacements will trigger an edit box so that you can review your message before sending it.

Everything up to the first pipe character (|, if any) in a text chat line will be stripped before the message is processed and sent. For quicker access to preset messages if you use them and the keyboard a lot, you can therefore prefix your messages with a custom shortcut and a pipe, which will enable the automatic suggestion list to pull up the desired message line as you start typing the prefix. Here is a preset message example enabling something like a dot-command for sending a bearing to your base airport to the currently selected pilot:

.qdm|Heading to airport $qdm

If a troll or angry user is polluting your session with undesired messages, click and hold the Dest. tool button in the text chat dock to add their callsign to the senders blacklist. All messages from the user will then be filtered out from the message pane.

Strip and flight plan details

Every initial contact by a pilot should basically make you hit F2 and enter at least the call sign announced. You should then soon figure out if:

  • a flight plan is filed, in which case you can save the strip relatively quickly and look for the FPL to link to it (middle click on the FPL entry);
  • a flight plan must be filed (e.g. IFR departure not filed by lazy pilot), which only takes a tick in the bottom-line box before saving to open a freshly linked FPL detail sheet to fill;
  • he was asked to contact you by a previous ATC, in which case you may have a strip handed over to you already (check the unassigned strip rack);
  • etc.

In airport mode, typing a single dot character '.' in an airport input field will instantly fill the box with your ICAO position. Use this as a shortcut from/to your airport when filling details.

Resolving strip–FPL conflicts:

  • to confirm strip details: open the strip detail sheet, tick the "push details to FPL" box and save to propagate the strip details;
  • to confirm FPL details: "pull FPL details" from the button menu to reset the conflicting strip details to the values filled in the linked flight plan;
  • to confirm some details of each source: open the strip sheet, get rid of the bad details before pushing to the flight plan.

Resolving local–online flight plan conflicts:

  • to update the online version with your local modifications, double-click the flight plan and tick the "publish" box before saving (if still decorated red, there was a network problem or the change was rejected by the server);
  • to discard all local modifications of an online FPL, remove the FPL from the list and check for new flight plans again (the deleted entry should be retrieved with online state).


Questions frequently asked (at least twice) about the program:

Q: How do I start anywhere else than bl*ody KSFO?

Use a command line argument: ./ATC-pie.py ICAO

Q: Why am I not seeing this aircraft on my radar? I know it is there: the pilot is sending chat messages and/or it is visible on the online live map...

You only see an aircraft on your screen if your radar picks up a transponder signal from it. The two following cases will therefore prevent you from seeing a connected aircraft:

  1. Its onboard transponder is turned off, i.e. not responding to your radar ping, and you should tell the pilot to switch it on. See the ATC-pie video tutorial 1. If the aircraft model does not support the transponder feature, it will be simulated by ATC-pie according to the fallback mode you have selected in the settings dialog; any non-zero mode will make the aircraft visible to you. Alternatively, you can switch on the primary radar system if you want to see aircraft's position, or activate the "radar cheat mode" if you want to go the radical way (tutorial 3).
  2. The aircraft is out of range, under the radar floor (minimum signal pick-up height) or too far out. Open the General settings dialog, check the NM range setting and set the floor to "SFC" to pick up all signals.

Q: What is the strip exchange server? Which one to use?

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 http://h2281805.stratoserver.net/FgFpServer. 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 create an account?

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?

Yes, and virtually anything else, using background images and hand drawings. To learn how, see the corresponding section above, read the resources/bg-img/Notice file and have a look at the packaged example for KSFO.

Q: How do I assign SIDs and STARs to aircraft?

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
    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
    When such route is parsed on the selected strip, text aliases $wpsid and $wpstar 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, $wpsid will turn into "FUBAR" and $wpstar 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 $sid alias that will automatically be filled in your sent messages when that strip is selected.

Q: FGCom radio is not working. What is going on?

There can be a variety of reasons, all of them to rule out before reporting a bug in the program. Start a single ATC-pie instance and try the echo test (System menu). If it works, you may skip directly to item 3 below.

  1. Bad FGCom version setting
    Verify the "FGCom version" set in the System menu, which should point to the right executable file under resources/fgcom and suit your operating system (see Notice file). Four versions are initially packaged with ATC-pie: Linux64, Linux32, Mac, Win32.
  2. FGCom server down
    This can happen, unfortunately even for up to a few days. Check for responses from the server, e.g. with ping fgcom.flightgear.org.
  3. FGCom subprocess error
    If the server is up (responding to ping), check for errors in the logged FGCom output files in the output directory.
  4. Port mess-up on your side
    If you are running multiple instances of ATC-pie, make sure you have no more than one radio box on every port. In any case, verify you only choose available ports that are not already in use by your operating system for example. Typically, default ports (from 16661 counting up) work fine, but you will have to change them for parallel instances, using the --fgcom-ports command line option (see section: starting the program). To check what port a radio box is using, see its "on/off" button tooltip.

Q: Tower view is not starting. The menu option is ticked but nothing happens.

Ruling out that FlightGear is not installed at all, your system path settings are probably wrong. From a terminal, find the right command to start FlightGear and enter it as FlightGear executable from the System menu. Do not add options of any kind; they will be taken care of internally. You may have to enter a FlightGear root directory as well, especially if you have the program files installed somewhere unexpected. Your entries will be saved after that.

Q: Why is my tower in the middle of the sea, and aircraft water landing/floating?

You are missing the FlightGear scenery data for your location, or ATC-pie does not know where it is. Check out the Tower viewing feature note in this article.