ATC-pie FAQ: Difference between revisions

Jump to navigation Jump to search
v1.8.0
(v1.7.1)
(v1.8.0)
Line 44: Line 44:


=== Recording ATIS with stand-alone FGCom: no beep is heard after pressing "record". ===
=== 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)...
Assuming FGCom standalone is working (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 the design of this legacy FGCom variant, you may only record an ATIS if the requested frequency is enlisted as recordable on the distant server's "phone book" for the airport. 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:
# it is of the "recorded" type (row code 50);
# it is of the "recorded" type (row code 50);
# its name contains the uppercase string "ATIS".
# its name contains the uppercase string "ATIS".


Unless you have updated or edited the frequency data yourself, check against the airport <code>.dat</code> file sourced on your side, as it should still be similar. One of the two conditions is probably not met, or the frequency missing all together.
If you are relying on the old data provided by ATC-pie, in other words you have not downloaded new data or edited the frequencies yourself, check against the <code>.dat</code> file extracted in the <code>OUTPUT</code> directory on your side, as it should still be similar to the one on the server's side. One of the two conditions is probably not met, or the frequency missing. 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).
In any case, consider switching to the newer FGCom-Mumble plug-in variant. It simulates radio waves, frequencies and ranges, which avoids the phone book problem all together.
 
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. ===
Line 95: Line 93:
* it is reserved for a different aircraft: the boxed strip is linked to a contact that is not the entering aircraft, or the aircraft is linked to a strip different to the one boxed.
* it is reserved for a different aircraft: the boxed strip is linked to a contact that is not the entering aircraft, or the aircraft is linked to a strip different to the one boxed.


Turning the runway occupation monitor off will deactivate all radar warnings regarding runways. If you are interested in the strip boxing and visual runway highlighting system but bothered by the alarm sound, you can mute the sound notification by unticking it in the notification dock pull-down menu.
Turning the runway occupation monitor off will deactivate all radar warnings regarding runways. If you are interested in the strip boxing and visual runway highlighting system but bothered by the alarm sound, you can mute the sound notification by unticking it in the general settings.


== Where is ...? Can I ...? How to ...? ==
== Where is ...? Can I ...? How to ...? ==
265

edits

Navigation menu