265
edits
ATC-pie FAQ: Difference between revisions
Jump to navigation
Jump to search
v1.8.7
Mickybadia (talk | contribs) (v1.8.6) |
Mickybadia (talk | contribs) (v1.8.7) |
||
| Line 12: | Line 12: | ||
* The aircraft is out of radar range, either too far out or under the radar floor. Check the horizontal range and floor settings ("SFC" will pick up all signals down to the ground). Primary and secondary radars share the same range. | * The aircraft is out of radar range, either too far out or under the radar floor. Check the horizontal range and floor settings ("SFC" will pick up all signals down to the ground). Primary and secondary radars share the same range. | ||
* Its onboard transponder is turned off (and primary radar is off); see [https://www.youtube.com/watch?v=kpPzRiwzx9Q&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb&index=1 ATC-pie video tutorial 1]. You should tell the pilot to switch it on. Otherwise if you accept cheating, you can activate the "radar cheat mode" which will simulate a mode S transponder for all aircraft in horizontal range; see [https://www.youtube.com/watch?v=lSyH88HR-4w&index=3&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb tutorial 3]. | * Its onboard transponder is turned off (and primary radar is off); see [https://www.youtube.com/watch?v=kpPzRiwzx9Q&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb&index=1 ATC-pie video tutorial 1]. You should tell the pilot to switch it on. Otherwise if you accept cheating, you can activate the "radar cheat mode" which will simulate a mode S transponder for all aircraft in horizontal range; see [https://www.youtube.com/watch?v=lSyH88HR-4w&index=3&list=PL1EQKKHhDVJvvWpcX_BqeOIsmeW2A_8Yb tutorial 3]. | ||
=== The aircraft vectoring tool does not come up when I click and drag out of radar contacts. === | === The aircraft vectoring tool does not come up when I click and drag out of radar contacts. === | ||
Your radar contact is not linked. Link it to a strip to enable the | Your radar contact is not linked. Link it to a strip to enable registering the mouse-issued vectors. Radar and strip displays will then be informed according to the current options, e.g. altitude reaching point, unfollowed vector warnings, etc. | ||
=== FGCom is not working. === | === FGCom is not working. === | ||
First, there are two variants | First, note that there are two variants of FGCom: the standard FGCom-mumble plug-in available in FlightGear and FSD sessions, and the legacy (deprecated) alternate available in FlightGear sessions only. They are ''not'' interoperable: users can only hear and interact with others using the same variant and server. | ||
'''FGCom-mumble''' is a plug-in that must be run with an external ''Mumble'' client (minimum version 1.4.0 to support plugins) connected to a chosen server. See the project [https://github.com/hbeni/fgcom-mumble/releases release] and wiki pages to download and install it. The control port in ATC-pie must be set to the one FGCom-mumble is listening on. To troubleshoot: | |||
* | * open a single ATC-pie instance; | ||
* check that your sound is on, your volume loud and your system picking up a signal from your microphone; | * check that your sound is on, your volume loud and your system picking up a signal from your microphone; | ||
* start an FGCom configuration test from the system tools menu; | * start an FGCom-mumble configuration test from the system tools menu; | ||
* speak in the microphone while the echo test is running | * speak in the microphone while the echo test is running. | ||
For the '''standalone''' variant ( | For the FlightGear '''standalone''' variant (selectable in the ''system settings''), the FGCom command in the system settings should be a valid command or path to an FGCom executable file. If you have FlightGear installed on your machine, you can point to the FGCom executable already available with it. On Linux, the default "fgcom" command usually does the job. Otherwise, get one from ATC-pie's [https://sourceforge.net/projects/atc-pie/files/fgcom-standalone/ SourceForge file list]. Try the entry from a terminal in the ATC-pie directory to manually check that it runs correctly, and try the echo test available from the settings box. Other things you might check if you really do not want to switch to FGCom-mumble: | ||
* server status: check for responses from the chosen server, e.g. with <code>ping</code>; | * server status: check for responses from the chosen server, e.g. with <code>ping</code>; | ||
* subprocess error: after turning a first radio on, check the FGCom error logs in the <code>OUTPUT</code> directory; | * subprocess error: after turning a first radio on, check the FGCom error logs in the <code>OUTPUT</code> directory; | ||
* port mess-up: make sure you choose an | * port mess-up: make sure you choose an unused port number for each created radio at run time. | ||
=== Tower view is not starting. === | === Tower view is not starting. === | ||
| Line 84: | Line 79: | ||
* the time hint value (see below) does not exceed 30 minutes. | * the time hint value (see below) does not exceed 30 minutes. | ||
The | The hint value for a strip is an estimated time difference between the linked aircraft touchdown and that of the traffic ahead, assuming: | ||
* both present ground speeds; | * both present ground speeds; | ||
* for the aircraft | * for the leading aircraft, a straight path to destination; | ||
* for the | * for the tailing aircraft, a path straight to the leading one first, then straight to destination. | ||
Caution | Caution, some judgement is required depending on the aircraft positions, because the actual paths to expect can vary from those above. For example, the interpretation of the hint should be different whether both aircraft are aligned with the runway or coming from opposite directions. But with some practice, the rate of the changes still help to optimise spacing when the displayed values don't. | ||
=== What do the various markings along the approach centre line mean? === | === What do the various markings along the approach centre line mean? === | ||