1
0
Fork 0
fgdata/Docs/InstallGuide/html/getstart.html
2002-02-14 23:15:39 +00:00

8176 lines
388 KiB
HTML
Raw Blame History

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html >
<head><title>FlightGear Flight Simulator - Installation and Getting Started</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="generator" content="TeX4ht (http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html)">
<!-- html -->
<meta name="src" content="getstart.tex">
<meta name="date" content="2002-02-14 12:08:00">
<link rel="stylesheet" type="text/css" href="getstart.css">
</head><body
>
<div align="center" class="maketitle">
<h2 class="titleHead">FlightGear Flight Simulator - Installation and
Getting Started</h2>
<div class="author" align="center"> <span
class="ptmr7t---120">Michael Basler (</span><a
href="mailto:pmb@epost.de" ><span
class="ptmr7t---120">pmb@epost.de</span></a><span
class="ptmr7t---120">)</span>
<br>
<br> <span
class="ptmr7t---120">including contributions by</span>
<br> <span
class="ptmr7t---120">Martin Spott (</span><a
href="mailto:Martin.Spott@uni-duisburg.de" ><span
class="ptmr7t---120">Martin.Spott@uni-duisburg.de</span></a><span
class="ptmr7t---120">),</span>
<br> <span
class="ptmr7t---120">Bernhard Buckel (</span><a
href="mailto:buckel@mail.uni-wuerzburg.de" ><span
class="ptmr7t---120">buckel@mail.uni-wuerzburg.de</span></a><span
class="ptmr7t---120">),</span>
<br> <span
class="ptmr7t---120">Curt Olson (</span><a
href="mailto:curt@flightgear.org" ><span
class="ptmr7t---120">curt@flightgear.org</span></a><span
class="ptmr7t---120">),</span>
<br> <span
class="ptmr7t---120">Jon Berndt (</span><a
href="mailto:jsb@hal-pc.org" ><span
class="ptmr7t---120">jsb@hal-pc.org</span></a><span
class="ptmr7t---120">),</span>
<br> <span
class="ptmr7t---120">Darrell Walisser </span><a
href="mailto:dwaliss1@purdue.edu" ><span
class="ptmr7t---120">dwaliss1@purdue.edu</span></a> <span
class="ptmr7t---120">and others</span>
<br> <div align="center"
class="centerline"><img
src="getstart0x.gif" alt="" class="fbox" > </div></div>
<br>
<div class="date" align="center"><span
class="ptmr7t---120">Getting Started version 0.5</span><br>
<span
class="ptmr7t---120">February, 15th, 2002</span><br>
<span
class="ptmr7t---120">This documentation was written for </span><span
class="ptmbi7t---120">FlightGear </span><span
class="ptmr7t---120">version 0.7.9.</span></div>
</div>
<h2 class="likechapterHead"><a
name="x1-1000"></a>Contents</h2> <div class="tableofcontents">
<span class="partToc"><a
href="#x1-3000I" name="QQ2-1-3">Installation</a></span>
<br> <span class="chapterToc">1 <a
href="#x1-40001" name="QQ2-1-4">Want to have a free flight? Take <span
class="ptmbi7t---109">FlightGear</span>!</a></span>
<br> &nbsp;<span class="sectionToc">1.1 <a
href="#x1-50001.1" name="QQ2-1-5">Yet another Flight Simulator?</a></span>
<br> &nbsp;<span class="sectionToc">1.2 <a
href="#x1-60001.2" name="QQ2-1-6">System requirements</a></span>
<br> &nbsp;<span class="sectionToc">1.3 <a
href="#x1-70001.3" name="QQ2-1-7">Which version should I use?</a></span>
<br> &nbsp;<span class="sectionToc">1.4 <a
href="#x1-80001.4" name="QQ2-1-8">Flight models</a></span>
<br> &nbsp;<span class="sectionToc">1.5 <a
href="#x1-90001.5" name="QQ2-1-9">To whom this guide is addressed and how it is organized</a></span>
<br> <span class="chapterToc">2 <a
href="#x1-100002" name="QQ2-1-10">Building the plane: Compiling the program</a></span>
<br> &nbsp;<span class="sectionToc">2.1 <a
href="#x1-110002.1" name="QQ2-1-11">Getting a development environment under Windows</a></span>
<br> &nbsp;<span class="sectionToc">2.2 <a
href="#x1-120002.2" name="QQ2-1-12">Compiling <span
class="ptmbi7t---109">FlightGear </span>under Linux/Windows </a></span>
<br> &nbsp;<span class="sectionToc">2.3 <a
href="#x1-130002.3" name="QQ2-1-13">Compiling <span
class="ptmbi7t---109">FlightGear </span>under Mac OS 10.1 </a></span>
<br> &nbsp;<span class="sectionToc">2.4 <a
href="#x1-140002.4" name="QQ2-1-14">Compiling on other systems</a></span>
<br> &nbsp;<span class="sectionToc">2.5 <a
href="#x1-150002.5" name="QQ2-1-15">Installing the base package</a></span>
<br> &nbsp;<span class="sectionToc">2.6 <a
href="#x1-160002.6" name="QQ2-1-16">For test pilots only: Building the CVS snapshots</a></span>
<br> <span class="chapterToc">3 <a
href="#x1-170003" name="QQ2-1-17">Preflight: Installing <span
class="ptmbi7t---109">FlightGear </span></a></span>
<br> &nbsp;<span class="sectionToc">3.1 <a
href="#x1-180003.1" name="QQ2-1-18">Installing the binary distribution on a Windows system</a></span>
<br> &nbsp;<span class="sectionToc">3.2 <a
href="#x1-190003.2" name="QQ2-1-19">Installing the binary distribution on a Macintosh system</a></span>
<br> &nbsp;<span class="sectionToc">3.3 <a
href="#x1-200003.3" name="QQ2-1-20">Installing the binary distribution on a Debian Linux system</a></span>
<br> &nbsp;<span class="sectionToc">3.4 <a
href="#x1-210003.4" name="QQ2-1-21">Installing the binary distribution on a SGI IRIX system</a></span>
<br> &nbsp;<span class="sectionToc">3.5 <a
href="#x1-220003.5" name="QQ2-1-22">Installing add-on scenery</a></span>
<br> &nbsp;<span class="sectionToc">3.6 <a
href="#x1-230003.6" name="QQ2-1-23">Installing documentation</a></span>
<br> <span class="partToc"><a
href="#x1-24000II" name="QQ2-1-24">Flying with <span
class="ptmbi7t---109">FlightGear</span></a></span>
<br> <span class="chapterToc">4 <a
href="#x1-250004" name="QQ2-1-25">Takeoff: How to start the program</a></span>
<br> &nbsp;<span class="sectionToc">4.1 <a
href="#x1-260004.1" name="QQ2-1-26">Launching the simulator under Unix/Linux</a></span>
<br> &nbsp;<span class="sectionToc">4.2 <a
href="#x1-270004.2" name="QQ2-1-27">Launching the simulator under Windows</a></span>
<br> &nbsp;<span class="sectionToc">4.3 <a
href="#x1-280004.3" name="QQ2-1-28">Launching the simulator under Mac OS X</a></span>
<br> &nbsp;<span class="sectionToc">4.4 <a
href="#x1-290004.4" name="QQ2-1-29">Command line parameters</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.1 <a
href="#x1-300004.4.1" name="QQ2-1-30">General Options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.2 <a
href="#x1-310004.4.2" name="QQ2-1-31">Features</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.3 <a
href="#x1-320004.4.3" name="QQ2-1-32">Flight model</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.4 <a
href="#x1-330004.4.4" name="QQ2-1-33">Aircraft model directory (Only for the UIUC Flight Dynamics Model)</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.5 <a
href="#x1-340004.4.5" name="QQ2-1-34">Initial Position and Orientation</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.6 <a
href="#x1-350004.4.6" name="QQ2-1-35">Rendering Options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.7 <a
href="#x1-360004.4.7" name="QQ2-1-36">HUD Options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.8 <a
href="#x1-370004.4.8" name="QQ2-1-37">Time Options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.9 <a
href="#x1-380004.4.9" name="QQ2-1-38">Network Options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.10 <a
href="#x1-390004.4.10" name="QQ2-1-39">Route/Waypoint Options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.11 <a
href="#x1-400004.4.11" name="QQ2-1-40">IO Options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.12 <a
href="#x1-410004.4.12" name="QQ2-1-41">Debugging options</a></span>
<br> &nbsp;&nbsp;<span class="subsectionToc">4.4.13 <a
href="#x1-420004.4.13" name="QQ2-1-42">Joystick properties</a></span>
<br> <span class="chapterToc">5 <a
href="#x1-430005" name="QQ2-1-43">In-flight: All about instruments, keystrokes and menus</a></span>
<br> &nbsp;<span class="sectionToc">5.1 <a
href="#x1-440005.1" name="QQ2-1-44">Starting the engine</a></span>
<br> &nbsp;<span class="sectionToc">5.2 <a
href="#x1-450005.2" name="QQ2-1-45">Keyboard controls</a></span>
<br> &nbsp;<span class="sectionToc">5.3 <a
href="#x1-460005.3" name="QQ2-1-46">Menu entries</a></span>
<br> &nbsp;<span class="sectionToc">5.4 <a
href="#x1-470005.4" name="QQ2-1-47">The Instrument Panel</a></span>
<br> &nbsp;<span class="sectionToc">5.5 <a
href="#x1-480005.5" name="QQ2-1-48">The Head Up Display</a></span>
<br> &nbsp;<span class="sectionToc">5.6 <a
href="#x1-490005.6" name="QQ2-1-49">Mouse controlled actions</a></span>
<br> &nbsp;<span class="sectionToc">5.7 <a
href="#x1-500005.7" name="QQ2-1-50">Some further reading for pilot students</a></span>
<br> <span class="partToc"><a
href="#x1-51000III" name="QQ2-1-51">Appendices</a></span>
<br> <span class="appendixToc">A <a
href="#x1-52000A" name="QQ2-1-52">Landing: Some further thoughts before leaving the plane</a></span>
<br> &nbsp;<span class="sectionToc">A.1 <a
href="#x1-53000A.1" name="QQ2-1-53">A not so Short History of <span
class="ptmbi7t---109">FlightGear</span></a></span>
<br> &nbsp;<span class="sectionToc">A.2 <a
href="#x1-54000A.2" name="QQ2-1-54">Those, who did the work</a></span>
<br> &nbsp;<span class="sectionToc">A.3 <a
href="#x1-55000A.3" name="QQ2-1-55">What remains to be done</a></span>
<br> <span class="appendixToc">B <a
href="#x1-57000B" name="QQ2-1-57">Missed approach: If anything refuses to work</a></span>
<br> &nbsp;<span class="sectionToc">B.1 <a
href="#x1-58000B.1" name="QQ2-1-58">FlightGear Problem Reports</a></span>
<br> &nbsp;<span class="sectionToc">B.2 <a
href="#x1-59000B.2" name="QQ2-1-59">General problems</a></span>
<br> &nbsp;<span class="sectionToc">B.3 <a
href="#x1-60000B.3" name="QQ2-1-60">Potential problems under Linux</a></span>
<br> &nbsp;<span class="sectionToc">B.4 <a
href="#x1-61000B.4" name="QQ2-1-61">Potential problems under Windows</a></span>
<br> <span class="appendixToc">C <a
href="#x1-62000C" name="QQ2-1-62">Some words on OpenGL graphics drivers</a></span>
<br> &nbsp;<span class="sectionToc">C.1 <a
href="#x1-63000C.1" name="QQ2-1-63">NVIDIA chip based cards under Linux</a></span>
<br> &nbsp;<span class="sectionToc">C.2 <a
href="#x1-64000C.2" name="QQ2-1-64">NVIDIA chip based cards under Windows</a></span>
<br> &nbsp;<span class="sectionToc">C.3 <a
href="#x1-65000C.3" name="QQ2-1-65">3DFX chip based cards under Windows</a></span>
<br> &nbsp;<span class="sectionToc">C.4 <a
href="#x1-66000C.4" name="QQ2-1-66">An alternative approach for Windows users</a></span>
<br> &nbsp;<span class="sectionToc">C.5 <a
href="#x1-67000C.5" name="QQ2-1-67">3DFX chip based cards under Linux</a></span>
<br> &nbsp;<span class="sectionToc">C.6 <a
href="#x1-68000C.6" name="QQ2-1-68">ATI chip based cards under Linux</a></span>
<br> &nbsp;<span class="sectionToc">C.7 <a
href="#x1-69000C.7" name="QQ2-1-69">Building your own OpenGL support under Linux</a></span>
<br> &nbsp;<span class="sectionToc">C.8 <a
href="#x1-70000C.8" name="QQ2-1-70">OpenGL on MacIntosh</a></span>
<br> <span class="chapterToc"> <a
href="#Q1-1-71">Index</a></span>
</div>
<h2 class="likechapterHead"><a
name="x1-2000"></a>Preface</h2>
<!--l. 31--><p class="noindent"><span
class="ptmbi7t---109">FlightGear </span>is a free Flight Simulator developed co-operatively over the Internet by a
group of Flight Simulation and Programming Enthusiasts. This &#8221;Installation and
Getting Started&#8221; is meant to give beginners a guide in getting the program up and
running. It is not intended to be a complete documentation of all the features
and add-ons of <span
class="ptmbi7t---109">FlightGear</span>, but just of those aspects necessary to get into the
air.
<!--l. 35--><p class="indent"> This guide is split into two parts. The first one describes how to install the program
while the second one details on how to actually fly with <span
class="ptmbi7t---109">FlightGear</span>.
<!--l. 37--><p class="indent"> In more detail, the chapters concentrate on the following aspects:
<!--l. 40--><p class="noindent"><span
class="ptmb7t---109">Part I: Installation</span>
<!--l. 44--><p class="noindent">Chapter <a
href="#x1-40001">1<!--tex4ht:ref: free--></a>, <span
class="ptmri7t---109">Want to have a free flight? Take </span><span
class="ptmbi7t---109">FlightGear</span>, introduces the concept,
describes the system requirements, and classifies the different versions available.
<!--l. 50--><p class="noindent">Chapter <a
href="#x1-100002">2<!--tex4ht:ref: building--></a>, <span
class="ptmri7t---109">Building the plane: Compiling the program</span>, explains how to build (compile
and link) the simulator. Depending on your platform this may or may not be required.
Generally, there will be executable programs (binaries) available for several
platforms. Those on such systems who want to take off immediately, without going
through the potentially troublesome process of compiling, may skip that Chapter.
<!--l. 59--><p class="noindent">In Chapter <a
href="#x1-170003">3<!--tex4ht:ref: prefligh--></a>, <span
class="ptmri7t---109">Preflight: Installing </span><span
class="ptmbi7t---109">FlightGear</span>, you will find instructions for installing the
binaries<a
name="dx1-2001"></a> in case you did not build them yourself as specified in the previous Chapter. You
will need to install scenery, textures, and other support files collected in the base
package<a
name="dx1-2002"></a>.
<!--l. 66--><p class="noindent"><span
class="ptmb7t---109">Part II: Installation</span>
<!--l. 70--><p class="noindent">The following Chapter <a
href="#x1-250004">4<!--tex4ht:ref: takeoff--></a>, <span
class="ptmri7t---109">Takeoff: How to start the program</span>, describes how to actually
start the program installed program. It includes an overview on the numerous command
line options as well as configuration files.
<!--l. 75--><p class="noindent">Chapter <a
href="#x1-430005">5<!--tex4ht:ref: flight--></a>, <span
class="ptmri7t---109">In-flight: All about instruments, keystrokes and menus</span>, describes how to
operate the program, i. e. how to actually fly with <span
class="ptmbi7t---109">FlightGear</span>. This includes a (hopefully)
complete list of pre-defined keystroke commands, an overview on the menu entries,
detailed descriptions of instrument panel and HUD (head up display) as well as hints on
using the mouse functions.
<!--l. 83--><p class="noindent">In Appendix <a
href="#x1-52000A">A<!--tex4ht:ref: landing--></a>, <span
class="ptmri7t---109">Landing: Some further thoughts before leaving the plane</span>, we would like
to give credit to those who deserve it, sketch an overview on the development of
<span
class="ptmbi7t---109">FlightGear</span>and point out what remains to be done.
<!--l. 89--><p class="noindent">In Appendix <a
href="#x1-57000B">B<!--tex4ht:ref: missed--></a>, <span
class="ptmri7t---109">Missed approach: If anything refuses to work</span>, we try to give you a hand
in case of some common problems faced with <span
class="ptmbi7t---109">FlightGear</span>.
<!--l. 94--><p class="noindent">The final chapter <a
href="#x1-62000C">C<!--tex4ht:ref: opengl--></a>, <span
class="ptmri7t---109">OpenGL graphics drivers</span>, describes some special problems you may
entounter in case your system lacks support for the graphics engine called OpenGL<a
name="dx1-2003"></a>
which <span
class="ptmbi7t---109">FlightGear </span>is based on.
<!--l. 99--><p class="noindent">Accordingly, we suggest reading the Chapters as follows:
<!--l. 104--><p class="noindent"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0"
frame="void" id="TBL-2-" ><colgroup id="TBL-2-1g"><col
id="TBL-2-1"><col
id="TBL-2-2"></colgroup><tr
valign="baseline" id="TBL-2-1-"><td align="left" nowrap="nowrap" id="TBL-2-1-1"
class="td11"> <span
class="ptmb7t---109">Installation </span></td><td align="left" nowrap="nowrap" id="TBL-2-1-2"
class="td11"> </td>
</tr><tr
valign="baseline" id="TBL-2-2-"><td align="left" nowrap="nowrap" id="TBL-2-2-1"
class="td11"> Users of binary distributions (notably under Windows):</td><td align="left" nowrap="nowrap" id="TBL-2-2-2"
class="td11"> <a
href="#x1-170003">3<!--tex4ht:ref: prefligh--></a> </td>
</tr><tr
valign="baseline" id="TBL-2-3-"><td align="left" nowrap="nowrap" id="TBL-2-3-1"
class="td11"> Installation under Linux/UNIX: </td><td align="left" nowrap="nowrap" id="TBL-2-3-2"
class="td11"> <a
href="#x1-100002">2<!--tex4ht:ref: building--></a>, <a
href="#x1-170003">3<!--tex4ht:ref: prefligh--></a> </td>
</tr><tr
valign="baseline" id="TBL-2-4-"><td align="left" nowrap="nowrap" id="TBL-2-4-1"
class="td11"> Installation under MacIntosh: </td><td align="left" nowrap="nowrap" id="TBL-2-4-2"
class="td11"> <a
href="#x1-170003">3<!--tex4ht:ref: prefligh--></a> </td>
</tr><tr
valign="baseline" id="TBL-2-5-"><td align="left" nowrap="nowrap" id="TBL-2-5-1"
class="td11"> <span
class="ptmb7t---109">Operation </span></td><td align="left" nowrap="nowrap" id="TBL-2-5-2"
class="td11"> </td>
</tr><tr
valign="baseline" id="TBL-2-6-"><td align="left" nowrap="nowrap" id="TBL-2-6-1"
class="td11"> Program start (all users): </td><td align="left" nowrap="nowrap" id="TBL-2-6-2"
class="td11"> <a
href="#x1-250004">4<!--tex4ht:ref: takeoff--></a> </td>
</tr><tr
valign="baseline" id="TBL-2-7-"><td align="left" nowrap="nowrap" id="TBL-2-7-1"
class="td11"> Keycodes, Panel, Mouse. . . (all users): </td><td align="left" nowrap="nowrap" id="TBL-2-7-2"
class="td11"> <a
href="#x1-430005">5<!--tex4ht:ref: flight--></a> </td>
</tr><tr
valign="baseline" id="TBL-2-8-"><td align="left" nowrap="nowrap" id="TBL-2-8-1"
class="td11"> <span
class="ptmb7t---109">Troubleshooting </span></td><td align="left" nowrap="nowrap" id="TBL-2-8-2"
class="td11"> </td>
</tr><tr
valign="baseline" id="TBL-2-9-"><td align="left" nowrap="nowrap" id="TBL-2-9-1"
class="td11"> Generally </td><td align="left" nowrap="nowrap" id="TBL-2-9-2"
class="td11"> <a
href="#x1-57000B">B<!--tex4ht:ref: missed--></a> </td>
</tr><tr
valign="baseline" id="TBL-2-10-"><td align="left" nowrap="nowrap" id="TBL-2-10-1"
class="td11"> Graphics problems: </td><td align="left" nowrap="nowrap" id="TBL-2-10-2"
class="td11"> <a
href="#x1-62000C">C<!--tex4ht:ref: opengl--></a> </td>
</tr><tr
valign="baseline" id="TBL-2-11-"><td align="left" nowrap="nowrap" id="TBL-2-11-1"
class="td11"> <span
class="ptmb7t---109">Optionally </span></td><td align="left" nowrap="nowrap" id="TBL-2-11-2"
class="td11"> <a
href="#x1-40001">1<!--tex4ht:ref: free--></a>, <a
href="#x1-52000A">A<!--tex4ht:ref: landing--></a></td>
</tr><!--ll--></table>
</div>
<!--l. 121--><p class="noindent">While this introductory guide is meant to be self contained, we stronly suggest having a
look into further documentation, notably in case of trouble:
<ul class="itemize1">
<li class="itemize">For additional hints on troubleshooting and more, see the <span
class="ptmb7t---109">FAQ</span><a
name="dx1-2004"></a> at
<!--l. 128--><p class="noindent"><a
href="http://www.flightgear.org/Docs/FlightGear-FAQ.html" >http://www.flightgear.org/Docs/FlightGear-FAQ.html</a>,
<!--l. 131--><p class="noindent">The FAQ contains a host of valuable information, notably on rapidly
changing flaws and additional reading, thus we strongly suggest consulting
it joiontly with our guide.
</li>
<li class="itemize">A handy <span
class="ptmb7t---109">leaflet</span><a
name="dx1-2005"></a> on operation for printout is available at
<!--l. 137--><p class="noindent"><a
href="http://www.flightgear.org/Docs/InstallGuide/FGShortRef.html" >http://www.flightgear.org/Docs/InstallGuide/FGShortRef.html</a>,
</li>
<li class="itemize">Additional user documentation on special aspects is available within the base
package under the directory <span
class="pcrr7t---109">/FlightGear/Docs</span>.</li></ul>
<!--l. 142--><p class="noindent">Finally:
<!--l. 147--><p class="indent"> We know, most people hate reading manuals. If you are sure the graphics driver for
your card supports OpenGL<a
name="dx1-2006"></a> (check documentation; for instance all NVIDIA<a
name="dx1-2007"></a> Windows
and Linux drivers for TNT<a
name="dx1-2008"></a>/TNT2/Geforce<a
name="dx1-2009"></a>/Geforce2/Geforce3 do) and if you are using
one of the following operating systems:
<ul class="itemize1">
<li class="itemize">Windows<a
name="dx1-2010"></a> 95/98/ME/NT/2000/XP,
</li>
<li class="itemize">Macintosh<a
name="dx1-2011"></a> Mac OSX
</li>
<li class="itemize">Debian Linux<a
name="dx1-2012"></a>
</li>
<li class="itemize">SGI Irix<a
name="dx1-2013"></a></li></ul>
<!--l. 156--><p class="noindent">you can possibly skip at least Part I of this manual and exploit the pre-compiled
binaries<a
name="dx1-2014"></a>. These as well as instructions on how to set them up can be found at
<!--l. 160--><p class="indent"> <a
href="http://www.flightgear.org/Downloads/" >http://www.flightgear.org/Downloads/</a>.
<!--l. 163--><p class="noindent">In case of running FlightGear on Linux you may also get Binareis bundled with your
distrinbution. Several vendoes already include <span
class="ptmbi7t---109">FlightGear </span>binaries into their
distributions.
<!--l. 166--><p class="indent"> Just download them, install them according to the description and run them via the
attached script <span
class="pcrr7t---109">runfgfs </span>or batch file <span
class="pcrr7t---109">runfgfs.bat</span>, resp.
<!--l. 168--><p class="indent"> There is no guarantee for this approach to work, though. If it doesn&#8217;t, don&#8217;t give up,
but have a closer look into the present manual, notably Section <a
href="#x1-170003">3<!--tex4ht:ref: prefligh--></a>, as well as into the
FAQ.
<h1 class="partHead"><span class="titlemark">Part&nbsp;I<br></span><a
name="x1-3000I"></a>Installation</h1>
<h2 class="chapterHead"><span class="titlemark">Chapter&nbsp;1</span><br><a
name="x1-40001"></a>Want to have a free flight? Take <span
class="ptmbi7t---109">FlightGear</span>!</h2>
<h3 class="sectionHead"><span class="titlemark">1.1</span> <a
name="x1-50001.1"></a>Yet another Flight Simulator?</h3>
<!--l. 37--><p class="noindent">Did you ever want to fly a plane yourself, but lacked the money or ability to do so? Are
you a real pilot looking to improve your skills without having to take off? Do you want to
try some dangerous maneuvers without risking your life? Or do you just want to have fun
with a more serious game not killing any people? If any of these questions applies, PC
flight simulators are just for you.
<!--l. 43--><p class="indent"> You already may have some experience using Microsoft<a
name="dx1-5001"></a>&#8217;s &copy; Flight Simulator or any
other of the commercially available PC flight simulators. As the price tag of those is
usually within the $50 range buying one of them should not be a serious problem given
that running any serious PC flight simulator requires a hardware within the $1500 range,
despite dropping prices, at least.
<!--l. 48--><p class="indent"> Why then that effort of spending hundreds or thousands of hours of programming to
build a free simulator? Obviously there must be good reason to do so:
<ul class="itemize1">
<li class="itemize">All of the commercial programs have a serious drawback: They are made
by a small group of developers defining their properties - often quite inert
and not listening too much to the customer. Anyone ever trying to contact
Microsoft<a
name="dx1-5002"></a> will immediately agree.
</li>
<li class="itemize">Commercial PC flight simulators usually try to cover a market segment as
broad as possible. For obvious reason, most of them want to serve the serious
pilot as well as the beginner and the gamer. The result is a compromise. As
<span
class="ptmbi7t---109">FlightGear </span>is free, there is no need for such compromise; it just can be given
the properties its users want. It defines itself via building.
</li>
<li class="itemize">Building a flight simulator is a challenge to the art of programming.
Contributing to that project makes you belong to those being able to
contribute to serious, ambitious and advanced software projects.
</li>
<li class="itemize">It is fun. Not only is it fun to write the code (. . . or documentation. . . ) but
also to belong to that - temporarily changing - club of clever people on the
net having discussed, struggled and finally succeeded in creating that project.
Even reading the <span
class="ptmbi7t---109">FlightGear </span>mailing lists is informative and fun for itself.</li></ul>
<!--l. 75--><p class="noindent">The above-mentioned points make <span
class="ptmbi7t---109">FlightGear </span>superior to its competitors in several
respect. <span
class="ptmbi7t---109">FlightGear </span>aims to be a civilian,<a
name="dx1-5003"></a> multi-platform,<a
name="dx1-5004"></a> open,<a
name="dx1-5005"></a> user-supported,<a
name="dx1-5006"></a>
user-extensible<a
name="dx1-5007"></a> platform.
<!--l. 84--><p class="indent"> <div align="center"
class="centerline"><img
src="getstart1x.gif" alt="" class="fbox" > </div>
<!--l. 87--><p class="noindent">Fig. 1: <span
class="ptmbi7t---109">FlightGear </span><span
class="ptmri7t---109">under UNIX: Bad approach to San Francisco International - by one of</span>
<span
class="ptmri7t---109">the authors of this manual. . .</span>
<ul class="itemize1">
<li class="itemize"><span
class="ptmb7t---109">Civilian:</span><a
name="dx1-5008"></a> The project is primarily aimed at civilian flight simulation. It
should be appropriate for simulating general aviation as well as civilian
aircraft. It is not a shoot&#8217;m-up game. However, in keeping with the open
concept of development, this naturally does not exclude someone taking the
code and integrating say weapon systems<a
name="dx1-5009"></a>, for instance.
</li>
<li class="itemize"><span
class="ptmb7t---109">Multi-platform:</span><a
name="dx1-5010"></a> The developers are attempting to keep the code as
platform-independent as possible. This is based on their observation that people
interested in flight simulations run quite a variety of computer hardware and
operating systems. The present code supports the following Operating
Systems<a
name="dx1-5011"></a>:
<ul class="itemize2">
<li class="itemize">Linux<a
name="dx1-5012"></a> (any distribution and platform),
</li>
<li class="itemize">Windows NT/2000/XP<a
name="dx1-5013"></a> (Intel/AMD platform),
</li>
<li class="itemize">Windows 95/98/ME<a
name="dx1-5014"></a>,
</li>
<li class="itemize">BSD UNIX<a
name="dx1-5015"></a>,
</li>
<li class="itemize">SGI IRIX<a
name="dx1-5016"></a>,
</li>
<li class="itemize">Sun-OS<a
name="dx1-5017"></a>,
</li>
<li class="itemize">Macintosh.</li></ul>
<!--l. 117--><p class="noindent">At present, there is no known flight simulator - commercial or free - supporting
such a broad range of platforms.
</li>
<li class="itemize"><span
class="ptmb7t---109">Open:</span><a
name="dx1-5018"></a> The project is not restricted to a static or elite cadre of developers. Anyone
who feels he or she is able to contribute is most welcome. The code (including
documentation) is copyrighted under the terms of the GPL<a
name="dx1-5019"></a> (Gnu Public
License<a
name="dx1-5020"></a>).
<!--l. 126--><p class="noindent">The GPL<a
name="dx1-5021"></a> is often misunderstood. In simple terms it states that you can copy and
freely distribute the program(s) so licensed. You can modify them if you like. You
are even allowed to charge as much money for the distribution of the modified or
original program as you want. However, you must distribute it complete with the
entire source code and it must retain the original copyrights. In short:
<!--l. 134--><p class="noindent"><div align="center"
class="centerline"> <span
class="ptmri7t---109">&#8221;You can do anything with the software except make it non-free&#8221;</span>. </div>
<!--l. 136--><p class="noindent">The full text of the GPL<a
name="dx1-5022"></a> can be obtained from
<!--l. 139--><p class="noindent"><a
href="http://www.gnu.org/copyleft/gpl.html" >http://www.gnu.org/copyleft/gpl.html</a>.
</li>
<li class="itemize"><span
class="ptmb7t---109">User-supported, user-extensible:</span><a
name="dx1-5023"></a> <a
name="dx1-5024"></a>Contrary to various commercial simulators
available, scenery and aircraft format, internal variables, etc. are user
accessible and documented from the beginning. Even without an explicit
development documentation<a
name="dx1-5025"></a> (which naturally has to be written at some
point) this is guaranteed by supplying the source code<a
name="dx1-5026"></a>. It is the goal of the
developers to build a basic engine to which scenery designers, panel engineers,
maybe adventure or ATC routine writers, sound artists, and others can (and
are solicited to) add. It is our hope, that the project will benefit from the
creativity and ideas of the hundreds of talented &#8221;simmers&#8221; around the
world.</li></ul>
<!--l. 155--><p class="noindent">Without doubt, the success of the Linux<a
name="dx1-5027"></a> project initiated by Linus Torvalds<a
name="dx1-5028"></a> inspired
several of the developers. Not only has it shown that distributed development of even
highly sophisticated software projects over the Internet is possible.
<h3 class="sectionHead"><span class="titlemark">1.2</span> <a
name="x1-60001.2"></a>System requirements</h3>
<a
name="dx1-6001"></a>
<!--l. 164--><p class="noindent">In comparison to other recent flight simulators the system requirements<a
name="dx1-6002"></a> for <span
class="ptmbi7t---109">FlightGear</span>
are not extravagant. A decent PII/400 or something in that range should be sufficient,
given you have a proper 3-D graphics card<a
name="dx1-6003"></a>. On the other hand, any modern
UNIX<a
name="dx1-6004"></a>-type workstation<a
name="dx1-6005"></a> with a 3D graphics card will handle <span
class="ptmbi7t---109">FlightGear </span>as
well.
<!--l. 170--><p class="indent"> One important prerequisite for running <span
class="ptmbi7t---109">FlightGear </span>is a graphics card whose driver
supports OpenGL<a
name="dx1-6006"></a>. If you don&#8217;t know what OpenGL<a
name="dx1-6007"></a> is, the overview given at the
OpenGL web site
<!--l. 174--><p class="indent"> <a
href="http://www.opengl.org" >http://www.opengl.org</a>
<!--l. 177--><p class="noindent">says it best: &#8221;Since its introduction in 1992, OpenGL has become the industry&#8217;s most
widely used and supported 2-D and 3-D graphics application programming interface
(API)...&#8221;.
<!--l. 182--><p class="indent"> <span
class="ptmbi7t---109">FlightGear </span>does not run (and will never run) on a graphics board supporting
Direct3D<a
name="dx1-6008"></a> only. Contrary to openGL, Direct3D is a propriatary interface, being restricted
to the Windows operating system.
<!--l. 184--><p class="indent"> You may be able to run <span
class="ptmbi7t---109">FlightGear </span>on a computer that features a 3-D video card
not supporting hardware accelerated OpenGL<a
name="dx1-6009"></a> - and even on systems without
3-D graphics hardware at all. However, the absence of hardware accelerated
OpenGL support can force even the fastest machine to its knees. The typical
signal for missing hardware acceleration are frame rate<a
name="dx1-6010"></a>s below 1 frame per
second.
<!--l. 190--><p class="indent"> Any more recent 3-D graphics featuring hardware OpenGL<a
name="dx1-6011"></a> will do. For Windows<a
name="dx1-6012"></a>
video card drivers that support OpenGL, visit the home page of your video card
manufacturer. You should note, that sometimes OpenGL drivers<a
name="dx1-6013"></a> are provided by the
manufacturers of the graphics chip instead of by the makers of the board. If you are
going to buy a graphics card for running <span
class="ptmbi7t---109">FlightGear</span>, one based on a NVIDIA chip (TNT
X/Geforce X) might be a good choice.
<!--l. 197--><p class="indent"> To install the executable and basic scenery, you will need around 50 MB of free disk
space<a
name="dx1-6014"></a>. In case you want/have to to compile the program yourself you will need additional
about 500 MB for the source code and for temporary files created during compilation.
This does not yet include the development environment, which possibly may have to be
installed under Windows yet, and which amounts to additional around 300 MB,
depending on the installed packages.
<!--l. 202--><p class="indent"> For the sound effects<a
name="dx1-6015"></a> any capable sound card<a
name="dx1-6016"></a> should suffice. Based on its flexible
concept, <span
class="ptmbi7t---109">FlightGear </span>supports a wide range of joysticks<a
name="dx1-6017"></a> or yokes<a
name="dx1-6018"></a> as well esd rudder
pedals<a
name="dx1-6019"></a> under Linux<a
name="dx1-6020"></a> as well as under Windows<a
name="dx1-6021"></a>.
<!--l. 205--><p class="indent"> <span
class="ptmbi7t---109">FlightGear </span>is being developed primarily under Linux<a
name="dx1-6022"></a>, a free UNIX clone (together
with lots of GNU utilities) developed cooperatively over the Internet in much the same
spirit as <span
class="ptmbi7t---109">FlightGear </span>itself. <span
class="ptmbi7t---109">FlightGear </span>also runs and is partly developed under several
flavors of Windows<a
name="dx1-6023"></a>. Building <span
class="ptmbi7t---109">FlightGear </span>is possible on a Macintosh (OSX) and on
several UNIX/X11 workstations, as well. Given you have a proper compiler<a
name="dx1-6024"></a> installed,
<span
class="ptmbi7t---109">FlightGear </span>can be built under all of these platforms. The primary compiler
for all platforms is the free GNU C++<a
name="dx1-6025"></a> compiler (the Cygnus <a
name="dx1-6026"></a>compiler under
Win32).
<!--l. 212--><p class="indent"> If you want to run <span
class="ptmbi7t---109">FlightGear </span>under Mac OS X we suggest a Power PC G3 300 MHz
or better. As a graphics card we would suggersr an ATI Rage 128 based card as a
minimum. Joysticks are supported under Mac OS 9.x only; there is no joystick support
under Max OSX available (yet).
<h3 class="sectionHead"><span class="titlemark">1.3</span> <a
name="x1-70001.3"></a>Which version should I use?</h3>
<a
name="dx1-7001"></a>
<!--l. 219--><p class="noindent">Concerning the <span
class="ptmbi7t---109">FlightGear </span>source code there exist two branches, a stable one and a
developmental branch.<a
name="dx1-7002"></a><a
name="dx1-7003"></a> Even version numbers like 0.6, 0.8, and (someday hopefully) 1.0
refer to stable releases, while odd numbers like 0.7, 0.9, and so on refer to developmental
releases. The policy is to only do bug fixes in the even versions, while new features are
generally added to odd-numbered versions which, after all things have stabilized, will
become the next stable release with a version number calculated by adding 0.1.
<!--l. 225--><p class="indent"> To add to the confusion, there usually are several versions of the &#8221;unstable&#8221; branch.
First, there is a &#8221;latest official release&#8221; which the pre-compiled binaries are based on. It is
available from
<!--l. 230--><p class="indent"> <a
href="ftp://ftp.flightgear.org/pub/fgfs/Source/FlightGear-X.X.X.tar.gz" ></a>
<!--l. 232--><p class="indent"> For developers there exist CVS snapshots<a
name="dx1-7004"></a><a
name="dx1-7005"></a> of the source code, available from
<!--l. 235--><p class="indent"> <a
href="ftp://www.flightgear.org/pub/flightgear/Devel/Snapshots/" >ftp://www.flightgear.org/pub/flightgear/Devel/Snapshots/</a>.
<!--l. 238--><p class="noindent">While theses are quite recent, they may still be sometimes a few days back behind
development. Thus, if you really want to get the very latest and greatest (and, at
times, buggiest) code, you can use a tool called anonymous cvs<a
name="dx1-7006"></a><a
name="dx1-7007"></a> available from
<!--l. 245--><p class="indent"> <a
href="http://www.cvshome.org/" >http://www.cvshome.org/</a>
<!--l. 248--><p class="noindent">to get the recent code. A detailed description of how to set this up for <span
class="ptmbi7t---109">FlightGear </span>can be
found at
<!--l. 253--><p class="indent"> <a
href="http://www.flightgear.org/cvsResources/" >http://www.flightgear.org/cvsResources/</a>.
<!--l. 256--><p class="noindent">Unfortunately, the system implemented above does not really work as it should. As a
matter of fact, the stable version is usually so much outdated, that it does not at all reflect
thee stated of development <span
class="ptmbi7t---109">FlightGear </span>has reached. Given that the recent developmental
versions on the other hands may contain bugs (. . . undocumented features), we
recommend using the &#8221;latest official (unstable) release&#8221; for the average user. This is the
latest version named at
<!--l. 261--><p class="indent"> <a
href="http://www.flightgear.org/News/" >http://www.flightgear.org/News/</a>;
<!--l. 264--><p class="noindent">usually this is also the version which the binary distributions<a
name="dx1-7008"></a> available at
<!--l. 268--><p class="indent"> <a
href="http://www.flightgear.org/Downloads/" >http://www.flightgear.org/Downloads/</a>
<!--l. 271--><p class="noindent">are based on. If not otherwise stated, all procedures in this &#8221;Installation and Getting
Started&#8221; will be based on these packages.
<h3 class="sectionHead"><span class="titlemark">1.4</span> <a
name="x1-80001.4"></a>Flight models</h3>
<a
name="dx1-8001"></a>
<a
name="dx1-8002"></a>
<!--l. 278--><p class="noindent">Historically, <span
class="ptmbi7t---109">FlightGear </span>has been based on a flight model it inherited (together with the
Navion airplane) from LaRCsim. As this had several limitations (most important,
many characteristics were hard wired in contrast to using configuration files),
there were several attempts to develop or include alternative flight models<a
name="dx1-8003"></a>. As a
result, <span
class="ptmbi7t---109">FlightGear </span>supports several different flight models, to be chosen from at
runtime.
<!--l. 284--><p class="indent"> The most important one is the JSB flight model developed by Jon Berndt. Actually,
the JSB flight model is part of a stand-alone project called <span
class="ptmbi7t---109">JSBSim</span>, having its home at
<!--l. 288--><p class="indent"> <a
href="http://jsbsim.sourceforge.net/" >http://jsbsim.sourceforge.net/</a>.
<!--l. 291--><p class="noindent">Concerning airplanes, the JSB flight model at present provides support for a Cessna 172<a
name="dx1-8004"></a>,
a Cessna 182<a
name="dx1-8005"></a>, a Cessna 310<a
name="dx1-8006"></a>, and for an experimental plane called X15<a
name="dx1-8007"></a>. Jon and his
group are gearing towards a very accurate flight model, and the JSB model is
expected to become <span
class="ptmbi7t---109">FlightGear</span>&#8217;s default flight model some time in the near
future.
<!--l. 297--><p class="indent"> As an interesting alternative, Christian Mayer developed a flight model of a hot air
balloon. Moreover, Curt Olson integrated a special slew mode called Magic Carpet,
which helps you to quickly fly from point A to point B.
<!--l. 301--><p class="indent"> Recently, Andrew Ross contributed another flight model called <span
class="ptmbi7t---109">YASim </span>for <span
class="ptmri7t---109">Yet</span>
<span
class="ptmri7t---109">another simulator</span>. At present, it sports another Cessna 172<a
name="dx1-8008"></a>, a Cessna 182<a
name="dx1-8009"></a> and a Boeing
747<a
name="dx1-8010"></a>. This one is based on geometry information rather than aerodynamic coefficients.
Although it is not that sophisticated like e.g. <span
class="ptmbi7t---109">JSBSim </span>it is intended to be &#8221;very somple to
use&#8221; and lets you fly many differnet airplanes.
<!--l. 303--><p class="indent"> As a further alternative, there is the UIUC flight model<a
name="dx1-8011"></a>, developed by a team from the
University of Illinois, independently from <span
class="ptmbi7t---109">FlightGear </span>in the beginning (while now using
it for their simulations). This project aims at studying the simulation of aircraft icing. Its
home is at
<!--l. 309--><p class="indent"> <a
href="http://amber.aae.uiuc.edu/~jscott/sis/" >http://amber.aae.uiuc.edu/&nbsp;jscott/sis/</a>.
<!--l. 312--><p class="noindent">The UIUC provides a host of different aircraft including several Cessna C172<a
name="dx1-8012"></a>, a Learjet
24<a
name="dx1-8013"></a>, a Twin Otter<a
name="dx1-8014"></a> and much more. To get an idea, you may check the folder
<span
class="pcrr7t---109">Aircraft-UIUC </span>of the <span
class="ptmbi7t---109">FlightGear </span>path.
<!--l. 317--><p class="indent"> Please note, that the UIUC models do <span
class="ptmb7t---109">not </span>have a working gear. So you might
experience some difficulties when starting from a runway. At least the nose gear will be
too weak and the airplane will fall on it&#8217;s nose. This can be circumvented by pulling the
stick more than usual for a while.
<!--l. 319--><p class="indent"> It is even possible to drive FlightGear&#8217;s scene display using an external FDM<a
name="dx1-8015"></a> running
on a different computer - although this might not be a setup recommended to people just
getting in touch with <span
class="ptmbi7t---109">FlightGear</span>.
<h3 class="sectionHead"><span class="titlemark">1.5</span> <a
name="x1-90001.5"></a>To whom this guide is addressed and how it is organized</h3>
<!--l. 330--><p class="noindent">There is little, if any, material in this Guide that is presented here exclusively. You could
even say with Montaigne that we &#8221;merely gathered here a big bunch of other men&#8217;s
flowers, having furnished nothing of my own but the strip to hold them together&#8221;. Most
(but fortunately not all) of the information can as well be obtained from the <span
class="ptmbi7t---109">FlightGear</span>
web site<a
name="dx1-9001"></a> located at:
<!--l. 337--><p class="indent"> <a
href="http://www.flightgear.org/" >http://www.flightgear.org/</a>
<!--l. 340--><p class="indent"> Please, keep in mind that there are several mirrors to all <span
class="ptmbi7t---109">FlightGear </span>Web sites, being
listed on this page. Sometimes it is preferred to download from them than from the
original place.
<!--l. 342--><p class="noindent">However, a neatly printed manual is arguably preferable over loosely scattered <span
class="ptmri7t---109">Readme</span>
files by some people, and those people may acknowledge the effort.
<!--l. 346--><p class="indent"> This <span
class="ptmbi7t---109">FlightGear </span><span
class="ptmri7t---109">Installation and Getting Started </span>manual is intended to be a first step
towards a more complete <span
class="ptmbi7t---109">FlightGear </span>documentation<a
name="dx1-9002"></a> (with the other parts, hopefully, to
be written by others). The target audience is the end-user who is not interested in
the internal workings of OpenGL<a
name="dx1-9003"></a> or in building his or her own scenery, for
instance. It is our hope, that someday there will be an accompanying <span
class="ptmbi7t---109">FlightGear</span>
<span
class="ptmri7t---109">Programmer&#8217;s Guide</span><a
name="dx1-9004"></a> (which could be based on some of the documentation found at
<!--l. 355--><p class="indent"> <a
href="http://www.flightgear.org/Docs" >http://www.flightgear.org/Docs</a>;
<!--l. 358--><p class="noindent">a <span
class="ptmbi7t---109">FlightGear </span><span
class="ptmri7t---109">Scenery Design Guide</span>,<a
name="dx1-9005"></a> describing the Scenery tools now packaged as
<span
class="ptmbi7t---109">TerraGear</span>; and a <span
class="ptmbi7t---109">FlightGear </span><span
class="ptmri7t---109">Flight School</span><a
name="dx1-9006"></a>, at least.
<!--l. 364--><p class="indent"> As a supplement, we recommend reading the <span
class="ptmbi7t---109">FlightGear </span>FAQ to be found
at
<!--l. 366--><p class="indent"> <a
href="http://www.flightgear.org/Docs/FlightGear-FAQ.html" >http://www.flightgear.org/Docs/FlightGear-FAQ.html</a>
<!--l. 368--><p class="indent"> which has a lot of supplementary information to (and, at times, more recent than) the
present document.
<!--l. 375--><p class="indent"> <span
class="ptmb7t---109">We kindly ask you to help me refine this document by submitting corrections,</span>
<span
class="ptmb7t---109">improvements, and more. Any user is invited to contribute descriptions of</span>
<span
class="ptmb7t---109">alternative setups (graphics cards, operating systems etc.). We will be more than</span>
<span
class="ptmb7t---109">happy to include those into future versions of this </span><span
class="ptmbi7t---109">Installation and Getting Started </span><span
class="ptmb7t---109">(of</span>
<span
class="ptmb7t---109">course not without giving credit to the authors).</span>
<!--l. 377--><p class="indent"> While we intend to continuously update this document at least for the foreseeable
future, supposedly we will not be able to produce a new one for any single release of
<span
class="ptmbi7t---109">FlightGear</span>. While we are watching the mailing lists, it would help if developers adding
new functionality would send us a short note.
<h2 class="chapterHead"><span class="titlemark">Chapter&nbsp;2</span><br><a
name="x1-100002"></a>Building the plane: Compiling the program</h2>
<!--l. 33--><p class="noindent">This central chapter describes how to build <span
class="ptmbi7t---109">FlightGear </span>on several systems. In case you
are on a Win32 (i. e. Windows95/98/ME/NT/2000/XP) platform or any of the other
platforms which binary executables are available for, you may not want to go though that
potentially troublesome process but skip that chapter instead and straightly
go to the next one. (Not everyone wants to build his or her plane himself or
herself, right?) However, there may be good reason for at least trying to build the
simulator:
<ul class="itemize1">
<li class="itemize">In case you are on a UNIX<a
name="dx1-10001"></a>/Linux<a
name="dx1-10002"></a> platform there may be no pre-compiled
binaries<a
name="dx1-10003"></a> available for your system. In practice it is common to install
programs like this one on UNIX<a
name="dx1-10004"></a> systems by recompiling them.
</li>
<li class="itemize">There are several options you can set during compile time only.
</li>
<li class="itemize">You may be proud you did.</li></ul>
<!--l. 51--><p class="noindent">On the other hand, compiling <span
class="ptmbi7t---109">FlightGear </span>is not a task for novice users. Thus, if you&#8217;re a
beginner (we all were once) on a platform which binaries<a
name="dx1-10005"></a> are available for, we
recommend postponing this task and just starting with the binary distribution<a
name="dx1-10006"></a> to get you
flying.
<!--l. 56--><p class="indent"> As you will notice, this Chapter is far from being complete. Basically, we describe
compiling for two operating systems only, Windows<a
name="dx1-10007"></a> and Linux<a
name="dx1-10008"></a>, and for only one
compiler, the GNU C compiler. <span
class="ptmbi7t---109">FlightGear </span>has been shown to be built under different
compilers (including Microsoft Visual C) as well as different systems (Macintosh) as
well. The reason for these limitations are:
<ul class="itemize1">
<li class="itemize">Personally, we have access to a Windows machine running the Cygnus
compiler only.
</li>
<li class="itemize">According to the mailing lists, these seem to be the systems with the largest
user base.
</li>
<li class="itemize">These are the simplest systems to compile <span
class="ptmbi7t---109">FlightGear </span>on. Other compilers
may need special add-ons (workplace etc.) or even modification of the code.
</li>
<li class="itemize">The GNU compiler is free in the same sense of the GPL as <span
class="ptmbi7t---109">FlightGear </span>is.</li></ul>
<!--l. 70--><p class="noindent">You might want to check Section <a
href="#x1-57000B">B<!--tex4ht:ref: missed--></a>, <span
class="ptmri7t---109">Missed approach</span>, if anything fails during
compilation. In case this does not help we recommend sending a note to one of the
mailing lists (for hints on subscription see Chapter <a
href="#x1-52000A">A<!--tex4ht:ref: landing--></a>).
<!--l. 73--><p class="indent"> There are several Linux distributions<a
name="dx1-10009"></a> on the market, and most of them should work.
Some come even bundled with (often outdated) versions of <span
class="ptmbi7t---109">FlightGear</span>. However, if you
are going to download or buy a distribution, Debian<a
name="dx1-10010"></a> (Woody) is suggested by most
people. SuSE<a
name="dx1-10011"></a> works well, too.
<!--l. 77--><p class="indent"> Contrary to Linux/Unix systems, Windows usually comes without any development
tools. This way, you first have to install a development environment. On Windows, in a
sense, before building the plane you will have to build the plant for building planes.
This will be the topic of the following section, which can be omitted by Linux
users.
<h3 class="sectionHead"><span class="titlemark">2.1</span> <a
name="x1-110002.1"></a>Getting a development environment under Windows</h3>
<!--l. 86--><p class="noindent">There is a powerful development environment available for Windows and this
even for free: The Cygnus development tools,<a
name="dx1-11001"></a> resp. <span
class="ptmbi7t---109">Cygwin</span>. Their home is at
<!--l. 91--><p class="indent"> <a
href="http://sources.redhat.com/cygwin/" >http://sources.redhat.com/cygwin/</a>,
<!--l. 94--><p class="noindent">and it is always a good idea to check back what is going on there now and then.
<!--l. 97--><p class="indent"> Nowadays, installing <span
class="ptmbi7t---109">Cygwin</span><a
name="dx1-11002"></a> is nearly automatic. First, make sure the drive you want
<span
class="ptmbi7t---109">Cygwin</span>, <span
class="ptmbi7t---109">PLIB</span>, <span
class="ptmbi7t---109">SimGear </span>and <span
class="ptmbi7t---109">FlightGear </span>to live on, has nearly 1 GB of free disk space<a
name="dx1-11003"></a>.
Create a temporary directory and download the installer from the site named
above to that directory. (While the installer does an automatic installation of the
Cygnus environment, it is a good idea to download a new installer from time to
time.)
<!--l. 104--><p class="indent"> Invoke the installer now. It gives you three options. To avoid having to download
stuff twice in case of a re-installation or installation on a second machine, we highly
recommended to take a two-step procedure. First, select the option <span
class="pcrr7t---109">Download</span>
<span
class="pcrr7t---109">from Internet</span>. Insert the path of your temporary directory, your Internet
connection settings and then choose a mirror form the list. Near servers might
be preferred, but may be sometimes a bit behind with mirroring. We found
<!--l. 112--><p class="indent"> <a
href="ftp://mirrors.rcn.net" >ftp://mirrors.rcn.net</a>
<!--l. 115--><p class="noindent">a very recent and fast choice. In the next windows the default settings are usually a good
start. Now choose <span
class="pcrr7t---109">Next</span>, sit back and wait.
<!--l. 119--><p class="indent"> If you are done, invoke the installer another time, now with the option <span
class="pcrr7t---109">Install</span>
<span
class="pcrr7t---109">from local directory</span>. After confirming the temporary directory you can
select a root directory (acting as the root directory of your pseudo UNIX file
system). Cygnus does not recommend taking the actual root directory of a drive,
thus choose <span
class="pcrr7t---109">c:/Cygwin </span>(while other drives than <span
class="pcrr7t---109">c: </span>work as well). Now, all
<span
class="ptmbi7t---109">Cygwin </span>stuff and all <span
class="ptmbi7t---109">FlightGear </span>stuff lives under this directory. In addition,
select
<!--l. 125--><p class="indent"> <span
class="pcrr7t---109">Default text file type: Unix</span>
<!--l. 127--><p class="indent"> You are free to isntall the compiler for all users or just for you.
<!--l. 129--><p class="indent"> As a final step you should include the binary directory<a
name="dx1-11004"></a> (for instance:
<span
class="pcrr7t---109">c:/Cygwin/bin</span>) into your path by adding <span class="obeylines-h"><span
class="pcrr7t---109">path=c:\Cygwin\bin</span></span> in your
<span
class="pcrr7t---109">autoexec.bat </span>under Windows 95/98/ME. Under WindowsNT/2000/XP, use the
<span
class="pcrr7t---109">Extended </span>tab under the <span
class="pcrr7t---109">System properties </span>page in Windows <span
class="pcrr7t---109">control</span>
<span
class="pcrr7t---109">panel</span>. There you&#8217;ll find a button <span
class="pcrr7t---109">Environment variables</span>, where you can add
the named directory.
<!--l. 133--><p class="indent"> Now you are done. Fortunately, all this is required only once. At this point you have a
nearly UNIX-like (command line) development environment. Because of this, the
following steps are nearly identical under Windows and Linux/Unix.
<h3 class="sectionHead"><span class="titlemark">2.2</span> <a
name="x1-120002.2"></a>Compiling <span
class="ptmbi7t---109">FlightGear </span>under Linux/Windows </h3>
<!--l. 141--><p class="noindent">A preminimary remark: For UNIX, make sure you have all necessary OpenGL libraries
first. Fortunately on all recent Linux distributions (i.e. SuSE-7.1) these are already put on
the right place. Be sure to install the proper package. Besides the basic X11
stuff you want to have - SuSE as an example - the following packages: mesa,
mesa-devel, mesasoft, xf86_glx, xf86glu, xf86glu-devel, mesaglut, mesaglut-devel and
plib.
<!--l. 147--><p class="indent"> Also you are expected to have a bunch of tools installed that are usually required to
compile the Linux kernel. So you may use the Linux kernel source package top
determine the required dependencies. The following packages might prove to be useful
when fiddling with the FlightGear sources: automake, autoconf, libtool, bison, flex and
some more, that are not required to build a Linux kernel.
<!--l. 154--><p class="indent"> Please compare the release of the Plib library with the one that ships with your Linux
distribution. It might be the case that FlightGear requires a newer one that is not yet
provided by your vendor.
<!--l. 158--><p class="indent"> Under Windows, the required libraries should have been installed with the <span
class="ptmbi7t---109">Cygwin</span>
installation above.
<!--l. 160--><p class="indent"> The following steps are identical under Linux/Unix and under Windows with minor
modifications. Under Windows, just open the <span
class="ptmbi7t---109">Cygwin </span>icon from the Start menu or from
the desktop to get a command line.
<!--l. 164--><p class="indent"> To begin with, the <span
class="ptmbi7t---109">FlightGear </span>build process is based on four packages which you
need to built and installed in this order:
<ul class="itemize1">
<li class="itemize">PLIB
</li>
<li class="itemize">SimGear
</li>
<li class="itemize">FlightGear Program
</li>
<li class="itemize">FlightGear base (data - no compilation required)</li></ul>
<ol type="1" class="enumerate1" start="1"
>
<li class="enumerate"><a
name="x1-12002x1"></a>First, choose an install directory<a
name="dx1-12003"></a> for FlightGear. This will not be the one your
binaries will live in but the one for your source code and compilation files.
We suggest
<!--l. 176--><p class="noindent"><span
class="pcrr7t---109">cd:/usr/local/</span>
<!--l. 178--><p class="noindent"><span
class="pcrr7t---109">mkdir source</span>
</li>
<li class="enumerate"><a
name="x1-12005x2"></a>Now, you have to install a support library <span
class="ptmbi7t---109">PLIB</span><a
name="dx1-12006"></a> which is absolutely essential
for the building process. <span
class="ptmbi7t---109">PLIB </span>contains most of the basic graphics rendering,
audio, and joystick routines. Download the latest stable version of <span
class="ptmbi7t---109">PLIB</span><a
name="dx1-12007"></a>
from
<!--l. 184--><p class="noindent"><a
href="http://plib.sourceforge.net/" >http://plib.sourceforge.net/</a>
<!--l. 187--><p class="noindent">to <span
class="pcrr7t---109">/usr/local/source</span>. Change to that directory and unpack <span
class="ptmbi7t---109">PLIB</span>
using
<!--l. 190--><p class="noindent"><span
class="pcrr7t---109">tar xvfz plib-X.X.X.tar.gz</span>.
<!--l. 192--><p class="noindent"><span
class="pcrr7t---109">cd </span>into <span
class="pcrr7t---109">plib-X.X.X </span>and run
<!--l. 194--><p class="noindent"><span
class="pcrr7t---109">./configure</span>
<br class="newline"><span
class="pcrr7t---109">make</span>
<br class="newline"><span
class="pcrr7t---109">make install</span>.
<!--l. 198--><p class="noindent">Under Linux, you have to become root for being able to <span
class="pcrr7t---109">make install</span>,
for instance via the <span
class="pcrr7t---109">su </span>command.
<!--l. 201--><p class="noindent">Confirm you now have <span
class="ptmbi7t---109">PLIB</span>&#8217;s header files<a
name="dx1-12008"></a> (as <span
class="pcrr7t---109">ssg.h </span>etc.) under
<span
class="pcrr7t---109">/usr/include/plib </span>(and nowhere else).
</li>
<li class="enumerate"><a
name="x1-12010x3"></a>Next, you have to install another library <span
class="ptmbi7t---109">SimGear</span><a
name="dx1-12011"></a> containing the basic
simulation routines. Get the most recent file <span
class="pcrr7t---109">SimGear-X.X.X.tar.gz</span><a
name="dx1-12012"></a>
from
<!--l. 207--><p class="noindent"><a
href="ftp://ftp.simgear.org/pub/simgear/Source/" >ftp://ftp.simgear.org/pub/simgear/Source/</a>
<!--l. 210--><p class="noindent">Download it to <span
class="pcrr7t---109">/usr/local/source</span>. Change to that directory and
unpack <span
class="ptmbi7t---109">SimGear </span>using
<!--l. 214--><p class="noindent"><span
class="pcrr7t---109">tar xvfz SimGear-X.X.X.tar.gz</span>.
<!--l. 216--><p class="noindent"><span
class="pcrr7t---109">cd </span>into <span
class="pcrr7t---109">SimGear-X.X.X </span>and run
<!--l. 219--><p class="noindent"><span
class="pcrr7t---109">./configure</span>
<br class="newline"><span
class="pcrr7t---109">make</span>
<br class="newline"><span
class="pcrr7t---109">make install</span>
<!--l. 223--><p class="noindent">Again, under Linux, you have to become root for being able to <span
class="pcrr7t---109">make</span>
<span
class="pcrr7t---109">install</span>, for instance via the <span
class="pcrr7t---109">su </span>command.
</li>
<li class="enumerate"><a
name="x1-12014x4"></a>Now, you&#8217;re prepared to
build <span
class="ptmbi7t---109">FlightGear </span>itself, finally. Get <span
class="pcrr7t---109">FlightGear-X.X.X.tar.gz </span>from
<!--l. 231--><p class="noindent"><a
href="ftp://www.flightgear.org/pub/flightgear/Source/" >ftp://www.flightgear.org/pub/flightgear/Source/</a>
<!--l. 234--><p class="noindent">and download it to <span
class="pcrr7t---109">/usr/local/source</span>. Unpack <span
class="ptmbi7t---109">FlightGear </span>using
<!--l. 238--><p class="noindent"><span
class="pcrr7t---109">tar xvfz FlightGear-X.X.X.tar.gz</span>.
<!--l. 241--><p class="noindent"><span
class="pcrr7t---109">cd </span>into <span
class="pcrr7t---109">FlightGear-X.X.X </span>and run
<!--l. 243--><p class="noindent"><span
class="pcrr7t---109">./configure</span>
<!--l. 246--><p class="noindent">configure<a
name="dx1-12015"></a> knows about numerous options, <a
name="dx1-12016"></a>with the more relevant ones to be
specified via switches as
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--with-network-olk</span>: Include Oliver Delise&#8217;s multi-pilot
networking support<a
name="dx1-12017"></a>,
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-network-olk</span>: Disable Oliver Delise&#8217;s multi-pilot
networking support<a
name="dx1-12018"></a>,
</li>
<li class="itemize"><span
class="pcrr7t---109">--with-old-weather</span>: Include original/simple weather
subsystem<a
name="dx1-12019"></a>,
</li>
<li class="itemize"><span
class="pcrr7t---109">--with-x</span>: Use the X Window system (Linux only)
<br class="newline">
</li>
<li class="itemize"><span
class="pcrr7t---109">--prefix=/XXX</span>: Install <span
class="ptmbi7t---109">FlightGear </span>in the directory <span
class="pcrr7t---109">XXX</span>.</li></ul>
<!--l. 261--><p class="noindent">A good choice would be <span
class="pcrr7t---109">--prefix=/usr/local/FlightGear</span>. In this case
<span
class="ptmbi7t---109">FlightGear</span>&#8217;s binaries<a
name="dx1-12020"></a> will live under <span
class="pcrr7t---109">/usr/local/FlightGear/bin</span>. (If you
don&#8217;t specify a <span
class="pcrr7t---109">--prefix </span>the binaries will go into <span
class="pcrr7t---109">/usr/local/bin </span>while
the base package files are expected under <span
class="pcrr7t---109">/usr/local/lib/FlightGear</span>.)
<!--l. 265--><p class="noindent">Assuming <span
class="pcrr7t---109">configure </span>finished successfully, run
<!--l. 268--><p class="noindent"><span
class="pcrr7t---109">make</span>
<br class="newline"><span
class="pcrr7t---109">make install</span>.
<!--l. 271--><p class="noindent">Again, under Linux, you have to become root for being able to <span
class="pcrr7t---109">make install</span>,
for instance via the <span
class="pcrr7t---109">su </span>command.
<!--l. 275--><p class="noindent">Note: You can save a significant amount of space by stripping all the debugging
symbols off the executable. To do this, make a
<!--l. 280--><p class="noindent"><span
class="pcrr7t---109">cd /usr/local/FlightGear/bin</span>
<!--l. 282--><p class="noindent">to the directory in the <span
class="pcrr7t---109">install tree </span>where your binaries live and run
<!--l. 286--><p class="noindent"><span
class="pcrr7t---109">strip *</span>.</li></ol>
<!--l. 290--><p class="noindent">This completes building the executable and should result in a file <span
class="pcrr7t---109">fgfs </span>(Unix) or
<span
class="pcrr7t---109">fgfs.exe </span>(Windows) under <span
class="pcrr7t---109">/usr/local/FlightGear/bin</span>
<!--l. 293--><p class="indent"> <span
class="ptmb7t---109">Note: </span>If for whatever reason you want to re-build the simulator, use the command <span
class="pcrr7t---109">make</span>
<span
class="pcrr7t---109">distclean </span>either in the <span
class="pcrr7t---109">SimGear-X.X.X </span>or in the <span
class="pcrr7t---109">FlightGear-X.X.X </span>directory
to remove all the build. If you want to re-run <span
class="pcrr7t---109">configure </span>(for instance because of
having installed another version of <span
class="ptmbi7t---109">PLIB </span>etc.), remove the files <span
class="pcrr7t---109">config.cache </span>from
these same directories before.
<h3 class="sectionHead"><span class="titlemark">2.3</span> <a
name="x1-130002.3"></a>Compiling <span
class="ptmbi7t---109">FlightGear </span>under Mac OS 10.1 </h3>
<!--l. 303--><p class="noindent">For compiling under Mac OS 10.1 you will need
<ul class="itemize1">
<li class="itemize">Mac OS 10.1 with 10.1 developer tools installed.
</li>
<li class="itemize">500MB disk (conservative estimate, might be a little less).
</li>
<li class="itemize">Fearlessness of command line compiling.</li></ul>
<!--l. 311--><p class="noindent">This will need a bit more bravery than buidling under Windows or Linux. First, there are
less poeple who tested it under sometimes strange configurations. Second, the
process as described here itself nees a touch more experience by using CVS
repositories.
<!--l. 314--><p class="indent"> First, download the development files. They are intended to simplify the build
process as much as possible:
<!--l. 318--><p class="indent"> <a
href="http://expert.cc.purdue.edu/~walisser/fg/fgdev.tar.gz" >http://expert.cc.purdue.edu/&nbsp;walisser/fg/fgdev.tar.gz</a>
<!--l. 321--><p class="indent"> Once you have this extracted, make sure you are using tcsh, since the setup script
requires it.
<ol type="1" class="enumerate1" start="1"
>
<li class="enumerate"><a
name="x1-13002x1"></a>Setup the build environment:
<br class="newline"><span
class="pcrr7t---109">cd fgdev</span>
<br class="newline"><span
class="pcrr7t---109">source bin/prepare.csh</span>
</li>
<li class="enumerate"><a
name="x1-13004x2"></a>Install automake/aclocal build tools
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR/src/automake-1.4-p4</span>
<br class="newline"><span
class="pcrr7t---109">./configure --prefix=$BUILDDIR</span>
<br class="newline"><span
class="pcrr7t---109">make install</span>
</li>
<li class="enumerate"><a
name="x1-13006x3"></a>Build PLIB
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR/src/plib-1.4.2</span>
<br class="newline"><span
class="pcrr7t---109">aclocal</span>
<br class="newline"><span
class="pcrr7t---109">automake</span>
<br class="newline"><span
class="pcrr7t---109">./configure --prefix=$BUILDDIR --with-GL=$BUILDDIR</span>
<br class="newline"><span
class="pcrr7t---109">make install</span>
</li>
<li class="enumerate"><a
name="x1-13008x4"></a>Get the SimGear sources
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR/src</span>
<br class="newline"><span
class="pcrr7t---109">setenv CVSROOT :pserver:cvs@cvs.hfrl.umn.edu:</span>
<br class="newline"><span
class="pcrr7t---109">/var/cvs/SimGear-0.0 </span>(one line)
<br class="newline"><span
class="pcrr7t---109">cvs login</span>
<br class="newline"># Enter &#8221;guest&#8221; for password
<br class="newline"><span
class="pcrr7t---109">cvs -z3 checkout SimGear</span>
<br class="newline">
</li>
<li class="enumerate"><a
name="x1-13010x5"></a>Build SimGear
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR/src/SimGear</span>
<br class="newline"><span
class="pcrr7t---109">cp ../$PLIB/install-sh ./</span>
<br class="newline"><span
class="pcrr7t---109">cp ../$PLIB/mkinstalldirs ./</span>
<br class="newline"><span
class="pcrr7t---109">aclocal</span>
<br class="newline"><span
class="pcrr7t---109">automake</span>
<br class="newline"><span
class="pcrr7t---109">autoconf</span>
<br class="newline"><span
class="pcrr7t---109">./configure --prefix=$BUILDDIR --host=powerpc</span>
<br class="newline"><span
class="pcrr7t---109">make install</span>
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR/lib</span>
<br class="newline"><span
class="pcrr7t---109">ranlib libmk4.a</span>
<br class="newline">
</li>
<li class="enumerate"><a
name="x1-13012x6"></a>Get the FlightGear sources <span
class="pcrr7t---109">cd $BUILDDIR/src</span>
<br class="newline"><span
class="pcrr7t---109">setenv CVSROOT :pserver:cvs@cvs.hfrl.umn.edu:</span>
<br class="newline"><span
class="pcrr7t---109">/var/cvs/FlightGear-0.7 </span>(one line!)
<br class="newline"><span
class="pcrr7t---109">cvs login</span>
<br class="newline">#enter &#8221;guest&#8221; for password
<br class="newline"><span
class="pcrr7t---109">cvs -z3 checkout FlightGear</span>
</li>
<li class="enumerate"><a
name="x1-13014x7"></a>Build FlightGear
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR/src/FlightGear</span>
<br class="newline"><span
class="pcrr7t---109">cp ../$PLIB/install-sh ./</span>
<br class="newline"><span
class="pcrr7t---109">cp ../$PLIB/mkinstalldirs ./</span>
<br class="newline"><span
class="pcrr7t---109">aclocal</span>
<br class="newline"><span
class="pcrr7t---109">automake</span>
<br class="newline"><span
class="pcrr7t---109">autoconf</span>
<br class="newline"><span
class="pcrr7t---109">./configure --prefix=$BUILDDIR --includedir=</span>
<br class="newline"><span
class="pcrr7t---109">$BUILDDIR --with-threads --without-x </span>(one line)
<br class="newline"><span
class="pcrr7t---109">patch -p0 &lt; ../jsb.diff</span>
</li>
<li class="enumerate"><a
name="x1-13016x8"></a>Get the base data files (if you don&#8217;t have them already)
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR</span>
<br class="newline"><span
class="pcrr7t---109">setenv CVSROOT :pserver:cvsguest@rockfish.net:</span>
<br class="newline"><span
class="pcrr7t---109">/home/cvsroot </span>(one line)
<br class="newline"><span
class="pcrr7t---109">cvs login</span>
<br class="newline">#password is &#8221;cvsguest&#8221;
<br class="newline"><span
class="pcrr7t---109">cvs -z3 checkout fgfsbase</span>
</li>
<li class="enumerate"><a
name="x1-13018x9"></a>Move data files (if you have them already)
<br class="newline">just make a symlink or copy data files to &#8221;fgfsbase&#8221; in $BUILDDIR
</li>
<li class="enumerate"><a
name="x1-13020x10"></a>Run FlightGear
<br class="newline"><span
class="pcrr7t---109">cd $BUILDDIR</span>
<br class="newline"><span
class="pcrr7t---109">src/FlightGear/src/Main/fgfs</span></li></ol>
<h3 class="sectionHead"><span class="titlemark">2.4</span> <a
name="x1-140002.4"></a>Compiling on other systems</h3>
<!--l. 400--><p class="noindent">Compiling on other Unix<a
name="dx1-14001"></a> systems - at least on IRIX<a
name="dx1-14002"></a> and on Solaris<a
name="dx1-14003"></a>, is pretty similar to
the procedure on Linux - given the presence of a working GNU C compiler. Especially
IRIX and also recent releases of Solaris come with the basic OpenGL libraries.<a
name="dx1-14004"></a>
Unfortunately the &#8221;glut&#8221; libraries are mostly missing and have to be installed separately
(see the introductory remark to this chapter). As compilation of the &#8221;glut&#8221; sources is not
a trivial task to everyone, you might want to use a prebuilt binary. Everything you need is
a static library &#8221;libglut.a&#8221; and an include file &#8221;glut.h&#8221;. An easy way to make them usable
is to place them into <span
class="pcrr7t---109">/usr/lib/ </span>and <span
class="pcrr7t---109">/usr/include/GL/</span>. In case you insist
on building the library yourself, you might want to have a look at FreeGLUT<a
name="dx1-14005"></a>
<!--l. 411--><p class="indent"> <a
href="http://freeglut.sourceforge.net/" >http://freeglut.sourceforge.net/</a>
<!--l. 414--><p class="noindent">which should compile with minor tweaks. Necessary patches might be found in
<!--l. 418--><p class="indent"> <a
href="ftp://ftp.uni-duisburg.de/X11/OpenGL/freeglut_portable.patch" >ftp://ftp.uni-duisburg.de/X11/OpenGL/freeglut_portable.patch</a>
<!--l. 421--><p class="noindent">Please note that you do <span
class="ptmb7t---109">not </span>want to create 64 bit binaries in IRIX with GCC (even if your
CPU is a R10/12/14k) because GCC produces a broken &#8221;fgfs&#8221; binary (in case the
compiler does&#8217;nt stop with &#8221;internal compiler error&#8221;). Things might look better if Eric
Hofman<a
name="dx1-14006"></a> manages to tweak the FlightGear sources for proper compiling with MIPSPro
compiler (it&#8217;s already mostly done).
<!--l. 428--><p class="indent"> There should be a workplace for Microsoft Visual C++<a
name="dx1-14007"></a> (MSVC6) included in the
official <span
class="ptmbi7t---109">FlightGear </span>distribution. Macintosh<a
name="dx1-14008"></a> users find the required CodeWarrior<a
name="dx1-14009"></a> files as a
<span
class="pcrr7t---109">.bin </span>archive at
<!--l. 433--><p class="indent"> <a
href="http://icdweb.cc.purdue.edu/~walisser/fg/" >http://icdweb.cc.purdue.edu/<img
src="getstart2x.gif" alt="~" class="tilde" > walisser/fg/</a>.
<!--l. 435--><p class="indent"> Numerous (although outdated, at times) hints on compiling on different systems are
included in the source code under <span
class="pcrr7t---109">docs-mini</span>.
<h3 class="sectionHead"><span class="titlemark">2.5</span> <a
name="x1-150002.5"></a>Installing the base package</h3>
<!--l. 441--><p class="noindent">If you succeede in performing the steps named above, you will have a directory holding
the executables for <span
class="ptmbi7t---109">FlightGear</span>. This is not yet sufficient for performing <span
class="ptmbi7t---109">FlightGear</span>,
though. Besides those, you will need a collection of support data files (scenery,
aircraft, sound) collected in the so-called base package. In case you compiled
the latest official release, the accompanying base package is available from
<!--l. 448--><p class="indent"> <a
href="ftp://www.flightgear.org/pub/flightgear/Shared/fgfs-base-X.X.X.tar.gz" >ftp://www.flightgear.org/pub/flightgear/Shared/fgfs-base-X.X.X.tar.gz</a>.
<!--l. 450--><p class="indent"> This package<a
name="dx1-15001"></a> is usually quite large (around 25 MB), but must be installed for
<span
class="ptmbi7t---109">FlightGear </span>to run. There is no compilation required for it. Just download it to
<span
class="pcrr7t---109">/usr/local </span>and install it with
<!--l. 454--><p class="indent"> <span
class="pcrr7t---109">tar xvfz fgfs-base-X.X.X.tar.gz</span>.
<!--l. 456--><p class="noindent">Now you should find all the <span
class="ptmbi7t---109">FlightGear </span>files under <span
class="pcrr7t---109">/usr/local/Flightgear </span>in the
following directory structure:<a
name="dx1-15002"></a><a
name="dx1-15003"></a>:
<!--l. 462--><p class="indent"> <span
class="pcrr7t---109">/usr/local/Flightgear</span>
<!--l. 464--><p class="indent"> <span
class="pcrr7t---109">/usr/local/Flightgear/Aircraft</span>
<!--l. 466--><p class="indent"> <span
class="pcrr7t---109">/usr/local/Flightgear/Aircraft-uiuc</span>
<!--l. 468--><p class="indent"> . . .
<!--l. 470--><p class="indent"> <span
class="pcrr7t---109">/usr/local/Flightgear/bin</span>
<!--l. 472--><p class="indent"> . . .
<!--l. 474--><p class="indent"> <span
class="pcrr7t---109">/usr/local/Flightgear/Weather</span>.
<h3 class="sectionHead"><span class="titlemark">2.6</span> <a
name="x1-160002.6"></a>For test pilots only: Building the CVS snapshots</h3>
<!--l. 481--><p class="noindent">It you are into adventures or feel you&#8217;re an advanced user, you can try one of the recent
bleeding edge snapshots<a
name="dx1-16001"></a><a
name="dx1-16002"></a> at
<!--l. 484--><p class="indent"> <a
href="http://www.flightgear.org/Downloads/" >http://www.flightgear.org/Downloads/</a>.
<!--l. 487--><p class="noindent">In this case you have to get the most recent Snapshot from <span
class="ptmbi7t---109">SimGear </span>at
<!--l. 491--><p class="indent"> <a
href="http://www.simgear.org/downloads.html" >http://www.simgear.org/downloads.html</a>
<!--l. 494--><p class="noindent">as well. But be prepared: These are for development and may (and often do) contain
bugs.
<!--l. 498--><p class="indent"> If you are using these CVS snapshots, the base package named above will usually not
be in sync with the recent code and you have to download the most recent developer&#8217;s
version from
<!--l. 503--><p class="indent"> <a
href="http://rockfish.net/fg/" >http://rockfish.net/fg/</a>.
<!--l. 506--><p class="noindent">We suggest downloading this package <span
class="pcrr7t---109">fgfs</span>_<span
class="pcrr7t---109">base-snap.X.X.X.tar.gz </span>to a
temporary directory. Now, decompress it using
<!--l. 511--><p class="indent"> <span
class="pcrr7t---109">tar xvfz fgfs</span>_<span
class="pcrr7t---109">base-snap.X.X.X.tar.gz</span>.
<!--l. 514--><p class="indent"> Finally, double-check you got the directory structure named above.
<h2 class="chapterHead"><span class="titlemark">Chapter&nbsp;3</span><br><a
name="x1-170003"></a>Preflight: Installing <span
class="ptmbi7t---109">FlightGear </span></h2>
<!--l. 33--><p class="noindent">You can skip this Section if you built <span
class="ptmbi7t---109">FlightGear </span>along the lines described in the
previous Chapter. If you did not and you&#8217;re jumping in here, your first step will consist in
installing the binaries. At present, there are pre-compiled binaries<a
name="dx1-17001"></a> available
for
<ul class="itemize1">
<li class="itemize">Windows (any flavor),
</li>
<li class="itemize">Macintosh OSX,
</li>
<li class="itemize">Debian Linux,
</li>
<li class="itemize">SGI Irix.</li></ul>
<h3 class="sectionHead"><span class="titlemark">3.1</span> <a
name="x1-180003.1"></a>Installing the binary distribution on a Windows system</h3>
<a
name="dx1-18001"></a>
<!--l. 49--><p class="noindent">The following supposes you are on a Windows (95/98/Me/NT/2000/XP) <a
name="dx1-18002"></a>system.
Installing the binaries is quite simple. Go to
<!--l. 53--><p class="indent"> <a
href="ftp://www.flightgear.org/pub/flightgear/Win32/" >ftp://www.flightgear.org/pub/flightgear/Win32/</a>
<!--l. 56--><p class="noindent">and download the three files <span
class="pcrr7t---109">fgfs-base-X.X.X.zip</span>, <span
class="pcrr7t---109">fgfs-manual-X.X.X.zip</span>,
and <span
class="pcrr7t---109">fgfs-win32-bin-X.X.X.zip </span>from
<!--l. 60--><p class="indent"> <a
href="ftp://www.flightgear.org/pub/flightgear/Win32/" >ftp://www.flightgear.org/pub/flightgear/Win32/</a>
<!--l. 63--><p class="noindent">to a drive of your choice. Windows XP includes a program for unpacking *.zip files. If
you are working under an older version of Windows, we suggest getting Winzip from
<!--l. 67--><p class="indent"> <a
href="http://www.winzip.com/" >http://www.winzip.com/</a>.
<!--l. 70--><p class="noindent">For a free alternative, you may consider <span
class="pcrr7t---109">unzip </span>from Info-ZIP,
<!--l. 74--><p class="indent"> http://www.info-zip.org/pub/infozip/
<!--l. 77--><p class="noindent">Extract the files named above. If you choose drive <span
class="pcrr7t---109">c: </span>you should find a file
<span
class="pcrr7t---109">runfgfs.bat </span>under <span
class="pcrr7t---109">c:/Flightgear </span>now. Double-clicking it should invoke the
simulator.
<!--l. 82--><p class="indent"> In case of doubt about the correct directory structure, see the summary at the end of
chapter <a
href="#x1-100002">2<!--tex4ht:ref: building--></a>.
<h3 class="sectionHead"><span class="titlemark">3.2</span> <a
name="x1-190003.2"></a>Installing the binary distribution on a Macintosh system</h3>
<a
name="dx1-19001"></a>
<!--l. 89--><p class="noindent">If your Macintosh<a
name="dx1-19002"></a> is running the conventional Mac OS 9<a
name="dx1-19003"></a> or earlier, there are versions up
to <span
class="ptmbi7t---109">FlightGear </span>0.7.6 available being provided courtesy Darrell Walisser)<a
name="dx1-19004"></a>. Download the
file <span class="obeylines-h"><span
class="pcrr7t---109">FlightGear_Installer_0.X.X.sit</span></span> from the corresponding subdirectory
under
<!--l. 94--><p class="indent"> <a
href="http://icdweb.cc.purdue.edu/~walisser/fg/" >http://icdweb.cc.purdue.edu/&nbsp;walisser/fg/</a>.
<!--l. 97--><p class="noindent">This file contains the program as well as the required base package files (scenery etc.).
For unpacking, use <span
class="pcrr7t---109">Stuffit Expander 5.0</span><a
name="dx1-19005"></a> or later.
<!--l. 101--><p class="indent"> The latest build available for Mac OS 9.x is 0.7.6, located in the same place.
The base package is part of the download for Mac OS 9.x, but not for Mac
OSX.
<!--l. 103--><p class="indent"> Alternatively, if you are running Mac OS X<a
name="dx1-19006"></a>, download <span
class="pcrr7t---109">fgfs-0.X.X.gz </span>from the
same site named above. The Mac OS X builds are in a gzip file in the same
directory. There is a readme file in the directory to help people identify what to
download.
<!--l. 106--><p class="indent"> Mac OS X requires that you first download the base package. Then extract it
with
<!--l. 108--><p class="noindent"><span
class="pcrr7t---109">tar -zxvf fgfs-base-X.X.X.tar.gz</span>
<br class="newline"><span
class="pcrr7t---109">gunzip fgfs-X.X.X.-date.gz</span>
<!--l. 112--><p class="noindent">Note that there is no <span
class="pcrr7t---109">runfgfs </span>script for Mac OS X yet.
<h3 class="sectionHead"><span class="titlemark">3.3</span> <a
name="x1-200003.3"></a>Installing the binary distribution on a Debian Linux system</h3>
<a
name="dx1-20001"></a>
<!--l. 119--><p class="noindent">Download the file <span class="obeylines-h"><span
class="pcrr7t---109">flightgear_0.7.6-6_i386.deb</span></span> (being provided courtesy Ove
Kaaven)<a
name="dx1-20002"></a> from any of the Debian<a
name="dx1-20003"></a> mirror sites listed at
<!--l. 123--><p class="indent"> <a
href="http://packages.debian.org/unstable/games/flightgear.html" >http://packages.debian.org/unstable/games/flightgear.html</a>.
<!--l. 126--><p class="noindent">Like any Debian package, this can be installed via
<!--l. 130--><p class="indent"> <span class="obeylines-h"><span
class="pcrr7t---109">dpkg</span><span
class="pcrr7t---109">&nbsp;--install</span><span
class="pcrr7t---109">&nbsp;flightgear_0.7.6-6_i386.deb</span></span>.
<!--l. 133--><p class="noindent">After installation, you will find the directory <span
class="pcrr7t---109">/usr/local/Flightgear </span>containing
the script <span
class="pcrr7t---109">runfgfs </span>to start the program.
<h3 class="sectionHead"><span class="titlemark">3.4</span> <a
name="x1-210003.4"></a>Installing the binary distribution on a SGI IRIX system</h3>
<a
name="dx1-21001"></a>
<!--l. 142--><p class="noindent">If there are binaries available for SGI IRIX systems, download all the required files
(being provided courtesy Erik Hofman)<a
name="dx1-21002"></a> from
<!--l. 146--><p class="indent"> <a
href="http://www.a1.nl/~ehofman/fgfs/" >http://www.a1.nl/&nbsp;ehofman/fgfs/</a>
<!--l. 149--><p class="noindent">and install them. Now you can start <span
class="ptmbi7t---109">FlightGear </span>via running the script
<br class="newline"><span
class="pcrr7t---109">/usr/local/FlightGear/bin/gofgfs</span>.
<h3 class="sectionHead"><span class="titlemark">3.5</span> <a
name="x1-220003.5"></a>Installing add-on scenery</h3>
<a
name="dx1-22001"></a>
<a
name="dx1-22002"></a>
<!--l. 157--><p class="noindent">There is a complete set of scenery files worldwide available created by Curt Olson<a
name="dx1-22003"></a> which
can be downloaded via a clickable map at
<!--l. 161--><p class="indent"> <a
href="http://www.flightgear.org/Downloads/world-scenery.html" >http://www.flightgear.org/Downloads/world-scenery.html</a>
<!--l. 164--><p class="noindent">Moreover, Curt provides the complete set of US Scenery on CD-ROM<a
name="dx1-22004"></a> for those who
really would like to fly over all of the USA. For more detail, check the remarks on the
downloads page above.
<!--l. 169--><p class="indent"> For installing these files, you have to unpack them under <span
class="pcrr7t---109">/Flightgear/Scenery</span>.
Do not de-compress the numbered scenery files like 958402.gz! This will be done by
<span
class="ptmbi7t---109">FlightGear </span>on the fly.
<!--l. 173--><p class="indent"> As an example, consider installation of the scenery package w120n30 containing the
Grand Canyon Scenery.
<!--l. 176--><p class="indent"> After having installed the base package<a
name="dx1-22005"></a>, you should have ended up with the following
directory structure:
<!--l. 179--><p class="noindent"><span
class="pcrr7t---109">/usr/local/FlightGear/Scenery</span>
<!--l. 182--><p class="noindent"><span
class="pcrr7t---109">/usr/local/FlightGear/w130n30</span>
<!--l. 185--><p class="noindent"><span
class="pcrr7t---109">/usr/local/FlightGear/w130n30/w122n37</span>
<br class="newline"><span
class="pcrr7t---109">/usr/local/FlightGear/Scenery/w130n30/w123n37</span>
<!--l. 189--><p class="noindent">with the directories w122n37 and w123n37m, resp. containing numerous *.gz files.
Installation of the Grand Canyon scenery adds to this the directories
<!--l. 193--><p class="noindent"><span
class="pcrr7t---109">/usr/local/FlightGear/w120n30/w112n30</span>
<br class="newline"><span
class="pcrr7t---109">/usr/local/FlightGear/w120n30/w112n31</span>
<br class="newline"><span
class="pcrr7t---109">...</span>
<br class="newline"><span
class="pcrr7t---109">/usr/local/FlightGear/w120n30/w120n39</span>.
<h3 class="sectionHead"><span class="titlemark">3.6</span> <a
name="x1-230003.6"></a>Installing documentation</h3>
<a
name="dx1-23001"></a>
<!--l. 204--><p class="noindent">Most of the packages named above include the complete <span
class="ptmbi7t---109">FlightGear </span>documentation
including a .pdf version of this <span
class="ptmri7t---109">Installation and Getting Started </span>Guide intended for pretty
printing using Adobe&#8217;s Acrobat Reader being available from
<!--l. 209--><p class="indent"> <a
href="http://www.adobe.com/acrobat" >http://www.adobe.com/acrobat</a>
<!--l. 212--><p class="noindent">Moreover, if properly installed, the .html version can be accessed via <span
class="ptmbi7t---109">FlightGear</span>&#8217;s <span
class="pcrr7t---109">help</span>
menu entry.
<!--l. 216--><p class="indent"> Besides, the source code contains a directory <span
class="pcrr7t---109">docs-mini </span>containing numerous
ideas on and solutions to special problems. This is also a good place for further
reading.
<h1 class="partHead"><span class="titlemark">Part&nbsp;II<br></span><a
name="x1-24000II"></a>Flying with <span
class="ptmbi7t---109">FlightGear</span></h1>
<h2 class="chapterHead"><span class="titlemark">Chapter&nbsp;4</span><br><a
name="x1-250004"></a>Takeoff: How to start the program</h2>
<h3 class="sectionHead"><span class="titlemark">4.1</span> <a
name="x1-260004.1"></a>Launching the simulator under Unix/Linux</h3>
<a
name="dx1-26001"></a>
<a
name="dx1-26002"></a>
<!--l. 33--><p class="noindent">Under Linux (or any other flavor of Unix), <span
class="ptmbi7t---109">FlightGear </span>will be invoked by
<!--l. 36--><p class="indent"> <span
class="pcrr7t---109">runfgfs --option1 --option2...</span>,
<!--l. 39--><p class="noindent">where the options will be described in Section <a
href="#x1-290004.4">4.4<!--tex4ht:ref: options--></a> below.
<!--l. 42--><p class="indent"> If something strange happens while using this shell script, if you want to do some
debugging (i.e. using &#8221;strace&#8221;) or if you just feel nice to be &#8221;keen&#8221;, then you can start
<span
class="ptmbi7t---109">FlightGear </span>directly by executing the &#8221;fgfs&#8221; binary. In this case you should at least add
one variable to your environment,<a
name="dx1-26003"></a> which is needed to locate the (mostly) shared library
built from the sources of the <span
class="ptmbi7t---109">SimGear </span>package. Please add the respective directory to
your <span class="obeylines-h"><span
class="pcrr7t---109">LD_LIBRARY_PATH</span></span>. You can do so with the following on Bourne shell
(compatibles):
<table width="100%"
class="verbatim"><tr class="verbatim"><td
class="verbatim"><pre class="verbatim">
&nbsp;LD_LIBRARY_PATH=/usr/local/FlightGear/lib:$LD_LIBRARY_PATH
&nbsp;export&nbsp;LD_LIBRARY_PATH/
</pre>
</td></tr></table>
<!--l. 55--><p class="noindent">or on C shell (compatibles):
<table width="100%"
class="verbatim"><tr class="verbatim"><td
class="verbatim"><pre class="verbatim">
&nbsp;setenv&nbsp;LD_LIBRARY_PATH
&nbsp;/usr/local/FlightGear/lib:$LD_LIBRARY_PATH
</pre>
</td></tr></table>
<!--l. 63--><p class="noindent">Besides this (used by the dynamic linker) &#8221;fgfs&#8221; knows about the following environment
variable
<!--l. 67--><p class="indent"> <span class="obeylines-h"><span
class="pcrr7t---109">FG_ROOT</span></span>: root directory for the FlightGear base package; this corresponds to the
<span
class="pcrr7t---109">--fg-root=</span><span
class="ptmri7t---109">path </span>option as described in Sec. <a
href="#x1-300004.4.1">4.4.1<!--tex4ht:ref: generaloptions--></a>
<h3 class="sectionHead"><span class="titlemark">4.2</span> <a
name="x1-270004.2"></a>Launching the simulator under Windows</h3>
<a
name="dx1-27001"></a>
<a
name="dx1-27002"></a>
<!--l. 72--><p class="noindent">Before starting the simulator, you may want to adaprt the file <span
class="pcrr7t---109">webrun.bat </span>situated in
the main <span
class="ptmbi7t---109">FlightGear </span>directory. Open the file with an editor
<!--l. 74--><p class="indent"> In Windows explorer, change to the directory <span
class="pcrr7t---109">/FlightGear </span>and double-click
<span
class="pcrr7t---109">runfgfs.bat</span>.
<!--l. 80--><p class="indent"> <div align="center"
class="centerline"><img
src="getstart3x.gif" alt="" class="fbox" > </div>
<!--l. 83--><p class="noindent">Fig. 3: <span
class="ptmri7t---109">Ready for takeoff. Waiting at the default startup position at San Francisco Itl.,</span>
<span
class="ptmri7t---109">KSFO.</span>
<!--l. 88--><p class="indent"> Alternatively, if for one or the other reason the batch file does not work or is missing,
you can open an MS-DOS shell, change to the directory where your binary resides
(typically something like <span
class="pcrr7t---109">c:/FlightGear/bin </span>where you might have to substitute
<span
class="pcrr7t---109">c: </span>in favor of your <span
class="ptmbi7t---109">FlightGear </span>directory), set the environment variable<a
name="dx1-27003"></a> via (note the
backslashes!)
<!--l. 95--><p class="indent"> <span
class="pcrr7t---109">SET FG</span>_<span
class="pcrr7t---109">ROOT=c:</span><span
class="cmsy-10--109">\</span><span
class="pcrr7t---109">FlightGear</span><span
class="cmsy-10--109">\</span><span
class="pcrr7t---109">bin</span>
<!--l. 98--><p class="noindent">and invoke <span
class="ptmbi7t---109">FlightGear </span>(within the same MS-DOS shell, as environment settings are only
valid locally within the same shell) via
<!--l. 103--><p class="indent"> <span
class="pcrr7t---109">fgfs --option1 --option2...</span>.
<!--l. 106--><p class="indent"> Of course, you can create your own <span
class="pcrr7t---109">runfgfs.bat </span>with Windows <span
class="pcrr7t---109">Editor </span>using
the two lines above.
<!--l. 109--><p class="indent"> For getting maximum performance it is recommended to minimize (iconize) the text
output window while running <span
class="ptmbi7t---109">FlightGear</span>.
<h3 class="sectionHead"><span class="titlemark">4.3</span> <a
name="x1-280004.3"></a>Launching the simulator under Mac OS X</h3>
<a
name="dx1-28001"></a>
<a
name="dx1-28002"></a>
<!--l. 115--><p class="noindent">Say you downloaded the base package and binary to yout home directory. Then you can
open <span
class="pcrr7t---109">Terminal.app </span>and execute the following sequence:
<!--l. 118--><p class="noindent"><span
class="pcrr7t---109">setenv FG</span>_<span
class="pcrr7t---109">ROOT </span><span
class="pcrr7t---109">&nbsp;/fgfs-base-X.X.X ./fgfs-X.X.X.-date</span>
<br class="newline"><span
class="pcrr7t---109">--option1 -- option 2 </span>(one line)
<!--l. 123--><p class="noindent">or
<!--l. 127--><p class="noindent"><span
class="pcrr7t---109">./fgfs-X.X.X-version-date --fg-root=</span><img
src="getstart4x.gif" alt="~/ " class="tilde" ><span
class="pcrr7t---109">fgfs-base-X.X.X</span>
<br class="newline"><span
class="pcrr7t---109">--option1 --option2</span>. (one line)
<h3 class="sectionHead"><span class="titlemark">4.4</span> <a
name="x1-290004.4"></a>Command line parameters</h3>
<a
name="dx1-29001"></a>
<!--l. 135--><p class="noindent">Following is a list and short description of the numerous command line options<a
name="dx1-29002"></a> available
for <span
class="ptmbi7t---109">FlightGear</span>. If you are running <span
class="ptmbi7t---109">FlightGear </span>under Windows<a
name="dx1-29003"></a> you can include these into
<span
class="pcrr7t---109">runfgfs.bat</span>.
<!--l. 139--><p class="indent"> However, in case of options you want to re-use continually (like joystick settings)
it is recommended to include them into a file called <span
class="pcrr7t---109">.fgfsrc</span><a
name="dx1-29004"></a> under Unix
systems and <span
class="pcrr7t---109">system.fgfsrc</span>,<a
name="dx1-29005"></a> resp. under Windows. This file has to be in
the top FlightGear directory (for instance /usr/local/Flightgear). As it depends
on your preferences<a
name="dx1-29006"></a>, it is not delivered with <span
class="ptmbi7t---109">FlightGear</span>, but can be created
with any text editor (notepad, emacs, vi, if you like). Examples for such a file
(including a detailed description on the configuration of joysticks) can be found at
<!--l. 149--><p class="indent"> <a
href="http://rockfish.net/shell/aboutjoy.txt" >http://rockfish.net/shell/aboutjoy.txt</a>.
<h4 class="subsectionHead"><span class="titlemark">4.4.1</span> <a
name="x1-300004.4.1"></a>General Options</h4><a
name="dx1-30001"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--help</span>, <span
class="pcrr7t---109">-h</span>: Gives a small help text, kind of a short version of this Section.
</li>
<li class="itemize"><span
class="pcrr7t---109">--fg-root=</span><span
class="ptmri7t---109">path</span>: Tells <span
class="ptmbi7t---109">FlightGear </span>where to look for its data files if you
didn&#8217;t compile it with the default settings<a
name="dx1-30002"></a>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--fg-scenery=</span><span
class="ptmri7t---109">path</span>: Allows specification of a path to the scenery
directorypath <a
name="dx1-30003"></a>, in case scenery is not at the default position under
<br class="newline"><span
class="pcrr7t---109">/Flightgear/Scenery</span>; this might be especially useful in case you
have scenery on a CD-ROM.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-game-mode</span>: Disables full screen display<a
name="dx1-30004"></a>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-game-mode</span>: Enables full screen display.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-splash-screen</span>: Turns off the rotating 3DFX logo when
the accelerator board gets initialized (3DFX only).
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-splash-screen</span>: If you like advertising, set this!
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-intro-music</span>: No audio sample is being played when
<span
class="ptmbi7t---109">FlightGear </span>starts up. Suggested in case of trouble with playing the intro.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-intro-music</span>: If your machine is powerful enough, enjoy
this setting.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-mouse-pointer</span>: Disables mouse interface<a
name="dx1-30005"></a>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-mouse-pointer</span>: Enables mouse interface<a
name="dx1-30006"></a>. Useful in full
screen mode for old Voodoo/VoodooII based cards.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-freeze</span>: This will put you into <span
class="ptmbi7t---109">FlightGear </span>with the engine
running, ready for Take-Off.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-freeze</span>: Starts <span
class="ptmbi7t---109">FlightGear </span>in frozen state<a
name="dx1-30007"></a>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-fuel-freeze</span>: Fuel is consumde normally.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-fuel-freeze</span>: Fuel tank quntity is forced to remain
constant.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-tod-freeze</span>: Time of day advances normally.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-tod-freeze</span>: Do not advance time of day.
</li>
<li class="itemize"><span
class="pcrr7t---109">--control-mode</span>: Specify your control device<a
name="dx1-30008"></a> (joystick<a
name="dx1-30009"></a>, keyboard,
mouse) Defaults to joystick<a
name="dx1-30010"></a> (yoke<a
name="dx1-30011"></a>).
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-auto-coordination</span>: Switches auto coordination<a
name="dx1-30012"></a>
between aileron/rudder off (default).
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-auto-coordination</span>: Switches auto coordination between
aileron/rudder on (recommended without pedals).
</li>
<li class="itemize"><span
class="pcrr7t---109">--browser-app=/path/to/app</span>: specify location of your web
browser. Example: <span
class="pcrr7t---109">--browser-app=</span>
<br class="newline"><span
class="pcrr7t---109">''C:</span><span
class="cmsy-10--109">\</span><span
class="pcrr7t---109">Programme</span><span
class="cmsy-10--109">\</span><span
class="pcrr7t---109">Internet</span><span
class="pcrr7t---109">&nbsp;Explorer</span><span
class="cmsy-10--109">\</span><span
class="pcrr7t---109">iexplore.exe'' </span>(Note
the &#8221; &#8221; because of the broken word Internet Explorer!).
</li>
<li class="itemize"><span
class="pcrr7t---109">--prop:name=value: </span>set property <span
class="pcrr7t---109">name </span>to <span
class="pcrr7t---109">value</span>
<br class="newline">Example: <span
class="pcrr7t---109">--prop:/engines/engine0/running=true </span>for starting
with running engines. Another example:
<br class="newline"><span
class="pcrr7t---109">--aircraft=c172</span>
<br class="newline"><span
class="pcrr7t---109">--prop:/consumables/fules/tank[0]/level-gal=10</span>
<br class="newline"><span
class="pcrr7t---109">--prop:/consumables/fules/tank[1]/level-gal=10</span>
<br class="newline">filles the Cessna for a short flight.
</li>
<li class="itemize"><span
class="pcrr7t---109">--config=path: </span>Load additional properties from the given path.
Example: <span
class="pcrr7t---109">runfgfs --config=./Aircraft/X15-set.xml</span>
</li>
<li class="itemize"><span
class="pcrr7t---109">--units-feed</span>: Use feet for distances.
</li>
<li class="itemize"><span
class="pcrr7t---109">--units-meters</span>: Use meters for distances.</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.2</span> <a
name="x1-310004.4.2"></a>Features</h4><a
name="dx1-31001"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--disable-hud</span>: Switches off the HUD<a
name="dx1-31002"></a> (<span
class="ptmb7t---109">H</span>ead <span
class="ptmb7t---109">U</span>p <span
class="ptmb7t---109">D</span>isplay).
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-hud</span>: Turns the HUD<a
name="dx1-31003"></a> on.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-anti-alias-hud</span>: Turns on anti-alised HUD lines<a
name="dx1-31004"></a> for better
quality, if hardware supports this.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-anti-alias-hud</span>: Turns off anti-aliased HUD lines.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-panel</span>: Turns the instrument panel<a
name="dx1-31005"></a> on (default).
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-panel</span>: Turns the instrument panel<a
name="dx1-31006"></a> off.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-sound</span>: Self explaining.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-sound</span>: See above.</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.3</span> <a
name="x1-320004.4.3"></a>Flight model</h4><a
name="dx1-32001"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--aircraft=</span><span
class="ptmri7t---109">name of aircraft</span>
<span
class="ptmri7t---109">definition file </span>Example: <span
class="pcrr7t---109">--aircraft=c310</span>. For possible choices check
the directory <span
class="pcrr7t---109">/FlightGear/Aircraft</span>. Do not include the extension
<span
class="pcrr7t---109">''-set.xml'' </span>into the aircraft name but use the remaining beginning of
the respective file names for choosing an aircraft. This way flight model,
panel etc. are all loaded in a consistent way.
</li>
<li class="itemize"><span
class="pcrr7t---109">--fdm=</span><span
class="ptmri7t---109">abcd </span>Select the core flight model<a
name="dx1-32002"></a>. Options are <span
class="pcrr7t---109">jsb, larcsim,</span>
<span
class="pcrr7t---109">yasim, magic, balloon, external, ada,</span>
<span
class="pcrr7t---109">null</span>. Default value is <span
class="pcrr7t---109">jsb </span>(<span
class="ptmbi7t---109">JSBSim</span>)<a
name="dx1-32003"></a>. larcsim is the flight model which
<span
class="ptmbi7t---109">FlightGear </span>inherited from the LaRCSim simulator. yasim ist Any Ross&#8217; Yet
Another Flight Dynamics Simulator. Magic is a slew mode. Balloon is a hot
air balloon. External refers to remote control of the simulator. Null selects no
flight synamics model at all. The UIUC flight model<a
name="dx1-32004"></a> is not chosen this way
but via the next option! For further information on flight models cf. Section
<a
href="#x1-80001.4">1.4<!--tex4ht:ref: flightmodels--></a> and below.
</li>
<li class="itemize"><span
class="pcrr7t---109">--aero=</span><span
class="ptmri7t---109">abcd </span>Specifies the aircraft model<a
name="dx1-32005"></a> to load. Default is a Cessna c172.
Alternatives available depend on the flight model chosen.
</li>
<li class="itemize"><span
class="pcrr7t---109">--model-hz=</span><span
class="ptmri7t---109">n </span>Run the Flight Dynamics Model with this rate (iterations
per second).
</li>
<li class="itemize"><span
class="pcrr7t---109">--speed=</span><span
class="ptmri7t---109">n </span>Run the Flight Dynamics Model this much faster than real
time.
</li>
<li class="itemize"><span
class="pcrr7t---109">--notrim </span>Do NOT attempt to trim the model when initializing JSBSim.
</li>
<li class="itemize"><span
class="pcrr7t---109">--on-ground</span>: Start up at ground level (default).
</li>
<li class="itemize"><span
class="pcrr7t---109">--in-air</span>: Start up in the air. Naturally, you have to specify an initial
altitude as below for this to make sense. This is a must for the X15.
</li>
<li class="itemize"><span
class="pcrr7t---109">--wind=</span><span
class="ptmri7t---109">DIR@SPEED</span>: Specify wind coming from the direction DIR (in
degrees) at speed SPEED (knots).</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.4</span> <a
name="x1-330004.4.4"></a>Aircraft model directory (Only for the UIUC Flight Dynamics Model)</h4><a
name="dx1-33001"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--aircraft-dir=</span><span
class="ptmri7t---109">path</span>: Aircraft directory relative to the root-path,
defined via <span
class="pcrr7t---109">$FG</span>_<span
class="pcrr7t---109">ROOT </span>or <span
class="pcrr7t---109">--fg-root</span>.</li></ul>
<!--l. 245--><p class="noindent">Remark: The difference in the handling of UIUC models has historic reasons. These
models use the LaRCsim FDM. As this FDM isn&#8217;t the default FDM any more you have
to specify it manually. Also the airplane description needs manual interaction as you
have to specify the directory by hand where the specific aircraft data resides. So you have
to use the following for flying the &#8217;TwinOtter&#8217;:
<!--l. 252--><p class="noindent"><span
class="pcrr7t---109">fgfs --fdm=larcsim --aero=uiuc</span>
<!--l. 255--><p class="noindent"><span
class="pcrr7t---109">--aircraft-dir=Aircraft-uiuc/TwinOtter</span>
<!--l. 259--><p class="noindent">Fortunately work has been done to simplificate this. At least those airplanes can be
flown easily by using an appropriate &#8217;--aircraft&#8217;-string. These are the following:
<!--l. 265--><p class="noindent"><span
class="pcrr7t---109">--aircraft=747-uiuc, --aircraft=beech99-uiuc,</span>
<br class="newline"><span
class="pcrr7t---109">--aircraft=c172-uiuc, --aircraft=c310-uiuc</span>
<!--l. 270--><p class="indent"> If time permits the remaining aircrafts will be adjusted soon. Please have a
look at <span
class="pcrr7t---109">$FG</span>_<span
class="pcrr7t---109">ROOT/Aircraft-uiuc </span>for the avaliable aircrafts provided
by the UIUC model collection. Also please read the notes in Section <a
href="#x1-80001.4">1.4<!--tex4ht:ref: flightmodels--></a> on
UIUC.
<h4 class="subsectionHead"><span class="titlemark">4.4.5</span> <a
name="x1-340004.4.5"></a>Initial Position and Orientation</h4><a
name="dx1-34001"></a><a
name="dx1-34002"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--airport-id=</span><span
class="ptmri7t---109">ABCD</span>: If you want to start directly at an airport<a
name="dx1-34003"></a>, enter its
international code,<a
name="dx1-34004"></a> i.e. KJFK for JFK airport in New York etc. A long/short
list of the IDs of the airports being implemented can be found in <span
class="pcrr7t---109">/Flight</span>
<span
class="pcrr7t---109">Gear/Airports</span>. You only have to unpack one of the files with <span
class="pcrr7t---109">gunzip</span>.
Keep in mind, you need the terrain data for the relevant region, though!<a
name="dx1-34005"></a>
</li>
<li class="itemize"><span
class="pcrr7t---109">--offset-distance=</span><span
class="ptmri7t---109">nm</span>: Here you can specify the distance to
threshold in nm.
</li>
<li class="itemize"><span
class="pcrr7t---109">--offset-azimuth=</span><span
class="ptmri7t---109">deg</span>: Here you can specify the heading to threshold
in degrees.
</li>
<li class="itemize"><span
class="pcrr7t---109">--lon=</span><span
class="ptmri7t---109">degrees</span>: This is the startup longitude<a
name="dx1-34006"></a> in degrees (west = -).
</li>
<li class="itemize"><span
class="pcrr7t---109">--lat=</span><span
class="ptmri7t---109">degrees</span>: This is the startup latitude<a
name="dx1-34007"></a> in degrees (south = -).
</li>
<li class="itemize"><span
class="pcrr7t---109">--altitude=</span><span
class="ptmri7t---109">feet</span>: This is useful if you want to start in free flight in
connection with <span
class="pcrr7t---109">--in-air</span>. Altitude specified in feet unless you choose
<span
class="pcrr7t---109">--units-meters</span>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--heading=</span><span
class="ptmri7t---109">degrees</span>: Sets the initial heading<a
name="dx1-34008"></a> (yaw angle) in degrees.
</li>
<li class="itemize"><span
class="pcrr7t---109">--roll=</span><span
class="ptmri7t---109">degrees</span>: Sets the startup roll angle<a
name="dx1-34009"></a> (roll angle) in degrees.
</li>
<li class="itemize"><span
class="pcrr7t---109">--pitch=</span><span
class="ptmri7t---109">degrees</span>: Sets the startup pitch angle<a
name="dx1-34010"></a> (pitch angle) in degrees.
</li>
<li class="itemize"><span
class="pcrr7t---109">--uBody=</span><span
class="ptmri7t---109">feet per second</span>: Speed along the body X axis in feet per second,
unless you choose <span
class="pcrr7t---109">--units-meters</span>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--vBody=</span><span
class="ptmri7t---109">feet per second</span>: Speed along the body Y axis in feet per second,
unless you choose <span
class="pcrr7t---109">--units-meters</span>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--wBody=</span><span
class="ptmri7t---109">feet per second</span>: Speed along the body Z axis in feet per second,
unless you choose <span
class="pcrr7t---109">--units-meters</span>.
</li>
<li class="itemize"><span
class="pcrr7t---109">--vc=</span><span
class="ptmri7t---109">knots</span>: Allows specifying the initial airspeed in knots (only in
connection with <span
class="pcrr7t---109">--fdm=jsb</span>).
</li>
<li class="itemize"><span
class="pcrr7t---109">--mach=</span><span
class="ptmri7t---109">num</span>: Allows specifying the initial airspeed as Mach number (only
in connection with <span
class="pcrr7t---109">--fdm=jsb</span>).</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.6</span> <a
name="x1-350004.4.6"></a>Rendering Options</h4>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--bpp=</span><span
class="ptmri7t---109">depth</span>: Specify the bits per pixel.
</li>
<li class="itemize"><span
class="pcrr7t---109">--fog-disable</span>: To cut down the rendering efforts, distant regions are
vanishing in fog<a
name="dx1-35001"></a> by default. If you disable fog<a
name="dx1-35002"></a>ging, you&#8217;ll see farther but your
frame rates will drop.
</li>
<li class="itemize"><span
class="pcrr7t---109">--fog-fastest</span>: The scenery will not look very nice but frame rate<a
name="dx1-35003"></a> will
increase.
</li>
<li class="itemize"><span
class="pcrr7t---109">--fog-nicest</span>: This option will give you a fairly realistic view of flying
on a hazy day.<a
name="dx1-35004"></a>
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-clouds</span>: Enable cloud layer<a
name="dx1-35005"></a> (default).
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-clouds</span>: Disable cloud layer.
</li>
<li class="itemize"><span
class="pcrr7t---109">--clouds-asl=</span><span
class="ptmri7t---109">xxx</span>: Specify altitude of cloud layer above sea level.
</li>
<li class="itemize"><span
class="pcrr7t---109">--fov=</span><span
class="ptmri7t---109">xx.x</span>: Sets the field of view<a
name="dx1-35006"></a> in degrees. Default is 55.0.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-fullscreen</span>: Disable full screen mode<a
name="dx1-35007"></a> (default).
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-fullscreen</span>: Enable full screen mode.
</li>
<li class="itemize"><span
class="pcrr7t---109">--shading-flat</span>: This is the fastest mode but the terrain will look ugly!
This option might help if your video processor is really slow.
</li>
<li class="itemize"><span
class="pcrr7t---109">--shading-smooth</span>: This is the recommended (and default) setting -
things will look really nice.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-skyblend</span>: No fogging or haze<a
name="dx1-35008"></a>, sky will be displayed using
just one color. Fast but ugly!
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-skyblend</span>: Fogging/haze is enabled, sky and terrain<a
name="dx1-35009"></a> look
realistic. This is the default and recommended setting.
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-textures</span>: Terrain details will be disabled. Looks ugly, but
might help if your video board is slow.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-textures</span>: Default and recommended.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-wireframe</span>: If you want to know how the world of
<span
class="ptmbi7t---109">FlightGear </span>looks like internally, try this!<a
name="dx1-35010"></a>
</li>
<li class="itemize"><span
class="pcrr7t---109">--disable-wireframe</span>: No wireframe. Default.
</li>
<li class="itemize"><span
class="pcrr7t---109">--geometry=</span><span
class="ptmri7t---109">WWWxHHH</span>: Defines the size of the window used, i.e.
<span
class="pcrr7t---109">WWWxHHH </span>can be <span
class="pcrr7t---109">640x480</span>, <span
class="pcrr7t---109">800x600</span>, or <span
class="pcrr7t---109">1024x768</span>.<a
name="dx1-35011"></a>
</li>
<li class="itemize"><span
class="pcrr7t---109">--view-offset=</span><span
class="ptmri7t---109">xxx</span>: Allows setting the default forward view direction
as an offset from straight ahead. Possible values are <span
class="pcrr7t---109">LEFT, RIGHT,</span>
<span
class="pcrr7t---109">CENTER</span>, or a specific number of degrees. Useful for multi-window display.<a
name="dx1-35012"></a>
</li>
<li class="itemize"><span
class="pcrr7t---109">--visibility=</span><span
class="ptmri7t---109">meters</span>: You can specify the initial visibility in meters
here.
</li>
<li class="itemize"><span
class="pcrr7t---109">--visibility-miles=</span><span
class="ptmri7t---109">miles</span>: You can specify the initial visibility in
miles here.</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.7</span> <a
name="x1-360004.4.7"></a>HUD Options</h4>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--hud-tris</span>: HUD displays the number of triangles<a
name="dx1-36001"></a> rendered.
</li>
<li class="itemize"><span
class="pcrr7t---109">--hud-culled</span>: HUD displays percentage of triangles culled.</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.8</span> <a
name="x1-370004.4.8"></a>Time Options</h4><a
name="dx1-37001"></a><a
name="dx1-37002"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--time-offset=</span><span
class="ptmri7t---109">[+-]hh:mm:ss</span>: Offset local time<a
name="dx1-37003"></a> by this amount.
</li>
<li class="itemize"><span
class="pcrr7t---109">--time-match-real</span>: Synchronize real-world and <span
class="ptmbi7t---109">FlightGear </span>time.
</li>
<li class="itemize"><span
class="pcrr7t---109">--time-match-local</span>: Synchronize local real-world and <span
class="ptmbi7t---109">FlightGear</span>
time.
</li>
<li class="itemize"><span
class="pcrr7t---109">--start-date-gmt=</span><span
class="ptmri7t---109">yyyy:mm:dd:hh:mm:ss</span>: Specify a starting time<a
name="dx1-37004"></a> and
date. Uses your system time.
</li>
<li class="itemize"><span
class="pcrr7t---109">--start-date-gmt=</span><span
class="ptmri7t---109">yyyy:mm:dd:hh:mm:ss</span>: Specify a starting time and
date. Time is Greenwich Mean Time.
</li>
<li class="itemize"><span
class="pcrr7t---109">--start-date-lat=</span><span
class="ptmri7t---109">yyyy:mm:dd:hh:mm:ss</span>: Specify a starting time and
date. Uses local aircraft time.</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.9</span> <a
name="x1-380004.4.9"></a>Network Options</h4><a
name="dx1-38001"></a><a
name="dx1-38002"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--httpd=port </span>Enable http server on the specified port.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-network-olk</span>: Enables Oliver Delises&#8217;s Multipilot mode.
</li>
<li class="itemize"><span
class="pcrr7t---109">--enable-network-olk</span>: Disables Oliver Delises&#8217;s Multipilot mode
(default).
</li>
<li class="itemize"><span
class="pcrr7t---109">--net-hud</span>: HUD displays network info.
</li>
<li class="itemize"><span
class="pcrr7t---109">--net-id=</span><span
class="ptmri7t---109">name</span>: Specify your own callsign<a
name="dx1-38003"></a></li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.10</span> <a
name="x1-390004.4.10"></a>Route/Waypoint Options</h4><a
name="dx1-39001"></a><a
name="dx1-39002"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--wp=</span><span
class="ptmri7t---109">ID[@alt]</span>: Allows specifying a waypoint for the GC autopilot; it is
possible to specify multiple waypoints (i.e. a route) via multiple instances of
this command.
</li>
<li class="itemize"><span
class="pcrr7t---109">--flight-plan=</span><span
class="ptmri7t---109">[file]</span>: This is more comfortable if you have several
waypoints. You can specify a file to read them from.</li></ul>
<!--l. 390--><p class="noindent">These options are rather geared to the advanced user who knows what he is
doing.
<h4 class="subsectionHead"><span class="titlemark">4.4.11</span> <a
name="x1-400004.4.11"></a>IO Options</h4><a
name="dx1-40001"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--gamin=</span><span
class="ptmri7t---109">params</span>: Open connection using the Garmin GPS protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--joyclient=</span><span
class="ptmri7t---109">params</span>: Open connection to an Agwagon joystick.
</li>
<li class="itemize"><span
class="pcrr7t---109">--native-ctrls=</span><span
class="ptmri7t---109">params</span>: Open connection using the FG NAtive
Controls protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--native-fdm=</span><span
class="ptmri7t---109">params</span>: Open connection using the FG Native FDM
protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--native=</span><span
class="ptmri7t---109">params</span>: Open connection using the FG Native protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--nmea=</span><span
class="ptmri7t---109">params</span>: Open connection using the NMEA protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--opengc=</span><span
class="ptmri7t---109">params</span>: Open connection using the OpenGC protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--props=</span><span
class="ptmri7t---109">params</span>: Open connection using the interactive property
manager.
</li>
<li class="itemize"><span
class="pcrr7t---109">--pve=</span><span
class="ptmri7t---109">params</span>: Open connection using the PVE protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--ray=</span><span
class="ptmri7t---109">params</span>: Open connection using the RayWoodworth motion chair
protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--rul=</span><span
class="ptmri7t---109">params</span>: Open connection using the RUL protocol.
</li>
<li class="itemize"><span
class="pcrr7t---109">--atc610x</span>: Enable atc610x interface.</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.12</span> <a
name="x1-410004.4.12"></a>Debugging options</h4><a
name="dx1-41001"></a>
<ul class="itemize1">
<li class="itemize"><span
class="pcrr7t---109">--trace-read=</span><span
class="ptmri7t---109">params</span>: Trace the reads for a property; multiple
instances are allowed.
</li>
<li class="itemize"><span
class="pcrr7t---109">--trace-write=</span><span
class="ptmri7t---109">params</span>: Trace the writes for a property; multiple
instances are allowed.</li></ul>
<h4 class="subsectionHead"><span class="titlemark">4.4.13</span> <a
name="x1-420004.4.13"></a>Joystick properties</h4><a
name="dx1-42001"></a> Could you imagine a pilot in his or her Cessna controlling
the machine with a keyboard alone? For getting the proper feeling of flight you will
need a joystick/yoke plus rudder pedals, right? However, the combination of
numerous types of joystick<a
name="dx1-42002"></a>s, flightsticks, yoke<a
name="dx1-42003"></a>s, pedal<a
name="dx1-42004"></a>s etc. on the market with the
several target operating systems, makes joystick support a nontrivial task in
<span
class="ptmbi7t---109">FlightGear</span>.
<!--l. 427--><p class="noindent">All of <span
class="ptmbi7t---109">FlightGear</span>&#8217;s joystick (as well as keyboard) properties are written in plain ASCII
files, thus anyone can adapt them, if necessary. Fortunately, there is a tool available
now, which takes most of the burden form the average user who, maybe, is
not that experienced with XML, the language which these files arwe written
in.
<!--l. 429--><p class="indent"> For configuring your joystick, open a command shell (command promt(DOS shell
under windows, to be foiund unter Start&#8212;All programs&#8212;Accessories). Change to the
directory <span
class="pcrr7t---109">/FlightGear/bin </span>via e.g. (modify to your path)
<!--l. 431--><p class="noindent"><span
class="pcrr7t---109">cd c:</span><span
class="cmsy-10--109">\</span><span
class="pcrr7t---109">FlightGear</span><span
class="cmsy-10--109">\</span><span
class="pcrr7t---109">bin</span>
<!--l. 434--><p class="indent"> and invoke the tool fgjs via
<!--l. 436--><p class="noindent"><span
class="pcrr7t---109">fgjs</span>
<!--l. 439--><p class="indent"> on a UNIX/Linux machine, or via
<!--l. 441--><p class="noindent"><span
class="pcrr7t---109">fgjs.exe</span>
<!--l. 444--><p class="indent"> on a Windows machine. The program will tell you which joysticks, if any, where
detected. Now follow the commands given on screen, i.e. move the axis and press the
buttons as required. Be careful, a minor touch already &#8221;counts&#8221; as a movement.
Check the reports on screen. If you feel something went wrong, just re-start the
program
<!--l. 446--><p class="indent"> After you are done with all the axis/switches, the directory above will hold a file
called <span
class="pcrr7t---109">fgfsrc.js</span>. If the <span
class="ptmbi7t---109">FlightGear </span>base directory <span
class="pcrr7t---109">FlighGear </span>does not already
contain an options file <span
class="pcrr7t---109">.fgfsrc </span>(under UNIX)/<span
class="pcrr7t---109">system.fgfsrc </span>(under Windows)
mentioned above, just copy
<!--l. 449--><p class="noindent"><span
class="pcrr7t---109">fgfsrc.js </span>into <span
class="pcrr7t---109">.fgfsrc </span>(UNIX)/<span
class="pcrr7t---109">system.fgfsrc </span>(Windows)
<!--l. 453--><p class="noindent">and place it into the directory <span
class="ptmbi7t---109">FlightGear </span>base directory <span
class="pcrr7t---109">FlighGear</span>. In case you
already wrote an options file, just open it as well as <span
class="pcrr7t---109">fgfsrc.js </span>with an editor and copy
the entries from <span
class="pcrr7t---109">fgfsrc.js </span>into <span
class="pcrr7t---109">.fgfsrc</span>/<span
class="pcrr7t---109">system.fgfsrc</span>. One hint: The output
of <span
class="pcrr7t---109">fgjs </span>is UNIX formatted. As a result, Windows Editor may not display it the proper
way. I suggest getting an editor being able to handle UNIX files as well. My favorite
freeware file editor for that purpose, although somewhat dated, is PFE still, to be
obtained from
<!--l. 456--><p class="indent"> <a
href="http://www.lancs.ac.uk/people/cpaap/pfe/" >http://www.lancs.ac.uk/people/cpaap/pfe/</a>.
<!--l. 458--><p class="indent"> The the axis/button assignment of <span
class="pcrr7t---109">fgjs </span>should, at least, get the axis assignments
right, its output may need some tweaking. There may be axis moving the opposite
way the should, the dead zones may be too small etc. For instance, I had to
change
<!--l. 460--><p class="indent"> <span
class="pcrr7t---109">--prop:/input/joysticks/js[1]/axis[1]/binding/factor=-1.0</span>
<!--l. 462--><p class="indent"> into
<!--l. 464--><p class="indent"> <span
class="pcrr7t---109">--prop:/input/joysticks/js[1]/axis[1]/binding/factor=1.0</span>
<!--l. 466--><p class="indent"> (USB CH Flightsim Yoke under Windows XP). Thus, here is a short introduction into
the assignments of joystick properties.
<!--l. 468--><p class="indent"> Basically, all axes settings are specified via lines having the following structure:
<!--l. 471--><p class="indent"> <span
class="pcrr7t---109">--prop:/input/joysticks/js[</span><span
class="ptmri7t---109">n</span><span
class="pcrr7t---109">]/axis[</span><span
class="ptmri7t---109">m</span><span
class="pcrr7t---109">]</span>
<br class="newline"><span
class="pcrr7t---109">/binding/command=property-scale</span>
<br class="newline"><span
class="pcrr7t---109">--prop:/input/joysticks/js[</span><span
class="ptmri7t---109">n</span><span
class="pcrr7t---109">]/axis[</span><span
class="ptmri7t---109">m</span><span
class="pcrr7t---109">]</span>
<br class="newline"><span
class="pcrr7t---109">/binding/property=/controls/</span><span
class="ptmri7t---109">steering option</span>
<br class="newline"><span
class="pcrr7t---109">--prop:/input/joysticks/js[</span><span
class="ptmri7t---109">n</span><span
class="pcrr7t---109">]/axis[</span><span
class="ptmri7t---109">m</span><span
class="pcrr7t---109">]</span>
<br class="newline"><span
class="pcrr7t---109">/binding/dead-band=</span><span
class="ptmri7t---109">db </span><span
class="pcrr7t---109">--prop:/input/joysticks/js[</span><span
class="ptmri7t---109">n</span><span
class="pcrr7t---109">]/axis[</span><span
class="ptmri7t---109">m</span><span
class="pcrr7t---109">]</span>
<br class="newline"><span
class="pcrr7t---109">/binding/offset=</span><span
class="ptmri7t---109">os </span><span
class="pcrr7t---109">--prop:/input/joysticks/js[</span><span
class="ptmri7t---109">n</span><span
class="pcrr7t---109">]/axis[</span><span
class="ptmri7t---109">m</span><span
class="pcrr7t---109">]</span>
<br class="newline"><span
class="pcrr7t---109">/binding/factor=</span><span
class="ptmri7t---109">fa</span>
<!--l. 483--><p class="noindent">where
<div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0"
frame="void" id="TBL-3-" ><colgroup id="TBL-3-1g"><col
id="TBL-3-1"><col
id="TBL-3-2"><col
id="TBL-3-3"></colgroup><tr
valign="baseline" id="TBL-3-1-"><td align="right" nowrap="nowrap" id="TBL-3-1-1"
class="td11"> <span
class="ptmri7t---109">n</span></td><td align="center" nowrap="nowrap" id="TBL-3-1-2"
class="td11"> =</td><td align="left" nowrap="nowrap" id="TBL-3-1-3"
class="td11"> number of device (usually starting with 0) </td>
</tr><tr
valign="baseline" id="TBL-3-2-"><td align="right" nowrap="nowrap" id="TBL-3-2-1"
class="td11"> <span
class="ptmri7t---109">m</span></td><td align="center" nowrap="nowrap" id="TBL-3-2-2"
class="td11"> =</td><td align="left" nowrap="nowrap" id="TBL-3-2-3"
class="td11"> number of axis (usually starting with 0) </td>
</tr><tr
valign="baseline" id="TBL-3-3-"><td align="right" nowrap="nowrap" id="TBL-3-3-1"
class="td11"> <span
class="ptmri7t---109">steering option</span></td><td align="center" nowrap="nowrap" id="TBL-3-3-2"
class="td11"> =</td><td align="left" nowrap="nowrap" id="TBL-3-3-3"
class="td11"> elevator, aileron, rudder, throttle, mixture, pitch </td>
</tr><tr
valign="baseline" id="TBL-3-4-"><td align="right" nowrap="nowrap" id="TBL-3-4-1"
class="td11"> <span
class="ptmri7t---109">dead-band</span></td><td align="center" nowrap="nowrap" id="TBL-3-4-2"
class="td11"> =</td><td align="left" nowrap="nowrap" id="TBL-3-4-3"
class="td11"> range, within which signals are discarded; </td>
</tr><tr
valign="baseline" id="TBL-3-5-"><td align="right" nowrap="nowrap" id="TBL-3-5-1"
class="td11"> </td><td align="center" nowrap="nowrap" id="TBL-3-5-2"
class="td11"> </td><td align="left" nowrap="nowrap" id="TBL-3-5-3"
class="td11"> useful to avoid jittering for minor yoke movements </td>
</tr><tr
valign="baseline" id="TBL-3-6-"><td align="right" nowrap="nowrap" id="TBL-3-6-1"
class="td11"> <span
class="ptmri7t---109">offset</span></td><td align="center" nowrap="nowrap" id="TBL-3-6-2"
class="td11"> =</td><td align="left" nowrap="nowrap" id="TBL-3-6-3"
class="td11"> specifies, if device not centered in its neutral position</td>
</tr><tr
valign="baseline" id="TBL-3-7-"><td align="right" nowrap="nowrap" id="TBL-3-7-1"
class="td11"> <span
class="ptmri7t---109">factor</span></td><td align="center" nowrap="nowrap" id="TBL-3-7-2"
class="td11"> =</td><td align="left" nowrap="nowrap" id="TBL-3-7-3"
class="td11"> controls sensitivity of that axis; defaults to +1, </td>
</tr><tr
valign="baseline" id="TBL-3-8-"><td align="right" nowrap="nowrap" id="TBL-3-8-1"
class="td11"> </td><td align="center" nowrap="nowrap" id="TBL-3-8-2"
class="td11"> </td><td align="left" nowrap="nowrap" id="TBL-3-8-3"
class="td11"> with a value of -1 reversing the behavior </td> </tr><!--rcl--></table>
</div>
<!--l. 499--><p class="noindent">You should be able to at least get your joystick working along these lines. Concerning all
the finer points, for instance, getting the joystick buttons working, John Check<a
name="dx1-42005"></a> has
written a very useful README being included in the base package to be found
under <span
class="pcrr7t---109">FlightGear/Docs/Readme/Joystick.html</span>. In case of any
trouble with your input device, it is highly recommended to have a look into this
document.
<h2 class="chapterHead"><span class="titlemark">Chapter&nbsp;5</span><br><a
name="x1-430005"></a>In-flight: All about instruments, keystrokes and menus</h2>
<!--l. 32--><p class="noindent">The following is a description of the main systems for controlling the program and
piloting the plane: Historically, keyboard controls<a
name="dx1-43001"></a> were developed first, and you can still
control most of the simulator via the keyboard alone. Later on, they were supplemented
by several menu entries, making the interface more accessible, particularly for beginners,
and providing additional functionality.
<!--l. 38--><p class="indent"> For getting a real feeling of flight, you should definitely consider getting a joystick<a
name="dx1-43002"></a> or
- preferred - a yoke<a
name="dx1-43003"></a> plus rudder pedals<a
name="dx1-43004"></a>. In any case, you can specify your device of
choice for control via the <span
class="pcrr7t---109">--control-mode </span>option, i.e. select joystick, keyboard<a
name="dx1-43005"></a>,
mouse<a
name="dx1-43006"></a>. The default setting is joystick. Concerning instruments, there are again two
alternatives: You can use the panel or the HUD.
<!--l. 44--><p class="indent"> A short leaflet based on this chapter can be found at
<!--l. 47--><p class="indent"> <a
href="http://www.flightgear.org/Docs/InstallGuide/FGShortRef.html" >http://www.flightgear.org/Docs/InstallGuide/FGShortRef.html</a>.
<!--l. 50--><p class="noindent">A version of this leaflet can also be opened via <span
class="ptmbi7t---109">FlightGear</span>&#8217;s help menu.
<h3 class="sectionHead"><span class="titlemark">5.1</span> <a
name="x1-440005.1"></a>Starting the engine</h3>
<a
name="dx1-44001"></a>
<!--l. 57--><p class="noindent">Depending on your situation, when you start the simulator the engines may be on or off.
When they are on you just can go on with the start. When they are off, you have to start
them first. The ignition switch for starting the engine is situated in the lower left corner
of the panel. It is shwon in Fig. 4.
<!--l. 62--><p class="indent"> <div align="center"
class="centerline"><img
src="getstart5x.gif" alt="" class="fbox" > </div>
<!--l. 65--><p class="noindent">Fig. 4: <span
class="ptmri7t---109">The ignition switch.</span>
<!--l. 69--><p class="indent"> It has five positions: &#8221;OFF&#8221;, &#8221;L&#8221;, &#8221;R&#8221;, &#8221;BOTH&#8221;, and &#8221;START&#8221;. The extreme right
position is for starting the engine. For starting the engine, put it onto the position
&#8221;BOTH&#8221; using the mouse first.
<!--l. 71--><p class="indent"> Keep in mind that the mixture lever has to be at 100 % (all the way in) for starting
the engine - otherwise you will fail. In addition, advance the throttle to about
25 %.
<!--l. 73--><p class="indent"> Operate the starter using the SPACE key now. When pressing the SPACE key you
will observe the ignition switch to change to the position &#8221;START&#8221; and the engine to
start after a few seconds. Afterwards you can bring the throttle back to idle (all the way
out).
<!--l. 75--><p class="indent"> In addition, have a look if the parking brakes are on (red field lit). If so, press the &#8221;B&#8221;
button to release them.
<h3 class="sectionHead"><span class="titlemark">5.2</span> <a
name="x1-450005.2"></a>Keyboard controls</h3>
<a
name="dx1-45001"></a>
<!--l. 81--><p class="noindent">While joystick<a
name="dx1-45002"></a>s or yoke<a
name="dx1-45003"></a>s are supported as are rudder<a
name="dx1-45004"></a> pedals, you can fly <span
class="ptmbi7t---109">FlightGear</span>
using the keyboard alone. For proper control of the plane during flight via the keyboard
(i) the <span
class="pcrr7t---109">NumLock</span><a
name="dx1-45005"></a> key must be switched on (ii) the <span
class="ptmbi7t---109">FlightGear </span>window must
have focus (if not, click with the mouse onto the graphics window). Several
of the keyboard controls might be helpful even in case you use a joystick or
yoke.
<!--l. 88--><p class="indent"> After activating <span
class="pcrr7t---109">NumLock </span>the following main keyboard controls<a
name="dx1-45006"></a> for driving the
plane should work:
<!--l. 91--><p class="noindent">Tab. 1: <span
class="ptmri7t---109">Main keyboard controls</span><a
name="dx1-45007"></a> <span
class="ptmri7t---109">for </span><span
class="ptmbi7t---109">FlightGear </span><span
class="ptmri7t---109">on the numeric keypad with activated</span>
<span
class="pcrro7t---109">NumLock </span><span
class="ptmri7t---109">key:</span>.
<!--l. 96--><p class="indent"> <div align="center"
class="centerline"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0" rules="groups"
frame="border" id="TBL-4-" ><colgroup id="TBL-4-1g"><col
id="TBL-4-1"></colgroup><colgroup id="TBL-4-2g"><col
id="TBL-4-2"></colgroup><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-4-1-"><td align="left" nowrap="nowrap" id="TBL-4-1-1"
class="td11"> Key </td><td align="left" nowrap="nowrap" id="TBL-4-1-2"
class="td11"> Action </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-4-2-"><td align="left" nowrap="nowrap" id="TBL-4-2-1"
class="td11"> Pg Up/Pg Dn </td><td align="left" nowrap="nowrap" id="TBL-4-2-2"
class="td11"> Throttle<a
name="dx1-45008"></a> </td>
</tr><tr
valign="baseline" id="TBL-4-3-"><td align="left" nowrap="nowrap" id="TBL-4-3-1"
class="td11"> Left Arrow/Right Arrow</td><td align="left" nowrap="nowrap" id="TBL-4-3-2"
class="td11"> Aileron<a
name="dx1-45009"></a> </td>
</tr><tr
valign="baseline" id="TBL-4-4-"><td align="left" nowrap="nowrap" id="TBL-4-4-1"
class="td11"> Up Arrow/Down Arrow </td><td align="left" nowrap="nowrap" id="TBL-4-4-2"
class="td11"> Elevator<a
name="dx1-45010"></a> </td>
</tr><tr
valign="baseline" id="TBL-4-5-"><td align="left" nowrap="nowrap" id="TBL-4-5-1"
class="td11"> Ins/Enter </td><td align="left" nowrap="nowrap" id="TBL-4-5-2"
class="td11"> Rudder<a
name="dx1-45011"></a> </td>
</tr><tr
valign="baseline" id="TBL-4-6-"><td align="left" nowrap="nowrap" id="TBL-4-6-1"
class="td11"> 5 </td><td align="left" nowrap="nowrap" id="TBL-4-6-2"
class="td11"> Center aileron/elevator/rudder</td>
</tr><tr
valign="baseline" id="TBL-4-7-"><td align="left" nowrap="nowrap" id="TBL-4-7-1"
class="td11"> Home/End </td><td align="left" nowrap="nowrap" id="TBL-4-7-2"
class="td11"> Elevator trim<a
name="dx1-45012"></a> </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-4-8-"><td align="left" nowrap="nowrap" id="TBL-4-8-1"
class="td11"> </td> </tr><!--|l|l|--></table> </div></div>
<!--l. 99--><p class="noindent">For changing views you have to de-activate <span
class="pcrr7t---109">NumLock</span>. Now <span
class="pcrr7t---109">Shift </span>+ <span
class="cmmi-10--109">&lt;</span><span
class="pcrr7t---109">Numeric</span>
<span
class="pcrr7t---109">Keypad Key</span><span
class="cmmi-10--109">&gt; </span>changes the view as follows:
<!--l. 103--><p class="noindent">Tab. 2: <span
class="ptmri7t---109">View directions</span><a
name="dx1-45013"></a> <span
class="ptmri7t---109">accessible after de-activating </span><span
class="pcrro7t---109">NumLock </span><span
class="ptmri7t---109">on the numeric keypad.</span>
<!--l. 108--><p class="indent"> <div align="center"
class="centerline"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0" rules="groups"
frame="border" id="TBL-5-" ><colgroup id="TBL-5-1g"><col
id="TBL-5-1"></colgroup><colgroup id="TBL-5-2g"><col
id="TBL-5-2"></colgroup><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-5-1-"><td align="center" nowrap="nowrap" id="TBL-5-1-1"
class="td11"> Numeric Key</td><td align="left" nowrap="nowrap" id="TBL-5-1-2"
class="td11"> View direction<a
name="dx1-45014"></a></td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-5-2-"><td align="center" nowrap="nowrap" id="TBL-5-2-1"
class="td11"> Shift-8 </td> <td align="left" nowrap="nowrap" id="TBL-5-2-2"
class="td11"> Forward </td>
</tr><tr
valign="baseline" id="TBL-5-3-"><td align="center" nowrap="nowrap" id="TBL-5-3-1"
class="td11"> Shift-7 </td> <td align="left" nowrap="nowrap" id="TBL-5-3-2"
class="td11"> Left/forward </td>
</tr><tr
valign="baseline" id="TBL-5-4-"><td align="center" nowrap="nowrap" id="TBL-5-4-1"
class="td11"> Shift-4 </td> <td align="left" nowrap="nowrap" id="TBL-5-4-2"
class="td11"> Left </td>
</tr><tr
valign="baseline" id="TBL-5-5-"><td align="center" nowrap="nowrap" id="TBL-5-5-1"
class="td11"> Shift-1 </td> <td align="left" nowrap="nowrap" id="TBL-5-5-2"
class="td11"> Left/back </td>
</tr><tr
valign="baseline" id="TBL-5-6-"><td align="center" nowrap="nowrap" id="TBL-5-6-1"
class="td11"> Shift-2 </td> <td align="left" nowrap="nowrap" id="TBL-5-6-2"
class="td11"> Back </td>
</tr><tr
valign="baseline" id="TBL-5-7-"><td align="center" nowrap="nowrap" id="TBL-5-7-1"
class="td11"> Shift-3 </td> <td align="left" nowrap="nowrap" id="TBL-5-7-2"
class="td11"> Right/back </td>
</tr><tr
valign="baseline" id="TBL-5-8-"><td align="center" nowrap="nowrap" id="TBL-5-8-1"
class="td11"> Shift-6 </td> <td align="left" nowrap="nowrap" id="TBL-5-8-2"
class="td11"> Right </td>
</tr><tr
valign="baseline" id="TBL-5-9-"><td align="center" nowrap="nowrap" id="TBL-5-9-1"
class="td11"> Shift-9 </td> <td align="left" nowrap="nowrap" id="TBL-5-9-2"
class="td11"> Right/forward </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-5-10-"><td align="center" nowrap="nowrap" id="TBL-5-10-1"
class="td11"> </td> </tr><!--|c|l|--></table> </div></div>
<!--l. 111--><p class="noindent">Besides, there are several more options for adapting display on screen:
<!--l. 115--><p class="noindent">Tab. 3: <span
class="ptmri7t---109">Display options</span><a
name="dx1-45015"></a>
<!--l. 119--><p class="indent"> <div align="center"
class="centerline"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0" rules="groups"
frame="border" id="TBL-6-" ><colgroup id="TBL-6-1g"><col
id="TBL-6-1"></colgroup><colgroup id="TBL-6-2g"><col
id="TBL-6-2"></colgroup><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-6-1-"><td align="left" nowrap="nowrap" id="TBL-6-1-1"
class="td11"> Key </td><td align="left" nowrap="nowrap" id="TBL-6-1-2"
class="td11"> Action </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-6-2-"><td align="left" nowrap="nowrap" id="TBL-6-2-1"
class="td11"> P </td><td align="left" nowrap="nowrap" id="TBL-6-2-2"
class="td11"> Toggle instrument panel<a
name="dx1-45016"></a> on/off </td>
</tr><tr
valign="baseline" id="TBL-6-3-"><td align="left" nowrap="nowrap" id="TBL-6-3-1"
class="td11"> s </td><td align="left" nowrap="nowrap" id="TBL-6-3-2"
class="td11"> Cycle panel style full/mini </td>
</tr><tr
valign="baseline" id="TBL-6-4-"><td align="left" nowrap="nowrap" id="TBL-6-4-1"
class="td11"> Shift-F5/F6</td><td align="left" nowrap="nowrap" id="TBL-6-4-2"
class="td11"> Shift the panel in y direction </td>
</tr><tr
valign="baseline" id="TBL-6-5-"><td align="left" nowrap="nowrap" id="TBL-6-5-1"
class="td11"> Shift-F7/F8</td><td align="left" nowrap="nowrap" id="TBL-6-5-2"
class="td11"> Shift the panel in x direction </td>
</tr><tr
valign="baseline" id="TBL-6-6-"><td align="left" nowrap="nowrap" id="TBL-6-6-1"
class="td11"> Shift-F3 </td><td align="left" nowrap="nowrap" id="TBL-6-6-2"
class="td11"> Read a panel from a property list </td>
</tr><tr
valign="baseline" id="TBL-6-7-"><td align="left" nowrap="nowrap" id="TBL-6-7-1"
class="td11"> i/I </td><td align="left" nowrap="nowrap" id="TBL-6-7-2"
class="td11"> Minimize/maximize HUD </td>
</tr><tr
valign="baseline" id="TBL-6-8-"><td align="left" nowrap="nowrap" id="TBL-6-8-1"
class="td11"> h/H </td><td align="left" nowrap="nowrap" id="TBL-6-8-2"
class="td11"> Change color of HUD/toggle HUD off </td>
</tr><tr
valign="baseline" id="TBL-6-9-"><td align="left" nowrap="nowrap" id="TBL-6-9-1"
class="td11"> </td><td align="left" nowrap="nowrap" id="TBL-6-9-2"
class="td11"> forward/backward </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-6-10-"><td align="left" nowrap="nowrap" id="TBL-6-10-1"
class="td11"> Ctrl + O/P </td><td align="left" nowrap="nowrap" id="TBL-6-10-2"
class="td11"> Tilt view down/up <a
name="dx1-45017"></a> </td>
</tr><tr
valign="baseline" id="TBL-6-11-"><td align="left" nowrap="nowrap" id="TBL-6-11-1"
class="td11"> x/X </td><td align="left" nowrap="nowrap" id="TBL-6-11-2"
class="td11"> Zoom in/out </td>
</tr><tr
valign="baseline" id="TBL-6-12-"><td align="left" nowrap="nowrap" id="TBL-6-12-1"
class="td11"> v </td><td align="left" nowrap="nowrap" id="TBL-6-12-2"
class="td11"> Cycle view modes<a
name="dx1-45018"></a> </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-6-13-"><td align="left" nowrap="nowrap" id="TBL-6-13-1"
class="td11"> W </td><td align="left" nowrap="nowrap" id="TBL-6-13-2"
class="td11"> Toggle full screen mode<a
name="dx1-45019"></a> on/off (3dfx only)</td>
</tr><tr
valign="baseline" id="TBL-6-14-"><td align="left" nowrap="nowrap" id="TBL-6-14-1"
class="td11"> z/Z </td><td align="left" nowrap="nowrap" id="TBL-6-14-2"
class="td11"> Change visibility<a
name="dx1-45020"></a> (fog) forward/backward </td>
</tr><tr
valign="baseline" id="TBL-6-15-"><td align="left" nowrap="nowrap" id="TBL-6-15-1"
class="td11"> F8 </td><td align="left" nowrap="nowrap" id="TBL-6-15-2"
class="td11"> Toggle fog on/off </td>
</tr><tr
valign="baseline" id="TBL-6-16-"><td align="left" nowrap="nowrap" id="TBL-6-16-1"
class="td11"> F2 </td><td align="left" nowrap="nowrap" id="TBL-6-16-2"
class="td11"> Refresh Scenery tile cache </td>
</tr><tr
valign="baseline" id="TBL-6-17-"><td align="left" nowrap="nowrap" id="TBL-6-17-1"
class="td11"> F4 </td><td align="left" nowrap="nowrap" id="TBL-6-17-2"
class="td11"> Force Lighting update </td>
</tr><tr
valign="baseline" id="TBL-6-18-"><td align="left" nowrap="nowrap" id="TBL-6-18-1"
class="td11"> F9 </td><td align="left" nowrap="nowrap" id="TBL-6-18-2"
class="td11"> Toggle texturing on/off </td>
</tr><tr
valign="baseline" id="TBL-6-19-"><td align="left" nowrap="nowrap" id="TBL-6-19-1"
class="td11"> F10 </td><td align="left" nowrap="nowrap" id="TBL-6-19-2"
class="td11"> Toggle menu on/off </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-6-20-"><td align="left" nowrap="nowrap" id="TBL-6-20-1"
class="td11"> </td> </tr><!--|l|l|--></table> </div></div>
<!--l. 122--><p class="noindent">The autopilot<a
name="dx1-45021"></a> is controlled via the following keys:
<!--l. 125--><p class="noindent">Tab. 4: <span
class="ptmri7t---109">Autopilot and related controls.</span><a
name="dx1-45022"></a>
<!--l. 129--><p class="indent"> <div align="center"
class="centerline"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0" rules="groups"
frame="border" id="TBL-7-" ><colgroup id="TBL-7-1g"><col
id="TBL-7-1"></colgroup><colgroup id="TBL-7-2g"><col
id="TBL-7-2"></colgroup><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-7-1-"><td align="left" nowrap="nowrap" id="TBL-7-1-1"
class="td11"> Key </td><td align="left" nowrap="nowrap" id="TBL-7-1-2"
class="td11"> Action </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-7-2-"><td align="left" nowrap="nowrap" id="TBL-7-2-1"
class="td11"> Ctrl + A</td><td align="left" nowrap="nowrap" id="TBL-7-2-2"
class="td11"> Altitude hold<a
name="dx1-45023"></a> toggle on/off </td>
</tr><tr
valign="baseline" id="TBL-7-3-"><td align="left" nowrap="nowrap" id="TBL-7-3-1"
class="td11"> Ctrl + G</td><td align="left" nowrap="nowrap" id="TBL-7-3-2"
class="td11"> Follow glide slope 1 toggle on/off </td>
</tr><tr
valign="baseline" id="TBL-7-4-"><td align="left" nowrap="nowrap" id="TBL-7-4-1"
class="td11"> Ctrl + H</td><td align="left" nowrap="nowrap" id="TBL-7-4-2"
class="td11"> Heading hold<a
name="dx1-45024"></a> toggle on/off </td>
</tr><tr
valign="baseline" id="TBL-7-5-"><td align="left" nowrap="nowrap" id="TBL-7-5-1"
class="td11"> Ctrl + N</td><td align="left" nowrap="nowrap" id="TBL-7-5-2"
class="td11"> Follow NAV 1 radial toggle on/off </td>
</tr><tr
valign="baseline" id="TBL-7-6-"><td align="left" nowrap="nowrap" id="TBL-7-6-1"
class="td11"> Ctrl + S </td><td align="left" nowrap="nowrap" id="TBL-7-6-2"
class="td11"> Autothrottle<a
name="dx1-45025"></a> toggle on/off </td>
</tr><tr
valign="baseline" id="TBL-7-7-"><td align="left" nowrap="nowrap" id="TBL-7-7-1"
class="td11"> Ctrl + T</td><td align="left" nowrap="nowrap" id="TBL-7-7-2"
class="td11"> Terrain follow toggle on/off </td>
</tr><tr
valign="baseline" id="TBL-7-8-"><td align="left" nowrap="nowrap" id="TBL-7-8-1"
class="td11"> Ctrl + U</td><td align="left" nowrap="nowrap" id="TBL-7-8-2"
class="td11"> Add 1000 ft. to your altitude (emergency)</td>
</tr><tr
valign="baseline" id="TBL-7-9-"><td align="left" nowrap="nowrap" id="TBL-7-9-1"
class="td11"> F6 </td><td align="left" nowrap="nowrap" id="TBL-7-9-2"
class="td11"> Toggle autopilot target: </td>
</tr><tr
valign="baseline" id="TBL-7-10-"><td align="left" nowrap="nowrap" id="TBL-7-10-1"
class="td11"> </td><td align="left" nowrap="nowrap" id="TBL-7-10-2"
class="td11"> current heading/waypoint </td>
</tr><tr
valign="baseline" id="TBL-7-11-"><td align="left" nowrap="nowrap" id="TBL-7-11-1"
class="td11"> F11 </td><td align="left" nowrap="nowrap" id="TBL-7-11-2"
class="td11"> Autopilot altitude dialog </td>
</tr><tr
valign="baseline" id="TBL-7-12-"><td align="left" nowrap="nowrap" id="TBL-7-12-1"
class="td11"> F12 </td><td align="left" nowrap="nowrap" id="TBL-7-12-2"
class="td11"> Autopilot heading dialog </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-7-13-"><td align="left" nowrap="nowrap" id="TBL-7-13-1"
class="td11"> </td> </tr><!--|l|l|--></table> </div></div>
<!--l. 132--><p class="noindent">Ctrl + T is especially interesting as it makes your Cessna 172<a
name="dx1-45026"></a> behave like a cruise
missile. Ctrl + U might be handy in case you feel you&#8217;re just about to crash. (Shouldn&#8217;t
real planes sport such a key, too?)
<!--l. 136--><p class="indent"> In case the autopilot<a
name="dx1-45027"></a> is enabled, some of the numeric keypad keys get a special
meaning:
<!--l. 139--><p class="noindent">Tab. 5: <span
class="ptmri7t---109">Special action of keys, if autopilot is enabled.</span><a
name="dx1-45028"></a>
<!--l. 143--><p class="indent"> <div align="center"
class="centerline"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0" rules="groups"
frame="border" id="TBL-8-" ><colgroup id="TBL-8-1g"><col
id="TBL-8-1"></colgroup><colgroup id="TBL-8-2g"><col
id="TBL-8-2"></colgroup><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-8-1-"><td align="left" nowrap="nowrap" id="TBL-8-1-1"
class="td11"> Key </td><td align="left" nowrap="nowrap" id="TBL-8-1-2"
class="td11"> Action </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-8-2-"><td align="left" nowrap="nowrap" id="TBL-8-2-1"
class="td11"> 8 / 2</td><td align="left" nowrap="nowrap" id="TBL-8-2-2"
class="td11"> Altitude adjust </td>
</tr><tr
valign="baseline" id="TBL-8-3-"><td align="left" nowrap="nowrap" id="TBL-8-3-1"
class="td11"> 0 / , </td><td align="left" nowrap="nowrap" id="TBL-8-3-2"
class="td11"> Heading adjust </td>
</tr><tr
valign="baseline" id="TBL-8-4-"><td align="left" nowrap="nowrap" id="TBL-8-4-1"
class="td11"> 9 / 3</td><td align="left" nowrap="nowrap" id="TBL-8-4-2"
class="td11"> Auto Throttle adjust</td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-8-5-"><td align="left" nowrap="nowrap" id="TBL-8-5-1"
class="td11"> </td> </tr><!--|l|l|--></table> </div></div>
<!--l. 146--><p class="noindent">There are several keys for starting and controlling the engine <a
name="dx1-45029"></a>:
<!--l. 148--><p class="noindent">Tab. 6: <span
class="ptmri7t---109">Engine control keys</span>
<!--l. 152--><p class="indent"> <div align="center"
class="centerline"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0" rules="groups"
frame="border" id="TBL-9-" ><colgroup id="TBL-9-1g"><col
id="TBL-9-1"></colgroup><colgroup id="TBL-9-2g"><col
id="TBL-9-2"></colgroup><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-9-1-"><td align="left" nowrap="nowrap" id="TBL-9-1-1"
class="td11"> Key </td><td align="left" nowrap="nowrap" id="TBL-9-1-2"
class="td11"> Action </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-9-2-"><td align="left" nowrap="nowrap" id="TBL-9-2-1"
class="td11"> SPACE</td><td align="left" nowrap="nowrap" id="TBL-9-2-2"
class="td11"> Fire starter on selected engine(s) </td>
</tr><tr
valign="baseline" id="TBL-9-3-"><td align="left" nowrap="nowrap" id="TBL-9-3-1"
class="td11"> ! </td><td align="left" nowrap="nowrap" id="TBL-9-3-2"
class="td11"> Select 1st engine </td>
</tr><tr
valign="baseline" id="TBL-9-4-"><td align="left" nowrap="nowrap" id="TBL-9-4-1"
class="td11"> @ </td><td align="left" nowrap="nowrap" id="TBL-9-4-2"
class="td11"> Select 2nd engine </td>
</tr><tr
valign="baseline" id="TBL-9-5-"><td align="left" nowrap="nowrap" id="TBL-9-5-1"
class="td11"> # </td><td align="left" nowrap="nowrap" id="TBL-9-5-2"
class="td11"> Select 3rd engine </td>
</tr><tr
valign="baseline" id="TBL-9-6-"><td align="left" nowrap="nowrap" id="TBL-9-6-1"
class="td11"> $ </td><td align="left" nowrap="nowrap" id="TBL-9-6-2"
class="td11"> Select 4th engine </td>
</tr><tr
valign="baseline" id="TBL-9-7-"><td align="left" nowrap="nowrap" id="TBL-9-7-1"
class="td11"> <span
class="cmsy-10--109">{ </span></td><td align="left" nowrap="nowrap" id="TBL-9-7-2"
class="td11"> Decrease Magneto on Selected Engine</td>
</tr><tr
valign="baseline" id="TBL-9-8-"><td align="left" nowrap="nowrap" id="TBL-9-8-1"
class="td11"> <span
class="cmsy-10--109">} </span></td><td align="left" nowrap="nowrap" id="TBL-9-8-2"
class="td11"> Increase Magneto on Selected Engine </td>
</tr><tr
valign="baseline" id="TBL-9-9-"><td align="left" nowrap="nowrap" id="TBL-9-9-1"
class="td11"> <span
class="cmsy-10--109">~ </span></td><td align="left" nowrap="nowrap" id="TBL-9-9-2"
class="td11"> Select all Engines </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-9-10-"><td align="left" nowrap="nowrap" id="TBL-9-10-1"
class="td11"> </td> </tr><!--|l|l|--></table> </div></div>
<!--l. 155--><p class="noindent">Beside these basic keys there are miscelleneous keys for special actions; some of these
you&#8217;ll probably not want to try during your first flight:
<!--l. 157--><p class="noindent">Tab. 7: <span
class="ptmri7t---109">Miscellaneous keyboard controls.</span><a
name="dx1-45030"></a>
<!--l. 160--><p class="indent"> <div align="center"
class="centerline"><!--tex4ht:inline--><div class="tabular"><table class="tabular"
cellspacing="0pt" cellpadding="0" rules="groups"
frame="border" id="TBL-10-" ><colgroup id="TBL-10-1g"><col
id="TBL-10-1"></colgroup><colgroup id="TBL-10-2g"><col
id="TBL-10-2"></colgroup><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-10-1-"><td align="left" nowrap="nowrap" id="TBL-10-1-1"
class="td11"> Key </td><td align="left" nowrap="nowrap" id="TBL-10-1-2"
class="td11"> Action </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-10-2-"><td align="left" nowrap="nowrap" id="TBL-10-2-1"
class="td11"> B </td><td align="left" nowrap="nowrap" id="TBL-10-2-2"
class="td11"> Toggle parking brake <a
name="dx1-45031"></a><a
name="dx1-45032"></a> on/off </td>
</tr><tr
valign="baseline" id="TBL-10-3-"><td align="left" nowrap="nowrap" id="TBL-10-3-1"
class="td11"> b </td><td align="left" nowrap="nowrap" id="TBL-10-3-2"
class="td11"> Apply/release all brakes<a
name="dx1-45033"></a> </td>
</tr><tr
valign="baseline" id="TBL-10-4-"><td align="left" nowrap="nowrap" id="TBL-10-4-1"
class="td11"> g </td><td align="left" nowrap="nowrap" id="TBL-10-4-2"
class="td11"> Toggle landing gear down <a
name="dx1-45034"></a><a
name="dx1-45035"></a> </td>
</tr><tr
valign="baseline" id="TBL-10-5-"><td align="left" nowrap="nowrap" id="TBL-10-5-1"
class="td11"> , </td><td align="left" nowrap="nowrap" id="TBL-10-5-2"
class="td11"> Left gear brake (useful for differential braking<a
name="dx1-45036"></a>) </td>
</tr><tr
valign="baseline" id="TBL-10-6-"><td align="left" nowrap="nowrap" id="TBL-10-6-1"
class="td11"> . </td><td align="left" nowrap="nowrap" id="TBL-10-6-2"
class="td11"> Right gear brake (useful for differential braking<a
name="dx1-45037"></a>) </td>
</tr><tr
valign="baseline" id="TBL-10-7-"><td align="left" nowrap="nowrap" id="TBL-10-7-1"
class="td11"> <span
class="cmr-10--109">]</span>/<span
class="cmr-10--109">[ </span></td><td align="left" nowrap="nowrap" id="TBL-10-7-2"
class="td11"> Extend/Retract flaps<a
name="dx1-45038"></a> </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-10-8-"><td align="left" nowrap="nowrap" id="TBL-10-8-1"
class="td11"> p </td><td align="left" nowrap="nowrap" id="TBL-10-8-2"
class="td11"> Toggle pause<a
name="dx1-45039"></a> on/off </td>
</tr><tr
valign="baseline" id="TBL-10-9-"><td align="left" nowrap="nowrap" id="TBL-10-9-1"
class="td11"> a/A </td><td align="left" nowrap="nowrap" id="TBL-10-9-2"
class="td11"> Speed up/slow down (time acceleration) </td>
</tr><tr
valign="baseline" id="TBL-10-10-"><td align="left" nowrap="nowrap" id="TBL-10-10-1"
class="td11"> t/T </td><td align="left" nowrap="nowrap" id="TBL-10-10-2"
class="td11"> Time speed up/slow down </td>
</tr><tr
valign="baseline" id="TBL-10-11-"><td align="left" nowrap="nowrap" id="TBL-10-11-1"
class="td11"> m/M </td><td align="left" nowrap="nowrap" id="TBL-10-11-2"
class="td11"> Change time offset<a
name="dx1-45040"></a> (warp) used by t/T forward/backward</td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-10-12-"><td align="left" nowrap="nowrap" id="TBL-10-12-1"
class="td11"> Shift-F2 </td><td align="left" nowrap="nowrap" id="TBL-10-12-2"
class="td11"> Save current flight to <span
class="pcrr7t---109">fgfs.sav </span></td>
</tr><tr
valign="baseline" id="TBL-10-13-"><td align="left" nowrap="nowrap" id="TBL-10-13-1"
class="td11"> Shift-F1 </td><td align="left" nowrap="nowrap" id="TBL-10-13-2"
class="td11"> Restore flight from <span
class="pcrr7t---109">fgfs.sav </span></td>
</tr><tr
valign="baseline" id="TBL-10-14-"><td align="left" nowrap="nowrap" id="TBL-10-14-1"
class="td11"> F3 </td><td align="left" nowrap="nowrap" id="TBL-10-14-2"
class="td11"> Save screen shot under <span
class="pcrr7t---109">fgfs-screen.ppm </span></td>
</tr><tr
valign="baseline" id="TBL-10-15-"><td align="left" nowrap="nowrap" id="TBL-10-15-1"
class="td11"> Shift-F4 </td><td align="left" nowrap="nowrap" id="TBL-10-15-2"
class="td11"> Re-read global preferences from <span
class="pcrr7t---109">preferences.xml </span></td>
</tr><tr
valign="baseline" id="TBL-10-16-"><td align="left" nowrap="nowrap" id="TBL-10-16-1"
class="td11"> Shift-F10</td><td align="left" nowrap="nowrap" id="TBL-10-16-2"
class="td11"> Toggle data logging of FDM on/off </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-10-17-"><td align="left" nowrap="nowrap" id="TBL-10-17-1"
class="td11"> ESC </td><td align="left" nowrap="nowrap" id="TBL-10-17-2"
class="td11"> Exit program </td>
</tr><tr
class="hline"><td><hr></td><td><hr></td></tr><tr
valign="baseline" id="TBL-10-18-"><td align="left" nowrap="nowrap" id="TBL-10-18-1"
class="td11"> </td> </tr><!--|l|l|--></table> </div></div>
<!--l. 163--><p class="noindent">Note: If you have difficulty processing the screenshot<a
name="dx1-45041"></a> <span
class="pcrr7t---109">fgfs-screen.ppm </span>on a
windows machine, just recall that simply pressing the &#8221;Print&#8221; key copies the screen to the
clipboard, from which you can paste it into any graphics program.
<!--l. 168--><p class="indent"> Finally: Starting from <span
class="ptmbi7t---109">FlightGear </span>0.7.7 these key bindings<a
name="dx1-45042"></a> are no longer hard
coded, but user-adjustable. You can check and change these setting via the file
<span
class="pcrr7t---109">keyboard.xml</span><a
name="dx1-45043"></a> to be found in the main <span
class="ptmbi7t---109">FlightGear </span>directory. This is a human
readable plain ASCII file. Although it&#8217;s perhaps not the best idea for beginners to
start just with modifying this file, more advanced users will find it useful to
change key bindings according to what they like (or, perhaps, know from other
simulators).
<h3 class="sectionHead"><span class="titlemark">5.3</span> <a
name="x1-460005.3"></a>Menu entries</h3>
<a
name="dx1-46001"></a>
<!--l. 179--><p class="noindent">By default, the menu is disabled after starting the simulator (you don&#8217;t see a menu in a
real plane, do you?). You can turn it on either using the toggle F10 or just by moving
the mouse pointer to the top left corner of the display. In casse you want the
menu to disappear just hit F10 again or move the mouse to the bottom of the
screen.
<!--l. 181--><p class="indent"> At present, the menu provides the following functions.
<ul class="itemize1">
<li class="itemize"><span
class="ptmb7t---109">File</span>
<ul class="itemize2">
<li class="itemize"><span
class="ptmb7t---109">Save flight </span>Saves<a
name="dx1-46002"></a> the current flight, by default to <span
class="pcrr7t---109">fgfs.sav</span>.
</li>
<li class="itemize"><span
class="ptmb7t---109">Load flight </span>Loads<a
name="dx1-46003"></a> the current flight, by default from <span
class="pcrr7t---109">fgfs.sav</span>.
</li>
<li class="itemize"><span
class="ptmb7t---109">Reset </span>Resets<a
name="dx1-46004"></a> you to the selected starting position. Comes handy in case
you got lost or something went wrong.
</li>
<li class="itemize"><span
class="ptmb7t---109">Hires Snap Shot </span>Saves a high resolution Screen Shot<a
name="dx1-46005"></a> under
<br class="newline"><span
class="pcrr7t---109">fgfs-screen-XXX.ppm</span>.
</li>
<li class="itemize"><span
class="ptmb7t---109">Snap Shot </span>Saves a normal resolution Screen Shot<a
name="dx1-46006"></a> under
<br class="newline"><span
class="pcrr7t---109">fgfs-screen-XXX.ppm</span>.
</li>
<li class="itemize"><span
class="ptmb7t---109">Exit </span>Exits<a
name="dx1-46007"></a> the program.</li></ul>
</li>
<li class="itemize"><span
class="ptmb7t---109">View</span><a
name="dx1-46008"></a>
<ul class="itemize2">
<li class="itemize"><span
class="ptmb7t---109">Toggle Panel </span>Toggles instrument panel<a
name="dx1-46009"></a> on/off.
</li>
<li class="itemize"><span
class="ptmb7t---109">Pilot Offset </span>Allows setting a different viewpoint (useful for R/C
flying).
</li>
<li class="itemize"><span
class="ptmb7t---109">HUD Alpha </span>Toggles antialiasing<a
name="dx1-46010"></a> of HUD lines on/off.
</li>
<li class="itemize"><span
class="ptmb7t---109">Properties </span>Provies access to numerous properies managed via
<span
class="ptmbi7t---109">FlightGear</span>&#8217;s property manager. This is actually a quite powerful tool
allowing to set all the values in the property tree. Obviously, this is a
good place to crash the program by entering a &#8221;bad&#8221; value.</li></ul>
</li>
<li class="itemize"><span
class="ptmb7t---109">Environment</span>
<ul class="itemize2">
<li class="itemize"><span
class="ptmb7t---109">Goto Airport </span>Enter the airport ID<a
name="dx1-46011"></a>. For details on how to get the IDs
see Section <a
href="#x1-340004.4.5">4.4.5<!--tex4ht:ref: aiportid--></a>.</li></ul>
</li>
<li class="itemize"><span
class="ptmb7t---109">Autopilot</span><a
name="dx1-46012"></a>
<ul class="itemize2">
<li class="itemize"><span
class="ptmb7t---109">Set Heading </span>Sets heading manually.
</li>
<li class="itemize"><span
class="ptmb7t---109">Set Altitude </span>Sets altitude manually.
</li>
<li class="itemize"><span
class="ptmb7t---109">Add Waypoint </span>Adds Waypoint to waypoint list.
</li>
<li class="itemize"><span
class="ptmb7t---109">Skip Current Waypoint </span>Self explaining.
</li>
<li class="itemize"><span
class="ptmb7t---109">Clear Route </span>Clears current route.
</li>
<li class="itemize"><span
class="ptmb7t---109">Adjust AP Settings </span>Allows input of several Autopilot parameters.
</li>
<li class="itemize"><span
class="ptmb7t---109">Toggle HUD format </span>Toggles figures of latitude/longitude in HUD.</li></ul>
</li>
<li class="itemize"><span
class="ptmb7t---109">Network</span><a
name="dx1-46013"></a> (supposes compile option <span
class="pcrr7t---109">--with-network-olk</span>)
<ul class="itemize2">
<li class="itemize"><span
class="ptmb7t---109">Toggle Display </span>Toggle call sign etc. on/off.
</li>
<li class="itemize"><span
class="ptmb7t---109">Enter Callsign </span>Enter your call sign.
</li>
<li class="itemize"><span
class="ptmb7t---109">Scan for Daemons </span>Scan for daemons on the net.
</li>
<li class="itemize"><span
class="ptmb7t---109">Register for FGD </span>Register for <span
class="ptmbi7t---109">FlightGear </span>Daemon.
</li>
<li class="itemize"><span
class="ptmb7t---109">Unregister for FGD </span>Unregister from <span
class="ptmbi7t---109">FlightGear </span>Daemon.</li></ul>
</li>
<li class="itemize"><span
class="ptmb7t---109">Help</span><a
name="dx1-46014"></a>
<ul class="itemize2">
<li class="itemize"><span
class="ptmb7t---109">Help </span>Should bring up this FlightGear Getting Started Guide<a
name="dx1-46015"></a>. At present
not yet fully implemented. Under windows this works via a batch file
<span
class="pcrr7t---109">webrun.bat </span>under <span
class="pcrr7t---109">/flightgear</span>. If you intend to use that feature
you may have to edit <span
class="pcrr7t---109">webrun.bat</span>. Under UNIX a comparable shell
script might do.</li></ul>
</li></ul>
<h3 class="sectionHead"><span class="titlemark">5.4</span> <a
name="x1-470005.4"></a>The Instrument Panel</h3>
<!--l. 244--><p class="noindent">The Cessna instrument panel is activated by default when you start <span
class="ptmbi7t---109">FlightGear</span>, but can
be de-activated by pressing the &#8221;P&#8221; key. While a complete description of all the functions
of the instrument panel of a Cessna is beyond the scope of this guide, we will at least try
to outline the main flight instrument<a
name="dx1-47001"></a>s or gauge<a
name="dx1-47002"></a>s.
<!--l. 249--><p class="indent"> All panel levers and knobs can be operated with the mouse To change a control,
just click with the left/middle mouse button on the corresponding knob/lever.
<!--l. 254--><p class="indent"> <div align="center"
class="centerline"><img
src="getstart6x.gif" alt="" class="fbox" > </div>
<!--l. 257--><p class="noindent">Fig. 5: <span
class="ptmri7t---109">The panel.</span>
<!--l. 261--><p class="indent"> Let us start with the most important instruments any simulator pilot must know. In
the center of the instrument panel (Fig. 5), in the upper row, you will find the artificial
horizon<a
name="dx1-47003"></a> (attitude indicator<a
name="dx1-47004"></a>) displaying pitch<a
name="dx1-47005"></a> and bank<a
name="dx1-47006"></a> of your plane. It has pitch marks as
well as bank marks at 10, 20, 30, 60, and 90 degrees.
<!--l. 267--><p class="indent"> Left to the artificial horizon, you&#8217;ll see the airspeed indicator<a
name="dx1-47007"></a>. Not only does it
provide a speed indication in knots but also several arcs showing characteristic velocity
rages<a
name="dx1-47008"></a> you have to consider. At first, there is a green arc indicating the normal
operating range of speed with the flaps fully retracted. The white arc indicates
the range of speed with flaps in action. The yellow arc shows a range, which
should only be used in smooth air. The upper end of it has a red radial indicating
the speed you must never exceeded - at least as long as you wan&#8217;t brake your
plane.
<!--l. 275--><p class="indent"> Below the airspeed indicator you can find the turn indicator<a
name="dx1-47009"></a>. The airplane in the
middle indicates the roll of your plane. If the left or right wing of the plane is aligned
with one of the marks, this would indicate a standard turn, i.e. a turn of 360 degrees in
exactly two minutes.
<!--l. 280--><p class="indent"> Below the plane, still in the turn indicator, is the inclinometer<a
name="dx1-47010"></a>. It indicates if rudder<a
name="dx1-47011"></a>
and aileron<a
name="dx1-47012"></a>s are coordinated. During turns, you always have to operate aileron<a
name="dx1-47013"></a> and rudder<a
name="dx1-47014"></a>
in such a way that the ball in the tube remains centered; otherwise the plane is skidding.
A simple rule says: &#8221;Step onto the ball&#8221;, i.e. step onto the left rudder pedal in case the
ball is on the l.h.s.
<!--l. 285--><p class="indent"> If you don&#8217;t have pedals or lack the experience to handle the proper ratio
between aileron/rudder automatically, you can start <span
class="ptmbi7t---109">FlightGear </span>with the option
<span
class="pcrr7t---109">--enable-auto-coordination</span>.<a
name="dx1-47015"></a>
<!--l. 289--><p class="indent"> To the r.h.s of the artificial horizon you will find the altimeter<a
name="dx1-47016"></a> showing the height
above sea level (not ground!) in hundreds of feet. Below the altimeter is the
vertical speed indicator<a
name="dx1-47017"></a> indicating the rate of climbing or sinking of your plane in
hundreds of feet per minute. While you may find it more convenient to use then
the altimeter in cases, keep in mind that its diplay usually has a certain lag in
time.
<!--l. 295--><p class="indent"> Further below the vertical speed indicator is the RPM (rotations per minute)
indicator<a
name="dx1-47018"></a>, which displays the rotations per minute in 100 RPMs. The green arc marks the
optimum region for long-time flight.
<!--l. 299--><p class="indent"> The group of the main instruments further includes the gyro compass<a
name="dx1-47019"></a> being situated
below the artificial horizon. Besides this one, there is a magnetic compass<a
name="dx1-47020"></a> sitting on top
of the panel.
<!--l. 303--><p class="indent"> Four of these gauges being arranged in the from of a &#8221;T&#8221; are of special importance:
The air speed indicator, the artificial horizon, the altimeter, and the compass should be
scanned regularly during flight.
<!--l. 307--><p class="indent"> Besides these, there are several supplementary instruments. To the very left you will
find the clock<a
name="dx1-47021"></a>, obviously being an important tool for instance for determining turn
rates.Below the clock there are several smaller gauges displaying the technical state of
your engine. Certainly the most important of them is the fuel indicator<a
name="dx1-47022"></a> - as any pilot
should know.
<!--l. 310--><p class="indent"> The ignition switch is situated in the lower left corner of the panel (cf. Fig. 4). It has
five positions: &#8221;OFF&#8221;, &#8221;L&#8221;, &#8221;R&#8221;, &#8221;BOTH&#8221;, and &#8221;START&#8221;. The first one is obvious. &#8221;L&#8221;
and &#8221;R&#8221; do not refer to two engines (actually the Cessna does only have one) but
to two magnetos being present for safety purposes. The two switch positions
can be used for test puposes during preflight. During normal flight the switch
should point on &#8221;BOTH&#8221;. The extreme right position is for starting the engine
using a battery-powered starter (to be operated with the SPACE key in flight
gear).
<!--l. 312--><p class="indent"> Like in most flight simulators, you actually get a bit more than in a real plane. The
red field directly below the gyro compass displays the state of the brakes, i.e., it is lit in
case of the brakes being engaged. The instruments below indicate the position of
youryoke<a
name="dx1-47023"></a>. This serves as kind of a compensation for the missing forces you feel while
pushing a real yoke. Three of the arrows correspond to the three axes of your yoke/pedal
controlling nose up/down, bank left/right, rudder left/right, and throttle. (Keep in mind:
They do <span
class="ptmb7t---109">not </span>reflect the actual position of the plane!) The left vertical arrow indicates
elevator trim.
<!--l. 314--><p class="indent"> The right hand side of the panel is occupied by the radio stack<a
name="dx1-47024"></a>. Here you find two
VOR<a
name="dx1-47025"></a> receivers (NAV),<a
name="dx1-47026"></a> an NDB<a
name="dx1-47027"></a> receiver (ADF<a
name="dx1-47028"></a>) and two communication radio<a
name="dx1-47029"></a>s
(COMM1/2)<a
name="dx1-47030"></a><a
name="dx1-47031"></a> as well as the autopilot.
<!--l. 319--><p class="indent"> The communication radio<a
name="dx1-47032"></a> is used for communication with air traffic facilities<a
name="dx1-47033"></a>; it is
just a usual radio transceiver working in a special frequency range. The frequency is
displayed in the &#8221;COMM&#8221; field. Usually there are two COM transceivers; this way you
can dial in the frequency of the next controller to contact while still being in contact with
the previous one.
<!--l. 325--><p class="indent"> The COM radio can be used to display STIS messages as well. For this purpose, just
to dial in the ATIS frequency of the relevant airport.
<!--l. 327--><p class="indent"> The VOR<a
name="dx1-47034"></a> (Very High Frequency Omni-Directional Range) receiver is used for course
guidance during flight. The frequency of the sender is displayed in the &#8221;NAV&#8221; field. In a
sense, a VOR acts similarly to a light house permitting to display the position of the
aircraft on a radial around the sender. It transmits one omni-directional ray of radio
waves plus a second ray, the phase of which differs from the first one depending on its
direction (which may be envisaged as kind of a &#8221;rotating&#8221; signal). The phase difference
between the two signals allows evaluating the angle of the aircraft on a 360
degrees circle around the VOR sender, the so-called radial. This radial is then
displayed on the gauges NAV1 and NAV2, resp., left to frequency field. This way it
should be clear that the VOR dispaly, while indicating the position of the aircraft
relative to the VOR sender, does not say anything about the orientation of the
plane.
<!--l. 336--><p class="indent"> Below the two COM/NAV devices is an NDB<a
name="dx1-47035"></a> receiver called ADF (automatic
direction finder). Again there is a field displaying the frequency of the facility. The ADF
can be used for navigation, too, but contrary to the VOR does not show the
position of the plane in a radial relative to the sender but the direct heading from
the aircraft to the sender. This is displayed on the gauge below the two NAV
gauges.
<!--l. 342--><p class="indent"> Above the COMM1 display you will see three LEDs in the colors blue, amber, and
white indicating the outer, middle, and, inner, resp. marker beakon.<a
name="dx1-47036"></a><a
name="dx1-47037"></a><a
name="dx1-47038"></a> These show the
distance to the runway threshold during landing. They to not require the input of a
frequency.
<!--l. 347--><p class="indent"> Below the radios you will find the autopilot. It has five keys for WL = &#8221;Wing-Leveler&#8221;,
&#8221;HDG&#8221; = &#8221;Heading&#8221;, NAV, APR = &#8221;Glide-Slope&#8221;, and ALT = &#8221;Altitude&#8221;. These keys
when engaged hold the corresponding property.
<!--l. 349--><p class="indent"> A detailed description of the workings of these instruments and their use for
navigation lies beyond this Guide; if you are interested in this exciting topic, we suggest
consulting a book on instrument flight (simulation). Besides, this would be material for a
yet to be written <span
class="ptmbi7t---109">FlightGear </span>Flight School.
<!--l. 354--><p class="indent"> It should be noted, that you can neglect these radio instruments as long as you are
strictly flying according to VFR<a
name="dx1-47039"></a> (visual flight rules<a
name="dx1-47040"></a>). For those wanting to do IFR<a
name="dx1-47041"></a>
(instrument flight rules<a
name="dx1-47042"></a>) flights, it should be mentioned that <span
class="ptmbi7t---109">FlightGear </span>includes a huge
database of navaids<a
name="dx1-47043"></a> worldwide.
<!--l. 356--><p class="indent"> Finally, you find the throttle<a
name="dx1-47044"></a>, mixture<a
name="dx1-47045"></a>, and flap control<a
name="dx1-47046"></a> in the lower right of the panel
(recall, flaps can be set via <span
class="cmr-10--109">[ </span>and <span
class="cmr-10--109">] </span>or just using the mouse).
<!--l. 359--><p class="indent"> As with the keyboard, the panel<a
name="dx1-47047"></a> can be re-configured using configuration files. As
these have to be plane specific, they can be found under the directory of the
corresponding plane. As an example, the configuration file for the default Cessna C172
can be found at <span
class="pcrr7t---109">FlightGear/Aircraft/c172/Panels </span>as c172-panel.xml. The
accompanying documentation for customizing it (i.e. shifting, replacing etc. gauges and
more) is contained in the file <span
class="pcrr7t---109">README.xmlpanel</span><a
name="dx1-47048"></a> written by John Check<a
name="dx1-47049"></a>, to be found
in the source code in the directory <span
class="pcrr7t---109">docs-mini</span>.
<!--l. 371--><p class="indent"> <div align="center"
class="centerline"><img
src="getstart7x.gif" alt="" class="fbox" > </div>
<!--l. 374--><p class="noindent">Fig. 6: <span
class="ptmri7t---109">The HUD, or Head Up Display.</span>
<h3 class="sectionHead"><span class="titlemark">5.5</span> <a
name="x1-480005.5"></a>The Head Up Display</h3>
<!--l. 382--><p class="noindent">At current, there are two options for reading off the main flight parameters of the plane:
One is the instrument panel already mentioned, while the other one is the HUD<a
name="dx1-48001"></a> (<span
class="ptmb7t---109">H</span>ead
<span
class="ptmb7t---109">U</span>p <span
class="ptmb7t---109">D</span>isplay) <a
name="dx1-48002"></a>. Neither are HUD<a
name="dx1-48003"></a>s used in usual general aviation planes nor in civilian
ones. Rather they belong to the equipment of modern military jets. However, some might
find it easier to fly using the HUD even with general aviation aircraft. Several Cessna<a
name="dx1-48004"></a>
pilots might actually love to have one, but technology is simply too expensive for
implementing HUDs in general aviation aircraft. Besides, the HUD displays several
useful figures characterizing simulator performance, not to be read off from the
panel.
<!--l. 392--><p class="indent"> The HUD<a
name="dx1-48005"></a> shown in Fig. 6 displays all main flight parameters of the plane. In
the center you find the pitch indicator<a
name="dx1-48006"></a> (in degrees) with the aileron indicator<a
name="dx1-48007"></a>
above and the rudder indicator<a
name="dx1-48008"></a> below. A corresponding scale for the elevation<a
name="dx1-48009"></a>
can be found to the left of the pitch scale. On the bottom there is a simple turn
indicator<a
name="dx1-48010"></a>.
<!--l. 398--><p class="indent"> There are two scales at the extreme left: The inner one displays the speed<a
name="dx1-48011"></a> (in kts)
while the outer one indicates position of the throttle<a
name="dx1-48012"></a>. The Cessna 172 takes off at around
55 kts. The two scales on the extreme r.h.s display your height<a
name="dx1-48013"></a>, i. e. the left one shows the
height above ground while the right of it gives that above zero, both being displayed in
feet.
<!--l. 404--><p class="indent"> Besides this, the HUD<a
name="dx1-48014"></a> delivers some additions information. On the upper left you
will find date and time. Besides, latitude<a
name="dx1-48015"></a> and longitude<a
name="dx1-48016"></a>, resp., of your current position are
shown on top.
<!--l. 407--><p class="indent"> You can change color of the <span
class="ptmb7t---109">HUD </span>using the &#8221;H&#8221; or &#8221;h&#8221; key. Pressing ethe toggle
&#8221;i/I&#8221; minimizes/maximizes the HUD.
<h3 class="sectionHead"><span class="titlemark">5.6</span> <a
name="x1-490005.6"></a>Mouse controlled actions</h3>
<!--l. 413--><p class="noindent">Besides just clicking the menues, your mouse has got certain valuable functions in
<span
class="ptmbi7t---109">FlightGear</span>.
<!--l. 416--><p class="indent"> There are three mouse modi. In the normal mode (pointer curser) panel&#8217;s controls can
be operated with the mouse. To change a control, click with the left/middle mouse button
on the corresponding knob/lever. While the left mouse button leads to small
increments/decrements, the middle one makes greater ones. Clicking on the left hand
side of the knob/lever decreases the value, while clicking on the right hand side increases
it.
<!--l. 419--><p class="indent"> Right clicking the mouse activates the simulator control mode (cross hair cursor).
This allows control of aileron/elevator via the mouse in absence of a joystick/yoke
(enable <span
class="pcrr7t---109">--enable-auto-coordination </span>in this case). If you have a joystick you
certainly will not make use of this mode
<!--l. 421--><p class="indent"> Right clicking the mouse another time activates the view control mode (arrow
cursor). This allows changing direction of view, i.e. pan and tilt the view, via the
mouse.
<!--l. 424--><p class="indent"> Right clicking the mouse once more resets it into the initial state.
<!--l. 426--><p class="indent"> If you are looking for some interesting places to discover<a
name="dx1-49001"></a> with <span
class="ptmbi7t---109">FlightGear </span>(which
may or may not require downloading additional scenery) you may want to check
<!--l. 430--><p class="indent"> <a
href="http://www.flightgear.org/Places/" >http://www.flightgear.org/Places/</a>.
<!--l. 433--><p class="noindent">There is now a menu entry for entering directly the airport code<a
name="dx1-49002"></a> of the airport you want to
start from.
<!--l. 437--><p class="indent"> Finally, if you&#8217;re done and are about to leave the plane, just hit the ESC key or use
the corresponding menu entry to exit<a
name="dx1-49003"></a> the program. It is not suggested to simply &#8221;kill&#8221; the
simulator by clicking the text window.
<h3 class="sectionHead"><span class="titlemark">5.7</span> <a
name="x1-500005.7"></a>Some further reading for pilot students</h3>
<!--l. 445--><p class="noindent">In view of that fact, that there is not yet a <span
class="ptmbi7t---109">FlightGear </span>specific flight course, here are
some useful hints to texts for those who want to learn piloting a plane.
<!--l. 448--><p class="indent"> First, a quite comprehensive manual is the Aeronautical Information Manual<a
name="dx1-50001"></a>,
published by the FAA<a
name="dx1-50002"></a>, and being online available at
<!--l. 452--><p class="indent"> <a
href="http://www.faa.gov/ATPubs/AIM/" >http://www.faa.gov/ATPubs/AIM/</a>.
<!--l. 455--><p class="noindent">This is the Official Guide to Basic Flight Information and ATC Procedures by the FAA. It
contains a lot of information on flight rules, flight safety, navigation, and more. If
you find this a bit too hard reading, you may prefer the FAA Training Book<a
name="dx1-50003"></a>,
<!--l. 461--><p class="indent"> <a
href="http://avstop.com/AC/FlightTraingHandbook/" >http://avstop.com/AC/FlightTraingHandbook/</a>,
<!--l. 464--><p class="noindent">which covers all aspects of flight, beginning with the theory of flight and the
working of airplanes, via procedures like takeoff and landing up to emergency
situations. This is an ideal reading for those who want to learn some basics
on flight but don&#8217;t (yet) want to spend bucks on getting a costly paper pilot&#8217;s
handbook.
<!--l. 470--><p class="indent"> While the handbook mentioned above is an excellent introduction on VFR<a
name="dx1-50004"></a> (visual
fligtht rules), it does not include flying according to IFR<a
name="dx1-50005"></a> (instrument flight rules).
However, an excellent introduction into navigation and flight according to Instrument
Flight Rules written by Charles Wood<a
name="dx1-50006"></a> can be found at
<!--l. 475--><p class="indent"> <a
href="http://www.navfltsm.addr.com/" >http://www.navfltsm.addr.com/</a>.
<!--l. 477--><p class="indent"> Another comprehensive but yet readable text is John Denker&#8217;s<a
name="dx1-50007"></a> &#8221;See how it flies<a
name="dx1-50008"></a>&#8221;,
available at
<!--l. 481--><p class="indent"> <a
href="http://www.monmouth.com/~jsd/how/htm/title.html" >http://www.monmouth.com/&nbsp;jsd/how/htm/title.html</a>.
<!--l. 484--><p class="noindent">This is a real online text book, beginning with Bernoulli&#8217;s principle, drag and power, and
the like, with the later chapters covering even advanced aspects of VFR as well as IFR
flying
<h1 class="partHead"><span class="titlemark">Part&nbsp;III<br></span><a
name="x1-51000III"></a>Appendices</h1>
<a
name="x1-51001r43"></a>
<h2 class="appendixHead"><span class="titlemark">Appendix&nbsp;A</span><br><a
name="x1-52000A"></a>Landing: Some further thoughts before leaving the plane</h2>
<h3 class="sectionHead"><span class="titlemark">A.1</span> <a
name="x1-53000A.1"></a>A not so Short History of <span
class="ptmbi7t---109">FlightGear</span></h3>
<!--l. 37--><p class="noindent">Alls this project goes back to a discussion among a group of net citizens in 1996
resulting in a proposal written by David Murr<a
name="dx1-53001"></a> who, unfortunately, dropped out of the
project (as well as the net) later. The original proposal<a
name="dx1-53002"></a> is still available from the
<span
class="ptmbi7t---109">FlightGear </span>web site and can be found under
<!--l. 43--><p class="indent"> <a
href="http://www.flightgear.org/proposal-3.0.1" >http://www.flightgear.org/proposal-3.0.1</a>.
<!--l. 46--><p class="noindent">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.
<!--l. 50--><p class="indent"> 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<a
name="dx1-53003"></a> from Berkeley University. Early code ran
under Linux<a
name="dx1-53004"></a> as well as under DOS<a
name="dx1-53005"></a>, OS/2<a
name="dx1-53006"></a>, Windows 95/NT<a
name="dx1-53007"></a>, and Sun-OS<a
name="dx1-53008"></a>. This
was found to be quite an ambitious project as it involved, among other things,
writing all the graphics routines<a
name="dx1-53009"></a> in a system-independent way entirely from
scratch.
<!--l. 58--><p class="indent"> 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.
<!--l. 62--><p class="indent"> It was Curt Olson<a
name="dx1-53010"></a> 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<a
name="dx1-53011"></a> available
running on workstation<a
name="dx1-53012"></a>s under different flavors of UNIX<a
name="dx1-53013"></a>. One of these, LaRCsim<a
name="dx1-53014"></a>
(developed by Bruce Jackson<a
name="dx1-53015"></a> 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 exploite a system-independent graphics platform: OpenGL<a
name="dx1-53016"></a>.
<!--l. 75--><p class="indent"> <div align="center"
class="centerline"><img
src="getstart8x.gif" alt="" class="fbox" > </div>
<!--l. 78--><p class="noindent">Fig. 7: <span
class="ptmri7t---109">LaRCsim</span><a
name="dx1-53017"></a><span
class="ptmri7t---109">&#8217;s Navion</span><a
name="dx1-53018"></a> <span
class="ptmri7t---109">is still available in </span><span
class="ptmbi7t---109">FlightGear</span><span
class="ptmri7t---109">.</span>
<!--l. 82--><p class="indent"> In addition, a clever decision on the selection of the basic scenery<a
name="dx1-53019"></a> data was made
in the very first version. <span
class="ptmbi7t---109">FlightGear </span>scenery is created based on satellite data
published by the U. S. Geological Survey<a
name="dx1-53020"></a>. These terrain data are available from
<!--l. 87--><p class="indent"> <a
href="http://edcwww.cr.usgs.gov/doc/edchome/ndcdb/ndcdb.html" >http://edcwww.cr.usgs.gov/doc/edchome/ndcdb/ndcdb.html</a>
<!--l. 90--><p class="noindent">for the U.S., and
<!--l. 94--><p class="indent"> <a
href="http://edcwww.cr.usgs.gov/landdaac/gtopo30/gtopo30.html" >http://edcwww.cr.usgs.gov/landdaac/gtopo30/gtopo30.html</a>,
<!--l. 97--><p class="noindent">resp., for other countries. Those freely accessible scenery data, in conjunction with
scenery building tools included with <span
class="ptmbi7t---109">FlightGear</span>, are an important feature enabling
anyone to create his or her own scenery.
<!--l. 103--><p class="indent"> This new <span
class="ptmbi7t---109">FlightGear </span>code - still largely being based on the original LaRCsim<a
name="dx1-53021"></a> code -
was released in July 1997. From that moment the project gained momentum again. Here
are some milestones in the more recent development history:
<ul class="itemize1">
<li class="itemize">The display of sun, moon and stars have been a weak point for PC flight
simulators for a long time. It is one of the great achievements of <span
class="ptmbi7t---109">FlightGear</span>
to include accurate modeling and display of sun, moon, and planets very
early. The corresponding astronomy code<a
name="dx1-53022"></a> was implemented in fall 1997 by
Durk Talsma<a
name="dx1-53023"></a>.
</li>
<li class="itemize">Texture support<a
name="dx1-53024"></a> was added by Curt Olson<a
name="dx1-53025"></a> in spring 1998. This marked a
significant improvement in terms of reality. You may recall that Microsoft
Flight Simulator had non-textured scenery up until version 4.0. Some
high-quality textures were submitted by Eric Mitchell<a
name="dx1-53026"></a> for the <span
class="ptmbi7t---109">FlightGear</span>
project.
</li>
<li class="itemize">A HUD<a
name="dx1-53027"></a> (head up display<a
name="dx1-53028"></a>) was added based on code provided by Michele
America<a
name="dx1-53029"></a> and Charlie Hotchkiss<a
name="dx1-53030"></a> in the fall of 1997 and was improved later by
Norman Vine. While not generally available for real Cessna 172<a
name="dx1-53031"></a>, the HUD
conveniently reports the actual flight performance of the simulation and may
be of further use in military jets later.
</li>
<li class="itemize">After improving the scenery<a
name="dx1-53032"></a> and texture<a
name="dx1-53033"></a> support frame rate<a
name="dx1-53034"></a> dropped down to
a point where <span
class="ptmbi7t---109">FlightGear </span>became unflyable in spring 1998. This issue was
resolved by exploiting hardware OpenGL<a
name="dx1-53035"></a> support, which became available
at that time, and implementing view frustrum culling<a
name="dx1-53036"></a> (a rendering technique
that ignores the part of the scenery not visible in a scene), done by Curt
Olson<a
name="dx1-53037"></a>. Taking these measures made <span
class="ptmbi7t---109">FlightGear </span>flyable again as long as they
included a 3-D graphics board that featured hardware OpenGL<a
name="dx1-53038"></a> support. With
respect to frame rate<a
name="dx1-53039"></a> one should keep in mind that the code, at present, is in
no way optimized, which leaves room for further improvements.
</li>
<li class="itemize">A rudimentary autopilot<a
name="dx1-53040"></a> implementing heading hold was contributed by Jeff
Goeke-Smith<a
name="dx1-53041"></a> in April 1998. It was improved by the addition of an altitude
hold and a terrain following switch in October 1998 and further developed
by Norman Vine<a
name="dx1-53042"></a> later.
</li>
<li class="itemize">The basis for a menu system<a
name="dx1-53043"></a> was laid based on another library, the Portable
Library <span
class="ptmbi7t---109">PLIB</span><a
name="dx1-53044"></a>, in June 1998. After having been idle for a time, the first
working menu entries came to life in spring 1999.
<!--l. 149--><p class="noindent"><span
class="ptmbi7t---109">PLIB </span>underwent rapid development later. It has been distributed as a
separate package by Steve Baker with a much broader range of applications
in mind, since spring 1999. It has provided the basic graphics rendering
engine for <span
class="ptmbi7t---109">FlightGear </span>since fall 1999.
</li>
<li class="itemize">Friedemann Reinhard <a
name="dx1-53045"></a>developed early instrument panel<a
name="dx1-53046"></a> code, which was
added in June 1998. Unfortunately, development of that panel slowed down
later, partly because of OpenGL<a
name="dx1-53047"></a> compatibility problems. Finally, David
Megginson <a
name="dx1-53048"></a>decided to rebuild the panel code from scratch in January 2000.
This led to a rapid addition of new instruments and features to the panel,
resulting in nearly all main instruments being included until spring 2001. A
handy minipanel was added in summer 2001.
</li>
<li class="itemize">A fully operational radio stack and working radios were added to the panel
by Curt Olson<a
name="dx1-53049"></a> in spring 2000. A huge database of Navaids contributed by
Robin Peel allows IFR navigation since then.
</li>
<li class="itemize">In 1998 there was basic audio support<a
name="dx1-53050"></a>, i. e. an audio library and
some basic background engine sound. This was later integrated into the
above-mentioned portable library, <span
class="ptmbi7t---109">PLIB</span><a
name="dx1-53051"></a>. This same library was extended to
support joystick/yoke/rudder<a
name="dx1-53052"></a> in October 1999, again marking a huge step in
terms of realism. To adapt on different joystick, configuration options were
introduced in fall 2000.
</li>
<li class="itemize">In September 1998 Curt Olson<a
name="dx1-53053"></a> succeeded in creating a complete terrain
model for the U.S. The scenery is available worldwide via a clickable map
<a
name="dx1-53054"></a>at:
<!--l. 176--><p class="noindent"><a
href="http://www.flightgear.org/Downloads/world-scenery.html" >http://www.flightgear.org/Downloads/world-scenery.html</a>.
</li>
<li class="itemize">Networking/multiplayer<a
name="dx1-53055"></a><a
name="dx1-53056"></a> code has been integrated by Oliver Delise <a
name="dx1-53057"></a>and Curt
Olson<a
name="dx1-53058"></a> starting fall 1999. This effort is aimed at enabling <span
class="ptmbi7t---109">FlightGear </span>to run
concurrently on several machines over a network, either an Intranet or the
Internet<a
name="dx1-53059"></a>, coupling it to a flight planner<a
name="dx1-53060"></a> running on a second machine, and
more. There emerged several approaches for remotely controlling FlightGear
over a Network during 2001. Notably there was added support working
together wirth the &#8221;Atlas&#8221; moving map program. Besides, an embedded
HTTP server developed late in 2001 by Curt Olson<a
name="dx1-53061"></a> can now act a property
manager for external programs.
</li>
<li class="itemize">Christian Mayer, <a
name="dx1-53062"></a>together with Durk Talsma,<a
name="dx1-53063"></a> contributed weather code in the
winter of 1999. This included clouds<a
name="dx1-53064"></a>, winds<a
name="dx1-53065"></a>, and even thunderstorms<a
name="dx1-53066"></a>.
</li>
<li class="itemize">Manually changing views<a
name="dx1-53067"></a> in a flight simulator is in a sense always &#8221;unreal&#8221;
but nonetheless required in certain situations. A possible solution was
supplied by Norman Vine<a
name="dx1-53068"></a> in the winter of 1999 by implementing code for
changing views using the mouse. Alternatively, you can use a hat switch for
this purpose, today.
</li>
<li class="itemize">Finally, LaRCsim<a
name="dx1-53069"></a>s Navion<a
name="dx1-53070"></a> was replaced as the default aircraft when the
Cessna 172<a
name="dx1-53071"></a> was stable enough in February 2000 - a move most users will
welcome. There are now several flight model<a
name="dx1-53072"></a> options to choose from at
runtime: a modified and improved LaRCsim Cessna 172<a
name="dx1-53073"></a> developed by Tony
Peden<a
name="dx1-53074"></a>, Jon Berndt&#8217;s <a
name="dx1-53075"></a>X15<a
name="dx1-53076"></a>, and Christian Mayer&#8217;s <a
name="dx1-53077"></a>hot air balloon. Jon Berndt<a
name="dx1-53078"></a>
has invested a lot of time in a more realistic and versatile flight model with
a more powerful aircraft configuration method. <span
class="ptmbi7t---109">JSBSim</span>, as it has come to
be called, may eventually replace LaRCsim as the default flight dynamics
model (FDM), and it is planned to include such features as fuel slosh effects,
turbulence, complete flight control systems, and other features not often
found all together in a flight simulator. As an alternative, Andy Ross<a
name="dx1-53079"></a> added
another flight dynamics model called <span
class="ptmbi7t---109">YASim </span>(Yet Another Flight Dynamics
Simulator) which aims at simpliciy of use, by the end of 2001. This one
bought us flight modles for a 747, an A4, and a DC-3.
</li>
<li class="itemize">The scenery was further improved by adding geographic features including
lakes, rivers, and coastlines later, an effort still going on. Since the end of
2000, there was again stronger focus on scenery. Textured runways were
added by Dave Cornish<a
name="dx1-53080"></a> in spring 2001. Light textures add to the visual
impression at night. To cope with the constant growth of scenery data, a
binary scenery format was introduced in spring 2001.
</li>
<li class="itemize">A property manager<a
name="dx1-53081"></a> was implemented by David Megginson<a
name="dx1-53082"></a> in fall
2000. It allows parsing a file called <span
class="pcrr7t---109">.fgfsrc</span><a
name="dx1-53083"></a> under UNIX/Linux and
<span
class="pcrr7t---109">system.fgfsrc</span><a
name="dx1-53084"></a> under Windows for input options. This plain ASCII file
has proven useful in submitting the growing number of input options, and
notably the joystick settings<a
name="dx1-53085"></a>. This has proven a useful concept, and joystick,
keyboard, and panel settings are no longer hard coded but set using *.xml
files since spring 2001 thanks to work mainly by David Megginson and John
Check.<a
name="dx1-53086"></a>
</li>
<li class="itemize">There was support added for static objects to the scenery in 2001, which
permits placing buildung, static planes, trees and so on in the scenery.
However, despite a few profs systematic includion of these landmarks is still
missing.
</li>
<li class="itemize">There was basic ATC support added in fall 2001 by David Luff<a
name="dx1-53087"></a>. This is not
yet fully implemented, but displaying ATIS messages is already possible.
</li>
<li class="itemize">A magneto switch with proper functions was added at the end of 2001 by
John Check<a
name="dx1-53088"></a> and David Megginson.<a
name="dx1-53089"></a>. Actually, several panels were vastly
improved during 2001 by John and others.</li></ul>
<!--l. 228--><p class="noindent">During development there were several code reorganization efforts. Various code
subsystems were moved into packages. As a result, presetnly code is organized as
follows:
<!--l. 232--><p class="indent"> The base of the graphics engine is <span
class="ptmb7t---109">OpenGL</span><a
name="dx1-53090"></a>, a platform independent graphics library.
Based on OpenGL<a
name="dx1-53091"></a>, the Portable Library <span
class="ptmbi7t---109">PLIB</span><a
name="dx1-53092"></a> provides basic rendering, audio, joystick
etc. routines. Based on <span
class="ptmbi7t---109">PLIB</span><a
name="dx1-53093"></a> is <span
class="ptmbi7t---109">SimGear</span><a
name="dx1-53094"></a>, which includes all of the basic routines
required for the flight simulator as well as for building scenery. On top of <span
class="ptmbi7t---109">SimGear</span><a
name="dx1-53095"></a> there
are (i) <span
class="ptmbi7t---109">FlightGear</span><a
name="dx1-53096"></a> (the simulator itself), and (ii) <span
class="ptmbi7t---109">TerraGear</span><a
name="dx1-53097"></a>, which comprises the scenery
building tools.
<!--l. 240--><p class="indent"> 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<a
name="dx1-53098"></a>, Oliver
Delise, <a
name="dx1-53099"></a>Christian Mayer, <a
name="dx1-53100"></a>Curt Olson,<a
name="dx1-53101"></a> Tony Peden, <a
name="dx1-53102"></a>Gary R. Van Sickle<a
name="dx1-53103"></a>, Norman Vine<a
name="dx1-53104"></a>, and
others. A more comprehensive list of contributors can be found in Chapter <a
href="#x1-52000A">A<!--tex4ht:ref: landing--></a> as well as in
the <span
class="pcrr7t---109">Thanks </span>file provided with the code. Also, the <span
class="ptmbi7t---109">FlightGear </span>Website<a
name="dx1-53105"></a> contains a
detailed history worth reading of all of the notable development milestones at
<!--l. 252--><p class="indent"> <a
href="http://www.flightgear.org/News/" >http://www.flightgear.org/News/</a>
<h3 class="sectionHead"><span class="titlemark">A.2</span> <a
name="x1-54000A.2"></a>Those, who did the work</h3>
<a
name="dx1-54001"></a>
<!--l. 258--><p class="noindent">Did you enjoy the flight? In case you did, don&#8217;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<a
name="dx1-54002"></a> 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 <span
class="ptmbi7t---109">FlightGear </span>mailing
lists<a
name="dx1-54003"></a> and contribute your thoughts there. Instructions to do so can be found at
<!--l. 266--><p class="indent"> <a
href="http://www.flightgear.org/mail.html" >http://www.flightgear.org/mail.html</a>.
<!--l. 269--><p class="noindent">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.
<!--l. 275--><p class="noindent">The following names the people who did the job (this information was essentially taken
from the file <span
class="pcrr7t---109">Thanks </span>accompanying the code).
<!--l. 280--><p class="noindent"><span
class="ptmb7t---109">A1 Free Sounds</span><a
name="dx1-54004"></a> (<a
href="mailto:techie@mail.ev1.net" >techie@mail.ev1.net</a>)
<br class="newline">Granted permission for the flightgear project to use some of the sound effects from their
site. Homepage under
<!--l. 286--><p class="indent"> <a
href="http://www.a1freesoundeffects.com" ></a>
<!--l. 288--><p class="noindent"><span
class="ptmb7t---109">Raul Alonzo</span><a
name="dx1-54005"></a> (<a
href="mailto:amil@las.es" >amil@las.es</a>)
<br class="newline">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:
<!--l. 295--><p class="indent"> <a
href="http://www1.las.es/~amil/ssystem" >http://www1.las.es/<img
src="getstart9x.gif" alt="~" class="tilde" > amil/ssystem</a>.
<!--l. 298--><p class="noindent"><span
class="ptmb7t---109">Michele America</span><a
name="dx1-54006"></a> (<a
href="mailto:nomimarketing@mail.telepac.pt" >nomimarketing@mail.telepac.pt</a>)
<br class="newline">Contributed to the HUD<a
name="dx1-54007"></a> code.
<!--l. 303--><p class="noindent"><span
class="ptmb7t---109">Michael Basler</span><a
name="dx1-54008"></a> (<a
href="mailto:pmb@epost.de" >pmb@epost.de</a>)
<br class="newline">Author of Installation and Getting Started. Flight Simulation Page at
<!--l. 307--><p class="indent"> <a
href="http://www.geocities.com/pmb.geo/flusi.htm" >http://www.geocities.com/pmb.geo/flusi.htm</a>
<!--l. 310--><p class="noindent"><span
class="ptmb7t---109">Jon S. Berndt</span><a
name="dx1-54009"></a> (<a
href="mailto:jsb@hal-pc.org" >jsb@hal-pc.org</a>)
<br class="newline">Working on a complete C++ rewrite/reimplimentation of the core FDM<a
name="dx1-54010"></a>. 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:
<!--l. 317--><p class="indent"> <a
href="http://jsbsim.sourceforge.net" >http://jsbsim.sourceforge.net</a>
<!--l. 320--><p class="noindent">Special attention to X15 is paid in separate pages on this site. Besides, Jon contributed
via a lot of suggestions/corrections to this Guide.
<!--l. 325--><p class="noindent"><span
class="ptmb7t---109">Paul Bleisch</span><a
name="dx1-54011"></a> (<a
href="mailto:pbleisch@acm.org" >pbleisch@acm.org</a>)
<br class="newline">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.
<!--l. 334--><p class="noindent"><span
class="ptmb7t---109">Jim Brennan</span><a
name="dx1-54012"></a> (<a
href="mailto:jjb@kingmont.com" >jjb@kingmont.com</a>)
<br class="newline">Provided a big chunk of online space to store USA scenery for <span
class="ptmbi7t---109">FlightGear</span>.
<!--l. 338--><p class="noindent"><span
class="ptmb7t---109">Bernie Bright</span><a
name="dx1-54013"></a> (<a
href="mailto:bbright@c031.aone.net.au" >bbright@c031.aone.net.au</a>)
<br class="newline">Many C++ style, usage, and implementation improvements, STL portability and much,
much more. Currently he is trying to create a BeOS port. Added threading support and a
threaded tile pager.
<!--l. 344--><p class="noindent"><span
class="ptmb7t---109">Bernhard H. Buckel</span><a
name="dx1-54014"></a> (<a
href="mailto:buckel@mail.uni-wuerzburg.de" >buckel@mail.uni-wuerzburg.de</a>)
<br class="newline">Contributed the README.Linux. Contributed several sections to earlier versions of
Installation and Getting Started.
<!--l. 350--><p class="noindent"><span
class="ptmb7t---109">Gene Buckle</span><a
name="dx1-54015"></a> (<a
href="mailto:geneb@deltasoft.com" >geneb@deltasoft.com</a>)
<br class="newline">A lot of work getting <span
class="ptmbi7t---109">FlightGear </span>to compile with the MSVC<a
name="dx1-54016"></a>++ compiler. Numerous
hints on detailed improvements.
<!--l. 356--><p class="noindent"><span
class="ptmb7t---109">Ralph Carmichael</span><a
name="dx1-54017"></a> (<a
href="mailto:ralph@pdas.com" >ralph@pdas.com</a>)
<br class="newline">Support of the project. The Public Domain Aeronautical Software web site at
<!--l. 360--><p class="indent"> <a
href="http://www.pdas.com" >http://www.pdas.com</a>
<!--l. 363--><p class="noindent">has the PDAS CD-ROM for sale containing great programs for astronautical
engineers.
<!--l. 366--><p class="noindent"><span
class="ptmb7t---109">Didier Chauveau</span><a
name="dx1-54018"></a> (<a
href="mailto:chauveau@math.univ-mlv.fr" >chauveau@math.univ-mlv.fr</a>)
<br class="newline">Provided some initial code to parse the 30 arcsec DEM files found at:
<!--l. 371--><p class="indent"> <a
href="http://edcwww.cr.usgs.gov/landdaac/gtopo30/gtopo30.html" >http://edcwww.cr.usgs.gov/landdaac/gtopo30/gtopo30.html</a>.
<!--l. 374--><p class="noindent"><span
class="ptmb7t---109">John Check</span><a
name="dx1-54019"></a> (<a
href="mailto:j4strngs@rockfish.net" >j4strngs@rockfish.net</a>)
<br class="newline">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. <span
class="ptmbi7t---109">FlightGear </span>page at
<!--l. 380--><p class="indent"> <a
href="http://rockfish.net/fg/" >http://rockfish.net/fg/</a>.
<!--l. 383--><p class="noindent"><span
class="ptmb7t---109">Dave Cornish</span><a
name="dx1-54020"></a> (<a
href="mailto:dmc@halcyon.com" >dmc@halcyon.com</a>)
<br class="newline">Dave created new cool runway textures.
<!--l. 387--><p class="noindent"><span
class="ptmb7t---109">Oliver Delise</span> <a
name="dx1-54021"></a>(<a
href="mailto:delise@mail.isis.de" >delise@mail.isis.de</a>)
<br class="newline">Started a FAQ, Documentation, Public relations. Working on adding some
networking/multi-user code.<a
name="dx1-54022"></a> Founder of the FlightGear MultiPilot Project at
<!--l. 393--><p class="indent"> <a
href="http://www.isis.de/members/~odelise/progs/flightgear" >http://www.isis.de/members/<img
src="getstart10x.gif" alt="~" class="tilde" > odelise/progs/flightgear</a>.
<!--l. 396--><p class="noindent"><span
class="ptmb7t---109">Jean-Francois Doue</span><a
name="dx1-54023"></a>
<br class="newline">Vector 2D, 3D, 4D and Matrix 3D and 4D inlined C++ classes. (Based on Graphics
Gems IV, Ed. Paul S. Heckbert)
<!--l. 401--><p class="indent"> <a
href="http://www.animats.com/simpleppp/ftp/public_html/topics/developers.html" >http://www.animats.com/simpleppp/ftp/public_html/topics/developers.html</a>.
<!--l. 404--><p class="noindent"><span
class="ptmb7t---109">Dave Eberly</span> <a
name="dx1-54024"></a>(<a
href="mailto:eberly@magic-software.com" >eberly@magic-software.com</a>)
<br class="newline">Contributed some sphere interpolation code used by Christian Mayer&#8217;s weather data
base system. On Dave&#8217;s web site there are tons of really useful looking code at
<!--l. 410--><p class="indent"> <a
href="http://www.magic-software.com" >http://www.magic-software.com</a>.
<!--l. 413--><p class="noindent"><span
class="ptmb7t---109">Francine Evans</span><a
name="dx1-54025"></a> (<a
href="mailto:evans@cs.sunysb.edu" >evans@cs.sunysb.edu</a>)
<!--l. 416--><p class="indent"> <a
href="http://www.cs.sunysb.edu/~evans/stripe.html" >http://www.cs.sunysb.edu/~evans/stripe.html</a>
<!--l. 419--><p class="noindent">Wrote the GPL&#8217;d tri-striper.
<!--l. 423--><p class="noindent"><span
class="ptmb7t---109">Oscar Everitt</span><a
name="dx1-54026"></a> (<a
href="mailto:bigoc@premier.net" >bigoc@premier.net</a>)
<br class="newline">Created single engine piston engine sounds as part of an F4U package for FS98<a
name="dx1-54027"></a>. They
are pretty cool and Oscar was happy to contribute them to our little project.
<!--l. 429--><p class="noindent"><span
class="ptmb7t---109">Bruce Finney</span><a
name="dx1-54028"></a> (<a
href="mailto:bfinney@gte.net" >bfinney@gte.net</a>)
<br class="newline">Contributed patches for MSVC5 compatibility.
<!--l. 433--><p class="noindent"><span
class="ptmb7t---109">Jean-loup Gailly</span><a
name="dx1-54029"></a> and <span
class="ptmb7t---109">Mark Adler</span><a
name="dx1-54030"></a> (<a
href="mailto:zlib@gzip.org" >zlib@gzip.org</a>)
<br class="newline">Authors of the zlib library<a
name="dx1-54031"></a>. Used for on-the-fly compression and decompression
routines,
<!--l. 438--><p class="indent"> <a
href="http://www.cdrom.com/pub/infozip/zlib/" >http://www.cdrom.com/pub/infozip/zlib/</a>.
<!--l. 441--><p class="noindent"><span
class="ptmb7t---109">Mohit Garg</span><a
name="dx1-54032"></a> (<a
href="mailto:theprotean_1@hotmail.com" >theprotean_1@hotmail.com</a>)
<br class="newline">Contributed to the manual.
<!--l. 446--><p class="noindent"><span
class="ptmb7t---109">Thomas Gellekum</span><a
name="dx1-54033"></a> (<a
href="mailto:tg@ihf.rwth-aachen.de" >tg@ihf.rwth-aachen.de</a>)
<br class="newline">Changes and updates for compiling on FreeBSD<a
name="dx1-54034"></a>.
<!--l. 451--><p class="noindent"><span
class="ptmb7t---109">Neetha Girish</span><a
name="dx1-54035"></a> (<a
href="mailto:neethagirish@usa.net" >neethagirish@usa.net</a>)
<br class="newline">Contributed the changes for the xml configurable HUD.
<!--l. 456--><p class="noindent"><span
class="ptmb7t---109">Jeff Goeke-Smith</span><a
name="dx1-54036"></a> (<a
href="mailto:jgoeke@voyager.net" >jgoeke@voyager.net</a>)
<br class="newline">Contributed our first autopilot<a
name="dx1-54037"></a> (Heading Hold). Better autoconf check for external
timezone/daylight variables.
<!--l. 462--><p class="noindent"><span
class="ptmb7t---109">Michael I. Gold</span><a
name="dx1-54038"></a> (<a
href="mailto:gold@puck.asd.sgi.com" >gold@puck.asd.sgi.com</a>)
<br class="newline">Patiently answered questions on OpenGL<a
name="dx1-54039"></a>.
<!--l. 467--><p class="noindent"><span
class="ptmb7t---109">Habibe</span><a
name="dx1-54040"></a> (<a
href="mailto:habibie@MailandNews.com" >habibie@MailandNews.com</a>)
<br class="newline">Made RedHat package building changes for SimGear.
<!--l. 471--><p class="noindent"><span
class="ptmb7t---109">Mike Hill</span><a
name="dx1-54041"></a> (<a
href="mailto:mikehill@flightsim.com" >mikehill@flightsim.com</a>)
<br class="newline">For allowing us to concert and use his wonderful planes, available form
<!--l. 475--><p class="indent"> <a
href="http://www.flightsimnetwork.com/mikehill/home.htm" >http://www.flightsimnetwork.com/mikehill/home.htm</a>,
<!--l. 477--><p class="noindent">for <span
class="ptmbi7t---109">FlightGear</span>.
<!--l. 481--><p class="noindent"><span
class="ptmb7t---109">Erik Hofman</span><a
name="dx1-54042"></a> (<a
href="mailto:erik.hofman@a1.nl" >erik.hofman@a1.nl</a>)
<br class="newline">Contributed SGI IRIX support and binaries.
<!--l. 485--><p class="noindent"><span
class="ptmb7t---109">Charlie Hotchkiss</span><a
name="dx1-54043"></a> (<a
href="mailto:clhotch@pacbell.net" >clhotch@pacbell.net</a>)
<br class="newline">Worked on improving and enhancing the HUD<a
name="dx1-54044"></a> code. Lots of code style tips and code
tweaks.
<!--l. 490--><p class="noindent"><span
class="ptmb7t---109">Bruce Jackson</span><a
name="dx1-54045"></a> (NASA) (<a
href="mailto:e.b.jackson@larc.nasa.gov" >e.b.jackson@larc.nasa.gov</a>)
<!--l. 494--><p class="indent"> <a
http://dcb.larc.nasa.gov/www/DCBStaff/ebj/ebj.html >http://dcb.larc.nasa.gov/www/DCBStaff/ebj/ebj.html</a>
<!--l. 497--><p class="noindent">Developed the LaRCsim<a
name="dx1-54046"></a> code under funding by NASA which we use to provide the
flight model. Bruce has patiently answered many, many questions.
<!--l. 503--><p class="noindent"><span
class="ptmb7t---109">Ove Kaaven</span> <a
name="dx1-54047"></a>(<a
href="mailto:ovek@arcticnet.no" >ovek@arcticnet.no</a>)
<br class="newline">Contributed the Debian binary.
<!--l. 507--><p class="noindent"><span
class="ptmb7t---109">Richard Kaszeta</span> <a
name="dx1-54048"></a>(<a
href="mailto:bofh@me.umn.edu" >bofh@me.umn.edu</a>)
<br class="newline">Contributed screen buffer to ppm screen shot routine. Also helped in the early
development of the &#8221;altitude hold autopilot module&#8221;<a
name="dx1-54049"></a> by teaching Curt Olson the basics of
Control Theory and helping him code and debug early versions. Curt&#8217;s &#8221;Boss&#8221; Bob
Hain (<a
href="mailto:bob@me.umn.edu" >bob@me.umn.edu</a>) also contributed to that. Further details available at:
<!--l. 515--><p class="indent"> <a
href="http://www.menet.umn.edu/~curt/fgfs/Docs/Autopilot/AltitudeHold/AltitudeHold.html" >http://www.menet.umn.edu/&nbsp;curt/fgfs/Docs/Autopilot/AltitudeHold/AltitudeHold.html</a>.
<!--l. 518--><p class="noindent">Rich&#8217;s Homepage is at
<!--l. 522--><p class="indent"> <a
href="http://www.menet.umn.edu/~kaszeta" >http://www.menet.umn.edu/&nbsp;kaszeta</a>.
<!--l. 525--><p class="noindent"><span
class="ptmb7t---109">Tom Knienieder</span><a
name="dx1-54050"></a> (<a
href="mailto:tom@knienieder.com" >tom@knienieder.com</a>)
<br class="newline">Ported the audio library<a
name="dx1-54051"></a> first to OpenBSD and IRIX and after that to Win32.
<!--l. 529--><p class="noindent"><span
class="ptmb7t---109">Reto Koradi</span><a
name="dx1-54052"></a> (<a
href="mailto:kor@mol.biol.ethz.ch" >kor@mol.biol.ethz.ch</a>)
<!--l. 532--><p class="indent"> <a
href="file:\protect \let \hyper:normalise \def \begingroup \catcode `\relax \unhbox \voidb@x \special {t4ht@+&nbsp;}x\active \def " { }\catcode `%\active \let %%\let %%\catcode `.html#\active \def ><a
href="http://www.mol.biol.ethz.ch/~{}kor" >http://www.mol.biol.ethz.ch/~kor</a></a>
<!--l. 535--><p class="noindent">Helped with setting up fog effects<a
name="dx1-54053"></a>.
<!--l. 539--><p class="noindent"><span
class="ptmb7t---109">Bob Kuehne</span><a
name="dx1-54054"></a> (<a
href="mailto:rpk@who.net" >rpk@who.net</a>)
<br class="newline">Redid the Makefile system so it is simpler and more robust.
<!--l. 543--><p class="noindent"><span
class="ptmb7t---109">Kyler B Laird</span><a
name="dx1-54055"></a> (<a
href="mailto:laird@ecn.purdue.edu" >laird@ecn.purdue.edu</a>)
<br class="newline">Contributed corrections to the manual.
<!--l. 547--><p class="noindent"><span
class="ptmb7t---109">David Luff</span><a
name="dx1-54056"></a> (<a
href="mailto:david.luff@nottingham.ac.uk" >david.luff@nottingham.ac.uk</a>)
<br class="newline">Contributed heavily to the IO360 piston engine model.
<!--l. 551--><p class="noindent"><span
class="ptmb7t---109">Christian Mayer</span><a
name="dx1-54057"></a> (<a
href="mailto:flightgear@christianmayer.de" >flightgear@christianmayer.de</a>)
<br class="newline">Working on multi-lingual conversion tools<a
name="dx1-54058"></a> for fgfs as a demonstration of technology.
Contributed code to read Microsoft Flight Simulator scenery textures. Christian is
working on a completely new weather<a
name="dx1-54059"></a> subsystem. Donated a hot air balloon<a
name="dx1-54060"></a> to the
project.
<!--l. 558--><p class="noindent"><span
class="ptmb7t---109">David Megginson</span><a
name="dx1-54061"></a> (<a
href="mailto:david@megginson.com" >david@megginson.com</a>)
<br class="newline">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<a
name="dx1-54062"></a>
code, playing better with OpenGL, with new features. Developed the property manager
and contributed to joystick support.
<!--l. 570--><p class="noindent"><span
class="ptmb7t---109">Cameron Moore</span><a
name="dx1-54063"></a> (<a
href="mailto:lists@toad.bitstreet.net" >lists@toad.bitstreet.net</a>)
<br class="newline">FAQ maintainer. Reigning list administration. Provided man pages.
<!--l. 575--><p class="noindent"><span
class="ptmb7t---109">Eric Mitchell</span><a
name="dx1-54064"></a> (<a
href="mailto:mitchell@mars.ark.com" >mitchell@mars.ark.com</a>)
<br class="newline">Contributed some topnotch scenery textures<a
name="dx1-54065"></a> being all original creations by him.
<!--l. 579--><p class="noindent"><span
class="ptmb7t---109">Alan Murta</span><a
name="dx1-54066"></a> (<a
href="mailto:amurta@cs.man.ac.uk" >amurta@cs.man.ac.uk</a>)
<!--l. 582--><p class="indent"> <a
href="http://www.cs.man.ac.uk/aig/staff/alan/software/" >http://www.cs.man.ac.uk/aig/staff/alan/software/</a>
<!--l. 585--><p class="noindent">Created the Generic Polygon Clipping library.
<!--l. 589--><p class="noindent"><span
class="ptmb7t---109">Phil Nelson</span><a
name="dx1-54067"></a> (<a
href="mailto:phil@cs.wwu.edu" >phil@cs.wwu.edu</a>)
<br class="newline">Author of GNU dbm, a set of database routines that use extendible hashing and work
similar to the standard UNIX dbm routines.
<!--l. 594--><p class="noindent"><span
class="ptmb7t---109">Alexei Novikov</span><a
name="dx1-54068"></a> (<a
href="mailto:anovikov@heron.itep.ru" >anovikov@heron.itep.ru</a>)
<br class="newline">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.
<!--l. 600--><p class="noindent"><span
class="ptmb7t---109">Curt Olson</span><a
name="dx1-54069"></a> (<a
href="mailto:curt@flightgear.org" >curt@flightgear.org</a>)
<br class="newline">Primary organization of the project.
<br class="newline">First implementation and modifications based on LaRCsim<a
name="dx1-54070"></a>.
<br class="newline">Besides putting together all the pieces provided by others mainly concentrating on the
scenery subsystem<a
name="dx1-54071"></a> as well as the graphics stuff. Homepage at
<!--l. 605--><p class="indent"> <a
href="http://www.menet.umn.edu/~curt/" >http://www.menet.umn.edu/&nbsp;curt/</a>
<!--l. 608--><p class="indent"> noindent <span
class="ptmb7t---109">Brian Paul</span><a
name="dx1-54072"></a>
<br class="newline">We made use of his TR library and of course of Mesa:
<!--l. 611--><p class="indent"> <a
href="http://www.mesa3d.org/brianp/TR.html" >http://www.mesa3d.org/brianp/TR.html</a>, <a
href="http://www.mesa3d.org" >http://www.mesa3d.org</a>
<!--l. 614--><p class="noindent"><span
class="ptmb7t---109">Tony Peden</span><a
name="dx1-54073"></a> (<a
href="mailto:apeden@earthlink.net" >apeden@earthlink.net</a>)
<br class="newline">Contributions on flight model development, including a LaRCsim based Cessna 172.
Contributed to <span
class="ptmbi7t---109">JSBSim </span>the initial conditions code, a more complete standard atmosphere
model, and other bugfixes/additions. His Flight Dynamics page can be found at:
<!--l. 621--><p class="indent"> <a
href="http://www.nwlink.com/~apeden" >http://www.nwlink.com/<img
src="getstart11x.gif" alt="~" class="tilde" > apeden</a>.
<!--l. 625--><p class="noindent"><span
class="ptmb7t---109">Robin Peel</span><a
name="dx1-54074"></a> (<a
href="mailto:robin@cpwd.com" >robin@cpwd.com</a>)
<br class="newline">Maintains worldwide airport and runway database for <span
class="ptmbi7t---109">FlightGear </span>as well as X-Plane.
<!--l. 629--><p class="noindent"><span
class="ptmb7t---109">Alex Perry</span><a
name="dx1-54075"></a> (<a
href="mailto:alex.perry@ieee.org" >alex.perry@ieee.org</a>)
<br class="newline">Contributed code to more accurately model VSI, DG, Alticude. Suggestions for
improvements of the layout of the simulator on the mailing list and help on
documentation.
<!--l. 635--><p class="noindent"><span
class="ptmb7t---109">Friedemann Reinhard</span><a
name="dx1-54076"></a> (<a
href="mailto:mpt218@faupt212.physik.uni-erlangen.de" >mpt218@faupt212.physik.uni-erlangen.de</a>)
<br class="newline">Development of an early textured instrument panel<a
name="dx1-54077"></a>.
<!--l. 640--><p class="noindent"><span
class="ptmb7t---109">Petter Reinholdtsen</span><a
name="dx1-54078"></a> (<a
href="mailto:pere@games.no" >pere@games.no</a>)
<br class="newline">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&#8217;t use the UNIX make system.
<!--l. 648--><p class="noindent"><span
class="ptmb7t---109">William Riley</span><a
name="dx1-54079"></a> (<a
href="mailto:riley@technologist.com" >riley@technologist.com</a>)
<br class="newline">Contributed code to add &#8221;brakes<a
name="dx1-54080"></a>&#8221;. Also wrote a patch to support a first joystick with
more than 2 axis.
<!--l. 653--><p class="noindent"><span
class="ptmb7t---109">Andy Ross</span><a
name="dx1-54081"></a> (<a
href="mailto:andy@plausible.org" >andy@plausible.org</a>)
<br class="newline">Contributed a new configurable FDM called YASim (Yet Another Fligth Dynamics
Simulator, based on geometry information rather than aerodynamic coefficients.
<!--l. 657--><p class="noindent"><span
class="ptmb7t---109">Paul Schlyter</span><a
name="dx1-54082"></a> (<a
href="mailto:pausch@saaf.se" >pausch@saaf.se</a>)
<br class="newline">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.
<!--l. 663--><p class="indent"> <a
href="http://welcome.to/pausch" >http://welcome.to/pausch</a>
<!--l. 666--><p class="noindent"><span
class="ptmb7t---109">Chris Schoeneman</span><a
name="dx1-54083"></a> (<a
href="mailto:crs@millpond.engr.sgi.com" >crs@millpond.engr.sgi.com</a>)
<br class="newline">Contributed ideas on audio support.
<!--l. 671--><p class="noindent"><span
class="ptmb7t---109">Phil Schubert</span><a
name="dx1-54084"></a> (<a
href="mailto:philip@zedley.com" >philip@zedley.com</a>)
<br class="newline">Contributed various textures and engine modelling.
<!--l. 675--><p class="indent"> <a
href="http://www.zedley.com/Philip/index.htm" >http://www.zedley.com/Philip/index.htm</a>.
<!--l. 678--><p class="noindent"><span
class="ptmb7t---109">Jonathan R Shewchuk</span><a
name="dx1-54085"></a> (<a
href="mailto:Jonathan\protect \unhbox \voidb@x \kern .06em\vbox {\hrule width.3em}R\protect \unhbox \voidb@x \kern .06em\vbox {\hrule width.3em}Shewchuk@ux4.sp.cs.cmu.edu" >Jonathan_R_Shewchuk@ux4.sp.cs.cmu.edu</a>)
<br class="newline">Author of the Triangle<a
name="dx1-54086"></a> program. Triangle is used to calculate the Delauney triangulation
of our irregular terrain.
<!--l. 684--><p class="noindent"><span
class="ptmb7t---109">Gordan Sikic</span><a
name="dx1-54087"></a> (<a
href="mailto:gsikic@public.srce.hr" >gsikic@public.srce.hr</a>)
<br class="newline">Contributed a Cherokee flight model<a
name="dx1-54088"></a> for LaRCsim<a
name="dx1-54089"></a>. Currently is not working and needs to
be debugged. Use configure <span
class="pcrr7t---109">--with-flight-model=cherokee </span>to build the
cherokee instead of the Cessna<a
name="dx1-54090"></a>.
<!--l. 691--><p class="noindent"><span
class="ptmb7t---109">Michael Smith</span><a
name="dx1-54091"></a> (<a
href="mailto:msmith99@flash.net" >msmith99@flash.net</a>)
<br class="newline">Contributed cockpit graphics, 3-D models, logos, and other images. Project Bonanza
<!--l. 696--><p class="indent"> <a
href="http://members.xoom.com/ConceptSim/index.html" >http://members.xoom.com/ConceptSim/index.html</a>.
<!--l. 699--><p class="noindent"><span
class="ptmb7t---109">Durk Talsma</span><a
name="dx1-54092"></a> (<a
href="mailto:d.talsma@chello.nl" >d.talsma@chello.nl</a>)
<br class="newline">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.<a
name="dx1-54093"></a> Website at
<!--l. 708--><p class="indent"> <a
href="http://people.a2000.nl/dtals" >http://people.a2000.nl/dtals</a>.
<!--l. 711--><p class="noindent"><span
class="ptmb7t---109">UIUC</span><a
name="dx1-54094"></a> - Department of Aeronautical and Astronautical Engineering
<br class="newline">Contributed modifications to LaRCsim to allow loading of aircraft parameters
from a file. These modifications were made as part of an icing research project.
<!--l. 718--><p class="indent"> Those did the coding and made it all work:
<br class="newline">Jeff Scott <a
href="mailto:jscott@students.uiuc.edu" >jscott@students.uiuc.edu</a><a
name="dx1-54095"></a>
<br class="newline">Bipin Sehgal <a
href="mailto:bsehgal@uiuc.edu" >bsehgal@uiuc.edu</a><a
name="dx1-54096"></a>
<br class="newline">Michael Selig <a
href="mailto:m-selig@uiuc.edu" >m-selig@uiuc.edu</a><a
name="dx1-54097"></a>
<!--l. 724--><p class="indent"> Moreover, those helped to support the effort:
<br class="newline">Jay Thomas <a
href="mailto:jthomas2@uiuc.edu" >jthomas2@uiuc.edu</a><a
name="dx1-54098"></a>
<br class="newline">Eunice Lee <a
href="mailto:ey-lee@students.uiuc.edu" >ey-lee@students.uiuc.edu</a><a
name="dx1-54099"></a>
<br class="newline">Elizabeth Rendon <a
href="mailto:mdfhoyos@md.impsat.net.co" >mdfhoyos@md.impsat.net.co</a><a
name="dx1-54100"></a>
<br class="newline">Sudhi Uppuluri <a
href="mailto:suppulur@students.uiuc.edu" >suppulur@students.uiuc.edu</a>
<!--l. 732--><p class="noindent"><span
class="ptmb7t---109">U. S. Geological Survey</span><a
name="dx1-54101"></a>
<!--l. 736--><p class="indent"> <a
href="http://edcwww.cr.usgs.gov/doc/edchome/ndcdb/ndcdb.html" >http://edcwww.cr.usgs.gov/doc/edchome/ndcdb/ndcdb.html</a>
<!--l. 739--><p class="noindent">Provided geographic data used by this project.
<!--l. 743--><p class="noindent"><span
class="ptmb7t---109">Mark Vallevand</span><a
name="dx1-54102"></a> (<a
href="mailto:Mark.Vallevand@UNISYS.com" >Mark.Vallevand@UNISYS.com</a>)
<br class="newline">Contributed some METAR parsing code and some win32 screen printing routines.
<!--l. 748--><p class="noindent"><span
class="ptmb7t---109">Gary R. Van Sickle</span><a
name="dx1-54103"></a> (<a
href="mailto:tiberius@braemarinc.com" >tiberius@braemarinc.com</a>)
<br class="newline">Contributed some initial GameGLUT<a
name="dx1-54104"></a> support and other fixes. Has done some interesting
preliminary work on a binary file format. Check
<!--l. 754--><p class="indent"> <a
href="http://www.woodsoup.org/projs/ORKiD/fgfs.htm" >http://www.woodsoup.org/projs/ORKiD/fgfs.htm</a>.
<!--l. 757--><p class="noindent"><span
class="ptmb7t---109">Martin Spott</span><a
name="dx1-54105"></a> (<a
href="mailto:Martin.Spott@uni-duisburg.de" >Martin.Spott@uni-duisburg.de</a>)
<br class="newline">Co-Author of the &#8221;Getting Started&#8221;.
<!--l. 761--><p class="noindent"><span
class="ptmb7t---109">Norman Vine</span><a
name="dx1-54106"></a> (<a
href="mailto:nhv@yahoo.com" >nhv@yahoo.com</a>)
<br class="newline">Provided more numerous URL&#8217;s to the &#8221;FlightGear Community&#8221;. 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.
<!--l. 770--><p class="noindent"><span
class="ptmb7t---109">Roland Voegtli</span><a
name="dx1-54107"></a> (<a
href="mailto:webmaster@sanw.unibe.ch" >webmaster@sanw.unibe.ch</a>)
<br class="newline">Contributed great photorealistic textures. Founder of European Scenery Project for
X-Plane:
<!--l. 776--><p class="indent"> <a
href="http://www.g-point.com/xpcity/esp/" >http://www.g-point.com/xpcity/esp/</a>
<!--l. 780--><p class="noindent"><span
class="ptmb7t---109">Carmelo Volpe</span><a
name="dx1-54108"></a> (<a
href="mailto:carmelo.volpe@mednut.ki.se" >carmelo.volpe@mednut.ki.se</a>)
<br class="newline">Porting <span
class="ptmbi7t---109">FlightGear </span>to the Metro Works<a
name="dx1-54109"></a> development environment (PC/Mac).
<!--l. 786--><p class="noindent"><span
class="ptmb7t---109">Darrell Walisser</span><a
name="dx1-54110"></a> (<a
href="mailto:dwaliss1@purdue.edu" >dwaliss1@purdue.edu</a>)
<br class="newline">Contributed a large number of changes to porting <span
class="ptmbi7t---109">FlightGear </span>to the Metro Works
development environment (PC/Mac). Finally produced the first Macintosh port.
Contributed to the Mac part of Getting Started, too.
<!--l. 791--><p class="noindent"><span
class="ptmb7t---109">Ed Williams</span><a
name="dx1-54111"></a> (<a
href="file:Ed_Williams@compuserve.com" >Ed_Williams@compuserve.com</a>).
<br class="newline">Contributed magnetic variation code (impliments Nima WMM 2000). We&#8217;ve also
borrowed from Ed&#8217;s wonderful aviation formulary at various times as well. Website at
<a
href="http://www.best.com/~williams/index.html" >http://www.best.com/<img
src="getstart12x.gif" alt="~" class="tilde" > williams/index.html</a>,
<!--l. 800--><p class="noindent"><span
class="ptmb7t---109">Jean-Claude Wippler</span><a
name="dx1-54112"></a> (<a
href="mailto:jcw@equi4.com" >jcw@equi4.com</a>)
<br class="newline">Author of MetaKit<a
name="dx1-54113"></a> - a portable, embeddible database with a portable data file format
used in <span
class="ptmbi7t---109">FlightGear</span>. Please see the following URL for more info:
<!--l. 806--><p class="indent"> <a
href="http://www.equi4.com/metakit" >http://www.equi4.com/metakit</a>
<!--l. 809--><p class="noindent"><span
class="ptmb7t---109">Woodsoup Project</span><a
name="dx1-54114"></a>
<br class="newline">
<!--l. 811--><p class="indent"> <a
href="http://www.woodsoup.org" >http://www.woodsoup.org</a>
<!--l. 813--><p class="indent"> While <span
class="ptmbi7t---109">FlightGear </span>no longer uses Woodsoup servies we appreciate the support
provied to our project during the time they hosted us. Once they provided computing
resources and services so that the <span
class="ptmbi7t---109">FlightGear </span>project could have a real home.
<!--l. 816--><p class="noindent"><span
class="ptmb7t---109">Robert Allan Zeh</span><a
name="dx1-54115"></a> (<a
href="mailto:raz@cmg.FCNBD.COM" >raz@cmg.FCNBD.COM</a>)
<br class="newline">Helped tremendously in figuring out the Cygnus<a
name="dx1-54116"></a> Win32 compiler and how to link with
.dll&#8217;s. Without him the first run-able Win32 version of <span
class="ptmbi7t---109">FlightGear </span>would have been
impossible.
<h3 class="sectionHead"><span class="titlemark">A.3</span> <a
name="x1-55000A.3"></a>What remains to be done</h3>
<!--l. 825--><p class="noindent">At first: If you read (and, maybe, followed) this guide until this point you may probably
agree: <span
class="ptmbi7t---109">FlightGear</span>, 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.
<!--l. 829--><p class="indent"> Despite, <span
class="ptmbi7t---109">FlightGear </span>needs - and gets - further development. Except internal tweaks,
there are several fields where <span
class="ptmbi7t---109">FlightGear </span>needs basics improvement and development. A
first direction is adding airport<a
name="dx1-55001"></a>s, streets, and more of those things bringing scenery to real
life and belonging to realistic airports. Another task is further implementation of the
menu system<a
name="dx1-55002"></a>, 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, <span
class="ptmbi7t---109">FlightGear </span>lacks any ATC<a
name="dx1-55003"></a> until
now.
<!--l. 838--><p class="indent"> There are already people working in all of these directions. If you&#8217;re a programmer
and think you can contribute, you are invited to do so.
<h4 class="likesubsectionHead"><a
name="x1-56000A.3"></a>Achnowledgements</h4> Obviously this document could not have been written without all
those contributors mentioned above making <span
class="ptmbi7t---109">FlightGear </span>a reality.
<!--l. 847--><p class="noindent">First, I was very glad to see Martin Spott <a
name="dx1-56001"></a>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
<!--l. 849--><p class="indent"> Besides, I would like to say special thanks to Curt Olson,<a
name="dx1-56002"></a> 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.
<!--l. 853--><p class="indent"> Next, Bernhard Buckel <a
name="dx1-56003"></a>wrote several sections of early versions of that Guide and
contributed at lot of ideas to it.
<!--l. 856--><p class="indent"> Jon S. Berndt <a
name="dx1-56004"></a>supported me by critical proofreading of several versions of the
document, pointing out inconsistences and suggesting improvements.
<!--l. 859--><p class="indent"> Moreover, I gained a lot of help and support from Norman Vine<a
name="dx1-56005"></a>. Maybe, without
Norman&#8217;s answers I would have never been able to tame different versions of the <span
class="ptmbi7t---109">Cygwin</span>
- <span
class="ptmbi7t---109">FlightGear </span>couple.
<!--l. 863--><p class="indent"> We were glad, our Mac expert Darrell Walisser <a
name="dx1-56006"></a>contributed the section on
compiling under Mac OS X. In addition he submitted several Mac related hints and
fixes.
<!--l. 865--><p class="indent"> Further contributions and donations on special points came from John Check,<a
name="dx1-56007"></a>
(general layout), Oliver Delise <a
name="dx1-56008"></a>(several suggestions including notes on that chapter),
Mohit Garg <a
name="dx1-56009"></a>(OpenGL), Kyler B. Laird <a
name="dx1-56010"></a>(corrections), Alex Perry<a
name="dx1-56011"></a> (OpenGL), and Kai
Troester<a
name="dx1-56012"></a> (compile problems).
<a
name="x1-56013r43"></a>
<h2 class="appendixHead"><span class="titlemark">Appendix&nbsp;B</span><br><a
name="x1-57000B"></a>Missed approach: If anything refuses to work</h2>
<!--l. 33--><p class="noindent">In the following, I tried to sort some problems<a
name="dx1-57001"></a> according to operating system, but if you
encounter a problem it may be a wise idea to look beyond &#8221;your&#8221; operating system - just
in case. Besides, you may want to check the FAQ maintained by Cameron Moore<a
name="dx1-57002"></a>
at
<!--l. 38--><p class="indent"> <a
href="http://www.flightgear.org/Docs/FlightGear-FAQ.html" >http://www.flightgear.org/Docs/FlightGear-FAQ.html</a>.
<!--l. 40--><p class="indent"> Moreover, the source code contains a directory <span
class="pcrr7t---109">docs-mini </span>containing numerous
ideas on and solutions to special problems. This is also a good place for further
reading.
<h3 class="sectionHead"><span class="titlemark">B.1</span> <a
name="x1-58000B.1"></a>FlightGear Problem Reports</h3>
<a
name="dx1-58001"></a>
<!--l. 48--><p class="noindent">The best place to look for help are generally the mailing lists<a
name="dx1-58002"></a> <span
class="ptmb7t---109">[FGFS-Devel] </span>and
<span
class="ptmb7t---109">[FGFS-User]</span>. Instructions for subscription can be found at
<!--l. 53--><p class="indent"> <a
href="http://www.flightgear.org/mail.html" >http://www.flightgear.org/mail.html</a>.
<!--l. 56--><p class="noindent">Often it already helps browsing through the archive at
<!--l. 60--><p class="indent"> <a
href="http://www.menet.umn.edu/~curt/fgfs/search.html" >http://www.menet.umn.edu/&nbsp;curt/fgfs/search.html</a>
<!--l. 63--><p class="noindent">to detect someone had that very same problem a week ago.
<!--l. 66--><p class="indent"> There are numerous helpful developers and users reading the lists, and usually
questions get answered quickly. However, messages of the type
<!--l. 69--><p class="indent"> <span
class="ptmri7t---109">FlightGear does not compile on my system. What shall I do?</span>
<!--l. 71--><p class="noindent">are hard to answer without any further detail given, aren&#8217;t they? Here are some ideas on
important information which may be helpful (depending on the problem you have):
<ul class="itemize1">
<li class="itemize"><span
class="ptmb7t---109">Operating system: </span>(Linux Redhat 7.0. . . /Windows 98SE. . . )
</li>
<li class="itemize"><span
class="ptmb7t---109">Computer: </span>(Pentium III, 1GHz. . . )
</li>
<li class="itemize"><span
class="ptmb7t---109">Graphics board/chip: </span>(Diamond Viper 770/NVIDIA RIVA TNT2. . . )
</li>
<li class="itemize"><span
class="ptmb7t---109">Compiler/version: </span>(Cygnus version 1.0. . . )
</li>
<li class="itemize"><span
class="ptmb7t---109">Versions of relevant libraries: </span>(PLIB 1.2.0, Mesa 3.0. . . )
</li>
<li class="itemize"><span
class="ptmb7t---109">Type of problem: </span>(Linker dies with message. . . )
</li></ul>
<!--l. 91--><p class="indent"> <span
class="ptmb7t---109">One final remark: </span>Please avoid posting binaries to these lists! They are widely
distributed and there are users with low bandwith connections. Thanks.
<h3 class="sectionHead"><span class="titlemark">B.2</span> <a
name="x1-59000B.2"></a>General problems</h3>
<a
name="dx1-59001"></a>
<ul class="itemize1">
<li class="itemize"><span
class="ptmbi7t---109">FlightGear </span>runs SOOO slow.
<br class="newline">If <span
class="ptmbi7t---109">FlightGear </span>says it&#8217;s running with something like 1 fps (frame per second)
or below you typically don&#8217;t have working hardware OpenGL<a
name="dx1-59002"></a> support. There
may be several reasons for this. First, there may be no OpenGL hardware
drivers available for older cards. In this case it is highly recommended to get
a new board.
<!--l. 105--><p class="noindent">Second, check if your drivers are properly installed. Several cards need
additional OpenGL support drivers besides the &#8221;native&#8221; windows ones. For
more detail check Appendix <a
href="#x1-62000C">C<!--tex4ht:ref: opengl--></a>.
</li>
<li class="itemize">Either <span
class="pcrr7t---109">configure </span>or <span
class="pcrr7t---109">make </span>dies with not found <span
class="ptmbi7t---109">PLIB </span>headers or libraries.
<br class="newline">Make sure you have the latest version of <span
class="ptmbi7t---109">PLIB </span>(<span
class="cmmi-10--109">&gt; </span>version 1.2) compiled and
installed. Its headers like <span
class="pcrr7t---109">pu.h </span>have to be under <span
class="pcrr7t---109">/usr/include/plib</span>
and its libraries like <span
class="pcrr7t---109">libplibpu.a </span>under <span
class="pcrr7t---109">/lib</span>. Double check there are
no <span
class="ptmbi7t---109">PLIB </span>headers/libraries sitting elsewhere!
<!--l. 117--><p class="noindent">Besides check careful the error messages of <span
class="pcrr7t---109">configure</span>. In several cases
it says what is missing.</li></ul>
<h3 class="sectionHead"><span class="titlemark">B.3</span> <a
name="x1-60000B.3"></a>Potential problems under Linux</h3>
<a
name="dx1-60001"></a>
<!--l. 124--><p class="noindent">Since we don&#8217;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.)
<ul class="itemize1">
<li class="itemize">Wrong library versions
<br class="newline">This is a rather common cause of grief especially when you prefer to install
the libraries needed by <span
class="ptmbi7t---109">FlightGear </span>by hand. Be sure that especially the Mesa
library contains support for the 3DFX<a
name="dx1-60002"></a> board and that GLIDE<a
name="dx1-60003"></a> libraries are
installed and can be found. If a <span
class="pcrr7t---109">ldd `which fgfs` </span>complains about
missing libraries you are in trouble.
<!--l. 138--><p class="noindent">You should also be sure to keep <span
class="ptmri7t---109">always the </span>latest version of <span
class="ptmbi7t---109">PLIB </span>on your
system. Lots of people have failed miserably to compile <span
class="ptmbi7t---109">FlightGear </span>just
because of an outdated plib.
</li>
<li class="itemize">Missing permissions<a
name="dx1-60004"></a>
<br class="newline"><span
class="ptmbi7t---109">FlightGear </span>needs to be setuid root in order to be capable of accessing an
accelerator board (or a special kernel module as described earlier in this
document) based on 3DFX chips. So you can either issue a
<!--l. 150--><p class="noindent"><span
class="pcrr7t---109">chown root.root /usr/local/bin/fgfs ;</span>
<br class="newline"><span
class="pcrr7t---109">chmod 4755 /usr/local/bin/fgfs</span>
<!--l. 153--><p class="noindent">to give the <span
class="ptmbi7t---109">FlightGear </span>binary the proper rights or install the 3DFX module.
The latter is the &#8220;clean&#8221; solution and strongly recommended!
</li>
<li class="itemize">Non-default install options
<br class="newline"><span
class="ptmbi7t---109">FlightGear </span>will display a lot of diagnostics when being started up. If it
complains about bad looking or missing files, check that you installed
them in the way they are supposed to be, i.e. latest version and proper
location. The canonical location <span
class="ptmbi7t---109">FlightGear </span>wants its data files under
<span
class="pcrr7t---109">/usr/local/lib</span>. Be sure to grab the latest versions of everything that
might be needed!
</li>
<li class="itemize">Compile problems in general
<br class="newline">Make sure you have the latest (official) version of gcc. Old versions of gcc
are a frequent source of trouble! On the other hand, recent versions of the
RedHat 7.0 reportedly have certain problems compiling <span
class="ptmbi7t---109">FlightGear </span>as they
include a preliminary version of GCC.
</li>
<li class="itemize">Problems with linking
<br class="newline">There may be several reasons; however in case you get a message like
<!--l. 175--><p class="noindent"><span
class="pcrr7t---109">libmk4.so.0</span>: cannot open shared object file
<!--l. 177--><p class="noindent">the reason is a missing library package called Metakit. This is provided with
Simgear in packed form. Unpack and install it first.</li></ul>
<h3 class="sectionHead"><span class="titlemark">B.4</span> <a
name="x1-61000B.4"></a>Potential problems under Windows</h3>
<a
name="dx1-61001"></a>
<ul class="itemize1">
<li class="itemize">The executable refuses to run.
<br class="newline">You may have tried to start the executable directly either by double-clicking
<span
class="pcrr7t---109">fgfs.exe </span>in Windows explorer or by invoking it within a MS-DOS
shell. Double-clicking via explorer does never work (except you set the
environment variable <span
class="pcrr7t---109">FG</span>_<span
class="pcrr7t---109">ROOT </span>in <span
class="pcrr7t---109">autoexec.bat </span>or otherwise). Rather
double-click <span
class="pcrr7t---109">runfgfs.bat</span>. For more detail, check Chapter <a
href="#x1-250004">4<!--tex4ht:ref: takeoff--></a>.
<!--l. 192--><p class="noindent">Another cause of grief might be you did not download the most recent
versions of the base package files required by <span
class="ptmbi7t---109">FlightGear</span>, or you did not load
any of them at all. Have a close look at this, as the scenery/texture format is
still under development and may change frequently. For more detail, check
Chapter <a
href="#x1-170003">3<!--tex4ht:ref: prefligh--></a>.
<!--l. 198--><p class="noindent">Next, if you run into trouble at runtime, do not use windows utilities for
unpacking the <span
class="pcrr7t---109">.tar.gz</span>. If you did, try it in the Cygnus shell with <span
class="pcrr7t---109">tar</span>
<span
class="pcrr7t---109">xvfz </span>instead.
</li>
<li class="itemize"><span
class="ptmbi7t---109">FlightGear </span>ignores the command line parameters.
<br class="newline">There is a problem with passing command line options containing a &#8221;=&#8221; to
windows batch files. Instead, include the options into <span
class="pcrr7t---109">runfgfs.bat</span>.
</li>
<li class="itemize">I am unable to build <span
class="ptmbi7t---109">FlightGear </span>under MSVC<a
name="dx1-61002"></a>/MS DevStudio<a
name="dx1-61003"></a>.
<br class="newline">By default, <span
class="ptmbi7t---109">FlightGear </span>is build with GNU C++, i. e. the Cygnus<a
name="dx1-61004"></a> compiler
for Win32. For hints or Makefiles required for MSVC for MSC DevStudio
have a look into
<!--l. 213--><p class="noindent"><a
href="ftp://www.flightgear.org/pub/flightgear/Source/" >ftp://www.flightgear.org/pub/flightgear/Source/</a>.
<!--l. 216--><p class="noindent">In principle, it should be possible to <span
class="ptmbi7t---109">FlightGear </span>with the project files
provided with the code.
</li>
<li class="itemize">Compilation of <span
class="ptmbi7t---109">FlightGear </span>dies.
<br class="newline">There may be several reasons for this, including true bugs. However, before
trying to do anything else or report a problem, make sure you have the latest
version of the <span
class="ptmbi7t---109">Cygwin </span>compiler, as described in Section <a
href="#x1-100002">2<!--tex4ht:ref: building--></a>. In case of doubt,
start <span
class="pcrr7t---109">setup.exe </span>anew and download and install the most recent versions
of bundles as they possibly may have changed.</li></ul>
<a
name="x1-61005r43"></a>
<h2 class="appendixHead"><span class="titlemark">Appendix&nbsp;C</span><br><a
name="x1-62000C"></a>Some words on OpenGL graphics drivers</h2>
<!--l. 32--><p class="noindent"><span
class="ptmbi7t---109">FlightGear</span>&#8217;s graphics engine is based on a graphics library<a
name="dx1-62001"></a> called OpenGL<a
name="dx1-62002"></a>. Its primary
advantage is its platform independence, i. e., programs written with OpenGL<a
name="dx1-62003"></a> support can
be compiled and executed on several platforms, given the proper drivers having been
installed in advance. Thus, independent of if you want to run the binaries only or if you
want to compile the program yourself you must have some sort of OpenGL<a
name="dx1-62004"></a> support
installed for your video card<a
name="dx1-62005"></a>.
<!--l. 39--><p class="indent"> A good review on OpenGL drivers<a
name="dx1-62006"></a> can be found at
<!--l. 42--><p class="indent"> <a
href="http://www.flightgear.org/Hardware" >http://www.flightgear.org/Hardware</a>.
<!--l. 45--><p class="noindent">Specific information is collected for windows at
<!--l. 49--><p class="indent"> <a
href="http://www.x-plane.com/SYSREQ/v5ibm.html" >http://www.x-plane.com/SYSREQ/v5ibm.html</a>
<!--l. 52--><p class="noindent">and for Macintosh at
<!--l. 56--><p class="indent"> <a
href="http://www.x-plane.com/SYSREQ/v5mac.html" >http://www.x-plane.com/SYSREQ/v5mac.html</a>.
<!--l. 60--><p class="noindent">An excellent place to look for documentation about Linux and 3-D accelerators is the
<span
class="ptmri7t---109">Linux Quake</span><a
name="dx1-62007"></a> <span
class="ptmri7t---109">HOWTO </span>at
<!--l. 65--><p class="indent"> <a
href="http://www.linuxquake.com" >http://www.linuxquake.com</a>.
<!--l. 68--><p class="noindent">This should be your first aid in case something goes wrong with your Linux 3-D
setup.
<!--l. 71--><p class="indent"> Unfortunately, there are so many graphics boards, chips and drivers out there that we
are unable to provide a complete description for all systems. Given the present market
dominance of NVIDIA combined with the fact that their chips have indeed been proven
powerful for running <span
class="ptmbi7t---109">FlightGear</span>, we will concentrate on NVIDIA drivers<a
name="dx1-62008"></a> in what
follows.
<h3 class="sectionHead"><span class="titlemark">C.1</span> <a
name="x1-63000C.1"></a>NVIDIA chip based cards under Linux</h3>
<!--l. 80--><p class="noindent">Recent Linux<a
name="dx1-63001"></a> distributions include and install anything needed to run OpenGL programs
under Linux<a
name="dx1-63002"></a>. Usually there is no need to install anything else.
<!--l. 83--><p class="indent"> If for whatever reason this does not work, you may try to download the most recent
drivers from the NVIDIA site at
<!--l. 87--><p class="indent"> <a
href="http://www.nvidia.com/Products/Drivers.nsf/Linux.html" >http://www.nvidia.com/Products/Drivers.nsf/Linux.html</a>
<!--l. 90--><p class="noindent">At present, this page has drivers for all NVIDIA chips for the following Linux
distributions:<a
name="dx1-63003"></a> RedHat 7.1, Redhat 7.0, Redhat 6.2, Redhat 6.1, Mandrake 7.1, Mandrake
7.2, SuSE 7.1, SuSE 7.0 in several formats (.rpm, .tar.gz). These drivers support OpenGL
natively and do not need any additional stuff.
<!--l. 96--><p class="indent"> The page named above contains a detailed <span
class="pcrr7t---109">README and Installation</span>
<span
class="pcrr7t---109">Guide </span>giving a step-by-step description, making it unnecessary to copy the material
here.
<h3 class="sectionHead"><span class="titlemark">C.2</span> <a
name="x1-64000C.2"></a>NVIDIA chip based cards under Windows</h3>
<!--l. 103--><p class="noindent">Again, you may first try the drivers coming with your graphics card. Usually they should
include OpenGL<a
name="dx1-64001"></a> support. If for whatever reason the maker of your board did not include
this feature into the driver, you should install the Detonator reference drivers<a
name="dx1-64002"></a><a
name="dx1-64003"></a> made by
NVIDIA<a
name="dx1-64004"></a> (which might be a good idea anyway). These are available in three
different versions (Windows 95/98/ME, Windows 2000, Windows NT) from
<!--l. 111--><p class="indent"> <a
href="http://www.nvidia.com/products.nsf/htmlmedia/detonator3.html" >http://www.nvidia.com/products.nsf/htmlmedia/detonator3.html</a>
<!--l. 114--><p class="noindent">Just read carefully the Release notes to be found on that page. Notably do not forget to
uninstall your present driver and install a standard VGA graphics adapter before
switching to the new NVIDIA drivers first.
<h3 class="sectionHead"><span class="titlemark">C.3</span> <a
name="x1-65000C.3"></a>3DFX chip based cards under Windows</h3>
<!--l. 124--><p class="noindent">With the Glide drivers no longer provided by 3DFX there seems to be little chance to
get it running (except to find older OpenGL drivers somewhere on the net or
privately). All pages which formerly provided official support or instructions for
3DFX are gone now. For an alternative, you may want to check the next section,
though.
<h3 class="sectionHead"><span class="titlemark">C.4</span> <a
name="x1-66000C.4"></a>An alternative approach for Windows users</h3>
<!--l. 134--><p class="noindent">There is now an attempt to build a program which detects the graphics chip on your
board and automatically installs the appropriate OpenGL drivers. This is called
OpenGL Setup<a
name="dx1-66001"></a> and is presently in beta stage. It&#8217;s home page can be found at
<!--l. 139--><p class="indent"> <a
href="http://www.glsetup.com/" >http://www.glsetup.com/</a>.
<!--l. 142--><p class="indent"> We did not try this ourselfes, but would suggest it for those completely
lost.
<h3 class="sectionHead"><span class="titlemark">C.5</span> <a
name="x1-67000C.5"></a>3DFX chip based cards under Linux</h3>
<!--l. 149--><p class="noindent">Notably, with 3DFX<a
name="dx1-67001"></a> now having been taken over by NVIDIA<a
name="dx1-67002"></a>, manufacturer&#8217;s support
already has disappeared. However with XFree86-4.x (with x at least being greater than 1)
Voodoo3 cards are known to be pretty usable in 16 bit colour mode. Newer cards should
work fine as well. If you are still running a version of Xfree86 3.X and run into problems,
consider an upgrade. The recent distributions by Debian or SuSE have been reported to
work well.
<h3 class="sectionHead"><span class="titlemark">C.6</span> <a
name="x1-68000C.6"></a>ATI chip based cards under Linux</h3>
<!--l. 160--><p class="noindent">There is excellent support for ATI chips in XFree86-4.1 and greater. Lots of AGP boards
based on the Rage128 chip - from simple Rage128 board to ATI Xpert2000 - are pretty
usuable for FlightGear. Since XFree86-4.1 you can use early Radeon chips - up to
Radeon7500 with XFree86-4.2.
<h3 class="sectionHead"><span class="titlemark">C.7</span> <a
name="x1-69000C.7"></a>Building your own OpenGL support under Linux</h3>
<!--l. 169--><p class="noindent">Setting up proper OpenGL support with a recent Linux distribution should be pretty
simple. As an example SuSE ships everything you need plus some small shell scripts to
adjust the missing bits automagically. If you just want to execute prebuilt binaries of
FlightGear, then you&#8217;re done by using the supplied FlightGear package plus the
mandantory runtime libraries (and kernel modules). The package manager will tell you
which ones to choose.
<!--l. 176--><p class="indent"> In case you want to run a selfmade kernel, you want to compile FlightGear yourself,
you&#8217;re tweaking your X server configuration file yourself or you even run a homebrewn
Linux &#8221;distribution&#8221; (this means, you want to compile everything yourself), this chapter
might be useful for you.
<!--l. 181--><p class="indent"> Now let&#8217;s have a look at the parts that build OpenGL support on Linux. First there&#8217;s a
Linux kernel with support for your graphics adapter.
<!--l. 184--><p class="indent"> Examples on which graphics hardware is supported natively by Open Source drivers
are provided on
<!--l. 188--><p class="noindent"><a
href="http://dri.sourceforge.net/status.phtml." >http://dri.sourceforge.net/status.phtml.</a>
<!--l. 192--><p class="indent"> There are a few graphics chip families that are not directly or no more than partly
supported by XFree86, the X window implementation on Linux, because vendors don&#8217;t
like to provide programming information on their chips. In these cases - notably
IBM/DIAMOND/now: ATI FireGL graphics boards and NVIDIA GeForce based cards -
you depend on the manufacturers will to follow the ongoing development of the XFree86
graphics display infrastructure. These boards might prove to deliver impressing
performance but in many cases - considering the CPU&#8217;s speed you find in today&#8217;s
PC&#8217;s - you have many choices which all lead to respectable performance of
FlightGear.
<!--l. 202--><p class="indent"> As long as you use a distribution provided kernel, you can expect to find all
necessary kernel modules at the approriate location. If you compile the kernel yourself,
then you have to take care of two submenues in the kernel configuration menue. You&#8217;ll
find them in the &#8221;Character devices&#8221; menue. Please notice that AGP support is not
compulsory for hardware accelerated OpenGL support on Linux. This also works quite
fine with some PCI cards (3dfx Voodoo3 PCI for example, in case you still own one).
Although every modern PC graphics card utilizes the AGP &#8217;bus&#8217; for fast data
transfer.
<!--l. 211--><p class="indent"> Besides &#8221;AGP Support&#8221; for your chipset - you might want to ask your mainboard
manual which one is on - you defnitely want to activate &#8221;Direct Rendering Manager&#8221;
for your garphics board. Please note that recent releases of XFree86 - namely
4.1.0 and higher might not be supported by the DRI included in older Linux
kernels. Also newer 2.4.x kernels from 2.4.8 up to 2.4.17 do not support DRI in
XFree86-4.0.x.
<!--l. 218--><p class="indent"> After building and installing your kernel modules and the kernel itself this task might
be completed by loading the &#8217;agpgart&#8217; module manually or, in case you linked it into the
kernel, by a reboot in purpose to get the new kernel up and running. While booting your
kernel on an AGP capable mainboard you may expect boot messages like this one:
<!--l. 226--><p class="noindent"><span
class="pcrr7t---109">&gt; Linux agpgart interface v0.99 (c) Jeff Hartmann</span>
<br class="newline"><span
class="pcrr7t---109">&gt; gpgart: Maximum main memory to use for agp memory:</span>
<span
class="pcrr7t---109">439M</span>
<br class="newline"><span
class="pcrr7t---109">&gt; agpgart: Detected Via Apollo Pro chipset</span>
<br class="newline"><span
class="pcrr7t---109">&gt; agpgart: AGP aperture is 64M @ 0xe4000000</span>
If you don&#8217;t encounter such messages on Linux kernel boot, then you might have
missed the right chipset. Part one of activation hardware accelerated OpenGL support on
your Linux system is now completed.
<!--l. 237--><p class="indent"> The second part consists of configuring your X server for OpenGL. This is not a big
deal as it simply consists of to instructions to load the appropriate modules on startup of
the X server. This is done by editing the configuration file <span
class="pcrr7t---109">/etc/X11/XF86Config</span>.
Today&#8217;s Linux distributions are supposed to provide a tool that does this job
for you on your demand. Please make shure there are these two instructions:
<!--l. 245--><p class="indent"> <span
class="pcrr7t---109">Load ''glx''</span>
<br class="newline"><span
class="pcrr7t---109">Load ''dri''</span>
<!--l. 249--><p class="noindent">in the &#8221;Module&#8221; section your X server configuration file. If everything is right the X
server will take care of loading the appropriate Linux kernel module for DRI support of
your graphics card. The right Linux kernel module name is determined by the &#8217;Driver&#8217;
statement in the &#8221;Device&#8221; section of the XF86Config. Please see four samples on how
such a &#8221;Device&#8221; section should look like:
<!--l. 258--><p class="noindent">Section &#8221;Device&#8221;
<!--l. 262--><p class="indent"> BoardName &#8221;3dfx Voodoo3 PCI&#8221;
<!--l. 264--><p class="indent"> BusID &#8221;0:8:0&#8221;
<!--l. 266--><p class="indent"> Driver &#8221;tdfx&#8221;
<!--l. 268--><p class="indent"> Identifier &#8221;Device[0]&#8221;
<!--l. 270--><p class="indent"> Screen 0
<!--l. 272--><p class="indent"> VendorName &#8221;3Dfx&#8221;
<!--l. 275--><p class="noindent">EndSection
<!--l. 279--><p class="noindent">Section &#8221;Device&#8221;
<!--l. 283--><p class="indent"> BoardName &#8221;ATI Xpert2000 AGP&#8221;
<!--l. 285--><p class="indent"> BusID &#8221;1:0:0&#8221;
<!--l. 287--><p class="indent"> Driver &#8221;ati&#8221;
<!--l. 289--><p class="indent"> Option &#8221;AGPMode&#8221; &#8221;1&#8221;
<!--l. 291--><p class="indent"> Identifier &#8221;Device[0]&#8221;
<!--l. 293--><p class="indent"> Screen 0
<!--l. 295--><p class="indent"> VendorName &#8221;ATI&#8221;
<!--l. 297--><p class="noindent">EndSection
<!--l. 301--><p class="noindent">Section &#8221;Device&#8221;
<!--l. 304--><p class="indent"> BoardName &#8221;ATI Radeon 32 MB DDR AGP&#8221;
<!--l. 306--><p class="indent"> BusID &#8221;1:0:0&#8221;
<!--l. 308--><p class="indent"> Driver &#8221;radeon&#8221;
<!--l. 310--><p class="indent"> Option &#8221;AGPMode&#8221; &#8221;4&#8221;
<!--l. 312--><p class="indent"> Identifier &#8221;Device[0]&#8221;
<!--l. 314--><p class="indent"> Screen 0
<!--l. 316--><p class="indent"> VendorName &#8221;ATI&#8221;
<!--l. 318--><p class="noindent">EndSection
<!--l. 322--><p class="indent"> By using the Option &#8221;AGPMode&#8221; you can tune AGP performance as long as the
mainboard and the graphics card permit. The BusID on AGP systems should always be
set to &#8221;1:0:0&#8221; - because you only have one AGP slot on your board - whereas the PCI
BusID differs with the slot your graphics card has been applied to. &#8217;lspci&#8217; might be your
friend in desperate situations. Also a look at the end of /var/log/XFree86.0.log, which
should be written on X server startup, should point to the PCI slot where your card
resides.
<!--l. 330--><p class="indent"> This has been the second part of installing hardware accelerated OpenGL support on
your Linux box.
<!--l. 333--><p class="indent"> The third part carries two subparts: First there are the OpenGL runtime libraries,
sufficient to run existing appliactions. For compiling FlightGear you also need the suiting
develoment headers. As compiling the whole X window system is not subject to this
abstract we expect that your distribution ships the necessary libraries and headers. In case
you told your package manager to install some sort of OpenGL support you are
supposed to find some OpenGL test utilities, at least there should be &#8217;glxinfo&#8217; or
&#8217;gl-info&#8217;.
<!--l. 342--><p class="indent"> These commandline utilities are useful to say if the previous steps where successfull.
If they refuse to start, then your package manager missed something because he should
have known that these utilities usually depend on the existence of OpenGL runtime
libraries. If they start, then you&#8217;re one step ahead. Now watch the output of this tool and
and have a look at the line that starts with
<!--l. 349--><p class="indent"> OpenGL renderer string:
<!--l. 351--><p class="indent"> If you find something like
<!--l. 354--><p class="indent"> <span
class="pcrr7t---109">OpenGL renderer string: FireGL2 / FireGL3 (Pentium3)</span>
<!--l. 357--><p class="noindent">or
<!--l. 361--><p class="indent"> <span
class="pcrr7t---109">OpenGL renderer string: Mesa DRI Voodoo3 20000224</span>
<!--l. 364--><p class="noindent">or
<!--l. 368--><p class="indent"> <span
class="pcrr7t---109">OpenGL renderer string: Mesa DRI Radeon 20010402 AGP 4x</span>
<span
class="pcrr7t---109">x86</span>
<!--l. 371--><p class="indent"> <span
class="pcrr7t---109">OpenGL renderer string: Mesa GLX Indirect</span>
<!--l. 374--><p class="noindent">mind the word &#8217;Indirect&#8217;, then it&#8217;s you who missed something, because OpenGL gets
dealt with in a software library running solely on your CPU. In this case you might want
to have a closer look at the preceding paragraphs of this chapter. Now please make
shure all necessary libraries are at their proper location. You will need three
OpenGL libraries for running FlightGear. In most cases you will find them in
/usr/lib/:
<!--l. 383--><p class="indent"> <span
class="pcrr7t---109">/usr/lib/libGL.so.1</span>
<!--l. 385--><p class="indent"> <span
class="pcrr7t---109">/usr/lib/libGLU.so.1</span>
<!--l. 387--><p class="indent"> <span
class="pcrr7t---109">/usr/lib/libglut.so.3</span>
<!--l. 389--><p class="indent"> These may be the libraries itself or symlinks to appropriate libraries located in some
other directories. Depending on the distribution you use these libraries might be shipped
in different packages. SuSE for example ships libGL in package &#8217;xf86_glx&#8217;, libGLU in
&#8217;xf86glu&#8217; and libglut in &#8217;mesaglut&#8217;. Additionally for FlightGear you need libplib which is
part of the &#8217;plib&#8217; package.
<!--l. 396--><p class="indent"> For compiling FlightGear yourself - as already mentioned - you need the appropriate
header files which often reside in /usr/include/GL/. Two are necessary for libGL and they
come in - no, not &#8217;xf86glx-devel&#8217; (o.k., they do but they do not work correctly) but in
&#8217;mesa-devel&#8217;:
<!--l. 402--><p class="indent"> <span
class="pcrr7t---109">/usr/include/GL/gl.h</span>
<!--l. 404--><p class="indent"> <span
class="pcrr7t---109">/usr/include/GL/glx.h</span>
<!--l. 407--><p class="noindent">One comes with libGLU in &#8217;xf86glu-devel&#8217;:
<!--l. 411--><p class="indent"> <span
class="pcrr7t---109">/usr/include/GL/glu.h</span>
<!--l. 414--><p class="indent"> and one with libglut in &#8217;mesaglut-devel&#8217;
<!--l. 417--><p class="indent"> <span
class="pcrr7t---109">/usr/include/GL/glut.h</span>
<!--l. 420--><p class="indent"> The &#8217;plib&#8217; package comes with some more libraries and headers that are too
many to be mentioned here. If all this is present and you have a comfortable
compiler environment, then you are ready to compile FlightGear and enjoy the
result.
<!--l. 426--><p class="indent"> Further information on OpenGL issues of specific XFree86 releases is avaliable here:
<!--l. 430--><p class="indent"> <a
href="http://www.xfree86.org/<RELEASE" NUMBER>/DRI.html >http://www.xfree86.org/<2F>RELEASE NUMBER<45>/DRI.html</a>
<!--l. 433--><p class="noindent">Additional reading on DRI:
<!--l. 437--><p class="indent"> <a
href="http://www.precisioninsight.com/piinsights.html" >http://www.precisioninsight.com/piinsights.html</a>
<!--l. 440--><p class="noindent">In case you are missing some &#8217;spare parts&#8217;:
<!--l. 444--><p class="indent"> <a
href="http://dri.sourceforge.net/res.phtml" >http://dri.sourceforge.net/res.phtml</a>
<h3 class="sectionHead"><span class="titlemark">C.8</span> <a
name="x1-70000C.8"></a>OpenGL on MacIntosh</h3>
<!--l. 451--><p class="noindent">OpenGL is pre-installed on Mac OS 9.x and later. You may find a newer version than the
one installed for Mac OS 9.x at
<!--l. 454--><p class="indent"> <a
href="file:www.apple.com/opengl.html" >www.apple.com/opengl</a>
<!--l. 457--><p class="indent"> You should receive the updates automatically for Mac OX 10.x.
<!--l. 460--><p class="noindent"><span
class="ptmb7t---109">One final word: </span>We would recommend that you test your OpenGL<a
name="dx1-70001"></a> support with one
of the programs that accompany the drivers, to be absolutely confident that
it is functioning well. There are also many little programs, often available as
screen savers, that can be used for testing. It is important that you are confident
in your graphics acceleration because <span
class="ptmbi7t---109">FlightGear </span>will try to run the card as
fast as possible. If your drivers aren&#8217;t working well, or are unstable, you will
have difficulty tracking down the source of any problems and have a frustrating
time.
<a
name="Q1-1-71"></a>
<h2 class="likechapterHead"><a
name="x1-71000C.8"></a><span
class="ptmr7t---90">Index</span></h2>
<div class="theindex"><span
class="ptmr7t---90">.fgfsrc, </span><a
href="getstart.html#dx1-29004" ><span
class="ptmr7t---90">1</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53083" ><span
class="ptmr7t---90">2</span></a> <br>
<span
class="ptmr7t---90">3DFX, </span><a
href="getstart.html#dx1-60002" ><span
class="ptmr7t---90">3</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-67001" ><span
class="ptmr7t---90">4</span></a>
<br>
<p class="theindex">
<span
class="ptmr7t---90">A1 Free Sounds, </span><a
href="getstart.html#dx1-54004" ><span
class="ptmr7t---90">5</span></a> <br>
<span
class="ptmr7t---90">add-on scenery, </span><a
href="getstart.html#dx1-22002" ><span
class="ptmr7t---90">6</span></a> <br>
<span
class="ptmr7t---90">ADF, </span><a
href="getstart.html#dx1-47028" ><span
class="ptmr7t---90">7</span></a> <br>
<span
class="ptmr7t---90">Adler, Mark, </span><a
href="getstart.html#dx1-54030" ><span
class="ptmr7t---90">8</span></a> <br>
<span
class="ptmr7t---90">Aeronautical Information Manual, </span><a
href="getstart.html#dx1-50001" ><span
class="ptmr7t---90">9</span></a> <br>
<span
class="ptmr7t---90">aileron, </span><a
href="getstart.html#dx1-45009" ><span
class="ptmr7t---90">10</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47012" ><span
class="ptmr7t---90">11</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47013" ><span
class="ptmr7t---90">12</span></a> <br>
<span
class="ptmr7t---90">aileron indicator, </span><a
href="getstart.html#dx1-48007" ><span
class="ptmr7t---90">13</span></a> <br>
<span
class="ptmr7t---90">air traffic facilities, </span><a
href="getstart.html#dx1-47033" ><span
class="ptmr7t---90">14</span></a> <br>
<span
class="ptmr7t---90">aircraft model, </span><a
href="getstart.html#dx1-32005" ><span
class="ptmr7t---90">15</span></a> <br>
<span
class="ptmr7t---90">aircraft model directory, </span><a
href="getstart.html#x1-330004.4.4" ><span
class="ptmr7t---90">16</span></a> <br>
<span
class="ptmr7t---90">airport, </span><a
href="getstart.html#dx1-34003" ><span
class="ptmr7t---90">17</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-55001" ><span
class="ptmr7t---90">18</span></a> <br>
<span
class="ptmr7t---90">airport code, </span><a
href="getstart.html#dx1-34004" ><span
class="ptmr7t---90">19</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-34005" ><span
class="ptmr7t---90">20</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-49002" ><span
class="ptmr7t---90">21</span></a> <br>
<span
class="ptmr7t---90">airport ID, </span><a
href="getstart.html#dx1-46011" ><span
class="ptmr7t---90">22</span></a> <br>
<span
class="ptmr7t---90">airspeed indicator, </span><a
href="getstart.html#dx1-47007" ><span
class="ptmr7t---90">23</span></a> <br>
<span
class="ptmr7t---90">Alonzo, Raul, </span><a
href="getstart.html#dx1-54005" ><span
class="ptmr7t---90">24</span></a> <br>
<span
class="ptmr7t---90">altimeter, </span><a
href="getstart.html#dx1-47016" ><span
class="ptmr7t---90">25</span></a> <br>
<span
class="ptmr7t---90">altitude hold, </span><a
href="getstart.html#dx1-45023" ><span
class="ptmr7t---90">26</span></a> <br>
<span
class="ptmr7t---90">America, Michele, </span><a
href="getstart.html#dx1-53029" ><span
class="ptmr7t---90">27</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54006" ><span
class="ptmr7t---90">28</span></a> <br>
<span
class="ptmr7t---90">anonymous cvs, </span><a
href="getstart.html#dx1-7006" ><span
class="ptmr7t---90">29</span></a> <br>
<span
class="ptmr7t---90">anti-alised HUD lines, </span><a
href="getstart.html#dx1-31004" ><span
class="ptmr7t---90">30</span></a> <br>
<span
class="ptmr7t---90">antialiasing, </span><a
href="getstart.html#dx1-46010" ><span
class="ptmr7t---90">31</span></a> <br>
<span
class="ptmr7t---90">artificial horizon, </span><a
href="getstart.html#dx1-47003" ><span
class="ptmr7t---90">32</span></a> <br>
<span
class="ptmr7t---90">astronomy code, </span><a
href="getstart.html#dx1-53022" ><span
class="ptmr7t---90">33</span></a> <br>
<span
class="ptmr7t---90">ATC, </span><a
href="getstart.html#dx1-55003" ><span
class="ptmr7t---90">34</span></a> <br>
<span
class="ptmr7t---90">ATI, </span><a
href="getstart.html#x1-68000C.6" ><span
class="ptmr7t---90">35</span></a> <br>
<span
class="ptmr7t---90">attitude indicator, </span><a
href="getstart.html#dx1-47004" ><span
class="ptmr7t---90">36</span></a> <br>
<span
class="ptmr7t---90">audio library, </span><a
href="getstart.html#dx1-54051" ><span
class="ptmr7t---90">37</span></a> <br>
<span
class="ptmr7t---90">audio support, </span><a
href="getstart.html#dx1-53050" ><span
class="ptmr7t---90">38</span></a> <br>
<span
class="ptmr7t---90">auto coordination, </span><a
href="getstart.html#dx1-30012" ><span
class="ptmr7t---90">39</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47015" ><span
class="ptmr7t---90">40</span></a> <br>
<span
class="ptmr7t---90">autopilot, </span><a
href="getstart.html#dx1-45021" ><span
class="ptmr7t---90">41</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45027" ><span
class="ptmr7t---90">42</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-46012" ><span
class="ptmr7t---90">43</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53040" ><span
class="ptmr7t---90">44</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54037" ><span
class="ptmr7t---90">45</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54049" ><span
class="ptmr7t---90">46</span></a> <br>
<span
class="ptmr7t---90">autopilot controls, </span><a
href="getstart.html#dx1-45022" ><span
class="ptmr7t---90">47</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45028" ><span
class="ptmr7t---90">48</span></a> <br>
<span
class="ptmr7t---90">autothrottle, </span><a
href="getstart.html#dx1-45025" ><span
class="ptmr7t---90">49</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">bank, </span><a
href="getstart.html#dx1-47006" ><span
class="ptmr7t---90">50</span></a> <br>
<span
class="ptmr7t---90">base package, </span><a
href="getstart.html#dx1-2002" ><span
class="ptmr7t---90">51</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-22005" ><span
class="ptmr7t---90">52</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;installation, </span><a
href="getstart.html#dx1-15001" ><span
class="ptmr7t---90">53</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-150002.5" ><span
class="ptmr7t---90">54</span></a> <br>
<span
class="ptmr7t---90">Basler, Michael, </span><a
href="getstart.html#dx1-54008" ><span
class="ptmr7t---90">55</span></a> <br>
<span
class="ptmr7t---90">Berndt, Jon, S., </span><a
href="getstart.html#dx1-53075" ><span
class="ptmr7t---90">56</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53078" ><span
class="ptmr7t---90">57</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53098" ><span
class="ptmr7t---90">58</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54009" ><span
class="ptmr7t---90">59</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56004" ><span
class="ptmr7t---90">60</span></a> <br>
<span
class="ptmr7t---90">binaries, </span><a
href="getstart.html#dx1-10005" ><span
class="ptmr7t---90">61</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-17001" ><span
class="ptmr7t---90">62</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Debian, </span><a
href="getstart.html#dx1-20001" ><span
class="ptmr7t---90">63</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;directory, </span><a
href="getstart.html#dx1-12020" ><span
class="ptmr7t---90">64</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Macintosh, </span><a
href="getstart.html#dx1-19001" ><span
class="ptmr7t---90">65</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;pre-compiled, </span><a
href="getstart.html#dx1-2014" ><span
class="ptmr7t---90">66</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;SGI Irix, </span><a
href="getstart.html#dx1-21001" ><span
class="ptmr7t---90">67</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Windows, </span><a
href="getstart.html#dx1-18001" ><span
class="ptmr7t---90">68</span></a> <br>
<span
class="ptmr7t---90">binaries, pre-compiled, </span><a
href="getstart.html#dx1-10003" ><span
class="ptmr7t---90">69</span></a> <br>
<span
class="ptmr7t---90">binary directory, </span><a
href="getstart.html#dx1-11004" ><span
class="ptmr7t---90">70</span></a> <br>
<span
class="ptmr7t---90">binary distribution, </span><a
href="getstart.html#dx1-2001" ><span
class="ptmr7t---90">71</span></a> <br>
<span
class="ptmr7t---90">bleeding edge snapshots, </span><a
href="getstart.html#dx1-16001" ><span
class="ptmr7t---90">72</span></a> <br>
<span
class="ptmr7t---90">Bleisch, Paul, </span><a
href="getstart.html#dx1-54011" ><span
class="ptmr7t---90">73</span></a> <br>
<span
class="ptmr7t---90">Boeing 747, </span><a
href="getstart.html#dx1-8010" ><span
class="ptmr7t---90">74</span></a> <br>
<span
class="ptmr7t---90">brakes, </span><a
href="getstart.html#dx1-45031" ><span
class="ptmr7t---90">75</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45033" ><span
class="ptmr7t---90">76</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54080" ><span
class="ptmr7t---90">77</span></a> <br>
<span
class="ptmr7t---90">branch, developmental, </span><a
href="getstart.html#dx1-7003" ><span
class="ptmr7t---90">78</span></a> <br>
<span
class="ptmr7t---90">branch, stable, </span><a
href="getstart.html#dx1-7002" ><span
class="ptmr7t---90">79</span></a> <br>
<span
class="ptmr7t---90">Brennan, Jim, </span><a
href="getstart.html#dx1-54012" ><span
class="ptmr7t---90">80</span></a> <br>
<span
class="ptmr7t---90">Bright, Bernie, </span><a
href="getstart.html#dx1-54013" ><span
class="ptmr7t---90">81</span></a> <br>
<span
class="ptmr7t---90">BSD UNIX, </span><a
href="getstart.html#dx1-5015" ><span
class="ptmr7t---90">82</span></a> <br>
<span
class="ptmr7t---90">Buckel, Bernhard, </span><a
href="getstart.html#dx1-54014" ><span
class="ptmr7t---90">83</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56003" ><span
class="ptmr7t---90">84</span></a> <br>
<span
class="ptmr7t---90">Buckle, Gene, </span><a
href="getstart.html#dx1-54015" ><span
class="ptmr7t---90">85</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">callsign, </span><a
href="getstart.html#dx1-38003" ><span
class="ptmr7t---90">86</span></a> <br>
<span
class="ptmr7t---90">Carmichael, Ralph, </span><a
href="getstart.html#dx1-54017" ><span
class="ptmr7t---90">87</span></a> <br>
<span
class="ptmr7t---90">CD-ROM, </span><a
href="getstart.html#dx1-22004" ><span
class="ptmr7t---90">88</span></a> <br>
<span
class="ptmr7t---90">Cessna, </span><a
href="getstart.html#dx1-48004" ><span
class="ptmr7t---90">89</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54090" ><span
class="ptmr7t---90">90</span></a> <br>
<span
class="ptmr7t---90">Cessna 172, </span><a
href="getstart.html#dx1-8004" ><span
class="ptmr7t---90">91</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-8008" ><span
class="ptmr7t---90">92</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45026" ><span
class="ptmr7t---90">93</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53031" ><span
class="ptmr7t---90">94</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53071" ><span
class="ptmr7t---90">95</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53073" ><span
class="ptmr7t---90">96</span></a> <br>
<span
class="ptmr7t---90">Cessna 182, </span><a
href="getstart.html#dx1-8005" ><span
class="ptmr7t---90">97</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-8009" ><span
class="ptmr7t---90">98</span></a> <br>
<span
class="ptmr7t---90">Cessna 310, </span><a
href="getstart.html#dx1-8006" ><span
class="ptmr7t---90">99</span></a> <br>
<span
class="ptmr7t---90">Cessna C172, </span><a
href="getstart.html#dx1-8012" ><span
class="ptmr7t---90">100</span></a> <br>
<span
class="ptmr7t---90">Chauveau, Didier, </span><a
href="getstart.html#dx1-54018" ><span
class="ptmr7t---90">101</span></a> <br>
<span
class="ptmr7t---90">Check, John, </span><a
href="getstart.html#dx1-42005" ><span
class="ptmr7t---90">102</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47049" ><span
class="ptmr7t---90">103</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53086" ><span
class="ptmr7t---90">104</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53088" ><span
class="ptmr7t---90">105</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54019" ><span
class="ptmr7t---90">106</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56007" ><span
class="ptmr7t---90">107</span></a> <br>
<span
class="ptmr7t---90">Cherokee flight model, </span><a
href="getstart.html#dx1-54088" ><span
class="ptmr7t---90">108</span></a> <br>
<span
class="ptmr7t---90">clock, </span><a
href="getstart.html#dx1-47021" ><span
class="ptmr7t---90">109</span></a> <br>
<span
class="ptmr7t---90">cloud layer, </span><a
href="getstart.html#dx1-35005" ><span
class="ptmr7t---90">110</span></a> <br>
<span
class="ptmr7t---90">clouds, </span><a
href="getstart.html#dx1-53064" ><span
class="ptmr7t---90">111</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54093" ><span
class="ptmr7t---90">112</span></a> <br>
<span
class="ptmr7t---90">CodeWarrior, </span><a
href="getstart.html#dx1-14009" ><span
class="ptmr7t---90">113</span></a> <br>
<span
class="ptmr7t---90">COMM1, </span><a
href="getstart.html#dx1-47030" ><span
class="ptmr7t---90">114</span></a> <br>
<span
class="ptmr7t---90">COMM2, </span><a
href="getstart.html#dx1-47031" ><span
class="ptmr7t---90">115</span></a> <br>
<span
class="ptmr7t---90">command line options, </span><a
href="getstart.html#dx1-29001" ><span
class="ptmr7t---90">116</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-29002" ><span
class="ptmr7t---90">117</span></a> <br>
<span
class="ptmr7t---90">communication radio, </span><a
href="getstart.html#dx1-47029" ><span
class="ptmr7t---90">118</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47032" ><span
class="ptmr7t---90">119</span></a> <br>
<span
class="ptmr7t---90">compiler, </span><a
href="getstart.html#dx1-6024" ><span
class="ptmr7t---90">120</span></a> <br>
<span
class="ptmr7t---90">compiling, </span><a
href="getstart.html#x1-100002" ><span
class="ptmr7t---90">121</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;IRIX, </span><a
href="getstart.html#x1-140002.4" ><span
class="ptmr7t---90">122</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Linux, </span><a
href="getstart.html#x1-120002.2" ><span
class="ptmr7t---90">123</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;MacIntosh, </span><a
href="getstart.html#x1-130002.3" ><span
class="ptmr7t---90">124</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;other systems, </span><a
href="getstart.html#x1-140002.4" ><span
class="ptmr7t---90">125</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Solaris, </span><a
href="getstart.html#x1-140002.4" ><span
class="ptmr7t---90">126</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Windows, </span><a
href="getstart.html#x1-120002.2" ><span
class="ptmr7t---90">127</span></a> <br>
<span
class="ptmr7t---90">configure, </span><a
href="getstart.html#dx1-12015" ><span
class="ptmr7t---90">128</span></a> <br>
<span
class="ptmr7t---90">contributors, </span><a
href="getstart.html#dx1-54001" ><span
class="ptmr7t---90">129</span></a> <br>
<span
class="ptmr7t---90">control device, </span><a
href="getstart.html#dx1-30008" ><span
class="ptmr7t---90">130</span></a> <br>
<span
class="ptmr7t---90">Cornish, Dave, </span><a
href="getstart.html#dx1-53080" ><span
class="ptmr7t---90">131</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54020" ><span
class="ptmr7t---90">132</span></a> <br>
<span
class="ptmr7t---90">CVS snapshots, </span><a
href="getstart.html#dx1-7004" ><span
class="ptmr7t---90">133</span></a> <br>
<span
class="ptmr7t---90">cvs, anonymous, </span><a
href="getstart.html#dx1-7007" ><span
class="ptmr7t---90">134</span></a> <br>
<span
class="ptmr7t---90">Cygnus, </span><a
href="getstart.html#dx1-6026" ><span
class="ptmr7t---90">135</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54116" ><span
class="ptmr7t---90">136</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-61004" ><span
class="ptmr7t---90">137</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;development tools, </span><a
href="getstart.html#dx1-11001" ><span
class="ptmr7t---90">138</span></a> <br>
<span
class="ptmr7t---90">Cygwin </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;setup, </span><a
href="getstart.html#dx1-11002" ><span
class="ptmr7t---90">139</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Debian, </span><a
href="getstart.html#dx1-10010" ><span
class="ptmr7t---90">140</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-20003" ><span
class="ptmr7t---90">141</span></a> <br>
<span
class="ptmr7t---90">default settings, </span><a
href="getstart.html#dx1-30002" ><span
class="ptmr7t---90">142</span></a> <br>
<span
class="ptmr7t---90">Delise, Oliver, </span><a
href="getstart.html#dx1-53057" ><span
class="ptmr7t---90">143</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53099" ><span
class="ptmr7t---90">144</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54021" ><span
class="ptmr7t---90">145</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56008" ><span
class="ptmr7t---90">146</span></a> <br>
<span
class="ptmr7t---90">Denker, John, </span><a
href="getstart.html#dx1-50007" ><span
class="ptmr7t---90">147</span></a> <br>
<span
class="ptmr7t---90">Detonator reference drivers, </span><a
href="getstart.html#dx1-64002" ><span
class="ptmr7t---90">148</span></a> <br>
<span
class="ptmr7t---90">development environment, </span><a
href="getstart.html#x1-110002.1" ><span
class="ptmr7t---90">149</span></a> <br>
<span
class="ptmr7t---90">differential braking, </span><a
href="getstart.html#dx1-45036" ><span
class="ptmr7t---90">150</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45037" ><span
class="ptmr7t---90">151</span></a> <br>
<span
class="ptmr7t---90">Direct3D, </span><a
href="getstart.html#dx1-6008" ><span
class="ptmr7t---90">152</span></a> <br>
<span
class="ptmr7t---90">directory structure, </span><a
href="getstart.html#dx1-15002" ><span
class="ptmr7t---90">153</span></a> <br>
<span
class="ptmr7t---90">disk space, </span><a
href="getstart.html#dx1-6014" ><span
class="ptmr7t---90">154</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-11003" ><span
class="ptmr7t---90">155</span></a> <br>
<span
class="ptmr7t---90">display options, </span><a
href="getstart.html#dx1-45015" ><span
class="ptmr7t---90">156</span></a> <br>
<span
class="ptmr7t---90">distribution </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;binary, </span><a
href="getstart.html#dx1-7008" ><span
class="ptmr7t---90">157</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-10006" ><span
class="ptmr7t---90">158</span></a> <br>
<span
class="ptmr7t---90">documentation, </span><a
href="getstart.html#dx1-5025" ><span
class="ptmr7t---90">159</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;installation, </span><a
href="getstart.html#dx1-23001" ><span
class="ptmr7t---90">160</span></a> <br>
<span
class="ptmr7t---90">DOS, </span><a
href="getstart.html#dx1-53005" ><span
class="ptmr7t---90">161</span></a> <br>
<span
class="ptmr7t---90">Doue, Jean-Francois, </span><a
href="getstart.html#dx1-54023" ><span
class="ptmr7t---90">162</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Eberly, Dave, </span><a
href="getstart.html#dx1-54024" ><span
class="ptmr7t---90">163</span></a> <br>
<span
class="ptmr7t---90">elevation indicator, </span><a
href="getstart.html#dx1-48009" ><span
class="ptmr7t---90">164</span></a> <br>
<span
class="ptmr7t---90">elevator trim, </span><a
href="getstart.html#dx1-45010" ><span
class="ptmr7t---90">165</span></a> <br>
<span
class="ptmr7t---90">engine </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;starting, </span><a
href="getstart.html#dx1-44001" ><span
class="ptmr7t---90">166</span></a> <br>
<span
class="ptmr7t---90">engine controls, </span><a
href="getstart.html#dx1-45029" ><span
class="ptmr7t---90">167</span></a> <br>
<span
class="ptmr7t---90">environment variable, </span><a
href="getstart.html#dx1-27003" ><span
class="ptmr7t---90">168</span></a> <br>
<span
class="ptmr7t---90">environment variables, </span><a
href="getstart.html#dx1-26003" ><span
class="ptmr7t---90">169</span></a> <br>
<span
class="ptmr7t---90">Evans, Francine, </span><a
href="getstart.html#dx1-54025" ><span
class="ptmr7t---90">170</span></a> <br>
<span
class="ptmr7t---90">Everitt, Oscar, </span><a
href="getstart.html#dx1-54026" ><span
class="ptmr7t---90">171</span></a> <br>
<span
class="ptmr7t---90">exit, </span><a
href="getstart.html#dx1-46007" ><span
class="ptmr7t---90">172</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-49003" ><span
class="ptmr7t---90">173</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">FAA, </span><a
href="getstart.html#dx1-50002" ><span
class="ptmr7t---90">174</span></a> <br>
<span
class="ptmr7t---90">FAA Training Book, </span><a
href="getstart.html#dx1-50003" ><span
class="ptmr7t---90">175</span></a> <br>
<span
class="ptmr7t---90">FAQ, </span><a
href="getstart.html#dx1-2004" ><span
class="ptmr7t---90">176</span></a> <br>
<span
class="ptmr7t---90">FDM, </span><a
href="getstart.html#dx1-54010" ><span
class="ptmr7t---90">177</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;external, </span><a
href="getstart.html#dx1-8015" ><span
class="ptmr7t---90">178</span></a> <br>
<span
class="ptmr7t---90">field of view, </span><a
href="getstart.html#dx1-35006" ><span
class="ptmr7t---90">179</span></a> <br>
<span
class="ptmr7t---90">Finney, Bruce, </span><a
href="getstart.html#dx1-54028" ><span
class="ptmr7t---90">180</span></a> <br>
<span
class="ptmr7t---90">flaps, </span><a
href="getstart.html#dx1-45038" ><span
class="ptmr7t---90">181</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47046" ><span
class="ptmr7t---90">182</span></a> <br>
<span
class="ptmr7t---90">flight dynamics model, </span><a
href="getstart.html#dx1-8001" ><span
class="ptmr7t---90">183</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-320004.4.3" ><span
class="ptmr7t---90">184</span></a> <br>
<span
class="ptmr7t---90">flight instrument, </span><a
href="getstart.html#dx1-47001" ><span
class="ptmr7t---90">185</span></a> <br>
<span
class="ptmr7t---90">flight model, </span><a
href="getstart.html#dx1-8002" ><span
class="ptmr7t---90">186</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-32002" ><span
class="ptmr7t---90">187</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53072" ><span
class="ptmr7t---90">188</span></a> <br>
<span
class="ptmr7t---90">flight models, </span><a
href="getstart.html#dx1-8003" ><span
class="ptmr7t---90">189</span></a> <br>
<span
class="ptmr7t---90">flight planner, </span><a
href="getstart.html#dx1-53060" ><span
class="ptmr7t---90">190</span></a> <br>
<span
class="ptmr7t---90">flight schools, </span><a
href="getstart.html#x1-500005.7" ><span
class="ptmr7t---90">191</span></a> <br>
<span
class="ptmr7t---90">Flight simulator </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;civilian, </span><a
href="getstart.html#dx1-5003" ><span
class="ptmr7t---90">192</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5008" ><span
class="ptmr7t---90">193</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;free, </span><a
href="getstart.html#dx1-53011" ><span
class="ptmr7t---90">194</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;multi-platform, </span><a
href="getstart.html#dx1-5004" ><span
class="ptmr7t---90">195</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5010" ><span
class="ptmr7t---90">196</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;open, </span><a
href="getstart.html#dx1-5005" ><span
class="ptmr7t---90">197</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5018" ><span
class="ptmr7t---90">198</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;user-extensible, </span><a
href="getstart.html#dx1-5007" ><span
class="ptmr7t---90">199</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5024" ><span
class="ptmr7t---90">200</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;user-sported, </span><a
href="getstart.html#dx1-5006" ><span
class="ptmr7t---90">201</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;user-supported, </span><a
href="getstart.html#dx1-5023" ><span
class="ptmr7t---90">202</span></a> <br>
<span
class="ptmr7t---90">FlightGear, </span><a
href="getstart.html#dx1-53096" ><span
class="ptmr7t---90">203</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;directory structure, </span><a
href="getstart.html#dx1-15003" ><span
class="ptmr7t---90">204</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;versions, </span><a
href="getstart.html#dx1-7001" ><span
class="ptmr7t---90">205</span></a> <br>
<span
class="ptmr7t---90">FlightGear documentation, </span><a
href="getstart.html#dx1-9002" ><span
class="ptmr7t---90">206</span></a> <br>
<span
class="ptmr7t---90">FlightGear Flight School, </span><a
href="getstart.html#dx1-9006" ><span
class="ptmr7t---90">207</span></a> <br>
<span
class="ptmr7t---90">FlightGear Getting Started Guide, </span><a
href="getstart.html#dx1-46015" ><span
class="ptmr7t---90">208</span></a> <br>
<span
class="ptmr7t---90">FlightGear Programmer&#8217;s Guide, </span><a
href="getstart.html#dx1-9004" ><span
class="ptmr7t---90">209</span></a> <br>
<span
class="ptmr7t---90">FlightGear Scenery Design Guide, </span><a
href="getstart.html#dx1-9005" ><span
class="ptmr7t---90">210</span></a> <br>
<span
class="ptmr7t---90">FlightGear Website, </span><a
href="getstart.html#dx1-9001" ><span
class="ptmr7t---90">211</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53105" ><span
class="ptmr7t---90">212</span></a> <br>
<span
class="ptmr7t---90">fog, </span><a
href="getstart.html#dx1-35001" ><span
class="ptmr7t---90">213</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-35002" ><span
class="ptmr7t---90">214</span></a> <br>
<span
class="ptmr7t---90">fog effects, </span><a
href="getstart.html#dx1-54053" ><span
class="ptmr7t---90">215</span></a> <br>
<span
class="ptmr7t---90">frame rate, </span><a
href="getstart.html#dx1-6010" ><span
class="ptmr7t---90">216</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-35003" ><span
class="ptmr7t---90">217</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53034" ><span
class="ptmr7t---90">218</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53039" ><span
class="ptmr7t---90">219</span></a> <br>
<span
class="ptmr7t---90">FreeBSD, </span><a
href="getstart.html#dx1-54034" ><span
class="ptmr7t---90">220</span></a> <br>
<span
class="ptmr7t---90">FreeGLUT, </span><a
href="getstart.html#dx1-14005" ><span
class="ptmr7t---90">221</span></a> <br>
<span
class="ptmr7t---90">frozen state, </span><a
href="getstart.html#dx1-30007" ><span
class="ptmr7t---90">222</span></a> <br>
<span
class="ptmr7t---90">FS98, </span><a
href="getstart.html#dx1-54027" ><span
class="ptmr7t---90">223</span></a> <br>
<span
class="ptmr7t---90">fuel indicator, </span><a
href="getstart.html#dx1-47022" ><span
class="ptmr7t---90">224</span></a> <br>
<span
class="ptmr7t---90">full screen display, </span><a
href="getstart.html#dx1-30004" ><span
class="ptmr7t---90">225</span></a> <br>
<span
class="ptmr7t---90">full screen mode, </span><a
href="getstart.html#dx1-35007" ><span
class="ptmr7t---90">226</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45019" ><span
class="ptmr7t---90">227</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Gailly, Jean-loup, </span><a
href="getstart.html#dx1-54029" ><span
class="ptmr7t---90">228</span></a> <br>
<span
class="ptmr7t---90">GameGLUT, </span><a
href="getstart.html#dx1-54104" ><span
class="ptmr7t---90">229</span></a> <br>
<span
class="ptmr7t---90">Garg, Mohit, </span><a
href="getstart.html#dx1-54032" ><span
class="ptmr7t---90">230</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56009" ><span
class="ptmr7t---90">231</span></a> <br>
<span
class="ptmr7t---90">gauge, </span><a
href="getstart.html#dx1-47002" ><span
class="ptmr7t---90">232</span></a> <br>
<span
class="ptmr7t---90">gear, </span><a
href="getstart.html#dx1-45034" ><span
class="ptmr7t---90">233</span></a> <br>
<span
class="ptmr7t---90">Geforce, </span><a
href="getstart.html#dx1-2009" ><span
class="ptmr7t---90">234</span></a> <br>
<span
class="ptmr7t---90">Gellekum, Thomas, </span><a
href="getstart.html#dx1-54033" ><span
class="ptmr7t---90">235</span></a> <br>
<span
class="ptmr7t---90">Girish, Neetha, </span><a
href="getstart.html#dx1-54035" ><span
class="ptmr7t---90">236</span></a> <br>
<span
class="ptmr7t---90">GLIDE, </span><a
href="getstart.html#dx1-60003" ><span
class="ptmr7t---90">237</span></a> <br>
<span
class="ptmr7t---90">GNU C++, </span><a
href="getstart.html#dx1-6025" ><span
class="ptmr7t---90">238</span></a> <br>
<span
class="ptmr7t---90">Gnu Public License, </span><a
href="getstart.html#dx1-5020" ><span
class="ptmr7t---90">239</span></a> <br>
<span
class="ptmr7t---90">Goeke-Smith, Jeff, </span><a
href="getstart.html#dx1-53041" ><span
class="ptmr7t---90">240</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54036" ><span
class="ptmr7t---90">241</span></a> <br>
<span
class="ptmr7t---90">Gold, Michael, I., </span><a
href="getstart.html#dx1-54038" ><span
class="ptmr7t---90">242</span></a> <br>
<span
class="ptmr7t---90">GPL, </span><a
href="getstart.html#dx1-5019" ><span
class="ptmr7t---90">243</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5021" ><span
class="ptmr7t---90">244</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5022" ><span
class="ptmr7t---90">245</span></a> <br>
<span
class="ptmr7t---90">graphics card, </span><a
href="getstart.html#dx1-6003" ><span
class="ptmr7t---90">246</span></a> <br>
<span
class="ptmr7t---90">graphics library, </span><a
href="getstart.html#dx1-62001" ><span
class="ptmr7t---90">247</span></a> <br>
<span
class="ptmr7t---90">graphics routines, </span><a
href="getstart.html#dx1-53009" ><span
class="ptmr7t---90">248</span></a> <br>
<span
class="ptmr7t---90">gyro compass, </span><a
href="getstart.html#dx1-47019" ><span
class="ptmr7t---90">249</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Habibe, </span><a
href="getstart.html#dx1-54040" ><span
class="ptmr7t---90">250</span></a> <br>
<span
class="ptmr7t---90">haze, </span><a
href="getstart.html#dx1-35004" ><span
class="ptmr7t---90">251</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-35008" ><span
class="ptmr7t---90">252</span></a> <br>
<span
class="ptmr7t---90">head up display, </span><a
href="getstart.html#dx1-48002" ><span
class="ptmr7t---90">253</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-480005.5" ><span
class="ptmr7t---90">254</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53028" ><span
class="ptmr7t---90">255</span></a> <br>
<span
class="ptmr7t---90">heading hold, </span><a
href="getstart.html#dx1-45024" ><span
class="ptmr7t---90">256</span></a> <br>
<span
class="ptmr7t---90">height, </span><a
href="getstart.html#dx1-48013" ><span
class="ptmr7t---90">257</span></a> <br>
<span
class="ptmr7t---90">help, </span><a
href="getstart.html#dx1-46014" ><span
class="ptmr7t---90">258</span></a> <br>
<span
class="ptmr7t---90">Hill, Mike, </span><a
href="getstart.html#dx1-54041" ><span
class="ptmr7t---90">259</span></a> <br>
<span
class="ptmr7t---90">History, </span><a
href="getstart.html#x1-53000A.1" ><span
class="ptmr7t---90">260</span></a> <br>
<span
class="ptmr7t---90">Hofman, Eric, </span><a
href="getstart.html#dx1-14006" ><span
class="ptmr7t---90">261</span></a> <br>
<span
class="ptmr7t---90">Hofman, Erik, </span><a
href="getstart.html#dx1-21002" ><span
class="ptmr7t---90">262</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54042" ><span
class="ptmr7t---90">263</span></a> <br>
<span
class="ptmr7t---90">hot air balloon, </span><a
href="getstart.html#dx1-54060" ><span
class="ptmr7t---90">264</span></a> <br>
<span
class="ptmr7t---90">Hotchkiss, Charlie, </span><a
href="getstart.html#dx1-53030" ><span
class="ptmr7t---90">265</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54043" ><span
class="ptmr7t---90">266</span></a> <br>
<span
class="ptmr7t---90">HUD, </span><a
href="getstart.html#dx1-31002" ><span
class="ptmr7t---90">267</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-31003" ><span
class="ptmr7t---90">268</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-360004.4.7" ><span
class="ptmr7t---90">269</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-48001" ><span
class="ptmr7t---90">270</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-48003" ><span
class="ptmr7t---90">271</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-48005" ><span
class="ptmr7t---90">272</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-48014" ><span
class="ptmr7t---90">273</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53027" ><span
class="ptmr7t---90">274</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54007" ><span
class="ptmr7t---90">275</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54044" ><span
class="ptmr7t---90">276</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">IFR, </span><a
href="getstart.html#dx1-47041" ><span
class="ptmr7t---90">277</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-50005" ><span
class="ptmr7t---90">278</span></a> <br>
<span
class="ptmr7t---90">inclinometer, </span><a
href="getstart.html#dx1-47010" ><span
class="ptmr7t---90">279</span></a> <br>
<span
class="ptmr7t---90">initial heading, </span><a
href="getstart.html#dx1-34008" ><span
class="ptmr7t---90">280</span></a> <br>
<span
class="ptmr7t---90">install directory, </span><a
href="getstart.html#dx1-12003" ><span
class="ptmr7t---90">281</span></a> <br>
<span
class="ptmr7t---90">instrument flight rules, </span><a
href="getstart.html#dx1-47042" ><span
class="ptmr7t---90">282</span></a> <br>
<span
class="ptmr7t---90">instrument panel, </span><a
href="getstart.html#dx1-31005" ><span
class="ptmr7t---90">283</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-31006" ><span
class="ptmr7t---90">284</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45016" ><span
class="ptmr7t---90">285</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-470005.4" ><span
class="ptmr7t---90">286</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53046" ><span
class="ptmr7t---90">287</span></a> <br>
<span
class="ptmr7t---90">Internet, </span><a
href="getstart.html#dx1-53059" ><span
class="ptmr7t---90">288</span></a> <br>
<span
class="ptmr7t---90">IRIX, </span><a
href="getstart.html#dx1-14002" ><span
class="ptmr7t---90">289</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Jackson, Bruce, </span><a
href="getstart.html#dx1-53015" ><span
class="ptmr7t---90">290</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54045" ><span
class="ptmr7t---90">291</span></a> <br>
<span
class="ptmr7t---90">joystick, </span><a
href="getstart.html#dx1-30009" ><span
class="ptmr7t---90">292</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-30010" ><span
class="ptmr7t---90">293</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-42002" ><span
class="ptmr7t---90">294</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-43002" ><span
class="ptmr7t---90">295</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45002" ><span
class="ptmr7t---90">296</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53052" ><span
class="ptmr7t---90">297</span></a> <br>
<span
class="ptmr7t---90">joystick settings, </span><a
href="getstart.html#dx1-53085" ><span
class="ptmr7t---90">298</span></a> <br>
<span
class="ptmr7t---90">joysticks, </span><a
href="getstart.html#dx1-6017" ><span
class="ptmr7t---90">299</span></a> <br>
<span
class="ptmr7t---90">JSBSim, </span><a
href="getstart.html#dx1-32003" ><span
class="ptmr7t---90">300</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Kaaven, Ove, </span><a
href="getstart.html#dx1-20002" ><span
class="ptmr7t---90">301</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54047" ><span
class="ptmr7t---90">302</span></a> <br>
<span
class="ptmr7t---90">Kaszeta, Richard, </span><a
href="getstart.html#dx1-54048" ><span
class="ptmr7t---90">303</span></a> <br>
<span
class="ptmr7t---90">key bindings </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;configuration, </span><a
href="getstart.html#dx1-45042" ><span
class="ptmr7t---90">304</span></a> <br>
<span
class="ptmr7t---90">keyboard, </span><a
href="getstart.html#dx1-43005" ><span
class="ptmr7t---90">305</span></a> <br>
<span
class="ptmr7t---90">keyboard controls, </span><a
href="getstart.html#dx1-43001" ><span
class="ptmr7t---90">306</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45001" ><span
class="ptmr7t---90">307</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45006" ><span
class="ptmr7t---90">308</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45007" ><span
class="ptmr7t---90">309</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;miscellaneous, </span><a
href="getstart.html#dx1-45030" ><span
class="ptmr7t---90">310</span></a> <br>
<span
class="ptmr7t---90">keyboard.xml, </span><a
href="getstart.html#dx1-45043" ><span
class="ptmr7t---90">311</span></a> <br>
<span
class="ptmr7t---90">Knienieder, Tom, </span><a
href="getstart.html#dx1-54050" ><span
class="ptmr7t---90">312</span></a> <br>
<span
class="ptmr7t---90">Koradi, Reto, </span><a
href="getstart.html#dx1-54052" ><span
class="ptmr7t---90">313</span></a> <br>
<span
class="ptmr7t---90">Korpela, Eric, </span><a
href="getstart.html#dx1-53003" ><span
class="ptmr7t---90">314</span></a> <br>
<span
class="ptmr7t---90">Kuehne, Bob, </span><a
href="getstart.html#dx1-54054" ><span
class="ptmr7t---90">315</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Laird, Kyler B., </span><a
href="getstart.html#dx1-54055" ><span
class="ptmr7t---90">316</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56010" ><span
class="ptmr7t---90">317</span></a> <br>
<span
class="ptmr7t---90">landing gear, </span><a
href="getstart.html#dx1-45035" ><span
class="ptmr7t---90">318</span></a> <br>
<span
class="ptmr7t---90">LaRCsim, </span><a
href="getstart.html#dx1-53014" ><span
class="ptmr7t---90">319</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53017" ><span
class="ptmr7t---90">320</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53021" ><span
class="ptmr7t---90">321</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53069" ><span
class="ptmr7t---90">322</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54046" ><span
class="ptmr7t---90">323</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54070" ><span
class="ptmr7t---90">324</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54089" ><span
class="ptmr7t---90">325</span></a> <br>
<span
class="ptmr7t---90">latitude, </span><a
href="getstart.html#dx1-48015" ><span
class="ptmr7t---90">326</span></a> <br>
<span
class="ptmr7t---90">Launching Flighgear </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Mac OS X, </span><a
href="getstart.html#dx1-28001" ><span
class="ptmr7t---90">327</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Windows, </span><a
href="getstart.html#dx1-27001" ><span
class="ptmr7t---90">328</span></a> <br>
<span
class="ptmr7t---90">Launching Flightgear </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Linux, </span><a
href="getstart.html#dx1-26001" ><span
class="ptmr7t---90">329</span></a> <br>
<span
class="ptmr7t---90">leaflet, </span><a
href="getstart.html#dx1-2005" ><span
class="ptmr7t---90">330</span></a> <br>
<span
class="ptmr7t---90">Learjet 24, </span><a
href="getstart.html#dx1-8013" ><span
class="ptmr7t---90">331</span></a> <br>
<span
class="ptmr7t---90">Lee, Eunice, </span><a
href="getstart.html#dx1-54099" ><span
class="ptmr7t---90">332</span></a> <br>
<span
class="ptmr7t---90">Linux, </span><a
href="getstart.html#dx1-2012" ><span
class="ptmr7t---90">333</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5012" ><span
class="ptmr7t---90">334</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5027" ><span
class="ptmr7t---90">335</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6020" ><span
class="ptmr7t---90">336</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6022" ><span
class="ptmr7t---90">337</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-10002" ><span
class="ptmr7t---90">338</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-10008" ><span
class="ptmr7t---90">339</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53004" ><span
class="ptmr7t---90">340</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-63001" ><span
class="ptmr7t---90">341</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-63002" ><span
class="ptmr7t---90">342</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-63000C.1" ><span
class="ptmr7t---90">343</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-67000C.5" ><span
class="ptmr7t---90">344</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-68000C.6" ><span
class="ptmr7t---90">345</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-69000C.7" ><span
class="ptmr7t---90">346</span></a> <br>
<span
class="ptmr7t---90">Linux distributions, </span><a
href="getstart.html#dx1-10009" ><span
class="ptmr7t---90">347</span></a> <br>
<span
class="ptmr7t---90">load flight, </span><a
href="getstart.html#dx1-46003" ><span
class="ptmr7t---90">348</span></a> <br>
<span
class="ptmr7t---90">longitude, </span><a
href="getstart.html#dx1-48016" ><span
class="ptmr7t---90">349</span></a> <br>
<span
class="ptmr7t---90">Luff, David, </span><a
href="getstart.html#dx1-53087" ><span
class="ptmr7t---90">350</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54056" ><span
class="ptmr7t---90">351</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Mac OS 9, </span><a
href="getstart.html#dx1-19003" ><span
class="ptmr7t---90">352</span></a> <br>
<span
class="ptmr7t---90">Mac OS X, </span><a
href="getstart.html#dx1-19006" ><span
class="ptmr7t---90">353</span></a> <br>
<span
class="ptmr7t---90">Macintosh, </span><a
href="getstart.html#dx1-2011" ><span
class="ptmr7t---90">354</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-14008" ><span
class="ptmr7t---90">355</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-19002" ><span
class="ptmr7t---90">356</span></a> <br>
<span
class="ptmr7t---90">magnetic compass, </span><a
href="getstart.html#dx1-47020" ><span
class="ptmr7t---90">357</span></a> <br>
<span
class="ptmr7t---90">mailing lists, </span><a
href="getstart.html#dx1-54003" ><span
class="ptmr7t---90">358</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-58002" ><span
class="ptmr7t---90">359</span></a> <br>
<span
class="ptmr7t---90">map, clickable, </span><a
href="getstart.html#dx1-53054" ><span
class="ptmr7t---90">360</span></a> <br>
<span
class="ptmr7t---90">marker, inner, </span><a
href="getstart.html#dx1-47037" ><span
class="ptmr7t---90">361</span></a> <br>
<span
class="ptmr7t---90">marker, middle, </span><a
href="getstart.html#dx1-47038" ><span
class="ptmr7t---90">362</span></a> <br>
<span
class="ptmr7t---90">marker, outer, </span><a
href="getstart.html#dx1-47036" ><span
class="ptmr7t---90">363</span></a> <br>
<span
class="ptmr7t---90">Mayer, Christian, </span><a
href="getstart.html#dx1-53062" ><span
class="ptmr7t---90">364</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53077" ><span
class="ptmr7t---90">365</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53100" ><span
class="ptmr7t---90">366</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54057" ><span
class="ptmr7t---90">367</span></a> <br>
<span
class="ptmr7t---90">Megginson, David, </span><a
href="getstart.html#dx1-53048" ><span
class="ptmr7t---90">368</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53082" ><span
class="ptmr7t---90">369</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53089" ><span
class="ptmr7t---90">370</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54061" ><span
class="ptmr7t---90">371</span></a> <br>
<span
class="ptmr7t---90">menu, </span><a
href="getstart.html#dx1-53043" ><span
class="ptmr7t---90">372</span></a> <br>
<span
class="ptmr7t---90">menu entries, </span><a
href="getstart.html#dx1-46001" ><span
class="ptmr7t---90">373</span></a> <br>
<span
class="ptmr7t---90">menu system, </span><a
href="getstart.html#dx1-55002" ><span
class="ptmr7t---90">374</span></a> <br>
<span
class="ptmr7t---90">MetaKit, </span><a
href="getstart.html#dx1-54113" ><span
class="ptmr7t---90">375</span></a> <br>
<span
class="ptmr7t---90">Metro Works, </span><a
href="getstart.html#dx1-54109" ><span
class="ptmr7t---90">376</span></a> <br>
<span
class="ptmr7t---90">Microsoft, </span><a
href="getstart.html#dx1-5001" ><span
class="ptmr7t---90">377</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-5002" ><span
class="ptmr7t---90">378</span></a> <br>
<span
class="ptmr7t---90">Mitchell, Eric, </span><a
href="getstart.html#dx1-53026" ><span
class="ptmr7t---90">379</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54064" ><span
class="ptmr7t---90">380</span></a> <br>
<span
class="ptmr7t---90">mixture, </span><a
href="getstart.html#dx1-47045" ><span
class="ptmr7t---90">381</span></a> <br>
<span
class="ptmr7t---90">Moore Cameron, </span><a
href="getstart.html#dx1-57002" ><span
class="ptmr7t---90">382</span></a> <br>
<span
class="ptmr7t---90">Moore, Cameron, </span><a
href="getstart.html#dx1-54063" ><span
class="ptmr7t---90">383</span></a> <br>
<span
class="ptmr7t---90">mouse, </span><a
href="getstart.html#dx1-43006" ><span
class="ptmr7t---90">384</span></a> <br>
<span
class="ptmr7t---90">mouse interface, </span><a
href="getstart.html#dx1-30005" ><span
class="ptmr7t---90">385</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-30006" ><span
class="ptmr7t---90">386</span></a> <br>
<span
class="ptmr7t---90">mouse, actions, </span><a
href="getstart.html#x1-490005.6" ><span
class="ptmr7t---90">387</span></a> <br>
<span
class="ptmr7t---90">MS DevStudio, </span><a
href="getstart.html#dx1-61003" ><span
class="ptmr7t---90">388</span></a> <br>
<span
class="ptmr7t---90">MSVC, </span><a
href="getstart.html#dx1-54016" ><span
class="ptmr7t---90">389</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-61002" ><span
class="ptmr7t---90">390</span></a> <br>
<span
class="ptmr7t---90">multi-lingual conversion tools, </span><a
href="getstart.html#dx1-54058" ><span
class="ptmr7t---90">391</span></a> <br>
<span
class="ptmr7t---90">multiplayer code, </span><a
href="getstart.html#dx1-53056" ><span
class="ptmr7t---90">392</span></a> <br>
<span
class="ptmr7t---90">Murr, David, </span><a
href="getstart.html#dx1-53001" ><span
class="ptmr7t---90">393</span></a> <br>
<span
class="ptmr7t---90">Murta, Alan, </span><a
href="getstart.html#dx1-54066" ><span
class="ptmr7t---90">394</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">NAV, </span><a
href="getstart.html#dx1-47026" ><span
class="ptmr7t---90">395</span></a> <br>
<span
class="ptmr7t---90">navaids, </span><a
href="getstart.html#dx1-47043" ><span
class="ptmr7t---90">396</span></a> <br>
<span
class="ptmr7t---90">Navion, </span><a
href="getstart.html#dx1-53018" ><span
class="ptmr7t---90">397</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53070" ><span
class="ptmr7t---90">398</span></a> <br>
<span
class="ptmr7t---90">NDB, </span><a
href="getstart.html#dx1-47027" ><span
class="ptmr7t---90">399</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47035" ><span
class="ptmr7t---90">400</span></a> <br>
<span
class="ptmr7t---90">Nelson, Phil, </span><a
href="getstart.html#dx1-54067" ><span
class="ptmr7t---90">401</span></a> <br>
<span
class="ptmr7t---90">network, </span><a
href="getstart.html#dx1-46013" ><span
class="ptmr7t---90">402</span></a> <br>
<span
class="ptmr7t---90">network options, </span><a
href="getstart.html#dx1-38001" ><span
class="ptmr7t---90">403</span></a> <br>
<span
class="ptmr7t---90">networking code, </span><a
href="getstart.html#dx1-53055" ><span
class="ptmr7t---90">404</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54022" ><span
class="ptmr7t---90">405</span></a> <br>
<span
class="ptmr7t---90">networking support, </span><a
href="getstart.html#dx1-12017" ><span
class="ptmr7t---90">406</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-12018" ><span
class="ptmr7t---90">407</span></a> <br>
<span
class="ptmr7t---90">nightly snapshots, </span><a
href="getstart.html#dx1-7005" ><span
class="ptmr7t---90">408</span></a> <br>
<span
class="ptmr7t---90">Novikov, Alexei, </span><a
href="getstart.html#dx1-54068" ><span
class="ptmr7t---90">409</span></a> <br>
<span
class="ptmr7t---90">NumLock, </span><a
href="getstart.html#dx1-45005" ><span
class="ptmr7t---90">410</span></a> <br>
<span
class="ptmr7t---90">NVIDIA, </span><a
href="getstart.html#dx1-2007" ><span
class="ptmr7t---90">411</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-64004" ><span
class="ptmr7t---90">412</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-67002" ><span
class="ptmr7t---90">413</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;drivers, </span><a
href="getstart.html#dx1-62008" ><span
class="ptmr7t---90">414</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Linux drivers, </span><a
href="getstart.html#dx1-63003" ><span
class="ptmr7t---90">415</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Windows drivers, </span><a
href="getstart.html#dx1-64003" ><span
class="ptmr7t---90">416</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">offset, </span><a
href="getstart.html#dx1-35012" ><span
class="ptmr7t---90">417</span></a> <br>
<span
class="ptmr7t---90">Olson, Curt, </span><a
href="getstart.html#dx1-22003" ><span
class="ptmr7t---90">418</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53010" ><span
class="ptmr7t---90">419</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53025" ><span
class="ptmr7t---90">420</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53037" ><span
class="ptmr7t---90">421</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53049" ><span
class="ptmr7t---90">422</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53053" ><span
class="ptmr7t---90">423</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53058" ><span
class="ptmr7t---90">424</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53061" ><span
class="ptmr7t---90">425</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53101" ><span
class="ptmr7t---90">426</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54069" ><span
class="ptmr7t---90">427</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56002" ><span
class="ptmr7t---90">428</span></a> <br>
<span
class="ptmr7t---90">OpenGL, </span><a
href="getstart.html#dx1-2003" ><span
class="ptmr7t---90">429</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-2006" ><span
class="ptmr7t---90">430</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6006" ><span
class="ptmr7t---90">431</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6007" ><span
class="ptmr7t---90">432</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6009" ><span
class="ptmr7t---90">433</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6011" ><span
class="ptmr7t---90">434</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-9003" ><span
class="ptmr7t---90">435</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53016" ><span
class="ptmr7t---90">436</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53035" ><span
class="ptmr7t---90">437</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53038" ><span
class="ptmr7t---90">438</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53047" ><span
class="ptmr7t---90">439</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53090" ><span
class="ptmr7t---90">440</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53091" ><span
class="ptmr7t---90">441</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54039" ><span
class="ptmr7t---90">442</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-59002" ><span
class="ptmr7t---90">443</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-62002" ><span
class="ptmr7t---90">444</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-62003" ><span
class="ptmr7t---90">445</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-62004" ><span
class="ptmr7t---90">446</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-64001" ><span
class="ptmr7t---90">447</span></a><span
class="ptmr7t---90">,</span>
<a
href="getstart.html#x1-69000C.7" ><span
class="ptmr7t---90">448</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-70001" ><span
class="ptmr7t---90">449</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;drivers, </span><a
href="getstart.html#dx1-6013" ><span
class="ptmr7t---90">450</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;libraries, </span><a
href="getstart.html#dx1-14004" ><span
class="ptmr7t---90">451</span></a> <br>
<span
class="ptmr7t---90">OpenGL drivers, </span><a
href="getstart.html#dx1-62006" ><span
class="ptmr7t---90">452</span></a> <br>
<span
class="ptmr7t---90">OpenGL Setup, </span><a
href="getstart.html#dx1-66001" ><span
class="ptmr7t---90">453</span></a> <br>
<span
class="ptmr7t---90">Operating Systems, </span><a
href="getstart.html#dx1-5011" ><span
class="ptmr7t---90">454</span></a> <br>
<span
class="ptmr7t---90">options </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;aircraft model directory, </span><a
href="getstart.html#dx1-33001" ><span
class="ptmr7t---90">455</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;debugging, </span><a
href="getstart.html#dx1-41001" ><span
class="ptmr7t---90">456</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;features, </span><a
href="getstart.html#dx1-31001" ><span
class="ptmr7t---90">457</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;flight model, </span><a
href="getstart.html#dx1-32001" ><span
class="ptmr7t---90">458</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;general, </span><a
href="getstart.html#dx1-30001" ><span
class="ptmr7t---90">459</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;HUD, </span><a
href="getstart.html#x1-360004.4.7" ><span
class="ptmr7t---90">460</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;initial position, </span><a
href="getstart.html#dx1-34001" ><span
class="ptmr7t---90">461</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;IO, </span><a
href="getstart.html#dx1-40001" ><span
class="ptmr7t---90">462</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;joystick, </span><a
href="getstart.html#dx1-42001" ><span
class="ptmr7t---90">463</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;network, </span><a
href="getstart.html#dx1-38002" ><span
class="ptmr7t---90">464</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;orientation, </span><a
href="getstart.html#dx1-34002" ><span
class="ptmr7t---90">465</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;rendering, </span><a
href="getstart.html#x1-350004.4.6" ><span
class="ptmr7t---90">466</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;route, </span><a
href="getstart.html#dx1-39001" ><span
class="ptmr7t---90">467</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;time, </span><a
href="getstart.html#dx1-37002" ><span
class="ptmr7t---90">468</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;waypoint, </span><a
href="getstart.html#dx1-39002" ><span
class="ptmr7t---90">469</span></a> <br>
<span
class="ptmr7t---90">options, configure, </span><a
href="getstart.html#dx1-12016" ><span
class="ptmr7t---90">470</span></a> <br>
<span
class="ptmr7t---90">OS/2, </span><a
href="getstart.html#dx1-53006" ><span
class="ptmr7t---90">471</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">panel, </span><a
href="getstart.html#dx1-46009" ><span
class="ptmr7t---90">472</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-470005.4" ><span
class="ptmr7t---90">473</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54062" ><span
class="ptmr7t---90">474</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54077" ><span
class="ptmr7t---90">475</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;reconfiguration, </span><a
href="getstart.html#dx1-47047" ><span
class="ptmr7t---90">476</span></a> <br>
<span
class="ptmr7t---90">parking brake, </span><a
href="getstart.html#dx1-45032" ><span
class="ptmr7t---90">477</span></a> <br>
<span
class="ptmr7t---90">Paul, Brian, </span><a
href="getstart.html#dx1-54072" ><span
class="ptmr7t---90">478</span></a> <br>
<span
class="ptmr7t---90">pause, </span><a
href="getstart.html#dx1-45039" ><span
class="ptmr7t---90">479</span></a> <br>
<span
class="ptmr7t---90">pedal, </span><a
href="getstart.html#dx1-42004" ><span
class="ptmr7t---90">480</span></a> <br>
<span
class="ptmr7t---90">Peden, Tony, </span><a
href="getstart.html#dx1-53074" ><span
class="ptmr7t---90">481</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53102" ><span
class="ptmr7t---90">482</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54073" ><span
class="ptmr7t---90">483</span></a> <br>
<span
class="ptmr7t---90">Peel, Robin, </span><a
href="getstart.html#dx1-54074" ><span
class="ptmr7t---90">484</span></a> <br>
<span
class="ptmr7t---90">permissions, </span><a
href="getstart.html#dx1-60004" ><span
class="ptmr7t---90">485</span></a> <br>
<span
class="ptmr7t---90">Perry, Alex, </span><a
href="getstart.html#dx1-54075" ><span
class="ptmr7t---90">486</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56011" ><span
class="ptmr7t---90">487</span></a> <br>
<span
class="ptmr7t---90">pitch, </span><a
href="getstart.html#dx1-47005" ><span
class="ptmr7t---90">488</span></a> <br>
<span
class="ptmr7t---90">pitch indicator, </span><a
href="getstart.html#dx1-48006" ><span
class="ptmr7t---90">489</span></a> <br>
<span
class="ptmr7t---90">places to discover, </span><a
href="getstart.html#dx1-49001" ><span
class="ptmr7t---90">490</span></a> <br>
<span
class="ptmr7t---90">PLIB, </span><a
href="getstart.html#dx1-12006" ><span
class="ptmr7t---90">491</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-12007" ><span
class="ptmr7t---90">492</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53044" ><span
class="ptmr7t---90">493</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53051" ><span
class="ptmr7t---90">494</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53092" ><span
class="ptmr7t---90">495</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53093" ><span
class="ptmr7t---90">496</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;header files, </span><a
href="getstart.html#dx1-12008" ><span
class="ptmr7t---90">497</span></a> <br>
<span
class="ptmr7t---90">preferences, </span><a
href="getstart.html#dx1-29006" ><span
class="ptmr7t---90">498</span></a> <br>
<span
class="ptmr7t---90">problem report, </span><a
href="getstart.html#dx1-58001" ><span
class="ptmr7t---90">499</span></a> <br>
<span
class="ptmr7t---90">problems, </span><a
href="getstart.html#dx1-57001" ><span
class="ptmr7t---90">500</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;general, </span><a
href="getstart.html#dx1-59001" ><span
class="ptmr7t---90">501</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Linux, </span><a
href="getstart.html#dx1-60001" ><span
class="ptmr7t---90">502</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Windows, </span><a
href="getstart.html#dx1-61001" ><span
class="ptmr7t---90">503</span></a> <br>
<span
class="ptmr7t---90">programmers, </span><a
href="getstart.html#dx1-54002" ><span
class="ptmr7t---90">504</span></a> <br>
<span
class="ptmr7t---90">property manager, </span><a
href="getstart.html#dx1-53081" ><span
class="ptmr7t---90">505</span></a> <br>
<span
class="ptmr7t---90">proposal, </span><a
href="getstart.html#dx1-53002" ><span
class="ptmr7t---90">506</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Quake, </span><a
href="getstart.html#dx1-62007" ><span
class="ptmr7t---90">507</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">radio stack, </span><a
href="getstart.html#dx1-47024" ><span
class="ptmr7t---90">508</span></a> <br>
<span
class="ptmr7t---90">README.xmlpanel, </span><a
href="getstart.html#dx1-47048" ><span
class="ptmr7t---90">509</span></a> <br>
<span
class="ptmr7t---90">Reinhard, Friedemann, </span><a
href="getstart.html#dx1-53045" ><span
class="ptmr7t---90">510</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54076" ><span
class="ptmr7t---90">511</span></a> <br>
<span
class="ptmr7t---90">Reinholdtsen, Petter, </span><a
href="getstart.html#dx1-54078" ><span
class="ptmr7t---90">512</span></a> <br>
<span
class="ptmr7t---90">Rendon, Elizabeth, </span><a
href="getstart.html#dx1-54100" ><span
class="ptmr7t---90">513</span></a> <br>
<span
class="ptmr7t---90">reset flight, </span><a
href="getstart.html#dx1-46004" ><span
class="ptmr7t---90">514</span></a> <br>
<span
class="ptmr7t---90">Riley, William, </span><a
href="getstart.html#dx1-54079" ><span
class="ptmr7t---90">515</span></a> <br>
<span
class="ptmr7t---90">Ross, Andy, </span><a
href="getstart.html#dx1-53079" ><span
class="ptmr7t---90">516</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54081" ><span
class="ptmr7t---90">517</span></a> <br>
<span
class="ptmr7t---90">RPM indicator, </span><a
href="getstart.html#dx1-47018" ><span
class="ptmr7t---90">518</span></a> <br>
<span
class="ptmr7t---90">rudder, </span><a
href="getstart.html#dx1-45004" ><span
class="ptmr7t---90">519</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45011" ><span
class="ptmr7t---90">520</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47011" ><span
class="ptmr7t---90">521</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47014" ><span
class="ptmr7t---90">522</span></a> <br>
<span
class="ptmr7t---90">rudder indicator, </span><a
href="getstart.html#dx1-48008" ><span
class="ptmr7t---90">523</span></a> <br>
<span
class="ptmr7t---90">rudder pedals, </span><a
href="getstart.html#dx1-6019" ><span
class="ptmr7t---90">524</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-43004" ><span
class="ptmr7t---90">525</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">save flight, </span><a
href="getstart.html#dx1-46002" ><span
class="ptmr7t---90">526</span></a> <br>
<span
class="ptmr7t---90">scenery, </span><a
href="getstart.html#dx1-53019" ><span
class="ptmr7t---90">527</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53032" ><span
class="ptmr7t---90">528</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;add-on, </span><a
href="getstart.html#dx1-22001" ><span
class="ptmr7t---90">529</span></a> <br>
<span
class="ptmr7t---90">scenery directory </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;path, </span><a
href="getstart.html#dx1-30003" ><span
class="ptmr7t---90">530</span></a> <br>
<span
class="ptmr7t---90">scenery subsystem, </span><a
href="getstart.html#dx1-54071" ><span
class="ptmr7t---90">531</span></a> <br>
<span
class="ptmr7t---90">Schlyter, Paul, </span><a
href="getstart.html#dx1-54082" ><span
class="ptmr7t---90">532</span></a> <br>
<span
class="ptmr7t---90">Schoenemann, Chris, </span><a
href="getstart.html#dx1-54083" ><span
class="ptmr7t---90">533</span></a> <br>
<span
class="ptmr7t---90">Schubert, Phil, </span><a
href="getstart.html#dx1-54084" ><span
class="ptmr7t---90">534</span></a> <br>
<span
class="ptmr7t---90">Scott, Jeff, </span><a
href="getstart.html#dx1-54095" ><span
class="ptmr7t---90">535</span></a> <br>
<span
class="ptmr7t---90">screenshot, </span><a
href="getstart.html#dx1-45041" ><span
class="ptmr7t---90">536</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-46005" ><span
class="ptmr7t---90">537</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-46006" ><span
class="ptmr7t---90">538</span></a> <br>
<span
class="ptmr7t---90">See how it flies, </span><a
href="getstart.html#dx1-50008" ><span
class="ptmr7t---90">539</span></a> <br>
<span
class="ptmr7t---90">Sehgal, Bipin, </span><a
href="getstart.html#dx1-54096" ><span
class="ptmr7t---90">540</span></a> <br>
<span
class="ptmr7t---90">Selig, Michael, </span><a
href="getstart.html#dx1-54097" ><span
class="ptmr7t---90">541</span></a> <br>
<span
class="ptmr7t---90">SGI IRIX, </span><a
href="getstart.html#dx1-5016" ><span
class="ptmr7t---90">542</span></a> <br>
<span
class="ptmr7t---90">SGI Irix, </span><a
href="getstart.html#dx1-2013" ><span
class="ptmr7t---90">543</span></a> <br>
<span
class="ptmr7t---90">Shewchuk, Jonathan, </span><a
href="getstart.html#dx1-54085" ><span
class="ptmr7t---90">544</span></a> <br>
<span
class="ptmr7t---90">Sikic, Gordan, </span><a
href="getstart.html#dx1-54087" ><span
class="ptmr7t---90">545</span></a> <br>
<span
class="ptmr7t---90">SimGear, </span><a
href="getstart.html#dx1-12011" ><span
class="ptmr7t---90">546</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-12012" ><span
class="ptmr7t---90">547</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53094" ><span
class="ptmr7t---90">548</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53095" ><span
class="ptmr7t---90">549</span></a> <br>
<span
class="ptmr7t---90">Smith, Michael, </span><a
href="getstart.html#dx1-54091" ><span
class="ptmr7t---90">550</span></a> <br>
<span
class="ptmr7t---90">snapshots, </span><a
href="getstart.html#dx1-16002" ><span
class="ptmr7t---90">551</span></a> <br>
<span
class="ptmr7t---90">Solaris, </span><a
href="getstart.html#dx1-14003" ><span
class="ptmr7t---90">552</span></a> <br>
<span
class="ptmr7t---90">sound card, </span><a
href="getstart.html#dx1-6016" ><span
class="ptmr7t---90">553</span></a> <br>
<span
class="ptmr7t---90">sound effects, </span><a
href="getstart.html#dx1-6015" ><span
class="ptmr7t---90">554</span></a> <br>
<span
class="ptmr7t---90">source code, </span><a
href="getstart.html#dx1-5026" ><span
class="ptmr7t---90">555</span></a> <br>
<span
class="ptmr7t---90">speed, </span><a
href="getstart.html#dx1-48011" ><span
class="ptmr7t---90">556</span></a> <br>
<span
class="ptmr7t---90">Spott, Martin, </span><a
href="getstart.html#dx1-54105" ><span
class="ptmr7t---90">557</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56001" ><span
class="ptmr7t---90">558</span></a> <br>
<span
class="ptmr7t---90">Starting Flightgear </span><br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Linux, </span><a
href="getstart.html#dx1-26002" ><span
class="ptmr7t---90">559</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Mac OS X, </span><a
href="getstart.html#dx1-28002" ><span
class="ptmr7t---90">560</span></a> <br>
<span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;</span><span
class="ptmr7t---90">&nbsp;Windows, </span><a
href="getstart.html#dx1-27002" ><span
class="ptmr7t---90">561</span></a> <br>
<span
class="ptmr7t---90">starting time, </span><a
href="getstart.html#dx1-37004" ><span
class="ptmr7t---90">562</span></a> <br>
<span
class="ptmr7t---90">startup latitude, </span><a
href="getstart.html#dx1-34007" ><span
class="ptmr7t---90">563</span></a> <br>
<span
class="ptmr7t---90">startup longitude, </span><a
href="getstart.html#dx1-34006" ><span
class="ptmr7t---90">564</span></a> <br>
<span
class="ptmr7t---90">startup pitch angle, </span><a
href="getstart.html#dx1-34010" ><span
class="ptmr7t---90">565</span></a> <br>
<span
class="ptmr7t---90">startup roll angle, </span><a
href="getstart.html#dx1-34009" ><span
class="ptmr7t---90">566</span></a> <br>
<span
class="ptmr7t---90">Stuffit Expander, </span><a
href="getstart.html#dx1-19005" ><span
class="ptmr7t---90">567</span></a> <br>
<span
class="ptmr7t---90">Sun-OS, </span><a
href="getstart.html#dx1-5017" ><span
class="ptmr7t---90">568</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53008" ><span
class="ptmr7t---90">569</span></a> <br>
<span
class="ptmr7t---90">SuSE, </span><a
href="getstart.html#dx1-10011" ><span
class="ptmr7t---90">570</span></a> <br>
<span
class="ptmr7t---90">system requirements, </span><a
href="getstart.html#dx1-6001" ><span
class="ptmr7t---90">571</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6002" ><span
class="ptmr7t---90">572</span></a> <br>
<span
class="ptmr7t---90">system.fgfsrc, </span><a
href="getstart.html#dx1-29005" ><span
class="ptmr7t---90">573</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53084" ><span
class="ptmr7t---90">574</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Talsma, Durk, </span><a
href="getstart.html#dx1-53023" ><span
class="ptmr7t---90">575</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53063" ><span
class="ptmr7t---90">576</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54092" ><span
class="ptmr7t---90">577</span></a> <br>
<span
class="ptmr7t---90">TerraGear, </span><a
href="getstart.html#dx1-53097" ><span
class="ptmr7t---90">578</span></a> <br>
<span
class="ptmr7t---90">terrain, </span><a
href="getstart.html#dx1-35009" ><span
class="ptmr7t---90">579</span></a> <br>
<span
class="ptmr7t---90">text books, </span><a
href="getstart.html#x1-500005.7" ><span
class="ptmr7t---90">580</span></a> <br>
<span
class="ptmr7t---90">texture, </span><a
href="getstart.html#dx1-53033" ><span
class="ptmr7t---90">581</span></a> <br>
<span
class="ptmr7t---90">textures, </span><a
href="getstart.html#dx1-53024" ><span
class="ptmr7t---90">582</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54065" ><span
class="ptmr7t---90">583</span></a> <br>
<span
class="ptmr7t---90">Thomas, Jay, </span><a
href="getstart.html#dx1-54098" ><span
class="ptmr7t---90">584</span></a> <br>
<span
class="ptmr7t---90">throttle, </span><a
href="getstart.html#dx1-45008" ><span
class="ptmr7t---90">585</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47044" ><span
class="ptmr7t---90">586</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-48012" ><span
class="ptmr7t---90">587</span></a> <br>
<span
class="ptmr7t---90">thunderstorms, </span><a
href="getstart.html#dx1-53066" ><span
class="ptmr7t---90">588</span></a> <br>
<span
class="ptmr7t---90">Tilt view, </span><a
href="getstart.html#dx1-45017" ><span
class="ptmr7t---90">589</span></a> <br>
<span
class="ptmr7t---90">time, </span><a
href="getstart.html#dx1-37003" ><span
class="ptmr7t---90">590</span></a> <br>
<span
class="ptmr7t---90">time offset, </span><a
href="getstart.html#dx1-45040" ><span
class="ptmr7t---90">591</span></a> <br>
<span
class="ptmr7t---90">time options, </span><a
href="getstart.html#dx1-37001" ><span
class="ptmr7t---90">592</span></a> <br>
<span
class="ptmr7t---90">TNT, </span><a
href="getstart.html#dx1-2008" ><span
class="ptmr7t---90">593</span></a> <br>
<span
class="ptmr7t---90">Torvalds, Linus, </span><a
href="getstart.html#dx1-5028" ><span
class="ptmr7t---90">594</span></a> <br>
<span
class="ptmr7t---90">triangle program, </span><a
href="getstart.html#dx1-54086" ><span
class="ptmr7t---90">595</span></a> <br>
<span
class="ptmr7t---90">triangles, </span><a
href="getstart.html#dx1-36001" ><span
class="ptmr7t---90">596</span></a> <br>
<span
class="ptmr7t---90">trim, </span><a
href="getstart.html#dx1-45012" ><span
class="ptmr7t---90">597</span></a> <br>
<span
class="ptmr7t---90">Troester, Kai, </span><a
href="getstart.html#dx1-56012" ><span
class="ptmr7t---90">598</span></a> <br>
<span
class="ptmr7t---90">turn indicator, </span><a
href="getstart.html#dx1-47009" ><span
class="ptmr7t---90">599</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-48010" ><span
class="ptmr7t---90">600</span></a> <br>
<span
class="ptmr7t---90">Twin Otter, </span><a
href="getstart.html#dx1-8014" ><span
class="ptmr7t---90">601</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">U. S. Geological Survey, </span><a
href="getstart.html#dx1-53020" ><span
class="ptmr7t---90">602</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54101" ><span
class="ptmr7t---90">603</span></a> <br>
<span
class="ptmr7t---90">UIUC, </span><a
href="getstart.html#dx1-54094" ><span
class="ptmr7t---90">604</span></a> <br>
<span
class="ptmr7t---90">UIUC flight model, </span><a
href="getstart.html#dx1-8011" ><span
class="ptmr7t---90">605</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-32004" ><span
class="ptmr7t---90">606</span></a> <br>
<span
class="ptmr7t---90">UNIX, </span><a
href="getstart.html#dx1-6004" ><span
class="ptmr7t---90">607</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-10001" ><span
class="ptmr7t---90">608</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-10004" ><span
class="ptmr7t---90">609</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53013" ><span
class="ptmr7t---90">610</span></a> <br>
<span
class="ptmr7t---90">Unix, </span><a
href="getstart.html#dx1-14001" ><span
class="ptmr7t---90">611</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Vallevand, Mark, </span><a
href="getstart.html#dx1-54102" ><span
class="ptmr7t---90">612</span></a> <br>
<span
class="ptmr7t---90">van Sickle, Gary, R., </span><a
href="getstart.html#dx1-53103" ><span
class="ptmr7t---90">613</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54103" ><span
class="ptmr7t---90">614</span></a> <br>
<span
class="ptmr7t---90">velocity rages, </span><a
href="getstart.html#dx1-47008" ><span
class="ptmr7t---90">615</span></a> <br>
<span
class="ptmr7t---90">vertical speed indicator, </span><a
href="getstart.html#dx1-47017" ><span
class="ptmr7t---90">616</span></a> <br>
<span
class="ptmr7t---90">VFR, </span><a
href="getstart.html#dx1-47039" ><span
class="ptmr7t---90">617</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-50004" ><span
class="ptmr7t---90">618</span></a> <br>
<span
class="ptmr7t---90">video card, </span><a
href="getstart.html#dx1-62005" ><span
class="ptmr7t---90">619</span></a> <br>
<span
class="ptmr7t---90">view, </span><a
href="getstart.html#dx1-46008" ><span
class="ptmr7t---90">620</span></a> <br>
<span
class="ptmr7t---90">view directions, </span><a
href="getstart.html#dx1-45013" ><span
class="ptmr7t---90">621</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45014" ><span
class="ptmr7t---90">622</span></a> <br>
<span
class="ptmr7t---90">view frustrum culling, </span><a
href="getstart.html#dx1-53036" ><span
class="ptmr7t---90">623</span></a> <br>
<span
class="ptmr7t---90">view modes, </span><a
href="getstart.html#dx1-45018" ><span
class="ptmr7t---90">624</span></a> <br>
<span
class="ptmr7t---90">views, </span><a
href="getstart.html#dx1-53067" ><span
class="ptmr7t---90">625</span></a> <br>
<span
class="ptmr7t---90">Vine, Norman, </span><a
href="getstart.html#dx1-53042" ><span
class="ptmr7t---90">626</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53068" ><span
class="ptmr7t---90">627</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53104" ><span
class="ptmr7t---90">628</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54106" ><span
class="ptmr7t---90">629</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56005" ><span
class="ptmr7t---90">630</span></a> <br>
<span
class="ptmr7t---90">visibility, </span><a
href="getstart.html#dx1-45020" ><span
class="ptmr7t---90">631</span></a> <br>
<span
class="ptmr7t---90">Visual C++, </span><a
href="getstart.html#dx1-14007" ><span
class="ptmr7t---90">632</span></a> <br>
<span
class="ptmr7t---90">visual flight rules, </span><a
href="getstart.html#dx1-47040" ><span
class="ptmr7t---90">633</span></a> <br>
<span
class="ptmr7t---90">Voegtli, Roland, </span><a
href="getstart.html#dx1-54107" ><span
class="ptmr7t---90">634</span></a> <br>
<span
class="ptmr7t---90">Volpe, Carmelo, </span><a
href="getstart.html#dx1-54108" ><span
class="ptmr7t---90">635</span></a> <br>
<span
class="ptmr7t---90">VOR, </span><a
href="getstart.html#dx1-47025" ><span
class="ptmr7t---90">636</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47034" ><span
class="ptmr7t---90">637</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Walisser, Darrell, </span><a
href="getstart.html#dx1-19004" ><span
class="ptmr7t---90">638</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-54110" ><span
class="ptmr7t---90">639</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-56006" ><span
class="ptmr7t---90">640</span></a> <br>
<span
class="ptmr7t---90">weapon systems, </span><a
href="getstart.html#dx1-5009" ><span
class="ptmr7t---90">641</span></a> <br>
<span
class="ptmr7t---90">weather, </span><a
href="getstart.html#dx1-54059" ><span
class="ptmr7t---90">642</span></a> <br>
<span
class="ptmr7t---90">weather subsystem, </span><a
href="getstart.html#dx1-12019" ><span
class="ptmr7t---90">643</span></a> <br>
<span
class="ptmr7t---90">Williams, Ed, </span><a
href="getstart.html#dx1-54111" ><span
class="ptmr7t---90">644</span></a> <br>
<span
class="ptmr7t---90">window size, </span><a
href="getstart.html#dx1-35011" ><span
class="ptmr7t---90">645</span></a> <br>
<span
class="ptmr7t---90">Windows, </span><a
href="getstart.html#dx1-2010" ><span
class="ptmr7t---90">646</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6012" ><span
class="ptmr7t---90">647</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6021" ><span
class="ptmr7t---90">648</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-6023" ><span
class="ptmr7t---90">649</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-10007" ><span
class="ptmr7t---90">650</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-18002" ><span
class="ptmr7t---90">651</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-29003" ><span
class="ptmr7t---90">652</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-64000C.2" ><span
class="ptmr7t---90">653</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#x1-65000C.3" ><span
class="ptmr7t---90">654</span></a> <br>
<span
class="ptmr7t---90">Windows 95/98/ME, </span><a
href="getstart.html#dx1-5014" ><span
class="ptmr7t---90">655</span></a> <br>
<span
class="ptmr7t---90">Windows 95/NT, </span><a
href="getstart.html#dx1-53007" ><span
class="ptmr7t---90">656</span></a> <br>
<span
class="ptmr7t---90">Windows NT/2000/XP, </span><a
href="getstart.html#dx1-5013" ><span
class="ptmr7t---90">657</span></a> <br>
<span
class="ptmr7t---90">winds, </span><a
href="getstart.html#dx1-53065" ><span
class="ptmr7t---90">658</span></a> <br>
<span
class="ptmr7t---90">Wippler, Jean-Claude, </span><a
href="getstart.html#dx1-54112" ><span
class="ptmr7t---90">659</span></a> <br>
<span
class="ptmr7t---90">wireframe, </span><a
href="getstart.html#dx1-35010" ><span
class="ptmr7t---90">660</span></a> <br>
<span
class="ptmr7t---90">Wood, Charles, </span><a
href="getstart.html#dx1-50006" ><span
class="ptmr7t---90">661</span></a> <br>
<span
class="ptmr7t---90">Woodsoup, </span><a
href="getstart.html#dx1-54114" ><span
class="ptmr7t---90">662</span></a> <br>
<span
class="ptmr7t---90">workstation, </span><a
href="getstart.html#dx1-6005" ><span
class="ptmr7t---90">663</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53012" ><span
class="ptmr7t---90">664</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">X15, </span><a
href="getstart.html#dx1-8007" ><span
class="ptmr7t---90">665</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-53076" ><span
class="ptmr7t---90">666</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">yoke, </span><a
href="getstart.html#dx1-30011" ><span
class="ptmr7t---90">667</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-42003" ><span
class="ptmr7t---90">668</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-43003" ><span
class="ptmr7t---90">669</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-45003" ><span
class="ptmr7t---90">670</span></a><span
class="ptmr7t---90">, </span><a
href="getstart.html#dx1-47023" ><span
class="ptmr7t---90">671</span></a> <br>
<span
class="ptmr7t---90">yokes, </span><a
href="getstart.html#dx1-6018" ><span
class="ptmr7t---90">672</span></a>
<br>
</p><p class="theindex">
<span
class="ptmr7t---90">Zeh, Allan, </span><a
href="getstart.html#dx1-54115" ><span
class="ptmr7t---90">673</span></a> <br>
<span
class="ptmr7t---90">zlib library, </span><a
href="getstart.html#dx1-54031" ><span
class="ptmr7t---90">674</span></a>
<br>
</p></div>
</body></html>