FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 09:09, 30 March 2009

2,178 bytes added ,  30 March 2009
→‎The Client installation
(→‎Solving Audio-Problems: adding this chapter)
Line 152: Line 152:
''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>
''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>
====Test the basic function====  
====Test the basic function====  
Prior to your first FGCom-tests you should verify your audio-system, because the FGCom-installation relies heavily on a good performance of it. If you had already used microphone-recordings or VoIP and thus “trust” your system, then you may pass this chapter and continue with the “-f910”-test. But be sure to return here just as soon as the audio system is not performing as you expected!
Prior to your first FGCom-tests you should verify your audio-system, because the FGCom-installation relies heavily on a good performance of it. If you had already used microphone-recordings or VoIP and thus “trust” your system, then you may pass this chapter and continue with [[the -f910 Test]]. But be sure to return here just as soon as the audio system is not performing as you expected!
(--> [[The "-f910"-Test]])
<br><br>For these basic tests you do not have to start the FGFS nor do you need to operate the PTT (PushToTalk) button.
<br><br>For these basic tests you do not have to start the FGFS nor do you need to operate the PTT (PushToTalk) button.


Line 236: Line 235:
'''5) Find the “best fit”'''
'''5) Find the “best fit”'''


Now perform the following “-f910” test and make final adjustments if needed:
Now perform the following “-f910 Test" and make final adjustments if needed:


--[[User:Jomo|Jomo]] 08:28, 18 March 2009 (EDT)
--[[User:Jomo|Jomo]] 08:28, 18 March 2009 (EDT)
<br>
<br>
=====The "-f910"-Test=====
=====The -f910 Test=====
Prior to executing the following [[Command line|command]] change into the directory, into which the FGCom was installed. This path will then shown up before the "$" sign.
Prior to executing the following [[Command line|command]] change into the directory, into which the FGCom was installed. This path will then shown up before the "$" sign.
In case of a "cvs" installation you have to replace "fgcom" with "sh ./run_fgcom.sh". Then type:
In case of a "cvs" installation you have to replace "fgcom" with "sh ./run_fgcom.sh". Then type:
Line 263: Line 262:
<br>'''In case of trouble''' check the following:
<br>'''In case of trouble''' check the following:


*'''"parsed command-line options"''' not successful: Check for wrong commands and/or missing “-” signs in front of them. See [[FGCOM#FGCom Options|FGcom Options]].
*'''"parsed command-line options"''' not successful: Check for wrong commands and/or missing “-” signs in front of them. See [[FGCOM#Commandline Parameters|Commandline Parameters]].
*'''"Reading list of airports .."''' not successful: Check your file “positions.txt” which should be in the same directory in which you installed the FGCom. This is a normal text-file in which you can add missing informations. (Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added).
*'''"Reading list of airports .."''' not successful: Check your file “positions.txt” which should be in the same directory in which you installed the FGCom. This is a normal text-file in which you can add missing informations. (Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added).
*'''"Initializing IAX client"''' not successful: Check if you defined the right server, it must be "-Sfgcom.flightgear.org.uk”. Watch it: The “S” must be capital in Linux, but small for Windows (“-sfgcom.flightgear.org.uk”)!  
*'''"Initializing IAX client"''' not successful: Check if you defined the right server, it must be "-Sfgcom.flightgear.org.uk”. Watch it: The “S” must be capital in Linux, but small for Windows (“-sfgcom.flightgear.org.uk”)!  
Line 293: Line 292:
|}
|}
Wait for the Program-Window to start and then define:<br><br>
Wait for the Program-Window to start and then define:<br><br>
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the  PTT-key (“Push To Talk”) available. See [[Tips and Tricks]])<br>  
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the  PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]])<br>  
→ Click “Next”<br><br>
→ Click “Next”<br><br>
'''2)''' As '''starting place''' please define the airport KPAO (Palo Alto)  runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br>
'''2)''' As '''starting place''' please define the airport KPAO (Palo Alto)  runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br>
Line 346: Line 345:
<br><br>WARNING: When saving these settings and reloading them again, FGrun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".
<br><br>WARNING: When saving these settings and reloading them again, FGrun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".
|}
|}
If you need to '''define the unique IP-Address''', open an [[Command|command-window]] and type
If you need to '''define the unique IP-Address''', open an [[Command line|command-window]] and type
{|border="1"
{|border="1"
|+
|+
Line 445: Line 444:
   Reading list of airports...done.  
   Reading list of airports...done.  
   Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
   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]]
