FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 08:20, 18 March 2009

337 bytes added ,  18 March 2009
m
→‎Functional Test + User Briefing: correct Win-Explorer dependencies
m (KPAO is Palo Alto not Livermore)
m (→‎Functional Test + User Briefing: correct Win-Explorer dependencies)
Line 177: Line 177:


====Functional Test + User Briefing====
====Functional Test + User Briefing====
''If in the following some pictures seem to small to read on your screen, click on it and it will enlarge. Then return with the left arrow at the top of your screen.''
=====Preflight=====
There is no real significance in the order in which we start FGFS and FGCom. Let us start the FGCom first, so that we can watch all of it's behavior from the beginning and then progress in a predefined order of appearance.


Open a [[command|command-window]] and change into the directory in which FGCom was installed (probably the same as the FGFS) and start the FGCom. Do not use any other options than the server address “-sfgcom.flightgear.org.uk”:
Experiences pointed out, that the cooperation FGCom/FGFS works more reliable, if the FGFS gets started first. So we will start with setting up a test-environment:
{|border="1"
=====Start the FGFS=====
|+
''If in the following some pictures seem to small to read on your screen, click on it and it will enlarge. Then return with the left arrow at the top of your screen.''<br><br>
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs<br>sh ./run_fgcom.sh
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Windows e.g.: ||D:<br>cd \flightgear<br>fgcom -sfgcom.flightgear.org.uk ||"-sfgcom..." with small "s"
|-
||for Mac: || ||
|}
The response should be:
  /fgcom - a communication radio based on VoIP with IAX/Asterisk
  (c)2007 by H. Wirtz <wirtz@dfn.de>
  Version 1.2.2 build 206M
  Using iaxclient library Version SVN 206M
 
  Successfully parsed command-line options.
  Reading list of airports...done.
  Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
If your printout is different see Chapter [[Test the basic function]]
 
Keep this command-window open and accessible for further status/problem indications.
 
 
'''Prepare the FGFS-start in FGrun:'''<br>
We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for the FGCom-operation:
We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for the FGCom-operation:


Line 237: Line 208:
|+
|+
|-
|-
|width=620|[[image:FGrun_base.jpg|thumb|left|600px|Basic + Multiplayer Options]]
|width=610|[[image:FGrun_base.jpg|thumb|left|600px|Basic + Multiplayer Options]]
|“AI models” must be activated in order to see all traffic
|“AI models” must be activated in order to see all traffic
<br><br>“Multiplayer” must be activated
<br><br>“Multiplayer” must be activated
Line 252: Line 223:
|+
|+
|-
|-
|[[image:FGrun_IP.jpg|thumb|left|400px|Advanced: Initial Position]]
|width=420|[[image:FGrun_IP.jpg|thumb|left|400px|Advanced: Initial Position]]
|
|
You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''
You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''
Line 261: Line 232:
|+
|+
|-
|-
|[[image:MPmap.jpg|thumb|left|500px|Preflight]]
|width=510|[[image:MPmap.jpg|thumb|left|500px|Preflight]]
|
|
*if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
*if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
Line 278: Line 249:
|+
|+
|-
|-
|[[image:FGrun_net.jpg|thumb|left|400px|Preflight]]
|width=420|[[image:FGrun_net.jpg|thumb|left|400px|Preflight]]
|Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.  
|Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.  
|}
|}
Line 308: Line 279:
|+
|+
|-
|-
|[[image:FGrun_IO.jpg|thumb|left|400px|Preflight]]
|width=420|[[image:FGrun_IO.jpg|thumb|left|400px|Preflight]]
|You do need a "generic" line as shown, because '''this defines the interface between FGFS and FGCom'''.
|You do need a "generic" line as shown, because '''this defines the interface between FGFS and FGCom'''.
<br><br><br>
<br><br><br>
Line 346: Line 317:
|+
|+
|-
|-
|[[image:FGrun_prop.jpg|thumb|left|500px|Preflight]]
|width=520|[[image:FGrun_prop.jpg|thumb|left|500px|Preflight]]
|
|
e.g. I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
e.g. I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
Line 353: Line 324:
<br><br>Delete a line: Click onto the line to be deleted then hit "Delete"
<br><br>Delete a line: Click onto the line to be deleted then hit "Delete"
|}
|}
Hit “OK” → “Run” and watch the FGFS starting. If screen-place allows you may want to pull the shown "FGFS Report-Window" to the side and watch how busy your PC is while loading the other multi-player models.<br>
--[[User:Jomo|Jomo]] 13:55, 12 March 2009 (EDT)
--[[User:Jomo|Jomo]] 13:55, 12 March 2009 (EDT)


