FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search
Remove all reference to fgcom01 server, as only fgcom.flightgear.org should be used
m (change server "delta384.server4you.de" to new "fgcom01.flightgear.org")
(Remove all reference to fgcom01 server, as only fgcom.flightgear.org should be used)
Line 120: Line 120:
then you can start fgcom like this:
then you can start fgcom like this:
<tr><pre>
<tr><pre>
./run_fgcom.sh -Sfgcom01.flightgear.org
./run_fgcom.sh -Sfgcom.flightgear.org
</pre></tr>
</pre></tr>
</table></div>
</table></div>
Line 263: Line 263:


==== Start FGCom ====
==== Start FGCom ====
Open a [[Command line|command-window]] and change into the directory in which FGCom was installed (probably the same as FlightGear) and start FGCom. You must decide what server you want to use! As of Oct.2013 there are 2 FGCOM-servers available:
Open a [[Command line|command-window]] and change into the directory in which FGCom was installed (probably the same as FlightGear) and start FGCom. The server you want to use for events is '''fgcom.flightgear.org''' (fgcom.flightgear.org.uk was the originally used server and is not available any more).
::{| border="2" cellpadding="5"
||fgcom01.flightgear.org||This is the currently (Oct 2013) used server for events.
|-
||fgcom.flightgear.org||This is a new development. It should be formally available with FS 3.0, expected for Spring 2014. You may use it for testing
|-
||''<small>(fgcom.flightgear.org.uk)</small>''||''<small>This originally used server is not available any more</small>''
|}
Due to technicalities it is not possible to speak from 1 server to the other - so try one and change if you notice that your friends are using the other.


To start FGCom with a defined server you must insert the server-address after a "-S" (watch: The "S" must be a capital!):
To start FGCom with the defined server you must insert the server address after a "-S" (watch: The "S" must be a capital!):
::{| border="2" cellpadding="5"
::{| border="2" cellpadding="5"
! style="background:#efefef" |Linux||fgcom -Sfgcom01.flightgear.org  
! style="background:#efefef" |Linux||fgcom -Sfgcom.flightgear.org  
|"-Sfgcom..." with capital "S"
|"-Sfgcom..." with capital "S"
|-
|-
Line 284: Line 276:
|-
|-
! style="background:#efefef" |Windows  
! style="background:#efefef" |Windows  
|cd 'C:\Program Files\Flightgear\win32'<br />fgcom.exe -Sfgcom01.flightgear.org  
|cd 'C:\Program Files\Flightgear\win32'<br />fgcom.exe -Sfgcom.flightgear.org  
|"-Sfgcom..." with capital "S"
|"-Sfgcom..." with capital "S"
|}
|}
Line 300: Line 292:
   Successfully parsed command-line options.  
   Successfully parsed command-line options.  
   Reading list of airports...done.  
   Reading list of airports...done.  
   Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org1)
   Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org)
If, due to a prior flight, COM1 was set to anything else but 118.600 (e.g. to 119.650) you will see the following 2 lines added to the above shown initialization of the FGCom-window:
If, due to a prior flight, COM1 was set to anything else but 118.600 (e.g. to 119.650) you will see the following 2 lines added to the above shown initialization of the FGCom-window:
  Selected frequency: 119.650  
  Selected frequency: 119.650  
Line 537: Line 529:
     Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!
     Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!


Also note that the current server (fgcom.flightgear.co) works with guest account, so '''do not use -U or -P'''
Also note that the current server (fgcom.flightgear.org) works with guest account, so '''do not use -U or -P'''


== Server installation ==
== Server installation ==
13

edits

Navigation menu