265
edits
ATC-pie installation guide: Difference between revisions
no edit summary
Mickybadia (talk | contribs) (v1.4.1) |
Mickybadia (talk | contribs) No edit summary |
||
| Line 22: | Line 22: | ||
=== More to install? === | === More to install? === | ||
The above alone will provide you with a working program, but a few software pieces can further be installed to enable extra features. They are recommended for more realistic fun, but not required and can be installed later anyway. These are: | The above alone will provide you with a working program, but a few software pieces can further be installed to enable extra features. They are recommended for more realistic fun, but not required and can be installed later anyway. These are: | ||
* ''FlightGear'' for '''tower viewing''' in airport | * ''FlightGear'' for '''tower viewing''' in airport mode (though it can be run on a separate machine, see [[ATC-pie user guide#Tower view window|feature note]] in the user guide); | ||
* ''PocketSphinx'' for '''voice instruction recognition''' in solo | * the ''Python IRC library'' to enable the ATC '''full coorindation and text chat sub-system''' in multi-player sessions; | ||
* ''pyttsx'' for '''speech synthesis''' of pilot radio communications in solo | * ''PocketSphinx'' for '''voice instruction recognition''' in solo sessions; | ||
* ''pyttsx'' for '''speech synthesis''' of pilot radio communications in solo sessions. | |||
See the general <code>README</code> file for more notes on installation. | See the general <code>README</code> file for more notes on installation. | ||
| Line 33: | Line 34: | ||
=== Two program modes === | === Two program modes === | ||
[[File:ATC-pie-screenshot-launcherDialog.png|thumbnail|Initial graphical launcher, with AD | [[File:ATC-pie-screenshot-launcherDialog.png|thumbnail|Initial graphical launcher, with AD vs. CTR mode choice]] | ||
On program start, a welcome launcher window should open, from which you may start a session in either airport (AD) or centre (CTR) mode, i.e. respectively with or without a base airfield. | On program start, a welcome launcher window should open, from which you may start a session in either airport (AD) or centre (CTR) mode, i.e. respectively with or without a base airfield. | ||
| Line 40: | Line 41: | ||
The '''centre mode''' is designed for en-route control centre simulation. It disables all airport-specific features, and allows to place the radar anywhere on Earth. When selecting this mode: | The '''centre mode''' is designed for en-route control centre simulation. It disables all airport-specific features, and allows to place the radar anywhere on Earth. When selecting this mode: | ||
* The location code is a designator of your choice (excluding airport codes), under which to save your location-specific settings. A good idea is to use ICAO airspace designations, e.g. <code>SBBS</code> for the Brasilia FIR in central Brazil or <code>LFFF</code> for the Paris region in France. | * The location code is a designator of your choice (excluding airport codes), under which to save your location-specific settings. A good idea is to use ICAO airspace designations, e.g. <code>SBBS</code> for the Brasilia FIR in central Brazil or <code>LFFF</code> for the Paris region in France. | ||
* The radar position field specifies the point on which to centre the radar. For example, <code>LFPO>090,15</code> will centre the radar on a point 15 NM to the East of Orly airport. Click on the help button for a summary of valid point specification formats, or read the ''Point specification'' section in the | * The radar position field specifies the point on which to centre the radar. For example, <code>LFPO>090,15</code> will centre the radar on a point 15 NM to the East of Orly airport. Click on the help button for a summary of valid point specification formats, or read the ''Point specification'' section in the quick reference for more detail. | ||
You may also bypass the launcher and start directly at a given location with the following command, using an ICAO code for an airport, or a previously defined CTR position: | You may also bypass the launcher and start directly at a given location with the following command, using an ICAO code for an airport, or a previously defined CTR position: | ||
| Line 59: | Line 60: | ||
=== Initial configuration === | === Initial configuration === | ||
Things you will want to do when running ATC-pie for the first time: | Things you will want to do when running ATC-pie for the first time: | ||
* If you intend to use the radio like you should in FlightGear multi-player | * To play multi-player, give yourself a nickname so that others recognise you when using any of the ATC coordination/exchange sub-systems. | ||
* If you intend to use the radio like you should in FlightGear multi-player sessions, try an echo test from the ''System'' menu. If you have problems hearing yourself, check the [[FGCom]] version in the system set-up, read the <code>resources/fgcom/Notice</code> file and search for "FGCom" in the [[ATC-pie FAQ]]. | |||
* In the same dialog, if you want to use the internal tower viewing system, make sure you have the right paths set for your [[FlightGear]] installation. | * In the same dialog, if you want to use the internal tower viewing system, make sure you have the right paths set for your [[FlightGear]] installation. | ||
A message pops up when opening a location for the first time, inviting you to configure the local settings and listing features that may be missing in the provided (X-plane) data. If you intend to play here or come back often, it is sensible to: | A message pops up when opening a location for the first time, inviting you to configure the local settings and listing features that may be missing in the provided (X-plane) data. If you intend to play here or come back often, it is sensible to: | ||
* open the location settings dialog to set things up, e.g. airport runway capabilities (necessary for more realisitc solo | * open the location settings dialog to set things up, e.g. airport runway capabilities (necessary for more realisitc aircraft intentions in solo simulation); | ||
* if you have a custom airport file to use, e.g. downloaded from the [https://gateway.x-plane.com/airports/page# X-plane gateway] to replace one reported insufficient, place it in <code>resources/apt</code> (see the <code>Notice</code> file there); | * if you have a custom airport file to use, e.g. downloaded from the [https://gateway.x-plane.com/airports/page# X-plane gateway] to replace one reported insufficient, place it in <code>resources/apt</code> (see the <code>Notice</code> file there); | ||
* if playing with radar: set up a background picture set with the terrain maps and procedure charts you need, and pin and save your preferred navpoints and labels so that they are restored on the next run; | * if playing with radar: set up a background picture set with the terrain maps and procedure charts you need, and pin and save your preferred navpoints and labels so that they are restored on the next run; | ||
| Line 77: | Line 79: | ||
* note that [[FGMS]] restricts callsign length to 7 characters. :-( | * note that [[FGMS]] restricts callsign length to 7 characters. :-( | ||
Solo | Solo simulation: | ||
* wind will be randomised at start, but can be forced to blow in a favourable direction if you select an active runway first; | * wind will be randomised at start, but can be forced to blow in a favourable direction if you select an active runway first; | ||
* traffic is spawned with intentions according to the solo | * traffic is spawned with intentions according to the solo simulation configuration options, so to avoid undesired traffic at start it is preferable to configure them before starting the session. | ||
[[Category:ATC-pie]] | [[Category:ATC-pie]] | ||