Part IV
Appendices

A Missed approach: If anything refuses to work
 A.1 FlightGear Problem Reports
 A.2 General problems
 A.3 Potential problems under Linux
 A.4 Potential problems under Windows
B Landing: Some further thoughts before leaving the plane
 B.1 A Sketch on the History of FlightGear
 B.2 Those, who did the work
 B.3 What remains to be done
Index

Appendix A
Missed approach: If anything refuses to work

In the following section, we tried to sort some problems according to operating system, but if you encounter a problem, it may be a wise idea to look beyond “your” operating system – just in case. If you are experiencing problems, we would strongly advise you to first check the FAQ maintained by Cameron Moore at

http://wiki.flightgear.org/Frequently_asked_questions.

Moreover, the source code contains a directory docs-mini containing numerous ideas on and solutions to special problems. This is also a good place to go for further reading.

A.1 FlightGear Problem Reports

The best place to look for help is generally the mailing lists, specifically the [Flightgear-User] mailing list. If you happen to be running a Git version of FlightGear, you may want to subscribe to the [Flightgear-Devel] list. Instructions for subscription can be found at

http://www.flightgear.org/mail.html.

It’s often the case that someone has already dealt with the issue you’re dealing with, so it may be worth your time to search the mailing list archives at

http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-users

http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-devel.

You should also consider searching the FlightGear forums for help, instructions and archives at

http://www.flightgear.org/forums.

There are numerous developers and users reading those lists and forums, so questions are generally answered. However, messages of the type FlightGear does not compile on my system. What shall I do? are hard to answer without any further detail given, aren’t they? Here are some things to consider including in your message when you report a problem:

For getting a trace of the output which FlightGear produces, the following command may come in handy (may need to be modified on some OSs or may not work on others at all, though):

%FG ROOT/BIN/fgfs >log.txt 2>&1

One final remark: Please avoid posting binaries to these lists or forums! List subscribers are widely distributed, and some users have low bandwidth and/or metered connections. Large messages may be rejected by the mailing list administrator. Thanks.

A.2 General problems

A.3 Potential problems under Linux

Since we don’t have access to all possible flavors of Linux distributions, here are some thoughts on possible causes of problems. (This Section includes contributions by Kai Troester.)

A.4 Potential problems under Windows

Appendix B
Landing: Some further thoughts before leaving the plane

B.1 A Sketch on the History of FlightGear

History may be a boring subject. However, from time to time there are people asking for the history of FlightGear. As a result, we’ll give a short outline.

The FlightGear project goes back to a discussion among a group of net citizens in 1996 resulting in a proposal written by David Murr who, unfortunately, dropped out of the project (as well as the net) later. The original proposal is still available from the FlightGear web site and can be found under

http://www.flightgear.org/proposal-3.0.1.

Although the names of the people and several of the details have changed over time, the spirit of that proposal has clearly been retained up to the present time.

Actual coding started in the summer of 1996 and by the end of that year essential graphics routines were completed. At that time, programming was mainly performed and coordinated by Eric Korpela from Berkeley University. Early code ran under Linux as well as under DOS, OS/2, Windows 95/NT, and Sun-OS. This was found to be quite an ambitious project as it involved, among other things, writing all the graphics routines in a system-independent way entirely from scratch.

Development slowed and finally stopped in the beginning of 1997 when Eric was completing his thesis. At this point, the project seemed to be dead and traffic on the mailing list went down to nearly nothing.

It was Curt Olson from the University of Minnesota who re-launched the project in the middle of 1997. His idea was as simple as it was powerful: Why invent the wheel a second time? There have been several free flight simulators available running on workstations under different flavors of UNIX. One of these, LaRCsim (developed by Bruce Jackson from NASA), seemed to be well suited to the approach. Curt took this one apart and re-wrote several of the routines such as to make them build as well as run on the intended target platforms. The key idea in doing so was to exploit a system-independent graphics platform: OpenGL.

In addition, a clever decision on the selection of the basic scenery data was made in the very first version. FlightGear scenery is created based on satellite data published by the U. S. Geological Survey. These terrain data are available from

http://edc.usgs.gov/geodata/

for the U.S., and

http://edcdaac.usgs.gov/gtopo30/gtopo30.html,

resp., for other countries. Those freely accessible scenery data, in conjunction with scenery building tools included with FlightGear, are an important feature enabling anyone to create his or her own scenery.

