FlightGear wiki - User contributions [en]

Howto:Set up a multiplayer server on FreeBSD

2013-07-10T23:18:39Z

Las:

FlightGear Multiplayer will build directly on FreeBSD. Below are the steps to build the lastest *nix release (v0.11.1 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]
== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
</pre>

== Building ==
<pre>
mkdir fgms-build
cd fgms-build/
cmake ../fgms-0-x
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines with comments in my /etc/fgms.conf:
<pre>
server.name = mpserverNN
server.port = 5000

server.telnet_port = 5001
server.admin_port = 5002
server.admin_user = xxxx
server.admin_pass = xxxx
server.admin_enable = xxxx
server.logfile = /var/log/fgms.log
# mpserver01 does this
server.tracked = false
server.daemon = true
# This only needed for one server on the network
server.is_hub = false
# Distance from which server will allow FG pilots see each other
server.out_of_reach = 100
# You will need to contact the admin of mpserver01 and tell them this server now exists.
relay.host = mpserver01.flightgear.org
relay.port = 5000
# it's only interresting for fgms-developers
# crossfeed.host = foo.example.com
</pre>

== Running ==
<pre>
$ fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
10.07.2013 15:26:43 # This is mpserver02
10.07.2013 15:26:43 # FlightGear Multiplayer Server v0.11.1 started
10.07.2013 15:26:43 # using protocol version v1.1 (LazyRelay enabled)
10.07.2013 15:26:43 # listening to port 5000
10.07.2013 15:26:43 # telnet port 5001
10.07.2013 15:26:43 # admin port x002
10.07.2013 15:26:43 # using logfile /var/log/fgms.log
10.07.2013 15:26:43 # listening on 64.69.45.88
10.07.2013 15:26:43 # tracking is disabled.
10.07.2013 15:26:43 # I have 1 relays
10.07.2013 15:26:43 # relay mpserver01.flightgear.org:5000
10.07.2013 15:26:43 # I have 0 crossfeeds
10.07.2013 15:26:43 # I have 2 blacklisted IPs
10.07.2013 15:26:43 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-10T22:57:16Z

Las: /* Running */

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]

== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>

== Building ==
<pre>
cmake ../fgms-0-x
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines with comments in my /etc/fgms.conf:
<pre>
server.name = mpserverNN
server.port = 5000

server.telnet_port = 5001
server.admin_port = 5002
server.admin_user = xxxx
server.admin_pass = xxxx
server.admin_enable = xxxx
server.logfile = /var/log/fgms.log
# mpserver01 does this
server.tracked = false
server.daemon = true
# This only needed for one server on the network
server.is_hub = false
# Distance from which server will allow FG pilots see each other
server.out_of_reach = 100
# You will need to contact the admin of mpserver01 and tell them this server now exists.
relay.host = mpserver01.flightgear.org
relay.port = 5000
# it's only interresting for fgms-developers
# crossfeed.host = foo.example.com
</pre>

== Running ==
<pre>
$ fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
10.07.2013 15:26:43 # This is mpserver02
10.07.2013 15:26:43 # FlightGear Multiplayer Server v0.11.1 started
10.07.2013 15:26:43 # using protocol version v1.1 (LazyRelay enabled)
10.07.2013 15:26:43 # listening to port 5000
10.07.2013 15:26:43 # telnet port 5001
10.07.2013 15:26:43 # admin port x002
10.07.2013 15:26:43 # using logfile /var/log/fgms.log
10.07.2013 15:26:43 # listening on 64.69.45.88
10.07.2013 15:26:43 # tracking is disabled.
10.07.2013 15:26:43 # I have 1 relays
10.07.2013 15:26:43 # relay mpserver01.flightgear.org:5000
10.07.2013 15:26:43 # I have 0 crossfeeds
10.07.2013 15:26:43 # I have 2 blacklisted IPs
10.07.2013 15:26:43 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-10T22:54:46Z

Las: /* Building */

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]

== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>

== Building ==
<pre>
cmake ../fgms-0-x
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines with comments in my /etc/fgms.conf:
<pre>
server.name = mpserverNN
server.port = 5000

server.telnet_port = 5001
server.admin_port = 5002
server.admin_user = xxxx
server.admin_pass = xxxx
server.admin_enable = xxxx
server.logfile = /var/log/fgms.log
# mpserver01 does this
server.tracked = false
server.daemon = true
# This only needed for one server on the network
server.is_hub = false
# Distance from which server will allow FG pilots see each other
server.out_of_reach = 100
# You will need to contact the admin of mpserver01 and tell them this server now exists.
relay.host = mpserver01.flightgear.org
relay.port = 5000
# it's only interresting for fgms-developers
# crossfeed.host = foo.example.com
</pre>

== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-10T22:54:04Z

Las: /* Modifications */

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]

== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>

== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines with comments in my /etc/fgms.conf:
<pre>
server.name = mpserverNN
server.port = 5000

server.telnet_port = 5001
server.admin_port = 5002
server.admin_user = xxxx
server.admin_pass = xxxx
server.admin_enable = xxxx
server.logfile = /var/log/fgms.log
# mpserver01 does this
server.tracked = false
server.daemon = true
# This only needed for one server on the network
server.is_hub = false
# Distance from which server will allow FG pilots see each other
server.out_of_reach = 100
# You will need to contact the admin of mpserver01 and tell them this server now exists.
relay.host = mpserver01.flightgear.org
relay.port = 5000
# it's only interresting for fgms-developers
# crossfeed.host = foo.example.com
</pre>

== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-10T22:50:39Z

Las: /* Configuring */

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]

== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>

== Modifications ==
*I received 2 error when compiling fgms-0-x/src/server/fg_util.cxx because integer constants were too large so just convert them to real.

The commands below will automatically make the above modifications.
<pre>
sed -i '' -e "s|1125899906842624)|1125899906842624.)|" ../fgms-0-x/src/server/fg_util.cxx
sed -i '' -e "s|1099511627776)|1099511627776.)|" ../fgms-0-x/src/server/fg_util.cxx
</pre>

== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines with comments in my /etc/fgms.conf:
<pre>
server.name = mpserverNN
server.port = 5000

server.telnet_port = 5001
server.admin_port = 5002
server.admin_user = xxxx
server.admin_pass = xxxx
server.admin_enable = xxxx
server.logfile = /var/log/fgms.log
# mpserver01 does this
server.tracked = false
server.daemon = true
# This only needed for one server on the network
server.is_hub = false
# Distance from which server will allow FG pilots see each other
server.out_of_reach = 100
# You will need to contact the admin of mpserver01 and tell them this server now exists.
relay.host = mpserver01.flightgear.org
relay.port = 5000
# it's only interresting for fgms-developers
# crossfeed.host = foo.example.com
</pre>

== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server

2013-07-09T19:40:26Z

Las: /* Public Server */

This page is dedicated to providing a short overview about installing the [[FlightGear Multiplayer Server]] ('fgms'). The reader is assumed to be reasonably familiar with working in a Unix/Linux shell environment.

