Bureaucrats, checkuser, Administrators
304
edits
Hellosimon (talk | contribs) No edit summary |
Hellosimon (talk | contribs) No edit summary |
||
Line 12: | Line 12: | ||
Where portnumber is usually 5000 or 5002 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. Please note that although this limitation has been removed in the most recent versions of the FG server; you should still specify a valid (non-loopback, i.e. not 127.0.0.1) IP address to keep the FG client happy. | Where portnumber is usually 5000 or 5002 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. Please note that although this limitation has been removed in the most recent versions of the FG server; you should still specify a valid (non-loopback, i.e. not 127.0.0.1) IP address to keep the FG client happy. | ||
Servers currently available are: mpserver01.flightgear.org (in Germany) | Servers currently available are: | ||
* mpserver01.flightgear.org (in Germany) | |||
* mpserver02.flightgear.org (in Hong Kong) | |||
* mpserver03.flightgear.org (East Coast USA) | |||
Port 5000 is usually for the latest stable version of FlightGear. Currently 0.9.10 | |||
Port 5002 is mainly used for development, i.e. stable version of FlightGear might not work with this server. | |||
Now, going more slowly for those who are completely lost... Try the above first, and if it doesn't work, read on. | Now, going more slowly for those who are completely lost... Try the above first, and if it doesn't work, read on. |