FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 07:20, 1 October 2009

9,751 bytes removed ,  1 October 2009
m
1st part of restructuring due to now 3 Parts: FGCOM, FGCOM for WIndows, FGCOM_Testing
m (1st part of restructuring due to now 3 Parts: FGCOM, FGCOM for WIndows, FGCOM_Testing)
Line 2: Line 2:


'''FGCom''' is an addon for [[FlightGear]]. With FGCom (and the infrastructure behind it), FlightGear now has a realtime voice communication system which enriches the FlightGear capabilities, especially for Multiplayer events, like:
'''FGCom''' is an addon for [[FlightGear]]. With FGCom (and the infrastructure behind it), FlightGear now has a realtime voice communication system which enriches the FlightGear capabilities, especially for Multiplayer events, like:
*flying in groups  (see e.g. the '''Forum Multiplayer Events'''):
*flying in groups  (see e.g. the '''Forum Multiplayer Events''' on http://www.flightgear.org/forums/):
**invite friends to a guided sightseeing tour in your most beloved area or do “Fly In's”
**invite friends to a guided sightseeing tour in your most beloved area or do “Fly In's”
**do military training like [[Howto: Air-Air Refueling|“Air-Air-Refuelling”]], “Dog fights”, “Escort flights”, etc.  
**do military training like [[Howto: Air-Air Refueling|“Air-Air-Refuelling”]], “Dog fights”, “Escort flights”, etc.  
*offering additional services at an airport like [[Air traffic control|ATC]], [[Vehicle|Snowplows, Pushbacks]], [[FlightGear Race|Racing-Events]] etc.
*offering additional services at an airport like [[Air traffic control|ATC]], [[Vehicle|Snowplows, Pushbacks]], [[FlightGear Race|Racing-Events]] etc.
*have a [[Dual control|real time flighttraing]] (e.g. pilot in Hongkong, teacher in Sydney) or do [[Soaring|Glider-towing]] or just ask for on-line support during flight or just ask somebody flying a plane of interest about specifics
*have a [[Dual control|real time flighttraing]] (e.g. pilot in Hongkong, teacher in Sydney) or do [[Soaring|Glider-towing]] or just ask for on-line support during flight or just ask somebody flying a plane of interest about specifics
*or e.g. just sit in a cockpit e.g. in Germany while sightseeing San Francisco in a C172, voice-chatting with a Texan in a plane I dreamed of as a boy (Super Constellation), and both getting informations from a New Zealand guy (it shall be a wonderful island – but do real people live there? He said: Yes!!).
*or e.g. just sit in a cockpit in Germany while sightseeing San Francisco in a C172, voice-chatting with a Texan in a plane I dreamed of as a boy (Super Constellation), and both getting informations from a New Zealand guy (it shall be a wonderful island – but do real people live there? He said: Yes!!).
*etc.
*etc.
You can even use it in models without radios - just use the standard FlightGear menu --> Equipment --> Radio Settings.<br>
You can even use it in models without radios - just use the standard FlightGear menu --> Equipment --> Radio Settings.<br>
Line 13: Line 13:
In the future FGCom surely will extend further and surely will get a “Speech to Text” capability in order to also integrate the Text-based automated ATC-routines inside FlightGear.
In the future FGCom surely will extend further and surely will get a “Speech to Text” capability in order to also integrate the Text-based automated ATC-routines inside FlightGear.


==Status==
<br><br>
*'''March, 2009:'''
=='''The Client installation'''==
Adding User-Informations for installing, using, maintaining FGCOM on different platforms.
===Prequisites===
 
*'''18 November, 2008:'''
Latest SVN (rev 163) has the compile problems fixed. Also we have a '''new server: fgcom.flightgear.org.uk'''. User accounts not required (ie. do '''not''' use -U or -P)
*'''31 October, 2008:'''
 
The latest SVN release at this time is the '''r149''' which does not compile due to a constant that is not defined (STL_STRING). Such constant appears at line 57 in the file ''src/fgcom_init.cpp'' which is:
''#include STL_STRING''
 
I guess that such constant must point to the STL library include file but I am not sure.
I revert to the '''r148''' SVN version which successfully compiles.
 
Command to get such version is: ''svn co -r148 svn://svn.dfn.de:/fgcom/trunk fgcom-r148''
 
* '''19 June, 2008:''' Currently the server is <u>down</u> due to hardware problems. It is unknown when the service comes back because he currently has no time to fix the problems.
 
* '''22 November 2007:''' Due to heavy development at this time there may be some differences between the information on the web pages and the installation. Please follow the discussions on the FlightGear development list!
 
==The Client installation==
===Installing FGCom===
====Hardware Requirements====
====Hardware Requirements====
If you are satisfied with the operation and responsetimes of your current FGFS installation, then you should see no significant difference after adding the FGCom. If your FGFS installation runs already a little marginal, then you might experience some delays when many new airplane-models etc. must be loaded. This may happen  when starting up at a busy airport. You can monitor/verify such a "short-time overload" in the FGstart command-window.
If you are satisfied with the operation and responsetimes of your current FGFS installation, then you should see no significant difference after adding the FGCom. If your FGFS installation runs already a little marginal, then you might experience some delays when many new airplane-models etc. must be loaded. This may happen  when starting up at a busy airport. You can monitor/verify such a "short-time overload" in the FGFS command-window.


For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html
For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html
Line 42: Line 23:
Of course you will also need a connection to the Internet for worldwide voice communication to work.
Of course you will also need a connection to the Internet for worldwide voice communication to work.


====Prequisites/Companions====
<br>
 
====Software Requirements====
{| style="width:75%" border="1"
{| style="width:75%" border="1"
|+
|+
|-
|-
|align="center" width="100" |'''FGFS''' ||The basic Flight-Gear-Flight-Simulation installation. This must be installed prior to installing the FGCom ''(except if installing the Linux "CVS complete" version which can install FGCom and FGFS concurrently)''. ref.: http://www.flightgear.org/  
|align="center" width="100" |'''FGFS''' ||The basic Flight-Gear-Flight-Simulation installation. This must be installed prior to installing the FGCom ''(except if installing the Linux "CVS complete" version which can install FGCom and FGFS concurrently)''.
ref.: http://www.flightgear.org/  
|-
|align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of the FGFS. As the name says, it enables communication of several players via a chat-function (keyboard) - or with this vocal interface ==> FGCom.
|}
<br>
====Nice to have====
{| style="width:75%" border="1"
|+
|-
|-
|align="center" | '''FGrun'''||This [[FlightGear Launch Control]] (also known as FG-Wizard), is a graphical front end to start the FGFS. This makes it very easy to startup the FGFS with all it's possible options. In some newer distributions this is already part of the basic FGFS installation package
|align="center" | '''FGrun'''||This [[FlightGear Launch Control]] (also known as FG-Wizard), is a graphical front end to start the FGFS. This makes it very easy to startup the FGFS with all it's possible options. In some newer distributions this is already part of the basic FGFS installation package
|-
|-
|align="center" |'''Atlas'''||[[Atlas]] displays the current position of your airplane on an landscape type of map together with navigational informations. It derives its data direct out of the installed FGFS databases. So you do not need any connections to the INTERNET.
|align="center" |'''MPMap'''||[[MPMap]] is a pure browser application based on Google Maps, so it does not need any installation, except a Web-Browser. With MPMap you can watch all Multiuser-planes worldwide on a road-map, satellite picture or a composite of both. It includes most of the airports, navigational aids, and current weather informations. So it can be used for preflight planning, without having the FGFS started or even installed. But it needs a constant connection to the INTERNET - on the other hand you can do your preflight planning anywhere where there is a PC, connected to the INTERNET.
|-
|-
|align="center" |'''MPMap'''||[[MPMap]] is a pure browser application based on Google Maps, so it does not need any installation, except a Web-Browser. With MPMap you can watch all Multiuser-planes worldwide on a road-map, satellite picture or a composite of both. It includes most of the airports, navigational aids, and current weather informations. So it can be used for preflight planning, without having the FGFS started or even installed. But it needs a constant connection to the INTERNET - on the other hand you can do your preflight planning anywhere where there is a PC, connected to the INTERNET.
|align="center" |'''Runwayfinder'''||This standalone Browser-Application( http://www.runwayfinder.com ) does present a fantastic Fight-Planning tool, showing similar aspects like the "MPMap" but adds an Aeronatical map. It does not link to FGFS or MPMap or Multiplayer -- and covers only the domestic USA.  
|-
|-
|align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of the FGFS. As the name says, it enables communication of several players via a chat-function (keyboard) - or with this vocal interface ==> FGCom.
|align="center" |'''Atlas'''||[[Atlas]] displays the current position of your airplane on an landscape type of map together with navigational informations. It derives its data direct out of the installed FGFS databases. So you do not need any connections to the INTERNET.
|-
|-
|align="center" |'''Festival'''||Festival is a TTS (Text To Speech) system that can convert all in the FGFS displayed written text (ATC, Chat, etc.) into speech and put it on your loudspeakers. ref.: http://www.flightgear.org/Docs/getstart/getstartch5.html#x10-790005.6  
|align="center" |'''Festival'''||Festival is a TTS (Text To Speech) system that can convert all in the FGFS displayed written text (ATC, Chat, etc.) into speech and put it on your loudspeakers. ref.: http://www.flightgear.org/Docs/getstart/getstartch5.html#x10-790005.6  
|-
|align="center" |'''Runwayfinder'''||This standalone Browser-Application( http://www.runwayfinder.com ) does present a fantastic Fight-Planning tool, showing similar aspects like the "MPMap" but adds an Aeronatical map. It does not link to FGFS or MPMap or Multiplayer -- and covers only the domestic USA.
|}
|}
<br>
===Installing FGCom===
====Install on Linux====
====Install on Linux====
For Linux-Systems there are 3 ways to install:
For Linux-Systems there are 3 ways to install:
Line 68: Line 57:
*'''Disadvantage:''' The availability of those packages is usually very late and most Distributors do not cover all FGFS-features. To our knowledge none of the Distributors has an FGCom package available as of March 2009.
*'''Disadvantage:''' The availability of those packages is usually very late and most Distributors do not cover all FGFS-features. To our knowledge none of the Distributors has an FGCom package available as of March 2009.
*'''Installation:''' Follow the usual procedures of your distributer on how to install additional packages.
*'''Installation:''' Follow the usual procedures of your distributer on how to install additional packages.
<br>
'''2) Installing a “CVS complete”'''  
'''2) Installing a “CVS complete”'''  
*'''Advantage:''' It is the very easiest form of installation and installs in one step all prerequisite/companion modules (FGFS, FGrun, FGcom, PLIB, OSG, Simgear, AT). Also it can be added and removed from the system without disturbing the rest of the system (Libraries, Menus, Structures, etc.). It was tested on several Ubuntu and Debian systems.
*'''Advantage:''' It is the very easiest form of installation and installs in one step all prerequisite/companion modules (FGFS, FGrun, FGcom, PLIB, OSG, Simgear, AT). Also it can be added and removed from the system without disturbing the rest of the system (Libraries, Menus, Structures, etc.). It was tested on several Ubuntu and Debian systems.
*'''Disadvantage:''' No automated maintenance available. The handling is a little different from the standard Menu-driven practice.
*'''Disadvantage:''' No automated maintenance available. The handling is a little different from the standard Menu-driven practice.
*'''Installation:'''  http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_Debian/Ubuntu
*'''Installation:'''  http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_Debian/Ubuntu
<br>
'''3) Compiling it locally'''
'''3) Compiling it locally'''
*'''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.
*'''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.
Line 105: Line 96:
  make install
  make install
</li><br><li>
</li><br><li>
continue with [[FGCOM#Test the basic function|testing the basic functions]]
continue with chapter [[FGCOM#Test the basic function|testing the basic functions]]
</li></ol>
</li></ol>


<br>
====Install on Windows====
====Install on Windows====
There is no download available directly from the FlightGear home-pages, so you need to search for one in the Internet. We found and tested that one: http://emmerich-j.de/FGFS
Please use the Windows-Installation description on http://wiki.flightgear.org/index.php/FGCOM_for_Windows
*Download the ZIP-file “'''FGCOM_win_08-19-2009.zip'''” (or similar) to your favorite download-directory
*Unzip the 3 downloaded files into your FGFS- or FGCOM-directory
** fgcom.exe
** phonebook.txt
** positions.txt
More detailed Informations about installing FGCOM under windows you find on: http://wiki.flightgear.org/index.php/FGCOM_for_Windows


<br>
====Install on Mac====
====Install on Mac====
You can download the "MAC OSX Binary" from the FGFS download-center ( http://www.flightgear.org/Downloads/binary.shtml#mac ). The current version of the code does contain the FGCOM.  
You can download the "MAC OSX Binary" from the FGFS download-center ( http://www.flightgear.org/Downloads/binary.shtml#mac ). The current version of the code does contain the FGCOM.  
Line 122: Line 109:
But '''you do need OS X 10.5''' as prerequisite. With lower versions you will end up with a generic "bus error" message!
But '''you do need OS X 10.5''' as prerequisite. With lower versions you will end up with a generic "bus error" message!


<br>
===Testing===
===Testing===
''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>
During testing we will
====Test the basic function====
#test the basic FGCOM-functions without the FGFS
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 [[FGCOM#The -f910 Test|the -f910 Test]]. But be sure to return here just as soon as the audio system is not performing as you expected!
#after that the FGCOM together with the FGFS
<br><br>For these basic tests you do not have to start the FGFS nor do you need to operate the PTT (PushToTalk) button.
#then test/adjust the Microphone and Loudspeaker


=====Verifying your Audio-System=====
For these tests please see the [[FGCOM_Testing|FGCOM_Testing]]
Keep the audio-tools easily accessible for adjustments. Please be aware that, due to the different Operating-Systems multiplied by the different Sound-Cards, there are thousands of different tools available for the following tasks. If you cannot recognize the tools by the sample-pictures, please see your system and/or sound-card documentation for the tools you can use for the following basic tasks:
#Make sure you have '''easy access to your audio-controls''' – and know them.
#From the devices available '''define the audio-devices''' you want to use. You may have an audio-module on your motherboard, and multiple sound-cards,  and headsets, and Dolby-surround, etc. etc. We strongly recommend to use a headset (at least not to use loudspeakers) in order to reduce the very possible problem of feedback noise. A further reduction in noise can be achieved by using USB-headsets.
#'''Adjust''' your master '''volume-control''' and possible sub-controls to please your ears. Check your volume-control-panel for all controls that may influence your sound output. At least there is one master-control affecting all outputs. In addition there may be several outputs with individual adjustments. You may switch all regulators and switches off – and then switch them on one by one to find out which ones you need. You may also look into all tabs of your volume-control-panel, to see if there are features which may not have been used yet (if e.g. you never yet used a microphone, or VoIP, etc.)
#'''Adjust the Microphone''' and “Boost” devices. All modern Operating-Systems do have an integrated audio-recorder for such adjustments – you should be able to make an acceptable speech-recording. Most microphones do need a “boost” device-driver or extra amplifier. It is nice that all systems do provide this capability, but you have to activate it manually (if needed)! Also be aware that some of the devices may be switched off automatically if the system gets rebooted or an application gets closed.
#Finally '''find the “best fit”''' between your hardware, the network, and the FGCom-server response.


See the following examples:
<br>
 
===Functional Test + User Briefing===
'''1) Easy access to your audio-controls:''' You may need those controls often, so they should be placed easily accessible. Check if you have the Audio-Icon in your Task-bar:  e.g.
[[image:FGCOM-Audio-Icon.jpg|thumb|center|400px|Audio-Icon]]
If there is no such Icon anywhere on the screen do:
{| align=center width=900 border="1"
|+
|width=300|typical for '''Linux'''
|width=300|typical for '''Windows'''
|width=300|typical for '''MAC'''
|-
|<br>To my knowledge the icon is shown on all graphical systems of all Linux-Distributions. Thus there is no action required.
|Click on Start → Control Panel → Sounds and Audio:
[[image:FGCOM-W-Volume.jpg|thumb|center|250px|Enabel Audio-Icon]]
|}
<br>'''2) Define the audio-devices to use:'''
{| align=center width=900 border="1"
|-
|width=300|Enter [[Command line|command]]: ''gnome-sound-properties''
[[image:FGCOM-U-Prefs.jpg|thumb|center|250px|test devices]]
For each task you can open a selection-menu (on the right the downward arrow) in order to select the wanted device. I suggest to first try setting all to "Autodetect". Then click onto the green "Test"-button. If you need to make changes, reboot the PC after each change!
|width=300|Click right onto the audio-icon → Preferences → Audio-tab:
[[image:FGCOM-W-Audio.jpg|thumb|center|250px|set devices]]
Select your Devices for Playback and Mic.
|width=300|
|}
If you did change these device-settings, it is a good idea to reboot the PC and retest the settings prior to continue.
<br><br>
'''3) Adjust volume-control'''  (for theses first adjustments you should switch off the Mic.!)
{| align=center width=900 border="1"
|-
|width=300|Click right on Audio-Icon → Open Vol. Ctrl:
[[image:FGCOM-UVolCtrl.jpg|thumb|center|250px|Volume Control]]
The amount of the slider-controls vary depending on the capabilities of the sound-card or the usage of USB-headsets.
 
The “booster” is available under “Switches”.
|width=300|Click right on the Audio-Icon → Volume-Ctrl. (or type command:  sndvol32)
[[image:FGCOM-W-VolCtrl.jpg|thumb|center|250px|set devices]]
In this example the card overrides the std. Microsoft “Mic.” with “Rear Pink In” because all jacks can accept whatever you like!) - in this case it is the Mic. Be aware of such changes caused by usually “high expense” devices!
 
The “booster” is available under options.
|-
|width=300|Just click onto the green “Test” marks in the above device-selection and adjust  the volume controls for a good sound.
|width=300|Click on tab. Sounds
[[image:FGCOM-W-Sound.jpg|thumb|center|250px|Sound-test]]
Select one of the longer lasting signals (1), then click on 2 and adjust loudness with above slider-controls.
|width=300|
|}
<br>'''4) Adjust the Microphone:'''
<br>Use the volume-control-panels to enable the microphone for this test. Then:
{| align=center width=900 border="1"
|-
|width=300|Open the recorder with the [[Command line|command]]: ''gnome-sound-recorder''
[[image:FGCOM-U-sndctrl.jpg|thumb|center|250px|Recording-test]]
*Record
*Stop
*Play
|width|Open the Recorder with [[Command line|command]]: ''sndrec32''
[[image:FGCOM-W-sndrec.jpg|thumb|center|250px|Recording-test]]
*Start recording (click red point)
*talk some words into the mic
*stop (rectangel)
*spool back ( < < )
*listen  (>)
|width=300|
|}
Try to find the lowest possible microphone-volume for a reasonable speech-replay, without adjusting the loudness-volume from the above set values. If needed add the “booster” or “gain”. But it would be better if you do not need/use the booster, because that will always try to adjust to a recordable volume – even if there are only some background-noises which nobody really wants to hear.
<br><br>
'''5) Find the “best fit”'''
 
Now perform the following “-f910 Test" and make final adjustments if needed:
=====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.
In case one use the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|download_and_compile.sh script]] the "fgcom" has to be replaced by "sh ./run_fgcom.sh". Then type:
 
    $ fgcom -Sfgcom.flightgear.org.uk -f910     
 
<br>That will give the following output:
    fgcom - a communication radio based on VoIP with IAX/Asterisk
    (c)2007 by H. Wirtz <wirtz@dfn.de>
    Version 1.2.2 build 163M
    Using iaxclient library Version SVN 163M
   
    Successfully parsed commandline options.
    Reading list of airports...done.
    Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
    Call 0 accepted
    Call 0 answered
 
speak into the mic and your words will be echoed back with a short delay.
<br>Then type <nowiki>ctrl-C</nowiki> to exit this Quick-Test
 
<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#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).
*'''"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”)!
*No response '''"Call 0 accepted"''': Check your network, especially your firewall for open ports.
*If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].
 
====Functional Test + User Briefing====


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 flight-test-environment:
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 flight-test-environment:
=====Start the FGFS=====
====Start the FGFS====
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 386: Line 269:
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>
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>


=====Start the FGCom=====
====Start the FGCom====
Open a [[Command line|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”:
Open a [[Command line|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"
{|border="1"
Line 528: Line 411:
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. Have fun when using it.
 
=====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 you get no answers, see the chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].
 
You also could participate in "Multiplayer Events". Most of them use the FGCom possibilities in addition to the text-based FGFS-Menu "Network --> Chat" to enable communication also outside the FGCom. See the Flightgear-Forum http://www.flightgear.org/forums/ and there the "Multiplayer Events".
 
Last but not least you can, while flying, tune your Radio to the (Tower-) frequency 910.00. This should give you the same delayed response as in the -f910 test (see above). Do not forget to switch back - on that frequency you can only receive your own voice!!


<br>
===Using FGCom===
===Using FGCom===
There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]):
There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]):
Line 543: Line 420:
*Finally you can manipulate the frequency-tables (positions.txt in your FGFS/FGCOM local directory) and define an own frequency for special events. e.g. a Flight-School at one airport with maybe multiple student-groups. Of course those are local manipulations on your own PC, which you have to agree on with your (planned to be) partners in advance.
*Finally you can manipulate the frequency-tables (positions.txt in your FGFS/FGCOM local directory) and define an own frequency for special events. e.g. a Flight-School at one airport with maybe multiple student-groups. Of course those are local manipulations on your own PC, which you have to agree on with your (planned to be) partners in advance.


<br>
===Supplemantery Informations===
===Supplemantery Informations===
====Tips and Tricks====
====Tips and Tricks====
Line 749: Line 627:
Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''
Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''


==Server installation==
<br><br>
=='''Server installation'''==


For running a FGCOM server you need Asterisk and depending on the amount of users much bandwith and CPU power. Because of putting pilots and ATCs in a VoIP conference the server-admin has to assure that there is enough network and cpu power to avoid drop-outs of the voice stream.
For running a FGCOM server you need Asterisk and depending on the amount of users much bandwith and CPU power. Because of putting pilots and ATCs in a VoIP conference the server-admin has to assure that there is enough network and cpu power to avoid drop-outs of the voice stream.
Line 907: Line 786:
If you have problems you can contact me via email at "dcoredump AT gmail.com".
If you have problems you can contact me via email at "dcoredump AT gmail.com".


==External links==
<br><br>
=='''External links'''==
* [http://squonk.abacab.org/dokuwiki/fgcom Old Official website]
* [http://squonk.abacab.org/dokuwiki/fgcom Old Official website]
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]
* [http://sourceforge.net/projects/fgcom/ fgcom(SourceForge-Project)]
* [http://sourceforge.net/projects/fgcom/ fgcom(SourceForge-Project)]
<br><br>
==Development==
==Development==


TODO
TODO
<br><br>
=='''Status'''==
*'''March, 2009:'''
Adding User-Informations for installing, using, maintaining FGCOM on different platforms.
*'''18 November, 2008:'''
Latest SVN (rev 163) has the compile problems fixed. Also we have a '''new server: fgcom.flightgear.org.uk'''. User accounts not required (ie. do '''not''' use -U or -P)
*'''31 October, 2008:'''


==See also==
The latest SVN release at this time is the '''r149''' which does not compile due to a constant that is not defined (STL_STRING). Such constant appears at line 57 in the file ''src/fgcom_init.cpp'' which is:
''#include STL_STRING''
 
I guess that such constant must point to the STL library include file but I am not sure.
I revert to the '''r148''' SVN version which successfully compiles.
 
Command to get such version is: ''svn co -r148 svn://svn.dfn.de:/fgcom/trunk fgcom-r148''
 
* '''19 June, 2008:''' Currently the server is <u>down</u> due to hardware problems. It is unknown when the service comes back because he currently has no time to fix the problems.
 
* '''22 November 2007:''' Due to heavy development at this time there may be some differences between the information on the web pages and the installation. Please follow the discussions on the FlightGear development list!
 
<br><br>
=='''See also'''==
*[[FlightGear related projects]]
*[[FlightGear related projects]]


[[Category:Software]]
[[Category:Software]]
Jomo
652

edits

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

Navigation menu