FlightGear wiki - User contributions [en]

User:Natovr

2012-06-23T16:19:46Z

Natovr: Blanked the page

User talk:Natovr

2012-06-23T16:19:14Z

Natovr: Blanked the page

FGCom (before 3.0)

2009-11-08T01:08:10Z

Natovr: /* Start the FGCom */ Once again..

'''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''' on http://www.flightgear.org/forums/):
**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.
*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
*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.
You can even use it in models without radios - just use the standard FlightGear menu --> Equipment --> Radio Settings. 

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.

 
=='''The Client installation'''==
===Prequisites===
====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 FGFS command-window.

For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html

Of course you will also need a connection to the Internet for this real-time, worldwide voice communication.

 
====Software Requirements====
{| 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" |'''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 (until now per keyboard - now also with this vocal interface: FGCom).
|}
 
====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" |'''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" |'''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
|}
 
===Installing FGCom===
====Install on Linux====
For Linux-Systems there are 3 ways to install:

'''1) Downloading from the “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).'''
*'''Advantage:''' This is the easiest way and ensures that maintenance and services for this package and all concurrencies to it are provided automatically for a reasonable time-frame.
*'''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.
 
'''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.
*'''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
 
'''3) Compiling it locally'''
*'''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.
*'''Disadvantage:''' No automated maintenance available. Also the user should have some basic knowledge of his system and it's devices.
*'''Installation:'''
<ol><li>
Fetch FGCom (a copy of a working iaxclient is inside) from 
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom
 
</li> <li>
Optional: edit iaxclient/lib/Makefile
::{| style="width:80%" border="2"
|+
|-
||USE_PA_OSS=0||Set to "1" to use the oss emulation
|-
||USE_PA_ALSA=0||Set to "1" to use portaudio alsa (WARNING: only if your card natively supports 8000Hz sample rate)
|-
||USE_PA_JACK=0||Set to "1" to use
|-
||AUDIO_ALSA=0||Set to "1" to use native alsa (WARNING: PTT won't work)
|-
||AUDIO_OPENAL=1||'''Set to "0"''' if you do not want to use OpenAl ('''as recommended and set as default for now'''. Note however, that it requires OpenAl with capture support.)
|-
|}
</li> <li>
Edit fgcom/src/Makefile and check the pathes for PLIB_PREFIX and OPENAL_PREFIX.
</li> <li>
Compile iaxclient and fgcom. To do so, do the following:
cd fgcom/src && make
</li> <li>
Install
make install
</li> <li>
continue with chapter [[FGCOM#Test the basic function|testing the basic functions]]
</li></ol>

 
====Install on Windows====
Please use the Windows-Installation description on http://wiki.flightgear.org/index.php/FGCOM_for_Windows

 
====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.

But '''you do need OS X 10.5''' as prerequisite. With lower versions you will end up with a generic "bus error" message!

 
===Testing===
During testing
#we will test the basic FGCOM-functions without the FGFS
#after that we test the FGCOM together with the FGFS
#finally we test/adjust the Microphone and Loudspeaker system

For these tests please see the [[FGCOM_Testing|FGCOM_Testing]]

 
===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:
====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:

If you don't have an Icon available to start the FGrun, then
*use a [[Command line|command-window]]
*change into the directory in which FGFS was installed
*and start the program from there:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs sh ./run_fgrun.sh
|-
||for Std. Linux e.g.: ||fgrun
|-
||for Windows e.g.: ||D: cd 'C:\Program Files\Flightgear\win32' fgrun.exe
|-
||for Mac: || ||
|}
Wait for the Program-Window to start and then define: 
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]] 
→ Click “Next” 
'''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. 
→ Click “Next” 
'''3)''' Define the '''Multiplayer options:''' (ref. wiki [[Howto: Multiplayer]] for details)
{|
|+
|-
|width=610|[[image:FGrun_base.jpg|thumb|left|600px|Basic + Multiplayer Options]]
|“AI models” must be activated in order to see all traffic
 “Multiplayer” must be activated
 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.
 Insert your “Callsign:” (max. 7 characters)
 define the “in” and “out” ports both with the standard “5000”
 With "Load/Save as" you may build up yourself a library of settings for different airports.
|}→ Click “Advanced” 
'''4)''' In the “'''Advanced Options'''” check the following sections (click/select them in the left column):
#General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
#Features: “AI Traffic” should be activated already
#Initial Position:
{|
|+
|-
|width=420|[[image:FGrun_IP.jpg|thumb|left|400px|Advanced: Initial Position]]
|
You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''
 ''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.
|}
Open http://mpmap01.flightgear.org
{|
|+
|-
|width=510|[[image:MPmap.jpg|thumb|left|500px|Preflight]]
|
*if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
*click on “nav”
*disable all options except “apt code”
*type “KPAO” into the filed “Navaids lookup”
*hit ENTER or click onto the reading-glass symbol
*click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”
*now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”
*then zoom into the airport
*set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen
*type those long/lat values into the field below and also the wanted heading of the plane while parking
|}
'''5) Network:'''
{|
|+
|-
|width=420|[[image:FGrun_net.jpg|thumb|left|400px|Preflight]]
|Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.
 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 a [[Command line|command-window]] and type
{|border="1"
|+
|width="100"|OS
|width="75"|'''to type'''
|width="40"|Cap. ||returned values
|-
||for linux: ||ifconfig ||eth0 ||
Link encap:Ethernet HWaddr 00:1d:92:80:a6:ab
 inet addr:'''192.168.178.23''' Bcast:192.168.178.255 Mask:255.255.255.0
|-
||for Windows: ||ipconfig /all ||et ||
Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF
 DHCP aktiviert. . . . . . . . . . : Ja
 Autokonfiguration aktiviert . . . : Ja
 IP-Adresse. . . . . . . . . . . . : '''192.168.178.20'''
 Subnetzmaske. . . . . . . . . . . : 255.255.255.0
 IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
|-
||for Mac: || || ||
|}
The '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!!

'''6) Input/Output:'''
{|
|+
|-
|width=420|[[image:FGrun_IO.jpg|thumb|left|400px|Preflight]]
|You do need a "generic" line as shown, because '''this defines the interface between FGFS and FGCom'''.
 
To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown. 
Editing an existing line: Start by clicking onto the existing one, then change as required. 
Deleting an existing Line: Click onto the line to be deleted, then hit "Delete"

|}

'''7) Avionics:''' let's define:
{|
|+
|-
|width="50"|
|width="60"|Nav1:
|width="100"|114.10 ||San Jose VOR
|-
| ||Nav2: || 115.80 ||SF VOR
|-
| ||ADF: || 379 || Brijj, beacon at SF
|}
and activate: DME to Nav1 
There is no field to input COM-radios, but remember them for setting them later manually:
{|
|+
|-
|width="50"|
|width="60" |Com1
|width="100" |118.60 ||Paolo Alto
|-
| ||Com2 || 120.50 || San Francisco
|}

'''8) Properties:'''
Here you can define any presetting for any values in the FGFS. see e.g.: FGFS-menu-bar --> File --> “Browse Internal Properties”
{|
|+
|-
|width=520|[[image:FGrun_prop.jpg|thumb|left|500px|Preflight]]
|
e.g. I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
 Input a new line: Just hit “New” and type your string.
 Edit a line: Be sure first to click onto an existing item and then edit this “Property”
 Delete a line: Click onto the line to be deleted then hit "Delete"
|}
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. 

====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”:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs sh ./run_fgcom.sh
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Windows e.g.: ||cd 'C:\Program Files\Flightgear\win32' fgcom.exe -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Mac: || ||
|}
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
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 206M
Using iaxclient library Version SVN 206M

Successfully parsed command-line options.
Reading list of airports...done.
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|Test the basic function]]

{|
|+
|-
|width="300"| ||
|-
|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: ||
|-
|
Selected frequency: 119.650
Call rejected by remote
|
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 118.60 (needed at Palo Alto):
|-
|
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
|This last line will be repeated according the to time span you defined in the “Input/Output” command “--generic=socket,in,'''10''',,5500,tcp”, you may change that value later according to your preferences.
|-
| 3) Press your PTT (PushToTalk on space-bar and joystick, as available):
|-
|
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.
|-
| Now lets set/verify the other Radios:
*COM2 = 120.50 San Francisco
*NAV1 = 114.10 San Jose
*NAV2 = 115.80 San Francisco
4) Pressing Upper+Space will switch to the next radio: '''NAV1'''
|-
|
Radio-Select: NAV1
Selected frequency: 114.100
Hanging up call 0
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|Compare this to the NAV2 indication 2 steps later: something is wrong – and it wasn't your fault: Although this NAV is valid (see ...FGFS/data/Airports/apt.dat.gz), it is missing in the FGCom listing .../FGCom/positions.txt. I encountered this problem several times, as well for Airports as also for VOR's. If this happens with your most beloved airport you can add those missing data with a text-editor. But before changing be sure to save the original data somewhere - just in case!
|-
| 5) Pressing Upper+Space once more switches to '''COM2'''
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km)
[LISTEN] mute mic, unmute speaker
Call 0 accepted
Call 0 answered
|That looks OK: San Francisco is about 29 km away watch the “km” instead of miles! '''10 km''' = '''6.2137 mi'''
|-
| 6) Pressing Upper+Space once more switches to '''NAV2'''
|-
|
Radio-Select: NAV2
Selected frequency: 115.800
Hanging up call 0
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|And Yes: The SF VOR is just a little closer than the airport(center)
|-
| 7) Pressing Upper+Space once more brings back '''COM1''':
|-
|
Radio-Select: COM1
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|-
| 8) Lets us start and continue flying in the direction about 130°:
|-
|
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km)
|notice that you first come closer (to the center of the airport) and after that getting away
|-
| 9) Let's switch to '''COM2''' (San Francisco) and watch:
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km)
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km)
..
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km)
Hanging up call 0
Radio-Select: NAV2
Selected frequency: 115.800
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|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).
 
If you got here without any (technical) problems your FGCom is fully functional. Have fun when using it.

 

===Using FGCom===
There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]):
*'''Normal usage at airports:''' i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through 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!) 
*The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - and 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, the 123.45 will follow soon. You may try from time to time if this limitations still exist. 
*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.

 
===Supplemantery Informations===
====Tips and Tricks====
<ol>
=====Airport missing in FGCom:=====
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line
KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
You can add extra lines for any locations you want. e.g.: (watch the separation comas)
apt-code = DUMY (a "dummy" or your favorite, but missing, airport code)
KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz”
or just take one of which you are sure that you do not need it in the FGFS-reality
(notice that several Airports (far apart) use same frequencies!
long/lat = take out of the Mpmap (or Google Map)
type = whatever
name = whatever
''(of course those definition are only known to your own PC and last only until the next data update!)''
 
=====Editing FGCOM-Data-Files=====
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
*For windows you can use "WordPad"
*For Linux the "gedit" works fine
 
=====Copying-Printing this WIKI-Page'''=====
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
*goto this page: ( http://wiki.flightgear.org/index.php/FGCOM )
*to copy:
**select in the Browser-Menu: "File" --> "Save Page as.. "
*to print:
**select the last entry in the sidebar on the left: "Printable version"
**Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"
**before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages!
**If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer


 
=====Joystick compatibility between Operating Systems:=====
ref also: [[Joystick]] 
You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"):
<axis> (instead of the usual <axis n=”3”> )
<desc>Mixture</desc>
<number>
<unix>3</unix>
<mac>5</mac>
<windows>5</windows>
</number>
<binding>
<command>nasal</command>
<script>controls.mixtureAxis()</script>
</binding>
</axis>

 
=====assign PTT to Joystick and PTT=====
If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)
<button n="x">
<desc>PTT - Push To Talk</desc>
<binding>
<command>nasal</command>
<script>controls.ptt(1)</script>
</binding>
<mod-up>
<binding>
<command>nasal</command>
<script>controls.ptt(0)</script>
</binding>
</mod-up>
</button>

====Helpfull INTERNET Adresses====
'''World-Time:'''
*for standard deviations:http://www.timeanddate.com/worldclock/custom.html?sort=1
*for direct conversions: http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Especially for multiplayer events you should define all times in the internationally used GMT (Greenwich Meantime). Just pick up your deviation from GMT and memorize it. If everybody does it, we could avoid a lot of misunderstandings. 
'''Decimal to Degree''' http://www.hbnweb.de/mathematik/grad-dezimal.html 
Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it. 
'''Miles, km, feet, etc. etc. ...''': http://www.convertunits.com/
 If like to avoid troubles (like e.g. NASA lost a satellite because of it) just look it up.

'''Ports needed''' 
In case of problems over the INTERNET you might check that the the following ports are allowed:
1314 TCP if the Festival-Server is used for Text/Sound
2005 UDP Vcp-Stream
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer (VPN Sftw.)
5001 UDP Enable HTTP-server
5002 UDP Enable property server
5003 UDP Enable Screen-Shot services
5004 UDP (may be used as a spare)
5505 UDP Terra Sync
16661 UDP FGCom listening to FGFS, usually “local host” only
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).

====Commandline Parameters====
fgcom --help
returns the following useful info
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

OPTION DESCRIPTION

-d, -debug, --debug= show debugging information
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')
-s, -fgserver, --fgserver= network device to connect to (default: 'localhost')
-p, -port, --port= where we should listen to FG (default: '16661')
-a, -airport, --airport= airport-id (ICAO) for ATC-mode
-f, -frequency, --frequency= frequency for ATC-mode
-U, -user, --user= username for VoIP account (default: 'guest')
-P, -password, --password= password for VoIP account (default: 'guest')
-i, -mic, --mic= mic input level (0.0 - 1.0)
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)
-b, -mic-boost, --mic-boost= enable mic boost
-l, -list-audio, --list-audio= list audio devices
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')

Available codecs:
u - ulaw (default and best codec because the mixing is based onto ulaw)
a - alaw
g - gsm
s - speex
7 - G.723

Mode 1: client for COM1 of flightgear:
$ fgcom
- connects fgcom to fgfs at localhost:16661
$ fgcom -sother.host.tld -p23456
- connects fgcom to fgfs at other.host.tld:23456

Mode 2: client for an ATC at <airport> on <frequency>:
$ fgcom -aKSFO -f120.500
- sets up fgcom for an ATC radio at KSFO 120.500 MHz

Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!

Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''

 

=='''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.

===Prerequirements===

Install Asterisk on top of your favorite distribution. Please refer to installation manuals (e.g. [[http://www.asteriskguru.com/|Asterisk-Guru]]) you can find on the net. You do not need H.323 or SIP because the fgcom client uses IAX2 as VoIP signaling protocol. Only if you think about connecting external VoIP applications to FGCOM you should consider to activate H.323 or SIP (but this is not the scope of this small howto).

Notice: You need to install the zaptel driver modules - even if you won't use any hardware for telecom interfacing. You need the ztdummy kernel module for the asterisk conference application MeetMe() because it simulates a hardware clock needed by this application. Further development of FGCOM might use app_conference which don't needs any timing device.

For now we want to use /etc/asterisk as the base configuration directory.

===Setting up the radio frequencies===

The radio frequencies are "simple" Conferences and realized due to the Asterisk application MeetMe().

====Part 1: General configuration====

First you have to set up the general configuration of the system. Put the following at the top of your "extensions.conf" file:

[general]
static=yes
writeprotect=yes
;
[globals]
;
[macro-com]
exten => s,1,Answer()
exten => s,n,MeetMe(${MACRO_EXTEN},qd)
exten => s,n,Hangup()
;
[macro-echo]
exten => s,1,Answer()
exten => s,n,Echo()
exten => s,n,Hangup()
;
[guest]
; ATC-Help
exten => 01-ZZZZ-911.000,1,Macro(com)
exten => 012525252591100,1,Dial(Local/01-ZZZZ-911.000)
exten => 01-ZZZZ-910.000,1,Macro(echo)
exten => 012525252591000,1,Dial(Local/01-ZZZZ-910.000)
;
[default]
include => guest
;
; Code:
; 01 - FlightGear
; 02 - Microsoft Flight-Simulator
; 03 - ...
;
; Air2Air
exten => 01-ZZZZ-123.450,1,Macro(com)
exten => 012525252512345,1,Dial(Local/01-ZZZZ-123.450)
exten => 01-ZZZZ-122.750,1,Macro(com)
exten => 012525252512275,1,Dial(Local/01-ZZZZ-122.750)

====Part 2: Adding your favorite (all?) frequencies====

For this you have simply to create an extension for every touple of airport/frequency in extensions.conf. The following is an example for Berlin-Tempelhof (EDDI). The information comes from the file "apt.dat.gz" of your FlightGear installation.

; EDDI ATIS 126.020 - Berlin Tempelhof
exten => 01-EDDI-126.020,1,Macro(com)
exten => 010403030812602,1,Dial(Local/01-EDDI-126.020)
;
; EDDI BERLIN DEP 120.620 - Berlin Tempelhof
exten => 01-EDDI-120.620,1,Macro(com)
exten => 010403030812062,1,Dial(Local/01-EDDI-120.620)
;
; EDDI BERLIN DIRECTOR 121.120 - Berlin Tempelhof
exten => 01-EDDI-121.120,1,Macro(com)
exten => 010403030812112,1,Dial(Local/01-EDDI-121.120)
;
; EDDI BERLIN ARR 126.420 - Berlin Tempelhof
exten => 01-EDDI-126.420,1,Macro(com)
exten => 010403030812642,1,Dial(Local/01-EDDI-126.420)
;
; EDDI GND 121.950 - Berlin Tempelhof
exten => 01-EDDI-121.950,1,Macro(com)
exten => 010403030812195,1,Dial(Local/01-EDDI-121.950)
;
; EDDI TWR 119.570 - Berlin Tempelhof
exten => 01-EDDI-119.570,1,Macro(com)
exten => 010403030811957,1,Dial(Local/01-EDDI-119.570)
;
; EDDI BERLIN DIRECTOR 136.100 - Berlin Tempelhof
exten => 01-EDDI-136.100,1,Macro(com)
exten => 010403030813610,1,Dial(Local/01-EDDI-136.100)
;
; EDDI TWR 118.100 - Berlin Tempelhof
exten => 01-EDDI-118.100,1,Macro(com)
exten => 010403030811810,1,Dial(Local/01-EDDI-118.100)
;
; EDDI BERLIN DEP 119.500 - Berlin Tempelhof
exten => 01-EDDI-119.500,1,Macro(com)
exten => 010403030811950,1,Dial(Local/01-EDDI-119.500)
;
; EDDI BERLIN ARR 119.620 - Berlin Tempelhof
exten => 01-EDDI-119.620,1,Macro(com)
exten => 010403030811962,1,Dial(Local/01-EDDI-119.620)

What does the above mean? There are two lines (three with the comment) for each frequency: The first one sets up an extension named "01-EDDI-119.500". Yes, for VoIP you can use textual extensions but be careful if you want to setup your Asterisk-Server with POTS (=Plain old telephone service). Therefor you need the second line which is the same as above but without dashes and the letters in the decimal representation of the ASCII Code. The second line does only a "rewrite" of the numerical representation to the textual one.

For setting up all airports you can write your own simple script. But this maybe also not needed in further versions of FGCOM.

After editing the extensions.conf file you have to reload the extensions file (e.g. "asterisk -rx extensions reload").

You can add further nice goodies to your extensions.conf: MorseCode() for morsing the code of the VOR (MorseCode() will only work in Asterisk >= 1.4), Recording of metar data and playing this recording back when using the frequency of the metar information, ...

===Setting up user accounts===

The user accounts are located in the file iax.conf (and perhaps also in sip.conf, but this is not necessary). The top of the file should look like this:

[general]
bandwith=low
disallow=lpc10
jitterbuffer=yes
forcejitterbuffer=no
tos=lowdelay
autokill=yes
disallow=all
allow=alaw
allow=gsm
allow=ilbc
allow=g726
allow=ulaw
language=en
maxauthreq=10
context=guest
;
[guest]
type=user
username=guest
context=guest
qualify=yes
callerid=Guest IAX User
host=dynamic
;

You may want to disallow more codecs or want to allow additional codecs (such as speex). But have in mind that the internal mixing of the conferences are done in "ulaw". But "ulaw" needs about 80 kBit/s because it does no compression. So you have to think about what's better for you: less bandwidth (per user) and more CPU usage or more bandwidth (per user) and less CPU usage... you should also consider the "sound" of some codecs may not have the 'real radio sound'.

For each user you have to add a bunch of lines to your iax.conf file:

[<USERNAME>]
type=user
username=<USERNAME>
secret=<PASSWORD>
context=default
host=dynamic
nat=yes
notransfer=yes

You just have to fill in the <USERNAME> and <PASSWORD>. After each change you have to reload the configuration (e.g. "asterisk -rx reload chan_iax2.so"). Perhaps you want to write scripts for automatic configuration and so on. But be warned: Further versions of fgcom may use the multiplayer servers for getting usernames and position data and you have to change your scripts.

===Problems?===

If you have problems you can contact me via email at "dcoredump AT gmail.com".

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

 
==Development==

TODO
 
=='''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:'''

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 down 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!

 
=='''See also'''==
*[[FlightGear related projects]]

[[Category:Software]]

FGCom (before 3.0)

2009-11-08T01:04:54Z

Natovr: /* Start the FGFS */ Forgot about win32 folder, and .exe suffix.

'''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''' on http://www.flightgear.org/forums/):
**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.
*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
*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.
You can even use it in models without radios - just use the standard FlightGear menu --> Equipment --> Radio Settings. 

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.

 
=='''The Client installation'''==
===Prequisites===
====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 FGFS command-window.

For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html

Of course you will also need a connection to the Internet for this real-time, worldwide voice communication.

 
====Software Requirements====
{| 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" |'''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 (until now per keyboard - now also with this vocal interface: FGCom).
|}
 
====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" |'''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" |'''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
|}
 
===Installing FGCom===
====Install on Linux====
For Linux-Systems there are 3 ways to install:

'''1) Downloading from the “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).'''
*'''Advantage:''' This is the easiest way and ensures that maintenance and services for this package and all concurrencies to it are provided automatically for a reasonable time-frame.
*'''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.
 
'''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.
*'''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
 
