Howto:Multiplayer: Difference between revisions

Jump to navigation Jump to search

Howto:Multiplayer (view source)

Revision as of 13:08, 26 March 2015

27 bytes removed ,  26 March 2015
no edit summary
mNo edit summary
No edit summary
Line 35: Line 35:
# In the <tt>Multiplayer Options</tt> area …
# In the <tt>Multiplayer Options</tt> area …
#* Type your desired callsign into the box.
#* Type your desired callsign into the box.
#* Set the in/out parameters in the two other boxes; see below for correct syntax.
#* Set the parameters for the two other boxes; see below for correct syntax.
#* Click {{button|OK}}, then run FlightGear.
#* Click {{button|OK}}, then run FlightGear.
{{-}}
{{-}}


=== Using multiplayer from the command line ===
=== Using multiplayer from the command line ===
{{wip}}
{{WIP}}
When running FlightGear from the [[command line]], you can specify multiplayer settings.  The two arguments are as follows:
When running FlightGear from the [[command line]], you can specify multiplayer settings.  The two arguments are as follows:
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
Line 47: Line 47:
</syntaxhighlight>
</syntaxhighlight>


<code>--multiplay</code>  
Obviously, <code>--callsign</code> can be anything you wish, although it is limited to seven characters.  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'''.


where 5000 is the port number the server is listening on (which is 5000 for the official servers).
; ip.address
: IP address of network interface being used by FlightGear.  If left blank, FlightGear will listen to all network intefaces.  If '''direction''' is set to <code>in</code>, FlightGear will listen to ''only'' this IP address.


If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:
; port
<syntaxhighlight lang="bash">
: Port that data is either being sent or received through. Usually set to <code>5000</code> and above.
--multiplay=in,10,your.ip.address,portnumber
</syntaxhighlight>
 
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:
<syntaxhighlight lang="bash">
--multiplay=in,10,,5000
</syntaxhighlight>


{{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O  port to the corresponding port of the other instance:
{{tip|For a local setup between two fgfs instances without any [[Fgms|fgms/multiplayer server]] being involved, you merely need to map each I/O  port to the corresponding port of the other instance:
Line 73: Line 69:
}}
}}


 
{{Note|FGRun expects you to enter a valid IP address or hostname for the local network interface.}}
''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!
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!
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/82852"

Navigation menu