265
edits
ATC-pie: Difference between revisions
New release: r7
Mickybadia (talk | contribs) mNo edit summary |
Mickybadia (talk | contribs) (New release: r7) |
||
| Line 10: | Line 10: | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = February 1, 2015 | | initialrelease = February 1, 2015 | ||
| latestrelease = | | latestrelease = September 21, 2015 (r7) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| os = Any | | os = Any | ||
| Line 65: | Line 65: | ||
Radar scope: | Radar scope: | ||
* Open multiple radar screens | * Open multiple radar screens | ||
* Custom radar background | * Custom radar background image and image display (e.g. to display maps/charts) | ||
* | * Show/hide options for navigation points, vectors and route assignments, etc. | ||
* Quick point-to-point heading | * Quick point-to-point heading and distance measuring tool and access to Earth coordinates | ||
* Custom text labels to annotate radar background | * Custom text labels to annotate radar background | ||
Tower viewing: | Tower viewing, scene rendering: | ||
* Real-time rendering of the airport scene from tower viewpoint, available in | * Real-time rendering of the airport scene from tower viewpoint, available in MP and solo game modes | ||
* Internally started (requires | * Internally started (requires FlightGear installed) or through connection to an external instance | ||
* | * Controller pane to orient/zoom view or follow aircraft | ||
* | * Possible use of custom scenery and aircraft model addition/substitution | ||
* Additional views can be connected | |||
=== ATC management === | === ATC management === | ||
| Line 85: | Line 86: | ||
Routes, vectors, conflicts: | Routes, vectors, conflicts: | ||
* Route parsing and | * Route parsing, drawing and world map view | ||
* Current leg and next waypoint display with geodesic calculations of headings and distances | * Current leg and next waypoint display with geodesic calculations of headings and distances | ||
* Assign vectors and change routes with direct mouse gestures | * Assign vectors and change routes with direct mouse gestures | ||
* Anticipated | * Anticipated conflict warnings and separation incident alarm | ||
* Visible mismatches between assigned vectors and picked up positions | * Visible mismatches between assigned vectors and picked up positions (see [[:File:ATC-pie-screenshot-courseAndAssignmentsGraphics.png|all-in-one graphics]]) | ||
=== Communications === | === Communications === | ||
Radio: | Radio: | ||
* [[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 | * ATIS recording with pre-filled preparation notepad (see [[:File:ATC-pie-screenshot-ATISdialog.png|feature dialog]]) | ||
* Multiple and single frequency transmissions | * Multiple and single frequency transmissions | ||
* Frequency-specific sound level selection | * Frequency-specific sound level selection | ||
Text chat: | Text chat: | ||
* | * Customisable preset messages and text aliases for context-sensitive replacements | ||
* Message history and single-click message recall | * Message history and single-click message recall | ||
* Hardcore communication sim possible by disabling unknown senders' callsigns | * Hardcore communication sim possible by disabling unknown senders' callsigns | ||
* Senders blacklist managament (filter out trolls) | |||
== Screenshots == | == Screenshots == | ||
| Line 109: | Line 110: | ||
|ATC-pie-screenshot-soloMode.png|Playing solo mode with three coloured racks | |ATC-pie-screenshot-soloMode.png|Playing solo mode with three coloured racks | ||
|ATC-pie-screenshot-towerViewing.png|Tower viewing, following a departing aircraft | |ATC-pie-screenshot-towerViewing.png|Tower viewing, following a departing aircraft | ||
|ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display | |ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display | ||
|ATC-pie-screenshot- | |ATC-pie-screenshot-routeDetailsView.png|View route details and world path | ||
|ATC-pie-screenshot-routeConflictDetection.png|Route conflict warning | |ATC-pie-screenshot-routeConflictDetection.png|Route conflict warning | ||
|ATC-pie-screenshot- | |ATC-pie-screenshot-LFPGcloseUp.png|Depiction of airport tarmac and objects | ||
}} | }} | ||
| Line 128: | Line 124: | ||
=== Strips === | === Strips === | ||
[[File:ATC-pie-screenshot-stripDetailSheet.png|thumbnail|The ATC-pie strip detail sheet]] | |||
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: | 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: | ||
* most importantly, the aircraft's ''callsign'', to be used on the radio; | * most importantly, the aircraft's ''callsign'', to be used on the radio; | ||
| Line 140: | Line 137: | ||
=== Radar identification === | === Radar identification === | ||
[[File:ATC-pie-screenshot-radarIdentification.png|thumbnail|Radar identification: both matched strip and radar contact marked in blue]] | |||
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: | 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: | ||
* the strip is assigned a transponder code; | * the strip is assigned a transponder code; | ||