'''3) Compiling it locally'''
*'''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.
*'''Disadvantage:''' No automated maintenance available. Also the user should have some basic knowledge of his system and it's devices.
*'''Installation:'''
<ol><li>
Fetch FGCom (a copy of a working iaxclient is inside) from 
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom
 
</li> <li>
Optional: edit iaxclient/lib/Makefile
::{| style="width:80%" border="2"
|+
|-
||USE_PA_OSS=0||Set to "1" to use the oss emulation
|-
||USE_PA_ALSA=0||Set to "1" to use portaudio alsa (WARNING: only if your card natively supports 8000Hz sample rate)
|-
||USE_PA_JACK=0||Set to "1" to use
|-
||AUDIO_ALSA=0||Set to "1" to use native alsa (WARNING: PTT won't work)
|-
||AUDIO_OPENAL=1||'''Set to "0"''' if you do not want to use OpenAl ('''as recommended and set as default for now'''. Note however, that it requires OpenAl with capture support.)
|-
|}
</li> <li>
Edit fgcom/src/Makefile and check the pathes for PLIB_PREFIX and OPENAL_PREFIX.
</li> <li>
Compile iaxclient and fgcom. To do so, do the following:
cd fgcom/src && make
</li> <li>
Install
make install
</li> <li>
continue with chapter [[FGCOM#Test the basic function|testing the basic functions]]
</li></ol>

 
====Install on Windows====
Please use the Windows-Installation description on http://wiki.flightgear.org/index.php/FGCOM_for_Windows

 
====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.

But '''you do need OS X 10.5''' as prerequisite. With lower versions you will end up with a generic "bus error" message!

 
===Testing===
During testing
#we will test the basic FGCOM-functions without the FGFS
#after that we test the FGCOM together with the FGFS
#finally we test/adjust the Microphone and Loudspeaker system

For these tests please see the [[FGCOM_Testing|FGCOM_Testing]]

 
===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:
====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:

If you don't have an Icon available to start the FGrun, then
*use a [[Command line|command-window]]
*change into the directory in which FGFS was installed
*and start the program from there:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs sh ./run_fgrun.sh
|-
||for Std. Linux e.g.: ||fgrun
|-
||for Windows e.g.: ||D: cd 'C:\Program Files\Flightgear\win32' fgrun.exe
|-
||for Mac: || ||
|}
Wait for the Program-Window to start and then define: 
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]] 
→ Click “Next” 
'''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. 
→ Click “Next” 
'''3)''' Define the '''Multiplayer options:''' (ref. wiki [[Howto: Multiplayer]] for details)
{|
|+
|-
|width=610|[[image:FGrun_base.jpg|thumb|left|600px|Basic + Multiplayer Options]]
|“AI models” must be activated in order to see all traffic
 “Multiplayer” must be activated
 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.
 Insert your “Callsign:” (max. 7 characters)
 define the “in” and “out” ports both with the standard “5000”
 With "Load/Save as" you may build up yourself a library of settings for different airports.
|}→ Click “Advanced” 
'''4)''' In the “'''Advanced Options'''” check the following sections (click/select them in the left column):
#General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
#Features: “AI Traffic” should be activated already
#Initial Position:
{|
|+
|-
|width=420|[[image:FGrun_IP.jpg|thumb|left|400px|Advanced: Initial Position]]
|
You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''
 ''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.
|}
Open http://mpmap01.flightgear.org
{|
|+
|-
|width=510|[[image:MPmap.jpg|thumb|left|500px|Preflight]]
|
*if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
*click on “nav”
*disable all options except “apt code”
*type “KPAO” into the filed “Navaids lookup”
*hit ENTER or click onto the reading-glass symbol
*click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”
*now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”
*then zoom into the airport
*set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen
*type those long/lat values into the field below and also the wanted heading of the plane while parking
|}
'''5) Network:'''
{|
|+
|-
|width=420|[[image:FGrun_net.jpg|thumb|left|400px|Preflight]]
|Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.
 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 a [[Command line|command-window]] and type
{|border="1"
|+
|width="100"|OS
|width="75"|'''to type'''
|width="40"|Cap. ||returned values
|-
||for linux: ||ifconfig ||eth0 ||
Link encap:Ethernet HWaddr 00:1d:92:80:a6:ab
 inet addr:'''192.168.178.23''' Bcast:192.168.178.255 Mask:255.255.255.0
|-
||for Windows: ||ipconfig /all ||et ||
Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF
 DHCP aktiviert. . . . . . . . . . : Ja
 Autokonfiguration aktiviert . . . : Ja
 IP-Adresse. . . . . . . . . . . . : '''192.168.178.20'''
 Subnetzmaske. . . . . . . . . . . : 255.255.255.0
 IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
|-
||for Mac: || || ||
|}
The '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!!

'''6) Input/Output:'''
{|
|+
|-
|width=420|[[image:FGrun_IO.jpg|thumb|left|400px|Preflight]]
|You do need a "generic" line as shown, because '''this defines the interface between FGFS and FGCom'''.
 
To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown. 
Editing an existing line: Start by clicking onto the existing one, then change as required. 
Deleting an existing Line: Click onto the line to be deleted, then hit "Delete"

|}

'''7) Avionics:''' let's define:
{|
|+
|-
|width="50"|
|width="60"|Nav1:
|width="100"|114.10 ||San Jose VOR
|-
| ||Nav2: || 115.80 ||SF VOR
|-
| ||ADF: || 379 || Brijj, beacon at SF
|}
and activate: DME to Nav1 
There is no field to input COM-radios, but remember them for setting them later manually:
{|
|+
|-
|width="50"|
|width="60" |Com1
|width="100" |118.60 ||Paolo Alto
|-
| ||Com2 || 120.50 || San Francisco
|}

'''8) Properties:'''
Here you can define any presetting for any values in the FGFS. see e.g.: FGFS-menu-bar --> File --> “Browse Internal Properties”
{|
|+
|-
|width=520|[[image:FGrun_prop.jpg|thumb|left|500px|Preflight]]
|
e.g. I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
 Input a new line: Just hit “New” and type your string.
 Edit a line: Be sure first to click onto an existing item and then edit this “Property”
 Delete a line: Click onto the line to be deleted then hit "Delete"
|}
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. 

====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”:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs sh ./run_fgcom.sh
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Windows e.g.: ||C: cd \programs\flightgear fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Mac: || ||
|}
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
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 206M
Using iaxclient library Version SVN 206M

Successfully parsed command-line options.
Reading list of airports...done.
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|Test the basic function]]

{|
|+
|-
|width="300"| ||
|-
|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: ||
|-
|
Selected frequency: 119.650
Call rejected by remote
|
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 118.60 (needed at Palo Alto):
|-
|
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
|This last line will be repeated according the to time span you defined in the “Input/Output” command “--generic=socket,in,'''10''',,5500,tcp”, you may change that value later according to your preferences.
|-
| 3) Press your PTT (PushToTalk on space-bar and joystick, as available):
|-
|
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.
|-
| Now lets set/verify the other Radios:
*COM2 = 120.50 San Francisco
*NAV1 = 114.10 San Jose
*NAV2 = 115.80 San Francisco
4) Pressing Upper+Space will switch to the next radio: '''NAV1'''
|-
|
Radio-Select: NAV1
Selected frequency: 114.100
Hanging up call 0
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|Compare this to the NAV2 indication 2 steps later: something is wrong – and it wasn't your fault: Although this NAV is valid (see ...FGFS/data/Airports/apt.dat.gz), it is missing in the FGCom listing .../FGCom/positions.txt. I encountered this problem several times, as well for Airports as also for VOR's. If this happens with your most beloved airport you can add those missing data with a text-editor. But before changing be sure to save the original data somewhere - just in case!
|-
| 5) Pressing Upper+Space once more switches to '''COM2'''
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km)
[LISTEN] mute mic, unmute speaker
Call 0 accepted
Call 0 answered
|That looks OK: San Francisco is about 29 km away watch the “km” instead of miles! '''10 km''' = '''6.2137 mi'''
|-
| 6) Pressing Upper+Space once more switches to '''NAV2'''
|-
|
Radio-Select: NAV2
Selected frequency: 115.800
Hanging up call 0
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|And Yes: The SF VOR is just a little closer than the airport(center)
|-
| 7) Pressing Upper+Space once more brings back '''COM1''':
|-
|
Radio-Select: COM1
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|-
| 8) Lets us start and continue flying in the direction about 130°:
|-
|
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km)
|notice that you first come closer (to the center of the airport) and after that getting away
|-
| 9) Let's switch to '''COM2''' (San Francisco) and watch:
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km)
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km)
..
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km)
Hanging up call 0
Radio-Select: NAV2
Selected frequency: 115.800
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|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).
 
If you got here without any (technical) problems your FGCom is fully functional. Have fun when using it.

 
===Using FGCom===
There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]):
*'''Normal usage at airports:''' i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through 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!) 
*The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - and 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, the 123.45 will follow soon. You may try from time to time if this limitations still exist. 
*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.

 
===Supplemantery Informations===
====Tips and Tricks====
<ol>
=====Airport missing in FGCom:=====
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line
KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
You can add extra lines for any locations you want. e.g.: (watch the separation comas)
apt-code = DUMY (a "dummy" or your favorite, but missing, airport code)
KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz”
or just take one of which you are sure that you do not need it in the FGFS-reality
(notice that several Airports (far apart) use same frequencies!
long/lat = take out of the Mpmap (or Google Map)
type = whatever
name = whatever
''(of course those definition are only known to your own PC and last only until the next data update!)''
 
=====Editing FGCOM-Data-Files=====
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
*For windows you can use "WordPad"
*For Linux the "gedit" works fine
 
=====Copying-Printing this WIKI-Page'''=====
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
*goto this page: ( http://wiki.flightgear.org/index.php/FGCOM )
*to copy:
**select in the Browser-Menu: "File" --> "Save Page as.. "
*to print:
**select the last entry in the sidebar on the left: "Printable version"
**Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"
**before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages!
**If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer


 
=====Joystick compatibility between Operating Systems:=====
ref also: [[Joystick]] 
You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"):
<axis> (instead of the usual <axis n=”3”> )
<desc>Mixture</desc>
<number>
<unix>3</unix>
<mac>5</mac>
<windows>5</windows>
</number>
<binding>
<command>nasal</command>
<script>controls.mixtureAxis()</script>
</binding>
</axis>

 
=====assign PTT to Joystick and PTT=====
If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)
<button n="x">
<desc>PTT - Push To Talk</desc>
<binding>
<command>nasal</command>
<script>controls.ptt(1)</script>
</binding>
<mod-up>
<binding>
<command>nasal</command>
<script>controls.ptt(0)</script>
</binding>
</mod-up>
</button>

====Helpfull INTERNET Adresses====
'''World-Time:'''
*for standard deviations:http://www.timeanddate.com/worldclock/custom.html?sort=1
*for direct conversions: http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Especially for multiplayer events you should define all times in the internationally used GMT (Greenwich Meantime). Just pick up your deviation from GMT and memorize it. If everybody does it, we could avoid a lot of misunderstandings. 
'''Decimal to Degree''' http://www.hbnweb.de/mathematik/grad-dezimal.html 
Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it. 
'''Miles, km, feet, etc. etc. ...''': http://www.convertunits.com/
 If like to avoid troubles (like e.g. NASA lost a satellite because of it) just look it up.

'''Ports needed''' 
In case of problems over the INTERNET you might check that the the following ports are allowed:
1314 TCP if the Festival-Server is used for Text/Sound
2005 UDP Vcp-Stream
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer (VPN Sftw.)
5001 UDP Enable HTTP-server
5002 UDP Enable property server
5003 UDP Enable Screen-Shot services
5004 UDP (may be used as a spare)
5505 UDP Terra Sync
16661 UDP FGCom listening to FGFS, usually “local host” only
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).

====Commandline Parameters====
fgcom --help
returns the following useful info
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

OPTION DESCRIPTION

-d, -debug, --debug= show debugging information
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')
-s, -fgserver, --fgserver= network device to connect to (default: 'localhost')
-p, -port, --port= where we should listen to FG (default: '16661')
-a, -airport, --airport= airport-id (ICAO) for ATC-mode
-f, -frequency, --frequency= frequency for ATC-mode
-U, -user, --user= username for VoIP account (default: 'guest')
-P, -password, --password= password for VoIP account (default: 'guest')
-i, -mic, --mic= mic input level (0.0 - 1.0)
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)
-b, -mic-boost, --mic-boost= enable mic boost
-l, -list-audio, --list-audio= list audio devices
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')

Available codecs:
u - ulaw (default and best codec because the mixing is based onto ulaw)
a - alaw
g - gsm
s - speex
7 - G.723

Mode 1: client for COM1 of flightgear:
$ fgcom
- connects fgcom to fgfs at localhost:16661
$ fgcom -sother.host.tld -p23456
- connects fgcom to fgfs at other.host.tld:23456

Mode 2: client for an ATC at <airport> on <frequency>:
$ fgcom -aKSFO -f120.500
- sets up fgcom for an ATC radio at KSFO 120.500 MHz

Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!

Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''

 

=='''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.

===Prerequirements===

Install Asterisk on top of your favorite distribution. Please refer to installation manuals (e.g. [[http://www.asteriskguru.com/|Asterisk-Guru]]) you can find on the net. You do not need H.323 or SIP because the fgcom client uses IAX2 as VoIP signaling protocol. Only if you think about connecting external VoIP applications to FGCOM you should consider to activate H.323 or SIP (but this is not the scope of this small howto).

Notice: You need to install the zaptel driver modules - even if you won't use any hardware for telecom interfacing. You need the ztdummy kernel module for the asterisk conference application MeetMe() because it simulates a hardware clock needed by this application. Further development of FGCOM might use app_conference which don't needs any timing device.

For now we want to use /etc/asterisk as the base configuration directory.

===Setting up the radio frequencies===

The radio frequencies are "simple" Conferences and realized due to the Asterisk application MeetMe().

====Part 1: General configuration====

First you have to set up the general configuration of the system. Put the following at the top of your "extensions.conf" file:

[general]
static=yes
writeprotect=yes
;
[globals]
;
[macro-com]
exten => s,1,Answer()
exten => s,n,MeetMe(${MACRO_EXTEN},qd)
exten => s,n,Hangup()
;
[macro-echo]
exten => s,1,Answer()
exten => s,n,Echo()
exten => s,n,Hangup()
;
[guest]
; ATC-Help
exten => 01-ZZZZ-911.000,1,Macro(com)
exten => 012525252591100,1,Dial(Local/01-ZZZZ-911.000)
exten => 01-ZZZZ-910.000,1,Macro(echo)
exten => 012525252591000,1,Dial(Local/01-ZZZZ-910.000)
;
[default]
include => guest
;
; Code:
; 01 - FlightGear
; 02 - Microsoft Flight-Simulator
; 03 - ...
;
; Air2Air
exten => 01-ZZZZ-123.450,1,Macro(com)
exten => 012525252512345,1,Dial(Local/01-ZZZZ-123.450)
exten => 01-ZZZZ-122.750,1,Macro(com)
exten => 012525252512275,1,Dial(Local/01-ZZZZ-122.750)

====Part 2: Adding your favorite (all?) frequencies====

For this you have simply to create an extension for every touple of airport/frequency in extensions.conf. The following is an example for Berlin-Tempelhof (EDDI). The information comes from the file "apt.dat.gz" of your FlightGear installation.

; EDDI ATIS 126.020 - Berlin Tempelhof
exten => 01-EDDI-126.020,1,Macro(com)
exten => 010403030812602,1,Dial(Local/01-EDDI-126.020)
;
; EDDI BERLIN DEP 120.620 - Berlin Tempelhof
exten => 01-EDDI-120.620,1,Macro(com)
exten => 010403030812062,1,Dial(Local/01-EDDI-120.620)
;
; EDDI BERLIN DIRECTOR 121.120 - Berlin Tempelhof
exten => 01-EDDI-121.120,1,Macro(com)
exten => 010403030812112,1,Dial(Local/01-EDDI-121.120)
;
; EDDI BERLIN ARR 126.420 - Berlin Tempelhof
exten => 01-EDDI-126.420,1,Macro(com)
exten => 010403030812642,1,Dial(Local/01-EDDI-126.420)
;
; EDDI GND 121.950 - Berlin Tempelhof
exten => 01-EDDI-121.950,1,Macro(com)
exten => 010403030812195,1,Dial(Local/01-EDDI-121.950)
;
; EDDI TWR 119.570 - Berlin Tempelhof
exten => 01-EDDI-119.570,1,Macro(com)
exten => 010403030811957,1,Dial(Local/01-EDDI-119.570)
;
; EDDI BERLIN DIRECTOR 136.100 - Berlin Tempelhof
exten => 01-EDDI-136.100,1,Macro(com)
exten => 010403030813610,1,Dial(Local/01-EDDI-136.100)
;
; EDDI TWR 118.100 - Berlin Tempelhof
exten => 01-EDDI-118.100,1,Macro(com)
exten => 010403030811810,1,Dial(Local/01-EDDI-118.100)
;
; EDDI BERLIN DEP 119.500 - Berlin Tempelhof
exten => 01-EDDI-119.500,1,Macro(com)
exten => 010403030811950,1,Dial(Local/01-EDDI-119.500)
;
; EDDI BERLIN ARR 119.620 - Berlin Tempelhof
exten => 01-EDDI-119.620,1,Macro(com)
exten => 010403030811962,1,Dial(Local/01-EDDI-119.620)

What does the above mean? There are two lines (three with the comment) for each frequency: The first one sets up an extension named "01-EDDI-119.500". Yes, for VoIP you can use textual extensions but be careful if you want to setup your Asterisk-Server with POTS (=Plain old telephone service). Therefor you need the second line which is the same as above but without dashes and the letters in the decimal representation of the ASCII Code. The second line does only a "rewrite" of the numerical representation to the textual one.

For setting up all airports you can write your own simple script. But this maybe also not needed in further versions of FGCOM.

After editing the extensions.conf file you have to reload the extensions file (e.g. "asterisk -rx extensions reload").

You can add further nice goodies to your extensions.conf: MorseCode() for morsing the code of the VOR (MorseCode() will only work in Asterisk >= 1.4), Recording of metar data and playing this recording back when using the frequency of the metar information, ...

===Setting up user accounts===

The user accounts are located in the file iax.conf (and perhaps also in sip.conf, but this is not necessary). The top of the file should look like this:

[general]
bandwith=low
disallow=lpc10
jitterbuffer=yes
forcejitterbuffer=no
tos=lowdelay
autokill=yes
disallow=all
allow=alaw
allow=gsm
allow=ilbc
allow=g726
allow=ulaw
language=en
maxauthreq=10
context=guest
;
[guest]
type=user
username=guest
context=guest
qualify=yes
callerid=Guest IAX User
host=dynamic
;

You may want to disallow more codecs or want to allow additional codecs (such as speex). But have in mind that the internal mixing of the conferences are done in "ulaw". But "ulaw" needs about 80 kBit/s because it does no compression. So you have to think about what's better for you: less bandwidth (per user) and more CPU usage or more bandwidth (per user) and less CPU usage... you should also consider the "sound" of some codecs may not have the 'real radio sound'.

For each user you have to add a bunch of lines to your iax.conf file:

[<USERNAME>]
type=user
username=<USERNAME>
secret=<PASSWORD>
context=default
host=dynamic
nat=yes
notransfer=yes

You just have to fill in the <USERNAME> and <PASSWORD>. After each change you have to reload the configuration (e.g. "asterisk -rx reload chan_iax2.so"). Perhaps you want to write scripts for automatic configuration and so on. But be warned: Further versions of fgcom may use the multiplayer servers for getting usernames and position data and you have to change your scripts.

===Problems?===

If you have problems you can contact me via email at "dcoredump AT gmail.com".

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

 
==Development==

TODO
 
=='''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:'''

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 down 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!

 
=='''See also'''==
*[[FlightGear related projects]]

[[Category:Software]]

FGCom (before 3.0)

2009-11-08T01:03:45Z

Natovr: M/* Start the FGFS */ MS doesn't support directories named without the partition it is on.

'''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''' on http://www.flightgear.org/forums/):
**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.
*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
*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.
You can even use it in models without radios - just use the standard FlightGear menu --> Equipment --> Radio Settings. 

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.

 
=='''The Client installation'''==
===Prequisites===
====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 FGFS command-window.

For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html

Of course you will also need a connection to the Internet for this real-time, worldwide voice communication.

 
====Software Requirements====
{| 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" |'''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 (until now per keyboard - now also with this vocal interface: FGCom).
|}
 
====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" |'''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" |'''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
|}
 
===Installing FGCom===
====Install on Linux====
For Linux-Systems there are 3 ways to install:

'''1) Downloading from the “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).'''
*'''Advantage:''' This is the easiest way and ensures that maintenance and services for this package and all concurrencies to it are provided automatically for a reasonable time-frame.
*'''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.
 
'''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.
*'''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
 
