ATC-pie FAQ: Difference between revisions

Jump to navigation Jump to search

ATC-pie FAQ (view source)

Revision as of 15:39, 1 September 2020

818 bytes added ,  1 September 2020
v1.7.1
(v1.7.0)
(v1.7.1)
Line 18: Line 18:
This happens with pre-2017.2 clients if you are using the latest protocol to encode properties. Tick the FGMS system option to "use the legacy protocol" for property encoding. Everybody should be able to read you, but it will come at the expense of network throughput. Tell those pilots to upgrade their client.
This happens with pre-2017.2 clients if you are using the latest protocol to encode properties. Tick the FGMS system option to "use the legacy protocol" for property encoding. Everybody should be able to read you, but it will come at the expense of network throughput. Tell those pilots to upgrade their client.


=== FGCom radio is not working. ===
=== FGCom is not working. ===
If you are using external clients, i.e. FGCom instances running outside of ATC-pie, you must troubleshoot them there. This section assumes you are trying with '''internal''' radio boxes.
First, verify that the FGCom variant selected in the ''system settings'' is the one you want to use. Check that your sound is on, your volume loud and your microphone working (system sound monitor picking up a signal). Close all open sessions and open a single ATC-pie instance.


First, try an echo test:
If you have chosen the '''stand-alone''' FGCom variant, take the steps below in order:
* check that your sound is on, your volume loud and your microphone working (e.g. system sound monitor picking up a signal);
# Echo test
* close all open ATC-pie sessions and open a single instance;
#: Start an ''FGCom configuration test'' from the ''System'' menu. While the test is running, speak in the microphone and check if you can hear yourself back. If so, you may skip directly to step 4.
* start the echo test from the ''System'' menu.
# Path to executable
#: Verify the FGCom command entered in the system settings. It should contain an executable system command or a relative or absolute 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, [https://sourceforge.net/projects/atc-pie/files/fgcom-standalone/ download an FGCom stand-alone program] from ATC-pie's SourceForge file list. In any case, try the entry from a terminal in the ATC-pie directory to manually check that it runs correctly.
# FGCom server status
#: The server may temporarily be down, unfortunately even for up to a few days. Check for responses from the server, e.g. with <code>ping fgcom.flightgear.org</code> (adjusting the server name to match the one entered in the settings). FGCom will not work without a responding server.
# FGCom subprocess error
#: After turning your radio on, check for errors in the logged FGCom output files in the <code>OUTPUT</code> directory.
# Port mess-up in your session?
#: When creating a new radio box at run time, make sure you choose an available port number for each. Caution when running multiple ATC-pie instances: do not use a port more than once across the system at the same time.
 
If you have chosen the '''FGCom-Mumble plug-in''':
# Plug-in status
#: Check that your Mumble client is connected and properly running the FGCom plug-in.
# Port setting
#: Check that the control port in ATC-pie is set to the one FGCom-Mumble is listening on.
# Echo test
#: Start an ''FGCom configuration test'' from the ''System'' menu.


If you hear yourself when you speak, you may skip directly to item 3 below. Otherwise start with 1.
Note that the two variants are ''not'' interoperable. Users will only be able to hear and interact with others using the same variant (and server) as their own.
# Bad FGCom version/path setting
#: Verify the FGCom command entered in the system settings. It should contain an executable system command or a relative or absolute path to an FGCom executable file (also see the [[ATC-pie installation guide]]). Try the entry from a terminal in the ATC-pie directory to check that FGCom runs correctly.
# FGCom server down
#: This can happen, unfortunately even for up to a few days. Check for responses from the server, e.g. with <code>ping fgcom.flightgear.org</code> (adjusting the server name to match the one entered in the settings).
# FGCom subprocess error
#: If the server is up (responding to ping), check for errors in the logged FGCom output files in the <code>OUTPUT</code> directory.
# Port mess-up on your side
#: If you are running multiple instances of ATC-pie, make sure you have no more than one radio box for every port number used on the system. To check what port a radio box is using, see its "on/off" button tooltip. When creating a new radio box, only choose available ports not reserved by your operating system. In general, ports from 16661 and counting up work fine on all platforms.


=== I cannot record an ATIS with FGCom. ===
=== Recording ATIS with stand-alone FGCom: no beep is heard after pressing "record". ===
Assuming FGCom is working otherwise (confirm this with an echo test before reading on), but no beep is heard after pressing "record"...
Assuming FGCom is working otherwise (confirm this with an echo test before reading on)...


Due to FGCom design, you may only record an ATIS if the requested frequency is enlisted as recordable on the distant server's "phone book" for the base airport (or the nearest one in CTR mode). The one for <code>fgcom.flightgear.org</code> was compiled a while ago, based on the latest <code>apt.dat</code> at the time. It filtered the frequencies through the two following conditions:
Due to FGCom design, you may only record an ATIS if the requested frequency is enlisted as recordable on the distant server's "phone book" for the base airport (or the nearest one in CTR mode). The one for <code>fgcom.flightgear.org</code> was compiled a while ago, based on the latest <code>apt.dat</code> at the time. It filtered the frequencies through the two following conditions:
Line 46: Line 53:


NB: The frequencies in the ATIS drop-down list of ATC-pie are matched against the condition (1), but not against the somewhat restrictive condition (2).
NB: The frequencies in the ATIS drop-down list of ATC-pie are matched against the condition (1), but not against the somewhat restrictive condition (2).
If frequencies are too much out of sync, the solution will be to switch to the FGCom-Mumble plug-in variant.


=== Tower view is not starting. ===
=== Tower view is not starting. ===
Mickybadia
265

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/127210"

Navigation menu