265
edits
ATC-pie user guide: Difference between revisions
Jump to navigation
Jump to search
Version update (1.2.0)
Mickybadia (talk | contribs) (Version update (1.1.2)) |
Mickybadia (talk | contribs) (Version update (1.2.0)) |
||
| Line 22: | Line 22: | ||
If you choose cloning with Git, you can update your software when a new release is announced with a single command from the downloaded directory: | If you choose cloning with Git, you can update your software when a new release is announced with a single command from the downloaded directory: | ||
: <code>git pull</code> | : <code>git pull</code> | ||
=== More to install? === | |||
The above alone will provide you with a working program. Optional packages may further be installed to enable two more features: | |||
* FlightGear for '''tower viewing''' in airport games, though it can be run on a separate machine (see feature note below); | |||
* PocketSphinx for '''voice instruction recognition''' in solo games (see the general <code>README</code> file for instructions). | |||
While obviously recommended for more realistic fun, they are not required and can be installed later. | |||
=== Starting the program === | === Starting the program === | ||
| Line 51: | Line 59: | ||
* Set up the important location-specific settings like airport runway parameters, especially ILS capability if you will be playing solo often at the same location. | * Set up the important location-specific settings like airport runway parameters, especially ILS capability if you will be playing solo often at the same location. | ||
NB: | NB: Callsigns for ATCs in FlightGear are expected to start with the ICAO code of the controlled airport or sector, and end with a hint on the provided service (twr, gnd, ctr...). Before choosing your callsign on MP connect, make sure it is not already in use, and note that [[FGMS]] restricts callsign length to 7 characters. :-( | ||
== Feature notes == | == Feature notes == | ||
| Line 175: | Line 183: | ||
[[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: | '''Instructions''' are given through different means: | ||
* | * provided the speech recognition modules are installed, you can turn on voice instructions from the solo game settings tab 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); | ||
* taxi | * if voice instructions are turned off: | ||
* | ** the mouse vector assignment tool will issue the corresponding instructions: click&drag out of a radar contact for heading, hold SHIFT and drag for altitude/FL vertically and speed horizontally (see [https://www.youtube.com/watch?v=BvA3MRlGJjU video 5] of the tutorial); | ||
** 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); | |||
* the dockable instruction panel works regardless of voice vs. mouse selection. | |||
NB: Instructions 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. | NB: 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. | ||
Things you can train for: | Things you can train for: | ||
| Line 197: | Line 208: | ||
* New traffic can be created at any time with a simple SHIFT+click&drag on the radar, specifying the place and face heading of the wanted traffic. A dialog pops up and allows you to choose a callsign (one is initially generated), altitude and other details. If near a parking position or runway threshold, you can place it on the ground instead, ready to taxi or for departure. | * New traffic can be created at any time with a simple SHIFT+click&drag on the radar, specifying the place and face heading of the wanted traffic. A dialog pops up and allows you to choose a callsign (one is initially generated), altitude and other details. If near a parking position or runway threshold, you can place it on the ground instead, ready to taxi or for departure. | ||
* Traffic is initially created in an "unspawned" state, in other words visible to you (marked "?") but not to the student. This allows you to change his transponder settings or get it into a certain state or place before spawning it into the student's world. | * Traffic is initially created in an "unspawned" state, in other words visible to you (marked "?") but not to the student. This allows you to change his transponder settings or get it into a certain state or place before spawning it into the student's world. | ||
* Controlling the traffic is done in the same way as in solo sessions, i.e. with the click&drag vector and taxi tools and through 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 linked if you want your vectors | * Controlling the traffic is done in the same way as in solo sessions without voice, i.e. with the click&drag vector and taxi tools and through 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 linked if you want your vectors drawn on the radar. The traffic creation dialog offers to create a linked strip with every new aircraft. | ||
* You may pause the whole simulation, or freeze each aircraft individually. | * You may pause the whole simulation, or freeze each aircraft individually. Frozen aircraft result in stationary flights on radars. | ||
'''Strip exchange''' is possible, either between both parties ("offline" exchanges) or between the student and the virtual ATCs (in-sim handovers). As the teacher, you must drop every strip on "Student" and select as prompted whom the strip should appear from on the student's side. As the student, drop your strip on any of the ATCs in the neighbours list to simulate a handover, or on "Teacher" if only showing it to your mentor. All student handovers are made visible to the teacher for supervision. Interestingly, for his convenience in further control of the traffic, the teacher's strips do not disappear on handovers. | '''Strip exchange''' is possible, either between both parties ("offline" exchanges) or between the student and the virtual ATCs (in-sim handovers). As the teacher, you must drop every strip on "Student" and select as prompted whom the strip should appear from on the student's side. As the student, drop your strip on any of the ATCs in the neighbours list to simulate a handover, or on "Teacher" if only showing it to your mentor. All student handovers are made visible to the teacher for supervision. Interestingly, for his convenience in further control of the traffic, the teacher's strips do not disappear on handovers. | ||
| Line 206: | Line 217: | ||
=== Tower viewing === | === Tower viewing === | ||
[[File:ATC-pie-screenshot-towerViewing.png|thumbnail|Tower viewing, following a departing aircraft]] | [[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 | 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. | ||
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. | 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. | ||