FlightGear wiki - User contributions [en]

FlightGear Newsletter December 2014

2014-12-29T21:16:10Z

JazzTp: /* Media */

{{Newsletter-header|December 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Events}}<br/>
|}
</div>

== Development news ==

== In the hangar ==
The EC135 got now finally a major update in FGAddon for FlightGear 3.4.0: simulating now the EC135 P2; complete accurate and detailed new 3d-model; complete flightdeck with dual and single analog panel - digtal panels coming; Rembrandt compatible; latest shaders; accurate and realistic fdm matching 90% POH values for AEO, OEI, Airspeed; flight handling based on tech reports; many different configurations possible; influence of configurations to weight and CoG; and some more things. Please see this video to start the engines, as autostart and }-key isn't working yet. Please also see the FGWiki page for additional informations.

{{#ev:youtube|CkMERfFOgtw}}

== Scenery corner ==
2 medium size German airports have been developed and uploaded to terrasync this month: EDLW(Dortmund) and EDDG(Münster Osnabrück)

== Events ==

== Media ==

[http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640 '''A new thread on the forum''' (http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640)] has been started inviting FlightGear users to share their '''3D anaglyph pictures'''. The first post includes the link to an [http://imgur.com/a/IVwVI '''online album''' (http://imgur.com/a/IVwVI)], and the post itself carries the album description which gives some hints for anybody new to 3D anaglyph.

[https://www.youtube.com/watch?v=VvxzmYOW-T8 '''A new video clip''' (https://www.youtube.com/watch?v=VvxzmYOW-T8)] has been published in YouTube showing [http://pattenflightgear.wifeo.com/textures-du-terrain.php '''impressive textures around LFKJ''' (http://pattenflightgear.wifeo.com/textures-du-terrain.php)]. The chosen aircraft is the '''JA37-Viggen''', developed by '''Icetail''' aka '''Nikolai'''. Although he already achieved a very good aircraft with nice systems and a great FDM, he is very actively implementing further improvements (you might want to read the latest changelog items!). So, if you want to fly it, be sure to grab the latest release from [https://sites.google.com/site/fghangar/ '''Just another FlightGear hangar''' (https://sites.google.com/site/fghangar/]).

{{#ev:youtube|VvxzmYOW-T8}}

[[Category:FlightGear Newsletter|2014 12]]

FlightGear Newsletter December 2014

2014-12-29T20:45:48Z

JazzTp: /* Media */

{{Newsletter-header|December 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Events}}<br/>
|}
</div>

== Development news ==

== In the hangar ==
The EC135 got now finally a major update in FGAddon for FlightGear 3.4.0: simulating now the EC135 P2; complete accurate and detailed new 3d-model; complete flightdeck with dual and single analog panel - digtal panels coming; Rembrandt compatible; latest shaders; accurate and realistic fdm matching 90% POH values for AEO, OEI, Airspeed; flight handling based on tech reports; many different configurations possible; influence of configurations to weight and CoG; and some more things. Please see this video to start the engines, as autostart and }-key isn't working yet. Please also see the FGWiki page for additional informations.

{{#ev:youtube|CkMERfFOgtw}}

== Scenery corner ==
2 medium size German airports have been developed and uploaded to terrasync this month: EDLW(Dortmund) and EDDG(Münster Osnabrück)

== Events ==

== Media ==

[http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640 '''A new thread on the forum''' (http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640)] has been started inviting FlightGear users to share their '''3D anaglyph pictures'''. The first post includes the link to an [http://imgur.com/a/IVwVI '''online album''' (http://imgur.com/a/IVwVI)], and the post itself carries the album description which gives some hints for anybody new to 3D anaglyph.

[https://www.youtube.com/watch?v=VvxzmYOW-T8 '''A new video clip''' (https://www.youtube.com/watch?v=VvxzmYOW-T8)] has been published in YouTube showing '''nice textures around LFKJ'''. The chosen aircraft is the '''JA37-Viggen''', developed by '''Icetail''' aka '''Nikolai'''. Although he already achieved a very good aircraft with nice systems and a great FDM, he is very actively implementing further improvements (you might want to read the latest changelog items!). So, if you want to fly it, be sure to grab the latest release from [https://sites.google.com/site/fghangar/ '''Just another FlightGear hangar''' (https://sites.google.com/site/fghangar/]).

{{#ev:youtube|VvxzmYOW-T8}}

[[Category:FlightGear Newsletter|2014 12]]

FlightGear Newsletter December 2014

2014-12-29T20:33:46Z

JazzTp: /* Media */

{{Newsletter-header|December 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Events}}<br/>
|}
</div>

== Development news ==

== In the hangar ==
The EC135 got now finally a major update in FGAddon for FlightGear 3.4.0: simulating now the EC135 P2; complete accurate and detailed new 3d-model; complete flightdeck with dual and single analog panel - digtal panels coming; Rembrandt compatible; latest shaders; accurate and realistic fdm matching 90% POH values for AEO, OEI, Airspeed; flight handling based on tech reports; many different configurations possible; influence of configurations to weight and CoG; and some more things. Please see this video to start the engines, as autostart and }-key isn't working yet. Please also see the FGWiki page for additional informations.

{{#ev:youtube|CkMERfFOgtw}}

== Scenery corner ==
2 medium size German airports have been developed and uploaded to terrasync this month: EDLW(Dortmund) and EDDG(Münster Osnabrück)

== Events ==

== Media ==

[http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640 '''A new thread on the forum''' (http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640)] has been started inviting FlightGear users to share their '''3D anaglyph pictures'''. The first post includes the link to an [http://imgur.com/a/IVwVI '''online album''' (http://imgur.com/a/IVwVI)], and the post itself carries the album description which gives some hints for anybody new to 3D anaglyph.

[https://www.youtube.com/watch?v=VvxzmYOW-T8 '''A new video clip''' (https://www.youtube.com/watch?v=VvxzmYOW-T8)] has been published in YouTube showing '''nice textures around LFKJ'''. The chosen aircraft is the '''JA37-Viggen'''. Although it is already a very good aircraft with nice systems and great FDM, it is being very actively improved by '''Icetail''' aka '''Nikolai''' (you might want to read the latest changelog items!), so if you want to fly it be sure to grab the latest release from [https://sites.google.com/site/fghangar/ '''Just another FlightGear hangar''' (https://sites.google.com/site/fghangar/]).

{{#ev:youtube|VvxzmYOW-T8}}

[[Category:FlightGear Newsletter|2014 12]]

FlightGear Newsletter December 2014

2014-12-29T20:26:16Z

JazzTp: /* Media */

{{Newsletter-header|December 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Events}}<br/>
|}
</div>

== Development news ==

== In the hangar ==
The EC135 got now finally a major update in FGAddon for FlightGear 3.4.0: simulating now the EC135 P2; complete accurate and detailed new 3d-model; complete flightdeck with dual and single analog panel - digtal panels coming; Rembrandt compatible; latest shaders; accurate and realistic fdm matching 90% POH values for AEO, OEI, Airspeed; flight handling based on tech reports; many different configurations possible; influence of configurations to weight and CoG; and some more things. Please see this video to start the engines, as autostart and }-key isn't working yet. Please also see the FGWiki page for additional informations.

{{#ev:youtube|CkMERfFOgtw}}

== Scenery corner ==
2 medium size German airports have been developed and uploaded to terrasync this month: EDLW(Dortmund) and EDDG(Münster Osnabrück)

== Events ==

== Media ==

[http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640 '''A new thread on the forum''' (http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640)] has been started inviting FlightGear users to share their '''3D anaglyph pictures'''. The first post includes the link to an [http://imgur.com/a/IVwVI '''online album''' (http://imgur.com/a/IVwVI)], and the post itself carries the album description which gives some hints for anybody new to 3D anaglyph.

[https://www.youtube.com/watch?v=VvxzmYOW-T8 '''A new video clip''' (https://www.youtube.com/watch?v=VvxzmYOW-T8)] has been published in YouTube showing '''nice textures around LFKJ'''. The chosen aircraft is the '''JA37-Viggen'''. Although it is already a very good aircraft with nice systems and great FDM, it is being very actively improved by '''Icetail''' aka '''Nikolai''' (you might want to read the latest changelog items!), so if you want to fly it be sure to grab the latest release from [https://sites.google.com/site/fghangar/ '''Just another FlightGear hangar''' (https://sites.google.com/site/fghangar/]).

[[Category:FlightGear Newsletter|2014 12]]

FlightGear Newsletter December 2014

2014-12-29T20:20:01Z

JazzTp: /* Media */

{{Newsletter-header|December 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|Events}}<br/>
|}
</div>

== Development news ==

== In the hangar ==
The EC135 got now finally a major update in FGAddon for FlightGear 3.4.0: simulating now the EC135 P2; complete accurate and detailed new 3d-model; complete flightdeck with dual and single analog panel - digtal panels coming; Rembrandt compatible; latest shaders; accurate and realistic fdm matching 90% POH values for AEO, OEI, Airspeed; flight handling based on tech reports; many different configurations possible; influence of configurations to weight and CoG; and some more things. Please see this video to start the engines, as autostart and }-key isn't working yet. Please also see the FGWiki page for additional informations.

{{#ev:youtube|CkMERfFOgtw}}

== Scenery corner ==
2 medium size German airports have been developed and uploaded to terrasync this month: EDLW(Dortmund) and EDDG(Münster Osnabrück)

== Events ==

== Media ==

[http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640 '''A new thread on the forum''' (http://forum.flightgear.org/viewtopic.php?f=19&t=24917&p=227640)] has been started inviting FlightGear users to share their '''3D anaglyph pictures'''. The first post includes the link to an [http://imgur.com/a/IVwVI '''online album''' (http://imgur.com/a/IVwVI)], and the post itself carries the album description which gives some hints for anybody new to 3D anaglyph.

[https://www.youtube.com/watch?v=VvxzmYOW-T8 '''A new video clip''' (https://www.youtube.com/watch?v=VvxzmYOW-T8)] has been published in YouTube showing '''nice textures around LFKJ'''. The chosen aircraft is the '''JA37-Viggen'''. Although it is already a very good aircraft with nice systems and great FDM, it is being very actively improved by '''Icetail''' aka '''Nikolai''', so if you want to fly it be sure to grab the latest release from [https://sites.google.com/site/fghangar/ '''Just another FlightGear hangar''' (https://sites.google.com/site/fghangar/]).

[[Category:FlightGear Newsletter|2014 12]]

FlightGear Newsletter December 2014

2014-12-20T22:13:27Z

JazzTp:

Howto:Multiplayer

2014-12-18T19:28:25Z

JazzTp: /* Problems associated with specific Internet Service Providers */

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.

== Getting online ==
[[File:Multiplayer settings dialog.jpg|thumb|300px|Multiplayer settings dialog]]
As of FlightGear 2.4.0, multiplayer settings can be accessed via the in-sime Multiplayer menu. All you need to do is enter a callsign and select a server from the menu. Press Connect to go online.

This is by far the easiest way to get online, but in some cases the methods mentioned below may be prefered.

'''Before starting tests''', you might want to check the section ''Problems associated with specific Internet Service Providers'' below in this page.

=== Using the 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.
#* '''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

{{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O port to the corresponding port of the other instance:
<syntaxhighlight lang="bash">
fgfs --multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=one &
fgfs --multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=two &
</syntaxhighlight>
You can use this kind of setup to test multiplayer related features or troubleshoot multiplayer related bug reports that may be otherwise hard to reproduce over MP, because you don't normally see what other people are doing in terms of configuring MP/fgfs.
[[File:Direct-p2p-multiplayer-setup.png|800px|Screen shots demonstrating a "peer-to-peer" setup between two fgfs instances running on the same machine via localhost/loopback (127.0.0.1) without any fgms/multiplayer server being involved]]
You can add an arbitrary number of channels to mirror your flight onto other servers, e.g. to a private fgms server using '''<nowiki>--multiplay=out,10,my.private.server.ip,5000</nowiki>'''.

Additionally, the "in"-argument above tells FG to listen '''only''' on the loopback/local interface - it will not receive packets arriving on the other network interface(s). If you want to also bind to other interfaces, just omit the IP address by using '''<nowiki>--multiplay=in,10,,5000</nowiki>'''.
}}

''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}}

{{note|Multiplayer chat is not supported by FlightGear 0.9.10 or older.}}

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.

== 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.

== 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.

== Servers ==
{{note|The multiplayer servers are interconnected. With few exceptions 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.}}
{{tip|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.}}

{| 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
|-
|fg.noahbuscher.com
|US
|{{no}}
|Noah Buscher
|Noah
|Noah
|May be merged with main servers in the near future.
|-
|-
|mpserver01.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Los Angeles, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Lloyd Stevens
|ls4680
|ls4680
|
|-
|mpserver03.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Hergen
|
|
|
|-
|mpserver04.flightgear.org
|UK
|{{no}}
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Berlin, Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Sven Teichmann
|
|D-SAMI
|Unlimited traffic
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|{{n/a}}
|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
|{{n/a}}
|Daniel Vigano
|Fauchi95
|
|Offline
|-
|mpserver10.flightgear.org
|Montpellier, France
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Alexis Bory
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|{{no}}
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|{{yes|[http://mpserver12.flightgear.org mpserver12]}}
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|{{no}}
|Charles Ingels
|charles
|cbz-026
|
|-
|mpserver14.flightgear.org
|Zurich, Switzerland
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Yves Sablonier
|gral
|gral
|
|-
|mpserver15.flightgear.org
|North Point, Hong Kong
|{{n/a}}
|Hazuki Amamiya
|Hazuki
|Hazuki
|This is FGTracker, not a multiplayer server
|-
|mpserver16.flightgear.org
|Kansas City, Missouri, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Rob Dosogne
|truthsolo
|truthsolo
|
|-
|mpserver17.flightgear.org
|Cluj, Romania
|{{n/a}}
|Marius
|tuxum
|tuxum
|Offline
|-
|mpserver18.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|
|
|
|
|}
''Information as at 2014-01-04''

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]].

== Problems associated with specific Internet Service Providers ==

'''Fibertel Argentina'''

It has been reported '''December 2014''' that UDP connection through port 5000 is not possible. Fibertel Argentina users do not have full access to the modem configuration at the moment, they have to pass through a ''very limited'' interface on the Fibertel web site, only aimed at allowing operations like switching on/off the wifi radio or switching between NAT router mode and bridge mode (and at the moment a bug made users unable to submit any configuration changes).
After various hours of tests by the user with and without Fibertel staff at the phone with the modem in NAT router mode and in bridge mode, after a supervisor decided to remotely flash the modem (Motorola) with a recent firmware and yet noticed strange behaviour and sent tech staff to replace the modem with a simpler one (another Motorola model with no wifi), after testing with it in bridge mode with tech staff at the phone, the user sought for help [http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034 in the forum] and finally '''a temporary standalone instance of the Multiplayer server software''' (located in Canada) was activated and '''the user was able to connect normally through all the tested ports (5001, 5002, 5003, 5507) but not through port 5000 which is the only available port in any FlightGear Multiplayer server at the moment'''. Through another Internet Service Provider (Speedy ADSL) the user could connect with no problems to port 5000 of any Multiplayer server.

Facing this evidence, Fibertel Argentina technical staff ''finally'' admitted: "It's not the modem, it's the network, our network uses port 5000 for setup purposes, it should be open for the user but it might not be fully functional". '''This is reported here to avoid other users a similar 60-70 hours time loss.''' The users reports he asked them with energy to stop filtering port 5000, the answer was that because of the implications that was not an option.

Port 5000 is unofficially associated both with FlightGear and the UPnP protocol.
However, it has been observed (discussion of [https://code.google.com/p/flightgear-bugs/issues/detail?id=1617&q=-Type%3DFeatureRequest%20-status%3ATesting&sort=-id&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone issue 1617]) that '''the fact that Fibertel Argentina is using port 5000 for network setup purposes shouldn't imply that they are filtering packets: ''"it should really only be when the packet has reached its destination that the port number has any meaning at all"'''''.

Forum thread full link: http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034).

Reported issue 1617 full link: https://code.google.com/p/flightgear-bugs/issues/detail?id=1617&q=-Type%3DFeatureRequest%20-status%3ATesting&sort=-id&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone

Besides investigating about '''possible workarounds(?)''' (port forwarding through UDP bidirectional tunnelling) which might or might not add too much network latency or CPU load or constitute a misuse of special purposes networks, the user suggested diversification of port numbers (''"offering two possible port numbers could mean offering twice the chances to connect to the Multiplayer network and would constitute a reasonable prevention measure of part of the possible connection problems of FlightGear users over the internet"'').

However, coding work on the server software is not priority at the moment, and any change to servers might turn out to be a "nightmare on the server admins side to implement [...]", not to mention "[...] the fact that most if not all of them are volunteering time and machines for this".

The simplest workaround would just be a new server offering a different port number.

== 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:Multiplayer

2014-12-17T19:12:52Z

JazzTp:

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.

== Getting online ==
[[File:Multiplayer settings dialog.jpg|thumb|300px|Multiplayer settings dialog]]
As of FlightGear 2.4.0, multiplayer settings can be accessed via the in-sime Multiplayer menu. All you need to do is enter a callsign and select a server from the menu. Press Connect to go online.

This is by far the easiest way to get online, but in some cases the methods mentioned below may be prefered.

'''Before starting tests''', you might want to check the section ''Problems associated with specific Internet Service Providers'' below in this page.

=== Using the 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.
#* '''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

{{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O port to the corresponding port of the other instance:
<syntaxhighlight lang="bash">
fgfs --multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=one &
fgfs --multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=two &
</syntaxhighlight>
You can use this kind of setup to test multiplayer related features or troubleshoot multiplayer related bug reports that may be otherwise hard to reproduce over MP, because you don't normally see what other people are doing in terms of configuring MP/fgfs.
[[File:Direct-p2p-multiplayer-setup.png|800px|Screen shots demonstrating a "peer-to-peer" setup between two fgfs instances running on the same machine via localhost/loopback (127.0.0.1) without any fgms/multiplayer server being involved]]
You can add an arbitrary number of channels to mirror your flight onto other servers, e.g. to a private fgms server using '''<nowiki>--multiplay=out,10,my.private.server.ip,5000</nowiki>'''.

Additionally, the "in"-argument above tells FG to listen '''only''' on the loopback/local interface - it will not receive packets arriving on the other network interface(s). If you want to also bind to other interfaces, just omit the IP address by using '''<nowiki>--multiplay=in,10,,5000</nowiki>'''.
}}

''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.

== 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.

== 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
|-
|fg.noahbuscher.com
|US
|{{no}}
|Noah Buscher
|Noah
|Noah
|May be merged with main servers in the near future.
|-
|-
|mpserver01.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Los Angeles, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Lloyd Stevens
|ls4680
|ls4680
|
|-
|mpserver03.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Hergen
|
|
|
|-
|mpserver04.flightgear.org
|UK
|{{no}}
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Berlin, Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Sven Teichmann
|
|D-SAMI
|Unlimited traffic
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|{{n/a}}
|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
|{{n/a}}
|Daniel Vigano
|Fauchi95
|
|Offline
|-
|mpserver10.flightgear.org
|Montpellier, France
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Alexis Bory
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|{{no}}
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|{{yes|[http://mpserver12.flightgear.org mpserver12]}}
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|{{no}}
|Charles Ingels
|charles
|cbz-026
|
|-
|mpserver14.flightgear.org
|Zurich, Switzerland
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Yves Sablonier
|gral
|gral
|
|-
|mpserver15.flightgear.org
|North Point, Hong Kong
|{{n/a}}
|Hazuki Amamiya
|Hazuki
|Hazuki
|This is FGTracker, not a multiplayer server
|-
|mpserver16.flightgear.org
|Kansas City, Missouri, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Rob Dosogne
|truthsolo
|truthsolo
|
|-
|mpserver17.flightgear.org
|Cluj, Romania
|{{n/a}}
|Marius
|tuxum
|tuxum
|Offline
|-
|mpserver18.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|
|
|
|
|}
''Information as at 2014-01-04''

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]].

== Problems associated with specific Internet Service Providers ==

'''Fibertel Argentina'''

It has been reported '''December 2014''' that UDP connection through port 5000 is not possible. Fibertel Argentina users do not have full access to the modem configuration at the moment, they have to pass through a ''very limited'' interface on the Fibertel web site, only aimed at allowing operations like switching on/off the wifi radio or switching between NAT router mode and bridge mode (and at the moment a bug made users unable to submit any configuration changes).
After various hours of tests by the user with and without Fibertel staff at the phone with the modem in NAT router mode and in bridge mode, after a supervisor decided to remotely flash the modem (Motorola) with a recent firmware and yet noticed strange behaviour and sent tech staff to replace the modem with a simpler one (another Motorola model with no wifi), after testing with it in bridge mode with tech staff at the phone, the user sought for help [http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034 in the forum] and finally '''a temporary standalone instance of the Multiplayer server software''' (located in Canada) was activated and '''the user was able to connect normally through all the tested ports (5001, 5002, 5003, 5507) but not through port 5000 which is the only available port in any FlightGear Multiplayer server at the moment'''. Through another Internet Service Provider (Speedy ADSL) the user could connect with no problems to port 5000 of any Multiplayer server.

Facing this evidence, Fibertel Argentina technical staff ''finally'' admitted: "It's not the modem, it's the network, our network uses port 5000 for setup purposes, it should be open for the user but it might not be fully functional". '''This is reported here to avoid other users a similar 60-70 hours time loss.''' The users reports he asked them with energy to stop filtering port 5000, the answer was that because of the implications that was not an option.

Port 5000 is unofficially associated both with FlightGear and the UPnP protocol.
However, it has been observed (discussion of [https://code.google.com/p/flightgear-bugs/issues/detail?id=1617&q=-Type%3DFeatureRequest%20-status%3ATesting&sort=-id&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone issue 1617]) that '''the fact that Fibertel Argentina is using port 5000 for network setup purposes shouldn't imply that they are filtering packets: ''"it should really only be when the packet has reached its destination that the port number has any meaning at all"'''''.

Forum thread full link: http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034).

Reported issue 1617 full link: https://code.google.com/p/flightgear-bugs/issues/detail?id=1617&q=-Type%3DFeatureRequest%20-status%3ATesting&sort=-id&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone

Besides investigating about '''possible workarounds(?)''' (port forwarding through UDP bidirectional tunnelling) which might or might not add too much network latency or CPU load or constitute a misuse of special purposes networks, the user suggested diversification of port numbers (''"offering two possible port numbers could mean offering twice the chances to connect to the Multiplayer network and would constitute a reasonable prevention measure of part of the possible connection problems of FlightGear users over the internet"'').

== 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:Multiplayer

2014-12-17T18:46:41Z

JazzTp:

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.

== Getting online ==
[[File:Multiplayer settings dialog.jpg|thumb|300px|Multiplayer settings dialog]]
As of FlightGear 2.4.0, multiplayer settings can be accessed via the in-sime Multiplayer menu. All you need to do is enter a callsign and select a server from the menu. Press Connect to go online.

This is by far the easiest way to get online, but in some cases the methods mentioned below may be prefered.

'''Before starting tests''', you might want to check the section ''Problems associated with specific Internet Service Providers'' below in this page.

=== Using the 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.
#* '''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

{{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O port to the corresponding port of the other instance:
<syntaxhighlight lang="bash">
fgfs --multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=one &
fgfs --multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=two &
</syntaxhighlight>
You can use this kind of setup to test multiplayer related features or troubleshoot multiplayer related bug reports that may be otherwise hard to reproduce over MP, because you don't normally see what other people are doing in terms of configuring MP/fgfs.
[[File:Direct-p2p-multiplayer-setup.png|800px|Screen shots demonstrating a "peer-to-peer" setup between two fgfs instances running on the same machine via localhost/loopback (127.0.0.1) without any fgms/multiplayer server being involved]]
You can add an arbitrary number of channels to mirror your flight onto other servers, e.g. to a private fgms server using '''<nowiki>--multiplay=out,10,my.private.server.ip,5000</nowiki>'''.

Additionally, the "in"-argument above tells FG to listen '''only''' on the loopback/local interface - it will not receive packets arriving on the other network interface(s). If you want to also bind to other interfaces, just omit the IP address by using '''<nowiki>--multiplay=in,10,,5000</nowiki>'''.
}}

''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.

== 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.

== 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
|-
|fg.noahbuscher.com
|US
|{{no}}
|Noah Buscher
|Noah
|Noah
|May be merged with main servers in the near future.
|-
|-
|mpserver01.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Los Angeles, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Lloyd Stevens
|ls4680
|ls4680
|
|-
|mpserver03.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Hergen
|
|
|
|-
|mpserver04.flightgear.org
|UK
|{{no}}
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Berlin, Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Sven Teichmann
|
|D-SAMI
|Unlimited traffic
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|{{n/a}}
|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
|{{n/a}}
|Daniel Vigano
|Fauchi95
|
|Offline
|-
|mpserver10.flightgear.org
|Montpellier, France
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Alexis Bory
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|{{no}}
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|{{yes|[http://mpserver12.flightgear.org mpserver12]}}
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|{{no}}
|Charles Ingels
|charles
|cbz-026
|
|-
|mpserver14.flightgear.org
|Zurich, Switzerland
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Yves Sablonier
|gral
|gral
|
|-
|mpserver15.flightgear.org
|North Point, Hong Kong
|{{n/a}}
|Hazuki Amamiya
|Hazuki
|Hazuki
|This is FGTracker, not a multiplayer server
|-
|mpserver16.flightgear.org
|Kansas City, Missouri, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Rob Dosogne
|truthsolo
|truthsolo
|
|-
|mpserver17.flightgear.org
|Cluj, Romania
|{{n/a}}
|Marius
|tuxum
|tuxum
|Offline
|-
|mpserver18.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|
|
|
|
|}
''Information as at 2014-01-04''

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]].

== Problems associated with specific Internet Service Providers ==

'''Fibertel Argentina'''

It has been reported '''December 2014''' that UDP connection through port 5000 is not possible. Fibertel Argentina users do not have full access to the modem configuration at the moment, they have to pass through a ''very limited'' interface on the Fibertel web site, only aimed at allowing operations like switching on/off the wifi radio or switching between NAT router mode and bridge mode (and at the moment a bug made users unable to submit any configuration changes).
After various hours of tests by the user with and without Fibertel staff at the phone with the modem in NAT router mode and in bridge mode, after a supervisor decided to remotely flash the modem (Motorola) with a recent firmware and yet noticed strange behaviour and sent tech staff to replace the modem with a simpler one (another Motorola model with no wifi), after testing with it in bridge mode with tech staff at the phone, the user sought for help [http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034 in the forum] and finally '''a temporary standalone instance of the Multiplayer server software''' (located in Canada) was activated and '''the user was able to connect normally through all the tested ports (5001, 5002, 5003, 5507) but not through port 5000 which is the only available port in any FlightGear Multiplayer server at the moment'''. Through another Internet Service Provider (Speedy ADSL) the user could connect with no problems to port 5000 of any Multiplayer server.

Facing this evidence, Fibertel Argentina technical staff ''finally'' admitted: "It's not the modem, it's the network, our network uses port 5000 for setup purposes, it should be open for the user but it might not be fully functional". This is reported here to avoid other users a similar 60-70 hours time loss.

It has been observed (discussion of [https://code.google.com/p/flightgear-bugs/issues/detail?id=1617&q=-Type%3DFeatureRequest%20-status%3ATesting&sort=-id&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone issue 1617]) that the fact that Fibertel Argentina is using port 5000 for network setup purposes shouldn't imply that they are filtering packets: ''"it should really only be when the packet has reached its destination that the port number has any meaning at all"''.

Reported issue 1617 full link: https://code.google.com/p/flightgear-bugs/issues/detail?id=1617&q=-Type%3DFeatureRequest%20-status%3ATesting&sort=-id&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone

Forum thread full link: http://forum.flightgear.org/viewtopic.php?f=27&t=24754&p=226034#p226034).

== 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:Multiplayer

2014-12-17T17:47:07Z

JazzTp: /* Getting online */

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.

== Getting online ==
[[File:Multiplayer settings dialog.jpg|thumb|300px|Multiplayer settings dialog]]
As of FlightGear 2.4.0, multiplayer settings can be accessed via the in-sime Multiplayer menu. All you need to do is enter a callsign and select a server from the menu. Press Connect to go online.

This is by far the easiest way to get online, but in some cases the methods mentioned below may be prefered.

'''Before starting tests''', you might want to check at the ending of the "Servers" section below in this page if '''your Internet Service Provider''' has been '''reported''' to be associated with '''problems''' related with the FlightGear Multiplayer connection.

=== Using the 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.
#* '''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

{{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O port to the corresponding port of the other instance:
<syntaxhighlight lang="bash">
fgfs --multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=one &
fgfs --multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=two &
</syntaxhighlight>
You can use this kind of setup to test multiplayer related features or troubleshoot multiplayer related bug reports that may be otherwise hard to reproduce over MP, because you don't normally see what other people are doing in terms of configuring MP/fgfs.
[[File:Direct-p2p-multiplayer-setup.png|800px|Screen shots demonstrating a "peer-to-peer" setup between two fgfs instances running on the same machine via localhost/loopback (127.0.0.1) without any fgms/multiplayer server being involved]]
You can add an arbitrary number of channels to mirror your flight onto other servers, e.g. to a private fgms server using '''<nowiki>--multiplay=out,10,my.private.server.ip,5000</nowiki>'''.

Additionally, the "in"-argument above tells FG to listen '''only''' on the loopback/local interface - it will not receive packets arriving on the other network interface(s). If you want to also bind to other interfaces, just omit the IP address by using '''<nowiki>--multiplay=in,10,,5000</nowiki>'''.
}}

''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.

== 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.

== 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
|-
|fg.noahbuscher.com
|US
|{{no}}
|Noah Buscher
|Noah
|Noah
|May be merged with main servers in the near future.
|-
|-
|mpserver01.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Los Angeles, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Lloyd Stevens
|ls4680
|ls4680
|
|-
|mpserver03.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Hergen
|
|
|
|-
|mpserver04.flightgear.org
|UK
|{{no}}
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Berlin, Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Sven Teichmann
|
|D-SAMI
|Unlimited traffic
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|{{n/a}}
|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
|{{n/a}}
|Daniel Vigano
|Fauchi95
|
|Offline
|-
|mpserver10.flightgear.org
|Montpellier, France
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Alexis Bory
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|{{no}}
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|{{yes|[http://mpserver12.flightgear.org mpserver12]}}
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|{{no}}
|Charles Ingels
|charles
|cbz-026
|
|-
|mpserver14.flightgear.org
|Zurich, Switzerland
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Yves Sablonier
|gral
|gral
|
|-
|mpserver15.flightgear.org
|North Point, Hong Kong
|{{n/a}}
|Hazuki Amamiya
|Hazuki
|Hazuki
|This is FGTracker, not a multiplayer server
|-
|mpserver16.flightgear.org
|Kansas City, Missouri, USA
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|Rob Dosogne
|truthsolo
|truthsolo
|
|-
|mpserver17.flightgear.org
|Cluj, Romania
|{{n/a}}
|Marius
|tuxum
|tuxum
|Offline
|-
|mpserver18.flightgear.org
|Germany
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
|
|
|
|
|}
''Information as at 2014-01-04''

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]].

== 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]]

FlightGear Git: data developers

2014-12-14T23:53:00Z

JazzTp: /* Single clone */

{{Git}}
Anyone contributing data to FlightGear, like aircraft models, dialogs or textures, is a '''data developer'''. This article helps those in setting up a correct workflow, to ease the inclusion of their work into the simulator.

== Note about aircraft ==
As of September 2014, all aircraft but those in the base package (that is shipped with a FlightGear release) have been copied over to a new [https://sourceforge.net/p/flightgear/fgaddon/ SVN repository]. Changes to those aircraft should be made there instead of in the Git fgdata repository discussed in this article. For the moment all aircraft are still present in the Git repository, but only base package aircraft are maintained in the Git repository. Before the release of FlightGear 3.4 in February 2014, all non-base package aircraft will be removed from Git.

== Preparations ==
The steps described in this section are only required once, at the initialization of your development environment.

=== Cloning the repository ===
The first thing to do as a prospective developer is to [https://gitorious.org/users/new register at Gitorious] if you haven't already done so. This will enable you to publish your edits and have them incorporated into the main project.

After logging in, you can create a personal "clone" of the data repository. This clone is where you will be working in, without touching the main repository. To create a clone, navigate to the fgdata repository on https://gitorious.org/fg/ and click the [http://gitorious.org/fg/fgdata/clone Clone repository] button. In general the default name is fine, but you can change it to whatever you like. Gitorious will now clone the data repository. Due to the size of our repository, this can take some time.

=== Obtaining the data ===
Before you can start editing, you first need to retrieve the data to your computer. There are two ways to do this. At the time of writing the data repository is over 5 GB. Continuing an interrupted cloning of a repository is not supported within Git. Therefore, if you have a slow or unstable connection to the internet, it is recommended to [[#Bundle|download the bundle]].

For both approaches, Git must be installed. There is a lot of software available, but the following are often used:
* '''Mac:''' [http://code.google.com/p/git-osx-installer/ Git for OS X]
* '''Windows:''' [http://msysgit.github.io/ msysGit]

==== Single clone ====
# Create a directory on your computer where you'll be storing the data.
# Change into that folder.
# Clone the repository with the following command. This will create a <tt>/fgdata</tt> subfolder and put all the contents of the repository in there.
#:<code><nowiki>git clone git://gitorious.org/fg/fgdata.git</nowiki></code>

{{{
Edit by a total newbie to Git and the FG Wiki, I hope it is correct and saves somebody some time:

The bittorrent bundle described below was today December 14th 2014 lacking seeds for part of the update files. After installing Git for Windows from the indicated link http://msysgit.github.io/ and giving outbound connection authorization in the Windows 8.1 firewall to the program C:\Program Files (x86)\Git\bin\ssh.exe (I had actually also authorized the following ones in the same folder but it ''might'' be irrelevant in order to use git bash: wish.exe, git.exe, sh.exe), I logged in to Gitorious, created an account, when it asked for my key I created it as indicated here https://help.github.com/articles/generating-ssh-keys/ and pasted the public part into my account settings as required, then I was able to clone the fg/fgdata repository with this command I found searching in google the words ''git problem adding the fg/fgdata repository'', after cd'ing to the folder in which I wanted the fgdata folder to be created:

git clone git@gitorious.org:fg/fgdata.git
}}}

==== Bundle ====
For the FlightGear-data there is a [http://www.kernel.org/pub/software/scm/git/docs/git-bundle.html git-bundle] (snapshot) [http://mxchange.org:23456/file?info_hash=%BF%FF%AB%0C%16%BF%8Eg%B8%A0%CFw%01%0A%5D%8F%3F%81%96y torrent] ([http://mxchange.org:23456/ tracker]; [http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.md5 md5]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha1 sha1]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha512 sha512]) available. This way you can resume interrupted downloads. After unpacking it only a comparatively small amount of data has to be transferred from the git server to synchronize your repository. Also download the fgdata-update-*.bundle updates linked in the [http://mxchange.org:23456/ tracker]. See also the Develop sections in [[FlightGear Git on Windows]].

# Create a directory on your computer where you'll be storing the data.
# Change into that folder.
# Do the following steps to extract the bundle and bring the repository up to date:
#:<code>git clone fgdata.bundle fgdata</code>
#:<code>cd fgdata</code>
#:<code>git checkout -b master-tmp</code>
#:<code>for N in 01 02 03 04 05 06 07 08 09 10 11; do git pull ../fgdata-update-0$N.bundle master; done</code>
#:<code>git remote rm origin</code>
#:<code><nowiki>git remote add origin git://gitorious.org/fg/fgdata.git</nowiki></code>
#:<code>git fetch origin</code>
#:<code>git branch --track master origin/master</code>
#:<code>git checkout master</code>
#:<code>git branch -D master-tmp</code>

You should be suspicious if based on the printed progress during the <code>git fetch origin</code> phase you estimate the data download during the fetch will exceed 1GB (assuming the bundle is not terribly outdated).

=== Authentication ===
In order to publish edits on Gitorious, you need to generate a secret key so you can be correctly identified.

# Navigate to your newly created fgdata directory and run:
#: <code>ssh-keygen</code>
# Enter the name of the file in which you prefer to save the key and press Enter.
# Enter your password/passphrase and press Enter. You'll have to do this twice.
# Your key is now being generated. Open the .pub file with an editor and copy the content.
# Visit your dashboard at Gitorious and navigate to "Manage SSH keys".
# Click the "Add SSH key" button and paste the content of the .pub file. Follow the instructions on the screen.
# Now run the following, again in your fgdata directory, with ''<url>'' as the line that you get by clicking SSH on your fgdata clone page at Gitorious (something like ''git@gitorious.org:~your/fg/yours-fgdata.git''):
#: <code>git remote set-url origin <url></code>

=== Obtaining the simulator ===
In order to test your work, you'll need the FlightGear version that matches the data. Since FlightGear is under constant development, data from Git does not work with previous releases. Fortunately obtaining the latest development version of the simulator is fairly straightforward for most operating systems.

* '''Mac:''' Download [http://flightgear.simpits.org:8080/job/FlightGear-mac/ the .dmg]
* '''Windows:''' Download the [http://flightgear.simpits.org:8080/job/Win32-installer-Cmake 32-bits] or [http://flightgear.simpits.org:8080/job/Win64-installer-Cmake 64-bits] installer and follow its instructions. Let it install the binary into a clean directory.

Point [[$FG_ROOT]] to your freshly obtained fgdata directory. When using [[FlightGear Launch Control|the launcher]], this can be done on the first page, previous from the aircraft selection.

== Making edits ==
It is recommended to split your new fgdata clone into separate local branches for your work. For instance, if you're working on the Boeing 747-400 and the aircraft reflection shader, you might create 2 branches named "747-400" and "reflect-shader". To do this, run the following commands:
:<code>git checkout master</code>
:<code>git checkout -b <branch name></code>
Then you can make your changes to the new local branch(es), which will make merge requests easier for both yourself and committers. To switch in between branches, simply use
:<code>git checkout <branch name></code>

== Publishing edits ==
To push local updates to your fgdata clone on Gitorious, perform the following steps:
# Switch to the branch that contains your edits:
#:<code>git checkout <branch name></code>
# List all the changed files:
#:<code>git status -- .</code>
# Now it's time to commit the changed files.
#* If you want to commit all changed files, run the following and type your commit message.
#*: <code>git commit -a</code>
#* If you only want to commit a selection of files, run the following:
#*: <code>git add <path/to/file></code> (for single files)
#*: <code>git add --all <path/to/folder></code> (to add all files within a certain folder)
#*: <code>git rm <path/to/file></code> (to remove files that you've removed)
#: Followed by
#:: <code>git commit -m "<commit message>"</code>
# Check if everything went fine, by loading Gitk:
#: <code>gitk</code>
# Finally, push the commit to your fgdata clone Gitorious with the following command. Replace <code>YourUID</code> with your Gitorious account:
#: <code>git push git@gitorious.org:~YourUID/fg/YourUIDs-fgdata.git</code>

== Requesting edits to be merged ==
[[File:Create merge request at Gitorious.png|thumb|270px|Creating a merge request at Gitorious.]]
# Click the "Request merge" button on your fgdata clone page. Loading the next page can take a while, as it will list all commits of the past years!
# Once again write a short summary (could be the same as used with git commit), but this time, also write an explanation of your merge request (what does it do?). Make sure you set the target repository to fgdata, target branch to master and source branch to the local branch with your updates.
# Tick the box in front of your commit and click the "Create merge request" button.
# Everyone can see the pending request, but in order to make sure that your request gets looked at, you may contact a contributor. You can find a list of people on the right side of the [https://gitorious.org/fg/fgdata repository page].

Creating merge requests using this method literally means merging an entire branch into fgdata; this may not be desirable for some situations, such as small changes that only require one little commit. There's a neat method to only push certain commits to a merge request discussed by Anders Gidenstam [http://forum.flightgear.org/viewtopic.php?f=4&t=10392&start=45#p115747 on the FlightGear Forums].

[[Category:Git]]

FlightGear Git: data developers

2014-12-14T23:49:47Z

JazzTp: /* Single clone */

{{Git}}
Anyone contributing data to FlightGear, like aircraft models, dialogs or textures, is a '''data developer'''. This article helps those in setting up a correct workflow, to ease the inclusion of their work into the simulator.

== Note about aircraft ==
As of September 2014, all aircraft but those in the base package (that is shipped with a FlightGear release) have been copied over to a new [https://sourceforge.net/p/flightgear/fgaddon/ SVN repository]. Changes to those aircraft should be made there instead of in the Git fgdata repository discussed in this article. For the moment all aircraft are still present in the Git repository, but only base package aircraft are maintained in the Git repository. Before the release of FlightGear 3.4 in February 2014, all non-base package aircraft will be removed from Git.

== Preparations ==
The steps described in this section are only required once, at the initialization of your development environment.

=== Cloning the repository ===
The first thing to do as a prospective developer is to [https://gitorious.org/users/new register at Gitorious] if you haven't already done so. This will enable you to publish your edits and have them incorporated into the main project.

After logging in, you can create a personal "clone" of the data repository. This clone is where you will be working in, without touching the main repository. To create a clone, navigate to the fgdata repository on https://gitorious.org/fg/ and click the [http://gitorious.org/fg/fgdata/clone Clone repository] button. In general the default name is fine, but you can change it to whatever you like. Gitorious will now clone the data repository. Due to the size of our repository, this can take some time.

=== Obtaining the data ===
Before you can start editing, you first need to retrieve the data to your computer. There are two ways to do this. At the time of writing the data repository is over 5 GB. Continuing an interrupted cloning of a repository is not supported within Git. Therefore, if you have a slow or unstable connection to the internet, it is recommended to [[#Bundle|download the bundle]].

For both approaches, Git must be installed. There is a lot of software available, but the following are often used:
* '''Mac:''' [http://code.google.com/p/git-osx-installer/ Git for OS X]
* '''Windows:''' [http://msysgit.github.io/ msysGit]

==== Single clone ====
# Create a directory on your computer where you'll be storing the data.
# Change into that folder.
# Clone the repository with the following command. This will create a <tt>/fgdata</tt> subfolder and put all the contents of the repository in there.
#:<code><nowiki>git clone git://gitorious.org/fg/fgdata.git</nowiki></code>

{{{
Edit by a total newbie to Git and the FG Wiki, I hope it is correct and saves somebody some time:

The bittorrent bundle described below was today December 14th 2014 lacking seeds for part of the update files. After installing Git for Windows from the indicated link http://msysgit.github.io/ and giving outbound connection authorization in the Windows 8.1 firewall to the program C:\Program Files (x86)\Git\bin\ssh.exe (I had actually also authorized the following ones in the same folder but it ''might'' be irrelevant in order to use git bash: wish.exe, git.exe, sh.exe), I logged in to Gitorious, created an account, when it asked for my key I created it as indicated here https://help.github.com/articles/generating-ssh-keys/ and pasted the public part into my account settings as required, then I was able to clone the fg/fgdata repository with this command I found searching in google the words '''git problem adding the fg/fgdata repository''', after cd'ing to the folder in which I wanted the fgdata folder to be created:

'''git clone git@gitorious.org:fg/fgdata.git'''
}}}

==== Bundle ====
For the FlightGear-data there is a [http://www.kernel.org/pub/software/scm/git/docs/git-bundle.html git-bundle] (snapshot) [http://mxchange.org:23456/file?info_hash=%BF%FF%AB%0C%16%BF%8Eg%B8%A0%CFw%01%0A%5D%8F%3F%81%96y torrent] ([http://mxchange.org:23456/ tracker]; [http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.md5 md5]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha1 sha1]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha512 sha512]) available. This way you can resume interrupted downloads. After unpacking it only a comparatively small amount of data has to be transferred from the git server to synchronize your repository. Also download the fgdata-update-*.bundle updates linked in the [http://mxchange.org:23456/ tracker]. See also the Develop sections in [[FlightGear Git on Windows]].

# Create a directory on your computer where you'll be storing the data.
# Change into that folder.
# Do the following steps to extract the bundle and bring the repository up to date:
#:<code>git clone fgdata.bundle fgdata</code>
#:<code>cd fgdata</code>
#:<code>git checkout -b master-tmp</code>
#:<code>for N in 01 02 03 04 05 06 07 08 09 10 11; do git pull ../fgdata-update-0$N.bundle master; done</code>
#:<code>git remote rm origin</code>
#:<code><nowiki>git remote add origin git://gitorious.org/fg/fgdata.git</nowiki></code>
#:<code>git fetch origin</code>
#:<code>git branch --track master origin/master</code>
#:<code>git checkout master</code>
#:<code>git branch -D master-tmp</code>

You should be suspicious if based on the printed progress during the <code>git fetch origin</code> phase you estimate the data download during the fetch will exceed 1GB (assuming the bundle is not terribly outdated).

=== Authentication ===
In order to publish edits on Gitorious, you need to generate a secret key so you can be correctly identified.

# Navigate to your newly created fgdata directory and run:
#: <code>ssh-keygen</code>
# Enter the name of the file in which you prefer to save the key and press Enter.
# Enter your password/passphrase and press Enter. You'll have to do this twice.
# Your key is now being generated. Open the .pub file with an editor and copy the content.
# Visit your dashboard at Gitorious and navigate to "Manage SSH keys".
# Click the "Add SSH key" button and paste the content of the .pub file. Follow the instructions on the screen.
# Now run the following, again in your fgdata directory, with ''<url>'' as the line that you get by clicking SSH on your fgdata clone page at Gitorious (something like ''git@gitorious.org:~your/fg/yours-fgdata.git''):
#: <code>git remote set-url origin <url></code>

=== Obtaining the simulator ===
In order to test your work, you'll need the FlightGear version that matches the data. Since FlightGear is under constant development, data from Git does not work with previous releases. Fortunately obtaining the latest development version of the simulator is fairly straightforward for most operating systems.

* '''Mac:''' Download [http://flightgear.simpits.org:8080/job/FlightGear-mac/ the .dmg]
* '''Windows:''' Download the [http://flightgear.simpits.org:8080/job/Win32-installer-Cmake 32-bits] or [http://flightgear.simpits.org:8080/job/Win64-installer-Cmake 64-bits] installer and follow its instructions. Let it install the binary into a clean directory.

Point [[$FG_ROOT]] to your freshly obtained fgdata directory. When using [[FlightGear Launch Control|the launcher]], this can be done on the first page, previous from the aircraft selection.

== Making edits ==
It is recommended to split your new fgdata clone into separate local branches for your work. For instance, if you're working on the Boeing 747-400 and the aircraft reflection shader, you might create 2 branches named "747-400" and "reflect-shader". To do this, run the following commands:
:<code>git checkout master</code>
:<code>git checkout -b <branch name></code>
Then you can make your changes to the new local branch(es), which will make merge requests easier for both yourself and committers. To switch in between branches, simply use
:<code>git checkout <branch name></code>

== Publishing edits ==
To push local updates to your fgdata clone on Gitorious, perform the following steps:
# Switch to the branch that contains your edits:
#:<code>git checkout <branch name></code>
# List all the changed files:
#:<code>git status -- .</code>
# Now it's time to commit the changed files.
#* If you want to commit all changed files, run the following and type your commit message.
#*: <code>git commit -a</code>
#* If you only want to commit a selection of files, run the following:
#*: <code>git add <path/to/file></code> (for single files)
#*: <code>git add --all <path/to/folder></code> (to add all files within a certain folder)
#*: <code>git rm <path/to/file></code> (to remove files that you've removed)
#: Followed by
#:: <code>git commit -m "<commit message>"</code>
# Check if everything went fine, by loading Gitk:
#: <code>gitk</code>
# Finally, push the commit to your fgdata clone Gitorious with the following command. Replace <code>YourUID</code> with your Gitorious account:
#: <code>git push git@gitorious.org:~YourUID/fg/YourUIDs-fgdata.git</code>

== Requesting edits to be merged ==
[[File:Create merge request at Gitorious.png|thumb|270px|Creating a merge request at Gitorious.]]
# Click the "Request merge" button on your fgdata clone page. Loading the next page can take a while, as it will list all commits of the past years!
# Once again write a short summary (could be the same as used with git commit), but this time, also write an explanation of your merge request (what does it do?). Make sure you set the target repository to fgdata, target branch to master and source branch to the local branch with your updates.
# Tick the box in front of your commit and click the "Create merge request" button.
# Everyone can see the pending request, but in order to make sure that your request gets looked at, you may contact a contributor. You can find a list of people on the right side of the [https://gitorious.org/fg/fgdata repository page].

Creating merge requests using this method literally means merging an entire branch into fgdata; this may not be desirable for some situations, such as small changes that only require one little commit. There's a neat method to only push certain commits to a merge request discussed by Anders Gidenstam [http://forum.flightgear.org/viewtopic.php?f=4&t=10392&start=45#p115747 on the FlightGear Forums].

[[Category:Git]]