ATC-pie user guide: Difference between revisions

ATC-pie user guide (view source)

Revision as of 21:19, 5 October 2017

76 bytes added , 5 October 2017

v1.4.0

Mickybadia

265

edits

@@ Line 15: / Line 15: @@
 === Filling details and linking ===
-A click on the "new strip" button (shortcut F2) or double click on an existing flight strip opens a dialog to edit the flight details.
+A click on the "new strip" tool bar button (shortcut F2) or double-click on an empty rack space will open a dialog to fill flight details on a fresh strip, e.g. destination, type of aircraft, etc. Double-clicking on an existing strip allows to edit the filled details.
 If providing radar service, strips should be '''linked''' to identified contacts to inform the radar display with the filled details and enable joint selection. To link a strip to a radar contact, select one and middle-click on the other. Conflicts between the strip details and the values squawked by the linked transponder contact are reported: the strip displays a "!!XPDR" warning and the strip dialog labels the conflicting details.
-A strip can also be linked to a filed flight plan (FPL) to merge the information. The strip dialog also shows the mismatching information between the two, though this is rather common because the strip typically gets updated with the flight progress.
+A strip can also be linked to a filed flight plan (FPL) to merge the information. The strip dialog also shows the mismatching information between the two, though this is rather common because the strip typically gets updated as the flight progresses.
 All together, a selection can involve up to three linked elements: strip, radar contact, flight plan. You can pull details from linked elements to strips (strip panel bottom menu), and push strip details to their linked flight plan if necessary (strip dialog bottom tick box). Unlinking is possible with SHIFT+middle-click. If you use linking carefully, auto-fill options are available from the general settings, to fill blank strip details with newly-linked information.
@@ Line 33: / Line 33: @@
 [[File:ATC-pie-screenshot-stripRacks.png|thumbnail|Strip rack panel]]
-A '''strip rack''' is the preferred way of keeping track of a sequence, e.g. a departure queue at a runway threshold. You can create as many racks as you wish and name them appropriately. Racks can be viewed in the main window and in their own docked or floating panel. The column views show all racked strips at once; the tabbed view avoids spreading the window horizontally. The "default" rack is permanent. It collects strips recovered or received when no other rack is defined.
+A '''strip rack''' is the preferred way of keeping track of a sequence, e.g. a departure queue at a runway threshold. Rack panels can be created from the main window workspace, popped out as separate windows, and a persistent one can be found among the available docks. You can create as many racks as you wish and name them appropriately. Double click on the rack name to edit its properties. Use mouse drag to move strips up and down a rack sequence.
+A '''loose strip bay''' allows free-hand positioning of strips in its reserved space. Such bays are useful for any kind of unsequenced traffic or to map out relative positions when controlling without a radar. You may also import background images, e.g. a ground chart to keep visual track of taxiing aircraft and vehicles. See <code>resources/bg-img/Notice</code> to learn how.
 [[File:ATC-pie-screenshot-runwayReserved.png|thumbnail|Reserved runway marked in yellow]]
-In the same panel, above the racks or in their own tab (resp. column or tabbed view), you can opt to show the '''runway boxes'''. A runway box is a placeholder for a single strip, named after a runway in use and denoting a clearence to use it (enter, cross, land...). Thorough use of runways boxes will help you never clear an aircraft to land over lined up traffic for example. When freed, runway boxes display a timer since last use together with the wake turbulance category of the last contained strip, to help with separation. What is more, if you use radar, a filled runway box marks the runway as ''reserved'' on the scope.
+A '''runway box''' is a placeholder for a single strip, named after a runway and denoting a clearence to use it (enter, cross, land...). Runway boxes are contained in their own dock, and made visible if a corresponding runway is marked in use. Thorough use of runway boxes will help you avoid bad mistakes like clear an aircraft to land over lined up traffic. When freed, runway boxes start and display a timer together with the wake turbulance category of the last contained strip to help with TKOF/LDG separation. What is more, if you use radar, a filled runway box marks the runway as ''reserved'' on the scope.
-The third placeholder type available is the '''loose strip bay''', allowing free-hand positioning of strips in its reserved space. Such bays can be useful for any kind of unsequenced traffic, or to map out relative positions when controlling without a radar. You may also import background images, e.g. a ground chart to keep visual track of taxiing aircraft and vehicles. See <code>resources/bg-img/Notice</code> to learn how.
 Besides, there are two other places a strip can be dropped on, usually when releasing a contact:
 * a connected ATC (if accepting strip exchange), to initiate a handover;
-* the '''strip shelf''' (visible in the bottom right-hand corner of every strip panel), which removes the strip from your work bench and stores it as shelved.
+* the '''strip shelf''' (visible at the bottom of loose and racked strip panels), which clears the strip from your work bench and stores it as shelved.
 == Airport scene rendering ==
+=== Tower view window ===
 [[File:ATC-pie-screenshot-towerViewing.png|thumbnail|Tower viewing, following a departing aircraft]]
 This feature allows you to overlook your airport and the connected (multi-player games) or simulated (solo and teaching sessions) traffic, like a controller from a tower viewpoint. It allows to choose from the tower positions specified in the source data if any, otherwise defaults to somewhere over the airport to allow towering of all available airports. It is disabled in CTR mode. Additionally, more views can be hooked up to your scene.
-=== Tower view window ===
 There are two ways of activating a tower view. You may let ATC-pie start its own suitably configured FlightGear process, or have it connect to an external viewer, manually set up and accepting connections.
@@ Line 214: / Line 213: @@
 To hand a strip over, drag it and drop it on the recipient in the list of connected controllers. Note that some ATCs may not be capable of strip exchange. Check [https://www.youtube.com/watch?v=oQIud-cAlT4 tutorial video 6] for a presentation of the feature.
-Received strips appear unlinked on their collecting rack (if defined), with an identification of the sender which disappears as soon as the strip is clicked on. Double-click on the rack tab or column header to add an ATC callsign from which to collect strips.
+Received strips appear on their collecting rack (if defined), with an identification of the sender which disappears as soon as the strip is clicked on. Double-click on the rack tab or column header to add an ATC callsign from which to collect strips. They may link automatically to identified radar contacts, according to the auto-link configuration (general settings).
 === OpenRadar interoperability ===
@@ Line 285: / Line 284: @@
 : <code>.qdm|Heading to airport $qdm</code>
-Lastly, if a troll or angry user is polluting your session with undesired messages, click and hold the ''Dest.'' tool button in the text chat dock to add their callsign to the '''senders blacklist'''. All messages from the user will then be filtered out from the message pane. You can view and clear this list at any time during the game.
+Lastly, if a troll or angry user is polluting your session with undesired messages, add their callsign to the '''senders blacklist'''. All messages from the user will then be filtered out from the message pane. You can view and clear this list at any time during the game.
 [[Category:ATC-pie]]