265
edits
ATC-pie: Difference between revisions
New release (r9)
Mickybadia (talk | contribs) m (r8d) |
Mickybadia (talk | contribs) (New release (r9)) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = | | latestrelease = May 8, 2016 (r9) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
| Line 20: | Line 20: | ||
}} | }} | ||
'''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo games | '''ATC-pie''' is an [[air traffic control]] simulation program allowing to play solo games, connect to [[FlightGear]] multi-player networks and set up tutorial sessions for teacher supervision of an ATC student. It features modes for en-route (CTR) control as well as airport-based service (TWR, APP, GND...) where tower viewing is possible for all types of games. It is essentially designed for realism and simulates many tasks of real-life ATC such as transponder identification, strip rack and sequence management, handovers to/from neighbouring controllers, ATIS recording, flight plan editing, routing and conflict anticipation. | ||
ATC-pie is free and open source, 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 (except for | ATC-pie is free and open source, 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 (except for internal tower viewing, which requires FlightGear and the appropriate scenery). | ||
== Program features == | == Program features == | ||
| Line 28: | Line 28: | ||
The features listed below have been tested on various Linux versions, Mac and Windows. | The features listed below have been tested on various Linux versions, Mac and Windows. | ||
=== | === General features === | ||
* | Games available: | ||
* | * Various game types: solo sessions, FlightGear multi-player, teacher–student connections | ||
* | * For all game types: en-route centre or airport mode | ||
* | |||
Common data sources: | |||
* Airport and navigation data retrieved from the latest [http://data.x-plane.com X-Plane] file set | |||
* Custom additions in separate nav/AD data files | |||
* Real world declination lookup and true/magnetic distinction | |||
Solo games: | Solo games: | ||
* | * Play CTR or a free combination of APP, TWR and DEP positions | ||
* Handovers to/from virtual ATCs | * Handovers to/from virtual ATCs | ||
* Instruction interface and pilot read back | * Instruction interface and pilot read back | ||
* Adjustable difficulty (traffic density) | * Adjustable difficulty (traffic density) | ||
* Departure–arrival and ILS–visual balance options | * Departure–arrival and ILS–visual balance options | ||
* Configurable runways in use | * Configurable runways in use and entry/exit/routing points | ||
FlightGear multi-player games: | |||
* | * Configurable [[FGMS]] connections | ||
* | * Weather: real world METAR retrieval | ||
* | * ATC handovers: strip exchange with other ATC-pie and [[OpenRadar]] instances in range | ||
* | * Flight plans: interface with [http://flightgear-atc.alwaysdata.net Lenny64's data base] (the ''de facto'' FG standard), including in-game retrieval, filing and editing (work on local copies and manage sync with online status) | ||
* In-app facility to announce ATC sessions on Lenny64's popular event page | |||
Teaching/learning sessions: | |||
* Teacher spawns and manipulates traffic visible to student (flight and transponder settings) | |||
* Strip exchange, configurable ATC neighbours and handover supervision by teacher | |||
* Wind control | |||
* Traffic snapshots and recall to repeat situations with the student | |||
GUI: | GUI: | ||
* Floatable, dockable and closable GUI panes: strips, radios, text chat, etc. (window layout saved) | * Floatable, dockable and closable GUI panes: strips, radios, text chat, etc. (window layout saved) | ||
* Notification system combining selectable sounds, status bar messages and | * Notification system combining selectable sounds, status bar messages and time-tagged history | ||
* General and location-specific | * General and location-specific settings and notes saved on close and restored on restart | ||
* Custom alarm clocks with quick two-key timer set-up | * Custom alarm clocks with quick two-key timer set-up | ||
* | * Selectable weather stations | ||
=== | === ATC surveillance === | ||
Radar and transponders: | |||
* Full support and mode-dependant behaviour (off, A, C, S) | * Full transponder support and mode-dependant radar behaviour (off, A, C, S) | ||
* Radar identification assistant (detects unique squawk code matches between radar pick-up and strip assignment) | |||
* Radar identification assistant (unique squawk | * Primary radar activation (see targets without XPDR signals) | ||
* | * Configurable horizontal and vertical radar ranges and rotation speed | ||
* Custom radar background images (integrated [[OpenStreetMap]] image retrieval) | |||
* Custom text labels to annotate radar background | |||
* Quick point-to-point heading and distance measuring tool and access to Earth coordinates | |||
* Open multiple radar screens | * Open multiple radar screens | ||
* | * Individual and general cheat modes | ||
* Ignore contacts | * Ignore contacts | ||
* Customisable colours | |||
Tower viewing | Tower viewing (not in CTR mode): | ||
* Real-time rendering of the airport scene from tower viewpoint | * Real-time rendering of the airport scene from tower viewpoint | ||
* Internally started (requires FlightGear installed) or through connection to an external instance | * Internally started (requires FlightGear installed) or through connection to an external instance | ||
* Controller pane to orient/zoom view or follow aircraft | * Controller pane to orient/zoom view or follow aircraft | ||
| Line 80: | Line 88: | ||
* Additional views can be connected | * Additional views can be connected | ||
=== | === Traffic management === | ||
Strips, racks, flight plans: | Strips, racks, flight plans: | ||
* | * User-defined racks with configurable colours for linked radar contacts | ||
* | * Mouse drag to move strips along and across racks; drop on neighbouring ATCs to hand over | ||
* Link strips to flight plans and radar contacts to merge editable details and inform radar display | * Link strips to flight plans and radar contacts to merge editable details and inform radar display | ||
* Conflicts between linked elements reported | * Conflicts between linked elements reported | ||
Routes, vectors, conflicts: | Routes, vectors, conflicts: | ||
| Line 100: | Line 107: | ||
* [[FGCom]] integration, incl. echo test and possible use of externally running client | * [[FGCom]] integration, incl. echo test and possible use of externally running client | ||
* ATIS recording with pre-filled preparation notepad (see [[:File:ATC-pie-screenshot-ATISdialog.png|feature dialog]]) | * ATIS recording with pre-filled preparation notepad (see [[:File:ATC-pie-screenshot-ATISdialog.png|feature dialog]]) | ||
* Multiple | * Multiple frequency transmissions and monitoring | ||
* Frequency-specific sound level selection | * Frequency-specific sound level selection | ||
| Line 150: | Line 157: | ||
== Using ATC-pie == | == Using ATC-pie == | ||
To download the program and learn more about how to use it, read the [[ATC-pie user guide]]. | To download the program and learn more about how to use it, read the [[ATC-pie user guide]]. If you have a question, check the [[ATC-pie FAQ|FAQ]] for help or try the forum. | ||
[[Category:ATC-pie]] | [[Category:ATC-pie]] | ||
[[Category:ATC clients]] | [[Category:ATC clients]] | ||