265
edits
ATC-pie installation guide: Difference between revisions
Jump to navigation
Jump to search
Version 1.6.2
Mickybadia (talk | contribs) mNo edit summary |
Mickybadia (talk | contribs) (Version 1.6.2) |
||
| Line 15: | Line 15: | ||
: <code>git clone git://git.code.sf.net/p/atc-pie/code ATC-pie</code> | : <code>git clone git://git.code.sf.net/p/atc-pie/code ATC-pie</code> | ||
In either case, you will have no compiling to do (make, etc.), but will require | In either case, you will have no compiling to do (make, etc.), but will require Python3 and its bindings to Qt5. The exact dependencies aere listed in the <code>README</code> file in the downloaded directory. | ||
If you chose cloning with Git, you can update your software when a new release is announced with a single command from the downloaded directory: | If you chose cloning with Git, you can update your software when a new release is announced with a single command from the downloaded directory: | ||
| Line 21: | Line 21: | ||
=== 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 | 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. These are: | ||
* ''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); | * ''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); | ||
* the ''Python IRC library'' to enable the ATC '''full coorindation and text chat sub-system''' in multi-player sessions; | * the ''Python IRC library'' to enable the ATC '''full coorindation and text chat sub-system''' in multi-player sessions; | ||
| Line 27: | Line 27: | ||
* ''pyttsx'' for '''speech synthesis''' of pilot radio communications in solo sessions. | * ''pyttsx'' for '''speech synthesis''' of pilot radio communications in solo sessions. | ||
Again, see the <code>README</code> file for more notes on installation. | |||
== Running == | == Running == | ||
Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you | Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you must do is run a Python3 interpreter on the <code>ATC-pie.py</code> file from the downloaded directory. | ||
=== Two program modes === | === Two program modes === | ||
| Line 59: | Line 59: | ||
=== 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. | ||
* To play multi-player, give yourself a "social name" so that others recognise you when using any of the ATC coordination/exchange sub-systems. | * To play multi-player, give yourself a "social name" 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 | * 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, read the <code>resources/fgcom/Notice</code> file and check the [[FGCom]] path in the system set-up. Also try a 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 | A message pops up when opening a location for the first time, inviting you to configure the local settings. If you intend to play here or come back often, it is sensible to: | ||
* | * set things up in the location settings dialog, e.g. airport runway capabilities (necessary for more realisitc aircraft intentions in solo simulation), radar/communication equipment; | ||
* | * download the latest airport data file from the [https://gateway.x-plane.com/airports/page# X-plane gateway] and place it in <code>resources/apt</code> (see the <code>Notice</code> file there); | ||
* if playing with radar: | * if playing with radar: create/import background pictures like terrain maps and useful procedure charts; | ||
* pin your preferred navpoints so that they are restored on every run; | |||
* create and name strip racks according to the service provided, they will be saved for future runs. | * create and name strip racks according to the service provided, they will be saved for future runs. | ||
| Line 80: | Line 81: | ||
Solo simulation: | Solo simulation: | ||
* wind will be randomised at start, but | * wind will be randomised at start, but will be forced to blow in a favourable direction if an active runway is selected before start; | ||
* traffic is spawned with intentions according to the solo simulation configuration options, so | * traffic is spawned with intentions according to the ''solo simulation configuration options'' (<code>Shift</code>+<code>F11</code>), so it is preferable to configure them before starting the session to avoid undesired traffic at start. | ||
[[Category:ATC-pie]] | [[Category:ATC-pie]] | ||