FlightGear wiki - User contributions [en]

Fr/Howto: Multijoueur

2011-03-03T20:25:21Z

IonCannon218: /* Serveurs */

Grâce aux fonctions '''multi-joueurs''' de [[FlightGear]], vous allez être capable de voir les autres pilotes connectés et réciproquement. Vous aurez alors la possibilité de voler en formation, de tester le [[Howto: Air-Air Refueling|ravitaillement en vol]] avec un avion ravitailleur piloté par un autre pilote ou de contacter le [[ATC|contrôle aérien]] pour les phases de décollage et d'atterrissage, et de faire plein d'autres choses.

Si vous souhaitez héberger votre propre serveur multi-joueurs, vous serez sûrement intéressé par la page [[Howto: Set up a multiplayer server|Howto: Héberger un serveur multi-joueurs]].

Cependant, voler en mode multi-joueurs peut potentiellement engendrer une chute du nombre d'[[Howto: Improve Framerates|images par secondes]], en particulier lors du chargement de modèles d'avions très détaillés, ce qui cause du ''lag'' (saccade des images).
D'autre part, la gigue réseau peut créer des effets surprenants comme le fait que vous voyiez subitement votre ailier reculer et passer derrière vous, comme si le temps s'était arrêté pour lui. Cela arrive de temps en temps.

Etant donné que l'aéroport par défaut est celui de San Francisco (KSFO) et qu'aux heures de pointe il peut être très chargé, il vous est conseillé de voler dans des endroits moins fréquentés où vous bénéficierez d'une meilleure fluidité.

== Serveurs ==

'''Veuillez noter:''' Les serveurs multi-joueurs sont tous inter-connectés; cela signifie que pour voir les pilotes connectés à un serveur en particulier, vous n'avez pas forcément besoin d'être connecté à ce serveur. Il vous suffit d'être connecté à n'importe quel autre serveur.
Cependant, pour assurer des temps de réponse optimaux, il vous est fortement recommandé de vous connecter sur un serveur qui est géographiquement situé le plus près de chez vous, c'est-à-dire un serveur qui a un temps de réponse au ''ping'' le plus bas possible.
Si vous envisagez un vol en formation avec d'autres pilotes, il est recommandé de se connecter sur le même serveur que celui sur lequel sont connectés les autres membres de la formation de façon à limiter le ''lag''.

Le tableau suivant fournit la liste des serveur MP (''Multi Players'') du monde entier. Il s'agit des serveurs officiels accessibles dans le domaine ''flightgear.org'' et sont tous inter-connectés entre eux. Vous connecter à un de ces serveurs vous rendra visible dans la matrice ''FlightGear''. Il existe certainement des serveurs locaux mais qui ne sont pas répertoriés ici.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2"
!Server
!Localisation
![http://fgfs.i-net.hu/modules/fgtracker/ Tracked]
!Opérateur
!Commentaires
|-
|mpserver01.flightgear.org
|Allemagne
|Oui
|Oliver Schroeder
|
|-
|mpserver03.flightgear.org
|Allemagne
|Oui
|
|
|-
|mpserver04.flightgear.org
|UK
|Oui
|Jon Stockill
|
|-
|mpserver05.flightgear.org
|Chiacgo, USA
|Oui
|Brant
|
|-
|mpserver06.flightgear.org
|Suède
|Non
|Anders Gidenstam
|Bande passante restreinte.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Oui
|Tom Betka
|
|-
|mpserver08.flightgear.org
|Frankfut am Main, Germany
|Oui
|Roland
|
|-
|mpserver09.flightgear.org
|Köln, Germany
|Oui
|Daniel Vigano
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Oui
|Alexis Bory
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Oui
|Darius
|
|-
|mpserver12.flightgear.org
|Amsterdam, Pays-Bas
|Oui
|Rob
|evilslut
|-
|mpserver13.flightgear.org
|Grenoble, France
|Oui
|Charles Ingels
|
|-
|74.208.230.119
|Kansas, USA
|
|Sabin
|En attente d'une entrée DNS dans le domaine flightgear.org
|}

Ce tableau est mis à jour assez régulièrement mais la pertinence des informations qu'il contient dépendent en grande partie de la fréquence de ces mises à jour.

