ATC-pie installation guide: Difference between revisions

v1.6.4
(Version 1.6.2)
(v1.6.4)
Line 6: Line 6:


=== Downloading ===
=== Downloading ===
There are essentially two ways of downloading [[ATC-pie]]: one is to download a '''tarball''' to extract locally; the other is to clone the '''Git repository'''. The latter requires [http://git-scm.com Git], but will keep you in sync with updates more easily. Your choice.
There are essentially two ways of downloading [[ATC-pie]]: one is to download a '''tarball''' to extract locally; the other is to clone the '''Git repository'''. The latter requires [http://git-scm.com Git], but will keep you in sync with updates more easily. Your choice. In either case, you will have no compiling to do (make, etc.), but will require Python3 and its bindings to Qt5. The exact dependencies are listed in the <code>README</code> file in the downloaded directory.


Downloading the '''tarball''':
Downloading the '''tarball''':
Line 14: Line 14:
To clone the Git '''repository''':
To clone the Git '''repository''':
: <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>
 
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:
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:
: <code>git pull</code>
: <code>git pull</code>


Line 66: Line 63:
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:
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;
* 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);
* download the latest airport data file from the [https://gateway.x-plane.com/airports/page# X-plane gateway] and place it in <code>CONFIG/ad.dat</code> (see the <code>Notice</code> file there);
* if playing with radar: create/import background pictures like terrain maps and useful procedure charts;
* 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;
* 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.


For more detailed and advanced configuration, check the <code>README</code> file for a summary of editable options and the corresponding <code>Notice</code> files.
For more detailed and advanced configuration, check the <code>CONFIG/Notice</code> file for a summary of editable options.


=== Starting sessions ===
=== Starting sessions ===
265

edits