internal: preamble downloads build and operation end
This wiki page tells you all about the latest - http://wiki.flightgear.org/index.php/FGCOM - built into the the FGFS app...
2016-11-17: FGCom has undergone a lot of evolution. When gitorious died, the source moved to sourceforge, along with all the other FlightGear source repositiories. I wanted to re-build it using MSVC14, so forked it to fgcom-fork, in the msvc140 branch, and since it seems SG/FG is ditching PLIB, included the PLIB Net module, as part of the source. A few fixes, and it compiled, and ran fine.
2013-10-12: FGCom has moved again. It is now part of the main FlightGear repository -
http://gitorious.org/fg/flightgear - and is built and installed as one of the utility components of FlightGear, like metar, terrasync, etc. That means it is included in the windows installer of flightgear. But more than that, now that fgcom functionality is also built into fgfs.exe, the need for this standalone version becomes less. Perhaps the only ongoing use of the standalone app is with OpenRadar.
2013-08-26: A lot of good things have happened to FGCom since 2012. In no particular order, some of them are :-
2012-06-11: Due to not having commit access to the original svn, a repository -
http://gitorious.org/fgcom - was started to house the updated source.
2011-07-26: The original source is still hosted on http://sourceforge.net/projects/fgcom/ , and I started with SVN version 260. Naturally you should check for a later svn command, but I used -
svn co https://fgcom.svn.sourceforge.net/svnroot/fgcom fgcom - to check out this now outdated original source. As usual I wanted to build it in WIN32, in this case using MSVC9.
Take care downloading and running executables from the web!
The prudent course is to always build your OWN from source.
Now that the source is well maintained in the Flightgear gitorious repository http://gitorious.org/fg/fgcom, and is easily downloaded using git - for Windows try msysgit - there only remains supplying binaries where possible.
Note, this the original source may no longer function with all current voip servers
|2011/07/11||fgcom-svn260.zip||4,200,028||Original SVN source||02c42712e1bab2ece0888faf1a42585d|
|2011/07/27||fgcom-msvc-01.zip||18,196||MSVC project files||92323b24cdd787e4d061eaf59f75490f|
Original source can be patched with fgcom-diff-01.txt
This is a copy of the README in the git source
This project can be build using CMake 2.8 or later See : http://www.cmake.org/ for download and install details.
OpenAL - sound libraries
PLIB - for network code plib net.lib and ul.lib
Building FGCOM in any system
1. Create an out of source 'build' directory
# mkdir build-fgcom
# cd build-fgcom
Windows MSVC users MUST copy config.h.msvc to that 'build' folder naming it config.h
# cmake /path/to/fgcom [-G <desired generator] \
Now depending on the generator chosen -
1: Unix/Linux Makefile, the standard unix mantra
# [sudo] make install
2: MSVC solutions files
(a) load the build files in the generators IDE, F7, to compile and link. INSTALL must be done separatley, or
(b) In command prompt
> cmake --build . --config Release
And if installation desired -
> cmake --build . --config Release --target INSTAll
> cmake -DBUILD_TYPE=Release -P cmake_install.cmake
3: cmake supports a considerable number of different generators. Run cmake --help to see the list supported on your platform.
To see the command line options run fgcom --help
Run fgcom binary with command -f910...
$ ./fgcom -f910
You should see...
Reading airports [/some/path/positions.txt]... loaded NNNNN entries.
Call 0 accepted
Call 0 answered
Speak 'one' into your microphone and you should hear an echoed 'one' from your speakers.
If the airports load fails, you may have to add -T/path/to/positions.txt
Ctrl+C to exit the application.
This is using the internal default voip server of fgcom.flightgear.org. If you want to connect to another server use -Sdelta384.server4you.de on the command line.
Running with FGFS:
This is only required with fgfs version 2.12 or less. fgfs 2.99 onwards has fgcom integrated. Use the Multiplayer -> FGCom setting dialog to configure fgcom. Normally the space-bar is the PTT button.
But with earlier fgfs versions...
1: Run fgfs with the added command -
This causes fgfs to output the information per the file <fgdata>/Protcol/fgcom.xml as udp data on port 16661. This includes your selected com and nav frequencies, your position, speed, callsign, altitude, etc - see the xml for details.
YOu can check the udp data stream with utilities like 'netcat'.
2: Run fgcom. There are command line options to change the port, the voip server etc. As stated above use --help to see all the options, but the default port is 16661 on localhost.
When you select a com frequency in fgfs, fgcom will see that selection, and establish a call to the chosen voip server, and you should hear other nearby pilots who are on speaking on that same frequency.
When you want to speak your intentions, like starting engine, taxing, taking off, arriving, landing, etc, press the PTT key (usually space bar), and talk clearly into your microphone, and you transmission will be relayed to other nearby pilots or any active ATC if that is the chosen frequency.
3: There is also a fgcomgui, that offers a graphical front end to using fgcom - see https://code.google.com/p/fgcomgui/
4: If you want to set up an ATC service at an airport of your choice, then the OpenRadar java app can also use fgcom for voice communications. See http://wiki.flightgear.org/OpenRadar
That's it folks ;=)) ENJOY!
20130825 - 20120615
And have FUN ;=))
EOP - fgcom.htm