FlightGear wiki - User contributions [en]

De/FGCom-mumble

2025-12-04T08:44:26Z

Hbeni: /* Bekannte Inkompatibilitäten */

'''FGCom-mumble''' simuliert Funkkommunikation basierend auf der freien VoIP software [https://www.mumble.info/ Mumble]. Es integriert sich vollstädnig mit den Funkgeräten deines Flugzeuges in FlightGear und erlaubt dir, mit anderen Piloten und Fluglotsen auf realistische Weise zu kommunizieren. Dafür simuliert es ein lückenloses Radiowellenspektrum.

FGCom-mumble ist eine Alternative zum altbekannten [[FGCom]] sowie [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble nutzt den Pluginmechanismus, der in Mumble 1.4.0 verfügbar wurde und benötigt lediglich ein vorkompiliertes Plugin, das von einem ganz normalen Mumble-Programm geladen wird. Das aktuellste Release kannst du hier herunterladen: https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Server ==

* Der FGCom-mumble test server ist <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
* Die Statusseite für diese Instanz, die alle verbundenen Clients anzeigt, ist hier: https://fgcom-dev.hallinger.org/
* Der mumble-testserver benutzt ein autoerneuerndes SSL-Zertifikat von Lets Encrypt.

== Hauptziele des Projektes ==
* Bereitstellen von Kommunikation, die sowohl örtlich als auch kanaltechnisch getrennt ist
* Realistische Funkkommunikation
* Einfachheit in der Installation und Benutzung
* Unterstützung für beliebige Frequenzen
* ATIS Aufnahme und Wiedergabe
* Zivile Radiostationen sollen unterstützt werden
* Festnetz/Intercom Unterstützung
* RDF-Signale für Clients
* Einfach auf einem Server zu installieren und zu betreieben
* Unabhängigkeit von Simulatoren wie z.B. Flightgear
* Fähigkeit, in FlightGear integriert zu werden, mit der Option, weitere Clients und Applikationen zu unterstützen (ATC, aber auch andere Flugsimulatoren)
* Modularer Aufbau, damit einzelne Komponenten unterschiedlich implementiert werden können und einfache Erweiterbarkeit besteht
* Gute und vollständige Dokumentation

== Installation and Einrichtung ==
Die aktuelle Version kann hier heruntergeladen werden: [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] bietet auch eine Debug-Variante an).

Die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#installation--einrichtung-des-mumble-plugins README] bietet detaillierte Angaben zur Installation.

Jemand hat sogar ein Video (engl.) von der Installation gemacht! :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk

Zusammengefasst:
* Du brauchst ein installiertes und eingerichtetes Mumble >= 1.4, und dann lade darin das Plugin (unter mumble Einstellungen/plugins)
* Auf dem Mumbleserver (Version >= 1.4.0) trittst du einem Channel bei, dessen Name mit `fgcom-mumble` beginnt
* Im FlightGear-Launcher fügst du im Addon-Tab den `fgfs-addon` Ordner der FGCom-Mumble Veröffentlichung hinzu
* Starte FlightGear und benutze deine Funkgeräte (du funkst mit den ganz normalen FGCom-Tastenkombinationen; siehe unten)

== Benutzung ==
FlightGear's FGCom-mumble Protokoll benutzt die normalen FGCom-Tastenkombinationen:
* Um auf COM1 zu funken, drückst du {{Key press|Space}}. Solange du überträgst, kannst du keine anderen Piloten durch das verwendete Funkgerät hören (diese sind Halbduplexgeräte).
* COM2 sendet mit {{Key press|Shift|Space}}.
* Seit FGCom-mumble 1.2.0:
** Mit COM3 funkst du über {{Key press|Alt|Space}} (früher musstest du ein eigenes Keybind definieren),
** Intercom sendet in full-duplex mit {{Key press|Ctrl|Space}}

Jedes Funkgerät kann außerdem über die COMBar benutzt werden (öffnen über ''Menu/Multiplayer/FGCom-mumble'').

Um FGCom-mumble ohne FlightGear zu probieren, kannst du auch die im Release mitgelieferte RadioGUI starten.

=== Deine Installation testen ===
Als erstes solltest du sicherstellen, dass mumble an Sich gut funktioniert und du gut zu verstehen bist sowie andere gut verstehst.
Dazu deaktivierst du am Besten das Plugin oder du sprichst mit anderen auf einem Channel, der nicht mit `fgcom-mumble`beginnt.

Das Plugin verändert Mumbles eingehende Audiopakete. Es fügt statisches Rauschen hinzu, das von der simulierten Funksignalstärke abhängt oder hebt den stream sogar auf, wenn der Funksender außerhalb der Reichweite liegt. Ausgehende Audiopakete werden nicht verändert.

Falls der Server es unterstützt, kannst du auch einen traditionellen Echo-Test machen (dazu muss am Server ein `fgcom-recorder-bot` laufen). Funke auf der Frequenz `910.00` MHz und der Recorderbot wird mit der Aufzeichnung beginnen (er schreibt das in den mumble-chat) und nach Abschluss einen bot an deiner Position erzeugen, der das aufgenommene auf der Frequenz wiedergibt. So kannst du dich selbst hören, wie andere dich hören würden.

=== Fehlerbehebung ===

Schau bitte in die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#fehlerbehebung README] des Projekts. Diese hat detaillierte Informationen hierzu.

Solange es nichts grundlegendes mit der Installation zu tun hat, hilft oft auch einfach ein Neustart von Mumble (das Plugin initialisiert sich selbständig frisch).

=== Kompatibilität ===
FGCom-mumble unterstützt grundsätzlich das alte FGCom-UDP-Protokoll und sollte somit kompatibel mit allen clients sein, die dieses verwenden (z.B. ältere ATCpie oder OpenRadar Versionen). Allerdings gibt es auch ein paar Erweiterungen, die mit dem alten Protokoll nicht zur Verfügung stehen.

* FlightGear wird durch ein [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon] unterstützt. Dieses erwartet die Standard-Funkgerätimplementierung (und funktioniert getestet zumindest mit der C172p und der C182S).
*[[ATC-pie]] hat eine integrierte Unterstützung (prüfe, ob "FGCom-mumble" anstelle von nur "FGCom" in den Einstellungen aktiviert ist).
*[[OpenRadar]] Unterstützt im Moment nur COM1 ([https://sourceforge.net/p/openradar/tickets/5/ Ticket dazu ist offen]). Für COM2 und weitere musst du entweder separate Mumble-Instanzen öffnen oder FGCom-mumble's RadioGUI zum Funken benutzen.
:Es gibt eine gepatchte Version von OpenRadar mit integriertem FGCom-mumble sowie 8.33 Channelmodus; verfügbar hier: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

==== Bekannte Inkompatibilitäten ====
* Das alte FGCom aktiviert sich selbständig, wenn du mit dem Mehrspielernetzwerk verbunden bist und dann die "FGCom"-Einstellungen (anstelle des "FGCm-Mumble"-Eintrags) aus dem Mehrspielermenü aufrufst. Wenn du mit aktiviertem alten FGCom PTT aktivierst, kann FlightGear abstürzen (aktuelle FGcom-mumble addons haben einen Workaround dafür).
* Das FlightGear UFO belegt {{Key press|Space}} selbst, sodass du nicht Funken kannst. Als workaround kannst du die COMBar benutzen, die mit dem FGFS Addon mitkommt.
* FGFS version <= 2020.3 ist nicht mit FGCom-mumble addon version >= 1.3.0 kompatibel. Es wird 1.2.0 benötigt, oder ein FGFS upgrade.
* FGExtend wechselt dich in mumble in einen anderen Channel, wenn du die Frequenz änderst. Wenn du FGCom-mumble benutzen möchtest, musst du FGExtend ausschalten.
* Mumble muss als nativer client laufen. Snap packs / flatpak Installationen können das Plugin nicht installieren.

== RadioGUI ==
Die RadioGUI ist eine kleine Java8 Applikation, die einen FGCom-mumble client implementiert und Funkgeräte bereitstellt. Sie sendet die notwendigen UDP Nachrichten an das Mumble plugin.

In der GUI kannst du deinen Standort über eine Karte auswählen und dann deine Funkgeräte einstellen und testen.
Damit kannst du auch komplett mit allen Funktionen am simulierten Funknetz teilnehmen, ohne FlightGear zu starten.

== Serverseite ==
Konzeptionell benötigst du als Minimum einfach einen Standard Mumbleserver (Version 1.4.0 oder höher), auf dem ein Channel eingerichtet wird, der mit `fgcom-mumble` beginnt. Das ist bereits genug, damit das Plugin Clientseitig den Rest erledigen kann. Der komplette Channel wird als einzelnes, weltumspannendes, kontinuierliches Radiowellenspektrum behandelt.

Weitere Funktionen werden über Lua-Bots implementiert (die auch auf einer anderen Maschine laufen können):
* ATIS Aufzeichnung udn Wiedergabe
* Radioprogramm Wiedergabe (OGG Wiedergabe auf einer beliebigen Funkfrequenz), z.B. nutzbar für eigene NDBs mit Morsecode ([https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons])
* Statusseite Datensammlung

Eine Statusseite fürs WWW ist als PHP-Seite implementiert, die die notwendigen Daten über den `fgcom-status-bot` bereitgestellt bekommt.

Detaillierte Installations- und Betriebsdokumentation ist in den Veröffentlichungen enthalten, aber auch [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server-de_DE.md online] im Projekt zugänglich.

== Wie funktiooniert das alles? (technische Information) ==
Die technischen Details sind in den verschiedenen Readme-Dateien im Projekt dargelegt (zum Start empfielt sich [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Zusammengefasst treten alle Teilnehmer einem einzigen Mumble-Channel bei und laden das fgcom-mumble Plugin. Das Plugin tauscht alle notwendigen Daten zwischen den Nutzern aus (Funkgeräte, Frequenzen, Standort, etc.) und basierend auf diesen Informationen werden die eingehenden Audioströme der anderen Nutzer entweder abgespielt oder stummgeschaltet. Für mehr Realismus werden abgespielte Audioströme mit Statischem Rauschen und weiteren Effekten unterlegt.
Aufgrund der Stummschaltefunktion abhängig von der Funkreichweite besteht eine unmittelbare Separierung nach Funkkanal und Standort, was allen Nutzern erlaubt, in ein und demselben Mumblekanal zu sein.

== Weiterführender Inhalt ==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] mit weiteren Tipps/Hinweisen
*[https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md FGCom-mumble README-de_DE.md] Haupt-Readme des Projektes mit allen Details, die du schon immer wissen wolltest

=== Forum topic ===
* Der {{forum link|t=37644|title=FGCom-mumble}} Forumshtread hat Entwicklungsrelevante Informationen und dient zur allgemeinen Diskussion
* {{forum link|p=374950|title=Re: EDDF-Triangle}} und {{forum link|p=374970|title=Re: EDDF-Triangle}} - behandeln Details zu Kompatibilität und Unterschieden zwischen FGCom, FGCom-mumble und Mumble

=== FlightGear Newsletter ===
*[[FlightGear_Newsletter_June_2020]]: Erster Prototyp angekündigt
*[[FlightGear_Newsletter_July_2020]]: Lasttests erfolgreich, RDF implementiert, Live-Status Seite hinzugefügt
*[[FlightGear_Newsletter_August_2020]]: Mehr tests, neue HF/VHF/UHF modelle, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API änderungen, verteilte Installation, Konfigurationsmöglichkeit per INI-Datei, Statistiken
*[[FlightGear_Newsletter_October_2020]]: Weitere API änderungen, realistische Simulation der 8.33kHz/25kHz Kanalüberlappung, RadiGUI hinzugefügt
*[[FlightGear_Newsletter_November_2020]]: Test server angekündigt
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringt Netzwerkfunktionen
*[[FlightGear_Newsletter_April_2021]]: RDF Implementierung umgebaut, 0.12.0 angekündigt, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Bessere Unterstützung von Airliners, 0.13.0 and 0.14.0 angekündigt, Releasepaket neustrukturiert
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 angekündigt, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 angekündigt, updater bugfixes Teil II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 veröffentlicht, Mumble 1.4 wurde veröffentlicht'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[en:FGCom-mumble]]

FGCom-mumble

2025-12-04T08:43:41Z

Hbeni: /* Known incompatibilities */

'''FGCom-mumble''' simulates radio communication based on the VoIP software [https://www.mumble.info/ Mumble]. It integrates fully with the radio stack of your FlightGear plane, allowing you to communicate with other pilots and airspace controllers during your flight. It simulates a global, continuous radio frequency spectrum.

FGCom-mumble is an alternative to the already known [[FGCom]] client and [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble leverages the plugin mechanism introduced by Mumble 1.4.0 and just needs a precompiled plugin loaded by a stock Mumble client.
You can download the latest release from https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Servers ==

*The main FGCom-mumble test server is <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
*The status page for that service showing all connected clients is at: https://fgcom-dev.hallinger.org/
*The mumble test server uses a autorenewed certificate from letsencrypt.

==Project main goals==
*Provide communication with geographic and channel separation
*Provide a realistic radio simulation
*Ease of use for the end user/pilot
*Arbitrary frequency support
*ATIS recording and playback
*Radio station broadcast support
*Landline/Intercom support
*RDF detection for clients
*Ease of server side installation and operation
*Standalone nature (no dependency on FlightGear)
* Capability to be integrated into FlightGear, with the option to support third party applications (ATC, but also other flight simulators)
*Modularity, so individual component implementations can be switched and its easy to add features
*Good and complete documentation

== Installation and setup==
The latest release can be fetched from [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] also has debug versions).

The provided [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#install--setup-for-the-client README] has detailed instructions on the needed prerequisites and installation procedures.

Someone even made an install video :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk
(thanks mate, well done! however HF is actually simulated already :)

In short:
* Have a stock Mumble client >= 1.4 running, and load the plugin (mumble settings/plugins page)
* Join a channel named `fgcom-mumble` (on a >= 1.4 mumble server)
* Add the `fgfs-addon` folder of the client release as FlightGear Addon in your launcher
* Start FlightGear and use your plane's radio stack (it uses default FGCom buttons, see below)

==Usage==
FlightGear's FGCom-mumble protocol uses the default FGCom buttons:
* When you want to talk on COM1 you have to press {{Key press|Space}}. While transmitting you can not hear other pilots trough the used radio (they are half-duplex).
* You can also talk on COM2 by pressing {{Key press|Shift|Space}}.
* since FGCom-mumble 1.2.0:
** For COM3 you use {{Key press|Alt|Space}} (previously you need to define a custom keybind),
** Intercom is available in full-duplex with {{Key press|Ctrl|Space}}

Any radio can also accessed by the COMBar (open from ''Menu/Multiplayer/FGCom-mumble'').

If you want to try it out without FlightGear, you can also start the supplied RadioGUI.

=== How to test your setup?===
First, make sure Mumble is working reliably by talking to other people. Either disable the plugin, or be sure you are outside any radio channel (starting with `fgcom-mumble`).

The plugin alters Mumble's receiving audio stream. It adds static noise depending on the radio signal quality, or cancels out all audio when not in range. The outgoing audio stream is not altered in any way.

If the server supports it (in essence there is a bot-manager running and a `fgcom-recorder-bot` listening) you may do a traditional echo test by tuning `910.00` and start to talk. The recorder-bot will record that (he writes that into mumbles chat) and spawn an echo bot at your position, replaying your message (so you will hear yourself like others will hear you).

===Troubleshooting===
For troubleshooting, refer to the projects [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#troubleshooting README] as it has further suggestions.

If it's nothing setup related, an easy fix is to just restart mumble (the plugin will reinitialize itself).

===Compatibility ===
FGCom-mumble supports the legacy FGCom UDP protocol and thus should be compatible to clients supporting that. However, it also features some new UDP fields.

*FlightGear is supported through an [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon]. This assumes the default radio implementation and works with at least the C172P and the C182S.
*[[ATC-pie]] has built in support already (be sure to activate "FGCom-mumble" instead of just "FGCom" in the settings).
*[[OpenRadar]] currently supports just COM1 ([https://sourceforge.net/p/openradar/tickets/5/ ticket pending]). To use COM2 and more, you need to either start several mumble instances, or use FGCom-mumble's RadioGUI.
:There is a patched version of OpenRadar with FGCom-mumble and 8.33 channel tuning support available here: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

====Known incompatibilities====
* The legacy FGCom auto-enables itself, if you are connected to a multiplayer server and then open the "FGCom" dialog (instead of the "FGCom-mumble" one) from the multiplayer dialog. Then activating PTT can cause a FlightGear segfault (newer FGCom-mumble addon versions have a workaround).
* The UFO aircraft rebinds {{Key press|Space}} so you can't transmit on the radio. As a workaround you can use the COMBar that comes integrated with the FGFS addon.
* FGFS version <= 2020.3 is not compatible with FGCom-mumble addon versions >= 1.3.0. You need to stick to 1.2.0 or upgrade FGFS.
* FGExtend switches you out of channels upon frequency change. You need to disable FGExtend when using FGCom-mumble.
* Mumble must be a native client. Snap packs / flatpack installation will not work, as the container won't support installing the plugin.

==RadioGUI==
The FGCom-mumble RadioGUI is a small Java 8 application that can send the FGCom-mumble UDP messages to the Mumble plugin.

Inside the GUI, you can pick your location from a map and then setup and use your radio stack.
That said, the RadiGUI can be used instead (or additionally to) FGFS to participate on the simulated radio net.

==Server side==
By design, all that is needed is a standard Murmur server (version 1.4.0 or later) and a specially named channel (it has to start with `fgcom-mumble`). This is enough to let the plugin do its work. The entire channel is treated as a single, worldwide continuous radio frequency spectrum.

Additional features are implemented using server side Lua bots (which may run somewhere else):
* ATIS recording and broadcasting
* Radio program broadcasting (OGG playback on a frequency), [https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons]
* Status page data collection

A status page showing client details is available as a PHP website, that gets its data fed from the fgcom-status-bot.

Detailed installation and operation documentation is shipped with the releases, but is also [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server.md online].

==How does it work? (technical information)==
The technical details are specified and described in the various readme files of the projects source code (as a starter read the [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Basicly, all users join the same mumble channel and run the fgcom-mumble plugin. The plugin knows everything necessary from the participating users (like radios used, frequencies tuned, locations, etc) and based on that information mutes or plays incoming voice messages from the other users. Based on signal quality, static noise is mixed in for more fun and a more realistic experience.
Because the voice of other users is muted, it is a design wise out-of-the-box feature that brings frequency and location separation but allows everyone to stay in the same mumble channel.

==Related content==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] with hints etc
*[https://github.com/hbeni/fgcom-mumble/blob/master/README.md FGCom-mumble README.md] Main readme of the project bringing all the details you always wanted to know

===Forum topic===
*The {{forum link|t=37644|title=FGCom-mumble}} has development discussions and release announcements
*{{forum link|p=374950|title=Re: EDDF-Triangle}} and {{forum link|p=374970|title=Re: EDDF-Triangle}} - Compatibility and differences between FGCom, FGCom-mumble and Mumble

===FlightGear Newsletter===
*[[FlightGear_Newsletter_June_2020]]: First prototype announced
*[[FlightGear_Newsletter_July_2020]]: Load tests successful, RDF implemented, Live-Status page added
*[[FlightGear_Newsletter_August_2020]]: More testing, new HF/VHF/UHF models, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API changes, distributed deployment, configuration trough INI, statistics
*[[FlightGear_Newsletter_October_2020]]: More API changes, proper 8.33kHz/25kHz overlap, RadiGUI added
*[[FlightGear_Newsletter_November_2020]]: Test server announced
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringing networking capability
*[[FlightGear_Newsletter_April_2021]]: RDF reworked, 0.12.0 announced, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Better airliner support, announced 0.13.0 and 0.14.0, restructured release package structure
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 announced, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 announced, updater bugfixes part II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 released, Mumble 1.4 hit the light'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

== Idea to integrate into FGFS ==
{{progressbar|10|10}} {{pending}}

EDIT: Core ticket: https://gitlab.com/flightgear/flightgear/-/issues/3095

ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212

Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum).

A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible?

libmubmble is not yet API-stable (but should be working), but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics:
* From FGCom-mumbles side, we need to integrate the data structures into the core. So radios need to be registered, etc. This should not be too hard
** we probably just need to not run the UPD-Server but send the needed data directly into the decoding function of it. At a later stage, we might better integrate that part, but for a first working solution, just creatig a FCGOM-mumble UDP-Packet string in FGFS and sending it periodically (or already on-demand?) into the udp-servers decoder function should be enough - it just creates some CPU overhead which should not be too bad and will establish the needed local data structure.
** Note, that we cannot rely on the mpservers data structures (even if there is radio data), because in FGCom-mumble potential other clients are also participating (like radio-playback bots for ATIS etc!). So we really need to use mumbles plugin messages.
* Basicly the libmumble will run its own threads for networking. Upon receiving mumble audio or mumble-plugin data, callback functions would be called from the lib (https://github.com/mumble-voip/libmumble/issues/18#issuecomment-1868498537):
** Incoming audio data need to be processed by the fgcom-mumble plugin functions, and then the result handed over into fgfs audio out handling.
** Incoming plugin data needs to be fed into the fgcom-mumble internal remote data struct (just hand the data into the existing data parser).
* Pressing the already existing fgfs PTT button
** would need to send plugin data to mumble, to inform other clients. This is currently done by calling a mumble client function. It would probably be enough, if fgfs core supplied an implemention that calls the appropriate libmumble function and hands over the data.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} And what about libmubmles dependencies, like OpenSSL?
*** technically, how to include that all into the existing build system?

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[de:FGCom-mumble]]

ATC-pie

2025-11-14T09:42:23Z

Hbeni:

{{forum|83|ATC-Pie support & development}}

{{about|the software and its features|help with installation or configuration|ATC-pie installation guide|a manual on how to use it|ATC-pie user guide}}

{{Infobox Software
| title = ATC-pie
| logo = ATC-pie-logo.png
| image = ATC-pie-screenshot-towerViewing.png
| alt = Tower viewing, following a departing aircraft
| developedby = Michael Filhol
| initialrelease = February 1, 2015
| latestrelease = 1.9.1 (March 25, 2025)
| writtenin = Python
| writteninversion = 3
| os = Any
| platform = Qt5
| developmentstatus = Active
| type = ATC client
| license = GNU GPL v3
| website = http://mickybadia.free.fr/atcpie
}}

'''ATC-pie''' is a free (libre) [[air traffic control]] simulation program with strong ties to [[FlightGear]]. It features:
* solo sessions with AI traffic (incl. voice instruction recognition and pilot read-back);
* "multi-player" network sessions (FlightGear and FSD protocols supported);
* tutorial sessions for teacher supervision of an ATC student.

It is designed to support a maximum range of ATC situations, and will allow any world location for every session type above. All control positions are possible, whether airport-based (TWR, APP, GND...) or en-route (CTR). Equipment can be set up to include radar screens, data link, etc. or be limited to binoculars and a view of the airfield.

Its essential goal is realism. It simulates many tasks of real-life ATC such as:
* strip racks and sequence management;
* coordination with neighbouring controllers (phone calls, handovers...);
* radar monitoring for traffic identification and sequencing;
* vectoring and course/level conflict anticipation;
* flight plan operations;
* CPDLC...

Development is on GitLab: https://gitlab.com/atc-pie/atc-pie

== Screenshots ==

<gallery mode="packed">
ATC-pie-screenshot-sectorView.png|Sector view around Geneva
ATC-pie-screenshot-soloMode.png|Solo session with three coloured racks
ATC-pie-screenshot-backgroundPixmapDrawing.png|Background image display
ATC-pie-screenshot-airportCloseUp.png|Depiction of airport tarmac and objects
ATC-pie-screenshot-runwayIncursion.png|Runway incursion detected and highlighted in red
ATC-pie-screenshot-flightPlans.png|Flight plan editor
</gallery>

Visit the [[:Category:ATC-pie screenshots|ATC-pie screenshot category]] for more.

== Sessions and environments ==

ATC-pie features five session/connection types, all of which support both ''airport'' and ''centre'' location modes.

Session types:
* solo simulation (AI traffic)
* FlightGear network connection ([[FGMS]] protocol)
* FSD connection (as served by https://github.com/kuroneko/fsd commit bc7d43, latest available in Dec. 2022)
* teaching service (spawn and simulate traffic visible to a connected student)
* student session (control traffic simulated by teacher)

Location modes:
* airport (AD): positions such as TWR, GND, APP, DEP at a selected airfield
* en-route centre (CTR): free positioning of radar, no base airport or TKOF/LDG-related options

{| class="wikitable" style="text-align:center"
|+ Feature support by session type
! || Solo || FlightGear || FSD || Tutoring (teacher/student)
|-
! ACFT traffic
| AI aircraft generated according to RWY capacities, ACFT equipment, intentions...
| colspan="2" | connected flight sim pilots
| created and simulated by teacher
|-
! ATCs and coordination
| virtual ATCs depending on assumed positions
| colspan="2" | connected ATC clients (full ATC-pie interaction, [[#Interoperability with other software|interoperability with other software]])
| teacher-configured ATCs
|-
! Voice radio
| voice recognition for instructions (mouse-only also available) and synthesis for pilot read-back
| colspan="2" | [[FGCom-mumble]] integration
| teacher simulates pilots
|-
! ATC phone lines
| N/A
| colspan="2" | integrated Mumble connection
| teacher simulates ATCs
|-
! Flight plans
| local entries only
| interface with the FlightGear ''de facto'' [http://flightgear-atc.alwaysdata.net data base by Lenny64]
| available from network (NB: protocol does not support open/close and only pilots can file/amend FPLs)
| shared virtual online system
|-
! CPDLC
| interpreted subset of instruction messages
| integrated (supported by MP IRC)
| integrated interface with [https://www.hoppie.nl/acars/ Hoppie's ACARS network]
| full simulation by teacher (with WILCO assistance to execute instructions)
|-
! Weather
| randomised and evolving
| real world METAR retrieval
| fetch from server or retrieve real world METAR
| controlled by teacher
|-
! Other specific features
| style="text-align:left" |
* aircraft type and airline choice with custom appearence in tower view
* configurable airspace rules and traffic density, incl. uncontrolled distractors
| style="text-align:left" |
* exact aircraft rendering in views (incl. control surfaces, etc.)
* historic [[FGCom_3.0|FGCom executable]] alternative supported
| style="text-align:left" |
* frequency tuning system for radio text chat
* text ATIS repeatedly sent through radio chat on recorded frequency
| style="text-align:left" |
* traffic snapshots and recall to repeat situations with the student
* individual aircraft freeze
|}

== Detailed feature list ==

=== ATC surveillance ===
Radars and tracking:
* SSR mode capability selection (none/A/C/S)
* primary radar toggle
* traffic identification assistant
* position/track vs. strip assignment mismatch warning system
* route/vector conflict anticipation
* separation incident alarm
* runway occupation/incursion detection

Tower view in airport mode (rendered by FlightGear):
* view of airport, aircraft, weather, time of day
* start internal process or use externally running instance
* control panel to orient/zoom view or follow aircraft
* additional views can be connected (for multiple camera angles)

Other:
* radio direction finding (RDF) and integration to radar
* multiple weather (METAR) station monitor
* [[ATIS]] recording and reminder alarm (see [[:File:ATC-pie-screenshot-ATISdialog.png|dialog]] with pre-filled notepad)

=== Traffic management ===
Strips and racks:
* user-defined strip racks with configurable colours (for linked radar contacts) and ATCs to receive from
* runway boxes with automatic RWY separation timers
* loose strip bays with customisable backgrounds

Flight plans and routes:
* flight plan system (file, edit, open, close, publish/retrieve online)
* world route suggestions, presets, analysis, radar drawing and world map view
* departure clearance assistant
* automatic strip printing for expected departures or arrivals (from FPLs)

Radar tools:
* convenient mouse input for instructions (vectors, taxi...) and CPDLC integration
* approach spacing hints (estimated touch-down time difference, sequence optimisation suggestions)
* quick point-to-point heading and distance measuring tool
* direct text annotation of radar screen
* flag/unflag (highlight) radar targets

=== Communications ===
With aircraft:
* voice radio with 8.33 kHz frequency spacing, multiple radio transmissions and monitoring
* [[controller-pilot data link communication]] (CPDLC), incl. DEP clearance delivery, multi-element messages...
* text radio chat with preset messages, auto-completion, predefined and custom aliases (context-sensitive replacements), sender blacklist

ATC coordination:
* strip exchange (handovers)
* CPDLC authority transfers
* telephone lines and switchboard (direct voice communication)
* text messaging (private channels and general ATC chat room)
* "who has?" requests

=== Other ===
Misc. tools:
* world airport, map navpoint and AD parking position browsing/indicating
* aeronautical unit conversion calculator
* custom alarm clocks with quick keyboard timer start
* general and location-specific notepads restored between sessions
* list of known ACFT types by callsign

GUI:
* multiple window workspace (radar screens, strip racks and bays) saved by location
* floatable/dockable panels and toolbars (see [[:File:ATC-pie-screenshot-toolbars.png|screenshot]]) and layout save/restore
* notification system combining selectable sounds, status bar messages and time-tagged history
* customisable style and colours

Data sources:
* airport and navigation data sourced in the [http://developer.x-plane.com/docs/specs X-Plane] format (old world-wide default file set provided but custom imports recommended)
* editable aircraft data base (ICAO designators, cruise speeds, WTC, etc.)
* custom radar background images and hand drawings (EuroScope/[http://www.vatsim.net VATSIM]/IVAO "sector file" conversion tool included)
* ground elevation maps (can be generated automatically with a provided script if FlightGear terrain data available)
* manual magnetic declination input

== Interoperability with other software ==

=== OpenRadar ===
[[OpenRadar]] is another stand-alone program able to connect to FlightGear networks. ATC-pie and OpenRadar's philosophies differ in several ways:
* OpenRadar's basic processing unit is the FGMS callsign, whereas ATC-pie's is the strip;
* OpenRadar's concept of handover is based on a shared notion of aircraft ownership, whereas ATC-pie allows any controller to pull out a strip and write a callsign on it;
* in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring users to see it complete, whereas ATC-pie considers that a strip sent is gone and assumed to land on the receiver's rack, without anybody else necessarily to know.

For most interactions to work in FlightGear sessions while respecting both approaches as much as possible, the following principles and restrictions apply to strip exchange between the two programs:
* ATC-pie users can only hand over strips to OpenRadar that are linked to a radar contact;
* aircraft under ATC-pie control are not shown as "owned" to OpenRadar users;
* handovers from ATC-pie will fail if an OpenRadar user is claiming ownership on the linked radar contact;
* when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally.

Callsign handover policy:
* OpenRadar to ATC-pie: FGMS callsign will appear on the strip, as if the sender had filled the detail herself;
* ATC-pie to OpenRadar: callsign resolved for the receiver, sender's entry will reappear next time ATC-pie handles the strip;
* pie-to-pie handovers through OpenRadar's service: strip detail preserved, whether present or absent.

Features not supported by OpenRadar:
* ATC phone lines;
* ATC text messaging;
* CPDLC transfers;
* wake turbulance category and departure clearances on strips (but details preserved for ATC-pie clients later receiving the strip).

Who-has requests are fully supported.

=== Euroscope ===
Euroscope is a popular program to control on VATSIM, a flight simulation network whose protocol is historically based on FSD. It has been increasingly tailored for VATSIM, although for a long time it allowed also to connect to "plain" (non-VATSIM) FSD servers. Operability outside of VATSIM is now discontinued all together, but older versions of Euroscope are still around and connecting to FSD networks. ATC-pie is able to interact with them in FSD sessions, but only to a limited extent:
* sending a strip to Euroscope will result in a loss of all strip details but the callsign (which must be connected), the only information left to the recipient being the FPL details for that callsign if any (strip changes made after FPL data retrieval are therefore lost);
* receiving a strip from Euroscope is supported, but the sender will see the hondover pending (never "assumed");
* who-has requests will remain unanswered by Euroscope;
* there are no integrated phone lines to Euroscope clients.

[[Category:ATC-pie]]
[[Category:ATC clients]]
[[Category:Air Traffic Control]]

Schleicher ASK 13

2025-11-12T09:05:06Z

Hbeni:

{{Stub}}
{{:{{PAGENAME}}/info}}
The '''Schleichter ASK 13''' is a two-seater [[Gliders|glider]] that was built by Alexander Schleicher. It was and still is widely used for ab-initio training of glider pilots.

You can find more details about this awesome aircraft [http://en.wikipedia.org/wiki/Schleicher_ASK_13 at Wikipedia].

The [[FlightGear]] model of the ASK-13 comes with a basic [[dual control]] support. So far this is only a passive passenger view, but yet an instructor can be with his student and help newcomers to discover the joys of soaring by real time piloting advices.

== Development status/Issues/Todo ==
Outside:

* texturing is very basic

General:

* Dual Control is now limited to a simple , passive passenger view.
* Passenger view has a very limited audio support.
* FDM is relatively accurate, but could be fine tuned. Testers are welcome !

== Related content ==
* [[Howto: Do aerotow over the net]]
* [[Soaring]]

== External links ==
* {{Wikipedia|Schleicher ASK 13 |lang=en}}
* POH https://www.psgc.co.uk/pdf/ask13_flight_manual.pdf

{{Schleicher}}

De/FGCom-mumble

2025-11-07T09:32:05Z

Hbeni: /* Bekannte Inkompatibilitäten */

'''FGCom-mumble''' simuliert Funkkommunikation basierend auf der freien VoIP software [https://www.mumble.info/ Mumble]. Es integriert sich vollstädnig mit den Funkgeräten deines Flugzeuges in FlightGear und erlaubt dir, mit anderen Piloten und Fluglotsen auf realistische Weise zu kommunizieren. Dafür simuliert es ein lückenloses Radiowellenspektrum.

FGCom-mumble ist eine Alternative zum altbekannten [[FGCom]] sowie [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble nutzt den Pluginmechanismus, der in Mumble 1.4.0 verfügbar wurde und benötigt lediglich ein vorkompiliertes Plugin, das von einem ganz normalen Mumble-Programm geladen wird. Das aktuellste Release kannst du hier herunterladen: https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Server ==

* Der FGCom-mumble test server ist <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
* Die Statusseite für diese Instanz, die alle verbundenen Clients anzeigt, ist hier: https://fgcom-dev.hallinger.org/
* Der mumble-testserver benutzt ein autoerneuerndes SSL-Zertifikat von Lets Encrypt.

== Hauptziele des Projektes ==
* Bereitstellen von Kommunikation, die sowohl örtlich als auch kanaltechnisch getrennt ist
* Realistische Funkkommunikation
* Einfachheit in der Installation und Benutzung
* Unterstützung für beliebige Frequenzen
* ATIS Aufnahme und Wiedergabe
* Zivile Radiostationen sollen unterstützt werden
* Festnetz/Intercom Unterstützung
* RDF-Signale für Clients
* Einfach auf einem Server zu installieren und zu betreieben
* Unabhängigkeit von Simulatoren wie z.B. Flightgear
* Fähigkeit, in FlightGear integriert zu werden, mit der Option, weitere Clients und Applikationen zu unterstützen (ATC, aber auch andere Flugsimulatoren)
* Modularer Aufbau, damit einzelne Komponenten unterschiedlich implementiert werden können und einfache Erweiterbarkeit besteht
* Gute und vollständige Dokumentation

== Installation and Einrichtung ==
Die aktuelle Version kann hier heruntergeladen werden: [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] bietet auch eine Debug-Variante an).

Die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#installation--einrichtung-des-mumble-plugins README] bietet detaillierte Angaben zur Installation.

Jemand hat sogar ein Video (engl.) von der Installation gemacht! :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk

Zusammengefasst:
* Du brauchst ein installiertes und eingerichtetes Mumble >= 1.4, und dann lade darin das Plugin (unter mumble Einstellungen/plugins)
* Auf dem Mumbleserver (Version >= 1.4.0) trittst du einem Channel bei, dessen Name mit `fgcom-mumble` beginnt
* Im FlightGear-Launcher fügst du im Addon-Tab den `fgfs-addon` Ordner der FGCom-Mumble Veröffentlichung hinzu
* Starte FlightGear und benutze deine Funkgeräte (du funkst mit den ganz normalen FGCom-Tastenkombinationen; siehe unten)

== Benutzung ==
FlightGear's FGCom-mumble Protokoll benutzt die normalen FGCom-Tastenkombinationen:
* Um auf COM1 zu funken, drückst du {{Key press|Space}}. Solange du überträgst, kannst du keine anderen Piloten durch das verwendete Funkgerät hören (diese sind Halbduplexgeräte).
* COM2 sendet mit {{Key press|Shift|Space}}.
* Seit FGCom-mumble 1.2.0:
** Mit COM3 funkst du über {{Key press|Alt|Space}} (früher musstest du ein eigenes Keybind definieren),
** Intercom sendet in full-duplex mit {{Key press|Ctrl|Space}}

Jedes Funkgerät kann außerdem über die COMBar benutzt werden (öffnen über ''Menu/Multiplayer/FGCom-mumble'').

Um FGCom-mumble ohne FlightGear zu probieren, kannst du auch die im Release mitgelieferte RadioGUI starten.

=== Deine Installation testen ===
Als erstes solltest du sicherstellen, dass mumble an Sich gut funktioniert und du gut zu verstehen bist sowie andere gut verstehst.
Dazu deaktivierst du am Besten das Plugin oder du sprichst mit anderen auf einem Channel, der nicht mit `fgcom-mumble`beginnt.

Das Plugin verändert Mumbles eingehende Audiopakete. Es fügt statisches Rauschen hinzu, das von der simulierten Funksignalstärke abhängt oder hebt den stream sogar auf, wenn der Funksender außerhalb der Reichweite liegt. Ausgehende Audiopakete werden nicht verändert.

Falls der Server es unterstützt, kannst du auch einen traditionellen Echo-Test machen (dazu muss am Server ein `fgcom-recorder-bot` laufen). Funke auf der Frequenz `910.00` MHz und der Recorderbot wird mit der Aufzeichnung beginnen (er schreibt das in den mumble-chat) und nach Abschluss einen bot an deiner Position erzeugen, der das aufgenommene auf der Frequenz wiedergibt. So kannst du dich selbst hören, wie andere dich hören würden.

=== Fehlerbehebung ===

Schau bitte in die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#fehlerbehebung README] des Projekts. Diese hat detaillierte Informationen hierzu.

Solange es nichts grundlegendes mit der Installation zu tun hat, hilft oft auch einfach ein Neustart von Mumble (das Plugin initialisiert sich selbständig frisch).

=== Kompatibilität ===
FGCom-mumble unterstützt grundsätzlich das alte FGCom-UDP-Protokoll und sollte somit kompatibel mit allen clients sein, die dieses verwenden (z.B. ältere ATCpie oder OpenRadar Versionen). Allerdings gibt es auch ein paar Erweiterungen, die mit dem alten Protokoll nicht zur Verfügung stehen.

* FlightGear wird durch ein [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon] unterstützt. Dieses erwartet die Standard-Funkgerätimplementierung (und funktioniert getestet zumindest mit der C172p und der C182S).
*[[ATC-pie]] hat eine integrierte Unterstützung (prüfe, ob "FGCom-mumble" anstelle von nur "FGCom" in den Einstellungen aktiviert ist).
*[[OpenRadar]] Unterstützt im Moment nur COM1 ([https://sourceforge.net/p/openradar/tickets/5/ Ticket dazu ist offen]). Für COM2 und weitere musst du entweder separate Mumble-Instanzen öffnen oder FGCom-mumble's RadioGUI zum Funken benutzen.
:Es gibt eine gepatchte Version von OpenRadar mit integriertem FGCom-mumble sowie 8.33 Channelmodus; verfügbar hier: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

==== Bekannte Inkompatibilitäten ====
* Das alte FGCom aktiviert sich selbständig, wenn du mit dem Mehrspielernetzwerk verbunden bist und dann die "FGCom"-Einstellungen (anstelle des "FGCm-Mumble"-Eintrags) aus dem Mehrspielermenü aufrufst. Wenn du mit aktiviertem alten FGCom PTT aktivierst, kann FlightGear abstürzen (aktuelle FGcom-mumble addons haben einen Workaround dafür).
* Das FlightGear UFO belegt {{Key press|Space}} selbst, sodass du nicht Funken kannst. Als workaround kannst du die COMBar benutzen, die mit dem FGFS Addon mitkommt.
* FGFS version <= 2020.3 ist nicht mit FGCom-mumble addon version >= 1.3.0 kompatibel. Es wird 1.2.0 benötigt, oder ein FGFS upgrade.
* FGExtend wechselt dich in mumble in einen anderen Channel, wenn du die Frequenz änderst. Wenn du FGCom-mumble benutzen möchtest, musst du FGExtend ausschalten.

== RadioGUI ==
Die RadioGUI ist eine kleine Java8 Applikation, die einen FGCom-mumble client implementiert und Funkgeräte bereitstellt. Sie sendet die notwendigen UDP Nachrichten an das Mumble plugin.

In der GUI kannst du deinen Standort über eine Karte auswählen und dann deine Funkgeräte einstellen und testen.
Damit kannst du auch komplett mit allen Funktionen am simulierten Funknetz teilnehmen, ohne FlightGear zu starten.

== Serverseite ==
Konzeptionell benötigst du als Minimum einfach einen Standard Mumbleserver (Version 1.4.0 oder höher), auf dem ein Channel eingerichtet wird, der mit `fgcom-mumble` beginnt. Das ist bereits genug, damit das Plugin Clientseitig den Rest erledigen kann. Der komplette Channel wird als einzelnes, weltumspannendes, kontinuierliches Radiowellenspektrum behandelt.

Weitere Funktionen werden über Lua-Bots implementiert (die auch auf einer anderen Maschine laufen können):
* ATIS Aufzeichnung udn Wiedergabe
* Radioprogramm Wiedergabe (OGG Wiedergabe auf einer beliebigen Funkfrequenz), z.B. nutzbar für eigene NDBs mit Morsecode ([https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons])
* Statusseite Datensammlung

Eine Statusseite fürs WWW ist als PHP-Seite implementiert, die die notwendigen Daten über den `fgcom-status-bot` bereitgestellt bekommt.

Detaillierte Installations- und Betriebsdokumentation ist in den Veröffentlichungen enthalten, aber auch [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server-de_DE.md online] im Projekt zugänglich.

== Wie funktiooniert das alles? (technische Information) ==
Die technischen Details sind in den verschiedenen Readme-Dateien im Projekt dargelegt (zum Start empfielt sich [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Zusammengefasst treten alle Teilnehmer einem einzigen Mumble-Channel bei und laden das fgcom-mumble Plugin. Das Plugin tauscht alle notwendigen Daten zwischen den Nutzern aus (Funkgeräte, Frequenzen, Standort, etc.) und basierend auf diesen Informationen werden die eingehenden Audioströme der anderen Nutzer entweder abgespielt oder stummgeschaltet. Für mehr Realismus werden abgespielte Audioströme mit Statischem Rauschen und weiteren Effekten unterlegt.
Aufgrund der Stummschaltefunktion abhängig von der Funkreichweite besteht eine unmittelbare Separierung nach Funkkanal und Standort, was allen Nutzern erlaubt, in ein und demselben Mumblekanal zu sein.

== Weiterführender Inhalt ==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] mit weiteren Tipps/Hinweisen
*[https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md FGCom-mumble README-de_DE.md] Haupt-Readme des Projektes mit allen Details, die du schon immer wissen wolltest

=== Forum topic ===
* Der {{forum link|t=37644|title=FGCom-mumble}} Forumshtread hat Entwicklungsrelevante Informationen und dient zur allgemeinen Diskussion
* {{forum link|p=374950|title=Re: EDDF-Triangle}} und {{forum link|p=374970|title=Re: EDDF-Triangle}} - behandeln Details zu Kompatibilität und Unterschieden zwischen FGCom, FGCom-mumble und Mumble

=== FlightGear Newsletter ===
*[[FlightGear_Newsletter_June_2020]]: Erster Prototyp angekündigt
*[[FlightGear_Newsletter_July_2020]]: Lasttests erfolgreich, RDF implementiert, Live-Status Seite hinzugefügt
*[[FlightGear_Newsletter_August_2020]]: Mehr tests, neue HF/VHF/UHF modelle, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API änderungen, verteilte Installation, Konfigurationsmöglichkeit per INI-Datei, Statistiken
*[[FlightGear_Newsletter_October_2020]]: Weitere API änderungen, realistische Simulation der 8.33kHz/25kHz Kanalüberlappung, RadiGUI hinzugefügt
*[[FlightGear_Newsletter_November_2020]]: Test server angekündigt
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringt Netzwerkfunktionen
*[[FlightGear_Newsletter_April_2021]]: RDF Implementierung umgebaut, 0.12.0 angekündigt, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Bessere Unterstützung von Airliners, 0.13.0 and 0.14.0 angekündigt, Releasepaket neustrukturiert
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 angekündigt, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 angekündigt, updater bugfixes Teil II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 veröffentlicht, Mumble 1.4 wurde veröffentlicht'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[en:FGCom-mumble]]

FGCom-mumble

2025-11-07T09:30:40Z

Hbeni: /* Known incompatibilities */

'''FGCom-mumble''' simulates radio communication based on the VoIP software [https://www.mumble.info/ Mumble]. It integrates fully with the radio stack of your FlightGear plane, allowing you to communicate with other pilots and airspace controllers during your flight. It simulates a global, continuous radio frequency spectrum.

FGCom-mumble is an alternative to the already known [[FGCom]] client and [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble leverages the plugin mechanism introduced by Mumble 1.4.0 and just needs a precompiled plugin loaded by a stock Mumble client.
You can download the latest release from https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Servers ==

*The main FGCom-mumble test server is <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
*The status page for that service showing all connected clients is at: https://fgcom-dev.hallinger.org/
*The mumble test server uses a autorenewed certificate from letsencrypt.

==Project main goals==
*Provide communication with geographic and channel separation
*Provide a realistic radio simulation
*Ease of use for the end user/pilot
*Arbitrary frequency support
*ATIS recording and playback
*Radio station broadcast support
*Landline/Intercom support
*RDF detection for clients
*Ease of server side installation and operation
*Standalone nature (no dependency on FlightGear)
* Capability to be integrated into FlightGear, with the option to support third party applications (ATC, but also other flight simulators)
*Modularity, so individual component implementations can be switched and its easy to add features
*Good and complete documentation

== Installation and setup==
The latest release can be fetched from [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] also has debug versions).

The provided [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#install--setup-for-the-client README] has detailed instructions on the needed prerequisites and installation procedures.

Someone even made an install video :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk
(thanks mate, well done! however HF is actually simulated already :)

In short:
* Have a stock Mumble client >= 1.4 running, and load the plugin (mumble settings/plugins page)
* Join a channel named `fgcom-mumble` (on a >= 1.4 mumble server)
* Add the `fgfs-addon` folder of the client release as FlightGear Addon in your launcher
* Start FlightGear and use your plane's radio stack (it uses default FGCom buttons, see below)

==Usage==
FlightGear's FGCom-mumble protocol uses the default FGCom buttons:
* When you want to talk on COM1 you have to press {{Key press|Space}}. While transmitting you can not hear other pilots trough the used radio (they are half-duplex).
* You can also talk on COM2 by pressing {{Key press|Shift|Space}}.
* since FGCom-mumble 1.2.0:
** For COM3 you use {{Key press|Alt|Space}} (previously you need to define a custom keybind),
** Intercom is available in full-duplex with {{Key press|Ctrl|Space}}

Any radio can also accessed by the COMBar (open from ''Menu/Multiplayer/FGCom-mumble'').

If you want to try it out without FlightGear, you can also start the supplied RadioGUI.

=== How to test your setup?===
First, make sure Mumble is working reliably by talking to other people. Either disable the plugin, or be sure you are outside any radio channel (starting with `fgcom-mumble`).

The plugin alters Mumble's receiving audio stream. It adds static noise depending on the radio signal quality, or cancels out all audio when not in range. The outgoing audio stream is not altered in any way.

If the server supports it (in essence there is a bot-manager running and a `fgcom-recorder-bot` listening) you may do a traditional echo test by tuning `910.00` and start to talk. The recorder-bot will record that (he writes that into mumbles chat) and spawn an echo bot at your position, replaying your message (so you will hear yourself like others will hear you).

===Troubleshooting===
For troubleshooting, refer to the projects [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#troubleshooting README] as it has further suggestions.

If it's nothing setup related, an easy fix is to just restart mumble (the plugin will reinitialize itself).

===Compatibility ===
FGCom-mumble supports the legacy FGCom UDP protocol and thus should be compatible to clients supporting that. However, it also features some new UDP fields.

*FlightGear is supported through an [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon]. This assumes the default radio implementation and works with at least the C172P and the C182S.
*[[ATC-pie]] has built in support already (be sure to activate "FGCom-mumble" instead of just "FGCom" in the settings).
*[[OpenRadar]] currently supports just COM1 ([https://sourceforge.net/p/openradar/tickets/5/ ticket pending]). To use COM2 and more, you need to either start several mumble instances, or use FGCom-mumble's RadioGUI.
:There is a patched version of OpenRadar with FGCom-mumble and 8.33 channel tuning support available here: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

====Known incompatibilities====
* The legacy FGCom auto-enables itself, if you are connected to a multiplayer server and then open the "FGCom" dialog (instead of the "FGCom-mumble" one) from the multiplayer dialog. Then activating PTT can cause a FlightGear segfault (newer FGCom-mumble addon versions have a workaround).
* The UFO aircraft rebinds {{Key press|Space}} so you can't transmit on the radio. As a workaround you can use the COMBar that comes integrated with the FGFS addon.
* FGFS version <= 2020.3 is not compatible with FGCom-mumble addon versions >= 1.3.0. You need to stick to 1.2.0 or upgrade FGFS.
* FGExtend switches you out of channels upon frequency change. You need to disable FGExtend when using FGCom-mumble.

==RadioGUI==
The FGCom-mumble RadioGUI is a small Java 8 application that can send the FGCom-mumble UDP messages to the Mumble plugin.

Inside the GUI, you can pick your location from a map and then setup and use your radio stack.
That said, the RadiGUI can be used instead (or additionally to) FGFS to participate on the simulated radio net.

==Server side==
By design, all that is needed is a standard Murmur server (version 1.4.0 or later) and a specially named channel (it has to start with `fgcom-mumble`). This is enough to let the plugin do its work. The entire channel is treated as a single, worldwide continuous radio frequency spectrum.

Additional features are implemented using server side Lua bots (which may run somewhere else):
* ATIS recording and broadcasting
* Radio program broadcasting (OGG playback on a frequency), [https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons]
* Status page data collection

A status page showing client details is available as a PHP website, that gets its data fed from the fgcom-status-bot.

Detailed installation and operation documentation is shipped with the releases, but is also [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server.md online].

==How does it work? (technical information)==
The technical details are specified and described in the various readme files of the projects source code (as a starter read the [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Basicly, all users join the same mumble channel and run the fgcom-mumble plugin. The plugin knows everything necessary from the participating users (like radios used, frequencies tuned, locations, etc) and based on that information mutes or plays incoming voice messages from the other users. Based on signal quality, static noise is mixed in for more fun and a more realistic experience.
Because the voice of other users is muted, it is a design wise out-of-the-box feature that brings frequency and location separation but allows everyone to stay in the same mumble channel.

==Related content==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] with hints etc
*[https://github.com/hbeni/fgcom-mumble/blob/master/README.md FGCom-mumble README.md] Main readme of the project bringing all the details you always wanted to know

===Forum topic===
*The {{forum link|t=37644|title=FGCom-mumble}} has development discussions and release announcements
*{{forum link|p=374950|title=Re: EDDF-Triangle}} and {{forum link|p=374970|title=Re: EDDF-Triangle}} - Compatibility and differences between FGCom, FGCom-mumble and Mumble

===FlightGear Newsletter===
*[[FlightGear_Newsletter_June_2020]]: First prototype announced
*[[FlightGear_Newsletter_July_2020]]: Load tests successful, RDF implemented, Live-Status page added
*[[FlightGear_Newsletter_August_2020]]: More testing, new HF/VHF/UHF models, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API changes, distributed deployment, configuration trough INI, statistics
*[[FlightGear_Newsletter_October_2020]]: More API changes, proper 8.33kHz/25kHz overlap, RadiGUI added
*[[FlightGear_Newsletter_November_2020]]: Test server announced
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringing networking capability
*[[FlightGear_Newsletter_April_2021]]: RDF reworked, 0.12.0 announced, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Better airliner support, announced 0.13.0 and 0.14.0, restructured release package structure
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 announced, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 announced, updater bugfixes part II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 released, Mumble 1.4 hit the light'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

== Idea to integrate into FGFS ==
{{progressbar|10|10}} {{pending}}

EDIT: Core ticket: https://gitlab.com/flightgear/flightgear/-/issues/3095

ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212

Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum).

A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible?

libmubmble is not yet API-stable (but should be working), but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics:
* From FGCom-mumbles side, we need to integrate the data structures into the core. So radios need to be registered, etc. This should not be too hard
** we probably just need to not run the UPD-Server but send the needed data directly into the decoding function of it. At a later stage, we might better integrate that part, but for a first working solution, just creatig a FCGOM-mumble UDP-Packet string in FGFS and sending it periodically (or already on-demand?) into the udp-servers decoder function should be enough - it just creates some CPU overhead which should not be too bad and will establish the needed local data structure.
** Note, that we cannot rely on the mpservers data structures (even if there is radio data), because in FGCom-mumble potential other clients are also participating (like radio-playback bots for ATIS etc!). So we really need to use mumbles plugin messages.
* Basicly the libmumble will run its own threads for networking. Upon receiving mumble audio or mumble-plugin data, callback functions would be called from the lib (https://github.com/mumble-voip/libmumble/issues/18#issuecomment-1868498537):
** Incoming audio data need to be processed by the fgcom-mumble plugin functions, and then the result handed over into fgfs audio out handling.
** Incoming plugin data needs to be fed into the fgcom-mumble internal remote data struct (just hand the data into the existing data parser).
* Pressing the already existing fgfs PTT button
** would need to send plugin data to mumble, to inform other clients. This is currently done by calling a mumble client function. It would probably be enough, if fgfs core supplied an implemention that calls the appropriate libmumble function and hands over the data.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} And what about libmubmles dependencies, like OpenSSL?
*** technically, how to include that all into the existing build system?

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[de:FGCom-mumble]]

FGCom-mumble

2025-03-03T10:16:06Z

Hbeni: /* Idea to integrate into FGFS */

'''FGCom-mumble''' simulates radio communication based on the VoIP software [https://www.mumble.info/ Mumble]. It integrates fully with the radio stack of your FlightGear plane, allowing you to communicate with other pilots and airspace controllers during your flight. It simulates a global, continuous radio frequency spectrum.

FGCom-mumble is an alternative to the already known [[FGCom]] client and [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble leverages the plugin mechanism introduced by Mumble 1.4.0 and just needs a precompiled plugin loaded by a stock Mumble client.
You can download the latest release from https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Servers ==

*The main FGCom-mumble test server is <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
*The status page for that service showing all connected clients is at: https://fgcom-dev.hallinger.org/
*The mumble test server uses a autorenewed certificate from letsencrypt.

==Project main goals==
*Provide communication with geographic and channel separation
*Provide a realistic radio simulation
*Ease of use for the end user/pilot
*Arbitrary frequency support
*ATIS recording and playback
*Radio station broadcast support
*Landline/Intercom support
*RDF detection for clients
*Ease of server side installation and operation
*Standalone nature (no dependency on FlightGear)
* Capability to be integrated into FlightGear, with the option to support third party applications (ATC, but also other flight simulators)
*Modularity, so individual component implementations can be switched and its easy to add features
*Good and complete documentation

== Installation and setup==
The latest release can be fetched from [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] also has debug versions).

The provided [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#install--setup-for-the-client README] has detailed instructions on the needed prerequisites and installation procedures.

Someone even made an install video :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk
(thanks mate, well done! however HF is actually simulated already :)

In short:
* Have a stock Mumble client >= 1.4 running, and load the plugin (mumble settings/plugins page)
* Join a channel named `fgcom-mumble` (on a >= 1.4 mumble server)
* Add the `fgfs-addon` folder of the client release as FlightGear Addon in your launcher
* Start FlightGear and use your plane's radio stack (it uses default FGCom buttons, see below)

==Usage==
FlightGear's FGCom-mumble protocol uses the default FGCom buttons:
* When you want to talk on COM1 you have to press {{Key press|Space}}. While transmitting you can not hear other pilots trough the used radio (they are half-duplex).
* You can also talk on COM2 by pressing {{Key press|Shift|Space}}.
* since FGCom-mumble 1.2.0:
** For COM3 you use {{Key press|Alt|Space}} (previously you need to define a custom keybind),
** Intercom is available in full-duplex with {{Key press|Ctrl|Space}}

Any radio can also accessed by the COMBar (open from ''Menu/Multiplayer/FGCom-mumble'').

If you want to try it out without FlightGear, you can also start the supplied RadioGUI.

=== How to test your setup?===
First, make sure Mumble is working reliably by talking to other people. Either disable the plugin, or be sure you are outside any radio channel (starting with `fgcom-mumble`).

The plugin alters Mumble's receiving audio stream. It adds static noise depending on the radio signal quality, or cancels out all audio when not in range. The outgoing audio stream is not altered in any way.

If the server supports it (in essence there is a bot-manager running and a `fgcom-recorder-bot` listening) you may do a traditional echo test by tuning `910.00` and start to talk. The recorder-bot will record that (he writes that into mumbles chat) and spawn an echo bot at your position, replaying your message (so you will hear yourself like others will hear you).

===Troubleshooting===
For troubleshooting, refer to the projects [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#troubleshooting README] as it has further suggestions.

If it's nothing setup related, an easy fix is to just restart mumble (the plugin will reinitialize itself).

===Compatibility ===
FGCom-mumble supports the legacy FGCom UDP protocol and thus should be compatible to clients supporting that. However, it also features some new UDP fields.

*FlightGear is supported through an [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon]. This assumes the default radio implementation and works with at least the C172P and the C182S.
*[[ATC-pie]] has built in support already (be sure to activate "FGCom-mumble" instead of just "FGCom" in the settings).
*[[OpenRadar]] currently supports just COM1 ([https://sourceforge.net/p/openradar/tickets/5/ ticket pending]). To use COM2 and more, you need to either start several mumble instances, or use FGCom-mumble's RadioGUI.
:There is a patched version of OpenRadar with FGCom-mumble and 8.33 channel tuning support available here: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

====Known incompatibilities====
* The legacy FGCom auto-enables itself, if you are connected to a multiplayer server and then open the "FGCom" dialog (instead of the "FGCom-mumble" one) from the multiplayer dialog. Then activating PTT can cause a FlightGear segfault.
* The UFO aircraft rebinds {{Key press|Space}} so you can't transmit on the radio. As a workaround you can use the COMBar that comes integrated with the FGFS addon.
* FGFS version <= 2020.3 is not compatible with FGCom-mumble addon versions >= 1.3.0. You need to stick to 1.2.0.

==RadioGUI==
The FGCom-mumble RadioGUI is a small Java 8 application that can send the FGCom-mumble UDP messages to the Mumble plugin.

Inside the GUI, you can pick your location from a map and then setup and use your radio stack.
That said, the RadiGUI can be used instead (or additionally to) FGFS to participate on the simulated radio net.

==Server side==
By design, all that is needed is a standard Murmur server (version 1.4.0 or later) and a specially named channel (it has to start with `fgcom-mumble`). This is enough to let the plugin do its work. The entire channel is treated as a single, worldwide continuous radio frequency spectrum.

Additional features are implemented using server side Lua bots (which may run somewhere else):
* ATIS recording and broadcasting
* Radio program broadcasting (OGG playback on a frequency), [https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons]
* Status page data collection

A status page showing client details is available as a PHP website, that gets its data fed from the fgcom-status-bot.

Detailed installation and operation documentation is shipped with the releases, but is also [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server.md online].

==How does it work? (technical information)==
The technical details are specified and described in the various readme files of the projects source code (as a starter read the [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Basicly, all users join the same mumble channel and run the fgcom-mumble plugin. The plugin knows everything necessary from the participating users (like radios used, frequencies tuned, locations, etc) and based on that information mutes or plays incoming voice messages from the other users. Based on signal quality, static noise is mixed in for more fun and a more realistic experience.
Because the voice of other users is muted, it is a design wise out-of-the-box feature that brings frequency and location separation but allows everyone to stay in the same mumble channel.

==Related content==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] with hints etc
*[https://github.com/hbeni/fgcom-mumble/blob/master/README.md FGCom-mumble README.md] Main readme of the project bringing all the details you always wanted to know

===Forum topic===
*The {{forum link|t=37644|title=FGCom-mumble}} has development discussions and release announcements
*{{forum link|p=374950|title=Re: EDDF-Triangle}} and {{forum link|p=374970|title=Re: EDDF-Triangle}} - Compatibility and differences between FGCom, FGCom-mumble and Mumble

===FlightGear Newsletter===
*[[FlightGear_Newsletter_June_2020]]: First prototype announced
*[[FlightGear_Newsletter_July_2020]]: Load tests successful, RDF implemented, Live-Status page added
*[[FlightGear_Newsletter_August_2020]]: More testing, new HF/VHF/UHF models, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API changes, distributed deployment, configuration trough INI, statistics
*[[FlightGear_Newsletter_October_2020]]: More API changes, proper 8.33kHz/25kHz overlap, RadiGUI added
*[[FlightGear_Newsletter_November_2020]]: Test server announced
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringing networking capability
*[[FlightGear_Newsletter_April_2021]]: RDF reworked, 0.12.0 announced, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Better airliner support, announced 0.13.0 and 0.14.0, restructured release package structure
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 announced, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 announced, updater bugfixes part II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 released, Mumble 1.4 hit the light'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

== Idea to integrate into FGFS ==
{{progressbar|10|10}} {{pending}}

EDIT: Core ticket: https://gitlab.com/flightgear/flightgear/-/issues/3095

ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212

Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum).

A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible?

libmubmble is not yet API-stable (but should be working), but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics:
* From FGCom-mumbles side, we need to integrate the data structures into the core. So radios need to be registered, etc. This should not be too hard
** we probably just need to not run the UPD-Server but send the needed data directly into the decoding function of it. At a later stage, we might better integrate that part, but for a first working solution, just creatig a FCGOM-mumble UDP-Packet string in FGFS and sending it periodically (or already on-demand?) into the udp-servers decoder function should be enough - it just creates some CPU overhead which should not be too bad and will establish the needed local data structure.
** Note, that we cannot rely on the mpservers data structures (even if there is radio data), because in FGCom-mumble potential other clients are also participating (like radio-playback bots for ATIS etc!). So we really need to use mumbles plugin messages.
* Basicly the libmumble will run its own threads for networking. Upon receiving mumble audio or mumble-plugin data, callback functions would be called from the lib (https://github.com/mumble-voip/libmumble/issues/18#issuecomment-1868498537):
** Incoming audio data need to be processed by the fgcom-mumble plugin functions, and then the result handed over into fgfs audio out handling.
** Incoming plugin data needs to be fed into the fgcom-mumble internal remote data struct (just hand the data into the existing data parser).
* Pressing the already existing fgfs PTT button
** would need to send plugin data to mumble, to inform other clients. This is currently done by calling a mumble client function. It would probably be enough, if fgfs core supplied an implemention that calls the appropriate libmumble function and hands over the data.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} And what about libmubmles dependencies, like OpenSSL?
*** technically, how to include that all into the existing build system?

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[de:FGCom-mumble]]

Addon

2025-02-24T08:55:38Z

Hbeni: /* Nasal API */

[[File:Fgaddonslogo202x89.png|right]]
To make it easier to create '''addons''' there is since FlightGear 2017.3 a new way to create addons. In essence FlightGear will load an overlay XML into the property tree and start a well known Nasal function.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314620#p314620
|title = <nowiki> Re: New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

We now have a simple way to add addons to FlightGear without the need to mess around with <code>FGData/Nasal</code> or <code>FGHome/Nasal</code> directories.<ref name="Forum_announcement">{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314563#p314563
|title = <nowiki> New Feature: Addon - "API" </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 18th, 2017
}}</ref>

{{TOC limit|3}}

== Installing and using an addon ==
Download and copy the addon to a directory on your computer.

If you use the launcher, select the Add-ons page from the icon bar on the left, then find the section Add-on Module folders and click the Add(+) button. Select the folder where you put the addon. Once the addon is shown in the list, make sure its check box is selected.

Use the command line switch <code>--addon=/path/to/some/addon</code>.<ref name="Forum_announcement"/>

== Creating an addon ==
There is a very simple Skeleton addon available in FGAddon to be used as a template.<ref name="Forum_announcement"/> See {{fgaddon source|path=Addons/Skeleton}}.

A leading slash (<code>/</code>) in this section indicates the base directory of the directory structure of the addon.

=== Minimum configuration ===
An addon may be installed in a directory anywhere on your hard disk and need at least two files:

* <code>/addon-config.xml</code> - A standard [[PropertyList XML files|PropertyList XML file]] to be used to populate or modify the [[property tree]]. (Same as to be used in <code>--config=foo.xml</code>)
* <code>/addon-main.nas</code> - The Nasal hook for the logic. This file needs a function called <code>main()</code> which will be called from the global addon initializer (<code>addons.nas</code>)

=== Additional common files ===
* <code>/addon-metadata.xml</code> - A PropertyList XML file with metadata about the addon it.
* <code>/addon-menubar-items.xml</code> - A PropertyList XML file describing menus to be added to the FlightGear menu bar.
* <code>/gui/dialogs/<my-foobar-dialog>.xml</code> - PropertyList XML files to create custom dialogs.

=== Good to know ===
The new addon mechanism lets you add a <code>addon-config.xml</code> to override the settings in <code>defaults.xml</code> and other files.

That will allow an addon to
* Override key bindings (as in the spoken ATC addon)
* Add or override autopilots and property rules
* Introduce XML state machines

Unless your really want to add/change/remove those at runtime, this should cater for most use cases.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314902#p314902
|title = <nowiki> Re: Spoken </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 23rd, 2017
|added = Jul 23rd, 2017
|script_version = 0.40
}}</ref>

We have some instructions how to use SVN [[FGAddon|in our wiki]]. It covers mostly aircraft development but the workflow is pretty much the same for addons.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314647#p314647
|title = <nowiki> Re: Spoken ATC </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

=== Sound Support ===
Sound support is available using fgcommand's.

See [[Nasal FAQ]] "play-audio-sample"

https://sourceforge.net/p/flightgear/flightgear/ci/5acf2e26d085b7553b2387b9753e9253e8b4bff4

[[Hackathon Proposal:Addon specific Sound Queues]]

== Addon initialization ==
On initialization fgfs takes care of:
* Through {{flightgear source|path=src/Main/options.cxx|text=<code>options.cxx</code>}}:<ref name="Forum_announcement"/>
** Creating a property under <code>/addons/addon[n]/path=/path/to/some/addon</code>
** Loading <code>/path/to/some/addon/addon-config.xml</code> into the property tree (same as <code>--config=/path/to/some/addon/addon-config.xml</code>)
** Adding <code>/path/to/some/addon</code> to the list of allowed directories (same as <code>--fg-aircraft=/path/to/some/addon</code>)
* Through {{fgdata source|path=Nasal/addons.nas|text=<code>addons.nas</code>}}:
** Loading <code>/foo/bar/baz/addon-main.nas</code> into namespace <code>__addon[ADDON_ID]__</code>
** Calling <code>main(addonGhost)</code> from <code>/foo/bar/baz/addon-main.nas</code>.

== Aircraft specific config (addon-hints) ==
Some addons need per-aircraft configuration. While addons should strive to be self-contained (ie. the addon should contain means to
detect different aircraft and apply config from whithin the addon) there is also the possibility for the addon to read so called "addon-hints".

For this, a special property tree exists: <code>/sim/addon-hints/<addon>/...</code>
The tree is expected to be populated from the aircraft.xml file. The addon can then read the properties from a common place regardless of loaded aircraft.

<syntaxhighlight lang="xml">
<sim>
<addon-hints>
<my-addon>
...
</my-addon>
</addon-hints>
</sim>
</syntaxhighlight>

== APIs ==
{{hatnote|For more details about these APIs, see the readme file, {{readme file|add-ons}}.}}
=== C++ API ===
There is a C++ API on FlightGear's side that handle some on the addon related tasks manly through the <code>AddonManager()</code>, <code>Addon()</code> and <code>AddonVersion()</code> classes.

=== Nasal API ===
The Nasal add-on API lives in the 'addons' namespace and can for example do queries to <code>AddonManager()</code> and read data from <code>addons.Addon</code> objects. It can for example compare addon versions if there is dependencies.

See: {{Repo link|site=gitlab|proj=flightgear|repo=fgdata|branch=next|path=Nasal/addons.nas}}

== Background ==
{{See also|Howto:Creating a simple modding framework}}

ATC chatter was removed in 2015, see fgdata commit: [https://sourceforge.net/p/flightgear/fgdata/ci/81607f734e13add9be02816ddaec305d05bc4e47/ 81607f734e13add9be02816ddaec305d05bc4e47]

And the devel list messages referenced in the commit log.
the other relevant commit is this: b60736ba7add2a7cd39af3d8a974d5be3ea46e8b
It would not be very difficult to restore this functionality, or even generalize/improve it significantly (which was the scope of the original discussion on the devel list)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288388#p288388
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

The restored functionality could be distributed as a tarball that is extracted into $FG_ROOT - alternatively, into $FG_HOME, because Nasal files there are treated as overlays, which basically means that you can install user-specific extensions there without having to tamper with $FG_ROOT, it would only take very minor changes to turn the chatter feature into a corresponding "addon" - not unlike fgcamera ...<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=288392#p288392
|title = <nowiki> Re: Whatever happened to radom radio </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Jun 11th, 2016
|added = Jun 11th, 2016
|script_version = 0.40
}}</ref>

We should absolutely stop telling anyone to edit preferences.xml in FG_ROOT; any documentation or advice which says to should be changes ASAP. <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=192632#p192632
|title = <nowiki> Re: NavCache:init failed:Sqlite error:Sqlite API abuse </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Oct 26th, 2013
|added = Oct 26th, 2013
|script_version = 0.40
}}</ref>

As of 12/2017, the addon API is in the process of being significantly updated <ref>https://sourceforge.net/p/flightgear/mailman/message/36146017/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150159/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36150444/</ref>

== List of Addons ==
You can find the official repository at {{fgaddon source|path=Addons}}

* [https://github.com/slawekmikula/flightgear-addon-hudheli Additional Heli HUD's] - ([https://github.com/slawekmikula/flightgear-addon-hudheli/blob/master/doc/manual.md manual]) - encapsulation of HeliHUD package as an addon
* [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere] AI towing aircraft for gliders at every airport.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?t=40742
|title = <nowiki> Re: Aerotow Everywhere </nowiki>
|author = <nowiki> Roman Ludwicki (PlayeRom) </nowiki>
|date = Aug 14th, 2022
|added = Aug 14th, 2022
|script_version = 0.40
}}</ref>
* [https://github.com/SP-NTX/AnotherGUI AnotherGUI] - An add-on that adds a new GUI style.
* ATC Chatter (ported by Torsten) {{progressbar|100}}
* [[Cargo Towing Addon]] <ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?t=36824
|title = <nowiki> Re: Cargo Towing Addon </nowiki>
|author = <nowiki> Wayne Bragg (wlbragg) </nowiki>
|date =
|added =
|script_version = 0.40
}}</ref>
* cockpit-view (work in progress by wkitty42)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316498#p316498
|title = <nowiki> Re: </nowiki>
|author = <nowiki> wkitty42 </nowiki>
|date = Aug 13th, 2017
|added = Aug 13th, 2017
|script_version = 0.40
}}</ref>
* [[Earthview#Customization]] - High resolution customization
* [[FaceTrackNoIR]] (ported by HHS)<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36454826/
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Unknown, HHS</nowiki>
|date = Nov 1th, 2018
}}</ref> - An addon to interface this [[Head tracking|head tracker]] with FlightGear
* [https://forum.flightgear.org/viewtopic.php?f=5&t=24792 Fencemaker] (Eases creating Fence-like scenery objects. Originally by VaLeo, converted to an addon by sfr) - ([https://www.mediafire.com/file/cf0la63v9g352md/fencemaker_addon.zip/file download])<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=5&t=24792&start=45#p390066
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Stefan Frank </nowiki>
|maintainer = <nowiki> Stefan Frank </nowiki>
|date = Aug 8th, 2021
}}</ref>
* [https://github.com/PlayeRom/flightgear-addon-fgcamera FGCamera] - ([https://github.com/PlayeRom/flightgear-addon-fgcamera/blob/master/Docs/manual.md manual]) - [[FGCamera | Wiki Page]]
* [[FGPlot]]
* [[Ground Services]] (ported by ThomasS)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316400#p316400
|title = <nowiki> Re: </nowiki>
|author = <nowiki> ThomasS </nowiki>
|date = Aug 12th, 2017
|added = Aug 12th, 2017
|script_version = 0.40
}}</ref>
* {{fgaddon source|path=Addons/Headtracker/|text=Headtracker addon}} Helps integrate FaceTrackNoIR and opentrack with FlightGear.
* [[HighAirTrader]] An in-sim mini game in which you transport goods to different airports.
* [https://github.com/tdammers/fg-hoppie-acars Hoppie ACARS client] - connect to [http://www.hoppie.nl/acars Hoppie's ACARS], used on VATSIM and other networks.
* [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/Illuminator/ Illuminator] - configure lights attached to 3D models (e.g. taxi light, landing light or a light attached to a scenery model like a light pole) at runtime.
* [https://github.com/slawekmikula/flightgear-addon-protocolkml KML Exporter (Google Earth)] - ([https://github.com/slawekmikula/flightgear-addon-protocolkml/blob/master/doc/manual.md manual])
* [[Landing Rate addon]] [https://forum.flightgear.org/viewtopic.php?f=6&t=33101&p=327787#p327787]
* [https://github.com/slawekmikula/flightgear-addon-linuxtrack LinuxTrack Head Tracker integration] - ([https://github.com/slawekmikula/flightgear-addon-linuxtrack/blob/master/doc/manual.md manual])
* [https://github.com/slawekmikula/flightgear-addon-littlenavmap LittleNavMap integration] - ([https://github.com/slawekmikula/flightgear-addon-littlenavmap/blob/master/doc/manual.md manual])
* [https://github.com/PlayeRom/flightgear-addon-logbook Logbook] all your flights to CSV file.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?t=41070
|title = <nowiki> Re: Logbook Add-on </nowiki>
|author = <nowiki> Roman Ludwicki (PlayeRom) </nowiki>
|date = Dec 11th, 2022
|added = Dec 11th, 2022
|script_version = 0.40
}}</ref>
* [https://gitlab.com/mdanil/flightgear-hax mdanilov hax!]: landing evaluation and aircraft development tools, TerraSync toggler
* [[Model Cockpit View]]
* [https://github.com/SP-NTX/MPChatImprovments MPChatImprovments] Multi-key commands for Multiplayer, new features for chat,...
* [[Oscilloscope addon]] - Allows displaying a property of Nasal function over time
* [[PAR instrument]] - Precision Approach Radar and Ground Controlled Approach
* [[Red Griffin ATC]] - Speaking Air Traffic Controller<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?f=6&t=36755
|title = <nowiki> Re: </nowiki>
|author = <nowiki> RedGriffin </nowiki>
|date = Jan 6th, 2020
|added = Jan 6th, 2020
|script_version = 1.0.0 RC2
}}</ref>
* [https://github.com/tdammers/fg-simbrief-addon SimBrief import] - Import flightplans, weights, fuel, and winds alof, from SimBrief.
* [[Spoken ATC]] (ported by Torsten)<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=314095#p314095
|title = <nowiki> Re: </nowiki>
|author = <nowiki> Torsten </nowiki>
|date = Jul 10th, 2017
|added = Jul 10th, 2017
|script_version = 0.40
}}</ref>
* [[Spoken GCA]] - An offline ground controlled approach (GCA) addon
* [[Log time-stamper add-on]] - Will print simulated UTC time, real local time, and/or real UTC time time-stamps at configurable intervals to the console and log.
* [https://gitlab.com/mdanil/flightgear-mickey Tiny HUD for mouse flying in FlightGear] - Visual feedback for mouse flying, to make up for mouse's lack of self-centering
* [https://github.com/slawekmikula/flightgear-addon-vfrflight VFRFlight integration] - ([https://github.com/slawekmikula/flightgear-addon-vfrflight/blob/master/doc/manual.md manual])
* [https://github.com/slawekmikula/flightgear-addon-vfrnavigator VFR Flying Helper] - ([https://github.com/slawekmikula/flightgear-addon-vfrnavigator/blob/master/doc/usage.md manual])
* [[YASim Development Tools]] (by jsb)
* [https://github.com/hbeni/fgfs-noGroundDamage noGroundDamage] - Addon to temporarily disable damage after landing and for ground operations for the c172/c182

== Experimental Addons ==

Addons which are in the development stage/unfinished but can be used as a quick view of addon functionality
* [https://github.com/slawekmikula/flightgear-addon-missions FlightGear Missions addon] - Add-on for missions/adventures code

== Ideas ==
=== Hooking into features using legacy OpenGL code ===
{{See also|Unifying the 2D rendering backend via canvas}}
In 09/2018, James suggested that legacy features using raw OpenGL calls (e.g. HUD/2D panels) could be easily replaced via scripted Canvas/Nasal solutions at the mere cost of providing a mechanism to hook into the legacy code implementing these features (namely, the HUD/instrumentation subsystems) <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/36399261/</ref>

=== Catalog & Package Manager support ===
if this works with more complex, pre-existing addons such as [[Bombable]], where the file layout is a replica of the old FGData layout, these types of mature addons might be better as SourceForge FlightGear sub-projects rather than being copied into FGAddon. Maybe the config file and nasal script could be used to automate the installation process ?<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953179/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>
The [[Bombable]] addon is one of the most popular addons out there, and a large number of aircraft in FGAddon have bombable support, so it is worth not forgetting about. Especially if the addon system one day becomes automated through a [[Catalog metadata|catalog.xml type system]]<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35953650/
|title = <nowiki> Re: [Flightgear-devel] Simple API for creating FlightGear
addons/plugins </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Jul 19th, 2017
|added = Jul 19th, 2017
|script_version = 0.40
}}</ref>

== References ==
{{Appendix}}

== Related content ==
=== Wiki articles ===
* [[FG Add-on FAQ]]
* [[Modules.nas]]
* [[FlightGear configuration via XML]]
* [[FlightGear configuration via XML#preferences.xml]]
* [[Nasal]]
* [[Property tree]]
* [[Properties persistent between sessions]]
* [[PropertyList XML File]]

=== Forum topics ===
* {{forum link|t=32561|title=New Feature: Addon - "API"}}

=== Readme files ===
* {{readme file|add-ons}}
* {{readme file|gui}} - Details on how to add menus and custom dialogs.

=== Source code ===
==== FGAddon ====
* {{fgaddon source|path=Addons/Skeleton}} - Skeleton addon to be used as a template.

==== FGData ====
* {{fgdata source|path=Nasal/addons.nas}}

==== FlightGear ====
* {{flightgear source|path=src/Main/options.cxx}}
* {{flightgear source|path=src/Add-ons/}}

[[Category:FlightGear addons| ]]

FlightGear Newsletter February 2025

2025-02-21T07:59:24Z

Hbeni: Newsletter creation, automatic preload from here

{{User:Skybike/Template:Newsletter-header-translate|2025-02}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==


* Comm radio instrument enhanced
** The configuration got a new optional setting in [[Instrumentation#Comm_Radio|instrumentation.xml]] to allow setting it to full-/half-duplex mode. In half-duplex mode, the radio will not receive (Atis, ...) when PTT is set to 1 (like when using FGCom). In 2024.1 this still defaults to "full-duplex", but in next this will change to the more sane half-duplex mode. This is chaneable also at runtime. Aircraft devs are only needing to get active if they want half-duplex in 2024.1, or if they simulate a full-duplex capable radio.
** The radio will expose a new runtime flag: <code>/instrumentation/comm[n]/receiving-flag</code> that is <code>true</code> when the device receives something (currently only ATIS/AWOS, also depending on the full-duplex mode and PTT).




== In the hangar ==









== Scenery corner ==
















== Help wanted ==
{{Help wanted}}

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2025 02]]

Instrumentation

2025-02-21T07:50:02Z

Hbeni: /* Comm Radio */

FlightGear's built-in '''Instrumentation system''' simulates basic instruments used in many aircraft and provide their output as [[Property|Properties]] to be used e.g. for [[Howto:Animate models|animating]] 3D instruments or [[Canvas]] instruments.

This article is meant to provide an overview over the instrumentation modules available and their configuration.

=== General configuration ===
The instrumentation modules to be available to an aircraft can be selected by the aircraft developer using an instrumentation XML configuration file. This file is called from the [[Aircraft-set.xml]]:<syntaxhighlight lang="xml">
<sim>
<instrumentation>
<path>Systems/my-aircraft-instrumentation.xml</path>
</instrumentation>
</sim>
</syntaxhighlight>A generic configuration file to be copied and customised can be found in Aircraft/Generic/generic-instrumentation.xml.

===== Common Elements =====
Instrument Root Path: typically '''/instrumentation/name[number]/''' e.g. '''/instrumentation/adf[1]/''' for the second ADF.

Electric Power Path (where applicable): typically '''/systems/electrical/outputs/name[number]''' e.g. '''/systems/electrical/outputs/comm[0]''' for the first comm radio.
{| class="wikitable"
|name
|typically used for the instrument's root path and, where applicable, electric power path
|-
|number
|used to differentiate between multiple objects using the same name.
|}
All instruments that inherit '''AbstractInstrument''' additionally accept the following config settings:
{| class="wikitable"
|power-supply
|custom property to be used as the electric power path
|-
|minimum-supply-volts
|minimum electric voltage at which the instrument works
|}

=== Instrument Modules ===

====[[ADF|ADF (Automatic Direction Finder)]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/adf.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/adf.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
This instrument simulates an [[ADF|Automatic Direction Finder]] used for navigating using [[NDB|Non-Directional Beacons]].

'''Configuration'''<syntaxhighlight lang="xml">
<adf>
<name>adf</name>
<number>0</number>
</adf>
</syntaxhighlight>

====[[Airspeed|Airspeed Indicator]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/airspeed_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/airspeed_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<airspeed-indicator>
<name>airspeed-indicator</name>
<number>0</number>
<total-pressure>/systems/pitot/total-pressure-inhg</total-pressure>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<has-overspeed-indicator>0</has-overspeed-indicator>
<pressure-alt-source>/instrumentation/altimeter/pressure-alt-ft</pressure-alt-source>
<ias-limit>248.0</ias-limit>
<mach-limit>0.48</mach-limit>
<alt-threshold>13200</alt-threshold>
</airspeed-indicator>
</syntaxhighlight>

*Total Pressure: see [[FGproperties/Systems/Pitot]]
*Static Pressure: see [[FGproperties/Systems/static]]
*see also: {{Repo link|repo=fgdata|pre=$FG_ROOT|path=Docs/README.airspeed-indicator}}

====[[Altimeter]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/altimeter.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/altimeter}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<altimeter>
<name>altimeter</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<quantum>0</quantum>
<tau>0</tau>
</altimeter>
</syntaxhighlight>

*Static Pressure: see [[FGproperties/Systems/static]]
*Quantum: TODO
* Tau: TODO

====[[Attitude indicator|Attitude Indicator (suction-powered)]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator>
<name>attitude-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.5</minimum-vacuum>
<limits>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</limits>
<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</attitude-indicator>
</syntaxhighlight>

* Note, the <code><minimum-vacuum></code>, <code><gyro></code> and <code><limits></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.
*Suction: see [[Aircraft systems#Vacuum]]

====Attitude Indicator (Electric)====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator_electric.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator_electric.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator-electric>
<name>attitude-indicator</name>
<number>0</number>


<config>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</config>
</attitude-indicator-electric>
</syntaxhighlight>

==== Clock ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/clock.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/clock.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<clock>
<name>clock</name>
<number>0</number>
</clock>
</syntaxhighlight>

==== Comm Radio ====
{| class="wikitable"
|Source File
|{{Repo link|site=gitlab|proj=flightgear|repo=flightgear|branch=next|path=src/Instrumentation/commradio.cxx}}
|-
|Header File
|{{Repo link|site=gitlab|proj=flightgear|repo=flightgear|branch=next|path=src/Instrumentation/commradio.hxx}}
|-
|extends
|{{Repo link|site=gitlab|proj=flightgear|repo=flightgear|branch=next|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<comm-radio>
<name>comm</name>
<number>0</number>
<eight-point-three>0</eight-point-three>
<full-duplex>0</full-duplex>
</comm-radio>

</syntaxhighlight>

* <code>eight-point-three</code>: Setting this to <code>1</code> (true) enables a simulation of the newer 8.33 kHz frequency raster
* <code>full-duplex</code>: set this to <code>1</code> to enable full duplex mode. In half-duplex mode, receiving will be disabled if <code>ptt</code> property is <code>1</code>. (Introduced in 2024.1 with default=1; after that default=0, so this usually is not needed to be set manually)
* see also [[Kx165]]

==== DCL GPS ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dclgps.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dclgps.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Information (from Source Code)'''<syntaxhighlight lang="c++">
// dclgps.cxx - a class to extend the operation of FG's current GPS
// code, and provide support for a KLN89-specific instrument. It
// is envisioned that eventually this file and class will be split
// up between current FG code and new KLN89-specific code and removed.
</syntaxhighlight>

==== [[Distance measuring equipment|DME (Distance Measuring Equipment)]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dme.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dme.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<dme>
<name>dme</name>
<number>0</number>
</dme>
</syntaxhighlight>

==== [[Global Positioning System|GPS (Global Positioning System)]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gps.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gps.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gps>
<name>gps</name>
<number>0</number>
</gps>
</syntaxhighlight>

==== GSDI/GSDA (Ground Speed Drift Angle Indicator) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gsdi.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gsdi.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gsdi>
<name>gsdi</name>
<number>0</number>
</gsdi>
</syntaxhighlight>This instrument configuration is not included in generic-instrumentation.xml. See the [[EC130]] for an aircraft implementing this instrument.

==== [[Avionics and instruments#Directional Gyro|Heading Indicator (Directional Gyro)]] ====

This is a realistic and highly configrable directional gyro based heading indicator. It can be either electrical or
suction driven and supports the gyro based errors like precession drift and transport wander.

{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_dg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_dg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}

'''Configuration'''

By default, the instrument is electrically driven and powered by '''/systems/electrical/outputs/DG[number]''' (for backwards-compatibility reasons)
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
</heading-indicator-dg>
</syntaxhighlight>

Like with most other electrically driven instruments you can explicitely set the power source:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<power-supply>/systems/electrical/outputs/heading-indicator</power-supply>
<minimum-supply-volts>12.0</minimum-supply-volts>
</heading-indicator-dg>
</syntaxhighlight>

To make it vacuum driven instead:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.0</minimum-vacuum> 
</heading-indicator-dg>
</syntaxhighlight>

You can optionally configure the instruments error behaviour and limits (to disable, set accordingly).
The defaults given in c++ are for demonstration and not realistic so these might be better:
<syntaxhighlight lang="xml">
<limits>
<yaw-limit-rate>11.5</yaw-limit-rate> 
<g-limit-lower>-0.8</g-limit-lower> 
<g-limit-upper>1.8</g-limit-upper> 
<yaw-error-factor>0.033</yaw-error-factor> 
<g-error-factor>0.033</g-error-factor> 
<g-limit-tumble-factor>1.5</g-limit-tumble-factor> 
<g-node>/accelerations/pilot-gdamped</g-node> 
<g-filter-time>10.0</g-filter-time> 
<yaw-rate-source>/orientation/yaw-rate-degps</yaw-rate-source> 
</limits>
<gyro>
<minimum-spin-norm>0.8</minimum-spin-norm> 
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
<heading-source>/orientation/heading-deg</heading-source> 
</syntaxhighlight>

The instrument has a built-in damping filter for the g-node, so spikes do not trigger tumbling. If tuning this is not sufficient, you can specify a custom source property.

'''Runtime configuration'''
The limits and gyro config are exposed to the instruments propoerty tree and can be changed at runtime.

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>caged-flag</code>
|Make the gyro caged. Use this to quickly stop tumbling (or prevent it in the first instance).
|-
|<code>align-deg</code>
|Should be used by the instruments model to rotate the disc, countering instrument errors.
|-
|<code>latitude-nut-setting</code>
|Set to the factory setting. At the nut's latitutde (<code>-90</code> to <code>90</code>) the precession by earths rotation is countered by a small weight on the gimbal.
|}

====[[Avionics and instruments#Directional Gyro|Heading Indicator (Electric Flux-Gate Compass)]]====
The flux-gate heading indicator always points to magnetic north automatically.

{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_fg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_fg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator-fg>
<name>heading-indicator-fg</name>
<number>0</number>
</heading-indicator-fg>

</syntaxhighlight>

* Powered by '''/systems/electrical/outputs/heading-indicator-fg[number]'''

==== Heading Indicator (Suction-Driven) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading-indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading-indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
</heading-indicator>
</syntaxhighlight>

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>offset-deg</code>
|Read/write; Gyro drift is reflected in this property, and can be countered by altering the value. If not initialized at instrument init time, will be synced to "/environment/magnetic-variation-deg" automatically.
|}

* Note, this is an unrealistic/simple instrument. For better realism options, you should use the "Heading Indicator (Directional Gyro)", see above.

* Suction: see [[Aircraft systems#Vacuum]]

==== King KR 87 Digital ADF (Automatic Direction Finder) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/kr_87.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/kr_87.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<KR-87>
<name>kr-87</name>
<number>0</number>
</KR-87>
</syntaxhighlight>

==== [[Avionics and instruments#Compass|Magnetic Compass]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mag_compass.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mag_compass.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<magnetic-compass>
<name>magnetic-compass</name>
<number>0</number>

<deviation>
<table>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>30</ind>
<dep>3</dep>
</entry>

<entry>
<ind>330</ind>
<dep>-2</dep>
</entry>
</table>
</deviation>
</magnetic-compass>
</syntaxhighlight>

* Deviation Table: This can be used to simulate [[Avionics and instruments#Magnetic deviation|Magnetic deviation]], e.g. to reflect what's written on a textured deviation card next to the compass. Can also be a property that is beeing read and dynamically calculated (<code><deviation>/instrumentation/magnetic-compass/deviation-deg</deviation></code>), for example to implement powered avionics influencing the magnetic field.

By default the compass simulates a fixed axis compass disc pitched at 0°. A pitched compass disc has an additional reading error.
The compass property tree exposes a <code>/instrumentation/magnetic-compass/pitch-offset-deg</code> prop that can be set to a fixed pitch angle to simulate pitched mounts or manually pitchable compass casings. By dynamically calculating the property, you can offset the plane's <code>/orientation-pitch-deg</code>, essentially nulling the effect. By adding some filters you can simulate a freely pitchable compass disc for a constrained pitch angle; that is: a compass disc mounted on a pivot-pin bearing (like most modern compasses feature). For an example see the [https://github.com/c172p-team/c172p/blob/a8bc43674af51cfe093c03ae21e2e84467b456fb/Systems/instruments.xml#L599-L802 filter implementation from the C172p].

The instrument exposes <code>pitch-deg</code> and <code>roll-deg</code> properties to simulate pitching and rolling of the compass disc based on flight forces and fluid viscosity.
You can use them in your 3D-models animation configs.

The damping can be adjusted by setting it in the instrumentation.xml config:
<code><fluid-viscosity type="double">8.2</fluid-viscosity></code> (8.2 mm²/s is the value of kerosene and should be good in most cases).

==== [[Radio beacons#Marker beacons|Marker Beacon]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/marker_beacon.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/marker_beacon.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<marker-beacon>
<name>marker-beacon</name>
<number>0</number>
</marker-beacon>
</syntaxhighlight>

==== [[Ground proximity warning system|MK-VIII]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mk_viii.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mk_viii.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<mk-viii>
<name>mk-viii</name>
<number>0</number>
</mk-viii>
</syntaxhighlight>For more information, see [[Ground proximity warning system]].

==== Master Reference Gyro ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mrg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mrg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<master-reference-gyro>
<name>master-reference-gyro</name>
<number>0</number>
</master-reference-gyro>
</syntaxhighlight>for more information, see [https://scottbouch.com/mcfs/lightningt5t55/docs/ap101b-1003-5-6-15a-part1-chap7-al2-nov84-instruments.pdf Lightning T Mk.5 Instruments PDF, p. 4f.]

==== Navigation Radio ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/navradio.cxx}},{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/newnavradio.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/navradio.hxx}},{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/newnavradio.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<nav-radio>
<name>nav</name>
<number>0</number>
</nav-radio>
</syntaxhighlight>

==== Radar Altimeter ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/rad_alt.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/rad_alt.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<radar-altimeter>
<name>radar-altimeter</name>
<number>0</number>
<update-interval-sec>0.1</update-interval-sec>
</radar-altimeter>
</syntaxhighlight>

==== [[Avionics and instruments#Turn Coordinator|Slip/Skid Ball]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/slip_skid_ball.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/slip_skid_ball.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<slip-skid-ball>
<name>slip-skid-ball</name>
<number>0</number>
</slip-skid-ball>

</syntaxhighlight>

==== [[Tactical Air Navigation|TACAN]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tacan.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tacan.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<tacan>
<name>tacan</name>
<number>0</number>
</tacan>
</syntaxhighlight>

==== [[Traffic alert and collision avoidance system|TCAS]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tcas.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tcas.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
For '''configuration''', see [[Traffic alert and collision avoidance system#Instrument List]]

==== [[Transponder]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/transponder.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/transponder.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<mode type="int">1</mode>
<auto-ground type="string">/gear/gear/wow</auto-ground>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<airspeed-path type="string">/instrumentation/airspeed-indicator/indicated-speed-kt</airspeed-path>
<mach-path type="string">/instrumentation/airspeed-indicator/indicated-mach</mach-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
</transponder>
</syntaxhighlight>

* Mode
** 0 = Mode A
** 1 = Mode C
** 2 = Mode S
* Auto-Ground: Set property to be used to detect when the ground-bit (mode-S only) should be set
* Encoder/Airspeed/Mach Path: Set instrument properties to feed the transponder
* '''for more information, see [[Transponder]].'''

==== [[Avionics and instruments#Turn Coordinator|Turn Indicator]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/turn_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/turn_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<turn-indicator>
<name>turn-indicator</name>
<number>0</number>

<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</turn-indicator>
</syntaxhighlight>

* Note, the <code><gyro></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.

==== Vertical Speed Indicator (VSI) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/vertical_speed_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/vertical_speed_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<vertical-speed-indicator>
<name>vertical-speed-indicator</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
</vertical-speed-indicator>
</syntaxhighlight>

* Static Pressure: see [[FGproperties/Systems/static]]

Aircraft properties reference/Instrumentation/COMM

2025-02-19T16:24:51Z

Hbeni:

Full documentation: [[Aircraft properties reference]]<pre>
/instrumentation/comm[%d]/add-noise
/instrumentation/comm[%d]/airport-id
/instrumentation/comm[%d]/atis
/instrumentation/comm[%d]/channel-button
/instrumentation/comm[%d]/chanel-mode-selector
/instrumentation/comm[%d]/cutoff-signal-quality
/instrumentation/comm[%d]/frequencies
/instrumentation/comm[%d]/frequencies/dial-khz
/instrumentation/comm[%d]/frequencies/dial-mhz
/instrumentation/comm[%d]/frequencies/selected-channel
/instrumentation/comm[%d]/frequencies/selected-channel-width-khz
/instrumentation/comm[%d]/frequencies/selected-mhz
/instrumentation/comm[%d]/frequencies/selected-mhz-fmt
/instrumentation/comm[%d]/frequencies/selected-real-frequency-mhz
/instrumentation/comm[%d]/frequencies/standby-channel
/instrumentation/comm[%d]/frequencies/standby-channel-width-khz
/instrumentation/comm[%d]/frequencies/standby-mhz
/instrumentation/comm[%d]/frequencies/standby-mhz-fmt
/instrumentation/comm[%d]/frequencies/standby-real-frequency-mhz
/instrumentation/comm[%d]/frq-swap-btn
/instrumentation/comm[%d]/height-above-station-ft
/instrumentation/comm[%d]/operable
/instrumentation/comm[%d]/power-btn
/instrumentation/comm[%d]/ptt
/instrumentation/comm[%d]/full-duplex
/instrumentation/comm[%d]/receiving-flag
/instrumentation/comm[%d]/servicable
/instrumentation/comm[%d]/signal-quality-norm
/instrumentation/comm[%d]/slant-distance-m
/instrumentation/comm[%d]/station-name
/instrumentation/comm[%d]/station-type
/instrumentation/comm[%d]/test-btn
/instrumentation/comm[%d]/track-distance-m
/instrumentation/comm[%d]/true-bearing-from-deg
/instrumentation/comm[%d]/true-bearing-to-deg
/instrumentation/comm[%d]/volume
/instrumentation/comm[%d]/volume-selected
</pre>

Since FGFS 2024.1 the radios can be configured to be full- or half-duplex. This is done either by runtime setting of the property, or by specifying <full-duplex> in the <comm> section of instrumentation.xml. Half duplex radios will be mute when PTT is on. The new receiving-flag will be false in that case.
For historic reasons, the full-duplex flag is TRUE in 2024.1, but this default will be changed to half-duplex for subsequent releases.

Aircraft properties reference/Instrumentation/COMM

2025-02-19T16:21:06Z

Hbeni: Added full-duplex and receiving-flag (see https://gitlab.com/flightgear/flightgear/-/merge_requests/55)

De/FGCom-mumble

2025-02-15T12:44:45Z

Hbeni: /* Bekannte Inkompatibilitäten */

'''FGCom-mumble''' simuliert Funkkommunikation basierend auf der freien VoIP software [https://www.mumble.info/ Mumble]. Es integriert sich vollstädnig mit den Funkgeräten deines Flugzeuges in FlightGear und erlaubt dir, mit anderen Piloten und Fluglotsen auf realistische Weise zu kommunizieren. Dafür simuliert es ein lückenloses Radiowellenspektrum.

FGCom-mumble ist eine Alternative zum altbekannten [[FGCom]] sowie [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble nutzt den Pluginmechanismus, der in Mumble 1.4.0 verfügbar wurde und benötigt lediglich ein vorkompiliertes Plugin, das von einem ganz normalen Mumble-Programm geladen wird. Das aktuellste Release kannst du hier herunterladen: https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Server ==

* Der FGCom-mumble test server ist <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
* Die Statusseite für diese Instanz, die alle verbundenen Clients anzeigt, ist hier: https://fgcom-dev.hallinger.org/
* Der mumble-testserver benutzt ein autoerneuerndes SSL-Zertifikat von Lets Encrypt.

== Hauptziele des Projektes ==
* Bereitstellen von Kommunikation, die sowohl örtlich als auch kanaltechnisch getrennt ist
* Realistische Funkkommunikation
* Einfachheit in der Installation und Benutzung
* Unterstützung für beliebige Frequenzen
* ATIS Aufnahme und Wiedergabe
* Zivile Radiostationen sollen unterstützt werden
* Festnetz/Intercom Unterstützung
* RDF-Signale für Clients
* Einfach auf einem Server zu installieren und zu betreieben
* Unabhängigkeit von Simulatoren wie z.B. Flightgear
* Fähigkeit, in FlightGear integriert zu werden, mit der Option, weitere Clients und Applikationen zu unterstützen (ATC, aber auch andere Flugsimulatoren)
* Modularer Aufbau, damit einzelne Komponenten unterschiedlich implementiert werden können und einfache Erweiterbarkeit besteht
* Gute und vollständige Dokumentation

== Installation and Einrichtung ==
Die aktuelle Version kann hier heruntergeladen werden: [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] bietet auch eine Debug-Variante an).

Die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#installation--einrichtung-des-mumble-plugins README] bietet detaillierte Angaben zur Installation.

Jemand hat sogar ein Video (engl.) von der Installation gemacht! :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk

Zusammengefasst:
* Du brauchst ein installiertes und eingerichtetes Mumble >= 1.4, und dann lade darin das Plugin (unter mumble Einstellungen/plugins)
* Auf dem Mumbleserver (Version >= 1.4.0) trittst du einem Channel bei, dessen Name mit `fgcom-mumble` beginnt
* Im FlightGear-Launcher fügst du im Addon-Tab den `fgfs-addon` Ordner der FGCom-Mumble Veröffentlichung hinzu
* Starte FlightGear und benutze deine Funkgeräte (du funkst mit den ganz normalen FGCom-Tastenkombinationen; siehe unten)

== Benutzung ==
FlightGear's FGCom-mumble Protokoll benutzt die normalen FGCom-Tastenkombinationen:
* Um auf COM1 zu funken, drückst du {{Key press|Space}}. Solange du überträgst, kannst du keine anderen Piloten durch das verwendete Funkgerät hören (diese sind Halbduplexgeräte).
* COM2 sendet mit {{Key press|Shift|Space}}.
* Seit FGCom-mumble 1.2.0:
** Mit COM3 funkst du über {{Key press|Alt|Space}} (früher musstest du ein eigenes Keybind definieren),
** Intercom sendet in full-duplex mit {{Key press|Ctrl|Space}}

Jedes Funkgerät kann außerdem über die COMBar benutzt werden (öffnen über ''Menu/Multiplayer/FGCom-mumble'').

Um FGCom-mumble ohne FlightGear zu probieren, kannst du auch die im Release mitgelieferte RadioGUI starten.

=== Deine Installation testen ===
Als erstes solltest du sicherstellen, dass mumble an Sich gut funktioniert und du gut zu verstehen bist sowie andere gut verstehst.
Dazu deaktivierst du am Besten das Plugin oder du sprichst mit anderen auf einem Channel, der nicht mit `fgcom-mumble`beginnt.

Das Plugin verändert Mumbles eingehende Audiopakete. Es fügt statisches Rauschen hinzu, das von der simulierten Funksignalstärke abhängt oder hebt den stream sogar auf, wenn der Funksender außerhalb der Reichweite liegt. Ausgehende Audiopakete werden nicht verändert.

Falls der Server es unterstützt, kannst du auch einen traditionellen Echo-Test machen (dazu muss am Server ein `fgcom-recorder-bot` laufen). Funke auf der Frequenz `910.00` MHz und der Recorderbot wird mit der Aufzeichnung beginnen (er schreibt das in den mumble-chat) und nach Abschluss einen bot an deiner Position erzeugen, der das aufgenommene auf der Frequenz wiedergibt. So kannst du dich selbst hören, wie andere dich hören würden.

=== Fehlerbehebung ===

Schau bitte in die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#fehlerbehebung README] des Projekts. Diese hat detaillierte Informationen hierzu.

Solange es nichts grundlegendes mit der Installation zu tun hat, hilft oft auch einfach ein Neustart von Mumble (das Plugin initialisiert sich selbständig frisch).

=== Kompatibilität ===
FGCom-mumble unterstützt grundsätzlich das alte FGCom-UDP-Protokoll und sollte somit kompatibel mit allen clients sein, die dieses verwenden (z.B. ältere ATCpie oder OpenRadar Versionen). Allerdings gibt es auch ein paar Erweiterungen, die mit dem alten Protokoll nicht zur Verfügung stehen.

* FlightGear wird durch ein [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon] unterstützt. Dieses erwartet die Standard-Funkgerätimplementierung (und funktioniert getestet zumindest mit der C172p und der C182S).
*[[ATC-pie]] hat eine integrierte Unterstützung (prüfe, ob "FGCom-mumble" anstelle von nur "FGCom" in den Einstellungen aktiviert ist).
*[[OpenRadar]] Unterstützt im Moment nur COM1 ([https://sourceforge.net/p/openradar/tickets/5/ Ticket dazu ist offen]). Für COM2 und weitere musst du entweder separate Mumble-Instanzen öffnen oder FGCom-mumble's RadioGUI zum Funken benutzen.
:Es gibt eine gepatchte Version von OpenRadar mit integriertem FGCom-mumble sowie 8.33 Channelmodus; verfügbar hier: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

==== Bekannte Inkompatibilitäten ====
* Das alte FGCom aktiviert sich selbständig, wenn du mit dem Mehrspielernetzwerk verbunden bist und dann die "FGCom"-Einstellungen (anstelle des "FGCm-Mumble"-Eintrags) aus dem Mehrspielermenü aufrufst. Wenn du mit aktiviertem alten FGCom PTT aktivierst, kann FlightGear abstürzen.
* Das FlightGear UFO belegt {{Key press|Space}} selbst, sodass du nicht Funken kannst. Als workaround kannst du die COMBar benutzen, die mit dem FGFS Addon mitkommt.
* FGFS version <= 2020.3 ist nicht mit FGCom-mumble addon version >= 1.3.0 kompatibel. Es wird 1.2.0 benötigt.

== RadioGUI ==
Die RadioGUI ist eine kleine Java8 Applikation, die einen FGCom-mumble client implementiert und Funkgeräte bereitstellt. Sie sendet die notwendigen UDP Nachrichten an das Mumble plugin.

In der GUI kannst du deinen Standort über eine Karte auswählen und dann deine Funkgeräte einstellen und testen.
Damit kannst du auch komplett mit allen Funktionen am simulierten Funknetz teilnehmen, ohne FlightGear zu starten.

== Serverseite ==
Konzeptionell benötigst du als Minimum einfach einen Standard Mumbleserver (Version 1.4.0 oder höher), auf dem ein Channel eingerichtet wird, der mit `fgcom-mumble` beginnt. Das ist bereits genug, damit das Plugin Clientseitig den Rest erledigen kann. Der komplette Channel wird als einzelnes, weltumspannendes, kontinuierliches Radiowellenspektrum behandelt.

Weitere Funktionen werden über Lua-Bots implementiert (die auch auf einer anderen Maschine laufen können):
* ATIS Aufzeichnung udn Wiedergabe
* Radioprogramm Wiedergabe (OGG Wiedergabe auf einer beliebigen Funkfrequenz), z.B. nutzbar für eigene NDBs mit Morsecode ([https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons])
* Statusseite Datensammlung

Eine Statusseite fürs WWW ist als PHP-Seite implementiert, die die notwendigen Daten über den `fgcom-status-bot` bereitgestellt bekommt.

Detaillierte Installations- und Betriebsdokumentation ist in den Veröffentlichungen enthalten, aber auch [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server-de_DE.md online] im Projekt zugänglich.

== Wie funktiooniert das alles? (technische Information) ==
Die technischen Details sind in den verschiedenen Readme-Dateien im Projekt dargelegt (zum Start empfielt sich [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Zusammengefasst treten alle Teilnehmer einem einzigen Mumble-Channel bei und laden das fgcom-mumble Plugin. Das Plugin tauscht alle notwendigen Daten zwischen den Nutzern aus (Funkgeräte, Frequenzen, Standort, etc.) und basierend auf diesen Informationen werden die eingehenden Audioströme der anderen Nutzer entweder abgespielt oder stummgeschaltet. Für mehr Realismus werden abgespielte Audioströme mit Statischem Rauschen und weiteren Effekten unterlegt.
Aufgrund der Stummschaltefunktion abhängig von der Funkreichweite besteht eine unmittelbare Separierung nach Funkkanal und Standort, was allen Nutzern erlaubt, in ein und demselben Mumblekanal zu sein.

== Weiterführender Inhalt ==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] mit weiteren Tipps/Hinweisen
*[https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md FGCom-mumble README-de_DE.md] Haupt-Readme des Projektes mit allen Details, die du schon immer wissen wolltest

=== Forum topic ===
* Der {{forum link|t=37644|title=FGCom-mumble}} Forumshtread hat Entwicklungsrelevante Informationen und dient zur allgemeinen Diskussion
* {{forum link|p=374950|title=Re: EDDF-Triangle}} und {{forum link|p=374970|title=Re: EDDF-Triangle}} - behandeln Details zu Kompatibilität und Unterschieden zwischen FGCom, FGCom-mumble und Mumble

=== FlightGear Newsletter ===
*[[FlightGear_Newsletter_June_2020]]: Erster Prototyp angekündigt
*[[FlightGear_Newsletter_July_2020]]: Lasttests erfolgreich, RDF implementiert, Live-Status Seite hinzugefügt
*[[FlightGear_Newsletter_August_2020]]: Mehr tests, neue HF/VHF/UHF modelle, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API änderungen, verteilte Installation, Konfigurationsmöglichkeit per INI-Datei, Statistiken
*[[FlightGear_Newsletter_October_2020]]: Weitere API änderungen, realistische Simulation der 8.33kHz/25kHz Kanalüberlappung, RadiGUI hinzugefügt
*[[FlightGear_Newsletter_November_2020]]: Test server angekündigt
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringt Netzwerkfunktionen
*[[FlightGear_Newsletter_April_2021]]: RDF Implementierung umgebaut, 0.12.0 angekündigt, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Bessere Unterstützung von Airliners, 0.13.0 and 0.14.0 angekündigt, Releasepaket neustrukturiert
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 angekündigt, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 angekündigt, updater bugfixes Teil II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 veröffentlicht, Mumble 1.4 wurde veröffentlicht'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[en:FGCom-mumble]]

FGCom-mumble

2025-02-15T12:44:10Z

Hbeni: /* Compatibility */

'''FGCom-mumble''' simulates radio communication based on the VoIP software [https://www.mumble.info/ Mumble]. It integrates fully with the radio stack of your FlightGear plane, allowing you to communicate with other pilots and airspace controllers during your flight. It simulates a global, continuous radio frequency spectrum.

FGCom-mumble is an alternative to the already known [[FGCom]] client and [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble leverages the plugin mechanism introduced by Mumble 1.4.0 and just needs a precompiled plugin loaded by a stock Mumble client.
You can download the latest release from https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Servers ==

*The main FGCom-mumble test server is <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
*The status page for that service showing all connected clients is at: https://fgcom-dev.hallinger.org/
*The mumble test server uses a autorenewed certificate from letsencrypt.

==Project main goals==
*Provide communication with geographic and channel separation
*Provide a realistic radio simulation
*Ease of use for the end user/pilot
*Arbitrary frequency support
*ATIS recording and playback
*Radio station broadcast support
*Landline/Intercom support
*RDF detection for clients
*Ease of server side installation and operation
*Standalone nature (no dependency on FlightGear)
* Capability to be integrated into FlightGear, with the option to support third party applications (ATC, but also other flight simulators)
*Modularity, so individual component implementations can be switched and its easy to add features
*Good and complete documentation

== Installation and setup==
The latest release can be fetched from [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] also has debug versions).

The provided [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#install--setup-for-the-client README] has detailed instructions on the needed prerequisites and installation procedures.

Someone even made an install video :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk
(thanks mate, well done! however HF is actually simulated already :)

In short:
* Have a stock Mumble client >= 1.4 running, and load the plugin (mumble settings/plugins page)
* Join a channel named `fgcom-mumble` (on a >= 1.4 mumble server)
* Add the `fgfs-addon` folder of the client release as FlightGear Addon in your launcher
* Start FlightGear and use your plane's radio stack (it uses default FGCom buttons, see below)

==Usage==
FlightGear's FGCom-mumble protocol uses the default FGCom buttons:
* When you want to talk on COM1 you have to press {{Key press|Space}}. While transmitting you can not hear other pilots trough the used radio (they are half-duplex).
* You can also talk on COM2 by pressing {{Key press|Shift|Space}}.
* since FGCom-mumble 1.2.0:
** For COM3 you use {{Key press|Alt|Space}} (previously you need to define a custom keybind),
** Intercom is available in full-duplex with {{Key press|Ctrl|Space}}

Any radio can also accessed by the COMBar (open from ''Menu/Multiplayer/FGCom-mumble'').

If you want to try it out without FlightGear, you can also start the supplied RadioGUI.

=== How to test your setup?===
First, make sure Mumble is working reliably by talking to other people. Either disable the plugin, or be sure you are outside any radio channel (starting with `fgcom-mumble`).

The plugin alters Mumble's receiving audio stream. It adds static noise depending on the radio signal quality, or cancels out all audio when not in range. The outgoing audio stream is not altered in any way.

If the server supports it (in essence there is a bot-manager running and a `fgcom-recorder-bot` listening) you may do a traditional echo test by tuning `910.00` and start to talk. The recorder-bot will record that (he writes that into mumbles chat) and spawn an echo bot at your position, replaying your message (so you will hear yourself like others will hear you).

===Troubleshooting===
For troubleshooting, refer to the projects [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#troubleshooting README] as it has further suggestions.

If it's nothing setup related, an easy fix is to just restart mumble (the plugin will reinitialize itself).

===Compatibility ===
FGCom-mumble supports the legacy FGCom UDP protocol and thus should be compatible to clients supporting that. However, it also features some new UDP fields.

*FlightGear is supported through an [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon]. This assumes the default radio implementation and works with at least the C172P and the C182S.
*[[ATC-pie]] has built in support already (be sure to activate "FGCom-mumble" instead of just "FGCom" in the settings).
*[[OpenRadar]] currently supports just COM1 ([https://sourceforge.net/p/openradar/tickets/5/ ticket pending]). To use COM2 and more, you need to either start several mumble instances, or use FGCom-mumble's RadioGUI.
:There is a patched version of OpenRadar with FGCom-mumble and 8.33 channel tuning support available here: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

====Known incompatibilities====
* The legacy FGCom auto-enables itself, if you are connected to a multiplayer server and then open the "FGCom" dialog (instead of the "FGCom-mumble" one) from the multiplayer dialog. Then activating PTT can cause a FlightGear segfault.
* The UFO aircraft rebinds {{Key press|Space}} so you can't transmit on the radio. As a workaround you can use the COMBar that comes integrated with the FGFS addon.
* FGFS version <= 2020.3 is not compatible with FGCom-mumble addon versions >= 1.3.0. You need to stick to 1.2.0.

==RadioGUI==
The FGCom-mumble RadioGUI is a small Java 8 application that can send the FGCom-mumble UDP messages to the Mumble plugin.

Inside the GUI, you can pick your location from a map and then setup and use your radio stack.
That said, the RadiGUI can be used instead (or additionally to) FGFS to participate on the simulated radio net.

==Server side==
By design, all that is needed is a standard Murmur server (version 1.4.0 or later) and a specially named channel (it has to start with `fgcom-mumble`). This is enough to let the plugin do its work. The entire channel is treated as a single, worldwide continuous radio frequency spectrum.

Additional features are implemented using server side Lua bots (which may run somewhere else):
* ATIS recording and broadcasting
* Radio program broadcasting (OGG playback on a frequency), [https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons]
* Status page data collection

A status page showing client details is available as a PHP website, that gets its data fed from the fgcom-status-bot.

Detailed installation and operation documentation is shipped with the releases, but is also [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server.md online].

==How does it work? (technical information)==
The technical details are specified and described in the various readme files of the projects source code (as a starter read the [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Basicly, all users join the same mumble channel and run the fgcom-mumble plugin. The plugin knows everything necessary from the participating users (like radios used, frequencies tuned, locations, etc) and based on that information mutes or plays incoming voice messages from the other users. Based on signal quality, static noise is mixed in for more fun and a more realistic experience.
Because the voice of other users is muted, it is a design wise out-of-the-box feature that brings frequency and location separation but allows everyone to stay in the same mumble channel.

==Related content==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] with hints etc
*[https://github.com/hbeni/fgcom-mumble/blob/master/README.md FGCom-mumble README.md] Main readme of the project bringing all the details you always wanted to know

===Forum topic===
*The {{forum link|t=37644|title=FGCom-mumble}} has development discussions and release announcements
*{{forum link|p=374950|title=Re: EDDF-Triangle}} and {{forum link|p=374970|title=Re: EDDF-Triangle}} - Compatibility and differences between FGCom, FGCom-mumble and Mumble

===FlightGear Newsletter===
*[[FlightGear_Newsletter_June_2020]]: First prototype announced
*[[FlightGear_Newsletter_July_2020]]: Load tests successful, RDF implemented, Live-Status page added
*[[FlightGear_Newsletter_August_2020]]: More testing, new HF/VHF/UHF models, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API changes, distributed deployment, configuration trough INI, statistics
*[[FlightGear_Newsletter_October_2020]]: More API changes, proper 8.33kHz/25kHz overlap, RadiGUI added
*[[FlightGear_Newsletter_November_2020]]: Test server announced
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringing networking capability
*[[FlightGear_Newsletter_April_2021]]: RDF reworked, 0.12.0 announced, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Better airliner support, announced 0.13.0 and 0.14.0, restructured release package structure
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 announced, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 announced, updater bugfixes part II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 released, Mumble 1.4 hit the light'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

== Idea to integrate into FGFS ==
{{progressbar|10|10}} {{pending}}

ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212

Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum).

A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible?

libmubmble is not yet API-stable (but should be working), but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics:
* From FGCom-mumbles side, we need to integrate the data structures into the core. So radios need to be registered, etc. This should not be too hard
** we probably just need to not run the UPD-Server but send the needed data directly into the decoding function of it. At a later stage, we might better integrate that part, but for a first working solution, just creatig a FCGOM-mumble UDP-Packet string in FGFS and sending it periodically (or already on-demand?) into the udp-servers decoder function should be enough - it just creates some CPU overhead which should not be too bad and will establish the needed local data structure.
** Note, that we cannot rely on the mpservers data structures (even if there is radio data), because in FGCom-mumble potential other clients are also participating (like radio-playback bots for ATIS etc!). So we really need to use mumbles plugin messages.
* Basicly the libmumble will run its own threads for networking. Upon receiving mumble audio or mumble-plugin data, callback functions would be called from the lib (https://github.com/mumble-voip/libmumble/issues/18#issuecomment-1868498537):
** Incoming audio data need to be processed by the fgcom-mumble plugin functions, and then the result handed over into fgfs audio out handling.
** Incoming plugin data needs to be fed into the fgcom-mumble internal remote data struct (just hand the data into the existing data parser).
* Pressing the already existing fgfs PTT button
** would need to send plugin data to mumble, to inform other clients. This is currently done by calling a mumble client function. It would probably be enough, if fgfs core supplied an implemention that calls the appropriate libmumble function and hands over the data.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} And what about libmubmles dependencies, like OpenSSL?
*** technically, how to include that all into the existing build system?

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[de:FGCom-mumble]]

De/FGCom-mumble

2025-02-08T17:48:59Z

Hbeni: /* Bekannte Inkompatibilitäten */

'''FGCom-mumble''' simuliert Funkkommunikation basierend auf der freien VoIP software [https://www.mumble.info/ Mumble]. Es integriert sich vollstädnig mit den Funkgeräten deines Flugzeuges in FlightGear und erlaubt dir, mit anderen Piloten und Fluglotsen auf realistische Weise zu kommunizieren. Dafür simuliert es ein lückenloses Radiowellenspektrum.

FGCom-mumble ist eine Alternative zum altbekannten [[FGCom]] sowie [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble nutzt den Pluginmechanismus, der in Mumble 1.4.0 verfügbar wurde und benötigt lediglich ein vorkompiliertes Plugin, das von einem ganz normalen Mumble-Programm geladen wird. Das aktuellste Release kannst du hier herunterladen: https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Server ==

* Der FGCom-mumble test server ist <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
* Die Statusseite für diese Instanz, die alle verbundenen Clients anzeigt, ist hier: https://fgcom-dev.hallinger.org/
* Der mumble-testserver benutzt ein autoerneuerndes SSL-Zertifikat von Lets Encrypt.

== Hauptziele des Projektes ==
* Bereitstellen von Kommunikation, die sowohl örtlich als auch kanaltechnisch getrennt ist
* Realistische Funkkommunikation
* Einfachheit in der Installation und Benutzung
* Unterstützung für beliebige Frequenzen
* ATIS Aufnahme und Wiedergabe
* Zivile Radiostationen sollen unterstützt werden
* Festnetz/Intercom Unterstützung
* RDF-Signale für Clients
* Einfach auf einem Server zu installieren und zu betreieben
* Unabhängigkeit von Simulatoren wie z.B. Flightgear
* Fähigkeit, in FlightGear integriert zu werden, mit der Option, weitere Clients und Applikationen zu unterstützen (ATC, aber auch andere Flugsimulatoren)
* Modularer Aufbau, damit einzelne Komponenten unterschiedlich implementiert werden können und einfache Erweiterbarkeit besteht
* Gute und vollständige Dokumentation

== Installation and Einrichtung ==
Die aktuelle Version kann hier heruntergeladen werden: [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] bietet auch eine Debug-Variante an).

Die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#installation--einrichtung-des-mumble-plugins README] bietet detaillierte Angaben zur Installation.

Jemand hat sogar ein Video (engl.) von der Installation gemacht! :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk

Zusammengefasst:
* Du brauchst ein installiertes und eingerichtetes Mumble >= 1.4, und dann lade darin das Plugin (unter mumble Einstellungen/plugins)
* Auf dem Mumbleserver (Version >= 1.4.0) trittst du einem Channel bei, dessen Name mit `fgcom-mumble` beginnt
* Im FlightGear-Launcher fügst du im Addon-Tab den `fgfs-addon` Ordner der FGCom-Mumble Veröffentlichung hinzu
* Starte FlightGear und benutze deine Funkgeräte (du funkst mit den ganz normalen FGCom-Tastenkombinationen; siehe unten)

== Benutzung ==
FlightGear's FGCom-mumble Protokoll benutzt die normalen FGCom-Tastenkombinationen:
* Um auf COM1 zu funken, drückst du {{Key press|Space}}. Solange du überträgst, kannst du keine anderen Piloten durch das verwendete Funkgerät hören (diese sind Halbduplexgeräte).
* COM2 sendet mit {{Key press|Shift|Space}}.
* Seit FGCom-mumble 1.2.0:
** Mit COM3 funkst du über {{Key press|Alt|Space}} (früher musstest du ein eigenes Keybind definieren),
** Intercom sendet in full-duplex mit {{Key press|Ctrl|Space}}

Jedes Funkgerät kann außerdem über die COMBar benutzt werden (öffnen über ''Menu/Multiplayer/FGCom-mumble'').

Um FGCom-mumble ohne FlightGear zu probieren, kannst du auch die im Release mitgelieferte RadioGUI starten.

=== Deine Installation testen ===
Als erstes solltest du sicherstellen, dass mumble an Sich gut funktioniert und du gut zu verstehen bist sowie andere gut verstehst.
Dazu deaktivierst du am Besten das Plugin oder du sprichst mit anderen auf einem Channel, der nicht mit `fgcom-mumble`beginnt.

Das Plugin verändert Mumbles eingehende Audiopakete. Es fügt statisches Rauschen hinzu, das von der simulierten Funksignalstärke abhängt oder hebt den stream sogar auf, wenn der Funksender außerhalb der Reichweite liegt. Ausgehende Audiopakete werden nicht verändert.

Falls der Server es unterstützt, kannst du auch einen traditionellen Echo-Test machen (dazu muss am Server ein `fgcom-recorder-bot` laufen). Funke auf der Frequenz `910.00` MHz und der Recorderbot wird mit der Aufzeichnung beginnen (er schreibt das in den mumble-chat) und nach Abschluss einen bot an deiner Position erzeugen, der das aufgenommene auf der Frequenz wiedergibt. So kannst du dich selbst hören, wie andere dich hören würden.

=== Fehlerbehebung ===

Schau bitte in die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#fehlerbehebung README] des Projekts. Diese hat detaillierte Informationen hierzu.

Solange es nichts grundlegendes mit der Installation zu tun hat, hilft oft auch einfach ein Neustart von Mumble (das Plugin initialisiert sich selbständig frisch).

=== Kompatibilität ===
FGCom-mumble unterstützt grundsätzlich das alte FGCom-UDP-Protokoll und sollte somit kompatibel mit allen clients sein, die dieses verwenden (z.B. ältere ATCpie oder OpenRadar Versionen). Allerdings gibt es auch ein paar Erweiterungen, die mit dem alten Protokoll nicht zur Verfügung stehen.

* FlightGear wird durch ein [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon] unterstützt. Dieses erwartet die Standard-Funkgerätimplementierung (und funktioniert getestet zumindest mit der C172p und der C182S).
*[[ATC-pie]] hat eine integrierte Unterstützung (prüfe, ob "FGCom-mumble" anstelle von nur "FGCom" in den Einstellungen aktiviert ist).
*[[OpenRadar]] Unterstützt im Moment nur COM1 ([https://sourceforge.net/p/openradar/tickets/5/ Ticket dazu ist offen]). Für COM2 und weitere musst du entweder separate Mumble-Instanzen öffnen oder FGCom-mumble's RadioGUI zum Funken benutzen.
:Es gibt eine gepatchte Version von OpenRadar mit integriertem FGCom-mumble sowie 8.33 Channelmodus; verfügbar hier: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

==== Bekannte Inkompatibilitäten ====
* Das alte FGCom aktiviert sich selbständig, wenn du mit dem Mehrspielernetzwerk verbunden bist und dann die "FGCom"-Einstellungen (anstelle des "FGCm-Mumble"-Eintrags) aus dem Mehrspielermenü aufrufst. Wenn du mit aktiviertem alten FGCom PTT aktivierst, kann FlightGear abstürzen.
* Das FlightGear UFO belegt {{Key press|Space}} selbst, sodass du nicht Funken kannst. Als workaround kannst du die COMBar benutzen, die mit dem FGFS Addon mitkommt.

== RadioGUI ==
Die RadioGUI ist eine kleine Java8 Applikation, die einen FGCom-mumble client implementiert und Funkgeräte bereitstellt. Sie sendet die notwendigen UDP Nachrichten an das Mumble plugin.

In der GUI kannst du deinen Standort über eine Karte auswählen und dann deine Funkgeräte einstellen und testen.
Damit kannst du auch komplett mit allen Funktionen am simulierten Funknetz teilnehmen, ohne FlightGear zu starten.

== Serverseite ==
Konzeptionell benötigst du als Minimum einfach einen Standard Mumbleserver (Version 1.4.0 oder höher), auf dem ein Channel eingerichtet wird, der mit `fgcom-mumble` beginnt. Das ist bereits genug, damit das Plugin Clientseitig den Rest erledigen kann. Der komplette Channel wird als einzelnes, weltumspannendes, kontinuierliches Radiowellenspektrum behandelt.

Weitere Funktionen werden über Lua-Bots implementiert (die auch auf einer anderen Maschine laufen können):
* ATIS Aufzeichnung udn Wiedergabe
* Radioprogramm Wiedergabe (OGG Wiedergabe auf einer beliebigen Funkfrequenz), z.B. nutzbar für eigene NDBs mit Morsecode ([https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons])
* Statusseite Datensammlung

Eine Statusseite fürs WWW ist als PHP-Seite implementiert, die die notwendigen Daten über den `fgcom-status-bot` bereitgestellt bekommt.

Detaillierte Installations- und Betriebsdokumentation ist in den Veröffentlichungen enthalten, aber auch [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server-de_DE.md online] im Projekt zugänglich.

== Wie funktiooniert das alles? (technische Information) ==
Die technischen Details sind in den verschiedenen Readme-Dateien im Projekt dargelegt (zum Start empfielt sich [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Zusammengefasst treten alle Teilnehmer einem einzigen Mumble-Channel bei und laden das fgcom-mumble Plugin. Das Plugin tauscht alle notwendigen Daten zwischen den Nutzern aus (Funkgeräte, Frequenzen, Standort, etc.) und basierend auf diesen Informationen werden die eingehenden Audioströme der anderen Nutzer entweder abgespielt oder stummgeschaltet. Für mehr Realismus werden abgespielte Audioströme mit Statischem Rauschen und weiteren Effekten unterlegt.
Aufgrund der Stummschaltefunktion abhängig von der Funkreichweite besteht eine unmittelbare Separierung nach Funkkanal und Standort, was allen Nutzern erlaubt, in ein und demselben Mumblekanal zu sein.

== Weiterführender Inhalt ==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] mit weiteren Tipps/Hinweisen
*[https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md FGCom-mumble README-de_DE.md] Haupt-Readme des Projektes mit allen Details, die du schon immer wissen wolltest

=== Forum topic ===
* Der {{forum link|t=37644|title=FGCom-mumble}} Forumshtread hat Entwicklungsrelevante Informationen und dient zur allgemeinen Diskussion
* {{forum link|p=374950|title=Re: EDDF-Triangle}} und {{forum link|p=374970|title=Re: EDDF-Triangle}} - behandeln Details zu Kompatibilität und Unterschieden zwischen FGCom, FGCom-mumble und Mumble

=== FlightGear Newsletter ===
*[[FlightGear_Newsletter_June_2020]]: Erster Prototyp angekündigt
*[[FlightGear_Newsletter_July_2020]]: Lasttests erfolgreich, RDF implementiert, Live-Status Seite hinzugefügt
*[[FlightGear_Newsletter_August_2020]]: Mehr tests, neue HF/VHF/UHF modelle, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API änderungen, verteilte Installation, Konfigurationsmöglichkeit per INI-Datei, Statistiken
*[[FlightGear_Newsletter_October_2020]]: Weitere API änderungen, realistische Simulation der 8.33kHz/25kHz Kanalüberlappung, RadiGUI hinzugefügt
*[[FlightGear_Newsletter_November_2020]]: Test server angekündigt
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringt Netzwerkfunktionen
*[[FlightGear_Newsletter_April_2021]]: RDF Implementierung umgebaut, 0.12.0 angekündigt, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Bessere Unterstützung von Airliners, 0.13.0 and 0.14.0 angekündigt, Releasepaket neustrukturiert
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 angekündigt, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 angekündigt, updater bugfixes Teil II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 veröffentlicht, Mumble 1.4 wurde veröffentlicht'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[en:FGCom-mumble]]

FGCom-mumble

2025-02-08T17:47:03Z

Hbeni: /* Known incompatibilities */

'''FGCom-mumble''' simulates radio communication based on the VoIP software [https://www.mumble.info/ Mumble]. It integrates fully with the radio stack of your FlightGear plane, allowing you to communicate with other pilots and airspace controllers during your flight. It simulates a global, continuous radio frequency spectrum.

FGCom-mumble is an alternative to the already known [[FGCom]] client and [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble leverages the plugin mechanism introduced by Mumble 1.4.0 and just needs a precompiled plugin loaded by a stock Mumble client.
You can download the latest release from https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Servers ==

*The main FGCom-mumble test server is <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
*The status page for that service showing all connected clients is at: https://fgcom-dev.hallinger.org/
*The mumble test server uses a autorenewed certificate from letsencrypt.

==Project main goals==
*Provide communication with geographic and channel separation
*Provide a realistic radio simulation
*Ease of use for the end user/pilot
*Arbitrary frequency support
*ATIS recording and playback
*Radio station broadcast support
*Landline/Intercom support
*RDF detection for clients
*Ease of server side installation and operation
*Standalone nature (no dependency on FlightGear)
* Capability to be integrated into FlightGear, with the option to support third party applications (ATC, but also other flight simulators)
*Modularity, so individual component implementations can be switched and its easy to add features
*Good and complete documentation

== Installation and setup==
The latest release can be fetched from [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] also has debug versions).

The provided [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#install--setup-for-the-client README] has detailed instructions on the needed prerequisites and installation procedures.

Someone even made an install video :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk
(thanks mate, well done! however HF is actually simulated already :)

In short:
* Have a stock Mumble client >= 1.4 running, and load the plugin (mumble settings/plugins page)
* Join a channel named `fgcom-mumble` (on a >= 1.4 mumble server)
* Add the `fgfs-addon` folder of the client release as FlightGear Addon in your launcher
* Start FlightGear and use your plane's radio stack (it uses default FGCom buttons, see below)

==Usage==
FlightGear's FGCom-mumble protocol uses the default FGCom buttons:
* When you want to talk on COM1 you have to press {{Key press|Space}}. While transmitting you can not hear other pilots trough the used radio (they are half-duplex).
* You can also talk on COM2 by pressing {{Key press|Shift|Space}}.
* since FGCom-mumble 1.2.0:
** For COM3 you use {{Key press|Alt|Space}} (previously you need to define a custom keybind),
** Intercom is available in full-duplex with {{Key press|Ctrl|Space}}

Any radio can also accessed by the COMBar (open from ''Menu/Multiplayer/FGCom-mumble'').

If you want to try it out without FlightGear, you can also start the supplied RadioGUI.

=== How to test your setup?===
First, make sure Mumble is working reliably by talking to other people. Either disable the plugin, or be sure you are outside any radio channel (starting with `fgcom-mumble`).

The plugin alters Mumble's receiving audio stream. It adds static noise depending on the radio signal quality, or cancels out all audio when not in range. The outgoing audio stream is not altered in any way.

If the server supports it (in essence there is a bot-manager running and a `fgcom-recorder-bot` listening) you may do a traditional echo test by tuning `910.00` and start to talk. The recorder-bot will record that (he writes that into mumbles chat) and spawn an echo bot at your position, replaying your message (so you will hear yourself like others will hear you).

===Troubleshooting===
For troubleshooting, refer to the projects [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#troubleshooting README] as it has further suggestions.

If it's nothing setup related, an easy fix is to just restart mumble (the plugin will reinitialize itself).

===Compatibility ===
FGCom-mumble supports the legacy FGCom UDP protocol and thus should be compatible to clients supporting that. However, it also features some new UDP fields.

*FlightGear is supported through an [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon]. This assumes the default radio implementation and works with at least the C172P and the C182S.
*[[ATC-pie]] has built in support already (be sure to activate "FGCom-mumble" instead of just "FGCom" in the settings).
*[[OpenRadar]] currently supports just COM1 ([https://sourceforge.net/p/openradar/tickets/5/ ticket pending]). To use COM2 and more, you need to either start several mumble instances, or use FGCom-mumble's RadioGUI.
:There is a patched version of OpenRadar with FGCom-mumble and 8.33 channel tuning support available here: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

====Known incompatibilities====
* The legacy FGCom auto-enables itself, if you are connected to a multiplayer server and then open the "FGCom" dialog (instead of the "FGCom-mumble" one) from the multiplayer dialog. Then activating PTT can cause a FlightGear segfault.
* The UFO aircraft rebinds {{Key press|Space}} so you can't transmit on the radio. As a workaround you can use the COMBar that comes integrated with the FGFS addon.

==RadioGUI==
The FGCom-mumble RadioGUI is a small Java 8 application that can send the FGCom-mumble UDP messages to the Mumble plugin.

Inside the GUI, you can pick your location from a map and then setup and use your radio stack.
That said, the RadiGUI can be used instead (or additionally to) FGFS to participate on the simulated radio net.

==Server side==
By design, all that is needed is a standard Murmur server (version 1.4.0 or later) and a specially named channel (it has to start with `fgcom-mumble`). This is enough to let the plugin do its work. The entire channel is treated as a single, worldwide continuous radio frequency spectrum.

Additional features are implemented using server side Lua bots (which may run somewhere else):
* ATIS recording and broadcasting
* Radio program broadcasting (OGG playback on a frequency), [https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons]
* Status page data collection

A status page showing client details is available as a PHP website, that gets its data fed from the fgcom-status-bot.

Detailed installation and operation documentation is shipped with the releases, but is also [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server.md online].

==How does it work? (technical information)==
The technical details are specified and described in the various readme files of the projects source code (as a starter read the [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Basicly, all users join the same mumble channel and run the fgcom-mumble plugin. The plugin knows everything necessary from the participating users (like radios used, frequencies tuned, locations, etc) and based on that information mutes or plays incoming voice messages from the other users. Based on signal quality, static noise is mixed in for more fun and a more realistic experience.
Because the voice of other users is muted, it is a design wise out-of-the-box feature that brings frequency and location separation but allows everyone to stay in the same mumble channel.

==Related content==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] with hints etc
*[https://github.com/hbeni/fgcom-mumble/blob/master/README.md FGCom-mumble README.md] Main readme of the project bringing all the details you always wanted to know

===Forum topic===
*The {{forum link|t=37644|title=FGCom-mumble}} has development discussions and release announcements
*{{forum link|p=374950|title=Re: EDDF-Triangle}} and {{forum link|p=374970|title=Re: EDDF-Triangle}} - Compatibility and differences between FGCom, FGCom-mumble and Mumble

===FlightGear Newsletter===
*[[FlightGear_Newsletter_June_2020]]: First prototype announced
*[[FlightGear_Newsletter_July_2020]]: Load tests successful, RDF implemented, Live-Status page added
*[[FlightGear_Newsletter_August_2020]]: More testing, new HF/VHF/UHF models, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API changes, distributed deployment, configuration trough INI, statistics
*[[FlightGear_Newsletter_October_2020]]: More API changes, proper 8.33kHz/25kHz overlap, RadiGUI added
*[[FlightGear_Newsletter_November_2020]]: Test server announced
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringing networking capability
*[[FlightGear_Newsletter_April_2021]]: RDF reworked, 0.12.0 announced, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Better airliner support, announced 0.13.0 and 0.14.0, restructured release package structure
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 announced, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 announced, updater bugfixes part II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 released, Mumble 1.4 hit the light'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

== Idea to integrate into FGFS ==
{{progressbar|10|10}} {{pending}}

ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212

Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum).

A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible?

libmubmble is not yet API-stable (but should be working), but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics:
* From FGCom-mumbles side, we need to integrate the data structures into the core. So radios need to be registered, etc. This should not be too hard
** we probably just need to not run the UPD-Server but send the needed data directly into the decoding function of it. At a later stage, we might better integrate that part, but for a first working solution, just creatig a FCGOM-mumble UDP-Packet string in FGFS and sending it periodically (or already on-demand?) into the udp-servers decoder function should be enough - it just creates some CPU overhead which should not be too bad and will establish the needed local data structure.
** Note, that we cannot rely on the mpservers data structures (even if there is radio data), because in FGCom-mumble potential other clients are also participating (like radio-playback bots for ATIS etc!). So we really need to use mumbles plugin messages.
* Basicly the libmumble will run its own threads for networking. Upon receiving mumble audio or mumble-plugin data, callback functions would be called from the lib (https://github.com/mumble-voip/libmumble/issues/18#issuecomment-1868498537):
** Incoming audio data need to be processed by the fgcom-mumble plugin functions, and then the result handed over into fgfs audio out handling.
** Incoming plugin data needs to be fed into the fgcom-mumble internal remote data struct (just hand the data into the existing data parser).
* Pressing the already existing fgfs PTT button
** would need to send plugin data to mumble, to inform other clients. This is currently done by calling a mumble client function. It would probably be enough, if fgfs core supplied an implemention that calls the appropriate libmumble function and hands over the data.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} And what about libmubmles dependencies, like OpenSSL?
*** technically, how to include that all into the existing build system?

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[de:FGCom-mumble]]

De/FGCom-mumble

2025-02-03T12:08:26Z

Hbeni:

'''FGCom-mumble''' simuliert Funkkommunikation basierend auf der freien VoIP software [https://www.mumble.info/ Mumble]. Es integriert sich vollstädnig mit den Funkgeräten deines Flugzeuges in FlightGear und erlaubt dir, mit anderen Piloten und Fluglotsen auf realistische Weise zu kommunizieren. Dafür simuliert es ein lückenloses Radiowellenspektrum.

FGCom-mumble ist eine Alternative zum altbekannten [[FGCom]] sowie [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble nutzt den Pluginmechanismus, der in Mumble 1.4.0 verfügbar wurde und benötigt lediglich ein vorkompiliertes Plugin, das von einem ganz normalen Mumble-Programm geladen wird. Das aktuellste Release kannst du hier herunterladen: https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Server ==

* Der FGCom-mumble test server ist <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
* Die Statusseite für diese Instanz, die alle verbundenen Clients anzeigt, ist hier: https://fgcom-dev.hallinger.org/
* Der mumble-testserver benutzt ein autoerneuerndes SSL-Zertifikat von Lets Encrypt.

== Hauptziele des Projektes ==
* Bereitstellen von Kommunikation, die sowohl örtlich als auch kanaltechnisch getrennt ist
* Realistische Funkkommunikation
* Einfachheit in der Installation und Benutzung
* Unterstützung für beliebige Frequenzen
* ATIS Aufnahme und Wiedergabe
* Zivile Radiostationen sollen unterstützt werden
* Festnetz/Intercom Unterstützung
* RDF-Signale für Clients
* Einfach auf einem Server zu installieren und zu betreieben
* Unabhängigkeit von Simulatoren wie z.B. Flightgear
* Fähigkeit, in FlightGear integriert zu werden, mit der Option, weitere Clients und Applikationen zu unterstützen (ATC, aber auch andere Flugsimulatoren)
* Modularer Aufbau, damit einzelne Komponenten unterschiedlich implementiert werden können und einfache Erweiterbarkeit besteht
* Gute und vollständige Dokumentation

== Installation and Einrichtung ==
Die aktuelle Version kann hier heruntergeladen werden: [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] bietet auch eine Debug-Variante an).

Die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#installation--einrichtung-des-mumble-plugins README] bietet detaillierte Angaben zur Installation.

Jemand hat sogar ein Video (engl.) von der Installation gemacht! :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk

Zusammengefasst:
* Du brauchst ein installiertes und eingerichtetes Mumble >= 1.4, und dann lade darin das Plugin (unter mumble Einstellungen/plugins)
* Auf dem Mumbleserver (Version >= 1.4.0) trittst du einem Channel bei, dessen Name mit `fgcom-mumble` beginnt
* Im FlightGear-Launcher fügst du im Addon-Tab den `fgfs-addon` Ordner der FGCom-Mumble Veröffentlichung hinzu
* Starte FlightGear und benutze deine Funkgeräte (du funkst mit den ganz normalen FGCom-Tastenkombinationen; siehe unten)

== Benutzung ==
FlightGear's FGCom-mumble Protokoll benutzt die normalen FGCom-Tastenkombinationen:
* Um auf COM1 zu funken, drückst du {{Key press|Space}}. Solange du überträgst, kannst du keine anderen Piloten durch das verwendete Funkgerät hören (diese sind Halbduplexgeräte).
* COM2 sendet mit {{Key press|Shift|Space}}.
* Seit FGCom-mumble 1.2.0:
** Mit COM3 funkst du über {{Key press|Alt|Space}} (früher musstest du ein eigenes Keybind definieren),
** Intercom sendet in full-duplex mit {{Key press|Ctrl|Space}}

Jedes Funkgerät kann außerdem über die COMBar benutzt werden (öffnen über ''Menu/Multiplayer/FGCom-mumble'').

Um FGCom-mumble ohne FlightGear zu probieren, kannst du auch die im Release mitgelieferte RadioGUI starten.

=== Deine Installation testen ===
Als erstes solltest du sicherstellen, dass mumble an Sich gut funktioniert und du gut zu verstehen bist sowie andere gut verstehst.
Dazu deaktivierst du am Besten das Plugin oder du sprichst mit anderen auf einem Channel, der nicht mit `fgcom-mumble`beginnt.

Das Plugin verändert Mumbles eingehende Audiopakete. Es fügt statisches Rauschen hinzu, das von der simulierten Funksignalstärke abhängt oder hebt den stream sogar auf, wenn der Funksender außerhalb der Reichweite liegt. Ausgehende Audiopakete werden nicht verändert.

Falls der Server es unterstützt, kannst du auch einen traditionellen Echo-Test machen (dazu muss am Server ein `fgcom-recorder-bot` laufen). Funke auf der Frequenz `910.00` MHz und der Recorderbot wird mit der Aufzeichnung beginnen (er schreibt das in den mumble-chat) und nach Abschluss einen bot an deiner Position erzeugen, der das aufgenommene auf der Frequenz wiedergibt. So kannst du dich selbst hören, wie andere dich hören würden.

=== Fehlerbehebung ===

Schau bitte in die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#fehlerbehebung README] des Projekts. Diese hat detaillierte Informationen hierzu.

Solange es nichts grundlegendes mit der Installation zu tun hat, hilft oft auch einfach ein Neustart von Mumble (das Plugin initialisiert sich selbständig frisch).

=== Kompatibilität ===
FGCom-mumble unterstützt grundsätzlich das alte FGCom-UDP-Protokoll und sollte somit kompatibel mit allen clients sein, die dieses verwenden (z.B. ältere ATCpie oder OpenRadar Versionen). Allerdings gibt es auch ein paar Erweiterungen, die mit dem alten Protokoll nicht zur Verfügung stehen.

* FlightGear wird durch ein [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon] unterstützt. Dieses erwartet die Standard-Funkgerätimplementierung (und funktioniert getestet zumindest mit der C172p und der C182S).
*[[ATC-pie]] hat eine integrierte Unterstützung (prüfe, ob "FGCom-mumble" anstelle von nur "FGCom" in den Einstellungen aktiviert ist).
*[[OpenRadar]] Unterstützt im Moment nur COM1 ([https://sourceforge.net/p/openradar/tickets/5/ Ticket dazu ist offen]). Für COM2 und weitere musst du entweder separate Mumble-Instanzen öffnen oder FGCom-mumble's RadioGUI zum Funken benutzen.
:Es gibt eine gepatchte Version von OpenRadar mit integriertem FGCom-mumble sowie 8.33 Channelmodus; verfügbar hier: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

==== Bekannte Inkompatibilitäten ====
* Das FlightGear UFO belegt {{Key press|Space}} selbst, sodass du nicht Funken kannst. Als workaround kannst du die COMBar benutzen, die mit dem FGFS Addon mitkommt.

== RadioGUI ==
Die RadioGUI ist eine kleine Java8 Applikation, die einen FGCom-mumble client implementiert und Funkgeräte bereitstellt. Sie sendet die notwendigen UDP Nachrichten an das Mumble plugin.

In der GUI kannst du deinen Standort über eine Karte auswählen und dann deine Funkgeräte einstellen und testen.
Damit kannst du auch komplett mit allen Funktionen am simulierten Funknetz teilnehmen, ohne FlightGear zu starten.

== Serverseite ==
Konzeptionell benötigst du als Minimum einfach einen Standard Mumbleserver (Version 1.4.0 oder höher), auf dem ein Channel eingerichtet wird, der mit `fgcom-mumble` beginnt. Das ist bereits genug, damit das Plugin Clientseitig den Rest erledigen kann. Der komplette Channel wird als einzelnes, weltumspannendes, kontinuierliches Radiowellenspektrum behandelt.

Weitere Funktionen werden über Lua-Bots implementiert (die auch auf einer anderen Maschine laufen können):
* ATIS Aufzeichnung udn Wiedergabe
* Radioprogramm Wiedergabe (OGG Wiedergabe auf einer beliebigen Funkfrequenz), z.B. nutzbar für eigene NDBs mit Morsecode ([https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons])
* Statusseite Datensammlung

Eine Statusseite fürs WWW ist als PHP-Seite implementiert, die die notwendigen Daten über den `fgcom-status-bot` bereitgestellt bekommt.

Detaillierte Installations- und Betriebsdokumentation ist in den Veröffentlichungen enthalten, aber auch [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server-de_DE.md online] im Projekt zugänglich.

== Wie funktiooniert das alles? (technische Information) ==
Die technischen Details sind in den verschiedenen Readme-Dateien im Projekt dargelegt (zum Start empfielt sich [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Zusammengefasst treten alle Teilnehmer einem einzigen Mumble-Channel bei und laden das fgcom-mumble Plugin. Das Plugin tauscht alle notwendigen Daten zwischen den Nutzern aus (Funkgeräte, Frequenzen, Standort, etc.) und basierend auf diesen Informationen werden die eingehenden Audioströme der anderen Nutzer entweder abgespielt oder stummgeschaltet. Für mehr Realismus werden abgespielte Audioströme mit Statischem Rauschen und weiteren Effekten unterlegt.
Aufgrund der Stummschaltefunktion abhängig von der Funkreichweite besteht eine unmittelbare Separierung nach Funkkanal und Standort, was allen Nutzern erlaubt, in ein und demselben Mumblekanal zu sein.

== Weiterführender Inhalt ==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] mit weiteren Tipps/Hinweisen
*[https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md FGCom-mumble README-de_DE.md] Haupt-Readme des Projektes mit allen Details, die du schon immer wissen wolltest

=== Forum topic ===
* Der {{forum link|t=37644|title=FGCom-mumble}} Forumshtread hat Entwicklungsrelevante Informationen und dient zur allgemeinen Diskussion
* {{forum link|p=374950|title=Re: EDDF-Triangle}} und {{forum link|p=374970|title=Re: EDDF-Triangle}} - behandeln Details zu Kompatibilität und Unterschieden zwischen FGCom, FGCom-mumble und Mumble

=== FlightGear Newsletter ===
*[[FlightGear_Newsletter_June_2020]]: Erster Prototyp angekündigt
*[[FlightGear_Newsletter_July_2020]]: Lasttests erfolgreich, RDF implementiert, Live-Status Seite hinzugefügt
*[[FlightGear_Newsletter_August_2020]]: Mehr tests, neue HF/VHF/UHF modelle, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API änderungen, verteilte Installation, Konfigurationsmöglichkeit per INI-Datei, Statistiken
*[[FlightGear_Newsletter_October_2020]]: Weitere API änderungen, realistische Simulation der 8.33kHz/25kHz Kanalüberlappung, RadiGUI hinzugefügt
*[[FlightGear_Newsletter_November_2020]]: Test server angekündigt
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringt Netzwerkfunktionen
*[[FlightGear_Newsletter_April_2021]]: RDF Implementierung umgebaut, 0.12.0 angekündigt, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Bessere Unterstützung von Airliners, 0.13.0 and 0.14.0 angekündigt, Releasepaket neustrukturiert
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 angekündigt, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 angekündigt, updater bugfixes Teil II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 veröffentlicht, Mumble 1.4 wurde veröffentlicht'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[en:FGCom-mumble]]

De/FGCom-mumble

2025-02-03T12:07:57Z

Hbeni:

'''FGCom-mumble''' simuliert Funkkommunikation basierend auf der freien VoIP software [https://www.mumble.info/ Mumble]. Es integriert sich vollstädnig mit den Funkgeräten deines Flugzeuges in FlightGear und erlaubt dir, mit anderen Piloten und Fluglotsen auf realistische Weise zu kommunizieren. Dafür simuliert es ein lückenloses Radiowellenspektrum.

FGCom-mumble ist eine Alternative zum altbekannten [[FGCom]] sowie [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble nutzt den Pluginmechanismus, der in Mumble 1.4.0 verfügbar wurde und benötigt lediglich ein vorkompiliertes Plugin, das von einem ganz normalen Mumble-Programm geladen wird. Das aktuellste Release kannst du hier herunterladen: https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Server ==

* Der FGCom-mumble test server ist <code>mumble://fgcom.hallinger.org/fgcom-mumble</code>
* Die Statusseite für diese Instanz, die alle verbundenen Clients anzeigt, ist hier: https://fgcom.hallinger.org/
* Der mumble-testserver benutzt ein autoerneuerndes SSL-Zertifikat von Lets Encrypt.

== Hauptziele des Projektes ==
* Bereitstellen von Kommunikation, die sowohl örtlich als auch kanaltechnisch getrennt ist
* Realistische Funkkommunikation
* Einfachheit in der Installation und Benutzung
* Unterstützung für beliebige Frequenzen
* ATIS Aufnahme und Wiedergabe
* Zivile Radiostationen sollen unterstützt werden
* Festnetz/Intercom Unterstützung
* RDF-Signale für Clients
* Einfach auf einem Server zu installieren und zu betreieben
* Unabhängigkeit von Simulatoren wie z.B. Flightgear
* Fähigkeit, in FlightGear integriert zu werden, mit der Option, weitere Clients und Applikationen zu unterstützen (ATC, aber auch andere Flugsimulatoren)
* Modularer Aufbau, damit einzelne Komponenten unterschiedlich implementiert werden können und einfache Erweiterbarkeit besteht
* Gute und vollständige Dokumentation

== Installation and Einrichtung ==
Die aktuelle Version kann hier heruntergeladen werden: [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] bietet auch eine Debug-Variante an).

Die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#installation--einrichtung-des-mumble-plugins README] bietet detaillierte Angaben zur Installation.

Jemand hat sogar ein Video (engl.) von der Installation gemacht! :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk

Zusammengefasst:
* Du brauchst ein installiertes und eingerichtetes Mumble >= 1.4, und dann lade darin das Plugin (unter mumble Einstellungen/plugins)
* Auf dem Mumbleserver (Version >= 1.4.0) trittst du einem Channel bei, dessen Name mit `fgcom-mumble` beginnt
* Im FlightGear-Launcher fügst du im Addon-Tab den `fgfs-addon` Ordner der FGCom-Mumble Veröffentlichung hinzu
* Starte FlightGear und benutze deine Funkgeräte (du funkst mit den ganz normalen FGCom-Tastenkombinationen; siehe unten)

== Benutzung ==
FlightGear's FGCom-mumble Protokoll benutzt die normalen FGCom-Tastenkombinationen:
* Um auf COM1 zu funken, drückst du {{Key press|Space}}. Solange du überträgst, kannst du keine anderen Piloten durch das verwendete Funkgerät hören (diese sind Halbduplexgeräte).
* COM2 sendet mit {{Key press|Shift|Space}}.
* Seit FGCom-mumble 1.2.0:
** Mit COM3 funkst du über {{Key press|Alt|Space}} (früher musstest du ein eigenes Keybind definieren),
** Intercom sendet in full-duplex mit {{Key press|Ctrl|Space}}

Jedes Funkgerät kann außerdem über die COMBar benutzt werden (öffnen über ''Menu/Multiplayer/FGCom-mumble'').

Um FGCom-mumble ohne FlightGear zu probieren, kannst du auch die im Release mitgelieferte RadioGUI starten.

=== Deine Installation testen ===
Als erstes solltest du sicherstellen, dass mumble an Sich gut funktioniert und du gut zu verstehen bist sowie andere gut verstehst.
Dazu deaktivierst du am Besten das Plugin oder du sprichst mit anderen auf einem Channel, der nicht mit `fgcom-mumble`beginnt.

Das Plugin verändert Mumbles eingehende Audiopakete. Es fügt statisches Rauschen hinzu, das von der simulierten Funksignalstärke abhängt oder hebt den stream sogar auf, wenn der Funksender außerhalb der Reichweite liegt. Ausgehende Audiopakete werden nicht verändert.

Falls der Server es unterstützt, kannst du auch einen traditionellen Echo-Test machen (dazu muss am Server ein `fgcom-recorder-bot` laufen). Funke auf der Frequenz `910.00` MHz und der Recorderbot wird mit der Aufzeichnung beginnen (er schreibt das in den mumble-chat) und nach Abschluss einen bot an deiner Position erzeugen, der das aufgenommene auf der Frequenz wiedergibt. So kannst du dich selbst hören, wie andere dich hören würden.

=== Fehlerbehebung ===

Schau bitte in die [https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md#fehlerbehebung README] des Projekts. Diese hat detaillierte Informationen hierzu.

Solange es nichts grundlegendes mit der Installation zu tun hat, hilft oft auch einfach ein Neustart von Mumble (das Plugin initialisiert sich selbständig frisch).

=== Kompatibilität ===
FGCom-mumble unterstützt grundsätzlich das alte FGCom-UDP-Protokoll und sollte somit kompatibel mit allen clients sein, die dieses verwenden (z.B. ältere ATCpie oder OpenRadar Versionen). Allerdings gibt es auch ein paar Erweiterungen, die mit dem alten Protokoll nicht zur Verfügung stehen.

* FlightGear wird durch ein [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon] unterstützt. Dieses erwartet die Standard-Funkgerätimplementierung (und funktioniert getestet zumindest mit der C172p und der C182S).
*[[ATC-pie]] hat eine integrierte Unterstützung (prüfe, ob "FGCom-mumble" anstelle von nur "FGCom" in den Einstellungen aktiviert ist).
*[[OpenRadar]] Unterstützt im Moment nur COM1 ([https://sourceforge.net/p/openradar/tickets/5/ Ticket dazu ist offen]). Für COM2 und weitere musst du entweder separate Mumble-Instanzen öffnen oder FGCom-mumble's RadioGUI zum Funken benutzen.
:Es gibt eine gepatchte Version von OpenRadar mit integriertem FGCom-mumble sowie 8.33 Channelmodus; verfügbar hier: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

==== Bekannte Inkompatibilitäten ====
* Das FlightGear UFO belegt {{Key press|Space}} selbst, sodass du nicht Funken kannst. Als workaround kannst du die COMBar benutzen, die mit dem FGFS Addon mitkommt.

== RadioGUI ==
Die RadioGUI ist eine kleine Java8 Applikation, die einen FGCom-mumble client implementiert und Funkgeräte bereitstellt. Sie sendet die notwendigen UDP Nachrichten an das Mumble plugin.

In der GUI kannst du deinen Standort über eine Karte auswählen und dann deine Funkgeräte einstellen und testen.
Damit kannst du auch komplett mit allen Funktionen am simulierten Funknetz teilnehmen, ohne FlightGear zu starten.

== Serverseite ==
Konzeptionell benötigst du als Minimum einfach einen Standard Mumbleserver (Version 1.4.0 oder höher), auf dem ein Channel eingerichtet wird, der mit `fgcom-mumble` beginnt. Das ist bereits genug, damit das Plugin Clientseitig den Rest erledigen kann. Der komplette Channel wird als einzelnes, weltumspannendes, kontinuierliches Radiowellenspektrum behandelt.

Weitere Funktionen werden über Lua-Bots implementiert (die auch auf einer anderen Maschine laufen können):
* ATIS Aufzeichnung udn Wiedergabe
* Radioprogramm Wiedergabe (OGG Wiedergabe auf einer beliebigen Funkfrequenz), z.B. nutzbar für eigene NDBs mit Morsecode ([https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons])
* Statusseite Datensammlung

Eine Statusseite fürs WWW ist als PHP-Seite implementiert, die die notwendigen Daten über den `fgcom-status-bot` bereitgestellt bekommt.

Detaillierte Installations- und Betriebsdokumentation ist in den Veröffentlichungen enthalten, aber auch [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server-de_DE.md online] im Projekt zugänglich.

== Wie funktiooniert das alles? (technische Information) ==
Die technischen Details sind in den verschiedenen Readme-Dateien im Projekt dargelegt (zum Start empfielt sich [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Zusammengefasst treten alle Teilnehmer einem einzigen Mumble-Channel bei und laden das fgcom-mumble Plugin. Das Plugin tauscht alle notwendigen Daten zwischen den Nutzern aus (Funkgeräte, Frequenzen, Standort, etc.) und basierend auf diesen Informationen werden die eingehenden Audioströme der anderen Nutzer entweder abgespielt oder stummgeschaltet. Für mehr Realismus werden abgespielte Audioströme mit Statischem Rauschen und weiteren Effekten unterlegt.
Aufgrund der Stummschaltefunktion abhängig von der Funkreichweite besteht eine unmittelbare Separierung nach Funkkanal und Standort, was allen Nutzern erlaubt, in ein und demselben Mumblekanal zu sein.

== Weiterführender Inhalt ==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] mit weiteren Tipps/Hinweisen
*[https://github.com/hbeni/fgcom-mumble/blob/master/README-de_DE.md FGCom-mumble README-de_DE.md] Haupt-Readme des Projektes mit allen Details, die du schon immer wissen wolltest

=== Forum topic ===
* Der {{forum link|t=37644|title=FGCom-mumble}} Forumshtread hat Entwicklungsrelevante Informationen und dient zur allgemeinen Diskussion
* {{forum link|p=374950|title=Re: EDDF-Triangle}} und {{forum link|p=374970|title=Re: EDDF-Triangle}} - behandeln Details zu Kompatibilität und Unterschieden zwischen FGCom, FGCom-mumble und Mumble

=== FlightGear Newsletter ===
*[[FlightGear_Newsletter_June_2020]]: Erster Prototyp angekündigt
*[[FlightGear_Newsletter_July_2020]]: Lasttests erfolgreich, RDF implementiert, Live-Status Seite hinzugefügt
*[[FlightGear_Newsletter_August_2020]]: Mehr tests, neue HF/VHF/UHF modelle, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API änderungen, verteilte Installation, Konfigurationsmöglichkeit per INI-Datei, Statistiken
*[[FlightGear_Newsletter_October_2020]]: Weitere API änderungen, realistische Simulation der 8.33kHz/25kHz Kanalüberlappung, RadiGUI hinzugefügt
*[[FlightGear_Newsletter_November_2020]]: Test server angekündigt
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringt Netzwerkfunktionen
*[[FlightGear_Newsletter_April_2021]]: RDF Implementierung umgebaut, 0.12.0 angekündigt, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Bessere Unterstützung von Airliners, 0.13.0 and 0.14.0 angekündigt, Releasepaket neustrukturiert
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 angekündigt, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 angekündigt, updater bugfixes Teil II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 veröffentlicht, Mumble 1.4 wurde veröffentlicht'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[en:FGCom-mumble]]

FGCom-mumble

2025-02-03T12:06:46Z

Hbeni:

'''FGCom-mumble''' simulates radio communication based on the VoIP software [https://www.mumble.info/ Mumble]. It integrates fully with the radio stack of your FlightGear plane, allowing you to communicate with other pilots and airspace controllers during your flight. It simulates a global, continuous radio frequency spectrum.

FGCom-mumble is an alternative to the already known [[FGCom]] client and [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble leverages the plugin mechanism introduced by Mumble 1.4.0 and just needs a precompiled plugin loaded by a stock Mumble client.
You can download the latest release from https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Servers ==

*The main FGCom-mumble test server is <code>mumble://fgcom-dev.hallinger.org/fgcom-mumble</code>
*The status page for that service showing all connected clients is at: https://fgcom-dev.hallinger.org/
*The mumble test server uses a autorenewed certificate from letsencrypt.

==Project main goals==
*Provide communication with geographic and channel separation
*Provide a realistic radio simulation
*Ease of use for the end user/pilot
*Arbitrary frequency support
*ATIS recording and playback
*Radio station broadcast support
*Landline/Intercom support
*RDF detection for clients
*Ease of server side installation and operation
*Standalone nature (no dependency on FlightGear)
* Capability to be integrated into FlightGear, with the option to support third party applications (ATC, but also other flight simulators)
*Modularity, so individual component implementations can be switched and its easy to add features
*Good and complete documentation

== Installation and setup==
The latest release can be fetched from [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] also has debug versions).

The provided [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#install--setup-for-the-client README] has detailed instructions on the needed prerequisites and installation procedures.

Someone even made an install video :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk
(thanks mate, well done! however HF is actually simulated already :)

In short:
* Have a stock Mumble client >= 1.4 running, and load the plugin (mumble settings/plugins page)
* Join a channel named `fgcom-mumble` (on a >= 1.4 mumble server)
* Add the `fgfs-addon` folder of the client release as FlightGear Addon in your launcher
* Start FlightGear and use your plane's radio stack (it uses default FGCom buttons, see below)

==Usage==
FlightGear's FGCom-mumble protocol uses the default FGCom buttons:
* When you want to talk on COM1 you have to press {{Key press|Space}}. While transmitting you can not hear other pilots trough the used radio (they are half-duplex).
* You can also talk on COM2 by pressing {{Key press|Shift|Space}}.
* since FGCom-mumble 1.2.0:
** For COM3 you use {{Key press|Alt|Space}} (previously you need to define a custom keybind),
** Intercom is available in full-duplex with {{Key press|Ctrl|Space}}

Any radio can also accessed by the COMBar (open from ''Menu/Multiplayer/FGCom-mumble'').

If you want to try it out without FlightGear, you can also start the supplied RadioGUI.

=== How to test your setup?===
First, make sure Mumble is working reliably by talking to other people. Either disable the plugin, or be sure you are outside any radio channel (starting with `fgcom-mumble`).

The plugin alters Mumble's receiving audio stream. It adds static noise depending on the radio signal quality, or cancels out all audio when not in range. The outgoing audio stream is not altered in any way.

If the server supports it (in essence there is a bot-manager running and a `fgcom-recorder-bot` listening) you may do a traditional echo test by tuning `910.00` and start to talk. The recorder-bot will record that (he writes that into mumbles chat) and spawn an echo bot at your position, replaying your message (so you will hear yourself like others will hear you).

===Troubleshooting===
For troubleshooting, refer to the projects [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#troubleshooting README] as it has further suggestions.

If it's nothing setup related, an easy fix is to just restart mumble (the plugin will reinitialize itself).

===Compatibility ===
FGCom-mumble supports the legacy FGCom UDP protocol and thus should be compatible to clients supporting that. However, it also features some new UDP fields.

*FlightGear is supported through an [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon]. This assumes the default radio implementation and works with at least the C172P and the C182S.
*[[ATC-pie]] has built in support already (be sure to activate "FGCom-mumble" instead of just "FGCom" in the settings).
*[[OpenRadar]] currently supports just COM1 ([https://sourceforge.net/p/openradar/tickets/5/ ticket pending]). To use COM2 and more, you need to either start several mumble instances, or use FGCom-mumble's RadioGUI.
:There is a patched version of OpenRadar with FGCom-mumble and 8.33 channel tuning support available here: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

====Known incompatibilities====
* The UFO aircraft rebinds {{Key press|Space}} so you can't transmit on the radio. As a workaround you can use the COMBar that comes integrated with the FGFS addon.

==RadioGUI==
The FGCom-mumble RadioGUI is a small Java 8 application that can send the FGCom-mumble UDP messages to the Mumble plugin.

Inside the GUI, you can pick your location from a map and then setup and use your radio stack.
That said, the RadiGUI can be used instead (or additionally to) FGFS to participate on the simulated radio net.

==Server side==
By design, all that is needed is a standard Murmur server (version 1.4.0 or later) and a specially named channel (it has to start with `fgcom-mumble`). This is enough to let the plugin do its work. The entire channel is treated as a single, worldwide continuous radio frequency spectrum.

Additional features are implemented using server side Lua bots (which may run somewhere else):
* ATIS recording and broadcasting
* Radio program broadcasting (OGG playback on a frequency), [https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons]
* Status page data collection

A status page showing client details is available as a PHP website, that gets its data fed from the fgcom-status-bot.

Detailed installation and operation documentation is shipped with the releases, but is also [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server.md online].

==How does it work? (technical information)==
The technical details are specified and described in the various readme files of the projects source code (as a starter read the [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Basicly, all users join the same mumble channel and run the fgcom-mumble plugin. The plugin knows everything necessary from the participating users (like radios used, frequencies tuned, locations, etc) and based on that information mutes or plays incoming voice messages from the other users. Based on signal quality, static noise is mixed in for more fun and a more realistic experience.
Because the voice of other users is muted, it is a design wise out-of-the-box feature that brings frequency and location separation but allows everyone to stay in the same mumble channel.

==Related content==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] with hints etc
*[https://github.com/hbeni/fgcom-mumble/blob/master/README.md FGCom-mumble README.md] Main readme of the project bringing all the details you always wanted to know

===Forum topic===
*The {{forum link|t=37644|title=FGCom-mumble}} has development discussions and release announcements
*{{forum link|p=374950|title=Re: EDDF-Triangle}} and {{forum link|p=374970|title=Re: EDDF-Triangle}} - Compatibility and differences between FGCom, FGCom-mumble and Mumble

===FlightGear Newsletter===
*[[FlightGear_Newsletter_June_2020]]: First prototype announced
*[[FlightGear_Newsletter_July_2020]]: Load tests successful, RDF implemented, Live-Status page added
*[[FlightGear_Newsletter_August_2020]]: More testing, new HF/VHF/UHF models, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API changes, distributed deployment, configuration trough INI, statistics
*[[FlightGear_Newsletter_October_2020]]: More API changes, proper 8.33kHz/25kHz overlap, RadiGUI added
*[[FlightGear_Newsletter_November_2020]]: Test server announced
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringing networking capability
*[[FlightGear_Newsletter_April_2021]]: RDF reworked, 0.12.0 announced, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Better airliner support, announced 0.13.0 and 0.14.0, restructured release package structure
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 announced, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 announced, updater bugfixes part II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 released, Mumble 1.4 hit the light'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

== Idea to integrate into FGFS ==
{{progressbar|10|10}} {{pending}}

ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212

Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum).

A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible?

libmubmble is not yet API-stable (but should be working), but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics:
* From FGCom-mumbles side, we need to integrate the data structures into the core. So radios need to be registered, etc. This should not be too hard
** we probably just need to not run the UPD-Server but send the needed data directly into the decoding function of it. At a later stage, we might better integrate that part, but for a first working solution, just creatig a FCGOM-mumble UDP-Packet string in FGFS and sending it periodically (or already on-demand?) into the udp-servers decoder function should be enough - it just creates some CPU overhead which should not be too bad and will establish the needed local data structure.
** Note, that we cannot rely on the mpservers data structures (even if there is radio data), because in FGCom-mumble potential other clients are also participating (like radio-playback bots for ATIS etc!). So we really need to use mumbles plugin messages.
* Basicly the libmumble will run its own threads for networking. Upon receiving mumble audio or mumble-plugin data, callback functions would be called from the lib (https://github.com/mumble-voip/libmumble/issues/18#issuecomment-1868498537):
** Incoming audio data need to be processed by the fgcom-mumble plugin functions, and then the result handed over into fgfs audio out handling.
** Incoming plugin data needs to be fed into the fgcom-mumble internal remote data struct (just hand the data into the existing data parser).
* Pressing the already existing fgfs PTT button
** would need to send plugin data to mumble, to inform other clients. This is currently done by calling a mumble client function. It would probably be enough, if fgfs core supplied an implemention that calls the appropriate libmumble function and hands over the data.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} And what about libmubmles dependencies, like OpenSSL?
*** technically, how to include that all into the existing build system?

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[de:FGCom-mumble]]

FGCom-mumble

2025-01-08T10:29:55Z

Hbeni: /* Idea to integrate into FGFS */

'''FGCom-mumble''' simulates radio communication based on the VoIP software [https://www.mumble.info/ Mumble]. It integrates fully with the radio stack of your FlightGear plane, allowing you to communicate with other pilots and airspace controllers during your flight. It simulates a global, continuous radio frequency spectrum.

FGCom-mumble is an alternative to the already known [[FGCom]] client and [https://forum.flightgear.org/viewtopic.php?t=30691 FGExtend].

FGCom-mumble leverages the plugin mechanism introduced by Mumble 1.4.0 and just needs a precompiled plugin loaded by a stock Mumble client.
You can download the latest release from https://github.com/hbeni/fgcom-mumble/releases.

{{Infobox Software
|title = FGCom-mumble
|logo = FGCom-mumble_logo.png|128px
|developedby = Benedikt Hallinger
|developmentstatus = Active
|type = Radio/Communication
|latestrelease = [https://github.com/hbeni/fgcom-mumble/releases see release page]
|initialrelease = 1.0.0 (17.01.2022)
|writtenin = C++/Lua/Java/PHP
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v3
|website = https://github.com/hbeni/fgcom-mumble
}}

==Servers ==

*The main FGCom-mumble test server is <code>mumble://fgcom.hallinger.org/fgcom-mumble</code>
*The status page for that service showing all connected clients is at: https://fgcom.hallinger.org/
*On first connection Mumble client will ask whether to trust the certificate presented by the server. Currently the server certificate has following details:

<pre>Common Name: Murmur Autogenerated Certificate v2
Valid from: Mon. Dec. 7 21:12:40 2020 GMT
Valid to: Sun. Dec. 2 21:12:40 2040 GMT
Serial: 3031
Public Key: 2048 bits RSA
Digest (SHA-1): E6:9A:FA:62:2C:48:4D:73:95:D7:EE:0E:14:0D:5A:C2:AE:14:1C:31
Digest (SHA-256): 50:CE:17:63:FB:FC:40:03:B4:BF:8F:1F:84:35:4C:BA:5D:5C:BE:E4:AD:F9:8C:D8:45:1F:C7:28:EB:CA:3A:C0</pre>

It is always a good idea to verify if the signature matches.

==Project main goals==
*Provide communication with geographic and channel separation
*Provide a realistic radio simulation
*Ease of use for the end user/pilot
*Arbitrary frequency support
*ATIS recording and playback
*Radio station broadcast support
*Landline/Intercom support
*RDF detection for clients
*Ease of server side installation and operation
*Standalone nature (no dependency on FlightGear)
* Capability to be integrated into FlightGear, with the option to support third party applications (ATC, but also other flight simulators)
*Modularity, so individual component implementations can be switched and its easy to add features
*Good and complete documentation

== Installation and setup==
The latest release can be fetched from [https://github.com/hbeni/fgcom-mumble/releases GitHub] ([https://github.com/hbeni/fgcom-mumble/actions nightly build] also has debug versions).

The provided [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#install--setup-for-the-client README] has detailed instructions on the needed prerequisites and installation procedures.

Someone even made an install video :) https://www.youtube.com/watch?v=jTRzfVfkgZE and https://www.youtube.com/watch?v=boHsPVTSddk
(thanks mate, well done! however HF is actually simulated already :)

In short:
* Have a stock Mumble client >= 1.4 running, and load the plugin (mumble settings/plugins page)
* Join a channel named `fgcom-mumble` (on a >= 1.4 mumble server)
* Add the `fgfs-addon` folder of the client release as FlightGear Addon in your launcher
* Start FlightGear and use your plane's radio stack (it uses default FGCom buttons, see below)

==Usage==
FlightGear's FGCom-mumble protocol uses the default FGCom buttons:
* When you want to talk on COM1 you have to press {{Key press|Space}}. While transmitting you can not hear other pilots trough the used radio (they are half-duplex).
* You can also talk on COM2 by pressing {{Key press|Shift|Space}}.
* since FGCom-mumble 1.2.0:
** For COM3 you use {{Key press|Alt|Space}} (previously you need to define a custom keybind),
** Intercom is available in full-duplex with {{Key press|Ctrl|Space}}

Any radio can also accessed by the COMBar (open from ''Menu/Multiplayer/FGCom-mumble'').

If you want to try it out without FlightGear, you can also start the supplied RadioGUI.

=== How to test your setup?===
First, make sure Mumble is working reliably by talking to other people. Either disable the plugin, or be sure you are outside any radio channel (starting with `fgcom-mumble`).

The plugin alters Mumble's receiving audio stream. It adds static noise depending on the radio signal quality, or cancels out all audio when not in range. The outgoing audio stream is not altered in any way.

If the server supports it (in essence there is a bot-manager running and a `fgcom-recorder-bot` listening) you may do a traditional echo test by tuning `910.00` and start to talk. The recorder-bot will record that (he writes that into mumbles chat) and spawn an echo bot at your position, replaying your message (so you will hear yourself like others will hear you).

===Troubleshooting===
For troubleshooting, refer to the projects [https://github.com/hbeni/fgcom-mumble/blob/master/README.md#troubleshooting README] as it has further suggestions.

If it's nothing setup related, an easy fix is to just restart mumble (the plugin will reinitialize itself).

===Compatibility ===
FGCom-mumble supports the legacy FGCom UDP protocol and thus should be compatible to clients supporting that. However, it also features some new UDP fields.

*FlightGear is supported through an [https://github.com/hbeni/fgcom-mumble/tree/master/client/fgfs-addon FlightGear addon]. This assumes the default radio implementation and works with at least the C172P and the C182S.
*[[ATC-pie]] has built in support already (be sure to activate "FGCom-mumble" instead of just "FGCom" in the settings).
*[[OpenRadar]] currently supports just COM1 ([https://sourceforge.net/p/openradar/tickets/5/ ticket pending]). To use COM2 and more, you need to either start several mumble instances, or use FGCom-mumble's RadioGUI.
:There is a patched version of OpenRadar with FGCom-mumble and 8.33 channel tuning support available here: http://fgcom.hallinger.org/OpenRadar_fgcom-mumble.jar

====Known incompatibilities====
* The UFO aircraft rebinds {{Key press|Space}} so you can't transmit on the radio. As a workaround you can use the COMBar that comes integrated with the FGFS addon.

==RadioGUI==
The FGCom-mumble RadioGUI is a small Java 8 application that can send the FGCom-mumble UDP messages to the Mumble plugin.

Inside the GUI, you can pick your location from a map and then setup and use your radio stack.
That said, the RadiGUI can be used instead (or additionally to) FGFS to participate on the simulated radio net.

==Server side==
By design, all that is needed is a standard Murmur server (version 1.4.0 or later) and a specially named channel (it has to start with `fgcom-mumble`). This is enough to let the plugin do its work. The entire channel is treated as a single, worldwide continuous radio frequency spectrum.

Additional features are implemented using server side Lua bots (which may run somewhere else):
* ATIS recording and broadcasting
* Radio program broadcasting (OGG playback on a frequency), [https://github.com/hbeni/fgcom-mumble/wiki/How-to-create-a-custom-NDB Custom NDB beacons]
* Status page data collection

A status page showing client details is available as a PHP website, that gets its data fed from the fgcom-status-bot.

Detailed installation and operation documentation is shipped with the releases, but is also [https://github.com/hbeni/fgcom-mumble/blob/master/server/Readme.server.md online].

==How does it work? (technical information)==
The technical details are specified and described in the various readme files of the projects source code (as a starter read the [https://github.com/hbeni/fgcom-mumble/blob/master/Readme.architecture.md Readme.architecture.md]).

Basicly, all users join the same mumble channel and run the fgcom-mumble plugin. The plugin knows everything necessary from the participating users (like radios used, frequencies tuned, locations, etc) and based on that information mutes or plays incoming voice messages from the other users. Based on signal quality, static noise is mixed in for more fun and a more realistic experience.
Because the voice of other users is muted, it is a design wise out-of-the-box feature that brings frequency and location separation but allows everyone to stay in the same mumble channel.

==Related content==
*[https://github.com/hbeni/fgcom-mumble/wiki FGCom-mumble GitHub wiki] with hints etc
*[https://github.com/hbeni/fgcom-mumble/blob/master/README.md FGCom-mumble README.md] Main readme of the project bringing all the details you always wanted to know

===Forum topic===
*The {{forum link|t=37644|title=FGCom-mumble}} has development discussions and release announcements
*{{forum link|p=374950|title=Re: EDDF-Triangle}} and {{forum link|p=374970|title=Re: EDDF-Triangle}} - Compatibility and differences between FGCom, FGCom-mumble and Mumble

===FlightGear Newsletter===
*[[FlightGear_Newsletter_June_2020]]: First prototype announced
*[[FlightGear_Newsletter_July_2020]]: Load tests successful, RDF implemented, Live-Status page added
*[[FlightGear_Newsletter_August_2020]]: More testing, new HF/VHF/UHF models, auto-updater
*[[FlightGear_Newsletter_September_2020]]: Mumble API changes, distributed deployment, configuration trough INI, statistics
*[[FlightGear_Newsletter_October_2020]]: More API changes, proper 8.33kHz/25kHz overlap, RadiGUI added
*[[FlightGear_Newsletter_November_2020]]: Test server announced
*[[FlightGear_Newsletter_December_2020]]: Release 0.8.0 bringing networking capability
*[[FlightGear_Newsletter_April_2021]]: RDF reworked, 0.12.0 announced, MacOS support
*[[FlightGear_Newsletter_May_2021]]: Better airliner support, announced 0.13.0 and 0.14.0, restructured release package structure
*[[FlightGear_Newsletter_June_2021]]: 0.14.1 announced, updater bugfixes
*[[FlightGear_Newsletter_July_2021]]: 0.14.2 announced, updater bugfixes part II
*[[FlightGear_Newsletter_January_2022]]: '''1.0.0 released, Mumble 1.4 hit the light'''

==Screenshots==
<gallery>
Fgcom-mumble_statuspage-0.6.0.png|Statuspage 0.6.0
FGCom-mumble_radioGUI-0.6.0.png|RadiGUI 0.6.0
</gallery>

== Idea to integrate into FGFS ==
{{progressbar|10|10}} {{pending}}

ML Discussion: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1919A28D-44D8-46F0-8A65-A5633A8AB743%40hallinger.org/#msg58717212

Using [https://github.com/mumble-voip/libmumble libmumble], a standalone mumble c++17 library, we could integrate FGCom-mumble directly into FlightGear. This way, FGFS would talk "mumble" to a mumble server and the plugins functions would be integrated into the core. For pilots, a simple "click" to connect in the multiplayer would be enough to participate, while having all the advanced features of fgcom-mumble available (like custom NDBs, radio stations; as well as the possibility for other clients (ATC!) to participate easily on the radio spectrum).

A main idea is also to use the existing fgcom-mumble code to avoid double work. But otoh maybe a direct rewrite of the core stuff may be cleaner; most of the magic is in the fgcom-mumble radio model code anyway, so we might just use some bits, if that is possible?

libmubmble is not yet API-stable (but should be working), but there was already a [https://github.com/mumble-voip/libmumble/issues/18 first dicussion] about feasability and basic mechanics:
* From FGCom-mumbles side, we need to integrate the data structures into the core. So radios need to be registered, etc. This should not be too hard
** we probably just need to not run the UPD-Server but send the needed data directly into the decoding function of it. At a later stage, we might better integrate that part, but for a first working solution, just creatig a FCGOM-mumble UDP-Packet string in FGFS and sending it periodically (or already on-demand?) into the udp-servers decoder function should be enough - it just creates some CPU overhead which should not be too bad and will establish the needed local data structure.
** Note, that we cannot rely on the mpservers data structures (even if there is radio data), because in FGCom-mumble potential other clients are also participating (like radio-playback bots for ATIS etc!). So we really need to use mumbles plugin messages.
* Basicly the libmumble will run its own threads for networking. Upon receiving mumble audio or mumble-plugin data, callback functions would be called from the lib (https://github.com/mumble-voip/libmumble/issues/18#issuecomment-1868498537):
** Incoming audio data need to be processed by the fgcom-mumble plugin functions, and then the result handed over into fgfs audio out handling.
** Incoming plugin data needs to be fed into the fgcom-mumble internal remote data struct (just hand the data into the existing data parser).
* Pressing the already existing fgfs PTT button
** would need to send plugin data to mumble, to inform other clients. This is currently done by calling a mumble client function. It would probably be enough, if fgfs core supplied an implemention that calls the appropriate libmumble function and hands over the data.
** also, the audio data needs to be fetched from the mic, and then handed over to libmumbles audio encoding and sending routine. This probably can somewhat be partly copied from the legacy fgcom implementation.
* Questions regarding fgfs currently are:
** {{tick}} (''Answer:'' use [[Howto:Create_new_subsystems|Subsystem]]) how to exactly the integration on fgfs side works. That needs peeks on fgcoms code as well as some discussion at the mailing list.
** how to integrate the libmubmle code into the fgfs build chain (its cmake).
*** {{tick}} legally: libmubmle has a [https://github.com/mumble-voip/libmumble/blob/master/LICENSE BSD 3-clause] licence, is that compatible?
*** {{tick}} And what about libmubmles dependencies, like OpenSSL?
*** technically, how to include that all into the existing build system?

[[Category:FGCom]]
[[Category:Air Traffic Control]]

[[de:FGCom-mumble]]

Aircraft maintenance

2024-10-25T07:19:30Z

Hbeni: /* Attitude indicator */

Some [[Bugs|bugfixes]] and improvements require [[aircraft]] to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest [[FlightGear]] version. The following ''Airworthiness Directives'' and ''Aviation Maintenance Alerts'' issued by the ''FlightGear Aviation Administration'' (FAA) should be considered for aircraft maintenance (A/B/C/D checks).

== JSBSim ==
=== Deprecated engine properties "egt_degc" and "egt_degf" ===
Properties will be removed with a future [[JSBSim]]/FlightGear version. Replace "_" with "-", i.e. use:
/engines/engine[..]/egt-degc
/engines/engine[..]/egt-degf

=== Ground reactions ===
As of FlightGear 3.1 JSBSim, just like YASim, supports ground effects like bumpiness, solid-ground detection and adjusting of friction actors. Actually JSBSim supports an extra feature, BOGEY contact points sink in a non-solid ground surface but STRUCTURE contact point do not, making it easy to define floats using STRUCTURE contact points.

See [http://forum.flightgear.org/viewtopic.php?f=66&t=22037 this forum topic] for more details and instructions on how to update your aircraft.

== Tanks ==
With >= FG2.4.0 the properties for mass, volume and density are interconnected and so are those representing the same property with just individual units. Aircraft should only set either mass or volume manually (i.e. on start-up), and NOT try to configure or compute both.
The fuel density has to be defined at start up or it defaults to 755kg/m^3 (Avgas).
Volume is derived from mass and vice versa. The last set property wins. The used formula is
mass = volume * density
or it's variation
volume = mass / density
Internally, content(mass), density(mass per volume), capacity(volume) and the unusable fuel(volume) are stored in metric units and the (US-)English units are derived by applying hard-coded conversion factors:
* LBS_PER_KG = 2.20462262
* KG_PER_LBS = 1.0/LBS_PER_KG
* USGAL_PER_M3 = 1000.0/3.785411784
* M3_PER_USGAL = 1.0/USGAL_PER_M3
* IMPGAL_PER_M3 = 1000.0/4.54609
* M3_PER_IMPGAL = 1.0/IMPGAL_PER_M3
No property-value can ever become less than zero. Division by zero errors (e.g. if density=0.0) are internally avoided.

The value of the property "unusable-xxx" is constantly compared against "content-xxx" and drives the value of the boolean property "empty". If content is less than usable, empty is true.

All the individual tanks are summed up to the properties /consumables/fuel/total-fuel-xxx

=== Aircraft developer's best practice ===
To create and initialize the tank properties for you aircraft, define your basic set of properties for each tank in your aircraft's -set.xml:
<syntaxhighlight lang="xml">
<consumables>
<fuel>
<tank n="0">
<name type="string">Left Wing</name>
<capacity-gal_us type="double">64.0</capacity-gal_us>
<unusable-gal_us type="double">2.5</unusable-gal_us>
<level-gal_us type="double">50</level-gal_us>
</tank>
<tank n="1">
<name type="string">Right Wing</name>
<capacity-gal_us type="double">64.0</capacity-gal_us>
<unusable-gal_us type="double">2.5</unusable-gal_us>
<level-gal_us type="double">50</level-gal_us>
</tank>
</fuel>
</consumables>
</syntaxhighlight>
This will initialize and maintain /consumables/fuel/tank[0..1]/*

Alternatively, just define the number of tanks and fill in the values later (e.g. from Nasal):
<syntaxhighlight lang="xml">
<consumables>
<fuel>
<numtanks>32</numtanks>
</fuel>
</consumables>
</syntaxhighlight>

This will initialize and maintain /consumables/fuel/tank[0..31]/*

Note: if /consumables/fuel/numtanks exist and at least one /consumables/fuel/tank exist, the latter takes precedence over numtanks.

== Instruments ==
=== Realistic NAV radio ===
With >= FG2.6.0 the NAV and DME radios are more realistic. Signals are "flickering" when at the edge of a station's range. The properties
/instrumentation/dme/in-range
/instrumentation/nav/in-range
may flicker on-off-on-... frequently. Some autopilots (mainly airliners) try to capture a localizer as soon as a NAV station is "in-range", which results in an issue when signal isn't stable yet. As a work-around, only use the properties above to enable/disable the NAV/DME cockpit display (to get the realistic display flickering effect), but use the property
/instrumentation/nav/signal-quality-norm
to detect a valid signal for the autopilot's capture logic, e.g. add a condition that requires a high signal strength, say above 0.9, to avoid capturing too early while the signal is still unstable.

=== DME vs NAV radio ===
Aircraft with DME displays must include a DME instrument. With <=FG2.4.0 is was enough to add a "nav" instrument in order to also get some DME properties - this is deprecated.
Add the DME instrument:
<dme>
<name>dme</name>
<number>0</number>
</dme>
The use of the NAV radio's DME properties is also deprecated. Instead of
/instrumentation/nav/dme-in-range
use
/instrumentation/dme/in-range
The deprecated DME properties are still supported with FG2.6.0, but will be removed with a later version.

=== Incorrect DME range displayed ===
Many aircraft (mainly airliners) do not display the correct DME distance.
To obtain the correct DME distance, use DME instrument properties - not the nav instrument's properties. For DMEs, do '''not''' use:
/instrumentation/nav/nav-distance
which does not reflect the correct DME distance. Instead use
/instrumentation/dme/indicated-distance-nm

=== DME/NAV display beyond station range ===
Many aircraft (mainly airliners) display DME and/or NAV information, even though the DME/VOR/ILS is out of range - or even when the selected station doesn't even provide DME/NAV information - which is not realistic. NAV/DME displays should have a condition respecting
/instrumentation/dme/in-range
for DME displays and a condition on
/instrumentation/nav/in-range
for NAV/ILS displays, and otherwise blank/disable the distance/direction/display.

=== Attitude indicator ===
The FG attitude indicator supports [http://en.wikipedia.org/wiki/Attitude_indicator caging], usually triggered by a push/pull switch next to the attitude indicator. The correct property name of FG's attitude indicator instrument is named
/instrumentation/attitude-indicator/caged-flag
Apparently a copy & paste issue has resulted in a large number of FlightGear aircraft incorrectly using the property
/instrumentation/attitude-indicator/caged
which has no effect. "caged" should be replaced by "caged-flag".

=== Heading Indicator ===
There are two implementations:
* A basic one: https://wiki.flightgear.org/Instrumentation#Heading_Indicator_(Suction-Driven)
* A advanced and very configurable one: https://wiki.flightgear.org/Instrumentation#Heading_Indicator_(Directional_Gyro)

Migrating from the former to the latter is basicly just a matter of switching the instrumentation.xml tag name.
You probably also need to tie the adjustment knob to the new property <code>align-deg</code> and look trough the available config options to set the behaviour (for example for tumbling etc)

== Sound ==
=== Stereo sound files unsupported ===
Stereo sound files can not (/no longer) be used for sound effects and must be converted to mono. Proper sound effects always required single channel wave sources. A 3D sound engine uses information on position, direction, speed of every source to ''render'' realistic 3D sound. This does '''not''' work with stereo files, since both channels would be rendered at the same position (no stereo effect anyway). Stereo files were usable with <=FG2.4.0, but resulted in many effects being broken (Doppler etc). To avoid such issues, >= FG2.6.0 produces a warning and rejects loading stereo files.

=== Avoiding sound file duplication ===
We have a large number of sound file duplicates in the FG repositories, which blow up the repository and download size. Generic sound files should be placed in the central /fgdata/Sound folder - and not be copied by individual aircraft. Check if a sound sample is available in the central "Sounds" folder, before copying it into an aircraft. New generic sounds may also be submitted to the central folder (use "git merge request" or mailing list) - which is better than producing loads of duplicates.

== FlightRecorder ==
{{Main article|Instant Replay}}
The default FlightGear flight recorder matches propeller/piston aircraft only. For >= FG2.6.0 the correct flight recorder configuration file matching the aircraft type should be selected. It is also possible to add custom properties.

== Rating System ==
{{Main article|Formalizing Aircraft Status}}
A new status rating system was introduced. Aircraft ratings should be encoded in the aircraft -set.xml file from where they are be picked up by launchers like FGRun, web pages etc.

== Parking positions ==
The new <tt>--parkpos=AVAILABLE</tt> option selects a fitting parking position, based on the dimensions, class and operator of the aircraft. The following lines should be added to the <sim> part of the aircraft's -set.xml.
<syntaxhighlight lang="xml">
<dimensions>
<radius-m type="double">10.0</radius-m>
<parkpos-offset-m type="double">0.0</parkpos-offset-m>
</dimensions>
<aircraft-class type="string">mil-fighter</aircraft-class>
<aircraft-operator></aircraft-operator>
<aircraft-data>
<path>/sim/dimensions/radius-m</path>
<path>/sim/dimensions/parkpos-offset-m</path> 
<path>/sim/aircraft-class</path>
<path>/sim/aircraft-operator</path>
</aircraft-data>
</syntaxhighlight>

[[Category:Aircraft enhancement]]

Instrumentation

2024-09-09T07:50:45Z

Hbeni: /* Magnetic Compass */

FlightGear's built-in '''Instrumentation system''' simulates basic instruments used in many aircraft and provide their output as [[Property|Properties]] to be used e.g. for [[Howto:Animate models|animating]] 3D instruments or [[Canvas]] instruments.

This article is meant to provide an overview over the instrumentation modules available and their configuration.

=== General configuration ===
The instrumentation modules to be available to an aircraft can be selected by the aircraft developer using an instrumentation XML configuration file. This file is called from the [[Aircraft-set.xml]]:<syntaxhighlight lang="xml">
<sim>
<instrumentation>
<path>Systems/my-aircraft-instrumentation.xml</path>
</instrumentation>
</sim>
</syntaxhighlight>A generic configuration file to be copied and customised can be found in Aircraft/Generic/generic-instrumentation.xml.

===== Common Elements =====
Instrument Root Path: typically '''/instrumentation/name[number]/''' e.g. '''/instrumentation/adf[1]/''' for the second ADF.

Electric Power Path (where applicable): typically '''/systems/electrical/outputs/name[number]''' e.g. '''/systems/electrical/outputs/comm[0]''' for the first comm radio.
{| class="wikitable"
|name
|typically used for the instrument's root path and, where applicable, electric power path
|-
|number
|used to differentiate between multiple objects using the same name.
|}
All instruments that inherit '''AbstractInstrument''' additionally accept the following config settings:
{| class="wikitable"
|power-supply
|custom property to be used as the electric power path
|-
|minimum-supply-volts
|minimum electric voltage at which the instrument works
|}

=== Instrument Modules ===

====[[ADF|ADF (Automatic Direction Finder)]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/adf.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/adf.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
This instrument simulates an [[ADF|Automatic Direction Finder]] used for navigating using [[NDB|Non-Directional Beacons]].

'''Configuration'''<syntaxhighlight lang="xml">
<adf>
<name>adf</name>
<number>0</number>
</adf>
</syntaxhighlight>

====[[Airspeed|Airspeed Indicator]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/airspeed_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/airspeed_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<airspeed-indicator>
<name>airspeed-indicator</name>
<number>0</number>
<total-pressure>/systems/pitot/total-pressure-inhg</total-pressure>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<has-overspeed-indicator>0</has-overspeed-indicator>
<pressure-alt-source>/instrumentation/altimeter/pressure-alt-ft</pressure-alt-source>
<ias-limit>248.0</ias-limit>
<mach-limit>0.48</mach-limit>
<alt-threshold>13200</alt-threshold>
</airspeed-indicator>
</syntaxhighlight>

*Total Pressure: see [[FGproperties/Systems/Pitot]]
*Static Pressure: see [[FGproperties/Systems/static]]
*see also: {{Repo link|repo=fgdata|pre=$FG_ROOT|path=Docs/README.airspeed-indicator}}

====[[Altimeter]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/altimeter.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/altimeter}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<altimeter>
<name>altimeter</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<quantum>0</quantum>
<tau>0</tau>
</altimeter>
</syntaxhighlight>

*Static Pressure: see [[FGproperties/Systems/static]]
*Quantum: TODO
* Tau: TODO

====[[Attitude indicator|Attitude Indicator (suction-powered)]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator>
<name>attitude-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.5</minimum-vacuum>
<limits>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</limits>
<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</attitude-indicator>
</syntaxhighlight>

* Note, the <code><minimum-vacuum></code>, <code><gyro></code> and <code><limits></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.
*Suction: see [[Aircraft systems#Vacuum]]

====Attitude Indicator (Electric)====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator_electric.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator_electric.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator-electric>
<name>attitude-indicator</name>
<number>0</number>


<config>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</config>
</attitude-indicator-electric>
</syntaxhighlight>

==== Clock ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/clock.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/clock.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<clock>
<name>clock</name>
<number>0</number>
</clock>
</syntaxhighlight>

==== Comm Radio ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/commradio.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/commradio.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<comm-radio>
<name>comm</name>
<number>0</number>
<eight-point-three>0</eight-point-three>
</comm-radio>

</syntaxhighlight>

* eight-point-three: Setting this to 1 (true) enables a simulation of the newer 8.33 kHz frequency raster
* see also [[Kx165]]

==== DCL GPS ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dclgps.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dclgps.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Information (from Source Code)'''<syntaxhighlight lang="c++">
// dclgps.cxx - a class to extend the operation of FG's current GPS
// code, and provide support for a KLN89-specific instrument. It
// is envisioned that eventually this file and class will be split
// up between current FG code and new KLN89-specific code and removed.
</syntaxhighlight>

==== [[Distance measuring equipment|DME (Distance Measuring Equipment)]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dme.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dme.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<dme>
<name>dme</name>
<number>0</number>
</dme>
</syntaxhighlight>

==== [[Global Positioning System|GPS (Global Positioning System)]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gps.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gps.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gps>
<name>gps</name>
<number>0</number>
</gps>
</syntaxhighlight>

==== GSDI/GSDA (Ground Speed Drift Angle Indicator) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gsdi.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gsdi.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gsdi>
<name>gsdi</name>
<number>0</number>
</gsdi>
</syntaxhighlight>This instrument configuration is not included in generic-instrumentation.xml. See the [[EC130]] for an aircraft implementing this instrument.

==== [[Avionics and instruments#Directional Gyro|Heading Indicator (Directional Gyro)]] ====

This is a realistic and highly configrable directional gyro based heading indicator. It can be either electrical or
suction driven and supports the gyro based errors like precession drift and transport wander.

{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_dg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_dg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}

'''Configuration'''

By default, the instrument is electrically driven and powered by '''/systems/electrical/outputs/DG[number]''' (for backwards-compatibility reasons)
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
</heading-indicator-dg>
</syntaxhighlight>

Like with most other electrically driven instruments you can explicitely set the power source:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<power-supply>/systems/electrical/outputs/heading-indicator</power-supply>
<minimum-supply-volts>12.0</minimum-supply-volts>
</heading-indicator-dg>
</syntaxhighlight>

To make it vacuum driven instead:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.0</minimum-vacuum> 
</heading-indicator-dg>
</syntaxhighlight>

You can optionally configure the instruments error behaviour and limits (to disable, set accordingly).
The defaults given in c++ are for demonstration and not realistic so these might be better:
<syntaxhighlight lang="xml">
<limits>
<yaw-limit-rate>11.5</yaw-limit-rate> 
<g-limit-lower>-0.8</g-limit-lower> 
<g-limit-upper>1.8</g-limit-upper> 
<yaw-error-factor>0.033</yaw-error-factor> 
<g-error-factor>0.033</g-error-factor> 
<g-limit-tumble-factor>1.5</g-limit-tumble-factor> 
<g-node>/accelerations/pilot-gdamped</g-node> 
<g-filter-time>10.0</g-filter-time> 
<yaw-rate-source>/orientation/yaw-rate-degps</yaw-rate-source> 
</limits>
<gyro>
<minimum-spin-norm>0.8</minimum-spin-norm> 
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
<heading-source>/orientation/heading-deg</heading-source> 
</syntaxhighlight>

The instrument has a built-in damping filter for the g-node, so spikes do not trigger tumbling. If tuning this is not sufficient, you can specify a custom source property.

'''Runtime configuration'''
The limits and gyro config are exposed to the instruments propoerty tree and can be changed at runtime.

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>caged-flag</code>
|Make the gyro caged. Use this to quickly stop tumbling (or prevent it in the first instance).
|-
|<code>align-deg</code>
|Should be used by the instruments model to rotate the disc, countering instrument errors.
|-
|<code>latitude-nut-setting</code>
|Set to the factory setting. At the nut's latitutde (<code>-90</code> to <code>90</code>) the precession by earths rotation is countered by a small weight on the gimbal.
|}

====[[Avionics and instruments#Directional Gyro|Heading Indicator (Electric Flux-Gate Compass)]]====
The flux-gate heading indicator always points to magnetic north automatically.

{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_fg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_fg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator-fg>
<name>heading-indicator-fg</name>
<number>0</number>
</heading-indicator-fg>

</syntaxhighlight>

* Powered by '''/systems/electrical/outputs/heading-indicator-fg[number]'''

==== Heading Indicator (Suction-Driven) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading-indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading-indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
</heading-indicator>
</syntaxhighlight>

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>offset-deg</code>
|Read/write; Gyro drift is reflected in this property, and can be countered by altering the value. If not initialized at instrument init time, will be synced to "/environment/magnetic-variation-deg" automatically.
|}

* Note, this is an unrealistic/simple instrument. For better realism options, you should use the "Heading Indicator (Directional Gyro)", see above.

* Suction: see [[Aircraft systems#Vacuum]]

==== King KR 87 Digital ADF (Automatic Direction Finder) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/kr_87.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/kr_87.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<KR-87>
<name>kr-87</name>
<number>0</number>
</KR-87>
</syntaxhighlight>

==== [[Avionics and instruments#Compass|Magnetic Compass]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mag_compass.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mag_compass.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<magnetic-compass>
<name>magnetic-compass</name>
<number>0</number>

<deviation>
<table>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>30</ind>
<dep>3</dep>
</entry>

<entry>
<ind>330</ind>
<dep>-2</dep>
</entry>
</table>
</deviation>
</magnetic-compass>
</syntaxhighlight>

* Deviation Table: This can be used to simulate [[Avionics and instruments#Magnetic deviation|Magnetic deviation]], e.g. to reflect what's written on a textured deviation card next to the compass. Can also be a property that is beeing read and dynamically calculated (<code><deviation>/instrumentation/magnetic-compass/deviation-deg</deviation></code>), for example to implement powered avionics influencing the magnetic field.

By default the compass simulates a fixed axis compass disc pitched at 0°. A pitched compass disc has an additional reading error.
The compass property tree exposes a <code>/instrumentation/magnetic-compass/pitch-offset-deg</code> prop that can be set to a fixed pitch angle to simulate pitched mounts or manually pitchable compass casings. By dynamically calculating the property, you can offset the plane's <code>/orientation-pitch-deg</code>, essentially nulling the effect. By adding some filters you can simulate a freely pitchable compass disc for a constrained pitch angle; that is: a compass disc mounted on a pivot-pin bearing (like most modern compasses feature). For an example see the [https://github.com/c172p-team/c172p/blob/a8bc43674af51cfe093c03ae21e2e84467b456fb/Systems/instruments.xml#L599-L802 filter implementation from the C172p].

The instrument exposes <code>pitch-deg</code> and <code>roll-deg</code> properties to simulate pitching and rolling of the compass disc based on flight forces and fluid viscosity.
You can use them in your 3D-models animation configs.

The damping can be adjusted by setting it in the instrumentation.xml config:
<code><fluid-viscosity type="double">8.2</fluid-viscosity></code> (8.2 mm²/s is the value of kerosene and should be good in most cases).

==== [[Radio beacons#Marker beacons|Marker Beacon]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/marker_beacon.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/marker_beacon.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<marker-beacon>
<name>marker-beacon</name>
<number>0</number>
</marker-beacon>
</syntaxhighlight>

==== [[Ground proximity warning system|MK-VIII]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mk_viii.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mk_viii.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<mk-viii>
<name>mk-viii</name>
<number>0</number>
</mk-viii>
</syntaxhighlight>For more information, see [[Ground proximity warning system]].

==== Master Reference Gyro ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mrg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mrg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<master-reference-gyro>
<name>master-reference-gyro</name>
<number>0</number>
</master-reference-gyro>
</syntaxhighlight>for more information, see [https://scottbouch.com/mcfs/lightningt5t55/docs/ap101b-1003-5-6-15a-part1-chap7-al2-nov84-instruments.pdf Lightning T Mk.5 Instruments PDF, p. 4f.]

==== Navigation Radio ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/navradio.cxx}},{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/newnavradio.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/navradio.hxx}},{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/newnavradio.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<nav-radio>
<name>nav</name>
<number>0</number>
</nav-radio>
</syntaxhighlight>

==== Radar Altimeter ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/rad_alt.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/rad_alt.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<radar-altimeter>
<name>radar-altimeter</name>
<number>0</number>
<update-interval-sec>0.1</update-interval-sec>
</radar-altimeter>
</syntaxhighlight>

==== [[Avionics and instruments#Turn Coordinator|Slip/Skid Ball]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/slip_skid_ball.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/slip_skid_ball.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<slip-skid-ball>
<name>slip-skid-ball</name>
<number>0</number>
</slip-skid-ball>

</syntaxhighlight>

==== [[Tactical Air Navigation|TACAN]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tacan.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tacan.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<tacan>
<name>tacan</name>
<number>0</number>
</tacan>
</syntaxhighlight>

==== [[Traffic alert and collision avoidance system|TCAS]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tcas.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tcas.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
For '''configuration''', see [[Traffic alert and collision avoidance system#Instrument List]]

==== [[Transponder]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/transponder.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/transponder.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<mode type="int">1</mode>
<auto-ground type="string">/gear/gear/wow</auto-ground>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<airspeed-path type="string">/instrumentation/airspeed-indicator/indicated-speed-kt</airspeed-path>
<mach-path type="string">/instrumentation/airspeed-indicator/indicated-mach</mach-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
</transponder>
</syntaxhighlight>

* Mode
** 0 = Mode A
** 1 = Mode C
** 2 = Mode S
* Auto-Ground: Set property to be used to detect when the ground-bit (mode-S only) should be set
* Encoder/Airspeed/Mach Path: Set instrument properties to feed the transponder
* '''for more information, see [[Transponder]].'''

==== [[Avionics and instruments#Turn Coordinator|Turn Indicator]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/turn_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/turn_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<turn-indicator>
<name>turn-indicator</name>
<number>0</number>

<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</turn-indicator>
</syntaxhighlight>

* Note, the <code><gyro></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.

==== Vertical Speed Indicator (VSI) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/vertical_speed_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/vertical_speed_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<vertical-speed-indicator>
<name>vertical-speed-indicator</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
</vertical-speed-indicator>
</syntaxhighlight>

* Static Pressure: see [[FGproperties/Systems/static]]

Instrumentation

2024-09-09T07:42:02Z

Hbeni: /* Heading Indicator (Directional Gyro) */ See: https://sourceforge.net/p/flightgear/codetickets/2900/

FlightGear's built-in '''Instrumentation system''' simulates basic instruments used in many aircraft and provide their output as [[Property|Properties]] to be used e.g. for [[Howto:Animate models|animating]] 3D instruments or [[Canvas]] instruments.

This article is meant to provide an overview over the instrumentation modules available and their configuration.

=== General configuration ===
The instrumentation modules to be available to an aircraft can be selected by the aircraft developer using an instrumentation XML configuration file. This file is called from the [[Aircraft-set.xml]]:<syntaxhighlight lang="xml">
<sim>
<instrumentation>
<path>Systems/my-aircraft-instrumentation.xml</path>
</instrumentation>
</sim>
</syntaxhighlight>A generic configuration file to be copied and customised can be found in Aircraft/Generic/generic-instrumentation.xml.

===== Common Elements =====
Instrument Root Path: typically '''/instrumentation/name[number]/''' e.g. '''/instrumentation/adf[1]/''' for the second ADF.

Electric Power Path (where applicable): typically '''/systems/electrical/outputs/name[number]''' e.g. '''/systems/electrical/outputs/comm[0]''' for the first comm radio.
{| class="wikitable"
|name
|typically used for the instrument's root path and, where applicable, electric power path
|-
|number
|used to differentiate between multiple objects using the same name.
|}
All instruments that inherit '''AbstractInstrument''' additionally accept the following config settings:
{| class="wikitable"
|power-supply
|custom property to be used as the electric power path
|-
|minimum-supply-volts
|minimum electric voltage at which the instrument works
|}

=== Instrument Modules ===

====[[ADF|ADF (Automatic Direction Finder)]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/adf.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/adf.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
This instrument simulates an [[ADF|Automatic Direction Finder]] used for navigating using [[NDB|Non-Directional Beacons]].

'''Configuration'''<syntaxhighlight lang="xml">
<adf>
<name>adf</name>
<number>0</number>
</adf>
</syntaxhighlight>

====[[Airspeed|Airspeed Indicator]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/airspeed_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/airspeed_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<airspeed-indicator>
<name>airspeed-indicator</name>
<number>0</number>
<total-pressure>/systems/pitot/total-pressure-inhg</total-pressure>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<has-overspeed-indicator>0</has-overspeed-indicator>
<pressure-alt-source>/instrumentation/altimeter/pressure-alt-ft</pressure-alt-source>
<ias-limit>248.0</ias-limit>
<mach-limit>0.48</mach-limit>
<alt-threshold>13200</alt-threshold>
</airspeed-indicator>
</syntaxhighlight>

*Total Pressure: see [[FGproperties/Systems/Pitot]]
*Static Pressure: see [[FGproperties/Systems/static]]
*see also: {{Repo link|repo=fgdata|pre=$FG_ROOT|path=Docs/README.airspeed-indicator}}

====[[Altimeter]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/altimeter.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/altimeter}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<altimeter>
<name>altimeter</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<quantum>0</quantum>
<tau>0</tau>
</altimeter>
</syntaxhighlight>

*Static Pressure: see [[FGproperties/Systems/static]]
*Quantum: TODO
* Tau: TODO

====[[Attitude indicator|Attitude Indicator (suction-powered)]]====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator>
<name>attitude-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.5</minimum-vacuum>
<limits>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</limits>
<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</attitude-indicator>
</syntaxhighlight>

* Note, the <code><minimum-vacuum></code>, <code><gyro></code> and <code><limits></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.
*Suction: see [[Aircraft systems#Vacuum]]

====Attitude Indicator (Electric)====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator_electric.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/attitude_indicator_electric.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator-electric>
<name>attitude-indicator</name>
<number>0</number>


<config>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</config>
</attitude-indicator-electric>
</syntaxhighlight>

==== Clock ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/clock.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/clock.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<clock>
<name>clock</name>
<number>0</number>
</clock>
</syntaxhighlight>

==== Comm Radio ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/commradio.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/commradio.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<comm-radio>
<name>comm</name>
<number>0</number>
<eight-point-three>0</eight-point-three>
</comm-radio>

</syntaxhighlight>

* eight-point-three: Setting this to 1 (true) enables a simulation of the newer 8.33 kHz frequency raster
* see also [[Kx165]]

==== DCL GPS ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dclgps.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dclgps.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Information (from Source Code)'''<syntaxhighlight lang="c++">
// dclgps.cxx - a class to extend the operation of FG's current GPS
// code, and provide support for a KLN89-specific instrument. It
// is envisioned that eventually this file and class will be split
// up between current FG code and new KLN89-specific code and removed.
</syntaxhighlight>

==== [[Distance measuring equipment|DME (Distance Measuring Equipment)]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dme.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/dme.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<dme>
<name>dme</name>
<number>0</number>
</dme>
</syntaxhighlight>

==== [[Global Positioning System|GPS (Global Positioning System)]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gps.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gps.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gps>
<name>gps</name>
<number>0</number>
</gps>
</syntaxhighlight>

==== GSDI/GSDA (Ground Speed Drift Angle Indicator) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gsdi.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/gsdi.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gsdi>
<name>gsdi</name>
<number>0</number>
</gsdi>
</syntaxhighlight>This instrument configuration is not included in generic-instrumentation.xml. See the [[EC130]] for an aircraft implementing this instrument.

==== [[Avionics and instruments#Directional Gyro|Heading Indicator (Directional Gyro)]] ====

This is a realistic and highly configrable directional gyro based heading indicator. It can be either electrical or
suction driven and supports the gyro based errors like precession drift and transport wander.

{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_dg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_dg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}

'''Configuration'''

By default, the instrument is electrically driven and powered by '''/systems/electrical/outputs/DG[number]''' (for backwards-compatibility reasons)
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
</heading-indicator-dg>
</syntaxhighlight>

Like with most other electrically driven instruments you can explicitely set the power source:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<power-supply>/systems/electrical/outputs/heading-indicator</power-supply>
<minimum-supply-volts>12.0</minimum-supply-volts>
</heading-indicator-dg>
</syntaxhighlight>

To make it vacuum driven instead:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.0</minimum-vacuum> 
</heading-indicator-dg>
</syntaxhighlight>

You can optionally configure the instruments error behaviour and limits (to disable, set accordingly).
The defaults given in c++ are for demonstration and not realistic so these might be better:
<syntaxhighlight lang="xml">
<limits>
<yaw-limit-rate>11.5</yaw-limit-rate> 
<g-limit-lower>-0.8</g-limit-lower> 
<g-limit-upper>1.8</g-limit-upper> 
<yaw-error-factor>0.033</yaw-error-factor> 
<g-error-factor>0.033</g-error-factor> 
<g-limit-tumble-factor>1.5</g-limit-tumble-factor> 
<g-node>/accelerations/pilot-gdamped</g-node> 
<g-filter-time>10.0</g-filter-time> 
<yaw-rate-source>/orientation/yaw-rate-degps</yaw-rate-source> 
</limits>
<gyro>
<minimum-spin-norm>0.8</minimum-spin-norm> 
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
<heading-source>/orientation/heading-deg</heading-source> 
</syntaxhighlight>

The instrument has a built-in damping filter for the g-node, so spikes do not trigger tumbling. If tuning this is not sufficient, you can specify a custom source property.

'''Runtime configuration'''
The limits and gyro config are exposed to the instruments propoerty tree and can be changed at runtime.

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>caged-flag</code>
|Make the gyro caged. Use this to quickly stop tumbling (or prevent it in the first instance).
|-
|<code>align-deg</code>
|Should be used by the instruments model to rotate the disc, countering instrument errors.
|-
|<code>latitude-nut-setting</code>
|Set to the factory setting. At the nut's latitutde (<code>-90</code> to <code>90</code>) the precession by earths rotation is countered by a small weight on the gimbal.
|}

====[[Avionics and instruments#Directional Gyro|Heading Indicator (Electric Flux-Gate Compass)]]====
The flux-gate heading indicator always points to magnetic north automatically.

{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_fg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading_indicator_fg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator-fg>
<name>heading-indicator-fg</name>
<number>0</number>
</heading-indicator-fg>

</syntaxhighlight>

* Powered by '''/systems/electrical/outputs/heading-indicator-fg[number]'''

==== Heading Indicator (Suction-Driven) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading-indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/heading-indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
</heading-indicator>
</syntaxhighlight>

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>offset-deg</code>
|Read/write; Gyro drift is reflected in this property, and can be countered by altering the value. If not initialized at instrument init time, will be synced to "/environment/magnetic-variation-deg" automatically.
|}

* Note, this is an unrealistic/simple instrument. For better realism options, you should use the "Heading Indicator (Directional Gyro)", see above.

* Suction: see [[Aircraft systems#Vacuum]]

==== King KR 87 Digital ADF (Automatic Direction Finder) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/kr_87.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/kr_87.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<KR-87>
<name>kr-87</name>
<number>0</number>
</KR-87>
</syntaxhighlight>

==== [[Avionics and instruments#Compass|Magnetic Compass]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mag_compass.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mag_compass.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<magnetic-compass>
<name>magnetic-compass</name>
<number>0</number>

<deviation>
<table>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>30</ind>
<dep>3</dep>
</entry>

<entry>
<ind>330</ind>
<dep>-2</dep>
</entry>
</table>
</deviation>
</magnetic-compass>
</syntaxhighlight>

* Deviation Table: This can be used to simulate [[Avionics and instruments#Magnetic deviation|Magnetic deviation]], e.g. to reflect what's written on a textured deviation card next to the compass. Can also be a property that is beeing read and dynamically calculated (<code><deviation>/instrumentation/magnetic-compass/deviation-deg</deviation></code>), for example to implement powered avionics influencing the magnetic field.

By default the compass simulates a fixed axis compass disc pitched at 0°. A pitched compass disc has an additional reading error.
The compass property tree exposes a <code>/instrumentation/magnetic-compass/pitch-offset-deg</code> prop that can be set to a fixed pitch angle to simulate pitched mounts or manually pitchable compass casings. By dynamically calculating the property, you can offset the plane's <code>/orientation-pitch-deg</code>, essentially nulling the effect. By adding some filters you can simulate a freely pitchable compass disc for a constrained pitch angle; that is: a compass disc mounted on a pivot-pin bearing (like most modern compasses feature). For an example see the [https://github.com/c172p-team/c172p/blob/a8bc43674af51cfe093c03ae21e2e84467b456fb/Systems/instruments.xml#L599-L802 filter implementation from the C172p].

==== [[Radio beacons#Marker beacons|Marker Beacon]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/marker_beacon.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/marker_beacon.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<marker-beacon>
<name>marker-beacon</name>
<number>0</number>
</marker-beacon>
</syntaxhighlight>

==== [[Ground proximity warning system|MK-VIII]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mk_viii.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mk_viii.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<mk-viii>
<name>mk-viii</name>
<number>0</number>
</mk-viii>
</syntaxhighlight>For more information, see [[Ground proximity warning system]].

==== Master Reference Gyro ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mrg.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/mrg.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<master-reference-gyro>
<name>master-reference-gyro</name>
<number>0</number>
</master-reference-gyro>
</syntaxhighlight>for more information, see [https://scottbouch.com/mcfs/lightningt5t55/docs/ap101b-1003-5-6-15a-part1-chap7-al2-nov84-instruments.pdf Lightning T Mk.5 Instruments PDF, p. 4f.]

==== Navigation Radio ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/navradio.cxx}},{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/newnavradio.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/navradio.hxx}},{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/newnavradio.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<nav-radio>
<name>nav</name>
<number>0</number>
</nav-radio>
</syntaxhighlight>

==== Radar Altimeter ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/rad_alt.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/rad_alt.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<radar-altimeter>
<name>radar-altimeter</name>
<number>0</number>
<update-interval-sec>0.1</update-interval-sec>
</radar-altimeter>
</syntaxhighlight>

==== [[Avionics and instruments#Turn Coordinator|Slip/Skid Ball]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/slip_skid_ball.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/slip_skid_ball.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<slip-skid-ball>
<name>slip-skid-ball</name>
<number>0</number>
</slip-skid-ball>

</syntaxhighlight>

==== [[Tactical Air Navigation|TACAN]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tacan.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tacan.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<tacan>
<name>tacan</name>
<number>0</number>
</tacan>
</syntaxhighlight>

==== [[Traffic alert and collision avoidance system|TCAS]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tcas.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/tcas.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
For '''configuration''', see [[Traffic alert and collision avoidance system#Instrument List]]

==== [[Transponder]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/transponder.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/transponder.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<mode type="int">1</mode>
<auto-ground type="string">/gear/gear/wow</auto-ground>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<airspeed-path type="string">/instrumentation/airspeed-indicator/indicated-speed-kt</airspeed-path>
<mach-path type="string">/instrumentation/airspeed-indicator/indicated-mach</mach-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
</transponder>
</syntaxhighlight>

* Mode
** 0 = Mode A
** 1 = Mode C
** 2 = Mode S
* Auto-Ground: Set property to be used to detect when the ground-bit (mode-S only) should be set
* Encoder/Airspeed/Mach Path: Set instrument properties to feed the transponder
* '''for more information, see [[Transponder]].'''

==== [[Avionics and instruments#Turn Coordinator|Turn Indicator]] ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/turn_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/turn_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<turn-indicator>
<name>turn-indicator</name>
<number>0</number>

<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</turn-indicator>
</syntaxhighlight>

* Note, the <code><gyro></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.

==== Vertical Speed Indicator (VSI) ====
{| class="wikitable"
|Source File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/vertical_speed_indicator.cxx}}
|-
|Header File
|{{Repo link|site=sf|repo=flightgear|path=src/Instrumentation/vertical_speed_indicator.hxx}}
|-
|extends
|{{Repo link|site=sf|repo=simgear|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<vertical-speed-indicator>
<name>vertical-speed-indicator</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
</vertical-speed-indicator>
</syntaxhighlight>

* Static Pressure: see [[FGproperties/Systems/static]]

Nasal library/string

2024-08-06T07:03:52Z

Hbeni: /* string.squeeze(s,length) */

{{Stub}}
{{Nasal Navigation}}
== String Handling ==
This page contains description of functions available in "$FG_ROOT\data\Nasal\strings.nas".
For string related functions in Nasal also see [[Nasal_library|Nasal library]] page.
UTF8 specific functions are from Nasal core library.

== One Character Functions ==
=== string.isalnum() ===
<syntaxhighlight lang="nasal">
string.isalnum();
</syntaxhighlight>
=== string.isalpha() ===
<syntaxhighlight lang="nasal">
string.isalpha();
</syntaxhighlight>
=== string.isascii() ===
<syntaxhighlight lang="nasal">
string.isascii();
</syntaxhighlight>
=== string.isblank() ===
<syntaxhighlight lang="nasal">
string.isblank();
</syntaxhighlight>
=== string.iscntrl() ===
<syntaxhighlight lang="nasal">
string.iscntrl();
</syntaxhighlight>
=== string.isdigit() ===
<syntaxhighlight lang="nasal">
string.isdigit();
</syntaxhighlight>
=== string.isgraph() ===
<syntaxhighlight lang="nasal">
string.isgraph();
</syntaxhighlight>
=== string.islower() ===
<syntaxhighlight lang="nasal">
string.islower();
</syntaxhighlight>
=== string.isprint() ===
<syntaxhighlight lang="nasal">
string.isprint();
</syntaxhighlight>
=== string.ispunct() ===
<syntaxhighlight lang="nasal">
string.ispunct();
</syntaxhighlight>
=== string.isspace() ===
<syntaxhighlight lang="nasal">
string.isspace();
</syntaxhighlight>
=== string.isupper() ===
<syntaxhighlight lang="nasal">
string.isupper();
</syntaxhighlight>
=== string.isxdigit() ===
<syntaxhighlight lang="nasal">
string.isxdigit();
</syntaxhighlight>
=== string.isxspace() ===
<syntaxhighlight lang="nasal">
string.isxspace();
</syntaxhighlight>
=== string.toupper() ===
<syntaxhighlight lang="nasal">
string.toupper();
</syntaxhighlight>
=== string.tolower() ===
<syntaxhighlight lang="nasal">
string.tolower();
</syntaxhighlight>

== String Functions ==
=== string.icmp(a,b) ===
Case insensitive string compare function.
<syntaxhighlight lang="nasal">
string.icmp(a,b);
</syntaxhighlight>

=== string.imatch(a,b) ===
Case insensitive match function.
<syntaxhighlight lang="nasal">
string.imatch(a,b);
</syntaxhighlight>
For example:
*string.imatch("alpha","beta") -> 0
*string.imatch("alpha","alpha") -> 1
*string.imatch("","alpha") -> 0
*string.imatch("","") -> 1

=== string.join(sep,list) ===
Join all elements of a list inserting a separator between every two of them. See [[Nasal_library#split()|split()]].
<syntaxhighlight lang="nasal">
string.join(sep,list);
</syntaxhighlight>

=== string.lc(str) ===
Return string converted to lower case letters.
<syntaxhighlight lang="nasal">
string.lc(str);
</syntaxhighlight>

=== string.match(str, patt) ===
Check if string <str> matches shell style pattern <patt>
<syntaxhighlight lang="nasal">
# Rules:
# ? stands for any single character
# * stands for any number (including zero) of arbitrary characters
# \ escapes the next character and makes it stand for itself; that is:
# \? stands for a question mark (not the "any single character" placeholder)
# [] stands for a group of characters:
# [abc] stands for letters a, b or c
# [^abc] stands for any character but a, b, and c (^ as first character -> inversion)
# [1-4] stands for digits 1 to 4 (1, 2, 3, 4)
# [1-4-] stands for digits 1 to 4, and the minus
# [-1-4] same as above
# [1-3-6] stands for digits 1 to 3, minus, and 6
# [1-3-6-9] stands for digits 1 to 3, minus, and 6 to 9
# [][] stands for the closing and the opening bracket (']' must be first!)
# [^^] stands for all characters but the caret symbol
# [\/] stands for a backslash or a slash (the backslash isn't an
# escape character in a [] character group)
#
# Note that a minus can't be a range delimiter, as in [a--e],
# which would be interpreted as any of a, e, or minus.
#
# Example:

string.match(name, "*[0-9].xml"); ... true if 'name' ends with digit followed by ".xml"
</syntaxhighlight>
=== string.normpath(path) ===
Removes superfluous slashes, empty and "." elements,
expands all ".." elements keeping relative paths,
and turns all backslashes into slashes.
The result will start with a slash if it started with a slash or backslash, it will end without slash.
<syntaxhighlight lang="nasal">
string.normpath(path);
</syntaxhighlight>
See also [[Nasal_library#resolvepath|resolvepath()]] function, which can be used to test if a file exists.

=== string.replace(str,old,new) ===
Replace all occurrences of 'old' by 'new'.
<syntaxhighlight lang="nasal">
string.replace(str,old,new);
</syntaxhighlight>
=== string.scanf(test,format,result) ===
Simple scanf function. Takes an input string, a pattern, and a vector.
It returns 0 if the format didn't match, and appends all found elements to the given vector.

Return values:
-1 string matched format ending with % (i.e. more chars than format cared about)
0 string didn't match format
1 string matched, but would still match if the right chars were added
2 string matched, and would not if any character would be added

<syntaxhighlight lang="nasal">
var r = string.scanf("comm3freq123.456", "comm%ufreq%f", var result = []);
</syntaxhighlight>
The result vector will be set to [3, 123.456].

=== string.squeeze(s,length) ===
Shorten string s to length by replacing characters in the middle by '...'.
(since 2020.4 / next as of 03.08.2024)

<syntaxhighlight lang="nasal">
var r = string.squeeze("FooBarBaz", 9);
</syntaxhighlight>
r now contains the string "Foo...Baz".

=== string.trim(str,lr[,func]) ===
Trim spaces at the left (lr < 0), at the right (lr > 0), or both (lr = 0) is default.
An optional function argument defines which characters should be trimmed:
<syntaxhighlight lang="nasal">
string.trim(a); # trim spaces
string.trim(a, 1, string.isdigit); # trim digits at the right
string.trim(a, 0, func(c) c == `\\` or c == `/`); # trim slashes/backslashes
</syntaxhighlight>
=== string.uc(str) ===
Return string converted to upper case letters.
<syntaxhighlight lang="nasal">
string.uc(str);
</syntaxhighlight>

=== string.compileTemplate(template,type=nil) ===
Get a function out of a string template for fast insertion of template parameters.
This allows to use the same templates as with most available tile mapping engines (eg. Leaflet, Polymaps).
Return a callable function object on success, and nil if parsing the templated fails.
<syntaxhighlight lang="nasal">
string.compileTemplate(template);
</syntaxhighlight>
Example (Build MapQuest tile url):
<syntaxhighlight lang="nasal">
var makeUrl = string.compileTemplate(
"http://otile1.mqcdn.com/tiles/1.0.0/map/{z}/{x}/{y}.jpg"
);
print( makeUrl({x: 5, y: 4, z: 3}) );

Output: http://otile1.mqcdn.com/tiles/1.0.0/map/3/5/4.jpg
</syntaxhighlight>

== UTF8 String Functions (Core) ==
=== utf8.chstr(unicode) ===
Returns a string containing the UTF8 representation of the specified unicode character value.
=== utf8.strc(string, index) ===
Returns the unicode character at the specified index within the UTF8 string. Dies on encoding error or overrun.
=== utf8.substr(string, start, len=nil) ===
As for regular substr(), but the indices are of UTF8 characters intead of bytes. Dies on encoding error or overflow.
=== utf8.size(string) ===
As for regular size() when called on a string, but returns the number of UTF8 unicode characters instead of bytes. Dies on encoding error.
=== utf8.validate(string, replace=`?`) ===
Checks the string for UTF8 validity. At every byte position where an encoding error is found, it replaces that byte with the specified replacement character (default is `?`). Note that the second argument is a number, not a string.

Swift

2024-08-05T07:45:00Z

Hbeni: /* Aircraft mapping (swift mapping tool) */

{{infobox subsystem
|image = FG swift connection.PNG
|name = swift-connection module
|started = 10/2018
|description = Connection module to swift pilot client which allows connections to FSD servers like VATSIM
|status = Released (FG 2020.1) and actively developed
|maintainers = Lars Toenning
|developers = Lars Toenning
|folders = {{flightgear source | path = src/Network/Swift/ }}
}}

This module allows [[FlightGear]] to connect to an externally running '''''swift''''' client.

''swift'' is an open-source pilot client for multiple flight simulators (FSX, P3D, FS9, XPlane, FG) and operating systems (Windows, MacOS, Linux). It allows connections to FSD servers like VATSIM. Further information about ''swift'' can be [https://datastore.swift-project.org/page/about.php found here].

== swift project status ==
''swift'' is actively developed [https://dev.swift-project.org/ here] and is in public beta status.

== Current features ==
The key features include:

* aircraft interpolation
* voice communication with ATC, support for new VATSIM codec planned
* model matching
* Database support for model mappings, users can contribute
* [[TCAS]] support

== Compatibility ==

<span style="color: red;">'''FlightGear 2019.1.2 and earlier isn't compatible with swift >= 0.11.0.'''</span>

For communication between FlightGear and swift dbus is used. To assure that both sides using the same commands for communication the FGSWIFTBUS_API_VERSION must match each other. Otherwise connection is not possible.

For compatibility see the following table:

{| class="wikitable" style="text-align:center; border: none; background: none;"
|-
!{{diagonal split header|swift|FlightGear}}
! scope="col"| <2019.2
! scope="col"| next
|-
! scope="row"| <=0.9.3
| style="background-color:#ff0000;"| -/-
| style="background-color:#00ff00;"| -/-
|-
! scope="row"| develop
| style="background-color:#ff0000;"| 1/-
| style="background-color:#ff0000;"| 1/-
|}

== Install/Setup ==
For an setup guide for FG see: https://swift-project.org/home/install/configure_fg/

Alot of good videos for the swift gui are on youtube: https://www.youtube.com/playlist?list=PLREsotdYQdGmeasv1x8vsNhiZGhankLoP

=== Linux specifics ===

==== Hotkeys support ====
https://swift-project.org/troubleshooting/linux_hotkeys/

On Linux, the swift client needs read access to the device nodes <code>/dev/input/event*</code>. In case your linux user does not have read access to this nodes, the swift client cannot grab keyboard events, and thus the PTT assigned keybind will not work.

To fix, for example in Debian 12, you just need to add a udev rule from the link above and reboot.

== Aircraft mapping (swift mapping tool) ==
For correct aircraft loading and parsing into swift you need to add FG's model directories.
The supported folders are:
* <tt>[[$FG_ROOT]]/AI/Aircraft</tt>
* Any other folder which contains user-flyable airplanes (in separate folders, one per plane). Note, that you need to add the folder containing the actual .ac/xml model, not the one with the -set.xml, as the latter won't work.

=== Note for Windows users ===
Starting with swift 0.9.1, swift automatically adds the sim and model paths if FlightGear was installed through the installer.

== WIP video ==
{{#ev:youtube|l5O3tRobYPY}}

[[Category:Software]]

Suggested Flights

2024-05-29T09:10:39Z

Hbeni: /* Australia and Oceania */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

== Hawai'i waterfalls tour ==
This flight will let you discover some of the famous Hawai'ian waterfalls, visiting the Islands of Kauai and Oahu.
{{note| Despite the scenery is very nice, the waterfalls are mostly not modeled (as of 5/2024)}}

* [https://skyvector.com/?ll=21.82733715471215,-158.96200561400335&chart=301&zoom=5&fpl=%20PHBK%202211N15938W%202206N15930W%202204N15925W%20LIH%202135N15817W%202138N15802W%202120N15746W%202116N15748W%20PHNL SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip except the VORTAC LIH 113.500 to cross the sea.
* Trip takes around 90 minutes air time at 110 KTAS.

First part of the trip:
* Start at Parking sands (PHBK), runway 34
* Takeoff, climb to 5000ft and follow the northern coast at about a heading of 030° until you reach Crawlers Ledge (about 8 minutes flight time).
* Turn southeast into the very dominant embayment and watch out for Hanakoa Falls, our first waterfall to visit.
* To your left should be a very dominant valley behind the ridge, featuring a river. Now climb to 6000ft and follow that valley southeastish and visit the famous Weeping wall waterfalls behind the ridge at the end of the valley.
* Bank left slightly (~100° heading), descend to 3000 ft and aim for Wailua waterfalls at the south side of the small hill near the coast (between the two towns).

This concludes the islands waterfalls after about 20 minutes flight.

Now either land at Lihue Airport (PHLI) to your right for a break, or continue the trip and intercept VORTAC LIH 113.500 radial 99/TO. Follow the radial to cross the Kauai Channel until you reach the tip of Oahu Island (the crossing of 63NM takes about 30 minutes at 120 knots. You may also opt to skip and start at PHDH).

* Follow overfly Kawaihapai Airfield (PHDH) and follow the northern coast.
* Shortly you will ovefly a prominent bend from east to nothertheast in the coast, still follow the coast. Note the windfarm appearing to your right ahead.
* Over Waimea (just before the very visible sand beach), turn right and fly to the inland behind (north of) the windfarm. Shortly after passing the wind turbines, look out for Waimea waterfalls.
* Follow the mountains to the southeast of the island and slowly climb to 4000ft (the left side is more rough and scenic).
* North of Diamond Head (a big crater at the south tip of the island) there are several waterfalls (roughly in the middle between Diamond head in the south and Kaneohe in the north), as well as very nice streams coming down the ridge. Also the north side of the ridge is very nice, so consider doing a circle over there.
* Continue south over Diamond head and proceed to land at Honolulu airport (PHNL).

This concludes the trip after about 1:30 hours.

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Suggested Flights

2024-05-29T06:34:53Z

Hbeni: /* Austrian alps soaring */ - no subsystem needed since years

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Suggested Flights

2024-05-29T06:32:54Z

Hbeni: /* Sightseeing the Alps in a C172 */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Using the AI subsystem, discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo &dagger;]].;

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Suggested Flights

2024-05-29T06:29:37Z

Hbeni: /* Sightseeing the Alps in a C172 */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

*Remember to give a look at the [[Suggested Airports]] page, where you can find a comprehensive list of high quality airports in FlightGear.
*If you enjoy these flights, please consider recording a flight and posting a link to it at the [[Suggested Prerecorded Flights]] page.

'''Remove before flight!''' 

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

This page includes the flights described on the [http://www.flightgear.org/places.html main website] and the suggested flights from the newsletters. It can serve as an archive for suggested flights from future [[FlightGear Newsletter|newsletters]] or can give a flight if creativity is low that month.

{{TOC limit|3}}

=Cross Continentals or World Tour=

* [[Breitling DC-3 World Tour]][[File:Rect17.png|thumbnail]]
* [[Flying the Hump]]

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
{{Location map | USA
| caption = Latitude: 39.790156 Longitude: -123.266403
| lat_deg = 39.790156
| lon_deg = -123.266403
}}

* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Half Moon Bay==
[[Image:KHAF-001.png|thumb|left|right after take off]]
[[Image:KHAF-002.png|thumb|right|Bridge]]
Start at [[KHAF|Half Moon Bay]], Runway 30, with 32km visibility; Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to [[KSFO]] for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as FlightGear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KHAF-003.png|thumb|left|surroundings]]
[[Image:World-KHAF.png|thumb|right|Latitude: 37.513333 Longitude: -122.501111]]
* [[KHAF|KHAF - Half Moon Bay]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KHAF.pdf chart]

no required scenery tile.
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSFO-001.png|thumb|left|Before landing]]
Use the default c172 airplane
* [[Cessna C172P]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KHAF --runway=30 --visibility=32000 --aircraft=c172
<div style="clear:both;"></div>
===Author===
April 2006 [[User:Hellosimon|Hellosimon]], format and extended by [[User:Francescobrisa|Francescobrisa]]

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:Grand_Canyon_Tour_4.jpg|700px|frameless|center]]
Being a special place, there are also special flight rules for VFR traffic around the Grand Canyon. There are multiple no-fly-zones set up and VFR traffic is only allowed to fly via the designated corridors. If you want to fly realistically, avoid these zones in FlightGear as well, following for example the [https://skyvector.com/?ll=36.18649251415492,-112.52223157994264&chart=230&zoom=5&fpl=%20KGCN%20VPGCF%20VPGCG%20VPGCD%20VPGCC%20VPGCA%203608N11252W%203609N11309W%201Z1%201G4%203AZ5 route shown here. (skyvector link)]

This flight takes you from KGCN, the Grand Canyon National Park airport, to 3AZ5, a small airfield called Hualapai located south of the Grand Canyon. Departing from KGCN, fly north-west bound to reach the canyon. From there, either follow the route shown on skyvector above, or fly visually through the canyon westbound towards 1Z1, Grand Canyon Bar Ten Airstrip. From there on, continue flying westward to 1G4. Called Grand Canyon West, 1G4 also marks about the western end of the canyon. To get to your destination 3AZ5, continue along the southern rim, flying eastward now. Shortly after leaving the breathtaking valley behind you, you will already reach your destination. Land and let your engine and your mind cool down from the special views :)

===Gallery===
<gallery>
Grand_Canyon_Tour_2.jpg
Grand_Canyon_Tour_3.jpg
Grand_Canyon_Tour_1.jpg
</gallery>

===Airports===
* KGCN - Grand Canyon National Park Airport - [https://www.aopa.org/destinations/airports/KGCN/details aopa.org]
* 1Z1 - Grand Canyon Bar Ten Airstrip - [https://www.airnav.com/airport/1Z1 airnav.com]
* 1G4 - Grand Canyon West - [https://www.airnav.com/airport/1G4 airnav.com]
* 3AZ5 - Hualapai - [https://www.airnav.com/airport/3AZ5 airnav.com]

===Suggested aircraft===
Most VFR aircraft with sufficiently big windows will serve the purpose, for example:
*[[Cessna C172P]]
*[[Optica]]
*[[Ryan_Navion]]
If you are more interested in flying helicopters, the [[Eurocopter EC130 B4]] with the Grand Canyon Helicopters livery might be for you.

===Links===
*[https://www.nps.gov/grca/learn/nature/upload/sfra.pdf Chart of the Grand Canyon special airspace, published by the National Park Service]
*[http://www.swaviator.com/html/issueJJ99/canyon.html An article about flying close to the Grand Canyon]
*[https://www.aopa.org/news-and-media/all-news/2017/april/flight-training-magazine/road-trip-grand-canyon AOPA Flight suggestion]

==Ranger Creek Airport==
[[File:21w-1.jpg|500px|center|Waiting for departure at Ranger Creek]]
Ranger Creek Airport is located in Greenwater, Washington, USA. Being wedged into the bottom of a steep canyon, you'll definitely need to be on your toes to get in and out of there. Switch on Advanced Weather and Live Data to experience what the winds can do to you in real life!
===Airports and coordinates===
* [[21W|21W - Ranger Creek]] - [http://www.airnav.com/airport/21W airnav.com]
===Gallery===
<gallery>
Ranger_Creek1.jpg|Departing between the mountains
Ranger_Creek_2.jpg|Looking back towards the airfield
Ranger_Creek_3.jpg|Downwind for approach back to Ranger Creek
</gallery>
===Suggested aircraft===
For this flight, the Piper PA-18 SuperCub is suggested, this is included in the [[Piper J3 Cub]] package

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>
===Author===
[[FlightGear Newsletter January 2011]] by [[User:Statto|Statto]], format and extended by [[User:Francescobrisa|Francescobrisa]].

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

== Wyoming - Grand Teton ==
Jackson Hole (KJAC) airport is located at around 6,400ft right next to the Teton range of mountains. The Tetons rise straight out of the plains, gaining over 5,000ft in 2 miles.

You will need the w120n40 scenery.

Tower frequency at KJAC is 118.07. Due to the high altitude, you will need to lean non-turbocharged piston aircraft before take-off. Don't forget that take-off distances will also be longer.

After take-off head to the North East. Grand Teton is the highest of the three peaks that rise straight from the flat-lands. Follow the line of mountains to the East, passing over Jenny Lake. After a couple of miles you will reach a huge lake. The large bulk of a mountain to the East is Mount Moran.

The Teton Mountain range is surprisingly thin - really just a string of mountains running SW-NE. Flying fast jets down the steep valleys is recommended.
* September 2006 by [[User:Stuart|Stuart]].

== Virginia Eastern Shore, Chesapeake Bay-Bridge Tunnel Sightseeing ==
[[Image:KTGI-001.png|thumb|left|before take off]]
[[Image:KTGI-002.png|thumb|right|right after take off]]

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.
*June 2006 by [[User:Sek|Sek]].

===Airports and coordinates===
[[Image:World-KTGI.png|thumb|right|Latitude: 37.8250835 Longitude: -75.9976665]]
* [[KTGI|KTGI - Tangier Island]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KTGI.pdf chart]
* [[KORF|KORF - Norfolk International]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KORF.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w80n30.tgz

===Suggested aircraft===
[[Image:KTGI-003.png|thumb|left|surroundings]]
[[Image:KORF-001.png|thumb|right|landing to KORF]]
I have tried this trip using a Seneca II
* [[Piper PA34-200T Seneca II]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KTGI --runway=20 --timeofday=dusk --aircraft=SenecaII
<div style="clear:both;"></div>

==Prince George to Calgary Springbank==
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW). Route created by reed, which can be seen at {{forum link|t=9772|text=the forums}}
*Published in [[FlightGear Newsletter November 2010]] By [[User:Cael|Cael]].
==Ketchikan to Juneau==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*October 2011 by [[User:PH-JBO|PH-JBO]] [[FlightGear Newsletter November 2011]]
==Searching Wizard Island==
*USA, Oregon, Klamath County
With one [[VORTAC]] behind our back we do an [[IFR]]/[[VFR]] search of Wizard Island, a mysterious place, a sacred place for native Americans. You might even find the <tt>Old Man of the Lake</tt>.

Don't pull up the map, that would spoil the surprise but I promise '''unique views'''. We will land on a short lawn runway. Terrain [[altitude]] will range from 4,000 to a max of 8,930 feet and down again. Total length of the trip will be about 50 NM. Select your aircraft with care. It must have one working navigational radio (VOR-DME), a strong engine, a strong undercarriage, must be capable of a good climb and a steep descend. I suggest to use Fair weather (Environment=>Global Weather). If needed remove some clouds (View=>Rendering Options=>Slider 3d Clouds to the left).
[[File:Mount Scott.jpg|thumb|250 px|Mount Scott (8,929 feet) just after depart from 2S7 (Two Sierra Seven). Wizard Island is just to the North-West of it.]]
*Park your aircraft on 2S7 (Two Sierra Seven), Chiloguin-State.
*Set [[NAV1]] on 115.9 (Klamath Falls VORTAC) and on radial 323<sup>o</sup> (Magnetic). We are at an [[elevation]] of 4,217 feet. Set QNH. Set heading bug at 275<sup>o</sup> (Magn).
*Take off an fly the course set with the heading bug.
*Intercept the radial.
*Monitor distance and you will find Wizard Island at 50 NM from Klamath Falls. The island has an elevation of 6,673 feet. I suggest a full 360<sup>o</sup> turn, take pictures.
*Set radial 318<sup>o</sup>, keep the same frequency. Do a new radial intercept.
*Try and find the airstrip (3S6, Three Sierra Six, Toketee-State) at 71 NM from Klamath Falls with an elevation of 3,361 feet, runway heading 275<sup>o</sup> (Magn). There are bumps around you should avoid.
*If you are capable of finding the island, finding the airstrip and landing without a crash, in one go..., you are a wizard.

Click [http://en.wikipedia.org/wiki/Crater_Lake this link] '''after''' you have landed so you know what amazing landscape you have seen.

*December 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter March 2012]].

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

==Copacabana to San Rafael over Lake Titicaca==
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the origin of the Amazon river since we are now at the starting point of that trip.
* October 2011 by [[User:PH-JBO|PH-JBO]], published in [[FlightGear_Newsletter_February_2012#Suggested_flights| Newsletter February 2012]].

==Origin of the Amazon River==
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

* October 2011 by [[User:PH-JBO|PH-JBO]]. Published [[FlightGear_Newsletter_March_2012|Newsletter May 2012]].

===Airports and coordinates===
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==Edinburgh to Oban==
See article: [[Edinburgh to Oban]].

==Oban to Prestwick==
The west coast of Scotland offers some stunning scenery and a number of small airfields and airports to land at on both the mainland and the small islands the dot the coast. The distances between the various airfields are quite small, and some of the runways are on the short side, so STOL or GA aircraft are ideal. The tour suggested here follows part of a microlight trip I made this month, photos of which can be found [http://www.nanjika.co.uk/photos/gigha/ here].

Oban airport (EGEO) lies on the west coast of Scotland, and offers fuel (both AVGAS and AVTUR) and a North/South tarmac runway.

From Oban it is just a 10 minute flight west to the grass airfield of Glenforsa (EG45), on the north-east coast of the island of Mull. Due to the hills and water channel, this airfield often gets quite strange wind patterns - the weather can be perfect in Oban, but much gustier and windier at Glenforsa. At times the windsocks at either end of the runway can blow in completely opposite directions!

Some distance north of Oban lie the airfields of the Isle of Skye (EG57) and Plockton (EG81). This is an excellent place from which to explore the mountains of the Isle of Skye, known as the Cuilins.

Heading south from Oban, one can follow the coast to the island of Jura, with it's distinctive hills (The Paps of Jura). From Jura one can head south to the island of Islay with its numarous malt whisky distilleries (many of which are modelled in FG). Islay Airport (EGPI) has extensive runways. From Islay head north east to the tiny island of Gigha. Despite it's small size, it too has an airfield (EG44), though the FG version is tarmac rather than grass.

From Gigha head east over the Mull of Kintyre, to the hilly isle of Arran, then north east to the Isle of Bute. Both islands have very small grass airstrips, which are sadly not present in FG. From Bute you can head south east to Prestwick International (EGPK), famous for being the only place Elvis touched down in the UK, and a fine place to end our tour.
*Published in [[FlightGear Newsletter July 2011]] by [[User:Stuart|Stuart]]

== Edinburgh to Dundee ==
Edinburgh Airport (EGPH) is located to the West of the city of Edinburgh and south of the Forth rail and road bridges. You'll need the w010n50 scenery and the latest set of objects from the scenery DB which include a number of models for the Edinburgh area.

From Edinburgh Airport, head north and circle the bridges, then follow the coast on the south eastwards past Edinburgh (watch out for the Castle!) and to East Lothian and Bass Rock - a volcanic plug in the sea that is host to thousands of sea-birds.

There are a number of sights in East Lothian, include a distillery.

If you wish to continue your tour, head back North, crossing the Firth of Forth to the Kingdom of Fife. Head approximated North West, tracking towards the Perth VOR (110.4). There is an airport here (Perth Scone, EGPT), but instead we will now track out on the 090 radial and pick up the ILS to Dundee Airport (108.10) landing beside the sea.
* September 2006 by [[User:Stuart|Stuart]].

==Austrian alps soaring==
Using the AI subsystem, discover the Austrian alps with a glider. [[Pinzgauer Spaziergang]]

== Sightseeing the Alps in a C172 ==
This tour will guide you to many of the most famous mountains, valleys, glaciers, snowfields, winter and summer vacation areas, etc. in the European Alps. In addition there are several hints to visit nearby areas of interest. On the tour you will visit Switzerland, Italy and France.
See the detailed description in: http://www.emmerich-j.de/FGFS/Alp-flying.pdf (mirrored to https://beni.hallinger.org/fgfs.nobackup/Alp-Tour-Jomo/)
*February 2011 by [[User:Jomo|Jomo]].

* The scenic trip does take about 2 hours.
* Skyvector route: https://skyvector.com/?ll=46.464097146192884,7.159790050777061&chart=301&zoom=6&fpl=%20LSZC%204700N00836E%204647N00840E%204642N00836E%204637N00835E%204634N00823E%204634N00812E%204633N00809E%204634N00805E%204634N00801E%204631N00803E%204624N00746E%204619N00745E%204618N00753E%204614N00752E%204612N00749E%204609N00747E%204603N00746E%204601N00745E%204600N00738E%204555N00724E%204555N00712E%204553N00703E%204547N00652E%204549N00649E%204604N00634E%20LSGG

== Salzburg to Zell am See via Hallstatt ==
[[File:LOWS-LOGO-LOWZ.jpg|thumb|The route for Salzburg to Zell am See via Hallstatt]]
This flight will bring you around a very scenic region of the austrian alps.
* [https://skyvector.com/?ll=47.5666119817603,13.107925427128999&chart=301&zoom=3&fpl=N0100A040%20LOWS%204735N01311E%204736N01339E%204733N01340E%204733N01343E%204735N01343E%204738N01355E%204727N01357E%20LOWZ SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 1 hr. air time at 120 KTAS.
* Fly at an altitude of about 4000ft or so (the entire trip can be done at that altitude safely).

* Start ''Salzburg (LOWS)''; follow the Autobahn in the valley to the southeast until you reach the fork at ''Golling''. To the south you see the Mountains of the ''Tennengebirge''.
* Alternatively (and I recommned that), you can also deviate sothwest around ''Mt. Untersberg'' (1972m, hosting germanys longest and deepest cave, the ''Riesending'') to visit lake ''Königsee'' and watch the peaks of the ''Steinernes Meer'' (the dominant and very famous ''Mt. Watzmann'', 2713m!) and north side of the ''Mt. Hochkönig''. You need to climb to at least 6200ft to cross the final ridge at the end of the lake valley. After crossing, descend to 4000ft, follow the valley and fly north at the next valley to rejoin the route.
* Turn east and follow the valley and hills, aim for a prominent V-shaped incision at the end. Fly through there and you suddenly break out at the lake ''Hallstätter See'', a fjord-like lake 125m deep.
* Follow the ''Hallstätter See'' to the south, on its western shore is the famous town of ''Hallstatt''. At the mountain to your right (north of Hallstatt) is a very old settlement dating back to the late bronce age (Hallstattzeit, c. 800–450 BC) and there was a very important Salt mine dating back to that time and important archeological grave findings.
Looking south you can see the ''Dachstein'' (2995 m), a high peak hosting the ''Hirlatzhöhle'', with 120km the twentiest longest and with 1560m sixth deepest cave of planet earth.
* Follow the valley east bend to ''Obertraun'', and then north over the ''Koppenpass'' and the town of ''Bad Aussee''.
* From ''Bad Aussee'', fly straight to the lakes ''Grundlsee'' and ''Toplitzsee'' (you can't see the latter yet).
* Between the two, turn southwards and aim for the reservoir lake ''Salza'' which is in the sharp incision you can see to the south.
* After passing the reservoir, you may try to get down to ''Niederoblarn'' (LOGO) to the southeast, it's a short airfield.
* From there, follow the railway in the valley of Enns westwards, LOWZ is about 20 minutes away. On your right side watch out for the other side of the ''Dachstein'' and the town of ''Schladming'', which lies down in the valley next the rocky hills with the river flowing trough. Look for the railway and the river Enns.
* Behind ''Schladming'' (south of Mt. ''Dachstein'', approximately halfway of the distance LOGO/LOWZ) the valley will widen a bit again, featuring a rocky mountain in the middle of the valley. Continue to follow the railway and river bending nortwest arond the small mountain.
* Near the bigger town of ''Radstadt'' the valley will open significantly. Follow west, heading for the next town ''Altenmark'' at the end of the opening.
* The railway will bend north at ''Altenmark'' and soon join the Autobahn A10/E55. This is the point we need to go southwest and follow the next valley.
* The valley leads us westward to the Town of ''St. Johann/Pongau''. probably around the middle of the valley you can spot the prominent ''Mt. Hochkönig'' (2941m) northwest of ''St. Johann'' and the ''Tennengebirge'' to its right.
* Once reaching ''St. Johann'', continue to follow the next big valley west-southwest.
* After about 16 miles you will reach ''Zell am See'' (LOWZ) where we will land after around one hour flight time in total. Beware this is a short field.

== Zell am See to Innsbruck via Mt. Venediger ==
[[File:LOWZ-LOWI.jpg|thumb|The route for Zell am See to Innsbruck]]
This flight will bring you to two of the core peaks of the Alpenhauptkamm.
* [https://skyvector.com/?ll=47.201656734623775,12.160079968084839&chart=301&zoom=3&fpl=N0100A120%20LOWZ%20LOWZ%204708N01241E%204708N01221E%204706N01214E%204710N01152E%204724N01150E%20LOWI SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather. There are no usable navaids for this trip.
* Trip takes around 45 minutes air time at 110 KTAS.
* Climb to at an altitude of about 10000ft or so after starting from [[:File:Lowz-parking.jpg|Zell am See]].

* After starting fly into the valley southwest over the town of ''Kaprun''. Maybe you need to circle a bit to gain altitude, near the mountains we need at least about 10000ft!
* Follow the valley until you overfly two lakes (''Stausee Wasserfallboden'' and ''Moorboden''). To your left you can see ''Mt. Großes Wiesbachhorn'' (3564m).
* The end of the valley goes over into a flank of the ''Großglockner'' which is near to the south. Follow the west bend of the valley end and fly over the lakes ''Tauernmoossee'' and ''Weißsee''. After you climb out of the valley, you already should see the peak of ''Mt. Venediger'' on the front left. Aim to the saddle right of its peak.
* You then fly that direction over several valleys that go from south to north, until you hit the very big valley that bend from south to west. The ridgeline right of that valley is the border between the Austrian states Tirol and Salzburg. Follow the valley up to the ''Venediger'', passing the ''Mt. Sandebentörl'' (2751m), still aiming for the saddle.
* Shortly after you reach the end of the valley and need to overfly the saddle with the glacier ''Venedigerkees'' behind it. The ridgeline is again the border between Tirol and Salzburg. Directly south of the ''Venedigerkees'' is the pyramid of ''Mt. Venediger''.
* Follow ''Venedigers'' ridge to the southwest, skip the first valley and overfly the next ridge.
* From here you can deviate into the valley north and visit the ''Krimmler Wasserfälle'', and from there west trough the main valley.
* If you instead follow the planned route westwards, aim to the peak of ''Mt. Zillerplattenspitze'' (3148m) with the small lake ''Eissee'' to its south flank which you should already see. This is a little hard to get right, but don't fly directly into the big valley but aim right to the second row mountain peaks at about 280 heading.
* Overfly the ridge with ''Eissee'' and follow the valley from there nothwest with the reservoir ''Zillergründl'' and ''Mt. Reichenspitze'' (3303m) to its right; until you reach the town ''Mayrhofen'' where the current valley meets the ''Zillertal'' valley. You also should start to descend now to about 3500ft with a rate of roughly -1000fpm.
* From ''Mayrhofen'' follow the ''Zillertal'' valley north and when reaching the ''Inntal'' valley near the town ''Jenbach'', Innsbruck Airport is a few minutes to the west. If you like, you can divert north at ''Jenbach'' to visit ''Achensee'', and even continue further north to land at Munich via lake ''Tegernsee'' or via the Isartal over ''Bad Tölz''.

== Crossing the alps ==
[[File:ED02-LIPB.jpg|thumb|The route for Fuessen to Bolzano]]
This trip brings us from germany via austria to italy, crossing the alps, visiting the famous castle Neuschwanstein and Mt. Zugspitze, germanys highest peak.
* [https://skyvector.com/?ll=47.068251080980836,10.959411633048108&chart=301&zoom=5&fpl=N01204735N01041E%204734N01045E%204729N01042E%204726N01046E%204724N01054E%204712N01054E%204704N01058E%204656N01103E%204655N01106E%204653N01109E%204650N01110E%204648N01113E%204638N01110E%20LIPB SkyVector route]
* Suggested plane: C172 or C182
* This is VFR only, so pick suitable weather and time (I suggest to start with the first light/sunrise).
* There are no helpful navaids for this trip, but Bolzano NDB: 362 BZO may serve as a final guidance.
* Trip takes around 45 minutes air time at 120 KTAS.

* Start at ED02 Fuessen, climb to about 3000 and head southeast to visit castle Neuschwanstein, south of the Forgensee.
* After looking at the castle (challenge: fly close around behind it), we start climbing to 3500 and aim southwestish and cross over from germany to austria.
* Fly into the big valley directing south. East of Reutte start climbing 500fpm to 6000 and follow the railway in the valley to the southeast.
* Once the valley opens significantly, you can see the famous mountain Zugspitze (germanys highest peak, 2962 m) to the front.
* Head southwards around the Mt. Gartnerwand over town Ehrwald and fly between the two small peaks over the Marienbergjoch mountain pass, 1789m/5870ft (between Mt. Wanning and Mt. Marienberg; challenge: who can make it with the least altitude?).

* After overflying the second mountain, to the south comes a new valley called Ötzal where you fly into.
* Follow that valley all the way to the south and slowly climb to at least 8600 now (300fpm or so). Note overflying Längenfelden, where the dominant valley joins from the east with the river Fischbach, halfaway the leg; this looks similar to the end, but isn't.
* Follow the valley until it starts to branch in all different directions at the end (over the town of Sölden and Zwieselstein).
* We follow the Southeast main branch and then turn quickly to a smaller valley branching off directly eastwards (look for the mountain pass road).
* That brings us to the mountain pass of the Timmelsjoch and is the place where we cross over to Italy.

* After passing, we can descend to 2500 or so, following the terrain. Follow the valley and its river "Passer" southeast, and follow its bend to the south.
* Follow the valley and make a nice turn around Mt. Kolbenspitze's east ridge, over San Leonardo, still following the Passer river now southwards.
* Where the valley hits the next big valley "Etschtal", is a bigger famous city called Merano. From there we follow the River Etsch and the Autobahn (highway) to the south and are soon approaching the somewhat hidden airport of Bolzano (LIPB) after an estimated time of somewhat under one hour at 120 knots.

From here you can also continue more to the south to Trento (LIDT, total FT ~1:00) or Verona (LIPX, total FT ~1:20) - just follow the river Etsch to the south! Venezia is also not far away, just ~30 minutes/62nm to the east of Verona.

==Grenoble Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( Grenoble Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.
*Published in [[Custom France Scenery]].

==Gulf of Finland sightseeing tour==
Take a VFR sightseeing tour over the Gulf of Finland from Helsinki to Tallinn! Estonia's landmarks are all recent additions, while Helsinki was one of the first cities to have original models in the scenery model database.

Take off from the smaller EFHF airfield in Helsinki, or try your luck fighting the virtual traffic at Vantaa, and head toward the port of Helsinki. Look for the Hartwall Arena, the Pasila tower, the railway station and the Olympic Stadium along the way. Make your way out over the Gulf flying just west of south - a heading of 190 should set you up nicely for a sightseeing tour of Tallinn. Try to come in from the west and do a sweeping left turn over the capital of Estonia, looking out for the Swissotel, Olympic Hotel, the Television tower, and other important landmarks in the capital city of Estonia. Make sure you look out for St. Olaf's Church, the tallest building in the capital city. Make your way over the Ulemiste Jarv (lake) to land on runway 09 at Tallinn's main airport.

If you desire, you can do a touch-and-go at Tallinn and set your course southeastward, landing at Tartu Airport, which is also modelled in FlightGear.

The distance between Helsinki and Tallinn is about 50 miles or 80 kilometres, while Tartu is twice the distance from Tallinn at 100 miles/160 kilometres. Fly a heading of 135 to get to Tartu from Tallinn.
*Published in [[FlightGear Newsletter October 2010]] by [[User:Statto|Statto]].

==Azores==
[[Image:LPLA-001.png|thumb|left|take off]]
[[Image:LPLA-002.png|thumb|right|approaching island]]
The [http://en.wikipedia.org/wiki/Azores Azores], set in the middle of the Atlantic ocean, has had many names. Fortunate Isles, the Blue Islands, the Islands of Tin and Silver, the Islands of the Seven Cities. We can add, the Islands of Amazing Sights and Flights.

Our flight is to celebrate the amazing views FlightGear can give us.

Start your plane at [[Lajes Field]] (LPLA). This once was an emergency landing site for the [[Space Shuttle]] so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: if you don't fly too high (stick around 3000 while you can) you will have some amazing views.

Next, fly towards and over LPPD. Look out the window and enjoy the view. Then head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!
*Published in [[FlightGear Newsletter August 2011]] by [[User:PH-JBO|PH-JBO]]

===Airports and coordinates===
[[Image:LPPD-001.png|thumb|left|over the island]]
[[Image:LPPD-002.png|thumb|right|landing]]

* [[LPLA|LPLA - Lajes Field]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPLA.pdf chart]
* [[LPPD|LPPD - Ponta del gada]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LPPD.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w020n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Cessna 550 Citation II]]

===FlightGear launching===
fgfs --airport=LPLA --aircraft=Citation-II
<div style="clear:both;"></div>

== Canary Islands Trip ==

An archipelago in the middle of the Atlantic sea, stunning beauty where you won't expect it. Seven islands, seven continents, thats what the canarian people say. And it's true, you will face seven totally different islands and nine different airports.
Take off from the largest one, GCLP, at the main island Gran Canaria. Leave the beautiful island heading to the west, and land at GCTS, the southern airport at Tenerife. Enjoy the view on Spains highest mountain, the glaciered Teide, when flying to La Gomera (GCGM), one of the greenest islands there. Master the short runway, and enjoy the view, before taking the challenge and approach El Hierro (GCHI). A short runway, with cliffs and rocks on both ends will cause you to sweat. From this island, which was claimed to be the western end of the world in medieval times, you'll turn to the beautiful and wild island of La Palma (GCLA). The next approach will be historical, because you are approaching the notorious Tenerife North (GCXO). Yes, I am serious, you will face that airport, where the worst civil plane crash ever took place. But you needn't worry, if you got that far, you will do this approach as easy as any other. The longest flight on your trip will take you to the eastern island, Lanzarote (GCRR). Take a look at the volcanic-red mountains, the vineyards, and the beaches. You want more beaches?? Depart to the south-west, fly over the small island of Los Lobos, and land in the holiday-paradise Fuerteventura. Enjoy dunes, bays, and very nice long beaches, before you finally touch down in Fuerteventura (GCFV). You want to stay? Okay, let's taxi to a parking position, and cut off the engines. If you still want more, fly back to Gran Canaria's GCLP, where we started our trip.

Custom scenery: [[Canary Islands Custom Scenery]] / direct source: https://github.com/D-ECHO/Canarys

=== Suggested Aircraft ===

* small civil aircraft, such as the Cessna Skylane, Skyhawk, or Citation
* small airliners, like the Q400, the ATR72, the CRJ200, or similar

Route by Flycanarias

<gallery>

</gallery>

==Gibraltar==
[[Image:LEMG-010.png|thumb|left|take off]]
[[Image:LEMG-011.png|thumb|right|just after take off]]
Traffic lights turn red, gates are closed. The only busy main road to the peninsula is closed and all the cars and trucks are waiting patiently. Waiting for a train to pass? No. Waiting for a plane to pass since the main road crosses a busy runway.

On both sides water and being crossed by a busy main road can only be one runway: [http://en.wikipedia.org/wiki/Gibraltar_Airport Gibraltar airport]!

One would expect an ILS installed on such a tricky runway but no, you will have to guess where it is and how far away it is. Not even an ADF points to it.

Take off from LEMG (Malaga). Go South-West and find the runway of LXGB somewhere to the right of the rock. Happy guessing!
*Published in [[FlightGear Newsletter September 2011]] by [[User:PH-JBO|PH-JBO]]
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:LEMG-013.png|thumb|left|search for this]]
[[Image:LEMG-015.png|thumb|right|landing]]

* [[LEMG|LEMG - Malaga]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LEMG.pdf chart]
* [[LXGB|LXGB - Gibraltar]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LXGB.pdf chart]

required scenery tile: http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Scenery-v2.4.0/w010n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
* [[Piper Aerostar]]

===FlightGear launching===
fgfs --airport=LEMG --aircraft=aerostar700 --adf1=300 --nav1=300:117.80
<div style="clear:both;"></div>

=Asia=
==Khorog, Tajikistan==
[[File:Fw190HinduKush.jpeg|left|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

*October 2011 by [[User:Armchair Ace| Armchair Ace]], published in [[FlightGear_Newsletter_January_2012#Suggested_flights| Newsletter January 2012]].
<br>
<br>
<br>
== Central Karakoram range ==
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier, above which K2 and Gasherbrum V and VI loom, is more than 13,000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the [[De Havilland Canada DHC-6 Twin Otter|Twin Otter]] is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

Published in [[FlightGear_Newsletter_April_2012#Suggested_flights| Newsletter April 2012]] by [[User:Thosten|Thosten]].

=Africa=
==Ngorngoro==
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*October 2011 by [[User:PH-JBO|PH-JBO]]. Published in [[FlightGear_Newsletter_December_2011#Suggested_flights | Newsletter December 2011]].
==Kisimayu to Kilimanjaro==
We have to take a big airliner for this trip. The runways are long enough but for this trip we need some altitude and a slow descend.

We park our Big Bird at HCMK, [http://en.wikipedia.org/wiki/Kismayo_Airport Kisimayu], Somalia, near the East coast of Africa. It's unsure what this airfield is used for but it's a long piece of tarmac. I could not find regular flights to and from this airfield, not so strange, there is no lighting, no radio beacons and... no fuel. What you can find is Global Air Rescue that has an air ambulance service based here (with a [http://www.globalairrescue.com/learjet-35.php Learjet 35]).

Our route will be around 425 nm in length. You know your aircraft and know what altitude you will need to fly.

Our destination, HTKJ, [http://en.wikipedia.org/wiki/Kilimanjaro_International_Airport Kilimanjaro], Tanzania, has only one ILS and I have learned, if an airfield has only one ILS there is probably a reason.

Flight Plan (short version):
#HCMK Kisimayu, length 12,177 ft, no navaids near.
#GAR Garissa [[VOR-DME]] freq 115.7 heading 268° dist 169 nm.
#KB Kilimanjaro [[NDB]] freq 393.0 heading 224° dist 258 nm, here is the holding pattern for the Kilimanjaro runway (and there is a [http://en.wikipedia.org/wiki/Mount_Kilimanjaro 19,000 ft] reason for this detour).
#KV Kilimanjaro VOR-DME freq 115.3 heading 70° dist 26 nm.
#HTKJ Kilimanjaro [[ILS]] freq 110.9 runway heading 88° elev 2,900 ft [[AMSL]] length 11,807 ft.

Prepare your flight well to receive amazing views of the landscape during the final steps of the route, if you don't you will discover why some pilots call Kilimanjaro Kill-You-Manjaro.

{{#ev:youtube | KCJi_ZaR8ec}}
Youtube video: Kilimanjaro approach in real, in FG not much different.

*February 2012 by [[User:PH-JBO|PH-JBO]].

=Australia and Oceania=

==Hawai'i==
[[Image:Maui03.jpg|thumb|250px]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.
*Published in [[FlightGear Newsletter September 2010]] by [[User:Statto|Statto]].

==Brisbane International Airport to Sydney International Airport==
Going from Brisbane International Airport to Sydney International Airport. You should have a heading of about 203. Might take sometime to arrive to this section. Maybe 10-30 mins into the flight. Can't really say but don't give up, you will eventually reach this section of the flight. '''''Your eyes will be rewarded!''''' .

[[Image:Fgfs-screen-020.png|200px]]
[[Image:Fgfs-screen-016.png|200px]]
[[Image:Fgfs-screen-012.png|200px]]
*Published in [[FlightGear Newsletter April 2011]] by [[User:Vin|Vin]]

=Antarctica=

{{Suggested}}

[[Category:Lists]]

Howto:Add sound effects to aircraft

2024-04-20T15:03:34Z

Hbeni: /* Configuration tags */

You can '''add sound effects to aircraft''' by adding the sound samples and configuring the sound effects in XML files. The sound effects can be conditional and the sound's pitch and volume can depend on properties in the property tree.

{{note|This text is partially incorrect/outdated. Especially how the final volume/pitch is calculated. Make sure to also read the {{fgdata source|Docs/README.xmlsound|text=official documentation}}.}}

Some sound effects are added other ways. For example, sounds from avionics like navigation radio receivers are automatically added when you add those radios.

{{FGCquote|1= The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/28505220/ | title = <nowiki>Re: [Flightgear-devel] Stereo sounds no longer supported?</nowiki> | author = <nowiki>syd adams</nowiki> | date = Dec 7th, 2011 }}}}

{{FGCquote|1= The old way was that the stereo sound would always play the left channel on the left side. Now you split the sound and place it in 3D space. When you turn your head, the speaker the left side sound comes out of changes with you|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257291#p257291 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>bugman</nowiki> | date = Sep 14th, 2015 }}}}

{{FGCquote|1= All sounds must now be mono point sources, and stereo simply requires the two sound sources to be positioned in the 3D environment. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34100151/ | title = <nowiki>[Flightgear-devel] Audit and proposal for handling non-supported stereo sound files in FGAddon via the 3D sound engine.</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = May 10th, 2015 }}}}

{{FGCquote|1= We use OpenAL for 3D positional audio and most OpenAL implementations can only handle one stereo file.Also Stereo files will not work in 3d space, so they will not be positional.But most aircraft developers did not know that and used several stereo files expecting everything to work properly but the truth was that in most implementations just one of those stereo files was played.And if you think of it, stereo separation does not work for boarding music either since it plays left channel to your left ear and right channel to your right ear. But in reality boarding music is played left channel to the left audio channel in the aircraft and right channel to the right audio channel in the aircraft.This works the same as normal stereo if you enter the aircraft, but will, reverse once you turn around.So the solution is to split up the stereo file into two mono files and play the proper channel at the proper side of the passenger compartment.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257289#p257289 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>erik</nowiki> | date = Sep 14th, 2015 }}}}

== Sound configuration files ==
The sound configuration files are [[PropertyList XML files]].

The top level sound configuration file is composed of a <code><fx></code> and a <code><name></code> tag, a <code><path></code> to a sound sample file and zero or more <code><volume></code> and/or <code><pitch></code>definitions.

Paths are relative to [[$FG_ROOT]], but absolute paths may also be used.

Comments are bracketed with <code></code>.

=== Example ===
This example would define an engine sound effect for a piston engine driven aeroplane.

The sound effect representing the engine is located in <code>$FG_ROOT/Sounds</code> and is named <code>wasp.wav</code>. The effect is started when the property <code>/engines/engine/running</code> becomes non-zero.

When that happens, the sound will be played looped (see <code><mode></code>) until the property returns zero again. As you can see the volume is dependent on the property <code>/engines/engine/mp-osi</code>, and the pitch of the sound depends on the property <code>/engines/engine/rpm</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<fx>
<engine>
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
<condition>
<property>/engines/engine/running</property>
</condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
<min>0.15</min>
<max>0.5</max>
<offset>0.15</offset>
</volume>
<pitch>
<property>/engines/engine/rpm</property>
<factor>0.0012</factor>
<min>0.3</min>
<max>5.0</max>
<offset>0.3</offset>
</pitch>
</engine>
</fx>
</PropertyList>
</syntaxhighlight>

=== Inclusion from the aircraft-set.xml file ===
In order for the sound configuration to be used, it has to be included from the [[aircraft-set.xml]] file.

This can be done by adding the path to the file relative to the aircraft's base path within the <code><sim></code> tags in the aircraft-set.xml file..

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>

<sim>

<sound>
<path type="string">My-sound-config.xml</path>
</sound>

</sim>

</PropertyList>
</syntaxhighlight>

== Configuration tags ==

; <code><fx></code>
: Named FX subtree living under /sim/sound

; <code>< ... ></code>
: This is the event separator. The text inside the brackets can be anything, but it is advised to give it a meaningful name like: crank, engine, rumble, gear, squeal, flap, wind or stall.

: The value can be defined multiple times, thus anything which is related may have the same name (grouping them together).

; <code><name></code>
: This defines the name of the event. This name is used internally and, although it can me defined multiple times in the same file, should normally have an unique value.

: Multiple definitions of the same name will allow multiple sections to interfere in the starting and stopping of the sample.

: This method can't be used to control the pitch or volume of the sample, but instead multiple volume or pitch section should be included inside the same event.

: The types "raise" and "fall" will stop the playback of the sample regardless of any other event. This means that when the type "raise" is supplied, sample playback will stop when the event turns false. Using the type "fall" will stop playback when the event turns true.

: IMPORTANT
:: If the trigger is used for anything else but stopping the sound at a certain event, all sections with the same name ''should'' have exactly the same sections for everything but property and type.

:: In the case of just stopping the sample at a certain event, the sections for path, volume and pitch may be omitted.

; <code><path></code>
: This defined the path to the sound file. The path is relative to the FlightGear root directory but could be specified absolute.

: The sound format must be mono.

; <code><condition></code>
: Define a condition that triggers the event.

: For a complete description of the FlightGear conditions, please read docs-mini/README.conditions or read the [[Conditions]] article on the wikie.

: An event should define either a condition or a property.

; <code><property></code>
: Define which property triggers the event, and refers to a node in the FlightGear property tree.

: Action is taken when the property is non zero.

: A more sophisticated mechanism to trigger the event is described in <condition></code>

; <code><mode></code>
: This defines how the sample should be played:

:; once
:: The sample is played once. This is the default.

:; looped
:: The sample plays continuously, until the event turns false.

:; in-transit
:: the sample plays continuously, while the property is changing its value.

; <code><type></code>
: This defines the type of this sample, each type also have seperate volume slider in sound settings menu:

:; fx
:: This is the default type and doesn't need to be defined.

:; avionics
:: Sounds set to this type don't have a position and orientation but are treated as if it's mounted to the aircraft panel.

:: It is up to the user to define if it can always be heard or only when in cockpit view.

:; atc
:: Is used by the ATC chatter add-on.

; <code><delay-sec></code>
: Delay after which the sound starts playing.

: This is useful to let a property start two sounds at the same time, where the second is delayed until the first stopped playing.

; <code><volume></code> / <code><pitch></code>
: Volume or Pitch definition.

: Currently there may be up to 5 volume and up to 5 pitch definitions defined within one sound event.

: There are two important results from each <volume> and <pitch> section: the offset and the value. Normally all offset values from the different volume/pitch are added together to create the total offset. The values from each <volume> or <pitch> section are multiplied together to create an final value. Then the volume (or pitch, respectively) is set to total offset + final value.

: A special condition occurs when the value of factor is negative, in which case the offset doesn't get added to the other offset values but instead will be used in the multiplication section.

: Pitch final output can range from 0 to 2. 1 represents the original pitch of the sound file. Offset defaults to 1, meaning that if no specific <pitch> parameters are given the file will be played at its original pitch.

: Volume final output can range from 0 to 1. 1 represents full volume and 0 is silence.

:; <code><expression></code>
:: Defines an [[Expressions|expression]], and will replace all other tags in this volume/pitch tag.

:; <code><property></code>
:: Defines which property supplies the value for the calculation.

:: Either a <property> or an <internal> should be defined. If none is defined, the property reverts to its default. For volume this is 0, meaning the sound will not be audible at all.

:: The value is treated as a floating point number.

:; <code><internal></code>
:: Defines which internal variable should be used for the calculation.

:: The value is treated as a floating point number.

:: The following internals are available at this time:

::; dt_play
::: The number of seconds since the sound started playing.

::; dt_stop
::: The number of seconds after the sound has stopped.

:; <code><type></code>
:: Defines the function that should be used upon the property before it is used for calculating the net result:

::; lin
::: Linear handling of the property value. This is the default.

::; ln
:: Convert the property value to a natural logarithmic value before scaling it.

::: Anything below 1 will return zero.

::; log
::: convert the property value to a true logarithmic value before scaling it. (log base 10)

::: Anything below 1 will return zero.

::; inv
::: Inverse linear handling (1/x).

::; abs
:: Absolute handling of the value (always positive).

::; sqrt
::: Calculate the square root of the absolute value before scaling it.

:; <code><factor></code>
:: Defines the multiplication factor for the property value.

:: A special condition is when scale is defined as a negative value. In this case the result of |<scale>| * <property) will be subtracted from <default>

:; <code><offset></code>
:: The initial value for this sound.

:: This value is also used as an offset value for calculating the end result.

:; <code><random></code>
:: Add a bit of randomness to the offset. Only used for pitch.

:; <code><min></code>
:: Minimum allowed value.

:: This is useful if sounds start to sound funny. Anything lower will be truncated to this value.

:; <code><max></code>
:: Maximum allowed value.

:: This is useful if sounds gets to loud. Anything higher will be truncated to this value.

:: Keep in mind that min & max are applied first, then offset. So for example if min = 0, max = 0.5 and offset = 1.0, then the resulting values will range 1 to 1.5.

; <code><position></code>
: Specify the position of the sounds source relative to the 3D models center.

: The coordinate system used is a left hand coordinate system where +Y = left, -Y = right, -Z = down, +Z = up, -X = forward, +X = aft. Distances are in meters.

: It's important to note that for sounds the Y axis is inverted compared to e.g. object animation coordinates (see also [[Howto:3D_Aircraft_Models]]).

: The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!

: Also take notice that the values should not be 0.0, since that can produce sound artifacts on some sound cards.

; <code><x></code>
: X dimension offset (-X = forward, +X = aft, in meters)

; <code><y></code>
: Y dimension offset (+Y = left, -Y = right)

; <code><z></code>
: Z dimension offset (-Z = down, +Z = up)

; <code><orientation></code>
: Specify the orientation of the sounds source.

: The zero vector is default, indicating that a Source is not directional.

: Specifying a non-zero vector will make the Source directional in the X,Y,Z direction

; <code><x></code>
: X dimension

; <code><y></code>
: Y dimension

; <code><z></code>
: Z dimension

; <code><inner-angle></code>
: The inner edge of the audio cone in degrees (0.0 - 360.0).

: Any sound withing that angle will be played at the current gain.

; <code><outer-angle></code>
: The outer edge of the audio cone in degrees (0.0 - 360.0).

: Any sound beyond the outer cone will be played at "outer-gain" volume.

; <code><outer-gain></code>
: The gain at the outer edge of the cone.

; <code><reference-dist></code>
: Set a reference distance of sound in meters. This is the distance where the volume is at its maximum. Default is 60.

: Volume is clamped to this maximum for any distance below.

: Volume is attenuated for any distance above.

: Attenuation depends on reference and maximum distance. See OpenAL specification on "AL_INVERSE_DISTANCE_CLAMPED" mode for details on exact computation.

; <code><max-dist></code>
: Set the maximum audible distance for the sound in meters. Default is 6000.

: Sound is cut-off above this distance.

== Creating a configuration file ==

To make things easy, there is a default value for most entries to allow a
sane configuration when a certain entry is omitted.

{| class="wikitable"
! Tag !! Default value
|-
| '''<type>''' || lin
|-
| '''<factor>''' || 1.0
|-
| '''<offset>''' || 0.0 for volume, 1.0 for pitch
|-
| '''<min>''' || 0.0
|-
| '''<max>''' || 0.0 (don't check)
|}

Calculations are made the following way (for both pitch and volume):
<syntaxhighlight lang="cpp">
value = 0;
offs = 0;

for (n = 0; n < max; n++) {
if (factor < 0) {
value += offset[n] - abs(factor[n]) * function(property[n]);
} else {
value *= factor[n] * function(property[n]);
offs += offset[n];
}
}

volume = offs + value;
if (volume > 1.0) vol = 1.0;
</syntaxhighlight>
where function can be one of: lin, ln, log, inv, abs or sqrt

== Multiplayer sound ==
The multiplayer sound file works just as the normal sound file, except it should reside in <code>/sim/model/sound</code> instead of <code>/sim/sound</code>. Make sure it depends on properties that are [[Howto:Transmit_properties_over_MP|transmitted over MP]].

An example could be found in FGAddon 777-200: {{fgaddon aircraft url|777}}
* <code>777-200-set.xml</code> extends <code>777-200-common.xml</code> (this is not mandatory, just here to explain the inheritance. The -set.xml does/can include the model directly)
* <code>777-200-common.xml</code> references <code>Aircraft/777/Models/777-200.xml</code>
* <code>Models/777-200.xml</code> has an <code><sound><path>Aircraft/777/Sounds/mp-sound.xml</path></sound></code> reference
* <code>Sounds/mp-sound.xml</code> contains an ordinary sound config file with relative property paths resolved to the relative <code>/ai/models/multiplayer/</code> nodes of the multiplayer instance.
* The result is a subnode <code>/ai/models/multiplayer/sim/sound</code>, with a "path" node pointing to <code>Aircraft/777/Sounds/mps-sound.xml</code>.

== Recommended audio file formats ==
{{note|The sound sample '''must be in mono''' format. This is because it can not be put in a 3D context otherwise. Also, as of at least June 2015 '''stereo samples will not be played'''.}}

There some considerations on the quality to the audio files. As a rule of thumb, any computer is able to playback sounds in DVD-quality (48 kHz/24 bits).
Macs still has trouble reading 32 bit files. Most standard sound cards also can't playback 32 bit files.

From a listeners point of view, anything above 44.1 kHz and 24 bits is only useful for high end music. Personally, I would think that 44.1 kHz with 16 bits should be more than enough to play engine sounds and alarms from the cockpit. Consider the disk-space against the gain in audio quality!

== Preventing sounds from playing when sim starts ==
Some times it can be hard to prevent sounds from playing right away, if the condition starts to evaluate to true. A hack to get this to work is to multiply the volume with a property that you in nasal set to true some seconds after the sim has been initialized.

== Bugs in the sound system ==
* The Doppler effect if you pass an aircraft in high speed sometimes is way too high pitch.
* None of the position coordinates must not be 0.0 as described above.
* Sounds using <code><mode></code> 'once' together with <code><max-dist></code> behave incorrectly when going out of range of the sound, then back in range, all while the trigger condition remains true:
** Until January 2023 (Flightgear 2020.3): the above causes the sound to incorrectly restart playing.
** Since January 2023 (for development versions): the sound stops entirely when going out of range, it is not possible to come back in range to hear the end of the sound.

== Related content ==
=== Wiki articles ===
* [[Conditions]]
* [[Expressions]]
* [[Howto:Reload sound configuration without restarting]]

=== Readme file ===
* {{readme file|xmlsound}}

=== Source code ===
* {{simgear file|simgear/sound/xmlsound.hxx}}
* {{simgear file|simgear/sound/xmlsound.cxx}}
* {{flightgear file|src/Sound/fg_fx.hxx}}
* {{flightgear file|src/Sound/fg_fx.cxx}}

[[Category:Aircraft enhancement]]

Howto:Add sound effects to aircraft

2024-04-20T14:38:04Z

Hbeni: /* Multiplayer sound */

You can '''add sound effects to aircraft''' by adding the sound samples and configuring the sound effects in XML files. The sound effects can be conditional and the sound's pitch and volume can depend on properties in the property tree.

{{note|This text is partially incorrect/outdated. Especially how the final volume/pitch is calculated. Make sure to also read the {{fgdata source|Docs/README.xmlsound|text=official documentation}}.}}

Some sound effects are added other ways. For example, sounds from avionics like navigation radio receivers are automatically added when you add those radios.

{{FGCquote|1= The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/28505220/ | title = <nowiki>Re: [Flightgear-devel] Stereo sounds no longer supported?</nowiki> | author = <nowiki>syd adams</nowiki> | date = Dec 7th, 2011 }}}}

{{FGCquote|1= The old way was that the stereo sound would always play the left channel on the left side. Now you split the sound and place it in 3D space. When you turn your head, the speaker the left side sound comes out of changes with you|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257291#p257291 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>bugman</nowiki> | date = Sep 14th, 2015 }}}}

{{FGCquote|1= All sounds must now be mono point sources, and stereo simply requires the two sound sources to be positioned in the 3D environment. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34100151/ | title = <nowiki>[Flightgear-devel] Audit and proposal for handling non-supported stereo sound files in FGAddon via the 3D sound engine.</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = May 10th, 2015 }}}}

{{FGCquote|1= We use OpenAL for 3D positional audio and most OpenAL implementations can only handle one stereo file.Also Stereo files will not work in 3d space, so they will not be positional.But most aircraft developers did not know that and used several stereo files expecting everything to work properly but the truth was that in most implementations just one of those stereo files was played.And if you think of it, stereo separation does not work for boarding music either since it plays left channel to your left ear and right channel to your right ear. But in reality boarding music is played left channel to the left audio channel in the aircraft and right channel to the right audio channel in the aircraft.This works the same as normal stereo if you enter the aircraft, but will, reverse once you turn around.So the solution is to split up the stereo file into two mono files and play the proper channel at the proper side of the passenger compartment.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257289#p257289 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>erik</nowiki> | date = Sep 14th, 2015 }}}}

== Sound configuration files ==
The sound configuration files are [[PropertyList XML files]].

The top level sound configuration file is composed of a <code><fx></code> and a <code><name></code> tag, a <code><path></code> to a sound sample file and zero or more <code><volume></code> and/or <code><pitch></code>definitions.

Paths are relative to [[$FG_ROOT]], but absolute paths may also be used.

Comments are bracketed with <code></code>.

=== Example ===
This example would define an engine sound effect for a piston engine driven aeroplane.

The sound effect representing the engine is located in <code>$FG_ROOT/Sounds</code> and is named <code>wasp.wav</code>. The effect is started when the property <code>/engines/engine/running</code> becomes non-zero.

When that happens, the sound will be played looped (see <code><mode></code>) until the property returns zero again. As you can see the volume is dependent on the property <code>/engines/engine/mp-osi</code>, and the pitch of the sound depends on the property <code>/engines/engine/rpm</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<fx>
<engine>
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
<condition>
<property>/engines/engine/running</property>
</condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
<min>0.15</min>
<max>0.5</max>
<offset>0.15</offset>
</volume>
<pitch>
<property>/engines/engine/rpm</property>
<factor>0.0012</factor>
<min>0.3</min>
<max>5.0</max>
<offset>0.3</offset>
</pitch>
</engine>
</fx>
</PropertyList>
</syntaxhighlight>

=== Inclusion from the aircraft-set.xml file ===
In order for the sound configuration to be used, it has to be included from the [[aircraft-set.xml]] file.

This can be done by adding the path to the file relative to the aircraft's base path within the <code><sim></code> tags in the aircraft-set.xml file..

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>

<sim>

<sound>
<path type="string">My-sound-config.xml</path>
</sound>

</sim>

</PropertyList>
</syntaxhighlight>

== Configuration tags ==

; <code><fx></code>
: Named FX subtree living under /sim/sound

; <code>< ... ></code>
: This is the event separator. The text inside the brackets can be anything, but it is advised to give it a meaningful name like: crank, engine, rumble, gear, squeal, flap, wind or stall.

: The value can be defined multiple times, thus anything which is related may have the same name (grouping them together).

; <code><name></code>
: This defines the name of the event. This name is used internally and, although it can me defined multiple times in the same file, should normally have an unique value.

: Multiple definitions of the same name will allow multiple sections to interfere in the starting and stopping of the sample.

: This method can't be used to control the pitch or volume of the sample, but instead multiple volume or pitch section should be included inside the same event.

: The types "raise" and "fall" will stop the playback of the sample regardless of any other event. This means that when the type "raise" is supplied, sample playback will stop when the event turns false. Using the type "fall" will stop playback when the event turns true.

: IMPORTANT
:: If the trigger is used for anything else but stopping the sound at a certain event, all sections with the same name ''should'' have exactly the same sections for everything but property and type.

:: In the case of just stopping the sample at a certain event, the sections for path, volume and pitch may be omitted.

; <code><path></code>
: This defined the path to the sound file. The path is relative to the FlightGear root directory but could be specified absolute.

: The sound format must be mono.

; <code><condition></code>
: Define a condition that triggers the event.

: For a complete description of the FlightGear conditions, please read docs-mini/README.conditions or read the [[Conditions]] article on the wikie.

: An event should define either a condition or a property.

; <code><property></code>
: Define which property triggers the event, and refers to a node in the FlightGear property tree.

: Action is taken when the property is non zero.

: A more sophisticated mechanism to trigger the event is described in <condition></code>

; <code><mode></code>
: This defines how the sample should be played:

:; once
:: The sample is played once. This is the default.

:; looped
:: The sample plays continuously, until the event turns false.

:; in-transit
:: the sample plays continuously, while the property is changing its value.

; <code><type></code>
: This defines the type of this sample, each type also have seperate volume slider in sound settings menu:

:; fx
:: This is the default type and doesn't need to be defined.

:; avionics
:: Sounds set to this type don't have a position and orientation but are treated as if it's mounted to the aircraft panel.

:: It is up to the user to define if it can always be heard or only when in cockpit view.

:; atc
:: Is used by the ATC chatter add-on.

; <code><delay-sec></code>
: Delay after which the sound starts playing.

: This is useful to let a property start two sounds at the same time, where the second is delayed until the first stopped playing.

; <code><volume></code> / <code><pitch></code>
: Volume or Pitch definition.

: Currently there may be up to 5 volume and up to 5 pitch definitions defined within one sound event.

: There are two important results from each <volume> and <pitch> section: the offset and the value. Normally all offset values from the different volume/pitch are added together to create the total offset. The values from each <volume> or <pitch> section are multiplied together to create an final value. Then the volume (or pitch, respectively) is set to total offset + final value.

: A special condition occurs when the value of factor is negative, in which case the offset doesn't get added to the other offset values but instead will be used in the multiplication section.

: Pitch final output can range from 0 to 2. 1 represents the original pitch of the sound file. Offset defaults to 1, meaning that if no specific <pitch> parameters are given the file will be played at its original pitch.

: Volume final output can range from 0 to 1. 1 represents full volume and 0 is silence.

:; <code><expression></code>
:: Defines an expression, and will replace all other tags in this volume/pitch tag.

:; <code><property></code>
:: Defines which property supplies the value for the calculation.

:: Either a <property> or an <internal> should be defined. If none is defined, the property reverts to its default. For volume this is 0, meaning the sound will not be audible at all.

:: The value is treated as a floating point number.

:; <code><internal></code>
:: Defines which internal variable should be used for the calculation.

:: The value is treated as a floating point number.

:: The following internals are available at this time:

::; dt_play
::: The number of seconds since the sound started playing.

::; dt_stop
::: The number of seconds after the sound has stopped.

:; <code><type></code>
:: Defines the function that should be used upon the property before it is used for calculating the net result:

::; lin
::: Linear handling of the property value. This is the default.

::; ln
:: Convert the property value to a natural logarithmic value before scaling it.

::: Anything below 1 will return zero.

::; log
::: convert the property value to a true logarithmic value before scaling it. (log base 10)

::: Anything below 1 will return zero.

::; inv
::: Inverse linear handling (1/x).

::; abs
:: Absolute handling of the value (always positive).

::; sqrt
::: Calculate the square root of the absolute value before scaling it.

:; <code><factor></code>
:: Defines the multiplication factor for the property value.

:: A special condition is when scale is defined as a negative value. In this case the result of |<scale>| * <property) will be subtracted from <default>

:; <code><offset></code>
:: The initial value for this sound.

:: This value is also used as an offset value for calculating the end result.

:; <code><random></code>
:: Add a bit of randomness to the offset. Only used for pitch.

:; <code><min></code>
:: Minimum allowed value.

:: This is useful if sounds start to sound funny. Anything lower will be truncated to this value.

:; <code><max></code>
:: Maximum allowed value.

:: This is useful if sounds gets to loud. Anything higher will be truncated to this value.

:: Keep in mind that min & max are applied first, then offset. So for example if min = 0, max = 0.5 and offset = 1.0, then the resulting values will range 1 to 1.5.

; <code><position></code>
: Specify the position of the sounds source relative to the 3D models center.

: The coordinate system used is a left hand coordinate system where +Y = left, -Y = right, -Z = down, +Z = up, -X = forward, +X = aft. Distances are in meters.

: It's important to note that for sounds the Y axis is inverted compared to e.g. object animation coordinates (see also [[Howto:3D_Aircraft_Models]]).

: The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!

: Also take notice that the values should not be 0.0, since that can produce sound artifacts on some sound cards.

; <code><x></code>
: X dimension offset (-X = forward, +X = aft, in meters)

; <code><y></code>
: Y dimension offset (+Y = left, -Y = right)

; <code><z></code>
: Z dimension offset (-Z = down, +Z = up)

; <code><orientation></code>
: Specify the orientation of the sounds source.

: The zero vector is default, indicating that a Source is not directional.

: Specifying a non-zero vector will make the Source directional in the X,Y,Z direction

; <code><x></code>
: X dimension

; <code><y></code>
: Y dimension

; <code><z></code>
: Z dimension

; <code><inner-angle></code>
: The inner edge of the audio cone in degrees (0.0 - 360.0).

: Any sound withing that angle will be played at the current gain.

; <code><outer-angle></code>
: The outer edge of the audio cone in degrees (0.0 - 360.0).

: Any sound beyond the outer cone will be played at "outer-gain" volume.

; <code><outer-gain></code>
: The gain at the outer edge of the cone.

; <code><reference-dist></code>
: Set a reference distance of sound in meters. This is the distance where the volume is at its maximum. Default is 60.

: Volume is clamped to this maximum for any distance below.

: Volume is attenuated for any distance above.

: Attenuation depends on reference and maximum distance. See OpenAL specification on "AL_INVERSE_DISTANCE_CLAMPED" mode for details on exact computation.

; <code><max-dist></code>
: Set the maximum audible distance for the sound in meters. Default is 6000.

: Sound is cut-off above this distance.

== Creating a configuration file ==

To make things easy, there is a default value for most entries to allow a
sane configuration when a certain entry is omitted.

{| class="wikitable"
! Tag !! Default value
|-
| '''<type>''' || lin
|-
| '''<factor>''' || 1.0
|-
| '''<offset>''' || 0.0 for volume, 1.0 for pitch
|-
| '''<min>''' || 0.0
|-
| '''<max>''' || 0.0 (don't check)
|}

Calculations are made the following way (for both pitch and volume):
<syntaxhighlight lang="cpp">
value = 0;
offs = 0;

for (n = 0; n < max; n++) {
if (factor < 0) {
value += offset[n] - abs(factor[n]) * function(property[n]);
} else {
value *= factor[n] * function(property[n]);
offs += offset[n];
}
}

volume = offs + value;
if (volume > 1.0) vol = 1.0;
</syntaxhighlight>
where function can be one of: lin, ln, log, inv, abs or sqrt

== Multiplayer sound ==
The multiplayer sound file works just as the normal sound file, except it should reside in <code>/sim/model/sound</code> instead of <code>/sim/sound</code>. Make sure it depends on properties that are [[Howto:Transmit_properties_over_MP|transmitted over MP]].

An example could be found in FGAddon 777-200: {{fgaddon aircraft url|777}}
* <code>777-200-set.xml</code> extends <code>777-200-common.xml</code> (this is not mandatory, just here to explain the inheritance. The -set.xml does/can include the model directly)
* <code>777-200-common.xml</code> references <code>Aircraft/777/Models/777-200.xml</code>
* <code>Models/777-200.xml</code> has an <code><sound><path>Aircraft/777/Sounds/mp-sound.xml</path></sound></code> reference
* <code>Sounds/mp-sound.xml</code> contains an ordinary sound config file with relative property paths resolved to the relative <code>/ai/models/multiplayer/</code> nodes of the multiplayer instance.
* The result is a subnode <code>/ai/models/multiplayer/sim/sound</code>, with a "path" node pointing to <code>Aircraft/777/Sounds/mps-sound.xml</code>.

== Recommended audio file formats ==
{{note|The sound sample '''must be in mono''' format. This is because it can not be put in a 3D context otherwise. Also, as of at least June 2015 '''stereo samples will not be played'''.}}

There some considerations on the quality to the audio files. As a rule of thumb, any computer is able to playback sounds in DVD-quality (48 kHz/24 bits).
Macs still has trouble reading 32 bit files. Most standard sound cards also can't playback 32 bit files.

From a listeners point of view, anything above 44.1 kHz and 24 bits is only useful for high end music. Personally, I would think that 44.1 kHz with 16 bits should be more than enough to play engine sounds and alarms from the cockpit. Consider the disk-space against the gain in audio quality!

== Preventing sounds from playing when sim starts ==
Some times it can be hard to prevent sounds from playing right away, if the condition starts to evaluate to true. A hack to get this to work is to multiply the volume with a property that you in nasal set to true some seconds after the sim has been initialized.

== Bugs in the sound system ==
* The Doppler effect if you pass an aircraft in high speed sometimes is way too high pitch.
* None of the position coordinates must not be 0.0 as described above.
* Sounds using <code><mode></code> 'once' together with <code><max-dist></code> behave incorrectly when going out of range of the sound, then back in range, all while the trigger condition remains true:
** Until January 2023 (Flightgear 2020.3): the above causes the sound to incorrectly restart playing.
** Since January 2023 (for development versions): the sound stops entirely when going out of range, it is not possible to come back in range to hear the end of the sound.

== Related content ==
=== Wiki articles ===
* [[Conditions]]
* [[Expressions]]
* [[Howto:Reload sound configuration without restarting]]

=== Readme file ===
* {{readme file|xmlsound}}

=== Source code ===
* {{simgear file|simgear/sound/xmlsound.hxx}}
* {{simgear file|simgear/sound/xmlsound.cxx}}
* {{flightgear file|src/Sound/fg_fx.hxx}}
* {{flightgear file|src/Sound/fg_fx.cxx}}

[[Category:Aircraft enhancement]]

Howto:Add sound effects to aircraft

2024-04-20T13:37:04Z

Hbeni: /* Multiplayer sound */

You can '''add sound effects to aircraft''' by adding the sound samples and configuring the sound effects in XML files. The sound effects can be conditional and the sound's pitch and volume can depend on properties in the property tree.

{{note|This text is partially incorrect/outdated. Especially how the final volume/pitch is calculated. Make sure to also read the {{fgdata source|Docs/README.xmlsound|text=official documentation}}.}}

Some sound effects are added other ways. For example, sounds from avionics like navigation radio receivers are automatically added when you add those radios.

{{FGCquote|1= The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/28505220/ | title = <nowiki>Re: [Flightgear-devel] Stereo sounds no longer supported?</nowiki> | author = <nowiki>syd adams</nowiki> | date = Dec 7th, 2011 }}}}

{{FGCquote|1= The old way was that the stereo sound would always play the left channel on the left side. Now you split the sound and place it in 3D space. When you turn your head, the speaker the left side sound comes out of changes with you|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257291#p257291 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>bugman</nowiki> | date = Sep 14th, 2015 }}}}

{{FGCquote|1= All sounds must now be mono point sources, and stereo simply requires the two sound sources to be positioned in the 3D environment. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34100151/ | title = <nowiki>[Flightgear-devel] Audit and proposal for handling non-supported stereo sound files in FGAddon via the 3D sound engine.</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = May 10th, 2015 }}}}

{{FGCquote|1= We use OpenAL for 3D positional audio and most OpenAL implementations can only handle one stereo file.Also Stereo files will not work in 3d space, so they will not be positional.But most aircraft developers did not know that and used several stereo files expecting everything to work properly but the truth was that in most implementations just one of those stereo files was played.And if you think of it, stereo separation does not work for boarding music either since it plays left channel to your left ear and right channel to your right ear. But in reality boarding music is played left channel to the left audio channel in the aircraft and right channel to the right audio channel in the aircraft.This works the same as normal stereo if you enter the aircraft, but will, reverse once you turn around.So the solution is to split up the stereo file into two mono files and play the proper channel at the proper side of the passenger compartment.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257289#p257289 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>erik</nowiki> | date = Sep 14th, 2015 }}}}

== Sound configuration files ==
The sound configuration files are [[PropertyList XML files]].

The top level sound configuration file is composed of a <code><fx></code> and a <code><name></code> tag, a <code><path></code> to a sound sample file and zero or more <code><volume></code> and/or <code><pitch></code>definitions.

Paths are relative to [[$FG_ROOT]], but absolute paths may also be used.

Comments are bracketed with <code></code>.

=== Example ===
This example would define an engine sound effect for a piston engine driven aeroplane.

The sound effect representing the engine is located in <code>$FG_ROOT/Sounds</code> and is named <code>wasp.wav</code>. The effect is started when the property <code>/engines/engine/running</code> becomes non-zero.

When that happens, the sound will be played looped (see <code><mode></code>) until the property returns zero again. As you can see the volume is dependent on the property <code>/engines/engine/mp-osi</code>, and the pitch of the sound depends on the property <code>/engines/engine/rpm</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<fx>
<engine>
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
<condition>
<property>/engines/engine/running</property>
</condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
<min>0.15</min>
<max>0.5</max>
<offset>0.15</offset>
</volume>
<pitch>
<property>/engines/engine/rpm</property>
<factor>0.0012</factor>
<min>0.3</min>
<max>5.0</max>
<offset>0.3</offset>
</pitch>
</engine>
</fx>
</PropertyList>
</syntaxhighlight>

=== Inclusion from the aircraft-set.xml file ===
In order for the sound configuration to be used, it has to be included from the [[aircraft-set.xml]] file.

This can be done by adding the path to the file relative to the aircraft's base path within the <code><sim></code> tags in the aircraft-set.xml file..

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>

<sim>

<sound>
<path type="string">My-sound-config.xml</path>
</sound>

</sim>

</PropertyList>
</syntaxhighlight>

== Configuration tags ==

; <code><fx></code>
: Named FX subtree living under /sim/sound

; <code>< ... ></code>
: This is the event separator. The text inside the brackets can be anything, but it is advised to give it a meaningful name like: crank, engine, rumble, gear, squeal, flap, wind or stall.

: The value can be defined multiple times, thus anything which is related may have the same name (grouping them together).

; <code><name></code>
: This defines the name of the event. This name is used internally and, although it can me defined multiple times in the same file, should normally have an unique value.

: Multiple definitions of the same name will allow multiple sections to interfere in the starting and stopping of the sample.

: This method can't be used to control the pitch or volume of the sample, but instead multiple volume or pitch section should be included inside the same event.

: The types "raise" and "fall" will stop the playback of the sample regardless of any other event. This means that when the type "raise" is supplied, sample playback will stop when the event turns false. Using the type "fall" will stop playback when the event turns true.

: IMPORTANT
:: If the trigger is used for anything else but stopping the sound at a certain event, all sections with the same name ''should'' have exactly the same sections for everything but property and type.

:: In the case of just stopping the sample at a certain event, the sections for path, volume and pitch may be omitted.

; <code><path></code>
: This defined the path to the sound file. The path is relative to the FlightGear root directory but could be specified absolute.

: The sound format must be mono.

; <code><condition></code>
: Define a condition that triggers the event.

: For a complete description of the FlightGear conditions, please read docs-mini/README.conditions or read the [[Conditions]] article on the wikie.

: An event should define either a condition or a property.

; <code><property></code>
: Define which property triggers the event, and refers to a node in the FlightGear property tree.

: Action is taken when the property is non zero.

: A more sophisticated mechanism to trigger the event is described in <condition></code>

; <code><mode></code>
: This defines how the sample should be played:

:; once
:: The sample is played once. This is the default.

:; looped
:: The sample plays continuously, until the event turns false.

:; in-transit
:: the sample plays continuously, while the property is changing its value.

; <code><type></code>
: This defines the type of this sample, each type also have seperate volume slider in sound settings menu:

:; fx
:: This is the default type and doesn't need to be defined.

:; avionics
:: Sounds set to this type don't have a position and orientation but are treated as if it's mounted to the aircraft panel.

:: It is up to the user to define if it can always be heard or only when in cockpit view.

:; atc
:: Is used by the ATC chatter add-on.

; <code><delay-sec></code>
: Delay after which the sound starts playing.

: This is useful to let a property start two sounds at the same time, where the second is delayed until the first stopped playing.

; <code><volume></code> / <code><pitch></code>
: Volume or Pitch definition.

: Currently there may be up to 5 volume and up to 5 pitch definitions defined within one sound event.

: There are two important results from each <volume> and <pitch> section: the offset and the value. Normally all offset values from the different volume/pitch are added together to create the total offset. The values from each <volume> or <pitch> section are multiplied together to create an final value. Then the volume (or pitch, respectively) is set to total offset + final value.

: A special condition occurs when the value of factor is negative, in which case the offset doesn't get added to the other offset values but instead will be used in the multiplication section.

: Pitch final output can range from 0 to 2. 1 represents the original pitch of the sound file. Offset defaults to 1, meaning that if no specific <pitch> parameters are given the file will be played at its original pitch.

: Volume final output can range from 0 to 1. 1 represents full volume and 0 is silence.

:; <code><expression></code>
:: Defines an expression, and will replace all other tags in this volume/pitch tag.

:; <code><property></code>
:: Defines which property supplies the value for the calculation.

:: Either a <property> or an <internal> should be defined. If none is defined, the property reverts to its default. For volume this is 0, meaning the sound will not be audible at all.

:: The value is treated as a floating point number.

:; <code><internal></code>
:: Defines which internal variable should be used for the calculation.

:: The value is treated as a floating point number.

:: The following internals are available at this time:

::; dt_play
::: The number of seconds since the sound started playing.

::; dt_stop
::: The number of seconds after the sound has stopped.

:; <code><type></code>
:: Defines the function that should be used upon the property before it is used for calculating the net result:

::; lin
::: Linear handling of the property value. This is the default.

::; ln
:: Convert the property value to a natural logarithmic value before scaling it.

::: Anything below 1 will return zero.

::; log
::: convert the property value to a true logarithmic value before scaling it. (log base 10)

::: Anything below 1 will return zero.

::; inv
::: Inverse linear handling (1/x).

::; abs
:: Absolute handling of the value (always positive).

::; sqrt
::: Calculate the square root of the absolute value before scaling it.

:; <code><factor></code>
:: Defines the multiplication factor for the property value.

:: A special condition is when scale is defined as a negative value. In this case the result of |<scale>| * <property) will be subtracted from <default>

:; <code><offset></code>
:: The initial value for this sound.

:: This value is also used as an offset value for calculating the end result.

:; <code><random></code>
:: Add a bit of randomness to the offset. Only used for pitch.

:; <code><min></code>
:: Minimum allowed value.

:: This is useful if sounds start to sound funny. Anything lower will be truncated to this value.

:; <code><max></code>
:: Maximum allowed value.

:: This is useful if sounds gets to loud. Anything higher will be truncated to this value.

:: Keep in mind that min & max are applied first, then offset. So for example if min = 0, max = 0.5 and offset = 1.0, then the resulting values will range 1 to 1.5.

; <code><position></code>
: Specify the position of the sounds source relative to the 3D models center.

: The coordinate system used is a left hand coordinate system where +Y = left, -Y = right, -Z = down, +Z = up, -X = forward, +X = aft. Distances are in meters.

: It's important to note that for sounds the Y axis is inverted compared to e.g. object animation coordinates (see also [[Howto:3D_Aircraft_Models]]).

: The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!

: Also take notice that the values should not be 0.0, since that can produce sound artifacts on some sound cards.

; <code><x></code>
: X dimension offset (-X = forward, +X = aft, in meters)

; <code><y></code>
: Y dimension offset (+Y = left, -Y = right)

; <code><z></code>
: Z dimension offset (-Z = down, +Z = up)

; <code><orientation></code>
: Specify the orientation of the sounds source.

: The zero vector is default, indicating that a Source is not directional.

: Specifying a non-zero vector will make the Source directional in the X,Y,Z direction

; <code><x></code>
: X dimension

; <code><y></code>
: Y dimension

; <code><z></code>
: Z dimension

; <code><inner-angle></code>
: The inner edge of the audio cone in degrees (0.0 - 360.0).

: Any sound withing that angle will be played at the current gain.

; <code><outer-angle></code>
: The outer edge of the audio cone in degrees (0.0 - 360.0).

: Any sound beyond the outer cone will be played at "outer-gain" volume.

; <code><outer-gain></code>
: The gain at the outer edge of the cone.

; <code><reference-dist></code>
: Set a reference distance of sound in meters. This is the distance where the volume is at its maximum. Default is 60.

: Volume is clamped to this maximum for any distance below.

: Volume is attenuated for any distance above.

: Attenuation depends on reference and maximum distance. See OpenAL specification on "AL_INVERSE_DISTANCE_CLAMPED" mode for details on exact computation.

; <code><max-dist></code>
: Set the maximum audible distance for the sound in meters. Default is 6000.

: Sound is cut-off above this distance.

== Creating a configuration file ==

To make things easy, there is a default value for most entries to allow a
sane configuration when a certain entry is omitted.

{| class="wikitable"
! Tag !! Default value
|-
| '''<type>''' || lin
|-
| '''<factor>''' || 1.0
|-
| '''<offset>''' || 0.0 for volume, 1.0 for pitch
|-
| '''<min>''' || 0.0
|-
| '''<max>''' || 0.0 (don't check)
|}

Calculations are made the following way (for both pitch and volume):
<syntaxhighlight lang="cpp">
value = 0;
offs = 0;

for (n = 0; n < max; n++) {
if (factor < 0) {
value += offset[n] - abs(factor[n]) * function(property[n]);
} else {
value *= factor[n] * function(property[n]);
offs += offset[n];
}
}

volume = offs + value;
if (volume > 1.0) vol = 1.0;
</syntaxhighlight>
where function can be one of: lin, ln, log, inv, abs or sqrt

== Multiplayer sound ==
The multiplayer sound file works just as the normal sound file, except it should reside in <code>/sim/model/sound</code> instead of <code>/sim/sound</code>. Make sure it depends on properties that are [[Howto:Transmit_properties_over_MP|transmitted over MP]].

An example could be found in FGAddon 777-200: {{fgaddon aircraft url|777}}
* <code>777-200-set.xml</code> extends <code>777-200-common.xml</code> (this is not mandatory, just here to explain the inheritance. The -set.xml does/can include the model directly)
* <code>777-200-common.xml</code> references <code>Aircraft/777/Models/777-200.xml</code>
* <code>Models/777-200.xml</code> has an <code><sound><path>Aircraft/777/Sounds/mp-sound.xml</path></sound></code> reference
* <code>Sounds/mp-sound.xml</code> contains an ordinary sound config file with relative property paths resolved to the relative <code>/ai/models/multiplayer/</code> nodes of the multiplayer instance.

== Recommended audio file formats ==
{{note|The sound sample '''must be in mono''' format. This is because it can not be put in a 3D context otherwise. Also, as of at least June 2015 '''stereo samples will not be played'''.}}

There some considerations on the quality to the audio files. As a rule of thumb, any computer is able to playback sounds in DVD-quality (48 kHz/24 bits).
Macs still has trouble reading 32 bit files. Most standard sound cards also can't playback 32 bit files.

From a listeners point of view, anything above 44.1 kHz and 24 bits is only useful for high end music. Personally, I would think that 44.1 kHz with 16 bits should be more than enough to play engine sounds and alarms from the cockpit. Consider the disk-space against the gain in audio quality!

== Preventing sounds from playing when sim starts ==
Some times it can be hard to prevent sounds from playing right away, if the condition starts to evaluate to true. A hack to get this to work is to multiply the volume with a property that you in nasal set to true some seconds after the sim has been initialized.

== Bugs in the sound system ==
* The Doppler effect if you pass an aircraft in high speed sometimes is way too high pitch.
* None of the position coordinates must not be 0.0 as described above.
* Sounds using <code><mode></code> 'once' together with <code><max-dist></code> behave incorrectly when going out of range of the sound, then back in range, all while the trigger condition remains true:
** Until January 2023 (Flightgear 2020.3): the above causes the sound to incorrectly restart playing.
** Since January 2023 (for development versions): the sound stops entirely when going out of range, it is not possible to come back in range to hear the end of the sound.

== Related content ==
=== Wiki articles ===
* [[Conditions]]
* [[Expressions]]
* [[Howto:Reload sound configuration without restarting]]

=== Readme file ===
* {{readme file|xmlsound}}

=== Source code ===
* {{simgear file|simgear/sound/xmlsound.hxx}}
* {{simgear file|simgear/sound/xmlsound.cxx}}
* {{flightgear file|src/Sound/fg_fx.hxx}}
* {{flightgear file|src/Sound/fg_fx.cxx}}

[[Category:Aircraft enhancement]]

Howto:Add sound effects to aircraft

2024-04-20T13:31:55Z

Hbeni: /* Multiplayer sound */

You can '''add sound effects to aircraft''' by adding the sound samples and configuring the sound effects in XML files. The sound effects can be conditional and the sound's pitch and volume can depend on properties in the property tree.

{{note|This text is partially incorrect/outdated. Especially how the final volume/pitch is calculated. Make sure to also read the {{fgdata source|Docs/README.xmlsound|text=official documentation}}.}}

Some sound effects are added other ways. For example, sounds from avionics like navigation radio receivers are automatically added when you add those radios.

{{FGCquote|1= The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/28505220/ | title = <nowiki>Re: [Flightgear-devel] Stereo sounds no longer supported?</nowiki> | author = <nowiki>syd adams</nowiki> | date = Dec 7th, 2011 }}}}

{{FGCquote|1= The old way was that the stereo sound would always play the left channel on the left side. Now you split the sound and place it in 3D space. When you turn your head, the speaker the left side sound comes out of changes with you|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257291#p257291 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>bugman</nowiki> | date = Sep 14th, 2015 }}}}

{{FGCquote|1= All sounds must now be mono point sources, and stereo simply requires the two sound sources to be positioned in the 3D environment. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34100151/ | title = <nowiki>[Flightgear-devel] Audit and proposal for handling non-supported stereo sound files in FGAddon via the 3D sound engine.</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = May 10th, 2015 }}}}

{{FGCquote|1= We use OpenAL for 3D positional audio and most OpenAL implementations can only handle one stereo file.Also Stereo files will not work in 3d space, so they will not be positional.But most aircraft developers did not know that and used several stereo files expecting everything to work properly but the truth was that in most implementations just one of those stereo files was played.And if you think of it, stereo separation does not work for boarding music either since it plays left channel to your left ear and right channel to your right ear. But in reality boarding music is played left channel to the left audio channel in the aircraft and right channel to the right audio channel in the aircraft.This works the same as normal stereo if you enter the aircraft, but will, reverse once you turn around.So the solution is to split up the stereo file into two mono files and play the proper channel at the proper side of the passenger compartment.|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=257289#p257289 | title = <nowiki>Re: 787-8 Boarding music</nowiki> | author = <nowiki>erik</nowiki> | date = Sep 14th, 2015 }}}}

== Sound configuration files ==
The sound configuration files are [[PropertyList XML files]].

The top level sound configuration file is composed of a <code><fx></code> and a <code><name></code> tag, a <code><path></code> to a sound sample file and zero or more <code><volume></code> and/or <code><pitch></code>definitions.

Paths are relative to [[$FG_ROOT]], but absolute paths may also be used.

Comments are bracketed with <code></code>.

=== Example ===
This example would define an engine sound effect for a piston engine driven aeroplane.

The sound effect representing the engine is located in <code>$FG_ROOT/Sounds</code> and is named <code>wasp.wav</code>. The effect is started when the property <code>/engines/engine/running</code> becomes non-zero.

When that happens, the sound will be played looped (see <code><mode></code>) until the property returns zero again. As you can see the volume is dependent on the property <code>/engines/engine/mp-osi</code>, and the pitch of the sound depends on the property <code>/engines/engine/rpm</code>.

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>
<fx>
<engine>
<name>engine</name>
<path>Sounds/wasp.wav</path>
<mode>looped</mode>
<condition>
<property>/engines/engine/running</property>
</condition>
<volume>
<property>/engines/engine/mp-osi</property>
<factor>0.005</factor>
<min>0.15</min>
<max>0.5</max>
<offset>0.15</offset>
</volume>
<pitch>
<property>/engines/engine/rpm</property>
<factor>0.0012</factor>
<min>0.3</min>
<max>5.0</max>
<offset>0.3</offset>
</pitch>
</engine>
</fx>
</PropertyList>
</syntaxhighlight>

=== Inclusion from the aircraft-set.xml file ===
In order for the sound configuration to be used, it has to be included from the [[aircraft-set.xml]] file.

This can be done by adding the path to the file relative to the aircraft's base path within the <code><sim></code> tags in the aircraft-set.xml file..

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>
<PropertyList>

<sim>

<sound>
<path type="string">My-sound-config.xml</path>
</sound>

</sim>

</PropertyList>
</syntaxhighlight>

== Configuration tags ==

; <code><fx></code>
: Named FX subtree living under /sim/sound

; <code>< ... ></code>
: This is the event separator. The text inside the brackets can be anything, but it is advised to give it a meaningful name like: crank, engine, rumble, gear, squeal, flap, wind or stall.

: The value can be defined multiple times, thus anything which is related may have the same name (grouping them together).

; <code><name></code>
: This defines the name of the event. This name is used internally and, although it can me defined multiple times in the same file, should normally have an unique value.

: Multiple definitions of the same name will allow multiple sections to interfere in the starting and stopping of the sample.

: This method can't be used to control the pitch or volume of the sample, but instead multiple volume or pitch section should be included inside the same event.

: The types "raise" and "fall" will stop the playback of the sample regardless of any other event. This means that when the type "raise" is supplied, sample playback will stop when the event turns false. Using the type "fall" will stop playback when the event turns true.

: IMPORTANT
:: If the trigger is used for anything else but stopping the sound at a certain event, all sections with the same name ''should'' have exactly the same sections for everything but property and type.

:: In the case of just stopping the sample at a certain event, the sections for path, volume and pitch may be omitted.

; <code><path></code>
: This defined the path to the sound file. The path is relative to the FlightGear root directory but could be specified absolute.

: The sound format must be mono.

; <code><condition></code>
: Define a condition that triggers the event.

: For a complete description of the FlightGear conditions, please read docs-mini/README.conditions or read the [[Conditions]] article on the wikie.

: An event should define either a condition or a property.

; <code><property></code>
: Define which property triggers the event, and refers to a node in the FlightGear property tree.

: Action is taken when the property is non zero.

: A more sophisticated mechanism to trigger the event is described in <condition></code>

; <code><mode></code>
: This defines how the sample should be played:

:; once
:: The sample is played once. This is the default.

:; looped
:: The sample plays continuously, until the event turns false.

:; in-transit
:: the sample plays continuously, while the property is changing its value.

; <code><type></code>
: This defines the type of this sample, each type also have seperate volume slider in sound settings menu:

:; fx
:: This is the default type and doesn't need to be defined.

:; avionics
:: Sounds set to this type don't have a position and orientation but are treated as if it's mounted to the aircraft panel.

:: It is up to the user to define if it can always be heard or only when in cockpit view.

:; atc
:: Is used by the ATC chatter add-on.

; <code><delay-sec></code>
: Delay after which the sound starts playing.

: This is useful to let a property start two sounds at the same time, where the second is delayed until the first stopped playing.

; <code><volume></code> / <code><pitch></code>
: Volume or Pitch definition.

: Currently there may be up to 5 volume and up to 5 pitch definitions defined within one sound event.

: There are two important results from each <volume> and <pitch> section: the offset and the value. Normally all offset values from the different volume/pitch are added together to create the total offset. The values from each <volume> or <pitch> section are multiplied together to create an final value. Then the volume (or pitch, respectively) is set to total offset + final value.

: A special condition occurs when the value of factor is negative, in which case the offset doesn't get added to the other offset values but instead will be used in the multiplication section.

: Pitch final output can range from 0 to 2. 1 represents the original pitch of the sound file. Offset defaults to 1, meaning that if no specific <pitch> parameters are given the file will be played at its original pitch.

: Volume final output can range from 0 to 1. 1 represents full volume and 0 is silence.

:; <code><expression></code>
:: Defines an expression, and will replace all other tags in this volume/pitch tag.

:; <code><property></code>
:: Defines which property supplies the value for the calculation.

:: Either a <property> or an <internal> should be defined. If none is defined, the property reverts to its default. For volume this is 0, meaning the sound will not be audible at all.

:: The value is treated as a floating point number.

:; <code><internal></code>
:: Defines which internal variable should be used for the calculation.

:: The value is treated as a floating point number.

:: The following internals are available at this time:

::; dt_play
::: The number of seconds since the sound started playing.

::; dt_stop
::: The number of seconds after the sound has stopped.

:; <code><type></code>
:: Defines the function that should be used upon the property before it is used for calculating the net result:

::; lin
::: Linear handling of the property value. This is the default.

::; ln
:: Convert the property value to a natural logarithmic value before scaling it.

::: Anything below 1 will return zero.

::; log
::: convert the property value to a true logarithmic value before scaling it. (log base 10)

::: Anything below 1 will return zero.

::; inv
::: Inverse linear handling (1/x).

::; abs
:: Absolute handling of the value (always positive).

::; sqrt
::: Calculate the square root of the absolute value before scaling it.

:; <code><factor></code>
:: Defines the multiplication factor for the property value.

:: A special condition is when scale is defined as a negative value. In this case the result of |<scale>| * <property) will be subtracted from <default>

:; <code><offset></code>
:: The initial value for this sound.

:: This value is also used as an offset value for calculating the end result.

:; <code><random></code>
:: Add a bit of randomness to the offset. Only used for pitch.

:; <code><min></code>
:: Minimum allowed value.

:: This is useful if sounds start to sound funny. Anything lower will be truncated to this value.

:; <code><max></code>
:: Maximum allowed value.

:: This is useful if sounds gets to loud. Anything higher will be truncated to this value.

:: Keep in mind that min & max are applied first, then offset. So for example if min = 0, max = 0.5 and offset = 1.0, then the resulting values will range 1 to 1.5.

; <code><position></code>
: Specify the position of the sounds source relative to the 3D models center.

: The coordinate system used is a left hand coordinate system where +Y = left, -Y = right, -Z = down, +Z = up, -X = forward, +X = aft. Distances are in meters.

: It's important to note that for sounds the Y axis is inverted compared to e.g. object animation coordinates (see also [[Howto:3D_Aircraft_Models]]).

: The volume calculation due to distance and orientation of the sounds source ONLY work on mono samples!

: Also take notice that the values should not be 0.0, since that can produce sound artifacts on some sound cards.

; <code><x></code>
: X dimension offset (-X = forward, +X = aft, in meters)

; <code><y></code>
: Y dimension offset (+Y = left, -Y = right)

; <code><z></code>
: Z dimension offset (-Z = down, +Z = up)

; <code><orientation></code>
: Specify the orientation of the sounds source.

: The zero vector is default, indicating that a Source is not directional.

: Specifying a non-zero vector will make the Source directional in the X,Y,Z direction

; <code><x></code>
: X dimension

; <code><y></code>
: Y dimension

; <code><z></code>
: Z dimension

; <code><inner-angle></code>
: The inner edge of the audio cone in degrees (0.0 - 360.0).

: Any sound withing that angle will be played at the current gain.

; <code><outer-angle></code>
: The outer edge of the audio cone in degrees (0.0 - 360.0).

: Any sound beyond the outer cone will be played at "outer-gain" volume.

; <code><outer-gain></code>
: The gain at the outer edge of the cone.

; <code><reference-dist></code>
: Set a reference distance of sound in meters. This is the distance where the volume is at its maximum. Default is 60.

: Volume is clamped to this maximum for any distance below.

: Volume is attenuated for any distance above.

: Attenuation depends on reference and maximum distance. See OpenAL specification on "AL_INVERSE_DISTANCE_CLAMPED" mode for details on exact computation.

; <code><max-dist></code>
: Set the maximum audible distance for the sound in meters. Default is 6000.

: Sound is cut-off above this distance.

== Creating a configuration file ==

To make things easy, there is a default value for most entries to allow a
sane configuration when a certain entry is omitted.

{| class="wikitable"
! Tag !! Default value
|-
| '''<type>''' || lin
|-
| '''<factor>''' || 1.0
|-
| '''<offset>''' || 0.0 for volume, 1.0 for pitch
|-
| '''<min>''' || 0.0
|-
| '''<max>''' || 0.0 (don't check)
|}

Calculations are made the following way (for both pitch and volume):
<syntaxhighlight lang="cpp">
value = 0;
offs = 0;

for (n = 0; n < max; n++) {
if (factor < 0) {
value += offset[n] - abs(factor[n]) * function(property[n]);
} else {
value *= factor[n] * function(property[n]);
offs += offset[n];
}
}

volume = offs + value;
if (volume > 1.0) vol = 1.0;
</syntaxhighlight>
where function can be one of: lin, ln, log, inv, abs or sqrt

== Multiplayer sound ==
The multiplayer sound file works just as the normal sound file, except it should reside in <code>/sim/model/sound</code> instead of <code>/sim/sound</code>. Make sure it depends on properties that are [[Howto:Transmit_properties_over_MP|transmitted over MP]].

An example could be found in FGAddon 777-200: {{fgaddon aircraft url|777}}
* <code>777-200-set.xml</code> extends <code>777-200-common.xml</code> (this is not mandatory, just here to explain the inheritance. The -set.xml does/can include the model directly)
* <code>777-200-common.xml</code> references <code>Aircraft/777/Models/777-200.xml</code>
* <code>Models/777-200.xml</code> has an <code><sound><path>Aircraft/777/Sounds/mp-sound.xml</path></sound></code> reference
* <code>Sounds/mp-sound.xml</code> contains an ordinary sound config file with relative property paths resolved to the relative <code>/ai/multiplayer</code> nodes of the multiplayer instance.

== Recommended audio file formats ==
{{note|The sound sample '''must be in mono''' format. This is because it can not be put in a 3D context otherwise. Also, as of at least June 2015 '''stereo samples will not be played'''.}}

There some considerations on the quality to the audio files. As a rule of thumb, any computer is able to playback sounds in DVD-quality (48 kHz/24 bits).
Macs still has trouble reading 32 bit files. Most standard sound cards also can't playback 32 bit files.

From a listeners point of view, anything above 44.1 kHz and 24 bits is only useful for high end music. Personally, I would think that 44.1 kHz with 16 bits should be more than enough to play engine sounds and alarms from the cockpit. Consider the disk-space against the gain in audio quality!

== Preventing sounds from playing when sim starts ==
Some times it can be hard to prevent sounds from playing right away, if the condition starts to evaluate to true. A hack to get this to work is to multiply the volume with a property that you in nasal set to true some seconds after the sim has been initialized.

== Bugs in the sound system ==
* The Doppler effect if you pass an aircraft in high speed sometimes is way too high pitch.
* None of the position coordinates must not be 0.0 as described above.
* Sounds using <code><mode></code> 'once' together with <code><max-dist></code> behave incorrectly when going out of range of the sound, then back in range, all while the trigger condition remains true:
** Until January 2023 (Flightgear 2020.3): the above causes the sound to incorrectly restart playing.
** Since January 2023 (for development versions): the sound stops entirely when going out of range, it is not possible to come back in range to hear the end of the sound.

== Related content ==
=== Wiki articles ===
* [[Conditions]]
* [[Expressions]]
* [[Howto:Reload sound configuration without restarting]]

=== Readme file ===
* {{readme file|xmlsound}}

=== Source code ===
* {{simgear file|simgear/sound/xmlsound.hxx}}
* {{simgear file|simgear/sound/xmlsound.cxx}}
* {{flightgear file|src/Sound/fg_fx.hxx}}
* {{flightgear file|src/Sound/fg_fx.cxx}}

[[Category:Aircraft enhancement]]

Julia photoscenery generator

2024-04-13T07:52:35Z

Hbeni: /* --help or -h */ update and reformat code block

{{Infobox Software
|title = FGCom-mumble
|logo = G91R1B taking off from LOWI .jpg|128px
|developedby = Adriano Bassignana
|developmentstatus = Active
|type = Photoscenery generator
|latestrelease = (rolling releases)
|initialrelease = 18.04.2021
|writtenin = julia
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v2
|website = https://github.com/abassign/Photoscenary
}}
[[File:G91R1B taking off from LOWI .jpg|thumb|500px|Photoscenery created with the Julia photoscenery generator behind a [[FIAT G91R1B|G91R1B]] taking off from LOWI. In this example the resolution of the tiles is 32K (s 6).]]

Through the '''Julia photoscenery generator''' using ImageMagic and written in the Julia programming language you can create photoscenery tiles.

Once you have everything installed you will discover how easy it is to fill your disk with hundreds of GB made from thousands of images of our planet and then fly over vast territories and recognize our cities and villages.

The use of World Scenery by FlightGear together with the photoscenery as a background can make the scene very rich in details and pleasing to your eyes.
== Quick method for Windows users ==
===Steps===
* 1. [https://julialang.org/downloads/#official_binaries_for_manual_download Down-Inst Julia Programming Language].
* 2. [https://imagemagick.org/script/download.php#windows Down-Inst ImageMagick].
* 3. [https://github.com/abassign/Photoscenary/archive/refs/heads/main.zip Down-Inst photoscenary.jl.zip] Easy Manual installation. Unzip Fhotoscenary-main folder, place it where you preferred. Look inside for the file photoscenary.jl and make it executable by Julia, using Right click >> Properties >> Navigate to the bin folder Julia.exe and choose open with Julia Programming Language.
===Check===
* 4. Open FGlauncher >> Settings >> Additional settings. Add the property: --telnet=5000
* 5. Make sure you have terrasync activated. Automatic download terrain in FGlauncher.
* 6. In FlightGear v2020.3.18 check the following: Start the simulator (one flight) and access the menu: VIEW/RENDERING OPTIONS. In the right column, make sure you have the "SATELLITE PHOTOSCENERY" option activated and close the flight.
===Run & Check===
* 7. Run the program photoscenary.jl. It will run and check with Julia, will prompt telnet connection attempts at 127.0.0.1:5000.
* 8. Run FG. Fly and check visually that you are getting textures. Give it a time, you'll get better textures progressively during your flight.
* 9. Check in C:\Users\YOUR_USER_NAME\FlightGear\Downloads\TerraSync\Orthophotos. You should see folders of type "e000n00" containing ".dds" files.
* 10. Check that the Julia's window running photoscenary.jl is getting data (tiles).

In case of doubts, the next video at SUMU Montevideo area by Manuel Aceña is recommended as a reference.
=== Video ===
{{#ev:youtube|PbYAvxmAkIc}}

==Background==
The success that photoscenery is achieving among FlightGear users has prompted me to study a program for downloading and installing photoscenery via a simple command to run inside a terminal (if we are in Linux or Mac OS) or in a command prompt (if we are in Windows).

The program was developed in Julia which is a latest generation programming language developed by MIT. This language looks quite similar to Nasal and therefore the code is easily readable by those who already use the FlightGear Nasal language script, but it is extremely faster and full of features that make the creation of this program quick and easy enough to evolve. Obviously the only inconvenience is that Julia has to be installed on your system, but it is a very simple action and equivalent to the same need to install ImageMagick on your system, this latter program allows the conversion of images in DDS format.
[[File:Julia photoscenery generator - Towards Budapest on the Danube plain.jpg|thumb|500x500px|The photoscenary allows to have very realistic effects on rather complex territories, such as crops in the plains. The image shows the signs of the passage of old rivers, still visible as a difference in the color of the vegetation.]]

==Installing the programs==

=== FlightGear ===
Currently to utilise photoscenery the minimum FlightGear version is 2020.3.18

===Julia installation===
https://julialang.org/

Julia installation is straightforward, whether using precompiled binaries or compiling from source. Download and install Julia by following the instructions at https://julialang.org/downloads/.
{| class="wikitable"
!Windows
| colspan="3" |'''64-bit (installer), 64-bit (portable)'''
| colspan="3" |32-bit (installer), 32-bit (portable)
|-
!macOS
| colspan="3" |'''64-bit'''
| colspan="3" |
|-
!Generic Linux on x86
| colspan="3" |'''64-bit (GPG), 64-bit (musl) (GPG)'''
| colspan="3" | 32-bit (GPG)
|-
!Generic Linux on ARM
| colspan="3" |'''64-bit (AArch64) (GPG)'''
| colspan="3" |32-bit (ARMv7-a hard float) (GPG)
|-
!Generic Linux on PowerPC
| colspan="3" |64-bit (little endian) (GPG)
| colspan="3" |
|-
!Generic FreeBSD on x86
| colspan="3" | 64-bit (GPG)
|
|}
For Linux users there are no particular problems, each distribution has Julia among the installable programs. The only problem is the version that may be older than 1.6, in this case I recommend wasting a little more time and updating the installation to 1.6, you can follow [https://medium.com/coffee-in-a-klein-bottle/install-julia-1-5-on-ubuntu-bb8be4b2571d this handy guide] that explains how to do everything in a few minutes.

The version to use is convenient that it is from '''1.6''' onwards, 1.5.4 is present in the Ubuntu repositories until 2020.10 but it is better to update it to 1.6 even if this requires a little work, But with Ubuntu/Kubuntu version 2021.4 Julia is already at version 1.6.1 and so just use the command:

<code>'''sudo apt install julia'''</code>

Julia is a young language that is continuously updated and the difference between Julia 1.5 and 1.6 is really very big for the application startup speed. For the execution there are no particular differences if you use Julia 1.5.4 onwards.

The installation with windows is absolutely the easiest to do, just follow the installer to get a version of Julia 1.6.x All users who have done the installation have never complained of problems.

For '''Mac users''' it might be the slightly more complicated thing, but from the users texts made, I haven't had any issues encountered among Mac users.

For '''Windows users''' have not encountered any particular problems with the installation, which is always the most up-to-date.

{{caution
|The program was designed to work in Linux (any distribution), Windows 10 and Mac OS. This is very unlikely to work with CygWin as there have been reports of problems calling Imagemagick. Instead, it works with Windows Subsystem for Linux, which is basically a well-integrated emulator of Linux inside the Windows system. In this case, multithreading may not work well, so I recommend running the program with only one Julia thread via the command:<BR><i>julia -t 1 photoscenary.jl ...</i><BR>Or with the command:<BR><i>julia photoscenary.jl</i><BR>But this approach seems like an unnecessary complication to me as the program works perfectly in Windows 10.
| width =
| padding =
| margin = 2%
}}

===ImageMagick installation===
https://imagemagick.org/index.php

For download program this is the link: https://imagemagick.org/script/download.php

Normally the files that are released by satellite image servers are in PNG format, but the PNG files are absolutely unsuitable to be used as photoscenery files. The reason is that the graphics engine of FlightGear must still convert these files into DDS format which is more compressed than the PNG format (about 4 times). Conversion, for very large files, takes a lot of CPU time, slowing down the execution of FlightGear. Therefore for this program it has been chosen to release only the DDS format and therefore ImageMagick is the most suitable program for this operation.

ImageMagick allows you to convert files transparently to the user very quickly.

In Linux distributions, ImageMagick is often already present, to find out just type the command <code>'''convert --version'''</code> and see if something responds. In windows it must be downloaded with an installer that can be downloaded here: https://imagemagick.org/script/download.php#windows

The installation in Windows of ImageMagick could give problems if it has not been correctly carried out. Therefore, if the photoscenary.jl program returns an error due to the lack of ImageMagick (the program always checks at the start) it is convenient to remove ImageMagick through the Windows program management and install it again.

===The photoscenary.jl installation===
https://github.com/abassign/Photoscenary

The program is written in pure Julia code, there are no scripts that can complicate your life. However, some rules must be followed that simplify all the work.

First create a directory where to place the program and its support files. The directory can be placed wherever you want as the program will dynamically build its references. Once the directory (or folder for Mac users) is done, download the Zip file that GitHub generates obtained from this link: https://github.com/abassign/Photoscenary.git

[[File:Github for photoscenary.jl.png|alt=|800x800px]]

Click on code and it will download the zip file that you can open and insert the contents into the folder you created. In the folder you will find some auxiliary files, but now let's analyze the program files.

*<code>'''photoscenary.jl'''</code> It is the Julia program to run, you can open it and see it with a simple text editor, I think some of you who have programmed in Python or NASAL will have no difficulty understanding how it works. However the program is compiled every time you run it, it is this compilation, really efficient and fast, that allows you to obtain an excellent executive performance.
*<code>'''params.xml'''</code> It is an XML file that contains some parameters necessary for the correct execution of the program.
*<code>'''airports.csv'''</code> It is the file, extracted from the correspondent of FlightGear, which contains a list of airports, their coordinates and the extended name. This file is essential in order to use a location option for the area to be downloaded.

==Execution of the program ==

===Hello World!===
There is a minimal execution that allows you to check if everything we have done has worked correctly, this is a sort of ''Hello World'' of the program.

The most important thing is to go to the directory (folder) where you installed the program with a ''terminal'' or with a ''command prompt'' (if you are in Windows).

So the first thing to do is to be with the terminal inside this directory and run this command:

<code>'''julia photoscenary.jl'''</code>

An area of 2048 pixels (long side) tiles with a size of approximately 10x10 NM is generated, with the coordinates of the ''Orio al Serio Airport'' (LIME) in the center. Not having entered any other parameters, the processing time is relatively long as only one download per tile is performed.

[[File:Test julia photoscenary.jl.png|frameless|800x800px]]

We carefully observe this execution, the first line shows the name of the program, the version and the date of realization, then follows the indication that the prerequisite test will take place. If we are at the first execution we will see an endless series of compilations that can make us think that something has not gone well, but do not worry, it is simply the module management system that downloads the modules useful for the execution of the program and that are not present in the base system. In this way the Julia program updates the necessary components without having to prompt the user to do it for him.

In this particular case, which occurs only the first time or in a version change, the application communicates that it will terminate the execution and invites the user, once back to the command prompt, to run the same command again, also in this case there could be a lot of updating of the modules that have not been updated in the first cycle, do not worry, everything is going great. At the end of the update, finally, the execution of the code contained in the program takes place.

The image above summarizes what happened during the download of the tiles.

Very important to note the line:

'''ImageMagick is operational!'''

This line tells us that the system has done a test with ImageMagick installed on its system and has verified that it works correctly. If this does not work, since without ImageMagick the system cannot do anything, you have an exit with a program error (Error code 504).

====Description of the individual status lines of the processes performed====
We now summarize the content of the individual lines that indicate the modules downloaded and their status:

{| class="wikitable"
!Column!!Content
|-
!Time:
|Processing time for individual tiles
|-
!elab:
|Total processing time
|-
!
( ... {{!}} ... ) 
|The processing time for each tile followed by the estimated time.
These two values allow us to understand the efficiency of the work in progress.
|-
!Tiles:
|Number of tiles that have been processed by the program.
|-
! on
|Total number of tiles to be processed.
|-
!res
|The residual tiles to be processed.
|-
!Th:
|Number of threads used by the process.
|-
!path:
| The path and name of the processed file.
|-
!MB/s:
|Download speed in Mega Bytes on second.
|-
!MB dw:
|Amount of mega bytes downloaded overall.
|-
!( ... )
| Type of activity carried out
|}

=== Activate the Julia multi thread ===
Julia is a language created for applications on supercomputers, artificial intelligence, number-crusher, etc.

These are applications that require systems with a lot of CPUs and therefore the compiler has the ability to activate very sophisticated strategies to better manage resources.

The photoscenary.jl program performs many processes in parallel in order to optimize the download and conversion of images. The conversion from the original PNG format to the more efficient format for FlightGear DDS requires a rather heavy application (ImageMagick) which can only be run on single CPUs. For this it is very efficient to run the program on multiple CPUs, but it is necessary to use some care that I explain below.

==== Core <-> CPU what are they ? ====
Any PC has a processor with a certain number of ''physical'' ''core'' ranging from 2 (Intel i3) to values that can go up to 12 or more for more performing desktop processors.

For years, all processor cores have been able to handle two separate CPU, using a hardware trick. Therefore an i3 processor with two core will allow to manage up to 4 CPU (or separate processes) at the same time.

At this point it is important the role of the operating system that must manage the available CPU and assign them to the running programs.

So when you start Julia it is possible to reserve the number of CPU to the application will require than and this must be done at the beginning so that the compiler will configure the code properly.

This is achieved with the '''-t n''' command where n is a number equal to or less than the number of available CPU.

==== The Julia -t n option ====
If you run the program with the command:

'''<code>julia photoscenary.jl</code>'''

Only one CPU will be used and this can be a bottleneck when downloading files from the web server that distributes the images, since, especially if you have images composed of a single file (from the smallest ones up to 2048 pixels) the program uses only one process (for larger images the program uses many more download processes).

So let's say we have a machine with 6 core and therefore 12 CPU we can launch the program with this command:

<code>'''julia -t 10 photoscenary.jl'''</code>

If we are on a 4 CPU as i3 it is necessary to reduce the value to 4, but maybe 3 would also be good, so we can write the command like this:

<code>'''julia -t 3 photoscenary.jl'''</code>

==== Be careful though ====
''If the value of the maximum number of CPU is too high, the behavior of the operating system could be such as to reduce the advantage in execution or even slow down the program!''

This certainly happens when the value of the '''''-t''' numbe''r is higher than the number of CPUs and if the system is windows 10 or 8 you will have an incredible slowdown of the program! Therefore on a Windows machine it is not advisable to always enter a value less than or equal to the number of CPU of the processor in use (''number of cores multiplied by 2'').

For Linux and Mac systems the problem seems to be less evident and so you can try to increase the number beyond the theoretical maximum value.

=== Now let's try to delete all the files just inserted===
This test allows us to understand the use of a very useful parameter to manage the files we create with this application, for example if we want to delete the files, perhaps to have an area managed with the traditional FlightGear system, we can do it with the following command:

<code>'''julia -t 10 photoscenary.jl --over 9'''</code>

We will get this result (I show only the last lines to focus attention on the fact that the system declares to perform some removes)

[[File:Test julia photoscenary.jl --over 9.png|frameless|800x800px]]

===Now lets put the turbojet into the download program===
We now put the <code>'''-t 10'''</code> option on the Julia compiler start command. This option allows you to run multiple threads at the same time allowing you to speed up the download of files.

<code>'''julia -t 10 photoscenary.jl'''</code>

[[File:Test julia -t 10 photoscenary.jl.png|frameless|800x800px]]

In this image I show all the lines processed to show how the progression of the download speed increase. As you can see at first the speed seems low, but in reality the system has launched about ten threads that form a queue of requests to the image server. The format of the images, when nothing is declared, as in this example, is 2048 pixels on the long side, and the size of the DDS file (we are at an intermediate latitude between 62-22 degrees) is 1 MB.

The average speed is 1.7 MB/s (but can go even higher) and is determined by the actual workload on the server distributing the images.

This way we have more than tripled the download speed.

Obviously these values can change a lot, but they are on average better than those obtained with single downloads. Not only that, but multithreading also works with the ImageMagick program that performs the transformation of the PNG file into DDS, this transformation is not fast, but in this way it is parallelized, making this phase less expensive in terms of time.

This feature is even more interesting for larger format images.

===Increase the resolution of the images, radius and --over option===
Let's see these two new options that can be given to the program:

<code>'''-r 5'''</code> where n is the number of miles of radius, if <code>'''-r'''</code> (Radius) is equal to 5 it means that we are covering a square whose diagonal is 5 NM. Note that if -r is not defined the system considers the radius of 10 NM.

<code>'''-s 4'''</code> indicates the resolution of the images we want to obtain, if this option is not inserted the default value is 2 equal to an image, on the long side, of 2048 pixels.

<code>j'''ulia -t 10 photoscenary.jl -r 5 -s 4'''</code>

[[File:Test julia -t 10 photoscenary.jl -r 5 -s 4 (skip).png|frameless|800x800px]]

In fact the system has not done anything, the status message, at the bottom of each line, tells us (skip) which means that the program has seen that an image is already present and this image cannot be overwritten as it is an image valid (actually the program checks the image by loading and verifying it), if the image was not valid, it would delete it and replace it with a new one.

But it is still possible to override by inserting the <code>'''--over 1'''</code> option at this point this interesting fact happens:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 4 --over 1'''</code>

[[File:Test julia -t 10 photoscenary.jl -r 5 -s 4 --over 1.png|frameless|800x800px]]

This download is '''16 times slower''' as the precedent download (Without the <code>-s</code> option the image downloads as <code>-s 2</code> which corresponds to 2048 pixels long edge) <code>'''-s 4'''</code> option downloads images of '''8192''' pixels long side. In fact the system downloads 16 images with size of '''2048''' and composes them into a matrix '''4x4,''' at the end of the composition the images are first transformed into an temporary PNG image format which will be processed by ImageMagick and becomes an DDS format image that is compatible with FlightGear without any on-the-fly conversion (which is done for PNG images). Therefore this line shows us the downloading of the single images that make up the matrix in order to give an idea that something is happening.

[[File:Julia -t 10 photoscenary.jl -r 5 -s 4 --over 1-BW.png|alt=|frameless|799x799px]]

Note that the download speed of individual images has increased (in this case 2.98 MB/s) as the system has opened several dozen download threads (96 download tasks are open at the same time as their number is the product of 6 threads x 16 images) .

It is important to understand this aspect of the program which can easily bring the network into saturation. In this example 3 MB/s correspond to about 30-40 MBit/s which is about 70-80% of the bandwidth that the network allows me to have. For this, if the band used is high, in order to keep a good surfing speed on the network, it is sufficient to reduce the value of the threads in Julia from -t 10 to -t 4 or -t 5.<blockquote>'''Note''': ''Julia is a programming language that has an incredible variety of methods for exploiting all possible hardware solutions. What I exploit in this program is only a small part, Julia even allows you to distribute the processing on remote machines, perhaps placed on different networks, in order to distribute the workload through the use of a few instructions.''</blockquote>From a series of tests that I have done, 8K images are the most interesting for systems that have at least 16 GB of RAM, if the RAM is lower these images can lead to FlightGear in memory overflow and therefore its closure by the system operating.

==== The -s parameter ====
<code>'''-s'''</code> defines 7 possible resolutions for images:
{| class="wikitable"
!Parameter!!Side px!! Format!!Size MB!! Comment
!PC RAM GB
|-
!-s 0
|style="text-align: center;"|512
|style="text-align: center;"|DDS
|style="text-align: center;"|0.064
|
|style="text-align: center;"|2
|-
!-s 1
|style="text-align: center;"|1024
|style="text-align: center;"|DDS
|style="text-align: center;"|0.256
|
|style="text-align: center;"|2
|-
!'''-s 2'''
|style="text-align: center;"|2048
|style="text-align: center;"|DDS
|style="text-align: center;"|1
|
|style="text-align: center;"|4
|-
!-s 3
|style="text-align: center;"|4096
|style="text-align: center;"|DDS
|style="text-align: center;"|4
|2 x 2 matrix = 4 images with 2048 pixels side to download
|style="text-align: center;"|8
|-
!'''-s 4'''
|style="text-align: center;"|8192
|style="text-align: center;"|DDS
|style="text-align: center;"|16
|4 x 4 matrix = 16 images with 2048 pixels side to download
|style="text-align: center;"|16
|-
!-s 5
|style="text-align: center;"|16384
|style="text-align: center;"|DDS
|style="text-align: center;"|64
|8 x 8 matrix = 64 images with 2048 pixels side to download
|style="text-align: center;"|16
|-
!-s 6
|style="text-align: center;"|32768
|style="text-align: center;"|DDS
|style="text-align: center;"|256
|8 x 8 matrix = 64 images with 4096 pixels side to download
|style="text-align: center;"|16
|}
The PC RAM that I recommend for PCs that need to download images. So I was able to download, even with Windows 10, which is much heavier than Linux, 16384 px images with only 4 GB of RAM! In this case there is a huge increase in virtual memory (''Both Linux with kernel 5 and Windows 10 have a dynamic virtual memory that is quite efficient if the hard disk is of the SSD type'') in use which, due to the structure of the program and the particular compiler used, it does not seem to slow down performance.

==== The --sdwn parameter====
<code>'''--sdwn'''</code> It is a parameter that defines how to change the value of the resolution or the distance using a linear method. For example, if the coverage radius is 100 nm and -s 5 (16K pixels), if we set <code>'''--sdwn 2'''</code> we will have this resolution trend:
{| class="wikitable"
!Dist. (nm)
!0
!10
!20
! 30
!40
! 50
!60
!70
!80
!90
!100
|-
!Res. (0..6)
|5
|4
|4
|4
|3
|3
|2
|2
|2
|2
|2
|}
As can be seen from the table, the resolution in pixels of the images varies with the distance from the center (radius).

With this method it is possible to obtain very large coverage without occupying too much memory and greatly reducing download times. Certainly the quality of the farther images is lower, but the problem could be not very perceptible as normally an airplane when it takes off is low on the ground and therefore the pilot wishes to have a high resolution (images with many pixels), but then rises in altitude and the resolution of the terrain is acceptable although much lower. With this method it is possible to cover large areas of land in a very short time, shorter than the flight necessary to cross that territory.

====The --over parameter====
A second important fact is the <code>'''--over 1'''</code> parameter which tells the system it can overwrite, the <code>'''--over'''</code> option <code>'''1'''</code> indicates that overwriting can only occur if the new file is larger than the file it replaces.

With this technique it is possible to build limited areas with higher resolution, for example airport areas, or particularly beautiful areas that we want to enhance.

The <code>'''--over'''</code> option has the following recognized parameters:
{| class="wikitable"
!Parameter!!Overwriting/deletion
|-
!--over 0
|Default option that inhibits any overwriting of images.
|-
!--over 1
|Overwrite only if the image to be replaced is larger than the present one
if the previous image is not present, the image will be inserted anyway.
|-
!--over 2
|Always overwrites, for example if you want to reduce the size of the images by a certain area.
|-
!--over 9
|Deletes the images present in the defined area.
|}

===Let's go to Fiumicino (Rome in Italy) by -i option===
<code>'''julia -t 10 photoscenary.jl -s 4 -i fiumicino'''</code>

[[File:Screenshot 20210520 125012.png|alt=|frameless|799x799px]]

We are already familiar with these options

The absence of '''<code>-r</code>''' indicates that the image extraction radius is the default of 10 nm.

<code>'''-s 4'''</code> indicates a resolution of 8192 pixels long side

But this is new

<code>'''-i fiumicino'''</code>

It means that we are selecting an airport containing the word '''fiumicino''<nowiki/>'. The search takes place in a database, with an Open Data license, which reports over 60,000 airports that have ICAO code.

The database is distributed together with the ''photoscenary.jl'' program with the ''airports.csv'' file, which is easily editable, via a text editor. The ''airports.csv'' file is not actually the database used by the program, but only the data source which is automatically converted into the more practical ''airports.jdb'' file which is the database file used by the JuliaDB package.

If you want to edit ''airports.csv'', once the file is saved, you will notice that the next time you run the ''photoscenary.jl'' program it will take a few seconds until a new ''airports.jdb'' is generated.

The text inserted after the '''<code>-i</code>''' parameter can contain a single word or a sentence, but in this case it must be delimited by double quotes.

'''<code>-i "leonardo da vinci"</code>'''

Once the program has started, the system will respond by entering also with this output:

[[File:Screenshot 20210520 213622.png|frameless|600x600px]]

For example, if you enter as a name

'''<code>-i rome</code>'''

The program will respond with the first 30 airports that correspond to the presence of the word Rome in one of the three search fields, as shown in this figure.

[[File:Screenshot 20210520 215037-2.png|frameless|800x800px]]

In this case, just enter a unique selector, such as the ICAO ID, to obtain the searched airport, as in this example:

'''<code>-i LIRF</code>'''

Therefore, the search using the -i option can be extremely convenient, as it allows you to quickly have the coordinates of any airport present in the ICAO database.

The search word can also be partial as in this example:

'''<code>-i zuric</code>'''

[[File:Screenshot 20210520 220731.png|frameless|600x600px]]

Any accented letters are normalized to the unaccented Latin form, for example:

''Zürich Airport'' becomes ''Zurich Airport''

and therefore the search can be successful if you write:

'''<code>-i "zurich airport"</code>'''

=== Dynamically download orthographic images by --connect ===
It is very convenient to download the orthographic images of the territory actually flown over by the plane.

In this case, the system will use the aircraft's course as reference, interspersed with points of radius -r.

The program will then download only the images actually needed, thus minimizing the amount of data to download.

The parameter to activate this function is this:

<code>'''--connect "<IP address>:<port>"'''</code>

When the program finds this parameter, checks if the syntax of the address is correct and listens showing a line that has as, first character and an arrow that rotates 45 degrees every second, followed by the sentence that begins with the text:

<code>'''Try the frist connection to Flightgear with address: ...'''</code>

This delay can last for an indefinite time, until Flightgear is activated with, obviously, the Telnet connection port activated, as explained above.

When Flightgear is activated, the program realizes it and starts evaluating the geographic position of the aircraft and then, if necessary, downloading and positioning the DDS images in the photorealistic scenario.

If you close Flightgear again, the program will be put on hold again, a situation indicated by the message:

<code>'''Try connect to Flightgear with address: ...'''</code>

To exit the program it is necessary to type the key sequence: [CTRL] + [C]

Exiting the program will have no effect on the downloaded DDS files as the program operates through transactional methods.

==== A simple example ====
For example, you can run this command:

<code>julia -t 4 photoscenary.jl --connect "127.0.0.1:5000"</code>

In this case the program will download the images in a radius of 10 nm for the entire length of the route. Thus forming a corridor of images that can give the illusion of a much larger territorial coverage than reality.

The images, if the <code>-s n</code> parameter is not specified, will have the size of 2048 px, this is a good enough size for flights above 10,000 ft.

If the speed of the plane is not too high and the internet line is good, it may happen that the pilot can get a flight with complete coverage of the orthographic images, giving the illusion of having downloaded very large geographical areas and more a narrow corridor that follows the route followed by the plane ..

If, on the other hand, the speed of the plane is high, or the speed of downloading the images is not high, it may be necessary, from time to time, to activate the option to update the scenario using the command:

''[menu] -> [debug] -> [Reload Scenery]''

In this case the simulator will freeze for a few seconds and then a scenario will be observed with orthographic images of the territory overflown.

==== Preparation of Flightgear to allow you to communicate with the photoscenary.jl program ====
[[File:Julia photoscenery generator - launcher QT configuration - 20210618 232448.png|frameless|800x800px]]

First you need to run Flightgear with the option:

<code>'''--telnet=5000'''</code>

This command will activate the telnet server on Flightgear with port 5000 active. The port can be changed, but the important thing is that it is then the communication port entered in the <code>--connect</code> command.

In the example in Additional Settings we see that the first line is the telnet server activation command, server needed to communicate with the photoscenary.jl program.

In additional settings I have inserted two other options that may be useful:

The parameter ''--httpd = 5001'' which activates an HTTP server, visible through the browser, useful for displaying the route on a geographic map. The third option instead activates multithreading which, eg run PC with at least 2 cores, allows you to render the flight more fluid.

==== Performing dynamic loading of orthographic images during flight ====
First you need to start Flightgear (and with it the telnet server we configured previously), wait for its loading phase to finish. And then start the program:

<code>'''julia -t 4 photoscenary.jl --connect "127.0.0.1:5000"'''</code>

[[File:Julia photoscenery generator - execution connect param - 20210618.png|frameless|800x800px]]

Unlike the other methods of selecting the areas to be filled with images, this method can show an intermediate step called "System pending ..." which allows you to communicate to the pilot that the program is running smoothly, but has already downloaded all the images needed for the current flyover area and then waits to reach the next area from which it will start downloading images again.

==== However, the other options are also allowed ====
<code>julia -t 4 photoscenary.jl --connect "127.0.0.1:5000" -s 3 --over 1</code>

The <code>--connect</code> command does not prevent the use of other options, such as image resolution and enabling overwriting if the new image is of a higher resolution than the one already present.

===Follow a route generated with route manager by --route===
The FlightGear ''route manager'' program allows you to generate a route that passes through various points and/or airports, the route can be saved to a file that is placed in the Export folder of the FlightGear $FG Home directory.

[[File:Screenshot 20210523 211312.png|frameless|600x600px]]

In this example, a route has been generated made up of 6 points, of which the first and last are respectively the departure airport and the arrival airport.

The route can be saved in a file which, in the example, has the name with a name ''LOWI-LIME.xml''

The file is saved in the ''Export'' directory of the FGFS HOME directory.

Being an XML file it is possible to open it through any text editor, and possibly also modify it, an operation, by the way, quite simple.

Here's what the xml file used for our example looks like:

[[File:Screenshot 20210523 211351.png|frameless|929x929px]]

The file can be as long as you like, however at the end it defines a path like this:

[[File:Screenshot 20210523 211204.png|frameless|600x600px]]

Now that it has been clarified what a route is and how it is saved, let's see how it can be exploited to cover the photoscenary only for the parts near the route.

'''<code>julia -t 10 photoscenary.jl --route LOWI-LIME.xml -s 2 -r 10 --over 1 -d 0</code>'''

In this example, the saved route is taken over by the program that searches for it. This little magic is used to simplify the program execution command as it is assumed that the file is of XML type and contains specific tags. If these tags are not present, the file will be considered invalid. If, on the other hand, if the file is validated, then it becomes the basis for extracting the path.

Once the file is validated, the program is executed, but first the project showing the single execution steps is shown.

The step is indicated with its step number and a decimal representing the sub-step. Therefore a step that has zero decimal indicates that that step has been inserted in the route manager, while the others are steps built by the algorithm to give continuity to the coverage of the tiles.

[[File:Screenshot 20210524 004027.png|frameless|800x800px]]

It is noted that at the end of the project (part in red in the screen shown here) the download phase begins for each single step, which, in this example, are 21.

Obviously the execution of the program can take a relatively long time, but certainly much less if that area had been covered with a single large set of tiles.

'''Note:''' ''that instead of entering the file name together with the path, only the file name can be entered, for example LIME-LIMJ.gpx somewhere, as long as it is inside the homepage or a subfolder. The program has an automatic search function which will find the file and use it as a route.''

==== Skyvector format ====
Since version 0.3.9 the automatic conversion of files produced with [https://skyvector.com/ Skyvector] has been defined. The file in .gpx format is automatically converted to produce the equivalent route to the file produced by the FGFS route manager when supplied via the <code>--route</code> parameter.

Skyvector is a very comprehensive route generator that is often used to plan routes in civil aviation. The use of this tool allows you to create route files in gpx format that can be read by the FGFS route manager and by this program. The conversion is transparent, that is, it is the program that parses the XML and determines its real format.

===Let's go via the geographic coordinates by -o -a <code>'''--latll --lonll --latur --lonur option'''</code>===
The coordinates are made explicit from the first line of the image:

central point ''lat: 21.317454 lon: -157.91603'' radius: ''5.0''

Not only that, but the second line reminds us in which area we are operating, that is an ideal rectangle with coordinates defined as follows:

Lower left corner

''latLL: 21,200 lonLL: -158,100''

Upper right corner

''latUR: 21.500 lonUR: -157.800''

But we could have had the same result with the following parameters that explicitly define the center point:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 3 -a 21.317454 -o ''-''157.91603'''</code>

Or with the parameters that define the lower left corner and the upper right corner

<code>'''julia -t 10 photoscenary.jl -s 3 --latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.8'''</code>

Entering the position values explicitly is a very convenient way when you do not know the acronym or name of an airport or want to select a particular area via google maps for example.

{{tip|Google maps allows you to give the coordinates in the degrees and fractions of degrees format, used by this program and FlightGear, by simply clicking the right mouse button on the map. Alternatively use the FlightGear [https://scenery.flightgear.org/static/map/index.html scene models map], which has coordinates in decimal format and tile information.}}

===The sea can be a problem --attemps option===
Now let's enlarge the radius area with <code>'''-r 20'''</code> (20 NM) with lower resolution tiles, we use in this example <code>'''-s 2'''</code> (2048 pixels long side)

<code>'''julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl --attemps 0'''</code>

At this point we look at the output which points out a few things

[[File:Test julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl top.png|frameless|800x800px]]

Meanwhile, let's see the effect of the <code>'''--over 0'''</code> parameter which prevents smaller images from overwriting images already present, but let's also observe another fact:

''The '''err''': column no longer reports the value 0 but numerical values that go up 7..10 and then beyond. This means that some tiles have not been uploaded, not only that, but there is also a very high reduction in the download speed that reaches, barely 0.16 MB/sec.''

The reason for this behavior is that around Honolulu there is the Pacific Ocean, or the sea, and the image server I am using does not show the sea beyond a certain distance from the coast. This means that the program tries to download a certain tile, but it returns an error, unfortunately not immediately, but only after a few seconds, the error starts a recovery procedure that performs the download attempt for two more times, if the third attempt fails, the system places the tiles, not downloaded, in a special list that can be retried in a subsequent cycle.

Here is what we will have at the end of the download batch:

[[File:Test julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl bottom.png|frameless|800x800px]]

Now let's see the incomplete file list that shows the tiles that have not been downloaded, the attempts parameter, in the ''Incomplete file list'', indicates the number of attempts made. By stating that the number of attempts is zero, it means that the program lists only the files that have resulted not downloaded and then exits the program. But if you enter a numeric value for the --attempt parameter instead, you can reprocess the tiles that have not been downloaded, but it is possible to change the number of attempts using the parameter:

<code>'''--attempts n'''</code> (''default is '''2''''')

Where <code>'''n'''</code> is any integer. Do not increase this value too much, and only do it if the internet connection line is unstable or if the image server often drops the connection.

Attempts to reconnect are quite slow, especially if the images are small, so it is better not to overdo it to avoid unnecessarily lengthening the download times.

===Try to recover the errors --attemps n===
Often the errors are due to the presence of marine areas that are covered by maps with lower resolution, so the only way to obtain an error recovery is to lower the resolution.

For this an algorithm has been inserted that in the first recovery step uses a width of '''1024''', width which is reduced to '''512,256,128''' etc ... for the following steps whose max number is defined by the value <code>'''--attempts n'''</code>.

Let's try this download, always with the airport of Honolulu adding the possibility of making 3 attempts:

'''<code>julia -t 10 photoscenary.jl -r 10 -s 2 -i Honolulu --attemps 3</code>'''

[[File:Julia -t 10 photoscenary.jl -r 10 -s 2 -i Honolulu --attemps 3.png|frameless|800x800px]]

At the end of the execution it is observed that 6 tiles have been inserted in the incomplete list, therefore it is possible, if the value of <code>'''--attemps'''</code> is greater than 0 (''by default I remember that it is '''2'''''), to obtain a re-execution only for the tiles in error with a resolution request starting from 1024 pixels down.

With the default value '''<code>--attemps 2</code>''' it is hereby possible to arrive at tiles of 512 pixels which always seem to be released by the server, with --attempts 3 it is also possible to try tiles of 256 pixels the server does not yet release 512 pixels.

The end result is complete coverage of the entire area. In two resolution groups, that of 2028 pixels proposed with '''<code>--s 2</code>''' and that of 1024 pixels used by the recovery function.

==Other options==
The program allows the use of other options that may be useful in certain circumstances, below I give a list with the relative possibilities of use.

===--map '''''n'''''===
You can change the standard image server. Each image server is identified with a unique id which currently selects the following addresses
{| class="wikitable"
|+List of servers currently active and inserted in the params.xml file
!Id
!Name
!Comment
! Address of the organization
|-
|'''1'''
|ESRI GIS
|Default, this servers is for all over the world
|[https://www.esri.com/en-us/about/about-esri/overview https://www.esri.com]
|-
|'''2'''
|USGS
|United States only. Public domain license, only US
|https://basemap.nationalmap.gov
|-
|'''3'''
|PNOA
| PNOA only Spain
|https://www.ign.es
|-
|'''4'''
|Geoportal
|geoportal.gov.pl only Poland
|https://www.geoportal.gov.pl
|}
[[File:Screenshot_20210524_205813.png|alt=|frameless|800x800px]]

This option allows you to select a specific server different from the standard one (Id = 1). All servers are inserted into the ''params.xml'' file in the following form:

Additional servers can be added simply by adding a new <server> ... </server> entry within the general <servers> ... </servers> entry. The Id must be unique, as it is the selector and can take any value. If someone adds their own server they can do it, but I recommend starting from a higher Id, for example 100, so as not to interfere with the Ids that could be added in the future.

''An important recommendation '''is to replace''', in URLs, any "'''&'''" character with "'''|'''" (Pipe or vertical bar)''

For example the URL:

'''<code><url-command>SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&LAYERS=OI ...</code>'''

It should be written in the form:

'''<code><url-command>SERVICE=WMS|VERSION=1.1.1|REQUEST=GetMap|LAYERS=OI ...</code>'''

This is the characteristic output that occurs during program execution and shows the image server in use

[[File:Screenshot 20210524 205939.png|frameless|800x800px]]

The selected server highlighted by the red line and shows the main data that allow it to be identified.

Be very careful to use the right server for a certain area, the program does not know if the selected server is valid or not for a certain area, so a wrong server could delete the previously inserted image files.

If you are unsure, check the server site or do a test limited to a certain area. The servers, when they are out of the area, do not give errors, but they release a completely white image, so always be very careful.

===--path or -p ===
The program normally downloads image files in DDS or PNG format directly to the directory:

'''<code>''<home>''/fgfs-scenery/photoscenery/Orthophotos</code>'''

However, sometimes a user wants to use a different destination, perhaps even a different mass storage unit, such as a NAS or a disk connected via USB, in these cases this option becomes very convenient.

There are two ways to define a path:

'''Path relative to the home directory ''('''''<nowiki/>''in the example the user is /home/abassign''')'''''<nowiki/>''':'''

'''<code>julia photoscenary.jl -i pantelleria -r 20 -s 3 --attemps 2 -p scenary-dir</code>'''

The system will respond:

The images path is: '''/home/abassign/scenary-dir/Orthophotos'''

'''Absolute path:'''

'''<code>julia photoscenary.jl -i pantelleria -r 20 -s 3 --attemps 2 -p /home/abassign/scenary-dir</code>'''

The path, in the case of using Windows, can be written in the Windows notation, for example:

''c:\users\abassign\scenary-dir''

or in Linux:

/home/abassign/scenary-dir

==== Automatic path if the program is connected to FGFS ====
Since version 0.3.8 a method has been introduced that extracts the path directly from the FGFS program if it is connected (use the '''--connect''' param for the connection). The method is therefore implicit if the program is connected and the path is not defined, the path used will be the one described in the property tree of FGFS ''/sim/fg-scenery''. Obviously, if in the command line there is the --path parameter, the path reported by this has a higher priority.

=== --save ===
The program '''always saves''' the images (''from version 0.3.8'') to a directory that can be implicit or explicitly defined with the '''--save "a path"''' parameter.

There are therefore two cases:

# If the '''--save''' parameter has a valid path, the program will save the images to be deleted on that path.
# If the save parameter is not present, the path is determined automatically by reading the path of insertion of the downloaded files by adding the sub-name '''''<path>-saved''''' to the path so as not to allow FGFS to use it as an operational directory.

If you do not want to save the replaced images, you must explicitly enter the parameter '''--nosave''' as explained in the next paragraph.

The path is always absolute, as it must be possible to manage external drives in which you want to insert the files to be saved.

With this technique it is possible to use an external disk, perhaps of a mechanical type of 1-4 TB, to save the files that have been downloaded by the program, all divided by size in pixels, as in this example:

'''<code>--save /media/abassign/save_2018/Salvataggi</code>'''

You will get a configuration similar to this:

[[File:Photoscenary julia save option example 01.png|frameless|740x740px]]

As you can see, the images are grouped by size in pixels (s 0 <-> 512 ... s 4 <-> 8196 ... etc) and therefore the program, depending on the size of the image to be inserted, can choose the most appropriate image.

It is interesting to try this configuration with -s 3 (4096 pix) which will load all the images from 4096 into the scenario directory:

<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 3 -r 20</code>

If you later want to have smaller images, for example le s 2 (2048 pix) or le s 1 from 1024 px just type this command:

<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 1 -r 20</code>

The '''--over 2''' option is used to allow the replacement of larger images with smaller ones, as explained in the appropriate paragraph.

The reorganization time of the images is very fast and is linked to the moving time of the images present in the system.

Note that if the 4096 pix images were not saved yet, before replacing with the smaller images, they will be saved in the path indicated by --save.

==== Summing up ====
With the --save option you can save the images that will be replaced when loading new images with different resolution. With this technique it is possible to save large areas of images on an external disk and finally, with this technique it is possible to change the resolution of the images without ever losing the downloaded images.

=== --nosave ===
If we want to inhibit the autosave mode, just enter the '''--nosave''' parameter in the command line. With this parameter, saving of images that are deleted from the path is blocked.

=== --png ===
It is a switch that allows you to download images in PNG format without switching to DDS images. This feature makes the downloaded images much larger (4 times) and easily viewable or editable by an image editing program such as GIMP or Imagemagick.

If you subsequently start the program without the --png option, the program will try, before downloading the images from some external server, to check if the PNG images present are compatible with the DDS to be generated, if they are you will have the rapid conversion live PNG images in DDS.

If the --save option has been activated, the PNG images will not be lost, but saved in the chosen path.

=== --tile===
The world of Flightgear is represented with a tessellation of rectangles according to a rule defined at this link:

https://wiki.flightgear.org/Tile_Index_Scheme

The tile defines the minimum loadable area for a photo scenery, its size varies with latitude. Here is an example of how the tiles are distributed on the globe taken from a FGUK movie:{{#ev:youtube|YxWV4wk_dHw}}All the images that make up the photoscenery have a unique numerical name that is calculated through a special algorithm according to the latitude and longitude of the tile. This number is defined as the tile identifier.

You can view the tile number in the FlightGear [https://scenery.flightgear.org/static/map/index.html scene models map] (lower left corner).

For example if you run the command:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 1 --tile 3105266'''</code>

You point to a tile that belongs to the LIME airport area and is approximately equivalent to this command:

'''<code>julia -t 10 photoscenary.jl -r 5 -s 1 -l lime</code>'''

In this way it is possible to select any area without having to enter particular coordinates, but only through this number.

===--sexagesimal or -x===
The angular parameters '''--lon --lat --lonll --latll --lonur --latur''' are normally expressed as hexadecimal. But it often happens that you have the coordinates in ''sexagesimal'' degrees. If the option is inserted, the system converts the decimal part from ''sexagesimal'' to ''centesimal''. For example, if you enter the value of '''52.21''' ''sexagesimal'' degrees, the program will convert them to '''52° 21' N''' which will then be converted to '''52.35''' degree.

'''Note''': ''It is not necessary to use the seconds as the tolerance of the tiles is 1/8 of a degree equal to about 7 minutes.''

For example is possible to write:

'''<code>julia -t 10 photoscenary.jl -r 10 -x -a 52.21 -o 13.30</code>'''

which is equivalent to writing

'''<code>julia -t 10 photoscenary.jl -r 10 -x -a 52.35 -o 13.50</code>'''

If the ''sexagesimal'' degrees are south or east, a minus sign must be entered, the field does not recognize the symbols N, S, E, W typically used in this type of notation.

===--proxy===
Which allows you to connect with a proxy server, the parameter is used, for example, as follows:

<code>julia -t 8 photoscenary.jl -s 5 -i "lowi" --over 1 -r 10 '''--proxy "<nowiki>http://192.168.0.9:8118</nowiki>"'''</code>

Where "''<nowiki>http://192.168.0.9:8118</nowiki>''" is the connection string to the proxy server.

===--debug or -d===
Currently the program defines two levels of debugging:

* level 1 <code>'''--debug 1'''</code> adds a series of messages that are a function of the progress of the program, this can be useful when you suspect that the program is not downloading anything or that the network is really slow. The problem is that this option does not display the progress log well and therefore is only useful in special cases.

*level 2 <code>'''--debug 2'''</code> is also used to display any execution errors. If the system is properly configured they should be rare, but in some cases it is useful to be able to see them.

=== --version===
It shows the program version and checks all the modules that need to be loaded:

<code>'''julia -t 10 photoscenary.jl --version'''</code>

[[File:Photoscenary-version.png|frameless|600x600px]]

=== --help or -h===
If you type the option -h or --help you get the complete list of options that can be recognized by the program, this list is obtained even if the option we enter or the value is not recognized, this is an example:
<nowiki>
$ julia photoscenary.jl --help
The actiual Julia is 1.9.4 The current version is correct in order to obtain the best performances

Photoscenary.jl ver: 0.4.00 date: 20230523 System prerequisite test

The Photoscenary.jl program has started, it can be stopped with CTRL-C

Photoscenery generator by Julia compilator,
Program for uploading Orthophotos files

Version: ImageMagick 6.9.12-98 Q16 x86_64 18038 https://legacy.imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC Modules OpenMP(4.5)
Delegates (built-in): bzlib djvu fftw fontconfig freetype heic jbig jng jp2 jpeg lcms lqr ltdl lzma openexr pangocairo png raw tiff webp wmf x xml zlib

ImageMagic is operative!
usage: <PROGRAM> [-g ARGS] [--map MAP] [--latll LATLL] [--lonll LONLL]
[--latur LATUR] [--lonur LONUR] [-a LAT] [-o LON]
[-x] [--png] [-i ICAO] [--route ROUTE] [-t TILE]
[-r RADIUS] [-s SIZE] [--sdwn SDWN] [--over OVER]
[--search SEARCH] [-p PATH] [--save SAVE] [--nosave]
[--connect CONNECT] [--proxy PROXY]
[--attemps ATTEMPS] [-d DEBUG] [--version] [-h]

optional arguments:
-g, --args ARGS The arguments files in txt format
--map MAP The map server id (type: Int64, default: 1)
--latll LATLL Lower left area lat (type: Float64, default:
0.0)
--lonll LONLL Lower left area lon (type: Float64, default:
0.0)
--latur LATUR Upper right area lat (type: Float64, default:
0.0)
--lonur LONUR Upper right area lon (type: Float64, default:
0.0)
-a, --lat LAT Latitude in deg of central point (type:
Float64)
-o, --lon LON Longitude in deg of central point (type:
Float64)
-x, --sexagesimal Set the sexagesimal unit degree.minutes
--png Set the only png format files
-i, --icao ICAO ICAO airport code for extract LAT and LON
--route ROUTE Route XML for extract route LAT and LON
-t, --tile TILE Tile index es coordinate reference (type:
Int64)
-r, --radius RADIUS Distance Radius around the center point (nm)
(type: Float64, default: 0.0)
-s, --size SIZE Max size of image 0->512 1->1024 2->2048
3->4096 4->8192 5->16384 6->32768 (type: Int64,
default: 2)
--sdwn SDWN Down size with distance (type: Int64, default:
0)
--over OVER Overwrite the tiles: |1|only if bigger
resolution |2|for all (type: Int64, default: 0)
--search SEARCH Search the DDS or PNG files in the specific
path
-p, --path PATH Path to store the dds images
--save SAVE Save the remove files in the specific path
--nosave Not save the DDS/PNG files
--connect CONNECT IP and port FGFS program, default value and
format: "127.0.0.1:5000"
--proxy PROXY Proxy string ipv4:port for example:
"192.168.0.1:8080"
--attemps ATTEMPS Number of download attempts (type: Int64,
default: 3)
-d, --debug DEBUG Debug level (type: Int64, default: 0)
--version Program version
-h, --help show this help message and exit

</nowiki>

== Management coverage of tiles on the territory ==
From version 0.2.8 a more articulated method of managing the loading and distribution of the tiles has been added.

=== Unloading of tiles on the territory assigned with a spiral rule ===
An algorithm performs the sequence of downloading the tiles as a function of the distance from the center. The download starts from the tiles closest to the center up to the last tiles downloaded which will be the ones farthest from the center.

In this motion it is possible to start the download procedure in parallel with the execution of the Flightgear program.

If you leave the airport where the plane is initially located and use the same airport as the center point (--icao lime for example) during take-off we will already have the tiles of the take-off area and therefore the scenario will appear well covered with orthographic images. During the climb of the plane it will therefore be probable that the following images will always give the pilot the illusion that the territory is well covered with images, even if we are only one part of the work. It will be enough for the pilot, from time to time, to update the scenario with the appropriate Flightgear menu.

=== Database of all orthographic images uploaded in .dds format. ===
This database is loaded at the beginning of the download session and contains all the images present in the home directory of the user who launched the program.

Before downloading the image from the designated website, the program checks in the database if the requested image is already present in the database, if the image is found in any directory of the home, it is copied to the current path. In this way it is possible to avoid carrying out a download job when the image is already present. Obviously the image must have and the pixel size requirements compatible with those required.

With this technique it is possible to distribute the images also on external supports and then make them converge on a working directory, usually with faster access (for example the system SSD). The only constraint is that the external media has a link that links it to a local folder.

With this technique it is also possible to exploit virtual folders that rely on other repositories, for example those shared with P2P techniques.

This example shows a mixed image download with database support. Images ('''copied''') are images copied from other directories on your system, ('''inserted''') are images inserted after a download from the image distribution web server. The images ('''skip''') are those already present in the folder of the images we are creating.

[[File:Screenshot 20210606 212142.png|frameless|800x800px]]

== Saving arguments in a text file ==
[[File:Julia Photoscenery Generator - args file.png|thumb|400x400px|Example of the contents in the '''args.txt''' file]]
Often the number and length of the arguments can become difficult to manage and therefore it is convenient to be able to save them on a file. For this reason, the '''--args''' (or '''-g''') parameter was introduced followed by a filename to be used as an argument container.

Let's take an example to better understand how this parameter works:

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

The arguments associated with the launch of the program are: <code>-i lowi -s 4 -r 20</code>

If we add the '''--args test.txt''' parameter:

<code>julia photoscenary.jl -i lowi -s 4 -r 20 --args test.txt</code>

In the directory where we ran the program we will find a new file called test.txt which contains the list of the parameters just entered.

It is now possible to recall the parameters entered using the command:

<code>julia photoscenary.jl test.txt</code>

The test.txt file, first created, can be edited with a simple text file editor and then modified according to our needs.

=== Arguments implicit saving ===
Launching the program with parameters, but without the '''--args''' option, still generates an arguments file called '''args.txt'''

This file can be recalled for the next program run, simply by running the program with no arguments.

For example:

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

The args.txt file is generated and the program, if run without parameters, will search the args.txt file and load it again using the previous parameters.

<code>julia photoscenary.jl</code>

The program runs exactly as in the previous execution.

== Recipes to be able to try the program and live satisfied ==
There are quite typical configurations that can give a lot of satisfaction to those who want a photorealistic vision, here I give some examples that can be used by anyone.

==== The simplest ====
<code>julia photoscenary.jl</code>

Will rerun with the last commands. The last commands are read from the file "args.txt".

At the first run, this will establish a telnet session where photoscenery is downloaded on demand from your flightgear instance;
see [[Julia_photoscenery_generator#Dynamically_download_orthographic_images_by_--connect]].

==== The scenario of the airport closest to you ====
<code>julia photoscenary.jl -i lowi</code>

''If we live near Innsbruck LOWI is the closest airport.''

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

'''''-i''' followed by the airport abbreviation ICAO, allows you to download that area for a radius of 20 nm ('''-r 20''') and resolution 8K pix ('''-s 4''')''

==== A flight plan has been generated with Skyvector <nowiki>https://skyvector.com/</nowiki> ====
<code>julia -t 6 photoscenary.jl -s 4 -r 20 --sdwn 1 --over 1 --route "LIMJ.gpx" --path "/media/abassign/test/fgfs-scenery/photoscenery"</code>

''The area is processed along a route defined with '''[https://skyvector.com/ Skyvector]''' (but the same methodology also applies to the one defined with the FGFS route planner). The program parses the xml file inserted as a parameter of '''--route''' and determines the format.''

==== The scenario is shown along the route ====
<code>julia -t 10 photoscenary.jl --connect "127.0.0.1:5000" -r 20 -s 3</code>

'''''-t 10''' tells the compiler that it can use up to 10 CPUs, this speeds up the download speed by 2-5 times. '''--connect''' allows you to connect to the Flightgear program (obviously if remote control has been activated (with port 5000) with the launch option of FGFS --telnet = 5000. The parameter '''-s 3''' means that the images will be 4096 pix, a good resolution for flights above 3000 ft.''

==== '''The images are saved for later reuse''' ====
<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 3 -r 20</code>

'''--save''' shows the possibility to save the images also in an external drive, in this way it is possible to create collections of images even in the order of TB avoiding using the system disk space.

'''--over 2''' It allows the replacement of images already present in the path directory, even if of higher resolution.

'''The images are saved for later reuse and the operational image directory is defined by the path option.'''

<code>julia -t 10 photoscenary.jl --over 1 --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 3 -r 20</code>

==== Generation of tiles along the route with maximum efficiency and quality ====
If you want to have a high quality scenario along the route, but at the same time light enough to allow the generation of images in good synchronization with the flight, you must enter the option '''--sdwn''' which, [[Julia photoscenery generator#The --sdwn parameter|as explained before]], allows you to automatically reduce the size of the tiles with the distance, in this way if the tile is distant a small tile is downloaded, if instead the tile is close, the downloaded tile is larger , at most the dimensions are those declared with the --s option. In this way it is possible to fly with a fairly synchronized scenario.

<code>julia -t 6 photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 4 -r 20 --over 1 --sdwn 1</code>

In case you want to get a faster loading of the images that are loaded along the route, remember that the program can overwrite the previous higher resolution images with lower resolution images '''without losing''' the images already downloaded, as they will be inserted in a area outside the scenario (for example a different disk) that can be reached with the path defined with the [[Julia photoscenery generator#--save|--save]] parameter.

This option means that instead of overwriting the images, the program first saves the files, then downloads the images from some external server and then overwrites them. With this technique the overall loading of the images (tiles) is faster as it is useless to download large images of 4-8-16 K pixels placed in distant areas from the pilot's point of view.

Therefore, to minimize the images it is necessary to communicate to the program that it will be able to overwrite the images with the option: [[Julia photoscenery generator#The --over parameter|--over 2]] But since the '''--save''' option is inserted, the program will not delete the previous images, but will insert them in the designated saving areas.

At this point a good command can be this:

<code>julia -t 6 photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" '''--save''' "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 4 -r 20 '''--over 2''' '''--sdwn 1'''</code>

''However, it must always be remembered that currently FGFS does not reload the images of the scenario automatically, but you must click on the debug menu under reload scenario.''

It is possible to avoid entering the --path and --save commands if you adopt the automatic path search method that is activated with --connect active. This makes the command simpler, but obviously you lose the ability to allocate unused images to a certain area on an explicit directory, this is an example:

<code>julia -t 6 photoscenary.jl --connect "127.0.0.1:5000" -s 4 -r 20 '''--over 2''' '''--sdwn 1'''</code>

=== Example of loading multiple scenarios ===
It is possible to use two sessions of photoscenary.jl at the same time to have an updated low resolution scenario (''obviously this method only makes sense if the route follows a path in which a tiles load has never been performed''). The first session will have a low resolution '''-s 1''' or '''-s 2''' while the second resolution could be much higher, e.g. '''-s 4''' or '''-s 5'''

With this configuration it is very likely that the download speed of the orthophoto server you have selected is sufficient to show the images of the territory at low resolution (''remember that currently FGFS requires the manual scenario update if we want to see the scenario just written''), while the second program proceeds to download the images at a higher resolution which will then be visible only in a second flight, obviously on the same route (''it is very unlikely that from resolutions of '''-s 4''' onwards the images can be downloaded with the same speed with which you fly over the territory'').

In this example I have given '''4 cores''' to the high resolution scenario, and '''3 cores''' to the lower resolution scenario. The number of cores cannot exceed the maximum allowed by your CPU, therefore the program, if this number exceeds the available one, automatically reduces the number of cores.

The presence of the '''--over 1''' parameter is fundamental, which manages the insertion of images according to the resolution. However, remember that the low resolution images that will be replaced will not be deleted if you have entered the '''--save''' parameter with the relative save path.

==== High resolution scenario tasks -s 4 (8K) and -r 10 ====
<code>julia '''-t 4''' photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" '''-s 4 -r 10 --over 1'''</code>

==== Low resolution scenario tasks -s 2 (2K) and -r 20 ====
<code>julia '''-t 3''' photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" '''-s 2 -r 20 --over 1'''</code>

==Using the generated photo scenery in FlightGear==
1. Inform FG about additional directory with scenery tiles:
''--fg-scenery=/your/path/to/photoscenery/directory/''
either in command line or as extra options in launcher.

E.g. if you have a directory structure like ''C:\FlightGear\fg_customscenery\photoscenery\Orthophotos\e000n40\e007n46'' then use ''--fg-scenery=C:\FlightGear\fg_customscenery\photoscenery''

2. Check the option Menu > View > Rendering Options > Satellite Photoscenery.

== Use the maps generated by photoscenary.jl for professional applications ==
The photoscenary.jl application allows you to generate maps even only in .png format useful to assemble with gimp (or other painting graphics programs) as the generation of the images guarantees the correct connection. Obviously, reference is made to cylindrical coordinates that must eventually be deformed in case you want to work with a different cartographic model. Currently the program defines the possibility of operating with some image sources defined in the parameter file '''params.xml''' in the sub-section ''<servers> ... </servers>''. Those that offer the most permissive license conditions are produced by USGS (USA) which is an American federal enete and therefore does not bind which all maps with particular limitations of use, the same rules apply as the otographic images produced by NASA that are used in Flightgear for images of the Earth as seen from space.

If one wants to read the terms of use, he can refer to what is reported in [https://www.usgs.gov/faqs/are-usgs-topographic-maps-copyrighted this USGS link].

=== Download images for professional use or publications ===
This paragraph is based on the terms of use of the USGS server, so they may not apply to other servers reachable with this program. The server, as you can see by reading the USGS params.xml file, has '''id = 2'''. For use not related to flightgear it is normally useful to work with files in .png format as the .dds is used only for simulation or games. For technical applications a pair of coordinates is normally used which are: Upper right (UR) and Lower Left (LL) of the requested area. You can also find a set of images using polar coordinates and a radius in nautical miles.

Let's now give one examples:

<code>'''julia -t 6 photoscenary.jl -s 5 --latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.3 --map 2 <small>--png -p</small>''' ''<small>'''"'''</small>'''''<small>/some path/ortho"</small>'''</code>

The coordinates are defined in:

'''-s 5''' is the resolution of the images (s 5 -> 16384 pix for tile)

'''--latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.3'''

Coordinates in six hundredth degrees.

'''--map 2''' indicates that the images will be downloaded from the USGS server.

'''--png''' means that the images WILL NOT BE CONVERTED to .dds but will remain in .png!

'''-p "''<path>''"''' Defines the path where the images will be downloaded.

'''-x''' If the coordinates are expressed in sexagesimal degrees, just enter this additional parameter,

In this case the decimal part of the coordinate value is in prime, for example:

'''--latll 21.50 --latll 158.50'''

It is equivalent to writing:

'''-x --latll 21.30 --lonll 158.30'''

===Wiki articles===
*[[Photoscenery]]

===Forum topics===
*{{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021 - May 2021)
*{{forum link|t=38057|title=16k Photoscenery}} (September 2020 - Gen 2021)

[[Category:Scenery]]
[[Category:Scenery software]]
[[Category:Photoscenery]]

Julia photoscenery generator

2024-04-13T07:38:20Z

Hbeni: /* The simplest */

{{Infobox Software
|title = FGCom-mumble
|logo = G91R1B taking off from LOWI .jpg|128px
|developedby = Adriano Bassignana
|developmentstatus = Active
|type = Photoscenery generator
|latestrelease = (rolling releases)
|initialrelease = 18.04.2021
|writtenin = julia
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v2
|website = https://github.com/abassign/Photoscenary
}}
[[File:G91R1B taking off from LOWI .jpg|thumb|500px|Photoscenery created with the Julia photoscenery generator behind a [[FIAT G91R1B|G91R1B]] taking off from LOWI. In this example the resolution of the tiles is 32K (s 6).]]

Through the '''Julia photoscenery generator''' using ImageMagic and written in the Julia programming language you can create photoscenery tiles.

Once you have everything installed you will discover how easy it is to fill your disk with hundreds of GB made from thousands of images of our planet and then fly over vast territories and recognize our cities and villages.

The use of World Scenery by FlightGear together with the photoscenery as a background can make the scene very rich in details and pleasing to your eyes.
== Quick method for Windows users ==
===Steps===
* 1. [https://julialang.org/downloads/#official_binaries_for_manual_download Down-Inst Julia Programming Language].
* 2. [https://imagemagick.org/script/download.php#windows Down-Inst ImageMagick].
* 3. [https://github.com/abassign/Photoscenary/archive/refs/heads/main.zip Down-Inst photoscenary.jl.zip] Easy Manual installation. Unzip Fhotoscenary-main folder, place it where you preferred. Look inside for the file photoscenary.jl and make it executable by Julia, using Right click >> Properties >> Navigate to the bin folder Julia.exe and choose open with Julia Programming Language.
===Check===
* 4. Open FGlauncher >> Settings >> Additional settings. Add the property: --telnet=5000
* 5. Make sure you have terrasync activated. Automatic download terrain in FGlauncher.
* 6. In FlightGear v2020.3.18 check the following: Start the simulator (one flight) and access the menu: VIEW/RENDERING OPTIONS. In the right column, make sure you have the "SATELLITE PHOTOSCENERY" option activated and close the flight.
===Run & Check===
* 7. Run the program photoscenary.jl. It will run and check with Julia, will prompt telnet connection attempts at 127.0.0.1:5000.
* 8. Run FG. Fly and check visually that you are getting textures. Give it a time, you'll get better textures progressively during your flight.
* 9. Check in C:\Users\YOUR_USER_NAME\FlightGear\Downloads\TerraSync\Orthophotos. You should see folders of type "e000n00" containing ".dds" files.
* 10. Check that the Julia's window running photoscenary.jl is getting data (tiles).

In case of doubts, the next video at SUMU Montevideo area by Manuel Aceña is recommended as a reference.
=== Video ===
{{#ev:youtube|PbYAvxmAkIc}}

==Background==
The success that photoscenery is achieving among FlightGear users has prompted me to study a program for downloading and installing photoscenery via a simple command to run inside a terminal (if we are in Linux or Mac OS) or in a command prompt (if we are in Windows).

The program was developed in Julia which is a latest generation programming language developed by MIT. This language looks quite similar to Nasal and therefore the code is easily readable by those who already use the FlightGear Nasal language script, but it is extremely faster and full of features that make the creation of this program quick and easy enough to evolve. Obviously the only inconvenience is that Julia has to be installed on your system, but it is a very simple action and equivalent to the same need to install ImageMagick on your system, this latter program allows the conversion of images in DDS format.
[[File:Julia photoscenery generator - Towards Budapest on the Danube plain.jpg|thumb|500x500px|The photoscenary allows to have very realistic effects on rather complex territories, such as crops in the plains. The image shows the signs of the passage of old rivers, still visible as a difference in the color of the vegetation.]]

==Installing the programs==

=== FlightGear ===
Currently to utilise photoscenery the minimum FlightGear version is 2020.3.18

===Julia installation===
https://julialang.org/

Julia installation is straightforward, whether using precompiled binaries or compiling from source. Download and install Julia by following the instructions at https://julialang.org/downloads/.
{| class="wikitable"
!Windows
| colspan="3" |'''64-bit (installer), 64-bit (portable)'''
| colspan="3" |32-bit (installer), 32-bit (portable)
|-
!macOS
| colspan="3" |'''64-bit'''
| colspan="3" |
|-
!Generic Linux on x86
| colspan="3" |'''64-bit (GPG), 64-bit (musl) (GPG)'''
| colspan="3" | 32-bit (GPG)
|-
!Generic Linux on ARM
| colspan="3" |'''64-bit (AArch64) (GPG)'''
| colspan="3" |32-bit (ARMv7-a hard float) (GPG)
|-
!Generic Linux on PowerPC
| colspan="3" |64-bit (little endian) (GPG)
| colspan="3" |
|-
!Generic FreeBSD on x86
| colspan="3" | 64-bit (GPG)
|
|}
For Linux users there are no particular problems, each distribution has Julia among the installable programs. The only problem is the version that may be older than 1.6, in this case I recommend wasting a little more time and updating the installation to 1.6, you can follow [https://medium.com/coffee-in-a-klein-bottle/install-julia-1-5-on-ubuntu-bb8be4b2571d this handy guide] that explains how to do everything in a few minutes.

The version to use is convenient that it is from '''1.6''' onwards, 1.5.4 is present in the Ubuntu repositories until 2020.10 but it is better to update it to 1.6 even if this requires a little work, But with Ubuntu/Kubuntu version 2021.4 Julia is already at version 1.6.1 and so just use the command:

<code>'''sudo apt install julia'''</code>

Julia is a young language that is continuously updated and the difference between Julia 1.5 and 1.6 is really very big for the application startup speed. For the execution there are no particular differences if you use Julia 1.5.4 onwards.

The installation with windows is absolutely the easiest to do, just follow the installer to get a version of Julia 1.6.x All users who have done the installation have never complained of problems.

For '''Mac users''' it might be the slightly more complicated thing, but from the users texts made, I haven't had any issues encountered among Mac users.

For '''Windows users''' have not encountered any particular problems with the installation, which is always the most up-to-date.

{{caution
|The program was designed to work in Linux (any distribution), Windows 10 and Mac OS. This is very unlikely to work with CygWin as there have been reports of problems calling Imagemagick. Instead, it works with Windows Subsystem for Linux, which is basically a well-integrated emulator of Linux inside the Windows system. In this case, multithreading may not work well, so I recommend running the program with only one Julia thread via the command:<BR><i>julia -t 1 photoscenary.jl ...</i><BR>Or with the command:<BR><i>julia photoscenary.jl</i><BR>But this approach seems like an unnecessary complication to me as the program works perfectly in Windows 10.
| width =
| padding =
| margin = 2%
}}

===ImageMagick installation===
https://imagemagick.org/index.php

For download program this is the link: https://imagemagick.org/script/download.php

Normally the files that are released by satellite image servers are in PNG format, but the PNG files are absolutely unsuitable to be used as photoscenery files. The reason is that the graphics engine of FlightGear must still convert these files into DDS format which is more compressed than the PNG format (about 4 times). Conversion, for very large files, takes a lot of CPU time, slowing down the execution of FlightGear. Therefore for this program it has been chosen to release only the DDS format and therefore ImageMagick is the most suitable program for this operation.

ImageMagick allows you to convert files transparently to the user very quickly.

In Linux distributions, ImageMagick is often already present, to find out just type the command <code>'''convert --version'''</code> and see if something responds. In windows it must be downloaded with an installer that can be downloaded here: https://imagemagick.org/script/download.php#windows

The installation in Windows of ImageMagick could give problems if it has not been correctly carried out. Therefore, if the photoscenary.jl program returns an error due to the lack of ImageMagick (the program always checks at the start) it is convenient to remove ImageMagick through the Windows program management and install it again.

===The photoscenary.jl installation===
https://github.com/abassign/Photoscenary

The program is written in pure Julia code, there are no scripts that can complicate your life. However, some rules must be followed that simplify all the work.

First create a directory where to place the program and its support files. The directory can be placed wherever you want as the program will dynamically build its references. Once the directory (or folder for Mac users) is done, download the Zip file that GitHub generates obtained from this link: https://github.com/abassign/Photoscenary.git

[[File:Github for photoscenary.jl.png|alt=|800x800px]]

Click on code and it will download the zip file that you can open and insert the contents into the folder you created. In the folder you will find some auxiliary files, but now let's analyze the program files.

*<code>'''photoscenary.jl'''</code> It is the Julia program to run, you can open it and see it with a simple text editor, I think some of you who have programmed in Python or NASAL will have no difficulty understanding how it works. However the program is compiled every time you run it, it is this compilation, really efficient and fast, that allows you to obtain an excellent executive performance.
*<code>'''params.xml'''</code> It is an XML file that contains some parameters necessary for the correct execution of the program.
*<code>'''airports.csv'''</code> It is the file, extracted from the correspondent of FlightGear, which contains a list of airports, their coordinates and the extended name. This file is essential in order to use a location option for the area to be downloaded.

==Execution of the program ==

===Hello World!===
There is a minimal execution that allows you to check if everything we have done has worked correctly, this is a sort of ''Hello World'' of the program.

The most important thing is to go to the directory (folder) where you installed the program with a ''terminal'' or with a ''command prompt'' (if you are in Windows).

So the first thing to do is to be with the terminal inside this directory and run this command:

<code>'''julia photoscenary.jl'''</code>

An area of 2048 pixels (long side) tiles with a size of approximately 10x10 NM is generated, with the coordinates of the ''Orio al Serio Airport'' (LIME) in the center. Not having entered any other parameters, the processing time is relatively long as only one download per tile is performed.

[[File:Test julia photoscenary.jl.png|frameless|800x800px]]

We carefully observe this execution, the first line shows the name of the program, the version and the date of realization, then follows the indication that the prerequisite test will take place. If we are at the first execution we will see an endless series of compilations that can make us think that something has not gone well, but do not worry, it is simply the module management system that downloads the modules useful for the execution of the program and that are not present in the base system. In this way the Julia program updates the necessary components without having to prompt the user to do it for him.

In this particular case, which occurs only the first time or in a version change, the application communicates that it will terminate the execution and invites the user, once back to the command prompt, to run the same command again, also in this case there could be a lot of updating of the modules that have not been updated in the first cycle, do not worry, everything is going great. At the end of the update, finally, the execution of the code contained in the program takes place.

The image above summarizes what happened during the download of the tiles.

Very important to note the line:

'''ImageMagick is operational!'''

This line tells us that the system has done a test with ImageMagick installed on its system and has verified that it works correctly. If this does not work, since without ImageMagick the system cannot do anything, you have an exit with a program error (Error code 504).

====Description of the individual status lines of the processes performed====
We now summarize the content of the individual lines that indicate the modules downloaded and their status:

{| class="wikitable"
!Column!!Content
|-
!Time:
|Processing time for individual tiles
|-
!elab:
|Total processing time
|-
!
( ... {{!}} ... ) 
|The processing time for each tile followed by the estimated time.
These two values allow us to understand the efficiency of the work in progress.
|-
!Tiles:
|Number of tiles that have been processed by the program.
|-
! on
|Total number of tiles to be processed.
|-
!res
|The residual tiles to be processed.
|-
!Th:
|Number of threads used by the process.
|-
!path:
| The path and name of the processed file.
|-
!MB/s:
|Download speed in Mega Bytes on second.
|-
!MB dw:
|Amount of mega bytes downloaded overall.
|-
!( ... )
| Type of activity carried out
|}

=== Activate the Julia multi thread ===
Julia is a language created for applications on supercomputers, artificial intelligence, number-crusher, etc.

These are applications that require systems with a lot of CPUs and therefore the compiler has the ability to activate very sophisticated strategies to better manage resources.

The photoscenary.jl program performs many processes in parallel in order to optimize the download and conversion of images. The conversion from the original PNG format to the more efficient format for FlightGear DDS requires a rather heavy application (ImageMagick) which can only be run on single CPUs. For this it is very efficient to run the program on multiple CPUs, but it is necessary to use some care that I explain below.

==== Core <-> CPU what are they ? ====
Any PC has a processor with a certain number of ''physical'' ''core'' ranging from 2 (Intel i3) to values that can go up to 12 or more for more performing desktop processors.

For years, all processor cores have been able to handle two separate CPU, using a hardware trick. Therefore an i3 processor with two core will allow to manage up to 4 CPU (or separate processes) at the same time.

At this point it is important the role of the operating system that must manage the available CPU and assign them to the running programs.

So when you start Julia it is possible to reserve the number of CPU to the application will require than and this must be done at the beginning so that the compiler will configure the code properly.

This is achieved with the '''-t n''' command where n is a number equal to or less than the number of available CPU.

==== The Julia -t n option ====
If you run the program with the command:

'''<code>julia photoscenary.jl</code>'''

Only one CPU will be used and this can be a bottleneck when downloading files from the web server that distributes the images, since, especially if you have images composed of a single file (from the smallest ones up to 2048 pixels) the program uses only one process (for larger images the program uses many more download processes).

So let's say we have a machine with 6 core and therefore 12 CPU we can launch the program with this command:

<code>'''julia -t 10 photoscenary.jl'''</code>

If we are on a 4 CPU as i3 it is necessary to reduce the value to 4, but maybe 3 would also be good, so we can write the command like this:

<code>'''julia -t 3 photoscenary.jl'''</code>

==== Be careful though ====
''If the value of the maximum number of CPU is too high, the behavior of the operating system could be such as to reduce the advantage in execution or even slow down the program!''

This certainly happens when the value of the '''''-t''' numbe''r is higher than the number of CPUs and if the system is windows 10 or 8 you will have an incredible slowdown of the program! Therefore on a Windows machine it is not advisable to always enter a value less than or equal to the number of CPU of the processor in use (''number of cores multiplied by 2'').

For Linux and Mac systems the problem seems to be less evident and so you can try to increase the number beyond the theoretical maximum value.

=== Now let's try to delete all the files just inserted===
This test allows us to understand the use of a very useful parameter to manage the files we create with this application, for example if we want to delete the files, perhaps to have an area managed with the traditional FlightGear system, we can do it with the following command:

<code>'''julia -t 10 photoscenary.jl --over 9'''</code>

We will get this result (I show only the last lines to focus attention on the fact that the system declares to perform some removes)

[[File:Test julia photoscenary.jl --over 9.png|frameless|800x800px]]

===Now lets put the turbojet into the download program===
We now put the <code>'''-t 10'''</code> option on the Julia compiler start command. This option allows you to run multiple threads at the same time allowing you to speed up the download of files.

<code>'''julia -t 10 photoscenary.jl'''</code>

[[File:Test julia -t 10 photoscenary.jl.png|frameless|800x800px]]

In this image I show all the lines processed to show how the progression of the download speed increase. As you can see at first the speed seems low, but in reality the system has launched about ten threads that form a queue of requests to the image server. The format of the images, when nothing is declared, as in this example, is 2048 pixels on the long side, and the size of the DDS file (we are at an intermediate latitude between 62-22 degrees) is 1 MB.

The average speed is 1.7 MB/s (but can go even higher) and is determined by the actual workload on the server distributing the images.

This way we have more than tripled the download speed.

Obviously these values can change a lot, but they are on average better than those obtained with single downloads. Not only that, but multithreading also works with the ImageMagick program that performs the transformation of the PNG file into DDS, this transformation is not fast, but in this way it is parallelized, making this phase less expensive in terms of time.

This feature is even more interesting for larger format images.

===Increase the resolution of the images, radius and --over option===
Let's see these two new options that can be given to the program:

<code>'''-r 5'''</code> where n is the number of miles of radius, if <code>'''-r'''</code> (Radius) is equal to 5 it means that we are covering a square whose diagonal is 5 NM. Note that if -r is not defined the system considers the radius of 10 NM.

<code>'''-s 4'''</code> indicates the resolution of the images we want to obtain, if this option is not inserted the default value is 2 equal to an image, on the long side, of 2048 pixels.

<code>j'''ulia -t 10 photoscenary.jl -r 5 -s 4'''</code>

[[File:Test julia -t 10 photoscenary.jl -r 5 -s 4 (skip).png|frameless|800x800px]]

In fact the system has not done anything, the status message, at the bottom of each line, tells us (skip) which means that the program has seen that an image is already present and this image cannot be overwritten as it is an image valid (actually the program checks the image by loading and verifying it), if the image was not valid, it would delete it and replace it with a new one.

But it is still possible to override by inserting the <code>'''--over 1'''</code> option at this point this interesting fact happens:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 4 --over 1'''</code>

[[File:Test julia -t 10 photoscenary.jl -r 5 -s 4 --over 1.png|frameless|800x800px]]

This download is '''16 times slower''' as the precedent download (Without the <code>-s</code> option the image downloads as <code>-s 2</code> which corresponds to 2048 pixels long edge) <code>'''-s 4'''</code> option downloads images of '''8192''' pixels long side. In fact the system downloads 16 images with size of '''2048''' and composes them into a matrix '''4x4,''' at the end of the composition the images are first transformed into an temporary PNG image format which will be processed by ImageMagick and becomes an DDS format image that is compatible with FlightGear without any on-the-fly conversion (which is done for PNG images). Therefore this line shows us the downloading of the single images that make up the matrix in order to give an idea that something is happening.

[[File:Julia -t 10 photoscenary.jl -r 5 -s 4 --over 1-BW.png|alt=|frameless|799x799px]]

Note that the download speed of individual images has increased (in this case 2.98 MB/s) as the system has opened several dozen download threads (96 download tasks are open at the same time as their number is the product of 6 threads x 16 images) .

It is important to understand this aspect of the program which can easily bring the network into saturation. In this example 3 MB/s correspond to about 30-40 MBit/s which is about 70-80% of the bandwidth that the network allows me to have. For this, if the band used is high, in order to keep a good surfing speed on the network, it is sufficient to reduce the value of the threads in Julia from -t 10 to -t 4 or -t 5.<blockquote>'''Note''': ''Julia is a programming language that has an incredible variety of methods for exploiting all possible hardware solutions. What I exploit in this program is only a small part, Julia even allows you to distribute the processing on remote machines, perhaps placed on different networks, in order to distribute the workload through the use of a few instructions.''</blockquote>From a series of tests that I have done, 8K images are the most interesting for systems that have at least 16 GB of RAM, if the RAM is lower these images can lead to FlightGear in memory overflow and therefore its closure by the system operating.

==== The -s parameter ====
<code>'''-s'''</code> defines 7 possible resolutions for images:
{| class="wikitable"
!Parameter!!Side px!! Format!!Size MB!! Comment
!PC RAM GB
|-
!-s 0
|style="text-align: center;"|512
|style="text-align: center;"|DDS
|style="text-align: center;"|0.064
|
|style="text-align: center;"|2
|-
!-s 1
|style="text-align: center;"|1024
|style="text-align: center;"|DDS
|style="text-align: center;"|0.256
|
|style="text-align: center;"|2
|-
!'''-s 2'''
|style="text-align: center;"|2048
|style="text-align: center;"|DDS
|style="text-align: center;"|1
|
|style="text-align: center;"|4
|-
!-s 3
|style="text-align: center;"|4096
|style="text-align: center;"|DDS
|style="text-align: center;"|4
|2 x 2 matrix = 4 images with 2048 pixels side to download
|style="text-align: center;"|8
|-
!'''-s 4'''
|style="text-align: center;"|8192
|style="text-align: center;"|DDS
|style="text-align: center;"|16
|4 x 4 matrix = 16 images with 2048 pixels side to download
|style="text-align: center;"|16
|-
!-s 5
|style="text-align: center;"|16384
|style="text-align: center;"|DDS
|style="text-align: center;"|64
|8 x 8 matrix = 64 images with 2048 pixels side to download
|style="text-align: center;"|16
|-
!-s 6
|style="text-align: center;"|32768
|style="text-align: center;"|DDS
|style="text-align: center;"|256
|8 x 8 matrix = 64 images with 4096 pixels side to download
|style="text-align: center;"|16
|}
The PC RAM that I recommend for PCs that need to download images. So I was able to download, even with Windows 10, which is much heavier than Linux, 16384 px images with only 4 GB of RAM! In this case there is a huge increase in virtual memory (''Both Linux with kernel 5 and Windows 10 have a dynamic virtual memory that is quite efficient if the hard disk is of the SSD type'') in use which, due to the structure of the program and the particular compiler used, it does not seem to slow down performance.

==== The --sdwn parameter====
<code>'''--sdwn'''</code> It is a parameter that defines how to change the value of the resolution or the distance using a linear method. For example, if the coverage radius is 100 nm and -s 5 (16K pixels), if we set <code>'''--sdwn 2'''</code> we will have this resolution trend:
{| class="wikitable"
!Dist. (nm)
!0
!10
!20
! 30
!40
! 50
!60
!70
!80
!90
!100
|-
!Res. (0..6)
|5
|4
|4
|4
|3
|3
|2
|2
|2
|2
|2
|}
As can be seen from the table, the resolution in pixels of the images varies with the distance from the center (radius).

With this method it is possible to obtain very large coverage without occupying too much memory and greatly reducing download times. Certainly the quality of the farther images is lower, but the problem could be not very perceptible as normally an airplane when it takes off is low on the ground and therefore the pilot wishes to have a high resolution (images with many pixels), but then rises in altitude and the resolution of the terrain is acceptable although much lower. With this method it is possible to cover large areas of land in a very short time, shorter than the flight necessary to cross that territory.

====The --over parameter====
A second important fact is the <code>'''--over 1'''</code> parameter which tells the system it can overwrite, the <code>'''--over'''</code> option <code>'''1'''</code> indicates that overwriting can only occur if the new file is larger than the file it replaces.

With this technique it is possible to build limited areas with higher resolution, for example airport areas, or particularly beautiful areas that we want to enhance.

The <code>'''--over'''</code> option has the following recognized parameters:
{| class="wikitable"
!Parameter!!Overwriting/deletion
|-
!--over 0
|Default option that inhibits any overwriting of images.
|-
!--over 1
|Overwrite only if the image to be replaced is larger than the present one
if the previous image is not present, the image will be inserted anyway.
|-
!--over 2
|Always overwrites, for example if you want to reduce the size of the images by a certain area.
|-
!--over 9
|Deletes the images present in the defined area.
|}

===Let's go to Fiumicino (Rome in Italy) by -i option===
<code>'''julia -t 10 photoscenary.jl -s 4 -i fiumicino'''</code>

[[File:Screenshot 20210520 125012.png|alt=|frameless|799x799px]]

We are already familiar with these options

The absence of '''<code>-r</code>''' indicates that the image extraction radius is the default of 10 nm.

<code>'''-s 4'''</code> indicates a resolution of 8192 pixels long side

But this is new

<code>'''-i fiumicino'''</code>

It means that we are selecting an airport containing the word '''fiumicino''<nowiki/>'. The search takes place in a database, with an Open Data license, which reports over 60,000 airports that have ICAO code.

The database is distributed together with the ''photoscenary.jl'' program with the ''airports.csv'' file, which is easily editable, via a text editor. The ''airports.csv'' file is not actually the database used by the program, but only the data source which is automatically converted into the more practical ''airports.jdb'' file which is the database file used by the JuliaDB package.

If you want to edit ''airports.csv'', once the file is saved, you will notice that the next time you run the ''photoscenary.jl'' program it will take a few seconds until a new ''airports.jdb'' is generated.

The text inserted after the '''<code>-i</code>''' parameter can contain a single word or a sentence, but in this case it must be delimited by double quotes.

'''<code>-i "leonardo da vinci"</code>'''

Once the program has started, the system will respond by entering also with this output:

[[File:Screenshot 20210520 213622.png|frameless|600x600px]]

For example, if you enter as a name

'''<code>-i rome</code>'''

The program will respond with the first 30 airports that correspond to the presence of the word Rome in one of the three search fields, as shown in this figure.

[[File:Screenshot 20210520 215037-2.png|frameless|800x800px]]

In this case, just enter a unique selector, such as the ICAO ID, to obtain the searched airport, as in this example:

'''<code>-i LIRF</code>'''

Therefore, the search using the -i option can be extremely convenient, as it allows you to quickly have the coordinates of any airport present in the ICAO database.

The search word can also be partial as in this example:

'''<code>-i zuric</code>'''

[[File:Screenshot 20210520 220731.png|frameless|600x600px]]

Any accented letters are normalized to the unaccented Latin form, for example:

''Zürich Airport'' becomes ''Zurich Airport''

and therefore the search can be successful if you write:

'''<code>-i "zurich airport"</code>'''

=== Dynamically download orthographic images by --connect ===
It is very convenient to download the orthographic images of the territory actually flown over by the plane.

In this case, the system will use the aircraft's course as reference, interspersed with points of radius -r.

The program will then download only the images actually needed, thus minimizing the amount of data to download.

The parameter to activate this function is this:

<code>'''--connect "<IP address>:<port>"'''</code>

When the program finds this parameter, checks if the syntax of the address is correct and listens showing a line that has as, first character and an arrow that rotates 45 degrees every second, followed by the sentence that begins with the text:

<code>'''Try the frist connection to Flightgear with address: ...'''</code>

This delay can last for an indefinite time, until Flightgear is activated with, obviously, the Telnet connection port activated, as explained above.

When Flightgear is activated, the program realizes it and starts evaluating the geographic position of the aircraft and then, if necessary, downloading and positioning the DDS images in the photorealistic scenario.

If you close Flightgear again, the program will be put on hold again, a situation indicated by the message:

<code>'''Try connect to Flightgear with address: ...'''</code>

To exit the program it is necessary to type the key sequence: [CTRL] + [C]

Exiting the program will have no effect on the downloaded DDS files as the program operates through transactional methods.

==== A simple example ====
For example, you can run this command:

<code>julia -t 4 photoscenary.jl --connect "127.0.0.1:5000"</code>

In this case the program will download the images in a radius of 10 nm for the entire length of the route. Thus forming a corridor of images that can give the illusion of a much larger territorial coverage than reality.

The images, if the <code>-s n</code> parameter is not specified, will have the size of 2048 px, this is a good enough size for flights above 10,000 ft.

If the speed of the plane is not too high and the internet line is good, it may happen that the pilot can get a flight with complete coverage of the orthographic images, giving the illusion of having downloaded very large geographical areas and more a narrow corridor that follows the route followed by the plane ..

If, on the other hand, the speed of the plane is high, or the speed of downloading the images is not high, it may be necessary, from time to time, to activate the option to update the scenario using the command:

''[menu] -> [debug] -> [Reload Scenery]''

In this case the simulator will freeze for a few seconds and then a scenario will be observed with orthographic images of the territory overflown.

==== Preparation of Flightgear to allow you to communicate with the photoscenary.jl program ====
[[File:Julia photoscenery generator - launcher QT configuration - 20210618 232448.png|frameless|800x800px]]

First you need to run Flightgear with the option:

<code>'''--telnet=5000'''</code>

This command will activate the telnet server on Flightgear with port 5000 active. The port can be changed, but the important thing is that it is then the communication port entered in the <code>--connect</code> command.

In the example in Additional Settings we see that the first line is the telnet server activation command, server needed to communicate with the photoscenary.jl program.

In additional settings I have inserted two other options that may be useful:

The parameter ''--httpd = 5001'' which activates an HTTP server, visible through the browser, useful for displaying the route on a geographic map. The third option instead activates multithreading which, eg run PC with at least 2 cores, allows you to render the flight more fluid.

==== Performing dynamic loading of orthographic images during flight ====
First you need to start Flightgear (and with it the telnet server we configured previously), wait for its loading phase to finish. And then start the program:

<code>'''julia -t 4 photoscenary.jl --connect "127.0.0.1:5000"'''</code>

[[File:Julia photoscenery generator - execution connect param - 20210618.png|frameless|800x800px]]

Unlike the other methods of selecting the areas to be filled with images, this method can show an intermediate step called "System pending ..." which allows you to communicate to the pilot that the program is running smoothly, but has already downloaded all the images needed for the current flyover area and then waits to reach the next area from which it will start downloading images again.

==== However, the other options are also allowed ====
<code>julia -t 4 photoscenary.jl --connect "127.0.0.1:5000" -s 3 --over 1</code>

The <code>--connect</code> command does not prevent the use of other options, such as image resolution and enabling overwriting if the new image is of a higher resolution than the one already present.

===Follow a route generated with route manager by --route===
The FlightGear ''route manager'' program allows you to generate a route that passes through various points and/or airports, the route can be saved to a file that is placed in the Export folder of the FlightGear $FG Home directory.

[[File:Screenshot 20210523 211312.png|frameless|600x600px]]

In this example, a route has been generated made up of 6 points, of which the first and last are respectively the departure airport and the arrival airport.

The route can be saved in a file which, in the example, has the name with a name ''LOWI-LIME.xml''

The file is saved in the ''Export'' directory of the FGFS HOME directory.

Being an XML file it is possible to open it through any text editor, and possibly also modify it, an operation, by the way, quite simple.

Here's what the xml file used for our example looks like:

[[File:Screenshot 20210523 211351.png|frameless|929x929px]]

The file can be as long as you like, however at the end it defines a path like this:

[[File:Screenshot 20210523 211204.png|frameless|600x600px]]

Now that it has been clarified what a route is and how it is saved, let's see how it can be exploited to cover the photoscenary only for the parts near the route.

'''<code>julia -t 10 photoscenary.jl --route LOWI-LIME.xml -s 2 -r 10 --over 1 -d 0</code>'''

In this example, the saved route is taken over by the program that searches for it. This little magic is used to simplify the program execution command as it is assumed that the file is of XML type and contains specific tags. If these tags are not present, the file will be considered invalid. If, on the other hand, if the file is validated, then it becomes the basis for extracting the path.

Once the file is validated, the program is executed, but first the project showing the single execution steps is shown.

The step is indicated with its step number and a decimal representing the sub-step. Therefore a step that has zero decimal indicates that that step has been inserted in the route manager, while the others are steps built by the algorithm to give continuity to the coverage of the tiles.

[[File:Screenshot 20210524 004027.png|frameless|800x800px]]

It is noted that at the end of the project (part in red in the screen shown here) the download phase begins for each single step, which, in this example, are 21.

Obviously the execution of the program can take a relatively long time, but certainly much less if that area had been covered with a single large set of tiles.

'''Note:''' ''that instead of entering the file name together with the path, only the file name can be entered, for example LIME-LIMJ.gpx somewhere, as long as it is inside the homepage or a subfolder. The program has an automatic search function which will find the file and use it as a route.''

==== Skyvector format ====
Since version 0.3.9 the automatic conversion of files produced with [https://skyvector.com/ Skyvector] has been defined. The file in .gpx format is automatically converted to produce the equivalent route to the file produced by the FGFS route manager when supplied via the <code>--route</code> parameter.

Skyvector is a very comprehensive route generator that is often used to plan routes in civil aviation. The use of this tool allows you to create route files in gpx format that can be read by the FGFS route manager and by this program. The conversion is transparent, that is, it is the program that parses the XML and determines its real format.

===Let's go via the geographic coordinates by -o -a <code>'''--latll --lonll --latur --lonur option'''</code>===
The coordinates are made explicit from the first line of the image:

central point ''lat: 21.317454 lon: -157.91603'' radius: ''5.0''

Not only that, but the second line reminds us in which area we are operating, that is an ideal rectangle with coordinates defined as follows:

Lower left corner

''latLL: 21,200 lonLL: -158,100''

Upper right corner

''latUR: 21.500 lonUR: -157.800''

But we could have had the same result with the following parameters that explicitly define the center point:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 3 -a 21.317454 -o ''-''157.91603'''</code>

Or with the parameters that define the lower left corner and the upper right corner

<code>'''julia -t 10 photoscenary.jl -s 3 --latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.8'''</code>

Entering the position values explicitly is a very convenient way when you do not know the acronym or name of an airport or want to select a particular area via google maps for example.

{{tip|Google maps allows you to give the coordinates in the degrees and fractions of degrees format, used by this program and FlightGear, by simply clicking the right mouse button on the map. Alternatively use the FlightGear [https://scenery.flightgear.org/static/map/index.html scene models map], which has coordinates in decimal format and tile information.}}

===The sea can be a problem --attemps option===
Now let's enlarge the radius area with <code>'''-r 20'''</code> (20 NM) with lower resolution tiles, we use in this example <code>'''-s 2'''</code> (2048 pixels long side)

<code>'''julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl --attemps 0'''</code>

At this point we look at the output which points out a few things

[[File:Test julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl top.png|frameless|800x800px]]

Meanwhile, let's see the effect of the <code>'''--over 0'''</code> parameter which prevents smaller images from overwriting images already present, but let's also observe another fact:

''The '''err''': column no longer reports the value 0 but numerical values that go up 7..10 and then beyond. This means that some tiles have not been uploaded, not only that, but there is also a very high reduction in the download speed that reaches, barely 0.16 MB/sec.''

The reason for this behavior is that around Honolulu there is the Pacific Ocean, or the sea, and the image server I am using does not show the sea beyond a certain distance from the coast. This means that the program tries to download a certain tile, but it returns an error, unfortunately not immediately, but only after a few seconds, the error starts a recovery procedure that performs the download attempt for two more times, if the third attempt fails, the system places the tiles, not downloaded, in a special list that can be retried in a subsequent cycle.

Here is what we will have at the end of the download batch:

[[File:Test julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl bottom.png|frameless|800x800px]]

Now let's see the incomplete file list that shows the tiles that have not been downloaded, the attempts parameter, in the ''Incomplete file list'', indicates the number of attempts made. By stating that the number of attempts is zero, it means that the program lists only the files that have resulted not downloaded and then exits the program. But if you enter a numeric value for the --attempt parameter instead, you can reprocess the tiles that have not been downloaded, but it is possible to change the number of attempts using the parameter:

<code>'''--attempts n'''</code> (''default is '''2''''')

Where <code>'''n'''</code> is any integer. Do not increase this value too much, and only do it if the internet connection line is unstable or if the image server often drops the connection.

Attempts to reconnect are quite slow, especially if the images are small, so it is better not to overdo it to avoid unnecessarily lengthening the download times.

===Try to recover the errors --attemps n===
Often the errors are due to the presence of marine areas that are covered by maps with lower resolution, so the only way to obtain an error recovery is to lower the resolution.

For this an algorithm has been inserted that in the first recovery step uses a width of '''1024''', width which is reduced to '''512,256,128''' etc ... for the following steps whose max number is defined by the value <code>'''--attempts n'''</code>.

Let's try this download, always with the airport of Honolulu adding the possibility of making 3 attempts:

'''<code>julia -t 10 photoscenary.jl -r 10 -s 2 -i Honolulu --attemps 3</code>'''

[[File:Julia -t 10 photoscenary.jl -r 10 -s 2 -i Honolulu --attemps 3.png|frameless|800x800px]]

At the end of the execution it is observed that 6 tiles have been inserted in the incomplete list, therefore it is possible, if the value of <code>'''--attemps'''</code> is greater than 0 (''by default I remember that it is '''2'''''), to obtain a re-execution only for the tiles in error with a resolution request starting from 1024 pixels down.

With the default value '''<code>--attemps 2</code>''' it is hereby possible to arrive at tiles of 512 pixels which always seem to be released by the server, with --attempts 3 it is also possible to try tiles of 256 pixels the server does not yet release 512 pixels.

The end result is complete coverage of the entire area. In two resolution groups, that of 2028 pixels proposed with '''<code>--s 2</code>''' and that of 1024 pixels used by the recovery function.

==Other options==
The program allows the use of other options that may be useful in certain circumstances, below I give a list with the relative possibilities of use.

===--map '''''n'''''===
You can change the standard image server. Each image server is identified with a unique id which currently selects the following addresses
{| class="wikitable"
|+List of servers currently active and inserted in the params.xml file
!Id
!Name
!Comment
! Address of the organization
|-
|'''1'''
|ESRI GIS
|Default, this servers is for all over the world
|[https://www.esri.com/en-us/about/about-esri/overview https://www.esri.com]
|-
|'''2'''
|USGS
|United States only. Public domain license, only US
|https://basemap.nationalmap.gov
|-
|'''3'''
|PNOA
| PNOA only Spain
|https://www.ign.es
|-
|'''4'''
|Geoportal
|geoportal.gov.pl only Poland
|https://www.geoportal.gov.pl
|}
[[File:Screenshot_20210524_205813.png|alt=|frameless|800x800px]]

This option allows you to select a specific server different from the standard one (Id = 1). All servers are inserted into the ''params.xml'' file in the following form:

Additional servers can be added simply by adding a new <server> ... </server> entry within the general <servers> ... </servers> entry. The Id must be unique, as it is the selector and can take any value. If someone adds their own server they can do it, but I recommend starting from a higher Id, for example 100, so as not to interfere with the Ids that could be added in the future.

''An important recommendation '''is to replace''', in URLs, any "'''&'''" character with "'''|'''" (Pipe or vertical bar)''

For example the URL:

'''<code><url-command>SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&LAYERS=OI ...</code>'''

It should be written in the form:

'''<code><url-command>SERVICE=WMS|VERSION=1.1.1|REQUEST=GetMap|LAYERS=OI ...</code>'''

This is the characteristic output that occurs during program execution and shows the image server in use

[[File:Screenshot 20210524 205939.png|frameless|800x800px]]

The selected server highlighted by the red line and shows the main data that allow it to be identified.

Be very careful to use the right server for a certain area, the program does not know if the selected server is valid or not for a certain area, so a wrong server could delete the previously inserted image files.

If you are unsure, check the server site or do a test limited to a certain area. The servers, when they are out of the area, do not give errors, but they release a completely white image, so always be very careful.

===--path or -p ===
The program normally downloads image files in DDS or PNG format directly to the directory:

'''<code>''<home>''/fgfs-scenery/photoscenery/Orthophotos</code>'''

However, sometimes a user wants to use a different destination, perhaps even a different mass storage unit, such as a NAS or a disk connected via USB, in these cases this option becomes very convenient.

There are two ways to define a path:

'''Path relative to the home directory ''('''''<nowiki/>''in the example the user is /home/abassign''')'''''<nowiki/>''':'''

'''<code>julia photoscenary.jl -i pantelleria -r 20 -s 3 --attemps 2 -p scenary-dir</code>'''

The system will respond:

The images path is: '''/home/abassign/scenary-dir/Orthophotos'''

'''Absolute path:'''

'''<code>julia photoscenary.jl -i pantelleria -r 20 -s 3 --attemps 2 -p /home/abassign/scenary-dir</code>'''

The path, in the case of using Windows, can be written in the Windows notation, for example:

''c:\users\abassign\scenary-dir''

or in Linux:

/home/abassign/scenary-dir

==== Automatic path if the program is connected to FGFS ====
Since version 0.3.8 a method has been introduced that extracts the path directly from the FGFS program if it is connected (use the '''--connect''' param for the connection). The method is therefore implicit if the program is connected and the path is not defined, the path used will be the one described in the property tree of FGFS ''/sim/fg-scenery''. Obviously, if in the command line there is the --path parameter, the path reported by this has a higher priority.

=== --save ===
The program '''always saves''' the images (''from version 0.3.8'') to a directory that can be implicit or explicitly defined with the '''--save "a path"''' parameter.

There are therefore two cases:

# If the '''--save''' parameter has a valid path, the program will save the images to be deleted on that path.
# If the save parameter is not present, the path is determined automatically by reading the path of insertion of the downloaded files by adding the sub-name '''''<path>-saved''''' to the path so as not to allow FGFS to use it as an operational directory.

If you do not want to save the replaced images, you must explicitly enter the parameter '''--nosave''' as explained in the next paragraph.

The path is always absolute, as it must be possible to manage external drives in which you want to insert the files to be saved.

With this technique it is possible to use an external disk, perhaps of a mechanical type of 1-4 TB, to save the files that have been downloaded by the program, all divided by size in pixels, as in this example:

'''<code>--save /media/abassign/save_2018/Salvataggi</code>'''

You will get a configuration similar to this:

[[File:Photoscenary julia save option example 01.png|frameless|740x740px]]

As you can see, the images are grouped by size in pixels (s 0 <-> 512 ... s 4 <-> 8196 ... etc) and therefore the program, depending on the size of the image to be inserted, can choose the most appropriate image.

It is interesting to try this configuration with -s 3 (4096 pix) which will load all the images from 4096 into the scenario directory:

<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 3 -r 20</code>

If you later want to have smaller images, for example le s 2 (2048 pix) or le s 1 from 1024 px just type this command:

<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 1 -r 20</code>

The '''--over 2''' option is used to allow the replacement of larger images with smaller ones, as explained in the appropriate paragraph.

The reorganization time of the images is very fast and is linked to the moving time of the images present in the system.

Note that if the 4096 pix images were not saved yet, before replacing with the smaller images, they will be saved in the path indicated by --save.

==== Summing up ====
With the --save option you can save the images that will be replaced when loading new images with different resolution. With this technique it is possible to save large areas of images on an external disk and finally, with this technique it is possible to change the resolution of the images without ever losing the downloaded images.

=== --nosave ===
If we want to inhibit the autosave mode, just enter the '''--nosave''' parameter in the command line. With this parameter, saving of images that are deleted from the path is blocked.

=== --png ===
It is a switch that allows you to download images in PNG format without switching to DDS images. This feature makes the downloaded images much larger (4 times) and easily viewable or editable by an image editing program such as GIMP or Imagemagick.

If you subsequently start the program without the --png option, the program will try, before downloading the images from some external server, to check if the PNG images present are compatible with the DDS to be generated, if they are you will have the rapid conversion live PNG images in DDS.

If the --save option has been activated, the PNG images will not be lost, but saved in the chosen path.

=== --tile===
The world of Flightgear is represented with a tessellation of rectangles according to a rule defined at this link:

https://wiki.flightgear.org/Tile_Index_Scheme

The tile defines the minimum loadable area for a photo scenery, its size varies with latitude. Here is an example of how the tiles are distributed on the globe taken from a FGUK movie:{{#ev:youtube|YxWV4wk_dHw}}All the images that make up the photoscenery have a unique numerical name that is calculated through a special algorithm according to the latitude and longitude of the tile. This number is defined as the tile identifier.

You can view the tile number in the FlightGear [https://scenery.flightgear.org/static/map/index.html scene models map] (lower left corner).

For example if you run the command:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 1 --tile 3105266'''</code>

You point to a tile that belongs to the LIME airport area and is approximately equivalent to this command:

'''<code>julia -t 10 photoscenary.jl -r 5 -s 1 -l lime</code>'''

In this way it is possible to select any area without having to enter particular coordinates, but only through this number.

===--sexagesimal or -x===
The angular parameters '''--lon --lat --lonll --latll --lonur --latur''' are normally expressed as hexadecimal. But it often happens that you have the coordinates in ''sexagesimal'' degrees. If the option is inserted, the system converts the decimal part from ''sexagesimal'' to ''centesimal''. For example, if you enter the value of '''52.21''' ''sexagesimal'' degrees, the program will convert them to '''52° 21' N''' which will then be converted to '''52.35''' degree.

'''Note''': ''It is not necessary to use the seconds as the tolerance of the tiles is 1/8 of a degree equal to about 7 minutes.''

For example is possible to write:

'''<code>julia -t 10 photoscenary.jl -r 10 -x -a 52.21 -o 13.30</code>'''

which is equivalent to writing

'''<code>julia -t 10 photoscenary.jl -r 10 -x -a 52.35 -o 13.50</code>'''

If the ''sexagesimal'' degrees are south or east, a minus sign must be entered, the field does not recognize the symbols N, S, E, W typically used in this type of notation.

===--proxy===
Which allows you to connect with a proxy server, the parameter is used, for example, as follows:

<code>julia -t 8 photoscenary.jl -s 5 -i "lowi" --over 1 -r 10 '''--proxy "<nowiki>http://192.168.0.9:8118</nowiki>"'''</code>

Where "''<nowiki>http://192.168.0.9:8118</nowiki>''" is the connection string to the proxy server.

===--debug or -d===
Currently the program defines two levels of debugging:

* level 1 <code>'''--debug 1'''</code> adds a series of messages that are a function of the progress of the program, this can be useful when you suspect that the program is not downloading anything or that the network is really slow. The problem is that this option does not display the progress log well and therefore is only useful in special cases.

*level 2 <code>'''--debug 2'''</code> is also used to display any execution errors. If the system is properly configured they should be rare, but in some cases it is useful to be able to see them.

=== --version===
It shows the program version and checks all the modules that need to be loaded:

<code>'''julia -t 10 photoscenary.jl --version'''</code>

[[File:Photoscenary-version.png|frameless|600x600px]]

=== --help or -h===
If you type the option -h or --help you get the complete list of options that can be recognized by the program, this list is obtained even if the option we enter or the value is not recognized, this is an example:

<code><small>julia photoscenary.jl --help</small></code>

<code><small>The actiual Julia is 1.7.0-beta3.0 The current version is correct in order to obtain the best performances</small></code>

<code><small>Photoscenary.jl ver: 0.3.5 date: Testing 20210816 System prerequisite test</small></code>

<code><small>Photoscenery generator by Julia compilator,</small></code>

<code><small>Program for uploading Orthophotos files</small></code>

<code><small>Version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 <nowiki>https://imagemagick.org</nowiki></small></code>

<code><small>Copyright: (C) 1999-2021 ImageMagick Studio LLC</small></code>

<code><small>License: <nowiki>https://imagemagick.org/script/license.php</nowiki></small></code>

<code><small>Features: Cipher DPC Modules OpenMP(4.5) </small></code>

<code><small>Delegates (built-in): bzlib djvu fftw fontconfig freetype heic jbig jng jp2 jpeg lcms lqr ltdl lzma openexr pangocairo png tiff webp wmf x xml zlib</small></code>

<code><small>ImageMagic is operative!</small></code>

<code><small>usage: photoscenary.jl [--map MAP] [--latll LATLL] [--lonll LONLL]</small></code>

<code><small> [--latur LATUR] [--lonur LONUR] [-a LAT]</small></code>

<code><small> [-o LON] [-x] [--png] [-i ICAO] [--route ROUTE]</small></code>

<code><small> [-t TILE] [-r RADIUS] [-s SIZE] [--sdwn SDWN]</small></code>

<code><small> [--over OVER] [-p PATH] [--save SAVE]</small></code>

<code><small> [--connect CONNECT] [--proxy PROXY]</small></code>

<code><small> [--attemps ATTEMPS] [-d DEBUG] [--version] [-h]</small></code>

<code><small>optional arguments:</small></code>

<code><small>-g, --args ARGS The arguments files in txt format</small></code>

<code><small> --map MAP The map server id (type: Int64, default: 1)</small></code>

<code><small> --latll LATLL Lower left area lat (type: Float64, default: 0.0)</small></code>

<code><small> --lonll LONLL Lower left area lon (type: Float64, default: 0.0)</small></code>

<code><small> --latur LATUR Upper right area lat (type: Float64, default: 0.0)</small></code>

<code><small> --lonur LONUR Upper right area lon (type: Float64, default: 0.0)</small></code>

<code><small> -a, --lat LAT Latitude in deg of central point (type: Float64, default: 45.66)</small></code>

<code><small> -o, --lon LON Longitude in deg of central point (type: Float64, default: 9.7)</small></code>

<code><small> -x, --sexagesimal Set the sexagesimal unit degree.minutes</small></code>

<code><small> --png Set the only png format files</small></code>

<code><small> -i, --icao ICAO ICAO airport code for extract LAT and LON</small></code>

<code><small> --route ROUTE Route XML for extract route LAT and LON</small></code>

<code><small> -t, --tile TILE Tile index es coordinate reference (type: Int64)</small></code>

<code><small> -r, --radius RADIUS Distance Radius around the center point (nm) (type: Float64, default: 0.0)</small></code>

<code><small> -s, --size SIZE Max size of image 0->512 1->1024 2->2048 3->4096 4->8192 5->16384 6->32768 (type: Int64, default: 2)</small></code>

<code><small> --sdwn SDWN Down size with distance (type: Int64, default: 0)</small></code>

<code><small> --over OVER Overwrite the tiles: |1|only if bigger resolution |2|for all (type: Int64, default: 0)</small></code>

<code><small> -p, --path PATH Path to store the dds images (default: "fgfs-scenery/photoscenery")</small></code>

<code><small> --save SAVE Save the remove files in the specific path</small></code>

<code><small>--nosave Not save the DDS/PNG files</small></code>

<code><small> --connect CONNECT IP and port FGFS program, example format: "127.0.0.1:5000"</small></code>

<code><small> --proxy PROXY Proxy string ipv4:port for example: "192.168.0.1:8080"</small></code>

<code><small> --attemps ATTEMPS Number of download attempts (type: Int64, default: 3)</small></code>

<code><small> -d, --debug DEBUG Debug level (type: Int64, default: 0)</small></code>

<code><small> --version Program version</small></code>

<code><small> -h, --help show this help message and exit</small></code>

== Management coverage of tiles on the territory ==
From version 0.2.8 a more articulated method of managing the loading and distribution of the tiles has been added.

=== Unloading of tiles on the territory assigned with a spiral rule ===
An algorithm performs the sequence of downloading the tiles as a function of the distance from the center. The download starts from the tiles closest to the center up to the last tiles downloaded which will be the ones farthest from the center.

In this motion it is possible to start the download procedure in parallel with the execution of the Flightgear program.

If you leave the airport where the plane is initially located and use the same airport as the center point (--icao lime for example) during take-off we will already have the tiles of the take-off area and therefore the scenario will appear well covered with orthographic images. During the climb of the plane it will therefore be probable that the following images will always give the pilot the illusion that the territory is well covered with images, even if we are only one part of the work. It will be enough for the pilot, from time to time, to update the scenario with the appropriate Flightgear menu.

=== Database of all orthographic images uploaded in .dds format. ===
This database is loaded at the beginning of the download session and contains all the images present in the home directory of the user who launched the program.

Before downloading the image from the designated website, the program checks in the database if the requested image is already present in the database, if the image is found in any directory of the home, it is copied to the current path. In this way it is possible to avoid carrying out a download job when the image is already present. Obviously the image must have and the pixel size requirements compatible with those required.

With this technique it is possible to distribute the images also on external supports and then make them converge on a working directory, usually with faster access (for example the system SSD). The only constraint is that the external media has a link that links it to a local folder.

With this technique it is also possible to exploit virtual folders that rely on other repositories, for example those shared with P2P techniques.

This example shows a mixed image download with database support. Images ('''copied''') are images copied from other directories on your system, ('''inserted''') are images inserted after a download from the image distribution web server. The images ('''skip''') are those already present in the folder of the images we are creating.

[[File:Screenshot 20210606 212142.png|frameless|800x800px]]

== Saving arguments in a text file ==
[[File:Julia Photoscenery Generator - args file.png|thumb|400x400px|Example of the contents in the '''args.txt''' file]]
Often the number and length of the arguments can become difficult to manage and therefore it is convenient to be able to save them on a file. For this reason, the '''--args''' (or '''-g''') parameter was introduced followed by a filename to be used as an argument container.

Let's take an example to better understand how this parameter works:

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

The arguments associated with the launch of the program are: <code>-i lowi -s 4 -r 20</code>

If we add the '''--args test.txt''' parameter:

<code>julia photoscenary.jl -i lowi -s 4 -r 20 --args test.txt</code>

In the directory where we ran the program we will find a new file called test.txt which contains the list of the parameters just entered.

It is now possible to recall the parameters entered using the command:

<code>julia photoscenary.jl test.txt</code>

The test.txt file, first created, can be edited with a simple text file editor and then modified according to our needs.

=== Arguments implicit saving ===
Launching the program with parameters, but without the '''--args''' option, still generates an arguments file called '''args.txt'''

This file can be recalled for the next program run, simply by running the program with no arguments.

For example:

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

The args.txt file is generated and the program, if run without parameters, will search the args.txt file and load it again using the previous parameters.

<code>julia photoscenary.jl</code>

The program runs exactly as in the previous execution.

== Recipes to be able to try the program and live satisfied ==
There are quite typical configurations that can give a lot of satisfaction to those who want a photorealistic vision, here I give some examples that can be used by anyone.

==== The simplest ====
<code>julia photoscenary.jl</code>

Will rerun with the last commands. The last commands are read from the file "args.txt".

At the first run, this will establish a telnet session where photoscenery is downloaded on demand from your flightgear instance;
see [[Julia_photoscenery_generator#Dynamically_download_orthographic_images_by_--connect]].

==== The scenario of the airport closest to you ====
<code>julia photoscenary.jl -i lowi</code>

''If we live near Innsbruck LOWI is the closest airport.''

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

'''''-i''' followed by the airport abbreviation ICAO, allows you to download that area for a radius of 20 nm ('''-r 20''') and resolution 8K pix ('''-s 4''')''

==== A flight plan has been generated with Skyvector <nowiki>https://skyvector.com/</nowiki> ====
<code>julia -t 6 photoscenary.jl -s 4 -r 20 --sdwn 1 --over 1 --route "LIMJ.gpx" --path "/media/abassign/test/fgfs-scenery/photoscenery"</code>

''The area is processed along a route defined with '''[https://skyvector.com/ Skyvector]''' (but the same methodology also applies to the one defined with the FGFS route planner). The program parses the xml file inserted as a parameter of '''--route''' and determines the format.''

==== The scenario is shown along the route ====
<code>julia -t 10 photoscenary.jl --connect "127.0.0.1:5000" -r 20 -s 3</code>

'''''-t 10''' tells the compiler that it can use up to 10 CPUs, this speeds up the download speed by 2-5 times. '''--connect''' allows you to connect to the Flightgear program (obviously if remote control has been activated (with port 5000) with the launch option of FGFS --telnet = 5000. The parameter '''-s 3''' means that the images will be 4096 pix, a good resolution for flights above 3000 ft.''

==== '''The images are saved for later reuse''' ====
<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 3 -r 20</code>

'''--save''' shows the possibility to save the images also in an external drive, in this way it is possible to create collections of images even in the order of TB avoiding using the system disk space.

'''--over 2''' It allows the replacement of images already present in the path directory, even if of higher resolution.

'''The images are saved for later reuse and the operational image directory is defined by the path option.'''

<code>julia -t 10 photoscenary.jl --over 1 --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 3 -r 20</code>

==== Generation of tiles along the route with maximum efficiency and quality ====
If you want to have a high quality scenario along the route, but at the same time light enough to allow the generation of images in good synchronization with the flight, you must enter the option '''--sdwn''' which, [[Julia photoscenery generator#The --sdwn parameter|as explained before]], allows you to automatically reduce the size of the tiles with the distance, in this way if the tile is distant a small tile is downloaded, if instead the tile is close, the downloaded tile is larger , at most the dimensions are those declared with the --s option. In this way it is possible to fly with a fairly synchronized scenario.

<code>julia -t 6 photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 4 -r 20 --over 1 --sdwn 1</code>

In case you want to get a faster loading of the images that are loaded along the route, remember that the program can overwrite the previous higher resolution images with lower resolution images '''without losing''' the images already downloaded, as they will be inserted in a area outside the scenario (for example a different disk) that can be reached with the path defined with the [[Julia photoscenery generator#--save|--save]] parameter.

This option means that instead of overwriting the images, the program first saves the files, then downloads the images from some external server and then overwrites them. With this technique the overall loading of the images (tiles) is faster as it is useless to download large images of 4-8-16 K pixels placed in distant areas from the pilot's point of view.

Therefore, to minimize the images it is necessary to communicate to the program that it will be able to overwrite the images with the option: [[Julia photoscenery generator#The --over parameter|--over 2]] But since the '''--save''' option is inserted, the program will not delete the previous images, but will insert them in the designated saving areas.

At this point a good command can be this:

<code>julia -t 6 photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" '''--save''' "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 4 -r 20 '''--over 2''' '''--sdwn 1'''</code>

''However, it must always be remembered that currently FGFS does not reload the images of the scenario automatically, but you must click on the debug menu under reload scenario.''

It is possible to avoid entering the --path and --save commands if you adopt the automatic path search method that is activated with --connect active. This makes the command simpler, but obviously you lose the ability to allocate unused images to a certain area on an explicit directory, this is an example:

<code>julia -t 6 photoscenary.jl --connect "127.0.0.1:5000" -s 4 -r 20 '''--over 2''' '''--sdwn 1'''</code>

=== Example of loading multiple scenarios ===
It is possible to use two sessions of photoscenary.jl at the same time to have an updated low resolution scenario (''obviously this method only makes sense if the route follows a path in which a tiles load has never been performed''). The first session will have a low resolution '''-s 1''' or '''-s 2''' while the second resolution could be much higher, e.g. '''-s 4''' or '''-s 5'''

With this configuration it is very likely that the download speed of the orthophoto server you have selected is sufficient to show the images of the territory at low resolution (''remember that currently FGFS requires the manual scenario update if we want to see the scenario just written''), while the second program proceeds to download the images at a higher resolution which will then be visible only in a second flight, obviously on the same route (''it is very unlikely that from resolutions of '''-s 4''' onwards the images can be downloaded with the same speed with which you fly over the territory'').

In this example I have given '''4 cores''' to the high resolution scenario, and '''3 cores''' to the lower resolution scenario. The number of cores cannot exceed the maximum allowed by your CPU, therefore the program, if this number exceeds the available one, automatically reduces the number of cores.

The presence of the '''--over 1''' parameter is fundamental, which manages the insertion of images according to the resolution. However, remember that the low resolution images that will be replaced will not be deleted if you have entered the '''--save''' parameter with the relative save path.

==== High resolution scenario tasks -s 4 (8K) and -r 10 ====
<code>julia '''-t 4''' photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" '''-s 4 -r 10 --over 1'''</code>

==== Low resolution scenario tasks -s 2 (2K) and -r 20 ====
<code>julia '''-t 3''' photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" '''-s 2 -r 20 --over 1'''</code>

==Using the generated photo scenery in FlightGear==
1. Inform FG about additional directory with scenery tiles:
''--fg-scenery=/your/path/to/photoscenery/directory/''
either in command line or as extra options in launcher.

E.g. if you have a directory structure like ''C:\FlightGear\fg_customscenery\photoscenery\Orthophotos\e000n40\e007n46'' then use ''--fg-scenery=C:\FlightGear\fg_customscenery\photoscenery''

2. Check the option Menu > View > Rendering Options > Satellite Photoscenery.

== Use the maps generated by photoscenary.jl for professional applications ==
The photoscenary.jl application allows you to generate maps even only in .png format useful to assemble with gimp (or other painting graphics programs) as the generation of the images guarantees the correct connection. Obviously, reference is made to cylindrical coordinates that must eventually be deformed in case you want to work with a different cartographic model. Currently the program defines the possibility of operating with some image sources defined in the parameter file '''params.xml''' in the sub-section ''<servers> ... </servers>''. Those that offer the most permissive license conditions are produced by USGS (USA) which is an American federal enete and therefore does not bind which all maps with particular limitations of use, the same rules apply as the otographic images produced by NASA that are used in Flightgear for images of the Earth as seen from space.

If one wants to read the terms of use, he can refer to what is reported in [https://www.usgs.gov/faqs/are-usgs-topographic-maps-copyrighted this USGS link].

=== Download images for professional use or publications ===
This paragraph is based on the terms of use of the USGS server, so they may not apply to other servers reachable with this program. The server, as you can see by reading the USGS params.xml file, has '''id = 2'''. For use not related to flightgear it is normally useful to work with files in .png format as the .dds is used only for simulation or games. For technical applications a pair of coordinates is normally used which are: Upper right (UR) and Lower Left (LL) of the requested area. You can also find a set of images using polar coordinates and a radius in nautical miles.

Let's now give one examples:

<code>'''julia -t 6 photoscenary.jl -s 5 --latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.3 --map 2 <small>--png -p</small>''' ''<small>'''"'''</small>'''''<small>/some path/ortho"</small>'''</code>

The coordinates are defined in:

'''-s 5''' is the resolution of the images (s 5 -> 16384 pix for tile)

'''--latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.3'''

Coordinates in six hundredth degrees.

'''--map 2''' indicates that the images will be downloaded from the USGS server.

'''--png''' means that the images WILL NOT BE CONVERTED to .dds but will remain in .png!

'''-p "''<path>''"''' Defines the path where the images will be downloaded.

'''-x''' If the coordinates are expressed in sexagesimal degrees, just enter this additional parameter,

In this case the decimal part of the coordinate value is in prime, for example:

'''--latll 21.50 --latll 158.50'''

It is equivalent to writing:

'''-x --latll 21.30 --lonll 158.30'''

===Wiki articles===
*[[Photoscenery]]

===Forum topics===
*{{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021 - May 2021)
*{{forum link|t=38057|title=16k Photoscenery}} (September 2020 - Gen 2021)

[[Category:Scenery]]
[[Category:Scenery software]]
[[Category:Photoscenery]]

Photoscenery

2024-04-13T06:44:15Z

Hbeni: /* Obtaining orthoimagery */

[[File:Brest.jpg|thumb|270px|A [[Cessna 172P]] flying over 1 m/pixel photoscenery of Brest, France.]]
'''Photoscenery''' is [[scenery]] in which orthoimagery (aerial photographs) is placed over the terrain.

== Why use photoscenery? ==
'''Advantages:'''
* Photoscenery shows the real world, it does not try to resemble it.
* Areas blend realistically, instead of a hard cut between urban and forest, or water and land for example.
* For VFR flight, more easy navigation in known locations because landmarks are more easily recognized

'''Disadvantages:'''
* One needs large (or many) textures for high resolution scenery. For low level (VFR) flying, {{abbr|1 m/pixel|1 pixel spans 1 x 1 m}} is the absolute minimum.
* Orthoimagery is often hard to obtain, especially under an open license.
* The system running photoscenery has a higher memory (RAM) demand

== Enabling photoscenery ==
Photoscenery can be enabled by navigating to the menubar: View, Rendering Options, and click on the Satellite Photoscenery checkbox.

This will load Photoscenery from your normal Scenery folders (subfolder "Orthophotos/").

== Obtaining orthoimagery ==
* [http://www.usgs.gov/ USGS], provides {{abbr|3 m/pixel|1 pixel spans 3 x 3 m}} imagery for the entire United States of America, released in the public domain (and thus GNU GPL compatible).

The prefered way of downloading these images depends on the used method Please read [[#Creating photoscenery|how to create photoscenery]], before starting.

{{note|The most easy and quick way nowadays is to install [https://julialang.org/ Julia] and use the [[Julia photoscenery generator]].}}

=== Preprocessing ===
* Since FlightGear adds haze to the scene, the textures should be "unhazed" to avoid double hazing.
* Shadows included in the images will conflict with shadows added by FlightGear. When creating small areas, shadows can be removed by hand from the textures, but this is usually undoable.

== Creating photoscenery ==
There are several ways of creating photoscenery for [[FlightGear]], of which some are discussed here.
{| class="wikitable"
! Feature
! [[#Texture overlays|Texture overlays]]
! [[#Texture materials|Texture materials]]
! [[#3D Model|3D Model]]
! [[Building FlightGear with osgEarth Integration|osgEarth]]

! Comment
|-
! style="text-align:left;" | Supported by stable FlightGear release (requires no patching)
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|
|-
! style="text-align:left;" | Toggle on run-time
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| With the current patch, the textures overlays are always loaded.
|-
! style="text-align:left;" | Water reflections, random buildings/trees
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Texture masks (not-so random objects)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | Requires no adapted scenery
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | High resolution
| {{no|ca. {{abbr|4m/pixel|1 pixel spans 4 x 4 m}}}}
| {{yes|{{abbr|1m/pixel|1 pixel spans 1 x 1 m}} or higher|colspan{{=}}"2"}}
| {{yes}}
|
|-
! style="text-align:left;" | Advanced weather support
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Requires no custom materials file
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|
|}

=== Texture overlays ===
This method places the photo texture on top of the normal scenery. It requires [http://blaniel.free.fr/pub/flightgear/brest/ patches to be applied] to the FGData and SimGear sources.

# Calculate the tile bounds.
# Cut the orthoimagery to the bounds of the tile and save it with the name of the tile (for example <code>3023737.png</code>).
#: A 4096 x 4096 pixel texture gives roughly a 4 m/pixel resolution. Most graphics cards cannot handle larger textures, so when distributing the scenery this can be considered to be the limit. Tests on various machines showed that 16384 x 16384 pixel textures are possible (1 m/pixel).
# Mirror the texture upside down.
# Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
#: It was found that 16384 x 16384 pixel textures can not be processed by nvcompress. The [http://code.google.com/p/gimp-dds/ DDS plugin for GIMP] worked fine though.
# Place this texture next to the respective <code>.btg.gz</code> file.
Simply launch FlightGear with [[$FG_SCENERY]] set to your scenery directory. Disable all shaders in the ''Main Menu'' > ''View'' > ''Rendering Options'' dialog. Model and Water can be enabled, but all other shaders will disable the photoscenery.

{{note|Step 1 to 5 can be done by the photoscenery perl script from the {{sourceforge source|flightgear|fgscenery/tools|path=Photoscenery|text=FGScenery tools}}, when the imagery is obtained via a [http://en.wikipedia.org/wiki/Web_Map_Service Web Map Service] (WMS).}}

=== Texture materials ===
Another approach is to add each photo texture as a "material" in the <code>materials.xml</code> file.

# Calculate the tile bounds with the python scripts from http://fgphotoscenery.square7.ch/#howto.
#: When creating low resolution scenery ({{abbr|4 m/pixel|1 pixel spans 4 x 4 m}} or lower), a single 4096 x 4096 pixel texture can cover one tile. Higher resolution scenery requires the tile to be cut into smaller pieces: we'll call those photo tiles.
# Repeat the following steps for each single photo tile.
## Mirror the texture upside down.
## Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
## Create a shapefile with the size/location of the texture. Save the shapefile with an unique name (for example <code>302373_3_2.shp</code>, where the <code>3_2</code> indicates the horizontal/vertical tile id. This is not needed when using just one texture per tile).
# Generate the scenery with [[TerraGear]], using the shapefiles as input.
# Currently TerraGear does not create good UV maps, so some manual steps are needed:
# Import (one of) the <code>.btg.gz</code> file(s) in [[Blender]] via the [[Blender and BTG]] plugin.
## Correct the uvmapping of each single sub-tile. The map should cover the texture exactly.
## Export the file again. Please note that you cannot re-import the file after exporting, so do not close Blender before verifying that the UV mapping is correct!
# Create a <code>materials.xml</code> file for your project. For example <code>[[$FG_ROOT]]/Photoscenery/materials-nl.xml</code> for Dutch scenery.
# Add a material definition for each single sub-tile, like:
#: <code><nowiki><material><name>3023745_1_1</name><texture>NL/3023745/3023745.1.1.dds</texture></material></nowiki></code>
#: The texture path is relative to <code>[[$FG_ROOT]]/Textures</code>.
Now launch FlightGear with [[$FG_SCENERY]] set to the output directory of TerraGear and the command <code>--materials-file=Photoscenery/materials-nl.xml</code> (for example).

=== 3D Model ===
[[File:Prague 3D photoscenery.png|thumb|270px|Prague, using the 3D model method.]]
Instead of using the normal terrain, one could replace it by a big 3D model.
# Create a 3D model of the terrain and texturize it with the orthoimagery.
# Place the model as any other 3D object in the scenery.
# Remove the corresponding <code>Terrain/.../... .stg</code> file to hide the normal scenery.

== Extending the photoscenery support in FlightGear ==
{{Out of date|category=section}}

For the earlier mentioned reasons, the texture overlay method seems to be the best and easiest for scenery developers. Nevertheless there are a few issues, stopping us from implementing it in the default FlightGear.

* It unconditionally uses texture unit 3 in the terrain fragment shader, even if no photo-realistic texture has been found.
* It seems to blend the photo textures with the default material textures using the alpha value of the photo texture, but that is not documented anywhere. The purpose of this is unclear (why would you want to blend something photo realistic with a material texture in the first place).
* It currently does not enable clamping, resulting in black tile borders.

Once there is basic support, a method should be found to split a single scenery tile into multiple texture tiles, so the resolution can be higher than 4 m/pixel.

== Projects ==
Several example photoscenery projects. The text between brackets indicates what method is used.
* [[Brest]], France (texture materials)
* [http://helijah.free.fr/flightgear/scenes.html Paris and surroundings], France (texture overlay)
* [http://flightgear-cz.wz.cz/ Prague], Czech Republic (3D Model)
* Selected places of the [http://fgphotoscenery.square7.ch/ United States of America] (texture overlay)

== Related content ==
=== Wiki articles ===
* [[Julia photoscenery generator]]

=== Forum topics ===
* {{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021-) Programs to generate and manipulate photoscenery for FGFS
* {{forum link|t=38057|title=16k Photoscenery}} (September 2020-)
* {{forum link|t=37866|title=Photoscenery?}} (August 2020-) Discussing a patch that simplifies adding photoscenery, that later was added to FlightGear
* {{forum link|p=201862|title=Re: DDS for textures Rotterdam}} (February 2014)
* {{forum link|t=22784|title=A project to create a source of free geo-referenced instrument charts}} (April 2014-June 2014)

[[Category:Photoscenery]]
[[Category:Scenery]]

Photoscenery

2024-04-13T06:35:12Z

Hbeni: /* Enabling photoscenery */

[[File:Brest.jpg|thumb|270px|A [[Cessna 172P]] flying over 1 m/pixel photoscenery of Brest, France.]]
'''Photoscenery''' is [[scenery]] in which orthoimagery (aerial photographs) is placed over the terrain.

== Why use photoscenery? ==
'''Advantages:'''
* Photoscenery shows the real world, it does not try to resemble it.
* Areas blend realistically, instead of a hard cut between urban and forest, or water and land for example.
* For VFR flight, more easy navigation in known locations because landmarks are more easily recognized

'''Disadvantages:'''
* One needs large (or many) textures for high resolution scenery. For low level (VFR) flying, {{abbr|1 m/pixel|1 pixel spans 1 x 1 m}} is the absolute minimum.
* Orthoimagery is often hard to obtain, especially under an open license.
* The system running photoscenery has a higher memory (RAM) demand

== Enabling photoscenery ==
Photoscenery can be enabled by navigating to the menubar: View, Rendering Options, and click on the Satellite Photoscenery checkbox.

This will load Photoscenery from your normal Scenery folders (subfolder "Orthophotos/").

== Obtaining orthoimagery ==
* [http://www.usgs.gov/ USGS], provides {{abbr|3 m/pixel|1 pixel spans 3 x 3 m}} imagery for the entire United States of America, released in the public domain (and thus GNU GPL compatible).

The prefered way of downloading these images depends on the used method Please read [[#Creating photoscenery|how to create photoscenery]], before starting.

=== Preprocessing ===
* Since FlightGear adds haze to the scene, the textures should be "unhazed" to avoid double hazing.
* Shadows included in the images will conflict with shadows added by FlightGear. When creating small areas, shadows can be removed by hand from the textures, but this is usually undoable.

== Creating photoscenery ==
There are several ways of creating photoscenery for [[FlightGear]], of which some are discussed here.
{| class="wikitable"
! Feature
! [[#Texture overlays|Texture overlays]]
! [[#Texture materials|Texture materials]]
! [[#3D Model|3D Model]]
! [[Building FlightGear with osgEarth Integration|osgEarth]]

! Comment
|-
! style="text-align:left;" | Supported by stable FlightGear release (requires no patching)
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|
|-
! style="text-align:left;" | Toggle on run-time
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| With the current patch, the textures overlays are always loaded.
|-
! style="text-align:left;" | Water reflections, random buildings/trees
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Texture masks (not-so random objects)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | Requires no adapted scenery
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | High resolution
| {{no|ca. {{abbr|4m/pixel|1 pixel spans 4 x 4 m}}}}
| {{yes|{{abbr|1m/pixel|1 pixel spans 1 x 1 m}} or higher|colspan{{=}}"2"}}
| {{yes}}
|
|-
! style="text-align:left;" | Advanced weather support
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Requires no custom materials file
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|
|}

=== Texture overlays ===
This method places the photo texture on top of the normal scenery. It requires [http://blaniel.free.fr/pub/flightgear/brest/ patches to be applied] to the FGData and SimGear sources.

# Calculate the tile bounds.
# Cut the orthoimagery to the bounds of the tile and save it with the name of the tile (for example <code>3023737.png</code>).
#: A 4096 x 4096 pixel texture gives roughly a 4 m/pixel resolution. Most graphics cards cannot handle larger textures, so when distributing the scenery this can be considered to be the limit. Tests on various machines showed that 16384 x 16384 pixel textures are possible (1 m/pixel).
# Mirror the texture upside down.
# Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
#: It was found that 16384 x 16384 pixel textures can not be processed by nvcompress. The [http://code.google.com/p/gimp-dds/ DDS plugin for GIMP] worked fine though.
# Place this texture next to the respective <code>.btg.gz</code> file.
Simply launch FlightGear with [[$FG_SCENERY]] set to your scenery directory. Disable all shaders in the ''Main Menu'' > ''View'' > ''Rendering Options'' dialog. Model and Water can be enabled, but all other shaders will disable the photoscenery.

{{note|Step 1 to 5 can be done by the photoscenery perl script from the {{sourceforge source|flightgear|fgscenery/tools|path=Photoscenery|text=FGScenery tools}}, when the imagery is obtained via a [http://en.wikipedia.org/wiki/Web_Map_Service Web Map Service] (WMS).}}

=== Texture materials ===
Another approach is to add each photo texture as a "material" in the <code>materials.xml</code> file.

# Calculate the tile bounds with the python scripts from http://fgphotoscenery.square7.ch/#howto.
#: When creating low resolution scenery ({{abbr|4 m/pixel|1 pixel spans 4 x 4 m}} or lower), a single 4096 x 4096 pixel texture can cover one tile. Higher resolution scenery requires the tile to be cut into smaller pieces: we'll call those photo tiles.
# Repeat the following steps for each single photo tile.
## Mirror the texture upside down.
## Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
## Create a shapefile with the size/location of the texture. Save the shapefile with an unique name (for example <code>302373_3_2.shp</code>, where the <code>3_2</code> indicates the horizontal/vertical tile id. This is not needed when using just one texture per tile).
# Generate the scenery with [[TerraGear]], using the shapefiles as input.
# Currently TerraGear does not create good UV maps, so some manual steps are needed:
# Import (one of) the <code>.btg.gz</code> file(s) in [[Blender]] via the [[Blender and BTG]] plugin.
## Correct the uvmapping of each single sub-tile. The map should cover the texture exactly.
## Export the file again. Please note that you cannot re-import the file after exporting, so do not close Blender before verifying that the UV mapping is correct!
# Create a <code>materials.xml</code> file for your project. For example <code>[[$FG_ROOT]]/Photoscenery/materials-nl.xml</code> for Dutch scenery.
# Add a material definition for each single sub-tile, like:
#: <code><nowiki><material><name>3023745_1_1</name><texture>NL/3023745/3023745.1.1.dds</texture></material></nowiki></code>
#: The texture path is relative to <code>[[$FG_ROOT]]/Textures</code>.
Now launch FlightGear with [[$FG_SCENERY]] set to the output directory of TerraGear and the command <code>--materials-file=Photoscenery/materials-nl.xml</code> (for example).

=== 3D Model ===
[[File:Prague 3D photoscenery.png|thumb|270px|Prague, using the 3D model method.]]
Instead of using the normal terrain, one could replace it by a big 3D model.
# Create a 3D model of the terrain and texturize it with the orthoimagery.
# Place the model as any other 3D object in the scenery.
# Remove the corresponding <code>Terrain/.../... .stg</code> file to hide the normal scenery.

== Extending the photoscenery support in FlightGear ==
{{Out of date|category=section}}

For the earlier mentioned reasons, the texture overlay method seems to be the best and easiest for scenery developers. Nevertheless there are a few issues, stopping us from implementing it in the default FlightGear.

* It unconditionally uses texture unit 3 in the terrain fragment shader, even if no photo-realistic texture has been found.
* It seems to blend the photo textures with the default material textures using the alpha value of the photo texture, but that is not documented anywhere. The purpose of this is unclear (why would you want to blend something photo realistic with a material texture in the first place).
* It currently does not enable clamping, resulting in black tile borders.

Once there is basic support, a method should be found to split a single scenery tile into multiple texture tiles, so the resolution can be higher than 4 m/pixel.

== Projects ==
Several example photoscenery projects. The text between brackets indicates what method is used.
* [[Brest]], France (texture materials)
* [http://helijah.free.fr/flightgear/scenes.html Paris and surroundings], France (texture overlay)
* [http://flightgear-cz.wz.cz/ Prague], Czech Republic (3D Model)
* Selected places of the [http://fgphotoscenery.square7.ch/ United States of America] (texture overlay)

== Related content ==
=== Wiki articles ===
* [[Julia photoscenery generator]]

=== Forum topics ===
* {{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021-) Programs to generate and manipulate photoscenery for FGFS
* {{forum link|t=38057|title=16k Photoscenery}} (September 2020-)
* {{forum link|t=37866|title=Photoscenery?}} (August 2020-) Discussing a patch that simplifies adding photoscenery, that later was added to FlightGear
* {{forum link|p=201862|title=Re: DDS for textures Rotterdam}} (February 2014)
* {{forum link|t=22784|title=A project to create a source of free geo-referenced instrument charts}} (April 2014-June 2014)

[[Category:Photoscenery]]
[[Category:Scenery]]

Photoscenery

2024-04-13T06:32:32Z

Hbeni: /* Why use photoscenery? */

[[File:Brest.jpg|thumb|270px|A [[Cessna 172P]] flying over 1 m/pixel photoscenery of Brest, France.]]
'''Photoscenery''' is [[scenery]] in which orthoimagery (aerial photographs) is placed over the terrain.

== Why use photoscenery? ==
'''Advantages:'''
* Photoscenery shows the real world, it does not try to resemble it.
* Areas blend realistically, instead of a hard cut between urban and forest, or water and land for example.
* For VFR flight, more easy navigation in known locations because landmarks are more easily recognized

'''Disadvantages:'''
* One needs large (or many) textures for high resolution scenery. For low level (VFR) flying, {{abbr|1 m/pixel|1 pixel spans 1 x 1 m}} is the absolute minimum.
* Orthoimagery is often hard to obtain, especially under an open license.
* The system running photoscenery has a higher memory (RAM) demand

== Enabling photoscenery ==
Photoscenery can be enabled by navigating to the menubar: View, Rendering Options, and click on the Satellite Photoscenery checkbox.

== Obtaining orthoimagery ==
* [http://www.usgs.gov/ USGS], provides {{abbr|3 m/pixel|1 pixel spans 3 x 3 m}} imagery for the entire United States of America, released in the public domain (and thus GNU GPL compatible).

The prefered way of downloading these images depends on the used method Please read [[#Creating photoscenery|how to create photoscenery]], before starting.

=== Preprocessing ===
* Since FlightGear adds haze to the scene, the textures should be "unhazed" to avoid double hazing.
* Shadows included in the images will conflict with shadows added by FlightGear. When creating small areas, shadows can be removed by hand from the textures, but this is usually undoable.

== Creating photoscenery ==
There are several ways of creating photoscenery for [[FlightGear]], of which some are discussed here.
{| class="wikitable"
! Feature
! [[#Texture overlays|Texture overlays]]
! [[#Texture materials|Texture materials]]
! [[#3D Model|3D Model]]
! [[Building FlightGear with osgEarth Integration|osgEarth]]

! Comment
|-
! style="text-align:left;" | Supported by stable FlightGear release (requires no patching)
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|
|-
! style="text-align:left;" | Toggle on run-time
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| With the current patch, the textures overlays are always loaded.
|-
! style="text-align:left;" | Water reflections, random buildings/trees
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Texture masks (not-so random objects)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | Requires no adapted scenery
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | High resolution
| {{no|ca. {{abbr|4m/pixel|1 pixel spans 4 x 4 m}}}}
| {{yes|{{abbr|1m/pixel|1 pixel spans 1 x 1 m}} or higher|colspan{{=}}"2"}}
| {{yes}}
|
|-
! style="text-align:left;" | Advanced weather support
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Requires no custom materials file
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|
|}

=== Texture overlays ===
This method places the photo texture on top of the normal scenery. It requires [http://blaniel.free.fr/pub/flightgear/brest/ patches to be applied] to the FGData and SimGear sources.

# Calculate the tile bounds.
# Cut the orthoimagery to the bounds of the tile and save it with the name of the tile (for example <code>3023737.png</code>).
#: A 4096 x 4096 pixel texture gives roughly a 4 m/pixel resolution. Most graphics cards cannot handle larger textures, so when distributing the scenery this can be considered to be the limit. Tests on various machines showed that 16384 x 16384 pixel textures are possible (1 m/pixel).
# Mirror the texture upside down.
# Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
#: It was found that 16384 x 16384 pixel textures can not be processed by nvcompress. The [http://code.google.com/p/gimp-dds/ DDS plugin for GIMP] worked fine though.
# Place this texture next to the respective <code>.btg.gz</code> file.
Simply launch FlightGear with [[$FG_SCENERY]] set to your scenery directory. Disable all shaders in the ''Main Menu'' > ''View'' > ''Rendering Options'' dialog. Model and Water can be enabled, but all other shaders will disable the photoscenery.

{{note|Step 1 to 5 can be done by the photoscenery perl script from the {{sourceforge source|flightgear|fgscenery/tools|path=Photoscenery|text=FGScenery tools}}, when the imagery is obtained via a [http://en.wikipedia.org/wiki/Web_Map_Service Web Map Service] (WMS).}}

=== Texture materials ===
Another approach is to add each photo texture as a "material" in the <code>materials.xml</code> file.

# Calculate the tile bounds with the python scripts from http://fgphotoscenery.square7.ch/#howto.
#: When creating low resolution scenery ({{abbr|4 m/pixel|1 pixel spans 4 x 4 m}} or lower), a single 4096 x 4096 pixel texture can cover one tile. Higher resolution scenery requires the tile to be cut into smaller pieces: we'll call those photo tiles.
# Repeat the following steps for each single photo tile.
## Mirror the texture upside down.
## Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
## Create a shapefile with the size/location of the texture. Save the shapefile with an unique name (for example <code>302373_3_2.shp</code>, where the <code>3_2</code> indicates the horizontal/vertical tile id. This is not needed when using just one texture per tile).
# Generate the scenery with [[TerraGear]], using the shapefiles as input.
# Currently TerraGear does not create good UV maps, so some manual steps are needed:
# Import (one of) the <code>.btg.gz</code> file(s) in [[Blender]] via the [[Blender and BTG]] plugin.
## Correct the uvmapping of each single sub-tile. The map should cover the texture exactly.
## Export the file again. Please note that you cannot re-import the file after exporting, so do not close Blender before verifying that the UV mapping is correct!
# Create a <code>materials.xml</code> file for your project. For example <code>[[$FG_ROOT]]/Photoscenery/materials-nl.xml</code> for Dutch scenery.
# Add a material definition for each single sub-tile, like:
#: <code><nowiki><material><name>3023745_1_1</name><texture>NL/3023745/3023745.1.1.dds</texture></material></nowiki></code>
#: The texture path is relative to <code>[[$FG_ROOT]]/Textures</code>.
Now launch FlightGear with [[$FG_SCENERY]] set to the output directory of TerraGear and the command <code>--materials-file=Photoscenery/materials-nl.xml</code> (for example).

=== 3D Model ===
[[File:Prague 3D photoscenery.png|thumb|270px|Prague, using the 3D model method.]]
Instead of using the normal terrain, one could replace it by a big 3D model.
# Create a 3D model of the terrain and texturize it with the orthoimagery.
# Place the model as any other 3D object in the scenery.
# Remove the corresponding <code>Terrain/.../... .stg</code> file to hide the normal scenery.

== Extending the photoscenery support in FlightGear ==
{{Out of date|category=section}}

For the earlier mentioned reasons, the texture overlay method seems to be the best and easiest for scenery developers. Nevertheless there are a few issues, stopping us from implementing it in the default FlightGear.

* It unconditionally uses texture unit 3 in the terrain fragment shader, even if no photo-realistic texture has been found.
* It seems to blend the photo textures with the default material textures using the alpha value of the photo texture, but that is not documented anywhere. The purpose of this is unclear (why would you want to blend something photo realistic with a material texture in the first place).
* It currently does not enable clamping, resulting in black tile borders.

Once there is basic support, a method should be found to split a single scenery tile into multiple texture tiles, so the resolution can be higher than 4 m/pixel.

== Projects ==
Several example photoscenery projects. The text between brackets indicates what method is used.
* [[Brest]], France (texture materials)
* [http://helijah.free.fr/flightgear/scenes.html Paris and surroundings], France (texture overlay)
* [http://flightgear-cz.wz.cz/ Prague], Czech Republic (3D Model)
* Selected places of the [http://fgphotoscenery.square7.ch/ United States of America] (texture overlay)

== Related content ==
=== Wiki articles ===
* [[Julia photoscenery generator]]

=== Forum topics ===
* {{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021-) Programs to generate and manipulate photoscenery for FGFS
* {{forum link|t=38057|title=16k Photoscenery}} (September 2020-)
* {{forum link|t=37866|title=Photoscenery?}} (August 2020-) Discussing a patch that simplifies adding photoscenery, that later was added to FlightGear
* {{forum link|p=201862|title=Re: DDS for textures Rotterdam}} (February 2014)
* {{forum link|t=22784|title=A project to create a source of free geo-referenced instrument charts}} (April 2014-June 2014)

[[Category:Photoscenery]]
[[Category:Scenery]]

Photoscenery

2024-04-13T06:31:49Z

Hbeni: /* Why use photoscenery? */

[[File:Brest.jpg|thumb|270px|A [[Cessna 172P]] flying over 1 m/pixel photoscenery of Brest, France.]]
'''Photoscenery''' is [[scenery]] in which orthoimagery (aerial photographs) is placed over the terrain.

== Why use photoscenery? ==
'''Advantages:'''
* Photoscenery shows the real world, it does not try to resemble it.
* Areas blend realistically, instead of a hard cut between urban and forest, or water and land for example.

'''Disadvantages:'''
* One needs large (or many) textures for high resolution scenery. For low level (VFR) flying, {{abbr|1 m/pixel|1 pixel spans 1 x 1 m}} is the absolute minimum.
* Orthoimagery is often hard to obtain, especially under an open license.
* The system running photoscenery has a higher memory (RAM) demand

== Enabling photoscenery ==
Photoscenery can be enabled by navigating to the menubar: View, Rendering Options, and click on the Satellite Photoscenery checkbox.

== Obtaining orthoimagery ==
* [http://www.usgs.gov/ USGS], provides {{abbr|3 m/pixel|1 pixel spans 3 x 3 m}} imagery for the entire United States of America, released in the public domain (and thus GNU GPL compatible).

The prefered way of downloading these images depends on the used method Please read [[#Creating photoscenery|how to create photoscenery]], before starting.

=== Preprocessing ===
* Since FlightGear adds haze to the scene, the textures should be "unhazed" to avoid double hazing.
* Shadows included in the images will conflict with shadows added by FlightGear. When creating small areas, shadows can be removed by hand from the textures, but this is usually undoable.

== Creating photoscenery ==
There are several ways of creating photoscenery for [[FlightGear]], of which some are discussed here.
{| class="wikitable"
! Feature
! [[#Texture overlays|Texture overlays]]
! [[#Texture materials|Texture materials]]
! [[#3D Model|3D Model]]
! [[Building FlightGear with osgEarth Integration|osgEarth]]

! Comment
|-
! style="text-align:left;" | Supported by stable FlightGear release (requires no patching)
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|
|-
! style="text-align:left;" | Toggle on run-time
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| With the current patch, the textures overlays are always loaded.
|-
! style="text-align:left;" | Water reflections, random buildings/trees
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Texture masks (not-so random objects)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | Requires no adapted scenery
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | High resolution
| {{no|ca. {{abbr|4m/pixel|1 pixel spans 4 x 4 m}}}}
| {{yes|{{abbr|1m/pixel|1 pixel spans 1 x 1 m}} or higher|colspan{{=}}"2"}}
| {{yes}}
|
|-
! style="text-align:left;" | Advanced weather support
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Requires no custom materials file
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|
|}

=== Texture overlays ===
This method places the photo texture on top of the normal scenery. It requires [http://blaniel.free.fr/pub/flightgear/brest/ patches to be applied] to the FGData and SimGear sources.

# Calculate the tile bounds.
# Cut the orthoimagery to the bounds of the tile and save it with the name of the tile (for example <code>3023737.png</code>).
#: A 4096 x 4096 pixel texture gives roughly a 4 m/pixel resolution. Most graphics cards cannot handle larger textures, so when distributing the scenery this can be considered to be the limit. Tests on various machines showed that 16384 x 16384 pixel textures are possible (1 m/pixel).
# Mirror the texture upside down.
# Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
#: It was found that 16384 x 16384 pixel textures can not be processed by nvcompress. The [http://code.google.com/p/gimp-dds/ DDS plugin for GIMP] worked fine though.
# Place this texture next to the respective <code>.btg.gz</code> file.
Simply launch FlightGear with [[$FG_SCENERY]] set to your scenery directory. Disable all shaders in the ''Main Menu'' > ''View'' > ''Rendering Options'' dialog. Model and Water can be enabled, but all other shaders will disable the photoscenery.

{{note|Step 1 to 5 can be done by the photoscenery perl script from the {{sourceforge source|flightgear|fgscenery/tools|path=Photoscenery|text=FGScenery tools}}, when the imagery is obtained via a [http://en.wikipedia.org/wiki/Web_Map_Service Web Map Service] (WMS).}}

=== Texture materials ===
Another approach is to add each photo texture as a "material" in the <code>materials.xml</code> file.

# Calculate the tile bounds with the python scripts from http://fgphotoscenery.square7.ch/#howto.
#: When creating low resolution scenery ({{abbr|4 m/pixel|1 pixel spans 4 x 4 m}} or lower), a single 4096 x 4096 pixel texture can cover one tile. Higher resolution scenery requires the tile to be cut into smaller pieces: we'll call those photo tiles.
# Repeat the following steps for each single photo tile.
## Mirror the texture upside down.
## Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
## Create a shapefile with the size/location of the texture. Save the shapefile with an unique name (for example <code>302373_3_2.shp</code>, where the <code>3_2</code> indicates the horizontal/vertical tile id. This is not needed when using just one texture per tile).
# Generate the scenery with [[TerraGear]], using the shapefiles as input.
# Currently TerraGear does not create good UV maps, so some manual steps are needed:
# Import (one of) the <code>.btg.gz</code> file(s) in [[Blender]] via the [[Blender and BTG]] plugin.
## Correct the uvmapping of each single sub-tile. The map should cover the texture exactly.
## Export the file again. Please note that you cannot re-import the file after exporting, so do not close Blender before verifying that the UV mapping is correct!
# Create a <code>materials.xml</code> file for your project. For example <code>[[$FG_ROOT]]/Photoscenery/materials-nl.xml</code> for Dutch scenery.
# Add a material definition for each single sub-tile, like:
#: <code><nowiki><material><name>3023745_1_1</name><texture>NL/3023745/3023745.1.1.dds</texture></material></nowiki></code>
#: The texture path is relative to <code>[[$FG_ROOT]]/Textures</code>.
Now launch FlightGear with [[$FG_SCENERY]] set to the output directory of TerraGear and the command <code>--materials-file=Photoscenery/materials-nl.xml</code> (for example).

=== 3D Model ===
[[File:Prague 3D photoscenery.png|thumb|270px|Prague, using the 3D model method.]]
Instead of using the normal terrain, one could replace it by a big 3D model.
# Create a 3D model of the terrain and texturize it with the orthoimagery.
# Place the model as any other 3D object in the scenery.
# Remove the corresponding <code>Terrain/.../... .stg</code> file to hide the normal scenery.

== Extending the photoscenery support in FlightGear ==
{{Out of date|category=section}}

For the earlier mentioned reasons, the texture overlay method seems to be the best and easiest for scenery developers. Nevertheless there are a few issues, stopping us from implementing it in the default FlightGear.

* It unconditionally uses texture unit 3 in the terrain fragment shader, even if no photo-realistic texture has been found.
* It seems to blend the photo textures with the default material textures using the alpha value of the photo texture, but that is not documented anywhere. The purpose of this is unclear (why would you want to blend something photo realistic with a material texture in the first place).
* It currently does not enable clamping, resulting in black tile borders.

Once there is basic support, a method should be found to split a single scenery tile into multiple texture tiles, so the resolution can be higher than 4 m/pixel.

== Projects ==
Several example photoscenery projects. The text between brackets indicates what method is used.
* [[Brest]], France (texture materials)
* [http://helijah.free.fr/flightgear/scenes.html Paris and surroundings], France (texture overlay)
* [http://flightgear-cz.wz.cz/ Prague], Czech Republic (3D Model)
* Selected places of the [http://fgphotoscenery.square7.ch/ United States of America] (texture overlay)

== Related content ==
=== Wiki articles ===
* [[Julia photoscenery generator]]

=== Forum topics ===
* {{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021-) Programs to generate and manipulate photoscenery for FGFS
* {{forum link|t=38057|title=16k Photoscenery}} (September 2020-)
* {{forum link|t=37866|title=Photoscenery?}} (August 2020-) Discussing a patch that simplifies adding photoscenery, that later was added to FlightGear
* {{forum link|p=201862|title=Re: DDS for textures Rotterdam}} (February 2014)
* {{forum link|t=22784|title=A project to create a source of free geo-referenced instrument charts}} (April 2014-June 2014)

[[Category:Photoscenery]]
[[Category:Scenery]]

Photoscenery

2024-04-13T06:30:39Z

Hbeni:

[[File:Brest.jpg|thumb|270px|A [[Cessna 172P]] flying over 1 m/pixel photoscenery of Brest, France.]]
'''Photoscenery''' is [[scenery]] in which orthoimagery (aerial photographs) is placed over the terrain.

== Why use photoscenery? ==
'''Advantages:'''
* Photoscenery shows the real world, it does not try to resemble it.
* Areas blend realistically, instead of a hard cut between urban and forest, or water and land for example.

'''Disadvantages:'''
* One needs large (or many) textures for high resolution scenery. For low level (VFR) flying, {{abbr|1 m/pixel|1 pixel spans 1 x 1 m}} is the absolute minimum.
* Orthoimagery is often hard to obtain, especially under an open license.

== Enabling photoscenery ==
Photoscenery can be enabled by navigating to the menubar: View, Rendering Options, and click on the Satellite Photoscenery checkbox.

== Obtaining orthoimagery ==
* [http://www.usgs.gov/ USGS], provides {{abbr|3 m/pixel|1 pixel spans 3 x 3 m}} imagery for the entire United States of America, released in the public domain (and thus GNU GPL compatible).

The prefered way of downloading these images depends on the used method Please read [[#Creating photoscenery|how to create photoscenery]], before starting.

=== Preprocessing ===
* Since FlightGear adds haze to the scene, the textures should be "unhazed" to avoid double hazing.
* Shadows included in the images will conflict with shadows added by FlightGear. When creating small areas, shadows can be removed by hand from the textures, but this is usually undoable.

== Creating photoscenery ==
There are several ways of creating photoscenery for [[FlightGear]], of which some are discussed here.
{| class="wikitable"
! Feature
! [[#Texture overlays|Texture overlays]]
! [[#Texture materials|Texture materials]]
! [[#3D Model|3D Model]]
! [[Building FlightGear with osgEarth Integration|osgEarth]]

! Comment
|-
! style="text-align:left;" | Supported by stable FlightGear release (requires no patching)
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
|
|-
! style="text-align:left;" | Toggle on run-time
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| With the current patch, the textures overlays are always loaded.
|-
! style="text-align:left;" | Water reflections, random buildings/trees
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Texture masks (not-so random objects)
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | Requires no adapted scenery
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
|
|-
! style="text-align:left;" | High resolution
| {{no|ca. {{abbr|4m/pixel|1 pixel spans 4 x 4 m}}}}
| {{yes|{{abbr|1m/pixel|1 pixel spans 1 x 1 m}} or higher|colspan{{=}}"2"}}
| {{yes}}
|
|-
! style="text-align:left;" | Advanced weather support
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| Depends on accuracy of underlying terrain (shapefiles)
|-
! style="text-align:left;" | Requires no custom materials file
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
|
|}

=== Texture overlays ===
This method places the photo texture on top of the normal scenery. It requires [http://blaniel.free.fr/pub/flightgear/brest/ patches to be applied] to the FGData and SimGear sources.

# Calculate the tile bounds.
# Cut the orthoimagery to the bounds of the tile and save it with the name of the tile (for example <code>3023737.png</code>).
#: A 4096 x 4096 pixel texture gives roughly a 4 m/pixel resolution. Most graphics cards cannot handle larger textures, so when distributing the scenery this can be considered to be the limit. Tests on various machines showed that 16384 x 16384 pixel textures are possible (1 m/pixel).
# Mirror the texture upside down.
# Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
#: It was found that 16384 x 16384 pixel textures can not be processed by nvcompress. The [http://code.google.com/p/gimp-dds/ DDS plugin for GIMP] worked fine though.
# Place this texture next to the respective <code>.btg.gz</code> file.
Simply launch FlightGear with [[$FG_SCENERY]] set to your scenery directory. Disable all shaders in the ''Main Menu'' > ''View'' > ''Rendering Options'' dialog. Model and Water can be enabled, but all other shaders will disable the photoscenery.

{{note|Step 1 to 5 can be done by the photoscenery perl script from the {{sourceforge source|flightgear|fgscenery/tools|path=Photoscenery|text=FGScenery tools}}, when the imagery is obtained via a [http://en.wikipedia.org/wiki/Web_Map_Service Web Map Service] (WMS).}}

=== Texture materials ===
Another approach is to add each photo texture as a "material" in the <code>materials.xml</code> file.

# Calculate the tile bounds with the python scripts from http://fgphotoscenery.square7.ch/#howto.
#: When creating low resolution scenery ({{abbr|4 m/pixel|1 pixel spans 4 x 4 m}} or lower), a single 4096 x 4096 pixel texture can cover one tile. Higher resolution scenery requires the tile to be cut into smaller pieces: we'll call those photo tiles.
# Repeat the following steps for each single photo tile.
## Mirror the texture upside down.
## Convert the texture to <code>.dds</code> via NVidia's nvcompress (part of the [http://developer.nvidia.com/legacy-texture-tools NVidia Tools]).
## Create a shapefile with the size/location of the texture. Save the shapefile with an unique name (for example <code>302373_3_2.shp</code>, where the <code>3_2</code> indicates the horizontal/vertical tile id. This is not needed when using just one texture per tile).
# Generate the scenery with [[TerraGear]], using the shapefiles as input.
# Currently TerraGear does not create good UV maps, so some manual steps are needed:
# Import (one of) the <code>.btg.gz</code> file(s) in [[Blender]] via the [[Blender and BTG]] plugin.
## Correct the uvmapping of each single sub-tile. The map should cover the texture exactly.
## Export the file again. Please note that you cannot re-import the file after exporting, so do not close Blender before verifying that the UV mapping is correct!
# Create a <code>materials.xml</code> file for your project. For example <code>[[$FG_ROOT]]/Photoscenery/materials-nl.xml</code> for Dutch scenery.
# Add a material definition for each single sub-tile, like:
#: <code><nowiki><material><name>3023745_1_1</name><texture>NL/3023745/3023745.1.1.dds</texture></material></nowiki></code>
#: The texture path is relative to <code>[[$FG_ROOT]]/Textures</code>.
Now launch FlightGear with [[$FG_SCENERY]] set to the output directory of TerraGear and the command <code>--materials-file=Photoscenery/materials-nl.xml</code> (for example).

=== 3D Model ===
[[File:Prague 3D photoscenery.png|thumb|270px|Prague, using the 3D model method.]]
Instead of using the normal terrain, one could replace it by a big 3D model.
# Create a 3D model of the terrain and texturize it with the orthoimagery.
# Place the model as any other 3D object in the scenery.
# Remove the corresponding <code>Terrain/.../... .stg</code> file to hide the normal scenery.

== Extending the photoscenery support in FlightGear ==
{{Out of date|category=section}}

For the earlier mentioned reasons, the texture overlay method seems to be the best and easiest for scenery developers. Nevertheless there are a few issues, stopping us from implementing it in the default FlightGear.

* It unconditionally uses texture unit 3 in the terrain fragment shader, even if no photo-realistic texture has been found.
* It seems to blend the photo textures with the default material textures using the alpha value of the photo texture, but that is not documented anywhere. The purpose of this is unclear (why would you want to blend something photo realistic with a material texture in the first place).
* It currently does not enable clamping, resulting in black tile borders.

Once there is basic support, a method should be found to split a single scenery tile into multiple texture tiles, so the resolution can be higher than 4 m/pixel.

== Projects ==
Several example photoscenery projects. The text between brackets indicates what method is used.
* [[Brest]], France (texture materials)
* [http://helijah.free.fr/flightgear/scenes.html Paris and surroundings], France (texture overlay)
* [http://flightgear-cz.wz.cz/ Prague], Czech Republic (3D Model)
* Selected places of the [http://fgphotoscenery.square7.ch/ United States of America] (texture overlay)

== Related content ==
=== Wiki articles ===
* [[Julia photoscenery generator]]

=== Forum topics ===
* {{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021-) Programs to generate and manipulate photoscenery for FGFS
* {{forum link|t=38057|title=16k Photoscenery}} (September 2020-)
* {{forum link|t=37866|title=Photoscenery?}} (August 2020-) Discussing a patch that simplifies adding photoscenery, that later was added to FlightGear
* {{forum link|p=201862|title=Re: DDS for textures Rotterdam}} (February 2014)
* {{forum link|t=22784|title=A project to create a source of free geo-referenced instrument charts}} (April 2014-June 2014)

[[Category:Photoscenery]]
[[Category:Scenery]]

Julia photoscenery generator

2024-04-13T06:29:51Z

Hbeni: Added proper software filehandler

{{Infobox Software
|title = FGCom-mumble
|logo = G91R1B taking off from LOWI .jpg|128px
|developedby = Adriano Bassignana
|developmentstatus = Active
|type = Photoscenery generator
|latestrelease = (rolling releases)
|initialrelease = 18.04.2021
|writtenin = julia
|os = Windows, GNU/Linux, MacOS
|license = [[GNU General Public License]] v2
|website = https://github.com/abassign/Photoscenary
}}
[[File:G91R1B taking off from LOWI .jpg|thumb|500px|Photoscenery created with the Julia photoscenery generator behind a [[FIAT G91R1B|G91R1B]] taking off from LOWI. In this example the resolution of the tiles is 32K (s 6).]]

Through the '''Julia photoscenery generator''' using ImageMagic and written in the Julia programming language you can create photoscenery tiles.

Once you have everything installed you will discover how easy it is to fill your disk with hundreds of GB made from thousands of images of our planet and then fly over vast territories and recognize our cities and villages.

The use of World Scenery by FlightGear together with the photoscenery as a background can make the scene very rich in details and pleasing to your eyes.
== Quick method for Windows users ==
===Steps===
* 1. [https://julialang.org/downloads/#official_binaries_for_manual_download Down-Inst Julia Programming Language].
* 2. [https://imagemagick.org/script/download.php#windows Down-Inst ImageMagick].
* 3. [https://github.com/abassign/Photoscenary/archive/refs/heads/main.zip Down-Inst photoscenary.jl.zip] Easy Manual installation. Unzip Fhotoscenary-main folder, place it where you preferred. Look inside for the file photoscenary.jl and make it executable by Julia, using Right click >> Properties >> Navigate to the bin folder Julia.exe and choose open with Julia Programming Language.
===Check===
* 4. Open FGlauncher >> Settings >> Additional settings. Add the property: --telnet=5000
* 5. Make sure you have terrasync activated. Automatic download terrain in FGlauncher.
* 6. In FlightGear v2020.3.18 check the following: Start the simulator (one flight) and access the menu: VIEW/RENDERING OPTIONS. In the right column, make sure you have the "SATELLITE PHOTOSCENERY" option activated and close the flight.
===Run & Check===
* 7. Run the program photoscenary.jl. It will run and check with Julia, will prompt telnet connection attempts at 127.0.0.1:5000.
* 8. Run FG. Fly and check visually that you are getting textures. Give it a time, you'll get better textures progressively during your flight.
* 9. Check in C:\Users\YOUR_USER_NAME\FlightGear\Downloads\TerraSync\Orthophotos. You should see folders of type "e000n00" containing ".dds" files.
* 10. Check that the Julia's window running photoscenary.jl is getting data (tiles).

In case of doubts, the next video at SUMU Montevideo area by Manuel Aceña is recommended as a reference.
=== Video ===
{{#ev:youtube|PbYAvxmAkIc}}

==Background==
The success that photoscenery is achieving among FlightGear users has prompted me to study a program for downloading and installing photoscenery via a simple command to run inside a terminal (if we are in Linux or Mac OS) or in a command prompt (if we are in Windows).

The program was developed in Julia which is a latest generation programming language developed by MIT. This language looks quite similar to Nasal and therefore the code is easily readable by those who already use the FlightGear Nasal language script, but it is extremely faster and full of features that make the creation of this program quick and easy enough to evolve. Obviously the only inconvenience is that Julia has to be installed on your system, but it is a very simple action and equivalent to the same need to install ImageMagick on your system, this latter program allows the conversion of images in DDS format.
[[File:Julia photoscenery generator - Towards Budapest on the Danube plain.jpg|thumb|500x500px|The photoscenary allows to have very realistic effects on rather complex territories, such as crops in the plains. The image shows the signs of the passage of old rivers, still visible as a difference in the color of the vegetation.]]

==Installing the programs==

=== FlightGear ===
Currently to utilise photoscenery the minimum FlightGear version is 2020.3.18

===Julia installation===
https://julialang.org/

Julia installation is straightforward, whether using precompiled binaries or compiling from source. Download and install Julia by following the instructions at https://julialang.org/downloads/.
{| class="wikitable"
!Windows
| colspan="3" |'''64-bit (installer), 64-bit (portable)'''
| colspan="3" |32-bit (installer), 32-bit (portable)
|-
!macOS
| colspan="3" |'''64-bit'''
| colspan="3" |
|-
!Generic Linux on x86
| colspan="3" |'''64-bit (GPG), 64-bit (musl) (GPG)'''
| colspan="3" | 32-bit (GPG)
|-
!Generic Linux on ARM
| colspan="3" |'''64-bit (AArch64) (GPG)'''
| colspan="3" |32-bit (ARMv7-a hard float) (GPG)
|-
!Generic Linux on PowerPC
| colspan="3" |64-bit (little endian) (GPG)
| colspan="3" |
|-
!Generic FreeBSD on x86
| colspan="3" | 64-bit (GPG)
|
|}
For Linux users there are no particular problems, each distribution has Julia among the installable programs. The only problem is the version that may be older than 1.6, in this case I recommend wasting a little more time and updating the installation to 1.6, you can follow [https://medium.com/coffee-in-a-klein-bottle/install-julia-1-5-on-ubuntu-bb8be4b2571d this handy guide] that explains how to do everything in a few minutes.

The version to use is convenient that it is from '''1.6''' onwards, 1.5.4 is present in the Ubuntu repositories until 2020.10 but it is better to update it to 1.6 even if this requires a little work, But with Ubuntu/Kubuntu version 2021.4 Julia is already at version 1.6.1 and so just use the command:

<code>'''sudo apt install julia'''</code>

Julia is a young language that is continuously updated and the difference between Julia 1.5 and 1.6 is really very big for the application startup speed. For the execution there are no particular differences if you use Julia 1.5.4 onwards.

The installation with windows is absolutely the easiest to do, just follow the installer to get a version of Julia 1.6.x All users who have done the installation have never complained of problems.

For '''Mac users''' it might be the slightly more complicated thing, but from the users texts made, I haven't had any issues encountered among Mac users.

For '''Windows users''' have not encountered any particular problems with the installation, which is always the most up-to-date.

{{caution
|The program was designed to work in Linux (any distribution), Windows 10 and Mac OS. This is very unlikely to work with CygWin as there have been reports of problems calling Imagemagick. Instead, it works with Windows Subsystem for Linux, which is basically a well-integrated emulator of Linux inside the Windows system. In this case, multithreading may not work well, so I recommend running the program with only one Julia thread via the command:<BR><i>julia -t 1 photoscenary.jl ...</i><BR>Or with the command:<BR><i>julia photoscenary.jl</i><BR>But this approach seems like an unnecessary complication to me as the program works perfectly in Windows 10.
| width =
| padding =
| margin = 2%
}}

===ImageMagick installation===
https://imagemagick.org/index.php

For download program this is the link: https://imagemagick.org/script/download.php

Normally the files that are released by satellite image servers are in PNG format, but the PNG files are absolutely unsuitable to be used as photoscenery files. The reason is that the graphics engine of FlightGear must still convert these files into DDS format which is more compressed than the PNG format (about 4 times). Conversion, for very large files, takes a lot of CPU time, slowing down the execution of FlightGear. Therefore for this program it has been chosen to release only the DDS format and therefore ImageMagick is the most suitable program for this operation.

ImageMagick allows you to convert files transparently to the user very quickly.

In Linux distributions, ImageMagick is often already present, to find out just type the command <code>'''convert --version'''</code> and see if something responds. In windows it must be downloaded with an installer that can be downloaded here: https://imagemagick.org/script/download.php#windows

The installation in Windows of ImageMagick could give problems if it has not been correctly carried out. Therefore, if the photoscenary.jl program returns an error due to the lack of ImageMagick (the program always checks at the start) it is convenient to remove ImageMagick through the Windows program management and install it again.

===The photoscenary.jl installation===
https://github.com/abassign/Photoscenary

The program is written in pure Julia code, there are no scripts that can complicate your life. However, some rules must be followed that simplify all the work.

First create a directory where to place the program and its support files. The directory can be placed wherever you want as the program will dynamically build its references. Once the directory (or folder for Mac users) is done, download the Zip file that GitHub generates obtained from this link: https://github.com/abassign/Photoscenary.git

[[File:Github for photoscenary.jl.png|alt=|800x800px]]

Click on code and it will download the zip file that you can open and insert the contents into the folder you created. In the folder you will find some auxiliary files, but now let's analyze the program files.

*<code>'''photoscenary.jl'''</code> It is the Julia program to run, you can open it and see it with a simple text editor, I think some of you who have programmed in Python or NASAL will have no difficulty understanding how it works. However the program is compiled every time you run it, it is this compilation, really efficient and fast, that allows you to obtain an excellent executive performance.
*<code>'''params.xml'''</code> It is an XML file that contains some parameters necessary for the correct execution of the program.
*<code>'''airports.csv'''</code> It is the file, extracted from the correspondent of FlightGear, which contains a list of airports, their coordinates and the extended name. This file is essential in order to use a location option for the area to be downloaded.

==Execution of the program ==

===Hello World!===
There is a minimal execution that allows you to check if everything we have done has worked correctly, this is a sort of ''Hello World'' of the program.

The most important thing is to go to the directory (folder) where you installed the program with a ''terminal'' or with a ''command prompt'' (if you are in Windows).

So the first thing to do is to be with the terminal inside this directory and run this command:

<code>'''julia photoscenary.jl'''</code>

An area of 2048 pixels (long side) tiles with a size of approximately 10x10 NM is generated, with the coordinates of the ''Orio al Serio Airport'' (LIME) in the center. Not having entered any other parameters, the processing time is relatively long as only one download per tile is performed.

[[File:Test julia photoscenary.jl.png|frameless|800x800px]]

We carefully observe this execution, the first line shows the name of the program, the version and the date of realization, then follows the indication that the prerequisite test will take place. If we are at the first execution we will see an endless series of compilations that can make us think that something has not gone well, but do not worry, it is simply the module management system that downloads the modules useful for the execution of the program and that are not present in the base system. In this way the Julia program updates the necessary components without having to prompt the user to do it for him.

In this particular case, which occurs only the first time or in a version change, the application communicates that it will terminate the execution and invites the user, once back to the command prompt, to run the same command again, also in this case there could be a lot of updating of the modules that have not been updated in the first cycle, do not worry, everything is going great. At the end of the update, finally, the execution of the code contained in the program takes place.

The image above summarizes what happened during the download of the tiles.

Very important to note the line:

'''ImageMagick is operational!'''

This line tells us that the system has done a test with ImageMagick installed on its system and has verified that it works correctly. If this does not work, since without ImageMagick the system cannot do anything, you have an exit with a program error (Error code 504).

====Description of the individual status lines of the processes performed====
We now summarize the content of the individual lines that indicate the modules downloaded and their status:

{| class="wikitable"
!Column!!Content
|-
!Time:
|Processing time for individual tiles
|-
!elab:
|Total processing time
|-
!
( ... {{!}} ... ) 
|The processing time for each tile followed by the estimated time.
These two values allow us to understand the efficiency of the work in progress.
|-
!Tiles:
|Number of tiles that have been processed by the program.
|-
! on
|Total number of tiles to be processed.
|-
!res
|The residual tiles to be processed.
|-
!Th:
|Number of threads used by the process.
|-
!path:
| The path and name of the processed file.
|-
!MB/s:
|Download speed in Mega Bytes on second.
|-
!MB dw:
|Amount of mega bytes downloaded overall.
|-
!( ... )
| Type of activity carried out
|}

=== Activate the Julia multi thread ===
Julia is a language created for applications on supercomputers, artificial intelligence, number-crusher, etc.

These are applications that require systems with a lot of CPUs and therefore the compiler has the ability to activate very sophisticated strategies to better manage resources.

The photoscenary.jl program performs many processes in parallel in order to optimize the download and conversion of images. The conversion from the original PNG format to the more efficient format for FlightGear DDS requires a rather heavy application (ImageMagick) which can only be run on single CPUs. For this it is very efficient to run the program on multiple CPUs, but it is necessary to use some care that I explain below.

==== Core <-> CPU what are they ? ====
Any PC has a processor with a certain number of ''physical'' ''core'' ranging from 2 (Intel i3) to values that can go up to 12 or more for more performing desktop processors.

For years, all processor cores have been able to handle two separate CPU, using a hardware trick. Therefore an i3 processor with two core will allow to manage up to 4 CPU (or separate processes) at the same time.

At this point it is important the role of the operating system that must manage the available CPU and assign them to the running programs.

So when you start Julia it is possible to reserve the number of CPU to the application will require than and this must be done at the beginning so that the compiler will configure the code properly.

This is achieved with the '''-t n''' command where n is a number equal to or less than the number of available CPU.

==== The Julia -t n option ====
If you run the program with the command:

'''<code>julia photoscenary.jl</code>'''

Only one CPU will be used and this can be a bottleneck when downloading files from the web server that distributes the images, since, especially if you have images composed of a single file (from the smallest ones up to 2048 pixels) the program uses only one process (for larger images the program uses many more download processes).

So let's say we have a machine with 6 core and therefore 12 CPU we can launch the program with this command:

<code>'''julia -t 10 photoscenary.jl'''</code>

If we are on a 4 CPU as i3 it is necessary to reduce the value to 4, but maybe 3 would also be good, so we can write the command like this:

<code>'''julia -t 3 photoscenary.jl'''</code>

==== Be careful though ====
''If the value of the maximum number of CPU is too high, the behavior of the operating system could be such as to reduce the advantage in execution or even slow down the program!''

This certainly happens when the value of the '''''-t''' numbe''r is higher than the number of CPUs and if the system is windows 10 or 8 you will have an incredible slowdown of the program! Therefore on a Windows machine it is not advisable to always enter a value less than or equal to the number of CPU of the processor in use (''number of cores multiplied by 2'').

For Linux and Mac systems the problem seems to be less evident and so you can try to increase the number beyond the theoretical maximum value.

=== Now let's try to delete all the files just inserted===
This test allows us to understand the use of a very useful parameter to manage the files we create with this application, for example if we want to delete the files, perhaps to have an area managed with the traditional FlightGear system, we can do it with the following command:

<code>'''julia -t 10 photoscenary.jl --over 9'''</code>

We will get this result (I show only the last lines to focus attention on the fact that the system declares to perform some removes)

[[File:Test julia photoscenary.jl --over 9.png|frameless|800x800px]]

===Now lets put the turbojet into the download program===
We now put the <code>'''-t 10'''</code> option on the Julia compiler start command. This option allows you to run multiple threads at the same time allowing you to speed up the download of files.

<code>'''julia -t 10 photoscenary.jl'''</code>

[[File:Test julia -t 10 photoscenary.jl.png|frameless|800x800px]]

In this image I show all the lines processed to show how the progression of the download speed increase. As you can see at first the speed seems low, but in reality the system has launched about ten threads that form a queue of requests to the image server. The format of the images, when nothing is declared, as in this example, is 2048 pixels on the long side, and the size of the DDS file (we are at an intermediate latitude between 62-22 degrees) is 1 MB.

The average speed is 1.7 MB/s (but can go even higher) and is determined by the actual workload on the server distributing the images.

This way we have more than tripled the download speed.

Obviously these values can change a lot, but they are on average better than those obtained with single downloads. Not only that, but multithreading also works with the ImageMagick program that performs the transformation of the PNG file into DDS, this transformation is not fast, but in this way it is parallelized, making this phase less expensive in terms of time.

This feature is even more interesting for larger format images.

===Increase the resolution of the images, radius and --over option===
Let's see these two new options that can be given to the program:

<code>'''-r 5'''</code> where n is the number of miles of radius, if <code>'''-r'''</code> (Radius) is equal to 5 it means that we are covering a square whose diagonal is 5 NM. Note that if -r is not defined the system considers the radius of 10 NM.

<code>'''-s 4'''</code> indicates the resolution of the images we want to obtain, if this option is not inserted the default value is 2 equal to an image, on the long side, of 2048 pixels.

<code>j'''ulia -t 10 photoscenary.jl -r 5 -s 4'''</code>

[[File:Test julia -t 10 photoscenary.jl -r 5 -s 4 (skip).png|frameless|800x800px]]

In fact the system has not done anything, the status message, at the bottom of each line, tells us (skip) which means that the program has seen that an image is already present and this image cannot be overwritten as it is an image valid (actually the program checks the image by loading and verifying it), if the image was not valid, it would delete it and replace it with a new one.

But it is still possible to override by inserting the <code>'''--over 1'''</code> option at this point this interesting fact happens:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 4 --over 1'''</code>

[[File:Test julia -t 10 photoscenary.jl -r 5 -s 4 --over 1.png|frameless|800x800px]]

This download is '''16 times slower''' as the precedent download (Without the <code>-s</code> option the image downloads as <code>-s 2</code> which corresponds to 2048 pixels long edge) <code>'''-s 4'''</code> option downloads images of '''8192''' pixels long side. In fact the system downloads 16 images with size of '''2048''' and composes them into a matrix '''4x4,''' at the end of the composition the images are first transformed into an temporary PNG image format which will be processed by ImageMagick and becomes an DDS format image that is compatible with FlightGear without any on-the-fly conversion (which is done for PNG images). Therefore this line shows us the downloading of the single images that make up the matrix in order to give an idea that something is happening.

[[File:Julia -t 10 photoscenary.jl -r 5 -s 4 --over 1-BW.png|alt=|frameless|799x799px]]

Note that the download speed of individual images has increased (in this case 2.98 MB/s) as the system has opened several dozen download threads (96 download tasks are open at the same time as their number is the product of 6 threads x 16 images) .

It is important to understand this aspect of the program which can easily bring the network into saturation. In this example 3 MB/s correspond to about 30-40 MBit/s which is about 70-80% of the bandwidth that the network allows me to have. For this, if the band used is high, in order to keep a good surfing speed on the network, it is sufficient to reduce the value of the threads in Julia from -t 10 to -t 4 or -t 5.<blockquote>'''Note''': ''Julia is a programming language that has an incredible variety of methods for exploiting all possible hardware solutions. What I exploit in this program is only a small part, Julia even allows you to distribute the processing on remote machines, perhaps placed on different networks, in order to distribute the workload through the use of a few instructions.''</blockquote>From a series of tests that I have done, 8K images are the most interesting for systems that have at least 16 GB of RAM, if the RAM is lower these images can lead to FlightGear in memory overflow and therefore its closure by the system operating.

==== The -s parameter ====
<code>'''-s'''</code> defines 7 possible resolutions for images:
{| class="wikitable"
!Parameter!!Side px!! Format!!Size MB!! Comment
!PC RAM GB
|-
!-s 0
|style="text-align: center;"|512
|style="text-align: center;"|DDS
|style="text-align: center;"|0.064
|
|style="text-align: center;"|2
|-
!-s 1
|style="text-align: center;"|1024
|style="text-align: center;"|DDS
|style="text-align: center;"|0.256
|
|style="text-align: center;"|2
|-
!'''-s 2'''
|style="text-align: center;"|2048
|style="text-align: center;"|DDS
|style="text-align: center;"|1
|
|style="text-align: center;"|4
|-
!-s 3
|style="text-align: center;"|4096
|style="text-align: center;"|DDS
|style="text-align: center;"|4
|2 x 2 matrix = 4 images with 2048 pixels side to download
|style="text-align: center;"|8
|-
!'''-s 4'''
|style="text-align: center;"|8192
|style="text-align: center;"|DDS
|style="text-align: center;"|16
|4 x 4 matrix = 16 images with 2048 pixels side to download
|style="text-align: center;"|16
|-
!-s 5
|style="text-align: center;"|16384
|style="text-align: center;"|DDS
|style="text-align: center;"|64
|8 x 8 matrix = 64 images with 2048 pixels side to download
|style="text-align: center;"|16
|-
!-s 6
|style="text-align: center;"|32768
|style="text-align: center;"|DDS
|style="text-align: center;"|256
|8 x 8 matrix = 64 images with 4096 pixels side to download
|style="text-align: center;"|16
|}
The PC RAM that I recommend for PCs that need to download images. So I was able to download, even with Windows 10, which is much heavier than Linux, 16384 px images with only 4 GB of RAM! In this case there is a huge increase in virtual memory (''Both Linux with kernel 5 and Windows 10 have a dynamic virtual memory that is quite efficient if the hard disk is of the SSD type'') in use which, due to the structure of the program and the particular compiler used, it does not seem to slow down performance.

==== The --sdwn parameter====
<code>'''--sdwn'''</code> It is a parameter that defines how to change the value of the resolution or the distance using a linear method. For example, if the coverage radius is 100 nm and -s 5 (16K pixels), if we set <code>'''--sdwn 2'''</code> we will have this resolution trend:
{| class="wikitable"
!Dist. (nm)
!0
!10
!20
! 30
!40
! 50
!60
!70
!80
!90
!100
|-
!Res. (0..6)
|5
|4
|4
|4
|3
|3
|2
|2
|2
|2
|2
|}
As can be seen from the table, the resolution in pixels of the images varies with the distance from the center (radius).

With this method it is possible to obtain very large coverage without occupying too much memory and greatly reducing download times. Certainly the quality of the farther images is lower, but the problem could be not very perceptible as normally an airplane when it takes off is low on the ground and therefore the pilot wishes to have a high resolution (images with many pixels), but then rises in altitude and the resolution of the terrain is acceptable although much lower. With this method it is possible to cover large areas of land in a very short time, shorter than the flight necessary to cross that territory.

====The --over parameter====
A second important fact is the <code>'''--over 1'''</code> parameter which tells the system it can overwrite, the <code>'''--over'''</code> option <code>'''1'''</code> indicates that overwriting can only occur if the new file is larger than the file it replaces.

With this technique it is possible to build limited areas with higher resolution, for example airport areas, or particularly beautiful areas that we want to enhance.

The <code>'''--over'''</code> option has the following recognized parameters:
{| class="wikitable"
!Parameter!!Overwriting/deletion
|-
!--over 0
|Default option that inhibits any overwriting of images.
|-
!--over 1
|Overwrite only if the image to be replaced is larger than the present one
if the previous image is not present, the image will be inserted anyway.
|-
!--over 2
|Always overwrites, for example if you want to reduce the size of the images by a certain area.
|-
!--over 9
|Deletes the images present in the defined area.
|}

===Let's go to Fiumicino (Rome in Italy) by -i option===
<code>'''julia -t 10 photoscenary.jl -s 4 -i fiumicino'''</code>

[[File:Screenshot 20210520 125012.png|alt=|frameless|799x799px]]

We are already familiar with these options

The absence of '''<code>-r</code>''' indicates that the image extraction radius is the default of 10 nm.

<code>'''-s 4'''</code> indicates a resolution of 8192 pixels long side

But this is new

<code>'''-i fiumicino'''</code>

It means that we are selecting an airport containing the word '''fiumicino''<nowiki/>'. The search takes place in a database, with an Open Data license, which reports over 60,000 airports that have ICAO code.

The database is distributed together with the ''photoscenary.jl'' program with the ''airports.csv'' file, which is easily editable, via a text editor. The ''airports.csv'' file is not actually the database used by the program, but only the data source which is automatically converted into the more practical ''airports.jdb'' file which is the database file used by the JuliaDB package.

If you want to edit ''airports.csv'', once the file is saved, you will notice that the next time you run the ''photoscenary.jl'' program it will take a few seconds until a new ''airports.jdb'' is generated.

The text inserted after the '''<code>-i</code>''' parameter can contain a single word or a sentence, but in this case it must be delimited by double quotes.

'''<code>-i "leonardo da vinci"</code>'''

Once the program has started, the system will respond by entering also with this output:

[[File:Screenshot 20210520 213622.png|frameless|600x600px]]

For example, if you enter as a name

'''<code>-i rome</code>'''

The program will respond with the first 30 airports that correspond to the presence of the word Rome in one of the three search fields, as shown in this figure.

[[File:Screenshot 20210520 215037-2.png|frameless|800x800px]]

In this case, just enter a unique selector, such as the ICAO ID, to obtain the searched airport, as in this example:

'''<code>-i LIRF</code>'''

Therefore, the search using the -i option can be extremely convenient, as it allows you to quickly have the coordinates of any airport present in the ICAO database.

The search word can also be partial as in this example:

'''<code>-i zuric</code>'''

[[File:Screenshot 20210520 220731.png|frameless|600x600px]]

Any accented letters are normalized to the unaccented Latin form, for example:

''Zürich Airport'' becomes ''Zurich Airport''

and therefore the search can be successful if you write:

'''<code>-i "zurich airport"</code>'''

=== Dynamically download orthographic images by --connect ===
It is very convenient to download the orthographic images of the territory actually flown over by the plane.

In this case, the system will use the aircraft's course as reference, interspersed with points of radius -r.

The program will then download only the images actually needed, thus minimizing the amount of data to download.

The parameter to activate this function is this:

<code>'''--connect "<IP address>:<port>"'''</code>

When the program finds this parameter, checks if the syntax of the address is correct and listens showing a line that has as, first character and an arrow that rotates 45 degrees every second, followed by the sentence that begins with the text:

<code>'''Try the frist connection to Flightgear with address: ...'''</code>

This delay can last for an indefinite time, until Flightgear is activated with, obviously, the Telnet connection port activated, as explained above.

When Flightgear is activated, the program realizes it and starts evaluating the geographic position of the aircraft and then, if necessary, downloading and positioning the DDS images in the photorealistic scenario.

If you close Flightgear again, the program will be put on hold again, a situation indicated by the message:

<code>'''Try connect to Flightgear with address: ...'''</code>

To exit the program it is necessary to type the key sequence: [CTRL] + [C]

Exiting the program will have no effect on the downloaded DDS files as the program operates through transactional methods.

==== A simple example ====
For example, you can run this command:

<code>julia -t 4 photoscenary.jl --connect "127.0.0.1:5000"</code>

In this case the program will download the images in a radius of 10 nm for the entire length of the route. Thus forming a corridor of images that can give the illusion of a much larger territorial coverage than reality.

The images, if the <code>-s n</code> parameter is not specified, will have the size of 2048 px, this is a good enough size for flights above 10,000 ft.

If the speed of the plane is not too high and the internet line is good, it may happen that the pilot can get a flight with complete coverage of the orthographic images, giving the illusion of having downloaded very large geographical areas and more a narrow corridor that follows the route followed by the plane ..

If, on the other hand, the speed of the plane is high, or the speed of downloading the images is not high, it may be necessary, from time to time, to activate the option to update the scenario using the command:

''[menu] -> [debug] -> [Reload Scenery]''

In this case the simulator will freeze for a few seconds and then a scenario will be observed with orthographic images of the territory overflown.

==== Preparation of Flightgear to allow you to communicate with the photoscenary.jl program ====
[[File:Julia photoscenery generator - launcher QT configuration - 20210618 232448.png|frameless|800x800px]]

First you need to run Flightgear with the option:

<code>'''--telnet=5000'''</code>

This command will activate the telnet server on Flightgear with port 5000 active. The port can be changed, but the important thing is that it is then the communication port entered in the <code>--connect</code> command.

In the example in Additional Settings we see that the first line is the telnet server activation command, server needed to communicate with the photoscenary.jl program.

In additional settings I have inserted two other options that may be useful:

The parameter ''--httpd = 5001'' which activates an HTTP server, visible through the browser, useful for displaying the route on a geographic map. The third option instead activates multithreading which, eg run PC with at least 2 cores, allows you to render the flight more fluid.

==== Performing dynamic loading of orthographic images during flight ====
First you need to start Flightgear (and with it the telnet server we configured previously), wait for its loading phase to finish. And then start the program:

<code>'''julia -t 4 photoscenary.jl --connect "127.0.0.1:5000"'''</code>

[[File:Julia photoscenery generator - execution connect param - 20210618.png|frameless|800x800px]]

Unlike the other methods of selecting the areas to be filled with images, this method can show an intermediate step called "System pending ..." which allows you to communicate to the pilot that the program is running smoothly, but has already downloaded all the images needed for the current flyover area and then waits to reach the next area from which it will start downloading images again.

==== However, the other options are also allowed ====
<code>julia -t 4 photoscenary.jl --connect "127.0.0.1:5000" -s 3 --over 1</code>

The <code>--connect</code> command does not prevent the use of other options, such as image resolution and enabling overwriting if the new image is of a higher resolution than the one already present.

===Follow a route generated with route manager by --route===
The FlightGear ''route manager'' program allows you to generate a route that passes through various points and/or airports, the route can be saved to a file that is placed in the Export folder of the FlightGear $FG Home directory.

[[File:Screenshot 20210523 211312.png|frameless|600x600px]]

In this example, a route has been generated made up of 6 points, of which the first and last are respectively the departure airport and the arrival airport.

The route can be saved in a file which, in the example, has the name with a name ''LOWI-LIME.xml''

The file is saved in the ''Export'' directory of the FGFS HOME directory.

Being an XML file it is possible to open it through any text editor, and possibly also modify it, an operation, by the way, quite simple.

Here's what the xml file used for our example looks like:

[[File:Screenshot 20210523 211351.png|frameless|929x929px]]

The file can be as long as you like, however at the end it defines a path like this:

[[File:Screenshot 20210523 211204.png|frameless|600x600px]]

Now that it has been clarified what a route is and how it is saved, let's see how it can be exploited to cover the photoscenary only for the parts near the route.

'''<code>julia -t 10 photoscenary.jl --route LOWI-LIME.xml -s 2 -r 10 --over 1 -d 0</code>'''

In this example, the saved route is taken over by the program that searches for it. This little magic is used to simplify the program execution command as it is assumed that the file is of XML type and contains specific tags. If these tags are not present, the file will be considered invalid. If, on the other hand, if the file is validated, then it becomes the basis for extracting the path.

Once the file is validated, the program is executed, but first the project showing the single execution steps is shown.

The step is indicated with its step number and a decimal representing the sub-step. Therefore a step that has zero decimal indicates that that step has been inserted in the route manager, while the others are steps built by the algorithm to give continuity to the coverage of the tiles.

[[File:Screenshot 20210524 004027.png|frameless|800x800px]]

It is noted that at the end of the project (part in red in the screen shown here) the download phase begins for each single step, which, in this example, are 21.

Obviously the execution of the program can take a relatively long time, but certainly much less if that area had been covered with a single large set of tiles.

'''Note:''' ''that instead of entering the file name together with the path, only the file name can be entered, for example LIME-LIMJ.gpx somewhere, as long as it is inside the homepage or a subfolder. The program has an automatic search function which will find the file and use it as a route.''

==== Skyvector format ====
Since version 0.3.9 the automatic conversion of files produced with [https://skyvector.com/ Skyvector] has been defined. The file in .gpx format is automatically converted to produce the equivalent route to the file produced by the FGFS route manager when supplied via the <code>--route</code> parameter.

Skyvector is a very comprehensive route generator that is often used to plan routes in civil aviation. The use of this tool allows you to create route files in gpx format that can be read by the FGFS route manager and by this program. The conversion is transparent, that is, it is the program that parses the XML and determines its real format.

===Let's go via the geographic coordinates by -o -a <code>'''--latll --lonll --latur --lonur option'''</code>===
The coordinates are made explicit from the first line of the image:

central point ''lat: 21.317454 lon: -157.91603'' radius: ''5.0''

Not only that, but the second line reminds us in which area we are operating, that is an ideal rectangle with coordinates defined as follows:

Lower left corner

''latLL: 21,200 lonLL: -158,100''

Upper right corner

''latUR: 21.500 lonUR: -157.800''

But we could have had the same result with the following parameters that explicitly define the center point:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 3 -a 21.317454 -o ''-''157.91603'''</code>

Or with the parameters that define the lower left corner and the upper right corner

<code>'''julia -t 10 photoscenary.jl -s 3 --latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.8'''</code>

Entering the position values explicitly is a very convenient way when you do not know the acronym or name of an airport or want to select a particular area via google maps for example.

{{tip|Google maps allows you to give the coordinates in the degrees and fractions of degrees format, used by this program and FlightGear, by simply clicking the right mouse button on the map. Alternatively use the FlightGear [https://scenery.flightgear.org/static/map/index.html scene models map], which has coordinates in decimal format and tile information.}}

===The sea can be a problem --attemps option===
Now let's enlarge the radius area with <code>'''-r 20'''</code> (20 NM) with lower resolution tiles, we use in this example <code>'''-s 2'''</code> (2048 pixels long side)

<code>'''julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl --attemps 0'''</code>

At this point we look at the output which points out a few things

[[File:Test julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl top.png|frameless|800x800px]]

Meanwhile, let's see the effect of the <code>'''--over 0'''</code> parameter which prevents smaller images from overwriting images already present, but let's also observe another fact:

''The '''err''': column no longer reports the value 0 but numerical values that go up 7..10 and then beyond. This means that some tiles have not been uploaded, not only that, but there is also a very high reduction in the download speed that reaches, barely 0.16 MB/sec.''

The reason for this behavior is that around Honolulu there is the Pacific Ocean, or the sea, and the image server I am using does not show the sea beyond a certain distance from the coast. This means that the program tries to download a certain tile, but it returns an error, unfortunately not immediately, but only after a few seconds, the error starts a recovery procedure that performs the download attempt for two more times, if the third attempt fails, the system places the tiles, not downloaded, in a special list that can be retried in a subsequent cycle.

Here is what we will have at the end of the download batch:

[[File:Test julia -t 10 photoscenary.jl -r 20 -s 2 -i phnl bottom.png|frameless|800x800px]]

Now let's see the incomplete file list that shows the tiles that have not been downloaded, the attempts parameter, in the ''Incomplete file list'', indicates the number of attempts made. By stating that the number of attempts is zero, it means that the program lists only the files that have resulted not downloaded and then exits the program. But if you enter a numeric value for the --attempt parameter instead, you can reprocess the tiles that have not been downloaded, but it is possible to change the number of attempts using the parameter:

<code>'''--attempts n'''</code> (''default is '''2''''')

Where <code>'''n'''</code> is any integer. Do not increase this value too much, and only do it if the internet connection line is unstable or if the image server often drops the connection.

Attempts to reconnect are quite slow, especially if the images are small, so it is better not to overdo it to avoid unnecessarily lengthening the download times.

===Try to recover the errors --attemps n===
Often the errors are due to the presence of marine areas that are covered by maps with lower resolution, so the only way to obtain an error recovery is to lower the resolution.

For this an algorithm has been inserted that in the first recovery step uses a width of '''1024''', width which is reduced to '''512,256,128''' etc ... for the following steps whose max number is defined by the value <code>'''--attempts n'''</code>.

Let's try this download, always with the airport of Honolulu adding the possibility of making 3 attempts:

'''<code>julia -t 10 photoscenary.jl -r 10 -s 2 -i Honolulu --attemps 3</code>'''

[[File:Julia -t 10 photoscenary.jl -r 10 -s 2 -i Honolulu --attemps 3.png|frameless|800x800px]]

At the end of the execution it is observed that 6 tiles have been inserted in the incomplete list, therefore it is possible, if the value of <code>'''--attemps'''</code> is greater than 0 (''by default I remember that it is '''2'''''), to obtain a re-execution only for the tiles in error with a resolution request starting from 1024 pixels down.

With the default value '''<code>--attemps 2</code>''' it is hereby possible to arrive at tiles of 512 pixels which always seem to be released by the server, with --attempts 3 it is also possible to try tiles of 256 pixels the server does not yet release 512 pixels.

The end result is complete coverage of the entire area. In two resolution groups, that of 2028 pixels proposed with '''<code>--s 2</code>''' and that of 1024 pixels used by the recovery function.

==Other options==
The program allows the use of other options that may be useful in certain circumstances, below I give a list with the relative possibilities of use.

===--map '''''n'''''===
You can change the standard image server. Each image server is identified with a unique id which currently selects the following addresses
{| class="wikitable"
|+List of servers currently active and inserted in the params.xml file
!Id
!Name
!Comment
! Address of the organization
|-
|'''1'''
|ESRI GIS
|Default, this servers is for all over the world
|[https://www.esri.com/en-us/about/about-esri/overview https://www.esri.com]
|-
|'''2'''
|USGS
|United States only. Public domain license, only US
|https://basemap.nationalmap.gov
|-
|'''3'''
|PNOA
| PNOA only Spain
|https://www.ign.es
|-
|'''4'''
|Geoportal
|geoportal.gov.pl only Poland
|https://www.geoportal.gov.pl
|}
[[File:Screenshot_20210524_205813.png|alt=|frameless|800x800px]]

This option allows you to select a specific server different from the standard one (Id = 1). All servers are inserted into the ''params.xml'' file in the following form:

Additional servers can be added simply by adding a new <server> ... </server> entry within the general <servers> ... </servers> entry. The Id must be unique, as it is the selector and can take any value. If someone adds their own server they can do it, but I recommend starting from a higher Id, for example 100, so as not to interfere with the Ids that could be added in the future.

''An important recommendation '''is to replace''', in URLs, any "'''&'''" character with "'''|'''" (Pipe or vertical bar)''

For example the URL:

'''<code><url-command>SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&LAYERS=OI ...</code>'''

It should be written in the form:

'''<code><url-command>SERVICE=WMS|VERSION=1.1.1|REQUEST=GetMap|LAYERS=OI ...</code>'''

This is the characteristic output that occurs during program execution and shows the image server in use

[[File:Screenshot 20210524 205939.png|frameless|800x800px]]

The selected server highlighted by the red line and shows the main data that allow it to be identified.

Be very careful to use the right server for a certain area, the program does not know if the selected server is valid or not for a certain area, so a wrong server could delete the previously inserted image files.

If you are unsure, check the server site or do a test limited to a certain area. The servers, when they are out of the area, do not give errors, but they release a completely white image, so always be very careful.

===--path or -p ===
The program normally downloads image files in DDS or PNG format directly to the directory:

'''<code>''<home>''/fgfs-scenery/photoscenery/Orthophotos</code>'''

However, sometimes a user wants to use a different destination, perhaps even a different mass storage unit, such as a NAS or a disk connected via USB, in these cases this option becomes very convenient.

There are two ways to define a path:

'''Path relative to the home directory ''('''''<nowiki/>''in the example the user is /home/abassign''')'''''<nowiki/>''':'''

'''<code>julia photoscenary.jl -i pantelleria -r 20 -s 3 --attemps 2 -p scenary-dir</code>'''

The system will respond:

The images path is: '''/home/abassign/scenary-dir/Orthophotos'''

'''Absolute path:'''

'''<code>julia photoscenary.jl -i pantelleria -r 20 -s 3 --attemps 2 -p /home/abassign/scenary-dir</code>'''

The path, in the case of using Windows, can be written in the Windows notation, for example:

''c:\users\abassign\scenary-dir''

or in Linux:

/home/abassign/scenary-dir

==== Automatic path if the program is connected to FGFS ====
Since version 0.3.8 a method has been introduced that extracts the path directly from the FGFS program if it is connected (use the '''--connect''' param for the connection). The method is therefore implicit if the program is connected and the path is not defined, the path used will be the one described in the property tree of FGFS ''/sim/fg-scenery''. Obviously, if in the command line there is the --path parameter, the path reported by this has a higher priority.

=== --save ===
The program '''always saves''' the images (''from version 0.3.8'') to a directory that can be implicit or explicitly defined with the '''--save "a path"''' parameter.

There are therefore two cases:

# If the '''--save''' parameter has a valid path, the program will save the images to be deleted on that path.
# If the save parameter is not present, the path is determined automatically by reading the path of insertion of the downloaded files by adding the sub-name '''''<path>-saved''''' to the path so as not to allow FGFS to use it as an operational directory.

If you do not want to save the replaced images, you must explicitly enter the parameter '''--nosave''' as explained in the next paragraph.

The path is always absolute, as it must be possible to manage external drives in which you want to insert the files to be saved.

With this technique it is possible to use an external disk, perhaps of a mechanical type of 1-4 TB, to save the files that have been downloaded by the program, all divided by size in pixels, as in this example:

'''<code>--save /media/abassign/save_2018/Salvataggi</code>'''

You will get a configuration similar to this:

[[File:Photoscenary julia save option example 01.png|frameless|740x740px]]

As you can see, the images are grouped by size in pixels (s 0 <-> 512 ... s 4 <-> 8196 ... etc) and therefore the program, depending on the size of the image to be inserted, can choose the most appropriate image.

It is interesting to try this configuration with -s 3 (4096 pix) which will load all the images from 4096 into the scenario directory:

<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 3 -r 20</code>

If you later want to have smaller images, for example le s 2 (2048 pix) or le s 1 from 1024 px just type this command:

<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 1 -r 20</code>

The '''--over 2''' option is used to allow the replacement of larger images with smaller ones, as explained in the appropriate paragraph.

The reorganization time of the images is very fast and is linked to the moving time of the images present in the system.

Note that if the 4096 pix images were not saved yet, before replacing with the smaller images, they will be saved in the path indicated by --save.

==== Summing up ====
With the --save option you can save the images that will be replaced when loading new images with different resolution. With this technique it is possible to save large areas of images on an external disk and finally, with this technique it is possible to change the resolution of the images without ever losing the downloaded images.

=== --nosave ===
If we want to inhibit the autosave mode, just enter the '''--nosave''' parameter in the command line. With this parameter, saving of images that are deleted from the path is blocked.

=== --png ===
It is a switch that allows you to download images in PNG format without switching to DDS images. This feature makes the downloaded images much larger (4 times) and easily viewable or editable by an image editing program such as GIMP or Imagemagick.

If you subsequently start the program without the --png option, the program will try, before downloading the images from some external server, to check if the PNG images present are compatible with the DDS to be generated, if they are you will have the rapid conversion live PNG images in DDS.

If the --save option has been activated, the PNG images will not be lost, but saved in the chosen path.

=== --tile===
The world of Flightgear is represented with a tessellation of rectangles according to a rule defined at this link:

https://wiki.flightgear.org/Tile_Index_Scheme

The tile defines the minimum loadable area for a photo scenery, its size varies with latitude. Here is an example of how the tiles are distributed on the globe taken from a FGUK movie:{{#ev:youtube|YxWV4wk_dHw}}All the images that make up the photoscenery have a unique numerical name that is calculated through a special algorithm according to the latitude and longitude of the tile. This number is defined as the tile identifier.

You can view the tile number in the FlightGear [https://scenery.flightgear.org/static/map/index.html scene models map] (lower left corner).

For example if you run the command:

<code>'''julia -t 10 photoscenary.jl -r 5 -s 1 --tile 3105266'''</code>

You point to a tile that belongs to the LIME airport area and is approximately equivalent to this command:

'''<code>julia -t 10 photoscenary.jl -r 5 -s 1 -l lime</code>'''

In this way it is possible to select any area without having to enter particular coordinates, but only through this number.

===--sexagesimal or -x===
The angular parameters '''--lon --lat --lonll --latll --lonur --latur''' are normally expressed as hexadecimal. But it often happens that you have the coordinates in ''sexagesimal'' degrees. If the option is inserted, the system converts the decimal part from ''sexagesimal'' to ''centesimal''. For example, if you enter the value of '''52.21''' ''sexagesimal'' degrees, the program will convert them to '''52° 21' N''' which will then be converted to '''52.35''' degree.

'''Note''': ''It is not necessary to use the seconds as the tolerance of the tiles is 1/8 of a degree equal to about 7 minutes.''

For example is possible to write:

'''<code>julia -t 10 photoscenary.jl -r 10 -x -a 52.21 -o 13.30</code>'''

which is equivalent to writing

'''<code>julia -t 10 photoscenary.jl -r 10 -x -a 52.35 -o 13.50</code>'''

If the ''sexagesimal'' degrees are south or east, a minus sign must be entered, the field does not recognize the symbols N, S, E, W typically used in this type of notation.

===--proxy===
Which allows you to connect with a proxy server, the parameter is used, for example, as follows:

<code>julia -t 8 photoscenary.jl -s 5 -i "lowi" --over 1 -r 10 '''--proxy "<nowiki>http://192.168.0.9:8118</nowiki>"'''</code>

Where "''<nowiki>http://192.168.0.9:8118</nowiki>''" is the connection string to the proxy server.

===--debug or -d===
Currently the program defines two levels of debugging:

* level 1 <code>'''--debug 1'''</code> adds a series of messages that are a function of the progress of the program, this can be useful when you suspect that the program is not downloading anything or that the network is really slow. The problem is that this option does not display the progress log well and therefore is only useful in special cases.

*level 2 <code>'''--debug 2'''</code> is also used to display any execution errors. If the system is properly configured they should be rare, but in some cases it is useful to be able to see them.

=== --version===
It shows the program version and checks all the modules that need to be loaded:

<code>'''julia -t 10 photoscenary.jl --version'''</code>

[[File:Photoscenary-version.png|frameless|600x600px]]

=== --help or -h===
If you type the option -h or --help you get the complete list of options that can be recognized by the program, this list is obtained even if the option we enter or the value is not recognized, this is an example:

<code><small>julia photoscenary.jl --help</small></code>

<code><small>The actiual Julia is 1.7.0-beta3.0 The current version is correct in order to obtain the best performances</small></code>

<code><small>Photoscenary.jl ver: 0.3.5 date: Testing 20210816 System prerequisite test</small></code>

<code><small>Photoscenery generator by Julia compilator,</small></code>

<code><small>Program for uploading Orthophotos files</small></code>

<code><small>Version: ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 <nowiki>https://imagemagick.org</nowiki></small></code>

<code><small>Copyright: (C) 1999-2021 ImageMagick Studio LLC</small></code>

<code><small>License: <nowiki>https://imagemagick.org/script/license.php</nowiki></small></code>

<code><small>Features: Cipher DPC Modules OpenMP(4.5) </small></code>

<code><small>Delegates (built-in): bzlib djvu fftw fontconfig freetype heic jbig jng jp2 jpeg lcms lqr ltdl lzma openexr pangocairo png tiff webp wmf x xml zlib</small></code>

<code><small>ImageMagic is operative!</small></code>

<code><small>usage: photoscenary.jl [--map MAP] [--latll LATLL] [--lonll LONLL]</small></code>

<code><small> [--latur LATUR] [--lonur LONUR] [-a LAT]</small></code>

<code><small> [-o LON] [-x] [--png] [-i ICAO] [--route ROUTE]</small></code>

<code><small> [-t TILE] [-r RADIUS] [-s SIZE] [--sdwn SDWN]</small></code>

<code><small> [--over OVER] [-p PATH] [--save SAVE]</small></code>

<code><small> [--connect CONNECT] [--proxy PROXY]</small></code>

<code><small> [--attemps ATTEMPS] [-d DEBUG] [--version] [-h]</small></code>

<code><small>optional arguments:</small></code>

<code><small>-g, --args ARGS The arguments files in txt format</small></code>

<code><small> --map MAP The map server id (type: Int64, default: 1)</small></code>

<code><small> --latll LATLL Lower left area lat (type: Float64, default: 0.0)</small></code>

<code><small> --lonll LONLL Lower left area lon (type: Float64, default: 0.0)</small></code>

<code><small> --latur LATUR Upper right area lat (type: Float64, default: 0.0)</small></code>

<code><small> --lonur LONUR Upper right area lon (type: Float64, default: 0.0)</small></code>

<code><small> -a, --lat LAT Latitude in deg of central point (type: Float64, default: 45.66)</small></code>

<code><small> -o, --lon LON Longitude in deg of central point (type: Float64, default: 9.7)</small></code>

<code><small> -x, --sexagesimal Set the sexagesimal unit degree.minutes</small></code>

<code><small> --png Set the only png format files</small></code>

<code><small> -i, --icao ICAO ICAO airport code for extract LAT and LON</small></code>

<code><small> --route ROUTE Route XML for extract route LAT and LON</small></code>

<code><small> -t, --tile TILE Tile index es coordinate reference (type: Int64)</small></code>

<code><small> -r, --radius RADIUS Distance Radius around the center point (nm) (type: Float64, default: 0.0)</small></code>

<code><small> -s, --size SIZE Max size of image 0->512 1->1024 2->2048 3->4096 4->8192 5->16384 6->32768 (type: Int64, default: 2)</small></code>

<code><small> --sdwn SDWN Down size with distance (type: Int64, default: 0)</small></code>

<code><small> --over OVER Overwrite the tiles: |1|only if bigger resolution |2|for all (type: Int64, default: 0)</small></code>

<code><small> -p, --path PATH Path to store the dds images (default: "fgfs-scenery/photoscenery")</small></code>

<code><small> --save SAVE Save the remove files in the specific path</small></code>

<code><small>--nosave Not save the DDS/PNG files</small></code>

<code><small> --connect CONNECT IP and port FGFS program, example format: "127.0.0.1:5000"</small></code>

<code><small> --proxy PROXY Proxy string ipv4:port for example: "192.168.0.1:8080"</small></code>

<code><small> --attemps ATTEMPS Number of download attempts (type: Int64, default: 3)</small></code>

<code><small> -d, --debug DEBUG Debug level (type: Int64, default: 0)</small></code>

<code><small> --version Program version</small></code>

<code><small> -h, --help show this help message and exit</small></code>

== Management coverage of tiles on the territory ==
From version 0.2.8 a more articulated method of managing the loading and distribution of the tiles has been added.

=== Unloading of tiles on the territory assigned with a spiral rule ===
An algorithm performs the sequence of downloading the tiles as a function of the distance from the center. The download starts from the tiles closest to the center up to the last tiles downloaded which will be the ones farthest from the center.

In this motion it is possible to start the download procedure in parallel with the execution of the Flightgear program.

If you leave the airport where the plane is initially located and use the same airport as the center point (--icao lime for example) during take-off we will already have the tiles of the take-off area and therefore the scenario will appear well covered with orthographic images. During the climb of the plane it will therefore be probable that the following images will always give the pilot the illusion that the territory is well covered with images, even if we are only one part of the work. It will be enough for the pilot, from time to time, to update the scenario with the appropriate Flightgear menu.

=== Database of all orthographic images uploaded in .dds format. ===
This database is loaded at the beginning of the download session and contains all the images present in the home directory of the user who launched the program.

Before downloading the image from the designated website, the program checks in the database if the requested image is already present in the database, if the image is found in any directory of the home, it is copied to the current path. In this way it is possible to avoid carrying out a download job when the image is already present. Obviously the image must have and the pixel size requirements compatible with those required.

With this technique it is possible to distribute the images also on external supports and then make them converge on a working directory, usually with faster access (for example the system SSD). The only constraint is that the external media has a link that links it to a local folder.

With this technique it is also possible to exploit virtual folders that rely on other repositories, for example those shared with P2P techniques.

This example shows a mixed image download with database support. Images ('''copied''') are images copied from other directories on your system, ('''inserted''') are images inserted after a download from the image distribution web server. The images ('''skip''') are those already present in the folder of the images we are creating.

[[File:Screenshot 20210606 212142.png|frameless|800x800px]]

== Saving arguments in a text file ==
[[File:Julia Photoscenery Generator - args file.png|thumb|400x400px|Example of the contents in the '''args.txt''' file]]
Often the number and length of the arguments can become difficult to manage and therefore it is convenient to be able to save them on a file. For this reason, the '''--args''' (or '''-g''') parameter was introduced followed by a filename to be used as an argument container.

Let's take an example to better understand how this parameter works:

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

The arguments associated with the launch of the program are: <code>-i lowi -s 4 -r 20</code>

If we add the '''--args test.txt''' parameter:

<code>julia photoscenary.jl -i lowi -s 4 -r 20 --args test.txt</code>

In the directory where we ran the program we will find a new file called test.txt which contains the list of the parameters just entered.

It is now possible to recall the parameters entered using the command:

<code>julia photoscenary.jl test.txt</code>

The test.txt file, first created, can be edited with a simple text file editor and then modified according to our needs.

=== Arguments implicit saving ===
Launching the program with parameters, but without the '''--args''' option, still generates an arguments file called '''args.txt'''

This file can be recalled for the next program run, simply by running the program with no arguments.

For example:

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

The args.txt file is generated and the program, if run without parameters, will search the args.txt file and load it again using the previous parameters.

<code>julia photoscenary.jl</code>

The program runs exactly as in the previous execution.

== Recipes to be able to try the program and live satisfied ==
There are quite typical configurations that can give a lot of satisfaction to those who want a photorealistic vision, here I give some examples that can be used by anyone.

==== The simplest ====
<code>julia photoscenary.jl</code>

''Download the scenario at 2048 pix for a radius of 10 nm with Orio airport (LIME) in the center.''

==== The scenario of the airport closest to you ====
<code>julia photoscenary.jl -i lowi</code>

''If we live near Innsbruck LOWI is the closest airport.''

<code>julia photoscenary.jl -i lowi -s 4 -r 20</code>

'''''-i''' followed by the airport abbreviation ICAO, allows you to download that area for a radius of 20 nm ('''-r 20''') and resolution 8K pix ('''-s 4''')''

==== A flight plan has been generated with Skyvector <nowiki>https://skyvector.com/</nowiki> ====
<code>julia -t 6 photoscenary.jl -s 4 -r 20 --sdwn 1 --over 1 --route "LIMJ.gpx" --path "/media/abassign/test/fgfs-scenery/photoscenery"</code>

''The area is processed along a route defined with '''[https://skyvector.com/ Skyvector]''' (but the same methodology also applies to the one defined with the FGFS route planner). The program parses the xml file inserted as a parameter of '''--route''' and determines the format.''

==== The scenario is shown along the route ====
<code>julia -t 10 photoscenary.jl --connect "127.0.0.1:5000" -r 20 -s 3</code>

'''''-t 10''' tells the compiler that it can use up to 10 CPUs, this speeds up the download speed by 2-5 times. '''--connect''' allows you to connect to the Flightgear program (obviously if remote control has been activated (with port 5000) with the launch option of FGFS --telnet = 5000. The parameter '''-s 3''' means that the images will be 4096 pix, a good resolution for flights above 3000 ft.''

==== '''The images are saved for later reuse''' ====
<code>julia -t 10 photoscenary.jl --over 2 --save "/media/abassign/save_2018/Salvataggi/Immagini" -s 3 -r 20</code>

'''--save''' shows the possibility to save the images also in an external drive, in this way it is possible to create collections of images even in the order of TB avoiding using the system disk space.

'''--over 2''' It allows the replacement of images already present in the path directory, even if of higher resolution.

'''The images are saved for later reuse and the operational image directory is defined by the path option.'''

<code>julia -t 10 photoscenary.jl --over 1 --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 3 -r 20</code>

==== Generation of tiles along the route with maximum efficiency and quality ====
If you want to have a high quality scenario along the route, but at the same time light enough to allow the generation of images in good synchronization with the flight, you must enter the option '''--sdwn''' which, [[Julia photoscenery generator#The --sdwn parameter|as explained before]], allows you to automatically reduce the size of the tiles with the distance, in this way if the tile is distant a small tile is downloaded, if instead the tile is close, the downloaded tile is larger , at most the dimensions are those declared with the --s option. In this way it is possible to fly with a fairly synchronized scenario.

<code>julia -t 6 photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 4 -r 20 --over 1 --sdwn 1</code>

In case you want to get a faster loading of the images that are loaded along the route, remember that the program can overwrite the previous higher resolution images with lower resolution images '''without losing''' the images already downloaded, as they will be inserted in a area outside the scenario (for example a different disk) that can be reached with the path defined with the [[Julia photoscenery generator#--save|--save]] parameter.

This option means that instead of overwriting the images, the program first saves the files, then downloads the images from some external server and then overwrites them. With this technique the overall loading of the images (tiles) is faster as it is useless to download large images of 4-8-16 K pixels placed in distant areas from the pilot's point of view.

Therefore, to minimize the images it is necessary to communicate to the program that it will be able to overwrite the images with the option: [[Julia photoscenery generator#The --over parameter|--over 2]] But since the '''--save''' option is inserted, the program will not delete the previous images, but will insert them in the designated saving areas.

At this point a good command can be this:

<code>julia -t 6 photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" '''--save''' "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" -s 4 -r 20 '''--over 2''' '''--sdwn 1'''</code>

''However, it must always be remembered that currently FGFS does not reload the images of the scenario automatically, but you must click on the debug menu under reload scenario.''

It is possible to avoid entering the --path and --save commands if you adopt the automatic path search method that is activated with --connect active. This makes the command simpler, but obviously you lose the ability to allocate unused images to a certain area on an explicit directory, this is an example:

<code>julia -t 6 photoscenary.jl --connect "127.0.0.1:5000" -s 4 -r 20 '''--over 2''' '''--sdwn 1'''</code>

=== Example of loading multiple scenarios ===
It is possible to use two sessions of photoscenary.jl at the same time to have an updated low resolution scenario (''obviously this method only makes sense if the route follows a path in which a tiles load has never been performed''). The first session will have a low resolution '''-s 1''' or '''-s 2''' while the second resolution could be much higher, e.g. '''-s 4''' or '''-s 5'''

With this configuration it is very likely that the download speed of the orthophoto server you have selected is sufficient to show the images of the territory at low resolution (''remember that currently FGFS requires the manual scenario update if we want to see the scenario just written''), while the second program proceeds to download the images at a higher resolution which will then be visible only in a second flight, obviously on the same route (''it is very unlikely that from resolutions of '''-s 4''' onwards the images can be downloaded with the same speed with which you fly over the territory'').

In this example I have given '''4 cores''' to the high resolution scenario, and '''3 cores''' to the lower resolution scenario. The number of cores cannot exceed the maximum allowed by your CPU, therefore the program, if this number exceeds the available one, automatically reduces the number of cores.

The presence of the '''--over 1''' parameter is fundamental, which manages the insertion of images according to the resolution. However, remember that the low resolution images that will be replaced will not be deleted if you have entered the '''--save''' parameter with the relative save path.

==== High resolution scenario tasks -s 4 (8K) and -r 10 ====
<code>julia '''-t 4''' photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" '''-s 4 -r 10 --over 1'''</code>

==== Low resolution scenario tasks -s 2 (2K) and -r 20 ====
<code>julia '''-t 3''' photoscenary.jl --path "/media/abassign/test/fgfs-scenery/photoscenery" --save "/media/abassign/save_2018/Salvataggi/Immagini" --connect "127.0.0.1:5000" '''-s 2 -r 20 --over 1'''</code>

==Using the generated photo scenery in FlightGear==
1. Inform FG about additional directory with scenery tiles:
''--fg-scenery=/your/path/to/photoscenery/directory/''
either in command line or as extra options in launcher.

E.g. if you have a directory structure like ''C:\FlightGear\fg_customscenery\photoscenery\Orthophotos\e000n40\e007n46'' then use ''--fg-scenery=C:\FlightGear\fg_customscenery\photoscenery''

2. Check the option Menu > View > Rendering Options > Satellite Photoscenery.

== Use the maps generated by photoscenary.jl for professional applications ==
The photoscenary.jl application allows you to generate maps even only in .png format useful to assemble with gimp (or other painting graphics programs) as the generation of the images guarantees the correct connection. Obviously, reference is made to cylindrical coordinates that must eventually be deformed in case you want to work with a different cartographic model. Currently the program defines the possibility of operating with some image sources defined in the parameter file '''params.xml''' in the sub-section ''<servers> ... </servers>''. Those that offer the most permissive license conditions are produced by USGS (USA) which is an American federal enete and therefore does not bind which all maps with particular limitations of use, the same rules apply as the otographic images produced by NASA that are used in Flightgear for images of the Earth as seen from space.

If one wants to read the terms of use, he can refer to what is reported in [https://www.usgs.gov/faqs/are-usgs-topographic-maps-copyrighted this USGS link].

=== Download images for professional use or publications ===
This paragraph is based on the terms of use of the USGS server, so they may not apply to other servers reachable with this program. The server, as you can see by reading the USGS params.xml file, has '''id = 2'''. For use not related to flightgear it is normally useful to work with files in .png format as the .dds is used only for simulation or games. For technical applications a pair of coordinates is normally used which are: Upper right (UR) and Lower Left (LL) of the requested area. You can also find a set of images using polar coordinates and a radius in nautical miles.

Let's now give one examples:

<code>'''julia -t 6 photoscenary.jl -s 5 --latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.3 --map 2 <small>--png -p</small>''' ''<small>'''"'''</small>'''''<small>/some path/ortho"</small>'''</code>

The coordinates are defined in:

'''-s 5''' is the resolution of the images (s 5 -> 16384 pix for tile)

'''--latll 21.2 --lonll 158.1 --latur 21.5 --lonur -157.3'''

Coordinates in six hundredth degrees.

'''--map 2''' indicates that the images will be downloaded from the USGS server.

'''--png''' means that the images WILL NOT BE CONVERTED to .dds but will remain in .png!

'''-p "''<path>''"''' Defines the path where the images will be downloaded.

'''-x''' If the coordinates are expressed in sexagesimal degrees, just enter this additional parameter,

In this case the decimal part of the coordinate value is in prime, for example:

'''--latll 21.50 --latll 158.50'''

It is equivalent to writing:

'''-x --latll 21.30 --lonll 158.30'''

===Wiki articles===
*[[Photoscenery]]

===Forum topics===
*{{forum link|t=39066|title=Photoscenery generator for Julia compiler}} (April 2021 - May 2021)
*{{forum link|t=38057|title=16k Photoscenery}} (September 2020 - Gen 2021)

[[Category:Scenery]]
[[Category:Scenery software]]
[[Category:Photoscenery]]

Category:Photoscenery

2024-04-13T06:29:31Z

Hbeni: Created page with "Software and articles related to Photoscenery Category:Scenery software"

Software and articles related to Photoscenery

[[Category:Scenery software]]

Nasal library

2024-04-09T08:15:45Z

Hbeni: /* split() */

{{Nasal Navigation|nocat=1}}
This page documents the global '''library functions and variables''' of FlightGear's built-in scripting language, [[Nasal]]. This includes ''[[#Core library functions|core library functions]]'', which were included in Nasal before its integration into FlightGear, the ''[[#Extension functions|extension functions]]'', which have been subsequently added, and are specifically designed for FlightGear, and the ''[[#variables|global variables]]'', which are conversion variables, added with extension functions, for converting between units. The relevant folders in [[Git]] are:
* {{flightgear file|src/Scripting}}
* {{simgear file|simgear/nasal}}

All these functions and variables are in the global namespace, that is, they are directly accessible (e.g., one can call <syntaxhighlight lang="nasal" inline>magvar()</syntaxhighlight> instead of <syntaxhighlight lang="nasal" inline>namespace.magvar()</syntaxhighlight>). However, if a namespace must be used, <code>globals</code> is the correct namespace, but using it is not recommended. For a more complete explanation, see [[Nasal Namespaces in-depth]].

{{tip|Copy & paste the examples into your [[Nasal Console]] and execute them to see what they do.|width=70%}}

== Core library functions ==
This is the list of the basic '''core library functions.''' Most of these functions were part of the original Nasal library (before its integration in to FlightGear), while some have been added or changed over time. See also:
* http://plausible.org/nasal/lib.html ([http://web.archive.org/web/20101010094553/http://plausible.org/nasal/lib.html archive])
* {{simgear file|simgear/nasal/lib.c}} ([http://sourceforge.net/p/flightgear/simgear/ci/next/log/?path=/simgear/nasal/lib.c history])

=== append() ===
{{Nasal doc
|syntax = append(vector, element[, element[, ...]]);
|source = {{simgear file|simgear/nasal/lib.c|l=42|t=Source}}
|text = This function appends, or adds, the given element(s) to the end of the vector given in the first argument. Returns the vector operated on.
|param1 = vector
|param1text = The vector to which the arguments will be appended.
|param2 = element
|param2text = An element to be added to the vector.
|example1 =
var vector = [1, 2, 3]; # Initialize the vector
append(vector, 4); # Append the number 4 to the end of the vector
debug.dump(vector); # Print the contents of the vector
|example2 =
var vector = [1, 2, 3]; # Initialize the vector
append(vector, 4, 5, 6); # Append the numbers 4, 5, and 6 to the end of the vector
debug.dump(vector); # Print the contents of the vector
}}

=== bind() ===
{{Nasal doc
|syntax = bind(function, locals[, outer_scope]);
|source = {{simgear file|simgear/nasal/lib.c|l=502|t=Source}}
|text = This creates a new function object. A function in Nasal is three things: the actual code, a hash/namespace of local variables available to the function namespace, and the closure object of that namespace. These correspond to the three arguments respectively.
|param1 = function
|param1text = Function to evaluate.
|param2 = locals
|param2text = Hash containing values that will become the namespace (first closure) for the function.
|param3 = outer_scope
|param3text = Optional function which is bound to the next closure. This can be bound to yet another, making a linked list.
|example1 = # This is a namespace/hash with a single member, named "key," which is initialized to 12
var Namespace = {
key: 12
};

# This is different namespace/hash containing a function
# dividing a variable "key" (which is unavailable/nil in this namespace) by 2
var AnotherNamespace = {
ret: func {
key /= 2;
}
};

# To see that key is not available, try to call AnotherNamespace.ret() first
call(AnotherNamespace.ret, [], nil, nil, var errors = []);
if(size(errors)){
print("Key could not be divided/resolved!");
debug.printerror(errors);
}

# Associate the AnotherNamespace.ret() function with the first namespace
# so that "key" is now available
var function = bind(AnotherNamespace.ret, Namespace);

# Invoke the new function
function();

# Print out the value of Namespace.key
# It was changed to 12 from 6 by AnotherNamespace.ret()
print(Namespace.key);
}}

=== call() ===
{{Nasal doc
|syntax = call(func[, args[, me[, locals[, error]]]);
|source = {{simgear file|simgear/nasal/lib.c|l=247|t=Source}}
|text = Calls the given function with the given arguments and returns the result. This function is very useful as it allows much more control over function calls and catches any errors or {{func link|die()}} calls that would normally trigger run-time errors cancelling execution of the script otherwise.
|param1 = func
|param1text = Function to execute.
|param2 = args
|param2text = Vector containing arguments to give to the called function.
|param3 = me
|param3text = <code>'''me'''</code> reference for the function call (i.e., for method calls). If given, this will override any <code>'''me'''</code> value existing in the namespace (locals argument).
|param4 = locals
|param4text = A hash with key/value pairs that will be available to the called function, typically used as the namespace for the function to be called.
|param5 = error
|param5text = A vector to append errors to. If the called function generates an error, the error, place, and line will be written to this. These errors can be printed using {{func link|printerror()|debug}}.
|example1 =
# prints "Called from call()"
call(func {
print("Called from call()");
});
|example2 =
# prints "a = 1 : b = 2
call(func(a, b){
print("a = ", a, " : b = ", b);
},
[1, 2]
);
|example3 =
var Hash = {
new: func {
var m = { parents: [Hash] };

m.el1 = "string1";
m.el2 = "string2";

return m;
}
};

# prints "me.el1 = string1", then "me.el2 = string2" on the next line
call(func(a, b){
print("me.el", a, " = ", me["el" ~ a]);
print("me.el", b, " = ", me["el" ~ b]);
},
[1, 2],
Hash.new()
);
|example4 =
# prints the value of math.pi
call(func {
print(pi);
}, nil, nil,
math
);
|example5 =
call(func {
print(math.ip); # math.ip doesn't exist
}, nil, nil, nil,
var errs = []
);
debug.printerror(errs); # The error is caught and printed using debug.printerror()
}}

=== caller() ===
{{Nasal doc
|syntax = caller([level]);
|source = {{simgear file|simgear/nasal/lib.c|l=404|t=Source}}
|text = Returns a vector containing a record from the current call stack. The level numbering starts from the currently executing function (level 0). Level 1 (the default) is the caller of the current function, and so on.

The result is a four-element vector containing '''[0]''' a hash of local variables, '''[1]''' the function object, '''[2]''' the full source file name (incl. path) and '''[3]''' the line number.
|param1 = level
|param1text = Optional integer specifying the stack level to return a result from. Defaults to 1 (i.e. the caller of the currently executing function).
|example1 =
var myFunction = func(a, b){
debug.dump(caller(0)[0]); # prints a hash of local variables, including arguments a and b
return 2 * 2;
};

print("2 x 2 = ", myFunction(2, 2));
|example2 =
var get_arg_value = func(){
print("Argument to myFunc = ", caller(1)[0]['a']); # print the value of myFunc's single argument, using caller()
};

var myFunc = func(a){
get_arg_value();
};

myFunc(3);
|example3text = This is a real example taken from {{fgdata file|Nasal/canvas/MapStructure.nas}}. Function <code>r()</code> (above the TODOs) returns a hash with the key/value pairs as per its arguments. For example, something like this is returned: <code>{ name: "<name>", vis: 1, zindex: nil }</code>.
|example3 =
var MapStructure_selfTest = func() {
var temp = {};
temp.dlg = canvas.Window.new([600,400],"dialog");
temp.canvas = temp.dlg.createCanvas().setColorBackground(1,1,1,0.5);
temp.root = temp.canvas.createGroup();
var TestMap = temp.root.createChild("map");
TestMap.setController("Aircraft position");
TestMap.setRange(25); # TODO: implement zooming/panning via mouse/wheel here, for lack of buttons :-/
TestMap.setTranslation(
temp.canvas.get("view[0]")/2,
temp.canvas.get("view[1]")/2
);
var r = func(name,vis=1,zindex=nil) return caller(0)[0];
# TODO: we'll need some z-indexing here, right now it's just random
# TODO: use foreach/keys to show all layers in this case by traversing SymbolLayer.registry direclty ?
# maybe encode implicit z-indexing for each lcontroller ctor call ? - i.e. preferred above/below order ?
foreach(var type; [r('TFC',0),r('APT'),r('DME'),r('VOR'),r('NDB'),r('FIX',0),r('RTE'),r('WPT'),r('FLT'),r('WXR'),r('APS'), ] )
TestMap.addLayer(factory: canvas.SymbolLayer, type_arg: type.name,
visible: type.vis, priority: type.zindex,
);
}; # MapStructure_selfTest
}}

=== chr() ===
{{Nasal doc
|syntax = chr(code);
|source = {{simgear file|simgear/nasal/lib.c|l=175|t=Source}}
|text = Returns a character as per the single argument. Extended ASCII is supported (see http://www.asciitable.com/ for a list of supported characters), although this may vary between different systems. For a list of the most commonly used characters, see the {{wikipedia|ASCII#ASCII printable code chart|ASCII printable code chart}} ('''Dec''' column). The following table lists supported control characters, along with their equivalent control characters in Nasal strings. {{Note|In Nasal, only strings enclosed with double-quotes (<code>"string"</code>) supports control chracters. Strings in single quotes (<code>'string'</code>) do not.}}
{{{!}} class="wikitable"
! Code !! Name !! Equivalent to
{{!-}}
{{!}} 10 {{!!}} {{Wikipedia|Newline}} {{!!}} <code>\n</code>
{{!-}}
{{!}} 9 {{!!}} {{Wikipedia|Tab key#Tab characters|Horizontal tab}} {{!!}} <code>\t</code>
{{!-}}
{{!}} 13 {{!!}} {{Wikipedia|Carriage return}} {{!!}} <code>\r</code>
{{!}}}
|param1 = code
|param1text = Integer character code for the desired glyph.
|example1 = print("Code 65 = ", chr(65)); # prints "Code 65 = A"
|example2text = This example displays all of the characters in a list, in the format <code>Code '''n''' = >'''char'''<</code>, '''n''' being the index, and '''char''' being the character.
|example2 =
for(var i = 0; i <= 255; i += 1){
print("Code ", i, " = >", chr(i), "<");
}
}}

=== closure() ===
{{Nasal doc
|syntax = closure(func[, level]);
|source = {{simgear file|simgear/nasal/lib.c|l=421|t=Source}}
|text = Returns the hash table containing the lexical namespace of the given function. The level numbering start with level 0 being the namespace of '''func'''.
|param1 = func
|param1text = Function to evaluate.
|param2 = level
|param2text = Optional integer specifying the scope level. Defaults to 0 (the namespace of '''func''').
|example1 =
var get_math_e = func {
return e; # return the value of math.e
}

var myFunction = bind(get_math_e, math); # bind get_math_e to the math namespace, so that math.e is immediately available to get_math_e
debug.dump(closure(myFunction)); # print the namespace of get_math_e

print(myFunction());
}}

=== cmp() ===
{{Nasal doc
|syntax = cmp(a, b);
|source = {{simgear file|simgear/nasal/lib.c|l=112|t=Source}}
|text = Compares two strings, returning -1 if '''a''' is less than '''b''', 0 if they are identical and 1 if '''a''' is greater than '''b'''.
|param1 = a
|param1text = First string argument for comparison.
|param2 = b
|param2text = Second string argument for comparison.
|example1 = print(cmp("1", "two")); # prints -1
|example2 = print(cmp("string", "string")); # prints 0
|example3 = print(cmp("one", "2")); # prints 1
|example4 = print(cmp("string1", "string2")); # prints -1
}}

=== compile() ===
{{Nasal doc
|syntax = compile(code[, filename]);
|source = {{simgear file|simgear/nasal/lib.c|l=220|t=Source}}
|text = Compiles the specified code string and returns a function object bound to the current lexical context. If there is an error, the function dies, with the argument to {{func link|die()}} being '''filename'''.
|param1 = code
|param1text = String containing Nasal code to be compiled.
|param2 = filename
|param2text = Optional string used for error messages/logging. Defaults to <code><compile></code>
|example1 =
var myCode = 'print("hello");';
var helloFunc = compile(myCode, "myCode");
helloFunc();
|example2text = <code>compile</code> is very convenient to support Nasal loaded from other files. For instance, [[PropertyList XML files]] (such as GUI dialogs) may contain embedded Nasal sections that need to be parsed, processed and compiled. For an example of how to do this, save the below XML code as <tt>''[[$FG_ROOT]]/gui/dialogs/test.xml''</tt>.
<syntaxhighlight lang="xml">
<?xml version="1.0"?>

<PropertyList>

<nasal><![CDATA[
print("You have FlightGear v", getprop("/sim/version/flightgear"));
]]></nasal>

</PropertyList>
</syntaxhighlight>
Now, start FlightGear and execute this code in the [[Nasal Console]].
|example2 =
# Build the path
var FGRoot = getprop("/sim/fg-root");
var filename = "/gui/dialogs/test.xml";
var path = FGRoot ~ filename;

var blob = io.read_properties(path);
var script = blob.getValues().nasal; # Get the nasal string

# Compile the script. We're passing the filename here for better runtime diagnostics
var code = call(func {
compile(script, filename);
}, nil, nil, var compilation_errors = []);

if(size(compilation_errors)){
die("Error compiling code in: " ~ filename);
}

# Invoke the compiled script, equivalent to code();
# We're using call() here to detect errors:
call(code, [], nil, nil, var runtime_errors = []);

if(size(runtime_errors)){
die("Error calling code compiled loaded from: " ~ filename);
}
}}

=== contains() ===
{{Nasal doc
|syntax = contains(hash, key);
|source = {{simgear file|simgear/nasal/lib.c|l=184|t=Source}}
|text = Returns 1 (True) if the hash contains the specified key, or 0 (False) if not.
|param1 = hash
|param1text = The hash to search in.
|param2 = key
|param2text = The scalar to be searched for, contained as a key in the hash.
|example1 =
# Initialize a hash
var hash = {
element: "value"
};
print(contains(hash, "element") ? "Yes" : "No"); # This will print "Yes"
|example2 =
# Initialize a hash
var hash = {
element: "value"
};
print(contains(hash, "element2") ? "Yes" : "No"); # This will print "No"
}}

===contains()===
{{Requires commit|desc=Vector support|details=see {{Merge-request|project=fgdata|id=305}}|commit=ee39abbd3b70c9b6d5e3a1c4ccedddaac1a92b11|repo=Simgear}}
{{Nasal doc
|syntax = contains(vector, item);
|source = {{simgear file|simgear/nasal/lib.c|l=184|t=Source}}
|text = Returns 1 (True) if the vector contains the specified item, or 0 (False) if not.
|param1 = vector
|param1text = The vector to search in.
|param2 = item
|param2text = The object to be searched for in the vector.
|example1 =
# Initialize a hash
var vec = ["element", "foo"];
print(contains(vec, "element") ? "Yes" : "No"); # This will print "Yes"
|example2 =
# Initialize a hash
var vec = ["element", "foo"];
print(contains(vec, "element2") ? "Yes" : "No"); # This will print "No"
}}

===delete() ===
{{Nasal doc
|syntax = delete(hash, key);
|source = {{simgear file|simgear/nasal/lib.c|l=83|t=Source}}
|text = Deletes the key from the hash if it exists. Operationally, this is NOT identical to setting the hash value specified by the key to <code>'''nil'''</code> as the key will stay in the hash (at least for a while). This variant potentially frees storage by deleting the reference to the key and by shrinking the hash. Returns the hash that has been operated on.
|param1 = hash
|param1text = The hash from which to delete the key.
|param2 = key
|param2text = The scalar to be deleted, contained as a key in the hash.
|example1 =
# Initialize the hash
var hash = {
element1: "value1",
element2: "value2"
};
delete(hash, "element1"); # Delete element1
debug.dump(hash); # prints the hash, which is now minus element1
}}

===die()===
{{Nasal doc
|syntax = die(error);
|source = {{simgear file|simgear/nasal/lib.c|l=288|t=Source}}
|text = Terminates execution and unwinds the stack. The place and the line will be added to the '''error'''. This invokes the same internal exception handler used for internal runtime errors. Use this to signal fatal errors, or to implement exception handling. The error thrown (including internal runtime errors) can be caught with {{func link|call()}}.
|param1 = error
|param1text = String describing the error.
:{{inote|This parameter is technically optional, but it is highly recommended to use it.}}
|example1 =
print("Will print");
die("Don't go any further!");
print("Won't print"); # Will not be printed because die() stops the process
}}

=== find()===
{{Nasal doc
|syntax = find(needle, haystack);
|source = {{simgear file|simgear/nasal/lib.c|l=450|t=Source}}
|text = Finds and returns the index of the first occurrence of the string '''needle''' in the string '''haystack''', or -1 if no such occurrence was found.
|param1 = needle
|param1text = String to search for.
|param2 = haystack
|param2text = String to search in.
|example1 = print(find("c", "abcdef")); # prints 2
|example2 = print(find("x", "abcdef")); # prints -1
|example3 = print(find("cd", "abcdef")); # prints 2
}}

===ghosttype()===
{{Nasal doc
|syntax = ghosttype(ghost);
|source = {{simgear file|simgear/nasal/lib.c|l=207|t=Source}}
|text = Returns a string containing either a descriptive name of a ghost (a raw C/C++ object), or a unique id (the pointer to the C/C++ <code>naGhostType</code> instance) if no name has been set. Ghost is an acronym that stands for '''G'''arbage-collected '''H'''andle to '''O'''ut'''S'''ide '''T'''hingy.
|param1 = ghost
|param1text = Ghost to return a description for.
|example1 = print(ghosttype(airportinfo())); # prints "airport"
}}

===id()===
{{Nasal doc
|syntax = id(object);
|source = {{simgear file|simgear/nasal/lib.c|l=570|t=Source}}
|text = Returns a string containing information on the type and ID of the object provided in the single argument. The information is returned in the form of <code>'''<type>''':'''<id>'''</code>, where '''<type>''' is the type of object, and '''<id>''' is the ID.
|param1 = object
|param1text = Can be either of a string, a vector, a hash, a code, a function, or a ghost.
|example1 = print(id("A")); # prints "str:000000001624A590"
}}

===int() ===
{{Nasal doc
|syntax = int(number);
|source = {{simgear file|simgear/nasal/lib.c|l=90|t=Source}}
|text = Returns the integer part of the numeric value of the single argument, or <code>'''nil'''</code> if none exists.
|param1 = number
|param1text = Number or string with just a number in it to return an integer from.
|example1 = print(int(23)); # prints "23"
|example2 = print(int(23.123)); # prints "23"
|example3 = debug.dump(int("string")); # prints "nil"
}}

===keys()===
{{Nasal doc
|syntax = keys(hash);
|source = {{simgear file|simgear/nasal/lib.c|l=33|t=Source}}
|text = Returns a vector containing the list of keys found in the single hash argument.
|param1 = hash
|param1text = The hash to return the keys from.
|example1 =
# Initialize a hash
var hash = {
element1: "value",
element2: "value"
};
debug.dump(keys(hash)); # print the vector
}}

===left()===
{{Nasal doc
|syntax = left(string, length);
|source = {{simgear file|simgear/nasal/lib.c|l=149|t=Source}}
|version = 2.12
|commit = {{simgear commit|bd7163|t=commit}}
|text = Returns a substring of '''string''', starting from the left.
|param1 = string
|param1text = String to return part of.
|param2 = length
|param2text = Integer specifying the length of the substring to return.
|example1 = print(left("string", 2)); # prints "st"
}}

=== num()===
{{Nasal doc
|syntax = num(number);
|source = {{simgear file|simgear/nasal/lib.c|l=102|t=Source}}
|text = Returns the numerical value of the single string argument, or <code>'''nil'''</code> if none exists.
|param1 = number
|param1text = String with just a number in it to return a number from.
|example1 = print(num("23")); # prints "23"
|example2 = print(num("23.123")); # prints "23.123"
|example3 = debug.dump(num("string")); # prints "nil"
}}

===pop()===
{{Nasal doc
|syntax = pop(vector);
|source = {{simgear file|simgear/nasal/lib.c|l=50|t=Source}}
|text = Removes and returns the last element of the single vector argument, or <code>'''nil'''</code> if the vector is empty.
|param1 = vector
|param1text = Vector to remove an element from.
|example1 =
var vector = [1, 2, 3];
pop(vector);
debug.dump(vector); # prints "[1, 2]"
|example2 =
var vector = [1, 2, 3];
debug.dump(pop(vector)); # prints "3"
|example3 =
var vector = [];
debug.dump(pop(vector)); # prints "nil"
}}

===right()===
{{Nasal doc
|syntax = right(string, length);
|source = {{simgear file|simgear/nasal/lib.c|l=161|t=Source}}
|version = 2.12
|commit = {{simgear commit|bd7163|t=commit}}
|text = Returns a substring of '''string''', starting from the right.
|param1 = string
|param1text = String to return part of.
|param2 = length
|param2text = Integer specifying the length of the substring to return.
|example1 = print(right("string", 2)); # prints "ng"
}}

=== setsize()===
{{Nasal doc
|syntax = setsize(vector, size);
|source = {{simgear file|simgear/nasal/lib.c|l=56|t=Source}}
|text = Sets the size of a vector. The first argument specifies a vector, the second a number representing the desired size of that vector. If the vector is currently larger than the specified size, it is truncated. If it is smaller, it is padded with <code>'''nil'''</code> entries. Returns the vector operated upon.
|param1 = vector
|param1text = The vector to be operated on.
|param2 = size
|param2text = The desired size of the vector in number of entries.
|example1 =
var vector = [1, 2, 3]; # Initialize a vector
setsize(vector, 4);
debug.dump(vector); # print the vector
|example2 =
var vector = [1, 2, 3]; # Initialize a vector
setsize(vector, 2);
debug.dump(vector); # print the vector
}}

===size()===
{{Nasal doc
|syntax = size(object);
|source = {{simgear file|simgear/nasal/lib.c|l=23|t=Source}}
|text = Returns the size of the single argument. For strings, this is the length in bytes. For vectors, this is the number of elements. For hashes, it is the number of key/value pairs. If the argument is <code>'''nil'''</code> or a number, this error will be thrown: <code>object has no size()</code>.
|param1 = object
|param1text = Object to find the size of. Must be a string, a vector or a hash.
|example1 =
var string = "string";
print(size(string)); # prints "6"
|example2 =
var vector = [1, 2, 3];
print(size(vector)); # prints "3"
|example3 =
var hash = {
element1: "value1",
element2: "value2",
element3: "value3"
};
print(size(hash)); # prints "3"
}}

=== sort()===
{{Nasal doc
|syntax = sort(vector, function);
|source = {{simgear file|simgear/nasal/lib.c|l=542|t=Source}}
|text = Returns a vector containing the elements in the input '''vector''' sorted in according to the rule given by '''function'''. Implemented with the ANSI C {{func link|qsort()|link=http://www.cplusplus.com/reference/cstdlib/qsort/}}, <code>sort()</code> is stable. This means that if the rules in the first example are used, equal elements in the output vector will appear in the same relative order as they do in the input. It is run in a loop, so '''function''' is run several times.
|param1 = vector
|param1text = Input vector to sort.
|param2 = function
|param2text = Function according to which the elements will be sorted by. It should take two arguments and should return one of 1, 0, or -1.
{{{!}} class="wikitable"
! Return value !! Meaning
{{!-}}
{{!}} less than 0 {{!!}} first argument should go before second argument
{{!-}}
{{!}} 0 {{!!}} first argument equals second argument
{{!-}}
{{!}} greater than 0 {{!!}} first argument should go after second argument
{{!}}}

|example1text = This example sorts elements from smallest to greatest.
|example1 =
var sort_rules = func(a, b){
if(a < b){
return -1; # A should before b in the returned vector
}elsif(a == b){
return 0; # A is equivalent to b
}else{
return 1; # A should after b in the returned vector
}
}
debug.dump(sort([3, 2, 5, 6, 4, 1], sort_rules)); # prints "[1, 2, 3, 4, 5, 6]"
|example2text = This example sorts elements from greatest to smallest.
|example2 =
# Outputs the elements in reverse order (greatest to smallest)
var sort_rules = func(a, b){
if(a < b){
return 1; # -1 in the above example
}elsif(a == b){
return 0;
}else{
return -1; # 1 in the above example
}
}
debug.dump(sort([3, 2, 5, 6, 4, 1], sort_rules)); # prints "[6, 5, 4, 3, 2, 1]"
|example3text = This example sorts a vector of strings (runways for example) from smallest to greatest.
|example3 =
var runways = ["09R","27R","26L","09L","15"];
var rwy = sort(runways,func(a,b) cmp(a,b));
debug.dump(rwy); # prints ['09L','09R','15','26L','27R']
}}

=== split()===
{{Nasal doc
|syntax = split(delimiter, string);
|source = {{simgear file|simgear/nasal/lib.c|l=460|t=Source}}
|text = Splits the input string into a vector of substrings bounded by occurrences of the delimiter substring. See [[Nasal_library/string#string.join(sep,list)|string.join()]].
|param1 = delimiter
|param1text = String that will split the substrings in the returned vector.
|param2 = string
|param2text = String to split up.
|example1 = debug.dump(split("cd", "abcdef")); # prints "['ab', 'ef']"
|example2 = debug.dump(split(".", "3.2.0")); # prints "[3, 2, 0]"
|example3 = debug.dump(split("/", "path/to/file")); # prints "['path', 'to', 'file']"
}}

===sprintf()===
{{Nasal doc
|syntax = <nowiki>sprintf(format[, arg[, arg, [...]]]);</nowiki>
|source = {{simgear file|simgear/nasal/lib.c|l=355|t=Source}}
|text = Creates and returns a string formatted using ANSI C {{func link|vsnprintf()|link=http://en.cppreference.com/w/c/io/vfprintf}} <ref>
{{Cite web
|url = http://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/nasal/lib.c#l308
|title = fgdata/simgear/simgear/nasal/lib.c, line 308
|accessdate = October 2015
}}
</ref>. Below is a table of supported format specifiers.
{{{!}} class="wikitable" width="75%"
{{!}}+ %[flags][width][.precision]specifier
! colspan="2" {{!}} Flags
{{!-}}
! Flag !! Output
{{!-}}
{{!}} <code>+</code> {{!!}} Forces to precede the result with a plus or minus sign ('''+''' or '''-''') even for positive numbers. By default, only negative numbers are preceded with a '''-''' sign.
{{!-}}
{{!}} ''space'' {{!!}} Prefixes non-signed numbers with a space.
{{!-}}
{{!}} <code>-</code> {{!!}} Left-align the output of this placeholder (the default is to right-align the output) when the width option is specified.
{{!-}}
{{!}} <code>0</code> {{!!}} Use 0 instead of spaces to pad a field when the width option is specified.
{{!-}}
{{!}} <code>#</code> {{!!}} Used with <code>o</code>, <code>x</code> or <code>X</code> specifiers the value is preceded with <tt>0</tt>, <tt>0x</tt> or <tt>0X</tt> respectively for values different than zero. Used with <code>e</code>, <code>E</code> and <code>f</code>, it forces the written output to contain a decimal point even if no digits would follow. By default, if no digits follow, no decimal point is written. Used with <code>g</code> or <code>G</code> the result is the same as with <code>e</code> or <code>E</code> but trailing zeros are not removed.
{{!-}}
! colspan="2" {{!}} Width
{{!-}}
{{!}} colspan="2" {{!}} Integer specifying the minimum number of characters to be returned. This includes the decimal point and decimal fraction as well as + or - signs.
{{!-}}
! colspan="2" {{!}} Precision
{{!-}}
{{!}} colspan="2" {{!}} Integer preceded by a dot specifying the number of decimal places to be written.
{{!-}}
! colspan="2" {{!}} Specifiers
{{!-}}
! Specifier !! Output
{{!-}}
{{!}} <code>d</code>, <code>i</code> {{!!}} Signed decimal number.
{{!-}}
{{!}} <code>s</code> {{!!}} A string
{{!-}}
{{!}} <code>%</code> {{!!}} Percent (%) character.
{{!-}}
{{!}} <code>c</code> {{!!}} A single character assigned to a character code, the code given in an integer argument. See http://www.asciitable.com/ for a list of supported characters and their codes.
{{!-}}
{{!}} <code>o</code> {{!!}} Unsigned integer as an octal number.
{{!-}}
{{!}} <code>u</code> {{!!}} Unsigned decimal integer.
{{!-}}
{{!}} <code>x</code>, <code>X</code> {{!!}} Unsigned integer as a hexadecimal number. If <code>x</code> is used, any letters in the number are lowercase, while <code>X</code> gives uppercase.
{{!-}}
{{!}} <code>e</code>, <code>E</code> {{!!}} Double value in scientific notation (i.e., ''[-]ddd.ddd'''e'''[+/-]ddd''), with an exponent being denoted by <tt>e</tt> or <tt>E</tt> depending on whether an upper or lowercase is used respectively.
{{!-}}
{{!}} <code>f</code> {{!!}} Floating-point number, in fixed decimal notation, by default with 6 decimal places.
{{!-}}
{{!}} <code>F</code> {{!!}} Appears to be available<ref>
{{Cite web
|url = http://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/nasal/lib.c#l389
|title = fgdata/simgear/simgear/nasal/lib.c, line 389
|accessdate = October 2015
}}
</ref>, but doesn't work.
{{!-}}
{{!}} <code>g</code>, <code>G</code> {{!!}} Double in either normal or exponential notation, whichever is more appropriate for its magnitude. <code>g</code> uses lower-case letters, <code>G</code> uses upper-case letters. This type differs slightly from fixed-point notation in that insignificant zeroes to the right of the decimal point are not included. Also, the decimal point is not included on whole numbers.
{{!}}}

|param1 = format
|param1text = String specifying the format. Can be used with or without a format specifiers. See below for examples.
|param2 = arg
|param2text = Argument specifying a value to replace a format placeholder (such as <code>%d</code>) in the format string. Not required if there are no format specifiers.

|example1 = print(sprintf("%i", 54)); # prints "54"
|example2 = print(sprintf("Pi = %+.10f", math.pi)); # prints "Pi = +3.1415926536"
|example3 =
print(sprintf("%6d", 23)); # prints " 23"
print(sprintf("%06d", 23)); # prints "000023"
|example4 =
var FGVer = getprop("/sim/version/flightgear");
print(sprintf("You have FlightGear v%s", FGVer)); # prints "You have FlightGear v<your version>"
|example5 =
print(sprintf("Hexadecimal 100000 = %X", 100000)); # prints "Hexadecimal 100000 = 186A0"
print(sprintf("Hexadecimal 100000 = %x", 100000)); # prints "Hexadecimal 100000 = 186a0"
|example6 = print(sprintf("Code 65 is %c", 65)); # prints "Code 65 is A"
|example7 =
print(sprintf("%e", 54)); # prints "5.400000e+001"
print(sprintf("%E", 54)); # prints "5.400000E+001"
|example8 = print(sprintf("%o", 54)); # prints "66"
|example9 = print(sprintf("50%% of 100 is %i", 100 / 2)); # prints "50% of 100 is 50"
|example10 =
print(sprintf("%.2f", 1.4)); #prints "1.40"
print(sprintf("%.1f", 1.4)); #prints "1.4"
print(sprintf("% 4.1f", 1.4)); #prints " 1.4"
print(sprintf("%04.1f", 1.4)); #prints "01.4"
print(sprintf("% 6.1f", 1.4)); #prints " 1.4"
print(sprintf("%06.1f", 1.4)); #prints "0001.4"
}}

===streq()===
{{Nasal doc
|syntax = streq(a, b);
|source = {{simgear file|simgear/nasal/lib.c|l=129|t=Source}}
|text = Tests the string values of the two arguments for equality. This function is needed because the <code>'''=='''</code> operator (see [[Nasal_Operators#Equality|Nasal Operators]]) tests for numeric equality first. If either or both the arguments are not strings, 0 (False) will be returned. Returns either 0 (False) or 1 (True). {{Note|This function is rarely required in typical code.}}
|param1 = a
|param1text = First argument for testing equality.
|param2 = b
|param2text = Second argument for testing equality.
|example1 = print(streq("0", "0")); # prints "1" (True)
|example2 =
print(0 == 0.0); # prints "1" (True)
print(streq("0", "0.0")); # prints "0" (False)
}}

===substr()===
{{Nasal doc
|syntax = substr(string, start [, length]);
|source = {{simgear file|simgear/nasal/lib.c|l=129|t=Source}}
|text = Similar the {{func link|subvec()}}, but operates on strings. Computes and returns a substring. The first argument specifies a string, the second is the index of the start of a substring, the optional third argument specifies a length (the default is to return the rest of the string from the start).
|param1 = string
|param1text = String to return a substring from.
|param2 = start
|param2text = Integer specifying the start of a substring. Negative values specify a position from the end of the string.
|param3 = length
|param3text = Optional argument specifying the length of the substring. Defaults to the end of the string.
|example1 = print(substr("abcde", 1, 3)); # prints "bcd"
|example2 = print(substr("abcde", 1)); # prints "bcde"
|example3 = print(substr("abcde", 2, 1)); # prints "c"
|example4 = print(substr("abcde", -2)); # prints "de"
|example5 = print(substr("abcde", -3, 2)); # prints "cd"
}}

===subvec()===
{{Nasal doc
|syntax = subvec(vector, start[, length]);
|source = {{simgear file|simgear/nasal/lib.c|l=63|t=Source}}
|text = Returns a sub-range of a vector. The first argument specifies a vector, the second a starting index, and the optional third argument indicates a length (the default is to the end of the vector).
|param1 = vector
|param1text = The vector to take the sub-vector from.
|param2 = start
|param2text = The starting point of the sub-vector within the given vector.
|param3 = length
|param3text = Optional argument specifying the length of the sub-vector, from the starting point.
'''Notes:'''
* Omitting the ''vector'' and ''start'' arguments is not an error (possibly it should be) but the return value is ''nil''.
* A negative ''start'' argument ''is'' an error. This seems wrong. Perhaps the language designer could comment.
* A value of ''start'' greater than ''size(vector)'' causes an error. A value equal to ''size(vector)'' returns an empty vector.
* If the value of ''length'' is greater than ''size(vector) - start'' then it is ignored. That is, all elements from ''start'' to the end of ''vector'' are returned. If ''length'' is zero then an empty vector is returned. A negative value of ''length'' causes an error.
|example1 =
var vector = [1, 2, 3];
debug.dump(subvec(vector, 0)); # prints "[1, 2, 3]"
|example2 =
var vector = [1, 2, 3];
debug.dump(subvec(vector, 1)); # prints "[2, 3]"
|example3 =
var vector = [1, 2, 3];
debug.dump(subvec(vector, 1, 1)); # prints "[2]"
}}

=== typeof()===
{{Nasal doc
|syntax = typeof(object);
|source = {{simgear file|simgear/nasal/lib.c|l=193|t=Source}}
|text = Returns a string indicating the whether the object is <code>'''nil'''</code>, a scalar (number or string), a vector, a hash, a function, or a ghost.
|param1 = object
|param1text = Object to return the type of.
|example1 =
var object = nil;
print(typeof(object)); # prints "nil"
|example2 =
var object = "Hello world!";
print(typeof(object)); # prints "scalar"
|example3 =
var object = math.pi;
print(typeof(object)); # prints "scalar"
|example4 =
var object = [1, 2, 3];
print(typeof(object)); # prints "vector"
|example5 =
var object = {};
print(typeof(object)); # prints "hash"
|example6 =
var object = func {};
print(typeof(object)); # prints "func"
|example7 =
var object = airportinfo();
print(typeof(object)); # prints "ghost"
}}



==Extension functions==
The '''extension functions''' are global functions that have been added to Nasal since its integration into FlightGear. Unlike the core library functions, they are generally specifically designed to interact directly with FlightGear. Extension functions come from three source files:
*{{flightgear file|src/Scripting/NasalPositioned.cxx}}
*{{flightgear file|src/Scripting/NasalSys.cxx}}
*{{fgdata file|Nasal/globals.nas}}

===abort()===
{{Nasal doc
|syntax = abort();
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=565|t=Source}}
|text = This function is a wrapper for the C++ {{func link|abort()|link=http://www.cplusplus.com/reference/cstdlib/abort/}} function. It simply aborts FlightGear with an error, which varies depending on the operating system. This function should not really be used; instead, please use the "exit" [[Fgcommands|fgcommand]], which will exit FlightGear more gracefully (see example below).
|example1text = This example will immediately stop FlightGear with an error, such as "FlightGear has stopped working."
|example1 = abort();
|example2text = For exiting FlightGear in a better way, please use the following code:
|example2 = fgcommand("exit");
}}

=== abs() ===
{{Nasal doc
|syntax = abs(number);
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|text = This simple function returns the {{wikipedia|absolute value|noicon=1}} of the provided number.
|param1 = number
|param1text = This argument is required and should be a number.
|example1 = print(abs(1)); # prints "1"
|example2 = print(abs(-1)); # prints "1"
}}

===aircraftToCart() ===
This new function in FG 2017.2.1 takes coordinates in aircraft structural coordinate system, and translate them into geocentric coordinates.
Example for (5,6,7):
<syntaxhighlight lang="nasal">
var pos = aircraftToCart({x: -5, y: 6, z: -7});
var coord = geo.Coord.new();
coord.set_xyz(pos.x, pos.y, pos.z);
</syntaxhighlight>
Notice: x and z is inverted sign on purpose.
if you want lat. lon, alt from that, just call: (degrees and meters)

<syntaxhighlight lang="nasal">
coord.lat()
coord.lon()
coord.alt()
</syntaxhighlight>

===addcommand() ===
{{Nasal doc
|syntax = addcommand(name, code);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=659|t=Source}}
|version = 2.12
|commit = {{flightgear commit|7b663c|t=commit}}
|text = {{see also|Howto:Add new fgcommands to FlightGear}}

This function enables the addition of a new custom [[fgcommands|fgcommand]] to FlightGear from within Nasal. An fgcommand created using this method can be used in exactly the same way as the built-in fgcommands. Also, an fgcommand created via this method will always return True or 1, like all other fgcommands.
|param1 = name
|param1text = This will become the name of the new fgcommand. Must be a string.
|param2 = code
|param2text = The code that will be executed when the fgcommand is run. Must be a function.
|example1text = This example adds a new fgcommand and then runs it. Although it executes a simple {{func link|print()}} statement, any valid Nasal code can be used.
|example1 = addcommand("myFGCmd", func(node) {
print("fgcommand 'myFGCmd' has been run.");
props.dump( node );
});
fgcommand("myFGCmd", props.Node.new({foo:1, bar:2}) );
|example2text = This example demonstrates how parameters are defined in a new fgcommand.
|example2 = addcommand("myFGCmd", func(node){
print(node.getNode("number").getValue()); # prints the value of "number," which is 12
});
fgcommand("myFGCmd", props.Node.new({"number": 12}));
}}

===airportinfo()===
{{Nasal doc
|syntax = airportinfo();
airportinfo(type);
airportinfo(id);
airportinfo(lat, lon[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1024|t=Source}}
|text = Function for retrieval of airport, heliport, or seaplane base information. It returns a Nasal ghost; however, its structure is like that of a Nasal hash. The following information is returned:
* '''parents''': A vector containing a hash of various functions to access information about the runway. See {{flightgear file|src/Scripting/NasalPositioned.cxx|l=2659}} for full list.
* '''lon''': Longitude of the location.
* '''lat''': Latitude of the location.
* '''has_metar''': True or false depending whether the airport has a [[METAR]] code defined for it.
* '''elevation''': Elevation of the location in metres.
* '''id''': ICAO code of the airport (or ID of the seaplane base/heliport).
* '''name''': Name of the airport/heliport/seaplane base.
* '''runways'''
** '''<runway name>'''
*** '''id''': Name of runway.
*** '''lat''': Latitude of the runway.
*** '''lon''': Longitude of the runway.
*** '''heading''': Heading of the runway.
*** '''length''': Length of the runway in metres.
*** '''width''': Width of the runway in metres.
*** '''surface''': Runway surface type.
*** '''threshold''': Length of the runway's {{wikipedia|displaced threshold}} in metres. Will return 0 if there is none.
*** '''stopway''': Length of the runway's stopway (the area before the threshold) in metres. Will return 0 if there is none.
*** '''reciprocal''': <code>runway</code> ghost of the reciprocal runway.
*** '''ils_frequency_mhz''': ILS frequency in megahertz.
*** '''ils''': <code>navaid</code> ghost of the ILS transmitter.
* '''helipads'''
** '''<helipad name>'''
*** '''id''': Name of helipad.
*** '''lat''': Latitude of the helipad.
*** '''lon''': Longitude of the helipad.
*** '''heading''': Heading of the helipad.
*** '''length''': Length of the helipad in metres.
*** '''width''': Width of the helipad in metres.
*** '''surface''': Helipad surface type.
* '''taxiways'''
** '''<taxiway name>'''
*** '''id''': Name of taxiway.
*** '''lat''': Latitude of the taxiway.
*** '''lon''': Longitude of the taxiway.
*** '''heading''': Heading of the taxiway.
*** '''length''': Length of the taxiway in metres.
*** '''width''': Width of the taxiway in metres.
*** '''surface''': Taxiway surface type.

Information is extracted in the same way as accessing members of a Nasal hash. For example:
<syntaxhighlight lang="nasal">
# prints to lengths of the runways of the nearest airport in feet and metres
var info = airportinfo();
print("-- Lengths of the runways at ", info.name, " (", info.id, ") --");
foreach(var rwy; keys(info.runways)){
print(rwy, ": ", math.round(info.runways[rwy].length * M2FT), " ft (", info.runways[rwy].length, " m)");
}
</syntaxhighlight>

Note that searches for locations that are a long way away (e.g., the nearest seaplane base to the middle of the Sahara) may cause FlightGear to pause for an amount of time.
|param1 = id
|param1text = The {{wikipedia|International Civil Aviation Organization airport code|ICAO code|noicon=1}} of an airport to retrieve information about.
|param2 = type
|param2text = When this argument is used, the function will return the closest airport of a certain type. Can be one of "heliport," "seaport," or "airport" (default).
: {{inote|Running this function without any parameters is equivalent to this:
: <syntaxhighlight lang="nasal">
airportinfo("airport");
</syntaxhighlight>
}}
|param3 = lat ''and'' lon
|param3text = When these parameters are used, the function will return information on the nearest airport, heliport or seaplane base (depending on the '''type''' parameter) to those coordinates.
|example1 = var info = airportinfo();
print("Nearest airport: ", info.name, " (", info.id, ")"); # prints the name and ICAO code of the nearest airport
|example2 = var info = airportinfo("heliport");
print("Elevation of the nearest heliport: ", math.round(info.elevation * M2FT), " ft"); # prints the elevation and name of the nearest heliport
|example3 = var info = airportinfo("KSQL");
print("-- Runways of ", info.name, " (", info.id, "): --");
foreach(var rwy; keys(info.runways)) {
print(rwy); # prints the runways of KSQL
}
|example4 = var info = airportinfo(37.81909385, -122.4722484);
print("Coordinates of the nearest airport: ", info.lat, ", ", info.lon); # print the name and ICAO of the nearest airport to the Golden Gate Bridge
|example5 = var info = airportinfo(37.81909385, -122.4722484, "seaport");
print("Nearest seaplane base: ", info.name, " (", info.id, ")"); # print the name and ID of the nearest seaplane base to the Golden Gate Bridge
|example6text = This example prints the all information from an <code>airportinfo()</code> call.
|example6 = var info = airportinfo("KSFO");
print(info.name);
print(info.id);
print(info.lat);
print(info.lon);
print(info.has_metar);
print(info.elevation);
foreach(var rwy; keys(info.runways)){
print("-- ", rwy, " --");
print(info.runways[rwy].lat);
print(info.runways[rwy].lon);
print(info.runways[rwy].length);
print(info.runways[rwy].width);
print(info.runways[rwy].heading);
print(info.runways[rwy].stopway);
print(info.runways[rwy].threshold);
<nowiki>}</nowiki>
}}

===airwaysRoute() ===
{{Nasal doc
|syntax = airwaysRoute(start, end[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1933|t=Source}}
|text = {{see also|Nasal Flightplan}}
This function returns a vector containing waypoints between two given waypoints. The returned waypoints are ghosts, but can be accessed in the same way as a Nasal hash. See [[Nasal Flightplan]] for more information.
|param1 = start
|param1text = Start waypoint, in the form of a waypoint ghost, such as that provided by {{func link|flightplan()}}.
|param2 = end
|param2text = Same as above.
|param3 = type
|param3text = Instructs the function to compute a high level route (when set to "highlevel"), or a low level route (when set to "lowlevel"). Defaults to "highlevel."
|example1text = In the [[route manager]] dialog, add two waypoints to the flightplan, ideally ones that are far apart (tip: use the [[Map]] for this). Then run this code in your Nasal Console.
|example1 = var fp = flightplan();
var start = fp.getWP(0);
var end = fp.getWP(fp.getPlanSize() - 1);
var rt = airwaysRoute(start, end);
foreach(var wp; rt){
print(wp.wp_name); # print the waypoints in the computed route
}
|example2text = Exactly the same as above, but computes a low level path.
|example2 = var fp = flightplan();
var start = fp.getWP(0);
var end = fp.getWP(fp.getPlanSize() - 1);
var rt = airwaysRoute(start, end, "lowlevel");
foreach(var wp; rt){
print(wp.wp_name); # print the waypoints in the computed route
<nowiki>}</nowiki>
}}

===airway()===

{{Nasal doc
|syntax = airway(ident [, pos]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=2644|t=Source}}
|text = {{see also|Nasal Flightplan}}
This function returns a ghost containing an airway of a specified id.
|param1 = ident
|param1text = a Positioned ghost (leg, navaid, airport) and so on, passed to the search function.
|param2 = pos
}}

===assert()===
{{Nasal doc
|syntax = assert(condition[, message]);
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|version = 3.2
|commit = {{fgdata commit|8b16a7|t=commit}}
|text = Returns either true if the condition evaluates as true, or aborts with a {{func link|die()}} call, which can be customised.
|param1 = condition
|param1text = Condition to evaluate.
|param2 = message
|param2text = Optional message that will be used in any {{func link|die()}} call. Defaults to "assertion failed!"
|example1 = var a = 1;
var b = 2;
print(assert(a < b)); # prints "1" (true)
|example2 = var a = 1;
var b = 2;
assert(a > b, 'a is not greater than b'); # aborts with a custom error message
}}

===carttogeod()===
{{Nasal doc
|syntax = carttogeod(x, y, z);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=945|t=Source}}
|text = Converts {{wikipedia|ECEF|Earth-centered, Earth-fixed}} coordinates (x, y and z) to {{wikipedia|geodetic coordinates}} (latitude, longitude, and altitude). A vector is returned containing latitude and longitude, both in degrees, and altitude, which is returned in metres above the equatorial radius of Earth as defined by the {{wikipedia|WGS 84}} (6,378,137 metres).<ref>{{simgear file|simgear/math/sg_geodesy.hxx|l=43}}</ref>
|param1 = x
|param1text = Mandatory x-axis value, in metres.
|param2 = y
|param2text = Mandatory y-axis value, in metres.
|param3 = z
|param3text = Mandatory z-axis value, in metres.
|example1 = var (lat, lon, alt) = carttogeod(6378137, 0, 0); # point is the intersection of the prime meridian and equator.
print("Latitude: ", lat); # prints lat, lon and alt, which are all zero, see above
print("Longitude: ", lon);
print("Altitude: ", alt);
}}

===cmdarg()===
{{Nasal doc
|private = _cmdarg()
|syntax = cmdarg();
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=513|t=Part 1}} {{!}} {{fgdata file|Nasal/globals.nas|t=Part 2}}
|text = <code>cmdarg()</code> returns the property root of certain types of XML files. These could be nodes in the [[Property Tree]], or temporary and/or non-public nodes outside the Property tree.
It is used by Nasal scripts embedded in XML files. It returns a <code>props.Node</code> object (see {{fgdata file|Nasal/props.nas}}), and you can use all of its methods on the returned value. <code>cmdarg()</code> should only be used in four types/places of XML files:
* Bindings: This is needed so that the value of a joystick's axis can be accessed internally.
* Dialogs: This will return the root of the dialog in the Property Tree. This is useful for dialogs that are created/modified procedurally (e.g. for populating/changing widgets while loading the dialog).
* Embedded Canvases: The Nasal code behind [[Canvas]] windows [[Howto:Adding a canvas to a GUI dialog|embedded in PUI dialogs]] can use it to accessing the root directory of their Canvas.
* Animation XML files: If the animation XML file is used in an AI/MP model, <code>cmdarg()</code> will return the root of the AI model in the <code>/ai/models/</code> directory. Examples: <code>/ai/models/aircraft[3]/</code>, <code>/ai/models/multiplayer[1]/</code>

You should not use <code>cmdarg()</code> in places other than those stated above. Although it won't cause an error, it will return the value of the last legitimate <code>cmdarg()</code> call.

Also, you should not delay <code>cmdarg()</code> using {{func link|maketimer()}}, {{func link|settimer()}} or {{func link|setlistener()}}, because it will return an unrelated property.
|example1 = fgcommand("dialog-show", {"dialog-name": "cmdarg-demo"});
|example1text = <br>This example demonstrates the usage of <code>cmdarg()</code> in a binding. Save the below XML snippet as <tt>[[$FG_ROOT]]/gui/dialogs/cmdarg-demo.xml</tt>. Then run the Nasal snippet below in your [[Nasal Console]]. Upon clicking {{button|Close}}, a message will be printed sowing the root of the binding in the Property Tree.
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>

<PropertyList>

<name>cmdarg-demo</name>
<layout>vbox</layout>

<text>
<label>Click "Close" to activate the demonstration (a message in the console).</label>
</text>

<button>
<legend>Close</legend>
<binding>
<command>nasal</command>
<script>print("Button binding root: '" ~ cmdarg().getPath() ~ "'");</script>
</binding>
<binding>
<command>dialog-close</command>
</binding>
</button>

</PropertyList>
</syntaxhighlight>
|example2text = This example demonstrates the usage of <code>cmdarg()</code> in Nasal code within dialogs. Open <tt>[[$FG_ROOT]]/gui/dialogs/cmdarg-demo.xml</tt> from the previous example, copy & paste the code below, and save it. Then run the same Nasal snippet as the previous example in your Nasal Console. If you click {{button|Click me!}}, the button's label will change to "I've been changed!"
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>

<PropertyList>

<name>cmdarg-demo</name>
<layout>vbox</layout>

<text>
<label>Click "Click me!" to activate the demonstration (the button's label will change).</label>
</text>

<button>
<legend>Click me!</legend>
<binding>
<command>nasal</command>
<script>change_label();</script>
</binding>
</button>

<button>
<legend>Close</legend>
<binding>
<command>dialog-close</command>
</binding>
</button>

<nasal>
<open><![CDATA[
var dlg_root = cmdarg();
var dlg_name = {"dialog-name": "cmdarg-demo"};
var change_label = func {
dlg_root.getNode("button[0]/legend").setValue("I've been changed!");
fgcommand("dialog-close", dlg_name);
fgcommand("dialog-show", dlg_name);
}
]]></open>
</nasal>

</PropertyList>
</syntaxhighlight>
|example3text = For an example of <code>cmdarg()</code> used with Canvas, please see [[Howto:Adding a canvas to a GUI dialog#FGPlot|Howto:Adding a canvas to a GUI dialog]].
}}

===courseAndDistance()===
{{Nasal doc
|syntax = courseAndDistance(to);
courseAndDistance(from, to);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1668|t=Source}}
|text = Returns a vector containing the course from one point to another and the distance between them in nautical miles. The course is the initial bearing (see [http://www.movable-type.co.uk/scripts/latlong.html#bearing here]), and is in the range 0–360. Both arguments can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object with geodetic coordinates (cartesian coordinates will not be accepted)
|param1 = from
|param1text = Optional parameter defining the from where the function should calculate its results. If the function is given one argument ('''to'''), the aircraft's current position will be used. As well as the argument types as defined above, this argument can be two numbers separated with a comma, as if the function is taking three arguments. See example 5 below.
|param2 = to
|param2text = Like the first parameter, but defines the second point.
|example1text = This example demonstrates the usage of the function with the <code>airport</code> ghost type.
|example1 = var from = airportinfo("KSFO");
var to = airportinfo("KSQL");
var (course, dist) = courseAndDistance(from, to);
print(course); # prints course from KSFO to KSQL
print(dist); # prints distance in nm from KSFO to KSQL
|example2text = This example demonstrates the usage of the function with hashes containing ''lat'' and ''lon''.
|example2 = var from = {lat: 0, lon: 0};
var to = {lat: 1, lon: 1};
var (course, dist) = courseAndDistance(from, to);
print(course);
print(dist);
|example3text = This example demonstrates usage of a geo.Coord object.
|example3 = var from = geo.Coord.new().set_latlon(0, 0);
var to = geo.Coord.new().set_latlon(1, 1);
var (course, dist) = courseAndDistance(from, to);
print(course);
print(dist);
|example4text = This example demonstrates usage of differing parameter types.
|example4 = var from = airportinfo("KSFO");
var to = geo.Coord.new().set_latlon(0, 0);
var (course, dist) = courseAndDistance(from, to);
print(course);
print(dist);
|example5text = The same as above, but the other way round.
|example5 = var to = {lat: 1, lon: 1};
var (course, dist) = courseAndDistance(0, 0, to);
print(course);
print(dist);
|example6text = Usage of just one parameter.
|example6 = var dest = airportinfo("KSQL");
var (course, dist) = courseAndDistance(dest);
print("Turn to heading ", math.round(course), ". You have ", sprintf("%.2f", dist), " nm to go");
}}

===createFlightplan()===
{{Nasal doc
|syntax = createFlightplan(path);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=2331|t=Source}}
|text = Creates an empty flightplan object. It accepts one argument, ''path'' passed an absolute path to a .fgfp / .gpx file, it will populate the flightplan with waypoints from the file.
|param1 = path
|param1text = Optional parameter defining the file from which a flightplan will be populated.
|example1 =
var path = getprop("/sim/fg-home") ~ "/Export/test.fgfp";
var flightplan = createFlightplan(path);
debug.dump(flightplan);
}}

===createDiscontinuity()===
{{Nasal doc
|syntax = createDiscontinuity();
|text = Returns a <code>waypoint</code> ghost object. A route discontinuity is inserted by an {{abbr|FMS|Flight Management System}} when it is unsure how to connect two waypoints.
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=2045|t=Source}}
|version = 2016.1
|commit = {{flightgear commit|caead6|t=commit}}
}}
===createViaTo()===
{{Nasal doc
|syntax = createViaTo(airway, waypoint);
|text = Returns a <code>waypoint</code> ghost object. It represents a route "via '''airway''' to '''waypoint'''".
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=2009|t=Source}}
|version = 2016.1
|commit = {{flightgear commit|caead6|t=commit}}
|param1 = airway
|param1text = The name of an airway.
|param2 = waypoint
|param2text = Must be in the airway and one of:
* The name of a waypoint.
* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, or <code>fix</code> ghost object.
}}
===createWP()===
{{Nasal doc
|syntax = createWP(pos, name[, flag]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1964|t=Source}}
|text = Creates a new waypoint ghost object.
|param1 = pos
|param1text = Dictates the position of the new waypoint. It can be one of the following:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. See example 4 below.
|param2 = name
|param2text = String that will become the name of the new waypoint.
|param3 = flag
|param3text = Optional string that will tell FlightGear what type of waypoint it is. Must be one of "sid," "star," "approach," "missed," or "pseudo."
|example1text = Creates a waypoint directly in front and 1 km away and appends it to the flight plan.
|example1 = var pos = geo.aircraft_position().apply_course_distance(getprop("/orientation/heading-deg"), 1000);
var wp = createWP(pos, "NEWWP");
var fp = flightplan();
fp.appendWP(wp);
|example2 = var pos = geo.aircraft_position().apply_course_distance(getprop("/orientation/heading-deg"), 1000);
var wp = createWP({lat: pos.lat(), lon: pos.lon()}, "NEWWP");
var fp = flightplan();
fp.appendWP(wp);
|example3 = var apt = airportinfo();
var wp = createWP(apt, "NEWWP");
var fp = flightplan();
fp.appendWP(wp);
|example4 = var pos = geo.aircraft_position().apply_course_distance(getprop("/orientation/heading-deg"), 1000);
var wp = createWP(pos.lat(), pos.lon(), "NEWWP");
var fp = flightplan();
fp.appendWP(wp);
|example5text = Creates a new waypoint and adds it to the flight plan. Waypoints of the type "pseudo" are then removed from the flight plan, including the new waypoint. The {{func link|print()}} statements show this.
|example5 = var pos = geo.aircraft_position().apply_course_distance(getprop("/orientation/heading-deg"), 1000);
var wp = createWP(pos, "NEWWP", "pseudo");
var fp = flightplan();
fp.appendWP(wp);
print(fp.getPlanSize());
fp.clearWPType("pseudo");
print(fp.getPlanSize());
}}

===createWPFrom()===
{{Nasal doc
|syntax = createWPFrom(object[, flag]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1989|t=Source}}
|text = Creates a new waypoint object from another object.
|param1 = object
|param1text = A ghost object. Must be a ghost type that is one of "airport," "navaid," "runway," or "fix."
|param2 = flag
|param2text = Optional string that will tell FlightGear what type of waypoint it is. Must be one of "sid," "star," "approach," "missed," or "pseudo."
|example1text = Creates a new waypoint and appends it to the flight plan.
|example1 = var apt = airportinfo("KSFO");
var wp = createWPFrom(apt);
var fp = flightplan();
fp.appendWP(wp);
|example2text = Creates a new waypoint and appends it to the flight plan. This way point is then removed; the {{func link|print()}} statements prove this.
|example2 = var apt = airportinfo("KSFO");
var wp = createWPFrom(apt, "pseudo");
print(wp.wp_name);
var fp = flightplan();
fp.appendWP(wp);
print(fp.getPlanSize());
fp.clearWPType("pseudo");
print(fp.getPlanSize());
}}

===defined()===
{{Nasal doc
|syntax = defined(symbol);
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|text = Returns 1 (true) or 0 (false) depending on whether a variable exists.
|param1 = symbol
|param1text = A string that will be what the function searches for.
|example1 = var number = 12;
var check_exist = func {
print("Variable 'number' ", defined("number") == 1 ? "exists" : "does not exist"); # 'number' does exist
print("Variable 'number2' ", defined("number2") == 1 ? "exists" : "does not exist"); # 'number2' does not exist
}
check_exist();
}}

===directory()===
{{Nasal doc
|syntax = directory(path);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=572|t=Source}}
|text = Returns a vector containing a list of the folders and files in a given file path or <code>'''nil'''</code> if the path doesn't exist. Hidden folders and files are not added to the vector.
{{inote|The first two elements of the vector will be <code>'.'</code> and <code>'..'</code>. These are for navigating back up the file tree, but have no use in Nasal. They can be safely removed from the vector.}}
|param1 = path
|param1text = Absolute file path.
|example1text = Gets the folders and files in [[$FG_ROOT]], and then removes the extra first two elements (see note above).
|example1 = var dir = directory(getprop("/sim/fg-root")); # get directory
dir = subvec(dir, 2); # strips off the first two elements
debug.dump(dir); # dump the vector
}}

===fgcommand()===
{{Nasal doc
|syntax = fgcommand(cmd[, args]);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=456|t=Part 1}} {{!}} {{fgdata file|Nasal/globals.nas|t=Part 2}}
|text = Runs an fgcommand. See also {{readme file|commands}} and [[Bindings]] for more information. See {{flightgear file|src/Main/fg_commands.cxx|l=1425}} for the full list of fgcommands. Note that fgcommands generated by {{func link|addcommand()}} can also be run using this function. Also, the full list of fgcommands depends on the version of FlightGear you have. Returns 1 (true) if the fgcommand succeeded or 0 (false) if it failed.
|param1 = cmd
|param1text = String that is the name of the command that is to be run.
|param2 = args
|param2text = If the fgcommand takes arguments, they are inputted using this argument. Can either be a <code>props.Node</code> object, or a hash (see examples below).
|example1 = fgcommand("null"); # does nothing
|example2 = var args = props.Node.new({'script': 'print("Running fgcommand");'});
if (fgcommand("nasal", args)) { # prints "Running fgcommand" and then one of these print statements
print("Fgcommand succeeded");
} else {
print("Fgcommand encountered a problem");
}
|example3 = var args = { 'dialog-name': 'about' };
fgcommand("dialog-show", args); # shows the 'about' dialog
}}

===findAirportsByICAO() ===
{{Nasal doc
|syntax = findAirportsByICAO(search[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1096|t=Source}}
|text = Returns a vector containing <code>airport</code> ghost objects which are (by default) airports whose ICAO code matches the search string. The results are sorted by range from closest to furthest.
|param1 = search
|param1text = Search string for the function. Can either be a partial or a full ICAO code.
:{{icaution|The more matches there are for the given code, the longer the function will take. Passing just one character (e.g., "K"), might make FlightGear hang for a certain amount of time.}}
|param2 = type
|param2text = This will narrow the search to airports of a certain type. By default, only airports are searched for. May be one of "airport," "heliport," or "seaport."
|example1 = var apts = findAirportsByICAO("KSF"); # finds all airports matching "KSF"
foreach(var apt; apts){
print(apt.name, " (", apt.id, ")"); # prints them
}
|example2 = var apts = findAirportsByICAO("SP0", "seaport"); # finds all seaplane bases matching "SP0"
foreach(var apt; apts){
print(apt.name, " (", apt.id, ")"); # prints them
}
|example3 = var apt = findAirportsByICAO("XBET"); # one way to check if an airport does exist"
if (size(apt) == 0) {
print("Airport does not exist"); # this one will be printed
} else {
print("Airport does exist");
<nowiki>}</nowiki>
}}

===findAirportsWithinRange()===
{{Nasal doc
|syntax = findAirportsWithinRange([pos, ]range[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1066|t=Source}}
|text = Returns a vector of <code>airport</code> ghost object which are (by default) airports that are within a given range of a given position, or the aircraft's current position. The results are sorted by range from closest to furthest.
|param1 = pos
|param1text = Optional position to search around. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. Example: <code>findAirportsWithinRange(lat, lon, range, type);</code>.
|param2 = range
|param2text = Mandatory number giving the range in nautical miles within which to search for airports/heliports/seaplane bases.only airports are searched for.
|param3 = type
|param3text = This will narrow the search to airports of a certain type. By default, only airports are searched for. May be one of "airport," "heliport," or "seaport."
|example1text = Searches for airports within 10 nm of [[KSFO]].
|example1 = var pos = airportinfo("KSFO");
var apts = findAirportsWithinRange(pos, 10);
foreach(var apt; apts){
print(apt.name, " (", apt.id, ")");
}
|example2text = Searches for seaplane bases within 15 nm of [[KSFO]].
|example2 = var pos = airportinfo("KSFO");
var apts = findAirportsWithinRange(pos, 15, "seaport");
foreach(var apt; apts){
print(apt.name, " (", apt.id, ")");
}
|example3text = Searches for airports within 10 nm of your current position.
|example3 = var apts = findAirportsWithinRange(10);
foreach(var apt; apts){
print(apt.name, " (", apt.id, ")");
<nowiki>}</nowiki>
}}

===findCommByFrequencyMHz()===
findCommByFrequencyMHz([pos, ]freq[, type]);
[[sourceforge:p/flightgear/flightgear/ci/next/tree/src/Scripting/NasalPositioned.cxx#l1547|source]]

Returns a <code>comm</code> ghost object for a station matching a given frequency. If there is more than one station with that frequency, the nearest station is returned.

'''pos'''

: Optional position to search around. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. Example: <code>findCommByFrequencyMHz(lat, lon, freq, type);</code>.
; freq
: Frequency, in megahertz, of the station to search for.
; type
: This will narrow the search to station of a certain type. Defaults to "all." For the full list of accepted type arguments, see flightgear/src/Navaids/positioned.cxx (line 160)
'''Example'''
var com = findCommByFrequencyMHz(123.6);
print("ID: ", com.id); # prints info about the comm station
print("Name: ", com.name);
print("Latitude: ", com.lat);
print("Longitude: ", com.lon);
print("Type: ", com.type);
print("Frequency: ", sprintf("%.3f", com.frequency), " Mhz");

=== findFixesByID() ===
{{Nasal doc
|syntax = findFixesByID([pos, ]id);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1627|t=Source}}
|text = Returns a vector containing <code>fix</code> ghost objects matching a given ID, sorted by range from a certain position.
{{inote|Fixes are (usually) also known as waypoints.}}
|param1 = pos
|param1text = Optional position to search around. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. Example: <code>findFixesByID(lat, lon, id);</code>.
|param2 = id
|param2text = Full or partial ID of the fix to search for.
:{{inote|1=Inputting a partial ID does not work correctly (see [http://forum.flightgear.org/viewtopic.php?f=30&t=28129 here]). It is best to just input a full ID.}}
|example1 = var fixes = findFixesByID("POGIC");
foreach(var fix; fixes){
print(fix.id, " - lat: ", fix.lat, " {{!}} lon: ", fix.lon); # prints information about POGIC
}
|example2 = var fix = findFixesByID("ZUNAP");
fix = fix[0];
var (course, dist) = courseAndDistance(fix);
print("Turn to heading ", math.round(course), ". You have ", sprintf("%.2f", dist), " nm to go to reach ", fixes[0].id);
}}

===findNavaidByFrequencyMHz()===
{{Nasal doc
|syntax = findNavaidByFrequencyMHz([pos, ]freq[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1547|t=Source}}
|text = Returns a <code>navaid</code> ghost object for a navaid matching a given frequency. If there is more than one navaid with that frequency, the nearest station is returned.
|param1 = pos
|param1text = Optional position to search around. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. Example: <code>findNavaidByFrequencyMHz(lat, lon, freq, type);</code>.
|param2 = freq
|param2text = Frequency, in megahertz, of the navaid to search for.
|param3 = type
|param3text = This will narrow the search to navaids of a certain type. Defaults to "all." For the full list of accepted type arguments, see {{flightgear file|src/Navaids/positioned.cxx|l=127}}.
|example1 = var navaid = findNavaidByFrequencyMHz(109.55);
print("ID: ", navaid.id); # prints info about the navaid
print("Name: ", navaid.name);
print("Latitude: ", navaid.lat);
print("Longitude: ", navaid.lon);
print("Elevation (AMSL): ", navaid.elevation, " m");
print("Type: ", navaid.type);
print("Frequency: ", sprintf("%.3f", navaid.frequency / 100), " Mhz");
print("Range: ", navaid.range_nm, " nm");
if(navaid.course) print("Course: ", navaid.course);
}}

=== findNavaidsByFrequencyMHz()===
{{Nasal doc
|syntax = findNavaidsByFrequencyMHz([pos, ]freq[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1572|t=Source}}
|text = Returns a vector conatining <code>navaid</code> ghost objects for navaids that match a given frequency, sorted from nearest to furthest.
|param1 = pos
|param1text = Optional position to search around. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. Example: <code>findNavaidsByFrequencyMHz(lat, lon, freq, type);</code>.
|param2 = freq
|param2text = Frequency, in megahertz, of the navaid to search for.
|param3 = type
|param3text = This will narrow the search to navaids of a certain type. Defaults to "all." For the full list of accepted type arguments, see {{flightgear file|src/Navaids/positioned.cxx|l=127}}.
|example1 = var navaids = findNavaidsByFrequencyMHz(109.55);
foreach(var navaid; navaids){
print("--");
print("ID: ", navaid.id); # prints info about the navaid
print("Name: ", navaid.name);
print("Latitude: ", navaid.lat);
print("Longitude: ", navaid.lon);
print("Elevation (AMSL): ", navaid.elevation, " m");
print("Type: ", navaid.type);
print("Frequency: ", sprintf("%.3f", navaid.frequency / 100), " Mhz");
print("Range: ", navaid.range_nm, " nm");
if(navaid.course) print("Course: ", navaid.course);
print("--");
<nowiki>}</nowiki>
}}

===findNavaidsByID()===
{{Nasal doc
|syntax = findNavaidsByID([pos, ]id[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1600|t=Source}}
|text = Returns a vector containing <code>navaid</code> ghost objects matching a given ID, sorted by range from a certain position.
|param1 = pos
|param1text = Optional position to search around. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. Example: <code>findNavaidsByID(lat, lon, id, type);</code>.
|param2 = id
|param2text = Full or partial ID of the fix to search for.
:{{inote|1=Inputting a partial ID does not work correctly (see [http://forum.flightgear.org/viewtopic.php?f=30&t=28129 here]). It is best to just input a full ID.}}
|param3 = type
|param3text = This will narrow the search to navaids of a certain type. Defaults to "all." For the full list of accepted type arguments, see {{flightgear file|src/Navaids/positioned.cxx|l=127}}.
|example1 = var navaid = findNavaidsByID("MXW");
navaid = navaid[0];
print("ID: ", navaid.id); # prints info about 'MXW' (a VOR station)
print("Name: ", navaid.name);
print("Latitude: ", navaid.lat);
print("Longitude: ", navaid.lon);
print("Elevation (AMSL): ", navaid.elevation, " m");
print("Type: ", navaid.type);
print("Frequency: ", sprintf("%.3f", navaid.frequency / 1000), " Mhz");
print("Range: ", navaid.range_nm, " nm");
}}

===findNavaidsWithinRange()===
{{Nasal doc
|syntax = findNavaidsWithinRange([pos, ]range[, type]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1518|t=Source}}
|text = Returns a vector of <code>navaid</code> ghost objects which are within a given range of a given position (by default the aircraft's current position). The results are sorted from closest to furthest.
|param1 = pos
|param1text = Optional position to search around. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost type
:* A hash with ''lat'' and ''lon'' members
:* A geo.Coord object
:* Two numbers separated by a comma, as if the function is taking three arguments. Example: <code>findNavaidsWithinRange(lat, lon, range, type);</code>.
|param2 = range
|param2text = Mandatory number giving the range in nautical miles within which to search for navaids.
|param3 = type
|param3text = This will narrow the search to navaids of a certain type. Defaults to "all." For the full list of accepted type arguments, see {{flightgear file|src/Navaids/positioned.cxx|l=127}}.
|example1text = Searches for navaids within 10 nm of [[KSFO]].
|example1 = var pos = airportinfo("KSFO");
var navs = findNavaidsWithinRange(pos, 10);
foreach(var nav; navs){
print(nav.name, " (ID: ", nav.id, ")");
}
|example2text = Searches for navaids within 10 nm of your current position.
|example2 = var navs = findNavaidsWithinRange(10);
foreach(var nav; navs){
print(nav.name, " (ID: ", nav.id, ")");
<nowiki>}</nowiki>
}}

===finddata()===
{{Nasal doc
|syntax = finddata(path);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=603|t=Source}}
|text = Takes a relative path and tries to return an absolute one. It works by appending the relative path to some paths and testing to see if they exist. As of FlightGear v3.7, these paths are the TerraSync directory (tested first) and [[$FG_ROOT]].
|param1 = path
|param1text = A relative path as a string.
|example1 = var path = finddata("Aircraft/Generic");
print(path); # prints the absolute path to $FG_ROOT/Aircraft/Generic
|example2 = var path = finddata("Airports");
print(path); # prints the absolute path to <TerraSync dir>/Airports
|example3 = var path = finddata("preferences.xml");
print(path); # prints the absolute path to $FG_ROOT/preferences.xml
}}

===flightplan()===
{{Nasal doc
|syntax = flightplan([path]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1738|t=Source}}
|text = {{see also|Nasal Flightplan}}
Returns a flight plan object, either one for the current flight plan, or one loaded from a given path.
|param1 = path
|param1text = Optional path to flight plan XML file.
|example1text = Gets the active flight plan and gets the ID of the current waypoint. Note that this example requires a flight plan to be set in the [[Route Manager]] first.
|example1 = var fp = flightplan();
print(fp.getWP(fp.current).id);
|example2text = Creates a new flight plan from an XML file and prints the IDs of the waypoints. Note that this example requires a flight plan to have been created and saved as <tt>''[[$FG_HOME]]/fp-demo.xml''</tt>.
|example2 = var path = getprop('/sim/fg-home') ~ '/fp-demo.xml';
var fp = flightplan(path);
for(var i = 0; i < fp.getPlanSize(); i += 1){
print(fp.getWP(i).id);
<nowiki>}</nowiki>
}}

===geodinfo()===
{{Nasal doc
|syntax = geodinfo(lat, lon[, max_alt]);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=981|t=Source}}
|text = Returns a vector containing two entries or <code>'''nil'''</code> if no information could be obtained because the terrain tile wasn't loaded. The first entry in the vector is the elevation (in meters) for the given point, and the second is a hash with information about the assigned material (as defined in <tt>''[[$FG_ROOT]]/Materials''</tt>), or <code>'''nil'''</code> if there was no material information available (for example, because there is an untextured building at that location). The structure of the hash is as follows (see also {{readme file|materials}}):
* '''light_coverage:''' The coverage of a single point of light in m<sup>2</sup>.
* '''bumpiness:''' Normalized bumpiness factor for the material.
* '''load_resistance:''' The amount of pressure in N/m<sup>2</sup> the material can withstand without deformation.
* '''solid:''' 1 (true) or false (0) depending on whether the material is solid or not.
* '''names:''' Vector of scenery types (usually generated by [[TerraGear]]) that will use this material.
* '''friction_factor:''' Normalized friction factor of the material.
* '''rolling_friction:''' The rolling friction coefficient of the material.

Note that this function is a ''very'' CPU-intensive operation, particularly in FlightGear v2.4 and earlier. It is advised to use this function as little as possible.
|param1 = lat
|param1text = Latitude, inputted as a number.
|param2 = lon
|param2text = Longitude, inputted as a number.
|param3 = max_alt
|param3text = The altitude, in metres, from which the function will begin searching for the height of the terrain. Defaults to 10,000 metres. If the terrain is higher than this argument specifies, <code>'''nil'''</code> will be returned.
|example1text = Dumps information about ground underneath the aircraft.
|example1 = var pos = geo.aircraft_position();
var info = geodinfo(pos.lat(), pos.lon());
debug.dump(info);
|example2text = Prints whether the ground underneath the aircraft is solid or is water.
|example2 = var pos = geo.aircraft_position();
var info = geodinfo(pos.lat(), pos.lon());
if (info != nil and info[1] != nil) {
print("The ground underneath the aircraft is ", info[1].solid == 1 ? "solid." : "water.");
<nowiki>}</nowiki>
}}

=== geodtocart() ===
{{Nasal doc
|syntax = geodtocart(lat, lon, alt);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=962|t=Source}}
|text = Converts {{wikipedia|geodetic coordinates}} (latitude, longitude, and altitude) to {{wikipedia|ECEF|Earth-centered, Earth-fixed}} coordinates (x, y and z). A vector is returned containing x, y, and z in metres. The equatorial radius of earth used is that defined by the {{wikipedia|WGS 84}} (6,378,137 metres). All argument are mandatory.
|param1 = lat
|param1text = Latitude, in degrees.
|param2 = lon
|param2text = Longitude, in degrees.
|param3 = alt
|param3text = Altitude, in metres.
|example1 = var (x, y, z) = geodtocart(0, 0, 0); # point is the intersection of the prime meridian and equator.
print("x: ", x); # prints "x: 6378137"
print("y: ", y); # prints "y: 0"
print("z: ", z); # prints "y: 0"
}}

=== get_cart_ground_intersection()===
Introduced in 2017.2.1, see [[Terrain Detection]].

===getprop()===
{{Nasal doc
|syntax = <nowiki>getprop(path[, path[, ...]]);</nowiki>
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=345|t=Source}}
|text = Returns the value of a node in the [[Property Tree]] or <code>'''nil'''</code> if the node does not exist or the value is not a number (NaN).
|param1 = path
|param1text = There needs to be at least one argument, but there is no limit to the maximum amount of arguments that can be given. The arguments will be concatenated together to form a property tree path. The arguments must be strings, but in FlightGear v3.2 onwards, there is also support (added by {{flightgear commit|34ed79}}) for numeric arguments as indices. See example 2 below.
|example1 = print("You have FlightGear v", getprop("/sim/version/flightgear")); # prints FlightGear version
|example2text = Note that the example below will only work in FlightGear 3.2 and above.
|example2 = for(var i = 0; i < 8; i += 1){
print("View #", i + 1, " is named ", getprop("/sim/view", i, "name"));
}
|example3text = Same as above, but is supported by all versions of FlightGear.
|example3 = for(var i = 0; i < 8; i += 1){
print("View #", i + 1, " is named ", getprop("/sim/view[" ~ i ~ "]/name"));
<nowiki>}</nowiki>
}}
==== See also====
{{note| If you have to read/write the same property multiple times (e.g. in an update loop), it is more efficient to use a node object:
To get a Node rather than its value, use <code>props.globals.getNode()</code> - see [[Nasal_library/props]]. }}

===greatCircleMove()===
{{Nasal doc
|syntax = greatCircleMove([pos, ]course, dist);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1681|t=Source}}
|text = Calculates a new set of geodetic coordinates using inputs of course and distance, either from the aircraft's current position (by default) or from another set of coordinates. Returns a hash containing two members, ''lat'' and ''lon'' (latitude and longitude respectively).
|param1 = pos
|param1text = Optional position to calculate from. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost object.
:* A hash with ''lat'' and ''lon'' members
:* A <code>geo.Coord</code> object
:* A lat/lon pair, that is, a pair of numbers (latitude followed by longitude) separated by a comma: <code>greatCircleMove(lat,lon, ...)</code>.
|param2 = course
|param2text = Course to new set of coordinates, in degrees (in the range 0–360).
|param3 = dist
|param3text = Distance in nautical miles to the new set of coordinates.
|example1 = var pos = greatCircleMove(0,0, 0, 1);
debug.dump(pos); # print hash with coordinates
|example2 = var fix = findFixesByID("POGIC");
fix = fix[0];
var pos = greatCircleMove(fix, 45, 10);
debug.dump(pos); # print hash with coordinates
}}

===interpolate()===
{{Nasal doc
|private = _interpolate()
|syntax = <nowiki>interpolate(prop, value1, time1[, value2, time2[, ...]]);</nowiki>
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=522|t=Part 1}} {{!}} {{fgdata file|Nasal/globals.nas|t=Part 2}}
|text = Linearly interpolates a node in the property tree to a given value in a specified time. The value/time pairs will be run one after the other in the order that they are passed to the function. Note that the interpolation will continue even when the simulation is paused.
|param1 = prop
|param1text = String or <code>props.Node</code> object that indicates a node in the property tree to be used.
|param2 = value''n''
|param2text = Target value to change the property to in the set amount of time. This should be a number.
|param3 = time''n''
|param3text = Time in seconds, that will be taken for the interpolation.
|example1text = Paste the code below into the Nasal Console and execute. Then, open the Property Browser and look for the property. Finally, run the code again, and watch the value of the property change.
|example1 = setprop("/test", 0); # (re-)set property
interpolate("/test",
50, 5, # interpolate to 50 in 5 seconds
10, 2, # interpolate to 10 in 2 seconds
0, 5); # interpolate to 0 in 5 seconds
|example2 = # Apply the left brake at 20% per second
var prop = "controls/gear/brake-left";
var dist = 1 - getprop(prop);
if (dist == 1) {
interpolate(prop, 1, dist / 0.2);
<nowiki>}</nowiki>
}}

===isa()===
{{Nasal doc
|syntax = isa(object, class);
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|text = Checks if an object is an instance of, or inherits from, a second object (or class), returning 1 (true) if it is and 0 (false) if otherwise.
|param1 = object
|param1text = Object to check.
|param2 = class
|param2text = Class/object to check that '''object''' inherits from or is an instance of.
|example1 = var coord = geo.Coord.new();
if(isa(coord, geo.Coord)){
print("Variable 'coord' is an instance of class 'geo.Coord'"); # this one will be printed
} else {
print("Variable 'coord' is not an instance of class 'geo.Coord'");
}
|example2 = var coord = geo.Coord.new();
if(isa(coord, props.Node)){
print("Variable 'coord' is an instance of class 'props.Node'");
} else {
print("Variable 'coord' is not an instance of class 'props.Node'"); # this one will be printed
}
|example3text = The example below demonstrates checking of inheritance.
|example3 = var Const = {
constant: 2,
getConst: func {
return me.constant;
}
};

var Add = {
new: func {
return { parents: [Add, Const] };
},

addToConst: func(a){
return a * me.getConst();
}
};

var m = Add.new();
print(m.addToConst(4));

if(isa(m, Add)) print("Variable 'm' is an instance of class 'Add'"); # will be printed
if(isa(m, Const)) print("Variable 'm' is an instance of class 'Const'"); # will also be printed
}}

===logprint()===
{{Nasal doc
|syntax = <nowiki>logprint(priority[, msg[, msg[, ...]]]);</nowiki>
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=431|t=Source}}
|text = Concatenates a message and logs it with a given priority level. Unlike {{func link|print()}} and {{func link|printlog()}}, message outputted by this function will be logged in your <code>[[Commonly used debugging tools#fgfs.log|fgfs.log]]</code> file as coming from the Nasal file itself rather than from {{flightgear file|src/Scripting/NasalSys.cxx}}.
|param1 = priority
|param1text = Number specifying the priority level of the outputted message:
:{{{!}} class="wikitable"
! Number !! Debug type
{{!-}}
{{!}} 1 {{!!}} Bulk
{{!-}}
{{!}} 2 {{!!}} Debug
{{!-}}
{{!}} 3 {{!!}} Info
{{!-}}
{{!}} 4 {{!!}} Warn
{{!-}}
{{!}} 5 {{!!}} Alert
{{!}}}
|param2 = msg
|param2text = The message. There is no limit to the arguments you give give. They will be concatenated together before logging.
|example1 = # logs the value of pi to three decimal places with log level 3
logprint(3, "pi = ", sprintf("%.3f", math.pi));
|example2 = logprint(5, "Alert! This is an important message!");
}}
{{note|
The following constants have been added to the development branch of FlightGear ("next") and will be releases with FG 2020.1 so you won't have to remember the numbers anymore:

LOG_BULK, LOG_WARN, LOG_DEBUG, LOG_INFO, LOG_ALERT, DEV_WARN, DEV_ALERT }}

===magvar() ===
{{Nasal doc
|syntax = magvar([pos]);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1642|t=Source}}
|text = Returns the {{wikipedia|magnetic variation}} at a given set of coordinates. The table below gives the magnetic model used depending on the version of FlightGear.
{{{!}} class="wikitable"
! FlightGear versions !! Model !! Reference date
{{!-}}
{{!}} 3.6 and above {{!!}} {{wikipedia|World Magnetic Model}} (WMM) 2015 {{!!}} 1 January 2015
{{!-}}
{{!}} 0.9.11-pre1 to 3.4 {{!!}} WMM 2005 {{!!}} 1 January 2005
{{!-}}
{{!}} 0.7.3 to 0.9.10 {{!!}} WMM 2000 {{!!}} 1 January 2000
{{!}}}
|param1 = pos
|param1text = Optional position to calculate from. If not given, the aircraft's current position will be used. Can be one of:
:* An <code>airport</code>, <code>navaid</code>, <code>runway</code>, <code>taxiway</code>, <code>fix</code>, or <code>waypoint</code> ghost object.
:* A hash with ''lat'' and ''lon'' members
:* A <code>geo.Coord</code> object
:* A lat/lon pair, that is, a pair of numbers (latitude followed by longitude) separated by a comma: <code>magvar(lat,lon)</code>.
|example1 = print(magvar(0, 0)); # prints the magnetic variation at 0, 0
}}

===maketimer() ===
{{Nasal doc
|syntax = maketimer(interval[, self], function);
|source = ''Implemented using the {{API Link|flightgear|class|TimerObj}} class.''<br>{{flightgear file|src/Scripting/NasalSys.cxx|l=90|t=Part 1}} {{!}} {{flightgear file|src/Scripting/NasalSys.cxx|l=533|t=Part 2}}
|version = 2.12
|commit = {{flightgear commit|ab939f|t=commit}}
|text = Returns a timer object containing the following methods and members:
* '''start()''': Starts the timer.
* '''stop()''': Stops the timer.
* '''restart(interval)''': Restarts the timer with the given interval.
* '''singleShot''': Bool showing whether the timer is only to be run once, or continuously until told to stop. Can be both set and read from (see examples).
* '''isRunning''': Read-only bool telling whether the timer is currently running.
* '''simulatedTime''': (FG 2017.1+; {{flightgear commit|0af316|t=commit}}) Bool telling whether the timer is using simulated time (which accounts for pause, etc.). Defaults to false (use real time). Can be both read and set. This cannot be changed while the timer is running.
Unlike {{func link|settimer()}}, which it replaces, <code>maketimer()</code> provides more control over the timer. In addition, it can help reduce memory usage.
|param1 = interval
|param1text = Interval in seconds for the timer.
|param2 = self
|param2text = Optional parameter specifying what any <code>'''me'''</code> references in the function being called will refer to.
|param3 = function
|param3text = Function to be called at the given interval.
|example1 = var timer = maketimer(1, func(){
print("Hello, World!"); # print "Hello, World!" once every second (call timer.stop() to stop it)
});
timer.start();
|example2 = var timer = maketimer(1, math, func(){
print(me.math); # 'me' reference is the 'math' namespace
});
timer.singleShot = 1; # timer will only be run once
timer.start();
|example3 = var timer = maketimer(1, func(){
print("Hello, World!"); # print "Hello, World!" once every second (call timer.stop() to stop it)
});
timer.start();
print(timer.isRunning); # prints 1
|example4text = In the example below, "Hello, World!" will be printed after one second the first time, and after two seconds thereafter.
|example4 = var update = func(){
print("Hello, World!");
timer.restart(2); # restarts the timer with a two second interval
}

var timer = maketimer(1, update);
timer.singleShot = 1;
timer.start();
}}

===maketimestamp()===
{{Nasal doc
|syntax = maketimestamp()
|source = ''Implemented using the {{API Link|flightgear|class|TimeStampObj}} class.''<br>{{flightgear file|src/Scripting/NasalSys.cxx|l=214|t=Part 1}} {{!}} {{flightgear file|src/Scripting/NasalSys.cxx|l=589|t=Part 2}}
|version = 2019.2
|commit = {{flightgear commit|7db06300|t=commit}}
|text = Returns a time stamp object to allow high resolution timing of Nasal operations. When created the timer will automatically be stamped. The object has the following methods:
* '''stamp()''': Resets the timing operation. Call this first.
* '''elapsedMSec()''': returns number of milliseconds elapsed since stamp() called. Resolution may vary depending on platform but is usually at least millisecond accuracy.
* '''elapsedUSec()''': returns number of microseconds elapsed since stamp() called. Resolution may vary depending on platform but is usually at least millisecond accuracy.
|
|example1text = In the example below the number of milliseconds elapsed will be printed.
|example1 = var timestamp = maketimestamp();
timestamp.stamp();
print(timestamp.elapsedMSec(), "ms elapsed");
print(timestamp.elapsedMSec(), "ms elapsed");
}}

===md5()===
{{Nasal doc
|syntax = md5(string);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=758|t=Source}}
|version = 3.2
|commit = {{flightgear commit|cfbf9e|t=commit}}
|text = Returns a the {{wikipedia|MD5}} hash (as a string) of the inputted string.
|param1 = string
|param1text = String the generate the hash of. Mandatory.
|example1text = The below code should output <code>65a8e27d8879283831b664bd8b7f0ad4</code>.
|example1 = print(md5("Hello, World!"));
}}

===navinfo()===
{{Nasal doc
|syntax = navinfo(lat, lon, type, id);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1453|t=Source}}
|text = Returns vector <code>navaid</code> ghost objects matching the given '''type''' and '''id''' or <code>'''nil'''</code> on error.
|param1 = lat ''and'' lon
|param1text = If given, the returned navaids will be put into order of ascending distance from the location.
|param2 = type
|param2text = Narrows the search to the given type. Must be one of "any," "fix," "vor," "ndb," "ils," "dme," or "tacan." Defaults to the equivalent of "any."
|param3 = id
|param3text = ID to search for. Note that, although all the parameters are technically optional, this parameter must be given, otherwise an empty vector will be returned.
|example1 = navinfo("vor"); # returns all VORs
|example2 = navinfo("HAM"); # return all navaids whose names start with "HAM"
|example3 = navinfo("vor", "HAM"); # return all VORs whose names start with "HAM"
|example4 = navinfo(34,48,"vor","HAM"); # return all VORs whose names start with "HAM" and sorted by distance relative to 34°, 48°
}}

===parse_markdown()===
{{Nasal doc
|syntax = parse_markdown(markdown);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=745|t=Part 1}} {{!}} {{simgear file|simgear/misc/SimpleMarkdown.cxx|t=Part 2}}
|version = 3.2
|text = Parses a string containing {{wikipedia|Markdown}} and returns the result as a string. As of FlightGear 2016.1, it is just a simple parser, and does the following:
* It strips whitespace from the beginning of the string.
* It supports [http://daringfireball.net/projects/markdown/syntax#p paragraphs and line breaks].
* It collapses whitespace.
* It converts unordered [http://daringfireball.net/projects/markdown/syntax#list lists] to use a bullet character (•). Note that the bullet character is implemented in hexadecimal UTF-8 character bytes (<code>E2 80 A2</code>), as so may not work properly when the being displayed in an encoding other than UTF-8.
|param1 = markdown
|param1text = String containing Markdown to be parsed.
|example1text =
Save the below code as <tt>''[[$FG_ROOT]]/gui/dialogs/test.xml''</tt>, then run the Nasal code below it to open the dialog. To change the markdown to be parsed, simply change the code in the highlighted section, save it, and reload the GUI (<tt>Debug > Reload GUI</tt>).
<syntaxhighlight lang="xml" highlight="41-50">
<?xml version="1.0" encoding="UTF-8"?>

<PropertyList>

<name>test</name>
<layout>vbox</layout>

<group>
<layout>hbox</layout>

<empty>
<stretch>true</stretch>
</empty>

<text>
<label>parse_markdown() test dialog</label>
</text>

<empty>
<stretch>true</stretch>
</empty>

<button>
<legend></legend>
<pref-width>16</pref-width>
<pref-height>16</pref-height>
<binding>
<command>dialog-close</command>
</binding>
</button>

</group>

<canvas>
<name>Canvas plot</name>
<stretch>true</stretch>
<pref-width>400</pref-width>
<pref-height>300</pref-height>
<nasal>
<load><![CDATA[
var text = 'Items:
* apples
* oranges
* pears

Some text.
Some more items:
* apples
* oranges
* pears';

var parsed = parse_markdown(text);

var root_canvas = canvas.get(cmdarg());
root_canvas.setColorBackground(255, 255, 255);
var root = root_canvas.createGroup();

var text_dis = root.createChild("text")
.setText(parsed)
.setTranslation(5, 5)
.setFont("LiberationFonts\LiberationSans-Regular.ttf")
.setFontSize(15)
.setColor(0, 0, 0)
.setDrawMode(canvas.Text.TEXT)
.setAlignment("left-top");
]]></load>
</nasal>
</canvas>

</PropertyList>
</syntaxhighlight>
|example1 = fgcommand("dialog-show", {"dialog-name": "test"});
|example2text = The example below parses Markdown and outputs it in a HTML document. The parsed text is placed in <syntaxhighlight lang="xml" inline><pre></pre></syntaxhighlight> tags. To change the Markdown to be parsed, simply edit the variable <tt>markdown</tt> at the top of the code.
|example2 = <nowiki>var markdown = 'Items:
* apples
* oranges
* pears

Some text.
Some more items:
* apples
* oranges
* pears';

var parsed = parse_markdown(markdown);

debug.dump(parsed);

var path = string.normpath(getprop("/sim/fg-home") ~ '/Export/parse_markdown()-test.html');

var file = io.open(path, "w");

var html = "<!DOCTYPE html>\n\n<html>\n\n<head>\n\t<meta charset=\"UTF-8\">\n\t<title>parse_markdown() test generated by Nasal</title>\n</head>\n\n<body>\n\t<pre>" ~ parsed ~ "</pre>\n</body>\n\n</html>";

io.write(file, html);
io.close(file);
print("Done, file ready for viewing (" ~ path ~ ")");</nowiki>
}}

===parsexml()===
{{Nasal doc
|syntax = <nowiki>parsexml(path[, start[, end[, data[, pro_ins]]]]);</nowiki>
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=710|t=Source}}
|text = This function is an interface into the built-in [http://expat.sourceforge.net/ Expat XML parser]. The absolute path to the file is returned as string, or <code>'''nil'''</code> is returned on error.
|param1 = path
|param1text = Mandatory absolute path to the XML file to be parsed.
|param2 = start
|param2text = Optional callback function that will be called for every starting tag. The function should take two argument: the tag name and a hash containing attributes.
|param3 = end
|param3text = Optional callback function that will be called for every ending tag. The function should take one argument: the tag name.
|param4 = data
|param4text = Optional callback function that will be called for every piece of data within a set of tags. The function should take one argument: the data as a string.
|param5 = pro_ins
|param5text = Optional callback function that will be called for every {{wikipedia|Processing Instruction|processing instruction}}. The function should take two argument: the target and the data string.
|example1text = Save the below XML code in <tt>''[[$FG_HOME]]/Export/demo.xml''</tt>. Then, execute the Nasal code below in the Nasal Console. The XML will be parsed and each bit of the code will be printed.
<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8"?>

<?xml-stylesheet type="text/xsl" href="style.xsl"?>

<foo>
<blah type="string"><![CDATA[ <sender>John Smith</sender> ]]></blah>
<blah2 type="string">Orange & lemons</blah2>
</foo>
</syntaxhighlight>
|example1 = var start = func(name, attr){
print("Starting tag: '", name, "'");
foreach(var a; keys(attr)){
print("\twith attribute ", a, '="', attr[a], '"');
}
}

var end = func(name){
print("Ending tag: '", name, "'");
}

var data = func(data){
print("Data = '", data, "'");
}

var pro_instr = func(target, data){
print("Processing instruction: target = '", target, "', data = '", data, "'");
}

parsexml(getprop("/sim/fg-home") ~ '/Export/demo.xml', start, end, data, pro_instr);
}}

===print()===
{{Note|As of 07/2020, we are in the process of slowly deprecating and removing Nasal print() (in fgdata) where possible in favor of log [[#logprint()]] which takes a priority level.

This is part of the goal that we achieve zero output at log-level at alert, and everything shown at ‘warn; is really a warning, not just information.<ref>https://sourceforge.net/p/flightgear/mailman/message/37042224/</ref>}}

{{Nasal doc
|syntax = <nowiki>print(data[, data[, ...]]);</nowiki>
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=415|t=Source}}
|text = Concatenates its arguments and then prints it to the terminal and the [[Commonly used debugging tools#fgfs.log|log]]. Note that a newline is automatically added.
|param1 = data
|param1text = Data to print. Only strings and numbers can be printed; other data types will not be. There many be any number of arguments; they will just be concatenated together.
|example1 = print("Just", " a ", "test"); # prints "Just a test"
|example2 = print("pi = ", math.pi); # prints "pi = 3.141592..."
}}

=== printf() ===
{{Nasal doc
|syntax = <nowiki>printf(format[, arg[, arg, [...]]]);</nowiki>
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|text = Creates and prints a formatted string. For a description of its arguments, see {{func link|sprintf()}} (it is, in fact, implemented using <code>sprintf()</code>).
|example1 = printf("In hexadecimal, 100000 = %X", 186A0); # prints "In hexadecimal, 100000 = 186A0"
}}

===printlog()===
{{Nasal doc
|syntax = <nowiki>printlog(level, data[, data[, ...]]);</nowiki>
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|text = Prints the given message with the given log level. If the log level is higher or equal to <code>/sim/logging/priority</code>, it is printed.
|param1 = level
|param1text = Mandatory log level as a string. Must be one of "none," "bulk," "debug," "info," "warn," or "alert." Note that "none" will mean that the message will never be printed.
|param2 = data
|param2text = Data to be printed. Only strings and numbers will be printed; others will not be. There may be any number of arguments; they will just be concatenated together.
|example1 = printlog("alert", "This is an alert"); # message will be printed
|example2 = printlog("info", "Just informing you about something"); # message will be printed only if log level is set to "info" or less
}}

===rand()===
{{Nasal doc
|syntax = rand();
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=554|t=Source}}
|text = Returns a random floating point number between 0 (inclusive) and 1 (exclusive). It takes no arguments.
|example1 = print(rand()); # prints random number
}}

===registerFlightPlanDelegate()===
{{Nasal doc
|syntax = registerFlightPlanDelegate(init_func);
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1879|t=Source}}
|text = Registers a flight plan delegate. See <tt>''{{fgdata file|Nasal/route_manager.nas|t=$FG_ROOT/Nasal/route_manager.nas}}''</tt> for examples.
|param1 = init_func
|param1text = Initialization function which will be called during FlightGear's startup.
}}
===removecommand()===
{{Nasal doc
|syntax = removecommand(cmd);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=668|t=Source}}
|text = Removes the given fgcommand. Returns <code>'''nil'''</code>.
{{caution|This will remove '''any''' [[fgcommands|fgcommand]], even those implemented in C++, so use with caution!}}
|param1 = cmd
|param1text = String specifying the name of the command to remove.
|example1 = addcommand("hello", func(){
print("Hello");
});
fgcommand("hello"); # "Hello" will be printed
removecommand("hello"); # removes it
}}

===removelistener()===
{{Nasal doc
|syntax = removelistener(id);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=1384|t=Part 1}} {{!}} {{flightgear file|src/Scripting/NasalSys.cxx|l=506|t=Part 2}}
|text = Removes and deactivates the given listener and returns the number of listeners left or <code>'''nil'''</code> on error.
{{note|It is good practice to remove listeners when they are not required anymore. This prevents the listeners reducing FlightGear's run performance.}}
|param1 = id
|param1text = ID of listener as returned by {{func link|setlistener()}}.
|example1 = var ls = setlistener("/sim/test", func(){
print("Property '/sim/test' has been changed");
});
setprop("/sim/test", "blah"); # trigger listener
var rem = removelistener(ls); # remove listener
print("There are ", rem, " listeners remaining");
}}

===resolvepath()===
{{Nasal doc
|syntax = resolvepath(path);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=604|t=Source}}
|text = Takes a relative path as a string and uses [[SimGear]]'s path-resolving framework to return an absolute path as a string. If the path could not be resolved, an empty string is returned. See [[Resolving Paths]] for a detailed description of the algorithm. This function can also be used to check if a file exists.
|param1 = path
|param1text = Relative path to be completed.
|example1 = print(resolvepath("Nasal/globals.nas")); # prints the equivalent of $FG_ROOT/Nasal/globals.nas
|example2 = print(resolvepath("blah")); # prints nothing; could not be resolved
|example3 = var file_path = resolvepath("Aircraft/SenecaII/some-file");
if (file_path != ""){
gui.popupTip("some-file found", 2);
} else {
gui.popupTip("some-file not found", 2);
<nowiki>}</nowiki>
}}

===setlistener()===
{{Nasal doc
|syntax = <nowiki>setlistener(node, code[, init[, type]]);</nowiki>
|private = _setlistener()
|source = {{flightgear file|src/Scripting/Nasal|l=499|t=Part 1}} {{!}} {{flightgear file|src/Scripting/Nasal|l=1350|t=Part 2}}<br>''Listener implemented using the {{API Link|flightgear|class|FGNasalListener}} class.''
|text = Creates a listener which will be triggered when the given property is changed (depending on the '''type'''). A unique integer ID is returned; this can later be used as the argument to {{func link|removelistener()}}.
{{note|Listeners are known to be a source of resource leaks. To avoid this, please take measures such as:
* Using {{func link|removelistener()}} when they are not needed any more.
* Using a single initialization listener.
* Avoiding tying listeners to properties that are rapidly updated (e.g., many times per frame).
}}
|param1 = node
|param1text = Mandatory string or <code>props.Node</code> object pointing to a property in the [[Property Tree]].
|param2 = code
|param2text = Mandatory callback function to execute when the listener is triggered. The function can take up to four arguments in the following order:
* '''changed''': a <code>props.Node</code> object pointing to the changed node.
* '''listen''': a <code>props.Node</code> object pointing to the listened-to node. Note that this argument maybe different depending on the '''type'''.
* '''mode''': an integer telling how the listener was triggered. 0 means that the value was changed. 1 means that a child property was added. -1 means that a child property was removed.
* '''is_child''': boolean telling whether '''changed''' is a child property of the listened-to '''node''' or not. 1 (true) if it is, 0 (false) otherwise.
|param3 = init
|param3text = If set to 1 (true), the listener will additionally be triggered when it is created. This argument is optional and defaults to 0 (false).
|param4 = type
|param4text = Integer specifying the listener's behavior. 0 means that the listener will only trigger when the property is changed. 1 means that the trigger will always be triggered when the property is written to. 2 will mean that the listener will be triggered even if child properties are modified. This argument is optional and defaults to 1.
|example1 = var prop = props.globals.initNode("/sim/test", "", "STRING"); # create property
var id = setlistener("/sim/test", func(n){ # create listener
print("Value: ", n.getValue());
});
setprop("/sim/test", "blah"); # trigger listener
removelistener(id); # remove listener
prop.remove(); # remove property
}}

===setprop()===
{{Nasal doc
|syntax = <nowiki>setprop(path[, path[, ...]], value);</nowiki>
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=385|t=Source}}
|text = Sets the value of a property in the [[Property Tree]]. If the property does not exist, it will be created. Returns 1 (true) on success or 0 (false) if there was an error.
{{note|If you want to remove a property, you will have to use one of the <code>props</code> helpers:
<syntaxhighlight lang="nasal">
props.globals.getNode("foo/bar").remove(); # take out the complete node
props.globals.getNode("foo").removeChild("bar"); # take out a certain child node
</syntaxhighlight>
}}
|param1 = path
|param1text = There needs to be at least one '''path''' argument, but there is no limit to the maximum amount that can be given. They will be concatenated together to form a property tree path. The arguments must be strings, but in FlightGear v3.2 onwards, there also is support (added by {{flightgear commit|34ed79}}) for numeric arguments as indices. See example 2 below.
|param2 = value
|param2text = Value to write to the given property. Must be either a string or a number.
|example1 = setprop("/sim/demo", "This is a demo");
|example2text = Note that the example below will only work in FlightGear 3.2 and above.
|example2 = for(var i = 0; i < 3; i += 1){
setprop("/sim/demo", i, "Demo #" ~ i));
}
|example3text = Same as above, but is supported by all versions of FlightGear.
|example3 = for(var i = 0; i < 3; i += 1){
setprop("/sim/demo[" ~ i ~ "]", "Demo #" ~ i));
<nowiki>}</nowiki>
}}
====See also====
{{note| If you have to read/write the same property multiple times (e.g. in an update loop), it is more efficient to use a node object:
To get a Node rather than its value, use <code>props.globals.getNode()</code> - see [[Nasal_library/props]]. }}

===settimer() ===
{{Nasal doc
|syntax = settimer(function, delta[, realtime]);
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=499|t=Part 1}} {{!}} {{flightgear file|src/Scripting/NasalSys.cxx|l=1286|t=Part 2}}
|text = Runs the given function a specified amount of seconds after the current time. Returns <code>'''nil'''</code>.
{{note|Improper use of <code>settimer()</code> may cause resource leaks. It is also highly recommended that the newer {{func link|maketimer()}} should be used instead of this function.}}
|param1 = function
|param1text = Mandatory function that will be called. It may be necessary to enclose code in an anonymous function (see example).
|param2 = delta
|param2text = Mandatory amount of time in seconds after which the function will be called.
|param3 = realtime
|param3text = If 1 (true), "real time" will be used instead of "simulation time." Defaults to 0 (false). Note that if "simulation time" is used, the timer will not run while FlightGear is paused.
|example1 = var myFunc = func(){
print("Hello");
}

settimer(myFunc, 2); # runs myFunc after 2 seconds
|example2 = var sqr = func(a){
return a * a;
}

settimer(func(){
print(sqr(2)); # will print 4 after 2 seconds
}, 2);
}}

===srand() ===
{{Nasal doc
|syntax = srand();
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=559|t=Source}}
|text = Makes the pseudorandom number generator (see {{func link|rand()}}) generate a new {{wikipedia|random seed|noicon=1}} based on time. Returns 0.
}}
===systime()===
{{Nasal doc
|syntax = systime();
|source = {{flightgear file|src/Scripting/NasalSys.cxx|l=770|t=Source}}
|text = Returns the {{wikipedia|Unix time}} (seconds since since 00:00:00 UTC, 1/1/1970) as a floating point number with high resolution. This function is useful for benchmarking purposes (see example 2).
{{note|1=High resolution timers under Windows can produce inaccurate or fixed sub-millisecond results.<ref>{{cite web|url=http://forum.flightgear.org/viewtopic.php?f=30&t=29259|title=Nasal: systime() ??!?|author=Necolatis|date=Apr 2nd, 2016}}</ref> This is due to the underlying {{func link|GetSystemTimeAsFileTime()|link=https://msdn.microsoft.com/en-us/library/windows/desktop/ms724397(v=vs.85).aspx}} API call, which depends on hardware availability of suitable high resolution timers. See also [https://msdn.microsoft.com/en-us/library/windows/desktop/dn553408(v=vs.85).aspx Acquiring high-resolution time stamps]}}
|example1 = print("Unix time: ", systime()); # prints Unix time
|example2 = var myFunc = func(){
for(var i = 0; i <= 10; i += 1){
print("Interation #", i);
}
}
var t = systime(); # record time
myFunc(); # run function
var t2 = systime(); # record new time
print("myFunc() took ", t2 - t, " seconds"); # print result
}}

===thisfunc()===
{{Nasal doc
|syntax = thisfunc();
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|text = Returns the function from which this function is called. This allows a function to reliably and safely call itself from within a closure.
|example1 = var stringify_vec = func(input){
if (typeof(input) == "scalar"){
return sprintf("%s", input);
} elsif (typeof(input) == "vector") {
if (size(input) == 0) return "[]";
var this = thisfunc();
var buffer = "[";
for(var i = 0; i < size(input); i += 1){
buffer ~= this(input[i]);
if (i == size(input) - 1) {
buffer ~= "]";
} else {
buffer ~= ", ";
}
}
return buffer;
} else {
die("stringify_vec(): Error! Invalid input. Must be a vector or scalar");
}
}

var test_vec = ["a", "b", "c", 1, 2, 3];
debug.dump(stringify_vec(test_vec)); # prints "[a, b, c, 1, 2, 3]"
test_vec = [];
debug.dump(stringify_vec(test_vec)); # prints "[]"
test_vec = {};
debug.dump(stringify_vec(test_vec)); # will throw an error
}}

===tileIndex() ===
{{Nasal doc
|syntax = tileIndex();
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1720|t=Source}}
|text = Returns the index of the tile at the aircraft's current position as a string. This corresponds to the name of the STG file of the tile. For example, at [[KSFO]], this would be <code>942050</code>, corresponding to <tt>''[[$FG_SCENERY]]/Terrain/w130n30/w123n3/942050.stg''</tt>.
|example1 = print(tileIndex()); # print index
}}

=== tilePath()===
{{Nasal doc
|syntax = tilePath();
|source = {{flightgear file|src/Scripting/NasalPositioned.cxx|l=1712|t=Source}}
|text = Returns the base path of the tile at the aircraft's current position as a string. For example, at KSFO, this would be <code>w130n30/w123n3</code>, corresponding to <tt>''[[$FG_SCENERY]]/Terrain/w130n30/w123n3''</tt>.
|example1 = print(tilePath()); # print path
}}

=== values()===
{{Nasal doc
|syntax = values(hash);
|source = {{fgdata file|Nasal/globals.nas|t=Source}}
|text = Returns a vector containing the values of the given hash.
|param1 = hash
|param1text = Mandatory hash to get the values of.
|example1 = var hash = {
"a": 1,
"b": 2,
"c": 3
};

foreach(var val; values(hash)){
print(val);
}
|example2text = The below example does exactly the same thing as the above example, but does not use <code>values()</code>:
|example2 = var hash = {
"a": 1,
"b": 2,
"c": 3
};

foreach(var key; keys(hash)){
print(hash[key]);
<nowiki>}</nowiki>
}}

==Extension functions new in FG 2020.1 ==
The following functions have been added to the nasal core library and will be released with FlightGear version 2020.1.
Before the release they are available in the development branch "next".

===isfunc()===
Returns 1 if type or argument is a function, otherwise 0.

===isghost()===
Returns 1 if type or argument is a ghost, otherwise 0.

=== ishash()===
Returns 1 if type or argument is a hash, otherwise 0.

===isint()===
{{Nasal doc
|syntax = isint(x);
|source = {{simgear file|simgear/nasal/lib.c|t=Source}}
|text = Returns 1 if argument has a numeric value and x == floor(x), e.g. integer.
}}

===isnum()===
{{Nasal doc
|syntax = isnum(x);
|source = {{simgear file|simgear/nasal/lib.c|t=Source}}
|text = Returns 1 if typeof(x) is "scalar" and x has a numeric value otherwise 0.
}}

===isscalar()===
{{Nasal doc
|syntax = isscalar(x);
|source = {{simgear file|simgear/nasal/lib.c|t=Source}}
|text = Returns 1 if type or argument is a scalar (string or numeric), otherwise (vector, hash, func, ...) it returns 0. This is useful to check if a variable can be converted to string e.g. when useing the string concat operator "~".
|example1 = var a = "foo";
var b=42;
if (isscalar(a) and isscalar(b)) print(a~b);
if (isstr(a)) print("a is a string");
if (isint(b)) print("b is an integer");
# if (isscalar(a))... is equivalent to if (typeof(a) == "scalar")...
}}

===isstr()===
Returns 1 if type or argument is a string, otherwise 0.

===isvec()===
Returns 1 if type or argument is a vector, otherwise 0.

===vecindex()===
{{Nasal doc
|syntax = vecindex(vector, value);
|source = {{simgear file|simgear/nasal/lib.c|t=Source}}
|text = Returns the index of value or nil, if value is not found in vector.
|example1=
var myvector = ["apple", "bananna", "coconut"];
# to check if a vector contains a certain value compare vecindex to nil
if (vecindex(myvector, "apple") != nil) {
print("found apple");
}
# WARNING: this will not work as desired because index is 0
if (vecindex(myvector, "apple")) {
print("found apple");
<nowiki>}</nowiki>

}}

==Variables==
Various global constants (technically variables) are provided for use in converting between different units. They are all found in {{fgdata file|Nasal/globals.nas|text=$FG_ROOT/Nasal/globals.nas}}.

===D2R===
{{Nasal doc
|syntax = var radians = degrees * D2R;
|text = Converts an angle from degrees to radians when multiplied by the angle in degrees. Equal to <code>π / 180</code>.
}}
===FPS2KT===
{{Nasal doc
|syntax = var knots = feet_per_second * FPS2KT;
|text = Converts a velocity from feet per second to knots when multiplied by the velocity in feet per second. Approximately equal to 0.5925.
}}
===FT2M===
{{Nasal doc
|syntax = var metres = feet * FT2M;
|text = Converts a length from feet to metres when multiplied by the length in feet. Equal to 0.3048.
}}
===GAL2L ===
{{Nasal doc
|syntax = var litres = gallons * GAL2L;
|text = Converts a volume from US liquid gallons to litres when multiplied by the volume in gallons. Approximately equal to 3.7854.
}}
===IN2M===
{{Nasal doc
|syntax = var metres = inches * IN2M;
|text = Converts a length from inches to metres when multiplied by the length in inches. Equal to 0.0254.
}}
===KG2LB===
{{Nasal doc
|syntax = var pounds = kilograms * KG2LB;
|text = Converts a mass from kilograms to pounds when multiplied by the mass in kilograms. Approximately equal to 2.2046.
}}
===KT2FPS===
{{Nasal doc
|syntax = var feet_per_second = knots * KT2FPS;
|text = Converts a velocity from knots to feet per second when multiplied by the velocity in knots. Approximately equal to 1.6878.
}}
===KT2MPS===
{{Nasal doc
|syntax = var metres_per_second = knots * KT2MPS;
|text = Converts a velocity from knots to metres per second when multiplied by the velocity in knots. Approximately equal to 0.5144.
}}
===L2GAL===
{{Nasal doc
|syntax = var gallons = litres * L2GAL;
|text = Converts a volume from litres to US liquid gallons when multiplied by the volume in litres. Approximately equal to 0.2642.
}}
===LB2KG===
{{Nasal doc
|syntax = var kilograms = pounds * LB2KG;
|text = Converts a mass from pounds to kilograms when multiplied by the mass in pounds. Approximately equal to 0.4536.
}}
===M2FT ===
{{Nasal doc
|syntax = var feet = metres * M2FT;
|text = Converts a length from metres to feet when multiplied by the length in metres. Approximately equal to 3.2808.
}}
===M2IN===
{{Nasal doc
|syntax = var inches = metres * M2IN;
|text = Converts a length from metres to inches when multiplied by the length in metres. Approximately equal to 39.3701.
}}
===M2NM ===
{{Nasal doc
|syntax = var nautical_miles = metres * M2NM;
|text = Converts a length from metres to nautical miles when multiplied by the length in metres. Approximately equal to 0.00054.
}}
===MPS2KT ===
{{Nasal doc
|syntax = var knots = metres_per_second * MPS2KT;
|text = Converts a velocity from metres per second to knots when multiplied by the velocity in metres per second. Approximately equal to 1.9438.
}}
===NM2M ===
{{Nasal doc
|syntax = var metres = nautical_miles * NM2M;
|text = Converts a length from nautical miles to metres when multiplied by the length in nautical miles. Equal to 1,852.
}}
===R2D===
{{Nasal doc
|syntax = var degrees = radians * R2D;
|text = Converts an angle from radians to degrees when multiplied by the angle in radians. Equal to <code>180 / π</code>.
}}

{{Appendix}}

{{Nasal namespaces}}

Nasal library/string

2024-04-09T08:14:46Z

Hbeni: /* string.join(sep,list) */

{{Stub}}
{{Nasal Navigation}}
== String Handling ==
This page contains description of functions available in "$FG_ROOT\data\Nasal\strings.nas".
For string related functions in Nasal also see [[Nasal_library|Nasal library]] page.
UTF8 specific functions are from Nasal core library.

== One Character Functions ==
=== string.isalnum() ===
<syntaxhighlight lang="nasal">
string.isalnum();
</syntaxhighlight>
=== string.isalpha() ===
<syntaxhighlight lang="nasal">
string.isalpha();
</syntaxhighlight>
=== string.isascii() ===
<syntaxhighlight lang="nasal">
string.isascii();
</syntaxhighlight>
=== string.isblank() ===
<syntaxhighlight lang="nasal">
string.isblank();
</syntaxhighlight>
=== string.iscntrl() ===
<syntaxhighlight lang="nasal">
string.iscntrl();
</syntaxhighlight>
=== string.isdigit() ===
<syntaxhighlight lang="nasal">
string.isdigit();
</syntaxhighlight>
=== string.isgraph() ===
<syntaxhighlight lang="nasal">
string.isgraph();
</syntaxhighlight>
=== string.islower() ===
<syntaxhighlight lang="nasal">
string.islower();
</syntaxhighlight>
=== string.isprint() ===
<syntaxhighlight lang="nasal">
string.isprint();
</syntaxhighlight>
=== string.ispunct() ===
<syntaxhighlight lang="nasal">
string.ispunct();
</syntaxhighlight>
=== string.isspace() ===
<syntaxhighlight lang="nasal">
string.isspace();
</syntaxhighlight>
=== string.isupper() ===
<syntaxhighlight lang="nasal">
string.isupper();
</syntaxhighlight>
=== string.isxdigit() ===
<syntaxhighlight lang="nasal">
string.isxdigit();
</syntaxhighlight>
=== string.isxspace() ===
<syntaxhighlight lang="nasal">
string.isxspace();
</syntaxhighlight>
=== string.toupper() ===
<syntaxhighlight lang="nasal">
string.toupper();
</syntaxhighlight>
=== string.tolower() ===
<syntaxhighlight lang="nasal">
string.tolower();
</syntaxhighlight>

== String Functions ==
=== string.icmp(a,b) ===
Case insensitive string compare function.
<syntaxhighlight lang="nasal">
string.icmp(a,b);
</syntaxhighlight>

=== string.imatch(a,b) ===
Case insensitive match function.
<syntaxhighlight lang="nasal">
string.imatch(a,b);
</syntaxhighlight>
For example:
*string.imatch("alpha","beta") -> 0
*string.imatch("alpha","alpha") -> 1
*string.imatch("","alpha") -> 0
*string.imatch("","") -> 1

=== string.join(sep,list) ===
Join all elements of a list inserting a separator between every two of them. See [[Nasal_library#split()|split()]].
<syntaxhighlight lang="nasal">
string.join(sep,list);
</syntaxhighlight>

=== string.lc(str) ===
Return string converted to lower case letters.
<syntaxhighlight lang="nasal">
string.lc(str);
</syntaxhighlight>

=== string.match(str, patt) ===
Check if string <str> matches shell style pattern <patt>
<syntaxhighlight lang="nasal">
# Rules:
# ? stands for any single character
# * stands for any number (including zero) of arbitrary characters
# \ escapes the next character and makes it stand for itself; that is:
# \? stands for a question mark (not the "any single character" placeholder)
# [] stands for a group of characters:
# [abc] stands for letters a, b or c
# [^abc] stands for any character but a, b, and c (^ as first character -> inversion)
# [1-4] stands for digits 1 to 4 (1, 2, 3, 4)
# [1-4-] stands for digits 1 to 4, and the minus
# [-1-4] same as above
# [1-3-6] stands for digits 1 to 3, minus, and 6
# [1-3-6-9] stands for digits 1 to 3, minus, and 6 to 9
# [][] stands for the closing and the opening bracket (']' must be first!)
# [^^] stands for all characters but the caret symbol
# [\/] stands for a backslash or a slash (the backslash isn't an
# escape character in a [] character group)
#
# Note that a minus can't be a range delimiter, as in [a--e],
# which would be interpreted as any of a, e, or minus.
#
# Example:

string.match(name, "*[0-9].xml"); ... true if 'name' ends with digit followed by ".xml"
</syntaxhighlight>
=== string.normpath(path) ===
Removes superfluous slashes, empty and "." elements,
expands all ".." elements keeping relative paths,
and turns all backslashes into slashes.
The result will start with a slash if it started with a slash or backslash, it will end without slash.
<syntaxhighlight lang="nasal">
string.normpath(path);
</syntaxhighlight>
See also [[Nasal_library#resolvepath|resolvepath()]] function, which can be used to test if a file exists.

=== string.replace(str,old,new) ===
Replace all occurrences of 'old' by 'new'.
<syntaxhighlight lang="nasal">
string.replace(str,old,new);
</syntaxhighlight>
=== string.scanf(test,format,result) ===
Simple scanf function. Takes an input string, a pattern, and a vector.
It returns 0 if the format didn't match, and appends all found elements to the given vector.

Return values:
-1 string matched format ending with % (i.e. more chars than format cared about)
0 string didn't match format
1 string matched, but would still match if the right chars were added
2 string matched, and would not if any character would be added

<syntaxhighlight lang="nasal">
var r = string.scanf("comm3freq123.456", "comm%ufreq%f", var result = []);
</syntaxhighlight>
The result vector will be set to [3, 123.456].

=== string.trim(str,lr[,func]) ===
Trim spaces at the left (lr < 0), at the right (lr > 0), or both (lr = 0) is default.
An optional function argument defines which characters should be trimmed:
<syntaxhighlight lang="nasal">
string.trim(a); # trim spaces
string.trim(a, 1, string.isdigit); # trim digits at the right
string.trim(a, 0, func(c) c == `\\` or c == `/`); # trim slashes/backslashes
</syntaxhighlight>
=== string.uc(str) ===
Return string converted to upper case letters.
<syntaxhighlight lang="nasal">
string.uc(str);
</syntaxhighlight>

=== string.compileTemplate(template,type=nil) ===
Get a function out of a string template for fast insertion of template parameters.
This allows to use the same templates as with most available tile mapping engines (eg. Leaflet, Polymaps).
Return a callable function object on success, and nil if parsing the templated fails.
<syntaxhighlight lang="nasal">
string.compileTemplate(template);
</syntaxhighlight>
Example (Build MapQuest tile url):
<syntaxhighlight lang="nasal">
var makeUrl = string.compileTemplate(
"http://otile1.mqcdn.com/tiles/1.0.0/map/{z}/{x}/{y}.jpg"
);
print( makeUrl({x: 5, y: 4, z: 3}) );

Output: http://otile1.mqcdn.com/tiles/1.0.0/map/3/5/4.jpg
</syntaxhighlight>

== UTF8 String Functions (Core) ==
=== utf8.chstr(unicode) ===
Returns a string containing the UTF8 representation of the specified unicode character value.
=== utf8.strc(string, index) ===
Returns the unicode character at the specified index within the UTF8 string. Dies on encoding error or overrun.
=== utf8.substr(string, start, len=nil) ===
As for regular substr(), but the indices are of UTF8 characters intead of bytes. Dies on encoding error or overflow.
=== utf8.size(string) ===
As for regular size() when called on a string, but returns the number of UTF8 unicode characters instead of bytes. Dies on encoding error.
=== utf8.validate(string, replace=`?`) ===
Checks the string for UTF8 validity. At every byte position where an encoding error is found, it replaces that byte with the specified replacement character (default is `?`). Note that the second argument is a number, not a string.

Bendix King KN62A DME

2024-04-08T16:30:18Z

Hbeni:

[[File:Kn62a.png|thumb|270px|Bendix/King KN-62A DME]]
The Bendix/King KN62A Distance Measurement Equipment ([[DME]]) allows you to get measurements to a tuned VOR station and displays ''distance'', ''speed'' and ''estimated time'' to the station.

== Operation ==

=== Power On/Off ===
The unit has two slider type switches and a frequency selection knob.
After switching the unit on using the power switch (the lower one), the mode slider switch (the upper one) determines operation.

The unit is usually wired to an electrical avionics circuit of your plane.

=== RMT mode (NAV1 linked) ===
The DME features a primary mode (''RMT'') which is automatically slaved to NAV1. It uses a VOR-DMEs assigned frequency automatically from the tuned NAV1 frequency.

=== FREQ mode ===
Changing the mode to `FREQ` allows you to adjust the secondary frequency using the inner and outer frequency selection knobs (while in ''FREQ'' mode, the distance to the station is displayed, so you can see if you have reception.).

=== GS/T mode (secondary frequency display) ===
Finally, the ''GS/T'' mode locks the secondary frequency selection and displays ''distance'', ''speed'' and ''estimated time'' to the secondary station.

This way, you can scan for stations and get information about a station without the need to retune NAV1.

[[Category:Aircraft instruments]]

Bendix King KN62A DME

2024-04-08T16:30:04Z

Hbeni: Created page with "Bendix/King KN-62A DME The Bendix/King KN62A Distance Measurement Equipment (DME) allows you to get measurements to a tuned VOR station and displays ''distance'', ''speed'' and ''estimated time'' to the station. == Operation == === Power On/Off === The unit has two slider type switches and a frequency selection knob. After switching the unit on using the power switch (the lower one), the mode slider switch (the upper one) determines opera..."

[[File:Kn62a.png|thumb|270px|Bendix/King KN-62A DME]]
The Bendix/King KN62A Distance Measurement Equipment (DME) allows you to get measurements to a tuned VOR station and displays ''distance'', ''speed'' and ''estimated time'' to the station.

== Operation ==

=== Power On/Off ===
The unit has two slider type switches and a frequency selection knob.
After switching the unit on using the power switch (the lower one), the mode slider switch (the upper one) determines operation.

The unit is usually wired to an electrical avionics circuit of your plane.

=== RMT mode (NAV1 linked) ===
The DME features a primary mode (''RMT'') which is automatically slaved to NAV1. It uses a VOR-DMEs assigned frequency automatically from the tuned NAV1 frequency.

=== FREQ mode ===
Changing the mode to `FREQ` allows you to adjust the secondary frequency using the inner and outer frequency selection knobs (while in ''FREQ'' mode, the distance to the station is displayed, so you can see if you have reception.).

=== GS/T mode (secondary frequency display) ===
Finally, the ''GS/T'' mode locks the secondary frequency selection and displays ''distance'', ''speed'' and ''estimated time'' to the secondary station.

This way, you can scan for stations and get information about a station without the need to retune NAV1.

[[Category:Aircraft instruments]]

De/Cessna 182S

2024-04-08T16:26:40Z

Hbeni:

{{:{{#titleparts:{{PAGENAME}}||2}}/info}}

Die '''Cessna 182S Skylane''' ist ein amerikanischer, viersitziger, einmotoriger Schulterdecker mit festem Dreibeinfahrwerk. [[Cessna]] baute es zwichen 1996 und 2001.
Sie benutzt ein Textron Lycoming IO-540 AB1A5 mit Direkteinspritzung, das 230PS bei 2400 RPM Leistung erzeugt.

== Features ==
Die Cessna 182S ist eines der hochqualitativen Modelle in FlightGear.

Das Cockpit hat ein sehr detailliertes 3D-modell. Alle Schalter und Leuchten sind funktional. Das FDM ist sehr realistisch und basiert auf echten aerodynamischen Koeffizienten sowie dem Pilots Operating Handbook (POH). Triebwerksleistung, EGT und Treibstoffeffizienz sind anhand der Performancedaten des POH eingestellt. Gewicht und Verteilung verhalten sich ebenfalls wie im POH beschrieben. Fliege nach dem Handbuch - ein link dazu is am Ende dieses Artikels verlinkt.

[[File:c182-panel-detail.jpg|center|800px]]

Das Flugzeugmodell bietet verschiedene Lackierungen an, darunter einige realistische von echten Vorbildern, aber auch generische, die eine eigene Typnummer unterstützen.

Im cockpit findet sich eine realistische Variante des [[De/Autopilot_Bendix/King_KAP140|Bendix KAP140 Autopilot]]. Das Cockpit kann mithilfe verschiedener Leuchtmittel beleuchtet werden (die beiden Cockpitknöpfe zum Drehen sowie die Überkopfleuchten; für den Notfall gibt es im Flugzeugmenü auch eine Taschenlampe).

Mit aktiviertem ALS gibt es Regen- und Frosteffekte auf den Scheiben, Schatten im Cockpit sowie Lande- und Taxilichter.

Es gibt auch Bodenequipment wie eine externe Stromversorgung (-> Flugzeugmenü), Tankwagen, Leitern und ein Vorheizgerät.
Dazu kommt noch realistisches Preflight wie Sicherungsspangurte und Radkeile.

[[File:c182-objects.jpg|600px|center|Cessna 182S with static elements]]

==Feature-Liste:==
Details und Nutzungshinweise sind auch in der [https://github.com/HHS81/c182s/blob/master/Documentation.md documentation] einzusehen.
* Akkurates Flugmodell, basierend auf aerodynamischen Koeffizienten und dem POH
* Akkurate Treibstoffverbrauchszalen, Triebwerksleistung, Geschwindikeit und Steigrate in nahezu allen Luftdruck- und temperaturumgebungen (<5% Unterschied zum POH)
* realistische Stalleigenschaften
* Berechnung des echten KIAS basierend auf KCAS, basierend auf dem POH
* Akkurate Gewichts- und -verteilungseigenschaften

* Verschiedene Startkonfigurationen (z.b. "Start im Flug")
* Autostart für Einsteiger

* Vollständige Simulation des Treibstoffsystems: Treibstoffluss durch Gravitation, Benzinpumpen, korrekte Priming-Prozedur für Kaltstart (siehe POH), Treibstoffkontamination
* Realistische Bordelektronik (Batterieleistung abhängig von Temperatur; funktionierende Sicherungen)
* Vollständige Simulation des Ölmanagements (Temperatur, Füllstand, Öltyp...)
* Simulatin der Kabinentemperatur und Frost/angelaufene Scheiben
* Simulation der Flügel- und Properllervereisung, Vereisung der Luftfilter, Statikportöffnungen und des Pitotrohrs
* Detaillierte Schadens- und Fehlersimulation

* Hochqualitatives 3D-modell und texturen
* Realistische Reflektionen der Außenhaut
* Auswählbare Chromnabe für den Propeller und die Radabdeckungen
* Sehr detailliertes 3D-Interieur
* Funktionale und bewegliche Sonnenblenden
* Alle Cockpitknöpfe funktionieren
* Vollständig funktionierendes Audiopanel
* Vollständiger und realistischer [[De/Autopilot_Bendix/King_KAP140|Bendix KAP140 Autopilot]]
* Vollständig funktionierende [[De/Davtron M803|Davtron M803]] Digitaluhr
* Vollständig funktionierender Bendix King avionics stack (zwei [[De/Kx165|KX-165 VHF COM/NAV radios]], [[De/Bendix_King_KN62A_DME|KN-62A DME]], [[Bendix_King_KT_76A|KT-67C Transponder]], [[De/Bendix_King_KR_87_ADF|KR-87 ADF]])
* Realistische Innenbeleuchtung und Schatteneffekte mit ALS Renderer
* Angelaufene scheiben und Frostsimulation mit ALS Renderer
* Optionales und voll funktionsfähiges Winterausrüstungs-Kit
* Außenequipment wie Leitern, Pylonen, Sicherungselemente, Externe Stromversorgung, Vorheizgerät, ....

* Fast vollständige Vorflugkontrolle
* Flugzeug merkt sich optional den letzten Zustand beim Verlassen von FlightGear
* Viele Lackierungen (mehrere mit multiplayerfähigen eigener Kennung)

=== Flugzeugschlepp für Segelflieger ===
Die C182S und C182T sind fähig, [[Howto: Do aerotow over the net|Segelflieger im Mehrspielermodus zu schleppen]]. Hierfür muss der Segelflugpilot {{key press|Ctrl|o}} drücken, wenn er hinter der Cessna ist.
Der Cessnapilot kann den Haken jederzeit mit {{key press|Shift|O}} lösen.

=== Multiplayer Copilot (Dual control) ===
Das Flugzeug unterstützt einen menschlichen Copiloten, der im Multiplayer mitfliegen kann [[Dual control|("Dual control")]].
Der Copilot muss die copilotvariante laden und dann das Pilotenflugzeug im "Multiplayer"-Menü auswählen.
Der Copilot muss entsprechend auf die gleiche Weise den Piloten auswählen.

Der Copilot ist im Moment nur Zuschauer und kann selbst nicht ins Flugzeug eingreifen.

=== Fallschirmspringer ===
Über das Flugzeugmenü kann die Cessna umgebaut werden (entfernen der rechten Tür und der Sitze), um Fallschirmspringer zu transportieren.
Werden die Passagiere angekickt, klettern sie hinaus und springen ab.
Die Fallschirmspringer sind sogar im Mehrspielermodus sichtbar, wenn die anderen Piloten das C182S-Modell installiert haben!

Anmerkung: Im Moment wird nur die Gewichtsverlagerung und der Windwiderstand simuliert, nicht das 3D-Modell beim Hinasuklettern (siehe [https://github.com/HHS81/c182s/issues/515 FR issue ticket #515]).

=== Erweiterte Fehler / Überraschungsmodus ===
Das Flugzeug bietet eine sehr detaillierte Fehlersimulation an. Optional kannst du dich auch zufällig überraschen lassen (sogar, ohne dich über einen aufgetretenen Fehler zu informieren). Das Fehler-Dialogfenster kannst du über das Flugzeugmenü erreichen. Du kannst die zufälligen Fehler auch für den Simulatorstart konfigurieren, indem du Konfigurationsoptionen hinterlegst. Details sind in der [https://github.com/HHS81/c182s/blob/master/Documentation.md#extended-failure-simulation Dokumentation] einzusehen.

== Flugzeugbedienung (für Einsteiger) ==
Du kannst jederzeit realistischere Simulationsoptionen über das Flugzeugmenü zuschalten; beispielsweise Treibstoffverunreinigung, Ölmanagement und realistische Motorsimulation inkl. Startverhalten.

Generell bietet die Checkliste eine vollständige Kurzanleitung für die Grundfunktionen des Flugzeug. Die Checkliste ist im Menü "Hilfe" von FlightGear verfügbar.

=== Vorflugkontrolle ===
[[File:C182-ready-for-take-off.jpg|270px||thumb|Cessna 182S bereit zum Start]]
Für die Vorflugkontrolle wird empfohlen, den "walker" zu aktivieren und damit um das Flugzeug zu laufen.

Es wird empfohlen, eine Außenansicht oder den Walker hierfür zu verwenden und im Gegenuhrzeigersinn um das Flugzeug zu gehen.
* Cockpit: Entfernen der Sicherung am Steuerhorn
* Überprüfe die Treibstoffmenge durch Klicken auf die Tankdeckel oben auf jeder Fläche
* Linke Tragfläche: Entferne den Spanngurt
* Linke Tragfläche: Entferne die Abdeckung des Staurohrs
* Linke Tragfläche: Überprüfe den Treibstoff auf Verschmutzung durch Klicken unterhalb der Tragfläche und Entnahme einer Treibstoffprobe. Ist diese hellblau, so ist der Treibstoff nicht verschmutzt und die Probe kann in den Tank zurückgegeben werden. Ist sie (teilweise) durchsichtig, enthält der Tribstoff Wasser, und die Probe muss entsorgt werden. Der Vorgang ist so lange zu wiederholen, bis die Probe komplett hellblau ist
* Linke Seite: Entferne den Radkeil am Hauptrad
* Heck: Entferne den Spanngurt
* Rechte Tragfläche: Entferne die Spanngurte
* Rechte Tragfläche: Überprüfe den Treibstoff auf Verschmutzung
* Rechte Seite: Entferne den Radkeil am Hauptrad
* Rechte Schnauze: Überprüfe den Treibstoff auf Verschmutzung am Treibstoffwähler (unter dem Flugzeug) und Treibstoffilter (rechte Nase)
* Schnauze: Überprüfe den Ölstand durch Klicken auf den Ölstutzen in der Nase. Niedriger Ölstand ist unterhalb 6.0 Quarts.
* Schnauze: Entferne den Radkeil am Bugrad

=== Motor Kaltstart (manual and complex startup) ===
* Gemisch: Idle-Cutoff (roter Hebel voll raus)
* Propeller: High RPM (blauer Hebel voll drin)
* Gashebel: 1/4 Zoll offen (schwarzer Hebel bei ~5%-8% Einstellung in der Simulation)
* Parkbremse: Angezogen ({{Key press|Shift|B}})
* Hauptschalter: An (beide roten Kippschalter)
* Treibstoff-Hilfspumpe: An
* Gemisch auf voll schieben, ca. 3 Sekunden halten, bis stetiger Treibstoffluss erreicht wird
* Dann Gemisch: Idle-Cutoff
* Treibstoff-Hilfspumpe: Aus
* Magnete: Beide (Drücke {{Key press|<nowiki>}</nowiki>}} 3x)
* Zündung: Start (halte {{Key press|S}} bis der Motor läuft)

Falls der Motor abgesoffen ist (zu viel Priming mit der Treibstoffpumpe):
* Gemisch: Idle-Cutoff
* Gashebel: 1/2 bis voll eingeschoben
* Zündung: Start (halte {{Key press|S}} bis der Motor läuft). Sobald der motor anspringt, Gemisch voll angereichert (roter Hebel rein) und Gashebel auf Leerlauf (fast ganz heraus).

War der Motor bereits vor kurzem auf Betriebstemperatur, reicht es in der Regel, das Gemisch auf Rich ("Fett") zu stellen (roter Hebel rein), und den Starter zu betätigen.

Alternativ zum manuellen (kalt-)Start gibt es eine Autostartfunktion im Flugzeugmenü.

=== Start ===
* Keine Landeklappen, oder 10 Grad
* Kühlklappen offen ({{Key press|Shift|F}} mehrfach drücken)
* Vollgas
* Rotieren bei ca. 50-60 KIAS

=== Steigflug ===
* Keine Landeklappen
* Kühlklappen offen
* Vollgas
* 80 KIAS
* Sobald sichere Flughöhe erreicht/Hindernisse überflogen: Gas zurücknehmen, um Motoranzeigen in die grünen Bereiche zu bringen
** Treibstoffluss: max 15Gph
** Gashebel: max 23 in.Hg

=== Reiseflug ===
[[File:c182-default.jpg|270px||thumb|Cessna 182S in der Luft]]
* Propeller: 2000-2400 RPM
* Gashebel: 18-23 mp
* Mixture "Fette Seite" über der EGT-Spitze als empfohlene "magere Einstellung" für den Reiseflug; oder 125°F EGT fetter für besten Schub
* Geschwindigkeit zwischen 120-140 Knoten IAS (abhängig von der Leistungseinstellung
* Kühlklappen geschlossen ({{Key press|f}} nach Bedarf -> CHT Anzeige beachten)

=== Landung ===
* Landeklappen 20 grad oder Voll
* 60-70 KIAS

=== Flugzeuggeschwindigkeiten ===
: ''Siehe auch [[De/Fluggeschwindigkeit#V-Speeds]]''

{| class="wikitable"
! Geschwindigkeit !! IAS
|-
| Überziehgeschwindigkeit, Landekonfiguration, V<sub>S<sub>0</sub></sub> || 36 kt
|-
| Überziehgeschwindigkeit, Reiseflugkonfiguration, V<sub>S<sub>1</sub></sub> || 43 kt
|-
| Rotationsgeschwindegkeit, V<sub>R</sub> || 55 kt
|-
| Bester Steigwinkel, V<sub>X</sub> || 63 kt
|-
| Höchste Steigrate, V<sub>Y</sub> || 80 kt
|-
| Höchstgeschwindegkeit bei ausgefahrenen Landeklappen, V<sub>FE</sub> || 100 kt
|-
| Manövergeschwindigkeit, V<sub>A</sub> || 110 kt
|-
| Maximale Reisegeschwindigkeit, V<sub>NO</sub> || 140 kt
|-
| Maximal zulässige Höchstgeschwindigkeit, V<sub>NE</sub> || 175 kt
|-
| Maximaler Seitenwind bei Landung|| 15 kt
|}

=== Performance ===

{| class="wikitable"
|Reiseflug, 80% Leistung, 6,000 ft || 140 kt
|-
|Reiseflug, 65% Leistung, 8,000 ft || 130 kt
|-
|Reiseflug, 55% Leistung, 10,000 ft || 121 kt
|}

{| class="wikitable"
|Entfernung, 75% Leistung, 6,000 ft || 820 nm
|-
|Entfernung, 65% Leistung, 8,000 ft || 910 nm
|-
|Entfernung, 55% Leistung, 10,000 ft || 968 nm
|}

{| class="wikitable"
|Beste Steigrate<ref>POH 5-19; bei 3100lbs, Seehöhe, 2400 RPM, Vollgas, Gemisch gesetzt nach "Maximum power Fuel Flow"-Plakette, Kühlklappen Offen, Standardtemperatur</ref> || 924fpm
|-
|Dienstgipfelhöhe || 18,100ft
|-
|Startrollweg: 795ft über 50ft Hindernis || 1,514ft
|-
|Landerollweg: 590ft über 50ft Hindernis || 1,390ft
|}

[[File:c182-cockpit-at-night.jpg|600px|center|Cessna 182S Konsolenbeleuchtung]]

== FAQ ==
'''''Ich frage mich, warum die 182s einfacher zu fliegen sein sollte, als die 172p?'''''

Ist sie das? Falls du denkst, das FDM (Flugdynamikmodell) ist nicht korrekt: Ein FDM ist nur so gut wie die zugrundeliegenden Daten. Das FDM der c182s benutzt reale Koeffizienzdaten, wo diese verfügbar sind, aber nicht alle benötigten Koeffizienten wurden gefunden. Wo diese nicht aufzutreiben waren, haben wir Beschreibungen von Piloten echter C182 benutzt, und diese sind naturgemäß subjektiv.

'''''Nach google stimmen die meisten Piloten überein, dass die 182 schwerer zu fliegen ist, als die 172'''''

Nicht wegen der Flugeigenschaften. Allerdings verbiegen sich viele Piloten beim Landen die Firewall, weil die Nase schwerer ist als bei einer 172. Viele Piloten mögen allerdings die größere Leistung, höhere Geschwindigkeit, die bessere Dienstgipfelhöhe, den [[constant speed propeller|Festdrehzahlpropeller]], Kühlklappen und die [[IFR]]-Ausrüstung. Und das ist auch schon der Grund - wegen all diesen Extras ist es schwerer, eine 182 zu fliegen, als eine 172. Die FAA zählt die Cessna 182 zu den "high perfomance aircraft". Stell dir vor, du befindest dich in einer überfüllten Gegend wie KLAX, im Anflug auf den Flughafen, während du alle paar Sekunden dem Funkverkehr zuhörst, die Höhe und Geschwindigkeit überwachst, den Motor regelst, die Nadeln des [[VOR]] jagst, alles gleichzeitig während du auf den Verkehr achtest und in schlechtem Wetter unterwegs bist - herausfordernd!

Vielleicht möchtest du dies hier lesen (englisch): [https://pilotbrian.blogspot.com/2009/05/stepping-up-to-c182.html Stepping Up to a C182 ]

'''''Wurde bei der C182S die Einfachheit zu fliegen gegenüber dem Realismus bevorzugt'''''

Nein. Die Autoren benutzen echte Zahlen und Daten als Grundlage, sofern sie verfügbar sind, und das Ziel ist ein möglichst realistisches Modell. Beispielsweise stimmen die Flugwerte sehr nah mit denen im POH überein, und es werden echte aerodynamische Koeffiziente eingesetzt, falls verfügbar.
Falls du etwas entdeckts, dass nicht passt, eröffne bitte ein [https://github.com/HHS81/c182s/issues Ticket im Entwicklungsprojekt] und wir finden heraus, was los ist.

'''''Warum hüpfe ich bei Landungen immer über die Rolbahn?'''''

Die C182 ist sehr Frontlastig, vor allem im Vergleich zu einer 172. Das erschwert den Flare bei der Landung, und du brauchst eine relativ ungewohnte, [[:File:C182s-LandingPicture.jpg|hohe Neigung]] um nicht zu früh aufzusetzen. Auch die Geschwindigkeit ist ein kritischer Faktor, versuche nicht mit zu hoher Geschwindigkeit zu landen (peile 60-70 KIAS für den Endanflug an, je nach Wind und Flaps). Am wichtigsten aber: Versuche nicht, die Maschine mit dem Steuerhorn auf den Boden zu zwingen, und lande nie mit dem Bugrad zuerst.
Eine perfekte Landung erkennst du daran, dass du die Stall-Warnung hörst, kurz bevor du sanft mit den beiden Rädern des Hauptfahrwerks aufsetzt, und wenn du danach das Bugrad sanft aufsetzt.

'''''Auf 3.000 ft komme ich nicht über 110 Knoten. MP: 23, RPM: 2450, Fuelflow: 14. Was hab ich übersehen?'''''

Die Checkliste! Wenn du nicht so schnell fliegst, wie du erwartest, prüfe: Gemisch, Propellergeschwindigkeit, Kühlklappen, Vereisung, Motordefekt (oder kalt).
Meistens wurde einfach vergessen, die Lande- oder Kühlklappen zu schließen. Ein anderer Grund kan sein, dass du [[De/Fluggeschwindigkeit#True_airspeed|KTAS (Knots True Airspeed) und KIAS (Knots Indicated Airspeed)]] verwechselst: Die Tabellen und Publikatoinen geben die Geschwindigkeit oft in KTAS an, und du musst KTAS vom {{wikipedia|Fahrtmesser|lang=de}} ablesen. Wie das geht? - lies weiter.

''''' Wie lese ich meine wahre Fluggeschwindigkeit ab? ([[De/Fluggeschwindigkeit#True_airspeed|KTAS]])?'''''

Der {{wikipedia|Fahrtmesser|lang=de}} hat ein kleines Fenster am oberen Rand. Mit dem Drehrad links unten stellst du die dahinterliegende Scheibe so ein, dass die Höhe (bei Standarddruck=29.92 inHG!) mit der Außentemperatur übereinstimmt. Im unteren Fenster des Fahrtmessers kannst du dann einfach über die Nadel die KTAS ablesen.

[[:File:C182s-ais-tas.png|Es gibt einen Screenshot]] der die Verwendung der TAS-Scheibe zeigt.

'''''Als ich in kaltem Wetter geflogen bin, verlor ich Fahrt und bin abgestürzt. Wo ist die Vergaservorwärmung?'''''

Die Cessna 182S hat keinen Vergaser, da sie einen Motor mit Direkteinspritzung benutzt. Was du allerdings erfahren hast, war Vereisung des Propellers und Flugzeugs.
Mit diesem Flugzeugtyp ist es nicht erlaubt, unter Bedingungen zu fliegen, die wahrscheinlich zu Vereisung führen. Vermeide feuchte Luft (Wolken....) bei Temperaturen um den Gefrierpunkt.

'''''Cessna 182S lässt sich nicht starten'''''

Möglicherweise ist folgendes passiert:
# vielleicht bist du der checkliste nicht akkurat genug gefolgt.
# vielleicht hast du den Motor beim Primen absaufen lassen. Folge [[De/Cessna_182S#Motor_Kaltstart_.28manual_and_complex_startup.29|der Prozedur am Ende dieses Abschnittes]].
# Nach einem missglückten Motorstart bei Temperturen unter dem Gefrierpunkt könnten nun die Zündkerzen vereist sein. Schließe das Vorheizgerät an und versuche es nach 5-10 (simulierten) Minuten erneut.
# Der Motor ist einfach zu kalt um anzuspringen. Schließe das Vorheizgerät an.
# du hast den Motor früher so beschädigt, dass er jetzt nicht mehr starten kann (hast du dunklen Qualm aus der Motorhaube bemerkt?).

'''''Mein Motor überhitzt beim Starten/Steigflug dauernd!'''''

Sobald du alle Hindernisse überflogen hast solltest du die Motorleistung reduzieren. Überwache die CHT-Anzeige engmaschig, und nimm die Leistung spätestens vor dem oberen Limit zurück.
Schau auch in den "Normal enroute climb" Abschnitt der Checkliste, um Details zu den Einstellungen zu finden (Kurzgesagt: halte Gas und Treibstoffluss im grünen Bereich, Kühlklappen offen).

'''''Warum kann ich die Flügelenden und die Motorhaube nicht sehen?'''''

Die Kopf/Augenposition wurde sorgfältig ausgewählt, nachdem wir Bilder der Cessna 182S/T und Pilotenberichte verglichen haben. Wenn du das ansiehst, stellst du fest, dass die Augenhöhe des Piloten mit der Oberkante des seitlichen Fensterrahmens übereinstimmt. Der Flügel sitzt jedoch viel höher, d.h. es ist unmöglich, das Flügelende zu sehen.
Der Blendschutz des Armaturenbretts ist ziemlich hoch, und so kannst du die Motorhaube vor dir nicht sehen.

== Entwicklungsstand / Fehler / ToDos ==

Dieses Flugzeugmodell wird kontinuierlich weiterentwickelt. Hierfür gibt es ein öffentliches [https://github.com/HHS81/c182s Repository], in dem auch eine [https://github.com/HHS81/c182s/issues Liste von offenen Fehlern und Erweiterungsideen] geführt wird. Das Repository ist einen Besuch wert!

* '''Defektes Fahrwerk in Multiplayer''': Das Schadensmodell wurde 5/2021 für FlightGear 2020.4.0 erweitert um Schaden daran zu simulieren. Ältere Versionen (2020.3 und älter) erhalten die Multiplayer-Daten hierfür nicht. Das führt dazu, dass das das "Fahrwerk-OK"-Property konstant ein defektes Fahrwerk für ältere Modelle anzeigt, wenn man selbst ein neueres Modell geladen hat. Die Lösung ist, dass der Pilot, der die ältere Modellversion hat, auf die neuere Version aktualisiert (aus FGADDON über den Launcher).

=== Die aktuellste Entwickerversion benutzen ===
Wenn du die aktuellste (potentiell unveröffentlichte) Version von github benutzen möchtest, kannst du sie ganz einfach herunterladen.
Es kann sein, dass diese Version nicht mit älteren FlightGear-Versionen funktioniert. Die Entwicklung zielt normalerweise darauf ab, die aktuell stabile FlightGear-Version zu unterstützen, allerdings kann es auch passieren, dass auf neueste Entwicklungen in FlightGear aufgebaut wird, und dann funktioniert das Flugzeug nur auf der FlightGear Entwicklerversion.

* Erstelle an einem für dich passenden Ort eine neuen Ordner namens "Aircraft" (falls du noch keinen solchen hast). Füge diesen Ordner im FlightGear-Starter im "Addons"-Tab als "Zusätzliche Flugzeug-Verzeichnisse" hinzu.
* Lade ein ZIP-Paket herunter (siehe Links in "Versionen" unten)
* Entpacke dieses ZIP-Paket in deinen "Aircraft"-Ordner
* Benenne den Ordner um: <code>c182s-<version></code> => <code>c182s</code>.

'''Versionen:'''
* Die letzte offizielle Veröffentlichug findest du hier: https://github.com/HHS81/c182s/releases. Dieses Release wird normalerweisein FGADDON für die nächste stabile FlightGear-Version ("next") hochgeladen und ist dann über den FlightGear-Starter bequem zu installieren. Kompatible Änderungen werden auch Fallweise in die aktuelle stabile FlightGear-Version zurückportiert.
* Aktuellster Entwicklungscode (<code>master</code>-branch) kann hier bezogen werden: https://github.com/HHS81/c182s/archive/refs/heads/master.zip

== Gallery ==
{{screenshot cat
| category = Cessna 182S screenshots
| subject = der Cessna 182S
| image = C182-default.jpg
}}{{-}}
<gallery mode="packed">
GXLTGAltenrhein.jpg|Flugzeug auf dem Vorfeld St. Gallen-Altenrhein/ Schweiz
Cessna182S compositor2.jpg|Flugzeug im Dunkeln, alle Lichter an
c182s.jpg|Cessna 182S am Abend
c182-cockpit-view.jpg|Standard Cockpitsicht
c182-external2.jpg|HB-CZV livery
c182-external3.jpg|D-ELFP livery
c182-external5.jpg|Cessna 182S über Kalifornien
c182-external6.jpg|Weitere Ansicht des HB-CZV livery
C182-4.jpg|Taking off
c182-rosskopf-at-dusk.jpg|Cessna 182S bei Roßkopf in Freiburg/ Deutschland
C182STakeOff.jpg|Cessna 182S mit selbstgewählter Kennung bei Siegerland / Deutschland
C182s-LandingPicture.jpg|C182s Landung, zeigt die nötige hohe Neigung
C182SDavtron803.jpg|Die Davtron 803 digitaluhr in Aktion
C182SWinterKit.jpg|Winterkit ausgerüstet, und Vorheizen mit dem Dragon heater
C182SFuelManagement.jpg|Fuel Management Dialog
c182-rain.jpg|Regeneffekt auf der Windschutzscheibe
C182-oil-cap.png|Position der Klappe zum Ölmesstab
C182SOilManagement.jpg|Oil Management Dialog
C182-fuelports.png|Treibstoffwähler und -filter Prüfports
c182-night-take-off.jpg|Ready to take off bei Nacht
c182-3.jpg|D-ELFP am Abend
C182SPitot.jpg|Pitot, Cover und Nachricht
C182SFreeMovementCheck.jpg|Prüfen der Querruder
C182SCustomRegistration.jpg|Selbstwählbare Kennung
c182-external4.jpg|N182PJ livery
c182-external-at-night.jpg|Default livery bei Nacht
c182-external1.jpg|N321HW livery
C182Scrashed.jpg|Flugzeug beschädigt
AboveSouthGermany.jpg|Flugzeug fliegt über Süddeutschland
Cessna182S compositor.jpg|Flugzeug im Dunkel, alle Lichter an

</gallery>

== External links ==
* {{Wikipedia|Cessna 182 Skylane|lang=en}}
* [http://www.freechecklists.net/Resources/Cessna/182S+Skylane/ Links to Cessna 182S Checklists and W&B sheet]
* [http://tssflyingclub.org/documents/C182S_POH.pdf Cessna 182S POH]
* [https://www.aopa.org/go-fly/aircraft-and-ownership/aircraft-fact-sheets/cessna-182 Cessna 182S Aircraft Information Booklet]
* [http://www.jberaeroclub.com/uploads/1/7/4/0/17405139/c182maneuversguiderev2.pdf C182 Standardized flight maneuvers guide]
* [https://airplaneacademy.com/9-actionable-cessna-182-landing-tips-you-can-implement-today/ 9 Actionable Cessna 182 Landing Tips You Can Implement Today]

{{Appendix}}

{{Cessna}}

[[Category:Aircraft with a cockpit-only autopilot]]
[[Category:Red Griffin ATC compatible aircraft]]

[[en:Cessna 182S]]

Cessna 182S

2024-04-08T16:26:26Z

Hbeni: /* Feature-List: */

{{:{{PAGENAME}}/info}}

The '''Cessna 182S Skylane''' is an American four-seat, single-engine, light [[Aircraft|airplane]], built by [[Cessna]] between 1996 and 2001. It uses a fuel-injected Textron Lycoming IO-540 AB1A5 with 230 HP at 2,400 RPM.

== Features ==
The Cessna 182S is one of the high-quality aircraft models in FlightGear.

The new Cessna 182S has a very detailed 3D model and a cockpit with highly detailed textures. Most of the switches in the cockpit are already clickable and working. It has a very realistic FDM based on real aerodynamic coefficients and the pilot operating handbook; engine power, EGT and fuel performance are tuned according the pilot operating handbook, the weight and balance behaves like written in the POH. Fly by the book - a link to real POH is given at the end of this page.

[[File:c182-panel-detail.jpg|center|800px]]

There are currently several liveries available: default Cessna livery, Blank, D-ELFP, HB-CZV, N182PJ, N321HW and some Custom registration Liveries.

The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]]. The cockpit can be illuminated at night by using the glareshield lighting, pedestal lighting and instruments/ radio lighting, controlled by two knobs. Dome lights which illuminates the cabin in a realistic way are in work. The knobs have two modes each, which can be used by clicking and dragging horizontally or vertically.

Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, some effects are activated such as cockpit shadows, visible landing lights from the cockpit and rain effect on the windshield.

The Cessna 182S comes with static objects which can be activated via the Ground Equipment dialog in the aircraft menu. These include a fuel tank trailer, ladders to access the fuel caps (and which the walker can climb(only in FG Versions before 2017.3.1 !!), ground power unit and a Dragon Engine Pre-Heater. Security cones are also available. Special Feature: The ground equipment will stay on ground where placed, independent from the movement of the aircraft! The aircraft can also go through a pre-flight check: wheel chocks, tie-downs and the pitot tube cover can now be added or removed.

[[File:c182-objects.jpg|600px|center|Cessna 182S with static elements]]

==Feature-List:==
For details and usage hints, please also read the [https://github.com/HHS81/c182s/blob/master/Documentation.md documentation].
*accurate flight model based on real test aerodynamic coefficients and POH
* accurate fuel flow numbers, engine power, airspeed and climbrate in nearly all pressure altitudes and temperatures with less than 5% difference from POH
* realistic stall behavior
* calculation of real KIAS based on KCAS, based on POH
* accurate weight and balance behavior

* New Start-up States: aircraft can be initialized in cruise, landing, takeoff and more states
* autostart for beginners

* fully simulated fuel system: fuel flow by gravity, engine pump and fuel pump simulated for each of the two tanks,; engine needs correct priming procedure according POH, fuel contamination simulated
* realistic electrical system, battery charge state depending on temperature, working circuit breakers
* fully simulated oil management (temperature, ....)
* simulation of cabin heat and defrost
* simulation of icing to wings, propellers and engines in icing conditions
* detailed damage and failure simulation

* High quality 3d-model, textures and animations
* Realistic exterior reflection shaders with fresnel effect and normalmap
* selectable chromed spinner and wheel fairings
* Very detailed 3d-interior
* moveable sun-visors
* all cockpit switches are working
* fully working audio panel
* fully simulated [[Bendix/King_KAP140_Autopilot]]
* fully simulated [[Davtron M803]] digital clock
* fully simulated Bendix King avionics stack (two [[Kx165|KX-165 VHF COM/NAV radios]], [[Bendix_King_KN62A_DME|KN-62A DME]], [[Bendix_King_KT_76A|KT-67C Transponder]], [[Bendix_King_KR_87_ADF_Receiver|KR-87 ADF]])
* Realistic interior light effects in ALS-Renderer
* Interior shadows in ALS-Renderer
* interior glass frost and fog effects in ALS-Renderer
* Exterior 3d-shadow in ALS-Renderer
* selectable and fully simulated Winterization kit
* External equipement like ladders, safety cones, tie ups, pitot cover, wheel chocks, external power source, simulated external engine pre-heater with sound - they keep their position on ground!
* aircraft can be preflight checked outside (free movement check of flight control surfaces; oil, fuel, pitot heat, ....)
* Walker - can be used to follow the Checklist outside
* [[Howto:Implement_Towbar|Towbar]] connecting to the nosewheel for ground handling
* Save states: aircraft remembers last switch, systems and configuration state
* Many liveries

=== Aerotowing gliders ===
The C182S and C182T are capable of [[Howto: Do aerotow over the net|aerotowing over multiplayer]] by the glider pilot pressing {{key press|Ctrl|o}} while behind the Cessna.
The Cessna pilot can release the hook anytime by pressing {{key press|Shift|O}}

=== Dual control ===
The plane supports [[Dual control]] where a copilot can ride along in another multiplayer plane. The copilot needs to start the C182 copilot variant and then select the pilots plane from the multiplayer dialog. The pilot also need to select the copilot this way.

Currently the copilot is view-only and cannot take over controls.

=== Parachuters ===
Via the aircraft options menu you can remove the right cabin door and seats, to haul parachuters. When clicking on your passengers, they will climb out to the strut and jump off.
The parachuters are even visible to other multiplayer aircraft (for that to work they need the C182s/t model installed)!

Note: The climb out procedure is modeled in regards to weight shift and drag, but not yet animated (see [https://github.com/HHS81/c182s/issues/515 FR issue ticket #515]).

=== Extended failures / surprise mode ===
The plane features a very detailed failure simulation and optionally can surprise you on the fly (if you wish, without notifying you). The failures dialog can be accessed by the aircraft menu, but you can also configure this for startup in your launcher by adding configuration options there. Please see [https://github.com/HHS81/c182s/blob/master/Documentation.md#extended-failure-simulation the documentation] for details.

== Handling The Aircraft (beginner version)==
You can activate more realistic handling at any time in the aircraft dialog, like fuel contamination, engine oil management and priming needs.

The full checklists are available ingame in the checklists dialog.

=== Pre-Flight Inspection ===
[[File:C182-ready-for-take-off.jpg|270px||thumb|Cessna 182S ready for take off]]
It's recommended to use any exterior view or activate the walker for these procedures.

* Cockpit: remove wind gust lock
* Check fuel quantity on both tanks (click on the red caps top of the wings)
* Left wing: remove pitot tube cover
* Left wing: remove tie-down
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue
* Left main wheel: remove chocks
* Tail: remove tie-down
* Right wing: remove tie-down
* Right wing: check water contamination
* Right main wheel: remove chocks
* Right nose: check water contamination of fuel selector (below plane) and fuel strainer (right nose)
* Nose: remove wheel chocks
* Nose: check oil level (more than 6.0 quarts)
* Nose: remove chocks

=== Engine Start (manual and complex startup) ===
* Mixture: Idle cut-off (red lever full out)
* Propeller: High RPM (blue lever full in)
* Throttle: Open 1/4 inch (black lever ~5%-8% setting inSim)
* Parking Brake: Applied ({{Key press|Shift|B}})
* Prop Area: Clear
* Master switch: ON (both)
* Auxiliary Fuel Pump Switch: ON
* Advance mixture to full rich, keep it 3-5sec
* Then Idle Cutoff
* Auxiliary Fuel Pump Switch: Off
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)
* Ignition: crank engine ({{Key press|S}} until engine fires)

If the engine was warm already, it usually starts without priming by just setting Mixture to rich and cranking.

If engine floods, then set mixture to idle cut off and throttle to 1/2 to full open and crank. When engine fires, set mixture to full rich and throttle to idle.

=== Takeoff ===
* no flaps or flaps 10deg
* cowl flaps open ({{Key press|Shift|F}} several times)
* full throttle
* rotate at 50-60 KIAS

=== Climbout ===
* no flaps
* cowl flaps open
* full throttle
* 80 KIAS
* Reduce power to stay in the green arcs as soon as obstacles are clear
** Fuel flow: max 15Gph
** Throttle: max 23 in.Hg

=== Cruise ===
[[File:c182-default.jpg|270px||thumb|Cessna 182S in the air]]
* 2000-2400 RPM
* 18-23 mp
* mixture rich of peak as recommended lean mixture setting for cruise or 125°F rich for best power
* speed between 120-140 knots depending on the power settings
* cowl flaps closed ({{Key press|f}} as appropriate -> watch CHT gauge)

=== Landing ===
* flaps 20deg or full flaps
* 60-70 KIAS

=== Airspeeds ===
: ''See also [[Aircraft speed#V speeds]]''

{| class="wikitable"
! Airspeed !! IAS
|-
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 36 kt
|-
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 43 kt
|-
| Rotation speed, V<sub>R</sub> || 55 kt
|-
| Best angle of climb speed, V<sub>X</sub> || 63 kt
|-
| Best rate of climb speed, V<sub>Y</sub> || 80 kt
|-
| Maximum flap extended speed, V<sub>FE</sub> || 100 kt
|-
| Manoeuvring speed, V<sub>A</sub> || 110 kt
|-
| Maximum structural cruising speed, V<sub>NO</sub> || 140 kt
|-
| Never exceed speed, V<sub>NE</sub> || 175 kt
|-
| Max. Crosswind at landing || 15 kt
|}

=== Performance ===

{| class="wikitable"
|Cruise, 80% power, 6,000 ft || 140 kt
|-
|Cruise, 65% power, 8,000 ft || 130 kt
|-
|Cruise, 55% power, 10,000 ft || 121 kt
|}

{| class="wikitable"
|Range, 75% power, 6,000 ft || 820 nm
|-
|Range, 65% power, 8,000 ft || 910 nm
|-
|Range, 55% power, 10,000 ft || 968 nm
|}

{| class="wikitable"
|Best Climb<ref>POH 5-19; with 3100lbs, sea level, 2400 RPM, Full Throttle, mixture set to Maximum power Fuel Flow placard, Cowl Flaps Open, Std. Temperature</ref> || 924fpm
|-
|Service Ceiling || 18,100ft
|-
|Takeoff ground roll: 795ft (242m) over 50ft obstacle || 1,514ft
|-
|Landing ground roll: 590ft (180m) over 50ft obstacle || 1,390ft
|}

[[File:c182-cockpit-at-night.jpg|600px|center|Cessna 182S panel illumination]]

== FAQ ==
'''''I wonder why would the 182s be easier to fly than the c172p?'''''

Is it? If you think the fdm is wrong: A fdm is only so good as the datas available. The c182s-fdm uses real coefficient data where available, but not all needed coeeficients could be found. Where not available, pilot reports had been used. And they are from a subjective view of the pilot.

'''''According to google, most pilots agree that the 182s is actually harder to fly than the 172p'''''

Not because of its flight characteristics. Though many pilot bends their firewalls on touchdown, due the nose heaviness of that aircraft. But a lot pilot likes the C182 more because of more power, more speed, higher possible altitudes, [[constant speed propeller]], cowl-flaps and the [[IFR]]-equipement. And that`s the reason - due to that all it is much more challenging to fly than the Cessna 172. So FAA counts the Cessna 182 to the high perfomace aircraft. Imagine beeing in a crowded area like KLAX, approaching the airport while listening to Radio calls every few seconds, watching speed, altitude, manage the engine and prop speed, chasing VOR-needles and watching the traffic around at the same time in bad weather condition - challenging!
You might wanna read this: [https://pilotbrian.blogspot.com/2009/05/stepping-up-to-c182.html Stepping Up to a C182 ]

'''''Is the C182S made easier to fly, instead of more realistic to fly?'''''

No. The authors uses real numbers, datas, coefficients and more where available, aiming to get everything realistic as it can be. As an example it matches all the numbers given in the POH, and uses real aerodynamic coeffcients for the fdm where available. If it doesn`t fly as you expect, you might be used to FSX? Just kidding...
Anyway, if encounter something you think it isn`t right, file an Issue-report [https://github.com/HHS81/c182s/issues here], and we will find out.

'''''Why do I always make bouncy landings?'''''

The C182 is quite nose heavy, especially compared to a 172. This makes it harder to flare correctly, and you actually need [[:File:C182s-LandingPicture.jpg|a high pitch attitude]] to not touchdown too early. Also airspeed is a critical factor, don't try to land too fast (aim for 60-70 KIAS, depending on flaps and wind). Most importantly: Don't try to force the plane down with the elevator and never land on the nose gear first. You had a perfect landing, when you hear the stall horn shortly before the main wheels gently touch the runway, and when you managed to lower the nose wheel gently afterwards.

'''''At 3,000 ft, I can't get over 110 knots. MP: 23 RPM: 2450 FF: 14. What am I missing?'''''

The checklist! If it doesn`t get the speed as you expect, check: Mixture, prop rpm, cowl flaps, oil temp, icing, engine damaged or cold,... Probably you simply forget to close the cowl flaps.
Another reason could be that you mistake KTAS (Knots True AirSpeed) with KIAS (Knots Indicated AirSpeed). The tables and many publications gives the speeds in KTAS. So you have to read the KTAS-values from your instruments, not the KIAS. How to?- just read below.

''''' Where I can see my True Airspeed ([[TAS|KTAS]])?'''''
The Air Speed Indicator has a dial at the upper part of the instrument face. So you simply dial in the pressure altitude (=Altimeter set to 29.92) in ft via the knob, and align it with the temperature mark just below.
Now you can read your true airspeed in the lower left window of your instrument.
[[:File:C182s-ais-tas.png|There is a screenshot]] showing an example of using the TAS disc.

'''''I flew in cold weather, but suddenly crashed because the aircraft slowed down. Where is the carb heat?'''''

The Cessna 182S uses an fuel-injected engine - like many modern cars. So there is no carburetor. But what you experienced is the icing of the prop and the aircraft body. Unfortunately there is indeed a bug: propeller icing of constant speed props can`t be simulated yet with JSBSim. The C182S-team tried to find a work-around, but might not have yet found the best solution....Not everything can be perfect! Anyway: with this type of aircraft you are not allowed to fly in known icing-conditions!

'''''Cessna 182S refuses to start'''''

The following might be happening:
# you probably didn`t follow the checklist.
# you might have flooded the engine. Follow this procedure: Pull back mixture to cut off, advance throttle to about about little more than 50-60%, then operate the starter again for a while. If the engine fires, promptly advance the mixture to full rich and return throttle to Idle.
# you may encounter spark plug icing in cold environment after a misfired start. Preheat the engine, wait 5-10 (simulated) minutes and try again.
# the engine might simply be too cold to be able to start. Preheat the engine.
# you damaged the engine previously to a state where it won't start again (have you seen black smoke from the cowling?)

'''''I always overheat my engine at takeoff/climbout!'''''

Reduce power when you cleared all takeoff obstacles. Closely watch your CHT gauge: reduce at latest when approaching the upper CHT limit. See the "Normal enroute climb" checklist section for details on power settings (in short: keep manifold pressure and fuel flow in the greens, open cowl flaps).

'''''Why I can`t see the wingtip and the cowl?'''''

The eye level position has been carefully set comapring informations from pictures showing the Cessna 182S or Cessna 182T and pilot reports. If you compare, you can see that the eye level of the pilot is sitting at the level of the upper edge of the side window frame. The wing root sits much higher, the wingtip even more. So it is impossible to see the wingtip.
The glareshield is quite high on the newer Cessna, and from you usual position you are not able to see the engine cowling in front of you.
And the eye level position is also set to the fact that a good landing is provided why you flare just before the touchdown. Your flare will be correct, when the upper edge of the glareshiels is virtually touching the horizon.

== Versions ==

=== Stable release ===
The Last official release for your matching FlightGear version can be downloaded from the Launcher (FGAddon default Hangar).
There you can also easily update the plane, once updates get published.

Alternatively, GIT releases (and changelogs between versions) are here: https://github.com/HHS81/c182s/releases

These releases are usually also synced to FGAddons trunk hangar (used by fgfs next, which gets stable together with the next fgfs release and can be updated to from the launcher)

=== Development status/Issues/TODO ===

This aircraft is undergoing a constant development, which can be followed on its [https://github.com/HHS81/c182s repository], where a [https://github.com/HHS81/c182s/issues list of issues and future enhancements] can also be found. Worth a visit!

* '''Damaged Gear in Multiplayer''': The damage model was updated recently (5/2021 for 2020.4.0) to also simulate gear collapse. Older versions (2020.3 and before) do not simulate this and thus do not transmit the necessary MP packets. This makes the "gear-OK" Property constantly showing a damage gear, if you use a newer model. The solution is that the pilot using the version showing the "crippled" gear to update his flightgear and plane to the latest FGAddon version OR use the [https://github.com/HHS81/c182s/releases/tag/version-1.4 GitHub release 1.4].

=== Using the latest development/git version ===
{{note|This may not work properly with the current stable (and older) flightgear versions. Development ''usually'' targets the latest flightgear stable, but may use also fresh features of flightgears "next" version.}}

If you want to use the latest github versions, they can be obtained here (<code>master</code>-branch): https://github.com/HHS81/c182s/archive/refs/heads/master.zip

* Make a new "Aircraft" folder (in case you don't already have one). Then add that directory to your launchers "Addons" tab as aircraft folder.
* Download a zipped version you want to use (links below).
* Extract the zipfile into your "Aircraft" folder.
* Rename the extracted <code>c182s-<version></code> folder to <code>c182s</code>.

== Gallery ==
{{screenshot cat
| category = Cessna 182S screenshots
| subject = the Cessna 182S
| image = C182-default.jpg
}}{{-}}
<gallery mode="packed">
GXLTGAltenrhein.jpg|aircraft sitting on the apron of St. Gallen-Altenrhein/ Switzerland
Cessna182S compositor2.jpg|aircraft sitting in the dark, all lights on
c182s.jpg|Cessna 182S at dusk
c182-cockpit-view.jpg|Default cockpit view
c182-external2.jpg|HB-CZV livery
c182-external3.jpg|D-ELFP livery
c182-external5.jpg|Cessna 182S over California
c182-external6.jpg|Another view of the HB-CZV livery
C182-4.jpg|Taking off
c182-rosskopf-at-dusk.jpg|Cessna 182S around Roßkopf in Freiburg/ Germany
C182STakeOff.jpg|Cessna 182S with custom registration at Siegerland Airport/ Germany
C182s-LandingPicture.jpg|C182s landing, showing the needed high pitch attitude
C182SDavtron803.jpg|The Davtron 803 clock in action
C182SWinterKit.jpg|Winterkit installed, and preheating the engine with an Engine Preheater
C182SFuelManagement.jpg|Fuel Management Dialog
c182-rain.jpg|Rain effect in the windshield
C182-oil-cap.png|Oil cap location
C182SOilManagement.jpg|Oil Management Dialog
C182-fuelports.png|Fuel selector and strainer quick drain valves location
c182-night-take-off.jpg|Ready to take off at night
c182-3.jpg|D-ELFP at dusk
C182SPitot.jpg|Pitot, Cover and message
C182SFreeMovementCheck.jpg|Checking the aileron
C182SCustomRegistration.jpg|The custom registration
c182-external4.jpg|N182PJ livery
c182-external-at-night.jpg|Default livery at night
c182-external1.jpg|N321HW livery
C182Scrashed.jpg|aircraft crashed
AboveSouthGermany.jpg|aircraft flying above South Germany
Cessna182S compositor.jpg|aircraft sitting in the dark, all lights on

</gallery>

== External links ==
* {{Wikipedia|Cessna 182 Skylane|lang=en}}
* [http://www.freechecklists.net/Resources/Cessna/182S+Skylane/ Links to Cessna 182S Checklists and W&B sheet]
* [http://tssflyingclub.org/documents/C182S_POH.pdf Cessna 182S POH]
* [https://www.aopa.org/go-fly/aircraft-and-ownership/aircraft-fact-sheets/cessna-182 Cessna 182S Aircraft Information Booklet]
* [http://www.jberaeroclub.com/uploads/1/7/4/0/17405139/c182maneuversguiderev2.pdf C182 Standardized flight maneuvers guide]
* [https://airplaneacademy.com/9-actionable-cessna-182-landing-tips-you-can-implement-today/ 9 Actionable Cessna 182 Landing Tips You Can Implement Today]

{{Appendix}}

{{Cessna}}

[[Category:Aircraft with a cockpit-only autopilot]]
[[Category:Red Griffin ATC compatible aircraft]]

[[de:Cessna 182S]]

File:Kn62a.png

2024-04-08T16:25:51Z

Hbeni: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Bendix/Kiing KN-62A DME}}
|date=2024-04-08
|source={{own}}
|author=[[User:Hbeni|Hbeni]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Instr]]
[[Category:Screenshots of cockpit details]]
[[Category:Aircraft instruments]]

De/Cessna 182S

2024-04-08T16:08:32Z

Hbeni: /* Feature-Liste: */

{{:{{#titleparts:{{PAGENAME}}||2}}/info}}

Die '''Cessna 182S Skylane''' ist ein amerikanischer, viersitziger, einmotoriger Schulterdecker mit festem Dreibeinfahrwerk. [[Cessna]] baute es zwichen 1996 und 2001.
Sie benutzt ein Textron Lycoming IO-540 AB1A5 mit Direkteinspritzung, das 230PS bei 2400 RPM Leistung erzeugt.

== Features ==
Die Cessna 182S ist eines der hochqualitativen Modelle in FlightGear.

Das Cockpit hat ein sehr detailliertes 3D-modell. Alle Schalter und Leuchten sind funktional. Das FDM ist sehr realistisch und basiert auf echten aerodynamischen Koeffizienten sowie dem Pilots Operating Handbook (POH). Triebwerksleistung, EGT und Treibstoffeffizienz sind anhand der Performancedaten des POH eingestellt. Gewicht und Verteilung verhalten sich ebenfalls wie im POH beschrieben. Fliege nach dem Handbuch - ein link dazu is am Ende dieses Artikels verlinkt.

[[File:c182-panel-detail.jpg|center|800px]]

Das Flugzeugmodell bietet verschiedene Lackierungen an, darunter einige realistische von echten Vorbildern, aber auch generische, die eine eigene Typnummer unterstützen.

Im cockpit findet sich eine realistische Variante des [[De/Autopilot_Bendix/King_KAP140|Bendix KAP140 Autopilot]]. Das Cockpit kann mithilfe verschiedener Leuchtmittel beleuchtet werden (die beiden Cockpitknöpfe zum Drehen sowie die Überkopfleuchten; für den Notfall gibt es im Flugzeugmenü auch eine Taschenlampe).

Mit aktiviertem ALS gibt es Regen- und Frosteffekte auf den Scheiben, Schatten im Cockpit sowie Lande- und Taxilichter.

Es gibt auch Bodenequipment wie eine externe Stromversorgung (-> Flugzeugmenü), Tankwagen, Leitern und ein Vorheizgerät.
Dazu kommt noch realistisches Preflight wie Sicherungsspangurte und Radkeile.

[[File:c182-objects.jpg|600px|center|Cessna 182S with static elements]]

==Feature-Liste:==
Details und Nutzungshinweise sind auch in der [https://github.com/HHS81/c182s/blob/master/Documentation.md documentation] einzusehen.
* Akkurates Flugmodell, basierend auf aerodynamischen Koeffizienten und dem POH
* Akkurate Treibstoffverbrauchszalen, Triebwerksleistung, Geschwindikeit und Steigrate in nahezu allen Luftdruck- und temperaturumgebungen (<5% Unterschied zum POH)
* realistische Stalleigenschaften
* Berechnung des echten KIAS basierend auf KCAS, basierend auf dem POH
* Akkurate Gewichts- und -verteilungseigenschaften

* Verschiedene Startkonfigurationen (z.b. "Start im Flug")
* Autostart für Einsteiger

* Vollständige Simulation des Treibstoffsystems: Treibstoffluss durch Gravitation, Benzinpumpen, korrekte Priming-Prozedur für Kaltstart (siehe POH), Treibstoffkontamination
* Realistische Bordelektronik (Batterieleistung abhängig von Temperatur; funktionierende Sicherungen)
* Vollständige Simulation des Ölmanagements (Temperatur, Füllstand, Öltyp...)
* Simulatin der Kabinentemperatur und Frost/angelaufene Scheiben
* Simulation der Flügel- und Properllervereisung, Vereisung der Luftfilter, Statikportöffnungen und des Pitotrohrs
* Detaillierte Schadens- und Fehlersimulation

* Hochqualitatives 3D-modell und texturen
* Realistische Reflektionen der Außenhaut
* Auswählbare Chromnabe für den Propeller und die Radabdeckungen
* Sehr detailliertes 3D-Interieur
* Funktionale und bewegliche Sonnenblenden
* Alle Cockpitknöpfe funktionieren
* Vollständig funktionierendes Audiopanel
* Vollständiger und realistischer [[De/Autopilot_Bendix/King_KAP140|Bendix KAP140 Autopilot]]
* Vollständig funktionierende [[De/Davtron M803|Davtron M803]] Digitaluhr
* Vollständig funktionierender Bendix King avionics stack (zwei [[De/Kx165|KX-165 VHF COM/NAV radios]], [[De/Bendix_King_KN62A_DME|KN-62A DME]], [[Bendix_King_KT_76A|KT-67 Transponder]], [[De/Bendix_King_KR_87_ADF|KR-87 ADF]])
* Realistische Innenbeleuchtung und Schatteneffekte mit ALS Renderer
* Angelaufene scheiben und Frostsimulation mit ALS Renderer
* Optionales und voll funktionsfähiges Winterausrüstungs-Kit
* Außenequipment wie Leitern, Pylonen, Sicherungselemente, Externe Stromversorgung, Vorheizgerät, ....

* Fast vollständige Vorflugkontrolle
* Flugzeug merkt sich optional den letzten Zustand beim Verlassen von FlightGear
* Viele Lackierungen (mehrere mit multiplayerfähigen eigener Kennung)

=== Flugzeugschlepp für Segelflieger ===
Die C182S und C182T sind fähig, [[Howto: Do aerotow over the net|Segelflieger im Mehrspielermodus zu schleppen]]. Hierfür muss der Segelflugpilot {{key press|Ctrl|o}} drücken, wenn er hinter der Cessna ist.
Der Cessnapilot kann den Haken jederzeit mit {{key press|Shift|O}} lösen.

=== Multiplayer Copilot (Dual control) ===
Das Flugzeug unterstützt einen menschlichen Copiloten, der im Multiplayer mitfliegen kann [[Dual control|("Dual control")]].
Der Copilot muss die copilotvariante laden und dann das Pilotenflugzeug im "Multiplayer"-Menü auswählen.
Der Copilot muss entsprechend auf die gleiche Weise den Piloten auswählen.

Der Copilot ist im Moment nur Zuschauer und kann selbst nicht ins Flugzeug eingreifen.

=== Fallschirmspringer ===
Über das Flugzeugmenü kann die Cessna umgebaut werden (entfernen der rechten Tür und der Sitze), um Fallschirmspringer zu transportieren.
Werden die Passagiere angekickt, klettern sie hinaus und springen ab.
Die Fallschirmspringer sind sogar im Mehrspielermodus sichtbar, wenn die anderen Piloten das C182S-Modell installiert haben!

Anmerkung: Im Moment wird nur die Gewichtsverlagerung und der Windwiderstand simuliert, nicht das 3D-Modell beim Hinasuklettern (siehe [https://github.com/HHS81/c182s/issues/515 FR issue ticket #515]).

=== Erweiterte Fehler / Überraschungsmodus ===
Das Flugzeug bietet eine sehr detaillierte Fehlersimulation an. Optional kannst du dich auch zufällig überraschen lassen (sogar, ohne dich über einen aufgetretenen Fehler zu informieren). Das Fehler-Dialogfenster kannst du über das Flugzeugmenü erreichen. Du kannst die zufälligen Fehler auch für den Simulatorstart konfigurieren, indem du Konfigurationsoptionen hinterlegst. Details sind in der [https://github.com/HHS81/c182s/blob/master/Documentation.md#extended-failure-simulation Dokumentation] einzusehen.

== Flugzeugbedienung (für Einsteiger) ==
Du kannst jederzeit realistischere Simulationsoptionen über das Flugzeugmenü zuschalten; beispielsweise Treibstoffverunreinigung, Ölmanagement und realistische Motorsimulation inkl. Startverhalten.

Generell bietet die Checkliste eine vollständige Kurzanleitung für die Grundfunktionen des Flugzeug. Die Checkliste ist im Menü "Hilfe" von FlightGear verfügbar.

=== Vorflugkontrolle ===
[[File:C182-ready-for-take-off.jpg|270px||thumb|Cessna 182S bereit zum Start]]
Für die Vorflugkontrolle wird empfohlen, den "walker" zu aktivieren und damit um das Flugzeug zu laufen.

Es wird empfohlen, eine Außenansicht oder den Walker hierfür zu verwenden und im Gegenuhrzeigersinn um das Flugzeug zu gehen.
* Cockpit: Entfernen der Sicherung am Steuerhorn
* Überprüfe die Treibstoffmenge durch Klicken auf die Tankdeckel oben auf jeder Fläche
* Linke Tragfläche: Entferne den Spanngurt
* Linke Tragfläche: Entferne die Abdeckung des Staurohrs
* Linke Tragfläche: Überprüfe den Treibstoff auf Verschmutzung durch Klicken unterhalb der Tragfläche und Entnahme einer Treibstoffprobe. Ist diese hellblau, so ist der Treibstoff nicht verschmutzt und die Probe kann in den Tank zurückgegeben werden. Ist sie (teilweise) durchsichtig, enthält der Tribstoff Wasser, und die Probe muss entsorgt werden. Der Vorgang ist so lange zu wiederholen, bis die Probe komplett hellblau ist
* Linke Seite: Entferne den Radkeil am Hauptrad
* Heck: Entferne den Spanngurt
* Rechte Tragfläche: Entferne die Spanngurte
* Rechte Tragfläche: Überprüfe den Treibstoff auf Verschmutzung
* Rechte Seite: Entferne den Radkeil am Hauptrad
* Rechte Schnauze: Überprüfe den Treibstoff auf Verschmutzung am Treibstoffwähler (unter dem Flugzeug) und Treibstoffilter (rechte Nase)
* Schnauze: Überprüfe den Ölstand durch Klicken auf den Ölstutzen in der Nase. Niedriger Ölstand ist unterhalb 6.0 Quarts.
* Schnauze: Entferne den Radkeil am Bugrad

=== Motor Kaltstart (manual and complex startup) ===
* Gemisch: Idle-Cutoff (roter Hebel voll raus)
* Propeller: High RPM (blauer Hebel voll drin)
* Gashebel: 1/4 Zoll offen (schwarzer Hebel bei ~5%-8% Einstellung in der Simulation)
* Parkbremse: Angezogen ({{Key press|Shift|B}})
* Hauptschalter: An (beide roten Kippschalter)
* Treibstoff-Hilfspumpe: An
* Gemisch auf voll schieben, ca. 3 Sekunden halten, bis stetiger Treibstoffluss erreicht wird
* Dann Gemisch: Idle-Cutoff
* Treibstoff-Hilfspumpe: Aus
* Magnete: Beide (Drücke {{Key press|<nowiki>}</nowiki>}} 3x)
* Zündung: Start (halte {{Key press|S}} bis der Motor läuft)

Falls der Motor abgesoffen ist (zu viel Priming mit der Treibstoffpumpe):
* Gemisch: Idle-Cutoff
* Gashebel: 1/2 bis voll eingeschoben
* Zündung: Start (halte {{Key press|S}} bis der Motor läuft). Sobald der motor anspringt, Gemisch voll angereichert (roter Hebel rein) und Gashebel auf Leerlauf (fast ganz heraus).

War der Motor bereits vor kurzem auf Betriebstemperatur, reicht es in der Regel, das Gemisch auf Rich ("Fett") zu stellen (roter Hebel rein), und den Starter zu betätigen.

Alternativ zum manuellen (kalt-)Start gibt es eine Autostartfunktion im Flugzeugmenü.

=== Start ===
* Keine Landeklappen, oder 10 Grad
* Kühlklappen offen ({{Key press|Shift|F}} mehrfach drücken)
* Vollgas
* Rotieren bei ca. 50-60 KIAS

=== Steigflug ===
* Keine Landeklappen
* Kühlklappen offen
* Vollgas
* 80 KIAS
* Sobald sichere Flughöhe erreicht/Hindernisse überflogen: Gas zurücknehmen, um Motoranzeigen in die grünen Bereiche zu bringen
** Treibstoffluss: max 15Gph
** Gashebel: max 23 in.Hg

=== Reiseflug ===
[[File:c182-default.jpg|270px||thumb|Cessna 182S in der Luft]]
* Propeller: 2000-2400 RPM
* Gashebel: 18-23 mp
* Mixture "Fette Seite" über der EGT-Spitze als empfohlene "magere Einstellung" für den Reiseflug; oder 125°F EGT fetter für besten Schub
* Geschwindigkeit zwischen 120-140 Knoten IAS (abhängig von der Leistungseinstellung
* Kühlklappen geschlossen ({{Key press|f}} nach Bedarf -> CHT Anzeige beachten)

=== Landung ===
* Landeklappen 20 grad oder Voll
* 60-70 KIAS

=== Flugzeuggeschwindigkeiten ===
: ''Siehe auch [[De/Fluggeschwindigkeit#V-Speeds]]''

{| class="wikitable"
! Geschwindigkeit !! IAS
|-
| Überziehgeschwindigkeit, Landekonfiguration, V<sub>S<sub>0</sub></sub> || 36 kt
|-
| Überziehgeschwindigkeit, Reiseflugkonfiguration, V<sub>S<sub>1</sub></sub> || 43 kt
|-
| Rotationsgeschwindegkeit, V<sub>R</sub> || 55 kt
|-
| Bester Steigwinkel, V<sub>X</sub> || 63 kt
|-
| Höchste Steigrate, V<sub>Y</sub> || 80 kt
|-
| Höchstgeschwindegkeit bei ausgefahrenen Landeklappen, V<sub>FE</sub> || 100 kt
|-
| Manövergeschwindigkeit, V<sub>A</sub> || 110 kt
|-
| Maximale Reisegeschwindigkeit, V<sub>NO</sub> || 140 kt
|-
| Maximal zulässige Höchstgeschwindigkeit, V<sub>NE</sub> || 175 kt
|-
| Maximaler Seitenwind bei Landung|| 15 kt
|}

=== Performance ===

{| class="wikitable"
|Reiseflug, 80% Leistung, 6,000 ft || 140 kt
|-
|Reiseflug, 65% Leistung, 8,000 ft || 130 kt
|-
|Reiseflug, 55% Leistung, 10,000 ft || 121 kt
|}

{| class="wikitable"
|Entfernung, 75% Leistung, 6,000 ft || 820 nm
|-
|Entfernung, 65% Leistung, 8,000 ft || 910 nm
|-
|Entfernung, 55% Leistung, 10,000 ft || 968 nm
|}

{| class="wikitable"
|Beste Steigrate<ref>POH 5-19; bei 3100lbs, Seehöhe, 2400 RPM, Vollgas, Gemisch gesetzt nach "Maximum power Fuel Flow"-Plakette, Kühlklappen Offen, Standardtemperatur</ref> || 924fpm
|-
|Dienstgipfelhöhe || 18,100ft
|-
|Startrollweg: 795ft über 50ft Hindernis || 1,514ft
|-
|Landerollweg: 590ft über 50ft Hindernis || 1,390ft
|}

[[File:c182-cockpit-at-night.jpg|600px|center|Cessna 182S Konsolenbeleuchtung]]

== FAQ ==
'''''Ich frage mich, warum die 182s einfacher zu fliegen sein sollte, als die 172p?'''''

Ist sie das? Falls du denkst, das FDM (Flugdynamikmodell) ist nicht korrekt: Ein FDM ist nur so gut wie die zugrundeliegenden Daten. Das FDM der c182s benutzt reale Koeffizienzdaten, wo diese verfügbar sind, aber nicht alle benötigten Koeffizienten wurden gefunden. Wo diese nicht aufzutreiben waren, haben wir Beschreibungen von Piloten echter C182 benutzt, und diese sind naturgemäß subjektiv.

'''''Nach google stimmen die meisten Piloten überein, dass die 182 schwerer zu fliegen ist, als die 172'''''

Nicht wegen der Flugeigenschaften. Allerdings verbiegen sich viele Piloten beim Landen die Firewall, weil die Nase schwerer ist als bei einer 172. Viele Piloten mögen allerdings die größere Leistung, höhere Geschwindigkeit, die bessere Dienstgipfelhöhe, den [[constant speed propeller|Festdrehzahlpropeller]], Kühlklappen und die [[IFR]]-Ausrüstung. Und das ist auch schon der Grund - wegen all diesen Extras ist es schwerer, eine 182 zu fliegen, als eine 172. Die FAA zählt die Cessna 182 zu den "high perfomance aircraft". Stell dir vor, du befindest dich in einer überfüllten Gegend wie KLAX, im Anflug auf den Flughafen, während du alle paar Sekunden dem Funkverkehr zuhörst, die Höhe und Geschwindigkeit überwachst, den Motor regelst, die Nadeln des [[VOR]] jagst, alles gleichzeitig während du auf den Verkehr achtest und in schlechtem Wetter unterwegs bist - herausfordernd!

Vielleicht möchtest du dies hier lesen (englisch): [https://pilotbrian.blogspot.com/2009/05/stepping-up-to-c182.html Stepping Up to a C182 ]

'''''Wurde bei der C182S die Einfachheit zu fliegen gegenüber dem Realismus bevorzugt'''''

Nein. Die Autoren benutzen echte Zahlen und Daten als Grundlage, sofern sie verfügbar sind, und das Ziel ist ein möglichst realistisches Modell. Beispielsweise stimmen die Flugwerte sehr nah mit denen im POH überein, und es werden echte aerodynamische Koeffiziente eingesetzt, falls verfügbar.
Falls du etwas entdeckts, dass nicht passt, eröffne bitte ein [https://github.com/HHS81/c182s/issues Ticket im Entwicklungsprojekt] und wir finden heraus, was los ist.

'''''Warum hüpfe ich bei Landungen immer über die Rolbahn?'''''

Die C182 ist sehr Frontlastig, vor allem im Vergleich zu einer 172. Das erschwert den Flare bei der Landung, und du brauchst eine relativ ungewohnte, [[:File:C182s-LandingPicture.jpg|hohe Neigung]] um nicht zu früh aufzusetzen. Auch die Geschwindigkeit ist ein kritischer Faktor, versuche nicht mit zu hoher Geschwindigkeit zu landen (peile 60-70 KIAS für den Endanflug an, je nach Wind und Flaps). Am wichtigsten aber: Versuche nicht, die Maschine mit dem Steuerhorn auf den Boden zu zwingen, und lande nie mit dem Bugrad zuerst.
Eine perfekte Landung erkennst du daran, dass du die Stall-Warnung hörst, kurz bevor du sanft mit den beiden Rädern des Hauptfahrwerks aufsetzt, und wenn du danach das Bugrad sanft aufsetzt.

'''''Auf 3.000 ft komme ich nicht über 110 Knoten. MP: 23, RPM: 2450, Fuelflow: 14. Was hab ich übersehen?'''''

Die Checkliste! Wenn du nicht so schnell fliegst, wie du erwartest, prüfe: Gemisch, Propellergeschwindigkeit, Kühlklappen, Vereisung, Motordefekt (oder kalt).
Meistens wurde einfach vergessen, die Lande- oder Kühlklappen zu schließen. Ein anderer Grund kan sein, dass du [[De/Fluggeschwindigkeit#True_airspeed|KTAS (Knots True Airspeed) und KIAS (Knots Indicated Airspeed)]] verwechselst: Die Tabellen und Publikatoinen geben die Geschwindigkeit oft in KTAS an, und du musst KTAS vom {{wikipedia|Fahrtmesser|lang=de}} ablesen. Wie das geht? - lies weiter.

''''' Wie lese ich meine wahre Fluggeschwindigkeit ab? ([[De/Fluggeschwindigkeit#True_airspeed|KTAS]])?'''''

Der {{wikipedia|Fahrtmesser|lang=de}} hat ein kleines Fenster am oberen Rand. Mit dem Drehrad links unten stellst du die dahinterliegende Scheibe so ein, dass die Höhe (bei Standarddruck=29.92 inHG!) mit der Außentemperatur übereinstimmt. Im unteren Fenster des Fahrtmessers kannst du dann einfach über die Nadel die KTAS ablesen.

[[:File:C182s-ais-tas.png|Es gibt einen Screenshot]] der die Verwendung der TAS-Scheibe zeigt.

'''''Als ich in kaltem Wetter geflogen bin, verlor ich Fahrt und bin abgestürzt. Wo ist die Vergaservorwärmung?'''''

Die Cessna 182S hat keinen Vergaser, da sie einen Motor mit Direkteinspritzung benutzt. Was du allerdings erfahren hast, war Vereisung des Propellers und Flugzeugs.
Mit diesem Flugzeugtyp ist es nicht erlaubt, unter Bedingungen zu fliegen, die wahrscheinlich zu Vereisung führen. Vermeide feuchte Luft (Wolken....) bei Temperaturen um den Gefrierpunkt.

'''''Cessna 182S lässt sich nicht starten'''''

Möglicherweise ist folgendes passiert:
# vielleicht bist du der checkliste nicht akkurat genug gefolgt.
# vielleicht hast du den Motor beim Primen absaufen lassen. Folge [[De/Cessna_182S#Motor_Kaltstart_.28manual_and_complex_startup.29|der Prozedur am Ende dieses Abschnittes]].
# Nach einem missglückten Motorstart bei Temperturen unter dem Gefrierpunkt könnten nun die Zündkerzen vereist sein. Schließe das Vorheizgerät an und versuche es nach 5-10 (simulierten) Minuten erneut.
# Der Motor ist einfach zu kalt um anzuspringen. Schließe das Vorheizgerät an.
# du hast den Motor früher so beschädigt, dass er jetzt nicht mehr starten kann (hast du dunklen Qualm aus der Motorhaube bemerkt?).

'''''Mein Motor überhitzt beim Starten/Steigflug dauernd!'''''

Sobald du alle Hindernisse überflogen hast solltest du die Motorleistung reduzieren. Überwache die CHT-Anzeige engmaschig, und nimm die Leistung spätestens vor dem oberen Limit zurück.
Schau auch in den "Normal enroute climb" Abschnitt der Checkliste, um Details zu den Einstellungen zu finden (Kurzgesagt: halte Gas und Treibstoffluss im grünen Bereich, Kühlklappen offen).

'''''Warum kann ich die Flügelenden und die Motorhaube nicht sehen?'''''

Die Kopf/Augenposition wurde sorgfältig ausgewählt, nachdem wir Bilder der Cessna 182S/T und Pilotenberichte verglichen haben. Wenn du das ansiehst, stellst du fest, dass die Augenhöhe des Piloten mit der Oberkante des seitlichen Fensterrahmens übereinstimmt. Der Flügel sitzt jedoch viel höher, d.h. es ist unmöglich, das Flügelende zu sehen.
Der Blendschutz des Armaturenbretts ist ziemlich hoch, und so kannst du die Motorhaube vor dir nicht sehen.

== Entwicklungsstand / Fehler / ToDos ==

Dieses Flugzeugmodell wird kontinuierlich weiterentwickelt. Hierfür gibt es ein öffentliches [https://github.com/HHS81/c182s Repository], in dem auch eine [https://github.com/HHS81/c182s/issues Liste von offenen Fehlern und Erweiterungsideen] geführt wird. Das Repository ist einen Besuch wert!

* '''Defektes Fahrwerk in Multiplayer''': Das Schadensmodell wurde 5/2021 für FlightGear 2020.4.0 erweitert um Schaden daran zu simulieren. Ältere Versionen (2020.3 und älter) erhalten die Multiplayer-Daten hierfür nicht. Das führt dazu, dass das das "Fahrwerk-OK"-Property konstant ein defektes Fahrwerk für ältere Modelle anzeigt, wenn man selbst ein neueres Modell geladen hat. Die Lösung ist, dass der Pilot, der die ältere Modellversion hat, auf die neuere Version aktualisiert (aus FGADDON über den Launcher).

=== Die aktuellste Entwickerversion benutzen ===
Wenn du die aktuellste (potentiell unveröffentlichte) Version von github benutzen möchtest, kannst du sie ganz einfach herunterladen.
Es kann sein, dass diese Version nicht mit älteren FlightGear-Versionen funktioniert. Die Entwicklung zielt normalerweise darauf ab, die aktuell stabile FlightGear-Version zu unterstützen, allerdings kann es auch passieren, dass auf neueste Entwicklungen in FlightGear aufgebaut wird, und dann funktioniert das Flugzeug nur auf der FlightGear Entwicklerversion.

* Erstelle an einem für dich passenden Ort eine neuen Ordner namens "Aircraft" (falls du noch keinen solchen hast). Füge diesen Ordner im FlightGear-Starter im "Addons"-Tab als "Zusätzliche Flugzeug-Verzeichnisse" hinzu.
* Lade ein ZIP-Paket herunter (siehe Links in "Versionen" unten)
* Entpacke dieses ZIP-Paket in deinen "Aircraft"-Ordner
* Benenne den Ordner um: <code>c182s-<version></code> => <code>c182s</code>.

'''Versionen:'''
* Die letzte offizielle Veröffentlichug findest du hier: https://github.com/HHS81/c182s/releases. Dieses Release wird normalerweisein FGADDON für die nächste stabile FlightGear-Version ("next") hochgeladen und ist dann über den FlightGear-Starter bequem zu installieren. Kompatible Änderungen werden auch Fallweise in die aktuelle stabile FlightGear-Version zurückportiert.
* Aktuellster Entwicklungscode (<code>master</code>-branch) kann hier bezogen werden: https://github.com/HHS81/c182s/archive/refs/heads/master.zip

== Gallery ==
{{screenshot cat
| category = Cessna 182S screenshots
| subject = der Cessna 182S
| image = C182-default.jpg
}}{{-}}
<gallery mode="packed">
GXLTGAltenrhein.jpg|Flugzeug auf dem Vorfeld St. Gallen-Altenrhein/ Schweiz
Cessna182S compositor2.jpg|Flugzeug im Dunkeln, alle Lichter an
c182s.jpg|Cessna 182S am Abend
c182-cockpit-view.jpg|Standard Cockpitsicht
c182-external2.jpg|HB-CZV livery
c182-external3.jpg|D-ELFP livery
c182-external5.jpg|Cessna 182S über Kalifornien
c182-external6.jpg|Weitere Ansicht des HB-CZV livery
C182-4.jpg|Taking off
c182-rosskopf-at-dusk.jpg|Cessna 182S bei Roßkopf in Freiburg/ Deutschland
C182STakeOff.jpg|Cessna 182S mit selbstgewählter Kennung bei Siegerland / Deutschland
C182s-LandingPicture.jpg|C182s Landung, zeigt die nötige hohe Neigung
C182SDavtron803.jpg|Die Davtron 803 digitaluhr in Aktion
C182SWinterKit.jpg|Winterkit ausgerüstet, und Vorheizen mit dem Dragon heater
C182SFuelManagement.jpg|Fuel Management Dialog
c182-rain.jpg|Regeneffekt auf der Windschutzscheibe
C182-oil-cap.png|Position der Klappe zum Ölmesstab
C182SOilManagement.jpg|Oil Management Dialog
C182-fuelports.png|Treibstoffwähler und -filter Prüfports
c182-night-take-off.jpg|Ready to take off bei Nacht
c182-3.jpg|D-ELFP am Abend
C182SPitot.jpg|Pitot, Cover und Nachricht
C182SFreeMovementCheck.jpg|Prüfen der Querruder
C182SCustomRegistration.jpg|Selbstwählbare Kennung
c182-external4.jpg|N182PJ livery
c182-external-at-night.jpg|Default livery bei Nacht
c182-external1.jpg|N321HW livery
C182Scrashed.jpg|Flugzeug beschädigt
AboveSouthGermany.jpg|Flugzeug fliegt über Süddeutschland
Cessna182S compositor.jpg|Flugzeug im Dunkel, alle Lichter an

</gallery>

== External links ==
* {{Wikipedia|Cessna 182 Skylane|lang=en}}
* [http://www.freechecklists.net/Resources/Cessna/182S+Skylane/ Links to Cessna 182S Checklists and W&B sheet]
* [http://tssflyingclub.org/documents/C182S_POH.pdf Cessna 182S POH]
* [https://www.aopa.org/go-fly/aircraft-and-ownership/aircraft-fact-sheets/cessna-182 Cessna 182S Aircraft Information Booklet]
* [http://www.jberaeroclub.com/uploads/1/7/4/0/17405139/c182maneuversguiderev2.pdf C182 Standardized flight maneuvers guide]
* [https://airplaneacademy.com/9-actionable-cessna-182-landing-tips-you-can-implement-today/ 9 Actionable Cessna 182 Landing Tips You Can Implement Today]

{{Appendix}}

{{Cessna}}

[[Category:Aircraft with a cockpit-only autopilot]]
[[Category:Red Griffin ATC compatible aircraft]]

[[en:Cessna 182S]]