Howto:Multiplayer: Difference between revisions

→‎Using multiplayer from the command line: re-enforce not using existing callsigns - line copied from another section of this page
(→‎Using multiplayer from the command line: re-enforce not using existing callsigns - line copied from another section of this page)
(8 intermediate revisions by 5 users not shown)
Line 44: Line 44:
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
--multiplay=direction,10,ip.address,port
--multiplay=direction,10,ip.address,port
--callsign=anything  
--callsign=anything
</syntaxhighlight>
</syntaxhighlight>


Obviously, <code>--callsign</code> can be anything you wish. There are four arguments to <code>--multiplay</code>:
Obviously, <code>--callsign</code> can be anything you wish but it must be limited to 7 (seven) characters in length counting any dashes. If your callsign is too long, it will be cut off in the various displays where it is shown. Generally speaking, callsigns are of the form X-XXXXX. 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! Please don't leave your callsign as "CALLSIG".
 
There are four arguments to <code>--multiplay</code>:
; direction
; 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'''.
: 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'''.
Line 87: Line 89:
[[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.]]
[[File:Direct-p2p-multiplayer-setup.png|800px|Screenshot demonstrating a "peer-to-peer" setup between two FlightGear instances running on the same machine via localhost (127.0.0.1) without any multiplayer server.]]


You can add an arbitrary number of channels to mirror your flight onto other servers, e.g. to a private fgms server using  
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">
<syntaxhighlight lang="bash">
--multiplay=out,10,my.private.server.ip,5000
--multiplay=out,10,my.private.server.ip,5000
Line 97: Line 99:
</syntaxhighlight>
</syntaxhighlight>


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




Line 128: Line 130:
</syntaxhighlight>
</syntaxhighlight>


Choose your own callsign, but check [http://fgfs.i-net.hu/modules/fgtracker/ this page] first to see whether your desired callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!
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;
Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;
Line 210: Line 212:
| {{yes|Up}}
| {{yes|Up}}
| Germany  
| Germany  
| {{no}}
| {{yes}}
| Hergen
| Hergen
| {{N/a}}
| {{N/a}}
| {{N/a}}
| {{N/a}}
| {{N/a|None}}
| [https://mpserver03.flightgear.org mpserver03.flightgear.org]
|-
|-
| mpserver04.flightgear.org
| mpserver04.flightgear.org
Line 358: Line 360:
| drr0ckso
| drr0ckso
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21111 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}}
| {{N/a|None}}
|-
|-
Line 369: Line 389:
| Radio horizon is 414 miles
| Radio horizon is 414 miles
|-
|-
| gameplayer.club
| mpserver87.megaf.info
| {{yes|Up}}
| {{yes|Up}}
| South San Francisco, California, USA
| Paris, France
| {{yes}}
| {{yes}}
| Marisa Giancarla
| Megaf
| marisag
| Megaf
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21111 marisag]
| [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21017 Megaf]
| {{N/a|None}}
| Not linked to others yet
|}
|}


185

edits