Utilisez [http://pigeond.net/flightgear/mpstatus/ ce lien] pour vérifier la disponibilité des serveurs.

[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]

=== Cartes multi-joueurs ===
{{Main article|MPMap}}

Il y a une magnifique carte de visualisation temps réel des pilotes connectés [http://mpmap01.flightgear.org mpmap01] et/ou [http://mpmap02.flightgear.org mpmap02]. Cela vous aidera à vérifier que vous êtes bien connecté sur un serveur.

== Utilisation de ''fgrun'' ==

[[Image:Multiplayer.jpg|thumb|300px|Options multi-joueurs sous [[FlightGear Wizard|''fgrun'']]]]
#Choisissez votre [[Aircraft]] ainsi que l'aéroport de départ comme indiqué dans [[FlightGear Launch Control|Fgrun]].
#Sur l'écran suivant, cochez la case ''Multiplayer''. Cochez également ''AI models'' afin de voir les autres pilotes connectés et d'être vu. Dans la zone de saisie de texte, entrez votre ''callsign'', puis dans la zone ''hostname'', entrez l'adresse d'un serveur multi-joueurs (par exemple: ''mpserver01.flightgear.org''). Indiquez 5000 pour le numéro de port à utiliser en entrée et en sortie (numéro par défaut).
#Cliquez sur ''run'' et vous allez pouvoir voler avec d'autres pilotes du monde entier !

Pour vérifier que vous êtes bien connecté en mode multi-joueurs, ouvrez votre navigateur et pointez sur l'URL

http://mpmap01.flightgear.org/

ou

http://mpmap02.flightgear.org/ (Hong Kong).

Lors de votre connexion, vous allez constater que vous serez prévenu de l'arrivée de tout nouveau pilote par un message du type: "''<pilote>: Hello''".

Pour des options plus avancées, l'onglet <tt>Advanced > network</tt> peut être ouvert où vous pourrez supprimer/modifier les lignes ''in'' et ''out''.

== Vérifier la disponibilité d'un serveur ==

Il n'est envisageable d'utiliser un serveur que s'il répond, ce qui paraît logique.
Vous pouvez commencer par faire un ''ping'' du serveur :

ping serveurXX.flightgear.org

mais même s'il répond, cela ne vous garantit pas que ''fgms'' tourne dessus.

Il existe une méthode très simple pour vérifier si un serveur est utilisable en multi-joueurs.
Tapez la commande suivante :

telnet serveurXX.flightgear.org 5001

et s'il est actif, vous devriez obtenir une liste de toutes les personnes connectées au réseau MP.

== Lancer fgfs multijoueur en ligne de commande ==

Pour ceux qui sont impatients et ont déjà une vague idée de ce qu'il font, les lignes de base pour le mode multijoueur sont :

--multiplay=out,10,server.adresse.ip,portnumber
--multiplay=in,10,votre.adresse.ip,portnumber
--callsign=anything

Où le ''portnumber'' est habituellement 5000 et ''votre.adresse.ip'' l'adresse de votre interface réseau utilisée par FG pour se connecter au serveur - même si c'est une adresse locale en 192.168... Notez qu'il faut spécifier une adresse valide (non loopback: ie non 127.0.0.1) pour que FG soit heureux, même si cette limitation a été enlevée sur les versions les plus récentes des serveurs FG.

Avec les dernières versions de FG (depuis OSG), vous pouvez aussi laisser le champ ''votre.adresse.ip'' vide. FlightGear écoutera alors sur toutes les interfaces réseau.

--multiplay=in,10,,5000

Dans la plupart des cas et avec les versions récentes de ''FlightGear'', cette ligne est d'ailleurs facultative.

Regardez sur [http://fgfs.i-net.hu/modules/fgtracker/ cette page] pour voir si votre ''callsign'' est déjà utilisé, ne prenez pas un nom existant, ce qui peut causer de problèmes.
Vous êtes libre de choisir votre callsign, pour peu qu'il ne soit pas déjà pris. Cependant, essayez de choisir un callsign normalisé dans le monde aéronautique. Un tel callsign débute par une lettre indiquant la zone aéronautique (F- pour la France), suivi par une lettre qui indique la série en cours (ex: F-G) puis trois lettres de votre choix (ex: F-GCBZ). Cela facilitera les communications avec un éventuel ATC.

=== Plus détaillé, pour ceux qui ont du mal à suivre... ===

Essayez en premier ce qui précède, et si vous rencontrez des difficultés, lisez la suite. Notez qu'avec les versions récentes de FlightGear, l'adresse IP locale n'est plus forcément nécessaire ce qui simplifie grandement la mise en oeuvre du mode multi-joueurs. Cependant, gardez à l'esprit les manipulations suivantes au cas où vous rencontriez des problèmes, elles peuvent vous aider.

Dans un premier temps, vous avez besoin de connaître l'adresse IP de votre ordinateur. En général, il s'agit d'une adresse de classe C du type 192.168.0.x mais elle peut être différente, tout dépend de votre installation.
La configuration la plus courante est un ordinateur derrière une ''box'' avec une connexion Ethernet entre les deux, cette ''box'' étant en fait un routeur.
Au niveau de ce routeur, vous devrez rediriger toutes les connexions entrantes sur les ports 5000 et 5001 en UDP vers votre ordinateur en ajoutant une route statique. Pour cela, connectez-vous via un navigateur sur votre box et cherchez un menu de configuration du type "route statique" ou quelque chose comme cela.
Cette modification indiquera à votre box qu'elle devra rediriger toute connexion entrante sur les ports 5000 et 5001 vers votre ordinateur.
Selon le modèle de votre box (et il y en a beaucoup), vous serez sûrement obligé de la redémarrer.

Si votre ordinateur est directement connecté à un modem ADSL via une liaison USB, vous aurez alors besoin de connaître l'adresse IP qui vous est attribuée par votre fournisseur d'accès. Pour cela, ouvrez un navigateur et allez sur [http://www.whatismyip.com cette page]. Dans ce cas, vous n'avez pas besoin de suivre les manipulations qui suivent et qui permettent de connaître l'adresse IP locale.

Pour connaitre l'adresse IP de votre ordinateur, voici comment faire:

* Sous '''Linux''', dans un shell, tapez la commande suivante:

<code>
/sbin/ifconfig
</code>

Vous devriez obtenir quelque chose comme ça:

<code>

eth0 Link encap:Ethernet HWaddr 00:0b:cd:98:4a:5c
inet adr:192.168.1.67 Bcast:192.168.1.255 Masque:255.255.255.0
adr inet6: fe80::20b:cdff:fe98:4a5c/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Packets reçus:2379 erreurs:0 :0 overruns:0 frame:0
TX packets:1915 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:1595650 (1.5 MB) Octets transmis:331672 (331.6 KB)
...

</code>

Dans cet exemple, la commande ''ifconfig'' renvoie la configuration de l'interface eth0. Vous pouvez bien sûr disposer d'interfaces réseau supplémentaires. L'important est de connaitre l'adresse IP de l'interface réseau par laquelle vous êtes connecté à internet.
Si vous êtes connecté par une interface Wifi, vous aurez vraisemblablement une interface nommée ''wlan0''.

* Sous '''Windows 98/Me/Se''', faites ''Démarrer->Executer'', puis tapez ''winipcfg''.

Ceci devrait ouvrir une fenêtre vous montrant tous les paramètres des interfaces réseau, dont l'adresse IP de votre machine.

* Sous '''Windows XP/Vista''', ouvrez une commande DOS ''Démarrer->Accessoires->Invite de commande'', puis tapez la commande suivante:

<code>
ipconfig /all
</code>

Ceci devrait également vous fournir toutes les informations relatives à votre (ou vos) carte réseau.

Si votre routeur (votre box) et/ou votre machine met en oeuvre un firewall, vous devrez lui indiquer de laisser passer les requêtes entrantes et sortantes sur les ports 5000 et 5001 sinon elles resteront bloquées et vous ne pourrez pas vous connecter en multi-joueurs.

Finalement, une fois votre installation correctement configurée, vous pouvez lancer FlightGear avec la commande suivante:

<code>
fgfs --callsign=''votre_callsign'' --multiplay=in,10,''votre_adresse_ip'',5000
--multiplay=out,10,mpserver10.flightgear.org,5000 --airport=KSFO
--runway=19R --aircraft=c172p
</code>

Remplacez ''votre_callsign'' par votre indicatif dans ''FlightGear''. De même, remplacez ''votre_adresse_ip'' par l'adresse IP de votre ordinateur (par exemple: 192.168.0.15).
Notez que votre indicatif sera tronqué à une longueur de 7 caractères maximum.

Si tout se passe bien, vous devriez vous retrouver sur l'aéroport (ici KSFO, San Francisco) et voir les autres pilotes connectés. Il vous sera également possible de ''chatter'' avec eux.

Vous pouvez consulter le tracker à cette URL: [http://fgfs.i-net.hu/modules/fgtracker/ this page] pour voir si vous voyez votre indicatif. Si vous le voyez, cela signifie que tous vos vols seront enregistrés ce qui vous permettra d'avoir un relevé précis de votre nombre d'heures de vol.

Si malgré tout ceci, vous rencontrez des difficultés, allez jeter un coup d'oeil au forum, vous trouverez sûrement des posts faisant état de problèmes similaires, ainsi que des solutions apportées.
Si au final vous n'avez toujours rien, n'hésitez pas à poster un message sur le forum et à être le plus précis possible.

== Chat en multijoueurs ==

Vous avez la possibilité de "chatter" avec d'autres personnes connectées de la même manière que vous le feriez avec une messagerie instantanée.
Allez dans le menu "Network" puis sélectionnez l'entrée "Chat". Une fenêtre va alors s'ouvrir dans laquelle vous pourrez retrouver l'historique des discussions entre les personnes connectées ainsi qu'une zone de saisie de texte dans laquelle vous pourrez taper votre texte et l'envoyer par un clic sur le bouton "Send".

Cependant, avoir constamment cette fenêtre affichée peut être gênant surtout lorsque vous êtes en vol. Aussi, il existe une autre possibilité plus rapide pour envoyer un message texte. Tapez sur la touche "_" (souligné). Il s'agit d'un raccourci clavier. Une petite zone de saisie apparaît alors et vous pouvez taper directement votre texte, puis l'envoyer en appuyant sur la touche "Enter" ou "Entrée".

Tous les messages émis entre les pilotes connectés apparaissent en haut de l'écran, et sont centrés horizontalement. Ils restent affichés quelques instants avant de disparaître, laissant la place à d'autres messages.

Notez que taper des messages alors que vous êtes en vol peut être difficile, surtout si vous êtes en train de voler avec un hélicoptère pour lequel le pilotage requiert une attention à chaque instant. C'est pour cela qu'il existe des projets de simulation de communications vocales comme le projet ''fgcom''. Alors que ''fgcom'' s'intègre bien avec ''Flightgear'', d'autres personnes utilisent ''Mumble'' pour communiquer.
Il existe également un autre projet qui n'en est qu'à ses début, il s'agit du projet réseau Wavac.

==Liens en rapport avec ce sujet==
* [[Howto: Set up a multiplayer server]]
* [[FlightGear Multiplayer Server]]

[[Category:Howto|Multiplayer]]

[[en:Howto: Multiplayer]]
[[es:Howto: Multijugador]]
[[nl:Howto: Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]

Nl/Howto: Multiplayer

2011-03-03T20:25:02Z

IonCannon218: /* Servers */

De '''Multiplayer''' functie van [[FlightGear/nl|FlightGear]] maakt het mogelijk om andere vliegtuigen te zien. Zo kan er in formatie worden gevlogen, in de lucht worden [[Howto: Air-Air Refueling|bijgetankt]] en de [[ATC|luchtverkeersleiding]] kan worden aangesproken.

Multiplay kan de framerate drastisch verlagen, vooraal tijdens het laden van een nieuw vliegtuig. Aangezien [[San Francisco International Airport|San Francisco]] het standaard vliegveld is, en daardoor het drukste, kan het slim zijn om het te vermijden. Meestal zijn elders ook meer serieuse piloten te vinden.

== Servers ==
'''Let op:''' de servers zijn onderling verbonden; het is niet nodig om op een bepaalde server te vliegen om anderen op diezelfde server te kunnen zien. Voor de beste prestaties is het slim om de dichtsbijzijnde of snelste en rustigste server te gebruiken.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2"
!Server
!Locatie
![http://fgfs.i-net.hu/modules/fgtracker/ Gevolgd]
!Eigenaar
!Opmerkingen
|-
|mpserver01.flightgear.org
|Duitsland
|Ja
|Oliver Schroeder
|
|-
|mpserver03.flightgear.org
|Duitsland
|Ja
|
|Langdurig offline
|-
|mpserver04.flightgear.org
|Engeland
|Ja
|Jon Stockill
|
|-
|mpserver05.flightgear.org
|Chicago, VS
|Ja
|Brant
|
|-
|mpserver06.flightgear.org
|Zweden
|Nee
|Anders Gidenstam
|
|-
|mpserver07.flightgear.org
|Wisconsin, VS
|Ja
|Tom Betka
|
|-
|mpserver08.flightgear.org
|Frankfut am Main, Duitsland
|Ja
|Roland
|
|-
|mpserver09.flightgear.org
|Köln, Duitsland
|Ja
|Daniel Vigano
|
|-
|mpserver10.flightgear.org
|Montpellier, Frankrijk
|Ja
|Alexis Bory
|
|-
|mpserver11.flightgear.org
|Vilnius, Litouwen
|Ja
|Darius
|
|-
|mpserver12.flightgear.org
|Amsterdam, Nederland
|Yes
|Rob
|
|}

Gebruik [http://pigeond.net/flightgear/mpstatus/ deze link] om te zien welke servers online zijn.
[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Map ===
{{Main article|MPMap}}

Geeft de locatie van alle vliegtuigen welke op de servers vliegen weer. Zowel te bereiken via [http://mpmap01.flightgear.org mpmap01] als [http://mpmap02.flightgear.org mpmap02]. De map kan handig zijn om te controleren of de connectie met de server is gelukt.

== De Windows launcher (fgrun) gebruiken==
[[Image:Multiplayer.jpg|thumb|300px|Multiplayer instelling in de [[FlightGear Wizard|FG Launcher]]]]
#Selecteer een vliegtuig en vliegveld als gewoonlijk.
#Klik op het volgende scherm de "Multiplayer" optie aan. Doe hetzelfde voor de "Computergestuurde modellen", anders zal je geen andere vliegtuigen zien. Voer een callsign naar keuze in (controleer wel eerst of niemand anders onder dezelfde naam vliegt!), kies een server en vul zowel bij "in" als "uit" 5000 in.
#Klik op start en ontmoet andere piloten!

==Geraleteerde inhoud==
* [[Howto: Set up a multiplayer server]]
* [[FlightGear Multiplayer Server]]

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

Es/Howto: Multijugador

2011-03-03T20:24:24Z

IonCannon218: /* Servidores */

Con la función '''Multijugador''' de [[FlightGear]] puedes ver a otros pilotos y viceversa. Esto hace posible el vuelo en formación, y [[Howto: Air-Air Refueling|conectarse a aviones cisterna]], controlados por usuarios reales o contactar con [[ATC]]s reales para pedir autorización aterrizaje/despegue.

Si estas interesado en alojar tu propio servidor Multijugador, necesitarás entrar en [[Howto: Set up a multiplayer server|como configurar un servidor Multijugador..]].

Multijuego puede causar grandes caidas de la [[Howto: Improve Framerates|tasa de fotogramas]], durante la carga de una nueva aeronave. Especialmente los modelos pesados pueden causar demoras. Por tanto se sugiere volar en Europa o en algun otra zona que no sea alrededor de San Francisco en donde hay muchos pilotos volando.

== Servidores ==
'''Por favor ten encuenta que:''' Los servidores multijugador están interconectados; Tu '''no tienes''' la necesidad de conectarte a un servidor especifico para poder ver otros pilotos que esten volando en ese servidor. Para tener el mejor rendimiento, deberías conectarte al servidor que esté geográficamente mas próximo a ti, que tenga la menor latencia (tiempo de respuesta ping) o que sea el mas tránquilo.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2"
!Servidor
!Ubicación
![http://fgfs.i-net.hu/modules/fgtracker/ Rastreo]
!Mantenedor
!Commentarios
|-
|mpserver01.flightgear.org
|Germany
|Yes
|Oliver Schroeder
|
|-
|mpserver03.flightgear.org
|Germany
|Yes
|
|Caído por un largo periodo de tiempo
|-
|mpserver04.flightgear.org
|UK
|Yes
|Jon Stockill
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Yes
|Brant
|
|-
|mpserver06.flightgear.org
|Sweden
|No
|Anders Gidenstam
|Tubo estrecho.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Yes
|Tom Betka
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Yes
|Roland
|
|-
|mpserver09.flightgear.org
|Köln, Germany
|Yes
|Daniel Vigano
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Yes
|Alexis Bory
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Yes
|Darius
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|Yes
|Rob
|
|}

Usa [http://pigeond.net/flightgear/mpstatus/ este] enlace para comprobar si los servidores Multijugador estan en línea.
[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Mapa Multijugador ===
{{Main article|MPMap}}

Hay un mapa muy majo que muestra la ubicación de los pilotos en línea en [http://mpmap01.flightgear.org mpmap01] y/o en [http://mpmap02.flightgear.org mpmap02]. También podrás encontrar útil comprobar que estás conectado con éxito en el servidor.

== Usando el lanzador de Windows / fgrun ==
[[Image:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
#Selecciona tu [[aircraft|aeronave]] y el aeropuerto de partida como es normal en [[FlightGear Launch Control|Fgrun]].
#En la siguiente pantalla, marca la casilla "Multiplayer". Marca también la casilla "AI models" o no podrás ver las aeronaves de otros pilotos. Introduce el identificativo ("Callsign") de tu elección, introduce mpserver01.flightgear.org en en la casilla de nombre de anfitrión ("Hostname") y 5000 en ambas casillas "in" and "out".
#Haz click en run y pronto estarás volando con otros pilotos!

Para confirmar que está funcionando, puedes ir al mapa multijugador de; http://mpmap02.flightgear.org/ (en Hong Kong).
También advertirás mensajes de chat diciendo "Hello" indicando como se van uniendo pilotos que estan en linea.
Quizás desees usar un servidor diferente (e.j. "Hostname" introducir);

Para más ajustes avanzados, la pestaña de <tt>Advanced > Network</tt> puede ser abierta.Por ejemplo solo a través de este metodo tienes la posibilidad de quitar las lineas in o out.

== Usando fgfs desde la linea de comandos ==

De primeras, para todos aquellos que esten muy impacientes y que tengan una vaga idea de lo que estamos haciendo, los argumentos básicos que hay que pasar a fgfs para multijugador son estos.;

--multiplay=out,10,server.ip.address,portnumber
--multiplay=in,10,your.ip.address,portnumber
--callsign=anything

En donde portnumber es usualmente 5000 y tu.dirección.ip es la dirección ip de la interfaz de red usada por FG para conectar con el sevidor - incluso si esta fuera una dirección local tipo 192.168. Por favor ten en cuenta que aunque esta limitación ha sido quitada en las versiones más recientes del servidor FG; todavía deberias especificar una dirección IP (no-loopback, e.j. no 127.0.0.1) para mantener al cliente FG contento.

Con los últimos FlightGear (al menos con OSG), también puedes dejar tu.dirección.ip en blanco. FlightGear entonces escucha en todos las interfases de red:

--multiplay=in,10,,5000

=== Ahora, vamos más despacio para aquellos que esten completamente perdidos... ===

Intenta lo de arriba primero, y si no funciona, lee esto.

Lo primero de todo, tienes que saber la dirección IP de la intefaz de red que estes utilizando para FlightGear multijugador. Si tu conexión a internet es via modem ADSL que esta conectado directamente sobre tu computadora con conexión USB, deberás poder encontrar tu dirección IP visitando http://www.whatismyip.com . Por favor advierte que tu ISP puede que no te de la misma dirección IP en cada momento. - si MP deja de funcionar, comprueba primero esto.

Si no es asi, y tu conexión va como via de algun tipo de enrutador que conecta tu computadora via RJ-45, o conector "Ethernet"(similar en forma a la conexión de cable de telefono), o por un enlace inalámbrico. Necesitas encontrar tu dirección IP de ese interfaz de red.

Bajo GNU/Linux, esto se puede encontrar identificandote como root y tecleando "ifconfig". Deberias encontrar más de un interfaz listado, comezando con "lo" - ignora este. Deberias tambien tener algo como "eth0" o "wlan0" en la lista - busca en el bloque de texto "inet addr". Esta estará seguida directamente por el numero que estas buscando, E.j. "inet addr:192.168.0.150"

Bajo Windows Xp, haz click en inicio, ejecutar, y teclea "cmd". En la ventana de terminal que aparece, teclea "ipconfig" Esto deberia mostrar tu dirección IP - anotala.

Con Windows 98, haz click en inicio, ejecutar, y teclea "winipcfg" para conseguir información sobre tu dirección IP.

Esta sección debería ser innecesaria ahora con las versiones recientes del servidor FG. If you have problems though, it won't hurt to follow through.

Ahora, todo (!) lo que queda es configurar tu enrutador para enviar el puerto UDP 5000 a la dirección IP que acabas de encontrar. Esto nos es algo que se pueda describir con detalle paso-a-paso, debido a que la configuración de interfaz de cada fabricante difiere bastante. Algunos puntos de más son dados aqui - if you get stuck, pregunta amablemete en el canal IRC [[FlightGear IRC channel]] para ayudarte (los detalles estan en el sitio web de flightgear ).

Deberás saber como entrar en la página de configuración del enrutador, usualmente via navegador web. Busca los ajustes pertinentes de "port forwarding" "virtual server" "Forwarding Rules" o similar. Cuando encuentres los ajustes relevantes, necesitas añadir una regla que envia el puerto 5000 a la dirección IP que descubriste antes. Si hay una elección dada, asegurate que esta es la de los puertos UDP que estan enviados. Si no hay otra elección, deberias asumir que ambos TCP y UDP estan siendo enviados. Salva tu configuración, muchos enrutadores necesitarán ser luego rearrancados para aplicar los cambios.

Nota: (para usuarios de BSD) si estas usando modem ADSL, deberás poner el comando de puerto adelantado en el archivo ppp.conf preferiblemente y no en el firewall. Esto es por que el codigo del cortafuegos correrá solo en el momento en el que la máquina es arrancada para que hacer que el código ppp vuelva a estar en linea.

Finalmente, inicia FG usando la línea de comando dada justamente al principio (si estas usando el lanzador de windows encontrarás cajas de entrada para los argumentos Multijugador - inserta los detalles relevantes allí). Acabaras con algo como esto;

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

Escoje tu propio identificativo (callsign) - este esta actualmente limitado a siete carácteres.<br>

Una vez has iniciado FG, deberias, si otros estan volando, ver mensajes en el terminal desde el cual se inició FG, similar a lo siguiente;

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

DEBES aportar tu dirección local, detrás-de-la-dirección IP del router para que funcione Multijugador. Confia en mi con esto!

Debes comprobar que tu cortafuegos no está causando problemas - en ese caso apagalo_temporalmente o añade una excepción para permitir las conexiones entrantes en el puerto 5000.

Si todavia no te funciona, pregunta amablemente en el canal de irc [[FlightGear IRC channel]] alguien deberia poder atenderte.

== Chat Multijugador ==
{{Main article|Chat Menu}}

Para charlar con otros pilotos, ve al menú "Network" y selecciona "Chat" en la primera opción del menú.
NOTA: El chat multijugador no es soportado por FlightGear 0.9.10.
El acceso directo para charlar es"_" (guión bajo) y te trae una pequeña ventana donde puedes teclear. Por defecto los mensajes de otras personas son visualizados en la parte de arriba de la ventana de FlightGear por unos segundos, pero aparacen por mucho mas tiempo si en la ventana de chat haces click en More V. Asi que si crees que has pedido algo, ve y miralo allí.

En la opción del menú Chat menu, puedes acceder a las opciones mas comunes de la fraseología aeronáutica o incluso editarlas, sin duda te pueden ser utiles para familiarizarte si desconoces tales terminos.

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

[[Category:Howto|Multiplayer]]

[[en:Howto: Multiplayer]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]

Howto:Multiplayer

2011-03-03T20:22:21Z

IonCannon218: /* Servers */

With the '''multiplayer''' function of [[FlightGear]] you are able to see other pilots and vice-versa. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers 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 [[KSFO]], where there are fewer pilots flying around.

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

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2"
! style="background:#efefef" |Server
! style="background:#efefef" |Location
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracked]
! style="background:#efefef" |Maintainer
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Comments
|-
|mpserver01.flightgear.org
|Germany
|Yes
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Yes
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|UK
|Yes
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Yes
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|No
|Anders Gidenstam
|AndersG
|AndersG
|Thin Pipe.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Yes
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Yes
|Roland
|Quix0r
|Quix0r
|10 TByte traffic!
|-
|mpserver09.flightgear.org
|Köln, Germany
|Yes
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Yes
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Yes
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|Yes
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Yes
|Charles Ingels
|charles
|cbz-026
|
|}

Use [http://mpmap01.flightgear.org/mpstatus/ this] or [http://mpmap02.flightgear.org/mpstatus/ this] link to check if the MP servers are online. Locations of the servers are also available at [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps].

If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].
[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Map ===
{{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.

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

== Using the Windows launcher / FGRun ==
[[Image: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. Enter the callsign of your choice (check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether it is already in use or not. Do not pick a callsign that is already used!), enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes.
#Click run and you'll soon be flying with other pilots!

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

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

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

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

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

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

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

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

--multiplay=in,10,,5000

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

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

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

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

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

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', 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=MyName --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.

== 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 Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

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

[[Category:Howto|Multiplayer]]

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

Howto:Multiplayer

2011-03-03T20:17:43Z

IonCannon218: /* Servers */

With the '''multiplayer''' function of [[FlightGear]] you are able to see other pilots and vice-versa. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers 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 [[KSFO]], where there are fewer pilots flying around.

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

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2"
! style="background:#efefef" |Server
! style="background:#efefef" |Location
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracked]
! style="background:#efefef" |Maintainer
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Comments
|-
|mpserver01.flightgear.org
|Germany
|Yes
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Yes
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|UK
|Yes
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Yes
|Brant Gipson
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|No
|Anders Gidenstam
|AndersG
|AndersG
|Thin Pipe.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Yes
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Yes
|Roland
|Quix0r
|Quix0r
|10 TByte traffic!
|-
|mpserver09.flightgear.org
|Köln, Germany
|Yes
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Yes
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Yes
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|Yes
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Yes
|Charles Ingels
|charles
|cbz-026
|
|}

Use [http://mpmap01.flightgear.org/mpstatus/ this] or [http://mpmap02.flightgear.org/mpstatus/ this] link to check if the MP servers are online. Locations of the servers are also available at [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps].

If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].
[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Map ===
{{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.

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

== Using the Windows launcher / FGRun ==
[[Image: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. Enter the callsign of your choice (check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether it is already in use or not. Do not pick a callsign that is already used!), enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes.
#Click run and you'll soon be flying with other pilots!

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

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

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

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

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

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

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

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

--multiplay=in,10,,5000

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

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

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

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

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

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', 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=MyName --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.

== 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 Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

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

[[Category:Howto|Multiplayer]]

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

Howto:Set up a multiplayer server

2009-10-12T23:50:05Z

IonCannon218: /* Facts */

{{Languages|Howto: Set up a multiplayer server}}
How to use [[FlightGear Multiplayer Server]]

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

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

= Traffic & Bandwidth Considerations =

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

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

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

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

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

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

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

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

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

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

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

= Getting fgms =

* download the latest stable version via http://fgms.sourceforge.net/stableversion.php / http://fgms.sourceforge.net/download.php, follow the instructions

(As of 05/2008, the latest stable version is still available via http://www.o-schroeder.de/fg_server/fgms-0.9.11.tar.gz)

To download a file to a server from an ssh session, you could use tools such as wget or lynx, i.e.:

$ FGMSURL=http://www.o-schroeder.de/fg_server/fgms-0.9.11.tar.gz wget $FGMSURL

= Compiling FGMS =
('''Note:''' if you want to build/install fgms using customized paths or settings (i.e. as non-root user, installing into your $HOME), you may want to consult the INSTALL file located in the source directory for additional help)

#. Extract the file to a temporary directory (i.e. using tar xzf filename.tgz) and cd into it
#. Run ''./configure'' to create the Makefile
#. Run ''make'' to build the packages.

You can combine the two latter steps by running:

$ ./configure && make

(In general, on any current machine this should ''not'' take any longer than 30-60 seconds)

= Setting up the config file =

At this point you should have a working fgms binary in the directory ''src/server'', so copy fgms_example.conf to fgms.conf and edit it to suit your situation. If the server will be offline or for private use (i.e. LAN-only, please comment out the relay servers section. This will save bandwidth from the server being consumed.

= Installation =

To install fgms, type ''make install''.
If you want to install fgms without root privileges, you will have to customize your configuration and build settings accordingly (please consult the previously mentioned INSTALL file or run ./configure --help for details). To install fgms within a subdirectory of your home directory, named 'bin' you could for example run:

$ PREFIX=~/bin ./configure --prefix=$PREFIX && make install || echo "Oops, there was a problem !"

Depending on whether ~/bin exists already and is already specified in your $PATH environment variable, you may also want to add this folder to $PATH.

= Running FGMS for the first time =

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

Which should present you with the following output:

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

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

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

=Related articles=
*[[MPmap]]
*[[Howto: Multiplayer]]

[[Category:Howto|Set up a multiplayer server]]