FlightGear wiki

FGCOM Testing: Difference between revisions

Page Discussion

FGCOM Testing (view source)

Revision as of 18:38, 1 January 2015

2,886 bytes added ,  1 January 2015
no edit summary
No edit summary
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{obsolete|FGCom_3.0}}
{{historical
| type  = article
| tense  = is
| text  = obsolete
| reason = The new version of FGCom is much more simple to use, a clean documentation is available at [[FGCom_3.0]]
| talk  =
| date  = 1 January 2015
| nocat  =
}}
This "FGCOM_Testing" is intended to support FGCOM-users in debugging their FGCOM-System directly after installation, but also for those who want to verify the basic functionality or want to readjust the audio-system. It covers the following 4 areas in more detail:
This "FGCOM_Testing" is intended to support FGCOM-users in debugging their FGCOM-System directly after installation, but also for those who want to verify the basic functionality or want to readjust the audio-system. It covers the following 4 areas in more detail:
# Testing of the standalone FGCOM Installation
# Testing of the standalone FGCOM Installation
Line 12: Line 27:
Prior to executing the following [[Command line|command]] open a command-window and change into the directory, into which the FGCom was installed. This path will then be shown shown in the command window, followed by a "$"-sign. Enter the following "fgcom"-command with the required/wanted options:
Prior to executing the following [[Command line|command]] open a command-window and change into the directory, into which the FGCom was installed. This path will then be shown shown in the command window, followed by a "$"-sign. Enter the following "fgcom"-command with the required/wanted options:


<pre>fgcom -Sfgcom.flightgear.org.uk -f910</pre>
<pre>fgcom -Sfgcom.flightgear.org -f910</pre>


: ''fgcom''
<small><pre>
:: the command ''(in case you installed by using the [[Scripted Compilation on Linux Debian/Ubuntu|download_and_compile.sh script]] for LINUX-Systems you have to replace the command "fgcom" with "sh ./run_fgcom.sh". Then the complete command would be: "'''sh ./run_fgcom.sh -f910'''")''
For MAC you may use:
: ''-Sfgcom.flightgear.org.uk''
/Applications/FlightGear.app/Contents/MacOS/fgcom -Sfgcom01.flightgear.org -f910
:: the central server for FGCOM
</pre></small>
: ''-f910''
 
: '''fgcom'''
:: the command ''(in case you installed by using the [[Scripted Compilation on Linux Debian/Ubuntu|download_and_compile.sh script]] for LINUX-Systems you have to replace the command "fgcom" with: "sh ./run_fgcom.sh". Then the complete command would be: "'''sh ./run_fgcom.sh -f910'''")''
: '''-Sfgcom.flightgear.org'''
:: one of two FGCOM-servers! Since Oct.2012 there are 2 FGCOM-servers available:
::# The original: '''fgcom.flightgear.org'''
::# A new one: '''fgcom01.flightgear.org'''
::Due to technicalities it is not possible to speak from 1 server to the other - so try one and change if you notice that your friends are using the other.
 
::So insert the server-address after a "-S" (watch: The "S" must be a capital!):
: '''-f910'''
:: the only available frequency for echo-tests
:: the only available frequency for echo-tests
: optional
: '''optional'''
:: In case your audiosystem is rather weak, you may try the options:
:: In case your audiosystem is rather weak, you may try the options:
:: ''-i and/or -o'': i=input(microphone) o=output(Speaker), both values between 0.0 and 1.0 (e.g.: -i0.9)
:: ''-i and/or -o'': i=input(microphone) o=output(Speaker), both values between 0.0 and 1.0 (e.g.: -i0.9)
Line 35: Line 60:
  Successfully parsed commandline options.
  Successfully parsed commandline options.
  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
  Call 0 accepted
  Call 0 accepted
  Call 0 answered
  Call 0 answered
Line 64: Line 89:
     The System cannot find the given path.
     The System cannot find the given path.
    
    
     C:\Users\emmerich>fgcom.exe -Sfgcom.flightgear.org.uk -f910
     C:\Users\emmerich>fgcom.exe -Sfgcom.flightgear.org -f910
     The command "fgcom.exe" is either mistyped or could not be found.
     The command "fgcom.exe" is either mistyped or could not be found.
