(v1.6.0)
(v1.8.8)
 
(17 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{forum|83|ATC-Pie support & development}}
{{forum|83|ATC-Pie support & development}}


{{about|the software in general|a manual on how to use it|ATC-pie user guide}}
{{about|the software and its features|help with installation or configuration|ATC-pie installation guide|a manual on how to use it|ATC-pie user guide}}


{{Infobox Software
{{Infobox Software
Line 10: Line 10:
| developedby            = Michael Filhol
| developedby            = Michael Filhol
| initialrelease        = February 1, 2015
| initialrelease        = February 1, 2015
| latestrelease          = 1.6.0 (March 31, 2019)
| latestrelease          = 1.8.8 (April 1, 2023)
| writtenin              = Python3
| writtenin              = Python
| writteninversion      = 3
| os                    = Any
| os                    = Any
| platform              = Qt5
| platform              = Qt5
Line 20: Line 21:
}}
}}


'''ATC-pie''' is an [[air traffic control]] simulation program featuring solo sessions, multi-player network connections (through [[FGMS]]) and tutorial sessions for teacher supervision of an ATC student. It can simulate en-route centre control (CTR) as well as airport-based services (TWR, APP, GND...), and allows 3D tower viewing through [[FlightGear]].
'''ATC-pie''' is a free (libre) [[air traffic control]] simulation program with strong ties to [[FlightGear]]. It features:
* solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
* "multi-player" network sessions (FlightGear and FSD protocols supported);
* tutorial sessions for teacher supervision of an ATC student.


It is essentially designed for realism and simulates many tasks and situations of real-life ATC such as:
It is designed to support a maximum range of ATC situations (roles, equipment...), at any world location and for every session type above. All control positions are possible, whether airport-based (TWR, APP, GND...) or en-route (CTR). Equipment may include radar screens, data link, etc. or be limited to binoculars and a view of the airfield.
* strip rack and sequence management;
* radar monitoring and transponder identification;
* handovers to/from neighbouring controllers;
* ATIS recording;
* flight plan filing and editing;
* routing and conflict anticipation;
* voice instruction recognition and pilot speech synthesis in solo sessions.


The program is free and open source, and programmed in Python3 for Qt5 hence system-independant. Only Python3 and its Qt5 bindings must be installed. That done, it is meant to work straight away, with no make/compile command to run or external resource to install. The whole world is immediately available on radar. Tower viewing requires the appropriate FlightGear aircraft and scenery.
Its essential goal is realism. It simulates many tasks of real-life ATC such as:
* strip racks and sequence management;
* coordination with neighbouring controllers (handovers, voice phone calls...);
* radar monitoring and identification of traffic;
* vectoring and course/level conflict anticipation;
* flight plan operations;
* CPDLC...


== Screenshots ==
== Screenshots ==
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.


<gallery mode="packed">
<gallery mode="packed">
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-soloMode.png|Playing solo with three coloured racks
ATC-pie-screenshot-soloMode.png|Solo session with three coloured racks
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
Line 46: Line 47:
</gallery>
</gallery>


== Working principles ==
Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.


=== General ===
== Detailed feature list ==
You are the air traffic controller, working with or without a tower window or radar scope, depending on your position and local facility. Players will connect to the network (multi-player), AI traffic be simulated (solo), or student traffic generated and controlled by the teacher, all with different types of aircraft, [[transponder]] equipment and intentions.


As in real life if you use a radar, your main technology is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], hence unless you cheat or activate the primary radar, it will show you only what you pick up from on-board transponders in its range. This means:
=== Sessions and environments ===
* if a transponder is off or out of range, you will not see the aircraft on your radar screen;
Session/connection types:
* if a transponder is on and in range, you will at least be able to see its position and read the transponder code, possibly its altitude and even its type and callsign, depending on the mode set by the pilot and your radar capabilities.
* solo simulation (AI traffic)
* FlightGear network connection ([[FGMS]] protocol)
* FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
* teaching service (spawn and simulate traffic visible to a connected student)
* student session (control traffic simulated by teacher)


