265
edits
ATC-pie: Difference between revisions
Version update (1.1.3)
Mickybadia (talk | contribs) m (Version update (1.1.2)) |
Mickybadia (talk | contribs) (Version update (1.1.3)) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = 1.1. | | latestrelease = 1.1.3 (April 17, 2017) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
| Line 71: | Line 71: | ||
To ''identify'' an aircraft and link the right radar contact to a strip, an ATC can rely on different things. He 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. | To ''identify'' an aircraft and link the right radar contact to a strip, an ATC can rely on different things. He 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. | ||
For instance, say a VFR traffic makes an initial radio contact giving his 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: | For instance, say a VFR traffic makes an initial radio contact giving his callsign and approximate position, with no mode S transponder. 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: | ||
* the strip is assigned a transponder code; | * the strip is assigned a transponder code; | ||
* no other strip is assigned the same code; | * no other strip is assigned the same code; | ||
| Line 121: | Line 121: | ||
GUI: | GUI: | ||
* Floatable | * Floatable/dockable panels and toolbars (see [[:File:ATC-pie-screenshot-toolbars.png|screenshot]]), save/restore custom window layout | ||
* '''Customisable colours''' | * '''Customisable colours''' | ||
* 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 | * Notes, general and location-specific settings saved on close and restored on restart | ||
=== ATC surveillance === | === ATC surveillance === | ||
| Line 139: | Line 139: | ||
Tower viewing (not in CTR mode): | Tower viewing (not in CTR mode): | ||
* Real-time '''rendering of the airport scene''' from tower viewpoint | * Real-time '''rendering of the airport scene''' from selected 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 | ||