If your printout up to that line is different go back to chapter [[FGCOM#Test the basic function]]


For this test position this command-window somewhere, where you can monitor it throughout the test.
For this test position this command-window somewhere, where you can monitor it throughout the test.
Line 567: Line 566:
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".
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".


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".
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)
<br>--[[User:Jomo|Jomo]] 04:20, 18 March 2009 (EDT)


Line 604: Line 603:
ToBeDefined
ToBeDefined
====Tips and Tricks====
====Tips and Tricks====
'''Airport missing in FGCom:'''<br>
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line
  KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
You can add extra lines for any locations you want. e.g.: (watch the separation comas)
apt-code = DUMY  (a "dummy" or your favorite, but missing, airport code)
KHz      = take it out of your “FGFS-home/data/Airports/apt.dat.gz” or just take one of which you are sure that you do not need it in reality (FGFS)
long/lat =  take out of the Mpmap (or Google Map)
type    = whatever
name    = whatever
''(of course those definition are only known to your own PC and last only until the next data update!)''<br>
'''Editing'''<br>
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
*For windows you can use "WordPad"
*For Linux the "gedit" works fine<br>
'''Copying-Printing this WIKI-Page'''<br>
'''Copying-Printing this WIKI-Page'''<br>
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
Line 616: Line 631:
Remember the policies: '''Private use only''' !
Remember the policies: '''Private use only''' !


'''Editing'''<br>
'''Joystick:  ''' ref also: [[Joystick]]<br>
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you allready. Check e.g.:<br>
*For windows you can use "WordPad"
  <axis>        (instead of usual <axis n=”3”>
*For Linux the "gedit" works fine
<desc>Mixture</desc>
<number>
<'''unix'''>3</unix>
<'''mac'''>5</mac>
<'''windows'''>5</windows>
</number>
<binding>
<command>nasal</command>
<script>controls.mixtureAxis()</script>
</binding>
  </axis>
 
'''Joystick and PTT'''<br>
If you want to assigne the PushToTalk function to your joystick, add the following (for n="1" you have to find your own number!)
<button n="1">
  <desc>PTT - Push To Talk</desc>
  <binding>
  <command>nasal</command>
  <script>controls.ptt(1)</script>
  </binding>
  <mod-up>
  <binding>
    <command>nasal</command>
    <script>controls.ptt(0)</script>
  </binding>
  </mod-up>
</button>


'''Ports needed'''<br>
In case of problems over the INTERENT you might check that the the following ports are allowed:
1314 TCP if the Festival-Server is used for Text/Sound
2005 UDP Vcp-Stream
4569 UDP FGCom  VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer    (VPN Sftw.)
5001 UDP Enable HTTP-server
5002 UDP Enable property server
5003 UDP Enable Screen-Shot services
5004  UDP    (may be used as a spare)
5505 UDP Terra Sync
16661 UDP FGCom listening to FGFS, usually “local host” only
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).
<br><br>
'''PTT Problems''' (Push To Talk)
'''PTT Problems''' (Push To Talk)
*'''if the FGCom Command-window initiates, but does not respond to any COMM or PTT activity:'''
*'''if the FGCom Command-window initiates, but does not respond to any COMM or PTT activity:'''
Line 649: Line 676:
**Be sure the FGFS window is the active window. Move the Mouse-Pointer into the FlightGear-Window and click once, then try again (while the Mouse-Pointer remains in that window! Some systems do change the “active Window” according to where the mouse is!)
**Be sure the FGFS window is the active window. Move the Mouse-Pointer into the FlightGear-Window and click once, then try again (while the Mouse-Pointer remains in that window! Some systems do change the “active Window” according to where the mouse is!)
**Check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line “<key n="32">” then this plane is intentionally  using “key 32” (Space) for something other than the PTT. Known planes that do that as of Feb. 2009 are: an2, bluebird-base, ogel, OV10..,  seafireIIc, spitfireIIa, ufo.
**Check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line “<key n="32">” then this plane is intentionally  using “key 32” (Space) for something other than the PTT. Known planes that do that as of Feb. 2009 are: an2, bluebird-base, ogel, OV10..,  seafireIIc, spitfireIIa, ufo.
<br>
'''Timezones'''<br>
When communicating it may be wise to always use the internationally accepted GMT (GreenwichMeanTime). On http://www.timezoneconverter.com/cgi-bin/tzc.tzc everybody can check what GMT means to him/her and thus knows what time you mean.


===Supplemantery Informations===
===Supplemantery Informations===
====Commandline Parameters====
====Helpfull INTERNET Adresses====
'''World-Time:''' http://www.timezoneconverter.com/cgi-bin/tzc.tzc
<br>especially for multiplayer evants you should define all times in the internationally used GMT (Greenwich Meantime). Just pick up your deviation from GMT and memorize it. If everybody does it, we could avoid a lot of misunderstandings.<br><br>
'''Dezimal to Degree''' http://www.hbnweb.de/mathematik/grad-dezimal.html <br>
Some programs need Decimal Lon/Lat values, others the Degrees/Minuts/Sec. Just convert it.<br><br>
'''Miles, km, feet, etc. etc. ...''': http://www.convertunits.com/
<br>If like to avoid troubles (like e.g. NASA lost a satellite because of it) just look it up.


''Or if it didn't work perfectly first time''
'''Ports needed'''<br>
 
In case of problems over the INTERENT you might check that the the following ports are allowed:
    fgcom --help
1314 TCP if the Festival-Server is used for Text/Sound
2005 UDP Vcp-Stream
4569 UDP FGCom  VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer    (VPN Sftw.)
5001 UDP Enable HTTP-server
5002 UDP Enable property server
5003 UDP Enable Screen-Shot services
5004  UDP    (may be used as a spare)
5505 UDP Terra Sync
16661 UDP FGCom listening to FGFS, usually “local host” only
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).


====Commandline Parameters====
fgcom --help
returns the following useful info
returns the following useful info
     fgcom - a communication radio based on VoIP with IAX/Asterisk
     fgcom - a communication radio based on VoIP with IAX/Asterisk
     (c)2007 by H. Wirtz <wirtz@dfn.de>
     (c)2007 by H. Wirtz <wirtz@dfn.de>
Jomo
652

edits

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

Navigation menu