FrontPage > comment_on_manual

Table of Contents

This page includes comments on the FlightGear Manual. It is intended to feedback toward next version of Manual.

v2.0.0 †

↑

Chapter 1 †

If you want to run FlightGearunder Mac OS X, you need to have Mac OS X 10.4 or higher.
Minimum hardware requirement is either a Power PC G4 1.0GHz or an intel Mac, but We suggest...
Historically, \FlightGear{} was based on a flight model it inherited (together
with the Navion airplane) from LaRCsim.
More details of the UIUC flight model can be found at
http://www.uiuc.edu/ph/www/m-selig/apasim.html
It is our hope that someday there will be an accompanying FlightGear
Programmer’s Guide a FlightGear Scenery Design Guide...
↑

v1.9.0 †

↑

Chapter 2 †

Windows - any flavor,
Macintosh OSX,
Linux.
↑

2.1 †

For Windows, this directory is likely to be
c:\Program Files\FlightGear\data\Scenery. 
To install the scenery, uncompress the tarball into the Scenery
directory. Most operating system provide tools to uncompress tarballs.
If you cannot uncompress the tarball, install an extractor program such
as 7-zip (http://www.7-zip.org/. 
Once you have uncompressed the tarball, the Terrain and Objects direcories
will contain additional sub-directories with your new scenery inside.
↑

2.1.2 †

2.1.2  FG_SCENERY
This is where FlightGear looks for Scenery files. It consists of a list of
directories that will be searched in order. The directories are separated by
“:” on Unix and “;” on Windows.
↑

2.1.3 †

-atlas=socket,out,1,localhost,5505,udp
Note that TerraSync (when called with the "-S" command line switch, as
recommended) is going to download Scenery via the Subversion protocol over
HTTP. Thus, is your Internet access is set up to use a HTTP proxy, plase make
yourself aware how to configure the "libsvn" Subversion client for use of a
proxy.
↑

2.1.4 †

↑

2.2 †

Simply download the file and uncompress it into the data/Aircraft subdirectory
of your installation. 
If you are successful, there will be a new sub-directory in your
FG_ROOT/data/Aircraft directory containing the aircraft.
The aircraft are downloaded as .tar.gz files.
Some computers will download them as .tar.gz.zip files. If so, simply rename
the file to .tar.gz before uncompressing them.
↑

2.3 †

Most of the packages named above include the complete FlightGear documentation
including a PDF version of The FlightGear Manual intended for pretty printing
using Adobe’s Acrobat Reader, available from
http://www.adobe.com/products/acrobat/
Moreover, if properly installed, the ḣtml version can be accessed via
FlightGear’s help menu entry.
↑

Chapter 3 †

↑

3.1 †

There are two environmental variables that must be defined to run FlightGear.
↑

3.1.1 †

This is the data subdirectory of where you installed FlightGear. e.g.
/usr/local/share/FlightGear/data or c:\Program  Files\FlightGear\data.
This is where FlightGear will look for scenery files. It consists of a list of
directories that will be searched in order. The directories are separated by
“:” on Unix and “;” on Windows. e.g.
↑

3.3.1 †

Open a command shell, change to the directory where your binary resides
(typically something like c:\Program Files\FlightGear\Win32\bin), set the
environment variables by typing 
SET FG_HOME=~c:\Program Files\FlightGear~  
SET FG_ROOT=~c:\Program Files\FlightGear\data~  
SET FG_SCENERY=~c:\Program Files\FlightGear\data\Scenery~
↑

3.4 †

3.4  Launching the simulator under Mac OS X
↑

3.5 †

3.5  Command line parameters
↑

3.5.3 †

For available choices check the directory /FlightGear/Aircraft, and look for
files ending in ”-set.xml”.
↑

3.5.8 †

However, the value set by these functions could be modified using the
–time-offset function.
↑

3.5.10 †

Allows specifying a waypoint for the GC autopilot; it is possible to specify
multiple waypoints (i.eȧ route) via multiple instances of this command.
↑

3.6 †

↑

3.6.1 †

$ °/ js demo
Under Windows, open a command shell (Start|All Programs|Accessories), go to
the FlightGear binary folder and start the program as follows (given
FlightGear is installed under c:\Flightgear) 
On our system, the first few lines of output are (stop the program with ˆ C
if it is quickly scrolling past your window!) as follows:
Joystick test program. 
... etc˙u p to ...
↑

3.6.2 †

If the FlightGear base directory FlightGear does not already contain an
options file .fgfsrc (under UNIX)/system.fgfsrc (under Windows) mentioned
above, just copy
http://www.lancs.ac.uk/people/cpaap/pfe/. 
–prop:/input/joysticks/js[1]/axis[1]/binding/factor=-1.0

into

–prop:/input/joysticks/js[1]/axis[1]/binding/factor=1.0
Concerning all the finer points, such as getting the joystick buttons working, 
John Check has written a very useful README included in the base package under 
FlightGear/Docs/Readme/Joystick.html.
↑

Chapter 4 †

↑

4.1 †

If the s are off, you’ll have to start them before proceeding any further.
For that you’ll need the , which you’ll find in the lower-left corner of the  instrument panel.
Now you can hit the “s” key to operate the .
↑

4.2 †

Ctrl + U	Add 1000 ftṫo your altitude (emergency)
Note: If you have difficulty processing the screenshot fgfs-screen.ppm
on a Windows machine, just recall that simply pressing the “Print” key
copies the screen to the clipboard, from which you can paste it into any
graphics program.
↑

4.4 †

If you don’t have pedals or lack the experience to handle the proper
ratio between aileron/rudder automatically, you can start FlightGear
with the option --enable-auto-coordination.
Besides these, there are several supplementary instruments. To the very
left you will find the clock, obviously being an important tool for
instance for determining turn rates.Below
The instruments below indicate the position of youryoke.
 

このページには、FlightGear Manual を1.0.0 に対応させる為のメモが書いています。何か判る事があったら追記してください。文章にまとまり次第、随時マニュアルを修正して行こうと思います。(Tat)

↑

第一章 †

↑

1.2 System Requirements †

つづく...

トップ   新規 一覧 単語検索 最終更新   ヘルプ   最終更新のRSS