265
edits
ATC-pie installation guide: Difference between revisions
Jump to navigation
Jump to search
v1.3.1
Mickybadia (talk | contribs) (Split from the user guide) |
Mickybadia (talk | contribs) (v1.3.1) |
||
| Line 28: | Line 28: | ||
See the general <code>README</code> file for more notes on installation. | See the general <code>README</code> file for more notes on installation. | ||
== | == Running == | ||
Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you need is to run a Python3 interpreter on the <code>ATC-pie.py</code> file in the top-level directory. | Depending on your system and preference, you might be double-clicking, typing stuff or pulling your hair out. In any case what you need is to run a Python3 interpreter on the <code>ATC-pie.py</code> file in the top-level directory. | ||
| Line 57: | Line 57: | ||
== Running for the first time == | == Running for the first time == | ||
=== Initial configuration === | |||
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 games, 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]]. | * If you intend to use the radio like you should in FlightGear multi-player games, 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 | * 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: | |||
* open the location settings dialog to set things up, e.g. airport runway capabilities (necessary for realisitc solo games); | |||
* 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; | |||
* create and name strip racks according to the service provided and save them for future runs too. | |||
=== Starting sessions === | |||
FlightGear multi-player connection: | |||
* 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; | |||
* note that [[FGMS]] restricts callsign length to 7 characters. :-( | |||
Solo games: | |||
* wind will be randomised at start, but you can choose an active runway first so that it is constrained to blow in a favourable direction; | |||
* traffic is spawned with intentions according to the solo game options, so to avoid undesired traffic at start it is preferable to configure them before starting the game. | |||
[[Category:ATC-pie]] | [[Category:ATC-pie]] | ||