265
edits
ATC-pie FAQ: Difference between revisions
Jump to navigation
Jump to search
r10h
Mickybadia (talk | contribs) (version update) |
Mickybadia (talk | contribs) (r10h) |
||
| Line 60: | Line 60: | ||
In FlightGear games, the strip exchange feature allows you to hand over strips to ATCs who are connected to the same server and within 180 NM from your position. The public server currently open for general multi-player use is <code>http://h2281805.stratoserver.net/FgFpServer</code>. To hand over a strip, drag it from its rack and drop it on the chosen callsign in the ATC handover list. Publicise your frequency so that ATCs around know what to tell pilots for them to contact you! | In FlightGear games, the strip exchange feature allows you to hand over strips to ATCs who are connected to the same server and within 180 NM from your position. The public server currently open for general multi-player use is <code>http://h2281805.stratoserver.net/FgFpServer</code>. To hand over a strip, drag it from its rack and drop it on the chosen callsign in the ATC handover list. Publicise your frequency so that ATCs around know what to tell pilots for them to contact you! | ||
=== What nickname should I use for | === What nickname should I use for FlightGear multi-player? === | ||
Choose any name you would like to be recognised by as playing the ATC. It will appear in a tooltip over your callsign in the ATC neighbours list of those connecting near enough to see you. In a sense, this feature is more social than technical, but makes sense as typical ATC callsigns (e.g. "VHHHtwr") remain mostly anonymous over MP. Use this field so that other players can identify you. | |||
== Where is ...? How to ...? == | == Where is ...? How to ...? == | ||
| Line 68: | Line 68: | ||
=== Can I draw SID and STAR procedures on the radar? === | === Can I draw SID and STAR procedures on the radar? === | ||
Yes, and virtually anything else, using background images | Yes, and virtually anything else, using background images. To learn about those: | ||
* see the corresponding user guide [[ATC-pie_user_guide#Background images|section]]; | * see the corresponding user guide [[ATC-pie_user_guide#Background images|section]]; | ||
* read the <code>resources/bg-img/Notice</code> file; | * read the <code>resources/bg-img/Notice</code> file; | ||
* examine the 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. Probably your best solution if you know your procedures are included. Here is how to use it: | |||
# Choose an output directory | |||
#: It is where you want the output files to be generated. You can create your own target directory, or choose the <code>output</code> directory of ATC-pie but mind that it is probably not empty (NB: the <code>cleanUp.sh</code> script will clean it nicely). It is ''not'' recommended to choose <code>resources/bg-img</code> directly. | |||
# Run the script: <code>sectorExtract.py sector_file centre:radius output_dir</code> where ''centre'' (Earth coordinates) and ''radius'' (range in nautical miles) specify the wanted coverage of the input sector file, centred on a point. | |||
#: 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 have many). | |||
# Import the results: | |||
#* move the drawing files under <code>resources/bg-img</code> and adjust the paths in <code>extract.lst</code> if you create subdirectories; | |||
#* rename the latter to <code>resources/bg-img/ICAO.lst</code> replacing ''ICAO'' by the location code where to draw the imported files. | |||
# Post-editing | |||
#: Each drawing block (point list under a colour) is labelled automatically with something that describes it best, and contains the line number it was sourced from in the sector file. ATC-pie does its best to understand the objects that are in the sector and to group things together depending on their type. But not everything can be guessed automatically, so you get a lot a files and useless things. This last step is now where you must merge, split, delete objects, rename points, change colours, etc. to your liking. | |||
=== How do I assign SIDs and STARs to aircraft? === | === How do I assign SIDs and STARs to aircraft? === | ||
| Line 89: | Line 103: | ||
=== How do I customise the GUI and colours? === | === How do I customise the GUI and colours? === | ||
To change the '''radar colours''', edit the <code>settings/colours.ini</code> file. Each line holds the paint colour for the corresponding object type in a typical <code>#RRGGBB</code> (red-green-blue) format. | To change the '''radar or strip colours''', edit the <code>settings/colours.ini</code> file. Each line holds the paint colour for the corresponding object type in a typical <code>#RRGGBB</code> (red-green-blue) format. | ||
Besides, ATC-pie is a Qt application and therefore allows you to customise all '''pieces of the GUI''' with ''stylesheets''. To change the general GUI looks, you may (either or both): | Besides, ATC-pie is a Qt application and therefore allows you to customise all '''pieces of the GUI''' with ''stylesheets''. To change the general GUI looks, you may (either or both): | ||