'''3) Compiling it locally'''
*'''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.
*'''Disadvantage:''' No automated maintenance available. Also the user should have some basic knowledge of his system and it's devices.
*'''Installation:'''
<ol><li>
Fetch FGCom (a copy of a working iaxclient is inside) from 
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom
 
</li> <li>
Optional: edit iaxclient/lib/Makefile
::{| style="width:80%" border="2"
|+
|-
||USE_PA_OSS=0||Set to "1" to use the oss emulation
|-
||USE_PA_ALSA=0||Set to "1" to use portaudio alsa (WARNING: only if your card natively supports 8000Hz sample rate)
|-
||USE_PA_JACK=0||Set to "1" to use
|-
||AUDIO_ALSA=0||Set to "1" to use native alsa (WARNING: PTT won't work)
|-
||AUDIO_OPENAL=1||'''Set to "0"''' if you do not want to use OpenAl ('''as recommended and set as default for now'''. Note however, that it requires OpenAl with capture support.)
|-
|}
</li> <li>
Edit fgcom/src/Makefile and check the pathes for PLIB_PREFIX and OPENAL_PREFIX.
</li> <li>
Compile iaxclient and fgcom. To do so, do the following:
cd fgcom/src && make
</li> <li>
Install
make install
</li> <li>
continue with chapter [[FGCOM#Test the basic function|testing the basic functions]]
</li></ol>

 
====Install on Windows====
Please use the Windows-Installation description on http://wiki.flightgear.org/index.php/FGCOM_for_Windows

 
====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.

But '''you do need OS X 10.5''' as prerequisite. With lower versions you will end up with a generic "bus error" message!

 
===Testing===
During testing
#we will test the basic FGCOM-functions without the FGFS
#after that we test the FGCOM together with the FGFS
#finally we test/adjust the Microphone and Loudspeaker system

For these tests please see the [[FGCOM_Testing|FGCOM_Testing]]

 
===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:
====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:

If you don't have an Icon available to start the FGrun, then
*use a [[Command line|command-window]]
*change into the directory in which FGFS was installed
*and start the program from there:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs sh ./run_fgrun.sh
|-
||for Std. Linux e.g.: ||fgrun
|-
||for Windows e.g.: ||D: cd 'C:\Program Files\Flightgear' fgrun
|-
||for Mac: || ||
|}
Wait for the Program-Window to start and then define: 
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]] 
→ Click “Next” 
'''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. 
→ Click “Next” 
'''3)''' Define the '''Multiplayer options:''' (ref. wiki [[Howto: Multiplayer]] for details)
{|
|+
|-
|width=610|[[image:FGrun_base.jpg|thumb|left|600px|Basic + Multiplayer Options]]
|“AI models” must be activated in order to see all traffic
 “Multiplayer” must be activated
 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.
 Insert your “Callsign:” (max. 7 characters)
 define the “in” and “out” ports both with the standard “5000”
 With "Load/Save as" you may build up yourself a library of settings for different airports.
|}→ Click “Advanced” 
'''4)''' In the “'''Advanced Options'''” check the following sections (click/select them in the left column):
#General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
#Features: “AI Traffic” should be activated already
#Initial Position:
{|
|+
|-
|width=420|[[image:FGrun_IP.jpg|thumb|left|400px|Advanced: Initial Position]]
|
You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''
 ''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.
|}
Open http://mpmap01.flightgear.org
{|
|+
|-
|width=510|[[image:MPmap.jpg|thumb|left|500px|Preflight]]
|
*if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
*click on “nav”
*disable all options except “apt code”
*type “KPAO” into the filed “Navaids lookup”
*hit ENTER or click onto the reading-glass symbol
*click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”
*now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”
*then zoom into the airport
*set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen
*type those long/lat values into the field below and also the wanted heading of the plane while parking
|}
'''5) Network:'''
{|
|+
|-
|width=420|[[image:FGrun_net.jpg|thumb|left|400px|Preflight]]
|Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.
 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 a [[Command line|command-window]] and type
{|border="1"
|+
|width="100"|OS
|width="75"|'''to type'''
|width="40"|Cap. ||returned values
|-
||for linux: ||ifconfig ||eth0 ||
Link encap:Ethernet HWaddr 00:1d:92:80:a6:ab
 inet addr:'''192.168.178.23''' Bcast:192.168.178.255 Mask:255.255.255.0
|-
||for Windows: ||ipconfig /all ||et ||
Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF
 DHCP aktiviert. . . . . . . . . . : Ja
 Autokonfiguration aktiviert . . . : Ja
 IP-Adresse. . . . . . . . . . . . : '''192.168.178.20'''
 Subnetzmaske. . . . . . . . . . . : 255.255.255.0
 IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
|-
||for Mac: || || ||
|}
The '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!!

'''6) Input/Output:'''
{|
|+
|-
|width=420|[[image:FGrun_IO.jpg|thumb|left|400px|Preflight]]
|You do need a "generic" line as shown, because '''this defines the interface between FGFS and FGCom'''.
 
To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown. 
Editing an existing line: Start by clicking onto the existing one, then change as required. 
Deleting an existing Line: Click onto the line to be deleted, then hit "Delete"

|}

'''7) Avionics:''' let's define:
{|
|+
|-
|width="50"|
|width="60"|Nav1:
|width="100"|114.10 ||San Jose VOR
|-
| ||Nav2: || 115.80 ||SF VOR
|-
| ||ADF: || 379 || Brijj, beacon at SF
|}
and activate: DME to Nav1 
There is no field to input COM-radios, but remember them for setting them later manually:
{|
|+
|-
|width="50"|
|width="60" |Com1
|width="100" |118.60 ||Paolo Alto
|-
| ||Com2 || 120.50 || San Francisco
|}

'''8) Properties:'''
Here you can define any presetting for any values in the FGFS. see e.g.: FGFS-menu-bar --> File --> “Browse Internal Properties”
{|
|+
|-
|width=520|[[image:FGrun_prop.jpg|thumb|left|500px|Preflight]]
|
e.g. I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
 Input a new line: Just hit “New” and type your string.
 Edit a line: Be sure first to click onto an existing item and then edit this “Property”
 Delete a line: Click onto the line to be deleted then hit "Delete"
|}
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. 

====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”:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs sh ./run_fgcom.sh
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Windows e.g.: ||C: cd \programs\flightgear fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Mac: || ||
|}
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
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 206M
Using iaxclient library Version SVN 206M

Successfully parsed command-line options.
Reading list of airports...done.
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|Test the basic function]]

{|
|+
|-
|width="300"| ||
|-
|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: ||
|-
|
Selected frequency: 119.650
Call rejected by remote
|
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 118.60 (needed at Palo Alto):
|-
|
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
|This last line will be repeated according the to time span you defined in the “Input/Output” command “--generic=socket,in,'''10''',,5500,tcp”, you may change that value later according to your preferences.
|-
| 3) Press your PTT (PushToTalk on space-bar and joystick, as available):
|-
|
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.
|-
| Now lets set/verify the other Radios:
*COM2 = 120.50 San Francisco
*NAV1 = 114.10 San Jose
*NAV2 = 115.80 San Francisco
4) Pressing Upper+Space will switch to the next radio: '''NAV1'''
|-
|
Radio-Select: NAV1
Selected frequency: 114.100
Hanging up call 0
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|Compare this to the NAV2 indication 2 steps later: something is wrong – and it wasn't your fault: Although this NAV is valid (see ...FGFS/data/Airports/apt.dat.gz), it is missing in the FGCom listing .../FGCom/positions.txt. I encountered this problem several times, as well for Airports as also for VOR's. If this happens with your most beloved airport you can add those missing data with a text-editor. But before changing be sure to save the original data somewhere - just in case!
|-
| 5) Pressing Upper+Space once more switches to '''COM2'''
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km)
[LISTEN] mute mic, unmute speaker
Call 0 accepted
Call 0 answered
|That looks OK: San Francisco is about 29 km away watch the “km” instead of miles! '''10 km''' = '''6.2137 mi'''
|-
| 6) Pressing Upper+Space once more switches to '''NAV2'''
|-
|
Radio-Select: NAV2
Selected frequency: 115.800
Hanging up call 0
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|And Yes: The SF VOR is just a little closer than the airport(center)
|-
| 7) Pressing Upper+Space once more brings back '''COM1''':
|-
|
Radio-Select: COM1
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|-
| 8) Lets us start and continue flying in the direction about 130°:
|-
|
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km)
|notice that you first come closer (to the center of the airport) and after that getting away
|-
| 9) Let's switch to '''COM2''' (San Francisco) and watch:
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km)
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km)
..
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km)
Hanging up call 0
Radio-Select: NAV2
Selected frequency: 115.800
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|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).
 
If you got here without any (technical) problems your FGCom is fully functional. Have fun when using it.

 
===Using FGCom===
There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]):
*'''Normal usage at airports:''' i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through 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!) 
*The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - and 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, the 123.45 will follow soon. You may try from time to time if this limitations still exist. 
*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.

 
===Supplemantery Informations===
====Tips and Tricks====
<ol>
=====Airport missing in FGCom:=====
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line
KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
You can add extra lines for any locations you want. e.g.: (watch the separation comas)
apt-code = DUMY (a "dummy" or your favorite, but missing, airport code)
KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz”
or just take one of which you are sure that you do not need it in the FGFS-reality
(notice that several Airports (far apart) use same frequencies!
long/lat = take out of the Mpmap (or Google Map)
type = whatever
name = whatever
''(of course those definition are only known to your own PC and last only until the next data update!)''
 
=====Editing FGCOM-Data-Files=====
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
*For windows you can use "WordPad"
*For Linux the "gedit" works fine
 
=====Copying-Printing this WIKI-Page'''=====
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
*goto this page: ( http://wiki.flightgear.org/index.php/FGCOM )
*to copy:
**select in the Browser-Menu: "File" --> "Save Page as.. "
*to print:
**select the last entry in the sidebar on the left: "Printable version"
**Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"
**before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages!
**If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer


 
=====Joystick compatibility between Operating Systems:=====
ref also: [[Joystick]] 
You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"):
<axis> (instead of the usual <axis n=”3”> )
<desc>Mixture</desc>
<number>
<unix>3</unix>
<mac>5</mac>
<windows>5</windows>
</number>
<binding>
<command>nasal</command>
<script>controls.mixtureAxis()</script>
</binding>
</axis>

 
=====assign PTT to Joystick and PTT=====
If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)
<button n="x">
<desc>PTT - Push To Talk</desc>
<binding>
<command>nasal</command>
<script>controls.ptt(1)</script>
</binding>
<mod-up>
<binding>
<command>nasal</command>
<script>controls.ptt(0)</script>
</binding>
</mod-up>
</button>

====Helpfull INTERNET Adresses====
'''World-Time:'''
*for standard deviations:http://www.timeanddate.com/worldclock/custom.html?sort=1
*for direct conversions: http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Especially for multiplayer events you should define all times in the internationally used GMT (Greenwich Meantime). Just pick up your deviation from GMT and memorize it. If everybody does it, we could avoid a lot of misunderstandings. 
'''Decimal to Degree''' http://www.hbnweb.de/mathematik/grad-dezimal.html 
Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it. 
'''Miles, km, feet, etc. etc. ...''': http://www.convertunits.com/
 If like to avoid troubles (like e.g. NASA lost a satellite because of it) just look it up.

'''Ports needed''' 
In case of problems over the INTERNET you might check that the the following ports are allowed:
1314 TCP if the Festival-Server is used for Text/Sound
2005 UDP Vcp-Stream
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer (VPN Sftw.)
5001 UDP Enable HTTP-server
5002 UDP Enable property server
5003 UDP Enable Screen-Shot services
5004 UDP (may be used as a spare)
5505 UDP Terra Sync
16661 UDP FGCom listening to FGFS, usually “local host” only
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).

====Commandline Parameters====
fgcom --help
returns the following useful info
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

OPTION DESCRIPTION

-d, -debug, --debug= show debugging information
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')
-s, -fgserver, --fgserver= network device to connect to (default: 'localhost')
-p, -port, --port= where we should listen to FG (default: '16661')
-a, -airport, --airport= airport-id (ICAO) for ATC-mode
-f, -frequency, --frequency= frequency for ATC-mode
-U, -user, --user= username for VoIP account (default: 'guest')
-P, -password, --password= password for VoIP account (default: 'guest')
-i, -mic, --mic= mic input level (0.0 - 1.0)
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)
-b, -mic-boost, --mic-boost= enable mic boost
-l, -list-audio, --list-audio= list audio devices
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')

Available codecs:
u - ulaw (default and best codec because the mixing is based onto ulaw)
a - alaw
g - gsm
s - speex
7 - G.723

Mode 1: client for COM1 of flightgear:
$ fgcom
- connects fgcom to fgfs at localhost:16661
$ fgcom -sother.host.tld -p23456
- connects fgcom to fgfs at other.host.tld:23456

Mode 2: client for an ATC at <airport> on <frequency>:
$ fgcom -aKSFO -f120.500
- sets up fgcom for an ATC radio at KSFO 120.500 MHz

Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!

Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''

 

=='''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.

===Prerequirements===

Install Asterisk on top of your favorite distribution. Please refer to installation manuals (e.g. [[http://www.asteriskguru.com/|Asterisk-Guru]]) you can find on the net. You do not need H.323 or SIP because the fgcom client uses IAX2 as VoIP signaling protocol. Only if you think about connecting external VoIP applications to FGCOM you should consider to activate H.323 or SIP (but this is not the scope of this small howto).

Notice: You need to install the zaptel driver modules - even if you won't use any hardware for telecom interfacing. You need the ztdummy kernel module for the asterisk conference application MeetMe() because it simulates a hardware clock needed by this application. Further development of FGCOM might use app_conference which don't needs any timing device.

For now we want to use /etc/asterisk as the base configuration directory.

===Setting up the radio frequencies===

The radio frequencies are "simple" Conferences and realized due to the Asterisk application MeetMe().

====Part 1: General configuration====

First you have to set up the general configuration of the system. Put the following at the top of your "extensions.conf" file:

[general]
static=yes
writeprotect=yes
;
[globals]
;
[macro-com]
exten => s,1,Answer()
exten => s,n,MeetMe(${MACRO_EXTEN},qd)
exten => s,n,Hangup()
;
[macro-echo]
exten => s,1,Answer()
exten => s,n,Echo()
exten => s,n,Hangup()
;
[guest]
; ATC-Help
exten => 01-ZZZZ-911.000,1,Macro(com)
exten => 012525252591100,1,Dial(Local/01-ZZZZ-911.000)
exten => 01-ZZZZ-910.000,1,Macro(echo)
exten => 012525252591000,1,Dial(Local/01-ZZZZ-910.000)
;
[default]
include => guest
;
; Code:
; 01 - FlightGear
; 02 - Microsoft Flight-Simulator
; 03 - ...
;
; Air2Air
exten => 01-ZZZZ-123.450,1,Macro(com)
exten => 012525252512345,1,Dial(Local/01-ZZZZ-123.450)
exten => 01-ZZZZ-122.750,1,Macro(com)
exten => 012525252512275,1,Dial(Local/01-ZZZZ-122.750)

====Part 2: Adding your favorite (all?) frequencies====

For this you have simply to create an extension for every touple of airport/frequency in extensions.conf. The following is an example for Berlin-Tempelhof (EDDI). The information comes from the file "apt.dat.gz" of your FlightGear installation.

; EDDI ATIS 126.020 - Berlin Tempelhof
exten => 01-EDDI-126.020,1,Macro(com)
exten => 010403030812602,1,Dial(Local/01-EDDI-126.020)
;
; EDDI BERLIN DEP 120.620 - Berlin Tempelhof
exten => 01-EDDI-120.620,1,Macro(com)
exten => 010403030812062,1,Dial(Local/01-EDDI-120.620)
;
; EDDI BERLIN DIRECTOR 121.120 - Berlin Tempelhof
exten => 01-EDDI-121.120,1,Macro(com)
exten => 010403030812112,1,Dial(Local/01-EDDI-121.120)
;
; EDDI BERLIN ARR 126.420 - Berlin Tempelhof
exten => 01-EDDI-126.420,1,Macro(com)
exten => 010403030812642,1,Dial(Local/01-EDDI-126.420)
;
; EDDI GND 121.950 - Berlin Tempelhof
exten => 01-EDDI-121.950,1,Macro(com)
exten => 010403030812195,1,Dial(Local/01-EDDI-121.950)
;
; EDDI TWR 119.570 - Berlin Tempelhof
exten => 01-EDDI-119.570,1,Macro(com)
exten => 010403030811957,1,Dial(Local/01-EDDI-119.570)
;
; EDDI BERLIN DIRECTOR 136.100 - Berlin Tempelhof
exten => 01-EDDI-136.100,1,Macro(com)
exten => 010403030813610,1,Dial(Local/01-EDDI-136.100)
;
; EDDI TWR 118.100 - Berlin Tempelhof
exten => 01-EDDI-118.100,1,Macro(com)
exten => 010403030811810,1,Dial(Local/01-EDDI-118.100)
;
; EDDI BERLIN DEP 119.500 - Berlin Tempelhof
exten => 01-EDDI-119.500,1,Macro(com)
exten => 010403030811950,1,Dial(Local/01-EDDI-119.500)
;
; EDDI BERLIN ARR 119.620 - Berlin Tempelhof
exten => 01-EDDI-119.620,1,Macro(com)
exten => 010403030811962,1,Dial(Local/01-EDDI-119.620)

What does the above mean? There are two lines (three with the comment) for each frequency: The first one sets up an extension named "01-EDDI-119.500". Yes, for VoIP you can use textual extensions but be careful if you want to setup your Asterisk-Server with POTS (=Plain old telephone service). Therefor you need the second line which is the same as above but without dashes and the letters in the decimal representation of the ASCII Code. The second line does only a "rewrite" of the numerical representation to the textual one.

For setting up all airports you can write your own simple script. But this maybe also not needed in further versions of FGCOM.

After editing the extensions.conf file you have to reload the extensions file (e.g. "asterisk -rx extensions reload").

You can add further nice goodies to your extensions.conf: MorseCode() for morsing the code of the VOR (MorseCode() will only work in Asterisk >= 1.4), Recording of metar data and playing this recording back when using the frequency of the metar information, ...

===Setting up user accounts===

The user accounts are located in the file iax.conf (and perhaps also in sip.conf, but this is not necessary). The top of the file should look like this:

[general]
bandwith=low
disallow=lpc10
jitterbuffer=yes
forcejitterbuffer=no
tos=lowdelay
autokill=yes
disallow=all
allow=alaw
allow=gsm
allow=ilbc
allow=g726
allow=ulaw
language=en
maxauthreq=10
context=guest
;
[guest]
type=user
username=guest
context=guest
qualify=yes
callerid=Guest IAX User
host=dynamic
;

You may want to disallow more codecs or want to allow additional codecs (such as speex). But have in mind that the internal mixing of the conferences are done in "ulaw". But "ulaw" needs about 80 kBit/s because it does no compression. So you have to think about what's better for you: less bandwidth (per user) and more CPU usage or more bandwidth (per user) and less CPU usage... you should also consider the "sound" of some codecs may not have the 'real radio sound'.

For each user you have to add a bunch of lines to your iax.conf file:

[<USERNAME>]
type=user
username=<USERNAME>
secret=<PASSWORD>
context=default
host=dynamic
nat=yes
notransfer=yes

You just have to fill in the <USERNAME> and <PASSWORD>. After each change you have to reload the configuration (e.g. "asterisk -rx reload chan_iax2.so"). Perhaps you want to write scripts for automatic configuration and so on. But be warned: Further versions of fgcom may use the multiplayer servers for getting usernames and position data and you have to change your scripts.

===Problems?===

If you have problems you can contact me via email at "dcoredump AT gmail.com".

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

 
==Development==

TODO
 
=='''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:'''

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 down 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!

 
=='''See also'''==
*[[FlightGear related projects]]

[[Category:Software]]

Fgfsrc

2009-10-08T20:14:15Z

Natovr:

= fgfsrc =
The files ''fgfsrc'' purpose is to contain [[Command Line Parameters]] which are read by ''fgfs'' at startup. This is for users who start FlightGear from the [[command line]], so users using a graphical user interface like [[fgrun]] don't have to bother with this at all. Anyhow, it is possible to use fgrun to create your personal set of options by copy-and-pasting them from the ''Show command line'' textbox (on the last page of FGRun) into ''fgfsrc''.

It is very likely that this file does not exist on your system yet, and therefore has to be created by the user, you. The contents of the file are handled the same way by ''fgfs'' on all operating systems, but the name and location is not:

* on ''GNU/Linux'' and ''Mac OS X'' the file is called ''.fgfsrc'' (note the leading dot!). ''Fgfs'' is looking for it inside the user's $HOME directory. To figure out where this is on your system, open a terminal window (shell) and enter <code>cd $HOME</code>.

* on ''Windows'' systems the file is called ''system.fgfsrc'' and lives in $FG_ROOT which, on a standard installation, is ''C:\Program Files\FlightGear\data''.

===== Some 'rules' for the content: =====
* Each line contains one option only.
* If the first 'visible' character is a '#', ''fgfs'' does not read this line (comment) and totally ignores it.
* Lines containing an option followed by a comment are *not* allowed! (<code>--some-option # some comment</code>) ''Fgfs'' will not ignore this.

===== An example of a basic ''fgfsrc'' file: =====

# $HOME/.fgfsrc

### Aircraft
#
--aircraft=ec135
## Catalina, dhc3[A/F], p47d-30, F1-156-de, ZivkoEdge540
## MPcarrier: nimitz, nimitz-ATC, nimitz_observer, foch, vinson, eisenhower

### Initial position
#
--airport=LOWI
#--runway=08L
#--parkpos=A11
#
# In air:
#--offset-distance=1.5
#--altitude=6000
#--vc=70
#--enable-freeze
#
# Coordinates:
## Oilrig Lennox:
#--lon=-3.17547
#--lat=53.63305
#--altitude=205

### Environment
#
--timeofday=noon
--random-wind
--enable-real-weather-fetch
##rain/snow:
--prop:/sim/rendering/precipitation-enable=false
--enable-horizon-effect
--enable-specular-highlight
--enable-ai-models
--enable-clouds3d
--shading-flat
--fog-nicest
--enable-random-objects
--prop:/sim/rendering/random-vegetation=true
--prop:/sim/frame-rate-throttle-hz=30
--ai-scenario=nimitz_demo

### Network
#
--callsign=I-FLY
#--prop:/sim/remote/pilot-callsign=U-FLY
--multiplay=out,10,mpserver01.flightgear.org,5000
#--multiplay=in,10,localhost,5000
--httpd=5500
## nice terrasync -p 5505 -S -d /opt/fgfs/scenery.terrasync :
--atlas=socket,out,1,localhost,5505,udp
## fgcom -Sfgcom.flightgear.org.uk [-f910] :
--generic=socket,out,10,localhost,16661,udp,fgcom

### System
#
#--log-level=info
## alarm,warn,info,debug
--fg-root=/opt/fgfs/data
--fg-scenery=/opt/fgfs/data/Scenery:/opt/fgfs/scenery.1.0.1:/opt/fgfs/scenery.terrasync
--geometry=1280x1024
--bpp=24
--control=joystick
--prop:/sim/traffic-manager/enabled=0
## disable mouse mode 'fly':
--prop:/input/mice/mouse/mode/button[2]/binding/value=2

Some options (mostly properties) are only temporary of interest to the 'normal' user or even only for CVS users:

## parkpos, temporary:
--prop:/sim/traffic-manager/use-custom-scenery-data=true
(explanation missing)

Please feel free to add other useful options to the temporary and basic ones!!!

Unique Features

2009-04-19T20:09:01Z

Natovr: /* Features */ *waters the seed*

{{Stub}}

This is meant to become a list of features that are truly unique to FlightGear, and that set FlightGear apart from its commercial counterparts.

= Features =
* support for [[Dual control]] aircraft
* All addons are free

User:Natovr

2009-04-19T11:16:38Z

Natovr: :

Nothing to see here people, *gives you a cookie*, bye :)

[[User_Talk:Natovr|Natovr's talk page]]

User talk:Natovr

2009-04-19T11:14:23Z

Natovr:

If you have a problem with anything I edited or any pages I made, please post here before deleting the page I made or undoing the thing I did... I probably have a logical reason :)

If you have a problem with my user page, please say why. I don't see that anyone will have a problem, because it's my user page, and I can do anything that I want with it, within reason.

User talk:Natovr

2009-04-19T11:12:44Z

Natovr: New page: If you have a problem with anything I edited or any pages I made, please post here before deleting the page I made or undoing the thing I did... I probably have a logical reason :)

If you have a problem with anything I edited or any pages I made, please post here before deleting the page I made or undoing the thing I did... I probably have a logical reason :)

User:Natovr

2009-04-19T11:11:42Z

Natovr:

Nothing to see here people, *gives you a cookie*, bye

[[User_Talk:Natovr|Natovr's talk page]]

User:Natovr

2009-04-19T11:11:01Z

Natovr: New page: Nothing to see here people, *gives you a cookie*, bye --~~~~ ^My Talk Page

Nothing to see here people, *gives you a cookie*, bye

--[[User:Natovr|Natovr]] 07:11, 19 April 2009 (EDT)
^My Talk Page

Rallye-MS893E

2009-04-17T09:55:13Z

Natovr: /* External Links */ French D:

{{infobox Aircraft
|name = Socata Rallye MS-893E
|image =rallye-MS893.jpg
|type =Civilian Aircraft
|authors =Patrice Poly ( 3D, FDM ) Beber ( Sounds )
|fdm =[[Yasim]]
|status = Alpha
|fgname = rallye-MS893
|download = http://www.bentha.net/fgfs/hangar/rallye-MS893.zip
}}
The Rallye 893 is a single engined, low wing monoplane of all metal construction, fitted with a fixed tricycle gear. It has a bulbous cockpit which houses four people and it can be used as a [[Howto:_Do_aerotow_over_the_net|towplane]] for [[:Category:Glider|sailplanes]].

One of its particularities is beeing equiped with automatic slats, that deploy at low speeds/high incidence, help in slow flight and enable the plane to sink in wings-level reduced-power stalls rather than break with a nose-down pitch change.

The slats combined to the important fowler flaps allow for very short take off and landings, even on rough surfaces.

==Aircraft help==
===Speeds===
*Cruise speed: 113 kt ( 209 km/h )
*Never-exceed (Vne): 156 kt ( 290 km/h )
*Maneuvering (Va): 113 kt ( 210 km/h )
*Approach speed: 65 kt ( 120 km/h )
*Stall speed (Vs): ( with full flaps) 50 kt ( 92 km/h )

===For aerotow===
*Place the Rallye within 60m to a glider
*The glider pilot has to press Ctrl-o to hook the link
*You can press Shift-o to release your hook
*A better aerotow help can be found on [[Howto:_Do_aerotow_over_the_net]]

===Controls===
{| class="prettytable"
!Key
!Function
|-
|o
|Hook aerotow
|-
|Shift-o
|Release aerotow
|-
|Shift-D
|Open/Close Canopy
|-
|d
|Aileron Trim Left
|-
|f
|Aileron Trim Right
|}

==Development status/Issues/Todo==
===Finished===
*3D geometry
*Sounds
*FDM
*Basic Texturing

===TODO===
*Detailing on the textures, liveries
*Immatriculation
*A proper electrical and instrumentation setup
*Lights
*clickable panel regions
*EGT display doesn't work
*oil pressure display doesn't work
*battery level display is missing

==External Links==
*[http://en.wikipedia.org/wiki/Socata_Rallye Rallye on the wikipedia]
*[http://aeromania.free.fr/pdf/MANEX_MS893E.PDF Rallye MS893E Pilot Operating Handbook in '''French''']
*[http://richard.ferriere.free.fr/archives/essai/rallye.pdf A nice ('''French''') text about the rallye history]
[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Civilian aircraft]]

Flightgear Stable to CVS : Piece of Cake

2009-04-14T21:18:19Z

Natovr: /* '''Here are detailed Instructions for the change''' */

{{merge|Using TortoiseCVS with FlightGear}}
{{merge|Keeping FlightGear (win32) up to date without compiling}}

This is Really Simple! All Users long to get the Developer version of Flightgear(CVS) but go back thinking they have to compile and go into the treacherous world of code.

== '''Detailed instructions for the change using Windows''' ==

1: Firstly you need A CVS client. I prefer [http://www.tortoisecvs.org/ Tortoise CVS]. Here is the Link for TortoiseCVS-1.10.10 -- [http://prdownloads.sourceforge.net/tortoisecvs/TortoiseCVS-1.10.10.exe Download].

2: Now Install Tortoise CVS. You might need to Restart.

3: '''Now to fetch the data.'''

First go to your desired directory and Creae a folder named '''Flightgear'''.Now Right click the folder and you will see a menu as follows

[[Image:CVS-Checkout.JPG]]

Click on CVS Checkout. Fill the '''CVS ROOT''' with
:pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9

'''User name''' with
cvsguest

'''Module''' with
data

You Should have something like this :

[[Image:CVS.JPG]]

4: Just Click OK. If you are Prompted for Password Enter
guest
You should have something running on like this :
[[Image:CVS-2.JPG]]

5: If you cant keep your PC on for long time till the process completes, you can abort it and then the next time you start just right click the '''data''' folder inside the '''Flightgear''' folder. And click '''CVS Update'''

[[Image:CVS-Update.JPG]]

6: '''Now for the Binaries'''

This is even more Simple. First Go to your Old '''Flightgear 1.0''' folder and copy the '''bin''' directory.
Then Paste it in the new '''Flightgear''' folder

Note: If you dont have the old files, please request at the [http://www.flightgear.org/forums/ forums], and i or someone else will upload them.

7: Now go to the binaries download page -[ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ Binary Page]

Get the latest file with the prefix '''fgrun+fgfs-osg-win32-''' and extract that into '''Flightgear/bin/win32'''

8: Repeat steps '''5''' and '''7''' regularly to keep updating.

'''Note: "Keep your CVS-data up to the binaries date" AND "DO NOT REPORT BUGS UNLESS YOUR PROGRAM AND DATA MATCH!
"'''

