2
edits
New to FlightGear: Difference between revisions
→Tutorials
(→Making your first flight: cleanup, update, removed duplication) |
|||
| (29 intermediate revisions by 15 users not shown) | |||
| Line 10: | Line 10: | ||
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>.) | 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]]. | 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 | 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 | 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 on Mac OS X === | ||
| Line 50: | Line 49: | ||
In FlightGear, scenery is generally stored in you [[$FG_ROOT]] directory, and 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. | ||
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 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 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]. | 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!''' | ||
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 === | ||
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]]. | |||
== Running FlightGear == | == Running FlightGear == | ||
=== Starting FlightGear === | === Starting FlightGear === | ||
The easiest way to start FlightGear is | 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 <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: | 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: | ||
fgfs --launcher # opens the FlightGear Qt launcher | |||
fgfs --show-aircraft # displays a list of installed aircraft | fgfs --show-aircraft # displays a list of installed aircraft | ||
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list) | 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, yet even a cheap joystick would improve so much | 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). | 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, | 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 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. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected ({{key press|Ctrl|V}}). | 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. 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}}. | 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}}. | ||
| Line 87: | Line 89: | ||
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. | 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. | ||
Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models 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. | 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 === | === Starting the engine === | ||
| Line 108: | Line 110: | ||
=== Online multiplayer flying === | === Online multiplayer flying === | ||
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There | 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]]. | ||
There's also a [[MPMap|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 [[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/] | |||
== Making your first flight == | == Making your first flight == | ||
| Line 123: | Line 129: | ||
* The Vertical Speed Indicator (VSI) is also subject to error. | * 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. | * 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''. | 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. | 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]]. | ||
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]]. | 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]]. | ||
| Line 134: | Line 141: | ||
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. | 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 | 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]]. | ||
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 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. | ||
== Getting help == | == The FlightGear community == | ||
Besides this wiki, there are | === 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 [[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; | |||
* [[Frequently asked questions]]; | |||
...and communication channels that can be used to obtain information or request help: | |||
* The [[FlightGear Manual]], a ''must read'' for beginners; | |||
* [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. | * Documents bundled with the release package. | ||
=== Customizing FlightGear without compiling it === | |||
[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. | |||
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. | |||
If you really plan to contribute to this project, you should take a look at some articles that will give you some hints: | |||
* [[ | * [[Howto:Understand the FlightGear development process]] | ||
* [ | * [[Implementing new features for FlightGear]] | ||
* [[How the FlightGear project works]] | |||
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 : | |||
* Help new users with downloading, compiling, installing and running FlightGear ( | * Help new users with downloading, compiling, installing and running FlightGear (https://forum.flightgear.org or on IRC) | ||
* Provide | * 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 : | |||
* 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 | ||
** 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]] | ||
[[es:Nuevo para FlightGear]] | [[es:Nuevo para FlightGear]] | ||
[[fr:Nouveau sur flightgear]] | [[fr:Nouveau sur flightgear]] | ||
[[ | [[it:Nuovo per FlightGear]] | ||
[[ja:FlightGear入門]] | |||
[[nl:Nieuw bij FlightGear]] | |||
[[pt:Novo no FlightGear]] | |||
[[zh:FlightGear新手]] | [[zh:FlightGear新手]] | ||
[[ | [[th:New to FlightGear]] | ||