</pre>
</pre>
Line 86: Line 111:
Successfully parsed command-line options.
Successfully parsed command-line options.
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
</pre>
</pre>
after some time there may appear:
after some time there may appear:
Line 144: Line 169:
Successfully parsed commandline options.
Successfully parsed commandline options.
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
Call 0 accepted
Call 0 accepted
Call 0 answered
Call 0 answered
Line 241: Line 266:
* After starting the FGFS click onto “File” in the FGFS menu-bar, then onto “Sound Configuration”: Adjust the upper slide-control to a proper volume. Be aware that this setting will get lost when you exit via “X” - always exit via “File” → “Exit/Quit”.
* After starting the FGFS click onto “File” in the FGFS menu-bar, then onto “Sound Configuration”: Adjust the upper slide-control to a proper volume. Be aware that this setting will get lost when you exit via “X” - always exit via “File” → “Exit/Quit”.
* To the opposite you may adjust the volume of your FGCOM by changing the “-o” and/or “-i” options to values between 0 and 1 (see the [[#The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"|FGOM command at the beginning of this wiki-page]]).
* To the opposite you may adjust the volume of your FGCOM by changing the “-o” and/or “-i” options to values between 0 and 1 (see the [[#The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"|FGOM command at the beginning of this wiki-page]]).
</li><br /><li>It is known that the AirToAir frequency 123.45 does not yet work - reason unknown and fix-date unknown. (This affects all Operating Systems!)
</li><br /><li>If you believe you did everything right - but still you cannot establish a connection: Use MPchat to ask which FGCOM-server the other('s) are using! Since Oct.2012 there are 2 FGCOM-servers available:
</li><br /><li>Did you know? If no Tower-frequency is in range, you also can use the VOR-frequencies - just put them into your COM1 or COM2.
# The original: '''fgcom.flightgear.org'''
</li></ol><br />
# A new one: '''fgcom01.flightgear.org'''
Due to technicalities it is not possible to speak from 1 server to the other - so try one and change if you notice that your friends are using the other.
</li></ol>
Try to keep in mind: FGCOM is proven to work! So if there are problems look also for surrounding PC-features like unique hardware, software, etc.
Try to keep in mind: FGCOM is proven to work! So if there are problems look also for surrounding PC-features like unique hardware, software, etc.
<br /><br />
<br /><br />
Line 255: Line 282:
So know your standard settings and check if they have changed (without your written permission!)
So know your standard settings and check if they have changed (without your written permission!)
<br /><br />
<br /><br />
==== Special for Linux (.alsoftrc) ====
==== Linux ALSA Sound ====
(ref [[Linux software audio mixing with FlightGear]]) <br />
(Reference [[Linux software audio mixing with FlightGear]]) <br />
check your Home-directory (“~/”) for a file "'''.alsoftrc'''"
 
(remember that the “show hidden files” must be enabled!)
Check your Home-directory (“~/” or $HOME) for a file "'''.alsoftrc'''"
* if ".alsoftrc" does not exist
(Remember that the “show hidden files” must be enabled!)
** Check if there is a (old version) ".openalrc"
 
*** if yes: Check if you really use the old OpenAL library and not the newer OpenAL-soft library. If still have the old you put something like this in ".openalrc":
===== If using Creative Labs' OpenAL library (or older OpenAL version) =====
(define devices '(alsa))
Check if you are using the old Creative Labs OpenAL library (or old version) which uses the ".openalrc" configuration file. If so, you can put something like this within ".openalrc":
(define alsa-out-device "plug:dmix")
 
** if not, create a new ".alsoftrc" file and insert something like the following into it:
$HOME/.openalrc
format = AL_FORMAT_STEREO16
<pre>
cf_level = 1
(define devices '(alsa))
drivers = alsa
(define alsa-out-device "plug:dmix")
[alsa] # ALSA backend stuff
(device alsa-in-device "plug:dsnoop")
device = plug:dmix
</pre>
capture = plug:dsnoop
 
===== If using OpenAL Soft (or newer OpenAL version) =====
It is more likely users of more recent Linux distributions are using this newer OpenAL Soft package, instead of the previously mentioned older Create Labs' OpenAL.  (Hence, the likely rational for renaming the default configuration file to something other than the more common previous naming format.)
 
Copy either the be /etc/openal/alsoft.conf, /usr/share/doc/openal-1.15.1-r2/alsoftrc.sample.bz2, or create a new $HOME/.alsoftrc file and insert the following:
 
<pre><nowiki>
format = AL_FORMAT_STEREO16
cf_level = 1
drivers = alsa
[alsa]
device = plug:dmix
capture = plug:dsnoop
</nowiki></pre>
 
[NOTE: format is now "sample-type = uint16", and cf_level would appear not needed for typical users, or only desired for headphone users.]
 
The system wide OpenAL-soft configuration file may be /etc/openal/alsoft.conf or similar. It usually contains comments describing all possible configuration options.
The system wide OpenAL-soft configuration file may be /etc/openal/alsoft.conf or similar. It usually contains comments describing all possible configuration options.
<br /><br />
<br /><br />
===== Linux ALSA Audiophiles avoiding Dmix =====
For audiophiles using Linux ALSA and with their custom $HOME/.asoundrc file preventing DMix usage, make sure you have both specified "device = plug:dmix" as well as "capture = plug:dsnoop".  Per ALSA's page, "dsnoop is the equivalent of the dmix plugin, but for recording sound."  Without specifying using dsnoop for the capture device alongside your $HOME/.asoundrc file preventing DMix usage, you will likely only get silence played back when usage FGCom.  FGCom is not working at this point, as the sound device is likely still locked by your $HOME/.asoundrc file and only recording silence or playing back silence during the echo test!
===== Using ALSA Custom "plug:" Filters =====
The OpenAL Soft (or the newer version of OpenAL) $HOME/.alsoftrc file also accepts using other $HOME/.asoundrc "plug:" incanatations, such as sections containing Dmix - alsa.opensrc.org's "pcm.dmixs51" customization for using DMix with 5.1 Surround Sound, and called as:
<pre>$ aplay -D "plug:dmixs51" Some_PCM_WAV_File.wav </pre>
$HOME/.alsoftrc
<pre>
"device = plug:dmixs51"
</pre>
Just remember to also uncomment layout_surround51, and note the likely fact FlightGear is still only using Stereo sound (or two channel audio) and is only set here for an example!
==== USB-Headsets-Problems with Linux (Ubuntu) ====
==== USB-Headsets-Problems with Linux (Ubuntu) ====
The following is based/verified on Ubuntu, but should be similar on other distributions:
The following is based/verified on Ubuntu, but should be similar on other distributions:
F-JJTH
577

edits

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