==Checking out an older version of a file or folder==

Sometimes you may wish to get an older version of a file than is at CVS head. As a made up example, let's say you just updated your source code from CVS head and now you get errors when you try to compile. You decide that a single file has been changed and the new version is causing your compile errors. You can get any previous version of that file (or any other file) from the CVS repository.

In Windows explorer, right-click on the file or folder that you want update from a certain date. From the pop-up menu, choose "CVS >" and then "Update special..." Check the "Get time/date" checkbox, select the desired date from the calendar shown and click the "OK" button to begin the checkout.

[[Image:Fgcvsrev.gif]]

Hope this Helps!!!

Piper J3 Cub Operations Manual

2009-04-14T20:09:30Z

Natovr:

{{Mergeto|Piper J3 Cub}}
'''''This article contains material which is suspected of not complying to the GPL Licence version 2. This material is subject to removal.'''''

[This information is copied from the 1946 J3C-65 owner's handbook.]

== FLYING HINTS ==

The Piper Cub Special represents more than 15 years of diligent
aircraft engineering and manufacturing experience. Its simplicity of
design and construction, its low operating and maintenance costs, its
inherent stability, ruggedness, and its outstanding safety and ease of
flying, have made it the most popular airplane in aviation history.
The Piper Cub Special is the time-tested product of millions of hours
of flying under all conceivable conditions both in the military and in
peace time.

There are hints on starting, flying, stopping, and other related
topics that are important to the owner who wants to conserve his
airplane -- keep it in maximum airworthy condition -- and enjoy a full
measure of flying satisfaction.

First, each pilot should become familiar enough with his Piper Cub
Special that he can accomplish a satisfactory pre-flight inspection.
This check is simple and requires only a few minutes. See Section IX
for check list. Daily check of airplane prior to flight should be the
first in a number of safe flying habits the pilot should acquire.

A. BEFORE STARTING ENGINE

(1) Make routine check of gasoline supply. Visible fuel gauge is
integral part of gas tank cap; it will not show number of gallons but
will show proportion of fuel in tank by length of rod which extends
upward from cap. A full tank of 12 U.S. gallons will be indicated by
11 inches of rod extending beyond cap. Keep gas gauge rod clean and
smooth with crocus cloth for accuracy and freedom of movement.

(2) Check oil level in engine sump by removing oil cap and gauge. Oil
stick should indicate oil level up to index mark of 4 quarts.

(3) Check freedom of movement of flight and engine controls.

B. STARTING ENGINE

(1) Chock wheels, or have occupant who is familiar with controls set
brakes in cabin.

(2) Ignition switch OFF. Verify.

(3) Set throttle approximately 1/10 open.

(4) Push fuel shut-off ON.

(5) Turn propeller through several times.

(6) Turn ignition switch ON.

(7) Start engine by pulling propeller through with a snap.

CAUTION -- Always handle propeller as if switch were "ON." Stand as
far in front of propeller as possible. Use both hands and grasp one
blad approximately midway from tip. Do not overgrasp blade. Do not
wear long, loose clothing. Make sure footing is sure to preclude
possibility of feet slipping.

(8) If engine does not start, turn switch OFF. Turn primer knob to
unlock, pull out, pump three or four times, then reseat primer and
lock by turning in opposite direction. In extremely cold weather a
few strokes of the primer as the engine starts will enable it to keep
running. NOTE -- Avoid excessive priming as it causes raw gasoline to
wash lubricating oil from engine cylinder walls. Do not prime warm
engine.

(9) Repeat starting procedures 6, 7.

(10) If engine loads up and refuses to start, turn ignition switch
"OFF,", open throttle wide and turn propeller through backwards
several times to unload excessive gas mixture in cylinders. Then
close throttle and repeat starting procedure.

C. ENGINE WARM-UP

(1) As soon as engine starts, advance throttle slightly to idle at 700
R.P.M. Check engine instruments. If oil pressure gauge does not
indicate pressure within 30 seconds, stop engine immediately, check
and correct trouble before any further operation. Oil temperature
during operating should not rise above 200° F. and oil pressure should
not fall below 30 pounds. With engine warm, idling speed should be
550-600 R.P.M.

(2) Rev engine up to 2100 R.P.M. on both magnetos. Switch to LEFT and
RIGHT magnetos. R.P.M. drop should not be over 75 R.P.M. CAUTION
--Do not operate engine on either single magneto for more than 30
seconds at a time, as this tends to foul the non-operating spark plugs
in the ignition circuit of the magneto that is switched off.

D. STOPPING ENGINE

(1) Never cut switch immediately after landing as this causes engine
to cool too rapidly.

(2) Idle engine, especially in high temperature operating conditions,
for several minutes. It is advisable to switch to each magneto for 30
second intervals to allow gradual cooling of engine. This helps to
prevent overheating of spark plug insulators and will lessen tendency
for "after-firing."

(3) Check for carburetor heat OFF during idling.

E. TAXIING

(1) Open throttle to start airplane in motion; then close throttle to
a setting sufficient to keep airplane rolling. Do not keep throttle
advanced so that it is necessary to control taxi speed of airplane
with brakes. This causes unnecessary wear and tear on brakes and
tires.

(2) Taxi slowly (speed of a fast walk) controlling direction with
rudder which is connected to a steerable tail wheel. Use brakes only
for positive, precision ground control when necessary.

(3) Taxi upwind with stick back; downwind with stick foreward. When
ground winds are in excess of 15 M.P.H., turn into wind using ailerons
in direction of turn; apply ailerons away from the turn when turning
downwind. This procedure helps to prevent the wind "picking up" a
wing during windy, gusty conditions. Always make ground turns slowly.

F. GENERAL FLYING

(1) For takeoff use full throttle, heading into wind. Airplane loaded
will become airborne at approximately 39 M.P.H. Best climb speed is
an indicated 55 M.P.H.

(2) Indicated R.P.M. for cruising speed of 73 M.P.H. is 2150.
Take-off R.P.M. is 2300. Do not fly at full throttle over 3 minutes.

(3) Use CARBURETOR AIR HEAT when engine runs "rough" and tachometer
shows drop in R.P.M. which may be due to ice forming in carburetor.
Tachometer should recover to within 50 R.P.M. below normal when using
carburetor heat. Push heater to "OFF" position, and if icing
condition has been cleared, R.P.M. should return to normal. Continued
use of carburetor heat will only cause increased fuel consumption and
loss of power.

(4) Maximum permissible diving speed is 122 M.P.H.

G. APPROACH AND LANDING

(1) Push carburetor heat ON prior to throttling back for glide, or for
any other flight maneuver.

(2) Glide between 50-60 M.P.H. depending upon loading of airplane and
gust conditions.

NOTE -- "Clear" engine by opening throttle gently, every 200-250 feet
of descent during a long glide so that engine temperature will be
maintained.

Throttle action on the part of the pilot should be smooth and gentle
at all times.

H. PARKING AND MOORING

(1) After termination of flight, enter flying time in aircraft and
engine log books.

(2) Turn ignition and fuel OFF.

(3) Chcok the wheels of airplane.

(4) If airplane is not to be flown for some time, it should be
hangared or tied down. Use good quality 1/2" - 5/8" diameter rope.
Secure to lift assist handle at aft end of fuselage; also at upper end
of both front wing lift struts where they attach to wing. Make sure
that rope passes between aileron cable and lift strut. Mooring ropes,
when airplane is tied down, should have no slack.

(5) Lock aileron and elevator controls by wrapping front seat belt
completely around rear control stick, tighten and buckle.

(6) Under excessively wind conditions, airplane should be tailed into
wind for mooring.

== Related content ==
[[Piper J3 Cub]]

Piper J3 Cub Operations Manual

2009-04-14T20:09:09Z

Natovr:

{{Mergeto|Piper J3 Cub}}
'''''This article contains material which is suspected of not complying to the GPL Licence version 2. This material is subject to removal.'''''
[This information is copied from the 1946 J3C-65 owner's handbook.]

== FLYING HINTS ==

The Piper Cub Special represents more than 15 years of diligent
aircraft engineering and manufacturing experience. Its simplicity of
design and construction, its low operating and maintenance costs, its
inherent stability, ruggedness, and its outstanding safety and ease of
flying, have made it the most popular airplane in aviation history.
The Piper Cub Special is the time-tested product of millions of hours
of flying under all conceivable conditions both in the military and in
peace time.

There are hints on starting, flying, stopping, and other related
topics that are important to the owner who wants to conserve his
airplane -- keep it in maximum airworthy condition -- and enjoy a full
measure of flying satisfaction.

First, each pilot should become familiar enough with his Piper Cub
Special that he can accomplish a satisfactory pre-flight inspection.
This check is simple and requires only a few minutes. See Section IX
for check list. Daily check of airplane prior to flight should be the
first in a number of safe flying habits the pilot should acquire.

A. BEFORE STARTING ENGINE

(1) Make routine check of gasoline supply. Visible fuel gauge is
integral part of gas tank cap; it will not show number of gallons but
will show proportion of fuel in tank by length of rod which extends
upward from cap. A full tank of 12 U.S. gallons will be indicated by
11 inches of rod extending beyond cap. Keep gas gauge rod clean and
smooth with crocus cloth for accuracy and freedom of movement.

(2) Check oil level in engine sump by removing oil cap and gauge. Oil
stick should indicate oil level up to index mark of 4 quarts.

(3) Check freedom of movement of flight and engine controls.

B. STARTING ENGINE

(1) Chock wheels, or have occupant who is familiar with controls set
brakes in cabin.

(2) Ignition switch OFF. Verify.

(3) Set throttle approximately 1/10 open.

(4) Push fuel shut-off ON.

(5) Turn propeller through several times.

(6) Turn ignition switch ON.

(7) Start engine by pulling propeller through with a snap.

CAUTION -- Always handle propeller as if switch were "ON." Stand as
far in front of propeller as possible. Use both hands and grasp one
blad approximately midway from tip. Do not overgrasp blade. Do not
wear long, loose clothing. Make sure footing is sure to preclude
possibility of feet slipping.

(8) If engine does not start, turn switch OFF. Turn primer knob to
unlock, pull out, pump three or four times, then reseat primer and
lock by turning in opposite direction. In extremely cold weather a
few strokes of the primer as the engine starts will enable it to keep
running. NOTE -- Avoid excessive priming as it causes raw gasoline to
wash lubricating oil from engine cylinder walls. Do not prime warm
engine.

(9) Repeat starting procedures 6, 7.

(10) If engine loads up and refuses to start, turn ignition switch
"OFF,", open throttle wide and turn propeller through backwards
several times to unload excessive gas mixture in cylinders. Then
close throttle and repeat starting procedure.

C. ENGINE WARM-UP

(1) As soon as engine starts, advance throttle slightly to idle at 700
R.P.M. Check engine instruments. If oil pressure gauge does not
indicate pressure within 30 seconds, stop engine immediately, check
and correct trouble before any further operation. Oil temperature
during operating should not rise above 200° F. and oil pressure should
not fall below 30 pounds. With engine warm, idling speed should be
550-600 R.P.M.

(2) Rev engine up to 2100 R.P.M. on both magnetos. Switch to LEFT and
RIGHT magnetos. R.P.M. drop should not be over 75 R.P.M. CAUTION
--Do not operate engine on either single magneto for more than 30
seconds at a time, as this tends to foul the non-operating spark plugs
in the ignition circuit of the magneto that is switched off.

D. STOPPING ENGINE

(1) Never cut switch immediately after landing as this causes engine
to cool too rapidly.

(2) Idle engine, especially in high temperature operating conditions,
for several minutes. It is advisable to switch to each magneto for 30
second intervals to allow gradual cooling of engine. This helps to
prevent overheating of spark plug insulators and will lessen tendency
for "after-firing."

(3) Check for carburetor heat OFF during idling.

E. TAXIING

(1) Open throttle to start airplane in motion; then close throttle to
a setting sufficient to keep airplane rolling. Do not keep throttle
advanced so that it is necessary to control taxi speed of airplane
with brakes. This causes unnecessary wear and tear on brakes and
tires.

(2) Taxi slowly (speed of a fast walk) controlling direction with
rudder which is connected to a steerable tail wheel. Use brakes only
for positive, precision ground control when necessary.

(3) Taxi upwind with stick back; downwind with stick foreward. When
ground winds are in excess of 15 M.P.H., turn into wind using ailerons
in direction of turn; apply ailerons away from the turn when turning
downwind. This procedure helps to prevent the wind "picking up" a
wing during windy, gusty conditions. Always make ground turns slowly.

F. GENERAL FLYING

(1) For takeoff use full throttle, heading into wind. Airplane loaded
will become airborne at approximately 39 M.P.H. Best climb speed is
an indicated 55 M.P.H.

(2) Indicated R.P.M. for cruising speed of 73 M.P.H. is 2150.
Take-off R.P.M. is 2300. Do not fly at full throttle over 3 minutes.

(3) Use CARBURETOR AIR HEAT when engine runs "rough" and tachometer
shows drop in R.P.M. which may be due to ice forming in carburetor.
Tachometer should recover to within 50 R.P.M. below normal when using
carburetor heat. Push heater to "OFF" position, and if icing
condition has been cleared, R.P.M. should return to normal. Continued
use of carburetor heat will only cause increased fuel consumption and
loss of power.

(4) Maximum permissible diving speed is 122 M.P.H.

G. APPROACH AND LANDING

(1) Push carburetor heat ON prior to throttling back for glide, or for
any other flight maneuver.

(2) Glide between 50-60 M.P.H. depending upon loading of airplane and
gust conditions.

NOTE -- "Clear" engine by opening throttle gently, every 200-250 feet
of descent during a long glide so that engine temperature will be
maintained.

Throttle action on the part of the pilot should be smooth and gentle
at all times.

H. PARKING AND MOORING

(1) After termination of flight, enter flying time in aircraft and
engine log books.

(2) Turn ignition and fuel OFF.

(3) Chcok the wheels of airplane.

(4) If airplane is not to be flown for some time, it should be
hangared or tied down. Use good quality 1/2" - 5/8" diameter rope.
Secure to lift assist handle at aft end of fuselage; also at upper end
of both front wing lift struts where they attach to wing. Make sure
that rope passes between aileron cable and lift strut. Mooring ropes,
when airplane is tied down, should have no slack.

(5) Lock aileron and elevator controls by wrapping front seat belt
completely around rear control stick, tighten and buckle.

(6) Under excessively wind conditions, airplane should be tailed into
wind for mooring.

== Related content ==
[[Piper J3 Cub]]

FGCom (before 3.0)

2009-03-09T17:58:51Z

Natovr: /* Status */

{{cleanup}}

'''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'''):
**invite friends to a guided sightseeing tour in your most beloved area or do “Fly In's”
**do military training like “midair tanking”, “Dog fights”, “Escort flights”, etc.
*offering additional services at an airport like ATC, Snowplows, Pushbacks, etc. (Visit e.g. KSFO on a weekend – sorry enough: Most communication is still by keyboard - we are sure that will change!)
*have a real time flightraing (e.g. pilot in Hongkong, teacher in Sydney) or just ask for online 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 plan 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.
In the future FGCom surely will extend further and surley will get a “Speech to Text” capability in order to also use the Text-based standard ATC-routines inside FlightGear (see also [[Development]]).

==Status==
*'''March, 2009:'''
<div style="font-size:150%">'''This wiki-Page is undergoing a Major Revision'''</div>

Since the new version Nov.2008 the usage of FGCom is picking up rapidly – but so are also the confusions of many “Computer-Non-Professionals” trying to use it. We hope to help users by adding many more user-specific informations, like e.g. installation on different Operating Systems, testing, operating, informing, and “how to get the most out of it”. The existing more tech. Informations will remain but will be restructured. We decided to do it online in the “wiki-fashion” so that others can benefit as soon as possible.
This major update will take about a month (or 2).

--[[User:Jomo|Jomo]] 12:46, 3 March 2009 (EST)

*'''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 down due to hardware problems. It is unknown when the service comes back becuase 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===
====Prequisites and Companions====
ToBeDefined

====Install on Linux====
Fetch FGCom (a copy of a working iaxclient is inside)

svn checkout svn://svn.dfn.de:/fgcom/trunk fgcom

Optional: edit iaxclient/lib/Makefile

To use OpenAl (Recommended and the default for now. Note however, that it requires OpenAl with capture support.)

USE_PA_OSS=0
USE_PA_ALSA=0
USE_PA_JACK=0
AUDIO_ALSA=0
AUDIO_OPENAL=1

To use oss emulation

USE_PA_OSS=1
USE_PA_ALSA=0
USE_PA_JACK=0
AUDIO_ALSA=0
AUDIO_OPENAL=0

To use native alsa (WARNING: PTT won't work)

USE_PA_OSS=0
USE_PA_ALSA=0
USE_PA_JACK=0
AUDIO_ALSA=1
AUDIO_OPENAL=0

To use portaudio alsa (WARNING: only if your card natively supports 8000Hz sample rate)

USE_PA_OSS=0
USE_PA_ALSA=1
USE_PA_JACK=0
AUDIO_ALSA=0
AUDIO_OPENAL=0

Edit fgcom/src/Makefile and check the pathes for PLIB_PREFIX and OPENAL_PREFIX.

Compile iaxclient and fgcom. To do so, do the following:

cd fgcom/src && make

Install

make install

and you should be ready for a quick test...

====Install on Windows====
ToBeDefined
====Install on Mac====
ToBeDefined

===Testing===
====Test the basic function====
''(The often so called "-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 of a "cvs" installation you have to replace "fgcom" with "sh ./run_fgcom.sh". Then type:

$ fgcom -Sfgcom.flightgear.org.uk -f910

 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.
 Then type <nowiki>ctrl-C</nowiki> to exit this Quick-Test

 '''In case of trouble''' check the following:

*'''"parsed commandline options"''' not successful: Check for wrong commands and/or missing “-” signs in front of them. See [[FGCOM#FGCom Options|FGcom Options]].
*'''"Reading list of airports .."''' not succesfull: 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 erros, allthough 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.
*If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].
--[[User:Jomo|Jomo]] 01:01, 7 March 2009 (EST)

====Solving Audio-Problems====
Before you start, make sure that your headset is (or speakers and microphone are) working and tested to sensible volumes. Headsets are strongly recommended in order to avoid feedback resonances, which could affect not only you but all fellow listeners with awful or even painful noises.
You may test your Audio-Devices using the basically installed Utilities of your operating system. e.g.: type into a command line for:
#Linux: "gnome-sound-recorder", (you may also check on: Linux software audio mixing with FlightGear)
#Windows: "audiorecorder"
#Mac: ???

more Tests / TestSetups etc. ToBeDefined

====Final Tests====
ToBeDefined

===Using FGCom===
ToBeDefined
====Tips and Tricks====
ToBeDefined

===Supplemantery Informations===
====Commandline Parameters====

''Or if it didn't work perfectly first time''

fgcom --help

returns the following useful info

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

OPTION DESCRIPTION

-d, -debug, --debug= show debugging information
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')
-s, -fgserver, --fgserver= fg to connect to (default: 'localhost')
-p, -port, --port= where we should listen to FG (default: '16661')
-a, -airport, --airport= airport-id (ICAO) for ATC-mode
-f, -frequency, --frequency= frequency for ATC-mode
-U, -user, --user= username for VoIP account (default: 'guest')
-P, -password, --password= password for VoIP account (default: 'guest')
-i, -mic, --mic= mic input level (0.0 - 1.0)
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)
-b, -mic-boost, --mic-boost= enable mic boost
-l, -list-audio, --list-audio= list audio devices
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')

Available codecs:
u - ulaw (default and best codec because the mixing is based onto ulaw)
a - alaw
g - gsm
s - speex
7 - G.723

Mode 1: client for COM1 of flightgear:
$ fgcom
- connects fgcom to fgfs at localhost:16661
$ fgcom -sother.host.tld -p23456
- connects fgcom to fgfs at other.host.tld:23456

Mode 2: client for an ATC at <airport> on <frequency>:
$ fgcom -aKSFO -f120.500
- sets up fgcom for an ATC radio at KSFO 120.500 MHz

Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!

Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''

==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.

===Prerequirements===

Install Asterisk on top of your favorite distribution. Please refer to installation manuals (e.g. [[http://www.asteriskguru.com/|Asterisk-Guru]]) you can find on the net. You do not need H.323 or SIP because the fgcom client uses IAX2 as VoIP signaling protocol. Only if you think about connecting external VoIP applications to FGCOM you should consider to activate H.323 or SIP (but this is not the scope of this small howto).

Notice: You need to install the zaptel driver modules - even if you won't use any hardware for telecom interfacing. You need the ztdummy kernel module for the asterisk conference application MeetMe() because it simulates a hardware clock needed by this application. Further development of FGCOM might use app_conference which don't needs any timing device.

For now we want to use /etc/asterisk as the base configuration directory.

===Setting up the radio frequencies===

The radio frequencies are "simple" Conferences and realized due to the Asterisk application MeetMe().

====Part 1: General configuration====

First you have to set up the general configuration of the system. Put the following at the top of your "extensions.conf" file:

[general]
static=yes
writeprotect=yes
;
[globals]
;
[macro-com]
exten => s,1,Answer()
exten => s,n,MeetMe(${MACRO_EXTEN},qd)
exten => s,n,Hangup()
;
[macro-echo]
exten => s,1,Answer()
exten => s,n,Echo()
exten => s,n,Hangup()
;
[guest]
; ATC-Help
exten => 01-ZZZZ-911.000,1,Macro(com)
exten => 012525252591100,1,Dial(Local/01-ZZZZ-911.000)
exten => 01-ZZZZ-910.000,1,Macro(echo)
exten => 012525252591000,1,Dial(Local/01-ZZZZ-910.000)
;
[default]
include => guest
;
; Code:
; 01 - FlightGear
; 02 - Microsoft Flight-Simulator
; 03 - ...
;
; Air2Air
exten => 01-ZZZZ-123.450,1,Macro(com)
exten => 012525252512345,1,Dial(Local/01-ZZZZ-123.450)
exten => 01-ZZZZ-122.750,1,Macro(com)
exten => 012525252512275,1,Dial(Local/01-ZZZZ-122.750)

====Part 2: Adding your favorite (all?) frequencies====

For this you have simply to create an extension for every touple of airport/frequency in extensions.conf. The following is an example for Berlin-Tempelhof (EDDI). The information comes from the file "apt.dat.gz" of your FlightGear installation.

; EDDI ATIS 126.020 - Berlin Tempelhof
exten => 01-EDDI-126.020,1,Macro(com)
exten => 010403030812602,1,Dial(Local/01-EDDI-126.020)
;
; EDDI BERLIN DEP 120.620 - Berlin Tempelhof
exten => 01-EDDI-120.620,1,Macro(com)
exten => 010403030812062,1,Dial(Local/01-EDDI-120.620)
;
; EDDI BERLIN DIRECTOR 121.120 - Berlin Tempelhof
exten => 01-EDDI-121.120,1,Macro(com)
exten => 010403030812112,1,Dial(Local/01-EDDI-121.120)
;
; EDDI BERLIN ARR 126.420 - Berlin Tempelhof
exten => 01-EDDI-126.420,1,Macro(com)
exten => 010403030812642,1,Dial(Local/01-EDDI-126.420)
;
; EDDI GND 121.950 - Berlin Tempelhof
exten => 01-EDDI-121.950,1,Macro(com)
exten => 010403030812195,1,Dial(Local/01-EDDI-121.950)
;
; EDDI TWR 119.570 - Berlin Tempelhof
exten => 01-EDDI-119.570,1,Macro(com)
exten => 010403030811957,1,Dial(Local/01-EDDI-119.570)
;
; EDDI BERLIN DIRECTOR 136.100 - Berlin Tempelhof
exten => 01-EDDI-136.100,1,Macro(com)
exten => 010403030813610,1,Dial(Local/01-EDDI-136.100)
;
; EDDI TWR 118.100 - Berlin Tempelhof
exten => 01-EDDI-118.100,1,Macro(com)
exten => 010403030811810,1,Dial(Local/01-EDDI-118.100)
;
; EDDI BERLIN DEP 119.500 - Berlin Tempelhof
exten => 01-EDDI-119.500,1,Macro(com)
exten => 010403030811950,1,Dial(Local/01-EDDI-119.500)
;
; EDDI BERLIN ARR 119.620 - Berlin Tempelhof
exten => 01-EDDI-119.620,1,Macro(com)
exten => 010403030811962,1,Dial(Local/01-EDDI-119.620)

What does the above mean? There are two lines (three with the comment) for each frequency: The first one sets up an extension named "01-EDDI-119.500". Yes, for VoIP you can use textual extensions but be careful if you want to setup your Asterisk-Server with POTS (=Plain old telephone service). Therefor you need the second line which is the same as above but without dashes and the letters in the decimal representation of the ASCII Code. The second line does only a "rewrite" of the numerical representation to the textual one.

For setting up all airports you can write your own simple script. But this maybe also not needed in further versions of FGCOM.

After editing the extensions.conf file you have to reload the extensions file (e.g. "asterisk -rx extensions reload").

You can add further nice goodies to your extensions.conf: MorseCode() for morsing the code of the VOR (MorseCode() will only work in Asterisk >= 1.4), Recording of metar data and playing this recording back when using the frequency of the metar information, ...

===Setting up user accounts===

The user accounts are located in the file iax.conf (and perhaps also in sip.conf, but this is not necessary). The top of the file should look like this:

[general]
bandwith=low
disallow=lpc10
jitterbuffer=yes
forcejitterbuffer=no
tos=lowdelay
autokill=yes
disallow=all
allow=alaw
allow=gsm
allow=ilbc
allow=g726
allow=ulaw
language=en
maxauthreq=10
context=guest
;
[guest]
type=user
username=guest
context=guest
qualify=yes
callerid=Guest IAX User
host=dynamic
;

You may want to disallow more codecs or want to allow additional codecs (such as speex). But have in mind that the internal mixing of the conferences are done in "ulaw". But "ulaw" needs about 80 kBit/s because it does no compression. So you have to think about what's better for you: less bandwidth (per user) and more CPU usage or more bandwidth (per user) and less CPU usage... you should also consider the "sound" of some codecs may not have the 'real radio sound'.

For each user you have to add a bunch of lines to your iax.conf file:

[<USERNAME>]
type=user
username=<USERNAME>
secret=<PASSWORD>
context=default
host=dynamic
nat=yes
notransfer=yes

You just have to fill in the <USERNAME> and <PASSWORD>. After each change you have to reload the configuration (e.g. "asterisk -rx reload chan_iax2.so"). Perhaps you want to write scripts for automatic configuration and so on. But be warned: Further versions of fgcom may use the multiplayer servers for getting usernames and position data and you have to change your scripts.

===Problems?===

If you have problems you can contact me via email at "dcoredump AT gmail.com".

==External links==
* [http://squonk.abacab.org/dokuwiki/fgcom Official website]
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]

==Development==

TODO

==See also==
*[[FlightGear related projects]]

[[Category:Software]]

Understanding Propeller Torque and P-Factor

2009-03-04T08:21:11Z

Natovr:

This is an attempt to answer the frequent question "Why is my aircraft turning left all the time?"

This occurs only in aircraft with propellers at the front of the aircraft. And, yes, it does occur in real life. Three distinct phenomena cause the effect, all causing the aircraft to turn in the same direction. They are:

==Prop wash==
A propeller pushes air not just horizontally to the back, but more in a twisting helix around the [http://en.wikipedia.org/wiki/Fuselage fuselage] (clockwise as seen from the cockpit). As the air whirls around the fuselage it pushes against the left side of the vertical tail, causing the plane to yaw to the left. The prop wash effect is at its greatest when the airflow is flowing more around the fuselage than along it, i.e., at high power and low airspeed, which is the situation when starting the takeoff run.

==Propeller Torque Effect==

Torque effect is the influence of engine torque on aircraft movement and control. It is generally exhibited as a left turning tendency in piston single engine propeller driven aircraft.

According to Newton's law, "for every action there is an equal and opposite reaction," such that the propeller, if turning clockwise (when viewed from the cockpit), imparts a tendency for the aircraft to rotate counterclockwise. Since most single engine aircraft have propellers rotating clockwise, they rotate to the left, pushing the left wing down.

Typically, the pilot is expected to counter this force through the control inputs. To counter the aircraft roll left, the pilot applies right aileron.

It is important to understand that torque is a movement about the roll axis. Aileron controls roll. Prop torque is not countered by moving the rudder or by setting rudder trim. It is countered by moving or trimming the aileron.

This correction induces adverse yaw, which is corrected by moving or trimming the rudder (right rudder).

On aircraft with contrarotating propellers (propellers that rotate in opposite directions) the torque from the two propellers cancel each other out, so that no compensation is needed.

Further Reading: [http://www.aerospaceweb.org/question/dynamics/q0015a.shtml Propeller Torque Factor]

== P-Factor ==

P-factor is the term for asymmetric propeller loading, causes the airplane to yaw to the left when at high angles of attack.

The descending right side of the propeller (as seen from the rear) has a higher angle of attack than the upward-moving blade on the left side and provides more thrust. This occurs only when the propeller is not meeting the oncoming airflow head-on, for example when an aircraft is moving down the runway at a nose-high attitude (i.e. at a high angle of attack), as is the case with tail-draggers. Aircraft with tricycle landing gear maintain a level attitude on the takeoff run, so there is little P-factor during takeoff. In all cases, though, the effect is weaker than prop wash.

According to What You Need to Know About Aerodyanics... by Franklin Gutierrez.

== Gyroscopic Precession ==

This is the tedency of a spinning object to precess or move about its axis when disturbed by a force. The engine and propeller act as a big gyroscope. However, gyroscopic precession is likely to be minimal in a typical aircraft.

Gyroscopic precession is frequenly confused with p-factor.

One author maintains p-factor is caused by a combination of factors unrelated to gyroscopic precession http://home.earthlink.net/~x-plane/FAQ-Theory-PFactor.html

== External Links ==

* [http://www.auf.asn.au/groundschool/umodule11.html#tophenomena Engine effects and aerodynamic phenomena] Recreational Aviation Australia Ground School article on "prop wash," prop torque, gyro precession, p-factor and other similar factors affecting taildraggers.

* [http://www.americanparagliding.com/propellerforces.htm http://www.americanparagliding.com/propellerforces.htm] The forces of P-factor, gyro precession and asymmetric blade thrust act with particular intensity in powere parachute gliders (paragliders), as this article relates.

{{Understanding}}

Princess Juliana International Airport

2009-03-01T15:17:21Z

Natovr: /* FlightGear Community */ The link is redirected.. not any more, though

{{infobox Airport
|name = Princess Juliana International Airport
|image =TNCM.jpg
|alt =Low approach of a [[Boeing 747-400]] at TNCM.
|iata =SXM
|icao =TNCM
|type =Public
|owner =Princess Juliana Int'l Airport Holding Company N.V.
|city =Sint Maarten (St. Martin)
|runway= 10/28
|length= 2350 m
|material= Asphalt
|website =http://www.pjiae.com
}}
'''Princess Juliana International Airport''' (IATA: '''SXM''', ICAO: '''TNCM''') serves the [[Dutch]] part of the island of Saint Martin. It is the second busiest airport in the Eastern Caribbean, after Luis Muñoz Marín International Airport in San Juan, Puerto Rico. It is named after Juliana of the Netherlands, who was crown princess when the airport opened.

== Runway ==
The airport is famous for its short runway — at only 2,180 metres (7,200 ft), it is barely long enough for heavy jets to land. Therefore, incoming airplanes approaching the island on short final for Runway 10 have to fly extremely low, passing only 10-20 meters (30-60 ft.) over relaxing tourists on Maho Beach.

==Scenery==
Princess Juliana Airport is available from the [[FlightGear Scenery Database|scenemodels database]], located on tile w070n10.

==FlightGear Community==
[[Pilots of the Caribbean]] use this airport.

==Related==
*[[Suggested Airports]]

[[Category:Airports]]

Space Shuttle (FG Space Program)

2009-03-01T15:15:39Z

Natovr: /* Development status/Issues/Todo */ Altidude.. hehehe

{{infobox Aircraft
|image =shuttle.jpg
|name =Space Shuttle
|type =
|fdm =JSBSim
|status =Development
|authors =Jon S. Berndt (FDM)
|fgname=<tt>shuttle-jsbsim</tt>
}}
NASA's '''Space Shuttle''', officially called the '''Space Transportation System''' ('''STS'''), is the spacecraft currently used by the United States government for its human spaceflight missions.

Space Shuttle Enterprise is on display at the [[National Air and Space Museum]].

== Development status/Issues/Todo ==
'''Outside:'''
* aircraft has no 3d model

'''Cockpit:'''
* 3d cockpit is not available

'''General:'''
* no hud available
* Because the shuttle is a glider without engines after re-entry, the initial starting position should be somewhere at an altitude of over 80000 feet

==Resources==
* http://www.shuttlepresskit.com/scom/scom.pdf

== Related content ==
*[[Shuttle Landing Facility‎]]
*[[Table of models]]
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Aircraft TODO]]

Howto:Understand console output

2009-03-01T15:07:56Z

Natovr: /* Warning: Picked up TriangleIntersect */ Yes, to alert :)

'''This document is intended to list common [[FlightGear]] errors and how to get rid of them.'''

===Could not find at least one of the following objects for animation:===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings.

===Error: bind() failed in make_server_socket()===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

===Failed to find .... in apt.dat.gz===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports IATA code (like KSFO).

===Failed to open file ...===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

===FGMultiplayMgr::MP_ProcessData: No such file or directory===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

===Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

===Near camera not rendering===
[[Image:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

===OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source.===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[FlightGear CVS|CVS]] version or solve the problem yourself and let someone commit the patch.

===OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data.===
Disabling sound is a temporarily solution for this problem.

===The system cannot find the file specified===
If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again.

'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.

===Unable to choose requested pixel format===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

===Unknown exception to the main loop. Aborting... Possible cause: No such file or directory===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug might provide some more information on what FlightGear was doing when the error occurred.
Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.

===Warning: Picked up TriangleIntersect===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. The errors might still be shown, but do not affect the game anymore.

[[Category:Howto|Get rid of common errors]]

Boeing 777-200

2009-02-28T17:06:37Z

Natovr:

''This includes the following models: '''777-200''', '''777-200ER'''''

{{infobox Aircraft
|image =777-200.jpg
|name =Boeing 777-200
|type =Airliner
|livery =Air India, British Airways, Delta Air Lines, [[Island Virtual Airways]], Lufthansa
|authors =Justin Smithies and Syd Adams
|fdm =YASim
|status =Development
|fgname =<tt>777-200</tt>
}}
[[Image:Cockpit.jpg|thumb|270px|The 3D [[cockpit]] of a 777-200]]
The '''777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).

