ATC-pie FAQ: Difference between revisions

=== Why am I not seeing this aircraft on my radar? ===

 

If you have chosen the '''stand-alone''' FGCom variant, take the steps below in order:

#: 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.

#: 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.

#: Start an ''FGCom configuration test'' from the ''System'' menu.

=== Recording ATIS with stand-alone FGCom: no beep is heard after pressing "record". ===

Do you have a ground elevation map for the location? Quoting from <code>CONFIG/elev/Notice</code>: "''When no elevation map is found for an airport, the field elevation value is used everywhere on the ground. This should be OK for a rough approximation on flat terrain, but ground traffic will not follow any slopes, thus may appear as floating above the ground, or dipping into it.''"

 

Read the full notice for instructions on how to build your elevation map. Once you have one or decide that your field is flat enough, the next focus is on the FlightGear aircraft models. Each model has its own coordinate system chosen at developer's discretion. ATC-pie must be given the height difference between each model's origin and the aircraft touch-down point (gear wheels) to position aircraft more accurately. You can do this on a per-model basis with ":height" specifications in <code>CONFIG/acft/icao2fgfs</code>. Read the associated <code>Notice</code> file for more information.

A last possible altitude adjustment is available from the location options: "Altitude adjustment for FlightGear views". It applies the given offset to all traffic rendered by the views.

To change the '''radar or strip drawing colours''', edit the <code>CONFIG/colours.conf</code> file. Each line specifies the paint colour for an object type, in a typical hex <code>RRGGBB</code> (red-green-blue) format or as an SVG colour keyword name like "white". To customise the '''main session window''', place a ''Qt stylesheet'' named <code>main-stylesheet.qss</code> in the <code>CONFIG</code> directory. ATC-pie will apply it to every session window. While you are working on your look and feel, use the reload feature from the "System" menu to avoid restarting after every change ({{key press|Shift|Alt|F12}}).