Changes

Jump to navigation Jump to search
1,186 bytes added ,  10:13, 1 November 2017
v1.4.1
Line 81: Line 81:     
=== What is the purpose of the flat "strip shelf" button in the strip panes? ===
 
=== What is the purpose of the flat "strip shelf" button in the strip panes? ===
More than a button, the strip shelf is where you should drop the contacts you release without a handover, e.g. parked traffic shutting down, VFR traffic flying out of your airspace, etc. Clicking on the shelf allows to browse the previously shelved strips, and to recall one (or more), for example shelved inadvertently.
+
More than a button, the strip shelf is where you should drop the contacts you release without a handover, e.g. parked traffic shutting down, VFR traffic flying out of your airspace, etc. Clicking on the shelf allows to browse the previously shelved strips, and to recall them, for example if shelved inadvertently.
    
=== Why do I keep getting runway incursion alarms? ===
 
=== Why do I keep getting runway incursion alarms? ===
Line 99: Line 99:  
* examine the (otherwise useless) packaged KSFO example.
 
* examine the (otherwise useless) packaged KSFO example.
   −
'''If you have a sector file''' of the ".sct" format used in VATSIM/IVAO, you should try the included <code>sectorExtract.py</code> script. It will extract most of the contents, including SID/STAR procedures, and translate them into ATC-pie's native drawing format. Probably your best solution if you know your procedures are included. Here is how to use it:
+
'''If you have a sector file''' of the ".sct" format used in VATSIM/IVAO, you should try to import it with the provided drawing extraction tool. It will extract most of the contents for the open location and current map range, including SID/STAR procedures, and translate them to ATC-pie's native drawing format. It is generally the best solution if you know your procedures are included.
# Run the script: <code>sectorExtract.py sector_file centre:radius output_dir</code>.
+
# Run the "extract drawings from sector file" option (''System'' menu) and select the file to extract from. In the output directory, the resulting files are:
#: In this command:
+
#* <code>ICAO.lst.extract</code>, a menu file for the generated drawings;
#:* ''sector_file'' is the input sector file you wish to extract from;
+
#* <code>bg-ICAO-*</code>, the extracted drawings in the native ATC-pie format;
#:* ''centre'' (Earth coordinates) and ''radius'' (range in nautical miles) specify the wanted coverage of the input sector file;
+
#* <code>bg-extract.err</code>, a log of the errors detected in your sector file (do not be alarmed as they often contain many).
#:* ''output_dir'' is where you want the output files to be generated.
  −
#: In the output directory, the resulting files are:
  −
#:* <code>geo-*</code>, <code>proc-*</code>, <code>boundaries-*</code>, containing the extracted drawings translated for ATC-pie;
  −
#:* <code>extract.lst</code>, a list of the generated drawing files in the expected format;
  −
#:* <code>extract.err</code>, a log of the errors detected in your sector file (do not be alarmed as they often contain many).
   
# Import the results:
 
# Import the results:
#* rename the <code>.lst</code> file to <code>resources/bg-img/ICAO.lst</code>, replacing ''ICAO'' with the location code of where to import the drawings;
+
#* move or copy-paste lines from <code>ICAO.lst.extract</code> to <code>resources/bg-img/ICAO.lst</code>;
#* move the drawing files under <code>resources/bg-img</code>, adjusting the paths in the <code>.lst</code> if you create subdirectories.
+
#* move the desired drawing files under <code>resources/bg-img</code>, adjusting the paths in the <code>.lst</code> menu as you organise subdirectories.
 
# Post-editing (cleaning)
 
# Post-editing (cleaning)
#: ATC-pie does its best to understand the objects in the sector file and to group things together depending on their type. But not everything can be guessed automatically, so you get a lot of files and useless things. This last step is where you merge, split, delete objects, rename points, change colours, etc. to your liking.
+
#: ATC-pie does its best to understand the objects in the sector file and to group things together depending on their type. But not everything can be guessed automatically. This last step is where you filter, merge and split objects, rename points, change colours, etc. to your liking.
#: Each generated drawing block (point list under a colour) is automatically given a label, ending with the line number it was sourced from in the sector file so you can easily trace it (<code>@nnn</code>). A tool like ''sed'' will help you get rid of all these unwanted suffixes once you have sorted and renamed your objects:
+
#: Each generated drawing section (point list under a colour) is automatically given a label, ending with the line number it was sourced from in the sector file so you can easily trace it (<code>@nnn</code>). A tool like ''sed'' will help you get rid of all these unwanted suffixes once you have sorted and renamed your objects:
 
#:: <code>sed -ri 's/ @[0-9]+$//' file_to_clean</code>
 
#:: <code>sed -ri 's/ @[0-9]+$//' file_to_clean</code>
 +
 +
Tip: You can check your image configuration without restarting the program, by reloading from the ''System'' menu or pressing <code>Shift+Alt+F12</code>.
 +
 +
NB: ATC-pie does not package or source from sector files directly because their data is not free, and a lot of it is redundant with its own GPL-licensed X-plane source (GPL).
    
=== How do I assign SIDs and STARs to aircraft? ===
 
=== How do I assign SIDs and STARs to aircraft? ===
Line 135: Line 134:     
Besides, you can create aliases with the local notepad for a quick and integrated way of sending them through text chat, which will be saved when you close ATC-pie. For example, use the following format, one runway per line: <code>ils05=111.11 MHz</code>. See [[ATC-pie_user_guide#Text chat|custom text aliases]] for more.
 
Besides, you can create aliases with the local notepad for a quick and integrated way of sending them through text chat, which will be saved when you close ATC-pie. For example, use the following format, one runway per line: <code>ils05=111.11 MHz</code>. See [[ATC-pie_user_guide#Text chat|custom text aliases]] for more.
 +
 +
=== The data is outdated. How can I upgrade navpoint names or frequencies/taxiways/etc. for my airport? ===
 +
 +
For '''navigation aids and fixes''', ATC-pie normally includes the latest X-plane data cycle. If not, please report! In any case you may override it with your own as explained in <code>resources/nav/Notice</code>. Do avoid editing the packaged X-plane sources directly.
 +
 +
For '''airport data''', the included source is the last world-wide <code>apt.dat</code> compiled before it became too large to maintain as one huge file. We keep it there because it allows to run ATC-pie anywhere in the world without requiring external data, but its contents will grow out of date with time. For better results, you should download maintained versions of airport specifications from the [http://gateway.x-plane.com/airports/page X-plane airport gateway], directly accessible from the ''System'' menu. Extract the <code>.dat</code> file from the download, name it after the airport's code (keeping the extension, e.g. <code>KJFK.dat</code>), and place it in <code>resources/apt</code>. Alternatively, for a quick manual touch-up of the included data, you can move and edit extracted files as explained in <code>resources/apt.extract/Notice</code>.
    
=== How do I customise the GUI and colours? ===
 
=== How do I customise the GUI and colours? ===
242

edits

Navigation menu