The direct equivalent from Airbus is the [[Airbus A330-300]]. A total of 88 -200s have been delivered to ten different customers as of July 2008.

You can see a guide on how to fly this plane on [[User:Vaeronic|Vaeron's wikipage]]

==Related content==
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ]
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]

Boeing 777

2009-02-28T17:05:00Z

Natovr:

[[Image:777-200.jpg|thumb|270px|[[Boeing 777-200]] in British Airways livery]]

The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.

As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350|A350 XWB]], which is currently under development. The 777 may eventually be replaced by a new product family, the [[Boeing Y3]], which would draw upon technologies from the [[Boeing 787|787]].

You can see a guide on how to fly this plane on [[User:Vaeronic|Vaeron's wikipage]]

==Variants==
* [[Boeing 777-200]]
==Related==
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ]

{{Boeing}}

Howto:Install scenery

2009-02-28T13:44:50Z

Natovr:

= Terrain =

You can download [[World Scenery]] 1.0.1 terrain from the FlightGear site : http://www.flightgear.org/Downloads/scenery-1.0.1.html

To install the scenery just extract (uncompress) the tar.gz archive file in the $FG_ROOT/Scenery directory (under Win32, using a tool such as for example [http://www.izarc.org/ izArc] or [http://www.7-zip.org/ 7-Zip]), preserving all directory structures in the file. The Scenery will be installed automatically.
You can use fgadmin to uninstall added scenery.

There is also a 4 DVD set available for download via BitTorent,
which can be a higher performance option for those wanting
to download the entire world:
http://www.torrentbox.com/download/59050/FlightGear_4_DVD_Disk-set.torrent

== Installing Scenery ==

In your FG_ROOT directory you would find the following directores
<pre>
./Translations
./Protocol
./Textures
./Timezone
./Airports
./gui
./Aircraft-uiuc
./Scenery
./Traffic
...
</pre>

The Scenery directory will show the following:-
(Scenery is shown for completeness and for easy reference to above)

<pre>
Scenery/
w130n30/
Terrain/
Objects/
</pre>

If you download a scenery module called w90n40.tgz from [[http://flightgear.org/Downloads/scenery-1.0.1.html flightgear.org]] then it will resemble something like the following:-

<pre>
Scenery/
'''w09n40/'''
w130n30/
Terrain/
Objects/
</pre>

Note the extra directory in bold.

TODO : Windows decompression help.

== Objects ==
Objects and models can be found at the [http://scenemodels.flightgear.org/ FlightGear Scenery Objects Database]

Objects are really part of the scenery and can be found in the Scenery directory under $FG_ROOT.

<pre>
Scenery/
Objects/
w130n30/
</pre>

Any objects should be installed under the Scenery/Objects directory

= Technical =
Scenery for FlightGear is determined by looking at the environment variable $FG_SCENERY. Should the paths in $FG_SCENERY not be valid, FlightGear falls back to $FG_ROOT/scenery.

Mixing scenery types is almost universally a bad idea, and is unsupported. In this connection you should note that the scenery packaged with the base package/windows installer may not be the latest scenery.

For this reason it's probably better to extract scenery files you've downloaded into a new folder, which we'll call, for the sake of this exercise, $FOOBAR/Scenery
In this directory, create two subdirectories . /Objects and /Terrain. You should untar individual files into the /Terrain folder.

Then you should set up $FG_SCENERY to use the new path:
On POSIX Clients
set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY
On Windows (fgrun)
Go back to the first page of fgrun, and add the $FOOBAR/Scenery folder to the list.

= Downloading From Mirrors =
A list of mirrors can be found here: http://www.flightgear.org/mirrors.html#ftp
 
On most of the mirrors, the latest scenery can be found under "Scenery-1.0.0/" Downloading from mirrors is often better than the official site, because mirrors are sometimes faster and have more user capacity. Use the graphical interface ( http://www.flightgear.org/Downloads/scenery-1.0.0.html ) and use the link locations to find the appropriate chunk. 
Be careful about confusing N with S, and E with W!! 
Here is how to find an airport's co-ordinates: 

* Go to the Wikipedia page for the airport in question (for example, PHNL for Honolulu)
* Find the co-ordinates (often at the top or right and side, marked with a small globe)
* e.g. PHNL is in 21 N 157 W. If it's in the western hemisphere, you should round it up... so you should find the block with W160N20 If the co-ords were 21 N 157 E, you would round it '''down'''.. meaning that this location would be E150N20.

= TerraSync =

TerraSync is a utility that automatically downloads needed FlightGear scenery while the simulator is running.

It is recommended to use a separate scenery directory for TerraSync (that is do not run it on your main scenery directory).

Usage example (for POSIX compliant [[command line]] shell):

Start terrasync:

<code>% nice terrasync -p 5500 -d /tmp/fgfsScenery</code>

Start FlightGear:

<code>% fgfs --atlas=socket,out,1,localhost,5500,udp --fg-scenery=$FG_ROOT/Scenery/:/tmp/fgfsScenery</code>

The full documentation and source for TerraSync is located in the FlighGear source distribution (in <code>utils/TerraSync/</code>).

TODO: More info

=See also=
* [[FlightGear Admin Wizard|FGAdmin]]
* [[Installing Aircraft]]
* [[Scenery FAQ]]

[[Category:Scenery]]

Building FlightGear - Linux

2008-12-30T10:18:24Z

Natovr: /* APT-GET List */

__TOC__

This section describes how to build FlightGear on Linux system.

Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.

'''October 29th 2006, Flightgear CVS MAIN Branch switched to OSG support.'''
Plib support remains available in CVS using PRE_OSG_PLIB_20061029 Branch.
(cvs up -rPRE_OSG_PLIB_20061029)

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

'''C++ compiler'''

These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.

'''CVS'''

Yes, the program is called 'CVS'. This is used for downloading the latest set of source code. Windows developers may wish to see [[Using TortoiseCVS with FlightGear]].

'''[[OpenGL]] support'''

More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running:

glxinfo | grep direct

Note: To run the above command, you need to have the tool '''mesa-utils''' installed.

You should then see:

direct rendering: Yes

This means you are good to go as far as OpenGL support is concerned.

If you see:

direct rendering: No

Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib1.8.4 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.

== Dependencies ==
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.

The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.

* FlightGear
** [http://openal.org OpenAL and ALUT]
** SimGear
*** [http://plib.sourceforge.net/ PLIB] (until version 0.9.10 release sources, PRE_OSG_PLIB_20061029 CVS branch). Since march 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.
**** For versions pre march/2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since march 2008, FreeGLUT as well as SDL are both considered depreciated in CVS/HEAD, please only use --enable-osgviewer during configuration instead])
*** [[ OpenSceneGraph ]] (svn trunk)
**** libfreetype6-dev
**** libjpeg62-dev
**** libungif4-dev
**** libtiff4-dev
**** libpng12-dev
**** libxmu-dev
**** libxi-dev

If you attack the above dependencies in the order listed below, you should be good:

1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.

2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution.

3. Plib - portability libraries and scene graph.

4. [[ OpenSceneGraph ]]

5. SimGear - Simulation support libraries. If you are building FlightGear from CVS, you need the CVS version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.

==== APT-GET List ====
This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. It is a list of all the libraries you and your computer needs to compile FG, SG, OSG, and PLib. All you have to do is copy the full command, paste it in Terminal, enter your password, and it will download all the packages for you, and install them too. The full command is at the bottom, and I hope someone finds it useful :) sub-dependencies (dependencies of the dependencies) are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it.

cvs - to get SG and FG 
subversion - to get OSG 
build-essential - to build (includes GCC, and other build tools) 
cmake - OSG Uses this 
libpng-dev - to enable FG to use PNG textures 
libfreetype6-dev - fonts 
libjpeg-dev 
libungif4-dev 
libtiff-dev 
libxmu-dev 
libxi-dev 
libalut-dev - sound 
libboost-dev - makes coding for some developers easier 
automake - needed by ./autogen.sh files 
autoconf - needed by ./autogen.sh files 
libfltk1.1-dev - You will need this if you will be using FGRun 
-----------
<pre>
sudo apt-get install cvs subversion build-essential cmake libpng-dev libfreetype6-dev libjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev
libalut-dev libboost-dev automake autoconf libfltk1.1-dev
</pre>
-----------
Total size is about 230 MB, depending on what you already have from other applications.

This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command.

== Compiling ==
Assuming you are root, do:
cd /usr/local/src

Note: When tracking a fast changing software like FlightGear/CVS it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.

=== Getting and compiling SimGear ===

'''Step 1:'''

Login to the cvs server and checkout the latest version of SimGear's source code with:
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source

'''Step 2:'''

Since all the source code will be downloaded into a directory called '''source''', you will need to rename the directory into something more meaningful.

Rename the above directory by doing:
mv source simgear

Next, go into the directory and make preparations for the compilation:
cd simgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command

'''Step 3:'''

Compile and install SimGear by doing:
make; make install.

''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like:

'<anonymous>' has incomplete type
take a look at http://bugs.gentoo.org/166723

=== Getting and compiling FlightGear ===

'''Step 1:'''

To login to the cvs version and checkout the latest version of Flightgear's source code, use:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source

A directory with the name '''source''' will then be created with all of Flightgear's source code downloaded into it.

'''Step 2:'''

To rename the above directory, use the following command:
mv source flightgear

Next, go into the folder and make preparations for the compilation:
cd flightgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you are building the OSG-version of FlightGear and didn't install OSG globally, you have to pass the OSG directory to the configure-command like this:
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/source/build.osg --enable-osgviewer
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
export LD_LIBRARY_PATH=/path/to/fgInstallation/lib:$LD_LIBRARY_PATH

'''Step 3:'''

Now you can compile and install Flightgear by:
make; make install

'''Step 4:'''

Get the data directory:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data

And install it in (or as) /usr/local/share/FlightGear
mv data /usr/local/share/FlightGear

== External links ==
=== Instructions ===
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 10.2 ]]
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X (0.9.10 and CVS)]

{{Building}}

''If you are lost see [[Portal:User]] or [[Portal:Developer]]''

Main Page

2008-12-28T13:27:16Z

Natovr:

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:56%; color:#000"| 
{| style="width:70%; border:solid 0px; background:none;"
|style="width:500px; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the FlightGear Wiki,</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">we now have [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>
|}
|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[Help:Tutorial|Editing]] '''·''' [[Help:Contents|Help]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|All pages]] '''·''' [[Special:Search|Search]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Flight Simulator</h2>
|-
|style="color:#000;"|
[[Image:FGlogo.jpg|left]] '''[[FlightGear]] Flight Simulator''' is an open-source flight simulator completely (including source) created by volunteers. Source code for the entire project is available from a [[CVS]] repository and licensed under [[GNU General Public License]]. FlightGear 1.9 was released on 22nd of December 2008.

The goals of the [[FlightGear]] project include creating a sophisticated flight simulator framework for use in research or academic environments, for the development and pursuit of other interesting flight simulation ideas, and as an end-user application. It can be expanded and improved upon by anyone interested in [[Volunteer|contributing]], and has many [[FlightGear related projects|related projects]] ([http://www.flightgear.org/links.html projects]).

FlightGear comes with a set of illustrated documentation, notably "The Manual", which is available as [http://mapserver.flightgear.org/getstart.pdf PDF] and [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. The FlightGear Wiki was started in 2006 and currently covers a wide range of FlightGear related topics.

'''Please choose a portal:'''
* [[Portal:User|User]]
* [[Portal:Developer|Developer]]

===== '''If you are new, please check the [[Help:Your_first_article|manual]] before you start editing or creating articles!''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Getting Started</h2>
|-
|style="color:#000;"|
* [[New to FlightGear ]]
* [[FAQ ]]
* [[Troubleshooting Problems ]]
* [[Howto: Multiplayer|Multiplayer Setup]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Using FlightGear</h2>
|-
|style="color:#000;"|
* [[Aircraft]]
* [[Flying the helicopter|Helicopter flying]]
* [[Table of models]]
'''[[Portal:User|More...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">News</h2>
|-
|style="color:#000;"|
* '''December 22 2008:''' FlightGear 1.9 released
* '''October 27th 2008:''' [[World Scenery 1.01]] released
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Developing FlightGear</h2>
|-
|style="color:#000;"|
* [[Portal:Developer/Scenery|Scenery Development Portal]]
* [[Portal:Developer/Aircraft|Aircraft Development Portal]]
* [[Building_terragear-cs_in_Ubuntu_64|Building Terragear in Ubuntu]]
* [[FlightGear Package Manager]]
'''[[Portal:Developer|More...]]'''
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Picture of the week</h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Did you know...</h2>
|-
|style="color:#000;"|
* ...that you can toggle the [[menubar]] on or off by pressing F10, and even change the GUI style by pressing Shift + F10?
* ...that you can now walk through some of the aircraft cabins?
* ...that FlightGear's first release was in July 1997. FlightGear is over 11 years old!

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

Main Page

2008-12-28T13:21:39Z

Natovr: twenty-secoth?

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:56%; color:#000"| 
{| style="width:70%; border:solid 0px; background:none;"
|style="width:500px; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the FlightGear Wiki,</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">we now have [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>
|}
|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[Help:Tutorial|Editing]] '''·''' [[Help:Contents|Help]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|All pages]] '''·''' [[Special:Search|Search]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Flight Simulator</h2>
|-
|style="color:#000;"|
[[Image:FGlogo.jpg|left]] '''[[FlightGear]] Flight Simulator''' is an open-source flight simulator completely (including source) created by volunteers. Source code for the entire project is available from a [[CVS]] repository and licensed under [[GNU General Public License]]. FlightGear 1.9 was released on 22nd of December 2008.

The goals of the [[FlightGear]] project include creating a sophisticated flight simulator framework for use in research or academic environments, for the development and pursuit of other interesting flight simulation ideas, and as an end-user application. It can be expanded and improved upon by anyone interested in [[Volunteer|contributing]], and has many [[FlightGear related projects|related projects]] ([http://www.flightgear.org/links.html projects]).

FlightGear comes with a set of illustrated documentation, notably "The Manual", which is available as [http://mapserver.flightgear.org/getstart.pdf PDF] and [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. The FlightGear Wiki was started in 2006 and currently covers a wide range of FlightGear related topics.

'''Please choose a portal:'''
* [[Portal:User|User]]
* [[Portal:Developer|Developer]]

===== '''If you are new, please check the [[Help:Your_first_article|manual]] before you start editing or creating articles!''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Getting Started</h2>
|-
|style="color:#000;"|
* [[New to FlightGear ]]
* [[FAQ ]]
* [[Troubleshooting Problems ]]
* [[Howto: Multiplayer|Multiplayer Setup]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Using FlightGear</h2>
|-
|style="color:#000;"|
* [[Aircraft]]
* [[Flying the helicopter|Helicopter flying]]
* [[Table of models]]
'''[[Portal:User|More...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">News</h2>
|-
|style="color:#000;"|
* '''December 22 2008:''' FlightGear 1.9 released
* '''October 27th 2008:''' [[World Scenery 1.01]] released
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Developing FlightGear</h2>
|-
|style="color:#000;"|
* [[Portal:Developer/Scenery|Scenery Development Portal]]
* [[Portal:Developer/Aircraft|Aircraft Development Portal]]
* [[Building_terragear-cs_in_Ubuntu_64|Building Terragear in Ubuntu]]
* [[FlightGear Packet Manager]]
'''[[Portal:Developer|More...]]'''
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Picture of the week</h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Did you know...</h2>
|-
|style="color:#000;"|
* ...that you can toggle the [[menubar]] on or off by pressing F10, and even change the GUI style by pressing Shift + F10?
* ...that you can now walk through some of the aircraft cabins?
* ...that FlightGear's first release was in July 1997. FlightGear is over 11 years old!

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

Building FlightGear - Linux

2008-12-28T13:16:24Z

Natovr: /* APT-GET List */ plib-dev shouldn't be in there

__TOC__

This section describes how to build FlightGear on Linux system.

Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.

'''October 29th 2006, Flightgear CVS MAIN Branch switched to OSG support.'''
Plib support remains available in CVS using PRE_OSG_PLIB_20061029 Branch.
(cvs up -rPRE_OSG_PLIB_20061029)

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

'''C++ compiler'''

These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.

'''CVS'''

Yes, the program is called 'CVS'. This is used for downloading the latest set of source code. Windows developers may wish to see [[Using TortoiseCVS with FlightGear]].

'''[[OpenGL]] support'''

More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running:

glxinfo | grep direct

Note: To run the above command, you need to have the tool '''mesa-utils''' installed.

You should then see:

direct rendering: Yes

This means you are good to go as far as OpenGL support is concerned.

If you see:

direct rendering: No

Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib1.8.4 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.

== Dependencies ==
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.

The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.

* FlightGear
** [http://openal.org OpenAL and ALUT]
** SimGear
*** [http://plib.sourceforge.net/ PLIB] (until version 0.9.10 release sources, PRE_OSG_PLIB_20061029 CVS branch). Since march 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.
**** For versions pre march/2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since march 2008, FreeGLUT as well as SDL are both considered depreciated in CVS/HEAD, please only use --enable-osgviewer during configuration instead])
*** [[ OpenSceneGraph ]] (svn trunk)
**** libfreetype6-dev
**** libjpeg62-dev
**** libungif4-dev
**** libtiff4-dev
**** libpng12-dev
**** libxmu-dev
**** libxi-dev

If you attack the above dependencies in the order listed below, you should be good:

1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.

2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution.

3. Plib - portability libraries and scene graph.

4. [[ OpenSceneGraph ]]

5. SimGear - Simulation support libraries. If you are building FlightGear from CVS, you need the CVS version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.

==== APT-GET List ====
This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. The fill command is at the bottom, and I hope someone finds it useful :) sub-dependencies are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it.

cvs - to get SG and FG 
subversion - to get OSG 
build-essential - to build (includes GCC, and other build tools) 
cmake - OSG Uses this 
libpng-dev - to enable FG to use PNG textures 
libfreetype6-dev - fonts 
libjpeg-dev 
libungif4-dev 
libtiff-dev 
libxmu-dev 
libxi-dev 
libalut-dev - sound 
libboost-dev - makes coding for some developers easier 
automake - needed by ./autogen.sh files 
autoconf - needed by ./autogen.sh files 
libfltk1.1-dev - You will need this if you will be using FGRun 
-----------
sudo apt-get install cvs subversion build-essential cmake libpng-dev libfreetype6-dev libjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev
libalut-dev libboost-dev automake autoconf libfltk1.1-dev
-----------
Total size is about 230 MB, depending on what you already have from other applications.

This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command.

== Compiling ==
Assuming you are root, do:
cd /usr/local/src

Note: When tracking a fast changing software like FlightGear/CVS it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.

=== Getting and compiling SimGear ===

'''Step 1:'''

Login to the cvs server and checkout the latest version of SimGear's source code with:
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source

'''Step 2:'''

Since all the source code will be downloaded into a directory called '''source''', you will need to rename the directory into something more meaningful.

Rename the above directory by doing:
mv source simgear

Next, go into the directory and make preparations for the compilation:
cd simgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command

'''Step 3:'''

Compile and install SimGear by doing:
make; make install.

''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like:

'<anonymous>' has incomplete type
take a look at http://bugs.gentoo.org/166723

=== Getting and compiling FlightGear ===

'''Step 1:'''

To login to the cvs version and checkout the latest version of Flightgear's source code, use:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source

A directory with the name '''source''' will then be created with all of Flightgear's source code downloaded into it.

'''Step 2:'''

To rename the above directory, use the following command:
mv source flightgear

Next, go into the folder and make preparations for the compilation:
cd flightgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you are building the OSG-version of FlightGear and didn't install OSG globally, you have to pass the OSG directory to the configure-command like this:
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/source/build.osg --enable-osgviewer
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
export LD_LIBRARY_PATH=/path/to/fgInstallation/lib:$LD_LIBRARY_PATH

'''Step 3:'''

Now you can compile and install Flightgear by:
make; make install

'''Step 4:'''

Get the data directory:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data

And install it in (or as) /usr/local/share/FlightGear
mv data /usr/local/share/FlightGear

== External links ==
=== Instructions ===
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 10.2 ]]
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X (0.9.10 and CVS)]

{{Building}}

''If you are lost see [[Portal:User]] or [[Portal:Developer]]''

Building FlightGear - Linux

2008-12-28T13:14:52Z

Natovr: /* APT-GET List */ Full stops

__TOC__

This section describes how to build FlightGear on Linux system.

Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.

'''October 29th 2006, Flightgear CVS MAIN Branch switched to OSG support.'''
Plib support remains available in CVS using PRE_OSG_PLIB_20061029 Branch.
(cvs up -rPRE_OSG_PLIB_20061029)

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

'''C++ compiler'''

These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.

'''CVS'''

Yes, the program is called 'CVS'. This is used for downloading the latest set of source code. Windows developers may wish to see [[Using TortoiseCVS with FlightGear]].

'''[[OpenGL]] support'''

More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running:

glxinfo | grep direct

Note: To run the above command, you need to have the tool '''mesa-utils''' installed.

You should then see:

direct rendering: Yes

This means you are good to go as far as OpenGL support is concerned.

If you see:

direct rendering: No

Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib1.8.4 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.

== Dependencies ==
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.

The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.

* FlightGear
** [http://openal.org OpenAL and ALUT]
** SimGear
*** [http://plib.sourceforge.net/ PLIB] (until version 0.9.10 release sources, PRE_OSG_PLIB_20061029 CVS branch). Since march 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.
**** For versions pre march/2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since march 2008, FreeGLUT as well as SDL are both considered depreciated in CVS/HEAD, please only use --enable-osgviewer during configuration instead])
*** [[ OpenSceneGraph ]] (svn trunk)
**** libfreetype6-dev
**** libjpeg62-dev
**** libungif4-dev
**** libtiff4-dev
**** libpng12-dev
**** libxmu-dev
**** libxi-dev

If you attack the above dependencies in the order listed below, you should be good:

1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.

2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution.

3. Plib - portability libraries and scene graph.

4. [[ OpenSceneGraph ]]

5. SimGear - Simulation support libraries. If you are building FlightGear from CVS, you need the CVS version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.

==== APT-GET List ====
This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. The fill command is at the bottom, and I hope someone finds it useful :) sub-dependencies are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it.

cvs - to get SG and FG 
subversion - to get OSG 
build-essential - to build (includes GCC, and other build tools) 
cmake - OSG Uses this 
libpng-dev - to enable FG to use PNG textures 
libfreetype6-dev - fonts 
libjpeg-dev 
libungif4-dev 
libtiff-dev 
libxmu-dev 
libxi-dev 
libalut-dev - sound 
libboost-dev - makes coding for some developers easier 
automake - needed by ./autogen.sh files 
autoconf - needed by ./autogen.sh files 
libfltk1.1-dev - You will need this if you will be using FGRun 
-----------
sudo apt-get install cvs subversion build-essential cmake libpng-dev plib-dev libfreetype6-dev libjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev
libalut-dev libboost-dev automake autoconf libfltk1.1-dev
-----------
Total size is about 230 MB, depending on what you already have from other applications.

This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command.

== Compiling ==
Assuming you are root, do:
cd /usr/local/src

Note: When tracking a fast changing software like FlightGear/CVS it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.

=== Getting and compiling SimGear ===

'''Step 1:'''

Login to the cvs server and checkout the latest version of SimGear's source code with:
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source

'''Step 2:'''

Since all the source code will be downloaded into a directory called '''source''', you will need to rename the directory into something more meaningful.

Rename the above directory by doing:
mv source simgear

Next, go into the directory and make preparations for the compilation:
cd simgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command

'''Step 3:'''

Compile and install SimGear by doing:
make; make install.

''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like:

'<anonymous>' has incomplete type
take a look at http://bugs.gentoo.org/166723

=== Getting and compiling FlightGear ===

'''Step 1:'''

To login to the cvs version and checkout the latest version of Flightgear's source code, use:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source

A directory with the name '''source''' will then be created with all of Flightgear's source code downloaded into it.

'''Step 2:'''

To rename the above directory, use the following command:
mv source flightgear

Next, go into the folder and make preparations for the compilation:
cd flightgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you are building the OSG-version of FlightGear and didn't install OSG globally, you have to pass the OSG directory to the configure-command like this:
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/source/build.osg --enable-osgviewer
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
export LD_LIBRARY_PATH=/path/to/fgInstallation/lib:$LD_LIBRARY_PATH

'''Step 3:'''

Now you can compile and install Flightgear by:
make; make install

'''Step 4:'''

Get the data directory:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data

And install it in (or as) /usr/local/share/FlightGear
mv data /usr/local/share/FlightGear

== External links ==
=== Instructions ===
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 10.2 ]]
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X (0.9.10 and CVS)]

{{Building}}

''If you are lost see [[Portal:User]] or [[Portal:Developer]]''

Building FlightGear - Linux

2008-12-28T13:14:00Z

Natovr: /* APT-GET List */ Still a bit too big :|

__TOC__

This section describes how to build FlightGear on Linux system.

Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.

'''October 29th 2006, Flightgear CVS MAIN Branch switched to OSG support.'''
Plib support remains available in CVS using PRE_OSG_PLIB_20061029 Branch.
(cvs up -rPRE_OSG_PLIB_20061029)

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

'''C++ compiler'''

These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.

'''CVS'''

Yes, the program is called 'CVS'. This is used for downloading the latest set of source code. Windows developers may wish to see [[Using TortoiseCVS with FlightGear]].

'''[[OpenGL]] support'''

More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running:

glxinfo | grep direct

Note: To run the above command, you need to have the tool '''mesa-utils''' installed.

You should then see:

direct rendering: Yes

This means you are good to go as far as OpenGL support is concerned.

If you see:

direct rendering: No

Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib1.8.4 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.

== Dependencies ==
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.

The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.

* FlightGear
** [http://openal.org OpenAL and ALUT]
** SimGear
*** [http://plib.sourceforge.net/ PLIB] (until version 0.9.10 release sources, PRE_OSG_PLIB_20061029 CVS branch). Since march 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.
**** For versions pre march/2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since march 2008, FreeGLUT as well as SDL are both considered depreciated in CVS/HEAD, please only use --enable-osgviewer during configuration instead])
*** [[ OpenSceneGraph ]] (svn trunk)
**** libfreetype6-dev
**** libjpeg62-dev
**** libungif4-dev
**** libtiff4-dev
**** libpng12-dev
**** libxmu-dev
**** libxi-dev

If you attack the above dependencies in the order listed below, you should be good:

1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.

2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution.

3. Plib - portability libraries and scene graph.

4. [[ OpenSceneGraph ]]

5. SimGear - Simulation support libraries. If you are building FlightGear from CVS, you need the CVS version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.

==== APT-GET List ====
This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. The fill command is at the bottom, and I hope someone finds it useful :) sub-dependencies are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it

cvs - to get SG and FG 
subversion - to get OSG 
build-essential - to build (includes GCC, and other build tools) 
cmake - OSG Uses this 
libpng-dev - to enable FG to use PNG textures 
libfreetype6-dev - fonts 
libjpeg-dev 
libungif4-dev 
libtiff-dev 
libxmu-dev 
libxi-dev 
libalut-dev - sound 
libboost-dev - makes coding for some developers easier 
automake - needed by ./autogen.sh files 
autoconf - needed by ./autogen.sh files 
libfltk1.1-dev - You will need this if you will be using FGRun 
-----------
sudo apt-get install cvs subversion build-essential cmake libpng-dev plib-dev libfreetype6-dev libjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev
libalut-dev libboost-dev automake autoconf libfltk1.1-dev
-----------
Total size is about 230 MB, depending on what you already have from other applications

This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command

== Compiling ==
Assuming you are root, do:
cd /usr/local/src

Note: When tracking a fast changing software like FlightGear/CVS it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.

=== Getting and compiling SimGear ===

'''Step 1:'''

Login to the cvs server and checkout the latest version of SimGear's source code with:
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source

'''Step 2:'''

Since all the source code will be downloaded into a directory called '''source''', you will need to rename the directory into something more meaningful.

Rename the above directory by doing:
mv source simgear

Next, go into the directory and make preparations for the compilation:
cd simgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command

'''Step 3:'''

Compile and install SimGear by doing:
make; make install.

''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like:

'<anonymous>' has incomplete type
take a look at http://bugs.gentoo.org/166723

=== Getting and compiling FlightGear ===

'''Step 1:'''

To login to the cvs version and checkout the latest version of Flightgear's source code, use:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source

A directory with the name '''source''' will then be created with all of Flightgear's source code downloaded into it.

'''Step 2:'''

To rename the above directory, use the following command:
mv source flightgear

Next, go into the folder and make preparations for the compilation:
cd flightgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you are building the OSG-version of FlightGear and didn't install OSG globally, you have to pass the OSG directory to the configure-command like this:
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/source/build.osg --enable-osgviewer
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
export LD_LIBRARY_PATH=/path/to/fgInstallation/lib:$LD_LIBRARY_PATH

'''Step 3:'''

Now you can compile and install Flightgear by:
make; make install

'''Step 4:'''

Get the data directory:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data

And install it in (or as) /usr/local/share/FlightGear
mv data /usr/local/share/FlightGear

== External links ==
=== Instructions ===
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 10.2 ]]
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X (0.9.10 and CVS)]

{{Building}}

''If you are lost see [[Portal:User]] or [[Portal:Developer]]''

Building FlightGear - Linux

2008-12-28T13:13:34Z

Natovr: /* APT-GET List */ Title is too big

__TOC__

This section describes how to build FlightGear on Linux system.

Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.

'''October 29th 2006, Flightgear CVS MAIN Branch switched to OSG support.'''
Plib support remains available in CVS using PRE_OSG_PLIB_20061029 Branch.
(cvs up -rPRE_OSG_PLIB_20061029)

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

'''C++ compiler'''

These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.

'''CVS'''

Yes, the program is called 'CVS'. This is used for downloading the latest set of source code. Windows developers may wish to see [[Using TortoiseCVS with FlightGear]].

'''[[OpenGL]] support'''

More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running:

glxinfo | grep direct

Note: To run the above command, you need to have the tool '''mesa-utils''' installed.

You should then see:

direct rendering: Yes

This means you are good to go as far as OpenGL support is concerned.

If you see:

direct rendering: No

Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib1.8.4 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.

== Dependencies ==
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.

The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.

* FlightGear
** [http://openal.org OpenAL and ALUT]
** SimGear
*** [http://plib.sourceforge.net/ PLIB] (until version 0.9.10 release sources, PRE_OSG_PLIB_20061029 CVS branch). Since march 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.
**** For versions pre march/2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since march 2008, FreeGLUT as well as SDL are both considered depreciated in CVS/HEAD, please only use --enable-osgviewer during configuration instead])
*** [[ OpenSceneGraph ]] (svn trunk)
**** libfreetype6-dev
**** libjpeg62-dev
**** libungif4-dev
**** libtiff4-dev
**** libpng12-dev
**** libxmu-dev
**** libxi-dev

If you attack the above dependencies in the order listed below, you should be good:

1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.

2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution.

3. Plib - portability libraries and scene graph.

4. [[ OpenSceneGraph ]]

5. SimGear - Simulation support libraries. If you are building FlightGear from CVS, you need the CVS version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.

=== APT-GET List ===
This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. The fill command is at the bottom, and I hope someone finds it useful :) sub-dependencies are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it

cvs - to get SG and FG 
subversion - to get OSG 
build-essential - to build (includes GCC, and other build tools) 
cmake - OSG Uses this 
libpng-dev - to enable FG to use PNG textures 
libfreetype6-dev - fonts 
libjpeg-dev 
libungif4-dev 
libtiff-dev 
libxmu-dev 
libxi-dev 
libalut-dev - sound 
libboost-dev - makes coding for some developers easier 
automake - needed by ./autogen.sh files 
autoconf - needed by ./autogen.sh files 
libfltk1.1-dev - You will need this if you will be using FGRun 
-----------
sudo apt-get install cvs subversion build-essential cmake libpng-dev plib-dev libfreetype6-dev libjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev
libalut-dev libboost-dev automake autoconf libfltk1.1-dev
-----------
Total size is about 230 MB, depending on what you already have from other applications

This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command

== Compiling ==
Assuming you are root, do:
cd /usr/local/src

Note: When tracking a fast changing software like FlightGear/CVS it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.

=== Getting and compiling SimGear ===

'''Step 1:'''

Login to the cvs server and checkout the latest version of SimGear's source code with:
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source

'''Step 2:'''

Since all the source code will be downloaded into a directory called '''source''', you will need to rename the directory into something more meaningful.

Rename the above directory by doing:
mv source simgear

Next, go into the directory and make preparations for the compilation:
cd simgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command

'''Step 3:'''

Compile and install SimGear by doing:
make; make install.

''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like:

'<anonymous>' has incomplete type
take a look at http://bugs.gentoo.org/166723

=== Getting and compiling FlightGear ===

'''Step 1:'''

To login to the cvs version and checkout the latest version of Flightgear's source code, use:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source

A directory with the name '''source''' will then be created with all of Flightgear's source code downloaded into it.

'''Step 2:'''

To rename the above directory, use the following command:
mv source flightgear

Next, go into the folder and make preparations for the compilation:
cd flightgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you are building the OSG-version of FlightGear and didn't install OSG globally, you have to pass the OSG directory to the configure-command like this:
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/source/build.osg --enable-osgviewer
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
export LD_LIBRARY_PATH=/path/to/fgInstallation/lib:$LD_LIBRARY_PATH

'''Step 3:'''

Now you can compile and install Flightgear by:
make; make install

'''Step 4:'''

Get the data directory:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data

And install it in (or as) /usr/local/share/FlightGear
mv data /usr/local/share/FlightGear

== External links ==
=== Instructions ===
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 10.2 ]]
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X (0.9.10 and CVS)]

{{Building}}

''If you are lost see [[Portal:User]] or [[Portal:Developer]]''

Building FlightGear - Linux

2008-12-28T13:13:08Z

Natovr: /* Dependencies */ Added APT-GET List

__TOC__

This section describes how to build FlightGear on Linux system.

Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.

'''October 29th 2006, Flightgear CVS MAIN Branch switched to OSG support.'''
Plib support remains available in CVS using PRE_OSG_PLIB_20061029 Branch.
(cvs up -rPRE_OSG_PLIB_20061029)

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

'''C++ compiler'''

These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.

'''CVS'''

Yes, the program is called 'CVS'. This is used for downloading the latest set of source code. Windows developers may wish to see [[Using TortoiseCVS with FlightGear]].

'''[[OpenGL]] support'''

More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running:

glxinfo | grep direct

Note: To run the above command, you need to have the tool '''mesa-utils''' installed.

You should then see:

direct rendering: Yes

This means you are good to go as far as OpenGL support is concerned.

If you see:

direct rendering: No

Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib1.8.4 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.

== Dependencies ==
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.

The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.

* FlightGear
** [http://openal.org OpenAL and ALUT]
** SimGear
*** [http://plib.sourceforge.net/ PLIB] (until version 0.9.10 release sources, PRE_OSG_PLIB_20061029 CVS branch). Since march 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.
**** For versions pre march/2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since march 2008, FreeGLUT as well as SDL are both considered depreciated in CVS/HEAD, please only use --enable-osgviewer during configuration instead])
*** [[ OpenSceneGraph ]] (svn trunk)
**** libfreetype6-dev
**** libjpeg62-dev
**** libungif4-dev
**** libtiff4-dev
**** libpng12-dev
**** libxmu-dev
**** libxi-dev

If you attack the above dependencies in the order listed below, you should be good:

1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.

2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution.

3. Plib - portability libraries and scene graph.

4. [[ OpenSceneGraph ]]

5. SimGear - Simulation support libraries. If you are building FlightGear from CVS, you need the CVS version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.

= APT-GET List =
This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. The fill command is at the bottom, and I hope someone finds it useful :) sub-dependencies are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it

cvs - to get SG and FG 
subversion - to get OSG 
build-essential - to build (includes GCC, and other build tools) 
cmake - OSG Uses this 
libpng-dev - to enable FG to use PNG textures 
libfreetype6-dev - fonts 
libjpeg-dev 
libungif4-dev 
libtiff-dev 
libxmu-dev 
libxi-dev 
libalut-dev - sound 
libboost-dev - makes coding for some developers easier 
automake - needed by ./autogen.sh files 
autoconf - needed by ./autogen.sh files 
libfltk1.1-dev - You will need this if you will be using FGRun 
-----------
sudo apt-get install cvs subversion build-essential cmake libpng-dev plib-dev libfreetype6-dev libjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev
libalut-dev libboost-dev automake autoconf libfltk1.1-dev
-----------
Total size is about 230 MB, depending on what you already have from other applications

This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command

== Compiling ==
Assuming you are root, do:
cd /usr/local/src

Note: When tracking a fast changing software like FlightGear/CVS it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.

=== Getting and compiling SimGear ===

'''Step 1:'''

Login to the cvs server and checkout the latest version of SimGear's source code with:
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 co source

'''Step 2:'''

Since all the source code will be downloaded into a directory called '''source''', you will need to rename the directory into something more meaningful.

Rename the above directory by doing:
mv source simgear

Next, go into the directory and make preparations for the compilation:
cd simgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command

'''Step 3:'''

Compile and install SimGear by doing:
make; make install.

''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like:

'<anonymous>' has incomplete type
take a look at http://bugs.gentoo.org/166723

=== Getting and compiling FlightGear ===

'''Step 1:'''

To login to the cvs version and checkout the latest version of Flightgear's source code, use:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
CVS passwd: guest

cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co source

A directory with the name '''source''' will then be created with all of Flightgear's source code downloaded into it.

'''Step 2:'''

To rename the above directory, use the following command:
mv source flightgear

Next, go into the folder and make preparations for the compilation:
cd flightgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you are building the OSG-version of FlightGear and didn't install OSG globally, you have to pass the OSG directory to the configure-command like this:
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/source/build.osg --enable-osgviewer
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
export LD_LIBRARY_PATH=/path/to/fgInstallation/lib:$LD_LIBRARY_PATH

'''Step 3:'''

Now you can compile and install Flightgear by:
make; make install

'''Step 4:'''

Get the data directory:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data

And install it in (or as) /usr/local/share/FlightGear
mv data /usr/local/share/FlightGear

== External links ==
=== Instructions ===
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 10.2 ]]
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X (0.9.10 and CVS)]

{{Building}}

''If you are lost see [[Portal:User]] or [[Portal:Developer]]''

Howto:Multiplayer

2008-12-22T18:41:20Z

Natovr: /* Using the Windows launcher / fgrun */ Server seems up again

With the '''Multiplayer''' function of [[FlightGear]] you are able to see other pilots and reversed. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate]] drops, during loading of a new aircraft. Especially heavy models will cause lag. Therefore it is suggested to fly in Europe or somewhere other than KSFO where there are fewer pilots flying around.

== Using the Windows launcher / fgrun ==
[[Image:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|Fgrun]]. On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft. Enter the callsign of your choice, enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes. Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong).
You will also notice chat messages that say "Hello" indicating pilots that are online and then as they join.
You may wish to use a different server (i.e. "Hostname" entry);

mpserver01.flightgear.org (in Germany) [T]
mpserver02.flightgear.org (in Hong Kong) [T]
mpserver03.flightgear.org (in Germany) [T] (down 21 Dec)
mpserver04.flightgear.org (UK)
mpserver06.flightgear.org (Sweden) [T] (tracked only on port 5002)

Servers marked with [T] above log all flights in the [http://fgfs.i-net.hu/modules/fgtracker/ FlighGear flight tracker]. Use [http://pigeond.net/flightgear/mpstatus/ this] link to check if the MP servers are online, because the info above can be out of date

'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you or has the lowest latency (ping time).

== Using fgfs from the command line ==

First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,portnumber
--multiplay=in,10,your.ip.address,portnumber
--callsign=anything

Where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. Please note that although this limitation has been removed in the most recent versions of the FG server; you should still specify a valid (non-loopback, i.e. not 127.0.0.1) IP address to keep the FG client happy.

With the latest FlightGear (at least with OSG), you can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

=== Now, going more slowly for those who are completely lost... ===

Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

Under linux, this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"

Under Windows XP, click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.

With Windows 98, click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all(!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=MyName --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver02.flightgear.org,5000 --airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. 

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] and someone should be able to assist.

[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
===Multiplayer Map===
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at http://mpmap02.flightgear.org . You will also find this useful to check that you are successfully connecting to the server.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "View" menu and select "Chat" at the bottom of the menu. Note that the other pilots may not have their chat box open, so they may not see your messages.
NOTE: Multiplayer chat is not supported by FlightGear 0.9.10 or older.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at View -> Chat. So if you think you've missed anything, go check there.

==Related content==
* [[Howto: Set up a multiplayer server]]
* [[FlightGear Multiplayer Server]]

[[Category:Howto|Multiplayer]]

Howto:Multiplayer

2008-12-22T11:06:54Z

Natovr:

With the '''Multiplayer''' function of [[FlightGear]] you are able to see other pilots and reversed. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate]] drops, during loading of a new aircraft. Especially heavy models will cause lag. Therefore it is suggested to fly in Europe or somewhere other than KSFO where there are fewer pilots flying around.

== Using the Windows launcher / fgrun ==
[[Image:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|Fgrun]]. On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft. Enter the callsign of your choice, enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes. Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong).
You will also notice chat messages that say "Hello" indicating pilots that are online and then as they join.
You may wish to use a different server (i.e. "Hostname" entry);

mpserver01.flightgear.org (in Germany) [T]
mpserver02.flightgear.org (in Hong Kong) [T]
mpserver03.flightgear.org (in Germany) [T] (down 21 Dec)
mpserver04.flightgear.org (UK) (down 21 Dec)
mpserver06.flightgear.org (Sweden) [T] (tracked only on port 5002)

Servers marked with [T] above log all flights in the [http://fgfs.i-net.hu/modules/fgtracker/ FlighGear flight tracker]. Use [http://pigeond.net/flightgear/mpstatus/ this] link to check if the MP servers are online, because the info above can be out of date

'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you or has the lowest latency (ping time).

== Using fgfs from the command line ==

First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,portnumber
--multiplay=in,10,your.ip.address,portnumber
--callsign=anything

Where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. Please note that although this limitation has been removed in the most recent versions of the FG server; you should still specify a valid (non-loopback, i.e. not 127.0.0.1) IP address to keep the FG client happy.

With the latest FlightGear (at least with OSG), you can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

=== Now, going more slowly for those who are completely lost... ===

Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

Under linux, this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"

Under Windows XP, click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.

With Windows 98, click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all(!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=MyName --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver02.flightgear.org,5000 --airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. 

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] and someone should be able to assist.

[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
===Multiplayer Map===
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at http://mpmap02.flightgear.org . You will also find this useful to check that you are successfully connecting to the server.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "View" menu and select "Chat" at the bottom of the menu. Note that the other pilots may not have their chat box open, so they may not see your messages.
NOTE: Multiplayer chat is not supported by FlightGear 0.9.10 or older.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at View -> Chat. So if you think you've missed anything, go check there.

==Related content==
* [[Howto: Set up a multiplayer server]]
* [[FlightGear Multiplayer Server]]

[[Category:Howto|Multiplayer]]

Howto:Multiplayer

2008-12-21T22:43:02Z

Natovr: /* Using the Windows launcher / fgrun */

With the '''Multiplayer''' function of [[FlightGear]] you are able to see other pilots and reversed. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate]] drops, during loading of a new aircraft. Especially heavy models will cause lag.

== Using the Windows launcher / fgrun ==
[[Image:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|Fgrun]]. On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft. Enter the callsign of your choice, enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes. Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong).
You will also notice chat messages that say "Hello" indicating pilots that are online and then as they join.
You may wish to use a different server (i.e. "Hostname" entry);

mpserver01.flightgear.org (in Germany) [T]
mpserver02.flightgear.org (in Hong Kong) [T]
mpserver03.flightgear.org (in Germany) [T] (down 21 Dec)
mpserver04.flightgear.org (UK) (down 21 Dec)
mpserver06.flightgear.org (Sweden) [T] (tracked only on port 5002)

Servers marked with [T] above log all flights in the [http://fgfs.i-net.hu/modules/fgtracker/ FlighGear flight tracker]. Use [http://pigeond.net/flightgear/mpstatus/ this] link to check if the MP servers are online, because the info above can be out of date

'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you or has the lowest latency (ping time).

== Using fgfs from the command line ==

First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,portnumber
--multiplay=in,10,your.ip.address,portnumber
--callsign=anything

Where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. Please note that although this limitation has been removed in the most recent versions of the FG server; you should still specify a valid (non-loopback, i.e. not 127.0.0.1) IP address to keep the FG client happy.

With the latest FlightGear (at least with OSG), you can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

=== Now, going more slowly for those who are completely lost... ===

Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

Under linux, this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"

Under Windows XP, click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.

With Windows 98, click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all(!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=MyName --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver02.flightgear.org,5000 --airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. 

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] and someone should be able to assist.

[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
===Multiplayer Map===
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at http://mpmap02.flightgear.org . You will also find this useful to check that you are successfully connecting to the server.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "View" menu and select "Chat" at the bottom of the menu. Note that the other pilots may not have their chat box open, so they may not see your messages.
NOTE: Multiplayer chat is not supported by FlightGear 0.9.10 or older.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at View -> Chat. So if you think you've missed anything, go check there.

==Related content==
* [[Howto: Set up a multiplayer server]]
* [[FlightGear Multiplayer Server]]

[[Category:Howto|Multiplayer]]

FlightGear CVS

2008-12-05T15:47:36Z

Natovr: /* FlightGear and CVS */ the ' only goes AFTER the S if it is plural, otherwise it goes BEFORE the S

In the field of software development, the '''Concurrent Versions System''' ('''CVS'''), also known as the '''Concurrent Versioning System''', provides a version control system based on open-source code. Version control system software keeps track of all work and all changes in a set of files, and allows several developers (potentially widely separated in space and/or time) to collaborate. This means that the newest stuff, which are still in development, are available in CVS before they do in the stable release. CVS has become popular in the open source software world and is released under the [[GNU General Public License]].

==FlightGear and CVS==
[[FlightGear]]'s CVS is available [http://cvs.flightgear.org/viewvc/ here] and can be considered as the most up-to-date version of the flightsimulators source and [[aircraft]]. To run CVS aircraft the user need to use the CVS, to prevent bugs and faults.

===External links===
* [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-cvslogs CVS Changelog] shows all updates made to the CVS repository
* [http://macflightgear.sourceforge.net/home/documents/how-to-build-flightgear-cvs-on-mac-os-x/ How to build FlightGear cvs on Mac OS X]
* [http://www.flightgear.org/cvs/anoncvs.html Instructions for the FlightGear CVS repository]

{{building}}

[[Category:Software]]

Howto:Aerial refueling

2008-11-18T20:01:06Z

Natovr: /* What's possible */

== What's possible ==
At present, there are two tanker [[aircraft]] ([[Boeing KC-135E|KC135-E]] and KA6-D) and several receiving aircraft ([[Douglas A4 Skyhawk|A4F]], [[Grumman A-6E|A-6E]], [[Fairchild A-10|A-10]], [[Grumman F-14 Tomcat|F-14 Tomcat]], [[English Electric Lightning|Lightning]] and [[Northrop T-38|T38]]) capable of in-air refuelling. When flying one of these aircraft in the default scenery area, one can locate the tanker aircraft using air-air [[TACAN]] and/or radar and then receive a full or partial load of fuel by flying in close formation behind the tanker. Refuelling is also possible between aircraft in a [[Howto: Multiplayer|Multiplayer]] session. The KC135 is a boom refueller, while the KA6 has a hose. The A4F and Lightning are both fitted with a probe for hose refuelling while the T38 is fitted with a boom receiver. At the moment, either type can refuel from any tanker, but in the future it is likely that the correct type will have to be used (this has been implemented in CVS).

It is not possible to control the boom position yet.

== Necessary preparations ==
Like the aircraft carriers, AAR is implemented as an "AI scenario". Selecting these normally requires editing the "preferences.xml" file in the flightgear data directory.

There is a shortcut in this case though; simply selecting the Lightning, A4F or T38 should automatically load a scenario containing a tanker, assuming you haven't changed anything in your preferences.xml file.

Assuming this is the case, choose one of the aforementioned aircraft, make sure that "AI models" are enabled and start at [[KSFO]] (the default airport.)

Depending on the scenario, you might see the tanker crossing overhead when the sim starts; if not, don't worry.

== In the cockpit ==
Perhaps the first thing to do after starting the engines if necessary is to select the appropriate TACAN channel if your aircraft is so equipped (the A4F and Lightning both are). For the KC135 (by default used by the Lightning and T38) this is currently "040X", and for the KA6D (used by the A4F) it is "050X". Enter this channel using the relevant dropdown boxes in the "radios" dialogue (from the menus, "equipment/radios" or press control-r).

You should now see the current bearing to the tanker indicated in the nav display of the A4 or the TACAN indicator (green needle) in the Lightning. If the tanker is within range, it will also appear on the radar display of the T38 or Lightning. Take off...

== In the Air ==
Turn to an appropriate heading, guided by the TACAN bearing (you should try a "leading" approach to close in on the tanker) and look for the tanker on the radar or nav. screen. Around 5nm away, you should reduce your speed to around 20kts faster than the tanker (these fly at 280 kts TAS) - a "slow overtake". The KC135 will be visible from about 10nm, the KA6-D, being smaller, just over 1 nm. You should use airbrakes as necessary to keep control of your speed should you find yourself overshooting.

[[Image:KC-135E.jpg|thumb|270px|The KC-135E aircraft with the boom.]]
Close to within 50ft of the tanker (don't get too close, or visual artifacts might hide the boom from view). You should see indication in the cockpit that you are receiving fuel - there is a green light in the A4 fuel gauge, and you should see the indicated tank load increase.

Getting to this stage is not necessarily easy - it can take a lot of practice. As with carrier landings, this is not an easy manoeuver in real life either and there are additional complications in the sim; the tanker, being an AI model, is unaffected by the wind and flies TAS (True Air Speed), while you are flying IAS (Indicated Air Speed) and are affected by the environment. As in real life, your aircraft will also steadily increase in weight as the tanks fill which will affect the trim of the aircraft. (You might find it helpful to use the autothrottle to help control your speed - ctrl-s then Page Up/Down to increase and decrease the set speed.)

Once your tanks are full, or you have taken as much fuel as you wish, close the throttle a little, back away from the tanker and continue your intended flight.

== More advanced topics ==

=== Multiplayer Refuelling ===

Refuelling is possible within a MultiPlayer session given certain conditions. A basic flyable KC135 model is available - the pilot of this aircraft should use the callsign "MOBIL1", "MOBIL2" or "MOBIL3". Other numbers are acceptable, but only these three have A-A TACAN channels assigned. These are 060X, 061X and 062X respectively.

If the receiving aircraft uses a YASim FDM, there are no further complications. Should the receiving aircraft be JSBSim based, the user must make sure that there are no AI tankers in their configuration. This means disabling (commenting out) all refuelling "scenarios" in the relevant aircraft-set.xml and in preferences.xml.

MP refuelling works in exactly the same way as AI refuelling and is a fun challenge. It is best to ensure that your network connection is as free from interruptions as possible; the MP code does a degree of prediction if there is a "blip" in the stream of packets and this can make close formation flight very difficult or even impossible.

''See also [[Chat Menu]]''

=== Selecting Different Scenarios ===

There are several AAR scenarios available in the AI directory. refueling_demo.xml has a KC135 circling near KSFO at 3000ft; refueling_demo_1.xml the KC135 on a North/South towline at 8000ft and refueling_demo_2.xml the KA6D on a similar N/S path but at 8500ft.

These can be selected by several methods; using the --ai-scenario command line option, or by editing preferences.xml.

==== Command line method ====

Add the --ai-scenario option to your usual flightgear command line; e.g. <code>fgfs --aircraft=lightning --ai-scenario=refueling_demo_2</code>

==== Preferences.xml method ====
Use your operating system's search facility to locate this if you don't know where it is). Open preferences.xml in a text editor (e.g. notepad if on windows) and search for the <ai> </ai> tags. Place a line like <code><scenario>refueling_demo</scenario></code> somewhere within the <ai> tags; you should see other scenarios already there too, perhaps commented out : i.e. with <! -- -->

[[Category:Howto|Air-Air Refueling]]

Howto:Multiplayer

2008-11-18T19:59:15Z

Natovr: /* Multiplayer Chat */

With the '''Multiplayer''' function of [[FlightGear]] you are able to see other pilots and reversed. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate]] drops, during loading of a new aircraft. Especially heavy models will cause lag.

== Using the Windows launcher / fgrun ==
[[Image:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|Fgrun]]. On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft. Enter the callsign of your choice, enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes. Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong).
You will also notice chat messages that say "Hello" indicating pilots that are online and then as they join.
You may wish to use a different server (i.e. "Hostname" entry);

mpserver01.flightgear.org (in Germany)
mpserver02.flightgear.org (in Hong Kong) [T]
mpserver03.flightgear.org (in Germany) [T]
mpserver04.flightgear.org (UK)
mpserver06.flightgear.org (Sweden)

Servers marked with [T] above log all flights in the [http://fgfs.i-net.hu/modules/fgtracker/ FlighGear flight tracker].

'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you or has the lowest latency (ping time).

== Using fgfs from the command line ==

First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,portnumber
--multiplay=in,10,your.ip.address,portnumber
--callsign=anything

Where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. Please note that although this limitation has been removed in the most recent versions of the FG server; you should still specify a valid (non-loopback, i.e. not 127.0.0.1) IP address to keep the FG client happy.

With the latest FlightGear (at least with OSG), you can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

=== Now, going more slowly for those who are completely lost... ===

Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

Under linux, this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"

Under Windows XP, click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.

With Windows 98, click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all(!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=MyName --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver02.flightgear.org,5000 --airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. 

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [irc://irc.flightgear.org/flightgear FlightGear IRC channel] and someone should be able to assist.

[[Image:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
===Multiplayer Map===
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at http://mpmap02.flightgear.org . You will also find this useful to check that you are successfully connecting to the server.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "View" menu and select "Chat" at the bottom of the menu. Note that the other pilots may not have their chat box open, so they may not see your messages.
NOTE: Multiplayer chat is not supported by FlightGear 0.9.10 or older.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at View -> Chat. So if you think you've missed anything, go check there.

==Related content==
* [[Howto: Set up a multiplayer server]]
* [[FlightGear Multiplayer Server]]

[[Category:Howto|Multiplayer]]

File:SU-37NvyFront.png

2008-10-27T11:36:07Z

Natovr: uploaded a new version of "Image:SU-37NvyFront.png"

A shot at KSFO of an SU-37 Navy livery

File:SU-37NvyBridge.png

2008-10-27T11:35:13Z

Natovr: uploaded a new version of "Image:SU-37NvyBridge.png"

A few SU-37s on a bridge

File:BlackbirdWith747.png

2008-10-26T16:31:50Z

Natovr: uploaded a new version of "Image:BlackbirdWith747.png"

747 from a blackbird SR71 cockpit

File:DR400SunsetAlps.png

2008-10-26T16:24:38Z

Natovr: uploaded a new version of "Image:DR400SunsetAlps.png"

Alps fly-in event during sunset

File:DR400SunsetAlps.png

2008-10-26T15:44:19Z

Natovr: Alps fly-in event during sunset

Alps fly-in event during sunset

File:BlackbirdWith747.png

2008-10-26T15:38:55Z

Natovr: 747 from a blackbird SR71 cockpit

747 from a blackbird SR71 cockpit

File:SU-37NvyBridge.png

2008-10-26T15:37:02Z

Natovr: A few SU-37s on a bridge

A few SU-37s on a bridge

File:SU-37NvyFront.png

2008-10-26T15:34:39Z

Natovr: A shot at KSFO of an SU-37 Navy livery

A shot at KSFO of an SU-37 Navy livery

Picture of teh day suggestions

2008-10-26T15:25:42Z

Natovr: Picture of teh day suggestions moved to Picture of the day suggestions: Lol.. teh...

#REDIRECT [[Picture of the day suggestions]]

Howto:Fly a helicopter

2008-10-25T10:53:38Z

Natovr: /* Summary */

==Summary==
Helicopters have something called collective. If you increase it you will rotate one way, so you need to increase the tail rotor so you don't spin. You can use rudder pedals or a twisting joystick for this. Helicopters control the RPM by themselves in FG, but not in real life. You're recommended to read the rest of the article if you don't understand.

== Preface ==
'''First:''' in principle everything that applies to real helicopters, applies also to [[FlightGear]]. Fundamental maneuvers are well described on: http://www.cybercom.net/~copters/pilot/maneuvers.html Some details are simplified in FlightGear, in particular the engine handling and some overstresses are not simulated or are without any consequence. In FlightGear it is (up to now) not possible to damage a helicopter in flight.

[[Image:bo105_cockpit.jpg]]

Since the release of version 0.9.10 some improvements have been made to the [[helicopter]] flight model and therefore version 1.0.0 or the CVS version should be used. With these improvements the helicopter flight model of FlightGear should be quite realistic. The only exceptions are “vortex ring conditions”. These occur if you descend too fast and perpendicularly (without forward speed). The heli can get into its own rotor downwash causing the lift to be substantially reduced. Recovering from this condition is possible only at higher altitudes. On the Internet you can find a video of a Seaking helicopter, which got into this condition during a flight demonstration and touched down so hard afterwards that it was completely destroyed.

For all Flightgear helicopters the parameters are not completely optimized and thus the performance data between model and original can deviate slightly. On the hardware side I recommend the use of a “good” [[joystick]]. A joystick without springs is recommended because it will not center by itself. You can have this by modifying (removing the spring) from a normal joystick, or by using a force feedback joystick, with a disconnected voltage supply. Further, the joystick should have a “thrust controller” (throttle). For controlling the tail rotor you should have pedals or at least a twistable joystick, keyboard would be the hard way. ('''hint:''' Flightgear supports more than one joystick attached at the same time.)

If using a mouse it's recommended to turn off the Auto-coordination in the [[FlightGear Wizard]].

== Getting started ==
The number of available helicopters in FlightGear is limited. In my opinion the [[Eurocopter Bo105|Bo105]] is the easiest to fly, since it reacts substantially more directly than other helicopters. Since helicopters get more and more popular in FlightGear, there are many other [[helicopter|helicopters]], all of them have their unique flight behavior.

Once you have loaded FlightGear, take a moment to centralize the controls by moving them around. In particular the collective is often at maximum on startup.

[[Image:s76c_landed.jpg]]

The helicopter is controlled by four functions. The stick (joystick) controls two of them, the inclination of the rotor disc (and thus the inclination of the helicopter) to the right/ left and forwards/back. Together these functions are called “cyclic blade control”. Next there is the “collective blade control”, which is controlled by the thrust controller. This causes a change of the thrust produced by the rotor. Since the powering of the main rotor transfers a torque to the fuselage, this must be compensated by the tail rotor. Since the torque is dependent on the collective and on the flight condition as well as wind can add additional torque on the fuselage, the [[tail rotor]] is also controlled by the pilot using the the pedals. If you push the right pedal, the helicopter turns to the right (!). The pedals are not a steering wheel. Using the pedals you can yaw helicopter around the vertical axis. The number of revolutions of the rotor is kept constant (if possible) by the aircraft.

[[Image:ec135_in_the_air.jpg]]

== Lift-Off ==
First reduce the collective to minimum. To increase the rotor thrust, you have to “pull” the collective. Therefore for minimum collective you have to push the control down (that is the full acceleration position (!) of the thrust controller). Equally, “full power” has the thrust controller at idle. Started the engine with “}”. After few seconds the rotor will start to turn and accelerates slowly. Keep the stick and the pedals approximately centered. Wait until the rotor has finished accelerating. For the Bo105 there is an instruments for engine and rotor speed on the left of the upper row.

Once rotor acceleration is complete, pull the collective very slowly. Keep your eye on the horizon. If the heli tilts or turns even slightly, stop increasing the collective and correct the position/movement with stick and pedals. If you are successful, continue pulling the collective (slowly!).

As the helicopter takes off, increase the collective a little bit more and try to keep the helicopter in a leveled position. The main challenge is reacting to the inadvertent rotating motion of the helicopter with the correct control inputs. Only three things can help you: practice, practice and practice. It is quite common for it to take hours of practice to achieve a halfway good looking hovering flight. Note: The stick position in a stable hover is not the center position of the joystick.

== In the air ==
To avoid the continual frustration of trying to achieve level flight, you may want to try forward flight. After take off continue pulling the collective a short time and then lower the nose a slightly using the control stick. The helicopter will accelerate forward. With forward speed the tail rotor does not have to be controlled as precisely due to the relative wind coming from directly ahead. Altogether the flight behavior in forward flight is quite similar to that of an badly trimmed airplane. The “neutral” position of the stick will depend upon airspeed and collective.

Transitioning from forward flight to hovering is easiest if you reduce speed slowly by raising the nose of the helicopter. At the same time, reduce the collective to stop the helicopter from climbing. As the helicopter slows, “translation lift” is reduced, and you will have to compensate by pulling the collective. When the speed is nearly zero, lower the nose to the position it was when hovering. Otherwise the helicopter will accelerate backwards!

== Back to Earth I ==
To land the helicopter transition to a hover as described above while reducing the altitude using the collective. Briefly before hitting the ground reduce the rate of descent slowly. A perfect landing is achieved if you managed to zero the altitude, speed and descent rate at the same time (gently). However, such landing are extremely difficult. Most pilots perform a hover more or less near to the ground and then decent slowly to the ground. Landing with forward velocity is easier, however you must make sure you don't land with any lateral (sideways) component to avoid a rollover.

[[Image:bo105_landed.jpg]]

== Back to Earth II ==
It is worth mentioning autorotation briefly. This is an unpowered flight condition, where the flow of air through the rotors rotates the rotor itself. At an appropriate altitude select a landing point (at first in the size of a larger airfield) and then switch the engine off by pressing "{". Reduce collective to minimum, place the tail rotor to approximately 0 degrees incidence (with the Bo push the right pedal about half , with Russian or French helicopters (like the [[Aérospatiale Alouette II|Alouette 2]]) the left). Approach at approximately 80 knots. Don't allow the rotor speed to rise more than a few percent over 100%, otherwise the rotor will be damaged (though this is not currently simulated). As you reach the ground, reduce the airspeed by lifting the nose. The descent rate will drop at the same time, so you do not need to pull the collective. It may be the case that the rotor speed rises beyond the permitted range. Counteract this by raising the collective if required. Just above the ground, reduce the descent rate by pulling the collective. The goal is it to touch down with a very low descent rate and no forward speed. With forward speed it is easier, but there is a danger of a roll over if the skids are not aligned parallel to the flight direction. During the approach it is not necessary to adjust the tail rotor, since without power there is almost no torque. If you feel (after some practice), that autorotation is too easy, try it with a more realistic payload via the payload menu.

[[Image:bo105_auto.jpg]]

'''Much fun with the Flightgear helicopters!'''

FGCom (before 3.0)

2008-10-20T17:19:50Z

Natovr: /* Registration */ Anti-spam stuff

{{cleanup}}

'''FGCom''' is an addon for [[FlightGear]]. With FGCom (and the infrastructure behind), FlightGear gets a realtime voice communication system. Which could be used for [[ATC]].

==Status==
* '''19 June, 2008:''' '''Currently the server is down due to hardware problems. It is unknown when the service comes back becuase 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!

==Installation==
Before you start, make sure that your speakers and mic are working and tested to sensible volumes.
===Linux===
Fetch FGCom (a copy of a working iaxclient is inside)

svn checkout svn://svn.dfn.de:/fgcom/trunk fgcom

Optional: edit iaxclient/lib/Makefile

To use oss emulation (recommended and the default for now)

USE_PA_OSS=1
USE_PA_ALSA=0
USE_PA_JACK=0
AUDIO_ALSA=0

To use native alsa (WARNING: PTT won't work)

USE_PA_OSS=0
USE_PA_ALSA=0
USE_PA_JACK=0
AUDIO_ALSA=1

To use portaudio alsa (WARNING: only if your card natively supports 8000Hz sample rate)

USE_PA_OSS=0
USE_PA_ALSA=1
USE_PA_JACK=0
AUDIO_ALSA=0

Edit fgcom/src/Makefile and check the pathes for PLIB_PREFIX and OPENAL_PREFIX.

Compile iaxclient and fgcom. To do so, do the following:

cd fgcom/src && make

Install

make install

and you should be ready for a quick test...

==Using==
===Testing===
quick test

$ fgcom -f910

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.1.0 build 42

Using iaxclient library Version SVN 42

Reading list of airports...done.

Initializing IAX client as guest:xxxxxxxxxxx@fgcom1.parasitstudio.de

Call 0 accepted

Echo-Box

Call 0 answered

speak into the mic and your words will be echoed back with a short delay.

type <nowiki>ctrl-C</nowiki> to exit this test

===Configuration===

''Or if it didn't work perfectly first time''

fgcom --help

returns the following useful info

fgcom - a communication radio based on VoIP with IAX/Asterisk

(c)2007 by H. Wirtz <wirtz@dfn.de>

Version 1.1.0 build 42

Using iaxclient library Version SVN 42

fgcom: unrecognized option `--help'

Usage: fgcom [-u user] -w [password] [[-s voipserver] [-p port]] | [[-a airport] [-f frequency]] [-d]

====Account options====
FGCom starts with a guest account unless you use -U and -P!

--user | -U username for VoIP account (default: 'guest')
--password | -P password for VoIP account (default: 'guest')
--voipserver | -s voip server to ceonnect to (default 'localhost')
--port | -p where we should listen to FG(default '16661')

====ATC mode options====
--airport | -a airport-id (ICAO) for ATC-mode
--frequency | -f frequency for ATC-mode

====Audio options====
--mic | -i mic input level (0.0 - 1.0)
--speaker | -o speaker output level (0.0 - 1.0)
--mic-boost | -b enable mic boost
--list-audio | -l list audio devices
--set-audio-in | -r use <devicename> as audio input
--set-audio-out | -k use <devicename> as audio output

====Misc options====
--debug | -d show debugging information

Mode 1: client for COM1 of flightgear:

$ fgcom

- connects fgcom to fgfs at localhost:16661

$ fgcom -sother.host.tld -p23456

- connects fgcom to fgfs at other.host.tld:23456

Mode 2: client for an ATC at <airport> on <frequency>:

$ fgcom -aKSFO -d120.500

- sets up fgcom for an ATC radio at KSFO 120.500 MHz

===Registration===
'''To make full use of FGCOM you will need an account!'''

Please email <nowiki> wirtz <at> dfn <dot> de</nowiki> (replace with @ and .) and login details will be sent to you shortly. Accounts will not be made until Autumn 2008. But you can test without an account (by default the used account is guest, password guest) with restricted frequency use. As guest you can only use the following frequencies:

* 911.000 MHz (ATC-Help)
* 910.000 MHz (Echo-Box)
* 123.450 MHz (Air2Air 1)
* 122.750 Mhz (Air2Air 2)

==External links==
* [http://squonk.abacab.org/dokuwiki/fgcom Official website]
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]

[[Category:Software]]

Modeling - SketchUp

2008-10-11T10:36:47Z

Natovr: /* Manual */ Funny

On this wikipage I'll add some information about placing objects from SketchUp into FlightGear. The page is not done, so don't worry.

Anybody who would, please feel free to add.
==Download==
===SketchUp===
You can download a free version of SketchUp at http://sketchup.google.com. But as far as I know you need the Pro version to convert models into .3ds or .obj. A free demo version is found at http://www.sketchup.com/?sid=509.
----
===Blender===
Download Blender for free through http://www.blender.org/download/get-blender/.

==Automatic Export==
An experimental SketchUp plugin to export directly to .ac format - and works with the free version of SketchUp, as well as pro. See [[SketchUp to AC3D exporter]] for the latest information about the exporter, including current issues and limitations.

==Manual==
'''This only works in Sketchup Pro, because the 3D exporter in the free version only lets you export to .kmz and .kml'''
===1. SketchUp===
After you modeled a building, bridge or tower etc., you need to be sure that the units are in meters. To check this, go to Window > Model Info > Units. Format should be Decimal and Meters. Then, go in SketchUp to File > Export > 3D Model and choose the file format .obj (or any other format that is supported by Blender, I use the .obj format in this tutorial, but other formats will look like this). Save that file somewhere on your computer where you can find it later on (maybe your desktop?).
----
===2. Blender===
[[Image:Modeling_SketchUp_1.jpg|thumb|300px|The .obj import window]]
Open Blender and remove the kubus with Delete. Go to File > Import > Wavefront object (.obj). Select your .obj file we've just saved and click on Import a Wavefront OBJ. Choose for Clamp scale: 0.00 and press OK. This is very important to get the right scale of the model!
Select your model through the A-key and go to File > Export > AC3D (.ac). Save the file in the coordinate-folder where your model is placed. The folder for the Empire State Building is w073n40. But in that folder we must place an other folder called 1745064. That's the tile-id of the scenery in FlightGear. You can find that one through the [[UFO from the 'White Project' of the UNESCO|UFO]]. Fly to your location (use Location from the menubar) and go to File > Internal properties > Environment. There should be a property called current-tile-id. That's your tile-id.

'''Find the long-, alt- and latitude of your building with''' http://www.gpscoordinates.eu/determine-gps-coordinates.php.
----
===3. Textures===
To view the textures in FlightGear we need to give them the .rgb extension. You could use the free programm Gimp to do it. You'll find your textures in a map on the same location on your computer as where you stored the .obj file. It's called the same. Open your textures in Gimp and save them all as .rgb.

'''See''' http://www.gimp.org

Now, place the texture file in the same folder as your .ac model file (usually <tt>FlightGear/data/aircraft/..../Models</tt>). Open the .ac file with a text editor like Notepad and replace all the .jpg textures with .rgb. So if you got something like this:
texture "untitled1.jpg"
replace it with:
texture "untitled1.rgb"
Save the file and close the texteditor.

----
===4. The .stg file===
To tell FlightGear where the models have to be placed we use .stg files, which you can open and edit with almost any text editor like Notepad.

There are two types of objects: shared and static objects. Shared are objects that are located at a lot of locations, like wind turbines and ships. Static ones are unique and are only located at one location, like the Empire State Building or the Golden Gate Bridge. This is an example of a .stg file with a static object (Empire State Building).
OBJECT_STATIC united_states/empire_state_building.ac -73.98594 40.74849 10 0
We'll have a closer look at the code.
* '''OBJECT_STATIC''' tells FlightGear we use a static object. If you use a shared object use OBJECT_SHARED.
* '''empire_state_building.ac:''' the model-file FlightGear has to use (we've saved this one earlier on this wikipage). When you use static objects this has to be in the same coordinate-folder as your model.
* '''-73.98594:''' the longitude.
* '''40.74849:''' the latitude.
* '''10:''' the elevation level in feet (altitude).
* '''0:''' the rotation in degrees.

''See [[Howto: Place 3D objects with the UFO]] for the main article''

As you should know the FlightGear scenery isn't very matching the reality according to height, rivers, woods etc. But when the scenery is becoming nicer and more matching the reality we need to have our buildings at the good spots. So don't place your buildings according to the scenery but to the
reality. '''''Example:''''' ''if you've placed a building on the right location, but in FlightGear it's standing in the middle of a river: just leave it.''
----

===4. Testing===
Let's test our scenery now! This is the nice part of placing objects in the scenery ;)

Open FlightGear and choose an aircraft (you may use the [[UFO from the 'White Project' of the UNESCO|UFO]], because that one is very easy to fly and you can look from all the different sides to the object(s) we've placed). When using the [[FlightGear Wizard]] fill in a location near your objects through Advanced > Initial position. Press run and...

'''Enjoy your flight!'''
----
===5. Sharing===
To share your models please go to the [http://scenemodels.flightgear.org/contribute.php FlightGear Scenery Object Database].

==External tutorials==
* [http://sketchup.google.com/tutorials.html SketchUp tutorials]
* [http://www.blender.org/tutorials-help/tutorials/ Blender tutorials]
* [http://www.gimp.org/tutorials/ Gimp tutorials]

{{3d}}

[[Category:Modeling]]