=== Strips ===
Location modes (available for all sessions):
[[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]]
* airport (AD): positions such as TWR, GND, APP, DEP at a selected airfield
Your basic traffic flow and sequence working unit is the '''strip''', each representing a controlled (or soon expected) aircraft. Strips are created, filled with details and moved along and across ''racks'' until handed over to a different controller or discarded. Strip details include:
* en-route centre (CTR): free positioning of radar, no base airport or runway-related options
* most importantly, the aircraft's ''callsign'', to be used on the radio;
* information like aircraft type, airspeed, route... that can be specified by the pilots themselves when filing ''flight plans'';
* transponder code and flight parameter assignments (or vectors: heading, altitude/FL, speed).


=== Linking strips ===
{| class="wikitable" style="text-align:center"
Strip details can be manually edited, but every strip can also be '''linked''' to a flight plan and/or a radar contact. Linking to a strip will automatically:
|+ Feature support by session type
* make the strip display the missing elements available from the linked aircraft transponder or flight plan;
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
* if you use radar, inform the contact label with useful details provided on the strip, e.g. assigned altitude.
|-
Any detail mismatch between a strip and its linked flight plan or radar contact will be reported for you to resolve.
! ACFT traffic
| AI aircraft generated according to RWY capacities, ACFT equipment, intentions...
| colspan="2" | connected flight sim pilots
| created and simulated by teacher
|-
! ATCs and coordination
| virtual ATCs depending on assumed positions
| colspan="2" | connected ATC clients (full ATC-pie interaction, [[#Interoperability with other software|interoperability with other software]])
| teacher-configured ATCs
|-
! Voice radio
| voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back
| colspan="2" | [[FGCom-mumble]] integration
| teacher simulates pilots
|-
! ATC phone lines
| N/A
| colspan="2" | integrated Mumble connection
| teacher simulates ATCs
|-
! Flight plans
| local entries only
| interface with the FlightGear ''de facto'' [http://flightgear-atc.alwaysdata.net data base by Lenny64]
| available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs)
| shared virtual online system
|-
! CPDLC
| interpreted subset of instruction messages
| integrated (supported by MP IRC)
| integrated interface with [https://www.hoppie.nl/acars/ Hoppie's ACARS network]
| full simulation by teacher (with WILCO assistance to execute instructions)
|-
! Weather
| randomised and evolving
| real world METAR retrieval
| fetch from server or retrieve real world METAR
| controlled by teacher
|-
! Other specific features
| style="text-align:left" |
* aircraft type and airline choice with custom appearence in tower view
* configurable airspace rules and traffic density, incl. uncontrolled distractors
| style="text-align:left" |
* exact aircraft rendering in views (incl. control surfaces, etc.)
* legacy [[FGCom_3.0|stand-alone FGCom]] alternate possible (although deprecated)
| style="text-align:left" |
* frequency tuning system for radio text chat
* text ATIS repeatedly sent through radio chat on recorded frequency
| style="text-align:left" |
* traffic snapshots and recall to repeat situations with the student
* individual aircraft freeze
|}


=== Radar identification ===
=== ATC surveillance ===
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]]
Radars and tracking:
When using radar, ATCs can rely on different things to ''identify'' an aircraft and link the right contact to a strip. They can read an aircraft's callsign straight away if its transponder has mode S turned on, tell from reported positions and altitudes, or use a transponder code.
* SSR mode capability selection (none/A/C/S)
* primary radar toggle
* traffic identification assistant
* position/track vs. strip assignment mismatch warning system
* route/vector conflict anticipation
* separation incident alarm
* runway occupation/incursion detection


For instance, say a transponder-equipped VFR traffic makes radio contact giving their callsign and approximate position. ATC will typically pull out a new blank strip and give the pilot a unique transponder code to squawk, writing it on the strip alongside the announced callsign, then wait for it to appear on the radar. This allows for '''radar identification''' of aircraft–strip pairs such that:
Tower view in airport mode (rendered by FlightGear):
* the strip is assigned a transponder code;
* view of airport, aircraft, weather, time of day
* no other strip is assigned the same code;
* start internal process or use externally running instance
* the aircraft is the only unidentified traffic squawking that code in radar range.
* control panel to orient/zoom view or follow aircraft
* additional views can be connected (for multiple camera angles)


ATC-pie identifies such pairs automatically and reports them to you so you can properly link the two and get back to the pilot: "radar identified".
Other:
* radio direction finding (RDF) and integration to radar
* multiple weather (METAR) station monitor


== Detailed feature list ==
=== Traffic management ===
Strips and racks:
* user-defined strip racks with configurable colours (for linked radar contacts) and ATCs to receive from
* runway boxes with automatic RWY separation timers
* loose strip bays with customisable backgrounds


Available session types:
Flight plans and routes:
* FlightGear multi-player network connections
* flight plan system (file, edit, open, close, publish/retrieve online)
* Solo sessions (simulated IFR traffic)
* world route suggestions, presets, analysis, radar drawing and world map view
* Teacher–student tutoring (teacher spawns and manipulates the traffic visible to the student)
* departure clearance assistant
* automatic strip printing for expected departures or arrivals (from FPLs)


For all session types:
Radar tools:
* airport mode (for ATC positions such as TWR, GND, APP, DEP at a selected airfiled)
* convenient mouse input for instructions (vectors, taxi...) and CPDLC integration
* en-route centre (free positioning of radar, no base airport or runway-related options)
* approach spacing hints (estimated touch-down time difference, sequence optimisation suggestions)
* quick point-to-point heading and distance measuring tool
* direct text annotation of radar screen
* flag/unflag (highlight) radar targets


=== General ===
=== Communications ===
Common data sources:
With aircraft:
* Airport and navigation data retrieved from [http://data.x-plane.com X-Plane] sources (whole world default file set included)
* voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
* [[ATIS]] recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)
* Radar background images and hand drawings (integrated EuroScope/[http://www.vatsim.net VATSIM]/IVAO .sct sector file import)
* [[controller-pilot data link communication]] (CPDLC), incl. DEP clearance delivery, multi-element messages...
* Ground elevation maps (can be generated automatically with a provided script)
* text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist
* Real world magnetic declination lookup


GUI features:
ATC coordination:
* Multiple window workspace (radar screens, strip racks and bays) saved by location
* strip exchange (handovers)
* Floatable/dockable panels and toolbars (see [[:File:ATC-pie-screenshot-toolbars.png|screenshot]]) and layout save/restore
* CPDLC authority transfers
* Customisable colours
* telephone lines and switchboard (direct voice communication)
* Notification system combining selectable sounds, status bar messages and time-tagged history
* text messaging (private channels and general ATC chat room)
* "who has?" requests


=== Other ===
Misc. tools:
Misc. tools:
* Quick point-to-point heading and distance measuring tool
* world airport, map navpoint and AD parking position browsing/indicating
* Multiple weather station monitor
* aeronautical unit conversion calculator
* Direct text annotation of radar screen
* custom alarm clocks with quick keyboard timer start
* World airport, map navpoint and AD parking position browsing/indicating
* general and location-specific notepads restored between sessions
* Aeronautical unit conversion calculator
* Custom alarm clocks with quick keyboard timer start
* General and location-specific notes and settings saved on close and restored on restart


=== ATC surveillance ===
GUI:
Radar and transponders:
* multiple window workspace (radar screens, strip racks and bays) saved by location
* SSR mode selection and primary radar activation
* floatable/dockable panels and toolbars (see [[:File:ATC-pie-screenshot-toolbars.png|screenshot]]) and layout save/restore
* Full transponder support and mode-dependant radar behaviour
* notification system combining selectable sounds, status bar messages and time-tagged history
* Traffic identification assistant
* customisable style and colours
* Runway occupation/incursion detection
* Position/track vs. assignment mismatch warning system


Tower viewing (airport mode, requires FlightGear):
Data sources:
* Renders view of airport, aircraft, weather, time of day
* airport and navigation data sourced in the [http://developer.x-plane.com/docs/specs X-Plane] format (old world-wide default file set provided but custom imports recommended)
* Internally started or through an externally running instance
* editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
* Control panel to orient/zoom view or follow aircraft
* custom radar background images and hand drawings (EuroScope/[http://www.vatsim.net VATSIM]/IVAO "sector file" conversion tool included)
* Additional views can be connected (for multiple camera angles)
* ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
* manual magnetic declination input


=== Traffic management ===
== Interoperability with other software ==
Strips and racks:
* User-defined racks with configurable colours for linked radar contacts and ATCs to collect strips from
* Strip auto-print for expected departures
* Runway boxes with automatic WTC timers when freed
* Loose strip bays with customisable backgrounds


Routes, vectors, conflicts:
=== OpenRadar ===
* World route suggestions, presets, analysis, radar drawing and world map view
[[OpenRadar]] is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:
* Convenient mouse input for vectors, taxi instructions and waypoint changes
* OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip;
* Current leg and next waypoint display with geodesic calculations of headings and distances
* 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 and write a callsign on it;
* Route/vector conflict anticipation and separation incident alarm
* in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring users to see it complete, whereas ATC-pie considers that a strip sent is gone and assumed to land on the receiver's rack, without anybody else necessarily to know.
* Approach spacing hints for inbound sequences
 
Communications:
* [[FGCom]] radio integration for multi-player and tutoring sessions (possible use of externally running client), incl. ATIS recording (see [[:File:ATC-pie-screenshot-ATISdialog.png|feature dialog]] with pre-filled preparation notepad), multiple frequency transmissions and monitoring, frequency-specific sound level selection
* Radio direction finding (RDF) and integration to radar
* Controller-pilot data link communication (CPDLC)
* Public text chat in MP with preset messages, auto-completion, predefined and custom aliases for context-sensitive replacements, sender blacklist to filter out trolls
 
ATC coordination:
* Private messaging with other ATCs (text "landlines")
* General ATC chat room
* "Who has?" requests


=== Session environments ===
For most interactions to work in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs:
FlightGear multi-player sessions:
* ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact;
* Strip exchange: handovers with other ATC-pie and [[OpenRadar]] instances in range
* aircraft under ATC-pie control are not shown as "owned" to OpenRadar users;
* Weather: real world METAR retrieval
* handovers from ATC-pie will fail if an OpenRadar user is claiming ownership on the linked radar contact;
* Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), incl. run-time retrieval, opening, closing, filing and editing (work on local copies and manage sync with online status)
* when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally.
* In-app announcement of ATC sessions on Lenny64's event page


Solo sessions (AI traffic):
Callsign handover policy:
* Strip exchange: handovers to/from virtual ATCs
* OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
* Weather: randomised
* ATC-pie to OpenRadar: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
* Voice instruction recognition (with Sphinx)
* pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.
* Pilot read-back speech synthesis (with pyttsx)
* Airline choice and custom aircraft appearence
* Configurable airspace rules
* Adjustable difficulty (traffic density)


Tutoring sessions (teacher with student):
Features not supported by OpenRadar:
* Strip exchange: configurable ATC neighbours and handover supervision by teacher
* wake turbulance category on strips (but detail preserved for ATC-pie clients later receiving the strip);
* Weather: controlled by teacher
* ATC text messaging;
* Traffic snapshots and recall to repeat situations with the student
* ATC phone lines;
* CPDLC transfers.


== Using ATC-pie ==
Who-has requests are fully supported.


To download the program and learn more about how to use it, read the ATC-pie [[ATC-pie installation guide|installation]] and [[ATC-pie user guide|user]] guides. If you have a question, check the [[ATC-pie FAQ|FAQ]] for help or try the forum.
=== Euroscope ===
Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD. It has been increasingly tailored for VATSIM, although for a long time it allowed also to connect to "plain" (non-VATSIM) FSD servers. Operability outside of VATSIM is now discontinued all together, but older versions of Euroscope are still around and connecting to FSD networks. ATC-pie is able to interact with them in FSD sessions, but only to a limited extent:
* sending a strip to Euroscope will result in a loss of all strip details but the callsign (which must be connected), the only information left to the recipient being the FPL details for that callsign if any (strip changes made after FPL data retrieval are therefore lost);
* receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed");
* who-has requests will remain unanswered by Euroscope;
* there are no integrated phone lines to Euroscope clients.


[[Category:ATC-pie]]
[[Category:ATC-pie]]
[[Category:ATC clients]]
[[Category:ATC clients]]
[[Category:Air Traffic Control]]
[[Category:Air Traffic Control]]

Latest revision as of 08:27, 2 April 2023

ATC-pie is a free (libre) air traffic control simulation program with strong ties to FlightGear. It features:

  • solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
  • "multi-player" network sessions (FlightGear and FSD protocols supported);
  • tutorial sessions for teacher supervision of an ATC student.
ATC-pie
ATC-pie logo
Tower viewing, following a departing aircraft
Tower viewing, following a departing aircraft
Developed by Michael Filhol
Initial release February 1, 2015
Latest release 1.8.8 (April 1, 2023)
Written in Python (Version 3)
OS Any
Platform Qt5
Development status Active
Type ATC client
License GNU GPL v3
Website

It is designed to support a maximum range of ATC situations (roles, equipment...), at any world location and for every session type above. All control positions are possible, whether airport-based (TWR, APP, GND...) or en-route (CTR). Equipment may include radar screens, data link, etc. or be limited to binoculars and a view of the airfield.

Its essential goal is realism. It simulates many tasks of real-life ATC such as:

  • strip racks and sequence management;
  • coordination with neighbouring controllers (handovers, voice phone calls...);
  • radar monitoring and identification of traffic;
  • vectoring and course/level conflict anticipation;
  • flight plan operations;
  • CPDLC...

Screenshots

Visit the ATC-pie screenshot category for more.

Detailed feature list

Sessions and environments

Session/connection types:

  • solo simulation (AI traffic)
  • FlightGear network connection (FGMS protocol)
  • FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
  • teaching service (spawn and simulate traffic visible to a connected student)
  • student session (control traffic simulated by teacher)

Location modes (available for all sessions):

  • airport (AD): positions such as TWR, GND, APP, DEP at a selected airfield
  • en-route centre (CTR): free positioning of radar, no base airport or runway-related options
Feature support by session type
Solo FlightGear FSD Tutoring (teacher/student)
ACFT traffic AI aircraft generated according to RWY capacities, ACFT equipment, intentions... connected flight sim pilots created and simulated by teacher
ATCs and coordination virtual ATCs depending on assumed positions connected ATC clients (full ATC-pie interaction, interoperability with other software) teacher-configured ATCs
Voice radio voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back FGCom-mumble integration teacher simulates pilots
ATC phone lines N/A integrated Mumble connection teacher simulates ATCs
Flight plans local entries only interface with the FlightGear de facto data base by Lenny64 available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs) shared virtual online system
CPDLC interpreted subset of instruction messages integrated (supported by MP IRC) integrated interface with Hoppie's ACARS network full simulation by teacher (with WILCO assistance to execute instructions)
Weather randomised and evolving real world METAR retrieval fetch from server or retrieve real world METAR controlled by teacher
Other specific features
  • aircraft type and airline choice with custom appearence in tower view
  • configurable airspace rules and traffic density, incl. uncontrolled distractors
  • exact aircraft rendering in views (incl. control surfaces, etc.)
  • legacy stand-alone FGCom alternate possible (although deprecated)
  • frequency tuning system for radio text chat
  • text ATIS repeatedly sent through radio chat on recorded frequency
  • traffic snapshots and recall to repeat situations with the student
  • individual aircraft freeze

ATC surveillance

Radars and tracking:

  • SSR mode capability selection (none/A/C/S)
  • primary radar toggle
  • traffic identification assistant
  • position/track vs. strip assignment mismatch warning system
  • route/vector conflict anticipation
  • separation incident alarm
  • runway occupation/incursion detection

Tower view in airport mode (rendered by FlightGear):

  • view of airport, aircraft, weather, time of day
  • start internal process or use externally running instance
  • control panel to orient/zoom view or follow aircraft
  • additional views can be connected (for multiple camera angles)

Other:

  • radio direction finding (RDF) and integration to radar
  • multiple weather (METAR) station monitor

Traffic management

Strips and racks:

  • user-defined strip racks with configurable colours (for linked radar contacts) and ATCs to receive from
  • runway boxes with automatic RWY separation timers
  • loose strip bays with customisable backgrounds

Flight plans and routes:

  • flight plan system (file, edit, open, close, publish/retrieve online)
  • world route suggestions, presets, analysis, radar drawing and world map view
  • departure clearance assistant
  • automatic strip printing for expected departures or arrivals (from FPLs)

Radar tools:

  • convenient mouse input for instructions (vectors, taxi...) and CPDLC integration
  • approach spacing hints (estimated touch-down time difference, sequence optimisation suggestions)
  • quick point-to-point heading and distance measuring tool
  • direct text annotation of radar screen
  • flag/unflag (highlight) radar targets

Communications

With aircraft:

  • voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
  • ATIS recording and reminder alarm (see dialog with pre-filled notepad)
  • controller-pilot data link communication (CPDLC), incl. DEP clearance delivery, multi-element messages...
  • text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist

ATC coordination:

  • strip exchange (handovers)
  • CPDLC authority transfers
  • telephone lines and switchboard (direct voice communication)
  • text messaging (private channels and general ATC chat room)
  • "who has?" requests

Other

Misc. tools:

  • world airport, map navpoint and AD parking position browsing/indicating
  • aeronautical unit conversion calculator
  • custom alarm clocks with quick keyboard timer start
  • general and location-specific notepads restored between sessions

GUI:

  • multiple window workspace (radar screens, strip racks and bays) saved by location
  • floatable/dockable panels and toolbars (see screenshot) and layout save/restore
  • notification system combining selectable sounds, status bar messages and time-tagged history
  • customisable style and colours

Data sources:

  • airport and navigation data sourced in the X-Plane format (old world-wide default file set provided but custom imports recommended)
  • editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
  • custom radar background images and hand drawings (EuroScope/VATSIM/IVAO "sector file" conversion tool included)
  • ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
  • manual magnetic declination input

Interoperability with other software

OpenRadar

OpenRadar is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's 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 and write a callsign on it;
  • in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring users to see it complete, whereas ATC-pie considers that a strip sent is gone and assumed to land on the receiver's rack, without anybody else necessarily to know.

For most interactions to work in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs:

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

Callsign handover policy:

  • OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
  • ATC-pie to OpenRadar: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
  • pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.

Features not supported by OpenRadar:

  • wake turbulance category on strips (but detail preserved for ATC-pie clients later receiving the strip);
  • ATC text messaging;
  • ATC phone lines;
  • CPDLC transfers.

Who-has requests are fully supported.

Euroscope

Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD. It has been increasingly tailored for VATSIM, although for a long time it allowed also to connect to "plain" (non-VATSIM) FSD servers. Operability outside of VATSIM is now discontinued all together, but older versions of Euroscope are still around and connecting to FSD networks. ATC-pie is able to interact with them in FSD sessions, but only to a limited extent:

  • sending a strip to Euroscope will result in a loss of all strip details but the callsign (which must be connected), the only information left to the recipient being the FPL details for that callsign if any (strip changes made after FPL data retrieval are therefore lost);
  • receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed");
  • who-has requests will remain unanswered by Euroscope;
  • there are no integrated phone lines to Euroscope clients.