This new FlightGear code - still largely being based on the original LaRCsim code - was released in July 1997. From that moment the project gained momentum again. Here are some milestones in the more recent development history.

B.1.1 Scenery

B.1.2 Aircraft

B.1.3 Environment

B.1.4 User Interface

During development there were several code reorganization efforts. Various code subsystems were moved into packages. As a result, code is organized as follows at present:

The base of the graphics engine is OpenGL, a platform independent graphics library. Based on OpenGL, the Portable Library PLIB provides basic rendering, audio, joystick etcṙoutines. Based on PLIB is SimGear, which includes all of the basic routines required for the flight simulator as well as for building scenery. On top of SimGear there are (i) FlightGear (the simulator itself), and (ii) TerraGear, which comprises the scenery building tools.

This is by no means an exhaustive history and most likely some people who have made important contributions have been left out. Besides the above-named contributions there was a lot of work done concerning the internal structure by: Jon S. Berndt, Oliver Delise, Christian Mayer, Curt Olson, Tony Peden, Gary R. Van Sickle, Norman Vine, and others. A more comprehensive list of contributors can be found in Chapter B as well as in the Thanks file provided with the code. Also, the FlightGear Website contains a detailed history worth reading of all of the notable development milestones at

http://www.flightgear.org/version.html

B.2 Those, who did the work

Did you enjoy the flight? In case you did, don’t forget those who devoted hundreds of hours to that project. All of this work is done on a voluntary basis within spare time, thus bare with the programmers in case something does not work the way you want it to. Instead, sit down and write them a kind (!) mail proposing what to change. Alternatively, you can subscribe to the FlightGear mailing lists and contribute your thoughts there. Instructions to do so can be found at

http://www.flightgear.org/mail.html.

Essentially there are two lists, one of which being mainly for the developers and the other one for end users. Besides, there is a very low-traffic list for announcements.

The following names the people who did the job (this information was essentially taken from the file Thanks accompanying the code).

A1 Free Sounds
Granted permission for the FlightGear project to use some of the sound effects from their site. Homepage under

http://www.a1freesoundeffects.com/

Syd Adams
Added clipping for 2D instruments, ATC volume control and created a wide variety of aircraft.

Raul Alonzo
Mr. Alonzo is the author of Ssystem and provided his kind permission for using the moon texture. Parts of his code were used as a template when adding the texture. Ssystem Homepage can be found at:

http://www1.las.es/˜amil/ssystem/.

Michele America
Contributed to the HUD code.

Michael Basler
Author of Installation and Getting Started. Flight Simulation Page at

http://www.geocities.com/pmb.geo/flusi.htm

Jon S. Berndt
Working on a complete C++ rewrite/reimplimentation of the core FDM. Initially he is using X15 data to test his code, but once things are all in place we should be able to simulate arbitrary aircraft. Jon maintains a page dealing with Flight Dynamics at:

http://jsbsim.sourceforge.net/

Special attention to X15 is paid in separate pages on this site. Besides, Jon contributed via a lot of suggestions/corrections to this Guide.

Paul Bleisch
Redid the debug system so that it would be much more flexible, so it could be easily disabled for production system, and so that messages for certain subsystems could be selectively enabled. Also contributed a first stab at a config file/command line parsing system.

Jim Brennan
Provided a big chunk of online space to store USA scenery for FlightGear!.

Bernie Bright
Many C++ style, usage, and implementation improvements, STL portability and much, much more. Added threading support and a threaded tile pager.

Stuart Buchanan
Updated various parts of the manual, wrote the initial tutorial subsystem, developed random vegetation and buildings.

Bernhard H. Buckel
Contributed the README.Linux. Contributed several sections to earlier versions of Installation and Getting Started.

Gene Buckle
A lot of work getting FlightGear to compile with the MSVC++ compiler. Numerous hints on detailed improvements.

Ralph Carmichael
Support of the project. The Public Domain Aeronautical Software web site at

http://www.pdas.com/

has the PDAS CD-ROM for sale containing great programs for astronautical engineers.

Didier Chauveau
Provided some initial code to parse the 30 arcsec DEM files found at:

http://edcwww.cr.usgs.gov/landdaac/gtopo30/gtopo30.html.

