265
edits
ATC-pie: Difference between revisions
Jump to navigation
Jump to search
Version 0.9.1 release
Mickybadia (talk | contribs) (r10h) |
Mickybadia (talk | contribs) (Version 0.9.1 release) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = | | latestrelease = 0.9.1 (Sept. 26, 2016) | ||
| 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, connect to [[FlightGear]] multi-player networks and set up tutorial sessions for teacher supervision of an ATC student. It features | '''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 en-route centre control (CTR) as well as airport-based service (TWR, APP, GND...) where 3d tower viewing is possible. It is essentially designed for realism and simulates many tasks of real-life ATC such as strip rack and sequence management, transponder identification, handovers to/from neighbouring controllers, ATIS recording, flight plan editing, routing and conflict anticipation. | ||
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 (except for internal tower viewing, which requires FlightGear and the appropriate scenery). | |||
== Program features == | == Program features == | ||
| Line 37: | Line 37: | ||
* Airport and navigation data retrieved from the latest [http://data.x-plane.com X-Plane] file set | * Airport and navigation data retrieved from the latest [http://data.x-plane.com X-Plane] file set | ||
* Nav/AD data customisation in separate files | * Nav/AD data customisation in separate files | ||
* Editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.) | |||
* Real world declination lookup and true/magnetic distinction | * Real world declination lookup and true/magnetic distinction | ||
* Script to assist data import from .sct sector files (EuroScope/[http://www.vatsim.net VATSIM], IVAO) | * Script to assist data import from .sct sector files (EuroScope/[http://www.vatsim.net VATSIM], IVAO) | ||
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), incl. in-game retrieval, filing and editing (work on local copies and manage sync with online status), opening and closing | |||
* In-app facility to announce ATC sessions on Lenny64's popular event page | |||
Solo games: | Solo games: | ||
| Line 44: | Line 52: | ||
* Handovers to/from virtual ATCs | * Handovers to/from virtual ATCs | ||
* Instruction interface and pilot read back | * Instruction interface and pilot read back | ||
* Airline choice for custom aircraft appearence | |||
* Randomised weather | |||
* Configurable runways in use and entry/exit/routing points | |||
* Adjustable difficulty (traffic density) | * Adjustable difficulty (traffic density) | ||
* Departure–arrival and ILS–visual balance options | * Departure–arrival and ILS–visual balance options | ||
Teaching/learning sessions: | Teaching/learning sessions: | ||
| Line 65: | Line 67: | ||
* 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 time-tagged history | * Notification system combining selectable sounds, status bar messages and time-tagged history | ||
* | * Notes, window state, general and location-specific settings 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 | * Selectable weather stations | ||
| Line 72: | Line 74: | ||
Radar and transponders: | Radar and transponders: | ||
* Full transponder support and mode-dependant radar behaviour (off, A, C, S) | * Full transponder support and mode-dependant radar behaviour (off, A, C, S) | ||
* Radar identification assistant (detects unique | * Radar identification assistant (detects unique matches between strip info and radar signals) | ||
* Primary radar activation (see targets without XPDR signals) | * Primary radar activation (see targets without XPDR signals) | ||
* Open multiple radar screens | * Open multiple radar screens | ||
* Configurable horizontal and vertical radar ranges and rotation speed | * Configurable horizontal and vertical radar ranges and rotation speed | ||
* | * Easy radar background text annotation | ||
* Quick point-to-point heading and distance measuring tool and access to Earth coordinates | * Quick point-to-point heading and distance measuring tool and access to Earth coordinates | ||
* Custom radar background images (and integrated [[OpenStreetMap]] image retrieval) | |||
* Individual and general cheat modes | * Individual and general cheat modes | ||
* Ignore contacts | * Ignore contacts | ||
| Line 88: | Line 90: | ||
* Controller pane to orient/zoom view or follow aircraft | * Controller pane to orient/zoom view or follow aircraft | ||
* Possible use of custom scenery and aircraft model addition/substitution | * Possible use of custom scenery and aircraft model addition/substitution | ||
* Additional views can be connected | * Additional views can be connected (for multiple camera angles) | ||
=== Traffic management === | === Traffic management === | ||
Strips, racks, flight plans: | Strips, racks, flight plans: | ||
* User-defined racks with configurable colours for linked radar contacts | * User-defined racks with configurable colours for linked radar contacts | ||
* Mouse drag to move strips along and across racks | * Mouse drag to move strips along and across racks or loose strip bays | ||
* Handovers with neighbouring or virtual ATCs | |||
* 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 | ||
| Line 132: | Line 135: | ||
=== General === | === General === | ||
You are the air traffic controller, and players will connect to the network (or AI/teacher traffic be simulated in solo | You are the air traffic controller, and players will connect to the network (or AI/teacher traffic be simulated in solo and student modes) with different types of aircraft and [[transponder]] equipment. As in real life, the radar is [http://en.wikipedia.org/wiki/Secondary_surveillance_radar SSR], hence unless you cheat or activate the primary radar, will show you only what you pick up from on-board transponders in your range. This means: | ||
* | * if a transponder is off or on standby, you will not see the aircraft on your radar screen; | ||
* | * if a transponder is on, 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. | ||
=== Strips === | === Strips === | ||
| Line 144: | Line 147: | ||
=== Linking strips === | === Linking strips === | ||
Strip details can be manually edited, but every strip can also be '''linked''' to a flight plan and/or a visible radar contact on the scope | Strip details can be manually edited, but every strip can also be '''linked''' to a flight plan and/or a visible radar contact on the scope screen. Linking to a strip will automatically: | ||
* make the strip display the missing elements | * make the strip display the missing elements available from the linked aircraft transponder or flight plan; | ||
* | * inform the radar 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. | Any detail mismatch between a strip and its linked flight plan or radar contact will be reported for you to resolve. | ||