265
edits
ATC-pie: Difference between revisions
Added tip on customising radar colour
Mickybadia (talk | contribs) (Major change for new program release) |
Mickybadia (talk | contribs) (Added tip on customising radar colour) |
||
| Line 7: | Line 7: | ||
| alt = ATC-pie at the KSFO mess | | alt = ATC-pie at the KSFO mess | ||
| developedby = Michael Filhol | | developedby = Michael Filhol | ||
| initialrelease = | | initialrelease = February 1, 2015 | ||
| latestrelease = July 19, 2015 (r5) | | latestrelease = July 19, 2015 (r5) | ||
| writtenin = Python3 | | writtenin = Python3 | ||
| Line 140: | Line 140: | ||
== User guide == | == User guide == | ||
This section helps one download and run ATC-pie, and lists a few tips on some of its features. Other sources to learn the program are: | This section helps one download and run ATC-pie, and lists a few tips on some of its features. Other sources to learn to use the program are: | ||
* the | * the '''online video tutorial''' on ''YouTube'' (follow/bookmark the [https://www.youtube.com/playlist?list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb link to the full playlist]); | ||
* the in-app '''quick reference''' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions, etc.). | |||
Anyone motivated to write a full user guide is obviously welcome to contact the developer. | Anyone motivated to write a full user guide is obviously welcome to contact the developer. | ||
| Line 169: | Line 169: | ||
Additional command-line options are available: | Additional command-line options are available: | ||
* --'''mp-callsign'''=''callsign'' to set a network callsign directly, modifiable on MP connect (default: ICAOobs) | * --'''mp-callsign'''=''callsign'' to set a network callsign directly, modifiable on MP connect (default: ICAOobs) | ||
: FGMS callsigns for ATCs typically start with the ICAO code of the controlled airport or sector, and end with a hint on the provided service: twr, gnd... When choosing your callsign on MP connect, make sure it is unique, and note that FGMS restricts callsign length to 7 characters. :-( | |||
* --'''fgcom-server'''=''server-address'' to change the server used by internal FGCom radio boxes (default: fgcom.flightgear.org) | * --'''fgcom-server'''=''server-address'' to change the server used by internal FGCom radio boxes (default: fgcom.flightgear.org) | ||
* --'''fgcom-ports'''=''port-spec'' to specify the local ports FGCom should use for internal FGCom radio boxes | * --'''fgcom-ports'''=''port-spec'' to specify the local ports FGCom should use for internal FGCom radio boxes | ||
: Specify a comma-separated port number list. The first one becomes reserved for echo test and ATIS recording while every other port will allow for an additional radio box in the game. Alternatively, enter a string of the form ''reserved''+''nboxes'' as a shortcut for a contiguous range of ports (default: 16665+4, i.e. 16665 for the reserved port, plus 16666 through 16669 for up to 4 radio boxes). | |||
If running ATC-pie for the first time and intending to use the radio, check the FGCom version setting (''System'' menu). Try an echo test and read the <code>resources/fgcom/Notice</code> file. | If running ATC-pie for the first time and intending to use the radio, check the FGCom version setting (''System'' menu). Try an echo test and read the <code>resources/fgcom/Notice</code> file. | ||
| Line 185: | Line 187: | ||
:<code>convert -transparent white input-file.png output-file.png</code> | :<code>convert -transparent white input-file.png output-file.png</code> | ||
Use the | Use the image positioning helper tool in the ''System'' menu if you want to adjust image corners visually rather than programmatically. All visible pixmap drawings will be moved simultaneously, so you can work with several at a time if you need to. On dialog box close, a file is generated in the <code>output</code> folder for you to open and copy/edit, or use as a direct substitution. | ||
==== Multi-player strip exchange (handovers) and OpenRadar interoperability ==== | ==== Multi-player strip exchange (handovers) and OpenRadar interoperability ==== | ||
| Line 297: | Line 299: | ||
* global settings: saved and restored regardless of airport, e.g. preset text chat messages. | * global settings: saved and restored regardless of airport, e.g. preset text chat messages. | ||
''' | You can '''customise the radar colours''' by editing the colour codes in the <code>settings/colours.ini</code> file generated on first run. | ||
'''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exceptions perhaps are the navigator and handover list tooltips, for easier human identification on the scope. All directions are geodesic. | '''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exceptions perhaps are the navigator and handover list tooltips, for easier human identification on the scope. All directions are geodesic. | ||