652
edits
FGCom (before 3.0): Difference between revisions
Jump to navigation
Jump to search
m
→Testing: minor typos, wording, refferences
m (→Installing FGCom: minor typos + remove author) |
m (→Testing: minor typos, wording, refferences) |
||
| Line 148: | Line 148: | ||
''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 [[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! | ||
<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 179: | Line 179: | ||
|width=300|Enter [[Command line|command]]: ''gnome-sound-properties'' | |width=300|Enter [[Command line|command]]: ''gnome-sound-properties'' | ||
[[image:FGCOM-U-Prefs.jpg|thumb|center|250px|test devices]] | [[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 | 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: | |width=300|Click right onto the audio-icon → Preferences → Audio-tab: | ||
[[image:FGCOM-W-Audio.jpg|thumb|center|250px|set devices]] | [[image:FGCOM-W-Audio.jpg|thumb|center|250px|set devices]] | ||
| Line 187: | Line 185: | ||
|width=300| | |width=300| | ||
|} | |} | ||
If you did change these device-settings, it is a good idea to reboot the | 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> | <br><br> | ||
'''3) Adjust volume-control''' (for theses first adjustments you should switch the Mic. | '''3) Adjust volume-control''' (for theses first adjustments you should switch off the Mic.!) | ||
{| align=center width=900 border="1" | {| align=center width=900 border="1" | ||
|- | |- | ||
|width=300|Click right on Audio-Icon → Open Vol. Ctrl: | |width=300|Click right on Audio-Icon → Open Vol. Ctrl: | ||
[[image:FGCOM-UVolCtrl.jpg|thumb|center|250px|Volume Control]] | [[image:FGCOM-UVolCtrl.jpg|thumb|center|250px|Volume Control]] | ||
The amount of the slider-controls | 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”. | The “booster” is available under “Switches”. | ||
| Line 232: | Line 230: | ||
Now perform the following “-f910 Test" and make final adjustments if needed: | Now perform the following “-f910 Test" and make final adjustments if needed: | ||
=====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. | ||
| Line 263: | Line 258: | ||
*No response '''"Call 0 accepted"''': Check your network, especially your firewall for open ports. | *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]]. | *If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]]. | ||
====Functional Test + User Briefing==== | ====Functional Test + User Briefing==== | ||
| Line 272: | Line 266: | ||
If you don't have an Icon available to start the FGrun, then | If you don't have an Icon available to start the FGrun, then | ||
*use a [[ | *use a [[Command line|command-window]] | ||
*change into the directory in which FGFS was installed | *change into the directory in which FGFS was installed | ||
*and start the program from there: | *and start the program from there: | ||
| Line 292: | Line 286: | ||
'''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> | ||
→ Click “Next”<br><br> | → Click “Next”<br><br> | ||
'''3)''' Define the '''Multiplayer options:''' ( | '''3)''' Define the '''Multiplayer options:''' (ref. wiki [[Howto: Multiplayer]] for details) | ||
{| | {| | ||
|+ | |+ | ||
| Line 299: | Line 293: | ||
|“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 | ||
<br><br>type “mpserverXX.flightgear.org” into the field “Hostname:”, replace “XX” with the | <br><br>type “mpserverXX.flightgear.org” into the field “Hostname:”, replace “XX” with the server number nearest you - select it in http://pigeond.net/flightgear/mpstatus/. Actually it does not matter which server you take (as long as it is online) - you might try which server gives you the best response-times. | ||
<br><br>Insert your “Callsign:” (max. 7 characters) | <br><br>Insert your “Callsign:” (max. 7 characters) | ||
<br><br>define the “in” and “out” ports both with the standard “5000” | <br><br>define the “in” and “out” ports both with the standard “5000” | ||
<br><br>With "Load/Save as" you may build up yourself library of settings for different airports. | <br><br>With "Load/Save as" you may build up yourself a library of settings for different airports. | ||
|}→ Click “Advanced”<br> | |}→ Click “Advanced”<br> | ||
'''4)''' In the “'''Advanced Options'''” check the following sections (click/select them in the left column): | '''4)''' In the “'''Advanced Options'''” check the following sections (click/select them in the left column): | ||
| Line 341: | Line 335: | ||
<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 | If you need to '''define the unique IP-Address''', open a [[Command line|command-window]] and type | ||
{|border="1" | {|border="1" | ||
|+ | |+ | ||
| Line 414: | Line 408: | ||
|} | |} | ||
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 [[ | 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 431: | Line 424: | ||
||for Mac: || || | ||for Mac: || || | ||
|} | |} | ||
The response should be: | For the following test position this command-window somewhere, where you can monitor it throughout the test. | ||
The first response should be: | |||
/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> | ||
| Line 440: | Line 435: | ||
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 [[FGCOM#Test the basic function]] | If your printout up to that line is different go back to chapter [[FGCOM#Test the basic function|Test the basic function]] | ||
{| | {| | ||
| Line 449: | Line 442: | ||
|width="300"| || | |width="300"| || | ||
|- | |- | ||
|1) If COM1 was set to 119.650 you will see the following 2 lines added to the initialization of the FGCom-window: || | |1) 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 initialization of the FGCom-window: || | ||
|- | |- | ||
| | | | ||
| Line 457: | Line 450: | ||
Instead of “119.650” there will be shown the last used frequency. In this case the source of the nearest ATC-Freq. 119.650 is more than 50km away from your actual position of the airplane, so FGCom rejects a connection to it. If the last frequency used would have been within 50 km you get an indication very similar to the next item. | Instead of “119.650” there will be shown the last used frequency. In this case the source of the nearest ATC-Freq. 119.650 is more than 50km away from your actual position of the airplane, so FGCom rejects a connection to it. If the last frequency used would have been within 50 km you get an indication very similar to the next item. | ||
|- | |- | ||
|2) Switch COM1 to | |2) Switch COM1 to 118.60 (needed at Palo Alto): | ||
|- | |- | ||
| | | | ||
| Line 477: | Line 470: | ||
|Only in between “SPEAK” and “LISTEN” you are able to talk to others. | |Only in between “SPEAK” and “LISTEN” you are able to talk to others. | ||
|- | |- | ||
|<br>Now lets set the other Radios: | |<br>Now lets set/verify the other Radios: | ||
*COM2 = 120.50 San Francisco | *COM2 = 120.50 San Francisco | ||
*NAV1 = 114.10 San Jose | *NAV1 = 114.10 San Jose | ||
*NAV2 = 115.80 San Francisco | *NAV2 = 115.80 San Francisco | ||
4) Pressing Upper+Space will | 4) Pressing Upper+Space will switch to the next radio: '''NAV1''' | ||
|- | |- | ||
| | | | ||
| Line 554: | Line 547: | ||
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 | |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! | ||
|} | |} | ||
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). | ||
| Line 560: | Line 553: | ||
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. | ||
=====Final 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 you get no answers, see the chapter | 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". | |||
===Using FGCom=== | ===Using FGCom=== | ||