De/Neu bei FlightGear: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(partly translatet)
mNo edit summary
Line 2: Line 2:
''Note some parts of this article have not been updated for 2008''
''Note some parts of this article have not been updated for 2008''


<div style="font-size:200%">Neu bei FlightGear</div>




Line 47: Line 49:


Wenn es installiert ist schaut man sich am besten gleich mal [[#FlightGear starten|FlightGear starten]] an, da fgrun, die grafische Oberfläche zum Starten des Simulators, nicht zwingend mitinstalliert worden ist.
Wenn es installiert ist schaut man sich am besten gleich mal [[#FlightGear starten|FlightGear starten]] an, da fgrun, die grafische Oberfläche zum Starten des Simulators, nicht zwingend mitinstalliert worden ist.
=== Getting Scenery ===
A limited set of [[scenery]] comes installed with [[FlightGear]], which consists of the area surrounding [[San Francisco International Airport|KSFO]].
In FlightGear, scenery is divided into two kinds of data: Objects and Terrain. Objects are the buildings, bridges and radio towers, etc. that represent three-dimensional structures. Terrain represents the contours, elevations and type of ground you fly over.
All object data goes in an Objects directory and all terrain data goes in a Terrain directory. The location of the scenery and its sub-directories depends on your particular installation.
To download Objects and Terrain for FlightGear, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page. On this page follow the link to download scenery from the map. Choose a block from the map where you will by flying. Once the package has downloaded, extract into your FlightGear scenery directory.
The scenery packages available from the FlightGear website contain both Objects and Terrain for the locations.
You may obtain additional and more up to date scenery Objects as they become available through the [http://fgfsdb.stockill.org/ FlightGear Scenery Database].
Information beyond this brief overview is available in [[Installing Scenery]] and [[Downloading New Flightgear Scenery for Windows XP]]
=== Getting Aircraft ===
To download additional [[Aircraft]] for FlightGear individually, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page, then choose [Aircraft Downloads http://www.flightgear.org/Downloads/aircraft/index.shtml].  A (possibly temporary) archive of all aircraft available as of 8/14/2006 is at: [FGaircraft_20060814.zip http://139.78.95.188/flightgear/FGaircraft_20060814.zip] (about 108 MB).
Once the aircraft package has downloaded, decompress and extract the archived files onto your computer. You may extract to a temporary directory and move them, or extract directly into the Aircraft directory in FlightGear. This is typically
/path/to/flight/gear/data/Aircraft
See also [[Installing Aircraft]] for more documentation.




Line 109: Line 86:




=== Online Multiplayer Flying ===
== Der erste Flug ==
{{Main article|Howto: Multiplayer}}
 
=== Using the Keyboard and Mouse ===
=== Using the Keyboard and Mouse ===


Line 170: Line 145:


[http://maps.google.com Google Maps] and The FlightGear Online Map for multiplayers are both good resources as well as the FlightGear Community Flight Planner.
[http://maps.google.com Google Maps] and The FlightGear Online Map for multiplayers are both good resources as well as the FlightGear Community Flight Planner.
== Zusätzliche Otionen ==
=== Scenery ===
A limited set of [[scenery]] comes installed with [[FlightGear]], which consists of the area surrounding [[San Francisco International Airport|KSFO]].
In FlightGear, scenery is divided into two kinds of data: Objects and Terrain. Objects are the buildings, bridges and radio towers, etc. that represent three-dimensional structures. Terrain represents the contours, elevations and type of ground you fly over.
All object data goes in an Objects directory and all terrain data goes in a Terrain directory. The location of the scenery and its sub-directories depends on your particular installation.
To download Objects and Terrain for FlightGear, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page. On this page follow the link to download scenery from the map. Choose a block from the map where you will by flying. Once the package has downloaded, extract into your FlightGear scenery directory.
The scenery packages available from the FlightGear website contain both Objects and Terrain for the locations.
You may obtain additional and more up to date scenery Objects as they become available through the [http://fgfsdb.stockill.org/ FlightGear Scenery Database].
Information beyond this brief overview is available in [[Installing Scenery]] and [[Downloading New Flightgear Scenery for Windows XP]]
=== Fluggeräte ===
To download additional [[Aircraft]] for FlightGear individually, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page, then choose [Aircraft Downloads http://www.flightgear.org/Downloads/aircraft/index.shtml].  A (possibly temporary) archive of all aircraft available as of 8/14/2006 is at: [FGaircraft_20060814.zip http://139.78.95.188/flightgear/FGaircraft_20060814.zip] (about 108 MB).
Once the aircraft package has downloaded, decompress and extract the archived files onto your computer. You may extract to a temporary directory and move them, or extract directly into the Aircraft directory in FlightGear. This is typically
/path/to/flight/gear/data/Aircraft
See also [[Installing Aircraft]] for more documentation.
=== Online Multiplayer Flying ===
{{Main article|Howto: Multiplayer}}


== Getting Help ==
== Getting Help ==

Revision as of 00:44, 10 October 2009

Template:Languages Note some parts of this article have not been updated for 2008


Neu bei FlightGear


Der Anfang

FlightGear besorgen

Der erste Anlaufpunkt um sich FlightGear und Zubehör zu besorgen ist die offizielle FlightGear Downloads Seite. Dort findet man Links zu den Quellen und zu fertigen Paketen für verschiedene Betriebssysteme der aktuellen, stabilen FlightGear Version. Je nach Wissensstand gibt es noch die Möglichkeit sich per CVS die aktuellsten Entwicklungen zu holen. Diese CVS-Version enthält die neuesten Features und ist manchmal sogar für neue oder überarbeitete Fluggeräte notwendig, ist aber deutlich umständlicher zu besorgen, zu installieren und kann zudem instabil sein.


Installation unter Windows

Die Installation wird durch einen Doppelklick auf das heruntergeladene Paket (zum Zeitpunkt des Schreibens fgsetup-1.9.1b.exe) gestartet und verläuft auch sonst wie von anderen Anwendungen gewohnt. Nach der Installation sollte FlightGear automatisch gestartet werden und es erscheint ein Fenster welches nach verschiedenen Pfaden verlangt, ähnlich diesem.

In der ersten Eingabebox, Executable, wird der Pfad zur Anwendung angegeben. Wenn bei der Installation nichts anderes angegeben wurde ist dies C:\Program Files\FlightGear\bin\win32\fgfs.exe bzw. C:\Programme\FlightGear\bin\win32\fgfs.exe.

Die zweite Zeile weist auf die Daten zu FlightGear, $FG_ROOT, und ist per Default C:\Programme\FlightGear\data.

In der dritten Box, $FG_SCENERY, kann man verschiedene Pfade zu installierten Sceneries (die Landschaft/Erdoberfläche) angeben. Hier sollte automatisch der Inhalt von $FG_ROOT mit einem angehängten /Scenery eingefügt werden. Weitere, später in einem anderen Verzeichnis installierte Sceneries können händisch hinzugefügt werden.

Sind die Pfade richtig eingegeben kann man im rechten unteren Fenstereck auf Weiter/Next klicken und man kommt zur Flugzeugauswahl. Das Fenster mit den den Pfaden erscheint nun beim Starten nicht mehr, man kann es aber jederzeit durch einen Klick auf Zurück/Prev in der Flugzeugauswahl aufrufen.


Installation unter Mac OS X

FlightGear auf Mac OS X installieren gestaltet sich sehr einfach. Nur den FlightGear Icon in das Verzeichnis /Applications verschieben. Fertig.

Beim ersten Start wird der FlightGear Icon im Dock ein Weilchen hüpfen bis die Flugzeug- und Flughafendaten geladen sind. Dann erscheint der GUI-Launcher und man kann mittels klick auf die Gear-Schaltflächen Startpunkt und Fluggerät auswählen. Start Flight startet dann den Simulator mit den eingegebenen Optionen. Hilfe zu weiteren Optionen findet man im Mac FlightGear Users Guide.

Um FlightGear per Kommandozeile zu starten öffnet man /Applications/Utilities/Terminal.app und gibt folgendes ein:

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

Die Umgebungsvariablen $FG_ROOT und $FG_SCENERY sind unter Mac OS X nicht per Default gesetzt. Um dies per Kommandozeile zu erledigen folgenden Codeblock in Terminal.app ausführen. Man kann diese Pfade aber auch als Option (--fg-root=PFAD und --fg-scenery=PFAD1:PFAD2...) an FlightGear übergeben.

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

Nach dem Starten des GUI-Launchers hat man ein Alias auf $FG_ROOT in $HOME/Documents/Flightgear/<Version>. Das ermöglicht einen einfachen Zugriff auf die Daten mittels des Finders.


Installation unter GNU/Linux

Da es sehr viele teilweise sehr unterschiedliche Distributionen gibt ist es nur sehr schwer möglich eine universelle Kurzanleitung zu schreiben. Allerdings ein paar grundsätzliche Dinge gelten für alle Distributionen. Zuerst schaut man ob ein FlightGear-Paket in den Paketquellen vorhanden ist und dies auch noch die aktuelle stabile FlightGear-Version enthält. Der zweite Anlaufpunkt sind dann 'inoffizielle' Pakete/Paketquellen, zum Beispiel von der FlightGear Downloads Seite oder auch im Forum tauchen hin und wieder Pakete auf. Die dritte und letzte Möglichkeit ist dann das Kompilieren des Quellcodes. Mehr Informationen dazu gibt der Artikel Building FlightGear - Linux. Für Benutzer von Ubuntu und Debian gibt es ein Script welches die komplette Installation inklusive Download der CVS-Version erledigt. Siehe dazu Scripted_Compilation_on_Linux_Debian/Ubuntu.

Wenn es installiert ist schaut man sich am besten gleich mal FlightGear starten an, da fgrun, die grafische Oberfläche zum Starten des Simulators, nicht zwingend mitinstalliert worden ist.


FlightGear starten

Grundsätzlich wird der Simulator mit dem Befehl fgfs und angehängten Optionen gestartet. Jetzt gibt es aber mehrere Arten wie man das umsetzen kann. Die meisten Anwender werden wohl ein Zusatzprogramm wie fgrun für Windows/POSIX oder den GUI-Launcher für Mac OS X bevorzugen um die Optionen für den Simulator festzulegen und diesem beim Start zu übergeben.

Benutzer die lieber von der Kommandozeile aus arbeiten (oder fgrun noch nicht kompiliert haben) seien noch ein paar Dinge zum leichteren Einstieg gesagt. Um FlightGear zu starten gibt man ein:

fgfs


Scheitert der Befehl gibt es mehrere Ursachen. Schauen wir dazu die Fehlermeldungen an:

fgfs: command not found

Das Programm befindet sich nicht in einem in $PATH angegebenen Pfad. Zur Lösung entweder den Ort von fgfs in die Variable $PATH mitaufnehmen oder beim Starten den kompletten Pfad mitangeben. (z.B.: /$HOME/FlightGear/bin/fgfs)


Base package check failed ... Found version [none] at: $HOME/FlightGear/share/FlightGear
Please upgrade to version: 1.9.0

fgfs findet das Datenverzeichnis $FG_ROOT nicht. Dazu entweder eine gleichnamige Umgebungsvariable anlegen oder den Pfad zu den Daten per Option übergeben. (z.B: --fg-root=$HOME/FlightGear/data)

Das gleiche gilt für $FG_SCENERY. Wenn diese Fehlt wird zwar kein Fehler angezeigt aber es wird auch keine Scenery geladen und das Flugzeug steht nach dem laden mitten im Wasser. (z.B.: --fg-scenery=$HOME/FlightGear/data/Scenery)

Natürlich sind oben genannte Pfade nur als Beispiel zu sehen und sind dem eigenen System nach anzupassen. Um herauszufinden wo sich fgfs befindet kann man das Dateisystem nach der Datei fgfs bzw. fgfs.exe durchsuchen. Um $FG_SCENERY zu finden kann man nach einem Ordner namens Scenery suchen. $FG_ROOT ist (im Normalfall) dann gleich $FG_SCENERY nur ohne das /Scenery am Ende.

Nach den Pfaden ist wohl die wichtigste Option die für die Flugzeugwahl. (--aircraft=c172p)
Eine Liste der installierten Flugzeuge erhält man mit --show-aircrafts.


Wenn man alle Pfade zusammengesucht hat und die Optionen dann zusammenstellt könnte dies folgendermaßen aussehen:

/$HOME/FlightGear/bin/fgfs --fg-root=$HOME/FlightGear/data --fg-scenery=$HOME/FlightGear/data/Scenery --aircraft=c172p

Natürlich ist es sehr umständlich jedes mal beim Starten von FlightGear die ganzen Optionen einzugeben. Deshalb unterstützt fgfs natürlich eine Konfigurationsdatei in welcher man die ganzen Optionen auflisten kann. Dies ist eine simple Textdatei (ASCII) namens .fgfsrc welche von fgfs in $HOME erwartet wird und pro Zeile eine Option enthalten sollte. Nachdem diese Angelegt ist können wir munter fortfahren weitere Optionen zu sammeln.

Eine Übersicht über die Optionen gibt's im Wiki unter Command Line Parameters und, wer hätt's gedacht, mit der Option --help bzw. --help --verbose.


Der erste Flug

Using the Keyboard and Mouse

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

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

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

First Time In the Cockpit

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

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

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

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

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

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


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

Making the First Flight

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

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

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

  • "Left Turning Syndrome" for the previously mentioned reasons.
  • Compass Turning Error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction.
  • The Vertical Speed Indicator is also subject to error.
  • The Horizontal Situation Indicator is driven by a gyroscope (that is why it's sometimes called a Directional Gyroscope), which is subject to a phenomenon called gyro drift. For a number of reasons, the gyro will drift from its current heading and must be periodically (about every 15 minutes) calibrated to agree with the magnetic compass heading.

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

Flying Using Navigational Aids and the Autopilot

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

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

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

For help with navigation see Understanding Navigation

Airports and Navigation Aids

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

Google Maps and The FlightGear Online Map for multiplayers are both good resources as well as the FlightGear Community Flight Planner.


Zusätzliche Otionen

Scenery

A limited set of scenery comes installed with FlightGear, which consists of the area surrounding KSFO.

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

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

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

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

You may obtain additional and more up to date scenery Objects as they become available through the FlightGear Scenery Database.

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

Fluggeräte

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

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

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

See also Installing Aircraft for more documentation.


Online Multiplayer Flying

1rightarrow.png Unter Howto: Multiplayer gibt es zu diesem Thema einen Hauptartikel.


Getting Help

Chat

The quickest way to get help with Flight Gear is to join in the chat room FlightGear IRC channel.

Email Discussion Group

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

Documents

The ways for _users_ to get help with FlightGear are:

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

Getting More Detailed Information

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

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

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

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

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

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

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

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

Does FlightGear come with a printed manual?

You are invited to read "The Manual" online as HTML or download a PDF for viewing with Acrobar Reader or printing.

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

How you can help

1rightarrow.png Unter Volunteer gibt es zu diesem Thema einen Hauptartikel.

Testing

  • Build the latest CVS code or download snapshots (link)
  • File Bug Reports

Debugging & Profiling

  • Running FlightGear via valgrind to track down memory leaks

Support

Development

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