265
edits
ATC-pie user guide: Difference between revisions
r7b adjustments
Mickybadia (talk | contribs) (New release: r7 + added screenshots) |
Mickybadia (talk | contribs) (r7b adjustments) |
||
| Line 31: | Line 31: | ||
{| class="wikitable" | {| class="wikitable" | ||
! Option || Effect and argument specification || Default | ! Option || Effect and argument specification || Default | ||
|- | |||
| --map-range=''range'' || Define the distance in NM from the radar centre up to which the map will be drawn and navpoints listed in the navigator (accepted values are 20..500). This is a different setting to the radar range configurable in the game settings. || 100 | |||
|- | |- | ||
| --tower-view-external=''host'' || Avoid running an internal FlightGear process for tower viewing, and specify a host on which a viewer is running. This may still be "localhost". || (none, start internal process) | | --tower-view-external=''host'' || Avoid running an internal FlightGear process for tower viewing, and specify a host on which a viewer is running. This may still be "localhost". || (none, start internal process) | ||
| Line 199: | Line 201: | ||
=== Interface and information display === | === Interface and information display === | ||
The '''''Options'' menu''' is divided in two sections. The | The '''''Options'' menu''' is divided in two sections. The item above the separator contains unsaved session options, which go back to their default setting on restart. Under the separator are saved settings, which come in two flavours: | ||
* airport-specific ( | * airport-specific (under a unique submenu): saved and restored when started at the same airport again, e.g. runway ILS capabilities; | ||
* global settings: saved and restored regardless of airports, e.g. preset text chat messages. | * global settings: saved and restored regardless of airports, e.g. preset text chat messages. | ||
| Line 254: | Line 256: | ||
You only see an aircraft on your screen if your radar picks up a transponder signal from it. The two following cases will therefore prevent you from seeing a connected aircraft: | You only see an aircraft on your screen if your radar picks up a transponder signal from it. The two following cases will therefore prevent you from seeing a connected aircraft: | ||
# Its onboard transponder is turned off, i.e. not responding to your radar ping, and you should tell the pilot to switch it on. See the [https://www.youtube.com/watch?v=kpPzRiwzx9Q&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb&index=1 ATC-pie video tutorial 1]. If the aircraft model does not support the transponder feature, it will be simulated by ATC-pie according to the fallback mode you have selected in the settings dialog; any non-zero mode will | # Its onboard transponder is turned off, i.e. not responding to your radar ping, and you should tell the pilot to switch it on. See the [https://www.youtube.com/watch?v=kpPzRiwzx9Q&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb&index=1 ATC-pie video tutorial 1]. If the aircraft model does not support the transponder feature, it will be simulated by ATC-pie according to the fallback mode you have selected in the settings dialog; any non-zero mode will make the aircraft visible to you. Alternatively, you can switch on the primary radar system if you want to see aircraft's position, or activate the "radar cheat mode" if you want to go the radical way ([https://www.youtube.com/watch?v=lSyH88HR-4w&index=3&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb tutorial 3]). | ||
# The aircraft is under the radar floor | # The aircraft is out of range, under the radar floor (minimum signal pick-up height) or too far out. Open the ''General settings'' dialog, check the NM range setting and set the floor to "SFC" to pick up all signals. | ||
'''Q: What is the strip exchange server? Which one to use?''' | '''Q: What is the strip exchange server? Which one to use?''' | ||