265
edits
ATC-pie user guide: Difference between revisions
v1.6.0 update
Mickybadia (talk | contribs) mNo edit summary |
Mickybadia (talk | contribs) (v1.6.0 update) |
||
| Line 1: | Line 1: | ||
{{forum|83|ATC-Pie support & development}} | {{forum|83|ATC-Pie support & development}} | ||
This article is a guide to '''[[ATC-pie]]''', describing some of its major features. A more exhaustive list can be found in the main article. For download and installation help, refer to the [[ATC-pie | This article is a guide to '''[[ATC-pie]]''', describing some of its major features. A more exhaustive list can be found in the main article. For download and installation help, refer to the [[ATC-pie installation guide]]. | ||
Anyone motivated to write a full user guide is obviously welcome to contact the developer, or improve this article. For support and troubleshooting, the [[ATC-pie FAQ]] might get you an answer first. Otherwise kindly ask on the FlightGear forum, where we have a dedicated sub-forum, so the discussion is public and its contents shared. | Anyone motivated to write a full user guide is obviously welcome to contact the developer, or improve this article. For support and troubleshooting, the [[ATC-pie FAQ]] might get you an answer first. Otherwise kindly ask on the FlightGear forum, where we have a dedicated sub-forum, so the discussion is public and its contents shared. | ||
| Line 81: | Line 81: | ||
* hold SHIFT and double-click to clear registered vecors from the linked strip. | * hold SHIFT and double-click to clear registered vecors from the linked strip. | ||
See [https://www.youtube.com/watch?v=BvA3MRlGJjU video 5] of the tutorial for more on vectoring, and check the quick reference ''display conventions'' to interpret the lines and colours of the course and vector graphics around radar contacts. | |||
NB: In multi-player sessions, an appropriate text chat instruction is suggested for every registered vector. This allows you to send it easily, for example to pilots whose communications are limited to text chat. | |||
=== Routes === | === Routes === | ||
| Line 184: | Line 186: | ||
=== Instructing aircraft === | === Instructing aircraft === | ||
[[File:ATC-pie-screenshot-taxiInstructionTool.png|thumbnail|Click&drag taxi instruction tool at OMDB ground]] | [[File:ATC-pie-screenshot-taxiInstructionTool.png|thumbnail|Click&drag taxi instruction tool at OMDB ground]] | ||
Instructions are given through different means: | |||
* provided the speech recognition modules are installed, you can turn on voice instructions from the solo simulation settings dialog and instruct aircraft through your microphone, using the <code>Ctrl</code> key as push-to-talk and standard phraseology (see the quick reference tab about it); | * provided the speech recognition modules are installed, you can turn on voice instructions from the solo simulation settings dialog and instruct aircraft through your microphone, using the <code>Ctrl</code> key as push-to-talk and standard phraseology (see the quick reference tab about it); | ||
* if voice instructions are turned off: | * if voice instructions are turned off: | ||
| Line 190: | Line 192: | ||
** handoffs are issued when dropping strips on an ATC receiver; | ** handoffs are issued when dropping strips on an ATC receiver; | ||
* instruct taxi routes by dragging out of radar contacts when they are considered on the ground (low enough or squawking GND); | * instruct taxi routes by dragging out of radar contacts when they are considered on the ground (low enough or squawking GND); | ||
* the dockable instruction panel works regardless of voice vs. mouse selection. | * the dockable instruction panel works regardless of voice vs. mouse selection; | ||
* if the aircraft is connected to CPDLC, you can be prompted to send the instruction through the data link. | |||
Instructions from the panel are always issued to the callsign entered in the top field, which should fill automatically on aircraft or strip selection when a callsign is known. Therefore, make sure you do not mess up your strip links or your instructions will realistically be acknowledged and followed by the wrong aircraft. | |||
=== Need a scenario? === | === Need a scenario? === | ||
| Line 305: | Line 308: | ||
When '''playing teacher''': | When '''playing teacher''': | ||
* The teaching console | * The teaching console is enabled, which allows you to control most aspects of the environment visible to the student. | ||
* You create new traffic with | * You create new traffic holding SHIFT down with a right click-and-drag on the radar specifying the position and face heading. A dialog pops up and allows you to choose a callsign (one is initially generated), altitude and other details. If near a ground route node, a parking position or runway, you can create it on the ground, ready to taxi or for departure (NB: parking overrides position/heading input). | ||
* Traffic is initially created in an "unspawned" state (round-shaped blip on radar), in other words visible to you but not to the student. This allows you to set its transponder or get it into a certain state before spawning it into the student's world. | * Traffic is initially created in an "unspawned" state (round-shaped blip on radar), in other words visible to you but not to the student. This allows you to set its transponder or get it into a certain state before spawning it into the student's world. | ||
* Controlling the traffic is done in the same way as in solo sessions without voice, i.e. using the click&drag vector and taxi tools and the instruction dock. The only difference is that you control the selected aircraft directly, regardless of your strip links and details. You therefore do not need a strip and a correctly filled callsign to instruct a pilot, though it is a good idea to have one if you want your vectors registered and drawn on the radar. The traffic creation dialog offers to create a linked strip with every new aircraft. | * Controlling the traffic is done in the same way as in solo sessions without voice, i.e. using the click&drag vector and taxi tools and the instruction dock. The only difference is that you control the selected aircraft directly, regardless of your strip links and details. You therefore do not need a strip and a correctly filled callsign to instruct a pilot, though it is a good idea to have one if you want your vectors registered and drawn on the radar. The traffic creation dialog offers to create a linked strip with every new aircraft. | ||