FlightGear wiki - User contributions [en]

Pt/Tutorial de Multiplayer

2017-12-29T18:46:32Z

Hergen: /* Servidores */

A função '''multi-jogador''' do [[pt/FlightGear|FlightGear]] torna possível ver outros pilotos e vice-versa. Isto torna possível voar em formação, realizar [[mid-air refueling|reabastecimentos aéreos]] com "tanques" controlados por pessoas reais ou contactar [[air traffic control|controladores de tráfego aéreo]] para pedir por orientação.

O multi-jogador pode causar [[troubleshooting performance issues|caídas de cadência]] extremas durante o carregamento de modelos de aeronaves, especialmente modelos pesados como o [[Boeing 777]] ou o [[Airbus A320neo]]. É sugerido voar em localizações que não incluam o aeroporto padrão [[San Francisco International Airport|Aeroporto Internacional de São Francisco]], devido a haver muitos pilotos na área que são, frequentemente, novos e não seguem CTA ou respeitam o tráfico.

==Notas==

* Indicativos de chamada podem ter um máximo de sete caracteres
* Pode querer verificar a secção de [[#Problemas conhecidos|problemas conhecidos]]

==Conectar ao Multi-jogador==
===Diálogo no simulador===
[[File:Multiplayer settings dialog.jpg|thumb|Caixa de diálogo das definições multi-jogador]]
A forma mais fácil de se ligar é com o diálogo de multi-jogador incorporado no simulador. Basta só introduzir um indicativo de chamada e selecionar um servidor do menu. Clique em {{button|Conectar}} para se ligar.

===Utilizando o ''FGRun''===
====Da página principal====
[[File:Multiplayer.jpg|thumb|Definições de multi-jogador no ''[[FGRun]]'']]
# Selecione a sua [[pt/Aeronaves|aeronave]] e aeroporto de partida como normal no ''[[FGRun]]''.
# No último menu, marque a caixa "''Multiplayer''". Certifique-se que a caixa "''AI models''" está selecionada, de modo a poder ver as aeronaves dos outros pilotos.
# Introduza...
#* '''''Callsign''''' da sua escolha.
#* '''''Hostname:''''' Introduza <code>mpserverXX.flightgear.org</code> (com <code>XX</code> sendo o [[#Servidores|número do servidor]]).
#* '''''In/out:''''' Designe ambos 5000.
# Clique {{button|''Run''}} para começar o FlightGear.
Para confirmar que está a funcionar, pode aceder ao mapa multi-jogador em http://mpmap02.flightgear.org/ (em Hong Kong). Assim que o FlightGear tenha começado, observará as mensagens do ''chat'' que dizem "''Hello''", indicador dos pilotos que estão ''online''. Também aparecerão quando um piloto se junte à rede ''MP''. Pode editar esta mensagem ao editar esta linha em <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>
Quererá utilizar um servidor diferente, especialmente um perto de si.

====Das definições de rede====
[[File:FGRun Advanced dialog - Network.png|thumb|A ''tab'' da "''<tt>Network</tt>''" (rede) da caixa de diálogo "''Advanced Options''" (Opções avançadas) no ''[[FGRun]]'' (no [[Changelog 3.2|FlightGear 3.2.0]]).]]
Também pode modificar as definições de multi-jogador na ''tab'' ''<tt>Network</tt>'' (Rede) das "''Advanced Options''" (Opções avançadas) do ''FGRun''.
# Na última página, clique em {{button|Advanced}}.
# Clique ''<tt>Network</tt>'' (Rede) na coluna esquerda.
# Na área ''<tt>Multiplayer Options</tt>'' (Opções multi-jogador)...
#* Escreva o indicativo de chamada desejado na caixa.
#* Defina os parâmetros das outras duas caixas; veja [[#Utilizando o multi-jogador pela linha de comando|abaixo]] para o sintaxe correcto.
#* Clique em {{button|OK}}, e depois corra o FlightGear.

=== Utilizando o multi-jogador pela linha de comando ===
Quando executa o FlightGear pela [[command line|linha de comando]], pode especificar as opções multi-jogador. Os dois argumentos são os seguintes:
<syntaxhighlight lang="bash">
--multiplay=direction,10,ip.address,port
--callsign=anything
</syntaxhighlight>

Evidentemente, <code>--callsign</code> pode ser tudo o que desejar. Existem quatro argumentos para com <code>--multiplay</code>:
; ''direction'' (direcção)
: <code>in</code> ou <code>out</code>. <code>in</code> diz ao FlightGear para ouvir a todos os pacotes de dados vindos pela '''porta''' especificada. <code>out</code> diz ao FlightGear para enviar dados pela '''porta'''

; ''ip.address''
: Endereço ''IP'' do interface da rede a ser utilizado pelo FlightGear. Se em branco, FlightGear ouvirá todos os interfaces da rede. Se a '''''direction''''' (direcção) estiver definida para <code>in</code>, FlightGear ouvirá '''só''' este endereço ''IP''.

; ''port'' (porta)
: A porta por qual os dados são enviados ou recebidos. Geralmente definido como <code>5000</code> e acima.

== Uso avançado do multi-jogador ==
=== Configuração local para testes ===
É possível configurar uma rede de multi-jogador local entre duas instâncias de FlightGear '''sem''' utilizar um [[FGMS|servidor multi-jogador]]. Tudo o que precisa fazer é mapear cada porta ''I/O'' de uma instância com a(s) porta(s) correspondente(s) da outra instância:

{{Note|
{{FGCquote
|''Traduzido/translated''

Uma conexão ''socket'' necessita não só de um endereço ''IP'', mas também um número de porta para cada lado da ligação - imagina um número de porta como se fosse uma "caixa-de-correio" num endereço. Esta caixa-de-correio é utilizada pelos processos de comunicação para enviar e receber "mensagens". Processos diferentes (mesmo quando programas possivelmente idênticos) precisarão de utilizar números de porta diferentes quando sendo executados, porque portas abertas ({{=}}caixas-de-correio) não podem ser partilhadas.

Portanto, terás de modificar as definições da porta no lado do cliente por cada instância adicional que estejas a correr na mesma máquina, e mapear a porta ''output'' de uma instância à porta ''input'' da outra instância (e 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>5ª-Feira, 10 de Junho</nowiki>
}}
}}
}}

Parâmetros de linha de comando para a primeira instância:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=Test1
</syntaxhighlight>

Parâmetros de linha de comando para a segunda instância:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=Test2
</syntaxhighlight>

Pode utilizar este tipo de configuração para testar funções relacionadas ao multi-jogador ou para solucionar relatórios de ''bugs'' relacionados com o multi-jogador, quais seriam difícil de reproduzir pelo ''MP''. Como não pode aceder às configurações do FlightGear de terceiros, esta técnica permite-lhe o controlo completo sobre as definições do FlightGear.

[[File:Direct-p2p-multiplayer-setup.png|800px|Um ''Screenshot'' demonstrando uma configuração "''peer-to-peer''" entre duas instâncias do FlightGear, a correr na mesma máquina via ''localhost'' (127.0.0.1), sem qualquer servidor multi-jogador.]]

Pode adicionar um número arbitrário de canais para copiar o seu vôo para outros servidores, por exemplo para um servidor ''fgms'' privado utilizando
<syntaxhighlight lang="bash">
--multiplay=out,10,my.private.server.ip,5000
</syntaxhighlight>

Adicionalmente, o argumento acima <code>in</code> diz ao FlightGear para '''só''' ouvir no ''loopback''/interface local - não vai receber pacotes que cheguem na(s) outra(s) interface(s) de rede. Se também quer ligar a outras interfaces, simplesmente omite o endereço ''IP'' utilizando
<syntaxhighlight lang="bash">
--multiplay=in,10,,5000
</syntaxhighlight>

Veja [http://fgfs.i-net.hu/modules/fgtracker/ esta página] para ver se o seu indicativo de chamada já está em uso ou não. Não escolha um indicativo de chamada que já esteja em uso, porque tal criará problemas!

==== Agora, para aos que estão completamente perdidos... ====
{{Note|Esta secção poderá conter informações desactualizadas ou incorrectas.}}

Esta secção '''devia''' devia ser desnecessária graças às versões recentes dos servidores do ''FG''. Contudo, se tiver com problemas, não dói se continuar a ler.

Primeiro, precisará de descobrir o endereço ''IP'' do interface da rede que irá utilizar para o multi-jogador no ''FG''.

Se a sua conexão ''Internet'' for através de um ''modem'' ADSL que está ligado directamente ao seu computador, há de descobrir o seu endereço ''IP'' visitando http://www.whatismyip.com.
{{Note|O seu {{Abbr|ISP|Inglês para "fornecedor de acesso à Internet"}} poderá dar-lhe um endereço ''IP'' diferente cada vez que se ligar.}}

Se a sua conexão for via um cabo ''Ethernet'' ou uma ligação sem-fio.

*'''''Linux:''''' Faça o ''log-in'' como ''root'' e execute <code>ifconfig</code> no terminal. No texto que-lhe é apresentado, procure por um nome de interface como <code>eth0</code> ou <code>wlan0</code>. Por fim, procure, sob o nome do interface, o texto <code>inet addr:ip.adress</code>. Por exemplo, devia mostrar algo como <code>inet addr:192.168.0.150</code>.
*'''''Windows:'''''
**'''''Windows XP''''' '''ou posterior:''' Execute uma linha de comando e digite <code>ipconfig</code> no terminal. Note o endereço de ''IP''
**'''''Windows 98:''''' Clique Iniciar, Correr, e digite "winipcfg" para obter informações sobre o seu endereço IP.

Agora, tudo o que resta é configurar o seu ''router'' para redirecionar a porta ''UDP'' 5000 ao endereço ''IP'' que acabou de encontrar. Isto não é algo que se possa descrever passo-a-passo, porque os interfaces de configuração de cada fabricante diferem muito. Vamos-lhe dar algumas dicas - se debater-se com problemas, peça cordialmente por ajuda no [[FlightGear IRC channel|canal ''IRC'' do FlightGear]] (detalhes na página do FlightGear).

Deve saber como fazer o ''log-in'' na página de configuração do seu ''router'', tal geralmente feito por um navegador ''web''. Estamos à procura de definições referindo a "redirecionamento de portas", "servidores virtuais", "regras de redirecionamento" ou semelhantes. Quando tiver encontrado as definições relevantes, terá de adicionar uma regra que redirecione a porta 5000 ao endereço ''IP'' que recentemente descobriu. Se lhe é posta a escolha, segure-se que a porta que redirecione é ''UDP''. Se não pode escolher, podemos assumir que ambos ''TCP'' e ''UDP'' estão a ser redirecionados. Grave as suas configurações, e dado que a maior parte dos ''routers'' terão de ser recomeçados para poder aplicar as definições, faça tal.

{{Note|Utilizadores de ''BSD'': Se estiver a usar um ''modem'' ADSL, poderá ter de por o comando de redirecionamento da porta no ficheiro "ppp.conf" em vez da ''firewall''. Isto deve-se que o ''script'' da ''firewall'' só correrá cada vez que a máquina for reiniciada ao cabo da linha "ppp", que o faz sempre que se ligar à ''Internet''.}}

Por fim, comece o ''FG'' utilizando a linha de comando dado no início desta página (se estiver a utilizar o lançador do ''Windows'', encontrará caixas para preencher com argumentos de multi-jogador - digite os detalhes relevantes aqui). Acabará com algo semelhante a isto:
<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>

Escolha o seu indicativo de chamada, mas verifique [http://fgfs.i-net.hu/modules/fgtracker/ esta página] primeiro para saber se o seu indicativo de chamada desejado já está a ser usado ou não. Não escolha um indicativo de chamada que já esteja a ser usado, qual criará problemas!

Assim que tiver começado o ''FG'' deveria, se houverem outros a voar, ver mensagens no terminal de onde o ''FG'' começou, semelhantes a:

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

TEM que dar o seu endereço local ''IP'' para que o multi-jogador funcione. Confie-me neste ponto!

Deve confirmar que a sua ''firewall'' não está a criar problemas - ou desligue-lha '''temporariamente''', ou adicione uma excepção para permitir as conexões vindas da porta 5000.

Se pura e simplesmente continuar a não funcionar, peça cordialmente no [[FlightGear IRC channel|canal ''IRC'']] ou no [http://forum.flightgear.org/ fórum] por ajuda e alguém será capaz de o acudir.

=== Conexões múltiplas por computador ===
É possível executar múltiplas instâncias do FlightGear num único computador e conectar-os todos à rede multi-jogador. Entretanto, isto requer pensar em alguns extras:
# Ambas instâncias utilizam a mesma porta <code>out</code>.
# Uma instância utiliza a porta <code>in</code> <code>5001</code>, a outra a porta <code>5002</code>.
# Ambas as instâncias têm que ter indicativos de chamada únicos.

=== Detecção de colisão opcional no multi-jogador ===

Um ''patch'' foi adicionado ao FlightGear (desde a versão 3.5) que permite a detecção de colisão opcional no multi-jogador. Para ligar a detecção de colisão, comece o FlightGear com:

<syntaxhighlight>
--prop:bool:/sim/multiplay/hot=true
</syntaxhighlight>

Os que são capazes de aplicar ''patches'' de ''FGData'' podem fazer o ''download'' do [http://sourceforge.net/p/flightgear/mailman/attachment/CAHs0wcrEwYZvXTddcUaH0ZMfmVNvEWRap8MXOrEoKybUDO58sQ%40mail.gmail.com/3/ mp-hot-fgdata.patch], que adiciona a ''checkbox'' à caixa de diálogo das definições to multi-jogador para activar ou desactivar a detecção de colisão enquanto o FlightGear corre.

== ''Chat'' multi-jogador ==
{{Main article|Chat Menu}}

Para falar com outros pilotos, vá no menu <tt>Multiplayer</tt> e selecione <tt>Menu Chat</tt> no fim do menu. Note que os outros pilotos podem não ter a caixa do ''chat'' aberta nem terem o serviço de mensagens activado, por isso podem não ver as suas mensagens.

O atalho para falar é {{button|-}} (hífen). Isto mostrará algum texto no canto esquerdo superior da página do FlightGear. Ao clicar nas teclas de dígitos correspondentes, pode enviar mensagens pré-feitas. Clicar no {{button|1}} permite-lhe escrever uma mensagem personalizada, qual pode enviar ao clicar em enter. Por defeito, as mensagens de outros serão exibidas no topo da página do FlightGear por alguns segundos, mas aparecerão por muito mais tempo na janela em <tt>Rede > Chat</tt>. Por isso, se pensa que perdeu algo, vá lá ver.

== Lidar com comportamentos abusivos ==

Caso se torne victima de comportamento abusivo ou irritante devido a qualquer piloto, tem a opção de ignorar-lo/-la. Para activar a função de ignorar, abra a caixa de diálogo <tt>Multiplayer > Lista de pilotos</tt> e clique no botão <tt>ignorar</tt> ao lado do indicativo de chamada do piloto. Isto impede as mensagens do piloto ignorado de aparecer e a aeronave de tal piloto não lhe será visível (a não ser que esteja a usar FlightGear 2.2 ou anterior).

== Mapa multi-jogador ==
[[File:MP_Server.jpg|thumb|300px|''Screenshot'' do [[MPMap]]]]
{{Main article|MPMap}}

Existe um mapa ''online'' muito bom que mostra a localização dos pilotos ligados em [http://mpmap02.flightgear.org ''mpmap02'']. Irá achar útil para certificar-se que está a conectar-se aos servidores com sucesso, tal como para ver ''navaids'', pontos de passagem, aeroportos, frequências, clima e muito mais!

== Servidores ==
Os servidores multi-jogador estão interligados. Tirando poucas excepções, '''não é''' necessário conectar a um servidor específico para ver pilotos em outros servidores. Para o melhor desempenho, deve conectar-se a um servidor que está perto de si geograficamente, tem a menor latência (''ping''), ou está menos ocupado.
{{tip|Utilize [http://mpmap01.flightgear.org/mpstatus/ este ''link''] ou [http://mpserver15.flightgear.org/mpserverstatus/ este] para verificar se os servidores ''MP'' estão ''online''. Ambas as páginas são automaticamente geradas. O [[#Diálogo no simulador|diálogo no simulador]] só mostra os servidores que estão disponíveis.}}

{| class="wikitable sortable"
! Endereço do servidor
! Estado
! Localização
! Rastreado (por [http://mpserver15.flightgear.org ''mpserver15''] se não especificado)
! Mantido por
! Nome no [[IRC]] de quem mantêm
! Nome no [http://flightgear.org/forums fórum] de quem mantêm
! Comentários
|-
| mpserver01.flightgear.org
| {{yes|''Online''}}
| Alemanha
| {{yes|Sim}}
| Oliver Schroeder
| os
| {{N/a}}
| {{N/a}}
|-
| mpserver02.flightgear.org
| {{yes|''Online''}}
| Los Angeles, EUA
| {{no|Não}}
| Lloyd Stevens
| ls4680
| ls4680
| {{N/a}}
|-
| mpserver03.flightgear.org
| {{yes|''Online''}}
| Alemanha
| {{yes|Sim}}
| Hergen
| {{N/a}}
| {{N/a}}
| [https://mpserver03.flightgear.org mpserver03]
|-
| mpserver04.flightgear.org
| {{yes|''Online''}}
| RU
| {{no|Não}}
| Jon Stockill
| Nav
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=738 JonS]
| {{N/a}}
|-
| mpserver05.flightgear.org
| {{no|''Offline''}}
| Chicago, EUA
| {{N/a}}
| Brant
| IonCannon218
| {{N/a}}
| {{N/a}}
|-
| mpserver06.flightgear.org
| {{no|''Offline''}}
| Berlim, Alemanha
| {{N/a}}
| Sven Teichmann
| {{N/a}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11839 D-SAMI]
| Tráfego ilimitado
|-
| mpserver07.flightgear.org
| {{no|''Offline''}}
| Wisconsin, EUA
| {{N/a}}
| Tom Betka
| TB
| {{N/a}}
| ''Offline''
|-
| mpserver08.flightgear.org
| {{no|''Offline''}}
| Frankfurt am Main, Alemanha
| {{N/a}}
| Roland
| Quix0r
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=7512 Quix0r]
| Tráfego a 10 TByte, principalmente ''pings'' curtos
|-
| mpserver09.flightgear.org
| {{no|''Offline''}}
| Colónia, Alemanha
| {{N/a}}
| Daniel Vigano
| Fauchi95
| {{N/a}}
| ''Offline''
|-
| mpserver10.flightgear.org
| {{no|''Offline''}}
| Montpellier, França
| {{N/a}}
| {{usr|Xiii|Alexis Bory}}
| xiii
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=884 xiii]
| {{N/a}}
|-
| mpserver11.flightgear.org
| {{no|''Offline''}}
| Vílnius, Lituânia
| {{N/a}}
| Darius
| {{N/a}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1122 ffg]
| {{N/a}}
|-
| mpserver12.org
| {{yes|''Online''}}
| Amesterdão, Países Baixos
| {{yes|Sim}} (por [http://mpserver12.org mpserver12.org])
| Rob
| evilslut
| {{N/a}}
| Antigamente mpserver12.flightgear.org<ref>http://forum.flightgear.org/viewtopic.php?f=27&t=27453&start=60#p258435</ref>
|-
| mpserver13.flightgear.org
| {{no|''Offline''}}
| Grenoble, França
| {{N/a}}
| Charles Ingels
| charles
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1592 cbz-026]
| {{N/a}}
|-
| mpserver14.flightgear.org
| {{yes|''Online''}}
| RU
| {{yes|Sim}}
| Pete
| {{N/a}}
| {{N/a}}
| {{N/a}}
|-
| mpserver15.flightgear.org
| {{N/a}}
| North Point, Hong Kong
| {{N/a}}
| Hazuki Amamiya
| Hazuki
| Hazuki
| Este é um servidor para rastrear, não para multi-jogador
|-
| mpserver16.flightgear.org
| {{yes|''Online''}}
| Kansas City, Missúri, EUA
| {{yes|Sim}}
| Rob Dosogne
| truthsolo
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9926 truthsolo]
| {{N/a}}
|-
| mpserver17.flightgear.org
| {{no|''Offline''}}
| Cluj, Roménia
| {{N/a}}
| Marius
| tuxum
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11636 tuxum]
| ''Offline''
|-
| mpserver18.flightgear.org
| {{no|''Offline''}}
| Alemanha
| {{N/a}}
| {{N/a}}
| {{N/a}}
| {{N/a}}
| {{N/a}}
|}

Localizações geograficas dos servidores estão disponiveis nos [http://goo.gl/maps/jBwUd mapas Google].

Se está interessado em anfitriar o seu servidor multi-jogador, quererá ver [[Howto: Set up a multiplayer server|Como montar um servidor multi-jogador (Inglês)]]

== Problemas conhecidos ==
=== Fibertel (Argentina) ===
Em Dezembro de 2014, foi dada a informação que a conexão ''UDP'' pela porta 5000 para quem tivesse a {{Wikipedia|Fibertel}} (Argentina) como ''ISP'' não era possível.

A Fibertel Argentina usa aparentemente esta porta para fins de configuração. "Deve estar aberta para todos os utilizadores, mas pode não estar completamente funcional."

A porta 5000 é uma porta genérica, e nem o FlightGear nem o protocolo {{Wikipedia|''UPnP''}} são utilizadores "oficiais" desta porta.

Uma solução seria expandir as portas entre os servidores; por exemplo, mpserver01.flightgear.org → 5001, mpserver02.flightgear.org → 5002

Veja também o [http://forum.flightgear.org/viewtopic.php?f=27&t=24754 ''post'' no fórum] e {{issue|1617}}.

== Conteúdo relacionado ==
* [[FlightGear Multiplayer Server|Servidor multi-jogador FlightGear]]
* [[Howto: Set up a multiplayer server|Como montar um servidor multi-jogador]]
* [[Multiplayer protocol|Protocolo multi-jogador]]
* [[Howto:Transmit_properties_over_MP|Como transmitir propriedades pelo ''MP'']]

{{Appendix}}

[[Category:Multiplayer]]
[[Category:Howto|Multiplayer]]

[[en:Howto: Multiplayer]]
[[de:Howto: Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[it:Come fare:Multiplayer]]
[[nl:Howto: Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]

Nl/Howto: Multiplayer

2017-12-29T18:46:00Z

Hergen: /* 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" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Locatie
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Gevolgd]
! style="background:#efefef" |Eigenaar
! style="background:#efefef" |[[IRC]] naam
! style="background:#efefef" |[http://forum.flightgear.org Forum] naam
! style="background:#efefef" |Opmerkingen
|-
|mpserver01.flightgear.org
|Duitsland
|Ja
|Oliver Schroeder
|
|
|
|-
|mpserver02.flightgear.org
|Kansas, VS
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|[https://mpserver03.flightgear.org mpserver03.flightgear.org]
|Duitsland
|Ja
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|Engeland
|Ja
|Jon Stockill
|
|
|
|-
|mpserver05.flightgear.org
|Chicago, VS
|Ja
|Brant
|
|
|
|-
|mpserver06.flightgear.org
|Zweden
|Nee
|Anders Gidenstam
|
|
|Offline sinds 20-06-2011
|-
|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
|Nee
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, Frankrijk
|Ja
|Charles Ingels
|charles
|cbz-026
|
|}

Gebruik [http://pigeond.net/flightgear/mpstatus/ deze link] om te zien welke servers online zijn. De locatie van de servers is ook beschikbaar via [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps].
[[File: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 ==
[[File: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]]

[[Category:Howto]]
[[Category:Multiplayer]]

[[de:Howto: Multiplayer]]
[[en:Howto:Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[it:Come fare:Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]
[[pt:Tutorial de Multiplayer]]

It/Come fare:Multiplayer

2017-12-29T18:45:13Z

Hergen: /* Server */

{{BeingTranslated}}[[User:Davideruocchio|Davideruocchio]] ([[User talk:Davideruocchio|talk]]) 14:46, 30 June 2015 (UTC)
La funzione '''multiplayer''' di [[It/FlightGear|FlightGear]] rende possibile vedere altri piloti e viceversa. Permette di volare in formazione, di compiere un [[Howto:Aerial_refueling|rifornimento a mezz'aria]] con aerei cisterna controllati da persone reali o di contattare reali [[Air_traffic_control|controllori di volo]] per chiedere assistenza.

Il multiplayer potrebbe causare un'estrema [[Troubleshooting_performance_issues|diminuzione del framerate]] durante il caricamento dei modelli di aeromobili, specialmente modelli più pesanti come il [[Boeing_777|Boeing 777]] o l'[[Airbus_A320neo|Airbus A320neo]]. È consigliato volare in luoghi diversi da quello di default ([[San_Francisco_International_Airport|San Francisco International Airport]]), poiché nell'area sono frequentemente connessi piloti alle prime armi, che non seguono le istruzioni dell'ATC, o non rispettano il traffico.

==Note==
*I callsign possono essere al massimo di sette caratteri.
*Potrebbbe essere utile visitare la sezione [[#Problemi_noti|Problemi noti]].

==Connettersi al Multiplayer==
===Interfaccia interna===
[[File:Multiplayer settings dialog.jpg|thumb|Interfaccia per le impostazioni Multiplayer]]
Il modo più semplice di connettersi online è usare l'interfaccia Multiplayer interna al simulatore. Tutto ciò di cui hai bisogno è inserire un callsign e selezionare un server dal menù. Premi Connect per andare online.

===Usando FGRun===
====Dalla pagina principale====
[[File:Multiplayer.jpg|thumb|Impostazioni del Multiplayer in [[FlightGear_Launch_Control|FGRun]]]]
#Seleziona l'[[It/Aerei|aeromobile]] e l'aeroporto di partenza come di solito in [[FlightGear_Launch_Control|FGRun]].
#Nell'ultima schermata, spunta la casella "Multiplayer". Sii anche sicuro di aver attivato gli "AI models" o non potrai vedere gli aerei degli altri piloti.
#Inserisci un...
#*'''Callsign''' a tua scelta.
#*'''Hostname''': Immetti <code>mpserverXX.flightgear.org</code> (dove <code>XX</code> sta per il [[#Server|numero del server]]).
#*'''In/Out''': Imposta entrambe le porte su 5000.
#Clicca {{button|Run}} per avviare FlightGear.
Per essere certo che funzioni, puoi visualizzare la mappa multiplayer all'indirizzo http://mpmap02.flightgear.org/ (server a Hong Kong). Una volta che FlightGear sarà avviato, potrai notare i messaggi della chat che riportano "Hello" a indicare i piloti che sono online. Appariranno anche quando un pilota si unirà alla rete Multiplayer. Puoi cambiare questo messaggio editando questa linea di codice 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>
Potresti voler usare un server differente, in particolare uno più vicino a te.

====Dalle impostazioni di rete====
[[File:FGRun Advanced dialog - Network.png|thumb|La scheda <tt>Network</tt> dell'interfaccia delle opzioni avanzate in [[FlightGear_Launch_Control|FGRun]] (in [[Changelog 3.2|FlightGear 3.2.0]]).]]
Puoi cambiare le impostazioni del multiplayer anche dalla scheda <tt>Network</tt> tra le opzioni avanzate di FGRun.

#Sull'ultima pagina, clicca {{button|Advanced}}.
#Clicca su <tt>Network</tt> sulla colonna di sinistra.
#Nell'area <tt>Multiplayer Options</tt> ...
#*Scrivi il callsign desiderato nella casella.
#*Imposta i parametri per le altre due caselle; vedi [[#Connettersi_al_multiplayer_dalla_command_line|sotto]] per la sintassi corretta.
#*Clicca su {{button|OK}}, poi avvia FlightGear.

===Connettersi al multiplayer dalla command line===
Avviando FlightGear tramite [[Command_line|command line]], puoi specificare le impostazioni di multiplayer. I due argomenti vanno definiti come di seguito:
<syntaxhighlight lang="bash">
--multiplay=direction,10,ip.address,port
--callsign=anything
</syntaxhighlight>

Ovviamente, <code>--callsign</code> può essere qualsiasi cosa desideri. Ci sono quattro argomenti per <code>--multiplay</code>:
;direction
:O <code>in</code> o <code>out</code>. <code>in</code> dice a FlightGear di ricevere e prestare attenzione ai pacchetti di dati che arrivano tramite la '''port''' (porta) specificata. <code>out</code> dice a FlightGear di inviare i dati tramite quella '''port'''.

;ip.address
:L'indirizzo IP dell'interfaccia di rete usato da FlightGear. Se lasciato bianco, FlightGear ascolterà tutte le interfacce di rete. Se '''direction''' è impostato su <code>in</code>, FlightGear ascolterà ''solo'' quest'indirizzo IP.

;port
:La porta tramite cui i dati sono inviati o ricevuti. Solitamente impostata su <code>5000</code> o più.

==Utilizzo avanzato del multiplayer==
===Avvio locale per test===
È possibile generare una rete multiplayer locale tra due istanze di FlightGear ''senza'' il supporto di un [[FlightGear_Multiplayer_Server|server multiplayer]]. Tutto ciò di cui hai bisogno è associare ogni porta I/O della prima istanza con la/e corrispondente/i porta/e dell'altra:
{{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>
}}
}}
}}{{Note|
{{FGCquote
|[traduzione] Una connessione socket richiede non solo un indirizzo IP, ma anche una numero di porta per ogni lato del collegamento - immagina un numero di porta come una "cassetta delle lettere" posta all'indirizzo. Questa cassetta è usata dai processi di comunicazione per inviare e ricevere "messaggi". Diversi processi (anche se dello stesso programma) avranno bisogno di diversi numeri di porta quando girano. In quanto le porte aperte ({{=}}le cassette) non possono essere condivise.
Perciò, hai bisogno di modificare le impostazioni della porta lato-client per ogni istanza addizionale che stai facendo girare sulla stessa macchina, e associare la porta di output di un'istanza con la porta di output dell'altra (e viceversa).
|{{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>
}}
}}
}}

I parametri della command line per la prima istanza:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=Test1
</syntaxhighlight>

I parametri della command line per la seconda:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=Test2
</syntaxhighlight>

Puoi fare uso di questo tipo di avvio per testare le funzioni relative al multiplayer o per risolvere resoconti di bug collegati al multiplayer che altrimenti potrebbero essere difficili da riprodurre in MP. Poiché non si può accedere alla configurazione di FlightGear di altre persone, questa tecnica permette di avere un completo controllo sulle impostazioni di FlightGear.

[[File:Direct-p2p-multiplayer-setup.png|800px|Screenshot che dimostra un setup "peer-to-peer" tra due istanze di FlightGear che girano sulla stessa macchina tramite localhost (127.0.0.1) senza alcun server multiplayer.]]

Puoi aggiungere un arbitrario numero di canali per far apparire il tuo volo in altri server, ad esempio in un server multiplayer privato, scrivendo
<syntaxhighlight lang="bash">
--multiplay=out,10,IP.del.mio.server.privato,5000
</syntaxhighlight>

Inoltre, l'argomento <code>in</code> di cui sopra dice a FG di ascoltare '''solo''' sull'interfaccia di loopback o locale - non riceverà pacchetti che arrivano su altre interfacce di rete. Se vuoi inglobare lo stesso altre interfacce, ometti semplicemente l'indirizzo IP in questo modo
<syntaxhighlight lang="bash">
--multiplay=in,10,,5000
</syntaxhighlight>

Controlla [http://fgfs.i-net.hu/modules/fgtracker/ questa pagina] per vedere se il tuo callsign è già in uso o meno. Non scegliere un callsign già in uso, altrimenti creerà problemi!

===Connessioni multiple per singolo computer===
È possibile far girare più istanze di FlightGear su un singolo computer e connetterle tutte alla rete del multiplayer. Comunque, ciò richiede alcune cose in più da tenere a mente:
#Entrambe le istanze usano la stessa porta <code>out</code>.
#Un'istanza usa <code>5001</code> come porta <code>in</code>, l'altra la porta <code>5002</code>.
#Entrambe le istanze hanno uguali callsign.

==Chat del Multiplayer==
{{Main article|Chat Menu}}

Per "chattare" con gli altri piloti, apri il menù <tt>Multiplayer</tt> e seleziona <tt>Chat menu</tt> nella parte in alto. Sappi che gli altri piloti potrebbero non avere la casella di chat aperta né i messaggi della chat abilitati, dunque potrebbero non vedere i tuoi messaggi.

Il modo più rapido per chattare è cliccare {{key press|-}} (trattino). L'azione farà comparire alcune righe di testo nella parte in alto a sinistra della finestra di FlightGear. Premendo il tasto numerato corrispondente, puoi mandare messaggi già scritti (standard). Premendo {{key press|1}} avrai modo di digitare un messaggio personalizzato, che potrai inviare premendo Invio. Di default, i messaggi delle altre persone compaiono nella parte alta della finestra di FlightGear per pochi secondi, ma saranno stampati per un tempo molto più lungo nella finestra di <tt>Network > Chat</tt>. Così, se credi di esserti perso qualcosa, va' a controllare là.

==Trattare un comportamento scorretto==
Se dovessi diventare vittima di un comportamento scorretto o fastidioso di un qualsiasi pilota, hai la possibilità di ignorarlo/a. Per attivare la funzione apri l'interfaccia <tt>Multiplayer > Pilot List</tt> e clicca il pulsante <tt>ignore</tt> affianco al callsign del pilota. Ciò impedirà ai messaggi della chat inviati dal pilota ignorato di apparire e non permetterà di vedere il suo aeromobile (salvo che tu stia usando FlightGear v2.2 o precedenti).

==Mappa del Multiplayer==
{{Main article|MPMap}}

Esiste una mappa online molto interessante che mostra la posizione dei piloti online su [http://mpmap02.flightgear.org mpmap02]. La troverai utile anche per controllare d'esserti connesso al server con successo, così come per cercare radiofari (navaids), punti di riferimento (waypoints), aeroporti (airports), frequenze (frequencies), meteo (wheather), e altro!

==Server==
I server multiplayer sono interconnessi. Con poche eccezioni ''non'' hai bisogno di connetterti ha un server specifico per poter vedere altri piloti che sono su quel server. Per le prestazioni migiori dovresti connetterti al server che o è geograficamente più vicino a te, o ha la minor latenza (tempo di ping, cioè di risposta), o è il meno occupato.
{{tip|Serviti di [http://mpmap01.flightgear.org/mpstatus/ questo link] o di [http://mpserver15.flightgear.org/mpserverstatus/ questo] per controllare se i server MP sono online. Entrambe le pagine sono generate automaticamente. L'[[#Interfaccia_interna|interfaccia interna]] mostrerà solo i server disponibili.}}
{| class="wikitable sortable"
! Indirizzo del server
! Stato
! Posizione
! Tracciato (da [http://mpserver15.flightgear.org mpserver15])?
! Manutentore
! Nome su [[IRC]] del manutentore
! Nome del [http://flightgear.org/forums forum] del manutentore
! Commenti
|-
| mpserver01.flightgear.org
| {{yes|Attivo}}
| Germania
| {{yes|Sì}}
| Oliver Schroeder
| os
| {{N/a}}
| {{N/a|Nessuno}}
|-
| mpserver02.flightgear.org
| {{yes|Attivo}}
| Los Angeles, Stati Uniti
| {{yes|Sì}}
| Lloyd Stevens
| ls4680
| ls4680
| {{N/a|Nessuno}}
|-
| mpserver03.flightgear.org
| {{yes|Attivo}}
| Germania
| {{yes|Sì}}
| Hergen
| {{N/a}}
| {{N/a}}
| [https://mpserver03.flightgear.org mpserver03]
|-
| mpserver04.flightgear.org
| {{yes|Attivo}}
| Regno Unito
| {{Yes|Sì}}
| Jon Stockill
| Nav
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=738 JonS]
| {{N/a|Nessuno}}
|-
| mpserver05.flightgear.org
| {{no|Inattivo}}
| Chicago, Stati Uniti
| {{no}}
| Brant
| IonCannon218
| {{N/a}}
| {{N/a|Nessuno}}
|-
| mpserver06.flightgear.org
| {{no|Inattivo}}
| Berlino, Germania
| {{no}}
| Sven Teichmann
| {{N/a}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11839 D-SAMI]
| Traffico illimitato
|-
| mpserver07.flightgear.org
| {{no|Inattivo}}
| Wisconsin, Stati Uniti
| {{N/a}}
| Tom Betka
| TB
| {{N/a}}
| Offline
|-
| mpserver08.flightgear.org
| {{no|Inattivo}}
| Francoforte sul Meno, Germania
| {{No}}
| Roland
| Quix0r
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=7512 Quix0r]
| 10 TByte di traffico, quasi sempre brevi tempi di ping
|-
| mpserver09.flightgear.org
| {{no|Inattivo}}
| Colonia, Germania
| {{N/a}}
| Daniel Vigano
| Fauchi95
| {{N/a}}
| Offline
|-
| mpserver10.flightgear.org
| {{yes|Attivo}}
| Montpellier, Francia
| {{yes|Sì}}
| {{usr|Xiii|Alexis Bory}}
| xiii
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=884 xiii]
| {{N/a|Nessuno}}
|-
| mpserver11.flightgear.org
| {{no|Inattivo}}
| Vilnius, Lituania
| {{No}}
| Darius
| {{N/a}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1122 ffg]
| {{N/a|Nessuno}}
|-
| mpserver12.flightgear.org
| {{yes|Attivo}}
| Amsterdam, Paesi Bassi
| {{yes|Sì}}
| Rob
| evilslut
| evilslut
| {{N/a|Nessuno}}
|-
| mpserver13.flightgear.org
| {{yes|Attivo}}
| Grenoble, Francia
| {{No}}
| Charles Ingels
| charles
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1592 cbz-026]
| {{N/a|Nessuno}}
|-
| mpserver14.flightgear.org
| {{yes|Attivo}}
| Zurigo, Svizzera
| {{yes|Sì}}
| Yves Sablonier
| gral
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=7698 gral]
| {{N/a|Nessuno}}
|-
| mpserver15.flightgear.org
| {{N/a}}
| North Point, Hong Kong
| {{N/a}}
| Hazuki Amamiya
| Hazuki
| Hazuki
| Questo è un server tracciatore, non un server multiplayer
|-
| mpserver16.flightgear.org
| {{yes|Attivo}}
| Kansas City, Missouri, Stati Uniti
| {{yes|Sì}}
| Rob Dosogne
| truthsolo
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9926 truthsolo]
| {{N/a|Nessuno}}
|-
| mpserver17.flightgear.org
| {{no|Inattivo}}
| Cluj, Romania
| {{N/a}}
| Marius
| tuxum
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11636 tuxum]
| Offline
|-
| mpserver18.flightgear.org
| {{no|Inattivo}}
| Germania
| {{yes|Sì}}
| {{N/a}}
| {{N/a}}
| {{N/a}}
| {{N/a|Nessuno}}
|}

La posizione geografica dei server è disponibile anche su [http://goo.gl/maps/jBwUd Google Maps].

Se sei interessato a fornire l'host di un tuo personale server, potresti voler visitare la pagina [[Howto: Set up a multiplayer server]].

==Problemi noti==
===Fibertel (Argentina)===
Nel dicembre 2014, è stato riportato che la connessione UDP tramite la porta 5000 non era possibile per gli utenti il cui {{Wikipedia|Internet Service Provider|ISP|lang=it}} era {{Wikipedia|Fibertel}} (Argentina).

Fibertel Argentina apparentemente usa la porta per propositi di setup. "Dovrebbe essere aperta agli utenti ma potrebbe non essere completamente funzionante".

La porta 5000 è una porta generica, e né FlightGear né il protocollo {{Wikipedia|UPnP|lang=it}} sono usi "ufficiali" della porta.

Una soluzione sarebbe dispiegare le porte tra i server; ad esempio, mpserver01.flightgear.org → 5001, mpserver02.flightgear.org → 5002.

Vedi anche la [http://forum.flightgear.org/viewtopic.php?f=27&t=24754 discussione del forum] e l'{{issue|1617|etichetta}}.

==Contenuti correlati==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]

{{Appendix}}

[[Category:Multiplayer]]
[[Category:Howto|Multiplayer]]

[[de:Howto: Multiplayer]]
[[en:Howto:Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]
[[pt:Tutorial de Multiplayer]]

Fr/Howto: Multijoueur

2017-12-29T18:43:59Z

Hergen: /* 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
|
|-
|[https://mpserver03.flightgear.org 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:

<syntaxhighlight lang="bash">
/sbin/ifconfig
</syntaxhighlight>

Vous devriez obtenir quelque chose comme ça:

<syntaxhighlight>
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)
...
</syntaxhighlight>

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:

<syntaxhighlight lang="bash">
ipconfig /all
</syntaxhighlight>

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:

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

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

[[de:Howto: Multiplayer]]
[[en:Howto:Multiplayer]]
[[es:Howto: Multijugador]]
[[it:Come fare:Multiplayer]]
[[nl:Howto: Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]
[[pt:Tutorial de Multiplayer]]

Es/Howto: Multijugador

2017-12-29T18:42:51Z

Hergen: /* 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
|
|-
|[https://mpserver03.flightgear.org 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.
[[File: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 ==
[[File: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]]
[[de:Howto: Multiplayer]]
[[en:Howto:Multiplayer]]
[[fr:Howto: Multijoueur]]
[[it:Come fare:Multiplayer]]
[[nl:Howto: Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]
[[pt:Tutorial de Multiplayer]]

[[Category:Howto|Multiplayer]]

Pl/Konfiguracja trybu multiplayer

2017-12-29T18:42:00Z

Hergen: /* W systemie Windows */

=W systemie Windows=
Najpierw wybierz samolot i lotnisko jak to robisz zazwyczaj. W kolejnym oknie zaznacz okienko "Multiplayer". Aby widzieć samoloty innych pilotów zaznacz też "AI models". Wprowadź callsign w pole o tej samej nazwie, a w pole "Hostname": mpserver01.flightgear.org (lub inny z listy). W pola "in" i "out" wpisz 5000. Teraz możesz kliknąć run i cieszyć się możliwością latania z pilotami z całego świata.
[[File:multiplayer.jpg|right|Wygląd okna multiplayer]]
Na stronie [http://mpmap02.flightgear.org/] dostępna jest także mapa w technologii google.

Oto lista serwerów multiplaer z jakich możesz korzystać:
* mpserver01.flightgear.org (in Germany)
* [https://mpserver03.flightgear.org mpserver03.flightgear.org] (in Germany) [T]
* mpserver04.flightgear.org (UK)
* mpserver06.flightgear.org (Sweden)

[T] oznacza że logi z serwera dostępne są na FlightGear flight tracker.

Uwaga: Serwery multiplayer są połączone. Nie musisz łączyć się z konkretnym serwerem aby widzieć pilotów którzy z niego korzystają. Dla najlepszych rezultatów powinieneś wybrać serwer który jest najbliżej.

-Multiplayer Chat-
Aby móc rozmawiać z innymi pilotami kliknij "View" i z rozwijanego menu wybierz "Chat". Pamiętaj, że aby widzieć twoje wiadomości inni użytkownicy muszą mieć otwarte okno czatu. Uwaga: Opcja czatu nie jest w spierana w wersji 9.10 i starszych.

Multiplayer w linii poleceń
Aby korzystać z opcji multiplayer gdy uruchamiasz FG z wiersza poleceń użyj następujących argumentów:

--multiplay=out,10,adres.ip.serwera,numerportu
--multiplay=in,10,twój.adres.ip,numerportu
--callsign=twojcallsign

numerportu to zazwyczaj 5000, a twój.adres.ip to adres ip interfejsu sieciowego z którego korzysta FG aby się połączyć z serwerem - nawet jeśli to adres lokalny typu 192.168.

[[de:Howto: Multiplayer]]
[[en:Howto:Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[it:Come fare:Multiplayer]]
[[nl:Howto: Multiplayer]]
[[pt:Tutorial de Multiplayer]]

De/Howto: Multiplayer

2017-12-29T18:39:15Z

Hergen: /* Server */

Mit der '''Multiplayer''' Funktion von [[:de:FlightGear|FlightGear]] kannst Du andere Piloten sehen und andersherum. Das macht es möglich in Formation zu fliegen oder [[:de:Luft zu Luft Betankung|Eine Luft-zu-Luft Betankung]] von einem Tankflugzeug durchzuführen, das von einem anderen Nutzer gesteuert wird. Außerdem kannst Du eine echte [[ATC|Flugsicherung]] um Start/Landefreigabe oder um den Überflug bitten.

Der Multiplayermodus kann hohe [[Troubleshooting performance issues|Framerate-Einbußen]] verursachen, weil er andere Flugzeuge mitladen muss. Gerade grosse Modelle, wie die [[:de:Boeing 707-420|Boeing 707]] oder der [[:de:Airbus A330-200 Series|Airbus A330-200]] können Stocken verursachen. Es wird empfohlen mit diesen an anderen Orten als dem Standardflughafen zu fliegen, da dort sehr viele Piloten unterwegs sind, die meißt neu sind und auch nicht auf die ATC(Flugsicherung) achten.

== Merke ==
* Das Rufzeichen (Callsign) darf nicht länger als sieben zeichen sein.
* Vielleicht willst Du Dir den [[#Bekannte Probleme|Bekannte Probleme-Bereich (weiter unten)]] anschauen.

== Verbindung mit dem Multiplayer herstellen ==
=== Dialog in der Simulation ===
[[File:Multiplayer settings dialog.jpg|thumb|Multiplayer-Einstellungen]]
Der leichteste Weg, online zu gehen ist der eingebaute Multiplayer Dialog.Alles, was Du tun musst, ist ein Rufzeichen anzugeben und dir einen Server aus dem Menü auszusuchen. Drücke dann {{Key press|Connect}}, um zu starten.

=== FGRun/Den Windows Starter benutzen ===
==== Von der FGRun Hauptseite ====
[[File:Multiplayer.jpg|thumb|Multiplayereinstellungen in [[:de:FlightGear Launch Control|FGRun]]]]
# Wähle Dein [[:de:Flugzeuge|Flugzeug]] und Startflughafen wie normal in [[:de:FlightGear Launch Control|FGRun]].
# Auf der letzten Seite, wähle die "Multiplayer" Box an. Wähle auch die Box "AI models" an, da Du sonst die Flugzeuge anderer Piloten nicht sehen kannst.
# Gib ...
## ein gewünschtes '''Rufzeichen''' ein (Bitte überprüfe auf [http://fgfs.i-net.hu/modules/fgtracker/ dieser Seite], ob dein gewünschtes Rufzeichen bereits in Verwendung ist oder nicht. Nehmen Sie kein Rufzeichen, das bereits verwendet wird!)
## <code>mpserverXX.flightgear.org</code> in das Feld Feld "Hostname" an (anstatt <code>XX</code> muss die [[#Server|Servernummer]]angegeben werden)
## in die Felder der '''In/Out''' Ports 5000 ein.
# Klicke auf {{button|Run}}, um Flightgear zu starten.

Um zu bestätigen, dass es funktioniert, kannst Du zur Multiplayer Karte gehen: http://mpmap02.flightgear.org/ (in Hong Kong).
Wenn FlightGear einmal gestartet ist, werden Sie Chatnachrichten bemerken, die alle "Hello" sagen, mit den dazugehörigen Namen der Piloten, die gerade online sind und eben dem Server beigetreten sind.
Du kannst diese Nachricht verändern, indem Du die die Zeile <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>
enstprechend anpassen. Vielleicht möchtest Du ja auch einen anderen Server benutzen, beispielsweise einen näheren Deutschland


==== Aus den FGRun Netzwerkeinstellungen starten ====
[[File:FGRun Advanced dialog - Network.png|thumb|Der <tt>Network</tt> Tab des "Advanced Options" Dialoges in [[:de:FlightGear Launch Control|FGRun]] (in [[Changelog 3.2|FlightGear 3.2.0]]).]]
Du kannst auch die Multiplayereinstellungen auf der <tt>Network</tt> Seite von FGRuns ''Advanced Options''.

# Klicke auf der letzten Seite {{button|Advanced}}.
# Klicke im linken Bereich auf <tt>Network</tt>.
# Im <tt>Multiplayer Options</tt> Bereich …
## Gib dein ausgesuchtes Rufzeichen in die Box ein.
## Setze Parameter für die zwei anderen Boxen; siehe [[#Multiplayer über die Kommandozeile starten|unten]] für die korrekte Eingabe.
## Klicke {{button|OK}}, und starte dann FlightGear.

=== Multiplayer über die Kommandozeile starten ===
Wenn Du FlightGear mithilfe der [[command line|Kommandozeile]] startest, kannst du auch verschiedene Einstellungen mitgeben. Die zwei Argumente sind die folgenden:
<syntaxhighlight lang="bash">
--multiplay=Richtung,10,ip.Adresse,Port
--callsign=deinRufzeichen
</syntaxhighlight>

Natürlich kann <code>--callsign</code> irgendetwas sein, was dir einfällt. Es gibt vier Argumente für <code>--multiplay</code>:
; Richtung
: Entweder <code>in</code> oder <code>out</code>. <code>in</code> weist Flightgear an, auf Pakete zu achten, die durch den angegebenen '''Port''' hereinkommen. <code>out</code> weist Flightgear an, Daten durch diesen '''Port''' zu senden.

; ip.Addresse
: Die IP Addresse der Netzwerkschnittstelle, das von FlightGear genutzt werden soll. Du kannst das Feld ip.Adresse auch leer lassen. FG wird dann auf allen verfügbaren Schnittstellen Verbindungen akzeptieren. Wenn die '''Richtung''' auf <code>in</code> gesetzt wurde, wird Flightgear ''nur'' von dieser IP-Adresse empfangen.

; port
: Port wodurch die Daten gesendet oder empfangen werden. Normalerweise auf <code>5000</code> gesetzt (Weil 5000 die Portnummer der offiziellen Server ist).

== Erweiterte Nutzung des Multiplayer ==
=== Lokale Einstellungen zum Testen (Direktverbindungen) ===
Es ist auch möglich, ein lokales Multiplayernetzwerk zwischen zwei FlightGear-Computern aufzubauen, ohne über einen [[FGMS|Multiplayer Server]] zu laufen. Alles, was man tun muss, ist den I/O Port des einen PC's auf den korrespondierenden Port des anderen PS's zu setzen:

{{Note|
{{FGCquote
|Eine direkte Verbindung braucht nicht nur eine IP-Adresse, sondern auch eine Portnummer auf jeder Seite der Verbindung - stelle dir vor, eine Portbox ist wie ein Briefkasten, der auf der Adresse sitzt. Dieser Briefkasten wird von dem kommunizierenden Prozess genutzt, um Nachrichten zu versenden und zu empfangen. Verschiedene Prozesse (Auch, wenn sie vom gleichen Programm sind) brauchen verschiedene Portnummern zum Laufen, da offene Ports ({{=}}mailboxes) nicht geteilt werden können.
Also musst Du die klientseitigen Einstellungen für jeden weiteren Teilnehmer auf der selben Maschine anpassen, indem Du den Out-Port des einen Computers suf den In-Port des anderen Computers anpasst (und andersherum).
|{{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>
}}
}}
}}

Kommandozeilenparameter für die erste Instanz:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5000 --multiplay=in,10,127.0.0.1,5001 --callsign=Test1
</syntaxhighlight>

Kommandozeilenparameter für die zweite Instanz:
<syntaxhighlight lang="bash">
--multiplay=out,10,127.0.0.1,5001 --multiplay=in,10,127.0.0.1,5000 --callsign=Test2
</syntaxhighlight>

Auf diese Weise kannst Du Multiplayerfunktionen Testen oder Fehler reproduktieren, die nicht über den normalen MP laufen sollen. Da Du sonst keine Einsicht in die FlightGear-Einstellungen der anderen Nutzer hast, erlaubt dir diese Technik, die vollständige Kontrolle über die anderen Einstellungen zu bekommen.

[[File:Direct-p2p-multiplayer-setup.png|800px|Screenshot der den "peer-to-peer" Aufbau zwischen zwei FlightGear Nutzern zeigt, die auf der gleichen Maschine mittels Localhost (127.0.0.1) ohne MultiplayerServer fliegen.]]

Du kannst eine willkürliche Nummer von Kanälen angeben, um deinen Flug gleichzeitig auch auf anderen Servern anzuzeigen , z.B. auf einem privaten fgms Server mithilfe von
<syntaxhighlight lang="bash">
--multiplay=out,10,my.private.server.ip,5000
</syntaxhighlight>

Außerdem gibt das <code>in</code> Argument oben an FlightGear, dass es '''nur''' von dem loopback/local interface empfangen soll - es wird keine Daten annehmen, die auf anderen network interface(s) ankommen. Wenn Du dich auch zu anderen verbinden willst, übermittele die IP Addresse mit
<syntaxhighlight lang="bash">
--multiplay=in,10,,5000
</syntaxhighlight>

Prüfe [http://fgfs.i-net.hu/modules/fgtracker/ diese Seite] um zu sehen, ob dein Rufzeichen/Callsign bereits genutzt wird oder nicht. Nimm kein Callsign, das bereits genutzt wird, da das Probleme verursachen wird!

==== Nochmal langsam, für alle, die oben bisher nur Bahnhof verstanden haben... ====
{{Caution|Dieser Bereich kann veraltete oder ungenaue Informationen enthalten}}
Diese Sektion ''sollte'' eigentlich bei den neusten Versionen des FG Servers überflüssig werden. Wenn es jedoch Probleme gibt, kann es nicht schaden, diesen Bereich zu lesen.

Als Erstes solltest Du die IP Addresse für die Netzwerkschnittstelle (network interface) kennen, die du für den FG Multiplayer nutzen willst.

Wenn deine Internetverbindung über ein ADSL Modem läuft, das indirekt auf deinen Computer sendet, solltest du deine IP-Adresse sehen, wenn du die Seite [http://www.whatismyip.com what is my ip] besuchst.
{{Note|Dein Internetanbieter kann die IP-Adresse zwischendurch auch jedes Mal ändern.}}

Wenn diene Verbindung über einen '''Ethernet connector''' oder über einen '''wireless link''' läuft.

* '''Linux:''' Log dich als root ein und starte <code>ifconfig</code> Im Terminal. In dem Text,der zurückgegeben wird, kannst Du nach einem Interface-Namen, wie <code>eth0</code> oder <code>wlan0</code> schauen. Dann schue in den Text unter den Interface-Namen nach der <code>inet addr:ip.address</code>. Zum Beispiel könnte das so aussehen: <code>inet addr:192.168.0.150</code>.
* '''Windows:'''
** '''Windows XP und später:''' Gib in die die Kommandozeile (CMD.exe) <code>ipconfig</code> ein. Notiere dann die IP-Adresse.
** '''Windows 98''', Klicke auf Start, Run, und gib dann ein "winipcfg" , um Informationen über deine IP-Adresse herauszufinden.

Jetzt ist alles, was Du noch tun musst, den Router auf den UDP port 5000 deiner IP Addresse zuzuweisen, die du gerade gefunden hast. Dies kann man hier nicht in einer Schritt-für-Schritt-Anleitung beschreiben, da die Einstellungen bei den verschiedenen Herstellern stark voneinander abweichen können. Einige Tipps wollen wir aber mitgeben – Wenn du nicht weiterweißt, frag nett auf dem [[FlightGear IRC channel]] um Hilfe (Details auf der FlightGear Website).

Du solltest wissen, wie du auf die Konfigurationsseite deines Routers kommst, normalerweise mit dem Browser. Du musst Nach Einstellungen mit dem Namen "port forwarding," "virtual server," "Forwarding Rules," oder ähnlichen Ausschau halten. Wenn Du die relevanten Einstellungen gefunden hast, musst du eine Anweisung erstellen, die den Port 5000 auf die IP Addresse zuweist, die du gerade herausgefunden hast. Wenn es mehrere Möglichkeiten gibt, sind des meist die UDP ports, die zugewiesen werden. Wenn die Wahl nicht besteht, musst Du davon ausgehen, dass beide (TCP und UDP) zugewiesen werden. Speichere Deine Einstellungen, die meisten Router starten dann neu.

Dann starte FG starte FG über die Kommandozeile wie am Start gegeben (Wenn du den Launcher nutzt, findest du eingabeboxen für dei Einstellungen – gib dort die relevanten Einstellungen ein). Du wirst nachher soetwas haben:
<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>

Wähle Dein eigenes Rufzeichen aber prüfe [http://fgfs.i-net.hu/modules/fgtracker/ diese Seite] um zu sehen, ob dein Rufzeichen/Callsign bereits genutzt wird oder nicht. Nimm kein Rufzeichen, das bereits genutzt wird, da das Probleme verursachen wird!

Sobald Du FG gestartet hast, solltest Du, wenn andere Piloten online sind, Nachrichten von denjenigen sehen, die Flightgear gestartet haben, ähnlich der folgenden;

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

Du MUSST deine Lokalnummer hinter der RouterIP mit angeben,um Multiplayer zum Laufen zu bekommen!

Du musst sicherstellen, dass deine Firewall keine Probleme verursacht - stelle sie zeitweise aus oder füge eine Ausnahme für den Port 5000 hinzu.

Wenn es immer noch nicht läuft, frag mal nett auf dem [[FlightGear IRC channel|IRC channel]] oder im [http://forum.flightgear.org/ Forum] nach, ob dir jemand helfen kann.

=== Mehrere Verbindungen pro Computer ===
Es ist möglich mehrere FlightGear Instanzen auf einem einzigen Computer auszuführen und mit all denjenigen zu einem Multiplayer Netzwerk zu verbinden. Bei dem muss man Folgendes beachten:
* Beide Instanzen benutzen denselben <code>out</code> Port.
* Die eine Instanz benutzt den <code>in</code> Port <code>5001</code>, die andere den in Port <code>5002</code>.
* Natürlich müssen beide Instanzen ein unterschiedliches Rufzeichen haben.

=== Optionale Kollisionsprüfung im Multiplayer ===
Es gibt in Flightgear seit Version 3.5 ein Patch, das eine optionale Kollisionserkennung im Multiplayer beinhaltet. Um die Kollisionserkennung zu aktivieren, starte FlightGear mit:

<syntaxhighlight>
--prop:bool:/sim/multiplay/hot=true
</syntaxhighlight>

Diejenigen, die lieber FGData anpassen möchten, können [http://sourceforge.net/p/flightgear/mailman/attachment/CAHs0wcrEwYZvXTddcUaH0ZMfmVNvEWRap8MXOrEoKybUDO58sQ%40mail.gmail.com/3/ mp-hot-fgdata.patch] herunterladen, was eine Checkbox dafür in die Multiplayereinstellungen hinzufügt.

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

Um mit anderen Piloten zu chatten, gehe in das <tt>Multiplayer</tt> Menü und aktiviere <tt>Chat Menu</tt> unten im Menü. Bedenke, dass vielleicht nicht alle Piloten ihre Nachrichtenbox oder Chatbox geöffnet haben, sodass sie also deine Nachrichten nicht sehen können.

Die Tastenbelegung zum Chat ist {{Key press|<nowiki>-</nowiki>}} (Bindestrich). Das lässt etwas Text auf der oberenb linken Exke des Flightgearfensters erscheinen. Mit dem Drücken der dazugehörigen Nummertasten kannst Du vorgeschriebene Nachrichten senden (Handy am Steuer(horn)?). Wenn Du {{Key press|1}} drückst, hannst Du eine eigene Nachricht eingeben, die mit {{Key press|Enter}} gesendet wird. Standardmäßig werden die Nachrichten von anderen kurz im oberen Bereich des FlightGear-Fensters gezeigt, aber sie bleiben viel länger im Fenster unter <tt>Network > Chat</tt>. Also wenn du dengst, dass du was verpasst hast, gehe dahin und lese die Nachricht.

=== Umgang mit beleidigendem Verhalten ===
Solltst Du Opfer von Beleidigungen oder Beschimpfungen eines Pilots werden, kannst Du ihn oder Sie ignorieren. Um die Ignorier-Funktion zu aktivieren, gehe in das <tt>Multiplayer > Pilot list</tt> Dialog und klicke den {{Button|ignore}} Button neben dem Rufzeichen des Piloten. Das wird die Chatnachrichten des Pilots unterdrücken und sein Flugzeug auch nicht mehr anzeigen (ab FlightGear v2.2).

=== Multiplayer Karte ===
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
{{Main article|MPMap}}

Es gibt eine schöne Online Karte, die die Position der Piloten, die gerade online sind, anzeigt. Die Karte ist unter [http://mpmap02.flightgear.org mpmap02] zu finden. Das kann auch nützlich sein, um herauszufinden, ob Du zu einem bestimmten Server verbunden bist. Außerdem findest du dort alle Navaids, Waypoints, Flughäfen, Frequenzen, Das Wetter, und mehr!

== Server ==
Die Multiplayerserver sind untereinander verbunden; Sie '''müssen sich nicht''' zu einem bestimmten Server verbinden, damit Sie andere Piloten sehen können, die gerade auf diesem Server spielen. Die Verbindung ist am Besten, wenn Sie sich mit dem Server verbinden, der ihnen geographisch am Nähesten liegt, der der die kleinste Ping Zeit hat, oder zu denen, die am wenigsten besetzt sind.
{{tip|Nutze [http://mpmap01.flightgear.org/mpstatus/ diesen Link] oder [http://mpserver15.flightgear.org/mpserverstatus/ diesen Link] um zu prüfen, ob die Server online sind. Beide Seiten sind automatisch generiert. Der [[#Dialog in der Simulation|Dialog in der Simulation]] zeigt ebenfalls nur die verfügbaren Server an.}}
{| class="wikitable sortable"
! Serveradresse
! Status
! Ort
! [http://mpserver15.flightgear.org mpserver15] Erfasst
! Betreiber
! [[IRC]] Betreiber
! [http://flightgear.org/forums Forumname] Betreiber
! Kommentare
|-
| mpserver01.flightgear.org
| {{yes|Verfügbar}}
| Deutschland
| {{yes|Ja}}
| Oliver Schroeder
| os
| {{N/a|?}}
| {{N/a|None}}
|-
| mpserver02.flightgear.org
| {{yes|Verfügbar}}
| Los Angeles, USA
| {{no|Nein}}
| Lloyd Stevens
| ls4680
| ls4680
| {{N/a|Keine}}
|-
| mpserver03.flightgear.org
| {{yes|Verfügbar}}
| Deutschland
| {{yes|Ja}}
| Hergen
| {{N/a|?}}
| {{N/a|?}}
| [https://mpserver03.flightgear.org mpserver03.flightgear.org]
|-
| mpserver04.flightgear.org
| {{yes|Verfügbar}}
| UK
| {{no|Nein}}
| Jon Stockill
| Nav
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=738 JonS]
| {{N/a|?}}
|-
| mpserver05.flightgear.org
| {{no|Aus}}
| Chicago, USA
| {{N/a|?}}
| Brant
| IonCannon218
| {{N/a|?}}
| {{N/a|?}}
|-
| mpserver06.flightgear.org
| {{no|Aus}}
| Berlin, Deutschland
| {{N/a|?}}
| Sven Teichmann
| {{N/a|?}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11839 D-SAMI]
| Unbegrenztes Volumen
|-
| mpserver07.flightgear.org
| {{no|Aus}}
| Wisconsin, USA
| {{N/a|?}}
| Tom Betka
| TB
| {{N/a|?}}
| Offline
|-
| mpserver08.flightgear.org
| {{no|Aus}}
| Frankfurt am Main, Germany
| {{N/a|?}}
| Roland
| Quix0r
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=7512 Quix0r]
| 10 TByte Volumen, meist kurze Pings
|-
| mpserver09.flightgear.org
| {{no|Aus}}
| Köln, Deutschland
| {{N/a|?}}
| Daniel Vigano
| Fauchi95
| {{N/a|?}}
| Offline
|-
| mpserver10.flightgear.org
| {{no|Aus}}
| Montpellier, France
| {{N/a|?}}
| {{usr|Xiii|Alexis Bory}}
| xiii
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=884 xiii]
| {{N/a|?}}
|-
| mpserver11.flightgear.org
| {{no|Aus}}
| Vilnius, Lithuania
| {{N/a|?}}
| Darius
| {{N/a|?}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1122 ffg]
| {{N/a|?}}
|-
| mpserver12.org
| {{yes|Verfügbar}}
| Amsterdam, the Netherlands
| {{yes|Ja}} [http://mpserver12.org mpserver12.org]
| Rob
| evilslut
| {{N/a|?}}
| Offiziell mpserver12.flightgear.org<ref>http://forum.flightgear.org/viewtopic.php?f=27&t=27453&start=60#p258435</ref>
|-
| mpserver13.flightgear.org
| {{no|Aus}}
| Grenoble, Frankreich
| {{N/a|?}}
| Charles Ingels
| charles
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1592 cbz-026]
| {{N/a|?}}
|-
| mpserver14.flightgear.org
| {{yes|Verfügbar}}
| UK
| {{yes|Ja}}
| Pete
| {{N/a|?}}
| {{N/a|?}}
| {{N/a|?}}
|-
| mpserver15.flightgear.org
| {{N/a|?}}
| North Point, Hong Kong
| {{N/a|?}}
| Hazuki Amamiya
| Hazuki
| Hazuki
| Dies ist ein Tracker Server, kein multiplayer Server
|-
| mpserver16.flightgear.org
| {{yes|Verfügbar}}
| Kansas City, Missouri, USA
| {{yes|Ja}}
| Rob Dosogne
| truthsolo
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9926 truthsolo]
| {{N/a|?}}
|-
| mpserver17.flightgear.org
| {{no|Aus}}
| Cluj, Romania
| {{N/a|?}}
| Marius
| tuxum
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11636 tuxum]
| Offline
|-
| mpserver18.flightgear.org
| {{no|Aus}}
| Deutschland
| {{N/a|?}}
| {{N/a|?}}
| {{N/a|?}}
| {{N/a|?}}
| {{N/a|?}}
|}
Die Standorte der Server können auch mit [http://goo.gl/maps/jBwUd Google Maps] eingesehen werden.

Wenn Du daran interessiert bist, einen eigenen Multiplayer Server zu hosten, könnte das hier für dich interessant sein. [[Howto: Set up a multiplayer server|Einen Multiplayer Server aufsetzen]].

== Bekannte Probleme ==
=== Fibertel (Argentinien) ===
Im Dezember 2014 wurde berichtet, dass die UDP Verbindung mit dem Port 5000 nicht möglich war, wenn ihr Internetanbieter {{Wikipedia|Fibertel}} (Argentinien) ist.

Fibertel Argentina nutzt diesen Port für Setup Zwecke. "Er steht zwar für die Nutzer offen, es kann aber vorkommen, dass er nur eingeschränkt funktionstüchtig ist."

Der Port 5000 ist ein nicht zugeordneter Port, und weder FlightGear, noch das {{Wikipedia|Universal Plug and Play|lang=de}} Protocol sind "offizielle" Nutzer dieses Ports.

Eine Lösung ist, jedem Server einen anderen Port zuzuordnen; z.B. mpserver01.flightgear.org → 5001, mpserver02.flightgear.org → 5002

Siehe auch den [http://forum.flightgear.org/viewtopic.php?f=27&t=24754 Forumbeitrag] und {{issue|1617}}.

== Weiterführende Seiten ==
* {{en|[[FlightGear Multiplayer Server]]}}
* {{en|[[Howto: Set up a multiplayer server]]}}
* {{en|[[Multiplayer protocol]]}}
* {{en|[[Howto:Transmit properties over MP]]}}

{{Appendix}}

[[Category:Multiplayer]]
[[Category:Howto|Multiplayer]]

[[en:Howto:Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[it:Come fare:Multiplayer]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]
[[pt:Tutorial de Multiplayer]]

Howto:Multiplayer

2017-12-27T15:49:28Z

Hergen: /* Servers */

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.

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.

== Notes ==
* Callsigns can be a maximum of seven characters.
* You might want to check the [[#Known issues|Known issues]] section.

== 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 FGRun ===
==== From the main page ====
[[File:Multiplayer.jpg|thumb|Multiplayer settings in [[FGRun]]]]
# Select your [[aircraft]] and starting airport as normal in [[FGRun]].
# 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.
# Enter the …
#* '''Callsign''' of your choice.
#* '''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. 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.

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

# On the last page, click {{button|Advanced}}.
# 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.

=== Using multiplayer from the command line ===
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>

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

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

; port
: Port that data is either being sent or received through. Usually set to <code>5000</code> and above.

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

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

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 (FlightGear Multiplayer 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 [https://fgtracker.ml/ 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... ====
{{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, 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.}}

If your connection is via an Ethernet connector or by a wireless link.

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

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

Choose your own callsign, but check [https://fgtracker.ml/ 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!

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|IRC channel]] or the [http://forum.flightgear.org/ forum] 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 <code>out</code> port.
# One instance uses <code>in</code> port <code>5001</code>, the other port <code>5002</code>.
# 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 ==
{{Main article|Chat Menu}}

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

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

== Multiplayer map ==
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at [http://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 ==
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] to check if the MP servers are online. Page is automatically generated. The [[#In-sim Dialog|in-sim dialog]] will only display servers that are available.}}

{| class="wikitable sortable"
! Server address
! Status
! Location
! Tracked (by [http://fgtracker.ml fgtracker.ml] unless otherwise specified)
! Maintainer
! Maintainer's [[IRC]] name
! Maintainer's [http://flightgear.org/forums forum] name
! Comments
|-
| mpserver01.flightgear.org
| {{yes|Up}}
| Germany
| {{yes}}
| Oliver Schröder
| os
| {{N/a}}
| {{N/a|None}}
|-
| mpserver02.flightgear.org
| {{yes|Up}}
| Los Angeles, USA
| {{N/a}}
| Lloyd Stevens
| ls4680
| ls4680
| {{N/a|None}}
|-
| mpserver03.flightgear.org
| {{yes|Up}}
| Germany
| {{yes}}
| Hergen
| {{N/a}}
| {{N/a}}
| [https://mpserver03.flightgear.org mpserver03.flightgear.org]
|-
| mpserver04.flightgear.org
| {{yes|Up}}
| UK
| {{no}}
| Jon Stockill
| Nav
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=738 JonS]
| {{N/a|None}}
|-
| mpserver05.flightgear.org
| {{no|Down}}
| Chicago, USA
| {{N/a}}
| Brant
| IonCannon218
| {{N/a}}
| {{N/a|None}}
|-
| mpserver06.flightgear.org
| {{no|Down}}
| Berlin, Germany
| {{N/a}}
| Sven Teichmann
| {{N/a}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11839 D-SAMI]
| Unlimited traffic
|-
| mpserver07.flightgear.org
| {{no|Down}}
| Wisconsin, USA
| {{N/a}}
| Tom Betka
| TB
| {{N/a}}
| Offline
|-
| mpserver08.flightgear.org
| {{no|Down}}
| Frankfurt am Main, Germany
| {{N/a}}
| Roland
| Quix0r
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=7512 Quix0r]
| 10 TByte traffic, mostly short pings
|-
| mpserver09.flightgear.org
| {{no|Down}}
| Köln, Germany
| {{N/a}}
| Daniel Vigano
| Fauchi95
| {{N/a}}
| Offline
|-
| mpserver10.flightgear.org
| {{no|Down}}
| Montpellier, France
| {{N/a}}
| {{usr|Xiii|Alexis Bory}}
| xiii
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=884 xiii]
| {{N/a|None}}
|-
| mpserver11.flightgear.org
| {{no|Down}}
| Vilnius, Lithuania
| {{N/a}}
| Darius
| {{N/a}}
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1122 ffg]
| {{N/a|None}}
|-
| mpserver12.org
| {{no}}
| Amsterdam, the Netherlands
| {{no}} ([http://mpserver12.org mpserver12.org])
| Rob
| 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
| {{yes|Up}}
| Beauvais, France
| {{N/a}}
| Charles Ingels
| charles
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=1592 cbz-026]
| {{N/a|None}}
|-
| mpserver14.flightgear.org
| {{yes|Up}}
| UK
| {{no}}
| Pete
| {{N/a}}
| {{N/a}}
| {{N/a|None}}
|-
| mpserver15.flightgear.org
| {{yes|Up}}
| North Point, Hong Kong
| {{yes}}
| Hazuki Amamiya
| Hazuki
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=8400 Hazuki]
| {{N/a|None}}
|-
| mpserver16.flightgear.org
| {{yes|Up}}
| Kansas City, Missouri, USA
| {{no}}
| Rob Dosogne
| truthsolo
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9926 truthsolo]
| {{N/a|None}}
|-
| mpserver17.flightgear.org
| {{no|Down}}
| Cluj, Romania
| {{N/a}}
| Marius
| tuxum
| [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=11636 tuxum]
| Offline
|-
| mpserver18.flightgear.org
| {{no|Down}}
| Germany
| {{N/a}}
| {{N/a}}
| {{N/a}}
| {{N/a}}
| {{N/a}}
|-
| mpserver19.flightgear.org
| {{yes|Up}}
| London, UK
| {{yes}}
| Dr. R0ckso
| drr0ckso
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21111 drR0ckso]
| {{N/a|None}}
|-
| mpserver20.flightgear.org
| {{yes|Up}}
| South San Francisco, California, USA
| {{yes}}
| Marisa Giancarla
| marisag
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21604 marisag]
| {{N/a|None}}
|-
| mpserver21.flightgear.org
| {{yes|Up}}
| Tokyo, Japan
| {{yes}}
| Marisa Giancarla
| marisag
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21604 marisag]
| {{N/a|None}}
|-
| 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
|}

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

== 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 ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
* [[Howto:Transmit_properties_over_MP]]

{{Appendix}}

[[Category:Multiplayer]]
[[Category:Howto|Multiplayer]]

[[de:Howto: Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[it:Come fare:Multiplayer]]
[[nl:Howto: Multiplayer]]
[[pl:Konfiguracja trybu multiplayer]]
[[pt:Tutorial de Multiplayer]]

Howto:Set up a multiplayer server

2016-01-17T13:26:45Z

Hergen:

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.
** For specific documentation for setting up on FreeBSD see [[Howto:Set up a multiplayer server on FreeBSD]].
* 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/g++ (compiler), make & cmake
* fgms source code, currently version 0.10.23
* 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.

In July 2013, mpserver01 load was reported averaging at 10 MBit/sec

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

== Getting & Building fgms ==

* You will need the build tools cmake and make, and also g++ to compile the fgms application. These can usually be found in the package manager for most the common Linux distributions. You will also need the git client to fetch the source code from the repository, if you plan to download it from the command line interface (see below).

* Once the build tools are installed on your machine, create a directory to hold the source code. This could be named anything, such as fgms. Create it in your user home directory. Note that this WILL NOT be the directory where the program will be compiled.

* Now 'cd' into the directory you just made, where you will run the command to fetch the source code from the git repository (see below).

* To download the latest stable version via HTTP, you can use direct your browse to the URL http://gitorious.org/fgms/fgms-0-x/. Download and unzip the source code, and place it in the directory you created above.

* To download a file directly to your server from an ssh session, you can use git tools with the following command:

$git clone https://gitlab.com/fgms/fgms-0-x.git

== Compiling FGMS ==

For FreeBSD-specific instructions, please see [[Howto:Set up a multiplayer server on FreeBSD]]

NOTE: In general, on any current machine this process should not take longer than about 60 seconds.

* Once you have the source code, 'cd' into the ~/fgms/fgms-0-x/ directory and note the presence of the CMakeLists.txt file and the README.cmake file. Open the README.cmake file and take a minute to read it over. Also, note the path to the CMakeLists.txt file, as you will need this in the following steps.

* Now create a build-fgms directory in your home directory, and 'cd' into it. From inside the ~/build-fgms/ directory, run the cmake command using the path to the CMakeLists.txt as an argument. For example: cmake /home/<user_name>/fgms/fgms-0-x/

* Once the build finishes, you can either run the "cmake --build ..." command as shown in the README.cmake file, or you can simply use "make" to build the program.

* Once the compilation process finishes, you need to install the program using "make install" (as user), or you can also install as root.

* Once the program has been installed, you need to copy the fgms_example.conf file from the /fgms/fgms-0-x/src/server directory, into the build-fgms directory. To do this from inside the /fgms/fgms-0-x/src/server directory, you can use this command: cp ./fgms_example.conf ~/build-fgms/

* Now 'cd' into the build-fgms directory, and rename the file you just copied as "fgms.conf" so that fgms can find the proper configuration.

== Setting up the config file ==

At this point you should have a working 'fgms' binary in the build-fgms directory. 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.

* Edit the fgms.conf file according to the instructions found elsewhere on this page, then save and close the file.

{{cquote|As long as you are not absolutly sure what you are doing you should:
- disable tracking
- disable HUB setting<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40454.html|title=<nowiki>Re: [Flightgear-devel] New FlightGear Multiplayer Server</nowiki>|author=Oliver Schröder|date=Wed, 10 Jul 2013 13:53:55 -0700}}</ref>|Oliver Schröder}}

{{cquote|fgms will ignore traffic comming from unknown relays and since the multiplayer network is a star topology you should list only mpserver01
as your only relay. Currently mpserver01 is the only HUB, Although multiple HUBs should work I have not tested a multi HUB environment yet.
And for those interrested: Current traffic load on mpserver01 is around 10 MBit/s<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40454.html|title=<nowiki>Re: [Flightgear-devel] New FlightGear Multiplayer Server</nowiki>|author=Oliver Schröder|date=Wed, 10 Jul 2013 13:53:55 -0700}}</ref>|Oliver Schröder}}

{{cquote|your fgms.conf should look like:
<pre>
# basic setting
server.name = mpserver02
server.port = 5000

# you can telnet to this port with this username/password
# and see statistics (nice cisco like CLI)
server.admin_port = 6002
server.admin_user = fred
server.admin_pass = fred

server.admin_enable = fred

# mpserver01 does this
server.tracked = false

# mpserver01 is hub
server.is_hub = false</pre><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40454.html|title=<nowiki>Re: [Flightgear-devel] New FlightGear Multiplayer Server</nowiki>|author=Oliver Schröder|date=Wed, 10 Jul 2013 13:53:55 -0700}}</ref>|Oliver Schröder}}

{{cquote|<pre># don't set this too high
server.out_of_reach = 100

# your only relay should be mpserver01
relay.host = mpserver01.flightgear.org
relay.port = 5000

# you don't need a crossfeed, it's only interresting for fgms-developers
# crossfeed.host = foo.example.com
# crossfeed.port = 5002

# you can add static entries of IPs which get blocked,
# but it's generally not needed and you can add them via
# the admin CLI
# blacklist = 123.123.123.123</pre><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40454.html|title=<nowiki>Re: [Flightgear-devel] New FlightGear Multiplayer Server</nowiki>|author=Oliver Schröder|date=Wed, 10 Jul 2013 13:53:55 -0700}}</ref>|Oliver Schröder}}

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

For others to know about your public server you should notify the developers of the existence of your server by posting a message to the [[Mailing list|developers mailing list]].

Add your server to this list: http://wiki.flightgear.org/Howto:Multiplayer#Servers

== Related content ==
* [http://fgms.freeflightsim.org/ Website: fgms.freeflightsim.org]
* [[Howto: Multiplayer|Multiplayer howto]]
* [[MPmap]]

<references/>

[[Category:Howto]]
[[Category:Multiplayer]]

[[fr:Installer un serveur multijoueur]]

De/Howto: Multiplayer

2013-10-04T20:49:14Z

Hergen:

Mit der '''multiplayer''' Funktion von [[FlightGear]] können Sie andere Piloten sehen. Das macht es möglich in Formation zu fliegen, [[Howto: Air-Air Refueling|zu Lufttankern zu verbinden]], die von echten Personen gesteuert werden, oder eine echte [[ATC|Flugsicherung]] um Start/Landefreigabe zu erbitten.

Der Multiplayermodus kann extrem hohe [[Howto: Improve Framerates|Frameraten]] verursachen, während dem Laden der Flugzeugmodellen. Gerade grosse Modelle können Stocken verursachen. Es wird empfohlen mit diesen an anderen Orten als [[KSFO]] zu fliegen, wo weniger Piloten in der Luft sind.

== Servers ==
'''Bitte beachten Sie:''' Die Multiplayerserver sind untereinander verbunden; Sie '''müssen sich nicht''' zu einem bestimmten Server verbinden, damit Sie andere Piloten sehen können, die gerade auf diesem Server spielen. Am schnellsten geht es, wenn Sie sich mit dem Server verbinden, der ihnen geographisch am nähesten liegt, der der die kleinste Ping Zeit hat, oder zu denen, die am wenigsten besetzt sind.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Standort
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracker]
! style="background:#efefef" |Verantwortlicher
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Kommentare
|-
|mpserver01.flightgear.org
|Deutschland
|Ja
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Nein
|Hergen
|
|
|
|-
|mpserver04.flightgear.org
|Vereinigtes Königreich
|Ja
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Ja
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|Nein
|Anders Gidenstam
|AndersG
|AndersG
|Offline seit 20.6.2011 bis in unbestimmte Zeit.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Ja
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Ja
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, meistens kurze Pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|Ja
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Ja
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Ja
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|Nein
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Ja
|Charles Ingels
|charles
|cbz-026
|
|}

Benutzen Sie [http://mpmap01.flightgear.org/mpstatus/ das hier], [http://mpmap02.flightgear.org/mpstatus/ dieses] or [http://flightgear.mxchange.org/mpstatus/ das hier] um zu überprüfen, ob die Multiplayer Server online sind. Die Standorte der Server können auch auf [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps] abgerufen werden.

Wenn Sie daran interessiert sind, einen eigenen Multiplayer Server zu hosten, könnte das hier für Sie interessant sein. [[Howto: Set up a multiplayer server|Einen Multiplayer Server aufsetzen]].
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Karte ===
{{Main article|MPMap}}

Es gibt eine schöne Online Karte, die die Position der Piloten, die gerade online sind, anzeigt. Die Karten sind hier zu finden: [http://mpmap01.flightgear.org mpmap01] und/oder [http://mpmap02.flightgear.org mpmap02]. Das kann auch nützlich sein, um herauszufinden, ob Sie zu einem bestimmten Server verbinden können.

== Mehrere Verbindungen pro Computer ==
Es ist möglich mehrere FlightGear Instanzen auf einem einzigen Computer auszuführen und mit all denjenigen zu einem Multiplayer Netzwerk zu verbinden.
Bei dem jedoch muss man folgendes beachten:
* Beide Instanzen benutzen denselben out Port
* Die eine Instanz benützt den in port 5001, die Andere den in Port 5002.
* Natürlich müssen beide Instanzen ein unterschiedliches Rufzeichen haben.

== Den Windows Starter benutzen / FGRun ==
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FGRUN]]]]
# Wählen Sie ihr [[Flugzeug]] und Startflughafen wie normal in [[FlightGear Launch Control|FGRun]].
# Im nächsten Dialog, wählen Sie die "Multiplayer" Box an. Wählen Sie auch die Box "AI models" an, da Sie sonst die Flugzeuge anderer Piloten nicht sehen könnten. Geben Sie ein gewünschtes Rufzeichen ein (Bitte überprüfen Sie auf [http://fgfs.i-net.hu/modules/fgtracker/ dieser Seite] ob ihr gewünschtes Rufzeichen bereits in Verwendung ist oder nicht. Nehmen Sie kein Rufzeichen, das bereits verwendet wird!), geben Sie mpserver01.flightgear.org im Feld "Hostname" an, und 5000 in die Felder "in" und "out".
# Nach einem Klick auf "Run" werden Sie mit anderen Piloten fliegen können.

Um zu bestätigen dass es funktioniert, können Sie zur Multiplayer Karte gehen: http://mpmap02.flightgear.org/ (in Hong Kong).
Wenn FlightGear einmal gestartet ist, werden Sie Chatnachrichten bemerken, die alle "Hello" sagen, mit den dazugehörigen Namen der Piloten, die gerade online sind und eben dem Server beigetreten sind.
(Sie können diese Nachricht verändern, indem Sie die die Zeile <tt><chat type="string">Hello</chat></tt> in <tt>[[$FG ROOT]]/preferences.xml</tt>) enstprechend anpassen. Vielleicht möchten Sie ja auch einen anderen Server benutzen.

Für weitere Einstellungen, kann der <tt>Advanced > Network</tt> Tab geöffnet werden. Nur dort können Sie z. B. die in oder out lines entfernen.

== Die Benutzung von fgfs aus der Kommandozeile ==
Erstens: Für alle, die sehr ungeduldig sind, und einigermassen eine Idee haben, was sie gerade tun, sind die Standardargumente, die fgfs übergeben werden müssen, folgende:

--multiplay=out,10,server.ip.Adresse,5000
--callsign=rufzeichen

Hier ist 5000 der Port, auf dem der Server eingehende Verbindungen akzeptiert. (Wobei 5000 die Portnummer der offiziellen Server ist)

Wenn Sie aus irgendeinem Grund einen anderen Port oder ein anderes Interface benutzen müssen, so sollten Sie folgende Argumente mitübergeben:

--multiplay=in,10,Ihre.ip.Adresse,Portnummer

Wobei "Portnummer" in der Regel 5000 ist, und Ihre.ip.Adresse die IP Adresse ihrer Netzwerkschnittstelle ist, die von FG benutzt werden soll, um zum Server verbinden. Auch wenn das eine lokal 192.168. Adresse ist.
Sie können das Feld Ihre.ip.Adresse auch leer lassen. FG wird dann auf allen verfügbaren Schnittstellen Verbindungen akzeptieren.
--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=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

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

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== 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]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]
[[de:Howto: Multiplayer]]

[[Category:Howto|Multiplayer]]

Howto:Multiplayer

2013-07-09T07:46:37Z

Hergen: /* 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 [[air traffic control]]lers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate drops]] during loading of aircraft models. Especially heavy models can cause severe lag. Therefore, it is suggested to fly in locations other than San Francisco's [[KSFO]], where there are fewer pilots flying around.

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

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Location
! style="background:#efefef" |[http://mpserver15.flightgear.org Tracked]
! style="background:#efefef" |Maintainer
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Comments
|-
|mpserver01.flightgear.org
|Germany
|[http://mpserver15.flightgear.org Yes]
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|Offline
|-
|mpserver03.flightgear.org
|Germany
|No
|Hergen
|
|
|
|-
|mpserver04.flightgear.org
|UK
|No
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|[http://mpserver15.flightgear.org Yes]
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Berlin, Germany
|[http://mpserver15.flightgear.org Yes]
|Sven Teichmann
|
|D-SAMI
|Unlimited traffic
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|
|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
|
|Daniel Vigano
|Fauchi95
|
|Offline
|-
|mpserver10.flightgear.org
|Montpellier, France
|No
|Alexis Bory
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|No
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|[http://mpserver12.flightgear.org MPServer12]
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|No
|Charles Ingels
|charles
|cbz-026
|
|-
|mpserver14.flightgear.org
|Zurich, Switzerland
|[http://mpserver15.flightgear.org Yes]
|Yves Sablonier
|gral
|gral
|
|-
|mpserver15.flightgear.org
|North Point, Hong Kong
|[http://mpserver15.flightgear.org Yes]
|Hazuki Amamiya
|Hazuki
|Hazuki
|
|-
|mpserver16.flightgear.org
|Texas, USA
|[http://mpserver15.flightgear.org Yes]
|Rob Dosogne
|truthsolo
|truthsolo
|
|-
|mpserver17.flightgear.org
|Cluj, Romania
|
|Marius
|tuxum
|tuxum
|Offline
|-
|mpserver18.flightgear.org
|Germany
|[http://mpserver15.flightgear.org Yes]
|
|
|
|
|}
''Information as at 2013-05-31''

Use [http://mpserver16.flightgear.org/ this], [http://mpmap01.flightgear.org/mpstatus/ this] or [http://flightgear.mxchange.org/mpstatus/ this] link to check if the MP servers are online. As of FlightGear 2.10.0, the in-sim dialog only displays servers that are available.

Geographic locations of the servers are also available at [http://goo.gl/maps/jBwUd Google Maps].

If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].

=== Multiplayer map ===
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at [http://mpmap01.flightgear.org mpmap01] and/or [http://mpmap02.flightgear.org mpmap02]. You will also find this useful to check that you are successfully connecting to the server.

== Getting online ==
As of FlightGear 2.4.0, multiplayer settings can be accessed via the in-sime Multiplayer menu. This is by far the easiest way to get online, but in some cases the methods mentioned below may be prefered.

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

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

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

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

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

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

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

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

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

--multiplay=in,10,,5000

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

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

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

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

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

* Under '''Linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP or later''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

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

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

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiple connections per computer ==
It is possible to run multiple FlightGear instances on a single computer and connect them all to the multiplayer network. However, this requires some extras to keep in mind:
* both instances use the same out-port.
* one instance uses in port=5001, the other port 5002.
* and of course should both instances have unique callsigns.

== Multiplayer chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Multiplayer > Pilot list dialog and click the ignore button next to the pilot's call sign. As of FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear 2.4.0 and later it will additionally prevent his aircraft from appearing.

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

[[Category:Multiplayer]]
[[Category:Howto|Multiplayer]]

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