John Check
John maintains the base package CVS repository. He contributed cloud textures, wrote an excellent Joystick Howto as well as a panel Howto. Moreover, he contributed new instrument panel configurations. FlightGear page at

http://www.rockfish.net/fg/.

Dave Cornish
Dave created new cool runway textures plus some of our cloud textures.

Oliver Delise
Started a FAQ, Documentation, Public relations. Working on adding some networking/multi-user code. Founder of the FlightGear MultiPilot

Jean-Francois Doue
Vector 2D, 3D, 4D and Matrix 3D and 4D inlined C++ classes. (Based on Graphics Gems IV, Ed. Paul S. Heckbert)

http://www.animats.com/simpleppp/ftp/public_html/topics/developers.html.

Dave Eberly
Contributed some sphere interpolation code used by Christian Mayer’s weather data base system.

Francine Evans
Wrote the GPL’d tri-striper we use.

http://www.cs.sunysb.edu/˜stripe/

Oscar Everitt
Created single engine piston engine sounds as part of an F4U package for FS98. They are pretty cool and Oscar was happy to contribute them to our little project.

Bruce Finney
Contributed patches for MSVC5 compatibility.

Olaf Flebbe
Improved the build system for Windows and provided pre-built dependencies.

Melchior Franz
Contributed joystick hat support, a LED font, improvements of the telnet and the http interface. Notable effort in hunting memory leaks in FlightGear, SimGear, and JSBSim.

Jean-loup Gailly and Mark Adler
Authors of the zlib library. Used for on-the-fly compression and decompression routines,

http://www.gzip.org/zlib/.

Mohit Garg
Contributed to the manual.

Thomas Gellekum
Changes and updates for compiling on FreeBSD.

Neetha Girish
Contributed the changes for the xml configurable HUD.

Jeff Goeke-Smith
Contributed our first autopilot (Heading Hold). Better autoconf check for external timezone/daylight variables.

Michael I. Gold
Patiently answered questions on OpenGL.

Habibe
Made RedHat package building changes for SimGear.

Mike Hill
For allowing us to concert and use his wonderful planes, available form

http://www.flightsimnetwork.com/mikehill/home.htm,

for FlightGear.

Erik Hofman
Major overhaul and parameterization of the sound module to allow aircraft-specific sound configuration at runtime. Contributed SGI IRIX support (including binaries) and some really great textures.

Charlie Hotchkiss
Worked on improving and enhancing the HUD code. Lots of code style tips and code tweaks.

Bruce Jackson (NASA)
Developed the LaRCsim code under funding by NASA which we use to provide the flight model. Bruce has patiently answered many, many questions.

Maik Justus
Added helicopter support, gear/ground interaction and aerotow/winch support to the YASim FDM.

Ove Kaaven
Contributed the Debian binary.

Richard Kaszeta
Contributed screen buffer to ppm screen shot routine. Also helped in the early development of the "altitude hold autopilot module" by teaching Curt Olson the basics of Control Theory and helping him code and debug early versions. Curt’s ´B  oss´B  ob Hain also contributed to that. Further details available at:

http://www.menet.umn.edu/˜curt/fgfs/Docs/Autopilot/AltitudeHold/AltitudeHold.html.

Rich’s Homepage is at

http://www.kaszeta.org/rich/.

Tom Knienieder
Ported the audio library first to OpenBSD and IRIX and after that to Win32.

Reto Koradi
Helped with setting up fog effects.

Bob Kuehne
Redid the Makefile system so it is simpler and more robust.

Kyler B Laird
Contributed corrections to the manual.

David Luff
Contributed heavily to the IO360 piston engine model.

Sam van der Mac
Contributed to The Manual by translating HTML tutorials to Latex.

Christian Mayer
Working on multi-lingual conversion tools for fgfs as a demonstration of technology. Contributed code to read Microsoft Flight Simulator scenery textures. Christian is working on a completely new weather subsystem. Donated a hot air balloon to the project.

David Megginson
Contributed patches to allow mouse input to control view direction yoke. Contributed financially towards hard drive space for use by the flight gear project. Updates to README.running. Working on getting fgfs and ssg to work without textures. Also added the new 2-D panel and the save/load support. Further, he developed new panel code, playing better with OpenGL, with new features. Developed the property manager and contributed to joystick support. Random ground cover objects

Cameron Moore
FAQ maintainer. Reigning list administrator. Provided man pages.

