FlightGear wiki - User contributions [en]

Fgfsrc

2010-09-08T12:56:18Z

Tat: Added a line for Mac OS X

Like all [http://www.catb.org/jargon/html/R/rc-file.html rc-files], the '''''fgfsrc'''''s purpose is to contain [[Command Line Options]] 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'' 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 Mac OS X, the same as GNU/Linux. A Terminal window is placed on /Applications/Utilities/Terminal.app

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

A simple way to have more than one setup is to replace ''fgfsrc'' by a link which can be changed according to the setup one wants to load. On a GNU/Linux system this could look like
ls -l ~/.fgfsrc*
... /home/user/.fgfsrc -> .fgfsrc.cvs
... /home/user/.fgfsrc.1.9.1
... /home/user/.fgfsrc.cvs

===== Some 'rules' for the file and it's content: =====

* The file is plain text (ASCII), like saving a .txt-file with Wordpad.
* Each line contains one option only.
* If the first 'visible' character is a '#', ''fgfs'' totally ignores the line (comment).
* Use comments following an option (<code>--some-option # some comment</code>) with care. At least with string containing''--prop='' options this will cause ''fgfs'' to fail.

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

Have in mind, that *at least* the local paths (like fg-root and fg-scenery) and the [[Multiplayer]] options have to be altered to work on your system!

# $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
#--enable-real-weather-fetch
--enable-horizon-effect
--enable-specular-highlight
--enable-ai-models
--enable-clouds3d
--shading-flat
--fog-nicest
--enable-random-objects
--prop:/sim/rendering/random-vegetation=true
## limit fps to 30:
--prop:/sim/frame-rate-throttle-hz=30
## rain/snow:
--prop:/sim/rendering/precipitation-enable=true
--ai-scenario=nimitz_demo
--ai-scenario=clemenceau_demo
#--ai-scenario=aircraft_demo

### Network
#
--callsign=I-FLY
#--prop:/sim/remote/pilot-callsign=U-FLY
--multiplay=out,10,mpserverXX.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:

* <code>--prop:/sim/traffic-manager/use-custom-scenery-data=true</code><BR>See [http://www.flightgear.org/forums/viewtopic.php?f=5&t=5589&p=42156&hilit=parking+positions#p42151 forum] and [http://sourceforge.net/mailarchive/message.php?msg_name=g87kri%24u4q%241%40osprey.mgras.de mailing list] for more info on this.

* <code>--random-wind # not in 1.9.1 and former versions</code><BR>Nice turbulences during approaches ;-).

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

FlightGear hangars

2009-08-03T00:25:31Z

Tat:

''See [[Links]] for a overall listing of FlightGear related external websites''

FlightGear has many [[aircraft]] available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a [[CVS]] build, to being compatible with [[FlightGear 1.9.0|version 1.9.0]], although some may still need [[FlightGear 1.0]] or [[0.9.10|older]] if an archive has not been updated.

===Official Hangars===
*[http://www.flightgear.org/Downloads/aircraft/ FlightGear Official 1.0.0 Hangar]
*[http://cvs.flightgear.org/viewvc/data/Aircraft/ CVS Hangar] (For CVS builds)

===Other FlightGear download hosts===
*[http://www.unitedfreeworld.com/ unitedfreeworld] (scenery, plane models, and livery)

===Developer & User Hangars===
*[http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
*[http://helijah.free.fr/flightgear/hangar.htm Helijah FGFS Hangar]
*[http://www.gidenstam.org/FlightGear/JSBSim-LTA/ Anders Lighter-than-air Hangar]
*[http://home.comcast.net/~davidculp2/hangar/hangar.html David Culp Hangar]
*[http://www.flightgear.nl.tp/ Gijs Hangar]
*[http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar]
*[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]
*[http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]
*[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]
*[http://ffgfs.free.fr/FlightGear/index.php?page=0 Dyn'aero MCR Sportster, Colomban MC-15 Cri-Cri, Piaggio Aero P-180 Avanti II, Dassault Rafale B, and Bombardier CRJ700]
*[http://mdsmith2.oxyhost.com/hangar.html Michael Smith's Hangar]
*[http://ltts.crlt.indiana.edu/grn/flightgear/ Buckaroo's Hangar: Lockheed 1049H Constellation]
*[http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]

*[http://www.xs4all.nl/~dtalsma/flightgear.html FlightGear AI Aircraft Download Page]

===Outdated Hangars===
*[http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar]
*[http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]

===Related content===
*[[Table of models]]
*[[Aircraft]] - [[Helicopter]] - [[Vehicle]]

[[Category:List]]

Portal:Developer

2008-10-20T18:31:05Z

Tat:

<div align="center">
[[Portal:Developer|Developer]] - [[Portal:User|User]]
</div>

{|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;">The Developer Portal</h2>
|-
|style="color:#000;"|
This portal is for developers contributing to FlightGear. If you wanna help with FlightGears development, it's a good idea to subscribe yourself to the [http://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear devel] mailing list. The [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-devel list archive] is also available and should be searched before posting the same question.<br><br>
'''Please choose a sub-portal:'''
* [[Portal:Developer/Aircraft|Aircraft]]
* [[Portal:Developer/Scenery|Scenery]]<br><br>
'''The FlightGear project is looking for organizations/individuals who would be willing to help sponsor a fulltime project coordinator/manager to help oversee the overall development process If you are interested in helping or have anything else to contribute to this issue, please subscribe to the the [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11813.html FlightGear Devel mailing list] to discuss details.'''
|}
|}

{|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;">Current Efforts/Branches & Work in Progress</h2>
|-
|style="color:#000;"|
*[[FlightGear Package Manager]] (New! Alpha release of Java/XML package manager!)
*[[Walk View‎]] (New! walk view code!)
'''[[Work in progress|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;">Latest Organizational Issues</h2>
|-
|style="color:#000;"|
* [[ Project Infrastructure Enhancements ]]
* [[Google Summer of Code Candidate Projects]] - application template to allow community members to prepare a possible application to decrease the effort required to actually apply
|-
! <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;">Background Info</h2>
|-
|style="color:#000;"|
* [[Resources]]
|-
! <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;">Compiling</h2>
|-
|style="color:#000;"|
* [[ Building Flightgear ]]
* [[ Building Flightgear - Windows]]
* [http://macflightgear.sourceforge.net/home/documents/how-to-build-flightgear-cvs-on-mac-os-x/ Building Flightgear - Mac OS X]
* [[ Building FlightGear Launch Control ]]
* [[ Building Terragear ]]
* [[ Keeping FlightGear (win32) up to date without compiling]]
* [[ OpenSceneGraph ]]
* [[ Tools of the Trade ]]
* [[ Using TortoiseCVS with FlightGear ]]
|-
! <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;">Contributing</h2>
|-
|style="color:#000;"|
* [[ Code Cleanup ]]
* [[ Contributor Repositories ]] mirrors, branches and forks privately maintained by contributors
* [[ Development Resources ]]
* [[ Extension Support ]]
* [[ Submitting Patches ]]
* [[ Technical Reports ]]
|-
! <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;">Code Internals</h2>
|-
|style="color:#000;"|
* [[Command Parameters]]
* [[ FDM API ]]
* [[ File Formats ]]
* [[ Initialization Sequence ]]
* [[ Nasal scripting language ]]
* [[ Property Tree ]]
* [[ Subsystems ]]
* [[ UML Diagrams ]]
* [[ YASim ]]
* [[ FlightGear 1.0 aircraft names for command line‎|1.0.0 a/c names for command line]]

|-
|}

|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;">Todo</h2>
|-
|style="color:#000;"|
* [[ Bugs ]]
* [[ Feature Requests / Proposals / Ideas ]]
* [[ FGFS Todo ]]
* [[ FlightGear Expo Checklist ]]
* [[ Long Term Goals ]]
|-
! <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;">Done</h2>
|-
|style="color:#000;"|
* [[ Changes since 0.9.10 ]]
|-
! <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;">HowTos</h2>
|-
|style="color:#000;"|
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender|Add smooth shadows in Blender]]
* [[Howto: 3D Aircraft Models|3D Aircraft Models]]
* [[Howto: Add aircraft lights|Add aircraft lights]]
* [[Howto: Edit a livery|Edit a livery]]
* [[Howto: Illuminate faces|Illuminate faces]]
* [[Howto: Make a helicopter|Make a helicopter]]
* [[Howto: Set up a multiplayer server|Set up a multiplayer server]]
'''[[:Category:Howto|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;">Instrumentation</h2>
|-
|style="color:#000;"|
* [[ Creating instruments for FG ]]
|-
! <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;">Nasal scripting</h2>
|-
|style="color:#000;"|
* [[ Nasal scripting language ]]
* [[ Writing simple scripts in %22nasal%22 ]]
* [[ Walk View‎]]
|-
! <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;">Autopilot configuration</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.org/Docs/XMLAutopilot/ FlightGear Autopilot] (Theory, Configuration, and Tuning)
* [[ Autopilot Tuning Resources ]]
|-
! <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;">3D Modeling</h2>
|-
|style="color:#000;"|
* [[ Howto: 3D Aircraft Models|3D Aircraft Models]] (howto)
* [[ Aircraft Information Resources ]]
* [[ Model Import and Export ]]
* [[ Modeling - FAQ ]]
* [[ Modeling - Getting Started ]]
* [[ Modeling Resources ]]
* [[ Modeling - SketchUp]]
* [[ Normals and Transparency Tutorial ]]
* [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro Blender3D Modeling]
|-
! <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;">Scenery</h2>
|-
|style="color:#000;"|
* [[ Blender Ground Signs Tutorial]]
* [[ Placing 3D Objects with the UFO ]]
* [[ Signs ]] (placing and explanation)
* [[ Using Terragear ]]
* [[ Using the Custom Scenery TerraGear Toolset ]]
* [[ Building_terragear-cs_in_Ubuntu_64|Building Terragear-cs in Ubuntu Hardy]]
|-
|}
|}

__NOTOC__
__NOEDITSECTION__

== Developer Documentation ==
=== RFC Topics ===
'''Clarification:'''In its current form, the RFC section is exclusively based on and covered by previous mailing list and forum discussions (as well as various wiki entries), as such it is not supposed to reflect work in progress (RFC="Request For Comments" and not WIP), but is rather to be seen as an attempt to provide comprehensive analyses and summaries of key issues identified in various FlightGear related discussions and feature requests (which are to be linked to in the corresponding resource sections, if that didn't yet take place, it's because of most of these RFCs being indeed WIP).

Thus, RFC entries are not meant to imply anyone "working" on any of these issues, in fact only because an RFC entry is listed here doesn't necessarily mean that work on that particular issue is endorsed by the FlightGear community.

* [[Next Generation Scenery ]] - revamping the FG scenery engine
* [[Keyboard function priority list]] - reorganizing FlightGear keybindings
* [[FlightGear Sessions]] - discussing possible steps to finally allow aircraft to be reliably switched at runtime
* [[Formalizing Aircraft Status]] - discussing suggestions about how to more properly describe aircraft development status
* [[Simplifying Aircraft Deployment]] - identifying potential steps to simplify deployment of FlightGear aircraft
* [[FDM engine feature standardization]] - discussing possible steps to standardize feature support of mainstream FlightGear FDM engines
* [[FlightGear Glass Cockpits]] - discussing required infrastructure changes to enable non-developers to easily access FlightGear-internals in order to enable them to model complex glass cockpit-type aircraft instrumentation systems
* [[Recommended Property Tree Enhancements]] - discussing possible property tree enhancements to help ensure integrity of crucial runtime state
* [[Backwards Compatibility Initiative]] - discussing possible ways to improve FlightGear's backwards compatibility
* [[Recommended Project Policies]] - discussing recommended policies for future contributions to the project
* [[Distributed Interactive Simulation]] - discussing possible steps to prepare FlightGear for HLA
* [[Property Tree Reorganization]] - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions)

=== Miscellaneous ===
* [[ Glass Cockpit Projects ]]
* [[ Copyright Inquiry ]]
* [http://www.cafepress.com/fgfs_gear FlightGear - Gear]
* [[ Sign Specification Proposal ]]

== Middleware & Base Package Development ==

* [[:Category:Aircraft TODO]]

=== Misc ===
* [[FGSD- How to make a airport]]

==Old work in progress links==
*Warning! These links outdated, and some of these projects are finished:
* [http://www.flightgear.org/forums/viewtopic.php?t=1378 Efforts to create photo realistic scenery for FlightGear] (Images: [http://www.brest-metropole-oceane.fr/vueduciel/images/101_106.jpg] [http://blaniel.free.fr/pub/flightgear/brest/brest1.png] [http://helijah.free.fr/LFRB/fgfs-screen-001.jpg] [http://helijah.free.fr/LFRB/fgfs-screen-003.jpg]
* [http://www.flightgear.org/forums/viewtopic.php?t=755 New aircraft model under development: Bede BD-5J]
* [http://www.flightgear.org/forums/viewtopic.php?t=542 F14-Tomcat aircraft model under development] ([[Grumman F-14 Tomcat|F-14 released!]])
* [http://www.flightgear.org/forums/viewtopic.php?t=1001 787 being revamped]
* [http://www.flightgear.org/forums/viewtopic.php?t=1436 LFLJ enhancements]
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16176.html Free Walking mode for FlightGear using the Jeep vehicle in CVS]
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15388.html Random Trees for FlightGear]

Portal:Developer

2008-10-20T17:56:21Z

Tat:

<div align="center">
[[Portal:Developer|Developer]] - [[Portal:User|User]]
</div>

{|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;">The Developer Portal</h2>
|-
|style="color:#000;"|
This portal is for developers contributing to FlightGear. If you wanna help with FlightGears development, it's a good idea to subscribe yourself to the [http://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear devel] mailing list. The [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-devel list archive] is also available and should be searched before posting the same question.<br><br>
'''Please choose a sub-portal:'''
* [[Portal:Developer/Aircraft|Aircraft]]
* [[Portal:Developer/Scenery|Scenery]]<br><br>
'''The FlightGear project is looking for organizations/individuals who would be willing to help sponsor a fulltime project coordinator/manager to help oversee the overall development process If you are interested in helping or have anything else to contribute to this issue, please subscribe to the the [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11813.html FlightGear Devel mailing list] to discuss details.'''
|}
|}

{|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;">Current Efforts/Branches & Work in Progress</h2>
|-
|style="color:#000;"|
*[[FlightGear Package Manager]] (New! Alpha release of Java/XML package manager!)
*[[Walk View‎]] (New! walk view code!)
'''[[Work in progress|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;">Latest Organizational Issues</h2>
|-
|style="color:#000;"|
* [[ Project Infrastructure Enhancements ]]
* [[Google Summer of Code Candidate Projects]] - application template to allow community members to prepare a possible application to decrease the effort required to actually apply
|-
! <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;">Background Info</h2>
|-
|style="color:#000;"|
* [[Resources]]
|-
! <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;">Compiling</h2>
|-
|style="color:#000;"|
* [[ Building Flightgear ]]
* [[ Building Flightgear - Windows]]
* [[ Building Flightgear - Mac OS X]]
* [[ Building FlightGear Launch Control ]]
* [[ Building Terragear ]]
* [[ Keeping FlightGear (win32) up to date without compiling]]
* [[ OpenSceneGraph ]]
* [[ Tools of the Trade ]]
* [[ Using TortoiseCVS with FlightGear ]]
|-
! <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;">Contributing</h2>
|-
|style="color:#000;"|
* [[ Code Cleanup ]]
* [[ Contributor Repositories ]] mirrors, branches and forks privately maintained by contributors
* [[ Development Resources ]]
* [[ Extension Support ]]
* [[ Submitting Patches ]]
* [[ Technical Reports ]]
|-
! <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;">Code Internals</h2>
|-
|style="color:#000;"|
* [[Command Parameters]]
* [[ FDM API ]]
* [[ File Formats ]]
* [[ Initialization Sequence ]]
* [[ Nasal scripting language ]]
* [[ Property Tree ]]
* [[ Subsystems ]]
* [[ UML Diagrams ]]
* [[ YASim ]]
* [[ FlightGear 1.0 aircraft names for command line‎|1.0.0 a/c names for command line]]

|-
|}

|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;">Todo</h2>
|-
|style="color:#000;"|
* [[ Bugs ]]
* [[ Feature Requests / Proposals / Ideas ]]
* [[ FGFS Todo ]]
* [[ FlightGear Expo Checklist ]]
* [[ Long Term Goals ]]
|-
! <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;">Done</h2>
|-
|style="color:#000;"|
* [[ Changes since 0.9.10 ]]
|-
! <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;">HowTos</h2>
|-
|style="color:#000;"|
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender|Add smooth shadows in Blender]]
* [[Howto: 3D Aircraft Models|3D Aircraft Models]]
* [[Howto: Add aircraft lights|Add aircraft lights]]
* [[Howto: Edit a livery|Edit a livery]]
* [[Howto: Illuminate faces|Illuminate faces]]
* [[Howto: Make a helicopter|Make a helicopter]]
* [[Howto: Set up a multiplayer server|Set up a multiplayer server]]
'''[[:Category:Howto|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;">Instrumentation</h2>
|-
|style="color:#000;"|
* [[ Creating instruments for FG ]]
|-
! <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;">Nasal scripting</h2>
|-
|style="color:#000;"|
* [[ Nasal scripting language ]]
* [[ Writing simple scripts in %22nasal%22 ]]
* [[ Walk View‎]]
|-
! <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;">Autopilot configuration</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.org/Docs/XMLAutopilot/ FlightGear Autopilot] (Theory, Configuration, and Tuning)
* [[ Autopilot Tuning Resources ]]
|-
! <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;">3D Modeling</h2>
|-
|style="color:#000;"|
* [[ Howto: 3D Aircraft Models|3D Aircraft Models]] (howto)
* [[ Aircraft Information Resources ]]
* [[ Model Import and Export ]]
* [[ Modeling - FAQ ]]
* [[ Modeling - Getting Started ]]
* [[ Modeling Resources ]]
* [[ Modeling - SketchUp]]
* [[ Normals and Transparency Tutorial ]]
* [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro Blender3D Modeling]
|-
! <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;">Scenery</h2>
|-
|style="color:#000;"|
* [[ Blender Ground Signs Tutorial]]
* [[ Placing 3D Objects with the UFO ]]
* [[ Signs ]] (placing and explanation)
* [[ Using Terragear ]]
* [[ Using the Custom Scenery TerraGear Toolset ]]
* [[ Building_terragear-cs_in_Ubuntu_64|Building Terragear-cs in Ubuntu Hardy]]
|-
|}
|}

__NOTOC__
__NOEDITSECTION__

== Developer Documentation ==
=== RFC Topics ===
'''Clarification:'''In its current form, the RFC section is exclusively based on and covered by previous mailing list and forum discussions (as well as various wiki entries), as such it is not supposed to reflect work in progress (RFC="Request For Comments" and not WIP), but is rather to be seen as an attempt to provide comprehensive analyses and summaries of key issues identified in various FlightGear related discussions and feature requests (which are to be linked to in the corresponding resource sections, if that didn't yet take place, it's because of most of these RFCs being indeed WIP).

Thus, RFC entries are not meant to imply anyone "working" on any of these issues, in fact only because an RFC entry is listed here doesn't necessarily mean that work on that particular issue is endorsed by the FlightGear community.

* [[Next Generation Scenery ]] - revamping the FG scenery engine
* [[Keyboard function priority list]] - reorganizing FlightGear keybindings
* [[FlightGear Sessions]] - discussing possible steps to finally allow aircraft to be reliably switched at runtime
* [[Formalizing Aircraft Status]] - discussing suggestions about how to more properly describe aircraft development status
* [[Simplifying Aircraft Deployment]] - identifying potential steps to simplify deployment of FlightGear aircraft
* [[FDM engine feature standardization]] - discussing possible steps to standardize feature support of mainstream FlightGear FDM engines
* [[FlightGear Glass Cockpits]] - discussing required infrastructure changes to enable non-developers to easily access FlightGear-internals in order to enable them to model complex glass cockpit-type aircraft instrumentation systems
* [[Recommended Property Tree Enhancements]] - discussing possible property tree enhancements to help ensure integrity of crucial runtime state
* [[Backwards Compatibility Initiative]] - discussing possible ways to improve FlightGear's backwards compatibility
* [[Recommended Project Policies]] - discussing recommended policies for future contributions to the project
* [[Distributed Interactive Simulation]] - discussing possible steps to prepare FlightGear for HLA
* [[Property Tree Reorganization]] - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions)

=== Miscellaneous ===
* [[ Glass Cockpit Projects ]]
* [[ Copyright Inquiry ]]
* [http://www.cafepress.com/fgfs_gear FlightGear - Gear]
* [[ Sign Specification Proposal ]]

== Middleware & Base Package Development ==

* [[:Category:Aircraft TODO]]

=== Misc ===
* [[FGSD- How to make a airport]]

==Old work in progress links==
*Warning! These links outdated, and some of these projects are finished:
* [http://www.flightgear.org/forums/viewtopic.php?t=1378 Efforts to create photo realistic scenery for FlightGear] (Images: [http://www.brest-metropole-oceane.fr/vueduciel/images/101_106.jpg] [http://blaniel.free.fr/pub/flightgear/brest/brest1.png] [http://helijah.free.fr/LFRB/fgfs-screen-001.jpg] [http://helijah.free.fr/LFRB/fgfs-screen-003.jpg]
* [http://www.flightgear.org/forums/viewtopic.php?t=755 New aircraft model under development: Bede BD-5J]
* [http://www.flightgear.org/forums/viewtopic.php?t=542 F14-Tomcat aircraft model under development] ([[Grumman F-14 Tomcat|F-14 released!]])
* [http://www.flightgear.org/forums/viewtopic.php?t=1001 787 being revamped]
* [http://www.flightgear.org/forums/viewtopic.php?t=1436 LFLJ enhancements]
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16176.html Free Walking mode for FlightGear using the Jeep vehicle in CVS]
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15388.html Random Trees for FlightGear]

New to FlightGear

2008-10-20T17:55:05Z

Tat:

See '''[[Portal:User]]''' if you are lost!

See the '''[http://www.flightgear.org/Gallery-v1.0/ FlightGear v1.0 Gallery]''' at FlightGear.org for much more about what [[FlightGear]] version 1.0 can do!

For those new to FlightGear, version 1.0 can be downloaded at '''[http://www.flightgear.org/Downloads/ Download Central]''', but most aircraft need to be separately downloaded '''[http://www.flightgear.org/Downloads/aircraft/ Here]''' and installed manually (see also [[FlightGear 1.0 default aircraft]]). Be aware of system requirements!

''Note some parts of this article have not been updated for 2008''

{|
|__TOC__
|}

== Getting Started ==

=== Getting FlightGear ===

You may download the latest files from [http://www.flightgear.org/Downloads/ FlightGear Downloads] page. Choose the source or binary files appropriate for your particular system. Or, depending on level technical expertise you may choose the CVS version if you wish to work with a development version of FlightGear. The CVS version typically has more features and can be required by the some the latest developmental aircraft, but can be unstable and is more complicated to acquire and install.

=== Installing on Windows ===

After installing Flight Gear v 1.0.0 on windows a dialog box appears to define file locations.

The first line asks for Flight Gear Executable. Use the browse button to navigate to the location of fgfs.exe. (In the default setup that is 'c:\Program Files\FlightGear\bin\win32\fgfs.exe')

The second line asks for Flight Gear Root. Use the browse button to navigate to the Data directory or enter the location of the 'data' directory. (n the defualt setup that is 'c:\Program Files\FlightGear\data')
This will populate the scenery box as well.

Once you have defines these defaults the setup will continue as explained here.

=== Installing on Mac OS X ===

Installing FlightGear on Mac OS X is very simple. Just drag and drop the FlightGear icon to /Applications folder. That's it. The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select an aircraft and and airport by clicking the "Gear" buttons at the right of the names. Pressing "Start flight" will launch the simulator. You can configure more options using the GUI launcher. see http://macflightgear.sourceforge.net/home/documents/users-guide/ for more details.

If you want to launch flightgear using command-line, launch /Applications/Utilities/Terminal.app and type the following.

cd /Applications/FlightGear.app/Contents/Resources
./fgfs --options.....

The $FG_ROOT and $FG_SCENERY are not set on Mac OS X. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=$FG_ROOT/Scenery

After launching the GUI launcher, you will have the alias to $FG_ROOT at $HOME/Documents/Flightgear/<version> so you can browse the data folder using Finder.

=== Getting Scenery ===

A limited set of [[scenery]] comes installed with [[FlightGear]], which consists of the area surrounding [[San Francisco International Airport|KSFO]].

In FlightGear, scenery is divided into two kinds of data: Objects and Terrain. Objects are the buildings, bridges and radio towers, etc. that represent three-dimensional structures. Terrain represents the contours, elevations and type of ground you fly over.

All object data goes in an Objects directory and all terrain data goes in a Terrain directory. The location of the scenery and its sub-directories depends on your particular installation.

To download Objects and Terrain for FlightGear, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page. On this page follow the link to download scenery from the map. Choose a block from the map where you will by flying. Once the package has downloaded, extract into your FlightGear scenery directory.

The scenery packages available from the FlightGear website contain both Objects and Terrain for the locations.

You may obtain additional and more up to date scenery Objects as they become available through the [http://fgfsdb.stockill.org/ FlightGear Scenery Database].

Information beyond this brief overview is available in [[Installing Scenery]] and [[Downloading New Flightgear Scenery for Windows XP]]

=== Getting Aircraft ===
To download additional [[Aircraft]] for FlightGear individually, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page, then choose [Aircraft Downloads http://www.flightgear.org/Downloads/aircraft/index.shtml]. A (possibly temporary) archive of all aircraft available as of 8/14/2006 is at: [FGaircraft_20060814.zip http://139.78.95.188/flightgear/FGaircraft_20060814.zip] (about 108 MB).

Once the aircraft package has downloaded, decompress and extract the archived files onto your computer. You may extract to a temporary directory and move them, or extract directly into the Aircraft directory in FlightGear. This is typically

/path/to/flight/gear/data/Aircraft

See also [[Installing Aircraft]] for more documentation.

=== Starting FlightGear ===

Many users choose to start FlightGear from the command line ("console" or "shell" as it is known to Unix users). Alternatively some use graphical interfaces such as [[FlightGear Launch Control|Fgrun]] (FlightGear Launch Control).

To start FlightGear type on the command line:

fgfs

and hit enter. This will start FlightGear.

If FlightGear fails to start, it is likely the compiled FlightGear binary software is not in your path. If you know Unix, you may add the location of the binary to your path and try starting again. Otherwise, you may find the location of the 'fgfs' binary and enter an absolute path to it like

/usr/games/fgfs

The location depends on your particular system and choices you made during compile and installation.

It is important to understand when not using a graphical interface to start FlightGear, your interaction will be entirely from the command line. To see available aircraft, you specify an option on the command line. To specify an aircraft, an airport, multiplayer server, etc. you add an option to the command line when starting FlightGear. Please consult the list of [[ Command Line Parameters ]]. The parameters are also useful to those starting FlightGear from [[ FlightGear Launch Control ]] graphical interface, as it allows you to specify parameters. If you are using FlightGear 1.0.0 this list may be useful [[FlightGear 1.0 aircraft names for command line]].

=== Displaying Available Aircraft ===

From the command line:

fgfs --show-aircraft

displays a list of available (installed) aircraft. (see also [[FlightGear 1.0 default aircraft]] and/or [[Table of models]])

=== Choosing an Aircraft ===

From the command line:

fgfs --aircraft=foo

where foo is the name of the folder the aircraft files live in. See also [[FlightGear 1.0 aircraft names for command line]] and/or [[Command Line Parameters]])

=== Online Multiplayer Flying ===

See the [[Multiplayer Howto]]

=== Using the Keyboard and Mouse ===

Users with limited access to a joystick or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard. Other adjustments may be made with the keyboard.

To get help with keyboard commands, with FlightGear running, go to the Help menu, look under Basic Keys (for simulator related commands) and Common Aircraft Keys (for commands universal to all aircraft) and Aircraft Help for key commands specific to your aircraft. A chart displaying what each key does will display.

To use the mouse to fly the aircraft, right click and move the mouse to direct the aircraft, right click again to look around, click again to return to normal.

=== First Time In the Cockpit ===

Finding your way around the cockpit can be daunting the first time.

Where is the 'virtual cockpit?' Not all FlightGear aircraft come with an interior, including a virtual cockpit. (Due to FlightGear being used by various research projects, some aircraft may not even come with an exterior model. Remember, FlightGear is very flexible.) A 2D panel may display over the 3d cockpit if one exists. You may turn this off using the View menu. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected.

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. Use the Zoom keys to zoom in on an instrument. The 'x' and Shift-X keys control eyepoint zoom in the Cockpit View. Use the joystick hat (or other controller assigned to this function) to pan the eyepoint to the instrument you wish to read. Then zoom in.

Alternate Method: Click the right mouse button until you get a cursor with two arrows (like this <=>). You can now move your view around the cockpit. Press 'x' and Shift-X to zoom in and out.

Note: Some functions, such as starter or magneto, may be difficult to use or lack "hotspots" to control with your mouse. Especially when flying an aircraft model that is still undergoing development. In this case, look for equivalent controls on a 2D panel or resort to the keyboard. The keyboard controls always work according to the assignments listed on the Help Menu (unless reassigned by an aircraft or configuration). Go to the main window menu, click Help, then click Basic Keys or Common Aircraft Keys.

One of the first steps I take on entering an unfamiliar cockpit is to press Ctrl-C to highlight all the "hotspots" on the 3d cockpit instrument panel. This enables you to easily see where to place the mouse to operate an instrument's controls, buttons, knobs, etc.

Many aircraft offer a help menu specific to that aircraft on the Aircraft Help menu (go to Help, then Aircraft Help.

== Making the First Flight ==

One of the most frequent questions novice pilots ask about any flight sim, but more so to FlightGear, is "why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the increased realism FlightGear provides. In a certain other flight simulator, some settings are turned down to make the aircraft easier to fly. This reduces effects such as propeller torque and p-factor, which may be the cause of the tendency to turn to the left (to figure out which effect, you may read more in [[ Understanding Propeller Torque and P-Factor ]]).

Despite marketing slogans to the contrary, some flight simulators are aimed at a casual game player market, and ship with their "realism" turned down. The realism is always turned up in FlightGear.

FlightGear offers a great deal of realism, which may be confusing to first time pilots.

* "Left Turning Syndrome" for the previously mentioned reasons.

* Compass Turning Error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction.

* The Vertical Speed Indicator is also subject to error.

* The Horizontal Situation Indicator is driven by a gyroscope (that is why it's sometimes called a Directional Gyroscope), which is subject to a phenomenon called gyro drift. For a number of reasons, the gyro will drift from its current heading and must be periodically (about every 15 minutes) calibrated to agree with the magnetic compass heading.

Many forces act on an aircraft in flight as well as on the instruments and systems used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. FlightGear models instrument errors that exist in the real world.

=== Flying Using Navigational Aids and the Autopilot ===

To make this very clear for new users: Some aircraft require you to use the autopilot available from the Autopilot menu, which is the original FlightGear autopilot. This is a '''generic''' autopilot and as such, many aircraft come with their own '''specific''' autopilot, frequently a model of the real life one. '''For aircraft that provide their own autopilot in the cockpit, you must use the autopilot controls available in the virtual cockpit'''. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot (generally).

FlightGear, as of version 0.9.9, comes with a "built-in" autopilot. The Autopilot dialog accessible from the FlightGear toolbar in the main FlightGear window _does not work with all aircraft_. It only works with aircraft that a) do not specify an autopilot, or b) aircraft that use the default autopilot. When an aircraft does not specify an autopilot, the default is used.

For aircraft that supply their own autopilot, you must use the autopilot controls in the 2D or virtual cockpit. The Cessna comes with a KAP140 autopilot in its virtual cockpit. You _cannot use_ the Autopilot dialog with this aircraft. It has no effect. You must use the autopilot device in the panel.

For help with navigation see [[Understanding Navigation]]

=== Airports and Navigation Aids ===

When you first start FlightGear, whether from the command line or the graphical interface, you may wonder how to determine what airports are available. Fgrun displays a list of airports, but you will not see details such as Tower or ILS frequencies. You will not find a map showing VORs and their frequencies. Short of finding an actual sectional map for the area you wish to fly, what can you do?

[http://maps.google.com Google Maps] and The FlightGear Online Map for multiplayers are both good resources as well as the FlightGear Community Flight Planner.

== Getting Help ==

=== Chat ===

The quickest way to get help with Flight Gear is to join in the chat room by IRC (Internet Relay Chat). The current chat server is

Primary Site: Host = irc.flightgear.org, channel = #flightgear, Emergency backup: Host = irc.freenode.net, channel = #flightgear

There are several mailing lists and discussion forums dedicated to FlightGear, check for the latest information at http://www.flightgear.org/mail.html

=== Email Discussion Group ===

The documentation for Flight Gear is sketchy and undergoing constant change as new features are developed. This makes chat the best place to find answers to problems getting FlightGear to run.

=== Documents ===

The ways for _users_ to get help with FlightGear are:

* Documents bundled with the release package.
* FlightGear IRC channel.
* FlightGear users mailing list.

== Getting More Detailed Information ==

This page is designed to give the user the essential things they need to know about using FG for the first time.

You now know enough to get started with FlightGear. To learn more, you may wish to start at the main page of this wiki and read the more detailed Getting Started section, or Using FlightGear section or study the Flying Resources to learn more about flight instruments and how to navigate and fly your aircraft.

Also, note that those using the CVS version of FlightGear may choose to update their aircraft files through the CVS system.

The following are some issues raised by new users of FlightGear. More detailed troubleshooting and answers can be found in [[Troubleshooting Problems]] and the [[FAQ]].

=== I do not want to compile FlightGear, what can I do? ===

http://www.flightgear.org/Downloads/

offers precompiled binaries for download and install on a variety of systems. Current platforms are Windows, Linux, Solaris, SGI, Mac OSX and FreeBSD. These are offered as a convienence and availablility may vary at times.

Note: FlightGear is highly configurable through editable XML files. You are free, and encouraged to, make changes to aircraft flight models and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. The flight model is not defined in a binary file. It is easy to modify (given enough knowledge). Although the install is binary, most of FlightGear's system is open to configuration through XML files and NASAL scripting.

=== Does FlightGear come with a printed manual? ===

You are invited to read "The Manual" online as [http://www.flightgear.org/Docs/getstart/getstart.html HTML]
or download a [ftp://ftp.de.flightgear.org/pub/fgfs/Docs/getstart.pdf PDF] for viewing with Acrobar Reader or printing.

"The Manual" is not always up to date with recent developments but provides a good start for beginners.

== How you can help ==

: ''See also [[Volunteer]]''

=== Testing ===
* [[Building Flightgear|Build]] the latest CVS code or download snapshots (link)
* File Bug Reports

=== Debugging & Profiling ===
* Running FlightGear via valgrind to track down memory leaks

=== Support ===
* Help new users with downloading, compiling, installing and running FlightGear (http://www.flightgear.org/forums or on IRC)
* Provide Ideas & Suggestions, see: [[Feature Requests / Proposals / Ideas]]
* help clean up this wiki
* help provide new contents for missing wiki pages

=== Development ===
* Writing documentation! Everyone is welcome to contribute to "The Manual"; having at least a little experience with LaTeX makes the task easier. Please contact the authors of The Manual if you would like to add corrections or whole chapters, you may also simply use this wiki to contribute fixes, modifications and new contents.
* C/C++ Coding:
** provide source code cleanups (i.e. help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
** provide bug fixes [[Bugs]]
** provide enhanced features [[Feature Requests / Proposals / Ideas]]
** provide new features
** get involved in any of the other FlightGear-affiliated projects
* Aircraft development (3D modelling, textures, FDMs, scripting)
* Scenery development

{{Understanding}}

Building FlightGear - Linux

2006-12-06T08:15:19Z

Tat: /* Instructions */

'''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 ==
* C++ compiler
* OpenGL support
* [[ OpenSceneGraph ]] (cvs HEAD branch)

== Dependencies ==
* pthreads
* (Free)GLUT or SDL
* [http://plib.sourceforge.net/ PLIB] (until version 0.9.10 release sources, PRE_OSG_PLIB_20061029 CVS branch)
* [http://openal.org OpenAL and ALUT]
* [http://simgear.org SimGear]

== Optional Dependencies ==

== Instructions ==
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 ]]
* [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)]
=== Tools ===

== Free/Open Source ==
* [http://www.gnu.org/software/gcc/onlinedocs/ gcc - the GNU compiler (collection)]
* [http://www.gnu.org/software/make/manual/make.html make - GNU make]
* [http://sources.redhat.com/autobook/ autools - autoconf, automake, libtool & co]
* [http://distcc.samba.org distcc - distributed (fast!) compilations for any network]
* [http://www.gnu.org/software/binutils/manual/gprof-2.9.1/gprof.html gprof - the GNU profiler]
* [http://ccache.samba.org ccache - compiler cache, pre-compiled objects for gcc]
* [http://www.stack.nl/~dimitri/doxygen/ doxygen - source code documenting]
* [http://www.gnu.org/software/gdb/documentation/ gdb - the GNU project debugger]
* [http://www.gnu.org/manual/ddd/ddd.html DDD - Data Display Debugger]
* CVS - Concurrent Versioning System
** http://cvsbook.red-bean.com/cvsbook.html
** http://www.cs.utah.edu/dept/old/texinfo/cvs/cvs_toc.html
** http://www.wincvs.org/
* SVN
**http://www.subversion.org

== Free/Proprietary ==
* [http://www.intel.com/vtune/ Intel VTune] [http://www.intel.com/cd/software/products/asmo-na/eng/download/download/index.htm (free Win32/Linux versions available for non-commercial use:requires an INTEL CPU!)]
* [http://developer.amd.com/downloads.aspx AMD's Developer Tools] (CodeAnalyst, available for free for [http://developer.amd.com/cawin.aspx Win32]/[http://developer.amd.com/calinux.aspx Linux] )