With the multiplayer function of FlightGear you are able to see other pilots and vice-versa. This makes it possible to fly in formation, connect to tankers controlled by real people or contact real air traffic controllers to ask for landing/takeoff clearence.
Multiplay may cause extreme 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.
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.
Using the launcher / FGRun
- Select your aircraft and starting airport as normal 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.
- Callsign: of your choice.
- Hostname: enter mpserverXX.flightgear.org (with XX being the 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 <chat type="string">Hello</chat> line in $FG ROOT/preferences.xml). You may wish to use a different server (i.e. "Hostname" entry).
For more advanced settings, the Advanced > Network 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;
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:
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:
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 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 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.
See Chat Menu for the main article about this subject.
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 Network > Chat. 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.
See MPMap for the main article about this subject.
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.
|Server||Location||Tracked||Maintainer||IRC Name||Forum Name||Comments|
|mpserver02.flightgear.org||Los Angeles, USA||mpserver15||Lloyd Stevens||ls4680||ls4680|
|mpserver06.flightgear.org||Berlin, Germany||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||mpserver15||Alexis Bory||xiii||xiii|
|mpserver12.flightgear.org||Amsterdam, the Netherlands||mpserver12||Rob||evilslut||evilslut|
|mpserver13.flightgear.org||Grenoble, France||No||Charles Ingels||charles||cbz-026|
|mpserver14.flightgear.org||Zurich, Switzerland||mpserver15||Yves Sablonier||gral||gral|
|mpserver15.flightgear.org||North Point, Hong Kong||mpserver15||Hazuki Amamiya||Hazuki||Hazuki|
|mpserver16.flightgear.org||Kansas City, Missouri, USA||mpserver15||Rob Dosogne||truthsolo||truthsolo|
Information as at 2014-01-04
Geographic locations of the servers are also available at Google Maps.
If you are interested in hosting your own multiplayer server, you may want to check out Howto: Set up a multiplayer server.