New to FlightGear: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (Update forum links)
(40 intermediate revisions by 18 users not shown)
Line 1: Line 1:
== Getting started ==
'''Welcome to [[FlightGear]]!''' Here we'll try to get you up in the virtual air in the shortest time possible. We'll also introduce you to some of the features of this flight simulator and also a few information on its community.
 
== Installation and setup ==
=== Hardware requirements ===
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers. OpenGL 2.0 or higher is required for FlightGear 2.0 and later. Most modern PCs support OpenGL, but if you are having trouble with slow frame-rates, see [[Hardware Recommendations]] for more information.
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 2.0 or higher. This is usually not a problem, but take a look at [[Hardware Recommendations]] to have a better idea.


Many laptops with insufficient 3D hardware acceleration capabilities are known to have issues with running FlightGear. Since laptops are smaller, the graphics card(s) on them are usually lower-end. See [[notebooks known to run FlightGear]] for reviews of several laptop systems.
Many laptops are known to have issues with FlightGear, as the graphics card(s) on them are usually lower-end. See [[notebooks known to run FlightGear]] for reviews of several laptop systems.


=== Getting FlightGear ===
=== Getting FlightGear ===
You may download the latest files from [http://www.flightgear.org/download/ FlightGear Downloads] page. Choose the source or binary files appropriate for your particular system. Or, depending on level technical expertise you may choose the [[Git]] version if you wish to work with a development version of FlightGear. The Git version typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to acquire and install. In general, the development version is not advised to the average user. You may also order Flightgear on a set of DVDs, availible on [http://www.flightgear.org/dvd/]
You may download the latest files from [http://www.flightgear.org/download/ FlightGear Downloads] page. Choose the source or binary files appropriate for your particular system. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <tt>fgfs</tt> or <tt>flightgear</tt>.)
 
Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you're willing to do some testing there's a nightly build for Windows or Mac available for download at the [[FlightGear Build Server]],and a daily-updated Ubuntu PPA. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].
 
You may also order FlightGear on a set of DVDs, available on the [http://www.flightgear.org/dvd/ FlightGear main site].


=== Installing on Windows ===
=== Installing on Windows ===
After installing FlightGear on Windows a dialog box appears to define file locations. This is [[FlightGear Launch Control]], also known as FGRun.
After you downloaded the installer, Run it and follow its instructions to install FlightGear.
 
Take care to temporarily disable your antivirus during installation. FlightGear is thought by some antiviruses to have a virus.


Apply the following settings:
* '''Executable''': the full path to the FlightGear program (<tt>fgfs.exe</tt>, usually <tt>C:/Program Files/FlightGear/bin/win32/fgfs.exe</tt> ). One can choose it directly using the file selection dialog that pops up when the folder button is hit.
* '''[[$FG ROOT|FG_ROOT]]''': the full path to the FlightGear base package (<tt>data/</tt> directory, usually <tt>C:/Program Files/FlightGear/data</tt>). If this path is wrong, no [[aircraft]] would be displayed and FlightGear won't run.


Once you have defined these default settings, you can press <tt>Next</tt> to select an airport, aircraft and edit additional settings.
With the Windows installer, you may choose where to install FlightGear. The FGROOT directory would be [your chosen directory]/data .


=== Installing on Mac OS X ===
=== Installing on Mac OS X ===
Line 37: Line 42:


=== Configuring OpenGL ===
=== Configuring OpenGL ===
FlightGear runs best with current [[OpenGL]] video drivers. If you are having trouble running FlightGear smoothly, see [[Configuring OpenGL]] for more information.
FlightGear runs best with current [[OpenGL]] video drivers. If you are having trouble running FlightGear, see [[Graphics drivers configuration]] for more information.


=== Getting scenery ===
=== Getting scenery ===
{{Main article|Howto: Install scenery}}
A limited set of [[scenery]] comes installed with FlightGear, which consists of the area surrounding [[San Francisco International Airport]] (KSFO).
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 three kinds of data:
In FlightGear, scenery is generally stored in you [[$FG_ROOT]] directory, and is divided into three kinds of data:
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Airports''' holds airport data, like runway usage and parking spots.
* '''Objects''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.


All object data goes in an <tt>Objects/</tt> directory and all terrain data goes in a <tt>Terrain/</tt> directory. The location of the scenery and its sub-directories depends on your particular installation.
The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! However, some might have problems with that, so you can also manually download and install new scenery parts, either official, the [[World Scenery]], or custom.
 
To download objects and terrain for FlightGear, go to [http://www.flightgear.org/download/scenery/ the scenery section] of the FlightGear website. 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 all needed data for the locations. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database].
The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''


Information beyond this brief overview is available in [[Howto: Install scenery]] and [[Downloading New Flightgear Scenery for Windows XP]].
Custom Scenery is available in many places. For example, in our forums ([http://forum.flightgear.org forum.flightgear.org]) or on repositories. An internet search should be able to find them.


=== Getting aircraft ===
=== Getting aircraft ===
{{Main article|Howto: Install aircraft}}
Additional [[aircraft]] can be downloaded and installed through the launcher. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. For the installation, see [[Howto: Install aircraft]].
To download additional [[aircraft]] for FlightGear individually, go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version.
 
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 <tt>[[$FG ROOT]]/Aircraft</tt>.


== Running FlightGear ==
=== Starting FlightGear ===
=== Starting FlightGear ===
Many users choose to start FlightGear from the command line ("console" or "shell" as it is known to Unix users). Alternatively some use graphical interfaces such as [[FlightGear Launch Control|Fgrun]] (FlightGear Launch Control).
The easiest way to start FlightGear is to use the desktop icon; this starts the graphical interface [[FlightGear Qt launcher]] where you can choose aircraft, start position etc.
 
To start FlightGear type on the command line:
 
fgfs
 
and hit enter. This will start FlightGear.
 
If FlightGear fails to start, it is likely the compiled FlightGear binary software is not in your path. If you know Unix, you may add the location of the binary to your path and try starting again. Otherwise, you may find the location of the 'fgfs' binary and enter an absolute path to it like
 
/usr/games/fgfs
 
The location depends on your particular system and choices you made during compile and installation.
 
It is important to understand when not using a graphical interface to start FlightGear, your interaction will be entirely from the command line. To see available aircraft, you specify an option on the command line. To specify an aircraft, an airport, multiplayer server, etc. you add an option to the command line when starting FlightGear. Please consult the list of [[Command Line Parameters]]. The parameters are also useful to those starting FlightGear from [[FlightGear Launch Control]] graphical interface, as it allows you to specify parameters.
 
=== Displaying available aircraft ===
From the command line:
 
fgfs --show-aircraft
 
displays a list of available (installed) aircraft.
 
=== Choosing an aircraft ===
From the command line:
 
fgfs --aircraft=foo
 
where foo is the name of the aircraft's <tt>*-set.xml</tt> file (eg. for the c172p this is <tt><u>c172p</u>-set.xml</tt>, so the command is <tt>--aircraft=c172p</tt>). See also [[Command Line Parameters]]. The following commands gives a list of available aircraft:
 
fgfs --show-aircraft


=== Online multiplayer flying ===
Many users choose however to start FlightGear directly from the command line. The executable name is <tt>fgfs</tt> and can be run without options. If it's "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:
{{Main article|Howto: Multiplayer}}
fgfs --launcher            # opens the FlightGear Qt launcher
fgfs --show-aircraft        # displays a list of installed aircraft
fgfs --aircraft=c172p      # start FG with the aircraft "c172p" (from the list)


=== Using the keyboard and/or mouse ===
=== Using the keyboard and/or 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 for flying. Adjustments (like throttle, instruments etc.) may be made with the keyboard.
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 for flying, yet even a cheap joystick would improve the experience so much.


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 list displaying what each key does will display.
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).


Coming from an other simulator? Check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear.
Coming from an other simulator? Check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear and the [[Flightgear dialogs and menubar]].


To use the mouse to fly the aircraft, right click (the cursor should change to a cross) and move the mouse to direct the aircraft. Right click again to look around (cursor should show a two sided arrow), click again to return to normal mode.
To use the mouse to fly the aircraft, press tab (the cursor should change to a cross) and move the mouse to direct the aircraft. Tab again to look around (cursor should show a two sided arrow), and tab again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[A330-200]]/[[A330-300|300]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.


=== First time in the cockpit ===
=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.
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.
Where is the "virtual cockpit?" Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off using the ''View'' menu or {{key press|Shift|V}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected ({{key press|Ctrl|V}}).


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.
You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (right click until you get a cursor shaped like a double arrow) to pan and the mousewheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.


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.
One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument's controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.


'''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.
Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.


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.
=== Starting the engine ===
You're eager to fly, but the engine's off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here's a general procedure that should work in many cases.


Many aircraft offer a help menu specific to that aircraft on the Aircraft Help menu (go to Help, then Aircraft Help.
In general to start the engine on a piston-engine type aircraft, you need:
# Fuel: some aircraft start the simulation with no fuel. You can add it in ''Equipment > Fuel and Payload''.
# Correct mixture: this is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)
# Magnetos set on ''both'': turn the key or press {{key press|&#125;}} ''three times'' to move through ''R'', ''L'', ''both''.
# Throttle: some engines start better with a little gas.
# Run the starter: click the "start" position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.


== Making your first flight ==
Starting all engines in a multi-engine aircraft is similar to the single engine--except you must follow the same start sequence for each and every engine.  Flightgear provides a convenient way to do this for all engines at once: press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2-D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.
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.
These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (Press {{key press|?}}) and/or at [[Aircraft|the aircraft's wiki]]. In general to start the engine on a jet engine type aircraft, you need to:
# Set cutoff ON
# Engage the starter
# Once the engines spools up to approximately 5% N1, set cutoff OFF
# Disengage the starter once the engine has reached operational speed


FlightGear offers a great deal of realism, which may be confusing to first time pilots.
=== Online multiplayer flying ===
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].


* "Left Turning Syndrome" for the previously mentioned reasons.
There's also a [[MPMap|multiplayer map]] that lets you see who's online right now,and even what navaids are nearby.
* 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.
==Learning to fly==
===Tutorials===
Many aircrafts have their own tutorial. With tutorials, you can learn to operate particular aircrafts but also learn to fly. You can access tutorials by going to the "Help" menu and selecting "Tutorial." A great place to start is the tutorial for the Cessna 172p aircraft, commonly used in real life to learn to fly fixed-winged aircrafts. If the tutorial starts without a runway and surrounded by water, your setup of Flighgear is missing the scenery for the airport at which the tutorial was supposed to run. To fix the problem, you have to [[Howto:Install scenery|download scenery]], which can be done by manually downloading the appropriate scenery, automatically downloading the scenery for the airport by enabling [[TerraSync]] by selecting "Download scenery automatically" from the "Downloads" section of the "Settings" menu of the Flightgear launcher, using the graphical Java-based tool [[TerraMaster]] (requiring the [http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html Java SE Runtime Environment]) to download the appropriate scenery, or obtaining the necessary scenery also available for purchase on Blu-ray from the FlightGear store. [http://store.flightgear.org/product/flightgear-complete-collection-bluray/]


=== Flying using navigational aids and the autopilot ===
== Making your first flight ==
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).
=== Realism ===
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 [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].


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 either
In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.
* do not specify an autopilot
* 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.
Here are some of the FlightGear realism points, 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 ([https://en.wikipedia.org/wiki/Aircraft_compass_turns more on this].)
* The Vertical Speed Indicator (VSI) is also subject to error.
* The Horizontal Situation Indicator (HSI) is driven by a gyroscope (that is why it's sometimes called a Directional Gyroscope), which is subject to ''gyro drift'': the indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
*You cannot just cancel a turn or climb by centring the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not mantain its altitude or heading by itself- a common mistake is trying to find a hands off yoke position. While with trims one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yokes.


For help with navigation see [[Understanding Navigation]].
Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] 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''.


=== Airports and navigation aids ===
=== 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 [[VOR]]s and their frequencies. Short of finding an actual sectional map for the area you wish to fly, what can you do?
When you first start FlightGear, whether from the command line or the graphical interface, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].


[http://maps.google.com Google Maps] and the [[MPMap|FlightGear Online Map for multiplayers]] are both good resources as well as the FlightGear [http://fgfs.i-net.hu/modules/fgplanner/ Community Flight Planner].
In-sim, there is a map you can use in ''Equipment > Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding Navigation]].


== Getting help ==
=== Flying using the autopilot ===
Besides this wiki, there are more places that can be visited to obtain information or request help:
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.
* Documents bundled with the release package.
* [http://flightgear.org/forums FlightGear Forum]
* [[FlightGear IRC channel]], the quickest way to get help.
* [[Malinglists|FlightGear users mailing list]], biggest chance to get in contact with developers.


== Getting more detailed information ==
For aircraft that provide their own autopilot, you should 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 in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].
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.
The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You cannot use the ''Autopilot'' dialog from the menu with this aircraft. You must use the autopilot device in the panel.


Also, note that those using the Git version of FlightGear may choose to update their aircraft files through the Git system.
== The FlightGear community ==
 
=== Getting help ===
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]].
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:
 
* [[Troubleshooting problems]] to help you with the most common issues;
=== I do not want to compile FlightGear, what can I do? ===
* [[Frequently asked questions]];
[http://www.flightgear.org/Downloads/ Our website] 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.
...and communication channels that can be used to obtain information or request help:
 
* The [[FlightGear Manual]], a ''must read'' for beginners;
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]].
* [https://forum.flightgear.org FlightGear Forum] and its subforums;
* [[FlightGear IRC channel]], the quickest way to get help;
* [[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
* Documents bundled with the release package.


=== Does FlightGear come with a printed manual? ===
=== Customizing FlightGear without compiling it ===
You are invited to read "[[The Manual]]" online as [http://www.flightgear.org/Docs/getstart/getstart.html HTML]
[http://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows and Mac OSX, while most Linux distros provide a packaged version in their repositories.
or download a [http://mapserver.flightgear.org/getstart.pdf 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.
Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].


== How you can help ==
=== How you can help ===
{{Main article|Volunteer}}
{{Main article|Volunteer}}
FlightGear is an opensource, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the forum and everything else. Volunteers, i.e. ''people that do things'', are fundamental to this project: without them, it wouldn't make a single step forward. So it is essential that contributors have fun in what they do.


=== Testing ===
If you really plan to contribute to this project, you should take a look at some articles that will give you some hints:
* [[Building Flightgear|Build]] the latest Git code or download snapshots (link)
* [[Howto:Understand the FlightGear development process]]
* [http://flightgear-bugs.googlecode.com File bug reports]
* [[Implementing new features for FlightGear]]
* [[How the FlightGear project works]]


=== Debugging & Profiling ===
There are never enough people contributing, and the fields where their help would be appreciated are many:
;Testing :
* [[Building Flightgear|Build]] the latest Git code or download snapshots from the [[FlightGear Build Server]]
* [https://sourceforge.net/p/flightgear/codetickets/ File bug reports]
* Running FlightGear via valgrind to track down memory leaks
* Running FlightGear via valgrind to track down memory leaks


=== Support ===
;Support :
* Help new users with downloading, compiling, installing and running FlightGear (http://forum.flightgear.org or on IRC)
* Help new users with downloading, compiling, installing and running FlightGear (https://forum.flightgear.org or on IRC)
* Provide Ideas & Suggestions, see: [[Feature Requests / Proposals / Ideas]]
* Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]
* Help clean up this wiki
* Help clean up this wiki
* Help provide new contents for missing wiki pages
* Help provide new contents for missing wiki pages


=== Development ===
;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:
* 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 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 bug fixes [[Bugs]] or new features  
** provide enhanced features [[Feature Requests / Proposals / Ideas]]
** provide new features  
** get involved in any of the other FlightGear-affiliated projects  
** get involved in any of the other FlightGear-affiliated projects  
* Aircraft development (3D modelling, textures, FDMs, scripting)
* Aircraft development (3D modelling, textures, FDMs, scripting)
* Scenery development
* Scenery development (terrain, model, weather)


[[Category:FlightGear]]
[[Category:FlightGear]]
 
[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[de:Neu bei FlightGear]]
[[Nl:Nieuw bij FlightGear]]
[[es:Nuevo para FlightGear]]
[[es:Nuevo para FlightGear]]
[[fr:Nouveau sur flightgear]]
[[fr:Nouveau sur flightgear]]
[[Pt:Novo no FlightGear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pt:Novo no FlightGear]]
[[zh:FlightGear新手]]
[[zh:FlightGear新手]]
[[ja:FlightGear入門]]
[[th:New to FlightGear]]

Revision as of 21:53, 26 March 2018

Welcome to FlightGear! Here we'll try to get you up in the virtual air in the shortest time possible. We'll also introduce you to some of the features of this flight simulator and also a few information on its community.

Installation and setup

Hardware requirements

For FlightGear to run smoothly, it requires a video card with OpenGL drivers 2.0 or higher. This is usually not a problem, but take a look at Hardware Recommendations to have a better idea.

Many laptops are known to have issues with FlightGear, as the graphics card(s) on them are usually lower-end. See notebooks known to run FlightGear for reviews of several laptop systems.

Getting FlightGear

You may download the latest files from FlightGear Downloads page. Choose the source or binary files appropriate for your particular system. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be fgfs or flightgear.)

Depending on your technical expertise you may choose the Git development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you're willing to do some testing there's a nightly build for Windows or Mac available for download at the FlightGear Build Server,and a daily-updated Ubuntu PPA. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled FGAddon aircraft development repository.

You may also order FlightGear on a set of DVDs, available on the FlightGear main site.

Installing on Windows

After you downloaded the installer, Run it and follow its instructions to install FlightGear.

Take care to temporarily disable your antivirus during installation. FlightGear is thought by some antiviruses to have a virus.


With the Windows installer, you may choose where to install FlightGear. The FGROOT directory would be [your chosen directory]/data .

Installing on Mac OS X

Installing FlightGear on Mac OS X is very simple. Just drag and drop the FlightGear icon to the /Applications folder. That's it.

The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select an aircraft and and airport by clicking the "Gear" buttons at the right of the names. Pressing "Start flight" will launch the simulator. You can configure more options using the GUI launcher. see the Users Guide for more details.

If you'd like to launch FlightGear using command-line, launch /Applications/Utilities/Terminal.app and type the following.

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

The $FG ROOT and $FG SCENERY are not set on Mac OS X. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

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

After launching the GUI launcher, you will have the alias to $FG ROOT at $HOME/Documents/Flightgear/<version> so you can browse the data folder using Finder.

Note: Once you have installed FlightGear, mac users can locate their $FG_ROOT folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft for installing new aircraft.

Configuring OpenGL

FlightGear runs best with current OpenGL video drivers. If you are having trouble running FlightGear, see Graphics drivers configuration for more information.

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 generally stored in you $FG_ROOT directory, and is divided into three kinds of data:

  • Airports holds airport data, like runway usage and parking spots.
  • Objects and Models are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
  • Terrain represents the contours, elevations and type of ground you fly/taxi over.

The current way of "installing" new scenery is enabling TerraSync, which will automatically download and update any place you visit - even on the fly! However, some might have problems with that, so you can also manually download and install new scenery parts, either official, the World Scenery, or custom.

The official, although outdated, scenery is available at the scenery download section of the FlightGear website, and can be installed following Howto: Install scenery. You may obtain additional and more up to date scenery objects as they become available through the FlightGear Scenery Database. This is recommended for users with weak internet connections or weak computers!

Custom Scenery is available in many places. For example, in our forums (forum.flightgear.org) or on repositories. An internet search should be able to find them.

Getting aircraft

Additional aircraft can be downloaded and installed through the launcher. Alternatively, you can go to the FlightGear website and navigate to the download page, then choose the aircraft download link that fits your FlightGear version. For the installation, see Howto: Install aircraft.

Running FlightGear

Starting FlightGear

The easiest way to start FlightGear is to use the desktop icon; this starts the graphical interface FlightGear Qt launcher where you can choose aircraft, start position etc.

Many users choose however to start FlightGear directly from the command line. The executable name is fgfs and can be run without options. If it's "not found", it is likely not in your path. The location depends on your particular system and choices you made during compile and installation. There is a list of Command Line Parameters which must be used to change many options, like the aircraft you want. The most important:

fgfs --launcher             # opens the FlightGear Qt launcher
fgfs --show-aircraft        # displays a list of installed aircraft
fgfs --aircraft=c172p       # start FG with the aircraft "c172p" (from the list)

Using the keyboard and/or 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 for flying, yet even a cheap joystick would improve the experience so much.

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).

Coming from an other simulator? Check key commands compared to other simulators for an overview of the difference between the key commands of that sim and FlightGear and the Flightgear dialogs and menubar.

To use the mouse to fly the aircraft, press tab (the cursor should change to a cross) and move the mouse to direct the aircraft. Tab again to look around (cursor should show a two sided arrow), and tab again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the A320neo and A330-200/300 this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.

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 actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off using the View menu or Shift+V. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected (Ctrl+V).

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the view mode of the mouse (right click until you get a cursor shaped like a double arrow) to pan and the mousewheel to zoom, or pan with the joystick hat and zoom with X and Shift+X.

One of the first steps that many take on entering an unfamiliar cockpit is to press Ctrl+C to highlight all the "hotspots", that is instrument's controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.

Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the Help menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.

Starting the engine

You're eager to fly, but the engine's off. Well, turning on the engines is not always easy. Some aircraft have an autostart entry in their custom menu, but here's a general procedure that should work in many cases.

In general to start the engine on a piston-engine type aircraft, you need:

  1. Fuel: some aircraft start the simulation with no fuel. You can add it in Equipment > Fuel and Payload.
  2. Correct mixture: this is generally rich, so push the red knob all the way in, or use the key m to enrich ( Shift+m leans.)
  3. Magnetos set on both: turn the key or press } three times to move through R, L, both.
  4. Throttle: some engines start better with a little gas.
  5. Run the starter: click the "start" position of the key on the panel, or press s. Hold the starter for sufficient time, even 10 seconds.

Starting all engines in a multi-engine aircraft is similar to the single engine--except you must follow the same start sequence for each and every engine. Flightgear provides a convenient way to do this for all engines at once: press ~ and all the procedure above will work for all the engines. Note though that the default 2-D panel is connected to only one engine and the ~ trick might not work. Also, give some gas to be sure that all the engines are on.

These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (Press ?) and/or at the aircraft's wiki. In general to start the engine on a jet engine type aircraft, you need to:

  1. Set cutoff ON
  2. Engage the starter
  3. Once the engines spools up to approximately 5% N1, set cutoff OFF
  4. Disengage the starter once the engine has reached operational speed

Online multiplayer flying

FlightGear has some multiplayer servers that will let you fly in more lively skies, see Howto: Multiplayer. There are also OpenRadar and ATC-pie, standalone programs that will let you be an air traffic controller.

There's also a multiplayer map that lets you see who's online right now,and even what navaids are nearby.

Learning to fly

Tutorials

Many aircrafts have their own tutorial. With tutorials, you can learn to operate particular aircrafts but also learn to fly. You can access tutorials by going to the "Help" menu and selecting "Tutorial." A great place to start is the tutorial for the Cessna 172p aircraft, commonly used in real life to learn to fly fixed-winged aircrafts. If the tutorial starts without a runway and surrounded by water, your setup of Flighgear is missing the scenery for the airport at which the tutorial was supposed to run. To fix the problem, you have to download scenery, which can be done by manually downloading the appropriate scenery, automatically downloading the scenery for the airport by enabling TerraSync by selecting "Download scenery automatically" from the "Downloads" section of the "Settings" menu of the Flightgear launcher, using the graphical Java-based tool TerraMaster (requiring the Java SE Runtime Environment) to download the appropriate scenery, or obtaining the necessary scenery also available for purchase on Blu-ray from the FlightGear store. [1]

Making your first flight

Realism

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 propeller torque and p-factor.

In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.

Here are some of the FlightGear realism points, 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 (more on this.)
  • The Vertical Speed Indicator (VSI) is also subject to error.
  • The Horizontal Situation Indicator (HSI) is driven by a gyroscope (that is why it's sometimes called a Directional Gyroscope), which is subject to gyro drift: the indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.
  • You cannot just cancel a turn or climb by centring the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not mantain its altitude or heading by itself- a common mistake is trying to find a hands off yoke position. While with trims one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yokes.

Many forces act on an aircraft in flight as well as on the avionics and instruments 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.

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. The launcher 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. What can you do? See Getting aeronautical charts.

In-sim, there is a map you can use in Equipment > Map, which will allow you to see navigation data and the position of airports and aids. For more help with navigation see Understanding Navigation.

Flying using the autopilot

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, you should 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 in some aircraft, including the Airbuses and the C172P.

The Cessna 172 comes with a Bendix/King KAP140 Autopilot in its virtual cockpit. You cannot use the Autopilot dialog from the menu with this aircraft. You must use the autopilot device in the panel.

The FlightGear community

Getting help

This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the User portal of this wiki, there are other pages you may want to read:

...and communication channels that can be used to obtain information or request help:

Customizing FlightGear without compiling it

Our website offers precompiled binaries for download and install on Windows and Mac OSX, while most Linux distros provide a packaged version in their repositories.

Although the install is binary, most of FlightGear's systems are open to configuration through XML files and NASAL scripting. You are free and encouraged to make changes to aircraft flight models, scenery, textures, OpenGL shaders and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the Developer portal.

How you can help

1rightarrow.png See Volunteer for the main article about this subject.

FlightGear is an opensource, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the forum and everything else. Volunteers, i.e. people that do things, are fundamental to this project: without them, it wouldn't make a single step forward. So it is essential that contributors have fun in what they do.

If you really plan to contribute to this project, you should take a look at some articles that will give you some hints:

There are never enough people contributing, and the fields where their help would be appreciated are many:

Testing
Support
Development
  • 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 or new features
    • get involved in any of the other FlightGear-affiliated projects
  • Aircraft development (3D modelling, textures, FDMs, scripting)
  • Scenery development (terrain, model, weather)