== Pre-Requisites ==
* A computer running a variant of *nix to compile and host the server. Speed of the machine isn't of great consequence as the protocol is a multiplexer which doesn't require much processing grunt.
** For specific documentation for setting up on FreeBSD see [[Howto:Set up a multiplayer server on FreeBSD]].
* direct/physical or remote access to the server (i.e. SSH/telnet, a conventional web hosting package will usually '''not''' be sufficient!)-suitable hosting packages are: dedicated root servers, virtual private servers, shell servers - for a collection of '''free''' shell account providers that may be suitable for fgms, see [[Free Shell Providers]] (you may want to check this out if you are interested in running fgms but don't have hosting yet)
* if the server is meant to be a public internet server: an internet connection, featuring sufficient upstream/downstream capabilities (see below for details concerning bandwidth requirements).
* firewall policies will need to be set up to allow for incoming and outgoing UDP traffic for the corresponding ports, the same applies to the administration port (TCP)
* permission to run unattended background processes (this may only be an issue with certain limited hosting packages)
* a working GNU toolchain including gcc/g++ (compiler), make & cmake
* fgms source code, currently version 0.10.23
* about 5-10 MB of hard disk space (mainly required for building the binary)

== Traffic & Bandwidth Considerations ==

Note: Currently (May 2008), the server code basically boils down to a packet multiplexer (i.e. most data is -unconditionally- transmitted to all 'active' clients), which may thus create considerable amounts of traffic; this ought to be taken into consideration due to bandwidth limitations in most hosting packages (i.e. '''fgms may create considerable amounts of traffic!'''). For basic calculations: inbound traffic is 25 Kilobit per second while outbound is 25 Kbits per second for each plane/client that can 'see' another.

By default, assuming a 10hz update interval, each active fgfs client will currently cause I/O traffic of approximately 5 kbytes/sec (one update consuming ~500 bytes) [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

As client updates have to be propagated to all other active clients by the server, this number has to be multiplied by the number of active clients -1 (i.e. clients within a configurable range, minus the originating client).
In addition, the fgms system allows for traffic updates to be sort of 'mirrored' on (relayed to) other configurable multiplayer/relay servers.

This feature makes it possible for users/clients to use an arbitrary server (with acceptable latency), but still see clients/vehicles connected to different servers. Thus, such relay servers may additionally increase inbound/outbound traffic considerably as all traffic is mirrored/propagated to such relays.

Having more servers should actually decrease the load on each server in high load situations, i.e. when most of the clients are within range of each other. See this
[http://www.gidenstam.org/FlightGear/fgms/fgms_bandwidth_estimates.txt brief note on the theoretical bandwidth behaviour of fgms.]

=== Facts ===
In March 2008, the main fgms multiplayer server (pigeond.net) was reported to consume approximately 15 gb of bandwidth per '''day''', with an average throughput of 200 kB/sec and peak loads of up to ~ 650 kB/sec [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

During the same month (the much less used but interconnected) mpserver06.flightgear.org had on average 742 MB incoming and 688 MB outgoing traffic per day (i.e. 72 kbit/sec respective 66 kbit/sec on average).

In September 2009, mpserver 05 had a massive peak bandwidth of 1.0 MB/sec. Average bandwidth consumed was about 9 GB of bandwidth per day. The average bandwidth usage per day is climbing due to more users moving from 02 to 05.

=== Reducing bandwidth requirements ===
Total network traffic is mainly determined by the number of active clients that 'see eachother' and configured mirrors.
If traffic considerations are relevant, the following options exist to reduce overall server/network load:

* configure a relatively low "server.out_of_reach" value, so that clients outside a certain range are not provided with updates (usually about 100 nm on the main server network)
* for virtual gatherings (i.e. fly-ins), have clients use airports and places that do not have lots of other traffic (i.e. in other words, avoid places like standard airports such as KSFO)
* avoid the use of unnecessary relay servers
* if you are not interested in your server being publicly available, only share its address with your friends privately
* for local testing/development purposes, you may want to run only a private fgms session, that may be specific to your LAN or even computer.

=== Hosting Packages known to be suitable for fgms hosting ===
(yet to be filled in)

== Getting & Building fgms ==

* You will need the build tools cmake and make, and also g++ to compile the fgms application. These can usually be found in the package manager for most the common Linux distributions. You will also need the git client to fetch the source code from the repository, if you plan to download it from the command line interface (see below).

* Once the build tools are installed on your machine, create a directory to hold the source code. This could be named anything, such as fgms. Create it in your user home directory. Note that this WILL NOT be the directory where the program will be compiled.

* Now 'cd' into the directory you just made, where you will run the command to fetch the source code from the git repository (see below).

* To download the latest stable version via HTTP, you can use direct your browse to the URL http://gitorious.org/fgms/fgms-0-x/. Download and unzip the source code, and place it in the directory you created above.

* To download a file directly to your server from an ssh session, you can use git tools with the following command:

$git clone git://gitorious.org/fgms/fgms-0-x.git

== Compiling FGMS ==

For FreeBSD-specific instructions, please see [[Howto:Set up a multiplayer server on FreeBSD]]

NOTE: In general, on any current machine this process should not take longer than about 60 seconds.

* Once you have the source code, 'cd' into the ~/fgms/fgms-0-x/ directory and note the presence of the CMakeLists.txt file and the README.cmake file. Open the README.cmake file and take a minute to read it over. Also, note the path to the CMakeLists.txt file, as you will need this in the following steps.

* Now create a build-fgms directory in your home directory, and 'cd' into it. From inside the ~/build-fgms/ directory, run the cmake command using the path to the CMakeLists.txt as an argument. For example: cmake /home/<user_name>/fgms/fgms-0-x/

* Once the build finishes, you can either run the "cmake --build ..." command as shown in the README.cmake file, or you can simply use "make" to build the program.

* Once the compilation process finishes, you need to install the program using "make install" (as user), or you can also install as root.

* Once the program has been installed, you need to copy the fgms_example.conf file from the /fgms/fgms-0-x/src/server directory, into the build-fgms directory. To do this from inside the /fgms/fgms-0-x/src/server directory, you can use this command: cp ./fgms_example.conf ~/build-fgms/

* Now 'cd' into the build-fgms directory, and rename the file you just copied as "fgms.conf" so that fgms can find the proper configuration.

== Setting up the config file ==

At this point you should have a working 'fgms' binary in the build-fgms directory. If the server will be offline or for private use (i.e. LAN-only, please comment out the relay servers section. This will save bandwidth from the server being consumed.

* Edit the fgms.conf file according to the instructions found elsewhere on this page, then save and close the file.

== Running FGMS for the first time ==

In addition to its configuration file, FGMS supports a number of configuration parameters that can be passed at startup (and that will by default override any configuration file settings), to get a summary of supported parameters, you may want to run:
$ ./fgms --help

Which should present you with the following output:

<pre>
options are:
-h print this help screen
-a PORT listen to PORT for telnet
-c config read 'config' as configuration file
-p PORT listen to PORT
-t TTL Time a client is active while not sending packets
-o OOR nautical miles two players must be apart to be out of reach
-l LOGFILE Log to LOGFILE
-v LEVEL verbosity (loglevel) in range 1 (few) and 5 (much)
-d do _not_ run as a daemon (stay in foreground)
-D do run as a daemon

the default is to run as a daemon, which can be overridden in the
config file.
commandline parameters always override config file options
</pre>

After having finished the fgms configuration, you can try running fgms and start up fgfs to use the new server.
=== Public Server ===
If you'd like to make it a public server, you can simply use your external (public) IP address to set up the multiplayer in fgfs.

For others to know about your public server you should notify the developers of the existence of your server by posting a message to the [[Mailing list|developers mailing list]].

Add your server to this list: http://wiki.flightgear.org/Howto:Multiplayer#Servers

== Related content ==
* [[Howto: Multiplayer|Multiplayer howto]]
* [[MPmap]]

[[Category:Howto]]
[[Category:Multiplayer]]

[[fr:Installer un serveur multijoueur]]

Howto:Set up a multiplayer server

2013-07-09T19:38:06Z

Las: /* Public Server */

This page is dedicated to providing a short overview about installing the [[FlightGear Multiplayer Server]] ('fgms'). The reader is assumed to be reasonably familiar with working in a Unix/Linux shell environment.

== Pre-Requisites ==
* A computer running a variant of *nix to compile and host the server. Speed of the machine isn't of great consequence as the protocol is a multiplexer which doesn't require much processing grunt.
** For specific documentation for setting up on FreeBSD see [[Howto:Set up a multiplayer server on FreeBSD]].
* direct/physical or remote access to the server (i.e. SSH/telnet, a conventional web hosting package will usually '''not''' be sufficient!)-suitable hosting packages are: dedicated root servers, virtual private servers, shell servers - for a collection of '''free''' shell account providers that may be suitable for fgms, see [[Free Shell Providers]] (you may want to check this out if you are interested in running fgms but don't have hosting yet)
* if the server is meant to be a public internet server: an internet connection, featuring sufficient upstream/downstream capabilities (see below for details concerning bandwidth requirements).
* firewall policies will need to be set up to allow for incoming and outgoing UDP traffic for the corresponding ports, the same applies to the administration port (TCP)
* permission to run unattended background processes (this may only be an issue with certain limited hosting packages)
* a working GNU toolchain including gcc/g++ (compiler), make & cmake
* fgms source code, currently version 0.10.23
* about 5-10 MB of hard disk space (mainly required for building the binary)

== Traffic & Bandwidth Considerations ==

Note: Currently (May 2008), the server code basically boils down to a packet multiplexer (i.e. most data is -unconditionally- transmitted to all 'active' clients), which may thus create considerable amounts of traffic; this ought to be taken into consideration due to bandwidth limitations in most hosting packages (i.e. '''fgms may create considerable amounts of traffic!'''). For basic calculations: inbound traffic is 25 Kilobit per second while outbound is 25 Kbits per second for each plane/client that can 'see' another.

By default, assuming a 10hz update interval, each active fgfs client will currently cause I/O traffic of approximately 5 kbytes/sec (one update consuming ~500 bytes) [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

As client updates have to be propagated to all other active clients by the server, this number has to be multiplied by the number of active clients -1 (i.e. clients within a configurable range, minus the originating client).
In addition, the fgms system allows for traffic updates to be sort of 'mirrored' on (relayed to) other configurable multiplayer/relay servers.

This feature makes it possible for users/clients to use an arbitrary server (with acceptable latency), but still see clients/vehicles connected to different servers. Thus, such relay servers may additionally increase inbound/outbound traffic considerably as all traffic is mirrored/propagated to such relays.

Having more servers should actually decrease the load on each server in high load situations, i.e. when most of the clients are within range of each other. See this
[http://www.gidenstam.org/FlightGear/fgms/fgms_bandwidth_estimates.txt brief note on the theoretical bandwidth behaviour of fgms.]

=== Facts ===
In March 2008, the main fgms multiplayer server (pigeond.net) was reported to consume approximately 15 gb of bandwidth per '''day''', with an average throughput of 200 kB/sec and peak loads of up to ~ 650 kB/sec [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

During the same month (the much less used but interconnected) mpserver06.flightgear.org had on average 742 MB incoming and 688 MB outgoing traffic per day (i.e. 72 kbit/sec respective 66 kbit/sec on average).

In September 2009, mpserver 05 had a massive peak bandwidth of 1.0 MB/sec. Average bandwidth consumed was about 9 GB of bandwidth per day. The average bandwidth usage per day is climbing due to more users moving from 02 to 05.

=== Reducing bandwidth requirements ===
Total network traffic is mainly determined by the number of active clients that 'see eachother' and configured mirrors.
If traffic considerations are relevant, the following options exist to reduce overall server/network load:

* configure a relatively low "server.out_of_reach" value, so that clients outside a certain range are not provided with updates (usually about 100 nm on the main server network)
* for virtual gatherings (i.e. fly-ins), have clients use airports and places that do not have lots of other traffic (i.e. in other words, avoid places like standard airports such as KSFO)
* avoid the use of unnecessary relay servers
* if you are not interested in your server being publicly available, only share its address with your friends privately
* for local testing/development purposes, you may want to run only a private fgms session, that may be specific to your LAN or even computer.

=== Hosting Packages known to be suitable for fgms hosting ===
(yet to be filled in)

== Getting & Building fgms ==

* You will need the build tools cmake and make, and also g++ to compile the fgms application. These can usually be found in the package manager for most the common Linux distributions. You will also need the git client to fetch the source code from the repository, if you plan to download it from the command line interface (see below).

* Once the build tools are installed on your machine, create a directory to hold the source code. This could be named anything, such as fgms. Create it in your user home directory. Note that this WILL NOT be the directory where the program will be compiled.

* Now 'cd' into the directory you just made, where you will run the command to fetch the source code from the git repository (see below).

* To download the latest stable version via HTTP, you can use direct your browse to the URL http://gitorious.org/fgms/fgms-0-x/. Download and unzip the source code, and place it in the directory you created above.

* To download a file directly to your server from an ssh session, you can use git tools with the following command:

$git clone git://gitorious.org/fgms/fgms-0-x.git

== Compiling FGMS ==

For FreeBSD-specific instructions, please see [[Howto:Set up a multiplayer server on FreeBSD]]

NOTE: In general, on any current machine this process should not take longer than about 60 seconds.

* Once you have the source code, 'cd' into the ~/fgms/fgms-0-x/ directory and note the presence of the CMakeLists.txt file and the README.cmake file. Open the README.cmake file and take a minute to read it over. Also, note the path to the CMakeLists.txt file, as you will need this in the following steps.

* Now create a build-fgms directory in your home directory, and 'cd' into it. From inside the ~/build-fgms/ directory, run the cmake command using the path to the CMakeLists.txt as an argument. For example: cmake /home/<user_name>/fgms/fgms-0-x/

* Once the build finishes, you can either run the "cmake --build ..." command as shown in the README.cmake file, or you can simply use "make" to build the program.

* Once the compilation process finishes, you need to install the program using "make install" (as user), or you can also install as root.

* Once the program has been installed, you need to copy the fgms_example.conf file from the /fgms/fgms-0-x/src/server directory, into the build-fgms directory. To do this from inside the /fgms/fgms-0-x/src/server directory, you can use this command: cp ./fgms_example.conf ~/build-fgms/

* Now 'cd' into the build-fgms directory, and rename the file you just copied as "fgms.conf" so that fgms can find the proper configuration.

== Setting up the config file ==

At this point you should have a working 'fgms' binary in the build-fgms directory. If the server will be offline or for private use (i.e. LAN-only, please comment out the relay servers section. This will save bandwidth from the server being consumed.

* Edit the fgms.conf file according to the instructions found elsewhere on this page, then save and close the file.

== Running FGMS for the first time ==

In addition to its configuration file, FGMS supports a number of configuration parameters that can be passed at startup (and that will by default override any configuration file settings), to get a summary of supported parameters, you may want to run:
$ ./fgms --help

Which should present you with the following output:

<pre>
options are:
-h print this help screen
-a PORT listen to PORT for telnet
-c config read 'config' as configuration file
-p PORT listen to PORT
-t TTL Time a client is active while not sending packets
-o OOR nautical miles two players must be apart to be out of reach
-l LOGFILE Log to LOGFILE
-v LEVEL verbosity (loglevel) in range 1 (few) and 5 (much)
-d do _not_ run as a daemon (stay in foreground)
-D do run as a daemon

the default is to run as a daemon, which can be overridden in the
config file.
commandline parameters always override config file options
</pre>

After having finished the fgms configuration, you can try running fgms and start up fgfs to use the new server.
=== Public Server ===
If you'd like to make it a public server, you can simply use your external (public) IP address to set up the multiplayer in fgfs.

For others to know about your public server you should notify the developers of the existence of your server by posting a message to the [[Mailing list|developers mailing list]].

Add your server to this list: http://wiki.flightgear.org/Howto:Multiplayer

== Related content ==
* [[Howto: Multiplayer|Multiplayer howto]]
* [[MPmap]]

[[Category:Howto]]
[[Category:Multiplayer]]

[[fr:Installer un serveur multijoueur]]

Howto:Set up a multiplayer server

2013-07-09T19:14:11Z

Las: /* Running FGMS for the first time */

This page is dedicated to providing a short overview about installing the [[FlightGear Multiplayer Server]] ('fgms'). The reader is assumed to be reasonably familiar with working in a Unix/Linux shell environment.

== Pre-Requisites ==
* A computer running a variant of *nix to compile and host the server. Speed of the machine isn't of great consequence as the protocol is a multiplexer which doesn't require much processing grunt.
** For specific documentation for setting up on FreeBSD see [[Howto:Set up a multiplayer server on FreeBSD]].
* direct/physical or remote access to the server (i.e. SSH/telnet, a conventional web hosting package will usually '''not''' be sufficient!)-suitable hosting packages are: dedicated root servers, virtual private servers, shell servers - for a collection of '''free''' shell account providers that may be suitable for fgms, see [[Free Shell Providers]] (you may want to check this out if you are interested in running fgms but don't have hosting yet)
* if the server is meant to be a public internet server: an internet connection, featuring sufficient upstream/downstream capabilities (see below for details concerning bandwidth requirements).
* firewall policies will need to be set up to allow for incoming and outgoing UDP traffic for the corresponding ports, the same applies to the administration port (TCP)
* permission to run unattended background processes (this may only be an issue with certain limited hosting packages)
* a working GNU toolchain including gcc/g++ (compiler), make & cmake
* fgms source code, currently version 0.10.23
* about 5-10 MB of hard disk space (mainly required for building the binary)

== Traffic & Bandwidth Considerations ==

Note: Currently (May 2008), the server code basically boils down to a packet multiplexer (i.e. most data is -unconditionally- transmitted to all 'active' clients), which may thus create considerable amounts of traffic; this ought to be taken into consideration due to bandwidth limitations in most hosting packages (i.e. '''fgms may create considerable amounts of traffic!'''). For basic calculations: inbound traffic is 25 Kilobit per second while outbound is 25 Kbits per second for each plane/client that can 'see' another.

By default, assuming a 10hz update interval, each active fgfs client will currently cause I/O traffic of approximately 5 kbytes/sec (one update consuming ~500 bytes) [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

As client updates have to be propagated to all other active clients by the server, this number has to be multiplied by the number of active clients -1 (i.e. clients within a configurable range, minus the originating client).
In addition, the fgms system allows for traffic updates to be sort of 'mirrored' on (relayed to) other configurable multiplayer/relay servers.

This feature makes it possible for users/clients to use an arbitrary server (with acceptable latency), but still see clients/vehicles connected to different servers. Thus, such relay servers may additionally increase inbound/outbound traffic considerably as all traffic is mirrored/propagated to such relays.

Having more servers should actually decrease the load on each server in high load situations, i.e. when most of the clients are within range of each other. See this
[http://www.gidenstam.org/FlightGear/fgms/fgms_bandwidth_estimates.txt brief note on the theoretical bandwidth behaviour of fgms.]

=== Facts ===
In March 2008, the main fgms multiplayer server (pigeond.net) was reported to consume approximately 15 gb of bandwidth per '''day''', with an average throughput of 200 kB/sec and peak loads of up to ~ 650 kB/sec [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

During the same month (the much less used but interconnected) mpserver06.flightgear.org had on average 742 MB incoming and 688 MB outgoing traffic per day (i.e. 72 kbit/sec respective 66 kbit/sec on average).

In September 2009, mpserver 05 had a massive peak bandwidth of 1.0 MB/sec. Average bandwidth consumed was about 9 GB of bandwidth per day. The average bandwidth usage per day is climbing due to more users moving from 02 to 05.

=== Reducing bandwidth requirements ===
Total network traffic is mainly determined by the number of active clients that 'see eachother' and configured mirrors.
If traffic considerations are relevant, the following options exist to reduce overall server/network load:

* configure a relatively low "server.out_of_reach" value, so that clients outside a certain range are not provided with updates (usually about 100 nm on the main server network)
* for virtual gatherings (i.e. fly-ins), have clients use airports and places that do not have lots of other traffic (i.e. in other words, avoid places like standard airports such as KSFO)
* avoid the use of unnecessary relay servers
* if you are not interested in your server being publicly available, only share its address with your friends privately
* for local testing/development purposes, you may want to run only a private fgms session, that may be specific to your LAN or even computer.

=== Hosting Packages known to be suitable for fgms hosting ===
(yet to be filled in)

== Getting & Building fgms ==

* You will need the build tools cmake and make, and also g++ to compile the fgms application. These can usually be found in the package manager for most the common Linux distributions. You will also need the git client to fetch the source code from the repository, if you plan to download it from the command line interface (see below).

* Once the build tools are installed on your machine, create a directory to hold the source code. This could be named anything, such as fgms. Create it in your user home directory. Note that this WILL NOT be the directory where the program will be compiled.

* Now 'cd' into the directory you just made, where you will run the command to fetch the source code from the git repository (see below).

* To download the latest stable version via HTTP, you can use direct your browse to the URL http://gitorious.org/fgms/fgms-0-x/. Download and unzip the source code, and place it in the directory you created above.

* To download a file directly to your server from an ssh session, you can use git tools with the following command:

$git clone git://gitorious.org/fgms/fgms-0-x.git

== Compiling FGMS ==

For FreeBSD-specific instructions, please see [[Howto:Set up a multiplayer server on FreeBSD]]

NOTE: In general, on any current machine this process should not take longer than about 60 seconds.

* Once you have the source code, 'cd' into the ~/fgms/fgms-0-x/ directory and note the presence of the CMakeLists.txt file and the README.cmake file. Open the README.cmake file and take a minute to read it over. Also, note the path to the CMakeLists.txt file, as you will need this in the following steps.

* Now create a build-fgms directory in your home directory, and 'cd' into it. From inside the ~/build-fgms/ directory, run the cmake command using the path to the CMakeLists.txt as an argument. For example: cmake /home/<user_name>/fgms/fgms-0-x/

* Once the build finishes, you can either run the "cmake --build ..." command as shown in the README.cmake file, or you can simply use "make" to build the program.

* Once the compilation process finishes, you need to install the program using "make install" (as user), or you can also install as root.

* Once the program has been installed, you need to copy the fgms_example.conf file from the /fgms/fgms-0-x/src/server directory, into the build-fgms directory. To do this from inside the /fgms/fgms-0-x/src/server directory, you can use this command: cp ./fgms_example.conf ~/build-fgms/

* Now 'cd' into the build-fgms directory, and rename the file you just copied as "fgms.conf" so that fgms can find the proper configuration.

== Setting up the config file ==

At this point you should have a working 'fgms' binary in the build-fgms directory. If the server will be offline or for private use (i.e. LAN-only, please comment out the relay servers section. This will save bandwidth from the server being consumed.

* Edit the fgms.conf file according to the instructions found elsewhere on this page, then save and close the file.

== Running FGMS for the first time ==

In addition to its configuration file, FGMS supports a number of configuration parameters that can be passed at startup (and that will by default override any configuration file settings), to get a summary of supported parameters, you may want to run:
$ ./fgms --help

Which should present you with the following output:

<pre>
options are:
-h print this help screen
-a PORT listen to PORT for telnet
-c config read 'config' as configuration file
-p PORT listen to PORT
-t TTL Time a client is active while not sending packets
-o OOR nautical miles two players must be apart to be out of reach
-l LOGFILE Log to LOGFILE
-v LEVEL verbosity (loglevel) in range 1 (few) and 5 (much)
-d do _not_ run as a daemon (stay in foreground)
-D do run as a daemon

the default is to run as a daemon, which can be overridden in the
config file.
commandline parameters always override config file options
</pre>

After having finished the fgms configuration, you can try running fgms and start up fgfs to use the new server.
=== Public Server ===
If you'd like to make it a public server, you can simply use your external (public) IP address to set up the multiplayer in fgfs.

For others to know about your public server you should notify the developers of the existence of your server by posting a message to the developers mailing list.

Add your server to this list: http://wiki.flightgear.org/Howto:Multiplayer

== Related content ==
* [[Howto: Multiplayer|Multiplayer howto]]
* [[MPmap]]

[[Category:Howto]]
[[Category:Multiplayer]]

[[fr:Installer un serveur multijoueur]]

Howto:Multiplayer

2013-07-09T19:10:37Z

Las: /* Servers */

With the '''multiplayer''' function of [[FlightGear]] you are able to see other pilots and vice-versa. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[air traffic control]]lers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate drops]] during loading of aircraft models. Especially heavy models can cause severe lag. Therefore, it is suggested to fly in locations other than San Francisco's [[KSFO]], where there are fewer pilots flying around.

== Servers ==
'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you, has the lowest latency (ping time) or is the least busy.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Location
! style="background:#efefef" |[http://mpserver15.flightgear.org Tracked]
! style="background:#efefef" |Maintainer
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Comments
|-
|mpserver01.flightgear.org
|Germany
|[http://mpserver15.flightgear.org Yes]
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Los Angeles, USA
|
|Lloyd Stevens
|ls4680
|ls4680
|
|-
|mpserver03.flightgear.org
|Germany
|No
|Hergen
|
|
|
|-
|mpserver04.flightgear.org
|UK
|No
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|[http://mpserver15.flightgear.org Yes]
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Berlin, Germany
|[http://mpserver15.flightgear.org Yes]
|Sven Teichmann
|
|D-SAMI
|Unlimited traffic
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|
|Tom Betka
|TB
|
|Offline
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|No
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, mostly short pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|
|Daniel Vigano
|Fauchi95
|
|Offline
|-
|mpserver10.flightgear.org
|Montpellier, France
|No
|Alexis Bory
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|No
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|[http://mpserver12.flightgear.org MPServer12]
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|No
|Charles Ingels
|charles
|cbz-026
|
|-
|mpserver14.flightgear.org
|Zurich, Switzerland
|[http://mpserver15.flightgear.org Yes]
|Yves Sablonier
|gral
|gral
|
|-
|mpserver15.flightgear.org
|North Point, Hong Kong
|[http://mpserver15.flightgear.org Yes]
|Hazuki Amamiya
|Hazuki
|Hazuki
|
|-
|mpserver16.flightgear.org
|Texas, USA
|[http://mpserver15.flightgear.org Yes]
|Rob Dosogne
|truthsolo
|truthsolo
|
|-
|mpserver17.flightgear.org
|Cluj, Romania
|
|Marius
|tuxum
|tuxum
|Offline
|-
|mpserver18.flightgear.org
|Germany
|[http://mpserver15.flightgear.org Yes]
|
|
|
|
|}
''Information as at 2013-05-31''

Use [http://mpserver16.flightgear.org/ this], [http://mpmap01.flightgear.org/mpstatus/ this] or [http://flightgear.mxchange.org/mpstatus/ this] link to check if the MP servers are online. As of FlightGear 2.10.0, the in-sim dialog only displays servers that are available.

Geographic locations of the servers are also available at [http://goo.gl/maps/jBwUd Google Maps].

If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].

=== Multiplayer map ===
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at [http://mpmap01.flightgear.org mpmap01] and/or [http://mpmap02.flightgear.org mpmap02]. You will also find this useful to check that you are successfully connecting to the server.

== Getting online ==
As of FlightGear 2.4.0, multiplayer settings can be accessed via the in-sime Multiplayer menu. This is by far the easiest way to get online, but in some cases the methods mentioned below may be prefered.

=== Using the Windows launcher / FGRun ===
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
# Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|FGRun]].
# On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft.
#* '''Callsign:''' of your choice. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether it is already in use or not. Do not pick a callsign that is already used!
#* '''Hostname:''' enter <tt>mpserverXX.flightgear.org</tt> (with <tt>XX</tt> being the [[#Servers|server number]]).
#* '''In/Out:''' set both ports to 5000.
# Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). Once FlightGear has started, you will notice chat messages that say "Hello" indicating pilots that are online and then as they join (you can change this message by editing the <tt><chat type="string">Hello</chat></tt> line in <tt>[[$FG ROOT]]/preferences.xml</tt>). You may wish to use a different server (i.e. "Hostname" entry).

For more advanced settings, the <tt>Advanced > Network</tt> tab can be opened. You are able to remove the in or out lines only through this method for example.

=== Using fgfs from the command line ===
First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,5000
--callsign=anything

where 5000 is the port number the server is listening on (which is 5000 for the official servers).

If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:

--multiplay=in,10,your.ip.address,portnumber

where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

''If you are using fgrun, please note that fgrun expects you to enter a valid (non-loopback, i.e. not 127.0.0.1) IP address or hostname for the local network interface.''

Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

==== Now, going more slowly for those who are completely lost... ====
Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

* Under '''Linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP or later''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiple connections per computer ==
It is possible to run multiple FlightGear instances on a single computer and connect them all to the multiplayer network. However, this requires some extras to keep in mind:
* both instances use the same out-port.
* one instance uses in port=5001, the other port 5002.
* and of course should both instances have unique callsigns.

== Multiplayer chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Multiplayer > Pilot list dialog and click the ignore button next to the pilot's call sign. As of FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear 2.4.0 and later it will additionally prevent his aircraft from appearing.

== Related content ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]

[[Category:Multiplayer]]
[[Category:Howto|Multiplayer]]

[[de:Howto: Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-08T22:21:16Z

Las: /* Modifications */

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]

== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>

== Modifications ==
*I received 2 error when compiling fgms-0-x/src/server/fg_util.cxx because integer constants were too large so just convert them to real.

The commands below will automatically make the above modifications.
<pre>
sed -i '' -e "s|1125899906842624)|1125899906842624.)|" ../fgms-0-x/src/server/fg_util.cxx
sed -i '' -e "s|1099511627776)|1099511627776.)|" ../fgms-0-x/src/server/fg_util.cxx
</pre>

== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines I changed in /etc/fgms.conf
<pre>
server.name = newmpserver
server.address = 64.69.45.88
server.logfile = /var/log/fgms.log
server.daemon = true
#relay.host = mpserver01.flightgear.org
#relay.port = 5000
server.out_of_reach = 10000
</pre>

== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-08T22:19:18Z

Las: /* Modifications */

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]

== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>

== Modifications ==
*I received two errors when building. malloc.h appears to be depreciated on FreeBSD and is replaced another already included source file so just comment it out.
*Also I received compile error on one file because integer constants were too large so just convert them to real.

The commands below will automatically make the above modifications.
<pre>
sed -i '' -e "s|1125899906842624)|1125899906842624.)|" ../fgms-0-x/src/server/fg_util.cxx
sed -i '' -e "s|1099511627776)|1099511627776.)|" ../fgms-0-x/src/server/fg_util.cxx
</pre>

== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines I changed in /etc/fgms.conf
<pre>
server.name = newmpserver
server.address = 64.69.45.88
server.logfile = /var/log/fgms.log
server.daemon = true
#relay.host = mpserver01.flightgear.org
#relay.port = 5000
server.out_of_reach = 10000
</pre>

== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-08T16:07:41Z

Las: /* Modifications */

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see [[Howto:Set up a multiplayer server]]

== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>

== Modifications ==
*I received two errors when building. malloc.h appears to be depreciated on FreeBSD and is replaced another already included source file so just comment it out.
*Also I received compile error on one file because integer constants were too large so just convert them to real.

The commands below will automatically make the above modifications.
<pre>
sed -i '' -e "s|#include <malloc.h>|//#include <malloc.h>|" ../fgms-0-x/src/libcli/libcli.cxx
sed -i '' -e "s|1125899906842624|1125899906842624.|" ../fgms-0-x/src/server/fg_util.cxx
sed -i '' -e "s|1099511627776|1099511627776.|" ../fgms-0-x/src/server/fg_util.cxx
</pre>

== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>

== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines I changed in /etc/fgms.conf
<pre>
server.name = newmpserver
server.address = 64.69.45.88
server.logfile = /var/log/fgms.log
server.daemon = true
#relay.host = mpserver01.flightgear.org
#relay.port = 5000
server.out_of_reach = 10000
</pre>

== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

[[Category:Multiplayer]]

Howto:Set up a multiplayer server

2013-07-06T01:25:35Z

Las: /* Pre-Requisites */

This page is dedicated to providing a short overview about installing the [[FlightGear Multiplayer Server]] ('fgms'). The reader is assumed to be reasonably familiar with working in a Unix/Linux shell environment.

== Pre-Requisites ==
* A computer running a variant of *nix to compile and host the server. Speed of the machine isn't of great consequence as the protocol is a multiplexer which doesn't require much processing grunt.
** For specific documentation for setting up on FreeBSD see http://wiki.flightgear.org/Howto:Set_up_a_multiplayer_server_on_FreeBSD
* direct/physical or remote access to the server (i.e. SSH/telnet, a conventional web hosting package will usually '''not''' be sufficient!)-suitable hosting packages are: dedicated root servers, virtual private servers, shell servers - for a collection of '''free''' shell account providers that may be suitable for fgms, see [[Free Shell Providers]] (you may want to check this out if you are interested in running fgms but don't have hosting yet)
* if the server is meant to be a public internet server: an internet connection, featuring sufficient upstream/downstream capabilities (see below for details concerning bandwidth requirements).
* firewall policies will need to be set up to allow for incoming and outgoing UDP traffic for the corresponding ports, the same applies to the administration port (TCP)
* permission to run unattended background processes (this may only be an issue with certain limited hosting packages)
* a working GNU toolchain including gcc/g++ (compiler), make & cmake
* fgms source code, currently version 0.10.23
* about 5-10 MB of hard disk space (mainly required for building the binary)

== Traffic & Bandwidth Considerations ==

Note: Currently (May 2008), the server code basically boils down to a packet multiplexer (i.e. most data is -unconditionally- transmitted to all 'active' clients), which may thus create considerable amounts of traffic; this ought to be taken into consideration due to bandwidth limitations in most hosting packages (i.e. '''fgms may create considerable amounts of traffic!'''). For basic calculations: inbound traffic is 25 Kilobit per second while outbound is 25 Kbits per second for each plane/client that can 'see' another.

By default, assuming a 10hz update interval, each active fgfs client will currently cause I/O traffic of approximately 5 kbytes/sec (one update consuming ~500 bytes) [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

As client updates have to be propagated to all other active clients by the server, this number has to be multiplied by the number of active clients -1 (i.e. clients within a configurable range, minus the originating client).
In addition, the fgms system allows for traffic updates to be sort of 'mirrored' on (relayed to) other configurable multiplayer/relay servers.

This feature makes it possible for users/clients to use an arbitrary server (with acceptable latency), but still see clients/vehicles connected to different servers. Thus, such relay servers may additionally increase inbound/outbound traffic considerably as all traffic is mirrored/propagated to such relays.

Having more servers should actually decrease the load on each server in high load situations, i.e. when most of the clients are within range of each other. See this
[http://www.gidenstam.org/FlightGear/fgms/fgms_bandwidth_estimates.txt brief note on the theoretical bandwidth behaviour of fgms.]

=== Facts ===
In March 2008, the main fgms multiplayer server (pigeond.net) was reported to consume approximately 15 gb of bandwidth per '''day''', with an average throughput of 200 kB/sec and peak loads of up to ~ 650 kB/sec [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16016.html].

During the same month (the much less used but interconnected) mpserver06.flightgear.org had on average 742 MB incoming and 688 MB outgoing traffic per day (i.e. 72 kbit/sec respective 66 kbit/sec on average).

In September 2009, mpserver 05 had a massive peak bandwidth of 1.0 MB/sec. Average bandwidth consumed was about 9 GB of bandwidth per day. The average bandwidth usage per day is climbing due to more users moving from 02 to 05.

=== Reducing bandwidth requirements ===
Total network traffic is mainly determined by the number of active clients that 'see eachother' and configured mirrors.
If traffic considerations are relevant, the following options exist to reduce overall server/network load:

* configure a relatively low "server.out_of_reach" value, so that clients outside a certain range are not provided with updates (usually about 100 nm on the main server network)
* for virtual gatherings (i.e. fly-ins), have clients use airports and places that do not have lots of other traffic (i.e. in other words, avoid places like standard airports such as KSFO)
* avoid the use of unnecessary relay servers
* if you are not interested in your server being publicly available, only share its address with your friends privately
* for local testing/development purposes, you may want to run only a private fgms session, that may be specific to your LAN or even computer.

=== Hosting Packages known to be suitable for fgms hosting ===
(yet to be filled in)

== Getting & Building fgms ==

* You will need the build tools cmake and make, and also g++ to compile the fgms application. These can usually be found in the package manager for most the common Linux distributions. You will also need the git client to fetch the source code from the repository, if you plan to download it from the command line interface (see below).

* Once the build tools are installed on your machine, create a directory to hold the source code. This could be named anything, such as fgms. Create it in your user home directory. Note that this WILL NOT be the directory where the program will be compiled.

* Now 'cd' into the directory you just made, where you will run the command to fetch the source code from the git repository (see below).

* To download the latest stable version via HTTP, you can use direct your browse to the URL http://gitorious.org/fgms/fgms-0-x/. Download and unzip the source code, and place it in the directory you created above.

* To download a file directly to your server from an ssh session, you can use git tools with the following command:

$git clone git://gitorious.org/fgms/fgms-0-x.git

== Compiling FGMS ==

NOTE: In general, on any current machine this process should not take longer than about 60 seconds.

* Once you have the source code, 'cd' into the ~/fgms/fgms-0-x/ directory and note the presence of the CMakeLists.txt file and the README.cmake file. Open the README.cmake file and take a minute to read it over. Also, note the path to the CMakeLists.txt file, as you will need this in the following steps.

* Now create a build-fgms directory in your home directory, and 'cd' into it. From inside the ~/build-fgms/ directory, run the cmake command using the path to the CMakeLists.txt as an argument. For example: cmake /home/<user_name>/fgms/fgms-0-x/

* Once the build finishes, you can either run the "cmake --build ..." command as shown in the README.cmake file, or you can simply use "make" to build the program.

* Once the compilation process finishes, you need to install the program using "make install" (as user), or you can also install as root.

* Once the program has been installed, you need to copy the fgms_example.conf file from the /fgms/fgms-0-x/src/server directory, into the build-fgms directory. To do this from inside the /fgms/fgms-0-x/src/server directory, you can use this command: cp ./fgms_example.conf ~/build-fgms/

* Now 'cd' into the build-fgms directory, and rename the file you just copied as "fgms.conf" so that fgms can find the proper configuration.

== Setting up the config file ==

At this point you should have a working 'fgms' binary in the build-fgms directory. If the server will be offline or for private use (i.e. LAN-only, please comment out the relay servers section. This will save bandwidth from the server being consumed.

* Edit the fgms.conf file according to the instructions found elsewhere on this page, then save and close the file.

== Running FGMS for the first time ==

In addition to its configuration file, FGMS supports a number of configuration parameters that can be passed at startup (and that will by default override any configuration file settings), to get a summary of supported parameters, you may want to run:
$ ./fgms --help

Which should present you with the following output:

<pre>
options are:
-h print this help screen
-a PORT listen to PORT for telnet
-c config read 'config' as configuration file
-p PORT listen to PORT
-t TTL Time a client is active while not sending packets
-o OOR nautical miles two players must be apart to be out of reach
-l LOGFILE Log to LOGFILE
-v LEVEL verbosity (loglevel) in range 1 (few) and 5 (much)
-d do _not_ run as a daemon (stay in foreground)
-D do run as a daemon

the default is to run as a daemon, which can be overridden in the
config file.
commandline parameters always override config file options
</pre>

After having finished the fgms configuration, you can try running fgms and start up fgfs to use the new server.
If you'd like to make it a public server, you can simply use your external (public) IP address to set up the multiplayer in fgfs.

== Related content ==
* [[Howto: Multiplayer|Multiplayer howto]]
* [[MPmap]]

[[Category:Multiplayer]]
[[Category:Howto|Set up a multiplayer server]]
[[fr:Installer un serveur multijoueur]]

Howto:Set up a multiplayer server on FreeBSD

2013-07-06T01:23:44Z

Las:

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
For generic setup information see http://wiki.flightgear.org/Howto:Set_up_a_multiplayer_server
== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>
== Modifications ==
*I received two errors when building. malloc.h appears to be depreciated on FreeBSD and is replaced another already included source file so just comment it out.
*Also I received compile error on one file because integer constants were to large so just convert them to real.

The commands below will automatically make the above modifications.
<pre>
sed -i '' -e "s|#include <malloc.h>|//#include <malloc.h>|" ../fgms-0-x/src/libcli/libcli.cxx
sed -i '' -e "s|1125899906842624|1125899906842624.|" ../fgms-0-x/src/server/fg_util.cxx
sed -i '' -e "s|1099511627776|1099511627776.|" ../fgms-0-x/src/server/fg_util.cxx
</pre>
== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>
== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines I changed in /etc/fgms.conf
<pre>
server.name = newmpserver
server.address = 64.69.45.88
server.logfile = /var/log/fgms.log
server.daemon = true
#relay.host = mpserver01.flightgear.org
#relay.port = 5000
server.out_of_reach = 10000
</pre>
== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

Howto:Set up a multiplayer server on FreeBSD

2013-07-06T01:22:06Z

Las:

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (v0.11.0 as of July 2013) on FreeBSD 9.0-STABLE.
== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>
== Modifications ==
*I received two errors when building. malloc.h appears to be depreciated on FreeBSD and is replaced another already included source file so just comment it out.
*Also I received compile error on one file because integer constants were to large so just convert them to real.

The commands below will automatically make the above modifications.
<pre>
sed -i '' -e "s|#include <malloc.h>|//#include <malloc.h>|" ../fgms-0-x/src/libcli/libcli.cxx
sed -i '' -e "s|1125899906842624|1125899906842624.|" ../fgms-0-x/src/server/fg_util.cxx
sed -i '' -e "s|1099511627776|1099511627776.|" ../fgms-0-x/src/server/fg_util.cxx
</pre>
== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>
== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines I changed in /etc/fgms.conf
<pre>
server.name = newmpserver
server.address = 64.69.45.88
server.logfile = /var/log/fgms.log
server.daemon = true
#relay.host = mpserver01.flightgear.org
#relay.port = 5000
server.out_of_reach = 10000
</pre>
== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

Howto:Set up a multiplayer server on FreeBSD

2013-07-06T01:18:57Z

Las: Created page with "FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (as of July 2013) on FreeBSD..."

FlightGear Multiplayer did not build directly on FreeBSD without a couple of modifications. Below are the steps to build the lastest *nix release (as of July 2013) on FreeBSD 9.0-STABLE.
== Download ==
If you do not have git installed you must install it first
<pre>
cd /usr/ports/devel/git
make install clean
</pre>
Download the latest version of fgms and create a build directory
<pre>
git clone git://gitorious.org/fgms/fgms-0-x.git
mkdir fgms-build
cd fgms-build/
</pre>
== Modifications ==
*I received two errors when building. malloc.h appears to be depreciated on FreeBSD and is replaced another already included source file so just comment it out.
*Also I received compile error on one file because integer constants were to large so just convert them to real.

The commands below will automatically make the above modifications.
<pre>
sed -i '' -e "s|#include <malloc.h>|//#include <malloc.h>|" ../fgms-0-x/src/libcli/libcli.cxx
sed -i '' -e "s|1125899906842624|1125899906842624.|" ../fgms-0-x/src/server/fg_util.cxx
sed -i '' -e "s|1099511627776|1099511627776.|" ../fgms-0-x/src/server/fg_util.cxx
</pre>
== Building ==
<pre>
cmake ../fgms-0-x
cmake --build .
make install
cp -n ../fgms-0-x/contrib/etc/fgms_production.skel.conf /etc/fgms.conf
</pre>
== Configuring ==
Make sure you edit the installed configuration file /etc/fgms.conf
Shown below are the lines I changed in /etc/fgms.conf
<pre>
server.name = newmpserver
server.address = 64.69.45.88
server.logfile = /var/log/fgms.log
server.daemon = true
#relay.host = mpserver01.flightgear.org
#relay.port = 5000
server.out_of_reach = 10000
</pre>
== Running ==
<pre>
fgms -c /etc/fgms.conf
processing /etc/fgms.conf
# using logfile /var/log/fgms.log
05.07.2013 18:16:38 # This is newmpserver
05.07.2013 18:16:38 # FlightGear Multiplayer Server v0.11.0 started
05.07.2013 18:16:38 # using protocol version v1.1 (LazyRelay enabled)
05.07.2013 18:16:38 # listening to port 5000
05.07.2013 18:16:38 # telnet port 5001
05.07.2013 18:16:38 # admin port 5002
05.07.2013 18:16:38 # using logfile /var/log/fgms.log
05.07.2013 18:16:38 # listening on 64.
05.07.2013 18:16:38 # tracking is disabled.
05.07.2013 18:16:38 # I have 1 relays
05.07.2013 18:16:38 # relay mpserver14.flightgear.org:5000
05.07.2013 18:16:38 # I have 0 crossfeeds
05.07.2013 18:16:38 # I have 2 blacklisted IPs
05.07.2013 18:16:38 # Files: exit=[/tmp/fgms_exit] stat=[/tmp/fgms_stat]
</pre>

TerraGear

2013-06-15T07:05:49Z

Las: /* Pre-compiled builds */

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].

:*[[TerraGear_Installation_for_Windows|Detailed Windows Installation Instructions]]

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** [http://www.cgal.org/ CGAL] - For high accuracy geometric calculations
** [http://www.gdal.org/ libgdal]

=== Building ===
cmake . [options]
make install
<tt>cmake</tt> options:
-DCMAKE_PREFIX_PATH="/path/to/lib/install/prefix"

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> <BR>See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear in Ubuntu 910 (32- or 64-bit)]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:TerraGear| ]]

[[es:TerraGear]]
[[fr:TerraGear]]

TerraGear Installation for Windows

2013-06-15T07:02:03Z

Las: Created page with "TerraGear build for Windows requires several libraries, some which must be downloaded separately. === TerraGear Windows Build=== [http://flightgear.simpits.org:8080/job/Terr..."

TerraGear build for Windows requires several libraries, some which must be downloaded separately.

=== TerraGear Windows Build===
[http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Download the Latest TerraGear Windows Build Archive] from the [[http://wiki.flightgear.org/FlightGear_Build_Server|FlightGear Build Server]].

Select a logical location on your system for TerraGear. It can be anywhere but for clarity the instruction below are for C:\Program Files

Extract the TerraGear Archive to a temporary location on your system. In the examples below the Archive was extracted to C:\Archive

* Move C:\Archive\install\msvc100\TerraGear\ to C:\Program Files
* Move C:\Archive\CGAL\auxiliary\gmp\lib\libgmp-10.dll to C:\Program Files\TerraGear\bin\
* Move C:\Archive\CGAL\auxiliary\gmp\lib\libmpfr-4.dll to C:\Program Files\TerraGear\bin\
* Move C:\Archive\gdal\bin\gdal110dev.dll to C:\Program Files\TerraGear\bin\

=== Required Libraries ===
[http://flightgear.simpits.org:8080/job/CGAL-Win-CMake/ws/install/msvc100/CGAL/bin/CGAL-vc100-mt-4.1.dll Download the CGAL library] from http://flightgear.simpits.org:8080/job/CGAL-Win-CMake/ws/install/msvc100/CGAL/bin/ and save the dll into C:\Program Files\TerraGear\bin\

[http://download.osgeo.org/proj/proj446_win32_bin.zip Download the Cartographic Projections Library] from http://trac.osgeo.org/proj/
You only need one file, proj.dll, from this archive. Save proj.dll into to C:\Program Files\TerraGear\bin\

=== Results ===
If you chose C:\Progam Files for your location when you are done you should have following directory structure.
* C:\Progam Files\TerraGear\bin
:* (contains 15 .exe files and 5 .dll files)
* C:\Progam Files\TerraGear\share\TerraGear
:* (contains 15 .txt files)

If you use [[TerraGear_GUI|TerraGear GUI]] its "TerraGear root" will be C:\Progam Files\TerraGear