FlightGear wiki

FGCom (before 3.0): Difference between revisions

Page Discussion

FGCom (before 3.0) (view source)

Revision as of 06:03, 9 April 2009

1,674 bytes added ,  9 April 2009
→‎The Client installation: add basic rules for usage
(→‎The Client installation: add basic rules for usage)
Line 557: Line 557:
  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 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!
|That means: at about 50KM we are getting out of range '''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).
Line 568: Line 568:
<br>--[[User:Jomo|Jomo]] 04:20, 18 March 2009 (EDT)
<br>--[[User:Jomo|Jomo]] 04:20, 18 March 2009 (EDT)


===Solving Audio-Problems===
The following assumes that you have problems even after you did set up your system as described in [[Verifying your Audio-System]].<br><br>
'''Poor Audio Quality'''
*Check especially your microphone-cables for a good quality shielding and root them as far away as possible from electromagnetic noise emitters (motors, blowers, AC-cabling, lamps, etc.).
*It even may help to place your sound-card into a different slot
*A (digital) USB-headset helps in avoiding noise and feedback problems
'''Background noise raising with time'''<br>
This is typical for an active automatic “Boost”, “Gain”, or “Amplifier” device, or a microphone set too sensible. i.e. while there is no “real sound” the devices will try to “boost” the “background noise” to a real sound level – and that may hurt your ears.
*'''Basically:''' Do not keep the PTT pushed longer than absolutely necessary,  before and after speaking!<br>
*Try to say something and the sound-system should adjust to that – but the problem will reappear after a short while. '''You should always switch off your microphone if you are not really talking – and keep the microphone level as low as possible!'''
*If anyhow possible, do not use automatic boosters. If your microphone does  need such a support, keep it to a minimum. Especially in the FGCom application the microphone output needs less power because the central server does equalize the loudness of all users.


'''Unexpected behavior'''<br>
Especially “high quality” sound-cards may get you into trouble, because e.g.:
*they may monitor how long the microphone was not used and switch it off after some timespan (without you noticing it)
*during reboot or restart they may initiate with values out of a special profile instead of reusing the “last used” values
*or they may set some slide controls to “0” (especially microphone sliders)
*some do switch the microphone only after pushing '''and''' releasing the space-bar – while we want to change the microphone-status only while the space-bar is pushed down! (This may not affect a PTT asigned to a joystick)<br>
So know your standard settings and check if they have changed (without your written permission!)<br><br>
'''Special for Linux'''
(ref [[Linux software audio mixing with FlightGear]]) <br>
check your Home-directory (“~/”) for a file "'''.alsoftrc'''"
(remember that the “show hidden files” must be enabled!)
*if ".alsoftrc" does not exist
**Check if there is a (old version) ".openalrc"
***if yes: rename that to ".alsoftrc"
***if not crate a new  ".alsoftrc"
*If not already done so insert into the file “.alsoftrc” the following :
(define devices '(alsa))
(define alsa-out-device "plug:dmix")


===Using FGCom===
===Using FGCom===
ToBeDefined
There are basically 3 types of FGCOM-usage: (compare the introduction to this wiki-page):
*'''Normal usage at airports:''' i.e. You set up your radio as usuall. Thus you are set up for the usual ATC-(keyboard)-procedures (either thru the "'" (UpperCase#) and/or the Chat-Menus. In addition you then can talk to anybody in a radius of about 50 km (about 30 miles) around the airport, may that be friends, a maintained FGCOM-ATC/Twr-Operator, airport utilities, etc.. Be aware that as of April 2009 only very few planes are using the FGCOM for ATC-purposes - thus you should always use the ATC-Chat "keyboard"-procedures to announce arrivals/departures/taxiing etc. in addition. (We hope that may change in some future!)<br><br>
*The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - but not yet "overcrowded!). Also when traveling you might want to listen on the 122.75 for others who want to contact you (or reverse). When there is much "talk" on the 122.75 you might just arrange with your partner to switch to 123.45 - and return to 122.75 afterward. As of April 2009 the 122.75 is already operational for this application (except for Windows-PC's, sorry), the 123.45 will follow. You may try from time to time if these limitations still exist.<br><br>
*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.
====Tips and Tricks====
====Tips and Tricks====
'''Airport missing in FGCom:'''<br>
'''Airport missing in FGCom:'''<br>
Line 675: Line 649:
**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.
===Solving Audio-Problems===
The following assumes that you have problems even after you did set up your system as described in [[Verifying your Audio-System]].<br><br>
'''Poor Audio Quality'''
*Check especially your microphone-cables for a good quality shielding and root them as far away as possible from electromagnetic noise emitters (motors, blowers, AC-cabling, lamps, etc.).
*It even may help to place your sound-card into a different slot
*A (digital) USB-headset helps in avoiding noise and feedback problems
'''Background noise raising with time'''<br>
This is typical for an active automatic “Boost”, “Gain”, or “Amplifier” device, or a microphone set too sensible. i.e. while there is no “real sound” the devices will try to “boost” the “background noise” to a real sound level – and that may hurt your ears.
*'''Basically:''' Do not keep the PTT pushed longer than absolutely necessary,  before and after speaking!<br>
*Try to say something and the sound-system should adjust to that – but the problem will reappear after a short while. '''You should always switch off your microphone if you are not really talking – and keep the microphone level as low as possible!'''
*If anyhow possible, do not use automatic boosters. If your microphone does  need such a support, keep it to a minimum. Especially in the FGCom application the microphone output needs less power because the central server does equalize the loudness of all users.
'''Unexpected behavior'''<br>
Especially “high quality” sound-cards may get you into trouble, because e.g.:
*they may monitor how long the microphone was not used and switch it off after some timespan (without you noticing it)
*during reboot or restart they may initiate with values out of a special profile instead of reusing the “last used” values
*or they may set some slide controls to “0” (especially microphone sliders)
*some do switch the microphone only after pushing '''and''' releasing the space-bar – while we want to change the microphone-status only while the space-bar is pushed down! (This may not affect a PTT asigned to a joystick)<br>
So know your standard settings and check if they have changed (without your written permission!)<br><br>
'''Special for Linux'''
(ref [[Linux software audio mixing with FlightGear]]) <br>
check your Home-directory (“~/”) for a file "'''.alsoftrc'''"
(remember that the “show hidden files” must be enabled!)
*if ".alsoftrc" does not exist
**Check if there is a (old version) ".openalrc"
***if yes: rename that to ".alsoftrc"
***if not crate a new  ".alsoftrc"
*If not already done so insert into the file “.alsoftrc” the following :
(define devices '(alsa))
(define alsa-out-device "plug:dmix")


===Supplemantery Informations===
===Supplemantery Informations===
Jomo
652

edits

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