FlightGear wiki - User contributions [en]

$FG HOME

2025-03-20T00:49:32Z

Flughund: Rant Mark II

[[File:Fghome-3.7.png|400px|right|Screen shot showing typical structure [[$FG_HOME]]]]

The [[Environment variables|environment variable]]<code>'''$FG_HOME'''</code> is a '''setting''' indicating the main location where user-specific FlightGear data is stored (not application data). <code>$FG_HOME</code> is a notable place were FlightGear data is written to. <code>$FG_HOME</code> is also where large amounts of data downloaded by FlightGear like [[TerraSync]] scenery or Aircraft data is written to, by default.

<code>$FG_HOME</code> should not be confused with <code>[[$FG_ROOT]]</code>, which is generally read-only.

<code>$FG_HOME</code> is normally used to refer to the operating system specific location for some settings/folders. Its default value is determined by the <code>fgfs</code> binary during startup and is a directory that varies with the operating system supported by FG (Windows, OS X and Linux). ''It is [https://sourceforge.net/p/flightgear/mailman/message/34995089/ highly recommended] to rely on the default value (i.e., not setting <code>$FG_HOME</code> yourself in any way), unless you Really Know What You Are Doing™.'' '''''Why is that?! What if one does not want fgfs to glut their $HOME folder with a massive amount of data (13G ~/.fgfs/TextureCache/)? Why is it so difficult to select another location? Why do developers think hiding the internals of a programme from the user is a good thing? This project claimed to be a simulator. Now it is a mere game. The qt launcher looks like an app. We do not want apps, we liked fgrun. Even specifiying --prop:sim/fg-home=$some_path does not prevent fgfs from clogging the $HOME folder.'''''
'''''We are aware of the possibility to set the env var. But that is not a userfriendly option. With the transition from fgrun to the qt launcher users have been stripped of the knowledge about the sim's, pardon me, game's, available options. The qt launcher is, in fact, not more userfriendly but more of a user dictation.''''''
Very advanced users (i.e. power users and developers) who wish to run parallel installs of FlightGear can specify a different <code>$FG_HOME</code> for each install as described below. '''''Really?! Where below? Do you have link to that section?!'''''

{{note|The <code>/sim/fg-home</code> property should be considered read-only, for similar reasons why <code>$FG_HOME</code> shouldn't be explicitly set by users.}}
{{note|FlightGear reads the <code>[[Fgfsrc|fgfsrc]]</code> config file from <code>$FG_HOME</code> if it exists (<tt>fgfsrc</tt> without any leading dot), in addition to <tt>.fgfsrc</tt> from <code>$HOME</code> (with a leading dot in this case).}}

== Content ==
In <code>$FG_HOME</code> is information stored between sessions. That information is for example configuration/preferences, properties marked with the <code>user-archive</code> attribute and aircraft-specific settings (using the data helper class in <code>aircraft.nas</code>). <code>$FG_HOME</code> is also the location for the SQLite-based [[Navdata cache|navdata cache]].

== Common paths ==
You can determine the location of your <code>$FG_HOME</code> by using the [[property browser]] and checking the value of <code>/sim/fg-home</code>, but the usual paths are shown below.

You can also use the [[Nasal Console]] to print out <code>$FG_HOME</code>:
<syntaxhighlight lang="nasal">
var path = getprop("/sim/fg-home");
print("Your $FG_HOME is at: ", path);
</syntaxhighlight>

The <code>/sim/</code> property subtree is also the place where you can find other folders, such as <code>fg-root</code>, <code>fg-scenery</code> and the current working directory (<code>fg-current</code>).

=== Linux ===
<code>~/.fgfs/</code>

=== Mac OS X ===
<code>~/Library/Application Support/FlightGear</code> (`~/Library` is a hidden folder by default. In versions of macOS newer than 10.12, you can use the shortcut `Cmd + Shift + .` to view hidden folders. For older versions, see [http://www.mikesel.info/show-hidden-files-mac-os-x-10-7-lion/])

As all future FlightGear versions will take their preferences from here, it is a good idea to have their access available easily.

Desktop/Finder/Go/Go to Folder is where you need to start.

When given the option, input: <code>~/Library/Application Support/FlightGear</code>

It is probably a good idea to have <code>~/Library/Application Support/FlightGear</code> saved on a Stickies note just in case you forget it.

If you want/need to refer to any of these files frequently, you could make an alias of a file, or the whole folder, and place it somewhere easier to access. TerraSync data is stored in <code>$FG_HOME/TerraSync</code> in the default configuration, see [[TerraSync]] for details.

=== Windows ===

==== FlightGear 2020.3 and later ====
<code>%userprofile%\FlightGear</code>

<code>%userprofile%</code> is the directory that contains the [https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/bb776892(v=vs.85) Windows user profile] ([http://web.archive.org/web/20210320110758/https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/bb776892%28v=vs.85%29 perm])<code>.</code>Ways to find the<code>%userprofile%</code> directory: 1). Press <code>Windows key+R</code>or bring up the RUN box. Type <code>%userprofile%</code> to open. 2). In command prompt, type <code>cd</code> <code>%userprofile%</code>

<code>%userprofile%</code> is<code>%homedrive%\Users\''User name''</code> by default. Usually on most peoples systems: <Code>%homedrive%</Code> is C:\.

For example if your user profile was called <code>MyUserProfile</code>, it would most often be located under <code>C:\Users\MyUserProfile</code> . Then the path to <code>$FG_HOME</code> would be <code>C:\Users\MyUserProfile\FlightGear.</code>

In 2020.3.x the [[FlightGear Qt launcher|qt-launcher]] will notify users who have data in the old location under <code>%userprofile%\Documents\FlightGear</code>, and prompt users to move files to the new location under <code>%userprofile%\FlightGear</code>.

==== FlightGear 3.0 and later ====
<code>%userprofile%\Documents\FlightGear</code>

<code>%userprofile%</code> is <code>%homedrive%\Users\''User name''</code> by default, and <Code>%homedrive%</code> is usually C:\.

==== Before FlightGear 3.0 ====
<code>%APPDATA%\flightgear.org\</code>

<code>%APPDATA%</code> is another environment variable that depends on your Windows version. On XP and older, it can be found under <code>C:\Documents and Settings\''User name''\Application Data</code>. On Vista and later it can be found under <code>C:\Users\''User name''\AppData\Roaming</code>. The folder is hidden by default. See [http://windows.microsoft.com/en-US/windows-vista/show-hidden-files these instructions] to show the folder.

== Use in troubleshooting ==
As one user once said, "When in doubt delete <code>$FG_HOME</code>". Many problems, including corrupted databases, broken [[TerraSync]] and many others can be fixed by deleting <code>fgfs_0.txt</code>, <code>fgfs.txt</code>, <code>terrasync_cache</code>, and the [[Navdata cache|navdata cache]].

When you encounter problems, try deleting the files, but '''always''' keep the <code>[[Commonly used debugging tools#fgfs.log|fgfs.log]]</code> and <code>fgfs_0.log</code> log files to help in troubleshooting.

== Power Users ==

=== Parallel installs of FlightGear ===
Note you can also override FG_HOME in the environment, to have totally distinct installs - this would be my recommend approach to running multiple versions in parallel.
(The installers will always replace the stable / dev version as other commenters pointed out, so you can't use those so easily, you need to copy files around - I'm nota Windows expert so I don't know if there something that could be changed or improved here)
If you start multiple instances (the same version or different) of FGFS using the same value of FG_HOME (whether that be the default or a custom one), we use a lock file to ensure only one (the first) has write access. The rest will go into read-only mode, and as you can maybe guess, treat FG_HOME as read-only.
Sharing of aircraft / scenery is entirely about which paths are configured, BTW. However, one final caveat is that having multiple instances both running TerraSync, using the same terrasync dir, would likely act a bit funny. It ought to actually work, but it might download some things twice, and it's not a tested or supported configuration for the moment.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=304170#p304170
|title = <nowiki> Re: Is it possible to install multiple instanes of FG in Win </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Jan 25th, 2017
|added = Jan 25th, 2017
|script_version = 0.40
}}</ref>

Using the same [[TerraSync|TerraSyn]]<nowiki/>c directory can save a lot of downloading and disk space. You can use the --terrasync-dir=path [[Command line options|command line]] option. For example --terrasync-dir=C:\Path\to\my\separate\terrasync\folder\TerraSync. It's possible to add this option in the <code>Settings > Additional Settings</code> section of the [[qt-launcher]].

== Related content ==
=== Wiki articles ===
* [[FlightGear configuration via XML]]
* [[$FG_ROOT]]
* [[Property browser]]
* [[Properties persistent between sessions]]

=== References ===
{{Appendix}}

[[Category:Special directories|HOME]]
[[Category:Environment variables]]

$FG HOME

2025-03-20T00:24:32Z

Flughund: This is a rant. Read it. Feel free to reverse it. But only do so if you want your software controlling you and your hardware environment.

[[File:Fghome-3.7.png|400px|right|Screen shot showing typical structure [[$FG_HOME]]]]

The [[Environment variables|environment variable]]<code>'''$FG_HOME'''</code> is a '''setting''' indicating the main location where user-specific FlightGear data is stored (not application data). <code>$FG_HOME</code> is a notable place were FlightGear data is written to. <code>$FG_HOME</code> is also where large amounts of data downloaded by FlightGear like [[TerraSync]] scenery or Aircraft data is written to, by default.

<code>$FG_HOME</code> should not be confused with <code>[[$FG_ROOT]]</code>, which is generally read-only.

<code>$FG_HOME</code> is normally used to refer to the operating system specific location for some settings/folders. Its default value is determined by the <code>fgfs</code> binary during startup and is a directory that varies with the operating system supported by FG (Windows, OS X and Linux). ''It is [https://sourceforge.net/p/flightgear/mailman/message/34995089/ highly recommended] to rely on the default value (i.e., not setting <code>$FG_HOME</code> yourself in any way), unless you Really Know What You Are Doing™.'' '''''Why is that?! What if one does not want fgfs to glut their $HOME folder with a massive amount of data (13G ~/.fgfs/TextureCache/)? Why is it so difficult to select another location? Why do developers think hiding the internals of a programme from the user is a good thing? This project claimed to be a simulator. Now it is a mere game. The qt launcher looks like an app. We do not want apps, we liked fgrun. Even specifiying --prop:sim/fg-home=$some_path does not prevent fgfs from clogging the $HOME folder.'''''

Very advanced users (i.e. power users and developers) who wish to run parallel installs of FlightGear can specify a different <code>$FG_HOME</code> for each install as described below.

{{note|The <code>/sim/fg-home</code> property should be considered read-only, for similar reasons why <code>$FG_HOME</code> shouldn't be explicitly set by users.}}
{{note|FlightGear reads the <code>[[Fgfsrc|fgfsrc]]</code> config file from <code>$FG_HOME</code> if it exists (<tt>fgfsrc</tt> without any leading dot), in addition to <tt>.fgfsrc</tt> from <code>$HOME</code> (with a leading dot in this case).}}

== Content ==
In <code>$FG_HOME</code> is information stored between sessions. That information is for example configuration/preferences, properties marked with the <code>user-archive</code> attribute and aircraft-specific settings (using the data helper class in <code>aircraft.nas</code>). <code>$FG_HOME</code> is also the location for the SQLite-based [[Navdata cache|navdata cache]].

== Common paths ==
You can determine the location of your <code>$FG_HOME</code> by using the [[property browser]] and checking the value of <code>/sim/fg-home</code>, but the usual paths are shown below.

You can also use the [[Nasal Console]] to print out <code>$FG_HOME</code>:
<syntaxhighlight lang="nasal">
var path = getprop("/sim/fg-home");
print("Your $FG_HOME is at: ", path);
</syntaxhighlight>

The <code>/sim/</code> property subtree is also the place where you can find other folders, such as <code>fg-root</code>, <code>fg-scenery</code> and the current working directory (<code>fg-current</code>).

=== Linux ===
<code>~/.fgfs/</code>

=== Mac OS X ===
<code>~/Library/Application Support/FlightGear</code> (`~/Library` is a hidden folder by default. In versions of macOS newer than 10.12, you can use the shortcut `Cmd + Shift + .` to view hidden folders. For older versions, see [http://www.mikesel.info/show-hidden-files-mac-os-x-10-7-lion/])

As all future FlightGear versions will take their preferences from here, it is a good idea to have their access available easily.

Desktop/Finder/Go/Go to Folder is where you need to start.

When given the option, input: <code>~/Library/Application Support/FlightGear</code>

It is probably a good idea to have <code>~/Library/Application Support/FlightGear</code> saved on a Stickies note just in case you forget it.

If you want/need to refer to any of these files frequently, you could make an alias of a file, or the whole folder, and place it somewhere easier to access. TerraSync data is stored in <code>$FG_HOME/TerraSync</code> in the default configuration, see [[TerraSync]] for details.

=== Windows ===

==== FlightGear 2020.3 and later ====
<code>%userprofile%\FlightGear</code>

<code>%userprofile%</code> is the directory that contains the [https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/bb776892(v=vs.85) Windows user profile] ([http://web.archive.org/web/20210320110758/https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/bb776892%28v=vs.85%29 perm])<code>.</code>Ways to find the<code>%userprofile%</code> directory: 1). Press <code>Windows key+R</code>or bring up the RUN box. Type <code>%userprofile%</code> to open. 2). In command prompt, type <code>cd</code> <code>%userprofile%</code>

<code>%userprofile%</code> is<code>%homedrive%\Users\''User name''</code> by default. Usually on most peoples systems: <Code>%homedrive%</Code> is C:\.

For example if your user profile was called <code>MyUserProfile</code>, it would most often be located under <code>C:\Users\MyUserProfile</code> . Then the path to <code>$FG_HOME</code> would be <code>C:\Users\MyUserProfile\FlightGear.</code>

In 2020.3.x the [[FlightGear Qt launcher|qt-launcher]] will notify users who have data in the old location under <code>%userprofile%\Documents\FlightGear</code>, and prompt users to move files to the new location under <code>%userprofile%\FlightGear</code>.

==== FlightGear 3.0 and later ====
<code>%userprofile%\Documents\FlightGear</code>

<code>%userprofile%</code> is <code>%homedrive%\Users\''User name''</code> by default, and <Code>%homedrive%</code> is usually C:\.

==== Before FlightGear 3.0 ====
<code>%APPDATA%\flightgear.org\</code>

<code>%APPDATA%</code> is another environment variable that depends on your Windows version. On XP and older, it can be found under <code>C:\Documents and Settings\''User name''\Application Data</code>. On Vista and later it can be found under <code>C:\Users\''User name''\AppData\Roaming</code>. The folder is hidden by default. See [http://windows.microsoft.com/en-US/windows-vista/show-hidden-files these instructions] to show the folder.

== Use in troubleshooting ==
As one user once said, "When in doubt delete <code>$FG_HOME</code>". Many problems, including corrupted databases, broken [[TerraSync]] and many others can be fixed by deleting <code>fgfs_0.txt</code>, <code>fgfs.txt</code>, <code>terrasync_cache</code>, and the [[Navdata cache|navdata cache]].

When you encounter problems, try deleting the files, but '''always''' keep the <code>[[Commonly used debugging tools#fgfs.log|fgfs.log]]</code> and <code>fgfs_0.log</code> log files to help in troubleshooting.

== Power Users ==

=== Parallel installs of FlightGear ===
Note you can also override FG_HOME in the environment, to have totally distinct installs - this would be my recommend approach to running multiple versions in parallel.
(The installers will always replace the stable / dev version as other commenters pointed out, so you can't use those so easily, you need to copy files around - I'm nota Windows expert so I don't know if there something that could be changed or improved here)
If you start multiple instances (the same version or different) of FGFS using the same value of FG_HOME (whether that be the default or a custom one), we use a lock file to ensure only one (the first) has write access. The rest will go into read-only mode, and as you can maybe guess, treat FG_HOME as read-only.
Sharing of aircraft / scenery is entirely about which paths are configured, BTW. However, one final caveat is that having multiple instances both running TerraSync, using the same terrasync dir, would likely act a bit funny. It ought to actually work, but it might download some things twice, and it's not a tested or supported configuration for the moment.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=304170#p304170
|title = <nowiki> Re: Is it possible to install multiple instanes of FG in Win </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Jan 25th, 2017
|added = Jan 25th, 2017
|script_version = 0.40
}}</ref>

Using the same [[TerraSync|TerraSyn]]<nowiki/>c directory can save a lot of downloading and disk space. You can use the --terrasync-dir=path [[Command line options|command line]] option. For example --terrasync-dir=C:\Path\to\my\separate\terrasync\folder\TerraSync. It's possible to add this option in the <code>Settings > Additional Settings</code> section of the [[qt-launcher]].

== Related content ==
=== Wiki articles ===
* [[FlightGear configuration via XML]]
* [[$FG_ROOT]]
* [[Property browser]]
* [[Properties persistent between sessions]]

=== References ===
{{Appendix}}

[[Category:Special directories|HOME]]
[[Category:Environment variables]]

Building FlightGear - Devuan

2025-02-21T19:58:19Z

Flughund: removed libc-ares-dev from dependencies

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: On Debian replace <code>libeudev-dev</code> with <code>libudev-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libc-ares-dev</code>, <code>libplib-dev</code>, <code>libpopenscenegraph-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libc-ares-dev libopenscenegraph-dev libplib-dev libsimgear-dev"

su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev libjpeg62-turbo-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev librsvg2-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [https://wiki.debian.org/EnvironmentVariables environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2024.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1 #OR# export FG_VERSION=next
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== libc-ares ===
This step is only required to compile FlightGear 'next':
cd $FG_SRC_DIR
<nowiki>git clone https://github.com/c-ares/c-ares.git libc-ares.git</nowiki>
cd libc-ares.git
git checkout v1.34.2
mkdir -p $FG_SRC_DIR/build-c-ares && cd $FG_SRC_DIR/build-c-ares
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX="$FG_INSTALL_DIR" $FG_SRC_DIR/libc-ares.git
make -j$(nproc)
make install

=== [[plib|libplib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install

=== [[OpenSceneGraph]] ===
To compile FlightGear release version branch <code>release/2024-build</code> is required, for FlightGear next branch <code>next</code>.
if [ "$FG_VERSION" = "release/2024.1" ]; then export FG_OSG_VERSION=release/2024-build; fi
if [ "$FG_VERSION" = "next" ]; then export FG_OSG_VERSION=next; fi

cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki>
cd FG-OpenSceneGraph.git
git checkout $FG_OSG_VERSION
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/simgear.git simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone https://gitlab.com/flightgear/simgear.git fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/flightgear.git flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR, the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

Building FlightGear - Devuan

2025-02-18T17:53:21Z

Flughund: sfourceforge --> gitlab

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: On Debian replace <code>libeudev-dev</code> with <code>libudev-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libc-ares-dev</code>, <code>libplib-dev</code>, <code>libpopenscenegraph-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libc-ares-dev libopenscenegraph-dev libplib-dev libsimgear-dev"

su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libc-ares-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev libjpeg62-turbo-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev librsvg2-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [https://wiki.debian.org/EnvironmentVariables environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2024.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1 #OR# export FG_VERSION=next
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== libc-ares ===
This step is only required to compile FlightGear 'next':
cd $FG_SRC_DIR
<nowiki>git clone https://github.com/c-ares/c-ares.git libc-ares.git</nowiki>
cd libc-ares.git
git checkout v1.34.2
mkdir -p $FG_SRC_DIR/build-c-ares && cd $FG_SRC_DIR/build-c-ares
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX="$FG_INSTALL_DIR" $FG_SRC_DIR/libc-ares.git
make -j$(nproc)
make install

=== [[plib|libplib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install

=== [[OpenSceneGraph]] ===
To compile FlightGear release version branch <code>release/2024-build</code> is required, for FlightGear next branch <code>next</code>.
if [ "$FG_VERSION" = "release/2024.1" ]; then export FG_OSG_VERSION=release/2024-build; fi
if [ "$FG_VERSION" = "next" ]; then export FG_OSG_VERSION=next; fi

cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki>
cd FG-OpenSceneGraph.git
git checkout $FG_OSG_VERSION
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/simgear.git simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone https://gitlab.com/flightgear/simgear.git fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/flightgear.git flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR, the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

FlightGear IRC channel

2025-01-09T01:41:00Z

Flughund: Some minor updates. (ChatZilla, Other Hosts, voice due to spam)

{{DEFAULTSORT:IRC channel}}
The '''FlightGear IRC Network''' is an online system that will allow you to talk to a lot of people around the world and is related to everything about [[FlightGear]]. It's mostly used by developers, but it is also a good place to ask for help if you are having a question.

== Connecting to the network ==
It consists of localised servers that are all linked up to form a seamless chat network so if you are based in England you would connect to a nearby server in England and you would see exactly the same people as someone connecting to a server in the USA.

To connect to the IRCnet network you first need a suitable client. You can also use [http://www.xchat.org/ XChat] (Linux and Windows), [http://sourceforge.net/projects/xchataqua/ X-Chat Aqua] (X Chat Mac), [http://www.pidgin.im/ Pidgin], [http://colloquy.info/ Colloquy] (for Mac/iOS), [http://www.mirc.com/ mIRC], [https://Konversation.kde.org Konversation] or any other client.

When you first login to the network you must pick yourself a unique nickname for the current chat session. Nicknames can be up to 31 characters in length and contain numbers and some punctuation characters. Some examples of nicknames you can use are:

* Fred
* BIG_fred
* ^Fred^
* Fred-
* ^Fred
* fred007

It doesn't matter about capital or lower case letters in the nickname since they are treated the same when people want to contact you and there are some weird and obscure rules about nicknames such as them not being able to begin with a "-" character. Most of these rules have no rhyme nor reason to them but we didn't write the software, we just have to try and tell people how to use it. Have an experiment and see what suits you best.

Once you found your personal unique nickname you may want to register it with [[#Network_Services|NickServ]] (see below).

== Official hosts ==
{| class="wikitable"
! Host !! Location
|-
| de.irc.flightgear.org
| Germany
|-
| irc.flightgear.org
| currently an alias for de.irc.flightgear.org
|}

The '''port''' to connect to is 6667 (or 6659 for SSL) for each server.

<s>These servers are interconnected to form the FlightGear IRC network. Please choose the host closest to you geographically.</s>

The FlightGear IRC network has several channels, some of which are listed below. To obtain a real list, use the IRC command "/list".

{| class="wikitable"
! Channel !! Use
|-
| #flightgear
| Main channel (English). If you get a message ''Cannot send to channel (+m)'' we're plagued by spam. In that case [[FlightGear_IRC_channel#NickServ|register]] your nick and contact (query) ''lru'' (or another operator) for autovoice.
|-
| #fg_school
| [[FlightGear Flight Academy | Flight School]]
|-
| #fgms
| [[fgms | Multiplayer Server]] related stuff
|-
| #fg_cantene
| Off topic community
|-
| #wiki
| Everything regarding our Wiki
|-
| #flightgear-forum
| Forum
|-
| #help
| General help on IRC and a go to with issues regarding our IRC network.
|-
|}

== Network Services ==
=== NickServ ===
NickServ allows you to "register" a nickname and prevent others from using it. In addition to that, occasionally we're plagued by spam, and only registered users are allowed to talk (voice). If you get a message ''Cannot send to channel (+m)'' this is the case. After registration query an operator to be granted voice. Thank you for understanding!

The following commands allow for registration and maintenance of nicknames; to use them, type

/msg NickServ ''COMMAND''

For more information on a specific command, type

/msg NickServ HELP ''COMMAND''

Some of the common commands are:

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a nickname.
|-
| GROUP
| Adds a nickname to your account.
|-
| IDENTIFY
| Identifies to services for a nickname.
|-
| GHOST
| Reclaims use of a nickname.
|}

This service is intended to provide a way for IRC users to ensure their identity is not compromised. It is ''not'' intended to facilitate "stealing" of nicknames or other malicious actions. Abuse of NickServ will result in, at minimum, loss of the abused nickname(s).

=== ChanServ ===
ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Some available commands are listed below; to use them, type

/msg ChanServ ''COMMAND''

For more information on a specific command, type:

/msg ChanServ HELP ''COMMAND''

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a channel.
|-
| RECOVER
| Regain control of your channel.
|-
| FLAGS
| Manipulates specific permissions on a channel.
|}

=== MemoServ ===
MemoServ is a utility allowing IRC users to send short messages to other IRC users, whether they are online at the time or not. Both the sender's nickname and the target nickname must be registered in order to send a memo.

MemoServ's commands include:

{| class="wikitable"
! Command !! Purpose
|-
| READ
| Reads a memo.
|-
| SEND
| Sends a memo to a user.
|-
| SENDGROUP
| Sends a memo to all members on a group.
|-
| SENDOPS
| Sends a memo to all ops on a channel.
|-
| DELETE
| Deletes memos.
|}

For help on any of the above commands, type:

/msg MemoServ HELP ''COMMAND''

To see a list of all available MemoServ commands, type:

/msg MemoServ HELP

=== HostServ ===
HostServ allows users to request a virtual hostname. Normally we only allow IPs to be shown on a users
connection (so no dns lookups are made upon a new connection). To hide your host to other users you are
free to select a vhost from a predefined list (or a uniquely requested one) via hostserv. In that case
your selected hostname will be shown to others instead of your real IP.

To see the list of all available commands, type:

/msg HostServ HELP

Some commands of interest are:

{| class="wikitable"
! IRC Command !! Purpose
|-
| OFFERLIST
| Lists all available vhosts.
|-
| TAKE
| Take an offered vhost for use.
|-
| ON
| Activate the taken vhost.
|-
| REQUEST
| Requests new virtual hostname for current nick.
|}

For further help type <tt>'''/msg ''SERVICE'' help'''</tt> (replace <tt>''SERVICE''</tt> with the name of the service)

== Other hosts ==
Our backup channel is located on [https://libera.chat libera]. For quick access, they provide a [https://web.libera.chat webchat client].
{| class="wikitable"
! Network:Port !! Channel !! Description
|-
| irc.libera.chat:6667
| #flightgear
| Official backup channel.
|-
| irc.libera.chat:6667
| #fg_cantene
| Off topic chat.
|}

== How to get in there with ChatZilla ==
[[File:IRC-ChatZilla.jpg|thumb|ChatZilla Client area]]
When using ChatZilla, go to your Mozilla/Firefox browser and enter [irc://de.irc.flightgear.org irc://de.irc.flightgear.org]. When ChatZilla has connected to the host, click "IRC" and "Join channel...". Pick the preferred channel.

To get directly to the main channel with ChatZilla, you can also enter [irc://de.irc.flightgear.org/flightgear irc://de.irc.flightgear.org/flightgear] in your browser.

In case you get a message ''Cannot send to channel (+m)'' when attempting to talk, see [[FlightGear_IRC_channel#NickServ | NickServ]].

== External links ==
* [http://www.ircbeginner.com/ General information about IRC]
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html General IRC commands]

[[Category:FlightGear]]
[[Category:Community]]

FlightGear IRC channel

2025-01-07T00:43:17Z

Flughund: Channel list clean-up

{{DEFAULTSORT:IRC channel}}
The '''FlightGear IRC Network''' is an online system that will allow you to talk to a lot of people around the world and is related to everything about [[FlightGear]]. It's mostly used by developers, but it is also a good place to ask for help if you are having a question.

== Connecting to the network ==
It consists of localised servers that are all linked up to form a seamless chat network so if you are based in England you would connect to a nearby server in England and you would see exactly the same people as someone connecting to a server in the USA.

To connect to the IRCnet network you first need a suitable client. You can also use [http://www.xchat.org/ XChat] (Linux and Windows), [http://sourceforge.net/projects/xchataqua/ X-Chat Aqua] (X Chat Mac), [http://www.pidgin.im/ Pidgin], [http://colloquy.info/ Colloquy] (for Mac/iOS), [http://www.mirc.com/ mIRC], [https://Konversation.kde.org Konversation] or any other client.

When you first login to the network you must pick yourself a unique nickname for the current chat session. Nicknames can be up to 31 characters in length and contain numbers and some punctuation characters. Some examples of nicknames you can use are:

* Fred
* BIG_fred
* ^Fred^
* Fred-
* ^Fred
* fred007

It doesn't matter about capital or lower case letters in the nickname since they are treated the same when people want to contact you and there are some weird and obscure rules about nicknames such as them not being able to begin with a "-" character. Most of these rules have no rhyme nor reason to them but we didn't write the software, we just have to try and tell people how to use it. Have an experiment and see what suits you best.

Once you found your personal unique nickname you may want to register it with [[#Network_Services|NickServ]] (see below).

== Official hosts ==
{| class="wikitable"
! Host !! Location
|-
| de.irc.flightgear.org
| Germany
|-
| irc.flightgear.org
| currently an alias for de.irc.flightgear.org
|}

The '''port''' to connect to is 6667 (or 6659 for SSL) for each server.

<s>These servers are interconnected to form the FlightGear IRC network. Please choose the host closest to you geographically.</s>

The FlightGear IRC network has several channels, some of which are listed below. To obtain a real list, use the IRC command "/list".

{| class="wikitable"
! Channel !! Use
|-
| #flightgear
| Main channel (English). Due to spamming it is required to have voice, [[FlightGear_IRC_channel#NickServ|register]] your nick and contact (query) ''lru'' for autovoice.
|-
| #fg_school
| [[FlightGear Flight Academy | Flight School]]
|-
| #fgms
| [[fgms | Multiplayer Server]] related stuff
|-
| #fg_cantene
| Off topic community
|-
| #wiki
| Everything regarding our Wiki
|-
| #flightgear-forum
| Forum
|-
| #help
| General help on IRC and a go to with issues regarding our IRC network.
|-
|}

== Network Services ==
=== NickServ ===
NickServ allows you to "register" a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type

/msg NickServ ''COMMAND''

For more information on a specific command, type

/msg NickServ HELP ''COMMAND''

Some of the common commands are:

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a nickname.
|-
| GROUP
| Adds a nickname to your account.
|-
| IDENTIFY
| Identifies to services for a nickname.
|-
| GHOST
| Reclaims use of a nickname.
|}

This service is intended to provide a way for IRC users to ensure their identity is not compromised. It is ''not'' intended to facilitate "stealing" of nicknames or other malicious actions. Abuse of NickServ will result in, at minimum, loss of the abused nickname(s).

=== ChanServ ===
ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Some available commands are listed below; to use them, type

/msg ChanServ ''COMMAND''

For more information on a specific command, type:

/msg ChanServ HELP ''COMMAND''

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a channel.
|-
| RECOVER
| Regain control of your channel.
|-
| FLAGS
| Manipulates specific permissions on a channel.
|}

=== MemoServ ===
MemoServ is a utility allowing IRC users to send short messages to other IRC users, whether they are online at the time or not. Both the sender's nickname and the target nickname must be registered in order to send a memo.

MemoServ's commands include:

{| class="wikitable"
! Command !! Purpose
|-
| READ
| Reads a memo.
|-
| SEND
| Sends a memo to a user.
|-
| SENDGROUP
| Sends a memo to all members on a group.
|-
| SENDOPS
| Sends a memo to all ops on a channel.
|-
| DELETE
| Deletes memos.
|}

For help on any of the above commands, type:

/msg MemoServ HELP ''COMMAND''

To see a list of all available MemoServ commands, type:

/msg MemoServ HELP

=== HostServ ===
HostServ allows users to request a virtual hostname. Normally we only allow IPs to be shown on a users
connection (so no dns lookups are made upon a new connection). To hide your host to other users you are
free to select a vhost from a predefined list (or a uniquely requested one) via hostserv. In that case
your selected hostname will be shown to others instead of your real IP.

To see the list of all available commands, type:

/msg HostServ HELP

Some commands of interest are:

{| class="wikitable"
! IRC Command !! Purpose
|-
| OFFERLIST
| Lists all available vhosts.
|-
| TAKE
| Take an offered vhost for use.
|-
| REQUEST
| Requests new virtual hostname for current nick.
|}

For further help type <tt>'''/msg ''SERVICE'' help'''</tt> (replace <tt>''SERVICE''</tt> with the name of the service)

== Other hosts ==
{| class="wikitable"
! Network !! Channel !! Description
|-
| irc.freenode.net
| #flightgear
| Only for emergencies.
|}

== How to get in there with ChatZilla ==
[[File:IRC-ChatZilla.jpg|thumb|ChatZilla Client area]]
When using ChatZilla, go to your Mozilla/Firefox browser and enter [irc://mpserver12.flightgear.org irc://mpserver12.flightgear.org]. When ChatZilla has connected to the host, click "IRC" and "Join channel...". Pick the preferred channel.

To get directly to the main channel with ChatZilla, you can also enter [irc://mpserver12.flightgear.org/flightgear irc://mpserver12.flightgear.org/flightgear] in your browser.

== External links ==
* [http://www.ircbeginner.com/ General information about IRC]
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html General IRC commands]

[[Category:FlightGear]]
[[Category:Community]]

Building FlightGear - Devuan

2024-11-30T13:53:46Z

Flughund: Add new dependency libc-ares.

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libc-ares-dev</code>, <code>libplib-dev</code>, <code>libpopenscenegraph-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libc-ares-dev libopenscenegraph-dev libplib-dev libsimgear-dev"

su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libc-ares-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev libjpeg62-turbo-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev librsvg2-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [https://wiki.debian.org/EnvironmentVariables environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2024.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1 #OR# export FG_VERSION=next
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== libc-ares ===
This step is only required to compile FlightGear 'next':
cd $FG_SRC_DIR
<nowiki>git clone https://github.com/c-ares/c-ares.git libc-ares.git</nowiki>
cd libc-ares.git
git checkout v1.34
mkdir -p $FG_SRC_DIR/build-c-ares && cd $FG_SRC_DIR/build-c-ares
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX="$FG_INSTALL_DIR" $FG_SRC_DIR/libc-ares.git
make -j$(nproc)
make install

=== [[plib|libplib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install

=== [[OpenSceneGraph]] ===
To compile FlightGear release version branch <code>release/2024-build</code> is required, for FlightGear next branch <code>next</code>.
if [ "$FG_VERSION" = "release/2024.1" ]; then export FG_OSG_VERSION=release/2024-build; fi
if [ "$FG_VERSION" = "next" ]; then export FG_OSG_VERSION=next; fi

cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki>
cd FG-OpenSceneGraph.git
git checkout $FG_OSG_VERSION
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR, the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

Building FlightGear - Devuan

2024-11-15T22:28:33Z

Flughund: OSG update and some dependencies

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libplib-dev</code>, <code>libpopenscenegraph-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libopenscenegraph-dev, libplib-dev libsimgear-dev"

su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libc-ares-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev libjpeg62-turbo-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev librsvg2-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [https://wiki.debian.org/EnvironmentVariables environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2024.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1 #OR# export FG_VERSION=next
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install

=== [[OpenSceneGraph]] ===
To compile FlightGear release version branch <code>release/2024-build</code> is required, for FlightGear next branch <code>next</code>.
if [ "$FG_VERSION" = "release/2024.1" ]; then export FG_OSG_VERSION=release/2024-build; fi
if [ "$FG_VERSION" = "next" ]; then export FG_OSG_VERSION=next; fi

cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki>
cd FG-OpenSceneGraph.git
git checkout $FG_OSG_VERSION
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR, the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

Building FlightGear - Devuan

2024-11-10T02:04:08Z

Flughund: Temporarily remove OSG from the equation until issues are resolved.

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libplib-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libplib-dev libsimgear-dev"


su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libc-ares-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev libopenscenegraph-dev"

== Build and install ==
Some things require customisation. We'll use [https://wiki.debian.org/EnvironmentVariables environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2024.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1 #OR# export FG_VERSION=next
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

Building FlightGear - Devuan

2024-11-09T02:04:43Z

Flughund: FG-OSG branch selection and fixed a broken link.

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libplib-dev</code>, <code>libpopenscenegraph-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libplib-dev libpopenscenegraph-dev libsimgear-dev"

su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libc-ares-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [https://wiki.debian.org/EnvironmentVariables environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2024.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1 #OR# export FG_VERSION=next
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install

=== [[OpenSceneGraph]] ===
To compile FlightGear release version branch <code>release/2024-build</code> is required, for FlightGear next branch <code>fgfs-osg-36-2</code>.
export FG_OSG_VERSION=release/2024-build #OR# export FG_OSG_VERSION=fgfs-osg-36-2

cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki>
cd FG-OpenSceneGraph.git
git checkout $FG_OSG_VERSION
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git
make -j$(nproc)
make install

=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

Building FlightGear - Devuan

2024-10-26T13:31:07Z

Flughund: OSG branch and libc-ares-dev

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libplib-dev</code>, <code>libpopenscenegraph-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libplib-dev libpopenscenegraph-dev libsimgear-dev"

su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libc-ares-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2020.3</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install

=== [[OpenSceneGraph]] ===
cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki>
cd FG-OpenSceneGraph.git
git checkout fgfs-osg-36-2
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git
make -j$(nproc)
make install

=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

Building FlightGear - Devuan

2024-10-18T23:28:16Z

Flughund: Update for the 2024.1 release

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.
: For VR support add package <code>libopenxr-dev</code> to the list below.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libplib-dev</code>, <code>libpopenscenegraph-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get remove libplib-dev libpopenscenegraph-dev libsimgear-dev"

su - -c "apt-get install freeglut3-dev libavcodec-dev libavformat-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev liblzma-dev libopenal-dev libqt5quick5 libqt5svg5-dev libswscale-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2020.3</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2024.1
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install

=== [[OpenSceneGraph]] ===
cd $FG_SRC_DIR
<nowiki>git clone https://gitlab.com/flightgear/openscenegraph.git FG-OpenSceneGraph.git</nowiki>
cd FG-OpenSceneGraph.git
git checkout release/2024-build
mkdir -p $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/FG-OpenSceneGraph.git
make -j$(nproc)
make install

=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias fgfs='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH $FG_INSTALL_DIR/bin/fgfs' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>fgfs --launcher</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#Keeping_it_current|git for laymen]] section.

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-osg && make uninstall; rm -R $FG_SRC_DIR/lib/osgPlugins-3.6.5
rm -RI $FG_INSTALL_DIR/include/plib; rm $FG_INSTALL_DIR/lib/libplib*.a
rm -RI $FG_INSTALL_DIR/share/fgdata

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

{{Building}}

FlightGear IRC channel

2024-05-26T03:35:05Z

Flughund: Voice required in #flightgear

{{DEFAULTSORT:IRC channel}}
The '''FlightGear IRC Network''' is an online system that will allow you to talk to a lot of people around the world and is related to everything about [[FlightGear]]. It's mostly used by developers, but it is also a good place to ask for help if you are having a question.

== Connecting to the network ==
It consists of localised servers that are all linked up to form a seamless chat network so if you are based in England you would connect to a nearby server in England and you would see exactly the same people as someone connecting to a server in the USA.

To connect to the IRCnet network you first need a suitable client. You can also use [http://www.xchat.org/ XChat] (Linux and Windows), [http://sourceforge.net/projects/xchataqua/ X-Chat Aqua] (X Chat Mac), [http://www.pidgin.im/ Pidgin], [http://colloquy.info/ Colloquy] (for Mac/iOS), [http://www.mirc.com/ mIRC], [https://Konversation.kde.org Konversation] or any other client.

When you first login to the network you must pick yourself a unique nickname for the current chat session. Nicknames can be up to 31 characters in length and contain numbers and some punctuation characters. Some examples of nicknames you can use are:

* Fred
* BIG_fred
* ^Fred^
* Fred-
* ^Fred
* fred007

It doesn't matter about capital or lower case letters in the nickname since they are treated the same when people want to contact you and there are some weird and obscure rules about nicknames such as them not being able to begin with a "-" character. Most of these rules have no rhyme nor reason to them but we didn't write the software, we just have to try and tell people how to use it. Have an experiment and see what suits you best.

Once you found your personal unique nickname you may want to register it with [[#Network_Services|NickServ]] (see below).

== Official hosts ==
{| class="wikitable"
! Host !! Location
|-
| de.irc.flightgear.org
| Germany
|-
| irc.flightgear.org
| currently an alias for de.irc.flightgear.org
|}

The '''port''' to connect to is 6667 (or 6659 for SSL) for each server.

These servers are interconnected to form the FlightGear IRC network. Please choose the host closest to you geographically.

The FlightGear IRC network has several channels, some of which are listed below. To obtain a real list, use the IRC command "/list".

{| class="wikitable"
! Channel !! Use
|-
| #flightgear
| Main channel (English). Due to spamming it is required to have voice, [[FlightGear_IRC_channel#NickServ|register]] your nick and contact (query) ''lru'' for autovoice.
|-
| #flightgear-blender
| [[Blender]]
|-
| #flightgearFR
| FlightGear Channel for French Speaking
|-
|#flightgearIT
|FlightGear Channel for Italian Speaking
|-
| #flightgearNL
| FlightGear Channel for Dutch Speaking
|-
|#flightgearPL
|FlightGear Channel for Polish Speaking
|-
| #fg_school
| [[FlightGear Flight Academy|Flight School]]
|-
| #fgms
| [[fgms]] related stuff
|-
| #airliners
| IFR Navigation Squawk
|-
| #fg_cantene
| Off topic community
|-
| #fg-ru
| Russian Flightgear Community
|-
| #wiki
| Wiki
|-
| #flightgear-forum
| Forum
|-
| #help
| general help on IRC
|-
| #staffers
| Server Admins
|-
| #flyingclub
| [[FlightGear Flying Club]]
|}

== Network Services ==
=== NickServ ===
NickServ allows you to "register" a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type

/msg NickServ ''COMMAND''

For more information on a specific command, type

/msg NickServ HELP ''COMMAND''

Some of the common commands are:

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a nickname.
|-
| GROUP
| Adds a nickname to your account.
|-
| IDENTIFY
| Identifies to services for a nickname.
|-
| GHOST
| Reclaims use of a nickname.
|}

This service is intended to provide a way for IRC users to ensure their identity is not compromised. It is ''not'' intended to facilitate "stealing" of nicknames or other malicious actions. Abuse of NickServ will result in, at minimum, loss of the abused nickname(s).

=== ChanServ ===
ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Some available commands are listed below; to use them, type

/msg ChanServ ''COMMAND''

For more information on a specific command, type:

/msg ChanServ HELP ''COMMAND''

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a channel.
|-
| RECOVER
| Regain control of your channel.
|-
| FLAGS
| Manipulates specific permissions on a channel.
|}

=== MemoServ ===
MemoServ is a utility allowing IRC users to send short messages to other IRC users, whether they are online at the time or not. Both the sender's nickname and the target nickname must be registered in order to send a memo.

MemoServ's commands include:

{| class="wikitable"
! Command !! Purpose
|-
| READ
| Reads a memo.
|-
| SEND
| Sends a memo to a user.
|-
| SENDGROUP
| Sends a memo to all members on a group.
|-
| SENDOPS
| Sends a memo to all ops on a channel.
|-
| DELETE
| Deletes memos.
|}

For help on any of the above commands, type:

/msg MemoServ HELP ''COMMAND''

To see a list of all available MemoServ commands, type:

/msg MemoServ HELP

=== HostServ ===
HostServ allows users to request a virtual hostname. Normally we only allow IPs to be shown on a users
connection (so no dns lookups are made upon a new connection). To hide your host to other users you are
free to select a vhost from a predefined list (or a uniquely requested one) via hostserv. In that case
your selected hostname will be shown to others instead of your real IP.

To see the list of all available commands, type:

/msg HostServ HELP

Some commands of interest are:

{| class="wikitable"
! IRC Command !! Purpose
|-
| OFFERLIST
| Lists all available vhosts.
|-
| TAKE
| Take an offered vhost for use.
|-
| REQUEST
| Requests new virtual hostname for current nick.
|}

For further help type <tt>'''/msg ''SERVICE'' help'''</tt> (replace <tt>''SERVICE''</tt> with the name of the service)

== Other hosts ==
{| class="wikitable"
! Network !! Channel !! Description
|-
| irc.freenode.net
| #flightgear
| Only for emergencies.
|}

== How to get in there with ChatZilla ==
[[File:IRC-ChatZilla.jpg|thumb|ChatZilla Client area]]
When using ChatZilla, go to your Mozilla/Firefox browser and enter [irc://mpserver12.flightgear.org irc://mpserver12.flightgear.org]. When ChatZilla has connected to the host, click "IRC" and "Join channel...". Pick the preferred channel.

To get directly to the main channel with ChatZilla, you can also enter [irc://mpserver12.flightgear.org/flightgear irc://mpserver12.flightgear.org/flightgear] in your browser.

== External links ==
* [http://www.ircbeginner.com/ General information about IRC]
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html General IRC commands]

[[Category:FlightGear]]
[[Category:Community]]

FlightGear IRC channel

2024-05-24T17:37:23Z

Flughund: corrected spelling to match channel name

{{DEFAULTSORT:IRC channel}}
The '''FlightGear IRC Network''' is an online system that will allow you to talk to a lot of people around the world and is related to everything about [[FlightGear]]. It's mostly used by developers, but it is also a good place to ask for help if you are having a question.

== Connecting to the network ==
It consists of localised servers that are all linked up to form a seamless chat network so if you are based in England you would connect to a nearby server in England and you would see exactly the same people as someone connecting to a server in the USA.

To connect to the IRCnet network you first need a suitable client. You can also use [http://www.xchat.org/ XChat] (Linux and Windows), [http://sourceforge.net/projects/xchataqua/ X-Chat Aqua] (X Chat Mac), [http://www.pidgin.im/ Pidgin], [http://colloquy.info/ Colloquy] (for Mac/iOS), [http://www.mirc.com/ mIRC], [https://Konversation.kde.org Konversation] or any other client.

When you first login to the network you must pick yourself a unique nickname for the current chat session. Nicknames can be up to 31 characters in length and contain numbers and some punctuation characters. Some examples of nicknames you can use are:

* Fred
* BIG_fred
* ^Fred^
* Fred-
* ^Fred
* fred007

It doesn't matter about capital or lower case letters in the nickname since they are treated the same when people want to contact you and there are some weird and obscure rules about nicknames such as them not being able to begin with a "-" character. Most of these rules have no rhyme nor reason to them but we didn't write the software, we just have to try and tell people how to use it. Have an experiment and see what suits you best.

Once you found your personal unique nickname you may want to register it with [[#Network_Services|NickServ]] (see below).

== Official hosts ==
{| class="wikitable"
! Host !! Location
|-
| de.irc.flightgear.org
| Germany
|-
| irc.flightgear.org
| currently an alias for de.irc.flightgear.org
|}

The '''port''' to connect to is 6667 (or 6659 for SSL) for each server.

These servers are interconnected to form the FlightGear IRC network. Please choose the host closest to you geographically.

The FlightGear IRC network has several channels, some of which are listed below. To obtain a real list, use the IRC command "/list".

{| class="wikitable"
! Channel !! Use
|-
| #flightgear
| Main channel (English)
|-
| #flightgear-blender
| [[Blender]]
|-
| #flightgearFR
| FlightGear Channel for French Speaking
|-
|#flightgearIT
|FlightGear Channel for Italian Speaking
|-
| #flightgearNL
| FlightGear Channel for Dutch Speaking
|-
|#flightgearPL
|FlightGear Channel for Polish Speaking
|-
| #fg_school
| [[FlightGear Flight Academy|Flight School]]
|-
| #fgms
| [[fgms]] related stuff
|-
| #airliners
| IFR Navigation Squawk
|-
| #fg_cantene
| Off topic community
|-
| #fg-ru
| Russian Flightgear Community
|-
| #wiki
| Wiki
|-
| #flightgear-forum
| Forum
|-
| #help
| general help on IRC
|-
| #staffers
| Server Admins
|-
| #flyingclub
| [[FlightGear Flying Club]]
|}

== Network Services ==
=== NickServ ===
NickServ allows you to "register" a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type

/msg NickServ ''COMMAND''

For more information on a specific command, type

/msg NickServ HELP ''COMMAND''

Some of the common commands are:

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a nickname.
|-
| GROUP
| Adds a nickname to your account.
|-
| IDENTIFY
| Identifies to services for a nickname.
|-
| GHOST
| Reclaims use of a nickname.
|}

This service is intended to provide a way for IRC users to ensure their identity is not compromised. It is ''not'' intended to facilitate "stealing" of nicknames or other malicious actions. Abuse of NickServ will result in, at minimum, loss of the abused nickname(s).

=== ChanServ ===
ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Some available commands are listed below; to use them, type

/msg ChanServ ''COMMAND''

For more information on a specific command, type:

/msg ChanServ HELP ''COMMAND''

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a channel.
|-
| RECOVER
| Regain control of your channel.
|-
| FLAGS
| Manipulates specific permissions on a channel.
|}

=== MemoServ ===
MemoServ is a utility allowing IRC users to send short messages to other IRC users, whether they are online at the time or not. Both the sender's nickname and the target nickname must be registered in order to send a memo.

MemoServ's commands include:

{| class="wikitable"
! Command !! Purpose
|-
| READ
| Reads a memo.
|-
| SEND
| Sends a memo to a user.
|-
| SENDGROUP
| Sends a memo to all members on a group.
|-
| SENDOPS
| Sends a memo to all ops on a channel.
|-
| DELETE
| Deletes memos.
|}

For help on any of the above commands, type:

/msg MemoServ HELP ''COMMAND''

To see a list of all available MemoServ commands, type:

/msg MemoServ HELP

=== HostServ ===
HostServ allows users to request a virtual hostname. Normally we only allow IPs to be shown on a users
connection (so no dns lookups are made upon a new connection). To hide your host to other users you are
free to select a vhost from a predefined list (or a uniquely requested one) via hostserv. In that case
your selected hostname will be shown to others instead of your real IP.

To see the list of all available commands, type:

/msg HostServ HELP

Some commands of interest are:

{| class="wikitable"
! IRC Command !! Purpose
|-
| OFFERLIST
| Lists all available vhosts.
|-
| TAKE
| Take an offered vhost for use.
|-
| REQUEST
| Requests new virtual hostname for current nick.
|}

For further help type <tt>'''/msg ''SERVICE'' help'''</tt> (replace <tt>''SERVICE''</tt> with the name of the service)

== Other hosts ==
{| class="wikitable"
! Network !! Channel !! Description
|-
| irc.freenode.net
| #flightgear
| Only for emergencies.
|}

== How to get in there with ChatZilla ==
[[File:IRC-ChatZilla.jpg|thumb|ChatZilla Client area]]
When using ChatZilla, go to your Mozilla/Firefox browser and enter [irc://mpserver12.flightgear.org irc://mpserver12.flightgear.org]. When ChatZilla has connected to the host, click "IRC" and "Join channel...". Pick the preferred channel.

To get directly to the main channel with ChatZilla, you can also enter [irc://mpserver12.flightgear.org/flightgear irc://mpserver12.flightgear.org/flightgear] in your browser.

== External links ==
* [http://www.ircbeginner.com/ General information about IRC]
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html General IRC commands]

[[Category:FlightGear]]
[[Category:Community]]

AI Traffic

2023-09-11T07:52:14Z

Flughund: s/aircrafts/aircraft/

{{AI Navbar}}

'''AI Traffic''' (Artificial Intelligence), '''AI-Traffic''', or '''Interactive Traffic''' was introduced with [[FlightGear]] version 0.9.5. The purpose of AI traffic is to automatically populate airports sceneries with animated aircraft models reflecting the actual daily movements at and between airports to enrich the flightgear experience and improve its realism. This page aims at providing the documentation needed to populate airports with AI traffic.

In essence, the AI controlled traffic system is comprised of four elements:
# AI Aircraft models: Are part of the base package under <tt>$DATA/AI/Aircraft</tt> and cannot be flown by end user like regular FDM models as they are dedicated and exclusive to AI systems.
# AI traffic schedules: Are part of the base package under <tt>$DATA/AI/Traffic</tt> and define where and when AI aircraft should fly. Files are unique per Operator's ICAO and split in sub-folders using the ICAO Initial. For example, traffic for United Airlines is stored under <tt>[[$FG ROOT]]/AI/Traffic/U/UAL.xml</tt>
# Groundnets: Are part of the scenery pack under <tt>[[terrasync]]/Airports</tt> and contain the information required to guide AI aircraft on the ground from gates to runways and vice versa, at each individual airport (one per airport). The parking stands defined in an airport groundnet can also be used as Starting Positions when flying an FDM aircraft. They are shown and can be selected in Flightgear's "Location" startup tab.
# Runway Use Configurations (RWYUSE): Are part of the scenery pack under <tt>[[terrasync]]/Airports</tt> and condition which runway(s) are for AI take off and landings based on the time of the day and wind conditions.

= Traffic Schedules =
Traffic pattern describe the relationship between two separate entities: Aircraft and Flights.

In real life, Flight Scheduling aims at maximizing the number of flights operated with the fleet of aircraft available, taking in account each aircraft’s initial location, the length of each flight, the required turnaround time at each airport and of course the routes operated. In practice an aircraft will fly different routes of different length on different day/time and not all aircraft will return to their home base the same day, especially in the case of long haul routes. The list of flights an aircraft will operate during a set period of time is the Aircraft Schedule.
AI aircraft provide some extra benefits: They do not need maintenance (or crew replacement) and so can be scheduled for use 24h00 per day; they are also never late nor cancelled hence they will perform 100% of their assigned flights on time.

To minimize the amount of data handled, a frequency is attached to each flight as either daily or weekly; For example an aircraft based at EHAM can fly daily in the morning to EGLL (and back) but then to different destinations in the afternoon depending on the day of the week (LFPG on Monday, EDDF on Tuesday etc). In this scenario the EGLL flights are operated daily and the LFPG and EDDF ones, weekly as it will take another full week before they are operated again.

Like in real life, the flights assigned to an aircraft must follow a logical routing sequence and the arrival city of one flight must be the departure city of the next (AI aircraft do not time travel no teleport).
Flightgear schedules are set for a full week and repeat indefinitely until the traffic file is updated. As a result, the routing sequence described above must be consistent with the schedule weekly reset: If the last flight in an aircraft schedule (Sunday night) take it to KSFO then the first flight in the schedule (Monday morning) must depart from KSFO.
From the above. The Home Base of an aircraft is always the departure city of its first flight in the schedule ie the airport it will be departing from for its first flight on Monday morning.

It is recommended the traffic schedules follow as much as possible reality and so they should include turnaround time at each airport even if an AI aircraft does not require cleaning and refuelling.

To facilitate scheduling, a new database format was introduced in FlightGear 1.9.0 and flights are no longer directly and rigidly assigned to a specific aircraft (Unique registration). Instead, a more generic description of a fleet is given, along with a series of flights that need to be carried out. The routing is then taken care of by FlightGear itself.

== An example of a traffic file ==

Below is a complete and working example of a Traffic Manager II file, as it can be used with FlightGear 1.9.0 and later:
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<trafficlist>
<aircraft>
<model>Aircraft/MD11/Models/KLMmd11.xml</model>
<livery>KLM</livery>
<airline>KLM</airline>
<home-port>EHAM</home-port>
<required-aircraft>MD11KLM</required-aircraft>
<actype>MD11/P</actype>
<offset>25</offset>
<radius>39</radius>
<flighttype>gate</flighttype>
<performance-class>jet_transport</performance-class>
<registration>PH-KCA</registration>
<heavy>true</heavy>
</aircraft>
<aircraft>
<model>Aircraft/MD11/Models/KLMmd11.xml</model>
<livery>KLM</livery>
<airline>KLM</airline>
<home-port>EHAM</home-port>
<required-aircraft>MD11KLM</required-aircraft>
<actype>MD11/P</actype>
<offset>25</offset>
<radius>39</radius>
<flighttype>gate</flighttype>
<performance-class>jet_transport</performance-class>
<registration>PH-KCB</registration>
<heavy>true</heavy>
</aircraft>

<flight>
<callsign>KLM0765</callsign>
<required-aircraft>MD11KLM</required-aircraft>
<fltrules>IFR</fltrules>
<departure>
<port>EHAM</port>
<time>0/12:35:00</time>
</departure>
<cruise-alt>330</cruise-alt>
<arrival>
<port>TNCM</port>
<time>0/21:15:00</time>
</arrival>
<repeat>WEEK</repeat>
</flight>

<flight>
<callsign>KLM0769</callsign>
<required-aircraft>MD11KLM</required-aircraft>
<fltrules>IFR</fltrules>
<departure>
<port>TNCM</port>
<time>3/01:25:00</time>
</departure>
<cruise-alt>330</cruise-alt>
<arrival>
<port>EHAM</port>
<time>3/10:50:00</time>
</arrival>
<repeat>WEEK</repeat>
</flight>
</trafficlist>
</syntaxhighlight>

== Dissecting the traffic file ==
Here I will discuss the general structure of a traffic file in more detail. As discussed, the traffic patterns are centered around aircraft and flights. Therefore, a minimal traffic file will consist of two sections: the aircraft definition and the flights section. In the next two sections, I will discuss each of these sections.

=== General layout ===
The general layout of each file should look like the above example.
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<trafficlist>

</trafficlist>
</syntaxhighlight>
The general layout of each file should look like the above example. The first line contains a generic xml header, which is followed on the second line with a '''<trafficlist>''' statement. Also, the last line in the file should close off the trafficlist section using the '''</trafficlist>''' statement. As will be illustrated below, between these two statements can be one or more aircraft definitions.

=== Defining the aircraft ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<trafficlist>
<aircraft>
<model>Aircraft/MD11/Models/KLMmd11.xml</model>
<livery>KLM</livery>
<airline>KLM</airline>
<home-port>EHAM</home-port>
<required-aircraft>MD11KLM</required-aircraft>
<actype>MD11/P</actype>
<offset>25</offset>
<radius>39</radius>
<flighttype>gate</flighttype>
<performance-class>jet_transport</performance-class>
<registration>PH-KCA</registration>
<heavy>true</heavy>
</aircraft>
<aircraft>
...
</aircraft>
</trafficlist>
</syntaxhighlight>
The first lines inside the '''<aircraft>''' definition specify some of the aircraft's performance characteristics.

* '''<model>''' Here is a path specified to the 3D model that should be used in FlightGear.
* '''<livery>''' This line is currently unused, and will likely remain unused. The original idea was to combine this with the '''<model>''' line (see above) to load a specific combination of aircraft type ('''<actype>''') and paint scheme, but I abandoned that idea, because it didn't turn out to be very compatible with the existing FlightGear model loading code.
* '''<airline>''' This line refers to the airline operating the aircraft. This information is currently used by FlightGear to handle gate/parking assignments. Use the official 3-letter [[ICAO]] airline code here, in case of commercial traffic. This keyword is unlikely to be used for general aviation and military traffic.
* '''<home-port>''' Each FlightGear aircraft is assigned to a home airport. Internally, this is used to ensure that routes are setup that will eventually lead back to the home airport. This is done to maintain some sensibility in the routing algorithm. '''[New for Traffic Manager II]'''
* '''<required-aircraft>''' This value is a key that binds aircraft and flights together. In case of this example, the key MD11KLM. Indicates that this aircraft will only carry out flights containing the same key. Usually, a combination of aircraft type, and airline will suffice for this key. In some cases, in particular, when specific aircraft / airlines are distributed across multiple hubs (i.e. home ports), it may be necessary to specify a key containing the home airport as well. For example, Delta Airlines operates 767's out of Atlanta, as well as out of New York. To separate between these two cases, it would be advisable to use two keys; one for KATL (e.g. 767DALKATL), and one for KJFK (e.g., 767DALKJFK). '''[NEW for Traffic Manager II]'''
* '''<actype>''' A description of the aircraft type reserved for future use in [[ATC]].
* '''<offset>''' Ground offset of the 3D model. Not all aircraft 3D models are built using the same convention. Use this parameter to align the wheels with the ground. Notice that this parameter will probably become obsolete in the near future, because model view point references can also be done in the XML file that the '''<model>''' keyword refers to.
* '''<radius>''' An estimate of the aircraft's size. This is mainly used at airports for gate assignments.
* '''<flighttype>''' In the near future, this keyword will be used for runway assignments, so that general aviation, commercial, and military traffic will use different runways if that is part of the airport's operational procedures. This line is also used for gate assignments and should be one of the following:
** '''ga''' (general aviation),
** '''cargo''' (cargo)
** '''gate''' (commercial passenger traffic)
** '''mil-fighter''' (military fighter)
** '''mil-cargo''' (military transport)
* '''<performance-class>''' This line is used to determine the performance characteristics of AI aircraft. This should match one of the performance classes that are predefined in FlightGear. Currently, the following performance classes are supported:
** '''light_aircraft''' (General aviation prop driven single or twin),
** '''turboprop_transport''' (Commercial Turboprop),
** '''jet_transport''' (Commercial jet)
** '''heavy_jet''' (Commercial jet w/ MTOW > 136tons)
** '''ww2_fighter''' (world war two fighter),
** '''jet_fighter''' (modern fighter aircraft)
** '''tanker''' (tanker aircraft), or.
** '''ufo''' (allows extreme accel/decel capabilities).
* '''<registration>''' The aircraft's tail number. Future versions of FlightGear will use this registration in ATC for general aviation traffic. For commercial traffic the registration number will likely remain unused.
* '''<heavy>''' Can be true or false. Reserved for future use by ATC, to determine whether the postfix "Heavy" should be appended to the aircraft's callsign.

=== Defining a flight ===
The Traffic Manager II file formats contains separate sections for both aircraft and flights information, with the common denominator being a shared key that links aircraft and flight information together. In other words, the general layout of a Traffic Manager II file looks something like this:
<syntaxhighlight lang="xml">
<aircraft>
...
<required-aircraft>MD11KLM</required-aircraft>
...
</aircraft>

<flight>
...
<required-aircraft>MD11KLM</required-aircraft>
...
</flight>
</syntaxhighlight>
Each flight is defined between the '''<flight>''' and '''</flight>''' statements. For example, let's have a look at a randomly selected flight from our KLM.xml example.
<syntaxhighlight lang="xml">
<flight>
<callsign>KLM0769</callsign>
<required-aircraft>MD11KLM</required-aircraft>
<fltrules>IFR</fltrules>
<departure>
<port>EHAM</port>
<time>2/12:35:00</time>
</departure>
<cruise-alt>330</cruise-alt>
<arrival>
<port>TNCB</port>
<time>2/22:15:00</time>
</arrival>
<repeat>WEEK</repeat>
</flight>
</syntaxhighlight>
The '''<flight>''' section is slightly more complex than the aircraft definition itself, because it has a few nested levels, however, these should mostly be self-explanatory. The following keywords should be specified:
* '''<flight>''' All the relevant parameter should be specified between the '''<flight></flight>''' keywords.
* '''<callsign>''' The airline callsign used for ATC. If this is an airline flight it should be combination of the airline callsign (e.g. '''KLM''' for KLM, or '''Springbok''' for South African Airways), and the flight number (e.g. '''KLM0605''', or '''Springbok0033''').
* '''<required-aircraft>''' The key that links this flight to a particular aircraft. The see explanation in the ''aircraft'' section.
* '''<fltrules>''' Can be ''IFR'' or ''VFR''. This is required for use in ATC, but currently not used. This is likely to change, however.
* '''<departure>''' Definition of the departure airport. This section should contain the '''<port>''' and '''<nowiki><time></nowiki>''' keywords.
* '''<cruise-alt>''' Cruising altitude for this flight. This is a bit of a simplification from the real world, where aircraft usually don't stay at the same cruise altitude throughout the flight. This behavior will probably also change in future versions. Values are in [https://en.wikipedia.org/wiki/Flight_level flightlevels]
* '''<arrival>''' Same as '''<departure>''', but now defining the '''<port>''' and '''<nowiki><time></nowiki>''' of arrival.
* '''<repeat>''' Repeat period. This can be either the keyword ''WEEK'', or a number followed by ''Hr''. ''WEEK'' means that the whole schedule repeats itself on a weekly basis. ''Hr'' means that the whole schedule repeats after the number of hours specified directly before it (e.g. ''24Hr'' means that the schedule repeats after 24 hours). With Traffic Manager II, it is generally recommended not to mix schedules that rotate on different frequencies. In general, the best results are obtained when using only weekly rotating flights. For flights that are in reality operated on a daily basis, it is recommended to just specify multiple entries, i.e. one separate flight for every weekday.
* '''<port>''' This should be the international ICAO airport code. This keyword should be specified only within the '''<departure>''' or '''<arrival>''' sections. As far as I know, here it should still be in upper case, although the FlightGear command line currently also supports lower case ICAO codes.
* '''<nowiki><time></nowiki>''' Used to specify the '''<departure>''' or '''<arrival>''' time. The format of this string is ''hour:minute:second''. Notice that departure day is optional and is specifically intended to be used in combination with a weekly repeating schedule. When used in combination with other schedules, results may be unpredictable. Times should be in UTC. Weekdays start on Sunday (0) and end on Saturday (6).

== Putting it all together: Including a traffic file ==
Traffic files are found under [[$FG_ROOT]]/AI/Traffic. The actual traffic files should be stored in a subdirectory one level below /AI/Traffic.
All traffic is organized by Operator ICAO code, and stored in a single letter directory. For example, KLM traffic can be found in [[$FG_ROOT]]/AI/Traffic/K/KLM.xml, and United Airlines traffic is stored in [[$FG_ROOT]]/AI/Traffic/U/UAL.xml.

The name of the file is the ICAO of the operator (aircraft owner) which is normally the same that the one found in the <airline> tag in the file itself but not alway. For example Compass Airlines in Minneapolis, has the ICAO code CPZ but operates flights for both American Airlines (AAL) and Delta Airlines (DAL). In this scenario the traffic file will be stored as [[$FG_ROOT]]/AI/Traffic/C/CPZ.xml and will contain a series of aircraft with airlines tags AAL and another series with tag DAL. Similarly, certain flights in the file will be numbered AAxxxx or DLxxxx.

= Ground networks =

[[File:LFPG T2E ParkPos.jpg|thumb|Using a Groundnet, AI aircraft can park precisely at the Terminal gates]]

Using the traffic files information above, the AI Traffic Manager knows which AI aircraft should land at (and take off from) each airport and when. It will automatically place the relevant aircraft models in the scenery and animate them so they navigate from the runways to the gates and vice versa, according to their individual schedule.

Although the physical layout of each airport is stored in FlightGear's APT.DAT master file, the information is not accurate enough to determine which specific routes AI models can use; Instead, Traffic manager will rely on a dedicated file containing a simple wireframe/network of taxiways and gates AI aircraft can follow whilst on the ground ie a GroundNet. A groundnet is made of 3 different elements: Parking Positions, Nodes and Segments (to join nodes and Parking together).

This routing information is aggregated, per airport, in a XML, stored and distributed by Terrasync as '''/Terrasync/Airports/[I]/[C]/[A]/[ICAO].groundnet.xml''' where ICAO stands for the 4 letter ICAO code of the relevant airport.

Similarly to Terrain and Objects, Terrasync groundnets can be overridden by placing a personalized version in your custom scenery folder, using the same path structure: /Custom Scenery/Airports/[I]/[C]/[A]/[ICAO].groundnet.xml.

Groundnets are not mandatory but, in absence of this routing information, AI Aircraft cannot park anywhere; they will still try to stick to their schedule, appearing magically at the centre of the airport and taxiing directly to the runways’ thresholds, over grass, buildings and static objects, on time.

Groundnets rely on the runway threshold information stored in /Terrasync/Airports/[I]/[C]/[A]/[ICAO].threshold.xml to determine where runways are (the space between each pair of thresholds in the file) and their heading. This data is used to determine an aircraft has reached the runway and can initiate take off. Similarly it is used to select where an arriving AI aircraft can touch down and start braking.

== A technical perspective ==
A ground network xml file consists of four tables:
* '''<frequencies>''' The Airport’s radio frequencies (Optional). As of v1.9.0, FlightGear uses these to display some ATC messages like start-up approval requests. You can "hear" them by tuning to the first ground frequency listed in the section.
* '''<parkingList>''' The details of each parking/gate at the airport and the characteristics of which AI aircraft can use them.
* '''<TaxiNodes>''' The list of all the nodes in the ground network.
* '''<TaxiWaySegments>''' A list of all links/segments (or "arcs" as David Luff called them initially) existing between all nodes and Parking Positions.

Each Parking and Node element in the groundnet has a unique index number, allowing routes be formed (from one ID to the next via a segment/arc) between parking positions and runways

''Parking Positions Parameters:''
* '''index''' Unique ID, internal to the file structure
* '''lat''' latitude in decimal minutes format, for example <code>N50 56.988</code>)
* '''lon''' longitude in decimal minutes format, for example <code>W01 21.756</code>)
* '''name & number ''' (gate identification as found on airport charts, for example <code>D23</code> or <code>C1</code>).
* '''type:''' The type of aircraft which can use this space. Matched to the <flighttype> parameter found in traffic files:
** '''ga''' (general aviation),
** '''cargo''' (cargo/freighter)
** '''gate''' (commercial passenger traffic)
** '''mil-fighter''' (military fighter)
** '''mil-cargo''' (military transport)
* '''heading:''' The heading at which the aircraft parks in this space.
* '''radius:''' The size of the parking spot. Matched to the aircraft <radius> parameter in traffic files to determine if a given AI Aircraft model will fit the position. See [[aircraft radii]]
* '''airlineCodes:''' a comma-separated list of ICAO airline codes allowed to park at this gate. Matched to the aircraft <airline> parameter of traffic files. Leave blank for all airline to be able to use the gate.
* '''pushBackRoute:''' The ID of the next node in the network along a pushback route. In a correctly configured network, the AI aircraft will taxi to this node in reverse, thus simulating being pushed back. See the documentation for the PushBack hold point type below.

''Nodes parameters:''

* '''isOnRunway'''' A logical value that is 1 when the node is on the runway, 0 otherwise. Aircraft waiting to take off will line up behind the last node marked “not on runway” (“0”) until the runway is clear
* '''holdPointType''' can have the following values:
** '''None''' Not a holding point (normal taxi-through node)
** '''PushBack''' The node marks the end of a pushback route, where the aircraft stops rolling backward and start rolling forward upon clearance. A pushback Holding Point can be part of more than one pushback route. See Pushback below.
** '''Normal''' (Not yet supported): a regular taxiway holding point.
** '''CAT II/III''' (Not yet supported): a special holding point for IFR conditions.

''segments parameters:''

* '''begin''' The id of the parking space or AINode where this segment starts
* '''end''' The id of the parking space or AINode where this segment ends
* '''IsPushBackRoute''' a logical value. Should be 1 if the current segment is part of a route connecting a gate to a push back hold point, or 0 otherwise.
* '''name''' Name of the taxiway.

== Tools & Source Material ==
Groundnets can be built using either FG Airports (v0.032 or later) or Taxidraw (legacy)

[[FGAirports]] is the current tool of choice. Its philosophy is airport centered rather than file specific and allows you to visualize at a glance all of the existing groundnets as well as editing them and submitting them to Terrasync. It leverages Open Street Map data, APT.DAT and scenery xmls to provide a visual representation of the airport layout as well as thresholds and tower positions.

FGA automatically checks the validity of groundnet files before submission and assess their adequacy by comparing the number of gates set against the volume of AI traffic at a particular airport.

[[TaxiDraw]] pre dates WED and allowed the creation of airport layouts from basic geometrical shapes. Its ground network module is somewhat separate from the rest of the airport project code but allows the creation and local export of simple groundnets.

See the [[TaxiDraw]] and [[FGAirports]] articles for instructions on how to obtain the tools and operating instructions.

Most Civil Aviation authorities make electronic versions of their Aeronautical Information Publication available on the web (Lookup 'eAIP' or go to https://www.eurocontrol.int/articles/ais-online). AIPs contain precise Airport Charts but also lists of parking stands with their exact Latitude/Longitude as well as usage (Cargo, Gate) and the category (radii) of aircraft they can accommodate.

Gates Numbers and Airlines operating them can often be found on Airports website. Most flight tracking sites/apps will also allow you to monitor a flight all to the way to its gate to identify who parks where.

In essence, all the information you need can be compiled from multiple sources, including Wikipedia, airport diagrams published on the net, in flight airline magazines, etc. etc. In other words, be creative!

== Ground traffic rendering ==
''19th November 2021.''

=== Performance ===

* CPU: Currently having a lot of nodes in the OSG scene-graph will rapidly make FlightGear CPU bound. A lot of separately animated ground traffic objects mean a lot of nodes. Static objects (i.e. non-animated objects) can be put into one mesh - meaning one scenegraph node with the current system.
* GPU: Having fewer draw calls is fast. Having fewer state changes is fast.
* The fast path for both CPU and GPU is creating a way to combine multiple animated objects in one mesh - this is how modern 3d applications do lots of objects with animations fast.

=== The fast way to do moving objects is to let the vertex shader look at information in buffers and position each object ===

* Have all the different path segments stored in one buffer that can be read by the vertex shader. This buffer can be generated at runtime for each airport, maybe using NASAL scripts, and not updated.It's also possible to store the 1st buffer in TerraSync.
* Have a second buffer store all per-object data in an array. The array is indexed by the object ID. This includes things like vehicle animation state, which path segment each object is on, the starting time, and a speed scaling factor. The second buffer is updated regularly by the CPU.
* Two approaches to packing different types of objects in a 1 or few meshes
**'''a).''' Every type of object is combined in one vertex buffer and rendered with the same shaders, texture atlas or array. Every vehicle is packed one after the other in the vertex buffers. Multiple types of vehicles are contained in the same mesh. Multiple instances of the same vehicle take up extra space.
*** All material parameters or uniform values that change between objects, or within objects, like specularity are added as vertex attributes or textures. A vertex shader that can handle all object animations is used.
*** The entire set of objects takes up one scene graph node, and is rendered in one draw call. It's possible to do ground vehicles and AI aircraft as two meshes.
*** The object ID (an integer) can be added to each vertex as an vertex attribute. This is used to lookup per-object info in the 2nd buffer, including the paths from the first buffer.
** '''b).''' Each different type of object (different ground vehicle) is instanced and takes up one scene-graph node. This can allow different shaders and textures per object type. There is less vertex data taking up RAM and VRAM. There are more scenegraph nodes, and draw calls.
*** The object ID (an integer) can be added as a per-instance vertex attribute.
* The vertex shader can trivially look at the object ID, then find the path segment, the starting time, speed scaling factor, and current time to position each object. If the current time is past the end of the current path, the object will stay at the end position.
* The buffers can be a uniform array (minimum of points in each path segment and more smoothing), Uniform Buffer Object (UBO - not available until Vulkan due to Macs not supporting it), a Texture Buffer Object (TBO - Mac support unknown), or a texture looked up in a vertex shader (maybe slower).
* Data format: Each path segment is x,y,z position at regular times - a time-series of positions - e.g. [10m, 20m, 0m elevation] at t = 1s. [20m, 25m, 0m] at t=2s . [30m, 30m, 0m] at t= 3s. 16 bit integers are enough, but 32 but floats can also be used at the cost of 2x the occupancy. 16 bit implementation: If a texture is used it can be 16bit RGB - R=x, G=y, B=z. 2 consecutive 8 bit values can also be read from a texture.16 bit integers can cover an ground traffic area of ~65km with a spacing of 1m. 16bits can give a ~13km ground traffic area with an accuracy of 20cm. The accuracy of the positions doesn't matter too much - the vertex shader can look at 2-3+ path positions and create a smooth interpolation (a smooth curve joining the points). The time steps can also be large.
* If a path has a slowly moving segment, it will take up more points. If a path segment takes a short amount of time, it can have a special xyz numner to indicate path has ended - otherwise the path start/end time information can be stored as uniforms or in a UBO. Vehicles that move faster can have a higher speed scaling. There can be different path segment variations, for example if vehicles have a different acceleration pattern - e.g. speeding up and braking hard, or sharper turns, in an emergency.
* Both ground vehicles, and taxiing aircraft can be done this way. It's possible to replace a conventional AI aircraft model, with a fast rendering ground traffic model once an aircraft starts taxiing.
* If models use animations, they should ideally use a vertex shader that can handle all these animations - so having multiple draw calls per model and CPU-side animation is avoided.
* It's possible to split of different parts of craft into separate meshes for parts that are very dissimilar - at the cost of more scenegraph nodes and draw calls. For example, a separate mesh for lights of various types - these lights will follow the same paths as the vechiles and position themselves correctly.
*

The way animation is handled (animation meaning moving objects, and parts of moving objects) in modern 3d application is to store the animation data in arrays/buffers on the GPU side and render multiple objects in one draw call.

From a quick google search - a 2010 blog about whether UBOs or TBOs are more suited for different tasks:

''"Personally I use them [UBOs] for instanced rendering by storing the model-view matrix and related information of each and every instance in a common uniform buffer and use the instance id as an index to this combined data structure. This usage performs very well on my system.''

''Also uniform buffers can be used to store the matrices of bones and use them for implementing skeletal animation, however, I personally prefer using normal 2D textures for this purpose to take advantage of the free interpolation thanks to the dedicated texture fetching units but that’s another story.''

''[..] Personally I use texture buffers for different geometry deformation techniques, to resolve batching issues when the size limitation of uniform buffers is a blocking factor, and for some inverse kinematics effects." - Rastergrid blog, 2010 [https://www.rastergrid.com/blog/2010/01/uniform-buffers-vs-texture-buffers/][https://web.archive.org/web/20211119134448/https://www.rastergrid.com/blog/2010/01/uniform-buffers-vs-texture-buffers/]''

This is from a 2010 blog - this general approach has been the way to do lots of animated objects for a long time.

Even really complicated animations like moving bodies and cloth physics are handled by moving animation data into buffers - this approach would be needed if FlightGear ever did a simulation of crowds at an airport - not just for boarding one plane which probably won't be too cripplingly slow. But for crowds boarding lots of planes, and moving about large airports. For animating humans, there are will be standard animation formats compatible with output of tools in blender or make human[http://www.makehumancommunity.org/]. This approach may also be worth while for rendering lots of seated passengers with really simple movements - and a few walking about with a simple walk cycle. It may also be justified for large amounts of ground personnel at big airports (not just a few relevant for the users plane).

== Warnings and Limitations ==
The complexity of building a fully functional groundnet (and the time spent on it) grows exponentially with the size of the airport but very small airports, on Pacific Islands for example, pose even larger challenges. An ideal project to start with is a Metropolitan airport with one or two runways, and two dozen of parking positions.

FG Scenery and Traffic manager have their limitations and dependencies which create specific challenges of their own. For example:
[[File:AI Traffic at KJFK former Terminal 3.jpg|300px|thumb|AI Traffic sitting on top of KJFK former Terminal 3]]
* TM does not space landing aircraft. You will most likely see packs of landing aircraft hitting your runways at once, sometimes from both ends. Departures are spaced properly though
* TM does not yet use Regular/Cat III Holding points data and so you cannot force an AI aircraft to pause/hold on a route.
* TM does not support the conditional use of gates (Do not use A if B is occupied); Always assume all the Parking position you set will be occupied.
* AI Aircraft cannot "pivot" on their parking positions. The last segment on a route leading to or exiting a parking position must have the same heading than the parking position itself (Park Straight)

* Groundnets, terrain and scenery objects are independent. If you see your AI aircraft rolling on grass or sitting on buildings and for as long as your groundnet lat.lon data is correct, consider that the airport terrain/layout may be outdated or misplaced. Similarly, Building/Object may have been placed at certain Lat/Lon but since demolished (example of JFK Terminal 3 on the right) to make space for a new taxiway as airports expand and change layout regularly.

Make sure you have verified the data in your ICAO.threshold.xml before starting building your groundnet. If the data is incorrect, locate the correct one on the web and post a request for adjustment in the FlightGear AI forum with a link to the correct data source.

Your candidate groundnet will need to be tested thoroughly by running it in FG, at different time of the day as wind conditions and traffic patterns will impact which runways are used and how many AI aircraft are handled.
You should have log/debug enabled as traffic manager will create :ai entries, allowing easier troubleshooting.

On the bright side, both Taxidraw and FG Airports contain a validation tool which will allow you to detect any structural problem with your groundnet. You will also find a lot of resources and tips in the AI section of the Flightgear forums.

Finally, the approach to creating a groudnet is described below as three separate phases, each one including its own specific testing which will hopefully simplify your journey.
[[File:Gate Definition in FG Airports.png|300px|thumb|FG Airports UI for Parking Position]]
== Creating the base network ==

Objective:
* You have enough gates for all AI aircraft using the airport
* Each gate has a valid incoming and outgoing link (route) to the rest of the groundnet
* Each Runway(s) threshold has a unique link to the rest of the groundnet
* Departing Aircraft can reach any threshold, from any parking position
* Arriving Aircraft can reach any suitable parking position from any threshold

'''Step 1 : Place and configure the Parking Positions'''

Place a parking position at each location an aircraft is allowed to park. Use your AIP Lat/Lon data and/or the FGA OSM background for extra precision.
[[File:Extend Route passed Displaced THR.png|thumb|Example of route ended after a displaced Threshold]]
AI Aircraft will be positioned so their centre of rotation (main gear and/or X=0 in .ac model file) sits at the Lat/Lon defined for the parking position.

Set a type for each off your gates: GATE if the stand is used by commercial traffic or CARGO if used by freighters.
Military and General Aviation can also be used if you are running personalized traffic files on your machine.

Adjust the heading and radius for each of your gates according to the maximum wingspan the stand can accommodate. See [[aircraft radii]].
Set a unique name for the gate.
Leave the AIRLINE field empty at this point.

'''Step 2 : Place and configure the Runway accesses'''

AI aircraft need an access route to each threshold of each runway you want them to use for take off or landing. Your groundnet will need at least one route to one threshold for validation.

At this stage, place only two access route per runway, one at each end, do not create routes starting/ending hallway (to vacate the runway at midpoint).
Your access routes will be used to ‘guide’ the aircraft all the way to a final node at which point it will be ‘handed over’ to the tower, start accelerating and take off.
This final node of each access route (Take Off Point) must sit within the runway thresholds. If not, departing aircraft will simply stop and queue at the entrance of the runway. This is crucial when dealing with displaced thresholds. As a rule of thumb, your access route should end up on the white marking indicating the runway number/identification.

Backtracking: Certain airports do not have taxiways along the runway and aircraft will 'backtrack' on the runway itself to reach the threshold (often circling on a turnaround area to align for take off). In this scenario, you still need a route to guide your aircraft all the way to the take off node by placing nodes and segments on the runway and the the turnaround loop area. Make sure your loop starts (exits the runway) ahead of passing the final take off node: see an example [[:File:Using_the_runway_to_backtrack_to_the_threshold.jpg|HERE]].

Your access routes (all routes at this stage in fact) must be bi directional so they can also be used for aircraft to vacate the runway if they taxi all the way to the threshold.
[[File:Multiple Route leading to a single Threshold.png|thumb|Runway access routes must be unique]]
Your access route must be unique: Traffic manager does not handle intersections (nodes with 4 routes) very well. Your take off points should not be connected to more than one route (case of taxiways on both sides of the runway feeding a single take off point from both sides as shown on the right.

Select each of the nodes placed on the physical runway (not the ones leading to it) and mark them "On Runway" with the toggle in their properties panel

'''Step 3 : Connect ParPos and Runway Access routes to form the groundnet.'''

Link each of your parking positions and runway access routes by marking the taxiways with segments, avoiding sharp 90 degrees angles by breaking curves into 2 or 3 segments.
Keep the network as unconstrained as possible; Make all segments bi-directional, do not include any holding points (Pushback, Regular or Cat III) and do not mark any segment as pushback; At this stage, the idea is to give AI aircraft as many routing options as possible.

Nodes should be placed only at points where the aircraft will change heading so they should be none in the middle of straight routes and definitely none at taxiway crossings.

Segments starting (or ending) at a parking position must have the same heading than the parking stand. AI aircraft park straight and leave their parking straight (rolling forward or pushing back).

Your groundnet does not need to cover 100% of the airport taxiways; certain areas (like De Icing stations or Engine Test Areas) will not be used by AI aircraft. In essence draw just enough routes so that all gates and runways are connected.

'''Step 4 : Visual Check'''
Once your base groundnet complete, Check visually that your parking positions do not overlap, that nodes placed on physical runways are marked as such and that intersections are formed properly (no node unless the aircraft can turn here)

'''Step 5 : Structural Check and Test'''

Run the verification tool (available in both Taxidraw and FGAirports). Both programs will ensure at this stage that routes are valid and that nodes on runway are marked as such.
Taxidraw does not check the routes structures individually but rather that a route solution exist: If an aircraft can use different path/routes to go from its ParkPos to a given runway threshold and even if one of these routes is "broken" (unconnected segments) no error will be reported, because the aircraft could use another (unbroken) route to get to the threshold and hence still has a routing solution.

FGAirports will do the same routing check but will also signal any unconnected node (broken routes).
Correct the errors found and re run the verification tools until no more problems are found.

Time to test with 'real' traffic. Save your groundnet and export it to a custom scenery folder (NOT to the Terrasync Folder), usually something like F:\My Sceneries\Airports\S\B\SBGR.groundnet.xml.
Startup Flightgear and add your custom scenery folder path (the parent of \Airports) to your extra sceneries list in the Add On screen. Select your Airport as Startup Location. Run

What to expect (normal behaviour with base groundnet, if FG has AI traffic at the airport):
[[File:Base GRoundnet Visual Check.jpg|border|right|950px|Base Taxidraw Groundnet for SBGR]]
* Parked aircraft will start appearing on the parking stands you have set. Departing aircraft will light up (red/green nav lights on wing tips, flashing beacon on top)
* Upon ATC clearance (automatic) Departing aircraft will roll forward into the terminal buildings then dance around a bit then join a taxiway and head for a threshold. The route they will use may not be the shortest nor the one you expected but it will be a route you have set.
* Departing Aircraft will queue up at the threshold. The first in line will enter the runway, accelerate (strobes lights activate) and take off. Aircraft will climb in a straight line and after +/- 10 seconds, change heading. At this point, the next aircraft in line will enter the runway and initiate its take off
* Arriving aircraft will start landing. The touchdown position will depend on the type of aircraft. Arrivals are not spaced out and you can see more than one aircraft landing at once on a single runway. After slowing down, they will taxi all the way to the end of the runway, exit via the access route you have set then head for an available parking position. Again the route they will use may not be the shortest or the one you expected and they may not park where you wanted. Once parked, Nav Lights will turn off
* At any given intersection (4 or more segments sharing a node) and at any time during the test, one aircraft will get stuck. Aircraft following it will start queueing. The intersection will remain clogged and AI taxiing stuck until you decide to shut down Flightgear.
* Aircraft will taxi from both directions on single taxiways, eventually passing through each other
* On larger airports where AI aircraft can use more than one route to go from one point to another and/or can park at multiple aprons they will show a geographical preference (normally North West) so parking and routes in this area will be busier.
What to look for (abnormal behaviour with base groundnet, if FG has AI traffic at the airport):
* Aircraft appearing in the middle of the airport and not following taxiways (not enough Parking Positions or not suitable in size or type CARGO/GATE)
* No aircraft (no AI traffic at this airport or not activated in FG options)
* Aircraft queue up at runway but do not take off (Misplaced Threshold in ICAO.threshold.xml)

=== Refining the network: Routing Flow & Baggage Carousels Belts ===

Objective:
* All Objectives in the "Creating the base Network" section
* No clogging at intersections
* No Head on crashes of aircraft sharing a single taxiway

The traffic manager code is not fully documented nor maintained so only repeated testing (and discussions on the FG AI Forum) will allow you to form and understanding of the way AI aircraft will behave based on the type of groundnet data you feed them. This is an interesting but potentially frustrating exercise.

You will eventually realize that AI traffic has a “mind of its own” which fluctuates between two extremes:
* AI traffic cannot make decisions: Typically, where presented with multiple routing options (an X intersection with 4 or more valid routes), AI traffic will consistently freeze/clog after some time if not immediately.
* AI traffic does not stand bullying: If presented with no alternative at all (too many unidirectional routes) AI traffic will move away from your groundnet taxiways and start mowing the lawns.

[[File:Groundnet Routing Flow Example.png|border|right|950px|Groundnet Routing Flow Example]]
Keeping these two constraints in mind, the clogging and head on collisions noted in your previous tests can be addressed by setting up a ‘Routing Flow’. The purpose of said routing is to guide each aircraft to their final destination (Parking or Threshold), by ensuring it uses a single route and never crosses any other aircraft path.
To achieve this we only have and need two tools: The ability to force the direction of traffic on any given segment (by making it “unidirectional”) and the ability of Traffic manager to handle priorities and queues formation at routes merging points (Y shaped intersections).

The complexity of Routing Flow will increase exponentially with the number of gates, thresholds and traffic files handled: A single groundnet flow must accommodate indifferently a cargo flight arriving on RWY 1 in the evening or a commuter departing from RWY 2 in the morning.

To better understand how efficient routing is achieved, draw on your experience at an airport Baggage carousel (or at a ‘Sushi Train' restaurant) where all bags arrive from one or two tunnels onto a moving belt and are then distributed to passengers waiting around the carousel.
That is all bags (Aircraft) arrive from a limited number of tunnels (Thresholds) and can reach any standing passenger (ParkPos) using a single belt (routing flow). It does not matter where the passenger stands nor what order the bags arrives in; if you wait long enough all bags will meet their owner, (unless you are at Heathrow).

An advantage AI aircraft have over bags is that they can ‘transfer’ from one belt to another if a segment belongs to more than one belt/route. Putting it visually, a typical routing flow will resemble something like the image on the right : ‘Belts’ in green rotate clockwise, red ones rotate counter clockwise, segments in blue provide access in and out of the belts. The main belt along the northern runway includes bypasses allowing an aircraft to quickly reach the other side of the belt without having to travel its full length.

Using the diagram, you can pick any combination of one runway access (threshold or intermediate vacating point) and one parking position and realize you can always find a unique route from A to B and another unique route from B to A without ever coming across an intersection, always using "Y" shaped merging lanes.

[[File:Apron Belt at Bahrein Intl.png|left|thumb|Using the Belt technique to feed the OBBI apron]]
An additional benefit of the technique is visible when comparing the routing flow diagram and the base network image in the previous section: A groundnet with proper routing uses less nodes and segments than a full network, saving you time during the building phase. In fact, as you get more familiar with the technique you will realize it is a good idea to map your routing flow before building your groundnet so you create just enough nodes and segments. It is also important to know that you do NOT need to mark each and every segment as "unidirectional" but only the ones forming your Y shaped intersections.

The belt technique can easily be adjusted to the specific shape of different airports: All of KJFK’s traffic is routed with only 2 belts set as concentric rings running in opposite directions. The inner ring connects all the aprons in an infinite loop; the external ring connects all the runways in a similar loop. A small number of “transfer belts” allow aircraft to move from one belt to the other.

You can have a look at existing groundnets’ routing to better understand how this technique can be applied to your project. VVNB has the most basic version; LEMD and LFPG have very elaborate ones.

Certain smaller airports do not have enough taxiways to allow the formation of a proper global belt but the technique can be used on individual aprons to ensure proper flow in and out of parking areas and simplify the design of pushback routes (next section) as shown on the image on the left, at Bahrein Intl.

Testing : Once your routing flows in place you should re-test you groundnet. The expected behaviour is the same then the one described in the “Base Network, Step 5” section, with the exception of head on collisions and clogged intersections which should no longer exist

=== Refining the network: Pushback routes ===

'''THIS SECTION IS WIP'''
With the above-mentioned refinements, the ground network should be fully working with one notable exception. Aircraft will be driving forward when leaving the gate, making a sharp turn (while probably destroying themselves and the terminal building in the process). To prevent this, a ''push back'' route should be created. A push back route consists of at least one or more taxiway segments that have the "PushBack Route" property set to true. The last of these segments should be terminated by a PushBack HoldPoint network node. Pushback routes are optional (if you like the terminal crashing scenario described above).

'''Examples of simple valid pushback routes''' (Left: If the taxiway is bidirectional | Centre: If the taxiway is not bidirectional | Right: With shared Pushback Holding point)

[[File:MultiDirectionnal Pushback Route in Taxidraw.jpg|400px|Valid AI Groudnet pushback for multi directional taxiway]]
[[File:UniDirectionnal Pushback Route in Taxidraw.jpg|400px|Valid Pushback Route on Un directional taxiway]]
[[File:Shared Pushback Holding Point in Taxidraw.jpg|400px|Shared Pushback Holding Point]]

[[File:Roll Forward Gate in Taxidraw.jpg|thumb|Invalid Park Pos Exist route : at and angle with Parking Position]]
===== Pushback Holding Points must be unique per Parking Position =====

Each Parking space (ParkPos) can't have more than one push back route and one pushback holding point at the end of the route. Nevertheless, multiple Parkpos can share part of their pushback routes and a single Pushback Holding Point.

The formal criteria for a valid push back route is that each gate should have a maximum of one push back holding point associated with it, which can be reached using one route only.
From an editing point of view, mark all segments between your parking position and its final holding point as "push back", do not forget to mark the ending node as Pushback Holding Point.

===== The AI code does not handle sharp angles =====

Add nodes to smoothen your routes so that no consecutive segments form an angle of less than 90 degrees.
This rule applies to both pushback and roll forward / taxiways routes

===== The Inbound route and the outbound routes are parallel =====
[[File:On Taxiway Pushback Holding Point in Taxidraw.jpg|thumb|Invalid Groudnet Pushback : Holding Point on Taxiway]]

The last segment of the pushback route will condition the aircraft heading:

1. During its travel along the pushback route

2. At the Pushback Holding point (whilst waiting for clearance)

3. On departing the pushback holding point, rolling forward to the runway.

You can not control/force an AI aircraft to leave a Pushback Holding point at a different angle/heading than the one it came onto its final holding node at, whatever the number of routes you add.

As a result, the last segment of the pushback route must align with the segment you expect the aircraft to use when starting to roll forward after clearance. The simpler set up is to have this final pushback segment overlapping the first segment of the roll forward route.

Alternatively, the last segment of the pushback route can -itself- be the first segment of the roll forward route but this means Traffic Manager will consider this segment 'reserved' whilst the aircraft is pushing back and no other aircraft will be able to use the taxiway.

For the same reason the Pushback Holding point should NOT be directly placed on the taxiway as shown in the image on the right 'On Taxiway Pushback Holding Point in Taxidraw'.
Using this particular configuration, once the aircraft 'cleared for taxi', it will ignore the taxiway segments on its left and right and keep its heading, rolling forward towards the original parking position, then 'get lost' and start spinning around, looking for a node to re-anchor to.

The "Roll Forward on my current heading" rules also applies to Parking position with no pushback route. These are often used for smaller propeller aircraft which "pivot" on their parking position before rolling forward. You cannot currently replicate this pivot behaviour in Flightgear AI

It is important to note that the Taxidraw "Verify Ground network" process ''should be run'' in order to get a correctly working push back system, because this function runs some internal consistency checks. Push back routes can be very simple, from just one route segment, to fairly complex, as illustrated below with all aircraft from one side of the E terminal are being linked to one shared push back point.

Given the current push back system allows for fairly complicated behavior it is advisable to test extensively your groundnet and play with various configurations before sharing it to the community.

Taxidraw note: TaxiDraw versions prior to February 5, 2009 did export the pushBackRoute attribute correctly.

[[File:TaxiDraw2.png|thumb]]

==== Verifying the network ====
Finally, with a network complete, it is important to verify it! The verification function not only detects obvious problems with the network, it also updates some internal states that FlightGear relies on. Presumably, an automatic verification process will be added to the export function, but until that is the case, make sure to do this manually. The verify network function can be found in the "Tools" menu.

Notice that TaxiDraw does not automatically fix problems. It is left to the user to fix the problems manually. TaxiDraw does select the offending node(s) / segments(s) for easier identification. Also note that TaxiDraw stops verifying at the first problem encountered, so it is worthwhile to continue checking until no further errors are found. Currently, the following checks are performed.

* '''On runway points''' Added on January 24, 2009, this check is most likely not yet available in any distributed version. This is currently just a very lame check to see if any point in the network has been marked as such. This check is not exhaustive, but simply meant as a reminder to the editor that the OnRunway points should still be marked. Ultimately, this check should be replaced by the aforementioned automatic geometry function.
* '''Duplicate Taxiway Segments''' It's easy to connect two network nodes twice. While this doesn't really hurt, it does add dead weight, so checking for duplicates is not a bad thing.
* '''Routing''' One of the most persistent headache causing problems is that of a disconnected parking space in the network. FlightGear will happily place an aircraft there, but bail out when that aircraft cannot reach the runway. The routing check attempts to prevent this. Notice that it is of utmost importance that the OnRunway points are set correctly, because TaxiDraw relies on these points for it's route finding algorithm. Because the route finding algorithm is rather computationally intensive, some progress information is currently written to the console (a proper progress bar would be nice). When a disconnected parking space is found, TaxiDraw selects both the parking and the runway node. It is still left to the user to trace a route between these two points and find where the two pieces are disconnected.
* '''Check and set pushback nodes''' this function verifies whether any specified pushback nodes adhere to the above specifications and updates some internal consistency.

=== Copying the ground network into FlightGear's scenery directory ===
Finally, once you have finished creating a groundnet project, you can test it in FlightGear. Create a directory in your <tt>[[$FG_SCENERY]]/Airports/[I]/[C]/[A]/</tt> directory, with the three first letters of the ICAO code of your airport. For example <tt>[[$FG_SCENERY]]/Airports/E/H/A/</tt>.

In Taxidraw menu select File, Export AI Network and save the file in the above folde as ICAO.groundnet.xml. Please note that the File / Save project menu applies only to the airport layout and does NOT save your groundnet.

=== Testing the network ===
Startup FlightGear at the airport for which you have just created the network, and make sure you have traffic for that aircraft. FlightGear will check the network and report errors on the console. Aircraft that can't be placed at one of the parking locations will be placed at a default location.

If the FlightGear AI system can't find a valid route between startup location and runway, it will list which nodes are not connected and exit.

=== Airports with ground networks ===

= Runway Usage Configuration =

ICAO.rwyuse.XML dictates which runway(s) should be used for AI take off and which ones accept AI landings. These instructions are organised in multiple sets (or configurations) and ordered by preference of use.

Schedules can be defined so different runway configurations can be used at different time of the day. Different Sets can also be applied to the General Aviation and Commercial traffic.

Each set of runway configuration is tested against the wind conditions and applies only if the crosswind and tailwind are within tolerance. If not, the next set in the order of preference, will be picked.

Examples below taken from the Amsterdam Schiphol EHAM.rwyuse.xml file.

Wind conditions are stored at the beginning of the file and indicate the maximum values of Crosswind and Tailwind acceptable to authorize take off and landing at the airport.

<syntaxhighlight lang="xml">
<wind tail="7"
cross="20" />
</syntaxhighlight>

{{quote|As well as aircraft, airports have operational crosswind and tailwind limits. [] The values vary but crosswind limits are normally 15-25 kts and tailwinds are normally no more than 10 kts.|ICAO|AMOFSG/10-SN No. 14}}

The < time > table defines the hours of activation for a particular Schedule. Each schedule contains a 'Pattern' ie a fixed number of runways allocated to either take off or landing).

For instance, at EHAM, the commercial "inbound" schedule is active from 06:20 to 08h30 UTC, at a time where there is more inbound than outbound traffic and the airport needs to allocate more runways to landing than to take off.

<syntaxhighlight lang="xml">
<time start = "06:20"
end = "08:30"
schedule = "inbound"/>
</syntaxhighlight>

In most cases, a single schedule can apply 24h every day.

<syntaxhighlight lang="xml">
<time start = "00:00"
end = "24:00"
schedule = "Day"/>
</syntaxhighlight>

The different sets of runways allocation are listed in each < schedule > table by order of preference and can be read/deciphered vertically as ”columns” delimited by commas.

When wind conditions do not allow the use of a set, the next one will apply (next “column”).

Still using the EHAM.rwyuse.xml file as example, from 06:20 to 08:30 UTC, when the Inbound schedule applies; AI traffic will preferably use runway 36L for take-offs, and both 06 and 36R for landings (first “column” of data).

<syntaxhighlight lang="xml">
<schedule name="inbound">
<takeoff>36L, 24, 18L, 36L, 24, 24, 18L, 09</takeoff>
<landing>06, 18R, 18R, 36R, 27, 18R, 18R, 06</landing>
<landing>36R, 18C, 18C, 36C, 18R, 22, 22, 09</landing>
</schedule>
</syntaxhighlight>

Shall wind conditions prevent the use of this configuration (Tailwind or Crosswind values exeeding the ones defined in <wind> above), the next set (or “column”) will apply ie 24 for take-offs, and 18R + 18C for landings.

Again, if wind conditions prevent this configuration use, the next set will be used (18L for take-offs, 18R and 18C for landing).

This test of runway sets against wind values will continue with the rest of the sets in the schedule until a valid one is found and applied.

It is necessary for each of the <takeoff> and <landing> entries to have an equal number of runway values, per schedule, so each set contains the same number of runways.

[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAMbEsE46ontK4G43zmrEqLEk%3D8ZK5sQ-vxZup%3DNjpaUDgb-ASw%40mail.gmail.com/#msg37166996 Source from Durk post in Devel]

= Model Animation =

To assist with creating realistic aircraft behaviour, some properties are set by the Traffic Manager during particular flight phases as follows

{| class="wikitable"
|-
! Property !! Description !! Type !! At Gate !! Taxiing !! Take-off !! Cruise !! Approach and Landing
|-
| gear/gear[0..5]/position-norm || Gear Position || double (interpolated over 10 seconds || 1.0 || 1.0 || 0.0 (above 400ft) || 0.0 || 1.0 (below 2000ft)
|-
| surface-positions/flap-pos-norm || Flaps position || double (interpolated over 20 seconds || 0.0 || 0.0 || 0.5 (below 2000ft) || 0.0 || 1.0 ( below 2000ft)
|-
| surface-positions/spoiler-pos-norm || Spoiler position || double || 0.0 || 0.0 || 0.0 || 0.0 || 1.0 (on runway)
|-
| surface-positions/speedbrake-pos-norm || Speedbrake position || double || 0.0 || 0.0 || 0.0 || 0.0 || 1.0 (below 2000ft)
|-
| controls/lighting/beacon || Beacon || bool || false || true || true || true || true
|-
| controls/lighting/cabin-lights || Cabin lights || bool || true || true || true || false || false
|-
| controls/lighting/landing-lights || Landing lights || bool || false || false || false || true || true
|-
| controls/lighting/nav-lights || Navigation lights || bool || false || true || true || true || true
|-
| controls/lighting/strobe || Strobes || bool || false || false || true || true || true
|-
| controls/lighting/taxi-lights || Taxi lights || bool || false || true || false || false || false
|}

= SIDs / STARs =
SID is an acronym for [[Standard Instrument Departure]]. Likewise, STAR is an acronym for [[Standard Terminal Arrival Route]]. Directly after takeoff, in particular at busy airports, aircraft follow a standard flight path, that will keep them safely separated from arriving traffic, avoid ground obstructions, and also keeps traffic away from populated areas as much as possible. Currently, steps are in progress to allow FlightGear traffic to follow SIDs. Ultimately, the plan is to provide SID and STAR data in a format that can also be used by the user controlled Aircraft's Flight Management Computer. Currently, some sample data exist in the form of a PropertyList formatted XML file that contains a list of way points.

This section of the AI Traffic documentation is meant as a stub that keeps track of the current development. At the moment of writing, some proof-of-concept data for EHAM SIDs will be committed to the World Scenery Repository, along with some experimental code in FlightGear to make use of this data. Note that this data is meant to be just that; a proof-of-concept. User contributions will be accepted as soon as the format has stabilized.

= Appendix: Special Notes =

== Performance ==
With recent versions of FlightGear, we have much better performance than before so realistic density of traffic is currently possible even for slower computers. For those who are still afraid, there is an, as of yet, unpublished feature: set a new property "/sim/traffic-manager/proportion" to any value between 0 and 1 in your preferences.xml. During program start up, the traffic manager draws a random number (between 0 and 1) for each aircraft, and if that random number is smaller than the value specified in /sim/traffic-manager/proportion, the aircraft is added, otherwise it is discarded. In essence, only the specified proportion of aircraft will be loaded.

Unfortunately you can't change this at runtime yet, so you need a little bit trial and error! However, it should allow the combination of slower computers and dense traffic files.

= Related content =
* [[Airports with ground networks]]
* [[FGAirports]] - A groundnet editor
* [[Flightplan XML formats]]
* [[Status of AI in FlightGear]]

[[de:Interaktiver Verkehr]]

[[Category:AI Traffic]]
[[Category:FlightGear feature]]
[[Category:Scenery enhancement]]

Building FlightGear - Devuan

2023-08-26T20:13:27Z

Flughund: Update for Devuan Daedalus / Debian Bookworm

How-To build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Daedalus). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bookworm, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the herein used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
: On Devuan Chimaera (Debian Bullseye) packages <code>g++-9</code> and <code>gcc-9</code> are required additionally. To utilize these older versions apply environment variables to SimGear's and FlightGear's cmake commands like so: <code>CC=gcc-9 CXX=g++-9 cmake [...]</code>.
su - -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace <code>libcurl4-openssl-dev</code> by <code>libcurl4-gnutls-dev</code>.

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are <code>libplib-dev</code> and <code>libsimgear-dev</code>.
su - -c "apt-get install freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev libeudev-dev libevent-dev libfreetype6-dev libglew-dev liblzma-dev libopenal-dev libopenscenegraph-dev libqt5quick5 libqt5svg5-dev libxi-dev libxmu-dev pkg-config qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"

== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' – The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2020.3</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' – The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' – The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2020.3
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir -p $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== [[FGData|FlightGear data]] ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir -p $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_BUILD_TYPE=Release -D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Building FlightGear - Devuan

2023-05-22T02:45:37Z

Flughund: Dependencies overhaul, clone fgdata before compiling FG

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Chimaera). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bullseye, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su - -c "apt-get install cmake g++ g++-9 gcc gcc-9 git make sed"

'''Dependencies'''
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.
su - -c "apt-get install freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev \
libeudev-dev libevent-dev libfreetype6-dev libglew-dev liblzma-dev libopenal-dev \
libopenscenegraph-dev libqt5quick5 libqt5svg5-dev libxi-dev libxmu-dev pkg-config \
qtbase5-dev qtbase5-private-dev qtdeclarative5-dev qttools5-dev zlib1g-dev"




== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2020.3</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2020.3
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
CC=gcc-9 CXX=gcc-9 cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
CC=gcc-9 CXX=g++-9 cmake CFLAGS="--std=c++17" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
CC=gcc-9 CXX=g++-9 cmake CFLAGS="--std=c++17" -D CMAKE_BUILD_TYPE=Release \
-D FG_BUILD_TYPE=Release -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Building FlightGear - Devuan

2023-05-16T22:45:30Z

Flughund: Update for Devuan Chimaera

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Chimaera). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Bullseye, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su -c "apt-get install cmake g++-9 gcc-9 git make sed"

'''Dependencies'''
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.
su -c "apt-get install \
freeglut3-dev liblzma-dev pkg-config \
libboost-dev libopenal-dev qml-module-qtquick2 \
libcurl4-openssl-dev libopenscenegraph-dev qml-module-qtquick-window2 \
libdbus-1-dev libqt5opengl5-dev qtbase5-private-dev \
libevent-dev libqt5svg5-dev qtdeclarative5-private-dev \
libfreetype6-dev libxi-dev qttools5-dev \
libglew-dev libxmu-dev zlib1g-dev"



== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2020.3</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2020.3
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
CXX=g++-9 cmake CFLAGS="--std=c++17" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
CXX=g++-9 cmake CFLAGS="--std=c++17" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

FlightGear IRC channel

2023-04-24T00:57:46Z

Flughund: Removing #flightgearde from channels list due to inactivity.

{{DEFAULTSORT:IRC channel}}
The '''FlightGear IRC Network''' is an online system that will allow you to talk to a lot of people around the world and is related to everything about [[FlightGear]]. It's mostly used by developers, but it is also a good place to ask for help if you are having a question.

== Connecting to the network ==
It consists of localised servers that are all linked up to form a seamless chat network so if you are based in England you would connect to a nearby server in England and you would see exactly the same people as someone connecting to a server in the USA.

To connect to the IRCnet network you first need a suitable client. You can also use [http://www.xchat.org/ XChat] (Linux and Windows), [http://sourceforge.net/projects/xchataqua/ X-Chat Aqua] (X Chat Mac), [http://www.pidgin.im/ Pidgin], [http://colloquy.info/ Colloquy] (for Mac/iOS), [http://www.mirc.com/ mIRC], [https://Konversation.kde.org Konversation] or any other client.

When you first login to the network you must pick yourself a unique nickname for the current chat session. Nicknames can be up to 31 characters in length and contain numbers and some punctuation characters. Some examples of nicknames you can use are:

* Fred
* BIG_fred
* ^Fred^
* Fred-
* ^Fred
* fred007

It doesn't matter about capital or lower case letters in the nickname since they are treated the same when people want to contact you and there are some weird and obscure rules about nicknames such as them not being able to begin with a "-" character. Most of these rules have no rhyme nor reason to them but we didn't write the software, we just have to try and tell people how to use it. Have an experiment and see what suits you best.

Once you found your personal unique nickname you may want to register it with [[#Network_Services|NickServ]] (see below).

== Official hosts ==
{| class="wikitable"
! Host !! Location
|-
| de.irc.flightgear.org
| Germany
|-
| irc.flightgear.org
| currently an alias for de.irc.flightgear.org
|}

The '''port''' to connect to is 6667 (or 6659 for SSL) for each server.

These servers are interconnected to form the FlightGear IRC network. Please choose the host closest to you geographically.

The FlightGear IRC network has several channels, some of which are listed below. To obtain a real list, use the IRC command "/list".

{| class="wikitable"
! Channel !! Use
|-
| #flightgear
| Main channel (English)
|-
| #flightgear-blender
| [[Blender]]
|-
| #flightgearFR
| FlightGear Channel for French Speaking
|-
|#flightgearIT
|FlightGear Channel for Italian Speaking
|-
| #flightgearNL
| FlightGear Channel for Dutch Speaking
|-
|#flightgearPL
|FlightGear Channel for Polish Speaking
|-
| #fg_school
| [[FlightGear Flight Academy|Flight School]]
|-
| #fgms
| [[fgms]] related stuff
|-
| #airliners
| IFR Navigation Squawk
|-
| #fg_canteen
| Off topic community
|-
| #fg-ru
| Russian Flightgear Community
|-
| #wiki
| Wiki
|-
| #flightgear-forum
| Forum
|-
| #help
| general help on IRC
|-
| #staffers
| Server Admins
|-
| #flyingclub
| [[FlightGear Flying Club]]
|}

== Network Services ==
=== NickServ ===
NickServ allows you to "register" a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type

/msg NickServ ''COMMAND''

For more information on a specific command, type

/msg NickServ HELP ''COMMAND''

Some of the common commands are:

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a nickname.
|-
| GROUP
| Adds a nickname to your account.
|-
| IDENTIFY
| Identifies to services for a nickname.
|-
| GHOST
| Reclaims use of a nickname.
|}

This service is intended to provide a way for IRC users to ensure their identity is not compromised. It is ''not'' intended to facilitate "stealing" of nicknames or other malicious actions. Abuse of NickServ will result in, at minimum, loss of the abused nickname(s).

=== ChanServ ===
ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Some available commands are listed below; to use them, type

/msg ChanServ ''COMMAND''

For more information on a specific command, type:

/msg ChanServ HELP ''COMMAND''

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a channel.
|-
| RECOVER
| Regain control of your channel.
|-
| FLAGS
| Manipulates specific permissions on a channel.
|}

=== MemoServ ===
MemoServ is a utility allowing IRC users to send short messages to other IRC users, whether they are online at the time or not. Both the sender's nickname and the target nickname must be registered in order to send a memo.

MemoServ's commands include:

{| class="wikitable"
! Command !! Purpose
|-
| READ
| Reads a memo.
|-
| SEND
| Sends a memo to a user.
|-
| SENDGROUP
| Sends a memo to all members on a group.
|-
| SENDOPS
| Sends a memo to all ops on a channel.
|-
| DELETE
| Deletes memos.
|}

For help on any of the above commands, type:

/msg MemoServ HELP ''COMMAND''

To see a list of all available MemoServ commands, type:

/msg MemoServ HELP

=== HostServ ===
HostServ allows users to request a virtual hostname. Normally we only allow IPs to be shown on a users
connection (so no dns lookups are made upon a new connection). To hide your host to other users you are
free to select a vhost from a predefined list (or a uniquely requested one) via hostserv. In that case
your selected hostname will be shown to others instead of your real IP.

To see the list of all available commands, type:

/msg HostServ HELP

Some commands of interest are:

{| class="wikitable"
! IRC Command !! Purpose
|-
| OFFERLIST
| Lists all available vhosts.
|-
| TAKE
| Take an offered vhost for use.
|-
| REQUEST
| Requests new virtual hostname for current nick.
|}

For further help type <tt>'''/msg ''SERVICE'' help'''</tt> (replace <tt>''SERVICE''</tt> with the name of the service)

== Other hosts ==
{| class="wikitable"
! Network !! Channel !! Description
|-
| irc.freenode.net
| #flightgear
| Only for emergencies.
|}

== How to get in there with ChatZilla ==
[[File:IRC-ChatZilla.jpg|thumb|ChatZilla Client area]]
When using ChatZilla, go to your Mozilla/Firefox browser and enter [irc://mpserver12.flightgear.org irc://mpserver12.flightgear.org]. When ChatZilla has connected to the host, click "IRC" and "Join channel...". Pick the preferred channel.

To get directly to the main channel with ChatZilla, you can also enter [irc://mpserver12.flightgear.org/flightgear irc://mpserver12.flightgear.org/flightgear] in your browser.

== External links ==
* [http://www.ircbeginner.com/ General information about IRC]
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html General IRC commands]

[[Category:FlightGear]]
[[Category:Community]]

Building FlightGear - Devuan

2021-01-10T18:07:00Z

Flughund: Update liblzma

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Beowulf). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Buster, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.
su -c "apt-get install \
freeglut3-dev libopenal-dev qml-module-qtquick-window2 \
libboost-dev libopenscenegraph-3.4-dev qt5-default \
libcurl4-openssl-dev libqt5opengl5-dev qtbase5-private-dev \
libdbus-1-dev libqt5svg5-dev qtdeclarative5-private-dev \
libevent-dev libxi-dev qttools5-dev \
libfreetype6-dev libxmu-dev zlib1g-dev \
libglew-dev pkg-config \
liblzma-dev qml-module-qtquick2"



== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2019.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2020.3
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Building FlightGear - Devuan

2020-08-26T22:43:23Z

Flughund: add missing slash "/"

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Beowulf). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Buster, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
su -c "apt-get install \
freeglut3-dev libopenal-dev qml-module-qtquick2 \
libboost-dev libopenscenegraph-3.4-dev qml-module-qtquick-window2 \
libcurl4-openssl-dev libqt5opengl5-dev qt5-default \
libdbus-1-dev libqt5svg5-dev qtbase5-private-dev \
libevent-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev pkg-config"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.


== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2019.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2020.2
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Building FlightGear - Devuan

2020-08-05T07:34:00Z

Flughund: 2019.1 --> 2020.2

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Beowulf). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Buster, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
su -c "apt-get install \
freeglut3-dev libopenal-dev qml-module-qtquick2 \
libboost-dev libopenscenegraph-3.4-dev qml-module-qtquick-window2 \
libcurl4-openssl-dev libqt5opengl5-dev qt5-default \
libdbus-1-dev libqt5svg5-dev qtbase5-private-dev \
libevent-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev pkg-config"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.


== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2019.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2020.2
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Building FlightGear - Devuan

2020-03-24T13:22:49Z

Flughund: Added missing libevent-dev for swift.

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Beowulf). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Buster, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
su -c "apt-get install \
freeglut3-dev libopenal-dev qml-module-qtquick2 \
libboost-dev libopenscenegraph-3.4-dev qml-module-qtquick-window2 \
libcurl4-openssl-dev libqt5opengl5-dev qt5-default \
libdbus-1-dev libqt5svg5-dev qtbase5-private-dev \
libevent-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev pkg-config"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.


== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2019.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2019.1
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Building FlightGear - Devuan

2020-03-23T19:52:29Z

Flughund: Update to Beowulf/Buster

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (Beowulf). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Buster, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
su -c "apt-get install \
freeglut3-dev qml-module-qtquick-window2 \
libboost-dev libqt5opengl5-dev qt5-default \
libcurl4-openssl-dev libqt5svg5-dev qtbase5-private-dev \
libdbus-1-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev libopenal-dev libopenscenegraph-3.4-dev \
pkg-config qml-module-qtquick2"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.


== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2019.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2019.1
export FG_SRC_DIR=$HOME/src/
export FG_INSTALL_DIR=$HOME/FlightGear
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Default head-up display

2020-02-27T18:47:03Z

Flughund: Removed links due to missing targets.

{{Note|The HUD system will one day be replaced by a [[Canvas HUD]] system.}}

The {{Wikipedia|Head-up display|'''Head-up display'''}} (HUD) is an important instrument in modern, mostly military, cockpits. FlightGear provides a XML-based system to relatively easily create HUDs for aircraft such as the [[F-14B]] and [[F-16]].

However, this article's focus is on FlightGear's default head-up displays. Those are available for any craft which does not include its own set. Have a look at [[#Further Information|Further Information]] if you're planning to create a HUD.

Activate the HUD with {{key press|h}}. Pressing it repeatedly moves through the configured colours and turns it off again. To change the brightness, press {{key press|Shift|h}}. Press {{key press|Shift|i}} to go through the available HUDs. Press {{key press|i}} to switch back to the first one at any time. Have in mind that some aircraft do assign one or more of those keys differently and therefore one or more function/s is/are missing on them.

Some of the head-up display's options can be altered in the menu: <code>View → Adjust HUD Properties</code>

[[File:HUD_default_overview.png|thumb|420px|Huds/default.xml]]
[[File:HUD_minimal_overview.png|thumb|420px|Huds/minimal.xml]]
[[File:HUD_NTPS_overview.png|thumb|420px|Huds/NTPS.xml]]

== Features ==
=== Control inputs ===
; [[Aileron]]
: Monitors the bearing of the control input on the aileron's axis. Attached along the upper side is the indicator for the trim input on that axis.
: Properties: <code>/controls/flight/aileron</code> and <code>/controls/flight/aileron-trim</code>

; [[Elevator]]
: Monitors the bearing of the control input on the elevator's axis. Attached to the left the trim on this axis.
: Properties: <code>/controls/flight/elevator</code> and <code>/controls/flight/elevator-trim</code>

; [[Rudder]]
: Monitors the bearing of the control input on the rudder's axis. Attached to the bottom the trim input.
: Properties: <code>/controls/flight/rudder</code> and <code>/controls/flight/rudder-trim</code>

; Throttle
: Monitors the throttle input axis.
: Property: <code>/controls/engines/engine/throttle</code>

=== Instruments ===
; [[AMSL]] (Height above mean sea level)
: Current altitude relative to sea level in feet (ft) (1 ft = 30.48 cm).
: Property: <code>/position/altitude-ft</code>

; g-load
: The {{Wikipedia|G-force}} appealing to the pilot - to avoid black-/redout.
: Property: <code>/accelerations/pilot/z-accel-fps_sec</code> with factor <tt>-0.03108095</tt>

; [[Avionics and Instruments#DirectionalGyro|Gyrocompass]]
: This is an ideal version of a gyrocompass without the drawbacks of a real one. It shows heading of the aircraft relative to the geographical North Pole (true north) in degree (360 degree scale).
: Property: <code>/orientation/heading-deg</code>

; [[KIAS]] ('''K'''nots '''I'''ndicated '''A'''ir'''s'''peed)
: Current speed relating to the ambient air in knot/knots (kt/kts) (1 kt = 1.151 mph = 1.852 km/h).
: Property: <code>/velocities/airspeed-kt</code>

; Latitude / Longitude
: Current location according to the {{Wikipedia|geographic coordinate system}}.
: To change the format of the displayed coordinates, go to <tt>Autopilot</tt> --> <tt>Set Lat/Lon-format</tt>.
: Properties: <code>/position/latitude-string</code> and <code>/position/longitude-string</code>

; Pitch ladder
: Displays the aircraft's pitch and roll relative to the ground's level/horizontal in degree. It's used as an artificial horizon ([[Avionics and Instruments#Attitude Indicator|Attitude indicator]]).
: Properties: <code>/orientation/roll-deg</code> and <code>/orientation/pitch-deg</code>

; Radio altimeter
: Shows current altitude [[above ground level]] (AGL) in feet. Relating to the location of the aircraft's radio altimeter, it's not zero if the aircraft is on the ground.
: Property: <code>/position/altitude-agl-ft</code>

; Turn-bank-indicator
: [[Avionics and Instruments#Turn Coordinator|Turn Coordinator]]
: Properties: <code>/orientation/roll-deg</code> and <code>/orientation/side-slip-deg</code>

[[File:HUD_default_autopilot.jpg|thumb|420px|HUD autopilot]]
=== [[Autopilot]] ===
If the autopilot is active the HUD displays its settings. For each active function (heading, altitude and speed) a box will appear below the gyrocompass containing information on its mode and, if existent, the associated value.
; Heading control
: Whether it is active or not and on which mode it operates is determined by the content of the <code>/autopilot/locks/heading</code> property.
: The values are taken from <code>/autopilot/settings/heading-bug-deg</code> and <code>/autopilot/settings/true-heading-deg</code>.

; Altitude control
: Active mode: <code>/autopilot/locks/altitude</code>
: Their values: <code>/autopilot/settings/target-altitude-ft</code>, <code>/autopilot/settings/vertical-speed-fpm</code> and <code>/autopilot/settings/target-agl-ft</code>.

; Speed control
: Active mode: <code>/autopilot/locks/speed</code>
: Their values: <code>/autopilot/settings/target-speed-kt</code> and <code>/autopilot/settings/target-speed-mach</code>

[[File:HUD_default_gps.jpg|thumb|420px|HUD GPS]]
=== [[GPS]] ===
The upper left hand corner shows the most important information on the actual state of the GPS. Namely these are (line by line):
: the mode the GPS operates in and the active waypoint's identifier.
: the distance "D" (in nautical miles, nm) and the calculated time to this waypoint "TTW".
: the bearing "BRG" to the active waypoint and the course deviation "XTR" based on the leg from the previous waypoint.
: the current speed relative to the ground "GS".

=== Big fat arrow ===
Remains of a going to be useful instrument.
: To get rid of it, remove or comment "runway.xml" from/in <tt>$FG_ROOT/Huds/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Huds/default.xml;hb=HEAD default.xml]</tt>.
: To make it point to the airport selected by menu item "Tower Position", apply patches as shown [http://sourceforge.net/mailarchive/message.php?msg_id=30422572 here].

== Further Information ==
HUDs may be replaced or added by changing or adding their paths in <tt>preferences.xml</tt> or by setting the paths as command line options. To change the order of the existing ones the options would be: <code>--prop:/sim/hud/path[1]=Huds/minimal.xml</code> <code>--prop:/sim/hud/path[2]=Huds/default.xml</code>

If you consider to create your own HUD have a look at [[Canvas HUD]] first.

The basic settings regarding to any HUD are set in <tt>$FG_ROOT/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=preferences.xml;hb=HEAD preferences.xml]</tt>. Search the file for the <tt><hud></tt>-tag and you will find a list of properties.

The setup of the default HUD is defined at <tt>[[$FG_ROOT]]/Huds/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Huds/default.xml;hb=HEAD default.xml]</tt> and documentation can be found at <tt>$FG_ROOT/Docs/[https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.hud README.hud]</tt>.

== Additional HUDs ==
; [http://wiki.beggabaur.rocks/ya/HeliHUD HeliHUD]
: Designed to fly helicopters in Helicopter View it is also handy for any craft with a not yet finished cockpit. It also contains a minimalistic HUD only showing some navigational information such as compass and GPS. The [http://beggabaur.rocks/fgfs/helihud_0.3.tar.bz2 download] contains instructions and specs.

[[Category:FlightGear feature]]
[[Category:Menubar]]

Building FlightGear - Devuan

2019-11-08T10:46:07Z

Flughund: Complete overhaul; new system for handling FlightGear versions; updated for 2019.1

HowTo build [[FlightGear]] on [https://devuan.org/ Devuan] GNU/Linux Stable (ASCII). Instructions probably apply to [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, ''checklist'' like, overview of the specific steps to compile FlightGear and components on Devuan. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

'''Tools'''
su -c "apt-get install cmake g++ gcc git make sed"

'''Dependencies'''
su -c "apt-get install \
freeglut3-dev qml-module-qtquick-window2 \
libboost-dev libqt5opengl5-dev qt5-default \
libcurl4-openssl-dev libqt5svg5-dev qtbase5-private-dev \
libdbus-1-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev libopenal-dev libopenscenegraph-3.4-dev \
pkg-config qml-module-qtquick2"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are libplib-dev and simgear-dev.


== Build and install ==
Some things require customisation. We'll use [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash environment variables] for them: 
: '''FG_VERSION''' - The version of FlightGear to build and install. This is either <code>next</code> (for the bleeding edge development branch) or a release number in the form <code>release/2019.1</code>. For a list of valid releases see [https://sourceforge.net/p/flightgear/flightgear/ref/next/branches/ here]. 
: '''FG_SRC_DIR''' - The absolute path to the directory which is supposed to hold the source codes. In case your user belongs to the group ''staff'', <code>/usr/local/src/</code> would be an appropriate location. But any location is fine, too, e.g. <code>$HOME/src/</code>. In any case the user has to have write access there. 
: '''FG_INSTALL_DIR''' - The absolute path to where FlightGear is going to be installed. Again, <code>/usr/local/</code> is appropriate, if your user belongs to ''staff''. But any location where the user has write access is ok, e.g. <code>$HOME/FlightGear/</code>. 

# Examples, adapt to your own needs:
export FG_VERSION=release/2019.1
export FG_SRC_DIR=/usr/local/src/
export FG_INSTALL_DIR=/usr/local/
: Remember to export these variables in each console you use in the process.
From here on it should™ be possible to just copy and paste the entire content of each code box at once into the console.
# Create specified directories if they do not exist:
mkdir -p $FG_SRC_DIR
mkdir -p $FG_INSTALL_DIR

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix versions for SimGear, FlighGear and fgdata! Mixing versions will almost certainly break the installation.

=== [[plib]] ===
While just installing package libplib-dev should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case libplib-dev ''must not'' be installed during the installation process of Simgear and Flightgear!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc)
make install



=== [[SimGear]] ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>
cd simgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc)
make install


=== FlightGear source ===
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>
cd flightgear.git
git checkout $FG_VERSION
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc)
make install


=== FlightGear data ===
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>
cd fgdata
git checkout $FG_VERSION

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run. In case your FG_INSTALL_DIR is <code>/usr/local/</code>, just run <code>fgfs --launcher</code>.

In case it's anywhere else on the system, things are a tad more complicated:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.
: Since [http://www.linfo.org/path_env_var.html $PATH] most likely does not cover the FG_INSTALL_DIR the full path to the fgfs binary is required to run it.
: Even though it's a tad more laborious than installing it to <code>/usr/local/</code>, this approach has the advantage of easlily managing several FlightGear installations.

To make it permanent and less complicated one option would be to create an alias:
echo -e "alias flightgear='LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib\
$FG_INSTALL_DIR/bin/fgfs --launcher' \n" >> $HOME/.bashrc
source $HOME/.bashrc
: Now running <code>flightgear</code> will start the simulator.

To keep the source code git repos up to date have a look at our [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section.

Please report issues or any kind of feedback to the [[Talk:Building_FlightGear_-_Devuan|talk page]].

== Uninstalling ==
To uninstall Flightgear and its components from e.g. <code>/usr/local/</code>, run <code>make uninstall</code> inside each software's build directory:
cd $FG_SRC_DIR/build-fg && make uninstall
cd $FG_SRC_DIR/build-sg && make uninstall
cd $FG_SRC_DIR/build-plib && make uninstall
rm -R $FG_INSTALL_DIR/share/fgdata


{{Building}}

Building FlightGear - Devuan

2019-02-05T12:41:46Z

Flughund: Update for 2018.3.2 (OSG v3.4.1)

HowTo build [[FlightGear]] Stable ([[Changelog_2018.3|2018.3]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (ASCII). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libopenscenegraph-dev qml-module-qtquick-window2 \
libboost-dev libqt5opengl5-dev qt5-default \
libcurl4-openssl-dev libqt5svg5-dev qtbase5-private-dev \
libdbus-1-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev pkg-config \
libopenal-dev qml-module-qtquick2"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev", "libopenscenegraph-3.4-dev", "libopenscenegraph-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case "libplib-dev" ''must not'' be installed!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[OpenSceneGraph]] ===
Stable and Next: 
Recommended version is 3.4.1 while the Devuan/Debian repo provides only 3.4.0. Plus, at this time, SimGear does not compile against 3.4.0 so we have to compile it ourselfes.

cd $FG_SRC_DIR
<nowiki>git clone --branch OpenSceneGraph-3.4.1 git://github.com/openscenegraph/OpenSceneGraph.git OpenSceneGraph.git</nowiki>
mkdir $FG_SRC_DIR/build-osg && cd $FG_SRC_DIR/build-osg
cmake -D LIB_POSTFIX="" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/OpenSceneGraph.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.3

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Building FlightGear - Devuan

2018-12-16T02:50:15Z

Flughund: note about libplib-dev

HowTo build [[FlightGear]] Stable ([[Changelog_2018.3|2018.3]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (ASCII). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libopenscenegraph-dev qml-module-qtquick-window2 \
libboost-dev libqt5opengl5-dev qt5-default \
libcurl4-openssl-dev libqt5svg5-dev qtbase5-private-dev \
libdbus-1-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev pkg-config \
libopenal-dev qml-module-qtquick2"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source. In this case "libplib-dev" ''must not'' be installed!
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.3

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Building FlightGear - Devuan

2018-10-30T18:34:28Z

Flughund: download_and_compile.sh no worky on debian, hence removing the link

HowTo build [[FlightGear]] Stable ([[Changelog_2018.3|2018.3]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (ASCII). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libopenscenegraph-dev qml-module-qtquick-window2 \
libboost-dev libqt5opengl5-dev qt5-default \
libcurl4-openssl-dev libqt5svg5-dev qtbase5-private-dev \
libdbus-1-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev pkg-config \
libopenal-dev qml-module-qtquick2"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.3

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Template:Building

2018-10-15T00:18:13Z

Flughund: Added Devuan

{{Navbox
| name = Building
| title = Building/Compiling
| listclass = hlist

| group1 = FlightGear
| list1 =
* [[Building Flightgear|Flightgear]] ([[Building_Flightgear_-_Debian|Debian]]/[[Building_FlightGear_-_Devuan|Devuan]]/[[Building_Flightgear_-_Gentoo|Gentoo]]/[[Building_FlightGear_-_Linux|Linux]]/[[Ubuntu]]/[[Building using CMake - Windows|Windows]])
* [[Howto: Build FlightGear with NetBeans using CMake|FlightGear with NetBeans using CMake]]
* [[Building FlightGear - Cross Compiling]]
| group2 = TerraGear
| list2 =
* [[Building Terragear|TerraGear]] ([[Building terragear-cs in Ubuntu 64|Ubuntu 64]])

| group3 = Related
| list3 =
* [[Tools of the Trade]]
* [[OpenSceneGraph]]
* [[FlightGear Git]]
}}<includeonly>{{main other|[[Category:Building from source]]}}</includeonly><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This template can be used at the bottom of articles describing how to build FlightGear and related software from source.

Adding this template to a page in the main (article) namespace will automatically add [[:Category:Building from source]] to that page.

== Usage ==
Place the template at the bottom of the articles, just before the category and language links.
<nowiki>{{building}}</nowiki>

}}

[[Category:Navigation templates]]
</noinclude>

Building FlightGear - Devuan

2018-10-15T00:13:11Z

Flughund: update for 2018.3

HowTo build [[FlightGear]] Stable ([[Changelog_2018.3|2018.3]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (ASCII). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libopenscenegraph-dev qml-module-qtquick-window2 \
libboost-dev libqt5opengl5-dev qt5-default \
libcurl4-openssl-dev libqt5svg5-dev qtbase5-private-dev \
libdbus-1-dev libxi-dev qtdeclarative5-private-dev \
libfreetype6-dev libxmu-dev qttools5-dev \
libglew-dev pkg-config \
libopenal-dev qml-module-qtquick2"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.3

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D CMAKE_BUILD_TYPE=Release \
-D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.3

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Building FlightGear - Devuan

2018-07-07T23:51:53Z

Flughund: update on dependencies: libqt5svg5-dev

HowTo build [[FlightGear]] Stable ([[Changelog_2018.2|2018.2]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (Ascii). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev \
libfreetype6-dev libglew-dev libopenal-dev libopenscenegraph-dev \
libqt5opengl5-dev libqt5svg5-dev libxi-dev libxmu-dev \
pkg-config qml-module-qtquick2 qml-module-qtquick-window2 \
qt5-default qtbase5-private-dev qtdeclarative5-private-dev"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.2

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" \
$FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.2

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.2

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Building FlightGear - Devuan

2018-05-23T23:17:39Z

Flughund: update for 2018.2

HowTo build [[FlightGear]] Stable ([[Changelog_2018.2|2018.2]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (Ascii). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev \
libfreetype6-dev libglew-dev libopenal-dev libopenscenegraph-dev \
libqt5opengl5-dev libxi-dev libxmu-dev pkg-config \
qml-module-qtquick2 qml-module-qtquick-window2 \
qt5-default qtbase5-private-dev qtdeclarative5-private-dev"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.2

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" \
$FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.2

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.2

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Building FlightGear - Devuan

2018-04-27T14:38:09Z

Flughund: update dependencies (for qt-launcher)

HowTo build [[FlightGear]] Stable ([[Changelog_2018.1|2018.1]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (Ascii). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev \
libfreetype6-dev libglew-dev libopenal-dev libopenscenegraph-dev \
libqt5opengl5-dev libxi-dev libxmu-dev pkg-config \
qml-module-qtquick2 qml-module-qtquick-window2 \
qt5-default qtbase5-private-dev qtdeclarative5-private-dev"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.1

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" \
$FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.1

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.1

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Building FlightGear - Devuan

2018-04-05T23:11:35Z

Flughund: Update for FG 2018.1 and to Devuan Ascii

HowTo build [[FlightGear]] Stable ([[Changelog_2018.1|2018.1]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | Next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (Ascii). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probably apply on [https://debian.org/ Debian] GNU/Linux Stretch, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands will cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install cmake g++ gcc git make sed"

; Dependencies
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev \
libfreetype6-dev libglew-dev libopenal-dev libopenscenegraph-dev \
libqt5opengl5-dev libxi-dev libxmu-dev pkg-config \
qt5-default qtbase5-private-dev qtdeclarative5-private-dev"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev".

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for Stable and Next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and Next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2018.1

Stable and Next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" \
$FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and Next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2018.1

Stable and Next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/share/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable and Next:
mkdir -p $FG_INSTALL_DIR/share && cd $FG_INSTALL_DIR/share
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

Stable only:
cd fgdata
git checkout release/2018.1

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

{{Building}}

Default head-up display

2018-01-15T09:40:27Z

Flughund: Typo, removed "'" from "HUD's"

{{Note|The HUD system will one day be replaced by a [[Canvas HUD]] system.}}

The {{Wikipedia|Head-up display|'''Head-up display'''}} (HUD) is an important instrument in modern, mostly military, cockpits. FlightGear provides a XML-based system to relatively easily create HUDs for aircraft such as the [[F-14B]] and [[F-16]].

However, this article's focus is on FlightGear's default head-up displays. Those are available for any craft which does not include its own set. Have a look at [[#Further Information|Further Information]] if you're planning to create a HUD.

Activate the HUD with {{key press|h}}. Pressing it repeatedly moves through the configured colours and turns it off again. To change the brightness, press {{key press|Shift|h}}. Press {{key press|Shift|i}} to go through the available HUDs. Press {{key press|i}} to switch back to the first one at any time. Have in mind that some aircraft do assign one or more of those keys differently and therefore one or more function/s is/are missing on them.

Some of the head-up display's options can be altered in the menu: <code>View → Adjust HUD Properties</code>

[[File:HUD_default_overview.png|thumb|420px|Huds/default.xml]]
[[File:HUD_minimal_overview.png|thumb|420px|Huds/minimal.xml]]
[[File:HUD_NTPS_overview.png|thumb|420px|Huds/NTPS.xml]]

== Features ==
=== Control inputs ===
; [[Aileron]]
: Monitors the bearing of the control input on the aileron's axis. Attached along the upper side is the indicator for the trim input on that axis.
: Properties: <code>/controls/flight/aileron</code> and <code>/controls/flight/aileron-trim</code>

; [[Elevator]]
: Monitors the bearing of the control input on the elevator's axis. Attached to the left the trim on this axis.
: Properties: <code>/controls/flight/elevator</code> and <code>/controls/flight/elevator-trim</code>

; [[Rudder]]
: Monitors the bearing of the control input on the rudder's axis. Attached to the bottom the trim input.
: Properties: <code>/controls/flight/rudder</code> and <code>/controls/flight/rudder-trim</code>

; Throttle
: Monitors the throttle input axis.
: Property: <code>/controls/engines/engine/throttle</code>

=== Instruments ===
; [[AMSL]] (Height above mean sea level)
: Current altitude relative to sea level in feet (ft) (1 ft = 30.48 cm).
: Property: <code>/position/altitude-ft</code>

; g-load
: The {{Wikipedia|G-force}} appealing to the pilot - to avoid black-/redout.
: Property: <code>/accelerations/pilot/z-accel-fps_sec</code> with factor <tt>-0.03108095</tt>

; [[Avionics and Instruments#DirectionalGyro|Gyrocompass]]
: This is an ideal version of a gyrocompass without the drawbacks of a real one. It shows heading of the aircraft relative to the geographical North Pole (true north) in degree (360 degree scale).
: Property: <code>/orientation/heading-deg</code>

; [[KIAS]] ('''K'''nots '''I'''ndicated '''A'''ir'''s'''peed)
: Current speed relating to the ambient air in knot/knots (kt/kts) (1 kt = 1.151 mph = 1.852 km/h).
: Property: <code>/velocities/airspeed-kt</code>

; Latitude / Longitude
: Current location according to the {{Wikipedia|geographic coordinate system}}.
: To change the format of the displayed coordinates, go to <tt>Autopilot</tt> --> <tt>Set Lat/Lon-format</tt>.
: Properties: <code>/position/latitude-string</code> and <code>/position/longitude-string</code>

; Pitch ladder
: Displays the aircraft's pitch and roll relative to the ground's level/horizontal in degree. It's used as an artificial horizon ([[Avionics and Instruments#Attitude Indicator|Attitude indicator]]).
: Properties: <code>/orientation/roll-deg</code> and <code>/orientation/pitch-deg</code>

; Radio altimeter
: Shows current altitude [[above ground level]] (AGL) in feet. Relating to the location of the aircraft's radio altimeter, it's not zero if the aircraft is on the ground.
: Property: <code>/position/altitude-agl-ft</code>

; Turn-bank-indicator
: [[Avionics and Instruments#Turn Coordinator|Turn Coordinator]]
: Properties: <code>/orientation/roll-deg</code> and <code>/orientation/side-slip-deg</code>

[[File:HUD_default_autopilot.jpg|thumb|420px|HUD autopilot]]
=== [[Autopilot]] ===
If the autopilot is active the HUD displays its settings. For each active function (heading, altitude and speed) a box will appear below the gyrocompass containing information on its mode and, if existent, the associated value.
; Heading control
: Whether it is active or not and on which mode it operates is determined by the content of the <code>/autopilot/locks/heading</code> property.
: The values are taken from <code>/autopilot/settings/heading-bug-deg</code> and <code>/autopilot/settings/true-heading-deg</code>.

; Altitude control
: Active mode: <code>/autopilot/locks/altitude</code>
: Their values: <code>/autopilot/settings/target-altitude-ft</code>, <code>/autopilot/settings/vertical-speed-fpm</code> and <code>/autopilot/settings/target-agl-ft</code>.

; Speed control
: Active mode: <code>/autopilot/locks/speed</code>
: Their values: <code>/autopilot/settings/target-speed-kt</code> and <code>/autopilot/settings/target-speed-mach</code>

[[File:HUD_default_gps.jpg|thumb|420px|HUD GPS]]
=== [[GPS]] ===
The upper left hand corner shows the most important information on the actual state of the GPS. Namely these are (line by line):
: the mode the GPS operates in and the active waypoint's identifier.
: the distance "D" (in nautical miles, nm) and the calculated time to this waypoint "TTW".
: the bearing "BRG" to the active waypoint and the course deviation "XTR" based on the leg from the previous waypoint.
: the current speed relative to the ground "GS".

=== Big fat arrow ===
Remains of a going to be useful instrument.
: To get rid of it, remove or comment "runway.xml" from/in <tt>$FG_ROOT/Huds/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Huds/default.xml;hb=HEAD default.xml]</tt>.
: To make it point to the airport selected by menu item "Tower Position", apply patches as shown [http://sourceforge.net/mailarchive/message.php?msg_id=30422572 here].

== Further Information ==
HUDs may be replaced or added by changing or adding their paths in <tt>preferences.xml</tt> or by setting the paths as command line options. To change the order of the existing ones the options would be: <code>--prop:/sim/hud/path[1]=Huds/minimal.xml</code> <code>--prop:/sim/hud/path[2]=Huds/default.xml</code>

If you consider to create your own HUD have a look at [[Canvas HUD]] first.

The basic settings regarding to any HUD are set in <tt>$FG_ROOT/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=preferences.xml;hb=HEAD preferences.xml]</tt>. Search the file for the <tt><hud></tt>-tag and you will find a list of properties.

The setup of the default HUD is defined at <tt>[[$FG_ROOT]]/Huds/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Huds/default.xml;hb=HEAD default.xml]</tt> and documentation can be found at <tt>$FG_ROOT/Docs/[https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.hud README.hud]</tt>.

== Additional HUDs ==
; Generic helicopter HUD
: This is a generic HUD for helicopters, inspired by MIL-STD 1295A and the AH-64A IHADSS symbology. [http://stefan.gofferje.net/downloads/flightgear/file/6-generic-helicopter-hud Download]

; HeliHUD
: Designed to fly helicopters in Helicopter View it is also handy for any craft with a not yet finished cockpit. It also contains a minimalistic HUD only showing some navigational information such as compass and GPS. The [http://beggabaur.rocks/fgfs/helihud_0.3.tar.bz2 download] contains instructions and specs.

; V(MX)-22 Osprey HUD
: [http://stefan.gofferje.net/downloads/flightgear/file/1-hud-for-vmx-22-osprey Download]

[[Category:FlightGear feature]]
[[Category:Menubar]]

FlightGear IRC channel

2017-10-28T21:14:38Z

Flughund: bring list of hosts up to date

The '''FlightGear IRC Network''' is an online system that will allow you to talk to a lot of people around the world and is related to everything about [[FlightGear]]. It's mostly used by developers, but it is also a good place to ask for help if you are having a question.

== Connecting to the network ==
It consists of localised servers that are all linked up to form a seamless chat network so if you are based in England you would connect to a nearby server in England and you would see exactly the same people as someone connecting to a server in the USA.

To connect to the IRCnet network you first need a suitable client. For users of Mozilla browsers (like Firefox), the plugin [https://addons.mozilla.org/en/firefox/addon/16 ChatZilla] is surely a good option. You can also use [http://www.xchat.org/ XChat] (Linux and Windows), [http://sourceforge.net/projects/xchataqua/ X-Chat Aqua] (X Chat Mac), [http://www.silverex.org/ SilverEx] (X Chat windows Free Build), [http://www.pidgin.im/ Pidgin], [http://colloquy.info/ Colloquy] (for Mac), [http://www.mirc.com/ mIRC] or any other client.

When you first login to the network you must pick yourself a unique nickname for the current chat session. Nicknames can be up to 31 characters in length and contain numbers and some punctuation characters. Some examples of nicknames you can use are:

* Fred
* BIG_fred
* ^Fred^
* Fred-
* ^Fred
* fred007

It doesn't matter about capital or lower case letters in the nickname since they are treated the same when people want to contact you and there are some weird and obscure rules about nicknames such as them not being able to begin with a "-" character. Most of these rules have no rhyme nor reason to them but we didn't write the software, we just have to try and tell people how to use it. Have an experiment and see what suits you best.

Once you found your personal unique nickname you may want to register it with [[#Network_Services|NickServ]] (see below).

== Official hosts ==
{| class="wikitable"
! Host !! Location
|-
| de.irc.flightgear.org
| Germany
|-
| irc.flightgear.org
| currently an alias for de.irc.flightgear.org
|}

The '''port''' to connect to is 6667 (or 6659 for SSL) for each server.

These servers are interconnected to form the FlightGear IRC network. Please choose the host closest to you geographically.

The FlightGear IRC network has several channels, some of which are listed below. To obtain a real list, use the IRC command "/list".

{| class="wikitable"
! Channel !! Use
|-
| #flightgear
| Main channel (English)
|-
| #flightgear-blender
| [[Blender]]
|-
| #flightgearDE
| Deutschsprachiger FlightGear-Kanal (German-speaking channel)
|-
| #flightgearFR
| FlightGear Channel for French Speaking
|-
| #flightgearNL
| FlightGear Channel for Dutch Speaking
|-
| #fg_school
| [[FlightGear Flight Academy|Flight School]]
|-
| #fgms
| [[fgms]] related stuff
|-
| #airliners
| IFR Navigation Squawk
|-
| #fg_canteen
| Off topic community
|-
| #fg-ru
| Russian Flightgear Community
|-
| #wiki
| Wiki
|-
| #flightgear-forum
| Forum
|-
| #help
| general help on IRC
|-
| #staffers
| Server Admins
|-
| #flyingclub
| [[FlightGear Flying Club]]
|}

== Network Services ==
=== NickServ ===
NickServ allows you to "register" a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type

/msg NickServ ''COMMAND''

For more information on a specific command, type

/msg NickServ HELP ''COMMAND''

Some of the common commands are:

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a nickname.
|-
| GROUP
| Adds a nickname to your account.
|-
| IDENTIFY
| Identifies to services for a nickname.
|-
| GHOST
| Reclaims use of a nickname.
|}

This service is intended to provide a way for IRC users to ensure their identity is not compromised. It is ''not'' intended to facilitate "stealing" of nicknames or other malicious actions. Abuse of NickServ will result in, at minimum, loss of the abused nickname(s).

=== ChanServ ===
ChanServ allows you to register and control various aspects of channels. ChanServ can often prevent malicious users from "taking over" channels by limiting who is allowed channel operator privileges. Some available commands are listed below; to use them, type

/msg ChanServ ''COMMAND''

For more information on a specific command, type:

/msg ChanServ HELP ''COMMAND''

{| class="wikitable"
! Command !! Purpose
|-
| REGISTER
| Registers a channel.
|-
| RECOVER
| Regain control of your channel.
|-
| FLAGS
| Manipulates specific permissions on a channel.
|}

=== MemoServ ===
MemoServ is a utility allowing IRC users to send short messages to other IRC users, whether they are online at the time or not. Both the sender's nickname and the target nickname must be registered in order to send a memo.

MemoServ's commands include:

{| class="wikitable"
! Command !! Purpose
|-
| READ
| Reads a memo.
|-
| SEND
| Sends a memo to a user.
|-
| SENDGROUP
| Sends a memo to all members on a group.
|-
| SENDOPS
| Sends a memo to all ops on a channel.
|-
| DELETE
| Deletes memos.
|}

For help on any of the above commands, type:

/msg MemoServ HELP ''COMMAND''

To see a list of all available MemoServ commands, type:

/msg MemoServ HELP

=== HostServ ===
HostServ allows users to request a virtual hostname. Normally we only allow IPs to be shown on a users
connection (so no dns lookups are made upon a new connection). To hide your host to other users you are
free to select a vhost from a predefined list (or a uniquely requested one) via hostserv. In that case
your selected hostname will be shown to others instead of your real IP.

To see the list of all available commands, type:

/msg HostServ HELP

Some commands of interest are:

{| class="wikitable"
! IRC Command !! Purpose
|-
| OFFERLIST
| Lists all available vhosts.
|-
| TAKE
| Take an offered vhost for use.
|-
| REQUEST
| Requests new virtual hostname for current nick.
|}

For further help type <tt>'''/msg ''SERVICE'' help'''</tt> (replace <tt>''SERVICE''</tt> with the name of the service)

== Other hosts ==
{| class="wikitable"
! Network !! Channel !! Description
|-
| irc.freenode.net
| #flightgear
| Only for emergencies.
|}

== How to get in there with ChatZilla ==
[[File:IRC-ChatZilla.jpg|thumb|ChatZilla Client area]]
When using ChatZilla, go to your Mozilla/Firefox browser and enter [irc://mpserver12.flightgear.org irc://mpserver12.flightgear.org]. When ChatZilla has connected to the host, click "IRC" and "Join channel...". Pick the preferred channel.

To get directly to the main channel with ChatZilla, you can also enter [irc://mpserver12.flightgear.org/flightgear irc://mpserver12.flightgear.org/flightgear] in your browser.

== External links ==
* [http://www.ircbeginner.com/ General information about IRC]
* [http://www.ircbeginner.com/ircinfo/ircc-commands.html General IRC commands]

[[Category:FlightGear]]
[[Category:Community]]

Building FlightGear - Devuan

2017-10-10T11:08:48Z

Flughund: Update for 2017.3; other plib repo; syntax

HowTo build [[FlightGear]] stable ([[Changelog_2017.3|2017.3]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (Jessie). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probabaly apply on [https://debian.org/ Debian] GNU/Linux Jessie, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].



[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands may cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install automake cmake coreutils g++ gcc git make sed subversion"

; Dependencies
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev \
libfltk1.3-dev libglew-dev libgtkglext1-dev libjpeg62-turbo-dev \
libopenal-dev libopenscenegraph-dev libqt5opengl5-dev \
librsvg2-dev libxml2-dev qt5-default qtdeclarative5-dev"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If "libjpeg62-turbo-dev" breaks package dependencies, just install one of the other versions' -dev.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev". 


== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.5 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for stable and next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and next: 
While just installing package "libplib-dev" should work, it's [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended] to build it from source.
cd $FG_SRC_DIR
<nowiki>git clone https://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git commit --all --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j$(nproc) && make install

=== [[SimGear]] ===
Stable and next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2017.3

Stable and next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake CFLAGS="--std=c++11" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" \
$FG_SRC_DIR/simgear.git
make -j$(nproc) && make install

=== FlightGear source ===
Stable and next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2017.3

Stable and next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake CFLAGS="--std=c++11" -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/fgdata" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j$(nproc) && make install

=== FlightGear data ===
Stable only:
cd $FG_INSTALL_DIR
<nowiki>wget http://sourceforge.net/projects/flightgear/files/release-2017.3/FlightGear-2017.3.1-data.tar.bz2/download -O FlightGear-2017.3.1-data.tar.bz2</nowiki>
tar xjf FlightGear-2017.3.1-data.tar.bz2

next only:
cd $FG_INSTALL_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

Talk:Building FlightGear - Devuan

2017-10-08T09:40:39Z

Flughund:

Hello,

I didn't try these instructions recently, but they proved very useful when I first built FG, so thanks for this!

Two remarks:
* plib being dead upstream, what is the point of building it? I've always used the Debian one for this without any problem (well, actually a fixed local version for joystick deadband management; sid now [https://bugs.debian.org/787464 has the fix] at last, but not stretch, unfortunately).
* Current FG from next requires these two packages when building with Qt support: qtdeclarative5-private-dev and qml-module-qtquick2 (since [https://sourceforge.net/p/flightgear/flightgear/ci/3a8d3506d651b770e3173841a034e6203528f465/ FG commit 3a8d350], committed on 2017-09-26).
--[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 18:31, 3 October 2017 (EDT)

: Oy!
: a) yw
: b) TBH I am not certain whether the plib step is required anymore, will look into that for the next update (for which I hope to have some spare time in the upcoming days). Last time I've checked it was required since Melchior's commits never went into a release and hence never reached Debian.
: c) Thanks for reporting the newly required packages, saves myself some research!
: --[[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 22:27, 3 October 2017 (EDT)

:: My pleasure. :)
::
:: It is true that plib svn has a significant amount of code changes that are not in the orig tarballs used by the Debian packages (at least stretch and sid for sure, probably several older releases too). OTOH, the Debian packages have two security fixes (for CVE-2011-4620 and CVE-2012-4552) and the corresponding patches never got applied in plib's svn repository. :/
:: --[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 03:27, 4 October 2017 (EDT)

::: The [https://sourceforge.net/p/libplib/code/ci/master/tree/ plib repository used by download_and_compile.sh] now has the security fixes, on top of the latest PLIB svn commit (I diffed [https://sourceforge.net/p/libplib/code/ci/1b3b3e1d7689a85a50720f112614022c65d592bb/ Clément's commit 1b3b3e1d] and the [https://sourceforge.net/p/plib/code/HEAD/tree/trunk/ official plib 'trunk'], the only differences are a 'version' file added at the repo root and the CMakeLists.txt files added by Clément).
::: --[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 04:02, 5 October 2017 (EDT)

:::: Yay, that's great news! Thanks a lot! For Saturday they're predicting rain so I probably will have time far an update.
:::: --[[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 12:06, 5 October 2017 (EDT)

:::: Do you think it'd be possible to alter the version to 1.8.6 in that repo, too? As suggested by Melchior in https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html
:::: AFAICS this would mean altering file "version" and file "src/util/ul.h" line 157.
:::: --[[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 21:02, 6 October 2017 (EDT)

::::: Mmmm, I read that mail and discovered things indeed, but I don't know if we can morally do that. :) Since this is not the official plib repo... it's always very delicate when one has to at least technically fork a project that is not maintained anymore. :/ Otherwise, I have [https://bugs.debian.org/787464 that bugfix] from 2015 too, related to joystick deadband management. Maybe some #define PLIB_FLIGHTGEAR_VARIANT would be cleaner...
::::: --[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 05:41, 7 October 2017 (EDT)

:::::: I don't think we run into problems regarding morality: https://sourceforge.net/p/plib/mailman/message/28580157/
:::::: Ah, interesting that bug. Always had the feeling something was wrong with the dead band of my simple joystick. Though not sure whether it's the stick itself or if that was because of this bug. Will try that as soon as I rebuild FG.
:::::: --[[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 06:16, 7 October 2017 (EDT)

::::::: Yeah, my use of the word “morally” was a bit of a joke, of course. Indeed, plib's author gave FG devs much latitude, but no one so far, TTBOMK, said “this is plib-ng [whatever the name] and I am maintaining it.” And distro packages still refer to the historic plib, and FG is not its only user (there is at least TORCS, maybe others)...
:::::::
::::::: I'll ask on flightgear-devel.
::::::: --[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 07:58, 7 October 2017 (EDT)

:::::::: Done, see [https://sourceforge.net/p/flightgear/mailman/message/36067462/ here].
:::::::: --[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 08:50, 7 October 2017 (EDT)

:::::::: I really appreciate this! I am a total noob when it comes to coding or handling code in any way. And the sed thingy in the plib section bothers me for a long time now. On my local copy of this article I already have applied the changes for the new repo but due to git and cmake it is even more hackish than before. So I was afraid to change it online and preferred to wait and hope for a better solution. Oh, and yes, your assumtion was correct, I am Alex D-HUND AKA flughund AKA debdog.
:::::::: --[[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 12:32, 7 October 2017 (EDT)

::::::::: You're welcome. I'm a bit surprised things get that ugly just because of the switch to Git and CMake; you could maybe post your command sequence here. Also, since Clément's repository only *adds* a CMake setup and the security fixes, you should be able to use the old build method too, just replacing an 'svn co' command with a 'git clone' one (and changing the repository address, of course).
:::::::::
::::::::: BTW, if you want to return the repository to its pristine state, there are two useful commands: 'git reset --hard' to restore files tracked by Git to their state in HEAD (this is equivalent to 'git reset --hard HEAD') and variants of 'git clean -df'. (use -n to see what would be done without doing it, and see 'git clean --help' for other options). This avoids having to clone the repo more often than needed...
::::::::: --[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 03:21, 8 October 2017 (EDT)

:::::::::: Well, not exactly ugly, just more hackish and even less user friendly:
cd $FG_SRC_DIR
<nowiki>git clone https://git.code.sf.net/p/libplib/code libplib.git</nowiki>
cd libplib.git
echo "1.8.6" > version
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
git add version src/util/ul.h && git commit --message "Increase tiny version to 6."
mkdir $FG_SRC_DIR/build-plib && cd $FG_SRC_DIR/build-plib
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/libplib.git
make -j2 && make install
:::::::::: --[[User:Flughund|Flughund]] ([[User talk:Flughund|talk]]) 05:40, 8 October 2017 (EDT)

Talk:Building FlightGear - Devuan

2017-10-07T16:33:19Z

Flughund:

Talk:Building FlightGear - Devuan

2017-10-07T10:16:39Z

Flughund:

Talk:Building FlightGear - Devuan

2017-10-07T01:03:20Z

Flughund:

Talk:Building FlightGear - Devuan

2017-10-05T16:07:01Z

Flughund:

Talk:Building FlightGear - Devuan

2017-10-04T02:27:41Z

Flughund:

Cessna 172P/info

2017-09-20T23:14:39Z

Flughund: removed dual-control as a feature since there is no trace of it in the craft

<includeonly>{{infobox aircraft
| name = Cessna 172P Skyhawk
| hangar = fgdata
| image = c172p-thumbnail.jpg
| image2 = C172p-cockpit2.jpg
| type = Civil aircraft/Civil utility aircraft
| config = High wing aircraft/Fixed gear aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Cessna
| authors = David Megginson/Gilberto Agostinho/Wayne Bragg/Juan Vera del Campo/onox/Fernando Barbosa/Daniel Dubreuil/Jonathan Schellhase/Israel Hernandez/Tuomas Kuosmanen/Anders Gidenstam/Waldo Kitty/algefaen
| fdm = JSBSim
| fgname = c172p
| status-fdm = 4
| status-systems = 5
| status-cockpit = 5
| status-model = 4
| ready = tutorials/checklist
| devel-repo = {{github url|user=Juanvvc|repo=c172p-detailed}}
| download = {{github zip file|user=Juanvvc|repo=c172p-detailed|full=1}}
| liverydbid = 70
| forumtid = 25157
| note = {{LangSwitch
| en = This is the default FlightGear aircraft and is distributed as part of the base package.
| de = Dies ist das FlightGear Standardflugzeug und im Basispaket der Software enthalten.
| zh = 这是FlightGear的默认机型，并被包括在FlightGear主程序中。
}}
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Cessna 172P]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Robin DR400 Dauphin/info

2017-09-19T20:29:32Z

Flughund: removed dual-control due to no worky

<includeonly>{{infobox aircraft
| name = Robin DR400 Dauphin
| hangar = fgaddon
| aircraft = DR400-dauphin
| image = DR400-dauphin.jpg
| image2 = DR400 Dauphin Rembrandt 02.jpg
| alt2 = The Robin DR400 Dauphin's cockpit lighting.
| type = Sport aircraft/Civil utility aircraft/Glider tug
| config = Low wing aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Avions Pierre Robin
| authors = Bertrand AUGRAS (3D)/Daniel DUBREUIL (FDM)/Clement de l'Hamaide (3D, Systems, Adaptation)/PAF team
| fdm = JSBSIM
| fgname = dr400-dauphin
| status-fdm = 4
| status-systems = 4
| status-cockpit = 5
| status-model = 4
| devel-hangar = paf
| ready = checklist/tutorials/rembrandt
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Robin DR400 Dauphin]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Default head-up display

2017-07-28T14:06:25Z

Flughund: update link to README.hud

{{Note|The HUD system will one day be replaced by a [[Canvas HUD]] system.}}

The {{Wikipedia|Head-up display|'''Head-up display'''}} (HUD) is an important instrument in modern, mostly military, cockpits. FlightGear provides a XML-based system to relatively easily create HUDs for aircraft such as the [[F-14B]] and [[F-16]].

However, this article's focus is on FlightGear's default head-up displays. Those are available for any craft which does not include its own set. Have a look at [[#Further Information|Further Information]] if you're planning to create a HUD.

Activate the HUD with {{key press|h}}. Pressing it repeatedly moves through the configured colours and turns it off again. To change the brightness, press {{key press|Shift|h}}. Press {{key press|Shift|i}} to go through the available HUD's. Press {{key press|i}} to switch back to the first one at any time. Have in mind that some aircraft do assign one or more of those keys differently and therefore one or more function/s is/are missing on them.

Some of the head-up display's options can be altered in the menu: <code>View → Adjust HUD Properties</code>

[[File:HUD_default_overview.png|thumb|420px|Huds/default.xml]]
[[File:HUD_minimal_overview.png|thumb|420px|Huds/minimal.xml]]
[[File:HUD_NTPS_overview.png|thumb|420px|Huds/NTPS.xml]]

== Features ==
=== Control inputs ===
; [[Aileron]]
: Monitors the bearing of the control input on the aileron's axis. Attached along the upper side is the indicator for the trim input on that axis.
: Properties: <code>/controls/flight/aileron</code> and <code>/controls/flight/aileron-trim</code>

; [[Elevator]]
: Monitors the bearing of the control input on the elevator's axis. Attached to the left the trim on this axis.
: Properties: <code>/controls/flight/elevator</code> and <code>/controls/flight/elevator-trim</code>

; [[Rudder]]
: Monitors the bearing of the control input on the rudder's axis. Attached to the bottom the trim input.
: Properties: <code>/controls/flight/rudder</code> and <code>/controls/flight/rudder-trim</code>

; Throttle
: Monitors the throttle input axis.
: Property: <code>/controls/engines/engine/throttle</code>

=== Instruments ===
; [[AMSL]] (Height above mean sea level)
: Current altitude relative to sea level in feet (ft) (1 ft = 30.48 cm).
: Property: <code>/position/altitude-ft</code>

; g-load
: The {{Wikipedia|G-force}} appealing to the pilot - to avoid black-/redout.
: Property: <code>/accelerations/pilot/z-accel-fps_sec</code> with factor <tt>-0.03108095</tt>

; [[Avionics and Instruments#DirectionalGyro|Gyrocompass]]
: This is an ideal version of a gyrocompass without the drawbacks of a real one. It shows heading of the aircraft relative to the geographical North Pole (true north) in degree (360 degree scale).
: Property: <code>/orientation/heading-deg</code>

; [[KIAS]] ('''K'''nots '''I'''ndicated '''A'''ir'''s'''peed)
: Current speed relating to the ambient air in knot/knots (kt/kts) (1 kt = 1.151 mph = 1.852 km/h).
: Property: <code>/velocities/airspeed-kt</code>

; Latitude / Longitude
: Current location according to the {{Wikipedia|geographic coordinate system}}.
: To change the format of the displayed coordinates, go to <tt>Autopilot</tt> --> <tt>Set Lat/Lon-format</tt>.
: Properties: <code>/position/latitude-string</code> and <code>/position/longitude-string</code>

; Pitch ladder
: Displays the aircraft's pitch and roll relative to the ground's level/horizontal in degree. It's used as an artificial horizon ([[Avionics and Instruments#Attitude Indicator|Attitude indicator]]).
: Properties: <code>/orientation/roll-deg</code> and <code>/orientation/pitch-deg</code>

; Radio altimeter
: Shows current altitude [[above ground level]] (AGL) in feet. Relating to the location of the aircraft's radio altimeter, it's not zero if the aircraft is on the ground.
: Property: <code>/position/altitude-agl-ft</code>

; Turn-bank-indicator
: [[Avionics and Instruments#Turn Coordinator|Turn Coordinator]]
: Properties: <code>/orientation/roll-deg</code> and <code>/orientation/side-slip-deg</code>

[[File:HUD_default_autopilot.jpg|thumb|420px|HUD autopilot]]
=== [[Autopilot]] ===
If the autopilot is active the HUD displays its settings. For each active function (heading, altitude and speed) a box will appear below the gyrocompass containing information on its mode and, if existent, the associated value.
; Heading control
: Whether it is active or not and on which mode it operates is determined by the content of the <code>/autopilot/locks/heading</code> property.
: The values are taken from <code>/autopilot/settings/heading-bug-deg</code> and <code>/autopilot/settings/true-heading-deg</code>.

; Altitude control
: Active mode: <code>/autopilot/locks/altitude</code>
: Their values: <code>/autopilot/settings/target-altitude-ft</code>, <code>/autopilot/settings/vertical-speed-fpm</code> and <code>/autopilot/settings/target-agl-ft</code>.

; Speed control
: Active mode: <code>/autopilot/locks/speed</code>
: Their values: <code>/autopilot/settings/target-speed-kt</code> and <code>/autopilot/settings/target-speed-mach</code>

[[File:HUD_default_gps.jpg|thumb|420px|HUD GPS]]
=== [[GPS]] ===
The upper left hand corner shows the most important information on the actual state of the GPS. Namely these are (line by line):
: the mode the GPS operates in and the active waypoint's identifier.
: the distance "D" (in nautical miles, nm) and the calculated time to this waypoint "TTW".
: the bearing "BRG" to the active waypoint and the course deviation "XTR" based on the leg from the previous waypoint.
: the current speed relative to the ground "GS".

=== Big fat arrow ===
Remains of a going to be useful instrument.
: To get rid of it, remove or comment "runway.xml" from/in <tt>$FG_ROOT/Huds/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Huds/default.xml;hb=HEAD default.xml]</tt>.
: To make it point to the airport selected by menu item "Tower Position", apply patches as shown [http://sourceforge.net/mailarchive/message.php?msg_id=30422572 here].

== Further Information ==
HUDs may be replaced or added by changing or adding their paths in <tt>preferences.xml</tt> or by setting the paths as command line options. To change the order of the existing ones the options would be: <code>--prop:/sim/hud/path[1]=Huds/minimal.xml</code> <code>--prop:/sim/hud/path[2]=Huds/default.xml</code>

If you consider to create your own HUD have a look at [[Canvas HUD]] first.

The basic settings regarding to any HUD are set in <tt>$FG_ROOT/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=preferences.xml;hb=HEAD preferences.xml]</tt>. Search the file for the <tt><hud></tt>-tag and you will find a list of properties.

The setup of the default HUD is defined at <tt>[[$FG_ROOT]]/Huds/[http://mapserver.flightgear.org/git/?p=fgdata;a=blob_plain;f=Huds/default.xml;hb=HEAD default.xml]</tt> and documentation can be found at <tt>$FG_ROOT/Docs/[https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.hud README.hud]</tt>.

== Additional HUDs ==
; Generic helicopter HUD
: This is a generic HUD for helicopters, inspired by MIL-STD 1295A and the AH-64A IHADSS symbology. [http://stefan.gofferje.net/downloads/flightgear/file/6-generic-helicopter-hud Download]

; HeliHUD
: Designed to fly helicopters in Helicopter View it is also handy for any craft with a not yet finished cockpit. It also contains a minimalistic HUD only showing some navigational information such as compass and GPS. The [http://beggabaur.rocks/fgfs/helihud_0.3.tar.bz2 download] contains instructions and specs.

; V(MX)-22 Osprey HUD
: [http://stefan.gofferje.net/downloads/flightgear/file/1-hud-for-vmx-22-osprey Download]

[[Category:FlightGear feature]]
[[Category:Menubar]]

Building FlightGear - Debian

2017-05-28T14:45:40Z

Flughund: Redirected to Building_FlightGear_-_Devuan until someone takes over here.

#REDIRECT[[Building_FlightGear_-_Devuan]]

Devuan

2017-05-28T13:38:08Z

Flughund: just a link to Building_FlightGear_-_Devuan

#REDIRECT[[Building_FlightGear_-_Devuan]]

Building FlightGear - Devuan

2017-05-28T13:35:56Z

Flughund: Compile FG 2017.2 on Devuan

HowTo build [[FlightGear]] stable ([[Changelog_2017.2|2017.2]]) or bleeding edge development version, hereinafter simply called [[FlightGear_Git#Repositories_and_branches | next]], on [https://devuan.org/ Devuan] GNU/Linux Stable (Jessie). Users of Testing or Unstable at least have to change package names (version numbering) accordingly. 
Instructions probabaly apply on [https://debian.org/ Debian] GNU/Linux Jessie, too.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands may cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install automake cmake g++ gcc git make sed subversion"

; Dependencies
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libdbus-1-dev \
libfltk1.3-dev libglew-dev libgtkglext1-dev libjpeg62-turbo-dev \
libopenal-dev libopenscenegraph-dev libqt5opengl5-dev \
librsvg2-dev libxml2-dev qt5-default qtdeclarative5-dev"

: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If "libjpeg62-turbo-dev" breaks package dependencies, just install one of the other versions' -dev.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.

: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely these are "libplib-dev" and "simgear-dev". 


== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-Stable</code> or <code>$HOME/FG-Stable</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make -j2 && make install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a [http://www.cmiss.org/cmgui/wiki/SettingEnvironmentVariablesInBash placeholder] for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-Stable && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT about 2.3 GiB (required disk space 4 GiB) / Stable about 1.6 GiB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 

For more/advanced cmake options and SimGear's and FlightGear's optional features see the [[Building_using_CMake#Optional_Features|cmake]] article.

[[File:Zeichen_144_icon.png|21px]] Do '''not''' mix instructions for stable and next! Not even for fgdata, mixing versions will almost certainly break the installation.

=== [[plib]] ===
Stable and next: 
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
cd $FG_SRC_DIR
<nowiki>svn co https://svn.code.sf.net/p/plib/code/trunk plib.svn</nowiki>
cd plib.svn
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 && make install

=== [[SimGear]] ===
Stable and next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/simgear simgear.git</nowiki>

Stable only:
cd simgear.git
git checkout release/2017.2

Stable and next:
mkdir $FG_SRC_DIR/build-sg && cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j2 && make install

=== FlightGear source ===
Stable and next:
cd $FG_SRC_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/flightgear flightgear.git</nowiki>

Stable only:
cd flightgear.git
git checkout release/2017.2

Stable and next:
mkdir $FG_SRC_DIR/build-fg && cd $FG_SRC_DIR/build-fg
cmake -D FG_DATA_DIR:PATH="$FG_INSTALL_DIR/fgdata" -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j2 && make install

=== FlightGear data ===
Stable only:
cd $FG_INSTALL_DIR
<nowiki>wget http://sourceforge.net/projects/flightgear/files/release-2017.2/FlightGear-2017.2.1-data.tar.bz2/download -O FlightGear-2017.2.1-data.tar.bz2</nowiki>
tar xjf FlightGear-2017.2.1-data.tar.bz2

next only:
cd $FG_INSTALL_DIR
<nowiki>git clone git://git.code.sf.net/p/flightgear/fgdata fgdata</nowiki>

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --launcher
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs