265
edits
ATC-pie: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Mickybadia (talk | contribs) No edit summary |
Mickybadia (talk | contribs) No edit summary |
||
| Line 33: | Line 33: | ||
* Notification system combining sounds and a time-tagged list | * Notification system combining sounds and a time-tagged list | ||
* Network text chat system | * Network text chat system | ||
* Strip route management | |||
* Manage ignored contacts | * Manage ignored contacts | ||
* Personal notepads (general and airport-specific) saved across sessions | * Personal notepads (general and airport-specific) saved across sessions | ||
| Line 110: | Line 111: | ||
Downloading the '''tarball''' requires nothing but the standard tar+gzip combo: | Downloading the '''tarball''' requires nothing but the standard tar+gzip combo: | ||
# | # download the [https://gitorious.org/atc-pie/atc-pie/archive/master.tar.gz compressed archive]; | ||
# extract the files in the directory of your choice. | # extract the files in the directory of your choice. | ||
| Line 126: | Line 127: | ||
Here are a few unsorted tips to help you navigate the program... | Here are a few unsorted tips to help you navigate the program... | ||
* '''Callsigns''' typically start with the ICAO code of a controlled airport, and end with a hint on the provided service: twr, gnd... With no callsign given, you will appear as "ICAOobs" on network connect. Note that FGMS restricts callsigns lengths to 7 characters. :-( | * '''Callsigns''' typically start with the ICAO code of a controlled airport, and end with a hint on the provided service: twr, gnd... With no callsign given, you will appear as "ICAOobs" on network connect. Note that FGMS restricts callsigns lengths to 7 characters. :-( | ||
* For more efficient | * For more efficient text chat, a growing list of '''text aliases''' exist (<code>$wind</code>, <code>$qnh</code>, <code>$icao</code>...), which you can use in instant and preset chat messages. They expand to the current value on message send. | ||
* '''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exception perhaps are the navigator tooltips, for easier identification on the scope. | * '''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exception perhaps are the navigator tooltips, for easier identification on the scope. | ||
* The '''transition level''' is by definition the lowest flight level that is still above the transition altitude. This does not mean the lowest assignable FL, which may take more vertical separation. | * The '''transition level''' is by definition the lowest flight level that is still above the transition altitude. This does not mean the lowest assignable FL, which may take more vertical separation. | ||
| Line 133: | Line 133: | ||
* The '''FGCom version setting''' is the name of a subdirectory in <code>resources/fgcom</code>. See <code>Notice</code> file there. | * The '''FGCom version setting''' is the name of a subdirectory in <code>resources/fgcom</code>. See <code>Notice</code> file there. | ||
* "OK" near the "route" field on the strip detail sheet means that the route could be parsed correctly; otherwise "!!" is displayed. This does not matter, only the info boxes will be showing destination (or nothing if unknown) instead of next waypoint. | * "OK" near the "route" field on the strip detail sheet means that the route could be parsed correctly; otherwise "!!" is displayed. This does not matter, only the info boxes will be showing destination (or nothing if unknown) instead of next waypoint. | ||
Say you are TWR coordinating with GND at an airport and you want to '''monitor both radio frequencies''' while you are only in charge of one. You can set this up by starting your own radio box on TWR frequency, and turn on a second one to monitor GND, setting the volume to "soft" on the latter so that you can always tell if a message is for you to answer or not. | |||
Resolving '''strip–FPL conflicts''': | Resolving '''strip–FPL conflicts''': | ||
| Line 143: | Line 145: | ||
*# finally push the strip details to the flight plan. | *# finally push the strip details to the flight plan. | ||
Resolving '''FPL local–online conflicts''': | |||
* to update the online version with your local modifications, double-click the flight plan and tick the "publish" box before saving (if still decorated red, there was a network problem or the change was rejected by the server); | |||
* to discard all local modifications of an online FPL, remove the FPL from the list and check for new flight plans again (the deleted entry should be retrieved with online state). | |||
=== Quick reference === | === Quick reference === | ||