FlightGear wiki

Howto:Multiplayer: Difference between revisions

Howto Discussion

Howto:Multiplayer (view source)

Revision as of 12:24, 16 May 2017

5,785 bytes added ,  16 May 2017
→‎Servers: Added mpserver51, self.
No edit summary
(→‎Servers: Added mpserver51, self.)
(48 intermediate revisions by 11 users not shown)
Line 1: Line 1:
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.
The '''multiplayer''' feature of [[FlightGear]] makes it possible to see other pilots and vice-versa. This makes it possible to fly in formation, perform [[mid-air refueling]] with tankers controlled by real people or contact real [[air traffic control|air traffic controllers]] to ask for guidance.


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.
Multiplayer may cause extreme [[troubleshooting performance issues|framerate drops]] during the loading of aircraft models, especially heavy models such as the [[Boeing 777]] or [[Airbus A320neo]]. It is suggested to fly in locations other than the default [[San Francisco International Airport]], as there are often lots of pilots in the area who are often new, and do not follow ATC, or respect traffic.


== Getting online ==
== Notes ==
[[File:Multiplayer settings dialog.jpg|thumb|300px|Multiplayer settings dialog]]
* Callsigns can be a maximum of seven characters.
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.  
* You might want to check the [[#Known issues|Known issues]] section.


This is by far the easiest way to get online, but in some cases the methods mentioned below may be prefered.
== Connecting to Multiplayer ==
=== Built-in launcher and in-sim dialog ===
[[File:Multiplayer settings dialog.jpg|thumb|Multiplayer settings dialog]]
The easiest way to get online is to use the [[FlightGear Qt launcher|built-in launcher]] or the in-sim Multiplayer dialog. All you need to do is enter a callsign and select a server from the menu. Press Connect to go online.


=== Using the launcher / FGRun ===
=== Using FGRun ===
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
==== From the main page ====
# Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|FGRun]].
[[File:Multiplayer.jpg|thumb|Multiplayer settings in [[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.
# Select your [[aircraft]] and starting airport as normal in [[FGRun]].
#* '''Callsign:''' of your choice.
# On the last screen, tick the "Multiplayer" box. Also make sure that the "AI models" box is checked or you will not be able to see the other pilots' aircraft.
#* '''Hostname:''' enter <tt>mpserverXX.flightgear.org</tt> (with <tt>XX</tt> being the [[#Servers|server number]]).
# Enter the …
#* '''In/Out:''' set both ports to 5000.
#* '''Callsign''' of your choice.
# Click run and you'll soon be flying with other pilots!
#* '''Hostname:''' Enter <code>mpserverXX.flightgear.org</code> (with <code>XX</code> being the [[#Servers|server number]]).
#* '''In/Out:''' Set both ports to 5000.
# Click {{button|Run}} to start FlightGear.


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).  
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.  They will also pop up when a pilot joins the MP network.  You can change this message by editing this line in <tt>''[http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/preferences.xml#l763 $FG_ROOT/preferences.xml]''</tt>:
<syntaxhighlight lang="xml">
<chat type="string" preserve="y">Hello</chat>
</syntaxhighlight>
You may wish to use a different server, especially one closer to you.  


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.
==== From Network Settings ====
[[File:FGRun Advanced dialog - Network.png|thumb|The <tt>Network</tt> tab of the Advanced Options dialog in [[FGRun]] (in [[Changelog 3.2|FlightGear 3.2.0]]).]]
You can also change multiplayer settings in the <tt>Network</tt> tab of FGRun's Advanced Options.


=== Using fgfs from the command line ===
# On the last page, click {{button|Advanced}}.
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;
# Click <tt>Network</tt> in the left column.
# In the <tt>Multiplayer Options</tt> area …
#* Type your desired callsign into the box.
#* Set the parameters for the two other boxes; see [[#Using multiplayer from the command line|below]] for correct syntax.
#* Click {{button|OK}}, then run FlightGear.


  --multiplay=out,10,server.ip.address,5000
=== Using multiplayer from the command line ===
--callsign=anything  
When running FlightGear from the [[command line]], you can specify multiplayer settings. The two arguments are as follows:
<syntaxhighlight lang="bash">
--multiplay=direction,10,ip.address,port
--callsign=anything  
</syntaxhighlight>


where 5000 is the port number the server is listening on (which is 5000 for the official servers).
Obviously, <code>--callsign</code> can be anything you wish.  There are four arguments to <code>--multiplay</code>:
; direction
: Either <code>in</code> or <code>out</code>.  <code>in</code> tells FlightGear to listen to packets of data coming in through the specified '''port'''.  <code>out</code> tells FlightGear to send data out through the '''port'''.


If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:
; ip.address
: IP address of network interface being used by FlightGear.  If left blank, FlightGear will listen to all network interfaces.  If '''direction''' is set to <code>in</code>, FlightGear will listen to ''only'' this IP address.


  --multiplay=in,10,your.ip.address,portnumber
; port
: Port that data is either being sent or received through. Usually set to <code>5000</code> and above.


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:
== Advanced usage of multiplayer ==
=== Local setup for testing ===
It is possible to set up a local multiplayer network between two FlightGear instances ''without'' using a [[FGMS|multiplayer server]]. All you need to do is map each I/O port of one instance to the corresponding port(s) of the other instance:


--multiplay=in,10,,5000
{{Note|
{{FGCquote
  |A socket connection requires not only an IP address, but also a port number for each side of the link - imagine a port number like a "mailbox" sitting at the address. This mailbox is used by the communicating processes to send out and receive "messages". Different processes (even when possibly identical programs) will need to use different port numbers when running. Because open ports ({{=}}mailboxes) cannot be shared.
Thus, you need to modify the client-side port settings for each additional instance that you are running on the same machine, and map the output port of one instance to the input port of the other instance (and vice versa).
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=83068#p83068
    |title=<nowiki>Re: 2 FGFS instances / 1 win7 running same time with MP?</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Thu Jun 10</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.''
Command line parameters for the first instance:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=Test1
</syntaxhighlight>
 
Command line parameters for the second instance:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=Test2
</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.  As you can't access the configuration of other people's FlightGear, this technique allows you to have complete control over FlightGear's settings.
 
[[File:Direct-p2p-multiplayer-setup.png|800px|Screenshot demonstrating a "peer-to-peer" setup between two FlightGear instances running on the same machine via localhost (127.0.0.1) without any multiplayer server.]]
 
You can add an arbitrary number of channels to mirror your flight onto other servers, e.g. to a private fgms server using
<syntaxhighlight lang="bash">
--multiplay=out,10,my.private.server.ip,5000
</syntaxhighlight>
 
Additionally, the <code>in</code> 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 
<syntaxhighlight lang="bash">
--multiplay=in,10,,5000
</syntaxhighlight>


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!
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... ====
==== Now, going more slowly for those who are completely lost... ====
Try the above first, and if it doesn't work, read on.
{{Note|This section may contain out of date or inaccurate information.}}
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.


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.
First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG.  


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.
If your Internet connection is via an ADSL modem that plugs directly into your computer, you should be able to find your IP address by visiting http://www.whatismyip.com.  
{{Note|Your {{Abbr|ISP|Internet Service Provider}} might not give you the same IP address each time.}}


* 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"
If your connection is via an Ethernet connector or by a wireless link.
* 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.
* '''Linux:''' Log in as root and run <code>ifconfig</code> in the terminal. In the text that is returned, you should to look for an interface name such as <code>eth0</code> or <code>wlan0</code>.  Finally, look in the text below the interface name for <code>inet addr:ip.address</code>. For example, this should read something like <code>inet addr:192.168.0.150</code>.
* '''Windows:'''
** '''Windows XP or later:''' Start Command Prompt and <code>ipconfig</code> into the terminal.  Write the IP address down.
** '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.


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).
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.
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.
{{Note|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;
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:
<syntaxhighlight lang="bash" enclose="div">
<other arguments> --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 --airport=KSFO --runway=28R --aircraft=hunter
</syntaxhighlight>


fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
Choose your own callsign, but check [http://fgfs.i-net.hu/modules/fgtracker/ this page] first to see whether your desired callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!
--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;
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;
Line 74: Line 136:
  Call: john51a,model: Aircraft/ufo/Models/ufo.xml  
  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 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.
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.


If it's still just not working for you, ask nicely on the [[FlightGear IRC channel|IRC channel]] or the [http://forum.flightgear.org/ forum] and someone should be able to assist.


=== Multiple connections per computer ===
=== 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:
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.
# Both instances use the same <code>out</code> port.
* one instance uses in port=5001, the other port 5002.
# One instance uses <code>in</code> port <code>5001</code>, the other port <code>5002</code>.
* and of course should both instances have unique callsigns.
# Both instances have unique callsigns.
 
 
=== Optional collision detection in multiplayer ===
 
A patch has been added to FlightGear (since Version 3.5) to allow optional collision detection in multiplayer. To enable collision detection, start FlightGear with:
 
<syntaxhighlight>
--prop:bool:/sim/multiplay/hot=true
</syntaxhighlight>
 
Those who are able to patch FGData themselves, can download [http://sourceforge.net/p/flightgear/mailman/attachment/CAHs0wcrEwYZvXTddcUaH0ZMfmVNvEWRap8MXOrEoKybUDO58sQ%40mail.gmail.com/3/ mp-hot-fgdata.patch], which adds a checkbox to the Multiplayer Settings dialog to enable or disable the collision detection at runtime.


== Multiplayer chat ==
== Multiplayer chat ==
{{Main article|Chat Menu}}
{{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.
To chat with other pilots, go to the <tt>Multiplayer</tt> menu and select <tt>Chat Menu</tt> 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.
The shortcut for chatting is {{Key press|<nowiki>-</nowiki>}} (hyphen).  This will bring up some text in the upper-left of the FlightGear window.  By pressing the corresponding number keys, you can send pre-made messages.  Pressing {{Key press|1}} will let you type in a custom message, which you can send by pressing enter. 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.
== Dealing with abusive behavior ==
 
Should you become victim of abusive or annoying behavior by any pilot, you have option to ignore him or her. To activate the ignore function open the <tt>Multiplayer > Pilot list</tt> dialog and click the <tt>ignore</tt> button next to the pilot's callsign. This will prevent chat messages from the ignored pilot appearing and prevent his aircraft from appearing (unless you are using FlightGear v2.2 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 ==
== Multiplayer map ==
Line 103: Line 173:
{{Main article|MPMap}}
{{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.
There is a very nice online map which displays the location of online pilots at [http://mpmap02.flightgear.org mpmap02]. You will also find this useful to check that you are successfully connecting to the server, as well as looking up navaids, waypoints, airports, frequencies, weather, and more!


== Servers ==
== 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.
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 either geographically closest to you, has the lowest latency (ping time), or is the least busy.
{{tip|Use [http://mpmap01.flightgear.org/mpstatus/ this link] or [http://mpserver15.flightgear.org/mpserverstatus/ this link] to check if the MP servers are online. Both pages are automatically generated.  The [[#In-sim Dialog|in-sim dialog]] will only display servers that are available.}}


{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
{| class="wikitable sortable"
! style="background:#efefef" |Server
! Server address
! style="background:#efefef" |Location
! Status
! style="background:#efefef" |[http://mpserver15.flightgear.org Tracked]
! Location  
! style="background:#efefef" |Maintainer
! Tracked (by [http://mpserver15.flightgear.org mpserver15] unless otherwise specified)
! style="background:#efefef" |[[IRC]] Name
! Maintainer  
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! Maintainer's [[IRC]] name
! style="background:#efefef" |Comments
! Maintainer's [http://flightgear.org/forums forum] name
|-
! Comments
|fg.noahbuscher.com
|US
|{{no}}
|Noah Buscher
|Noah
|Noah
|May be merged with main servers in the near future.
|-
|-
|-
|mpserver01.flightgear.org
| mpserver01.flightgear.org
|Germany
| {{yes|Up}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Germany
|Oliver Schroeder
| {{yes}}
|os
| Oliver Schroeder
|
| os
|
| {{N/a}}
| {{N/a|None}}
|-
|-
|mpserver02.flightgear.org
| mpserver02.flightgear.org
|Los Angeles, USA
| {{no|Down}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Los Angeles, USA
|Lloyd Stevens
| {{N/a}}
|ls4680
| Lloyd Stevens
|ls4680
| ls4680
|
| ls4680
| {{N/a|None}}
|-
|-
|mpserver03.flightgear.org
| mpserver03.flightgear.org
|Germany  
| {{yes|Up}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Germany  
|Hergen
| {{yes}}
|
| Hergen
|
| {{N/a}}
|
| {{N/a}}
| {{N/a|None}}
|-
|-
|mpserver04.flightgear.org
| mpserver04.flightgear.org
|UK
| {{yes|Up}}
|{{no}}
| UK
|Jon Stockill
| {{no}}
|Nav
| Jon Stockill
|JonS
| Nav
|
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=738 JonS]
| {{N/a|None}}
|-
|-
|mpserver05.flightgear.org
| mpserver05.flightgear.org
|Chicago, USA
| {{no|Down}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Chicago, USA
|Brant
| {{N/a}}
|IonCannon218
| Brant
|
| IonCannon218
|
| {{N/a}}
| {{N/a|None}}
|-       
|-       
|mpserver06.flightgear.org
| mpserver06.flightgear.org
|Berlin, Germany
| {{no|Down}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Berlin, Germany
|Sven Teichmann
| {{N/a}}
|
| Sven Teichmann
|D-SAMI
| {{N/a}}
|Unlimited traffic
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11839 D-SAMI]
| Unlimited traffic
|-       
|-       
|mpserver07.flightgear.org
| mpserver07.flightgear.org
|Wisconsin, USA
| {{no|Down}}
|{{n/a}}
| Wisconsin, USA
|Tom Betka
| {{N/a}}
|TB
| Tom Betka
|
| TB
|Offline
| {{N/a}}
| Offline
|-       
|-       
|mpserver08.flightgear.org
| mpserver08.flightgear.org
|Frankfurt am Main, Germany
| {{no|Down}}
|{{no}}
| Frankfurt am Main, Germany
|Roland
| {{N/a}}
|Quix0r
| Roland
|Quix0r
| Quix0r
|10 TByte traffic, mostly short pings
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=7512 Quix0r]
| 10 TByte traffic, mostly short pings
|-
|-
|mpserver09.flightgear.org
| mpserver09.flightgear.org
|Köln, Germany
| {{no|Down}}
|{{n/a}}
| Köln, Germany
|Daniel Vigano
| {{N/a}}
|Fauchi95
| Daniel Vigano
|
| Fauchi95
|Offline
| {{N/a}}
| Offline
|-
|-
|mpserver10.flightgear.org
| mpserver10.flightgear.org
|Montpellier, France
| {{no|Down}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Montpellier, France
|Alexis Bory
| {{N/a}}
|xiii
| {{usr|Xiii|Alexis Bory}}
|xiii
| xiii
|
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=884 xiii]
| {{N/a|None}}
|-
|-
|mpserver11.flightgear.org
| mpserver11.flightgear.org
|Vilnius, Lithuania
| {{no|Down}}
|{{no}}
| Vilnius, Lithuania
|Darius
| {{N/a}}
|
| Darius
|ffg
| {{N/a}}
|
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1122 ffg]
| {{N/a|None}}
|-
|-
|mpserver12.flightgear.org
| mpserver12.org
|Amsterdam, the Netherlands
| {{yes|Up}}
|{{yes|[http://mpserver12.flightgear.org mpserver12]}}
| Amsterdam, the Netherlands
|Rob
| {{yes}} (by [http://mpserver12.org mpserver12.org])
|evilslut
| Rob
|evilslut
| evilslut
|
| {{N/a}}
| Formerly mpserver12.flightgear.org<ref>http://forum.flightgear.org/viewtopic.php?f=27&t=27453&start=60#p258435</ref>
|-
|-
|mpserver13.flightgear.org
| mpserver13.flightgear.org
|Grenoble, France
| {{no|Down}}
|{{no}}
| Grenoble, France
|Charles Ingels
| {{N/a}}
|charles
| Charles Ingels
|cbz-026
| charles
|
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1592 cbz-026]
| {{N/a|None}}
|-
|-
|mpserver14.flightgear.org
| mpserver14.flightgear.org
|Zurich, Switzerland
| {{yes|Up}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| UK
|Yves Sablonier
| {{no}}
|gral
| Pete
|gral
| {{N/a}}
|
| {{N/a}}
| {{N/a|None}}
|-
|-
|mpserver15.flightgear.org
| mpserver15.flightgear.org
|North Point, Hong Kong
| {{yes|Up}}
|{{n/a}}
| North Point, Hong Kong
|Hazuki Amamiya
| {{yes}}
|Hazuki
| Hazuki Amamiya
|Hazuki
| Hazuki
|This is FGTracker, not a multiplayer server
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=8400 Hazuki]
| {{N/a|None}}
|-
|-
|mpserver16.flightgear.org
| mpserver16.flightgear.org
|Kansas City, Missouri, USA
| {{yes|Up}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Kansas City, Missouri, USA
|Rob Dosogne
| {{no}}
|truthsolo
| Rob Dosogne
|truthsolo
| truthsolo
|
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9926 truthsolo]
| {{N/a|None}}
|-
|-
|mpserver17.flightgear.org
| mpserver17.flightgear.org
|Cluj, Romania
| {{no|Down}}
|{{n/a}}
| Cluj, Romania
|Marius
| {{N/a}}
|tuxum
| Marius
|tuxum
| tuxum
|Offline
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11636 tuxum]
| Offline
|-
|-
|mpserver18.flightgear.org
| mpserver18.flightgear.org
|Germany
| {{no|Down}}
|{{yes|[http://mpserver15.flightgear.org mpserver15]}}
| Germany
|
| {{N/a}}
|
| {{N/a}}
|
| {{N/a}}
|
| {{N/a}}
| {{N/a}}
|-
| mpserver51.flightgear.org
| {{yes|Up}}
| Atlanta, Georgia, USA
| {{yes}}
| Dr. R0ckso
| drr0ckso
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21111 drR0ckso]
| Radio horizon is 414 miles
|}
|}
''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].
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]].
If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].
== Known issues ==
=== Fibertel (Argentina) ===
In December 2014, it was reported that UDP connection through port 5000 was not possible for users whose ISP was {{Wikipedia|Fibertel}} (Argentina).
Fibertel Argentina apparently uses the port for setup purposes. "It should be open for the user but it might not be fully functional."
Port 5000 is a generic port, and neither FlightGear nor the {{Wikipedia|UPnP}} protocol are an "official" usage of the port. 
A solution would be to spread the ports between the servers; e.g., mpserver01.flightgear.org → 5001, mpserver02.flightgear.org → 5002
See also the [http://forum.flightgear.org/viewtopic.php?f=27&t=24754 forum thread] and {{issue|1617}}.


== Related content ==
== Related content ==
Line 282: Line 381:
* [[Howto: Set up a multiplayer server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
* [[Multiplayer protocol]]
* [[Howto:Transmit_properties_over_MP]]
{{Appendix}}


[[Category:Multiplayer]]
[[Category:Multiplayer]]
Line 289: Line 391:
[[es:Howto: Multijugador]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[fr:Howto: Multijoueur]]
[[it:Come fare:Multiplayer]]
[[nl:Howto: Multiplayer]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]
[[pt:Tutorial de Multiplayer]]
DrR0ckso
4

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/70099...107827"