> If someone needs translation into another language, you might try to
> translate the web page using google translation. <http://
> www.google.com/language_tools?hl=en>
>
> The english language version is here:
>
> <http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux-
> user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2F&langpair=de%
> 7Cen&hl=en&safe=off&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools>
Google somehow only translated the first part into a very crude translation.
So here is a better one (hand crafted ;-), other German speakers can probably
correct me if I am wrong somewhere):
Flying With FlightGear
High Above
----------
UFO's over San Franscisco? With the free flight simulator FlightGear you leave
this earth -- if needed in an UFO. Validate your free ticket here. Kristian
Kißling, Jörg Luther
-----------
README
This article instructs you on the usage of the free flight simulator
FlightGear and highlights its strong and weak points compared to its
commercial competitors.
Despite the so called low fare airlines, flying is an expensive hobby. This is
even more true for piloting a plane yourself. A (hobby [sic!]) pilots training
costs thousands of Euros, a visit in a professional full flight simulator
comes at 200 to 300 Euro. No surprise, a lot of flight enthusiasts turn their
PC into a cockpit: But even for flight sims for your own living room you have
to spend 20 to 30 Euro -- extensions like additional models or detailed
scenery excluded. This sums to a nice amount over time.
On the other hand you can get the free flight simulator FlightGear platform
independent and at no cost (Figure 1). Technically not in the same league
like current commercial competitors, it is steadily developed further and
with lots of features seems to be close to reality.
FIGURE 1
((1)) A Cessna passing the Golden Gate Bridge of San Francisco in the free
flight simulator Flightgear.
Check-in
A slightly outdated version of FlightGear is installed for Suse via Yast and
via Apt for Debian. For the newest release you have to compile the source
code yourself [1]. For Mandrake 10.2, Fedora Core 3 and the newest version
5.10 of Ubuntu packets exist for the current release 0.9.8 of FlightGear. The
packets may be found here [2].
To install FlightGear, you will need a 3D driver for your graphics card, since
you will surely spare the bucking (TF not sure it's the right translation)
without it. Install FlightGear via the respective packet manager.
The console plays an important role: unlike other flight simulators you define
parameters of the program before the start. With different options you
determine for example the start position, the type of aircraft or the local
time at the departure location. A typical start line is:
fgfs --enable-fullscreen --aircraft=ufo --airport-id=KJFK
--start-date-lat=2005:09:09:12:00:00 --enable-auto-coordination
Now have a look to the single options: --enable-fullscreen turns on the
fullscreen mode, for --aircraft you choose the UFO, departure aerodrome is
John-F.-Kennedy airport (JFK) near New York.
-----------------------
UFO: One of the less realistic aircraft in FlightGear. The UFO is fast, never
crashes and provides a handy way to explore the scenery.
------------------------
Every airport worldwide possesses an ICAO code, which you can query at this
website [3].
------------------------
ICAO: ICAO stands for International Civil Aviation Organisation, which assigns
airport codes to international airports.
------------------------
Your first flight does not start at JFK though: FlightGear by default only
starts in the vicinity of San Franscisco. Other regions of the world can be
downloaded from the FlightGear Website [4]: How to install such addons you
can read in the box "Extending FlightGear".
=========================
Extending FlightGear
The FlightGear world is divided into 10x10 degrees quadrants. In the basic
version you only get one such tile around Los Angeles, the rest of the world
consists of water. With the right extension files [4], you get scenery for
the rest of the world too.
FIGURE 2
((2)) If you like to fly to a new airport or region, first you must download
and install the right scenery tiles.
The download of so called scenery tiles causes tremendous download volumes: A
single tile comes at around 80MB; flightgear.org provides the whole world
scenery on 3 DVD for purchase. We have put the Middle European region onto
the attached CD.
The region consists of the four tiles from 0°E 50°N (e000n50.tgz) to 10°E 40°N
(e010n40.tgz). Not only Germany but also Benelux, Denmark, the south of
Scandinavia, large parts of France and Italy as well as the Balcan area come
into your reach.
To install the scenery, copy the archives from the CD depending on your
distribution into the Scenery or Scenery/Terrain subdirectories and unpack
with the command tar -xvzf e0*. In a similar manner proceed with other
downloaded FlightGear scenery tiles.
Similar to the extension of the flight regions is the extension of the
available aircrafts: In an own download area on flightgear.org [8] you find
lots of aircraft from hang gliders and soaring planes to piston and jet
engines from all epochs up to X-planes from NASA. If one of them is missing
in your collection just download the respective archive and unpack it into
the Aircraft subdirectory of your FlightGear installation. At the next start
of the simulator your new purchase is waiting "at the gate" already.
=============================
To ensure daylight conditions, we begin the flight -- according to the option
--start-date-lat -- on the September, 9th 2005 at noon local time. The
activated option --auto-coordination ensures coordinated action of aileron
and rudder.
In the FlightGear manual [5] you can find further options for the commandline
shell [6] as well as a list of existing aircraft types [7] -- though not all
models are functional. If the performance of your graphics card is a bit
weak, deactivate textures and other eye candy. The look is worse but the
simulation runs fluently. Start the simulator now on the console with
fgfs --enable-fullscreen --start-date-lat=2005:09:09:12:00:00 .
Ready for Take-off
As usual with flight simulators at first you look from a cockpit (Figure 3)
onto a runway in the vicinity of San Franscisco.
[FIGURE 3]
((3)) View from the cockpit onto a runway. The default airport of FlightGear
is in the vicinity of San Franscisco.
By default your aircaraft is a Cessna 172, perfect for a local flight. The
first step is somehow getting the plane into the air. The best way is to use
a joystick (see box "Virtual Stick") or alternatively with active support
from mouse and keyboard.
==============================
Virtual Stick
FlightGear supports, like any other good flight simulation, control via
joystick including additional throttle quadrants and rudder pedals. The
simulator comes already with configuration files for well known products from
CH Products, Logitech, Microsoft, Saitek or Thrustmaster.
All current distributions detect a connected joystick via hotplug. You can
check this for your system with dmesg:
$ dmesg | grep Joystick
input: USB HID v1.10 Joystick [<i>Microsoft Sidewinder Precision 2
Joystick<i>] on usb-0000:00:1d.0-1
In most cases also FlightGear detects the correct type by itself and load the
corresponding configuration from the Input/Joysticks/Vendor subdirectory. If
not start your text editor and change in the file joysticks.xml die line for
the default device to the right joystick configuration:
<!-- Default device --> <!-- js n="0"
include="Input/Joysticks/Default/joystick.xml"/-->
<js n="0" include="Input/Joysticks/Microsoft/Sidewinder-precision-pro.xml"/>
If you don't like the default axis/button assignment for your joystick you can
modify it to your heart in the same configuration file. Possibilities how to
do this are to be found in the file README.Joystick.html, which you can find
in the Docs subdirectory of your installation.
For the control of aileron, rudder and elevator as well as throttle naturally
the variants are limited and the need for modification is rare.
For the assignment of the buttons on the other hand nearly every PC pilot has
his own preferences -- no problem: In the section <binding> of every button
statement in the configuration file you can modify the funtion of the button
as you like. If for example you like to map a keyboard function to the
button, first search in keyboard.xml for the corresponding key binding.
Replace [sic!] copy the binding section there and replace the corresponding
lines in the joystick configuration file.
To use e.g. the fire button of the joystick -- typically button 1 -- to change
the view, add the following section to your configuration:
<button n="0">
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>view.stepView(1)</script>
</binding>
</button>
To configure a completely unknown joystick you can in the same way build a
complete configuration yourself. Though this is necessary only in extremely
rare cases -- usually it suffices to use an existing file and to modify it
slightly.
==============================
A click with the right mouse button changes the pointer to a cross hair. In
this mode the mouse moves the aircraft controls. A further right click
activates 'View' mode and turns the pointer into a double arrow from left to
right. Now you can comfortably look around in your cockpit. A third right
click changes back to 'Menu' mode, in which you can use the menu functions.
During a flight you can switch between these modes at will.
Test now, if the engine of your plane is runnning. In the Cessna you can see
with your naked eye whether the propeller is spinning and whether the
RPM-meter is active (Figure 4).
FIGURE 4
((4)) The cockpit of the Cessna 172, the default FlightGear aircraft. The
instruments inform about altitude, speed and und attitude of the plane.
To start the engines, activate the magnetos -- some sort of ignition system--
by pressing [AltGr ]+[0] thrice (figure 4), then press the space bar until
the engine is running. By the way via [AltGr]+[7] you can turn the engines
off again. Maybe you have to release the parking brake via [Shift-B] -- now
we are ready for takeoff. Switch into the 'Cointrol' mode of your mouse and
accelerate slowly with [Page-Up]. The aircraft begins to roll. Soon you will
realize a slight left turning: the reason is the so called torque effect,
which is caused by the vortexed air from the propeller. With [0] and [Enter]
on the number pad you correct your trajectory. As soon as the airspeed
indicator (figure 4) shows 55kts the nose begins to rise slightly, at 65kts
the plane begins to climb. Observe the altitude indicator (figure 4) and
climb to an altitude of 600ft. You have reached this altitude if the large
needle is pointing to the 6. Alternatively a head up display, which you can
activate with [H], shows airspeed on the left side and altitude on the right
side.
On autopilot
To relieve the pilot on multihour flights autopilots exist. If you reached a
stable attitude in around 800ft, press [P] to pause the simulation. Change to
menu mode via right mouse click. From the menu 'Autopilot' choose 'Settings'
and enter 800ft into the altitude field. In the same menu is the option 'Add
Waypoint'. There you can enter airfields which the autopilot should head to.
Replace the code KSFO for the airport of San Francisco for example with KLAX,
the airport of Los Angeles. After pressing [P] again the plane automatically
changes course to Los Angeles, [Ctrl]+[A] stabilizes the plane thanks to the
autopilot in an altitude of 800ft. Now at first enjoy the view, if you like:
bring the mouse into 'View' mode and look through one of the side windows
down. If you press [V] multiple times, you can change the camera perspective.
In view mode look at your aircraft from all sides an zoom with [X] and
[Shift]+[X] (figure 5).
Dort tragen Sie Flughäfen ein, die der Autopilot ansteuern soll. Ersetzen Sie
die Abkürzung KSFO für den Flughafen in San Francisco zum Beispiel durch KLAX
für den Flughafen von Los Angeles. Nach erneutem Drücken von [P] nimmt das
Flugzeug automatisch Kurs auf Los Angeles, [Strg]+[A] stabilisiert das
Fluggerät dank des Autopiloten auf einer Höhe von 800 Fuß. Genießen Sie nun
ruhig erstmal die Aussicht: Stellen Sie die Maus auf den Ansichtsmodus und
schauen Sie aus einem der Seitenfenster nach unten. Indem Sie mehrmals [V]
drücken, ändern Sie die Kameraperspektive. Im Ansichtsmodus betrachten Sie
Ihr Flugzeug zudem von allen Seiten und zoomen mit [X] und [Umschalt]+[X] in
einen Bildausschnitt heran (Abbildung ((5))).
FIGURE 5
((5)) With [X] and [Shift]+[X] you can look at your aircraft and the scenery
in detail. Here the Cessna is flying over San Francisco.
How long it takes -- in nautical miles -- to L.A. and how long it lasts, you
can see in the display which is activated by pressing [H].
Entertainment on board
From the menu you reach further options. Play god in the 'Wheather' menu by
changing the conditions for different flight altitudes. You can define wind
speed, wind direction, visibility and temperature. In 'Clouds' you define
where a cloud layer sits, how thick it is and what type of clouds [sic!] you
prefer. With 'Time of Day' you can change the local time.
Interesting for the view outside the cockpit is 'Adjust View Distance' from
the 'View' menu. With the help of the options 'Heading','Pitch' and 'Radius'
you define how much you see from the cockpit and from the rest of the world.
With 'System Failure' and 'Instrument Failure' you simulate system failures
and can that way replace the stroke suffering captain on your next vacation
trip. On what frequencies you contact the tower you can see in the menu
'ATC/AI', if you enter in 'Frequencies' the ICAO code of the airport. If you
then in the menu 'Equipment' click on the knob next to COM1 you'll hear the
tower traffic. If you don't like the keyboard control just click on the
instruments in the cockpit with the mouse.
Wish and Reality
Experienced flight simulator pilot -- and of course especially the ones which
collected thousands of hours on the competing product from Redmond for their
virtual log book -- adapt easily and without problems to the usage of
FlightGear. They recognize a few pecularities of FlightGear though, which
don't fit well with the claim of an flight simulator.
In this category falls the behaviour of lots of aircraft models. For example
in the Piper Cherokee Warrior II the flaps bump out in a split second; in
the F-16 all rudders shake already on the runway. Also the aerodynamics
leaves a lot of wishes. In a test we were unable to bring any of the aircraft
from stall into tailspin.
At high g's there's no black nor white out, you don't have to worry about the
structural integrity of the cell. Even at extremely high speed you can extend
flaps and landing gear without danger. Extremly low flying is no big thrill
because of lacking collision detection with buildings, bridges or other
objects.
That may be even desirable, compared to the instrumentation of many 3D
cockpits in the FlightGear models: In most of them basic instruments like
indicators for trim, gear or flaps lack, sometimes the whole panel is
completely empty. Even the the otherwise well equipped Cessna 172 lacks in
the 2D panel DME and buttons for lighting, the 3D cockpit misses any sign of
trim and flap indicators.
---------------------------
DME: Distance Measuring Equipment. Distance measuring eqwuipment (TF :-)),
which measures the distance from the DME ground station to the aircraft.
----------------------------
Radio Navigation
----------------------
A special instrument is missing in all FlightGear cockpits: a transponder,
which causes a unique identification of the own aircraft on the radar screen
of the local air traffic controller. This points to another weakness in the
FlightGear feature set: A virtual dummy ATC controls the via 'ATC/AI' menu
addable AI traffic, a real dialog with the ATC controller from the own
cockpit is missing though. That way you don't have to care about clearances.
----------------------------
ATC: Air Traffic Control. Air traffic control, the operative part of the
aviation authorities. Often also used for the controller himself. AI Traffic:
AI stands euphemistically for Artificial Intelligence. Virtual air traffic
created by the simulation, which is usually based on scripting.
------------------------------
A real highlight is the fact, that all radio navigation facilities operate on
the frequencies of their real life counterparts (figure 6). That way original
flight maps like Jeppesen charts or DoD flight information publications can be
used. That VOR/DMEs, NDBs and ILS are located in the exact position from the
charts makes the precise following of SIDs and STARs a snap. According to
flightgear.org you have the choice between 22000 aerodromes worldwide.
------------------------------
VOR: VHF Omnidirectional Radio Range. VHF Omnidirectional Radio Range for
flight navigation.
NDB: Non Directional Beacon. Non Directional Beacon for flight navigation.
ILS: Instrument Landing System. Radio navigation system for precise approaches
consisting of Glide Scope, Localizer and Markers.
SID: Standard Instrument Departure Route. (TF well, self explaining for
english speakers :-))
STAR: Standard Instrument Arrival Route.
---------------------------------
FIGURE 6
((6)) Cessna 172 in final to Ben Gurion International (LLBG). On approach via
the Mediterranean from IAF Siron (16.0 DME BGN) on Radial 119 of VOR/DME Ben
Gurion (BGN) the plane jut passed the outer marker (NDB Tel Aviv LL, 5.2 DME
BGN) and is now nearly precise [sic!] on final course, though nearly 400ft
above glide path.
Backside: Without these charts radio navigation is a no go -- a possibility to
look up existing navigation facilities is lacking as well as a 'moving map',
which is bound to this function in many other simulators. A pilot without the
respective charts is left only with the GPS "navigation" of the simulator,
which only allows flights from airport to airport.
Conclusion
What is called PC flight simulator, is to be measured against the old bull of
the genre -- Microsoft's Flight Simulator. It has -- including the preceding
version of Sublogic -- now 25 years worth of development time. The resulting
know how lead has been made up by the 16 years younger FlightGear project in
an impressive way, though it is in the current 0.9.8 release more than a
noses length (TF: what's the correct idion here?) behind the pendant from
Redmond.
Too complex for a game, too less realistic for a simulation, FlightGear
currently is interesting for two user groups. Beginners are provided a
possibility to get a whiff of the world of flight simulation and to learn
basic flight and navigation techniques. More experienced PC pilots with a
faible for IFR procedures find a vast training area with realistic
possibilities for instrument based approaches and departures -- as far as
they are able to tolerate the sometimes unrealistic aerodynamics and
avionics.
-------------------------
IFR: Instrument Flight Rules. Rules for instrument flight, often under control
of ATC. Also: Flying without sight. Opposite: VFR (Visual Flight Rules).
------------------------------
If you don't belong to any of these two groups, its better to stay with your
present choice -- also if you don't particularly like the operating system it
runs under.
(kki/jlu)
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