=====FGCom cooperating with FGFS=====
=====Start the FGCom=====
In the open FGrun program-window hit “OK” → “Run” and watch the FGCom command-window (constantly, if screen-space allows):
Open a [[command|command-window]] and change into the directory in which FGCom was installed (probably the same as the FGFS) and start the FGCom. Do not use any other options than the server address “-sfgcom.flightgear.org.uk”:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs<br>sh ./run_fgcom.sh
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Windows e.g.: ||D:<br>cd \flightgear<br>fgcom -sfgcom.flightgear.org.uk ||"-sfgcom..." with small "s"
|-
||for Mac: || ||
|}
The response should be:
  /fgcom - a communication radio based on VoIP with IAX/Asterisk
  (c)2007 by H. Wirtz <wirtz@dfn.de>
  Version 1.2.2 build 206M
  Using iaxclient library Version SVN 206M
 
  Successfully parsed command-line options.
  Reading list of airports...done.
  Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
If your printout up to that line is different go back to chapter [[Test the basic function]]
 
For this test position this command-window somewhere, where you can monitor it throughout the test.
 
{|
{|
|+
|+
Line 362: Line 360:
|width="300"| ||
|width="300"| ||
|-
|-
|1) If COM1 was set to 119.650 during a prior session you will now see the following 2 lines added to the initialization of the FGCom-window, as soon as FGFS comes up: ||
|1) If COM1 was set to 119.650 you will see the following 2 lines added to the initialization of the FGCom-window: ||
|-
|-
|
|
Line 467: Line 465:
  Call rejected by remote  
  Call rejected by remote  
  [LISTEN] mute mic, unmute speaker  
  [LISTEN] mute mic, unmute speaker  
|That means: at about 50KM we are getting out of range and thus the on COM2 active SF getts terminated. Notice that also the inactive NAV2 gets terminated, because it exceeded the allowable range at about the same time!
|That means: at about 50KM we are getting out of ran'''Start the FGFS:'''<br>ge and thus the on COM2 active SF getts terminated. Notice that also the inactive NAV2 gets terminated, because it exceeded the allowable range at about the same time!
|}
|}
10) You could turn now and watch the opposite: At about the same distance those two will become active again (automatically, if you did not change the settings).
10) You could turn now and watch the opposite: At about the same distance those two will become active again (automatically, if you did not change the settings).
<br><br>
<br><br>
If you got here without any (technical) problems your FGCom is fully functional. All you have to do now, is trying to test the audio.
If you got here without any (technical) problems your FGCom is fully functional. All you have to do now, is trying to test the audio.
=====Audio Test=====
=====Final Audio Test=====
There is no formal Test-Environment for that. Just cruise within the San Francisco (or any other) area and listen and/or try calling from time to time:  “This is ''YourCallSign'', is somebody listing” or similar. If you hear somebody talking (and it is not the AI-ATC chatter!) but get no answers, see the chapter "Solving Audio-Problems".
There is no formal Test-Environment for that. Just cruise within the San Francisco (or any other) area and listen and/or try calling from time to time:  “This is ''YourCallSign'', is somebody listing” or similar. If you hear somebody talking (and it is not the AI-ATC chatter!) but you get no answers, see the chapter "Solving Audio-Problems".
--[[User:Jomo|Jomo]] 05:36, 13 March 2009 (EDT)
 
Also there are many "Multiplayer Events" which use the FGCom possibilities, but also use the text-based FGFS-Menu "Network --> Chat" to enable communication outside the FGCom. See the Flightgear-Forum [[ http://www.flightgear.org/forums/]] and there the "Multiplayer Events".
<br>--[[User:Jomo|Jomo]] 04:20, 18 March 2009 (EDT)


===Solving Audio-Problems===
===Solving Audio-Problems===
Jomo
652

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/11466"

Navigation menu