Eric Mitchell
Contributed some topnotch scenery textures being all original creations by him.

Anders Morken
Former maintainer of European web pages.

Alan Murta
Created the Generic Polygon Clipping library.

http://www.cs.man.ac.uk/aig/staff/alan/software/

Phil Nelson
Author of GNU dbm, a set of database routines that use extendible hashing and work similar to the standard UNIX dbm routines.

Alexei Novikov
Created European Scenery. Contributed a script to turn fgfs scenery into beautifully rendered 2-D maps. Wrote a first draft of a Scenery Creation Howto.

Curt Olson
Primary organization of the project.
First implementation and modifications based on LaRCsim.
Besides putting together all the pieces provided by others mainly concentrating on the scenery subsystem as well as the graphics stuff. Homepage at

http://www.menet.umn.edu/˜curt/

Brian Paul
We made use of his TR library and of course of Mesa:

http://www.mesa3d.org/brianp/TR.html, http://www.mesa3d.org

Tony Peden
Contributions on flight model development, including a LaRCsim based Cessna 172. Contributed to JSBSim the initial conditions code, a more complete standard atmosphere model, and other bugfixes/additions.

Robin Peel
Maintains worldwide airport and runway database for FlightGear as well as X-Plane.

Alex Perry
Contributed code to more accurately model VSI, DG, Altitude. Suggestions for improvements of the layout of the simulator on the mailing list and help on documentation.

Friedemann Reinhard
Development of an early textured instrument panel.

Petter Reinholdtsen
Incorporated the GNU automake/autoconf system (with libtool). This should streamline and standardize the build process for all UNIX-like platforms. It should have little effect on IDE type environments since they don’t use the UNIX make system.

William Riley
Contributed code to add ”brakes”. Also wrote a patch to support a first joystick with more than 2 axis. Did the job to create scenery based on VMap0 data.

Andy Ross
Contributed a new configurable FDM called YASim (Yet Another Flight Dynamics Simulator, based on geometry information rather than aerodynamic coefficients.

Paul Schlyter
Provided Durk Talsma with all the information he needed to write the astro code. Mr. Schlyter is also willing to answer astro-related questions whenever one needs to.

http://www.welcome.to/pausch/

Chris Schoeneman
Contributed ideas on audio support.

Phil Schubert
Contributed various textures and engine modeling.

http://www.zedley.com/Philip/.

Jonathan R. Shewchuk
Author of the Triangle program. Triangle is used to calculate the Delauney triangulation of our irregular terrain.

Gordan Sikic
Contributed a Cherokee flight model for LaRCsim. Currently is not working and needs to be debugged. Use configure --with-flight-model=cherokee to build the cherokee instead of the Cessna.

Michael Smith
Contributed cockpit graphics, 3D models, logos, and other images. Project Bonanza

Martin Spott
Co-Author of The Manual.

Jon Stockill
Maintains a database of objects and their location to populate the worldwide scenery.

Durk Talsma
Accurate Sun, Moon, and Planets. Sun changes color based on position in sky. Moon has correct phase and blends well into the sky. Planets are correctly positioned and have proper magnitude. Help with time functions, GUI, and other things. Contributed 2-D cloud layer. Website at

http://people.a2000.nl/dtals/.

UIUC - Department of Aeronautical and Astronautical Engineering
Contributed modifications to LaRCsim to allow loading of aircraft parameters from a file. These modifications were made as part of an icing research project.

Those did the coding and made it all work:
Jeff Scott
Bipin Sehgal
Michael Selig

Moreover, those helped to support the effort:
Jay Thomas
Eunice Lee
Elizabeth Rendon
Sudhi Uppuluri

U. S. Geological Survey

Provided geographic data used by this project.

http://edc.usgs.gov/geodata/

Mark Vallevand
Contributed some METAR parsing code and some win32 screen printing routines.

Gary R. Van Sickle
Contributed some initial GameGLUT support and other fixes. Has done preliminary work on a binary file format. Check

http://www.woodsoup.org/projs/ORKiD/fgfs.htm.

His Ćygwin Tips´p  age might be helpful for you at

http://www.woodsoup.org/projs/ORKiD/cygwin.htm.

Norman Vine
Provided more numerous URL’s to the “FlightGear Community”. Many performance optimizations throughout the code. Many contributions and much advice for the scenery generation section. Lots of Windows related contributions. Contributed wgs84 distance and course routines. Contributed a great circle route autopilot mode based on wgs84 routines. Many other GUI, HUD and autopilot contributions. Patch to allow mouse input to control view direction. Ultra hires tiled screen dumps. Contributed the initial ǵoto airportánd ŕeset´f  unctions and the initial http image server code

Roland Voegtli
Contributed great photorealistic textures. Founder of European Scenery Project for X-Plane:

http://www.g-point.com/xpcity/esp/

Carmelo Volpe
Porting FlightGear to the Metro Works development environment (PC/Mac).

Darrell Walisser
Contributed a large number of changes to porting FlightGear to the Metro Works development environment (PC/Mac). Finally produced the first Macintosh port. Contributed to the Mac part of Getting Started, too.

Ed Williams
Contributed magnetic variation code (impliments Nima WMM 2000). We’ve also borrowed from Ed’s wonderful aviation formulary at various times as well. Website at http://williams.best.vwh.net/.

Jim Wilson
Wrote a major overhaul of the viewer code to make it more flexible and modular. Contributed many small fixes and bug reports. Contributed to the PUI property browser and to the autopilot.

Jean-Claude Wippler
Author of MetaKit - a portable, embeddible database with a portable data file format previously used in FlightGear. Please see the following URL for more info:

http://www.equi4.com/metakit/

Woodsoup Project

While FlightGear no longer uses Woodsoup servies we appreciate the support provided to our project during the time they hosted us. Once they provided computing resources and services so that the FlightGear project could have a real home.

http://www.woodsoup.org/

Robert Allan Zeh
Helped tremendously in figuring out the Cygnus Win32 compiler and how to link with ḋll’s. Without him the first run-able Win32 version of FlightGear would have been impossible.

Others
The following individuals have contributed to the scenery object database: Jon Stockill, Martin Spott, Dave Martin, Thomas Foerster, Chris Metzler, Frederic Bouvier, Melchior Franz, Roberto Inzerillo, Erik Hofman, Mike Round, Innis Cunningham, David Megginson, Stuart Buchanan, Josh Babcock, Esa Hyytia, Mircea Lutic, Jens Thoms Toerring, Mark Akermann, Torsten Dreyer, Martin C. Doege, Alexis Bory, Sebastian Bechtold, Julien Pierru, Bertrand Augras, Gerard Robin, Jakub Skibinski, Morten Oesterlund Joergensen, Carsten Vogel, Dominique Lemesre, Daniel Leygnat, Bertrand Gilot, Morten Skyt Eriksen, Alex Bamesreiter, Oliver Predelli, Georg Vollnhals, and Paul Richter.

B.3 What remains to be done

If you read (and, maybe, followed) this guide up to this point you may probably agree: FlightGear even in its present state, is not at all for the birds. It is already a flight simulator which sports even several selectable flight models, several planes with panels and even a HUD, terrain scenery, texturing, all the basic controls and weather.

Despite, FlightGear needs – and gets – further development. Except internal tweaks, there are several fields where FlightGear needs basics improvement and development. A first direction is adding airports, buildings, and more of those things bringing scenery to real life and belonging to realistic airports and cities. Another task is further implementation of the menu system, which should not be too hard with the basics being working now. A lot of options at present set via command line or even during compile time should finally make it into menu entries. Finally, FlightGear lacks any ATC until now.

There are already people working in all of these directions. If you’re a programmer and think you can contribute, you are invited to do so.

Achnowledgements

Obviously this document could not have been written without all those contributors mentioned above making FlightGear a reality.

First, I was very glad to see Martin Spott entering the documentation effort. Martin provided not only several updates and contributions (notably in the OpenGL section) on the Linux side of the project but also several general ideas on the documentation in general.

Besides, I would like to say special thanks to Curt Olson, whose numerous scattered Readmes, Thanks, Webpages, and personal eMails were of special help to me and were freely exploited in the making of this booklet.

Next, Bernhard Buckel wrote several sections of early versions of that Guide and contributed at lot of ideas to it.

Jon S. Berndt supported me by critical proofreading of several versions of the document, pointing out inconsistences and suggesting improvements.

Moreover, I gained a lot of help and support from Norman Vine. Maybe, without Norman’s answers I would have never been able to tame different versions of the CygwinFlightGear couple.

We were glad, our Mac expert Darrell Walisser contributed the section on compiling under Mac OS X. In addition he submitted several Mac related hints and fixes.

Further contributions and donations on special points came from John Check, (general layout), Oliver Delise (several suggestions including notes on that chapter), Mohit Garg (OpenGL), Kyler B. Laird (corrections), Alex Perry (OpenGL), Kai Troester (compile problems), Dave Perry (joystick support), and Michael Selig (UIUC models).

Besides those whose names got lost withing the last-minute-trouble we’d like to express our gratitude to the following people for contributing valuable ‘bug fixes’ to this version of The FlightGear Manual (in random order): Cameron Moore, Melchior Franz, David Megginson, Jon Berndt, Alex Perry,, Dave Perry, Andy Ross, Erik Hofman, and Julian Foad.

Index

.fgfsrc, 57, 352
2D cockpit, 82
3D clouds, 65
3D cockpit, 82
3D panels, 350
3DFX, 341

A1 Free Sounds, 353
abort, 172
Adams, Syd, 353
additional scenery, 29
ADF, 166
Adler, Mark, 355
Aeronautical Information Manual, 129
AI, 89
aileron, 81, 165
aileron indicator, 92
Air Traffic Control, 238
air traffic facilities, 166
Air-Air Refuelling, 119
aircraft
    installation, 32
    selection, 60
aircraft aeronautical model, 61
Aircraft Carrier, 98
airport, 62, 362
airspeed indicator, 165
Airwave Xtreme 150, 25
Alonzo, Raul, 353
Altimeter, 217
altimeter, 144, 166
    tuning, 144
altitude
    absolute, 144
altitude hold, 82
America, Michele, 349, 353
artificial horizon, 165
astronomy code, 351
ATC, 350, 362
ATIS, 205
ATIS messages, 350
Atlas, 103, 352
attitude indicator, 165
audio library, 357
audio support, 351
auto coordination, 165
auto-co-ordination, 59
autopilot, 82, 87, 178, 226, 349, 356
    modes
        heading mode, 178
        roll control mode, 178
        vertical speed mode, 179
autopilot controls, 82
autothrottle, 82
Avionics, 69

Baker, Steve, 351
bank, 165
Basler, Michael, 353
Bendix transponder, 350
Berndt, Jon, 363
Berndt, Jon, S., 350, 352, 353, 362
binaries
    pre-compiled, 12
binary distribution, 11
Bleisch, Paul, 354
brakes, 81, 147, 358
    left wheel [,] (colon), 147
    right wheel [.] (dot), 147
Brennan, Jim, 354
Bright, Bernie, 354
BSD UNIX, 21
Buchanan, Stuart, 354
Buckel, Bernhard, 354, 362
Buckle, Gene, 354

Carmichael, Ralph, 354
Cessna, 359
Cessna 172, 349, 350
Chauveau, Didier, 354
Check, John, 350, 352, 354, 362
Cherokee flight model, 359
clock, 166
cloud layers, 65
clouds, 351, 359
cockpit, 82
COM transceiver, 166
COMM1, 166
COMM2, 166
command line options, 57
communication radio, 166
compiler, 23
contributors, 353
control surface, movable, 350
Cornish, Dave, 348, 355
Cygnus, 23, 361
Cygwin, 23, 343

debug, 90
default settings, 58
Delise, Oliver, 351, 352, 355, 362
Denker, John, 130
differential braking, 81
Direct3D, 23
DirectX, 23
disk space, 23
display options, 82
documentation, 21
    installation, 33
DOS, 347
Doue, Jean-Francois, 355

Eberly, Dave, 355
elevation indicator, 92
elevator, 81
engine
    shut down, 156
    starting, 79
        jet, 80
        piston, 79
        turboprop, 79
engine controls, 81
environment variables, 41
equipment, 88
Evans, Francine, 355
Everitt, Oscar, 355
exit, 85

FAA, 129
FAA Training Book, 129
FAQ, 339
FDM, 350, 353
    external, 25
    pipe, 25
FG_ROOT, 41
FG_SCENERY, 31, 42
field of view, 67
Finney, Bruce, 355
flaps, 81, 159, 165
    control lever, 159
    steps, 160
Flebbe, Olaf, 355
flight dynamics model, 24, 61, 350
flight model, 24, 61, 350
flight planner, 352
Flight simulator
    civilian, 20
    free, 347
    multi-platform, 20
    open, 20, 21
    user-extensible, 20, 21
    user-supported, 20, 21
FlightGear, 352
    versions, 24
FlightGear documentation, 25
FlightGear Flight School, 25
FlightGear forums, 339
FlightGear Programmer’s Guide, 25
FlightGear Scenery Design Guide, 25
FlightGear Website, 25, 352
flightmodels, 24
Foad, Julian, 363
fog, 67
fog effects, 357
frame rate, 23, 67, 348
Franz, Melchior, 355, 363
FreeBSD, 355
FS98, 355
fuel indicator, 166
full screen display, 66

Gailly, Jean-loup, 355
GameGLUT, 360
Garg, Mohit, 355, 362
gear, 81
Gellekum, Thomas, 355
generic autopilot, 82
geographic features, 348
Girish, Neetha, 356
GLIDE, 341
GNU C++, 23
GNU General Public License, 21
Go Around, 252
Goeke-Smith, Jeff, 349, 356
Gold, Michael, I., 356
GPL, 21
graphics card, 22
graphics routines, 347
GSHHS data, 348
gyro compass, 166

Habibe, 356
hang glider, 25
head up display, 91, 349
heading hold, 82
height, 92
help, 90
Hill, Mike, 356
History, 347
history
    aircraft, 349
    environment, 351
    scenery, 348
    user interface, 351
Hofman, Erik, 348, 356, 363
hot air balloon, 357
Hotchkiss, Charlie, 349, 356
HTTP server, 352
http server, 71
HUD, 68, 91, 92, 349, 353, 356
HUD (Head Up Display
    full mode), 184
HUD (Head Up Display), 184–186

icing
    modelling, 25
IFR, 130
ignition switch, 166
inclinometer, 165
installing aircraft, 32
instrument panel, 66, 82, 90, 349
Internet, 352

Jackson, Bruce, 347, 356
joystick, 74, 351
joystick settings, 352
joystick/self detection, 351
joysticks, 23
Justus, Maik, 356

Kaaven, Ove, 356
Kaszeta, Richard, 356
keybindings
    configuration, 80
keyboard, 80, 138
    numeric, 138
    uppercase and lowercase keys, 138
keyboard controls, 80
    display, 82
    general, 82
    view, 81
    aircraft, 81
    autopilot, 82
    engine, 81
    primary, 80
    simulator controls, 81
keyboard.xml, 80
Knienieder, Tom, 357
Koradi, Reto, 357
Korpela, Eric, 347
Kuehne, Bob, 357

Laird, Kyler B., 357, 362
landing, 169
    aid signals, 144
landing gear, 81
LaRCsim, 347, 348, 350, 356, 358, 359
latitude, 63, 92
Launching Flightgear
    Linux, 42
    Mac OS X, 47
    Windows, 45
leaflet, 12
light textures, 348
Linux, 20, 22, 23, 347
Livermore, 202
location, 86
longitude, 63, 92
Luff, David, 350, 357

magnetic compass, 166
magneto, 153
magneto switch, 350
mailing lists, 339, 353
map, clickable, 348
Mayer, Christian, 351, 352, 357
Megginson, David, 129, 348–352, 357, 363
menu, 351
menu entries, 84
menu system, 362
MetaKit, 361
Metro Works, 360
Microsoft, 19
Mitchell, Eric, 348, 357
mixture, 155, 232
    lever, 155
    optimisation, 155
Moore Cameron, 339
Moore, Cameron, 357, 363
Morken, Anders, 357
mouse, 83
    normal mode, 140
    rudder control, 147
    view mode, 140
    yoke mode, 140
mouse modes, 83
mouse pointer, 66
mouse, actions, 83
mouse, control, 83
mouse, normal, 83
mouse, view, 84
MS DevStudio, 343
MSVC, 343, 354
multi-engine support, 350
multi-lingual conversion tools, 357
Multiplayer, 95
multiplayer, 89
multiplayer code, 351
Multiple Displays, 103
Murr, David, 347
Murta, Alan, 357

NAV, 166
Navion, 350
NDB, 166
Nelson, Phil, 357
network, 352
network options, 70
networking code, 351, 355
Novikov, Alexei, 358
NumLock, 80
NVIDIA, 12

offset, 68
Olson, Curt, 347, 348, 350–352, 358, 362
OpenGL, 12, 22, 23, 25, 341, 347, 348, 352, 356
    drivers, 23
Operating Systems, 20
options
    aircraft, 60
    Aircraft Systems, 69
    debugging, 73
    environment, 64
    features, 59
    flight model, 61
    general, 57
    HUD, 68
    initial position, 62
    IO, 71
    network, 70
    orientation, 62
    rendering, 65
    route, 71
    sound, 60
    time, 69
    waypoint, 71
orientation, 63
OS/2, 347
Others, 361

panel, 90, 357, 358
parking brake, 79, 81
Paul, Brian, 358
pause, 82
Peden, Tony, 352, 358
Peel, Robin, 350, 358
permissions, 342
Perry, Alex, 358, 362, 363
Perry, Dave, 362, 363
pitch, 165
pitch indicator, 92
Playback, 108
PLIB, 351, 352
problem report, 339
problems, 339
    general, 340
    Linux, 341
    Windows, 342
programmers, 353
property manager, 352
proposal, 347

radio, 205
radio stack, 166, 350
random ground objects, 349
Reid-Hillview, 202
Reinhard, Friedemann, 349, 358
Reinholdtsen, Petter, 358
reset flight, 84
Riley, William, 348, 358
Ross, Andy, 350, 358, 363
RPM indicator, 166
rudder, 81, 165
    keyboard control, 147
    mouse control, 147
rudder indicator, 92
rudder pedals, 23
runway lighting, 348

scenery, 29, 347, 348
    additional, 29
Scenery Database, 361
scenery directory
    path, 58
scenery subsystem, 358
Schlyter, Paul, 358
Schoenemann, Chris, 359
Schubert, Phil, 359
screenshot, 85
Sectional, 198
See how it flies, 130
Selig, Michael, 350, 362
Shewchuk, Jonathan, 359
shutdown, 172
side-slip, 161
Sikic, Gordan, 359
SimGear, 352
Smith, Michael, 359
sound card, 23
sound effects, 23
source code, 21
speed, 92
    units
        knot [nautical mile per hour], 149
speed brakes, 81
spin, 161
spoilers, 81
Spott, Martin, 359, 362
stall, 161
starter, 166
Starting Flightgear
    Linux, 42
    Mac OS X, 47
    Windows, 45
starting the engine, 166
Startup latitude, 63
Startup longitude, 63
static objects, 349
Stockill, Jon, 359
Sun-OS, 21, 347
system requirements, 22
system.fgfsrc, 57, 352

tachometer, 146
tail-wheel lock, 81
Talsma, Durk, 351, 359
telnet server, 71
TerraGear, 352
Text To Speech, 110
texture, 348
textures, 348, 357
throttle, 81, 92
throttle lever, 154
thunderstorms, 351
time options, 69
Torvalds, Linus, 22
Traffic Pattern, 239
triangle program, 359
trim, 81, 162
Troester, Kai, 341, 362
troubles
    mouse speed, 142
    stuttered simulation, 136
turn coordinator, 146
turn indicator, 92, 165
tutorial, 129

U. S. Geological Survey, 347, 360
UIUC, 350, 359
UIUC flight model, 25
UNIX, 347

Vallevand, Mark, 360
van der Mac, Sam, 357
van Sickle, Gary, R., 352, 360
VASI, 249
velocity rages, 165
vertical speed indicator, 166
VFR, 130, 167
view, 85
    changing, 138
    instant replay, 139
view direction, 81
view directions, 81
view frustrum culling, 348
view modes, 82
views, 352
Vine, Norman, 349, 352, 360, 362
visual flight rules, 167
VMap0 data, 348
Voegtli, Roland, 360
Volpe, Carmelo, 360
VOR, 166

Walisser, Darrell, 360, 362
weather, 87, 357
wiki, 13
Williams, Ed, 361
Wilson, Jim, 361
window size, 68
Windows, 23
Windows 95/98/ME, 21
Windows 95/NT, 347
Windows NT/2000/XP/Seven, 21
winds, 351
windsock, 175
Wippler, Jean-Claude, 361
wireframe, 67
Wood, Charles, 130
Woodsoup, 361
workstation, 347
Wright Flyer, 25

XFree86, 342

YASim, 24
yoke, 139
    mouse yoke mode, 140, 143
    pulling, 142
yokes, 23

Zeh, Allan, 361
zlib library, 355