FlightGear wiki - User contributions [en]

Howto:Translate FlightGear

2025-03-27T10:08:31Z

CaptB: URL was 404, changed to work

FlightGear supports localization, that is, showing the user interface in the user's native language rather than in English.

This page will help you translate FlightGear to a new language or improve the existing translations.

== What can be translated ==
The following parts of the simulator can be translated:
* the menus, splash screens, startup tips and the text shown when the <code>--help</code> command-line option is used (FlightGear 2.7.0 and later)
* the shortcut file on Linux systems (FlightGear 2017.1 and later)
* the man pages (FlightGear 2017.3 and later)
* the built-in launcher (FlightGear 2018.3 and later)

== How to translate ==
# Determine the two letter ISO 639-1 language code for the language you want to translate FlightGear to. A list can be found on the [https://www.loc.gov/standards/iso639-2/php/code_list.php Library of Congress Web site].
# Check whether your language already has a subdirectory below [https://gitlab.com/flightgear/fgdata/-/tree/next/Translations?ref_type=heads the Translations directory]. If it does not, ask on the development mailing for the empty translation files to be created for you. (It's better to do this than copying an existing translation, because of data that will be accidentally included otherwise)
# Open the .XLF files in the subdirectory of your language and translate the English strings in them. You can edit the .XLF files in a text editor (such as Notepad++ or GEdit) but you can also use translation tools such as Qt Linguist or any XLIFF editor. Using a structured tool is recommended because it can track the translation state (flagging untranslated strings) and most tools include helpers to partially automate the translation process.
# Start FlightGear to test your translation. By default, the simulator will select the locale of your operating system as the language to use; you can explicitly select a language using the command-line option <code>--language=<i>language code</i></code>.
# Submit your updated .XLF files for inclusion via the development mailing list or a SourceForge merge request

There are two XLF files in each language subdirectory : one for the core simulator strings (startup messages, command line arg help, hints) and one for the launcher.

Note that the user interface might have not full Unicode support (some special/accented characters might not be shown): should you encounter such a location, please write to the flightgear-devel mailing list at {{Mailing list e-mail address|flightgear-devel}}.

== How to translate the shortcut file ==
Open [{{flightgear url|path=package/org.flightgear.FlightGear.desktop}} the FlightGear <code>.desktop</code> file] and translate the ''GenericName'', ''Comment'' and ''Keywords'' keys (add the ''GenericName[xx]'', ''Comment[xx]'' and ''Keywords[xx]'' keys, where ''xx'' is the two letter ISO 639-1 code of the language).

== How to translate the man pages ==
# Determine the two letter ISO 639-1 language code for the language you want to translate the man pages to.
# Check whether your language already has a subdirectory below [{{flightgear url|path=man}} the man pages directory]. If it does not, create an empty directory in it named after the language code, then copy <code>man1</code> and <code>man5</code> from the man pages directory to the directory of your language.
# Edit [{{flightgear url|path=man/CMakeLists.txt}} man/CMakeLists.txt] and add the instruction <code>add_subdirectory(xx)</code> in the <code>if(NOT WIN32)</code> block (where ''xx'' is the language code).
# Edit <code>man/xx/man1/CMakeLists.txt</code> and <code>man/xx/man5/CMakeLists.txt</code>: on the last row, set the installation directory (<code>DESTINATION</code>), respectively, to <code>${CMAKE_INSTALL_MANDIR}/xx/man1</code> and <code>${CMAKE_INSTALL_MANDIR}/xx/man5</code>.
# Open the man pages in the subdirectory of your language and translate them.

== Using QtLinguist to translate XLF Files ==

One can use QtLinguist (application from the QT package) to translate XLIFF files. Install QT package from the Qt home page (https://www.qt.io/download). Opening QtLinguist will show default translation environment. Open XLF file and start translating. The interface is divided into four main sections:

* Context - this is a grouping of the strings to translate. Defined by the developer. Icon beside the group show translation status. Everything should be in the end with the green check sign.
* Strings - strings in the selected group. Select string to translate it
* Sources and Forms - additional information about location of the translated string in the source code (not always visible and with correct information)
* Source text - the main place where translation occurs. Translate here selected strings.

One have to translate the original strings into the target language. Icon beside the original text in the 'Strings' section will show status. Green check mark when everything is correct. Yellow question mark, when the translation is in place but it it not marked as "verified". Untranslated strings are marked with the grey question mark. Sometimes QtLinguist displays exclamation mark - this shows that the translated text does not conform to the original text e.g. original text ends with the punctuation but the translated text not. Buttons (and keyboard shortcuts) on the main toolbar area helps with the strings matching. When the text is translated and you're comfortable with the style/meaning etc. you select green check mark button. It marks the translation as translated-verified. So this is the expected end state for this.

[[File:Qt Linquist.png|700px|frameless]]

Reference:
* [https://doc.qt.io/qt-5/qtlinguist-index.html Qt Linguist manual]
* [https://doc.qt.io/qt-5/linguist-translators.html Qt Linguist for translators guide]

== Related content ==
* [[Howto: Translate FlightGear Launch Control‎‎]]
* [[Translation requests]]

[[Category:Howto|Translate FlightGear]]

Grumman G-21 Goose

2020-12-23T10:39:36Z

CaptB:

{{infobox Aircraft
|image =Goose.JPG
|name =Grumman G21 Goose
|type =
|livery =
|authors =
|status =
|fdm =
|3dcockpit =
|carrier =
|fgname = goose
|note = The [http://ltts.crlt.indiana.edu/grn/flightgear/Goose.zip original download link] is dead.
}}
The '''Grumman G21 Goose''' is an eight seater amphibious aircraft, it first entered service in 1937, and saw service in WW2 with the US coastguard.

[[Category:Historical aircraft]]
[[Category:Flying boats]]

Ilyushin IL-96-400

2019-04-20T19:44:12Z

CaptB: Dead link(server not found on 20.04.2019)

{{infobox aircraft
| name = Il-96-400
| hangar = bermuda
| image = IL-96-400 Jet Airways.bmp
| type = Airliner
| config = Wide-body aircraft
| propulsion = Quadjet
| authors = Xsaint/Petar Jedvaj
| fdm = YASim/JSBSim
| fgname = IL-96-400 Long Ranger(T)
| status = Released
| note = The [http://fguk.eu/index.php/hangar/summary/9-civil-jets/383-il-96-400 original download link] is dead.
}}
The '''Ilyushin Il-96-400''' is a shortened, long-range, and advanced technology development of Russia's first widebody [[airliner]], the Ilyushin Il-86. It was developed with Russian avionics and engines. It is based on the Il-96M/T fuselage and is powered by four Aviadvigatel PS90-A1 turbofans. It can carry up to 436 passengers. Typical two-class configuration will have 386 passengers. Range with 315 passengers in a three-class configuration is about 10,000 km.<ref>{{cite web |url=http://en.wikipedia.org/wiki/IL-96-400 |title=Ilyushin Il-96 |work=Wikipedia }}</ref>

{{Appendix}}

Howto:Install aircraft

2019-04-10T08:13:52Z

CaptB:

{{installing}}
The latest official [[aircraft]] can be downloaded and installed with a single click through the aircraft tab in the [[FlightGear Qt launcher|built-in launcher]] see [[FlightGear Qt launcher]]. This article describes the manual process, only to be performed when not using the launcher.

== Installation process ==
Aircraft packages are available on [http://www.flightgear.org/download/ FlightGear.org Aircraft]. These require unzipping software to extract from a compressed file format. Then these must be manually installed in a FlightGear software installation to use. The details depend on the method of download, operating system, and user setup.

Alternatively if you are using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], or you wish to manage your aircraft collection using version control tools, the aircraft can be obtained directly from the [[FGAddon|official FlightGear aircraft repository - FGAddon]].

=== Linux ===
(Ubuntu 12.04)
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside <tt>/usr/share/games/flightgear/</tt>. For example, use <tt>/home/{YourUserName}/FlightGear/Aircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear. Append the root aircraft folder (<tt>/home/{YourUserName}/FlightGear/Aircraft</tt> in our example) to the [[$FG_AIRCRAFT]] list on the first page (previous to aircraft selection) of the launcher. Your aircraft should now show up in the list.

=== Macintosh OS X ===
First, We need to make sure that the FG application is in the application folder which can be done by simply dragging it into the applications folder from wherever it is currently located.
Now let's get down to actually adding aircraft:

# Go to applications in folder
# Control+Click FlightGear
# Click the second option which reads "Show Package Contents"
# Then click on the following folders: "Contents >> Resources >> data >> Aircraft"
# Now just click and drag the aircraft data downloaded from the FG website in the Aircraft folder

(Works on MacOS Sierra)

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\Documents\FlightGear\Aircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear. Append the root aircraft folder (<tt>C:\Users\{YourUserName}\Documents\FlightGear\Aircraft</tt> in our example) to the <tt>[[$FG_AIRCRAFT]]</tt> list on the first page (previous to aircraft selection) of the launcher. Your aircraft should now show up in the list.

== When installing an aircraft fails ==
=== Rename Aircraft Folder ===
If FlightGear fails to start with the new aircraft you have installed, or if it starts but the aircraft is invisible you might have to rename the folder where the aircraft files are.
This issue is most often encountered when downloading a .zip file from some online git repository. In those cases you will most likely end up with a folder name of the following form MyZippedRepo-[branch]. In this case you should rename the folder to be just '''MyZippedRepo'''.

If the above doesn't work, or for other cases, check for a readme file and have a look there for instructions.

Otherwise open the aircraft-set.xml file and search in it for paths containing '''Aircraft/AircraftFolderName'''. The name of the folder should match '''AircraftFolderName'''.

For instance if in the imaginary-set.xml you would find an instance like this:
<syntaxhighlight lang="xml">
<splash-texture>Aircraft/MyCreation/splash1.png</splash-texture>
</syntaxhighlight>
that means that you should rename the folder where imaginary-set.xml is to '''MyCreation'''.

=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:

$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'

If any of the methods above do not work, ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the [http://forum.flightgear.org/viewforum.php?f=11 forum].

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]

Normal Landing

2019-04-10T06:58:10Z

CaptB:

{{cleanup}}

This training flight develops the student's use of proper landing techniques to perform a normal or crosswind landing.

== Aim of a landing training ==
The Take off training should train/teach you...
* How to determine landing performance and limitations.
* Configuration, power, and trim.
* Obstructions and other hazards which should be considered.
* A stabilized approach at the recommended airspeed to the selected touchdown area.*
* Coordination of flight controls.
* A precise ground track.
* Wind shear and wake turbulence.
* Most suitable crosswind technique.
* Timing, judgment, and control technique during roundout and touchdown.
* Directional control after touchdown.
* Use of brakes.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 10 Minutes || 0:00 - 0:10
|-
| 2 || Travel to training area || 10 Minutes || 0:10 - 0:20
|-
| 3 || Instructor Demonstration || 10 Minutes || 0:20 - 0:30
|-
| 4 || Student Practice || 30 Minutes || 0:30 - 1:00
|-
| 5 || Return from practice area || 10 Minutes || 1:00 - 1:10
|-
| 6 || Post-flight Review || 10 Minutes || 1:10 - 1:20
|}

Total time: 1:20

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal or crosswind landing.
# Demonstrate normal and crosswind landing.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each landing [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each landing [[#Used abbreviations|IAW PTS]]

=== Common errors ===
* Failure to establish the approach or landing configuration at the appropriate time or in the proper sequence.
* Failure to establish and maintain a stabilized approach.
* Faulty technique during roundout and flare.
* Poor directional control during rollout.

== Introduction ==
Just as a successful takeoff is required for any flight, so must there be a successful landing. Most people will remember the landing more than the rest of the flight. It doesn’t matter how smooth the takeoff was and how uneventful the flight was, if the landing is poor, then the flight is poor. No two landings are ever the same. There is always something different about each landing. The trick is to have a baseline, recognize what has changed and adjust from there. This is where a stabilized approach comes in.

== Checklist for Flight ==
=== Lesson Requirements ===
## Task: Perform a normal or crosswind landing.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Exhibits knowledge of the elements related to a normal and crosswind approach and landing.
### Adequately surveys the intended landing area (ASES).
### Considers the wind conditions, landing surface, obstructions, and selects a suitable touchdown point.
### Establishes the recommended approach and landing configuration and airspeed, and adjusts pitch attitude and power as required.
### Maintains a stabilized approach and recommended airspeed, or in its absence, not more than 1.3 VSO, +10/-5 knots, with wind gust factor applied.
### Makes smooth, timely, and correct control application during the roundout and touchdown.
### Contacts the water at the proper pitch attitude (ASES).
### Touches down smoothly at approximate stalling speed (ASEL).
### Touches down at or within 400 feet (120 meters) beyond a specified point, with no drift, and with the airplane's longitudinal axis aligned with and over the runway center/landing path.
### Maintains crosswind correction and directional control throughout the approach and landing sequence.
### Completes the appropriate checklist.
# ELO: Understand the concept of a stabilized approach.
## What is a stabilized approach? It is an approach that essentially requires very little control input to land the plane. This means you are at the correct flap settings (usually full, but adjustments can be made based on conditions), gear position, airspeed (1.3VsO) and pitch attitude until you are ready to land the airplane. The idea is that you are not making any major adjustments once you are established on final.
Figure 1: Stabilized Approach
## Student Check:
### What is the approach speed for this airplane? _______
### What is the correct flap setting for this airplane on final? ______
# ELO: Adjust the approach for crosswind.
## What effect will a crosswind have on an approach? Just like any other time the airplane is in the air, the crosswind will push the airplane to one side of the runway.
## How do you correct the drifting tendency of the crosswind? There are two techniques. We will practice both of them. The first technique is a simple crab. Crab the airplane like you normally would for normal flight. The second method is to do the wing low method.
## Crab method.
### Crab like you normally would for flying.
### Maintain the crab until just before landing.
### Then kick in the appropriate rudder and lower the upwind wing. (wing low method).
### Land with one wing slightly lower than the other.
### This method requires good timing to ensure the plane does not drift sideways just prior to landing.
## Wing low method.
### Place the upwind wing down.
### Maintain directional control with the rudder.
### You will be cross controlled, this is ok. Maintain airspeed.
### Maintain this posture until you land.
# ELO: Identify the round out point.
## What is the round out point? The round out point is that point at which you will stop the descent of the airplane and begin the transition to flare and land the airplane.
## What is the benefit of the round out point? The round out point will allow you to land almost exactly where you want to every time.
## How do I pick out the round out point? Pick a point some distance before your desired touchdown point. (Try a couple hundred feet for a Cessna 172). Take care to pick a point close enough that you don’t land short. Once you pick out that, keep it in the same spot in your windshield. Pitch for airspeed, power for altitude. Fly to it. When you reach the round out point, stop the descent by pulling back gently on the yoke. Keep applying back pressure to complete the flare and touch down.
Figure 2: Roundout and Flare
# ELO: Identify common errors in approaches and landing.
Figure 3: Common Errors in Landing
# ELO: Perform a normal or crosswind landing.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Use either technique to correct for the crosswind. Stay lined up with the centerline.
## Ensure correct flaps, power and gear settings.
## Maintain correction through the roundout point.
## Begin the roundout. Make sure the wing in the crosswind is down.
## Idle power.
## Touchdown main wheels first. Hold the nose off the ground until it is ready to touch down. IT IS OK TO HEAR THE STALL WARNING HORN HERE.
## Apply the minimum required braking power. As the airspeed drops, pulling back on the yoke will help slow the airplane.
## Clear the runway when able. Complete the after landing check list.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Normal Landing

2019-04-10T06:57:20Z

CaptB: Cleanup. only "figure 1" etc remain which I don't know what to do with.

{{cleanup}}

This training flight develops the student's use of proper landing techniques to perform a normal or crosswind landing.

== Aim of a takeoff training ==
The Take off training should train/teach you...
OBJECTIVE: To conduct a normal or crosswind landing.

ELEMENTS:

* How to determine landing performance and limitations.
* Configuration, power, and trim.
* Obstructions and other hazards which should be considered.
* A stabilized approach at the recommended airspeed to the selected touchdown area.*
* Coordination of flight controls.
* A precise ground track.
* Wind shear and wake turbulence.
* Most suitable crosswind technique.
* Timing, judgment, and control technique during roundout and touchdown.
* Directional control after touchdown.
* Use of brakes.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 10 Minutes || 0:00 - 0:10
|-
| 2 || Travel to training area || 10 Minutes || 0:10 - 0:20
|-
| 3 || Instructor Demonstration || 10 Minutes || 0:20 - 0:30
|-
| 4 || Student Practice || 30 Minutes || 0:30 - 1:00
|-
| 5 || Return from practice area || 10 Minutes || 1:00 - 1:10
|-
| 6 || Post-flight Review || 10 Minutes || 1:10 - 1:20
|}

Total time: 1:20

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal or crosswind landing.
# Demonstrate normal and crosswind landing.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each landing [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each landing [[#Used abbreviations|IAW PTS]]

=== Common errors ===
* Failure to establish the approach or landing configuration at the appropriate time or in the proper sequence.
* Failure to establish and maintain a stabilized approach.
* Faulty technique during roundout and flare.
* Poor directional control during rollout.

== Introduction ==
Just as a successful takeoff is required for any flight, so must there be a successful landing. Most people will remember the landing more than the rest of the flight. It doesn’t matter how smooth the takeoff was and how uneventful the flight was, if the landing is poor, then the flight is poor. No two landings are ever the same. There is always something different about each landing. The trick is to have a baseline, recognize what has changed and adjust from there. This is where a stabilized approach comes in.

== Checklist for Flight ==
=== Lesson Requirements ===
## Task: Perform a normal or crosswind landing.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Exhibits knowledge of the elements related to a normal and crosswind approach and landing.
### Adequately surveys the intended landing area (ASES).
### Considers the wind conditions, landing surface, obstructions, and selects a suitable touchdown point.
### Establishes the recommended approach and landing configuration and airspeed, and adjusts pitch attitude and power as required.
### Maintains a stabilized approach and recommended airspeed, or in its absence, not more than 1.3 VSO, +10/-5 knots, with wind gust factor applied.
### Makes smooth, timely, and correct control application during the roundout and touchdown.
### Contacts the water at the proper pitch attitude (ASES).
### Touches down smoothly at approximate stalling speed (ASEL).
### Touches down at or within 400 feet (120 meters) beyond a specified point, with no drift, and with the airplane's longitudinal axis aligned with and over the runway center/landing path.
### Maintains crosswind correction and directional control throughout the approach and landing sequence.
### Completes the appropriate checklist.
# ELO: Understand the concept of a stabilized approach.
## What is a stabilized approach? It is an approach that essentially requires very little control input to land the plane. This means you are at the correct flap settings (usually full, but adjustments can be made based on conditions), gear position, airspeed (1.3VsO) and pitch attitude until you are ready to land the airplane. The idea is that you are not making any major adjustments once you are established on final.
Figure 1: Stabilized Approach
## Student Check:
### What is the approach speed for this airplane? _______
### What is the correct flap setting for this airplane on final? ______
# ELO: Adjust the approach for crosswind.
## What effect will a crosswind have on an approach? Just like any other time the airplane is in the air, the crosswind will push the airplane to one side of the runway.
## How do you correct the drifting tendency of the crosswind? There are two techniques. We will practice both of them. The first technique is a simple crab. Crab the airplane like you normally would for normal flight. The second method is to do the wing low method.
## Crab method.
### Crab like you normally would for flying.
### Maintain the crab until just before landing.
### Then kick in the appropriate rudder and lower the upwind wing. (wing low method).
### Land with one wing slightly lower than the other.
### This method requires good timing to ensure the plane does not drift sideways just prior to landing.
## Wing low method.
### Place the upwind wing down.
### Maintain directional control with the rudder.
### You will be cross controlled, this is ok. Maintain airspeed.
### Maintain this posture until you land.
# ELO: Identify the round out point.
## What is the round out point? The round out point is that point at which you will stop the descent of the airplane and begin the transition to flare and land the airplane.
## What is the benefit of the round out point? The round out point will allow you to land almost exactly where you want to every time.
## How do I pick out the round out point? Pick a point some distance before your desired touchdown point. (Try a couple hundred feet for a Cessna 172). Take care to pick a point close enough that you don’t land short. Once you pick out that, keep it in the same spot in your windshield. Pitch for airspeed, power for altitude. Fly to it. When you reach the round out point, stop the descent by pulling back gently on the yoke. Keep applying back pressure to complete the flare and touch down.
Figure 2: Roundout and Flare
# ELO: Identify common errors in approaches and landing.
Figure 3: Common Errors in Landing
# ELO: Perform a normal or crosswind landing.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Use either technique to correct for the crosswind. Stay lined up with the centerline.
## Ensure correct flaps, power and gear settings.
## Maintain correction through the roundout point.
## Begin the roundout. Make sure the wing in the crosswind is down.
## Idle power.
## Touchdown main wheels first. Hold the nose off the ground until it is ready to touch down. IT IS OK TO HEAR THE STALL WARNING HORN HERE.
## Apply the minimum required braking power. As the airspeed drops, pulling back on the yoke will help slow the airplane.
## Clear the runway when able. Complete the after landing check list.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Take Off

2019-04-10T06:48:02Z

CaptB:

This training flight develops the student's use of proper takeoff techniques for a given situation.

== Aim of a takeoff training ==
The Take off training should train/teach you...

* Review of wind conditions and takeoff surface.
* Takeoff hazards including windshear and wake turbulence.
* Use of wing flaps.
* Alignment with takeoff path.
* Initial positioning of flight controls.
* Power application.
* Directional control during acceleration on the surface.
* Crosswind control technique during acceleration on the surface, lift-off attitude and airspeed.
* Use of ground effect.
* Climb attitude, power setting, and airspeed (Vy or Vx).
* Crosswind correction and track during climb.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 15 Minutes || 0:00 - 0:15
|-
| 2 || Travel to training area || 10 Minutes || 0:15 - 0:25
|-
| 3 || Instructor Demonstration || 20 Minutes || 0:25 - 0:45
|-
| 4 || Student Practice || 45 Minutes || 0:45 - 1:30
|-
| 5 || Return from practice area || 10 Minutes || 1:30 - 1:40
|-
| 6 || Post-flight Review || 20 Minutes || 1:40 - 1:20
|}

Total time: 2:00

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal takeoff.
# Demonstrate normal takeoff.
# Demonstrate crosswind takeoff.
# Demonstrate short field takeoff.
# Demonstrate soft field takeoff.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each takeoff [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each takeoff [[#Used abbreviations|IAW PTS]]

=== Common errors ===
* Normal/Crosswind Takeoffs
** Improper initial positioning or flight controls and wing flaps.
** Improper power application.
** Inappropriate removal of hand from throttle.
** Poor directional control.
** Improper use of ailerons.
** Improper pitch attitude during liftoff.
** Failure to establish and maintain proper climb configuration and airspeed.
** Drift during climb.

* Short-field Takeoffs
** Failure to position the airplane for maximum utilization of available takeoff area.
** Improper initial positioning or flight controls and wing flaps.
** Improper power application.
** Inappropriate removal of hand from throttle.
** Poor directional control.
** Improper use of ailerons.
** Improper pitch attitude during liftoff.
** Failure to establish and maintain proper climb configuration and airspeed.
** Drift during climb.

* Soft-field Takeoffs
** Improper initial positioning or flight controls and wing flaps.
** Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
** Improper power application.
** Inappropriate removal of hand from throttle.
** Poor directional control.
** Improper use of brakes.
** Improper pitch attitude during takeoff.
** Hazards of settling back to takeoff surface after becoming airborne.
** Failure to establish and maintain proper climb configuration.
** Drift during climb.

== Introduction ==

Takeoffs are central to being able to get into the air. In many cases the takeoff is the easiest of all flight maneuvers. Just because it is easy doesn’t mean that it should be taken for granted. Takeoffs occur in a wide variety of weather conditions. First we are going to perform a normal takeoff. Oddly enough this is the least common type of takeoff. Very rarely will the airplane be traveling down a runway perfectly aligned with the current winds. The most common type of takeoff you will experience will be the crosswind takeoff. Once you have mastered these two types of takeoffs, we will learn how to do the short field and soft field takeoffs. These two are really just variations of the normal takeoff, so don’t be too frightened of them. Today we will practice these takeoffs. During your training , we will continue to practice them until you are confident you can takeoff under most circumstances.

== Checklist for Flight ==
=== Lesson Requirements ===
## Task: Perform a takeoff.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Normal/Crosswind Takeoff:
### Exhibits knowledge of the elements related to a normal and crosswind takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off, and accelerates to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Short Field Takeoff:
### Exhibits knowledge of the elements related to a short-field takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position so as to allow maximum utilization of available takeoff area and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off and accelerates to the recommended obstacle clearance airspeed or V X .
### Establishes the pitch attitude for the recommended obstacle clearance airspeed, or V X , and maintains that airspeed, +10/-5 knots, until the obstacle is cleared, or until the airplane is 50 feet (20 meters) above the surface.
### After clearing the obstacle, accelerates to V Y , establishes the pitch attitude for V Y , and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Soft Field Takeoff:
### Exhibits knowledge of the elements related to a soft-field takeoff and climb.
### Positions the flight controls for the existing wind conditions and so as to maximize lift as quickly as possible; sets the flaps as recommended.
### Clears the area; taxies onto the takeoff surface at a speed consistent with safety and aligns the airplane without stopping while advancing the throttle smoothly to takeoff power.
### Establishes and maintains the pitch attitude that will transfer the weight of the airplane from the wheels to the wings as rapidly as possible.
### Lifts off and remains in ground effect while accelerating to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

# ELO: Understand a crosswind and its effects on an aircraft on the ground.
## What is a crosswind component? The crosswind component is that wind that is not blowing directly down the runway.
## What effect does crosswind have on the airplane on the ground? Crosswinds have the tendency to lift one of the wings higher than the other. When this occurs on the ground, there is the potential to cause the aircraft to have the opposite wing hit the ground. This is why we use the crosswind taxi technique.
## What is the crosswind taxi technique? Simply put it is an attempt to minimize the effect of the crosswind on the airplane. A simple memory tool is to “climb into” a crosswind coming from the front and to “dive away from” a crosswind coming from the tail.
## Student Check:
### What is the maximum crosswind component of this airplane? _______
### What could happen if you exceed the maximum crosswind component? ______

# ELO: Identify the effects of crosswind on takeoff.
## What effect does crosswind have on takeoff? Aside from what we discussed earlier, the crosswind will tend to push the airplane to the side of the runway as the airplane gets airborne. This is why we takeoff with aileron down into the crosswind and then upon lift off assume a crab into the wind.
## What effect will gusting winds have on takeoff? Gusts can stop in the middle of the takeoff. If this occurs, there may not be enough air moving over the wings to keep takeoff lift. This may cause the airplane to settle back onto the runway. We minimize this by obtaining a higher than normal takeoff speed prior to lift off.

# ELO: Identify common errors in the normal takeoff.

## Improper initial positioning or flight controls and wing flaps.

## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# Student Check:
## What is Vx on this aircraft? ________
## What is Vy on this aircraft? ________

# ELO: Perform a normal takeoff.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
## For retractable gear aircraft, retract the gear when there is no useable runway left.
## For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in crosswind takeoffs. The same as above plus:
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
vDrift during climb.

# ELO: Perform a crosswind takeoff.
## Why use crosswind take off techniques? A crosswind tends to lift one of the wings off the ground and could potentially cause an airplane to tip over. During take off, the crosswind could cause the airplane to skip sideways along the runway. This put tremendous loads on the landing gear and could in some instances cause the gear to collapse. Proper crosswind technique minimizes these effects. In simple terms, you keep the wing in the crosswind DOWN until you are airborne. You will lift off with a greater airspeed than normal to help you control the airplane. Otherwise the take off is the same as a normal take off. You may find yourself combining this takeoff with soft or short field takeoffs. Because the wind rarely blows down the center of any runway, this will become your most used takeoff procedure. Always apply full aileron deflection into the crosswind and neutralize it enough to keep the wings level.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL aileron down into the wind. This prevents that wing from rising in the wind.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed.
### Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
### Keep the aileron into the wind DOWN until the crosswind becomes more of a headwind. As the ailerons become more effective you can return the yoke SLOWLY to neutral bank.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at a speed greater than Vy. This will counteract the effects of any gusts and ensure that the airplane does not settle back onto the runway if any gusts should stop.
## Wings level.
## Crab into the wind.
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in short field takeoffs.
## Failure to position the airplane for maximum utilization of available takeoff area.
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# ELO: Perform a short field takeoff.
## This takeoff assumes you have a very short runway and there is a 50 foot obstacle at the end of the runway you must clear. You have to get the airplane as high as you can get it in a very short time. You do this by starting your takeoff roll at the runway’s edge with the engine already at full power. You then climb out at Vx (or best angle of climb) until you clear the obstacle. Then climb out as normal.

## Align the airplane with the runway. Make sure the plane is on the centerline at the END of the runway. You need all the runway you can get!!!!
## Make sure you have the proper flap setting. (Usually 20 degrees or so) You need all the lift you can get.
## Both feet on the rudder pedals.
## Apply full braking power so the plane cannot move.
## Apply FULL power. Hold the brakes.
## Check engine instruments and make sure they are operating correctly.
## Release brakes.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vx (best angle of climb). Maintain Vx until you clear obstacles at the end of the runway. (PTS assumes 50 foot obstacle)
## After clearing the obstacle accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in soft field takeoffs.
## Improper initial positioning or flight controls and wing flaps.
## Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of brakes.
## Improper pitch attitude during takeoff.
## Hazards of settling back to takeoff surface after becoming airborne.
## Failure to establish and maintain proper climb configuration.
## Drift during climb.

# ELO: Perform a soft field takeoff.
## Wet grass or mud can cause a runway to be so soft that the airplane’s takeoff performance is seriously compromised. The landing gear could even get stuck during the takeoff roll. The intent is to transfer the weight of the airplane from the landing gear to the wings as quickly as possible. In essence you will get flying before you are supposed to. You get the plane airborne at a very low airspeed and stay in ground effect until the airplane accelerates to a safe climb speed.
## Keep back pressure on the elevator. This includes during the taxi. This keeps the nose wheel off the ground and helps prevent it from getting stuck in the mud or some other substance.
## Align the airplane with the runway. Make sure the plane is on the centerline. DO NOT STOP!!!
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You will need to apply right rudder to counter-act yaw to the left.
## Keeping back pressure on the elevator, allow the nose to lift off the ground, the plane will fly “sooner than it is ready”. This is ok.
## As soon as the plane is airborne, bring the nose level. Keep the airplane in ground effect unto you reach Vx.
## At Vx begin to climb until you clear any obstacles. (PTS assumes 50 foot obstacle)
## After clearing any obstacles accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Take Off

2019-04-10T06:45:58Z

CaptB:

This training flight develops the student's use of proper takeoff techniques for a given situation.

== Aim of a takeoff training ==
The Take off training should train/teach you...

* Review of wind conditions and takeoff surface.
* Takeoff hazards including windshear and wake turbulence.
* Use of wing flaps.
* Alignment with takeoff path.
* Initial positioning of flight controls.
* Power application.
* Directional control during acceleration on the surface.
* Crosswind control technique during acceleration on the surface, lift-off attitude and airspeed.
* Use of ground effect.
* Climb attitude, power setting, and airspeed (Vy or Vx).
* Crosswind correction and track during climb.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 15 Minutes || 0:00 - 0:15
|-
| 2 || Travel to training area || 10 Minutes || 0:15 - 0:25
|-
| 3 || Instructor Demonstration || 20 Minutes || 0:25 - 0:45
|-
| 4 || Student Practice || 45 Minutes || 0:45 - 1:30
|-
| 5 || Return from practice area || 10 Minutes || 1:30 - 1:40
|-
| 6 || Post-flight Review || 20 Minutes || 1:40 - 1:20
|}

Total time: 2:00

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal takeoff.
# Demonstrate normal takeoff.
# Demonstrate crosswind takeoff.
# Demonstrate short field takeoff.
# Demonstrate soft field takeoff.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each takeoff [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each takeoff [[#Used abbreviations|IAW PTS]]

=== Common errors ===
* Normal/Crosswind Takeoffs
** Improper initial positioning or flight controls and wing flaps.
** Improper power application.
** Inappropriate removal of hand from throttle.
** Poor directional control.
** Improper use of ailerons.
** Improper pitch attitude during liftoff.
** Failure to establish and maintain proper climb configuration and airspeed.
** Drift during climb.

* Short-field Takeoffs
** Failure to position the airplane for maximum utilization of available takeoff area.
** Improper initial positioning or flight controls and wing flaps.
** Improper power application.
** Inappropriate removal of hand from throttle.
** Poor directional control.
** Improper use of ailerons.
** Improper pitch attitude during liftoff.
** Failure to establish and maintain proper climb configuration and airspeed.
** Drift during climb.

* Soft-field Takeoffs
** Improper initial positioning or flight controls and wing flaps.
** Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
** Improper power application.
** Inappropriate removal of hand from throttle.
** Poor directional control.
** Improper use of brakes.
** Improper pitch attitude during takeoff.
** Hazards of settling back to takeoff surface after becoming airborne.
** Failure to establish and maintain proper climb configuration.
** Drift during climb.

== Introduction ==

Takeoffs are central to being able to get into the air. In many cases the takeoff is the easiest of all flight maneuvers. Just because it is easy doesn’t mean that it should be taken for granted. Takeoffs occur in a wide variety of weather conditions. First we are going to perform a normal takeoff. Oddly enough this is the least common type of takeoff. Very rarely will the airplane be traveling down a runway perfectly aligned with the current winds. The most common type of takeoff you will experience will be the crosswind takeoff. Once you have mastered these two types of takeoffs, we will learn how to do the short field and soft field takeoffs. These two are really just variations of the normal takeoff, so don’t be too frightened of them. Today we will practice these takeoffs. During your training , we will continue to practice them until you are confident you can takeoff under most circumstances.

== Checklist for Flight ==
=== Lesson Requirements ===

## Task: Perform a takeoff.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Normal/Crosswind Takeoff:
### Exhibits knowledge of the elements related to a normal and crosswind takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off, and accelerates to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Short Field Takeoff:
### Exhibits knowledge of the elements related to a short-field takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position so as to allow maximum utilization of available takeoff area and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off and accelerates to the recommended obstacle clearance airspeed or V X .
### Establishes the pitch attitude for the recommended obstacle clearance airspeed, or V X , and maintains that airspeed, +10/-5 knots, until the obstacle is cleared, or until the airplane is 50 feet (20 meters) above the surface.
### After clearing the obstacle, accelerates to V Y , establishes the pitch attitude for V Y , and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Soft Field Takeoff:
### Exhibits knowledge of the elements related to a soft-field takeoff and climb.
### Positions the flight controls for the existing wind conditions and so as to maximize lift as quickly as possible; sets the flaps as recommended.
### Clears the area; taxies onto the takeoff surface at a speed consistent with safety and aligns the airplane without stopping while advancing the throttle smoothly to takeoff power.
### Establishes and maintains the pitch attitude that will transfer the weight of the airplane from the wheels to the wings as rapidly as possible.
### Lifts off and remains in ground effect while accelerating to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

# ELO: Understand a crosswind and its effects on an aircraft on the ground.
## What is a crosswind component? The crosswind component is that wind that is not blowing directly down the runway.
## What effect does crosswind have on the airplane on the ground? Crosswinds have the tendency to lift one of the wings higher than the other. When this occurs on the ground, there is the potential to cause the aircraft to have the opposite wing hit the ground. This is why we use the crosswind taxi technique.
## What is the crosswind taxi technique? Simply put it is an attempt to minimize the effect of the crosswind on the airplane. A simple memory tool is to “climb into” a crosswind coming from the front and to “dive away from” a crosswind coming from the tail.
## Student Check:
### What is the maximum crosswind component of this airplane? _______
### What could happen if you exceed the maximum crosswind component? ______

# ELO: Identify the effects of crosswind on takeoff.
## What effect does crosswind have on takeoff? Aside from what we discussed earlier, the crosswind will tend to push the airplane to the side of the runway as the airplane gets airborne. This is why we takeoff with aileron down into the crosswind and then upon lift off assume a crab into the wind.
## What effect will gusting winds have on takeoff? Gusts can stop in the middle of the takeoff. If this occurs, there may not be enough air moving over the wings to keep takeoff lift. This may cause the airplane to settle back onto the runway. We minimize this by obtaining a higher than normal takeoff speed prior to lift off.

# ELO: Identify common errors in the normal takeoff.

## Improper initial positioning or flight controls and wing flaps.

## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# Student Check:
## What is Vx on this aircraft? ________
## What is Vy on this aircraft? ________

# ELO: Perform a normal takeoff.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
## For retractable gear aircraft, retract the gear when there is no useable runway left.
## For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in crosswind takeoffs. The same as above plus:
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
vDrift during climb.

# ELO: Perform a crosswind takeoff.
## Why use crosswind take off techniques? A crosswind tends to lift one of the wings off the ground and could potentially cause an airplane to tip over. During take off, the crosswind could cause the airplane to skip sideways along the runway. This put tremendous loads on the landing gear and could in some instances cause the gear to collapse. Proper crosswind technique minimizes these effects. In simple terms, you keep the wing in the crosswind DOWN until you are airborne. You will lift off with a greater airspeed than normal to help you control the airplane. Otherwise the take off is the same as a normal take off. You may find yourself combining this takeoff with soft or short field takeoffs. Because the wind rarely blows down the center of any runway, this will become your most used takeoff procedure. Always apply full aileron deflection into the crosswind and neutralize it enough to keep the wings level.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL aileron down into the wind. This prevents that wing from rising in the wind.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed.
### Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
### Keep the aileron into the wind DOWN until the crosswind becomes more of a headwind. As the ailerons become more effective you can return the yoke SLOWLY to neutral bank.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at a speed greater than Vy. This will counteract the effects of any gusts and ensure that the airplane does not settle back onto the runway if any gusts should stop.
## Wings level.
## Crab into the wind.
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in short field takeoffs.
## Failure to position the airplane for maximum utilization of available takeoff area.
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# ELO: Perform a short field takeoff.
## This takeoff assumes you have a very short runway and there is a 50 foot obstacle at the end of the runway you must clear. You have to get the airplane as high as you can get it in a very short time. You do this by starting your takeoff roll at the runway’s edge with the engine already at full power. You then climb out at Vx (or best angle of climb) until you clear the obstacle. Then climb out as normal.

## Align the airplane with the runway. Make sure the plane is on the centerline at the END of the runway. You need all the runway you can get!!!!
## Make sure you have the proper flap setting. (Usually 20 degrees or so) You need all the lift you can get.
## Both feet on the rudder pedals.
## Apply full braking power so the plane cannot move.
## Apply FULL power. Hold the brakes.
## Check engine instruments and make sure they are operating correctly.
## Release brakes.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vx (best angle of climb). Maintain Vx until you clear obstacles at the end of the runway. (PTS assumes 50 foot obstacle)
## After clearing the obstacle accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in soft field takeoffs.
## Improper initial positioning or flight controls and wing flaps.
## Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of brakes.
## Improper pitch attitude during takeoff.
## Hazards of settling back to takeoff surface after becoming airborne.
## Failure to establish and maintain proper climb configuration.
## Drift during climb.

# ELO: Perform a soft field takeoff.
## Wet grass or mud can cause a runway to be so soft that the airplane’s takeoff performance is seriously compromised. The landing gear could even get stuck during the takeoff roll. The intent is to transfer the weight of the airplane from the landing gear to the wings as quickly as possible. In essence you will get flying before you are supposed to. You get the plane airborne at a very low airspeed and stay in ground effect until the airplane accelerates to a safe climb speed.
## Keep back pressure on the elevator. This includes during the taxi. This keeps the nose wheel off the ground and helps prevent it from getting stuck in the mud or some other substance.
## Align the airplane with the runway. Make sure the plane is on the centerline. DO NOT STOP!!!
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You will need to apply right rudder to counter-act yaw to the left.
## Keeping back pressure on the elevator, allow the nose to lift off the ground, the plane will fly “sooner than it is ready”. This is ok.
## As soon as the plane is airborne, bring the nose level. Keep the airplane in ground effect unto you reach Vx.
## At Vx begin to climb until you clear any obstacles. (PTS assumes 50 foot obstacle)
## After clearing any obstacles accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Take Off

2019-04-10T06:42:47Z

CaptB:

This training flight develops the student's use of proper takeoff techniques for a given situation.

== Aim of a takeoff training ==
The Take off training should train/teach you...

* Review of wind conditions and takeoff surface.
* Takeoff hazards including windshear and wake turbulence.
* Use of wing flaps.
* Alignment with takeoff path.
* Initial positioning of flight controls.
* Power application.
* Directional control during acceleration on the surface.
* Crosswind control technique during acceleration on the surface, lift-off attitude and airspeed.
* Use of ground effect.
* Climb attitude, power setting, and airspeed (Vy or Vx).
* Crosswind correction and track during climb.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 15 Minutes || 0:00 - 0:15
|-
| 2 || Travel to training area || 10 Minutes || 0:15 - 0:25
|-
| 3 || Instructor Demonstration || 20 Minutes || 0:25 - 0:45
|-
| 4 || Student Practice || 45 Minutes || 0:45 - 1:30
|-
| 5 || Return from practice area || 10 Minutes || 1:30 - 1:40
|-
| 6 || Post-flight Review || 20 Minutes || 1:40 - 1:20
|}

Total time: 2:00

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal takeoff.
# Demonstrate normal takeoff.
# Demonstrate crosswind takeoff.
# Demonstrate short field takeoff.
# Demonstrate soft field takeoff.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each takeoff [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each takeoff [[#Used abbreviations|IAW PTS]]

=== Common errors ===
A. Normal/Crosswind Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

B. Short-field Takeoffs
* Failure to position the airplane for maximum utilization of available takeoff area.
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

C. Soft-field Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of brakes.
* Improper pitch attitude during takeoff.
* Hazards of settling back to takeoff surface after becoming airborne.
* Failure to establish and maintain proper climb configuration.
* Drift during climb.

== Introduction ==

Takeoffs are central to being able to get into the air. In many cases the takeoff is the easiest of all flight maneuvers. Just because it is easy doesn’t mean that it should be taken for granted. Takeoffs occur in a wide variety of weather conditions. First we are going to perform a normal takeoff. Oddly enough this is the least common type of takeoff. Very rarely will the airplane be traveling down a runway perfectly aligned with the current winds. The most common type of takeoff you will experience will be the crosswind takeoff. Once you have mastered these two types of takeoffs, we will learn how to do the short field and soft field takeoffs. These two are really just variations of the normal takeoff, so don’t be too frightened of them. Today we will practice these takeoffs. During your training , we will continue to practice them until you are confident you can takeoff under most circumstances.

== Checklist for Flight ==
=== Lesson Requirements ===

## Task: Perform a takeoff.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Normal/Crosswind Takeoff:
### Exhibits knowledge of the elements related to a normal and crosswind takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off, and accelerates to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Short Field Takeoff:
### Exhibits knowledge of the elements related to a short-field takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position so as to allow maximum utilization of available takeoff area and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off and accelerates to the recommended obstacle clearance airspeed or V X .
### Establishes the pitch attitude for the recommended obstacle clearance airspeed, or V X , and maintains that airspeed, +10/-5 knots, until the obstacle is cleared, or until the airplane is 50 feet (20 meters) above the surface.
### After clearing the obstacle, accelerates to V Y , establishes the pitch attitude for V Y , and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Soft Field Takeoff:
### Exhibits knowledge of the elements related to a soft-field takeoff and climb.
### Positions the flight controls for the existing wind conditions and so as to maximize lift as quickly as possible; sets the flaps as recommended.
### Clears the area; taxies onto the takeoff surface at a speed consistent with safety and aligns the airplane without stopping while advancing the throttle smoothly to takeoff power.
### Establishes and maintains the pitch attitude that will transfer the weight of the airplane from the wheels to the wings as rapidly as possible.
### Lifts off and remains in ground effect while accelerating to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

# ELO: Understand a crosswind and its effects on an aircraft on the ground.
## What is a crosswind component? The crosswind component is that wind that is not blowing directly down the runway.
## What effect does crosswind have on the airplane on the ground? Crosswinds have the tendency to lift one of the wings higher than the other. When this occurs on the ground, there is the potential to cause the aircraft to have the opposite wing hit the ground. This is why we use the crosswind taxi technique.
## What is the crosswind taxi technique? Simply put it is an attempt to minimize the effect of the crosswind on the airplane. A simple memory tool is to “climb into” a crosswind coming from the front and to “dive away from” a crosswind coming from the tail.
## Student Check:
### What is the maximum crosswind component of this airplane? _______
### What could happen if you exceed the maximum crosswind component? ______

# ELO: Identify the effects of crosswind on takeoff.
## What effect does crosswind have on takeoff? Aside from what we discussed earlier, the crosswind will tend to push the airplane to the side of the runway as the airplane gets airborne. This is why we takeoff with aileron down into the crosswind and then upon lift off assume a crab into the wind.
## What effect will gusting winds have on takeoff? Gusts can stop in the middle of the takeoff. If this occurs, there may not be enough air moving over the wings to keep takeoff lift. This may cause the airplane to settle back onto the runway. We minimize this by obtaining a higher than normal takeoff speed prior to lift off.

# ELO: Identify common errors in the normal takeoff.

## Improper initial positioning or flight controls and wing flaps.

## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# Student Check:
## What is Vx on this aircraft? ________
## What is Vy on this aircraft? ________

# ELO: Perform a normal takeoff.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
## For retractable gear aircraft, retract the gear when there is no useable runway left.
## For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in crosswind takeoffs. The same as above plus:
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
vDrift during climb.

# ELO: Perform a crosswind takeoff.
## Why use crosswind take off techniques? A crosswind tends to lift one of the wings off the ground and could potentially cause an airplane to tip over. During take off, the crosswind could cause the airplane to skip sideways along the runway. This put tremendous loads on the landing gear and could in some instances cause the gear to collapse. Proper crosswind technique minimizes these effects. In simple terms, you keep the wing in the crosswind DOWN until you are airborne. You will lift off with a greater airspeed than normal to help you control the airplane. Otherwise the take off is the same as a normal take off. You may find yourself combining this takeoff with soft or short field takeoffs. Because the wind rarely blows down the center of any runway, this will become your most used takeoff procedure. Always apply full aileron deflection into the crosswind and neutralize it enough to keep the wings level.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL aileron down into the wind. This prevents that wing from rising in the wind.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed.
### Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
### Keep the aileron into the wind DOWN until the crosswind becomes more of a headwind. As the ailerons become more effective you can return the yoke SLOWLY to neutral bank.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at a speed greater than Vy. This will counteract the effects of any gusts and ensure that the airplane does not settle back onto the runway if any gusts should stop.
## Wings level.
## Crab into the wind.
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in short field takeoffs.
## Failure to position the airplane for maximum utilization of available takeoff area.
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# ELO: Perform a short field takeoff.
## This takeoff assumes you have a very short runway and there is a 50 foot obstacle at the end of the runway you must clear. You have to get the airplane as high as you can get it in a very short time. You do this by starting your takeoff roll at the runway’s edge with the engine already at full power. You then climb out at Vx (or best angle of climb) until you clear the obstacle. Then climb out as normal.

## Align the airplane with the runway. Make sure the plane is on the centerline at the END of the runway. You need all the runway you can get!!!!
## Make sure you have the proper flap setting. (Usually 20 degrees or so) You need all the lift you can get.
## Both feet on the rudder pedals.
## Apply full braking power so the plane cannot move.
## Apply FULL power. Hold the brakes.
## Check engine instruments and make sure they are operating correctly.
## Release brakes.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vx (best angle of climb). Maintain Vx until you clear obstacles at the end of the runway. (PTS assumes 50 foot obstacle)
## After clearing the obstacle accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in soft field takeoffs.
## Improper initial positioning or flight controls and wing flaps.
## Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of brakes.
## Improper pitch attitude during takeoff.
## Hazards of settling back to takeoff surface after becoming airborne.
## Failure to establish and maintain proper climb configuration.
## Drift during climb.

# ELO: Perform a soft field takeoff.
## Wet grass or mud can cause a runway to be so soft that the airplane’s takeoff performance is seriously compromised. The landing gear could even get stuck during the takeoff roll. The intent is to transfer the weight of the airplane from the landing gear to the wings as quickly as possible. In essence you will get flying before you are supposed to. You get the plane airborne at a very low airspeed and stay in ground effect until the airplane accelerates to a safe climb speed.
## Keep back pressure on the elevator. This includes during the taxi. This keeps the nose wheel off the ground and helps prevent it from getting stuck in the mud or some other substance.
## Align the airplane with the runway. Make sure the plane is on the centerline. DO NOT STOP!!!
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You will need to apply right rudder to counter-act yaw to the left.
## Keeping back pressure on the elevator, allow the nose to lift off the ground, the plane will fly “sooner than it is ready”. This is ok.
## As soon as the plane is airborne, bring the nose level. Keep the airplane in ground effect unto you reach Vx.
## At Vx begin to climb until you clear any obstacles. (PTS assumes 50 foot obstacle)
## After clearing any obstacles accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Take Off

2019-04-10T06:25:31Z

CaptB:

This training flight develops the student's use of proper takeoff techniques for a given situation.

== Aim of a takeoff training ==
The Take off training should train/teach you...

* Review of wind conditions and takeoff surface.
* Takeoff hazards including windshear and wake turbulence.
* Use of wing flaps.
* Alignment with takeoff path.
* Initial positioning of flight controls.
* Power application.
* Directional control during acceleration on the surface.
* Crosswind control technique during acceleration on the surface, lift-off attitude and airspeed.
* Use of ground effect.
* Climb attitude, power setting, and airspeed (Vy or Vx).
* Crosswind correction and track during climb.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 15 Minutes || 0:00 - 0:15
|-
| 2 || Travel to training area || 10 Minutes || 0:15 - 0:25
|-
| 3 || Instructor Demonstration || 20 Minutes || 0:25 - 0:45
|-
| 4 || Student Practice || 45 Minutes || 0:45 - 1:30
|-
| 5 || Return from practice area || 10 Minutes || 1:30 - 1:40
|-
| 6 || Post-flight Review || 20 Minutes || 1:40 - 1:20
|}

Total time: 2:00

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal takeoff.
# Demonstrate normal takeoff.
# Demonstrate crosswind takeoff.
# Demonstrate short field takeoff.
# Demonstrate soft field takeoff.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each takeoff [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each takeoff [[#Used abbreviations|IAW PTS]] the PTS.

=== Common errors ===
A. Normal/Crosswind Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

B. Short-field Takeoffs
* Failure to position the airplane for maximum utilization of available takeoff area.
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

C. Soft-field Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of brakes.
* Improper pitch attitude during takeoff.
* Hazards of settling back to takeoff surface after becoming airborne.
* Failure to establish and maintain proper climb configuration.
* Drift during climb.

== Introduction ==

Takeoffs are central to being able to get into the air. In many cases the takeoff is the easiest of all flight maneuvers. Just because it is easy doesn’t mean that it should be taken for granted. Takeoffs occur in a wide variety of weather conditions. First we are going to perform a normal takeoff. Oddly enough this is the least common type of takeoff. Very rarely will the airplane be traveling down a runway perfectly aligned with the current winds. The most common type of takeoff you will experience will be the crosswind takeoff. Once you have mastered these two types of takeoffs, we will learn how to do the short field and soft field takeoffs. These two are really just variations of the normal takeoff, so don’t be too frightened of them. Today we will practice these takeoffs. During your training , we will continue to practice them until you are confident you can takeoff under most circumstances.

== Checklist for Flight ==
=== Lesson Requirements ===

## Task: Perform a takeoff.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Normal/Crosswind Takeoff:
### Exhibits knowledge of the elements related to a normal and crosswind takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off, and accelerates to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Short Field Takeoff:
### Exhibits knowledge of the elements related to a short-field takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position so as to allow maximum utilization of available takeoff area and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off and accelerates to the recommended obstacle clearance airspeed or V X .
### Establishes the pitch attitude for the recommended obstacle clearance airspeed, or V X , and maintains that airspeed, +10/-5 knots, until the obstacle is cleared, or until the airplane is 50 feet (20 meters) above the surface.
### After clearing the obstacle, accelerates to V Y , establishes the pitch attitude for V Y , and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Soft Field Takeoff:
### Exhibits knowledge of the elements related to a soft-field takeoff and climb.
### Positions the flight controls for the existing wind conditions and so as to maximize lift as quickly as possible; sets the flaps as recommended.
### Clears the area; taxies onto the takeoff surface at a speed consistent with safety and aligns the airplane without stopping while advancing the throttle smoothly to takeoff power.
### Establishes and maintains the pitch attitude that will transfer the weight of the airplane from the wheels to the wings as rapidly as possible.
### Lifts off and remains in ground effect while accelerating to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

# ELO: Understand a crosswind and its effects on an aircraft on the ground.
## What is a crosswind component? The crosswind component is that wind that is not blowing directly down the runway.
## What effect does crosswind have on the airplane on the ground? Crosswinds have the tendency to lift one of the wings higher than the other. When this occurs on the ground, there is the potential to cause the aircraft to have the opposite wing hit the ground. This is why we use the crosswind taxi technique.
## What is the crosswind taxi technique? Simply put it is an attempt to minimize the effect of the crosswind on the airplane. A simple memory tool is to “climb into” a crosswind coming from the front and to “dive away from” a crosswind coming from the tail.
## Student Check:
### What is the maximum crosswind component of this airplane? _______
### What could happen if you exceed the maximum crosswind component? ______

# ELO: Identify the effects of crosswind on takeoff.
## What effect does crosswind have on takeoff? Aside from what we discussed earlier, the crosswind will tend to push the airplane to the side of the runway as the airplane gets airborne. This is why we takeoff with aileron down into the crosswind and then upon lift off assume a crab into the wind.
## What effect will gusting winds have on takeoff? Gusts can stop in the middle of the takeoff. If this occurs, there may not be enough air moving over the wings to keep takeoff lift. This may cause the airplane to settle back onto the runway. We minimize this by obtaining a higher than normal takeoff speed prior to lift off.

# ELO: Identify common errors in the normal takeoff.

## Improper initial positioning or flight controls and wing flaps.

## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# Student Check:
## What is Vx on this aircraft? ________
## What is Vy on this aircraft? ________

# ELO: Perform a normal takeoff.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
## For retractable gear aircraft, retract the gear when there is no useable runway left.
## For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in crosswind takeoffs. The same as above plus:
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
vDrift during climb.

# ELO: Perform a crosswind takeoff.
## Why use crosswind take off techniques? A crosswind tends to lift one of the wings off the ground and could potentially cause an airplane to tip over. During take off, the crosswind could cause the airplane to skip sideways along the runway. This put tremendous loads on the landing gear and could in some instances cause the gear to collapse. Proper crosswind technique minimizes these effects. In simple terms, you keep the wing in the crosswind DOWN until you are airborne. You will lift off with a greater airspeed than normal to help you control the airplane. Otherwise the take off is the same as a normal take off. You may find yourself combining this takeoff with soft or short field takeoffs. Because the wind rarely blows down the center of any runway, this will become your most used takeoff procedure. Always apply full aileron deflection into the crosswind and neutralize it enough to keep the wings level.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL aileron down into the wind. This prevents that wing from rising in the wind.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed.
### Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
### Keep the aileron into the wind DOWN until the crosswind becomes more of a headwind. As the ailerons become more effective you can return the yoke SLOWLY to neutral bank.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at a speed greater than Vy. This will counteract the effects of any gusts and ensure that the airplane does not settle back onto the runway if any gusts should stop.
## Wings level.
## Crab into the wind.
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in short field takeoffs.
## Failure to position the airplane for maximum utilization of available takeoff area.
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# ELO: Perform a short field takeoff.
## This takeoff assumes you have a very short runway and there is a 50 foot obstacle at the end of the runway you must clear. You have to get the airplane as high as you can get it in a very short time. You do this by starting your takeoff roll at the runway’s edge with the engine already at full power. You then climb out at Vx (or best angle of climb) until you clear the obstacle. Then climb out as normal.

## Align the airplane with the runway. Make sure the plane is on the centerline at the END of the runway. You need all the runway you can get!!!!
## Make sure you have the proper flap setting. (Usually 20 degrees or so) You need all the lift you can get.
## Both feet on the rudder pedals.
## Apply full braking power so the plane cannot move.
## Apply FULL power. Hold the brakes.
## Check engine instruments and make sure they are operating correctly.
## Release brakes.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vx (best angle of climb). Maintain Vx until you clear obstacles at the end of the runway. (PTS assumes 50 foot obstacle)
## After clearing the obstacle accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in soft field takeoffs.
## Improper initial positioning or flight controls and wing flaps.
## Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of brakes.
## Improper pitch attitude during takeoff.
## Hazards of settling back to takeoff surface after becoming airborne.
## Failure to establish and maintain proper climb configuration.
## Drift during climb.

# ELO: Perform a soft field takeoff.
## Wet grass or mud can cause a runway to be so soft that the airplane’s takeoff performance is seriously compromised. The landing gear could even get stuck during the takeoff roll. The intent is to transfer the weight of the airplane from the landing gear to the wings as quickly as possible. In essence you will get flying before you are supposed to. You get the plane airborne at a very low airspeed and stay in ground effect until the airplane accelerates to a safe climb speed.
## Keep back pressure on the elevator. This includes during the taxi. This keeps the nose wheel off the ground and helps prevent it from getting stuck in the mud or some other substance.
## Align the airplane with the runway. Make sure the plane is on the centerline. DO NOT STOP!!!
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You will need to apply right rudder to counter-act yaw to the left.
## Keeping back pressure on the elevator, allow the nose to lift off the ground, the plane will fly “sooner than it is ready”. This is ok.
## As soon as the plane is airborne, bring the nose level. Keep the airplane in ground effect unto you reach Vx.
## At Vx begin to climb until you clear any obstacles. (PTS assumes 50 foot obstacle)
## After clearing any obstacles accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Take Off

2019-04-10T06:24:56Z

CaptB:

{{cleanup}}

This training flight develops the student's use of proper takeoff techniques for a given situation.

== Aim of a takeoff training ==
The Take off training should train/teach you...

* Review of wind conditions and takeoff surface.
* Takeoff hazards including windshear and wake turbulence.
* Use of wing flaps.
* Alignment with takeoff path.
* Initial positioning of flight controls.
* Power application.
* Directional control during acceleration on the surface.
* Crosswind control technique during acceleration on the surface, lift-off attitude and airspeed.
* Use of ground effect.
* Climb attitude, power setting, and airspeed (Vy or Vx).
* Crosswind correction and track during climb.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 15 Minutes || 0:00 - 0:15
|-
| 2 || Travel to training area || 10 Minutes || 0:15 - 0:25
|-
| 3 || Instructor Demonstration || 20 Minutes || 0:25 - 0:45
|-
| 4 || Student Practice || 45 Minutes || 0:45 - 1:30
|-
| 5 || Return from practice area || 10 Minutes || 1:30 - 1:40
|-
| 6 || Post-flight Review || 20 Minutes || 1:40 - 1:20
|}

Total time: 2:00

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal takeoff.
# Demonstrate normal takeoff.
# Demonstrate crosswind takeoff.
# Demonstrate short field takeoff.
# Demonstrate soft field takeoff.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each takeoff [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each takeoff [[#Used abbreviations|IAW PTS]] the PTS.

=== Common errors ===
A. Normal/Crosswind Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

B. Short-field Takeoffs
* Failure to position the airplane for maximum utilization of available takeoff area.
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

C. Soft-field Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of brakes.
* Improper pitch attitude during takeoff.
* Hazards of settling back to takeoff surface after becoming airborne.
* Failure to establish and maintain proper climb configuration.
* Drift during climb.

== Introduction ==

Takeoffs are central to being able to get into the air. In many cases the takeoff is the easiest of all flight maneuvers. Just because it is easy doesn’t mean that it should be taken for granted. Takeoffs occur in a wide variety of weather conditions. First we are going to perform a normal takeoff. Oddly enough this is the least common type of takeoff. Very rarely will the airplane be traveling down a runway perfectly aligned with the current winds. The most common type of takeoff you will experience will be the crosswind takeoff. Once you have mastered these two types of takeoffs, we will learn how to do the short field and soft field takeoffs. These two are really just variations of the normal takeoff, so don’t be too frightened of them. Today we will practice these takeoffs. During your training , we will continue to practice them until you are confident you can takeoff under most circumstances.

== Checklist for Flight ==
=== Lesson Requirements ===

## Task: Perform a takeoff.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Normal/Crosswind Takeoff:
### Exhibits knowledge of the elements related to a normal and crosswind takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off, and accelerates to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Short Field Takeoff:
### Exhibits knowledge of the elements related to a short-field takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position so as to allow maximum utilization of available takeoff area and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off and accelerates to the recommended obstacle clearance airspeed or V X .
### Establishes the pitch attitude for the recommended obstacle clearance airspeed, or V X , and maintains that airspeed, +10/-5 knots, until the obstacle is cleared, or until the airplane is 50 feet (20 meters) above the surface.
### After clearing the obstacle, accelerates to V Y , establishes the pitch attitude for V Y , and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Soft Field Takeoff:
### Exhibits knowledge of the elements related to a soft-field takeoff and climb.
### Positions the flight controls for the existing wind conditions and so as to maximize lift as quickly as possible; sets the flaps as recommended.
### Clears the area; taxies onto the takeoff surface at a speed consistent with safety and aligns the airplane without stopping while advancing the throttle smoothly to takeoff power.
### Establishes and maintains the pitch attitude that will transfer the weight of the airplane from the wheels to the wings as rapidly as possible.
### Lifts off and remains in ground effect while accelerating to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

# ELO: Understand a crosswind and its effects on an aircraft on the ground.
## What is a crosswind component? The crosswind component is that wind that is not blowing directly down the runway.
## What effect does crosswind have on the airplane on the ground? Crosswinds have the tendency to lift one of the wings higher than the other. When this occurs on the ground, there is the potential to cause the aircraft to have the opposite wing hit the ground. This is why we use the crosswind taxi technique.
## What is the crosswind taxi technique? Simply put it is an attempt to minimize the effect of the crosswind on the airplane. A simple memory tool is to “climb into” a crosswind coming from the front and to “dive away from” a crosswind coming from the tail.
## Student Check:
### What is the maximum crosswind component of this airplane? _______
### What could happen if you exceed the maximum crosswind component? ______

# ELO: Identify the effects of crosswind on takeoff.
## What effect does crosswind have on takeoff? Aside from what we discussed earlier, the crosswind will tend to push the airplane to the side of the runway as the airplane gets airborne. This is why we takeoff with aileron down into the crosswind and then upon lift off assume a crab into the wind.
## What effect will gusting winds have on takeoff? Gusts can stop in the middle of the takeoff. If this occurs, there may not be enough air moving over the wings to keep takeoff lift. This may cause the airplane to settle back onto the runway. We minimize this by obtaining a higher than normal takeoff speed prior to lift off.

# ELO: Identify common errors in the normal takeoff.

## Improper initial positioning or flight controls and wing flaps.

## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# Student Check:
## What is Vx on this aircraft? ________
## What is Vy on this aircraft? ________

# ELO: Perform a normal takeoff.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
## For retractable gear aircraft, retract the gear when there is no useable runway left.
## For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in crosswind takeoffs. The same as above plus:
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
vDrift during climb.

# ELO: Perform a crosswind takeoff.
## Why use crosswind take off techniques? A crosswind tends to lift one of the wings off the ground and could potentially cause an airplane to tip over. During take off, the crosswind could cause the airplane to skip sideways along the runway. This put tremendous loads on the landing gear and could in some instances cause the gear to collapse. Proper crosswind technique minimizes these effects. In simple terms, you keep the wing in the crosswind DOWN until you are airborne. You will lift off with a greater airspeed than normal to help you control the airplane. Otherwise the take off is the same as a normal take off. You may find yourself combining this takeoff with soft or short field takeoffs. Because the wind rarely blows down the center of any runway, this will become your most used takeoff procedure. Always apply full aileron deflection into the crosswind and neutralize it enough to keep the wings level.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL aileron down into the wind. This prevents that wing from rising in the wind.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed.
### Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
### Keep the aileron into the wind DOWN until the crosswind becomes more of a headwind. As the ailerons become more effective you can return the yoke SLOWLY to neutral bank.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at a speed greater than Vy. This will counteract the effects of any gusts and ensure that the airplane does not settle back onto the runway if any gusts should stop.
## Wings level.
## Crab into the wind.
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in short field takeoffs.
## Failure to position the airplane for maximum utilization of available takeoff area.
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# ELO: Perform a short field takeoff.
## This takeoff assumes you have a very short runway and there is a 50 foot obstacle at the end of the runway you must clear. You have to get the airplane as high as you can get it in a very short time. You do this by starting your takeoff roll at the runway’s edge with the engine already at full power. You then climb out at Vx (or best angle of climb) until you clear the obstacle. Then climb out as normal.

## Align the airplane with the runway. Make sure the plane is on the centerline at the END of the runway. You need all the runway you can get!!!!
## Make sure you have the proper flap setting. (Usually 20 degrees or so) You need all the lift you can get.
## Both feet on the rudder pedals.
## Apply full braking power so the plane cannot move.
## Apply FULL power. Hold the brakes.
## Check engine instruments and make sure they are operating correctly.
## Release brakes.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vx (best angle of climb). Maintain Vx until you clear obstacles at the end of the runway. (PTS assumes 50 foot obstacle)
## After clearing the obstacle accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in soft field takeoffs.
## Improper initial positioning or flight controls and wing flaps.
## Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of brakes.
## Improper pitch attitude during takeoff.
## Hazards of settling back to takeoff surface after becoming airborne.
## Failure to establish and maintain proper climb configuration.
## Drift during climb.

# ELO: Perform a soft field takeoff.
## Wet grass or mud can cause a runway to be so soft that the airplane’s takeoff performance is seriously compromised. The landing gear could even get stuck during the takeoff roll. The intent is to transfer the weight of the airplane from the landing gear to the wings as quickly as possible. In essence you will get flying before you are supposed to. You get the plane airborne at a very low airspeed and stay in ground effect until the airplane accelerates to a safe climb speed.
## Keep back pressure on the elevator. This includes during the taxi. This keeps the nose wheel off the ground and helps prevent it from getting stuck in the mud or some other substance.
## Align the airplane with the runway. Make sure the plane is on the centerline. DO NOT STOP!!!
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You will need to apply right rudder to counter-act yaw to the left.
## Keeping back pressure on the elevator, allow the nose to lift off the ground, the plane will fly “sooner than it is ready”. This is ok.
## As soon as the plane is airborne, bring the nose level. Keep the airplane in ground effect unto you reach Vx.
## At Vx begin to climb until you clear any obstacles. (PTS assumes 50 foot obstacle)
## After clearing any obstacles accelerate to Vy.
### For retractable gear aircraft, retract the gear when there is no useable runway left.
### For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Continue to climb out according to departure procedure/instructions.
## Pitch for airspeed.
## Trim to relieve pressures.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Take Off

2019-04-10T06:15:27Z

CaptB:

{{cleanup}}

This training flight develops the student's use of proper takeoff techniques for a given situation.

== Aim of a takeoff training ==
The Take off training should train/teach you...

* Review of wind conditions and takeoff surface.
* Takeoff hazards including windshear and wake turbulence.
* Use of wing flaps.
* Alignment with takeoff path.
* Initial positioning of flight controls.
* Power application.
* Directional control during acceleration on the surface.
* Crosswind control technique during acceleration on the surface, lift-off attitude and airspeed.
* Use of ground effect.
* Climb attitude, power setting, and airspeed (Vy or Vx).
* Crosswind correction and track during climb.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 15 Minutes || 0:00 - 0:15
|-
| 2 || Travel to training area || 10 Minutes || 0:15 - 0:25
|-
| 3 || Instructor Demonstration || 20 Minutes || 0:25 - 0:45
|-
| 4 || Student Practice || 45 Minutes || 0:45 - 1:30
|-
| 5 || Return from practice area || 10 Minutes || 1:30 - 1:40
|-
| 6 || Post-flight Review || 20 Minutes || 1:40 - 1:20
|}

Total time: 2:00

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal takeoff.
# Demonstrate normal takeoff.
# Demonstrate crosswind takeoff.
# Demonstrate short field takeoff.
# Demonstrate soft field takeoff.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each takeoff [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each takeoff [[#Used abbreviations|IAW PTS]] the PTS.

=== Common errors ===
A. Normal/Crosswind Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

B. Short-field Takeoffs
* Failure to position the airplane for maximum utilization of available takeoff area.
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

C. Soft-field Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of brakes.
* Improper pitch attitude during takeoff.
* Hazards of settling back to takeoff surface after becoming airborne.
* Failure to establish and maintain proper climb configuration.
* Drift during climb.

== Introduction ==

Takeoffs are central to being able to get into the air. In many cases the takeoff is the easiest of all flight maneuvers. Just because it is easy doesn’t mean that it should be taken for granted. Takeoffs occur in a wide variety of weather conditions. First we are going to perform a normal takeoff. Oddly enough this is the least common type of takeoff. Very rarely will the airplane be traveling down a runway perfectly aligned with the current winds. The most common type of takeoff you will experience will be the crosswind takeoff. Once you have mastered these two types of takeoffs, we will learn how to do the short field and soft field takeoffs. These two are really just variations of the normal takeoff, so don’t be too frightened of them. Today we will practice these takeoffs. During your training , we will continue to practice them until you are confident you can takeoff under most circumstances.

== Checklist for Flight ==
=== Lesson Requirements ===

## Task: Perform a takeoff.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Normal/Crosswind Takeoff:
### Exhibits knowledge of the elements related to a normal and crosswind takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off, and accelerates to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Short Field Takeoff:
### Exhibits knowledge of the elements related to a short-field takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position so as to allow maximum utilization of available takeoff area and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off and accelerates to the recommended obstacle clearance airspeed or V X .
### Establishes the pitch attitude for the recommended obstacle clearance airspeed, or V X , and maintains that airspeed, +10/-5 knots, until the obstacle is cleared, or until the airplane is 50 feet (20 meters) above the surface.
### After clearing the obstacle, accelerates to V Y , establishes the pitch attitude for V Y , and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Soft Field Takeoff:
### Exhibits knowledge of the elements related to a soft-field takeoff and climb.
### Positions the flight controls for the existing wind conditions and so as to maximize lift as quickly as possible; sets the flaps as recommended.
### Clears the area; taxies onto the takeoff surface at a speed consistent with safety and aligns the airplane without stopping while advancing the throttle smoothly to takeoff power.
### Establishes and maintains the pitch attitude that will transfer the weight of the airplane from the wheels to the wings as rapidly as possible.
### Lifts off and remains in ground effect while accelerating to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

# ELO: Understand a crosswind and its effects on an aircraft on the ground.
## What is a crosswind component? The crosswind component is that wind that is not blowing directly down the runway.
## What effect does crosswind have on the airplane on the ground? Crosswinds have the tendency to lift one of the wings higher than the other. When this occurs on the ground, there is the potential to cause the aircraft to have the opposite wing hit the ground. This is why we use the crosswind taxi technique.
## What is the crosswind taxi technique? Simply put it is an attempt to minimize the effect of the crosswind on the airplane. A simple memory tool is to “climb into” a crosswind coming from the front and to “dive away from” a crosswind coming from the tail.
## Student Check:
### What is the maximum crosswind component of this airplane? _______
### What could happen if you exceed the maximum crosswind component? ______

# ELO: Identify the effects of crosswind on takeoff.
## What effect does crosswind have on takeoff? Aside from what we discussed earlier, the crosswind will tend to push the airplane to the side of the runway as the airplane gets airborne. This is why we takeoff with aileron down into the crosswind and then upon lift off assume a crab into the wind.
## What effect will gusting winds have on takeoff? Gusts can stop in the middle of the takeoff. If this occurs, there may not be enough air moving over the wings to keep takeoff lift. This may cause the airplane to settle back onto the runway. We minimize this by obtaining a higher than normal takeoff speed prior to lift off.

# ELO: Identify common errors in the normal takeoff.

## Improper initial positioning or flight controls and wing flaps.

## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
## Drift during climb.

# Student Check:
## What is Vx on this aircraft? ________
## What is Vy on this aircraft? ________

# ELO: Perform a normal takeoff.
## Align the airplane with the runway. Make sure the plane is on the centerline.
## Both feet on the rudder pedals. Heels on the floor, away from the brakes.
## Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.
## Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
## Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.
## Lift off at Vy (best rate of climb).
## Continue to climb out according to departure procedure/instructions.
## For retractable gear aircraft, retract the gear when there is no useable runway left.
## For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.
## Pitch for airspeed.
## Trim to relieve pressures.

# ELO: Identify and correct common errors in crosswind takeoffs. The same as above plus:
## Improper initial positioning or flight controls and wing flaps.
## Improper power application.
## Inappropriate removal of hand from throttle.
## Poor directional control.
## Improper use of ailerons.
## Improper pitch attitude during liftoff.
## Failure to establish and maintain proper climb configuration and airspeed.
vDrift during climb.

G. ELO 6: Perform a crosswind takeoff.

1. Why use crosswind take off techniques? A crosswind tends to lift one of the wings off the ground and could potentially cause an airplane to tip over. During take off, the crosswind could cause the airplane to skip sideways along the runway. This put tremendous loads on the landing gear and could in some instances cause the gear to collapse. Proper crosswind technique minimizes these effects. In simple terms, you keep the wing in the crosswind DOWN until you are airborne. You will lift off with a greater airspeed than normal to help you control the airplane. Otherwise the take off is the same as a normal take off. You may find yourself combining this takeoff with soft or short field takeoffs. Because the wind rarely blows down the center of any runway, this will become your most used takeoff procedure. Always apply full aileron deflection into the crosswind and neutralize it enough to keep the wings level.

2. Align the airplane with the runway. Make sure the plane is on the centerline.

3. Both feet on the rudder pedals. Heels on the floor, away from the brakes.

4. Apply FULL aileron down into the wind. This prevents that wing from rising in the wind.

5. Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.

6. Accelerate down the runway to rotation speed.

i. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
ii. Keep the aileron into the wind DOWN until the crosswind becomes more of a headwind. As the ailerons become more effective you can return the yoke SLOWLY to neutral bank.

7. Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.

8. Lift off at a speed greater than Vy. This will counteract the effects of any gusts and ensure that the airplane does not settle back onto the runway if any gusts should stop.

9. Wings level.

10. Crab into the wind.

11. Continue to climb out according to departure procedure/instructions.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

12. Pitch for airspeed.

13. Trim to relieve pressures.

H. ELO 7: Identify and correct common errors in short field takeoffs.

1. Failure to position the airplane for maximum utilization of available takeoff area.

2. Improper initial positioning or flight controls and wing flaps.

3. Improper power application.

4. Inappropriate removal of hand from throttle.

5. Poor directional control.

6. Improper use of ailerons.

7. Improper pitch attitude during liftoff.

8. Failure to establish and maintain proper climb configuration and airspeed.

9. Drift during climb.

I. ELO 8: Perform a short field takeoff.

1. This takeoff assumes you have a very short runway and there is a 50 foot obstacle at the end of the runway you must clear. You have to get the airplane as high as you can get it in a very short time. You do this by starting your takeoff roll at the runway’s edge with the engine already at full power. You then climb out at Vx (or best angle of climb) until you clear the obstacle. Then climb out as normal.

2. Align the airplane with the runway. Make sure the plane is on the centerline at the END of the runway. You need all the runway you can get!!!!

3. Make sure you have the proper flap setting. (Usually 20 degrees or so) You need all the lift you can get.

4. Both feet on the rudder pedals.

5. Apply full braking power so the plane cannot move.

6. Apply FULL power. Hold the brakes.

7. Check engine instruments and make sure they are operating correctly.

8. Release brakes.

9. Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.

10. Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.

11. Lift off at Vx (best angle of climb). Maintain Vx until you clear obstacles at the end of the runway. (PTS assumes 50 foot obstacle)

12. After clearing the obstacle accelerate to Vy.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

13. Continue to climb out according to departure procedure/instructions.

14. Pitch for airspeed.

15. Trim to relieve pressures.Align the airplane with the runway. Make sure the plane is on the centerline.

16. Both feet on the rudder pedals. Heels on the floor, away from the brakes.

17. Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.

18. Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.

19. Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.

20. Lift off at Vy (best rate of climb).

21. Continue to climb out according to departure procedure/instructions.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

22. Pitch for airspeed.

23. Trim to relieve pressures.

J. ELO 7: Identify and correct common errors in soft field takeoffs.

11. Improper initial positioning or flight controls and wing flaps.

12. Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.

13. Improper power application.

14. Inappropriate removal of hand from throttle.

15. Poor directional control.

16. Improper use of brakes.

17. Improper pitch attitude during takeoff.

18. Hazards of settling back to takeoff surface after becoming airborne.

19. Failure to establish and maintain proper climb configuration.

20. Drift during climb.

K. ELO 7: Perform a soft field takeoff.

1. Wet grass or mud can cause a runway to be so soft that the airplane’s takeoff performance is seriously compromised. The landing gear could even get stuck during the takeoff roll. The intent is to transfer the weight of the airplane from the landing gear to the wings as quickly as possible. In essence you will get flying before you are supposed to. You get the plane airborne at a very low airspeed and stay in ground effect until the airplane accelerates to a safe climb speed.

2. Keep back pressure on the elevator. This includes during the taxi. This keeps the nose wheel off the ground and helps prevent it from getting stuck in the mud or some other substance.

3. Align the airplane with the runway. Make sure the plane is on the centerline. DO NOT STOP!!!

4. Both feet on the rudder pedals. Heels on the floor, away from the brakes.

5. Apply FULL power. You will need to apply right rudder to counter-act yaw to the left.

6. Keeping back pressure on the elevator, allow the nose to lift off the ground, the plane will fly “sooner than it is ready”. This is ok.

7. As soon as the plane is airborne, bring the nose level. Keep the airplane in ground effect unto you reach Vx.

8. At Vx begin to climb until you clear any obstacles. (PTS assumes 50 foot obstacle)

9. After clearing any obstacles accelerate to Vy.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

10. Continue to climb out according to departure procedure/instructions.

11. Pitch for airspeed.

12. Trim to relieve pressures.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Take Off

2019-04-09T22:37:20Z

CaptB: ongoing cleanup

{{cleanup}}

This training flight develops the student's use of proper takeoff techniques for a given situation.

== Aim of a takeoff training ==
The Take off training should train/teach you...

* Review of wind conditions and takeoff surface.
* Takeoff hazards including windshear and wake turbulence.
* Use of wing flaps.
* Alignment with takeoff path.
* Initial positioning of flight controls.
* Power application.
* Directional control during acceleration on the surface.
* Crosswind control technique during acceleration on the surface, lift-off attitude and airspeed.
* Use of ground effect.
* Climb attitude, power setting, and airspeed (Vy or Vx).
* Crosswind correction and track during climb.
* Use of checklist.

{| class="wikitable"
|-
! !! Maneuver !! Duration !! Time
|-
| 1 || Pre-flight instruction || 15 Minutes || 0:00 - 0:15
|-
| 2 || Travel to training area || 10 Minutes || 0:15 - 0:25
|-
| 3 || Instructor Demonstration || 20 Minutes || 0:25 - 0:45
|-
| 4 || Student Practice || 45 Minutes || 0:45 - 1:30
|-
| 5 || Return from practice area || 10 Minutes || 1:30 - 1:40
|-
| 6 || Post-flight Review || 20 Minutes || 1:40 - 1:20
|}

Total time: 2:00

== Equipment ==
You will need a functional [[aircraft]], a free practice area and airport and an instructor

== Tasks ==
=== Instructor’s Actions ===
# Conduct preflight training on the elements of a normal takeoff.
# Demonstrate normal takeoff.
# Demonstrate crosswind takeoff.
# Demonstrate short field takeoff.
# Demonstrate soft field takeoff.
# Conduct post flight briefing.

=== Student’s Actions ===
# Ask questions, review homework.
# Perform preflight.
# Observe demonstrations.
# Perform each takeoff [[#Used abbreviations|IAW PTS]].

=== Performance Criteria ===
# Student performs each takeoff [[#Used abbreviations|IAW PTS]] the PTS.

=== Common errors ===
A. Normal/Crosswind Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

B. Short-field Takeoffs
* Failure to position the airplane for maximum utilization of available takeoff area.
* Improper initial positioning or flight controls and wing flaps.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of ailerons.
* Improper pitch attitude during liftoff.
* Failure to establish and maintain proper climb configuration and airspeed.
* Drift during climb.

C. Soft-field Takeoffs
* Improper initial positioning or flight controls and wing flaps.
* Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.
* Improper power application.
* Inappropriate removal of hand from throttle.
* Poor directional control.
* Improper use of brakes.
* Improper pitch attitude during takeoff.
* Hazards of settling back to takeoff surface after becoming airborne.
* Failure to establish and maintain proper climb configuration.
* Drift during climb.

== Introduction ==

Takeoffs are central to being able to get into the air. In many cases the takeoff is the easiest of all flight maneuvers. Just because it is easy doesn’t mean that it should be taken for granted. Takeoffs occur in a wide variety of weather conditions. First we are going to perform a normal takeoff. Oddly enough this is the least common type of takeoff. Very rarely will the airplane be traveling down a runway perfectly aligned with the current winds. The most common type of takeoff you will experience will be the crosswind takeoff. Once you have mastered these two types of takeoffs, we will learn how to do the short field and soft field takeoffs. These two are really just variations of the normal takeoff, so don’t be too frightened of them. Today we will practice these takeoffs. During your training , we will continue to practice them until you are confident you can takeoff under most circumstances.

== Checklist for Flight ==
=== Lesson Requirements ===

## Task: Perform a takeoff.
## Condition: Given a functional aircraft.
## Standard: IAW the PTS.
### Normal/Crosswind Takeoff:
### Exhibits knowledge of the elements related to a normal and crosswind takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off, and accelerates to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Short Field Takeoff:
### Exhibits knowledge of the elements related to a short-field takeoff and climb.
### Positions the flight controls for the existing wind conditions; sets the flaps as recommended.
### Clears the area; taxies into the takeoff position so as to allow maximum utilization of available takeoff area and aligns the airplane on the runway centerline.
### Advances the throttle smoothly to takeoff power.
### Rotates at the recommended airspeed, lifts off and accelerates to the recommended obstacle clearance airspeed or V X .
### Establishes the pitch attitude for the recommended obstacle clearance airspeed, or V X , and maintains that airspeed, +10/-5 knots, until the obstacle is cleared, or until the airplane is 50 feet (20 meters) above the surface.
### After clearing the obstacle, accelerates to V Y , establishes the pitch attitude for V Y , and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

## Soft Field Takeoff:
### Exhibits knowledge of the elements related to a soft-field takeoff and climb.
### Positions the flight controls for the existing wind conditions and so as to maximize lift as quickly as possible; sets the flaps as recommended.
### Clears the area; taxies onto the takeoff surface at a speed consistent with safety and aligns the airplane without stopping while advancing the throttle smoothly to takeoff power.
### Establishes and maintains the pitch attitude that will transfer the weight of the airplane from the wheels to the wings as rapidly as possible.
### Lifts off and remains in ground effect while accelerating to V Y.
### Establishes the pitch attitude for V Y and maintains V Y , +10/-5 knots, during the climb.
### Retracts the landing gear, if retractable, and flaps after a positive rate of climb is established.
### Maintains takeoff power to a safe maneuvering altitude.
### Maintains directional control and proper wind-drift correction throughout the takeoff and climb.
### Complies with noise abatement procedures.
### Completes the appropriate checklist.

# ELO: Understand a crosswind and its effects on an aircraft on the ground.
## What is a crosswind component? The crosswind component is that wind that is not blowing directly down the runway.
## What effect does crosswind have on the airplane on the ground? Crosswinds have the tendency to lift one of the wings higher than the other. When this occurs on the ground, there is the potential to cause the aircraft to have the opposite wing hit the ground. This is why we use the crosswind taxi technique.
## What is the crosswind taxi technique? Simply put it is an attempt to minimize the effect of the crosswind on the airplane. A simple memory tool is to “climb into” a crosswind coming from the front and to “dive away from” a crosswind coming from the tail.
## Student Check:
### What is the maximum crosswind component of this airplane? _______
### What could happen if you exceed the maximum crosswind component? ______

# ELO: Identify the effects of crosswind on takeoff.
## What effect does crosswind have on takeoff? Aside from what we discussed earlier, the crosswind will tend to push the airplane to the side of the runway as the airplane gets airborne. This is why we takeoff with aileron down into the crosswind and then upon lift off assume a crab into the wind.
## What effect will gusting winds have on takeoff? Gusts can stop in the middle of the takeoff. If this occurs, there may not be enough air moving over the wings to keep takeoff lift. This may cause the airplane to settle back onto the runway. We minimize this by obtaining a higher than normal takeoff speed prior to lift off.

D. ELO 4: Identify common errors in the normal takeoff.

1. Improper initial positioning or flight controls and wing flaps.

2. Improper power application.

3. Inappropriate removal of hand from throttle.

4. Poor directional control.

5. Improper use of ailerons.

6. Improper pitch attitude during liftoff.

7. Failure to establish and maintain proper climb configuration and airspeed.

8. Drift during climb.

Student Check:

i. What is Vx on this aircraft? ________
ii. What is Vy on this aircraft? ________

E. ELO 4: Perform a normal takeoff.

1. Align the airplane with the runway. Make sure the plane is on the centerline.

2. Both feet on the rudder pedals. Heels on the floor, away from the brakes.

3. Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.

4. Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.

5. Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.

6. Lift off at Vy (best rate of climb).

7. Continue to climb out according to departure procedure/instructions.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

8. Pitch for airspeed.

9. Trim to relieve pressures.

F. ELO 5: Identify and correct common errors in crosswind takeoffs. The same as above plus:

1. Improper initial positioning or flight controls and wing flaps.

2. Improper power application.

3. Inappropriate removal of hand from throttle.

4. Poor directional control.

5. Improper use of ailerons.

6. Improper pitch attitude during liftoff.

7. Failure to establish and maintain proper climb configuration and airspeed.

8. Drift during climb.

G. ELO 6: Perform a crosswind takeoff.

1. Why use crosswind take off techniques? A crosswind tends to lift one of the wings off the ground and could potentially cause an airplane to tip over. During take off, the crosswind could cause the airplane to skip sideways along the runway. This put tremendous loads on the landing gear and could in some instances cause the gear to collapse. Proper crosswind technique minimizes these effects. In simple terms, you keep the wing in the crosswind DOWN until you are airborne. You will lift off with a greater airspeed than normal to help you control the airplane. Otherwise the take off is the same as a normal take off. You may find yourself combining this takeoff with soft or short field takeoffs. Because the wind rarely blows down the center of any runway, this will become your most used takeoff procedure. Always apply full aileron deflection into the crosswind and neutralize it enough to keep the wings level.

2. Align the airplane with the runway. Make sure the plane is on the centerline.

3. Both feet on the rudder pedals. Heels on the floor, away from the brakes.

4. Apply FULL aileron down into the wind. This prevents that wing from rising in the wind.

5. Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.

6. Accelerate down the runway to rotation speed.

i. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.
ii. Keep the aileron into the wind DOWN until the crosswind becomes more of a headwind. As the ailerons become more effective you can return the yoke SLOWLY to neutral bank.

7. Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.

8. Lift off at a speed greater than Vy. This will counteract the effects of any gusts and ensure that the airplane does not settle back onto the runway if any gusts should stop.

9. Wings level.

10. Crab into the wind.

11. Continue to climb out according to departure procedure/instructions.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

12. Pitch for airspeed.

13. Trim to relieve pressures.

H. ELO 7: Identify and correct common errors in short field takeoffs.

1. Failure to position the airplane for maximum utilization of available takeoff area.

2. Improper initial positioning or flight controls and wing flaps.

3. Improper power application.

4. Inappropriate removal of hand from throttle.

5. Poor directional control.

6. Improper use of ailerons.

7. Improper pitch attitude during liftoff.

8. Failure to establish and maintain proper climb configuration and airspeed.

9. Drift during climb.

I. ELO 8: Perform a short field takeoff.

1. This takeoff assumes you have a very short runway and there is a 50 foot obstacle at the end of the runway you must clear. You have to get the airplane as high as you can get it in a very short time. You do this by starting your takeoff roll at the runway’s edge with the engine already at full power. You then climb out at Vx (or best angle of climb) until you clear the obstacle. Then climb out as normal.

2. Align the airplane with the runway. Make sure the plane is on the centerline at the END of the runway. You need all the runway you can get!!!!

3. Make sure you have the proper flap setting. (Usually 20 degrees or so) You need all the lift you can get.

4. Both feet on the rudder pedals.

5. Apply full braking power so the plane cannot move.

6. Apply FULL power. Hold the brakes.

7. Check engine instruments and make sure they are operating correctly.

8. Release brakes.

9. Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.

10. Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.

11. Lift off at Vx (best angle of climb). Maintain Vx until you clear obstacles at the end of the runway. (PTS assumes 50 foot obstacle)

12. After clearing the obstacle accelerate to Vy.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

13. Continue to climb out according to departure procedure/instructions.

14. Pitch for airspeed.

15. Trim to relieve pressures.Align the airplane with the runway. Make sure the plane is on the centerline.

16. Both feet on the rudder pedals. Heels on the floor, away from the brakes.

17. Apply FULL power. You may need to apply right rudder to counter-act yaw to the left.

18. Accelerate down the runway to rotation speed. Maintain directional control with the rudder. As airspeed increases, the control surfaces will become more effective. Use smaller inputs to the rudder to maintain control.

19. Apply slight back pressure to the elevator, just enough to lift the nose off the ground. Watch for left yawing tendency.

20. Lift off at Vy (best rate of climb).

21. Continue to climb out according to departure procedure/instructions.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

22. Pitch for airspeed.

23. Trim to relieve pressures.

J. ELO 7: Identify and correct common errors in soft field takeoffs.

11. Improper initial positioning or flight controls and wing flaps.

12. Hazards of allowing the airplane to stop on the takeoff surface prior to initiating takeoff.

13. Improper power application.

14. Inappropriate removal of hand from throttle.

15. Poor directional control.

16. Improper use of brakes.

17. Improper pitch attitude during takeoff.

18. Hazards of settling back to takeoff surface after becoming airborne.

19. Failure to establish and maintain proper climb configuration.

20. Drift during climb.

K. ELO 7: Perform a soft field takeoff.

1. Wet grass or mud can cause a runway to be so soft that the airplane’s takeoff performance is seriously compromised. The landing gear could even get stuck during the takeoff roll. The intent is to transfer the weight of the airplane from the landing gear to the wings as quickly as possible. In essence you will get flying before you are supposed to. You get the plane airborne at a very low airspeed and stay in ground effect until the airplane accelerates to a safe climb speed.

2. Keep back pressure on the elevator. This includes during the taxi. This keeps the nose wheel off the ground and helps prevent it from getting stuck in the mud or some other substance.

3. Align the airplane with the runway. Make sure the plane is on the centerline. DO NOT STOP!!!

4. Both feet on the rudder pedals. Heels on the floor, away from the brakes.

5. Apply FULL power. You will need to apply right rudder to counter-act yaw to the left.

6. Keeping back pressure on the elevator, allow the nose to lift off the ground, the plane will fly “sooner than it is ready”. This is ok.

7. As soon as the plane is airborne, bring the nose level. Keep the airplane in ground effect unto you reach Vx.

8. At Vx begin to climb until you clear any obstacles. (PTS assumes 50 foot obstacle)

9. After clearing any obstacles accelerate to Vy.

i. For retractable gear aircraft, retract the gear when there is no useable runway left.
ii. For high performance aircraft you will need to adjust MP and RPM to bring them back within tolerance. THROTTLE FIRST THEN RPM. Keep manifold pressure BELOW rpm at all times.

10. Continue to climb out according to departure procedure/instructions.

11. Pitch for airspeed.

12. Trim to relieve pressures.

== Used abbreviations ==
* IAW = In Accordance With
* PTS = Practical Test Standards

[[Category:FlightGear Flight Academy]]

Modelling guidelines

2017-11-17T18:05:03Z

CaptB: The correct Blender naming for what the P key does is to "separate" part of a mesh. Split is more assosiated with edge splitting which could be misleading for beginners.

{{Merge|Modeling - Getting Started#Improving models for best FlightGear performance}}

When modelling an aircraft, building or any other 3D model, you are encouraged to follow the '''modelling guidelines''' outlined in this article.

Feel free to add/modify. (''please leave a comment in the [[Talk:Modelling guidelines|talk page]] for radical modifications'').

== Definitions ==
*Model = the file.
*Object/Mesh = part of the Model file. The Model can contain several Objects.
*Texture = image file (.rgb, .png).

== Modelling guidelines ==
*Vertices are free up to a point - use as many as you need.
*Many small (in vertex numbers) Objects/Meshes have a far worse negative impact on performance than a single Object/Mesh with very high vertex numbers.
*Combine all different parts of the Model into one single Object/Mesh, with the exception of parts that need to be animated, or of transparent parts.
** '''Blender''': Select some objects and press {{Key press|Ctrl|J}} to join them into one Object. The new object origin/transform/orientation/name will be based on the ones of the last object selected.
*Use different unique names for each of the Objects in a Model file. Even more so when the different parts need to be animated.
*Make all faces of the objects single sided.
*If you need a part of the model to be visible from both sides, duplicate it in place and flip the normals. The extra geometry overhead is negligible compared to the extra work generated by double-sided faces.
*Separate transparent parts into their own objects.
** '''Blender''': Go into Edit Mode, select the part of the object that you would like to separate and press {{Key press|P}}.
*Assign to all transparent Objects at least the ''model-transparent'' effect:
<syntaxhighlight lang="xml">
<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>Transparent-object1</object-name>
<object-name>Transparent-object2</object-name>
<object-name>Transparent-object3</object-name>
<object-name>other-Transparent-object</object-name>
</effect>
</syntaxhighlight>
*The interior should be a separate Model. Having it separate enables delayed loading of such models in multiplayer/AI contexts.
Only one instance of the tag is allowed for the whole aircraft. Such a model is specified as follows in the .xml file:
<syntaxhighlight lang="xml">
<model>
<usage>interior</usage> 
<path>Models/your-interior-model.xml</path>
</model>
</syntaxhighlight>

If your <model> require an <offsets> you must move the <offsets> section in the children XML like:

your/aircraft/Models/aircraft.xml:
<syntaxhighlight lang="xml">
<PropertyList>
<path>path/to/model.ac</path>
<model>
<path>your/aircraft/Models/Interior/model.xml</path>
<usage>interior</usage>
</model>
...
</PropertyList>
</syntaxhighlight>

your/aircraft/Models/Interior/model.xml:
<syntaxhighlight lang="xml">
<PropertyList>
<path>path/to/another/model.ac</path>
<offsets>
<x-m> -1.91552 </x-m>
<y-m> 0.00000 </y-m>
<z-m> 0.23706 </z-m>
<roll-deg> 40.0 </roll-deg>
<pitch-deg> 35.0 </pitch-deg>
<heading-deg> 60.0 </heading-deg>
</offsets>

<model>
<path>path/to/another/model.xml</path>
</model>
...
</syntaxhighlight>

== Texturing guidelines ==
*Combine as many parts of a single Model to a single texture as you can - the maximum texture size is 4096 x 4096 pixels.
*Do not assign multiple textures to the same Object/Mesh. The Object will be split so as to have a single texture/Mesh.
*Do not use different parts of a single texture for different models. Split the texture into smaller parts then.
*If using the same texture on multiple models, use a single file, do not make different copies.
*Prefer texture replacing animations to textranslate for models that spend large amounts of their time in one state (day/night animations).
*Avoid transparency like the plague, it kills frame rate like nothing else: remove the alpha channel from textures if they are non-transparent.
** '''GIMP''': Go to <tt>Layers > Transparency > Remove alpha layer</tt>.
** '''Inkscape''': Go to <tt>File > Document Properties</tt> and set the "Background" to a non transparent colour (preferably black).
*Hive off transparent parts of textures into their own textures.
*Use power of two dimensions for textures (2<sup>n</sup>, e.g. 256x256, 512x1024). Do not worry if your image would get stretched in the texture, you can fix that with the mapping on the model.
*Do not have textures with the image in one corner and the rest unused.
*Recommended texture format is: '''.png'''. In general any texture format supported by OSG could be used, but be aware of varying cross-platform support for such formats, or of lossy compression.
 

[[Category:Modeling]]

Howto:Serializing Nasal data structures

2017-08-13T16:37:01Z

CaptB: /* Background */

{{Stub}}
== Objective ==
# serialization: convert a Nasal data structure to a string using valid Nasal syntax
# deserialization: compile that string to a temporary Nasal function, call it to retrieve the original data structure

== Background ==

Nasal's hash syntax is already close enough to JSON that Nasal could even serialie a property tree without requiring much work, analogous to props.getValues() which is already traversing a property tree node and which turns it into a Nasal data structure (hash).

<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=296382#p296382
|title = <nowiki> Re: Why not use Erlang instead of </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Oct 9th, 2016
|added = Oct 9th, 2016
|script_version = 0.40
}}</ref>

Another possibility would be using a subset of JSON, i.e. to serialize/unserialize Nasal data structures as scalars, vectors and hashes - which should be pretty straightforward. The format would then be plain text, and it would just be evaluated via Nasal's compile()/call() APIs to turn data structures back into Nasal types.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=257091#p257091
|title = <nowiki> Re: String manipulation and file I/O (pm2thread) </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Sep 12th, 2015
|added = Sep 12th, 2015
|script_version = 0.40
}}</ref>

you could then also directly use io.load_nasal() to load a Nasal file from disk (think mydata.nas) and for serialiation purposes, write to the same file - just make sure that it is valid Nasal<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=257091#p257091
|title = <nowiki> Re: String manipulation and file I/O (pm2thread) </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Sep 12th, 2015
|added = Sep 12th, 2015
|script_version = 0.40
}}</ref>

depending on how much can be saved using a space-time or time-memory tradeoff, you could compute lookup tables using Nasal vectors/hashes (or both) and serialie those to disk - e.g. using JSON, which is basically equivalent to the syntax used by Nasal.
You would basically compute your lookup tables once and then use a nested for-loop to read the lookup tables and serialize/write those to a custom file in $FG_HOME/Export, at that point you can then copy the whole thing into a folder where it can be loaded at runtime using the helpers available in io.nas
(using JSON would be much less verbose than using PropertyList/XML, but obviously not as efficient as using a binary serialization format).
Basically, this would be equivalent to programmatically creating a complex texture and storing that on disk to save reduce the runtime overhead (treating the texture as a multi-dimensional lookup table).
https://en.wikipedia.org/wiki/Space%E2%80%93time_tradeoff

[https://en.wikipedia.org/wiki/JSON https://en.wikipedia.org/wiki/JSON]<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=316425#p316425
|title = <nowiki> Re: Space Shuttle </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Aug 12th, 2017
|added = Aug 12th, 2017
|script_version = 0.40
}}</ref>

== Proof of concept ==

[[Nasal Console]]

<syntaxhighlight lang="javascript">

var serializeVector = func(vector) {
retVal = "[";
foreach(var item; vector) {
retVal ~= serialize(item) ~ ',';
}

return retVal~"]";
}

var serializeHash = func(hash) {
var retVal = "{";
foreach(var member; keys(hash)) {
retVal ~= serialize(member) ~ ',';

}

return retVal ~"}";
}

var serialize = func (data) {
var type = typeof(data);
if (type == "scalar") return data;
if (type == "vector") return serializeVector(data);
if (type == "hash") return serializeHash(data);
if (type == "ghost" or type == "func") return "nil";
die("cannot serialize unsupported data type:", type);
}

# create an empty vector
var myVector = [];

# populate the vector with elements with [index, index^2]
for (var i=0;i<=40;i+=1) {
append(myVector,[i, i*i]);
}

# debug.dump(myVector);

# serialize the data structure to a string that is valid Nasal syntax
var serialized = serialize(myVector);

# debug.dump(serialized);

# next, compile the serialized string to a Nasal function
var compiled = compile(serialized);
# actually call the function, and store the return value
var result = compiled();

# dump the deserialized return value to the console
debug.dump(result);

</syntaxhighlight>

== Finally ==
the original Nasal example, already contains a helper function to serialie a Nasal type:<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=257123#p257123
|title = <nowiki> Re: String manipulation and file I/O (pm2thread) </nowiki>
|author = <nowiki> Hooray </nowiki>
|date = Sep 12th, 2015
|added = Sep 12th, 2015
|script_version = 0.40
}}</ref>

http://plausible.org/nasal/sample.nas
<syntaxhighlight lang="nasal">##
## A rockin' metaprogramming hack. Generates and returns a deep copy
## of the object in valid Nasal syntax. A warning to those who might
## want to use this: it ignores function objects (which cannot be
## inspected from Nasal) and replaces them with nil references. It
## also makes no attempt to escape special characters in strings, which
## can break re-parsing in strange (and possibly insecure!) ways.
##
dump = func(o) {
result = "";
if(typeof(o) == "scalar") {
n = num(o);
if(n == nil) { result = result ~ '"' ~ o ~ '"'; }
else { result = result ~ o; }
} elsif(typeof(o) == "vector") {
result = result ~ "[ ";
if(size(o) > 0) { result = result ~ dump(o[0]); }
for(i=1; i<size(o); i=i+1) {
result = result ~ ", " ~ dump(o[i]);
}
result = result ~ " ]";
} elsif(typeof(o) == "hash") {
ks = keys(o);
result = result ~ "{ ";
if(size(o) > 0) {
k = ks[0];
result = result ~ k ~ ":" ~ dump(o[k]);
}
for(i=1; i<size(o); i=i+1) {
k = ks[i];
result = result ~ ", " ~ k ~ " : " ~ dump(o[k]);
}
result = result ~ " }";
} else {
result = result ~ "nil";
}
return result;
}
</syntaxhighlight>

== References ==
{{Appendix}}

Howto:Creating FlightGear Promo Videos

2017-08-07T13:39:40Z

CaptB: /* Video Recording Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k
{{Release}}
== Examples ==

Recent example of a good video:

{{#ev:youtube|yPBdJT2Pkdc|900px|center|}}

Illustration of using a recent model GPU, good memory, and full settings while using a IR point tracker to impress the FSX guys:

{{#ev:youtube|ajvenT55IG8|900px|center|}}

We recommend two different styles. The first video is showing you the detailed features of FlightGear Version 3.2:

{{#ev:youtube|EoNQ1NpcnMw|900px|center|}}

The second video shows you how to present a FlightGear Version 2.10 video in the form of a slideshow:

{{#ev:youtube|MZVCmHgAX6Y|900px|center|}}

== Content ==
Use the [[Next changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

Please also try to include your system specs, so that others can more easily determine if certain features are likely to work with their own hardware, specifically:

* operating system
* hardware (CPU, GPU, RAM, VRAM)
* FlightGear relevant settings (Rembrandt vs. ALS, Basic weather vs. advanced weather)

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:

{| class="wikitable"
|-
! Name !! Platform !! License !! Notes
|-
| Action! || Windows || Commercial || one of the best, has openGL support, can utilize multi-threading.
|-
| CamStudio || Windows || GPL || Last release 2013
|-
| Fraps || Windows || Commercial || Works great if configured right
|-
| Glc-capture || Linux || Free || License unspecified see glc.h. Difficult, Fast capture, Produces large files.
|-
| Nvidia Share || Windows || Proprietary || Formerly Nvidia ShadowPlay. Requires Nvidia card & recent drivers. Good frames. Part of Nvidia GFE
|-
| Open Broadcaster Software || Linux, Mac, Windows || GPL v2 || Modern, Intuitive.
|-
| QuickTime X || Mac || Proprietary || Part of MacOS
|-
| RecordMyDesktop || Linux || GPL || Last release 2008
|-
| VLC || Linux, Mac, Windows || GPL || Multiplatform
|}

== Video Editing Software ==
Programs to edit your video:

{| class="wikitable"
|-
! Name !! Platform !! License !! Notes
|-
| Adobe Premiere Pro || Windows, Mac || Commercial||
|-
| Kdenlive || Linux, BSD, Mac, Windows || GPL ||
|-
| OpenShot|| Linux, Mac, Windows || LGPL ||
|-
| Pitivi|| Linux || GPL ||
|-
| IMovie || Mac || Commercial || IMovie comes with every mac for free. Paid upgrades.
|-
| Sony Vegas Pro || Windows || Commercial ||
|-
| VirtualDub || Windows|| GPL || Discontinued
|}

== Helpful Tips & Tricks ==

* It is recommended to record in full screen mode, this gets rid of any compositor double vertical synching effect, on Linux you simply disable the compositor(the implementation depends on your distro), while for Windows Vista and 7, just disable the Aero theme, unfortunately for Windows 8 and above, the compositor cannot be disabled, the compositor runs as DWM.exe, and is re-instanced by the winlogon.exe manager whenever you try to close it, two alternatives exists is to run the classic shell, or you follow this guideline for a hack to disable DWM.exe temporarily(this will break some effects including the Window Manager). [http://superuser.com/questions/581673/disable-desktop-composition-in-windows-8-force-it disable-desktop-composition-in-windows-8-force-it]

* If you have a powerful machine, it is best to disable VSync(as it adjusts frame-spacing to a minumum static value), if you are worried about maintaining a constant FPS for recording, just impose an internal frame cap in Flightgear by going to View > Rendering Options > Throttle Framerate. From my experience most OpenGL screen recorders impose an FPS limit anyway(unlike some DirectX recorders).

'''Linux:''' export the env variable "vblank_mode=0" on the same session you're running FG from.

'''Windows w/ Nvidia GPU:''' Nvidia Control Panel > Manage 3D settings > Program Settings.

* It is better to write to a separate HDD then the one you're running Flightgear from, as not to overwhelm your drive's IO controller.

* Avoid live encoding, as that would bog down the CPU while recording and consume lots of memory, always perform transmuxing without re-encoding if you want to edit, i recommend ffmpeg if you know how to operate it, or MP4Box(GUI MP4 stream extractor for Windows).

== Finally ==
Everything else is up to the editor... ;)

[[Category:Howto|Creating FlightGear Promo Videos]]

Howto:Creating FlightGear Promo Videos

2017-08-07T12:44:56Z

CaptB: /* Examples */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k
{{Release}}
== Examples ==

Recent example of a good video:

{{#ev:youtube|yPBdJT2Pkdc|900px|center|}}

Illustration of using a recent model GPU, good memory, and full settings while using a IR point tracker to impress the FSX guys:

{{#ev:youtube|ajvenT55IG8|900px|center|}}

We recommend two different styles. The first video is showing you the detailed features of FlightGear Version 3.2:

{{#ev:youtube|EoNQ1NpcnMw|900px|center|}}

The second video shows you how to present a FlightGear Version 2.10 video in the form of a slideshow:

{{#ev:youtube|MZVCmHgAX6Y|900px|center|}}

== Content ==
Use the [[Next changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

Please also try to include your system specs, so that others can more easily determine if certain features are likely to work with their own hardware, specifically:

* operating system
* hardware (CPU, GPU, RAM, VRAM)
* FlightGear relevant settings (Rembrandt vs. ALS, Basic weather vs. advanced weather)

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:

{| class="wikitable"
|-
! Header text !! Header text !! Header text !! Header text
|-
| Action! || Windows || Commercial || one of the best, has openGL support, can utilize multi-threading.
|-
| CamStudio || Windows || GPL || Last release 2013
|-
| Fraps || Windows || Commercial || Works great if configured right
|-
| Glc-capture || Linux || Free || License unspecified see glc.h. Difficult, Fast capture, Produces large files.
|-
| Nvidia Share || Windows || Proprietary || Formerly Nvidia ShadowPlay. Requires Nvidia card & recent drivers. Good frames. Part of Nvidia GFE
|-
| Open Broadcaster Software || Linux, Mac, Windows || GPL v2 || Modern, Intuitive.
|-
| QuickTime X || Mac || Proprietary || Part of MacOS
|-
| RecordMyDesktop || Linux || GPL || Last release 2008
|-
| VLC || Linux, Mac, Windows || GPL || Multiplatform
|}

== Video Editing Software ==
Programs to edit your video:

{| class="wikitable"
|-
! Name !! Platform !! License !! Notes
|-
| Adobe Premiere Pro || Windows, Mac || Commercial||
|-
| Kdenlive || Linux, BSD, Mac, Windows || GPL ||
|-
| OpenShot|| Linux, Mac, Windows || LGPL ||
|-
| Pitivi|| Linux || GPL ||
|-
| IMovie || Mac || Commercial || IMovie comes with every mac for free. Paid upgrades.
|-
| Sony Vegas Pro || Windows || Commercial ||
|-
| VirtualDub || Windows|| GPL || Discontinued
|}

== Helpful Tips & Tricks ==

* It is recommended to record in full screen mode, this gets rid of any compositor double vertical synching effect, on Linux you simply disable the compositor(the implementation depends on your distro), while for Windows Vista and 7, just disable the Aero theme, unfortunately for Windows 8 and above, the compositor cannot be disabled, the compositor runs as DWM.exe, and is re-instanced by the winlogon.exe manager whenever you try to close it, two alternatives exists is to run the classic shell, or you follow this guideline for a hack to disable DWM.exe temporarily(this will break some effects including the Window Manager). [http://superuser.com/questions/581673/disable-desktop-composition-in-windows-8-force-it disable-desktop-composition-in-windows-8-force-it]

* If you have a powerful machine, it is best to disable VSync(as it adjusts frame-spacing to a minumum static value), if you are worried about maintaining a constant FPS for recording, just impose an internal frame cap in Flightgear by going to View > Rendering Options > Throttle Framerate. From my experience most OpenGL screen recorders impose an FPS limit anyway(unlike some DirectX recorders).

'''Linux:''' export the env variable "vblank_mode=0" on the same session you're running FG from.

'''Windows w/ Nvidia GPU:''' Nvidia Control Panel > Manage 3D settings > Program Settings.

* It is better to write to a separate HDD then the one you're running Flightgear from, as not to overwhelm your drive's IO controller.

* Avoid live encoding, as that would bog down the CPU while recording and consume lots of memory, always perform transmuxing without re-encoding if you want to edit, i recommend ffmpeg if you know how to operate it, or MP4Box(GUI MP4 stream extractor for Windows).

== Finally ==
Everything else is up to the editor... ;)

[[Category:Howto|Creating FlightGear Promo Videos]]

Howto:Creating FlightGear Promo Videos

2017-08-07T12:39:31Z

CaptB: /* Video Recording Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k
{{Release}}
== Examples ==
{{#ev:youtube|yPBdJT2Pkdc|900px|center|}}

Illustration of using a recent model GPU, good memory, and full settings while using a IR point tracker to impress the FSX guys :)

{{#ev:youtube|ajvenT55IG8}}

We recommend two different styles. The first video is showing you the detailed features of FlightGear Version 3.2.

{{#ev:youtube|EoNQ1NpcnMw}}

The second video shows you how to present a FlightGear Version 2.10 video in the form of a slideshow.

{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the [[Next changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

Please also try to include your system specs, so that others can more easily determine if certain features are likely to work with their own hardware, specifically:

* operating system
* hardware (CPU, GPU, RAM, VRAM)
* FlightGear relevant settings (Rembrandt vs. ALS, Basic weather vs. advanced weather)

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:

{| class="wikitable"
|-
! Header text !! Header text !! Header text !! Header text
|-
| Action! || Windows || Commercial || one of the best, has openGL support, can utilize multi-threading.
|-
| CamStudio || Windows || GPL || Last release 2013
|-
| Fraps || Windows || Commercial || Works great if configured right
|-
| Glc-capture || Linux || Free || License unspecified see glc.h. Difficult, Fast capture, Produces large files.
|-
| Nvidia Share || Windows || Proprietary || Formerly Nvidia ShadowPlay. Requires Nvidia card & recent drivers. Good frames. Part of Nvidia GFE
|-
| Open Broadcaster Software || Linux, Mac, Windows || GPL v2 || Modern, Intuitive.
|-
| QuickTime X || Mac || Proprietary || Part of MacOS
|-
| RecordMyDesktop || Linux || GPL || Last release 2008
|-
| VLC || Linux, Mac, Windows || GPL || Multiplatform
|}

== Video Editing Software ==
Programs to edit your video:

{| class="wikitable"
|-
! Name !! Platform !! License !! Notes
|-
| Adobe Premiere Pro || Windows, Mac || Commercial||
|-
| Kdenlive || Linux, BSD, Mac, Windows || GPL ||
|-
| OpenShot|| Linux, Mac, Windows || LGPL ||
|-
| Pitivi|| Linux || GPL ||
|-
| IMovie || Mac || Commercial || IMovie comes with every mac for free. Paid upgrades.
|-
| Sony Vegas Pro || Windows || Commercial ||
|-
| VirtualDub || Windows|| GPL || Discontinued
|}

== Helpful Tips & Tricks ==

* It is recommended to record in full screen mode, this gets rid of any compositor double vertical synching effect, on Linux you simply disable the compositor(the implementation depends on your distro), while for Windows Vista and 7, just disable the Aero theme, unfortunately for Windows 8 and above, the compositor cannot be disabled, the compositor runs as DWM.exe, and is re-instanced by the winlogon.exe manager whenever you try to close it, two alternatives exists is to run the classic shell, or you follow this guideline for a hack to disable DWM.exe temporarily(this will break some effects including the Window Manager). [http://superuser.com/questions/581673/disable-desktop-composition-in-windows-8-force-it disable-desktop-composition-in-windows-8-force-it]

* If you have a powerful machine, it is best to disable VSync(as it adjusts frame-spacing to a minumum static value), if you are worried about maintaining a constant FPS for recording, just impose an internal frame cap in Flightgear by going to View > Rendering Options > Throttle Framerate. From my experience most OpenGL screen recorders impose an FPS limit anyway(unlike some DirectX recorders).

'''Linux:''' export the env variable "vblank_mode=0" on the same session you're running FG from.

'''Windows w/ Nvidia GPU:''' Nvidia Control Panel > Manage 3D settings > Program Settings.

* It is better to write to a separate HDD then the one you're running Flightgear from, as not to overwhelm your drive's IO controller.

* Avoid live encoding, as that would bog down the CPU while recording and consume lots of memory, always perform transmuxing without re-encoding if you want to edit, i recommend ffmpeg if you know how to operate it, or MP4Box(GUI MP4 stream extractor for Windows).

== Finally ==
Everything else is up to the editor... ;)

[[Category:Howto|Creating FlightGear Promo Videos]]

Howto:Creating FlightGear Promo Videos

2017-08-07T12:04:01Z

CaptB: /* Video Editing Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k
{{Release}}
== Examples ==
{{#ev:youtube|yPBdJT2Pkdc|900px|center|}}

Illustration of using a recent model GPU, good memory, and full settings while using a IR point tracker to impress the FSX guys :)

{{#ev:youtube|ajvenT55IG8}}

We recommend two different styles. The first video is showing you the detailed features of FlightGear Version 3.2.

{{#ev:youtube|EoNQ1NpcnMw}}

The second video shows you how to present a FlightGear Version 2.10 video in the form of a slideshow.

{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the [[Next changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

Please also try to include your system specs, so that others can more easily determine if certain features are likely to work with their own hardware, specifically:

* operating system
* hardware (CPU, GPU, RAM, VRAM)
* FlightGear relevant settings (Rembrandt vs. ALS, Basic weather vs. advanced weather)

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac | only captures the full screen
* VLC (free, multi-platform)
* Fraps (paid) - Windows | works great if configured right
* Action! (paid) - Windows | one of the best, has openGL support, can utilize multi-threading.
* recordmydesktop - Linux
* NVidia ShadowPlay (free) - Windows | Requires higher end NVidia card with recent drivers. Works great with minimal frame rate hit but must be used in desktop capture mode with OpenGL.
* glc-capture (free) - Linux | A little more difficult to use, but it forms a layer inbetween FlightGear and your graphics card for the fastest way of capturing video. Also files become very big, so make sure your disk is big enough.

MAGIX is a set of Applications that handles video and audio editing, it also has a recording software.

To install record my desktop on Ubuntu(and it's variations), Linux Mint and Debian open the terminal and type:
'''sudo apt-get install gtk-recordmydesktop'''

== Video Editing Software ==
Programs to edit your video:

{| class="wikitable"
|-
! Name !! Platform !! License !! Notes
|-
| Adobe Premiere Pro || Windows, Mac || Commercial||
|-
| Kdenlive || Linux, BSD, Mac, Windows || GPL ||
|-
| OpenShot|| Linux, Mac, Windows || LGPL ||
|-
| Pitivi|| Linux || GPL ||
|-
| IMovie || Mac || Commercial || IMovie comes with every mac for free. Paid upgrades.
|-
| Sony Vegas Pro || Windows || Commercial ||
|-
| VirtualDub || Windows|| GPL || Discontinued
|}

== Helpful Tips & Tricks ==

* It is recommended to record in full screen mode, this gets rid of any compositor double vertical synching effect, on Linux you simply disable the compositor(the implementation depends on your distro), while for Windows Vista and 7, just disable the Aero theme, unfortunately for Windows 8 and above, the compositor cannot be disabled, the compositor runs as DWM.exe, and is re-instanced by the winlogon.exe manager whenever you try to close it, two alternatives exists is to run the classic shell, or you follow this guideline for a hack to disable DWM.exe temporarily(this will break some effects including the Window Manager). [http://superuser.com/questions/581673/disable-desktop-composition-in-windows-8-force-it disable-desktop-composition-in-windows-8-force-it]

* If you have a powerful machine, it is best to disable VSync(as it adjusts frame-spacing to a minumum static value), if you are worried about maintaining a constant FPS for recording, just impose an internal frame cap in Flightgear by going to View > Rendering Options > Throttle Framerate. From my experience most OpenGL screen recorders impose an FPS limit anyway(unlike some DirectX recorders).

'''Linux:''' export the env variable "vblank_mode=0" on the same session you're running FG from.

'''Windows w/ Nvidia GPU:''' Nvidia Control Panel > Manage 3D settings > Program Settings.

* It is better to write to a separate HDD then the one you're running Flightgear from, as not to overwhelm your drive's IO controller.

* Avoid live encoding, as that would bog down the CPU while recording and consume lots of memory, always perform transmuxing without re-encoding if you want to edit, i recommend ffmpeg if you know how to operate it, or MP4Box(GUI MP4 stream extractor for Windows).

== Finally ==
Everything else is up to the editor... ;)

[[Category:Howto|Creating FlightGear Promo Videos]]

Howto:Creating FlightGear Promo Videos

2017-08-07T12:03:32Z

CaptB: /* Video Editing Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k
{{Release}}
== Examples ==
{{#ev:youtube|yPBdJT2Pkdc|900px|center|}}

Illustration of using a recent model GPU, good memory, and full settings while using a IR point tracker to impress the FSX guys :)

{{#ev:youtube|ajvenT55IG8}}

We recommend two different styles. The first video is showing you the detailed features of FlightGear Version 3.2.

{{#ev:youtube|EoNQ1NpcnMw}}

The second video shows you how to present a FlightGear Version 2.10 video in the form of a slideshow.

{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the [[Next changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

Please also try to include your system specs, so that others can more easily determine if certain features are likely to work with their own hardware, specifically:

* operating system
* hardware (CPU, GPU, RAM, VRAM)
* FlightGear relevant settings (Rembrandt vs. ALS, Basic weather vs. advanced weather)

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac | only captures the full screen
* VLC (free, multi-platform)
* Fraps (paid) - Windows | works great if configured right
* Action! (paid) - Windows | one of the best, has openGL support, can utilize multi-threading.
* recordmydesktop - Linux
* NVidia ShadowPlay (free) - Windows | Requires higher end NVidia card with recent drivers. Works great with minimal frame rate hit but must be used in desktop capture mode with OpenGL.
* glc-capture (free) - Linux | A little more difficult to use, but it forms a layer inbetween FlightGear and your graphics card for the fastest way of capturing video. Also files become very big, so make sure your disk is big enough.

MAGIX is a set of Applications that handles video and audio editing, it also has a recording software.

To install record my desktop on Ubuntu(and it's variations), Linux Mint and Debian open the terminal and type:
'''sudo apt-get install gtk-recordmydesktop'''

== Video Editing Software ==
Programs to edit your video:

{| class="wikitable"
|-
! Name !! Platform !! License !! Notes
|-
| Adobe Premiere Pro || Windows, Mac || Commercial||
|-
| Kdenlive || Linux, BSD, Mac, Windows || GPL ||
|-
| OpenShot|| Linux, Mac, Windows || LGPL ||
|-
| Pitivi|| Linux || GPL ||
|-
| IMovie || Mac || Commercial || IMovie comes with every mac for free. Paid upgrades.
|-
| Sony Vegas Pro || Windows || Commercial ||
|-
| VirtualDub || Windows|| GPL || Discontinued
|-
| Example || Example || Example ||
|-
| Example || Example || Example ||
|}
== Helpful Tips & Tricks ==

* It is recommended to record in full screen mode, this gets rid of any compositor double vertical synching effect, on Linux you simply disable the compositor(the implementation depends on your distro), while for Windows Vista and 7, just disable the Aero theme, unfortunately for Windows 8 and above, the compositor cannot be disabled, the compositor runs as DWM.exe, and is re-instanced by the winlogon.exe manager whenever you try to close it, two alternatives exists is to run the classic shell, or you follow this guideline for a hack to disable DWM.exe temporarily(this will break some effects including the Window Manager). [http://superuser.com/questions/581673/disable-desktop-composition-in-windows-8-force-it disable-desktop-composition-in-windows-8-force-it]

* If you have a powerful machine, it is best to disable VSync(as it adjusts frame-spacing to a minumum static value), if you are worried about maintaining a constant FPS for recording, just impose an internal frame cap in Flightgear by going to View > Rendering Options > Throttle Framerate. From my experience most OpenGL screen recorders impose an FPS limit anyway(unlike some DirectX recorders).

'''Linux:''' export the env variable "vblank_mode=0" on the same session you're running FG from.

'''Windows w/ Nvidia GPU:''' Nvidia Control Panel > Manage 3D settings > Program Settings.

* It is better to write to a separate HDD then the one you're running Flightgear from, as not to overwhelm your drive's IO controller.

* Avoid live encoding, as that would bog down the CPU while recording and consume lots of memory, always perform transmuxing without re-encoding if you want to edit, i recommend ffmpeg if you know how to operate it, or MP4Box(GUI MP4 stream extractor for Windows).

== Finally ==
Everything else is up to the editor... ;)

[[Category:Howto|Creating FlightGear Promo Videos]]

Howto:Creating FlightGear Promo Videos

2017-08-07T12:02:11Z

CaptB: /* Video Editing Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k
{{Release}}
== Examples ==
{{#ev:youtube|yPBdJT2Pkdc|900px|center|}}

Illustration of using a recent model GPU, good memory, and full settings while using a IR point tracker to impress the FSX guys :)

{{#ev:youtube|ajvenT55IG8}}

We recommend two different styles. The first video is showing you the detailed features of FlightGear Version 3.2.

{{#ev:youtube|EoNQ1NpcnMw}}

The second video shows you how to present a FlightGear Version 2.10 video in the form of a slideshow.

{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the [[Next changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

Please also try to include your system specs, so that others can more easily determine if certain features are likely to work with their own hardware, specifically:

* operating system
* hardware (CPU, GPU, RAM, VRAM)
* FlightGear relevant settings (Rembrandt vs. ALS, Basic weather vs. advanced weather)

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac | only captures the full screen
* VLC (free, multi-platform)
* Fraps (paid) - Windows | works great if configured right
* Action! (paid) - Windows | one of the best, has openGL support, can utilize multi-threading.
* recordmydesktop - Linux
* NVidia ShadowPlay (free) - Windows | Requires higher end NVidia card with recent drivers. Works great with minimal frame rate hit but must be used in desktop capture mode with OpenGL.
* glc-capture (free) - Linux | A little more difficult to use, but it forms a layer inbetween FlightGear and your graphics card for the fastest way of capturing video. Also files become very big, so make sure your disk is big enough.

MAGIX is a set of Applications that handles video and audio editing, it also has a recording software.

To install record my desktop on Ubuntu(and it's variations), Linux Mint and Debian open the terminal and type:
'''sudo apt-get install gtk-recordmydesktop'''

== Video Editing Software ==
Programs to edit your video:

{| class="wikitable"
|-
! Name !! Platform !! License !! Notes
|-
| Adobe Premiere Pro || Windows, Mac || Commercial||
|-
| Kdenlive || Linux, BSD, Mac, Windows || GPL ||
|-
| OpenShot|| Linux, Mac, Windows || LGPL ||
|-
| Pitivi|| Linux || GPL ||
|-
| IMovie || Mac || Commercial || IMovie comes with every mac for free. Paid upgrades.
|-
| Sony Vegas Pro || Windows || Commercial ||
|-
| VirtualDub || Windows|| GPL || Discontinued
|-
| Example || Example || Example ||
|-
| Example || Example || Example ||

== Helpful Tips & Tricks ==

* It is recommended to record in full screen mode, this gets rid of any compositor double vertical synching effect, on Linux you simply disable the compositor(the implementation depends on your distro), while for Windows Vista and 7, just disable the Aero theme, unfortunately for Windows 8 and above, the compositor cannot be disabled, the compositor runs as DWM.exe, and is re-instanced by the winlogon.exe manager whenever you try to close it, two alternatives exists is to run the classic shell, or you follow this guideline for a hack to disable DWM.exe temporarily(this will break some effects including the Window Manager). [http://superuser.com/questions/581673/disable-desktop-composition-in-windows-8-force-it disable-desktop-composition-in-windows-8-force-it]

* If you have a powerful machine, it is best to disable VSync(as it adjusts frame-spacing to a minumum static value), if you are worried about maintaining a constant FPS for recording, just impose an internal frame cap in Flightgear by going to View > Rendering Options > Throttle Framerate. From my experience most OpenGL screen recorders impose an FPS limit anyway(unlike some DirectX recorders).

'''Linux:''' export the env variable "vblank_mode=0" on the same session you're running FG from.

'''Windows w/ Nvidia GPU:''' Nvidia Control Panel > Manage 3D settings > Program Settings.

* It is better to write to a separate HDD then the one you're running Flightgear from, as not to overwhelm your drive's IO controller.

* Avoid live encoding, as that would bog down the CPU while recording and consume lots of memory, always perform transmuxing without re-encoding if you want to edit, i recommend ffmpeg if you know how to operate it, or MP4Box(GUI MP4 stream extractor for Windows).

== Finally ==
Everything else is up to the editor... ;)

[[Category:Howto|Creating FlightGear Promo Videos]]

Translation requests

2015-01-07T23:18:01Z

CaptB:

Please post your translation requests here, so that other people can more easily track what's going on, hopefully avoiding duplicate efforts.

In general, it is a good idea to check out the wiki statistics before translating a page, so that the most popular and most important pages get translated first: [[Special:PopularPages]]
*How to translate is described here: [[Help:Translate]].

== Currently work in progress ==
*Please see table below.
*Please add {{tl|BeingTranslated}} to articles that are being translated, remove this when you are finished.
*Please add {{tl|UpdateTranslation}} to articles that have an up-to-date English version but an out-of-date local version.
*Also look at [[:Category:Articles being translated]].

== Open translation requests ==
Check out [[Special:Statistics]] for the most viewed pages:

{| class="wikitable"
! English !! Deutsch !! Español !! Suomi !! Français !! Italiano !! Nederlands !! Português !! Polski !! Русский !! 中文 !! Svenska
|- style="font-weight:bold"
|[[Help:Translate]] || '''/H'''[[De/Help:Übersetzen|De/Done]] || '''/H'''[[Es/Help:Traducir|Es/Done]]|| Suomi
||'''/H'''[[Fr/Help:Traduire|Fr/Done]]|| Italiano || [[Nl/Help:Vertalen|Nl/Done]]|| [[Pt/Help: Traduzir|Pt/Done]] || [[Pl/Pomoc:Tłumaczenie|Pl/Done]] || '''/H'''[[Ru/Справка:Перевод|Ru/Done]]|| 中文||'''/H'''[[Sv/Hjälp:Översättning|Sv/Done]]
|-
|[[Main Page]]|| [[De/Hauptseite| De/Done]]|| [[Es/Portada| Es/Done]] || [[Fi/Etusivu| Fi/Done]]
|| [[Fr/Accueil| Fr/Done]] || [[It/Pagina principale| It/Done]]|| [[Nl/Hoofdpagina| Nl/Done]]|| [[Pt/Página principal| Pt/Done]]|| [[Pl/Strona główna| Pl/Done]]|| [[Ru/Заглавная страница| Ru/Done]]|| [[Zh/首页| Zh/Done]]||Svenska
|-
|[[New to FlightGear]]|| '''/H'''[[De/Neu bei FlightGear| De 50%]]|| [[Es/Nuevo en FlightGear| Es/ Done]] || Suomi
||[[Fr/Nouveau sur flightgear| Fr/Done]]|| [[It/Nuovo per FlightGear|It/50%]] || [[Nl/Nieuw bij FlightGear|Nl 50%]] || [[Pt/Novo no FlightGear|Pt/Done]] || Polski || Русский || [[Zh/FlightGear新手| Zh 50%]]||Svenska
|-
|[[Aircraft]]|| [[De/Flugzeuge| De/Done]]|| [[Es/Aeronaves|Es/Done]]|| Suomi
||[[Fr/Avions| Fr/Done]]||[[It/Aerei|It/Done]]|| '''/H''' [[Nl/Luchtvaartuigen|Nl 50%]] || [[Pt/Avião|Pt/Done]]|| Polski || Русский || 中文||Svenska
|-
|[[Frequently asked questions]]|| '''/H'''[[De/FAQ| De 50%]]|| [[Es/Preguntas frecuentes| Es/Done]]|| Suomi
||[[Fr/Foire aux questions| Fr/Done]]|| [[It/Domande_frequenti| It/Done]] || Nederlands || [[Pt-Br/FAQ|PT/Done]] || [[Pl/FAQ| Pl/Done]] || Русский || 中文||Svenska
|-
|[[Portal:User]]|| [[De/Portal:Benutzer|De/Done]]|| [[Es/Portal:Usuario| Es/Done]] || Suomi
||[[Fr/Portal:Utilisateur|Fr/Done]]|| [[It/Portal:Utente| It/Done]] || Nederlands || Português || [[Pl/Portal:Dla użytkowników|Pl 50%]]|| Русский || [[Zh/Portal:用户|Zh/Done]]||Svenska
|-
|[[Howto: Multiplayer]]|| [[De/Howto: Multiplayer| De/Done]] || [[Es/Howto: Multijugador| Es/Done]]|| Suomi
||[[Fr/Howto: Multijoueur|Fr/Done]]|| Italiano || [[Nl/Howto: Multiplayer|Nl/Done]]|| [[Pt/Tutorial de Multiplayer|PT/Done]] || [[Pl/Konfiguracja trybu multiplayer|Pl/Done]]|| Русский || 中文||Svenska
|-
|[[Howto: Install scenery]]|| [[De/Szenerie installieren|De/Done]] || [[Es/Instalación de escenarios| Es/Done]] || Suomi
|| [[Fr/Installer une scène|Fr/Done]] || Italiano || [[Nl/Scenery_installeren|Nl 50%]] || [[Pt/Instalando Cenário|Pt/Done]]|| [[PL/Instalowanie scenerii|Pl 50%]]|| Русский || 中文||Svenska
|-
|[[Flying the helicopter]]|| [[De/Fliegen mit dem Helikopter|De/Done]]|| [[Es/Volando el helicoptero|Es/Done]]|| Suomi ||[[Fr/Piloter l'hélicoptère|Fr/Done]]||[[it/Pilotare un elicottero|It/Done]]|| [[Nl/Vliegen met de helicopter|Nl/Done]]|| [[Pt/Voando de Helicóptero|PT/Done]] || [[Pl/Lot śmigłowcem|Pl/Done]]|| Русский || 中文||Svenska
|-
|[[Troubleshooting problems]]|| Deutsch || Español || Suomi
||[[Fr/Troubleshooting Problems|Fr/Done]] || Italiano || Nederlands || [[Pt/Resolvendo Problemas|PT/Done]] || Polski || Русский || 中文||Svenska
|-
|[[Altitude]] || '''/H'''[[De/Flughöhe| De 50%]]|| Español || Suomi
||[[Fr/Altitude|Fr/Done]] || Italiano || Nederlands || Português || Polski || Русский || 中文||Svenska
|-
| [[FlightGear hangars]]|| Deutsch || Español || Suomi
|| [[Fr/FlightGear hangars|Fr/Done]] || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|-
| [[FlightGear Launch Control]]|| [[De/FlightGear Launch Control|De/Done]]|| Español || Suomi
|| [[Fr/FlightGear Launch Control|Fr/Done]] || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|-
| [[FlightGear]]|| [[De/FlightGear|De/Done]]|| [[Es/FlightGear|Es/Done]]|| Suomi
|| [[Fr/FlightGear|Fr/Done]] || [[It/FlightGear| It/Done]] || [[Nl/FlightGear|Nl/Done]]|| [[Pt/FlightGear|Pt/Done]]|| [[Pl/FlightGear|Pl/Done]] || Русский || 中文|| Svenska
|-
| [[TerraSync]]|| [[De/TerraSync|De/Done]] || [[Es/TerraSync|Es/Done]] || Suomi
|| [[Fr/TerraSync|Fr/Done]] || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|-
| new article|| Deutsch || Español || Suomi
|| Français || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|}

*Pages that are not linked from the English page are not listed. (that is no guarantee there is no (partial) translation)
*Pages that say 50% are in the process of being translated but feel free to help out (since some authors have gone MIA).
*Items in the table that have no link need your assistance.
*Items or lines in the table that are marked with '''/H''' request your help.
*Help and keep this page up-to-date please (so to avoid double work).

[[Category:Contribution requests]]

Pl/FlightGear Wiki

2015-01-06T22:49:45Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Liczba artykułów i statystyka oglądalności.]]
'''FlightGear Wiki''' jest oficjalnym wiki dla [[:pl:FlightGear|FlightGear]]. Powstał on w 2006 roku i obecnie zawiera szeroki zakres tematów dotyczących [[:pl:FlightGear|FlightGear]]. Zawiera stworzoną przez ochotników treść na licencji [[GPL]] dotyczącą rozwoju i użytkowania FlightGear oraz pokrewnych projektów, jak też ogólnych informacji dotyczących lotnictwa i [[:category:Software|oprogramowania]].

Główne dojścia do artykułów to portale [[pl/Portal:User|użytkownik]] i [[pl/Portal:Developer|developer]].

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

Pl/FlightGear

2015-01-06T22:32:42Z

CaptB:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] w 0.9.9
| OpracowanePrzez = Developerzy FlightGear i współtwórcy
| PierwszeWydanie = Lipec 17, 1997
| ObecnaWersja = 3.2.0
| NapisaneW = C++
| SystemyOperacyjne = 32-bit Windows, Linux, Mac OS X, FreeBSD, Solaris lub IRIX
| platforma = wieloplatformowy
| developmentstatus = Aktywny (1996-)
| typ = Symulator Lotu
| licencja = [[GNU General Public License]]
| strona = http://www.flightgear.org/
}}

[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

'''FlightGear Flight Simulator''' (w skrócie '''FlightGear''' lub '''FGFS''') to stworzona przez ochotników, wyrafinowana i darmowa platforma symulacji lotu na licencji Open Source. FlightGear jest wydany na zasadach licencji [[GNU General Public License]] i jest on w większości napisany przy użyciu języka programowania C++.

Coraz bardziej szczegółowe i zaawansowane wersje FlightGear są corocznie wydawane od zapoczątkowania projektu w 1996 roku.

Najnowsze publiczne wydanie dostępne jest do pobrania na [http://www.flightgear.org/Downloads/ http://www.flightgear.org/Downloads/] wraz z właściwymi wersjami dla Microsoft Windows (Win 32), Mac OS X, Linux, IRIX, i Solaris.

== Historia ==
{{main article|FlightGear History}}

Rozwój FlightGear rozpoczął się od propozycji w 1996 roku, w oparciu o własny kod 3D. Rozwój wersji opartej na [[OpenGL]] rozpoczął się w 1997 roku Curtis Olson. Wiele innych osób miało wkład w projekt od jego zapoczątkowania.

FlightGear włączył w projekt inne oprogramowanie oparte na licencji Open Source, włączając w to model lotu NASA - LaRCsim, jak również darmowy Numeryczny Model Terenu (DEM). Pierwsze wydanie binarne z kodem 3D opartym na OpenGL zostało udostępnione w 1997 roku.

[[File:FG-A-10.jpg|thumb|270px|Kokpit 3D Cockpit [[A-10]] w wersji 1.0.0 rok 2008]]

W 2008 roku wersja 1.9.0 FlightGear przeszła z biblioteki [[PLIB]] na [[OSG]] co spowodowało tymczasową utratę niektórych funkcji programu, takich jak wyświetlanie chmury 3D i cienie, za to nowo wprowadzone funkcje programu wprowadziły symulacje na nowy poziom realizmu.

== Program ==

Silnik symulacji we FlightGear to [[SimGear]]. Jest on używany zarówno jako aplikacja użytkownika końcowego jak i przy pracach badawczych w środowiskach akademickich w celu rozwoju zagadnień związanych z symulacją lotu.

Przykładem na możliwość dostosowywania FlightGear jest szeroki wachlarz modeli dostępnych statków powietrznych, od [[:Category:Gliders|glider]] do [[Helicopter]], przez [[:Category:Airliners|airliners]] do [[Military aircraft|fighter jets]]. Modele te zostały wykonane i dodane do projektu przez wielu ochchotników ze społecznośći FlightGear.

Od wersji 0.9.10 statki powietrzne we FlightGear używają jednego z trzech Modeli Danych Lotu (FDM), są to: JSBSim, YAsim lub UIUC. Obecnie wyłącznie jeden silnik terenu jest w użyciu, jest nim TerraGear. Dostępne efekty pogodowe to między innymi chmury 3D, efekty świetlne, pory dnia i nocy.

=== Modele Dynamiki Lotu ===
[[Flight Dynamics Models]] (FDM) odpowiada za to w jaki sposób w programie jest symulowany lot statku powietrznego. FlightGear korzysta z własnych oraz zewnętrznych projektów Modeli Dynamiki Lotu. Każdy statek powietrzny musi być tak zaprogramowany, aby korzystał z jednego z dostępnych modeli dynamiki lotu. Obecnie FlightGear jest jedynym graficznym symulatorem lotu korzystającym ze wszystkich wspomnianych Modeli dynamiki Lotu, a UIUC and YASim zostały rozwinięte z myślą i w szczególności dla FlightGear.

Wczesne wersje programu używały FDM opartym na [[:aRCsim]] od NASA, który w kolejnych wersjach został zastąpiony przez bardziej elastyczne FDM.

* [[JSBSim]] - Domyślny Model Dynamiki Lotu od 2000 roku.
* [[YASim]] - Inny FDM, używający odmiennych metod obliczeniowych. Wprowadzony od wersji 0.7.9 w 2002 roku.
* [[UIUC]] - Kolejny FDM, rozwinięty przez UIUC Applied Aerodynamics Group z Uniwersytetu w Illinois na Urbana-Champaign, jako podstawę użyty został LaRCsim.
* FlightGear może być tak skonfigurowany, aby przyjmować dane z zewnętrznych źródeł FDM takich jak MatLab.
* Inne FDM zostały rozwinięte dla szczgólnych przypadków statków lotniczych takich jak balony i sterowce.

=== Zależności FlightGear ===

W przeciwieństwie do komercyjnych tytułów, głównym wynikim pracy projektu jest wydanie zestawu kodów źródłowych. Aby użyć programu należy skompulować udostępniony kod dla docelowej platfory, na której ma pracować. Biblioteki użyte przez FlightGear były różne w zależności od okresu. Główną biblioteką zależną jest [[SimGear], która jest silnikiem symulacji dla FlightGear. [[TerraGear]] nie jest zależnością, a raczej tylko nazwą dla domyślnego silnika odpowiadającego za generowanie terenu we FlightGear. OpenAL jest używany dla obsługi dźwięku, włączając wsparcie dla SDL ( od wrsji 0.9.5 ). PLIB jest użyte do obsługi sprzętowej, przed wprowadzeniem OpenAL, także dla obsługi dźwięku. [[OpenGL]] jest użyty dla swoich funkcji 3D, DirectX nie jest wspierany. [[OpenSceneGraph]] jest również zintegrowany we FlightGear. Na koniec do kompilacji jest konieczna biblioteka Simple Direct Media Layer (SDL) Niektóre zależności mogą się różnić w zależności od tego na jaką platformę docelową jest kompilowany kod. Użytkownicy FlightGear powinni sami kompilować kod, lub jeżeli nie jest ona dostępna w ramach projektu, korzystać z wersji binarnej udostępnionej przez osoby trzecie.

== Sprzęt==

Sprzęt konieczny do uruchomienia FlightGear jest ograniczony do sprzętu, który wspiera [[OpenGL]] i akceleracje 3D, przy czym najlepej wspierana jest NVIDIA. Wczesne wersje posiadały wsparcie dla kart 3dfx, jednak wsparcie to zostało wycofane wraz z zwiększającymi się wymaganiami sprzętowymi.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]
== dodatki i dostosowywanie ==

Oprogramowanie może być zintegrowane z FlightGear poprzez zależności lub jest zewnętrzne, współdziałające z nim. Oprogramowanie to może być cześcią projektu FlightGear lub takie, które jest rozwijane niezależnie, ale udostępniane przez projekt FlightGear.

Ważnym dodatkowym oprogramowaniem jest interfejs graficzny służący do wykonania pliku startowego FlightGear. We wczesnych wersjach FlightGear był wykonywany jedynie poprzez [[comman line]], jednak w 2003 roku od wersji 0.9.3 FlightGear Launch Control został załączony z Front-Endem ""[[FG Launcher]]"".
Podobną rolę spełnia ''[[KFreeFlight]]'' dla środowiska KDE. ''FGTools'' jest alternatywnym front-endem dla środowiska Windows. ''FGKicker'' jest używany dla GTK+.

Inne ważne oprogramowanie to edytory i projekty dla danych terenu. ''[[Atlas]]'' pozwala na wspieranie map we Flightear; ''[[Kelpie Flight Planner]]'' to rozwijane w Javie narzędzie do planowania lotów.
''[[FlightGear Scenery Designer]]'' to edytor scenerii pomocny przy pracy z danymi terenu. Projekt ''[[World Custom Scenery Project]]'' to projekt pomagający koordynować wspólne wysiłki na rzecz tworzenia scenerii. Na koniec edytor ''[[TaxiDraw]]'' do tworzenia nowych pasów startowych i dróg kołowania.

=== Statki Powietrzne ===
{{Main article|Table of models}}

Na początku FlightGear dysponował tylko jednym statkiem powietrznym, był to Navion zawarty w projekcie LaRCsim od NASA, który w 2000 roku został zastąpiony przez Cessnę 172. Wprowadzenie i rozwój UIUC, jak też JSBSim jak również poźniejsze wprowadzienie YAsim, ktory został głównym FDM projektu FlightGear, zaowocowało wprowadzeniem do projektu kilku dodatkowych statków powietrznych. W projekcie 1.9.0 jest dostępnych ponad 230 statków powietrznych, jednak tylko część jest zawarta w głównej dystrybucji.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] zaparkowany w scenerii [[EHAM]] ]]

=== Sceneria ===
{{Main article|Scenery}}

Projekt [[WorldScenery]] dla FlightGear zawiera dane o wysokości i klasie terenu całego świata.
Objekty takie jak terminale, wiatraki i mosty są zebrane w [[FlightGear Scenery Database|Scenery Database]].

=== Sieć i wiele monitorów ===

Istnieje kilka możliwośći, które pozwalają kounikować się FlightGear z inną instancją FlightGear. Dostępny jest protokół [[Multiplayer Howto|multiplayer]], co umożliwia lot w formacji lub symulowanie kontroli ruchu lotniczego w sieci lokalnej. Protokół Multiplayer zostanie wkrótce tak rozbudowany, aby także pozwalał na pracę w internecie. Dodatkową cechą możliwości sieciowych jest opcja podglądu innych graczy na mapach Google.

Kilka instancji FlightGEar może zostać tak zsynchronizowane, aby korzystać z wielu monitorów. Możliwe jest uzyskanie bardzo dobrej synchronizacji między monitorami jeżeli wszystkie instancje FlightGear będą pracować z tą samą częstotliwością wyświetlania klatek.

== Kod FlightGear vs wersja binarna ==

W przeciwieństwie do komercyjnego oprogramowania, data wydania dotyczy wyłącznie kodu źródłowego, a nie do wersji binarnej. Aby stworzyć wykonywalny program, kod źródłowy musi zostać skompilowany, co wymaga kilku bibliotek, włączając w to kilka ogólnych oraz szczegółowych dla poszczególnych platform, jednak
jest to zbyt trudne zadanie dla wielu zwykłych użytkowników, dlatego ochotnicy społeczności pracują, aby udostępnić wersje binarne dla poszczególnych platform i systemów operacyjnych. Dystrybucje te różnią się poziomem stabilności, wydajnością, zależnościami, a także tym, jak aktualne są one w stosunku do kodu źródłowego. Dla przykładu, niektóre ze starszych wersji binarnych pracują poprawnie pod Mac OS9, ale nowsze wersje wymagają szczególnych wersji Mac OS X.

Inny przykład, najnowsza wersja kodu w 2007 roku to 0.9.11-pre1 (pre-release ) i 0.9.10 (finalna) Jednak dostępne wersje binarne znacznie się różniły. Oto kilka dostępnych wersji binarnych rok po udostępnieniu kodu 0.9.10:

* Win-32 pakiet ~138MB (v0.9.10) Dla Windows 98, 2000, ME, 32 bitowe XP )
* Linux - pakiety dla poszczególnych dystrybucji
** Pakiet Slackware (v0.9.10), Fedora Core 2,3,4 packages (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9)
* Pakiet Solaris packages dla SPARC lub procesorów x86.
** SPARC (v0.9.8), x86 (v0.9.9)
* Silicon Graphics IRIX
** Wersja binarna SGI binaries (v0.9.9)
* Mac OS X
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)
* Pakiet FreeBSD (v0.9.10)

== Recenzje FlightGear ==
{{Main article|FlightGear Reviews}}

== Łącza zewnętrzne ==
{{Main article|Links}}
* [http://www.flightgear.org Official website]
* [http://fgfs.i-net.hu/ Community website]
* [http://www.caballerosaguila.shialeweb.com/ Club website] (Spanish)
* [http://gallery.flightgear.org.uk/ Development screenshots]

== Źródłą ==
* [http://www.flightgear.org/proposal-3.0.1 Original Flight Gear Proposal] by David L. Murr (Revision 3.0.1)
* [http://en.wikipedia.org/wiki/FlightGear Wikipedia]

[[de:FlightGear]]
[[en:FlightGear]]
[[es:FlightGear]]
[[fr:FlightGear]]
[[is:FlightGear]]
[[nl:FlightGear]]
[[pt:FlightGear]]
[[pl:FlightGear]]

Pl/FlightGear

2015-01-06T22:06:22Z

CaptB:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] w 0.9.9
| OpracowanePrzez = Developerzy FlightGear i współtwórcy
| PierwszeWydanie = Lipec 17, 1997
| ObecnaWersja = 3.2.0
| NapisaneW = C++
| SystemyOperacyjne = 32-bit Windows, Linux, Mac OS X, FreeBSD, Solaris lub IRIX
| platforma = wieloplatformowy
| developmentstatus = Aktywny (1996-)
| typ = Symulator Lotu
| licencja = [[GNU General Public License]]
| strona = http://www.flightgear.org/
}}

[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

'''FlightGear Flight Simulator''' (w skrócie '''FlightGear''' lub '''FGFS''') to stowrzona przez ochotników wyrafinowana i darmowa platforma symulacji lotu na lincencji open source. FlightGear jest wydany na zasadach licencji [[GNU General Public License]] i jest on w większości napisany przy użyciu języka programowania C++.

Coraz bardziej szczegółowe i zaawansowane wersje FlightGear są wydawane corocznie od zapoczątkowania projektu w 1996 roku.

Najnowsze publiczne wydanie jest dostępne do pobrania na [http://www.flightgear.org/Downloads/ http://www.flightgear.org/Downloads/] wraz z właściwymu wersjami dla Microsoft Windows (Win 32), Mac OS X, Linux, IRIX, i Solaris.

== Historia ==
{{main article|FlightGear History}}

Rozwój FlightGear rozpoczął się od propozycji w 1996 roku, w oparciu o własny kodu 3D. Rozwój wersji opartej na [[OpenGL]] rozpoczął w 1997 roku Curtis Olson. Wiele innych osób miało wkład w project od jego zapoczątkowania.

FlightGear włączył w projekt inne operogramowanie oparte na licencji open source, włączając w to model lotu NASA - LaRCsim jak również darmowy Numeryczny Model Terenu (DEM) Pierwsze wydanie binarne z kodem 3D opartym na OpenGL zostało udostępnione w 1997 roku.

[[File:FG-A-10.jpg|thumb|270px|Kokpit 3D Cockpit [[A-10]] w wersji 1.0.0 rok 2008]]

W 2008 roku wersja 1.9.0 FlightGear przeszła z biblioteki [[PLIB]] na [[OSG]] co spowodowało tymczasową utratę niektórych funkcji programu, takich jak wyświetlanie chmury 3D i cienie, za to nowo wprowadzone funkcje programu wprowadziły symulacje na nowy poziom realizmu.

== Program ==

Silnik symulacji we FlightGear to [[SimGear]]. Jest on używany zarówno jako aplikacja użytkownika końcowego jak i przy pracach badawczych w środowiskach akademickich w celu rozwoju zagadnień związanych z symulacją lotu.

Przykładem na możliwość zdolnośc dostosowywania FlightGear jest szeroki wachlarz modeli dostępnych statków powietrznych, od [[:Category:Gliders|glider]] do [[Helicopter]], przez [[:Category:Airliners|airliners]] do [[Military aircraft|fighter jets]]. Modele te zostałe wykonane i dodane do projektu przez wielu ochchotników ze społecznośći FlightGear.

Od wersji 0.9.10 statki powietrzne we FlightGear używaja jednego z trzech Modeli Danych Lotu (FDM), są to JSBSim, YAsim lub UIUC. Obecnie wyłącznie jeden silnik terenu jest w użyciu, jest to TerraGear. Dostępne efekty pogodowe to między innymi chmury 3D, efekty świetlne, pory dnia i nocy.

=== Modele Dynamiki Lotu ===
[[Flight Dynamics Models]] (FDM) odpowiada za to w jaki sposób w programie jest symulowany lot statku powietrznego. FlightGear korzysta z własnych oraz zewnętrznych projektów Modeli Dynamiki Lotu. Każdy statek powietrzny musi być tak zaprogramowany aby korzystać z jednego z dostępnych modeli dynamiki lotu. Obecnie FlightGear jest jedynym graficznym symulatorem lotu korzystającym ze wszystkich wspomnianych Modeli dynamiki Lotu, a UIUC and YASim zostały rozwinięte z myślą i w szczególności dla FlightGear.

Wczesne wersje programu używały FDM opartym na [[:aRCsim]] od NASA. który w kolejnych wersjach został zastąpiony przez bardziej elastyczne FDM

* [[JSBSim]] - Domyślny Model Dynamiki Lotu od 2000 roku.
* [[YASim]] - Inny FDM, używający odmiennych metod obliczeniowych. Wprowadzony od wersji 0.7.9 w 2002 roku.
* [[UIUC]] - Kolejny FDM, rozwinięty przez UIUC Applied Aerodynamics Group z Uniwersytetu w Illinois na Urbana-Champaign, jako podstawę użyty został LaRCsim.
* FlightGear może być tak skonfigurowany aby przyjmować dane z zewnętrznych źródeł FDM takich jak MatLab.
* Inne FDM zostały rozwinięte dla szczgólnych przypadków statków lotniczych takich jak balony i sterowce.

=== Zależności FlightGear ===

W przeciwieństwie do komercyjnych tytułów, głównym wynikim pracy projektu jest wydanie zestawu kodów źródłowych. Aby użyć programu należy skompulować udostępniony kod dla docelowej platfory na której ma pracować. Biblioteky użyte przez FlightGear były różne w zalężności od okresu. Główną biblioteką zależną jest [[SimGear]] która jest silnikiem symulacji dla FlightGear. [[TerraGear]] nie jest zależnością a raczej tylko nazwą dla domyślnego silnika odpowiadającego za generowanie terenu we FlightGear. OpenAL jest używany dla obsługi dzwięku, włączając wsparcie dla SDL ( od wrsji 0.9.5 ). PLIB jest użyte do obsługi sprzętowej, przed wprowadzeniem OpenAL także dla obsługo dzwięku. [[OpenGL]] jest użyty dla swoich funkcji 3D, DirectX nie jest wspierany. [[OpenSceneGraph]] jest również zintegrowany we FlightGear. Na koniec do kompilacji jest konieczna biblioteka Simple Direct Media Layer (SDL) Niektóre zależności mogą się różnić w zależności id tego na jaką platformę docelową jest kompilowany kod. Użytkownicy FlightGear powinni sami kompilować kod, lub jeżeli nie jest ona dostępna w ramach projektu, korzystać z wersji binarnej udostępnionej przez osoby trzecie.

== Sprzęt==

Sprzęt konieczny do uruchomienia FlightGear jest ograniczony do sprzętu który wspiera [[OpenGL]] i akceleracje 3D, przy czym najlepej wspierana jest NVIDIA. Wczesne wersje posiadały wsparcie dla kart 3dfx, jednak wsparcie to zostało wycofane wraz z zwiększającymi sie wymaganiami sprzętowymi.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]
== dodatki i dostosowywanie ==

Oprogramowanie może być zintegrowane z FlightGear poprzez zależności lub jest zewnętrzne współdziałające z nim. Oprogramowanie to może być cześcią projektu FlightGear, lub takie które jest rozwijane niezależnie ale udostępniane przez projekt FlightGear.

Ważnym dodatkowym oprogramowaniem jest interfejs graficzny służący do wykonania pliku startowego FlightGear. We wczesnych wersjach FlightGear był wykonywany jedynie poprzez [[comman line]], jednak w 2003 roku od wersji 0.9.3 FlightGear Launch Control został załączony z Front-Endem ""[[FG Launcher]]"".
Podobnym rolę spełnia ''[[KFreeFlight]]'' dla środowiska KDE. ''FGTools'' jest alternatywnym front-endem dla środowiska Windows. ''FGKicker'' jest używany dla GTK+.

Inne ważne oprogramowanie to edytory i projekty dla anych terenu. ''[[Atlas]]'' pozwala na wspieranie map we Flightear; ''[[Kelpie Flight Planner]]'' to rozwijane w Javie narzędzie do planowania lotów.
''[[FlightGear Scenery Designer]]'' to edytor scenerii pomocny przy pracy z anymi terenu. Project ''[[World Custom Scenery Project]]'' to projekt pomagający koordynować wspólne wysiłki na rzecz tworzenia scenerii. Na koniec edytor ''[[TaxiDraw]]'' do tworzenia nowych pasów startowych i dróg kołowania.

=== Statki Powietrzne ===
{{Main article|Table of models}}

Na początku FlightGear dysponował tylko jednym statkiem powietrznym, był to Navion zawarty w projekcie LaRCsim od NASA, który w 2000 roku został zastąpiony przez Cessne 172. Wprowadzenie i rozwój UIUC jak też JSBSim jak również poźniejsze wprowadzienie YAsim, ktory został głównym FDM projektu FlightGear zaowocowało wprowadzeniem do projektu kilka dodatkowych statków powietrznych. W projekcie 1.9.0 jest dostępnych ponad 230 statków powietrznych, jednak tylko część jest zawarta w głównej dystrybucji.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] zaparkowany w scenerii [[EHAM]] ]]

=== Sceneria ===
{{Main article|Scenery}}

Projekt [[WorldScenery]] dla FlightGear zawiera dane o wysokosci i klasie terenu całego świata.
Objekty takie jak terminale, wiatraki i mosty są zebrane w [[FlightGear Scenery Database|Scenery Database]].

=== Sieć i wiele monitorów ===

Istnieje kilka możliwośći które pozwalają kounikować się FlightGear z inna isnatncją FlightGear. Dostępny jest protokół [[Multiplayer Howto|multiplayer]] co umożliwia lot w formacji lub symulowanie kontroli ruchu lotniczego w sieci lokalnej. Protokół Multiplayer został wkrótce tak rozbudowany aby także pozwalał na pracę w internecie. Dodatkową cechą możłiwości sieciowych jest opcja podglądu innych graczy na mapach google.

Kilka instancji FlightGEar mogą zostać tak zsynchronizowane aby korzystać z wielu monitorów. Możliwe jest uzyskanie bardzo dobrej synchronizacji między monitorami jeżeli wszystkie instancje FlightGear będą pracować z tą samą częstotliwością wyświetlania klatek.

== Kod FlightGear vs wersja binarna ==

W przeciwieństwie do komercyjnego oprogramowania, data wydania dotyczy wyłącznie kodu źródłowego a nie do wersji binarnej. Aby stworzyć wykonywalny program, kod źródłowy musi zostać skompilowany, co wymaga kilku bibliotek, włączając w to kilka ogólnych oraz szczególnych dla poszczególnych platform, jednak
jest zbyt trudne zadanie dla wielu zwykłych użytkowników dlatego ochotnicy społeczności pracują aby udostępnić wersje binarne dla poszczególnych platform i systemów operacyjnych. Dystrybucje te różnią się poziomem stabilności, wydajnością, zależnościami a także tym jak aktualne one są w stosunku do kodu źródłowego. Dla przykładu, niektóre ze starszych wersji binarnych pracują poprawnie pod Mac OS9 ale nowsze wersje wymagają szczególnych wersji Mac OS X.

Inny przykład, najnowsza wersja kodu w 2007 roku to 0.9.11-pre1 (pre-release ) i 0.9.10 (finalna) Jednak dostępne wersje binarne znacznie się różniły. Otot kilka przykładów dostępnych wersji binarnych rok po udostępnieniu kodu 0.9.10:

* Win-32 pakiet ~138MB (v0.9.10) Dla Windows 98, 2000, ME, 32 bitowe XP )
* Linux - pakiety dla poszczególnych dystrybucji
** Pakiet Slackware (v0.9.10), Fedora Core 2,3,4 packages (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9)
* Pakiet Solaris packages dla SPARC lub procesorów x86.
** SPARC (v0.9.8), x86 (v0.9.9)
* Silicon Graphics IRIX
** Wersja binarna SGI binaries (v0.9.9)
* Mac OS X
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)
* Pakiet FreeBSD (v0.9.10)

== Recenzje FlightGear ==
{{Main article|FlightGear Reviews}}

== Łącza zewnętrzne ==
{{Main article|Links}}
* [http://www.flightgear.org Official website]
* [http://fgfs.i-net.hu/ Community website]
* [http://www.caballerosaguila.shialeweb.com/ Club website] (Spanish)
* [http://gallery.flightgear.org.uk/ Development screenshots]

== Źródłą ==
* [http://www.flightgear.org/proposal-3.0.1 Original Flight Gear Proposal] by David L. Murr (Revision 3.0.1)
* [http://en.wikipedia.org/wiki/FlightGear Wikipedia]

[[de:FlightGear]]
[[en:FlightGear]]
[[es:FlightGear]]
[[fr:FlightGear]]
[[is:FlightGear]]
[[nl:FlightGear]]
[[pt:FlightGear]]
[[pl:FlightGear]]

Pt/FlightGear

2015-01-06T22:04:41Z

CaptB:

{{out of date}}
{{UpdateTranslation}}

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] na versão 0.9.9
| developedby = Comunidade do FlightGear
| initialrelease = 17 de Julho de 1997
| latestrelease = 3.4
| writtenin = C++
| os = Windows, Linux, Mac OS X, FreeBSD, Solaris ou IRIX
| platform = Várias
| developmentstatus = Ativo (1996-)
| type = Simulador de voo
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/
}}

[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] no FlightGear 1.0]]

'''O Simulador de Voo FlightGear''' (abreviado como '''FlightGear''' ou '''FGFS''') é um simulador de voo sofisticado, livre, completamente feito em código aberto, criado por voluntários. FlightGear é publicado sob os termos da [[GNU General Public License]]. A maior parte do FlightGear é escrita na linguagem de programação C++.

Versões cada vez mais detalhadas e realistas do FlightGear tem sido lançadas todo ano desde que o projeto foi lançado em 1996.

A última versão estável está disponível para download em [http://www.flightgear.org/Downloads/ http://www.flightgear.org/Downloads/], com compilações para vários sistemas operacionais incluindo o Microsoft Windows (32 e 64 bits), Mac OS X, Linux, IRIX, e Solaris.

== História ==
{{main article|FlightGear History}}

O desenvolvimento do FlightGear começou com uma proposta online em 1996, usando gráficos cutomizados em 3D. O desenvolvimento de uma versão em [[Pt/OpenGL|OpenGL]] foi iniciado por Curtis Olson em 1997. Muitas pessoas já contribuíram para o projeto desde sua concepção.

FlightGear incorporou outros recursos em código aberto ao invés de começar "do zero". Um deles é o modelo e voo LaRCsim da NASA e dados de elevação livres (SRTM). Os primeiros binários funcionando (.exe) saíram em 1997. Um grande desenvolvimento comunitário de novas versões resultou em versões progressivamente mais estáveis e avançadas. Por volta de 2001, o time estava lançando novas versões beta regularmente, e em torno de 2005, a maturidade do programa causou mais avaliações e aumentou a popularidade do FlightGear. Em 2007, o projeto saiu da fase beta com o lançamento da versão 1.0.0, dez anos após o lançamento inicial do FlightGear em 1997.

[[File:FG-A-10.jpg|thumb|270px|Cockpit 3D do [[A-10]] na versão 1.0.0 em 2008]]

Em 2008, a versão 1.9.0 do FlightGear foi lançada com a transição do sistema [[Pt/PLIB|PLIB]] para o sistema [[Pt/OpenSceneGraph|OSG]], o que causou a perda temporária de algumas funções como nuvens 3D e sombras. Porém, novas funções gráficas (como partículas) aumentaram o realismo gráfico do FlightGear.

== Software ==

O motor de simulação do FlightGear é chamado de [[Pt/SimGear|SimGear]]. É usado tanto para pesquisa acadêmica quanto para simulação de voo.

FlightGear é altamente customizável, possuindo desde [[:Category:Gliders|planador]]es até [[Pt/Helicóptero|helicópteros]], [[:Category:Airliners|jatos comerciais]] e [[Military aircraft|aviões militares]]. Esses modelos foram desenvolvidos por diversas pessoas.

As aeronaves do FlightGear utilizam um dos três modelos de voo: JSBSim, YAsim ou UIUC. Atualmente, apenas um motor de terreno é usado, TerraGear. Efeitos de clima incluem nuvens 3D, efeitos de luz, hora do dia, entre outros.

=== Modelos de voo ===
[[Pt/Modelos de Voo|Modelos de voo]] (FDM ou MDV) são como o voo é simulado no FlightGear. Toda aeronave precisa ser programada com um MDV para que o simulador saiba seu peso, velocidade de estol etc. UIUC e YAsim foram desenvolvidos especialmente para o FlightGear.

As primeiras versões utilizavam uma variante do MDV [[Pt/LaRCsim|LaRCsim]] da NASA, porém esse não era muito flexível, provocando a mudança para os MDVs atuais, mais flexíveis e realistas.

* [[Pt/JSBSim|JSBSim]] - o MDV padrão desde 2000.
* [[Pt/YASim|YASim]] - outro MDV utilizando outro tipo de cálculo. Apareceu pela primeira vez na versão 0.7.9 em 2002.
* [[Pt/UIUC|UIUC]] - mais um MDV, desenvolvido pelo UIUC Applied Aerodynamics Group na Universidade de Illinois em Urbana-Champaign, baseado no LaRCsim.
* FlightGear também pode usar MDVs externos (não incluídos por padrão), como o Matlab.
* Outros tipos de MDV para aeronaves específicas foram criados, como para dirigíveis e outras aeronaves mais leves que o ar.

=== Dependências ===
Ao contrário de softwares comerciais, tudo o que é feito no projeto sai em código-fonte C. Para transformá-lo em um programa utilizável, ele deve ser compilado para uma plataforma específica. As bibliotecas de software usadas para compilar o FlightGear têm mudado ao longo dos anos. A principal é a [[Pt/SimGear|SimGear]], que é a biblioteca usada para a simulação. [[Pt/TerraGear|TerraGear]] não é uma dependência, mas simplesmente um nome para o programa gerenciador de terreno padrão no FlightGear. O OpenAL é usado para som incluindo suporte à SDL (desde a versão 0.9.5). PLIB é usado para suporte de hardware e antigamente era usado para áudio, mas foi substituído pelo OpenAL. [[Pt/OpenGL|OpenGL]] é usado para suporte 3D e outro tipo de aceleração (como DirecX) não é suportada. O [[Pt/OpenSceneGraph|OpenSceneGraph]] é integrado ao FlightGear e serve para renderizar gráficos, em conjunto com o OpenGL. Por fim, Simple DirectMedia Layer é uma biblioteca de software que é usada para compilação. Algumas das dependências variam dependendo da plataforma para qua o código será compilado. Os usuários do FlightGear podem compilar o código por si próprios ou usar binários pré-compilados.

== Hardware ==
Os requisitos de hardware de que o FlightGear necessita são pequenos para máquinas que suportam o [[Pt/OpenGL|OpenGL]] e com aceleração de hardware 3D, com hardware da NVIDIA tendo o melhor suporte. As primeiras versões suportavam placas de vídeo 3dfx, porém isso foi cancelado porque os requerimentos de hardware aumentavam

[[File:Fgrun-page2.jpg|thumb|left|270px|O [[Pt/Assistente do FlightGear|Assistente do FlightGear]]]]
== Add-ons e customização ==
Há programas que estão integrados no FlightGear (dependências) e programas que se integrram como opcionais (add-ons). Alguns add-ons estão incluídos nos binários do FlightGear, dependendo do sistema operacional, como o [[Pt/Assistente do FlightGear|Assistente do FlightGear]], feitos pela comunidade. Porém, há add-ons independentes (não incluídas nos binários) mas que são hospedadas pelo FlightGear (como aeronaves).

Um software adicional (mas incluído) é a interface gráfica para iniciar o FlightGear. Por um tempo, no início, o FlightGear só podia ser iniciado através de uma [[Pt/Linha de comando|linha de comando]]. Porém, o controle gráfico de início do FlightGear foi incluído na versão 0.9.3 em 2003. ''[[Pt/KFreeFlight|KFreeFlight]]'' é um iniciador do FlightGear para KDE/Linux. o ''FGTools'' é um inciador alternativo para Windows. ''FGKicker'' é um iniciador baseado em GTK+.

Outros programas importantes incluem editores e projetos para terreno e cenário. ''[[Pt/Atlas|Atlas]]'' é um leitor de cartas e mapas para FlightGear.; ''[[Pt/Kelpie Flight Planner|Kelpie Flight Planner]]'' é um planejador de voo baseado em Java. ''[[Pt/FlightGear Scenery Designer|FlightGear Scenery Designer]]'' é um editor de cenário e terreno para FlightGear. O ''[[Pt/World Custom Scenery Project|World Custom Scenery Project]]'' é um projeto coordenando adições ao cenário como terreno detalhado e construções 3D. Por fim, ''[[Pt/TaxiDraw|TaxiDraw]]'' é um editor para pistas e pistas de táxi de um aeroporto.

=== Aeronaves ===

{{Main article|Table of models}}

O FlightGear começou com uma aeronave incluída do LaRCsim da NASA, um Navion, que foi trocado por um Cessna 172 em 2000. A criação e desenvolvimento do UIUC e JSBSim possibilitou o desenvolvimento de muito mais aeronaves, assim como o YASim, que então se tornou o MDV mais usado no FlightGear. Mais de 230 aeronaves estão disponíveis para o FlightGear 1.9.1, porém apenas poucas estão incluídas no instalador base do FlightGear.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300]] parado no cenário de [[EHAM]]]]

=== Cenário ===
{{Main article|Scenery}}
O [[Pt/Cenário|Cenário]] do FlightGear contém dados de elevação (SRTM) e dados de terreno do mundo todo. Objetos como terminais, moinhos e pontes estão na [[FlightGear Scenery Database|Base de Dados de Cenário]].

=== Rede e multi-display ===
Opções de rede possiblitam o contato entre vários usuários do FlightGear. Um protocolo de multiplayer está disponível para usar o FlightGear online com outros jogadores. Isso pode ser usado para voos em formação, linhas aéreas virtuais ou [[Pt/Simulação de Torre de Controle|Simulação de Torre de Controle]]. Outras funções incluem um mapa (MPMap) que possibilita usuários ver onde outros usuários estão.

Ver também: [[Pt/Tutorial de Multiplayer|Tutorial de Multiplayer]].

Também é possível sincronizar múltiplas instâncias do FlightGear para uso em diferentes monitores simultaneamente. Se todas essas instâncias estiverem sendo exectuadas com a mesma taxa de quadros (FPS), é possível ter boa sincronização entre displays.

== Código-fonte vs. binários ==

Ao contrário de muitos softwares comerciais, as datas de lançamento de versões correspondem ao lançamento do código-fonte, não o instalador executável. Para transformar o código em um programa utilizável, o mesmo deve ser compilado, o que necessita de bibliotecas específicas (ver a seção "Dependências"). Porém, como isto é uma tarefa difícil para a maioria dos usuários, outros contribuidores irão trabalhar para produzir arquivos pré-compilados (binários) para uma certa plataforma e sistema operacional. Estes arquivos variam em sua estabilidade, performance, dependências e o quão atualizadas estão em relação às outras.

Por exemplo, por volta de 2007 a última versão (experimental) era 0.9.11-pre1 e a versão 0.9.10 era a estável. Porém, os binários variam significativamente. Veja como estavam as versões após um ano do lançamento 0.9.10:

* Windows tinha um binário de 138 MB (v0.9.10) para Windows 98, 2000, ME e XP.

* Versões pré-compiladas para diferentes distribuições do Linux:
** Slackware (v0.9.10), Fedora Core 2,3 e 4 (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9).

* Solaris para processadores SPARC e x86:
** SPARC (v0.9.8), x86 (v0.9.9)

* Silicon Graphics IRIX (v0.9.9)

* Mac OS X:
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)

* FreeBSD tinha um binário da versão 0.9.10

== Avaliações do FlightGear ==
{{Main article|FlightGear Reviews}}

== Ligações externas ==
{{Main article|Links}}
* [http://www.flightgear.org Website oficial]
* [http://fgfs.i-net.hu/ Website da comunidade]
* [http://www.caballerosaguila.shialeweb.com/ Website da comunidade em Espanhol]
* [http://gallery.flightgear.org.uk/ Screenshots dos desenvolvedores]

== Ver também ==
* [http://www.flightgear.org/proposal-3.0.1 Proposta original (em Inglês)] por David L. Murr (Revisão 3.0.1)
* [http://pt.wikipedia.org/wiki/FlightGear Artigo na Wikipédia]

[[Category:FlightGear]]
[[de:FlightGear]]
[[en:FlightGear]]
[[es:FlightGear]]
[[fr:FlightGear]]
[[it:FlightGear]]
[[nl:FlightGear]]
[[pl:FlightGear]]

It/FlightGear

2015-01-06T22:02:47Z

CaptB:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Aereo dei fratelli Wright]] in 0.9.9
| developedby = FlightGear Developers & Contributors
| initialrelease = 17 Luglio 1997
| latestrelease = 3.2 (15 Ottobre 2014)
| writtenin = C++
| os = Windows, Linux, Mac OS X, FreeBSD, Solaris oppure IRIX
| platform = Multipiattaforma
| developmentstatus = Attivo (1996-)
| type = Simulatore di volo
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/
}}[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

'''FlightGear Flight Simulator''' (semplicemente '''FlightGear''' o con il diminutivo '''FGFS''') è un sofisticato, libero, e completamente open-source framework per i simulatori di volo, creato da volontari. FlightGear è rilasciato sotto i termini della licenza [[GNU General Public License]]. FlightGear è in massima parte scritto nel linguaggio di programmazione C++.

Ogni anno dal 1996 sono state rilasciate versioni sempre più dettagliate e realistiche di FlightGear.

L'ultima versione rilasciata al pubblico è disponibile come download libero quì [http://www.flightgear.org/download/ flightgear.org/download/], con pacchetti ed eseguibili di facile installazione per vari sistemi operativi che includono Microsoft Windows, Mac OS X e GNU/Linux.

== Storia ==
{{main article|Storia di FlightGear}}

Lo sviluppo di FlightGear é iniziato come una proposta fatta in rete nel 1996, utilizzando codice grafico 3D personalizzato. Dal 1997, Curtis Olson ha guidato lo sviluppo di una versione basata su [[OpenGL]]. Sin dagli inizi molte persone hanno contribuito al progetto.

FlightGear incorpora altre risorse open-source come il modello di volo LaRCsim sviluppato dalla NASA e i dati di elevazione liberamente disponibili. I primi binari funzionanti che utilizzavano OpenGL per la grafica 3D uscirono nel 1997. L'entusiamo nello sviluppare sempre nuove versioni nel corso degli anni ha progressivamente portato a rilasci sempre più stabili ed avanzati delle stesse. Dal 2001 con regolarità il team ha rilasciato nuove versioni beta e dal 2005 lo stato sempre più maturo del software ha portato a recensioni più diffuse e un'aumento in popolarità. Il 2007 ha segnato il formale abbandono della fase di sviluppo beta grazie all'uscita della versione 1.0.0, dieci anni dopo il primo rilascio di FlightGear nel 1997.
[[File:FG-A-10.jpg|thumb|270px|Cabina di pilotaggio in 3D per [[A-10]] nella verione 1.0.0 del 2008]]

Nel 2008 la versione 1.9.0 di FlightGear ha introdotto un cambiamento importante da [[PLIB]] a [[OSG]] che ha comportato la perdità di alcune caratteristiche come le nuvole e le ombre in 3D ma nel contempo ha permesso di aggiungerne altre quali le particelle portando un nuovo livello di realismo nella simulazione.

== Software ==

Il motore della simulazione di FlightGear viene denominato [[SimGear]]. Viene utilizzato sia come applicazione dall'utente finale sia come ambiente di studio e ricerca, per lo sviluppo e il perguimento di idee legate alla simulazione del volo.

Queste personalizzazioni in FlightGear sono dimostrate dall'ampia gamma di modelli e tipi di aerei disponibili che variano dagli [[:Category:Gliders|Alianti]] agli [[Helicopter|Elicotteri]] e dagli [[:Category:Airliners|Aerei di linea]] fino agli [[Military aircraft|Aerei militari]]. Questi diversi tipi di aerei sono disponibili grazie al contributo di tante persone.

In generale gli aereoplani di FlightGear utilizzano uno dei due modelli di volo [[JSBSim]] oppure [[YAsim]]. Attualmente vi è un solo motore per i terreni ed è TerraGear. Gli effetti legati al clima icludono nuvole in 3D, fulmini e orari della giornata.

=== Modelli Dinamici di Volo ===
Per [[Flight Dynamics Models]] (FDM) si intende come il volo per un aereoplano è simulato dal programma. FlightGear usa un'ampia gamma di modelli dinamici di volo alcuni scritti internamente altri importati. Ogni aereoplano deve essere programmato perchè usi uno di questi modelli. Attualmente FlightGear è l'unico simulatore grafico di volo in cui si possono usare tutti gli FDM presenti anche quelli specificamente sviluppati per lui come l'UIUC e YASim.

Le prime versioni usavano un FDM basato su [[LaRCsim]] della NASA che è poi stato sostituito da un tipo molto più flessibile.

* [[JSBSim]] - il Modello Dinamico di Volo predefinito sin dal 2000.
* [[YASim]] - un'altro FDM che usa metodi di calcolo diversi. Introdotto dalla versione 0.7.9 nel 2002.
* [[UIUC]] - sviluppato dal UIUC Applied Aerodynamics Group dell'Università dell'Illinois a Urbana-Champaign che usa anche lui LaRCsim. Essendo una volta ampiamente usato, è ad oggi incluso in maniera predefinita in FlightGear.
* FlightGear può essere configurato per usare un FDM esterno come quello di [[MATLAB]].
* Sono stati scritti altri FDM per particolari aereoplani come quelli per mongolfiere e dirigibili.

=== Dipendenze di FlightGear ===
A differenza dei titoli del software commerciale, il risultato principale del progetto è "semplicemente" il rilascio di codice sorgente. Per trasformarlo in un programma eseguibile deve essere compilato per una determinata piattaforma. Le librerie software utilizzate per creare FlightGear sono cambiate nel corso degli anni. La principale è [[SimGear]], che è il motore grafico di simulazione per FlightGear. [[TerraGear]] non è una dipendenza, ma semplicemente il nome dato al programma predefinito per i dati dei terrain in FlightGear. OpenAL è usato per i suoni e l'audio ed include il supporto per SDL già dalla versione 0.9.5. PLIB è utilizzato per routine hardware di supporto, precedentemente usato anche per il supporto dell'audio ma che è stato preso in carico da OpenAL. [[OpenGL]] è usato per le routine di grafica 3D integrata, e altri (vedi DirectX) dove l'accelerazione hardware non è supportata. [[OpenSceneGraph]] che è integrato in FlightGear. Ed infine, Simple DirectMedia Layer che è una libreria software che viene utilizzata per la compilazione. Alcune dipendenze variano a seconda della piattaforma in cui il codice sorgente viene compilato. Gli utenti di FlightGear devono compilarsi il codice sorgente da soli oppure trovare una terza persona che lo faccia per loro e rilasci un binario eseguibile, se non è già tra quelli disponibili nel progetto.

== Hardware ==
L' hardware che richiede FlightGear deve supportare l'[[OpenGL]] e l'accelerazione hardware 3D con l'hardware NVIDIA che ha un supporto migliore. Le prime versioni supportavano anche le schede 3dfx ma sono stato abbandonato visto che le richieste hardware hanno iniziato a salire.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]
== Add-ons e personalizzazioni ==
In FlightGear ci sono programmi integrati (dipendenze) con esso altri invece eseguono una funzione insieme ad esso. Alcuni di questi sono inclusi nel rilascio di FlightGear e sono spefcifici per una piattaforma ma creati all'interno del progetto mentre altri sono distribuiti in maniera indipendente ma sono ospitati dal progetto FlightGear.

Uno molto importante di questi è l'attuale interfaccia per lanciare l'eseguibile di FlightGear. Per gran parte della sua vita iniziale FlightGear poteva essere eseguito tramite l'interfaccia [[command line]]. Tuttavia, [[FlightGear Launch Control]] è stato incluso sin dalla versione 0.9.3 nel 2003. ''[[KFreeFlight]]'' è un launcher/front-end per KDE. ''FGTools'' è un launcher/front-end alternativo per Windows. ''FGKicker'' è un front-end basato su GTK+.

Altri programmi significativi includono editor e progetti per i dati relativi ai terrain. '[[Atlas]]'' è un carta/mappa di supporto a FlightGear; ''[[Kelpie Flight Planner]]''

Other significant programs include editors and projects for terrain data. ''[[Atlas]]'' is a chart/map support for FlightGear; ''[[Kelpie Flight Planner]]'' permette di pianificare i voli con FlightGear ed è basato su Java. Infine, ''[[WorldEditor]]'' é un editor per le piste e le vie di rullagio degli aereoporti.

=== Aereoplani ===
{{Main article|Table of models}}

Inizialmente FlightGear aveva un aereplano un Navion che era incluso nel progetto LaRCsim della NASA per poi sostituirlo nel 2000 con un Cessna 172. Lo sviluppo di UIUC e JSBsim ha permesso di avere molti più aerei così come lo sviluppo di YASim che é diventato l'FDM principale di FlightGear. Dalla versione 2.12 circa 400 aereoplani con oltre 900 livree sono disponibili anche se non tutti/e sono inclusi/e nel pacchetto base.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 730]] parcheggiato nello scenario dell'aereoporto [[EHAM]]]]

=== Scenari ===
{{Main article|Scenery}}
Il progetto di FlightGears [[world scenery|Scenari mondiali]] contiene l'elevazione e i dati ambientali del mondo intero. Oggetti -come i terminal degli aereporti, mulini a vento e i ponti- sono catalogati nel [[FlightGear Scenery Database|Database degli Scenari]].

=== Networking e multi-display ===
Funzionalità di rete permettono a FlightGear di comunicare con altre istanze di FlightGear. É inoltre disponibile un protocollo [[Multiplayer Howto|multigiocatore]] per utilizzare FlightGear in una rete locale con più di un aereoplano. Questo modalità può essere usata per volare in formazine oppure come simulazione della [[ATC|Torre di controllo]]. La modalità multigiocatore é stata subito aggiornata per permettere di giocare attravero Internet. Altre caratteristiche incluse sono una mappa basata su Google maps che permette a vari giocatori di vedere gli altri partecipanti dove sono.

Diverse istanze di FlightGear possono essere sincronizzate così da creare un ambiente multi-monitor. E se tutte le istanze riescono a girare alla stezza frequenza e possibile ottenere una buona e stretta sincronizzazione frà i vari display.

== FlightGear codice sorgente contro binari ==
A differenza del software commerciale, le date di rilascio del progetto si applicano solo al codice sorgente e non ai binari del programma. Per creare un programma eseguibile il codice sorgente deve essere compilato il che richiede parecchie librerie specifiche, altre più generiche ad in alcuni casi librerie specifiche per la piattaforma. Comunque, dato che la compilazione del codice binario è un'operazione molto impegnativa per il semplice utilizzatore, ci sono altri collaboratori che si impegnano a rendere disponibili i binari per i vari sistemi operativi e le relative piattaforme. Per esempio alcuni vecchi binari funzionano con Mac OS 9 ma le nuove versioni richiedono versioni specifiche di Mac OS X.

Per esempio alla fine del 2012 l'ultima versione del codice rilasciato era la 2.10 (pre-release) e 2.8.0 (finale). Generalmente i binari dell'ultima versione rilasciata sono disponibili per tutte le piattaforme più diffuse. [http://www.flightgear.org/download/main-program/ Cliccka quì per aprire la pagina del download]

I binari per altre architetture come IRIX non sono più supportate, anche se le versioni pre-1.0 possono ancora funzionare e si trovano [http://gitorious.org/fg/ nel repository git del codice sorgente].

==Applicazioni ed usi==
{{Main article|Professional and educational FlightGear users}}
FlightGear é usato in un ampia gamma di progetti di studio, industriali (compreso la NASA) e in cabine di pilotaggio costruite in casa.

== Recensioni ==
{{Main article|FlightGear Reviews}}

== Collegamenti ==
{{Main article|Links}}
* [http://www.flightgear.org Sito Web Ufficiale]
* [http://forum.flightgear.org/ Forums di discussione]
* [http://code.google.com/p/flightgear-bugs/ Bug tracker]

{{Appendix|all|
* {{cite web |url=http://www.flightgear.org/proposal-3.0.1 |title=Original FlightGear Proposal |last=Murr |first=David L. |date=11 September, 1998 }}
* {{cite web |url=http://en.wikipedia.org/wiki/FlightGear |title=FlightGear |publisher=Wikipedia }}
}}

[[Category:FlightGear| ]]

[[de:FlightGear]]
[[en:FlightGear]]
[[es:FlightGear]]
[[fr:FlightGear]]
[[nl:FlightGear]]
[[pl:FlightGear]]
[[pt:FlightGear]]

Es/FlightGear

2015-01-06T22:00:32Z

CaptB:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] in 0.9.9
| developedby = FlightGear Developers & Contributors
| initialrelease = July 17, 1997
| lastrelease = 1.9.1
| writtenin = C++
| os = 32-bit Windows, Linux, Mac OS X, FreeBSD, Solaris or IRIX
| platform = Cross-platform
| developmentstatus = Active (1996-)
| type = Flight simulator
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/
}}

[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

'''FlightGear Simulador de vuelo''' (a menudo acortado como '''FlightGear''' , '''FGFS''' o '''FG''') creado por voluntarios es un marco de trabajo de simulación de vuelo, libre, sofisticado, de código completamente abierto.

El proyecto empezó tiempo atrás en 1996, con su primera publicación en 1997. La más reciente versión pública 1.9.1 es de Diciembre del 2008, con específicas arquitecturas para una variedad de sistemas operativos incluido Microsoft Windows (Win 32), Mac OS X, GNU/Linux, IRIX, and Solaris.

FlightGear es publicado bajo los términos de [[GNU General Public License]]. FlightGear está principalmente escrito en C++ con algunos lenguajes de programación en C.

== Historia ==
=== Comienzos (1996-1997) ===
El desarrollo formal comienza a finales de 1990 con una propuesta en línea y código escrito en 1996, pero usando código de gráficos 3D personalizado. El desarrollo de una versión basada en [[OpenGL]] fué encabezada por Curtis Olsen comenzando en 1997, trás la salida inicial en el 1996. Una extensa respuesta de la comunidad ha guiado muchas contribuciones para el proyecto desde su comienzo en los pasados '90s hasta el presente.

Lejos de empezar enteramente de la nada. Los desarrolladores de FlightGear hicieron uso del modelo de vuelo LaRCsim de la NASA, con OpenGL para el código de graficos 3D, y datos de elevación libremente disponibles. Los primeros trabajos binarios salieron en 1997, progresivamente más estable y con programas más avanzados, resultado de una intensa actualización de nuevas versiones durante años.

=== Versiones 0.7–0.9 (2001–2003) ===
En 2001, el equipo publicó regularmente nuevas versiones beta (0.7.x, 0.8.0, en los años 2001-2003) y con 0.9.xx (2003-2006). A finales de la década, el ritmo de las publicaciones finales públicas se ralentizó, pero con gran cantidad de contenido (0.9.10, 1.0.0 etc.). La madurez del software en 2005 comenzó a extender las críticas y a incrementarse la polularidad.

=== Version 0.9.0-0.9.11 (2002-2007) ===
El uso de los numeros de versión se ralentizó drásticamente a finales del 2002 después de la publicación de la versión 0.9.0. Versiones 0.9.9 (2005) y 0.9.10 (2006) contaron con ocho [[aircraft/es|aeronaves]] totalmente nuevas o rehechas sumandose a un total de 70-90 aeronaves. FlightGear 0.9.10 ganó el premio Softpedia "Pick" award (5 estrellas de 5 posibles) el 3 de Junio de 2006 tambien se llevó el premio de Softpedia "100% Limpio".

Entre escenas estaba la publicación 0.9.11-pre1 que terminó siendo remplazada por FlightGear 1.0. La pre-versión tenia unos 33 aeronaves nuevas o rehechas.

[[File:FG-A-10.jpg|thumb|270px|3D Cockpit panel for [[A-10]] in version 1.0.0 in 2008]]

=== Versión 1.0 (2008) ===
El numero de versión marcó una transcición formal fuera del estado de desarrollo beta desde la primera publicación del software en 1997, 10 años antes.

=== Versión 1.9.0 (2008) ===
En el momento en que la versión 1.9.0 fue publicada FlightGear cambió de [[PLIB]] a [[OSG]], que causó la perdida temporal de algunas de las características como las sombras y las nubes en 3D. La buena noticia es que nuevas caracteristicas como la de particulas aporta un nuevo grado de realismo a la simulación. La mayoria de las aeronaves desarrolladas por OSG no funcionan con versiones anteriores. Los usuarios pueden elegir 230 aeronaves provistas con 1.9.0, sin embargo solo unos cuantos son incluido en el paquete básico.

=== Linea de tiempo de la publicación ===
Años y Fechas de publicación de código final construido.

{| class="vatop"
|width="500" |
{| class="wikitable"
|-
! Date
! Version
|-
|17 de Julio , 1997 || Primera publicación de código principal
|-
|23 de Septiembre, 1997 || 0.12
|-
|9 de Diciembre 1997 || 0.15
|-
|17 de Diciembre 1997 || 0.18
|-
|30 de Diciembre, 1997 || 0.19 (first binaries)
|-
|6 de Enero, 1998 || 0.22
|-
|11 de Marzo, 1998 || 0.37
|-
|8 de Abril, 1998 || 0.41
|-
|14 de Abril, 1998 || 0.42
|-
|23 de Abril, 1998 || 0.43
|-
|28 de Abril, 1998 || 0.44
|-
|7 de Mayo, 1998 || 0.45
|-
|11 de Mayo, 1998 || 0.46
|-
|18 de Mayo, 1998 || 0.47
|-
|9 de Junio, 1998 || 0.48
|-
|27 de Junio, 1998 || 0.49
|-
|13 de Julio, 1998 || 0.50
|-
|21 de Julio, 1998 || 0.51
|-
|15 de Agosto, 1998 || 0.52
|-
|2 de Septiembre, 1998 || 0.53
|-
|25 de Septiembre, 1998 || 0.54
|-
|23 de Octubre, 1998 || 0.55
|-
|23 de Noviembre, 1998 || 0.56
|-
|21 de Enero, 1999 || 0.57
|-
|10 de Febrero, 1999 || 0.58
|-
|31 de Marzo, 1999 || 0.59
|-
|26 de Mayo, 1999 || 0.6.0
|}
|width="500" |
{| class="wikitable"
! Date
! Version
|-
|21 de Junio, 1999 || 0.6.1 (Stable)
|-
|rowspan=2 | 11 de Septiembre, 1999 || 0.7.0 (Development)
|-
|0.6.2 (Stable)
|-
|22 de Octubre, 1999 || 0.7.1 (Development)
|-
|17 de Febrero, 2000 || 0.7.2 (Development)
|-
|18 de Mayo, 2000 || 0.7.3 (Development)
|-
|20 de July, 2000 || 0.7.4
|-
|18 de Septiembre, 2000 || 0.7.5
|-
|19 de Diciembre, 2000 || 0.7.6
|-
|20 de Junio, 2001 || 0.7.7
|-
|13 de Julio, 2001 || 0.7.8
|-
|16 de Febrero, 2002 || 0.7.9
|-
|20 de Abril, 2002 || 0.7.10
|-
|7 de Septiembre, 2002 || 0.8.0
|-
|3 de Diciembre, 2002 || 0.9.0
|-
|5 de Diciembre, 2002 || 0.9.1
|-
|4 de June, 2003 || 0.9.2
|-
|24 de Octubre, 2003 || 0.9.3
|-
|26 de Marzo, 2004 || 0.9.4
|-
|29 de Julio 29, 2004 || 0.9.5
|-
|12 de Octubre, 2004 || 0.9.6
|-
|18 de Enero, 2005 || 0.9.8
|-
|17 de Noviembre, 2005 || 0.9.9
|-
|5 Abril, 2006 || 0.9.10
|-
|Mayo, 2007 || 0.9.11-pre1
|-
|17 de Diciembre, 2007 || 1.0.0
|-
|22 de Diciembre, 2008 || 1.9.0 (latest final build)
|}
|}

== Software ==
El motor de simulación en FlightGear es llamado [[SimGear]]. Este es usado tanto como por usuarios finales, en entornos académicos y de investigación para el desaróllo y prosecución de ideas de simulación de vuelo.

Esta personalización de FlightGear está ilustrada por un amplio rango de modelos de aeronaves que estan disponibles en FlightGear, desde [[:Category:Gliders|Planeadores]] hasta [[Helicopter]]os, y desde [[:Category:Airliners|aviones de aerolínea]] hasta [[Military aircraft|jets de combate]]. Estos modelos de aeronave han sido contribución de mucha gente diferente.

La aeronaves de FlightGear usan unos de los tres modelos principales de datos JSBSim, YAsim, o UIUC desde la version 0.9.10. En la actualidad solo un modelo de motor de terreno es usado, TerraGear. Los efectos de metereología incluyen nubes 3D , efectos de relámpagos, y hora del día.

=== Modelos Dinámicos de Vuelo ===
[[Flight Dynamics Models]] (FDM) Es como el programa simula el vuelo de una aeronave. FlightGear usa una variedad de proyectos de modelos de vuelo internamente escritos. Toda aeronave ha de ser programada para usar estos modelos. En la actualidad FlightGear es el único simulador de vuelo gráfico que es usado por todos los modelos dinámicos de vuelo, UIUC y YASim fueron desarrollados específicamente para FlightGear.

La versión temprana usaba un FDM de la NASA basado en [[LaRCsim]], el cual fue reemplazado por un FDM más flexible.

* [[JSBSim]] - desde el 2000 el software de Modelos Dinámicos de Vuelo por defecto.
* [[YASim]] - otro FDM que usa un metodo de calculo diferente. Se introdujo en 2002 comenzando en 0.7.9.
* [[UIUC]] - otro FDM incluido, desarrollado por el UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign, también hace uso de LaRCsim.
* FlightGear también puede ser configurado para rendir usando entradas de fuentes FDM externas, como así desde Matlab.
* Han sido escritos otros FDM personalizados para aeronaves específicas, como aquellas aeronaves que sean más ligeras que el aire.

=== Dependencias FlightGear ===
A diferencia de los títulos de software comercial, el resultado principal del proyecto es simplemente el lanzamiento de una colección de código. Para convertirlo en un programa útil debe ser compilado para una plataforma determinada. Las bibliotecas de software utilizadas para crear FlightGear han variado con el tiempo. La principal es [[SimGear]], que es el motor de simulación subyacente de FlightGear. [[TerraGear]] no es una dependencia, sino simplemente un nombre para el programa predeterminado de datos de terreno en FlightGear. OpenAL se utiliza para el software de sonido/audio, incluyendo soporte para SDL (desde 0.9.5). PLIB se utiliza para las rutinas de soporte de hardware, anteriormente utilizada para el soporte de sonido, que también se hizo cargo de OpenAL. [[OpenGL]] se utiliza para sus rutinas de gráficos 3D integrados, aceleración de hardware y otros (es decir, DirectX) no es compatible. [[OpenSceneGraph]] también está integrado en FlightGear. Por último, Simple DirectMedia Layer es una librería de software que se utiliza para la compilación. Algunas de las dependencias varían dependiendo de la plataforma en la el código está siendo compilado. Los usuarios de FlightGear deben compilar el código ellos mismos, o encontrar a un tercero para lanzar un binario, si no se encuentra entre los disponibles del proyecto.

== Hardware ==
El hardware necesario para FlightGear está ligado a las máquinas que soportan [[OpenGL]] y aceleración de hardware 3D, con el hardware de NVIDIA tiene mejor soporte. Las primeras versiones tenían soporte para las tarjetas 3dfx, aunque esta se redujo a medida que se incrementan los requisitos de hardware.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]

== Complementos y personalizaciones ==
Hay programas que están o integrados en FlightGear (dependencias) o realizan una función con la misma. Algunos de estos se incluyen en la versión de FlightGear para una plataforma específica, pero hechas para el proyecto, mientras que otros son distribuidos de forma independiente, pero son recibidos por el proyecto FlightGear.

Un software adicional importante es la actual interfaz para el lanzamiento de un archivo ejecutable de FlightGear. En sus primeros años de vida FlightGear se ha ejecutado sólo a través de interfaces de [[command line|linea de comandos]]. Sin embargo, el FlightGear Launch Control ha sido incluido en el ''[[FG launcher]]'' desde 0.9.3 en 2003. ''[[KFreeFlight]]'' es un lanzador de aplicaciones para usuario de KDE. ''FGTools''es un lanzador de ventanas alternativa para el usuario. ''FGKicker''es un frente basado en GTK+.

Otros programas importantes son los editores y proyectos para el terreno de datos. ''[[Atlas]]'' es un soporte de cartas/mapas de FlightGear; ''[[Kelpie Flight Planner]]'' es un planificador de vuelo basado en Java para FlightGear. ''[[FlightGear Scenery Designer]]'' es un editor de escenarios FlightGear para trabajar con datos sobre el terreno. El ''[[World Custom Scenery Project]]'' es un proyecto que coordina esfuerzos en escenarios personalizados. Por último, ''[[TaxiDraw]]'' es un editor para pistas de aterrizaje y calles de rodaje.

=== Aeronaves ===
{{Main article|Table of models}}

FlightGear comenzó con un avión incluido en LaRCsim de la NASA, un Navion, que fue sustituido por un Cessna 172 en el año 2000. UIUC, así como el desarrollo JSBSim trajo varios aviones más con ellos, al igual que el desarrollo de Yasim se han convertido en los FDM principales utilizados en FG. Desde la versión 1.9.0 más de 230 aeronaves son proporcionadas.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] atracado en [[EHAM]] ]]

=== Escenarios ===
{{Main article|Scenery}}
El proyecto de [[world scenery|escenario mundial]] de FlightGear contiene datos de elevación y terreno del mundo entero. Objetos como terminales, molinos y puentes, se recogen en la [[FlightGear Scenery Database|Base de Datos de Escenarios]]

=== Red y Multi-visualización ===

Varias opciones de red permiten a FlightGear comunicarse con otras instancias de FlightGear. Un protocolo [[Multiplayer Howto|multijugador]] está disponible para el uso de FlightGear en una red local en un entorno de múltiples aviones. Esto podría ser utilizado para vuelo en formación o simulación de [[ATC|control aéreo]]. Multijugador se amplió pronto para permitir jugar a través de Internet. Otras características incluyen los mapas de Google basado en movimiento que permite a los usuarios observar donde están los otros jugadores.

Varios instancias de FlightGear se pueden sincronizar para permitir un entorno multi-monitor. Si todas las instancias están funcionando a la misma velocidad constante, es posible obtener una buena estrecha sincronización entre las pantallas.

== FlightGear código vs binarios ==
A diferencia de la mayoría del software comercial, las fechas de lanzamiento del proyecto sólo se aplican a una liberación de código, no a un programa ejecutable. Para crear un programa ejecutable el código debe ser compilado, se requieren varias librerías específicas, entre ellas algunas generales y, en algunos casos algunos específicas a la plataforma. Sin embargo, ya que es bastante difícil para la mayoría de los usuarios, otros colaboradores trabajarán para hacer binarios disponibles para cada plataforma específica y sistema operativo. Estos paquetes varían en su estabilidad, rendimiento, dependencias, y en como se actualizan con el código base. Por ejemplo, algunos binarios antiguos funcionan en Mac OS 9, pero las versiones más recientes requieren específicas versiones de Mac OS X.

Por ejemplo, a finales de 2007, la última versión de código era 0.9.11-pre1 (versión preliminar) y 0.9.10 (final). Sin embargo, los binarios disponibles actuales pueden variar significativamente. Ejemplos de archivos binarios reales disponibles un año después del lanzamiento de la versión 0.9.10 del código:

* Win-32 tiene ~ 138 Mb de paquetes (v0.9.10) (Para Windows 98, 2000, ME, XP de 32 bits)
* Los paquetes de Linux pre-construido para las diferentes distribuciones Linux
** Paquete de Slackware (v0.9.10), los paquetes de Fedora Core 2,3,4 (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9)
* Los paquetes de Solaris, ya sea para que funcione en cualquiera de los procesadores SPARC y x86.
** SPARC (v0.9.8), 86 (v0.9.9)
* Silicon Graphics IRIX
** SGI binarios para (v0.9.9)
* Mac OS X
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)
* FreeBSD tiene un paquete para(v0.9.10)

== Comentarios FlightGear ==
{{Main article|FlightGear Reviews}}

== Enlaces externos ==
* [http://www.flightgear.org Official website]
* [http://fgfs.i-net.hu/ Community website]
* [http://gallery.flightgear.org.uk/ Development screenshots]

== Fuentes ==
* [http://en.wikipedia.org/wiki/FlightGear Wikipedia]

[[Category:FlightGear]]

[[de:FlightGear]]
[[en:FlightGear]]
[[fr:FlightGear]]
[[it:FlightGear]]
[[nl:FlightGear]]
[[pt:FlightGear]]
[[pl:FlightGear]]

Fr/FlightGear

2015-01-06T21:59:25Z

CaptB:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] in 0.9.9
| developedby = FlightGear Developers & Contributors
| initialrelease = July 17, 1997
| latestrelease = 3.2 (October 15, 2014)
| writtenin = C++
| os = 32-bit Windows, Linux, Mac OS X, FreeBSD, Solaris or IRIX
| platform = Cross-platform
| developmentstatus = Active (1996-)
| type = Flight simulator
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/
}}[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

'''FlightGear''' ( Souvent nommé '''Flightgear''' ou '''FGFS''') est un simulateur de vol sophistiqué, libre, et créé par des volontaires. FlightGear est distribué sous les termes de la [[GNU General Public License]]. Le logiciel est principalement codé en C++.

Des versions de plus en plus détaillées et réalistes sont distribuées depuis le début du projet, en 1996, et dorénavant tous les six mois.

La dernière version en date est disponible à l'adresse [http://www.flightgear.org/download/ flightgear.org/download/], fonctionnelle sur nombre de systèmes d'exploitation dont Microsoft Windows, Mac OS X, Linux, IRIX, et Solaris.

== Histoire ==
{{main article|FlightGear History}}

Le développement de flightgear commença par un échange sur internet en 1996, contenant un code inédit de graphiques 3D. Le développement d'une version basée sur [[OpenGL]] fut menée par Curtis Olson dès 1997. Nombre de volontaires ont contribués au projet, depuis.

FlightGear associe d'autres ressources libres, comme plusieurs modèles de vol dont JSBsim, ainsi que certaines données de paysages, concues par la NASA et disponibles gratuitement. les premières librairies fontionnelles utilisant l'Opengl pour la 3D furent réalisées en 1997. Un développement fulgurant et professionnel de nouvelles versions pendant plusieurs années fut à l'origine de la sophistication du logiciel. Depuis 2001, L'équipe Flightgear sort de nouvelles versions "beta" régulièrement, et dès 2005, la qualité du software conduit à des critiques plus appliquées, et plus sérieuses, accompagnée par une popularité grandissante. L'année 2007 marque une symbolique sortie du développement secondaire avec la distribution de la version 1.0.0 , 10 ans après la première version en 1997.

[[File:FG-A-10.jpg|thumb|270px|3D Cockpit panel for [[A-10]] in version 1.0.0 in 2008]]

En 2008, la version 1.9.0 de FlightGear introduit un majeur changement de [[PLIB]] à [[OSG]], qui causa temporairement la perte de fonctionalités comme les nuages 3D ou les ombres, tandis que les nouvelles, comme les particules, impacte sur le degré de réalisme de la simulation.

== Software ==

Le moteur de simulation dans FlightGear est appelé [[SimGear]]. Il est utile à la fois pour l'utilisateur normal et dans les milieux universitaires et de recherche, pour le developpement et la recherche d'idées sur la simulation de vol.

La flexibité de FlightGear est illustrée par la grande quantité d'appareils, qui y sont disponibles: Nous pouvons compter plusieurs catégories, dont: [[:Category:Gliders|glider]]s,[[Helicopter]]s, [[:Category:Airliners|airliners]],[[Military aircraft|fighter jets]]. Ces modèles ont été créés par des développeurs différents.

Les aéronefs de Flightgear utilisent un au moins des trois modèles de vols JSBSim, YAsim, ou UIUC depuis la version 0.9.10. Pour l'instant seulement un seul moteur de simulation est utilisé, TerraGear. Les effects météo (cf.[[Weather]]) sont très complexes et réalistes, de même que les effects visuels qui y sont liés: nuages 3D, effects lumineux, effects d'horizon, et heure de la journée.

=== Flight Dynamics Models, alias...FDM ===

Le modèle de vol [[Flight Dynamics Models]] ou (FDM) ) simule le comportement de l'avion dans une situation précise. FlightGear utilise beaucoup de scripts et de FDM codés de manière interne au programme .
Tout aéronef ''doit'' être programmé pour obéir à un de ces modèles de vol. Actuellement FlightGear est le seul simulateur utilisant autant de FDMs, et dont au moins trois sont créés de manière spécifique pour le logiciel.
Les plus anciennes versions utilisaient [[LaRCsim]], FDM créé par la NASA, mais il fut remplacé par des modèles plus flexibles.

* [[JSBSim]] - Depuis 2000, le FDM par défaut de flightgear.
* [[YASim]] - Autre FDM utilisant une approche différente. Fait partie de la version 0.7.9 en 2002.
* [[UIUC]] - Autre FDM inclut, developpé par le ''UIUC Applied Aerodynamics Group'' à l' Université de l'Illinois à Urbana-Champaign, également partit de LaRCsim.
* FlightGear peut aussi être configuré pour utiliser des entrées de FDM externes, comme [[MATLAB]].
* D'autres FDM marginaux pour un aéronef spécifique ont été écrits, comme les appareils volants "plus légers que l'air", tel le Zeppelin, ballon contenu dans la version de base de flightgear.

=== FlightGear dependencies ===

Contrairement à certains titres commerciaux, le but principal du projet est la sortie d'un code source. Pour le rendre utile, il faut le compiler sur une quelconque système d'exploitation. Les librairies utilisées par flightgear ont changées au cours du temps, et des versions. la principale est [[SimGear]], qui est le moteur de simulation necessaire à flightgear. Dans le cas de [[TerraGear]], il ne s'agit pas de secteur de dépendance, mais seulement d'un nom pour le programme de ''données de terrain'' dans le simulateur. OpenAL est utilisée pour le son d'entrée/sortie, dont un support pour SDL (depuis 0.9.5). PLIB est utilisé pour le support matériel (driver), anciennement utilisé par le pilote son, actuellement repris par OpenAl. [[OpenGL]] est utilisé pour ses routines graphiques intégrées, et il est bon de savoir que d'autres accélérations matérielles (directX) ne sont pas prises en charge. [[OpenSceneGraph]] est aussi intégré dans FlightGear. Enfin, Simple DirectMedia Layer est une logitèque qui est utilisée pour compiler. certains de ces secteurs de dépendances varient, la plateforme utilisée faisant la différence. Les utilisateurs de FlightGear doivent à la fois compiler le code eux-même, ou trouver un tiers pour distribuer un fichier binaire.

== Hardware ==

Le matériel nécessaire pour faire tourner FlightGear est relativement faible, bien qu'il faut savoir que les cartes graphiques les plus compatibles sont de la série Nvidia . Les premières versions du simulateur avaient le support des cartes 3dfx, bien que la proportion de rencontrer ce genre de cartes a chutée de la même manière que la configuration matérielle moyenne s'est accrue.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]

== Add-ons et tuning ==

Certains programmes sont soit intégrés dans flightgear ("dependencies"),soit font une action, une opération à travers lui. Quelque uns sont intégrés dans la distribution populaire du simulateur (pour une plateforme spécifique,quelques fois) mais créées pour le projet, quand d'autres sont étrangers à Flightgear bien que supportés par la communauté.

Un logiciel important est l'interface destinée à lancer FlightGear. A ses débuts, FlightGear ne pouvait se lancer que par l'interface DOS ([[command line]]). Cependant, ''the FlightGear Launch Control'' fut inclus dans le FGrun (''[[FG launcher]]'') depuis la version 0.9.3 en 2003. ''[[KFreeFlight]]'' est un "launcher/front-end" pour KDE. ''FGTools'' est une fenêtre alternative de lancement. ''FGKicker'' est une front-end basée GTK+ .

D'autres projets très utiles contiennent des éditeurs de données de terrain. ''[[Atlas]]'' est un support de cartes aéronautiques pour FlightGear; ''[[Kelpie Flight Planner]]'' est un plannificateur de vol Java pour FlightGear. ''[[FlightGear Scenery Designer]]'' est un éditeur de scènes. Le ''[[World Custom Scenery Project]]'' est un projet destiné à coordiner tous les efforts effectués sur les scènes et les données de terrain. Enfin, ''[[TaxiDraw]]'' est un éditeur de pistes et taxiway, permettant un meilleur confort visuel.

=== Aéronefs ===
{{Main article|Table of models}}

FlightGear commença avec un avion inclut dans le FDM LaRCsim, le Navion, qui fut remplacé par un Cessna 170 en 2000. Le développement des trois FDM, en particulier YASim, apporta son lot de nouveaux avions: Plus de 350 aéronefs et 450 livrées uniques, sont disponibles pour la version 2.0.0, alors que seulement quelques uns sont inclus dans le package de base.
[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] docked in the [[EHAM]] scenery]]

=== Scènes ===
{{Main article|Scenery}}
Le monde de FlightGears ([[world scenery]]) couvre des données d'élévation et de terrain du monde entier. Les moulins à vents, les ponts et autres objets sont présents dans la base de données ([[FlightGear Scenery Database|Scenery Database]]) .
Vous pouvez téléchargez le monde entier sur le site officiel de flightgear, indiqué plus haut.

=== Mise en réseau et multi-écrans ===

Plusieurs options de réseaux permettent une communication entre flightgear et ses instances. Un serveur multijoueurs ([[Multiplayer Howto|multiplayer]]) fut disponible pour utiliser FlightGear sur un réseau local dans un environnement à plusieurs aéronefs. Il peut être usé pour les vols en formation, ou la simulation de l' [[ATC|control tower]]. Le Multijoueurs fut bientôt élargit pour permettre aux joueurs de voler sur Internet. D'autres fonctionalitées comme la carte Google Map permettant de connaître la position de chaque avions dans flightgear existent.
Plusieurs instances de FlightGear peuvent être synchronisées pour permettre un environnement multi-moniteur. Si toutes ces instances fonctionnent aux mêmes Frames per second, il est possible d'obtenir une bonne synchronisation agréable, et réaliste.

== FlightGear code vs. binaries ==

Les dates de la sortie du logiciel consiste à la distribution du code, et nond'un executable. Pour créer un programme efficace, il faut le compiler, ce qui requiert certaines logithèques, dont certaines sont générales, tandis que d'autres sont spécifiques au système. En revanche, puisque la tâche demande nombre de compétences informatiques pour la plupart des utilisateurs grand public, d'autres contributeurs travailleront à rendre les binaires disponibles pour une plate-forme spécifique. Les performances, dépendent de la date de la mise à jour du code. Par exemple, certains travaux plus anciens binaires marchent sur Mac OS 9, mais les nouvelles versions nécessitent certaines versions du Mac OS.

Par exemple, fin 2007, la dernière version du code était 0.9.11-pre1 (pre-release) et 0.9.10 (final). Toutefois, la date de distribution des fichiers binaires réels varient considérablement. Des exemples de binaires réels disponibles un an après la sortie de la version 0.9.10 du code:

* Win-32 has ~138 Mb package (v0.9.10) (For Windows 98, 2000, ME, 32-bit XP)
* Linux- pre-built packages for specific Linux distributions
** Slackware package (v0.9.10), Fedora Core 2,3,4 packages (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9)
* Solaris packages either for it running on either SPARC or x86 processors.
** SPARC (v0.9.8), x86 (v0.9.9)
* Silicon Graphics IRIX
** SGI binaries for (v0.9.9)
* Mac OS X
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)
* FreeBSD has a package for(v0.9.10)

==Applications et usages==
{{Main article|Professional and educational FlightGear users}}
FlightGear a été utilisé dans une série de projets dans le milieu universitaire et de l'industrie (y compris la NASA) ainsi que dans des simulateurs "maison".

== Reviews ==
{{Main article|FlightGear Reviews}}

== liens externes ==
{{Main article|Links}}
* [http://www.flightgear.org Official website]
* [http://fgfs.i-net.hu/ Community website]

{{Appendix|all|
* {{cite web |url=http://www.flightgear.org/proposal-3.0.1 |title=Original FlightGear Proposal |last=Murr |first=David L. |date=11 September, 1998 }}
* {{cite web |url=http://en.wikipedia.org/wiki/FlightGear |title=FlightGear |publisher=Wikipedia }}
}}

[[de:FlightGear]]
[[en:FlightGear]]
[[es:FlightGear]]
[[it:FlightGear]]
[[nl:FlightGear]]
[[pt:FlightGear]]
[[pl:FlightGear]]

[[Category:FlightGear| ]]

De/FlightGear

2015-01-06T21:57:15Z

CaptB:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] in 0.9.9
| developedby = FlightGear Entwickler & Mitwirkende
| initialrelease = 17. Juli, 1997
| latestrelease = 3.2 (15. October 2014)
| writtenin = C++
| os = 32-bit Windows, Linux, Mac OS X, FreeBSD, Solaris oder IRIX
| platform = Plattformübergreifend
| developmentstatus = Aktiv (1996-)
| type = Flugsimulator
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/
}}

[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

Der '''FlightGear Flight Simulator''' (oft mit '''FlightGear''' oder '''FGFS''' abgekürzt) ist ein ausgereifter, anspruchsvoller, quelloffener Flugsimulator und ist ausschliesslich von Freiwilligen erschaffen. FlightGear wird unter den Bestimmungen der [[GNU General Public License]] veröffentlicht. Er ist hauptsächlich in der Programmiersprache C++ geschrieben.

Seit dem Projektstart im Jahre 1996 werden jedes Jahr noch detailliertere und realistischere Versionen veröffentlicht.

Die neueste Veröffentlichung kann kostenlos unter [http://www.flightgear.org/Downloads/ http://www.flightgear.org/Downloads/] heruntergeladen werden, dazu gehören vorgefertigte Versionen für eine Reihe von Betriebssystemen, darunter Microsoft Windows (Win 32), Mac OS X, Linux, IRIX und Solaris.

== Geschichte ==

Siehe auch: Hauptartikel Geschichte von FlightGear (engl.)
{{main article|FlightGear History}}

Die Entwicklung von FlightGear begann im Jahre 1996 mit einem Vorhaben, einen Flugsimulator durch die Mitarbeit einer Internet-Gemeinschaft von Grund auf neu zu erschaffen. Angeführt von Curtis Olsen begann dann 1997 die Ausarbeitung einer OpenGL-basierten Version. Von Anbeginn an steuerten viele Leute dem Projekt bei.

FlightGear schloss andere Open-Source-Ressourcen wie das Flugdynamikmodell LaRCsim der NASA und öffentlich erhältliche Höhendaten mit ein. Die ersten funktionierenden ausführbaren Dateien, die OpenGL als Grafikcode benutzten, kamen 1997 heraus. Durch enthusiastische Arbeit entstanden in den folgenden Jahren stabilere und fortgeschrittene Versionen. Seit 2001 veröffentlichte das Team regelmässig neue Betaversionen, seit 2005 sorgt die Reife des Programms für ein immer grösseres und breiteres Publikum. 2007 fand mit der Version 1.0.0 der formale Austritt aus dem Betastadium statt, zehn Jahre nach der ersten Veröffentlichung von FlightGear.

[[File:FG-A-10.jpg|thumb|270px|3D-Cockpit einer [[A-10]], Version 1.0.0, 2008]]

Version 1.9.0, herausgekommen im Jahr 2008, beinhaltete eine grosse Veränderung: Duch den Wechsel von [[PLIB]] zu [[OSG]] gingen zeitweilig einige
Features wie 3D-Wolken und Schatten verloren, während andere, z.B. Partikel, die Simulation noch realistischer machten.

== Software ==

Die Simulationsengine von FlightGear, also die Funktionseinheit, die die komplexen Berechnungen der Simulation durchführt, heisst [[SimGear]]. Sie wird sowohl als Endbenutzerapplikation als auch im akademischen Umfeld und zur Forschung verwendet, um Ideen im Bereich Flugsimulation realisieren zu können.
An der grossen Breite unterschiedlichster Fluggeräte, die von [[:Category:Gliders|Segelflieger]]n über [[Helicopter|Helikopter]] bis hin zu [[:Category:Airliners|Verkehrflugzeugen]] und [[Military aircraft|Kampfjets]] reicht, lässt sich die Anpassungsfähigkeit von FlightGear ermessen. Diese Modelle wurden und werden von vielen unterschiedlichen Freiwilligen beigesteuert.

Die Fluggeräte benutzen eine der drei primären Datenmodelle: JSBSim, YASim oder, ab Version 0.9.10, UIUC. Als Geländeengine wird zur Zeit TerraGear verwendet. Zu den Wettereffekten gehören 3D-Wolken, Beleuchtungseffekte und Tageszeit.

=== Flugdynamikmodell ===

Das [[Flight Dynamics Models|Flugdynamikmodell]] (FDM) bestimmt, wie die Flugeigenschaften eines Flugzeuges vom Programm simuliert werden. FlightGear benutzt eine Vielfalt von internen und importierten Flugmodellprojekten. Jedwedes Fluggerät muss für eines dieser Modelle programmiert werden. Zur Zeit ist FlightGear der einzige grafische Flugsimulator, der alle FDMs benutzt, wobei UIUC und YASim speziell für FlightGear entwickelt wurden.

Frühere Versionen benutzten ein FDM, das auf dem NASA-Modell [[LaRCsim]] basierte; dieses wurde aber später durch flexiblere ersetzt.

* [[JSBSim]] - Die voreingestellte FDM-Software seit dem Jahr 2000.
* [[YASim]] - ein weiteres FDM, das andere Berechnungsmethoden verwendet. Eingeführt 2002 mit Version 0.7.9.
* [[UIUC]] - entwickelt von der UIUC Applied Aerodynamics Group an der Universität von Illinois in Urbana-Champaign; benutzt auch LaRCsim.
* FlightGear kann auch so eingestellt werden, dass es den Input externer Datenquellen wie z.B. Matlab verwenden kann.
* Ebenso wurden FDMs für sehr spezielle Flieger wie etwa Gasballons oder Zeppeline geschrieben.

=== Abhängigkeiten von FlightGear ===

Anders als kommerzielle Softwaretitel ist das Hauptergebnis des FGFS-Projektes eine Ansammlung von Softwarecode. Um sie in ein nutzbares Programm zu verwandeln, muss sie für eine bestimmte Plattform kompiliert werden. Dazu werden Softwarebibliotheken, sogenannte Libraries gebraucht. Mit der Zeit hat FlightGear unterschiedliche Libraries verwendet. Die wichtigste hierbei ist [[SimGear]], das die zugrundeliegende Simulationseinheit darstellt. [[TerraGear]] gehört nicht zu den Abhängigkeiten, sondern ist einfach der Name des hauptsächlich benutztem Geländedatenprogramms. OpenAL wird als Audio-/Sound-Software verwendet, seit Version 0.9.5 auch mit Unterstützung für SDL. Vorher sorgte PLIB als Audio-/Sound-Software, dient aber nun nur noch als Unterstützung für Hardwareroutinen. [[OpenGL]] wird wegen seiner integrierten 3D-Grafikroutinen verwendet; andere Hardwarebeschleunigung (namentlich DirectX) wird nicht unterstützt. [[OpenSceneGraph]] ist ebenso in FlightGear integriert. Zuguterletzt wird der sogenannte Simple DirectMedia Layer als Softwarebibliothek beim Kompilieren benutzt. Einige der Abhängigkeiten variieren je nach Plattform, auf der kompiliert wird. Benutzer von FlightGear können den Code entweder selbst kompilieren, oder eines der für viele Plattformen bereits erhältlichen vorkompilierten ausführbaren Programme nutzen.

== Hardware ==

Die Hardware, die für FlightGear benötigt wird, braucht auf jeden Fall Unterstützung für [[OpenGL]] und 3D-Hardwarebeschleunigung, wobei sich NVIDIA als bessere Lösung herausgestellt hat. Frühere Versionen unterstützten auch 3dfx-Grafikkarten, mit immer höheren Hardwareanforderungen wurde die Unterstützung allerdings eingestellt.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]

== Erweiterungen und persönliche Anpassung ==

Es gibt Programme, die entweder ''IN'' FlightGear integriert arbeiten (Abhängigkeiten), oder solche, die ''MIT'' FlightGear arbeiten. Einige der Programme sind schon in den Veröffentlichungen des Projektes für spezifische Plattformen enthalten, andere werden unabhängig zur Verfügung gestellt, aber vom FGFS-Projekt beherbergt.
Zu den bedeutenden Zusatzprogrammen gehören solche, die es dem Benutzer erlauben, FlightGear mit Hilfe einer grafischen Oberfläche (Frontend), und nicht mit Hilfe einer [[command line|Kommandozeile]] zu starten. Die ''FlightGear Launch Control'' mit der ''[[FG launcher]]''-Oberfläche wurde 2003 mit Version 0.9.3 eingeführt. ''[[KFreeFlight]]'' ist ebensolch ein Frontend für die UNIX-Arbeitsumgebung KDE, ''FGTools'' eine Alternative unter Windows und der ''FGKicker'' ein auf GTK+ basierendes Startprogramm.

Zu den anderen signifikanten Programmen gehören Editoren und Projekte für Geländedaten. ''[[Atlas]]'' z.B. ist eine sich bewegende Landkarte, der ''[[Kelpie Flight Planner]]'' ein Java-basierter Flugroutenplaner für FlightGear. ''[[FlightGear Scenery Designer]]'' arbeitet mit Geländedaten und kann zum editieren der FlightGear-Szenerie benutzt werden. Das ''[[World Custom Scenery Project]]'' ist ein Projekt, das die Arbeit an der Verfeinerung der Szenerie koordiniert; Mit ''[[TaxiDraw]]'' kann man Startbahnen und Rollfelder von Flughäfen bearbeiten.

=== Flugzeuge etc. ===

Siehe auch Hauptartikel: Liste der Modelle (engl.)
{{Main article|Table of models}}

FlightGear begann mit einem Flugzeug namens Navion mit dem NASA-Flugdynamikmodell LaRCSim; Die Navion wurde im Jahr 2000 von der Cessna 172 abgelöst. Die Weiterentwicklung sowohl von UIUC wie auch von JSBSim brachte mehrere Flugzeuge mit sich, genauso wie die Entwicklung von YASim, das mittlerweile das Haupt-FDM von FlightGear darstellt. Von den über 230 Fluggeräten, die für Version 1.9.0 erhältlich sind, ist nur eine Auswahl im Basispaket enthalten.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] docked in the [[EHAM]] scenery]]
=== Szenerie ===

Siehe auch Hauptartikel: Szenerie (engl.)
{{Main article|Scenery}}

Das ''[[world scenery|FlightGear World Scenery Project]]'' beinhaltet Höhen- und Landschaftsdaten der gesamten Erde. Objekte wie Flughafenterminals, Windmühlen oder Brücken sind in der [[FlightGear Scenery Database|Scenerie-Datenbank]] zusammengefasst.

=== Netzwerk und Multidisplay ===

Etliche Netzwerkoptionen erlauben es den verschiedenen Instanzen von FlightGear untereinander zu kommunizieren. Ein [[Multiplayer Howto|Mehrspieler]]-Protokoll steht zur Verfügung, um FlightGear in einem lokalen Netzwerk mit mehrern Flugzeugen zu betreiben, was man zum Formationsflug oder zur Simulation eines [[ATC|Kontrollturmss]] nutzen kann. Schnell entwickelte sich die Mehrspieler-Option dazu, FlightGear auch über das Internet spielen zu können. Ein weiteres Feature ist die Möglichkeit, auf einer Google-Maps basierten Karte zu beobachten, wo sich die anderen FG-Flieger gerade befinden.
Mehrere Instanzen von FlightGear können so synchronisiert werden, dass mehrere Bildschirme gleichzeitig benutz werden können. Laufen alle Instanzen beständig mit der gleichen Frequenz, ist eine gute und akkurate Synchronization der Bildschirme möglich.

== FlightGear-Code oder Binärdatei? ==

Der Grossteil kommerzieller Software ist als ausführbare Dateien, also als sogenannte Binaries oder Executables, erhältlich. Das FlightGear-Projekt veröffentlicht im Gegensatz dazu an den jeweiligen Erscheinungsdaten nur den zugrundeliegenden Code. Um ein lauffähiges Programm daraus zu schaffen, muss dieser Code kompiliert werden; Dazu werden mehrere spezielle Softwarebibliotheken benötigt, davon sind einige generell, andere spezifisch nötig, je nach Plattform und Betriebssystem. Da für die breite Masse diese Prozedur zu schwierig ist, werden von den FGFS-Mitwirkenden verschiedene plattform- und betriebssystem-spezifisch vorkompilierte Binaries zur Verfügnug gestellt. Diese können sich hinsichtlich ihrer Stabilität, Leistung, Abhängigkeiten und Aktualität unterscheiden. Zum Beispiel laufen einige ältere Binaries auf Mac OS 9, für Mac OS X werden allerdings neuere Versionen benötigt.

Als Ende 2007 der zu der Zeit neueste Code unter der Bezeichnung 0.9.11-pre1 (Vorveröffentlichung) und 0.9.10 (endgültige Veröffentlichung) herauskam, variierten die dazugehörigen Binaries stark untereinander. Hier einige Beispiele:

* Win-32 - als Paket mit 138 Mb (v0.9.10) (für Windows 98, 2000, ME, 32-bit XP)
* Linux- pre-built-Paket für spezifische Linux-Distributionen
** Slackware-Paket (v0.9.10), Fedora Core 2,3,4 Pakete (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9)
* Solaris-Pakete entweder für SPARC- oder x86-Prozessoren.
** SPARC (v0.9.8), x86 (v0.9.9)
* Silicon Graphics IRIX
** SGI Binaries für (v0.9.9)
* Mac OS X
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)
* FreeBSD-Paket für (v0.9.10)

== FlightGear-Rezensionen ==

Siehe auch Hauptartikel FlightGear-Rezensionen (engl.)
{{Main article|FlightGear Reviews}}

== Externe Links ==
{{Main article|Links}}
* [http://www.flightgear.org Offizielle Website]
* [http://fgfs.i-net.hu/ Community Website]
* [http://www.caballerosaguila.shialeweb.com/ Club Website] (Spanish)
* [http://gallery.flightgear.org.uk/ Screenshots der Entwicklerversion]

== Quellen ==
* [http://www.flightgear.org/proposal-3.0.1 Original Flight Gear Proposal] by David L. Murr (Revision 3.0.1)
* [http://en.wikipedia.org/wiki/FlightGear Wikipedia]

[[Category:FlightGear|FlightGear]]

[[en:FlightGear]]
[[es:FlightGear]]
[[it:FlightGear]]
[[nl:FlightGear]]
[[pl:FlightGear]]

Pl/FlightGear

2015-01-06T21:16:04Z

CaptB: Initial version

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] w 0.9.9
| OpracowanePrzez = Developerzy FlightGear i współtwórcy
| PierwszeWydanie = Lipec 17, 1997
| ObecnaWersja = 3.2.0
| NapisaneW = C++
| SystemyOperacyjne = 32-bit Windows, Linux, Mac OS X, FreeBSD, Solaris lub IRIX
| platforma = wieloplatformowy
| developmentstatus = Aktywny (1996-)
| typ = Symulator Lotu
| licencja = [[GNU General Public License]]
| strona = http://www.flightgear.org/
}}

[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

'''FlightGear Flight Simulator''' (w skrócie '''FlightGear''' lub '''FGFS''') to stowrzona przez ochotników wyrafinowana i darmowa platforma symulacji lotu na lincencji open source. FlightGear jest wydany na zasadach licencji [[GNU General Public License]] i jest on w większości napisany przy użyciu języka programowania C++.

Coraz bardziej szczegółowe i zaawansowane wersje FlightGear są wydawane corocznie od zapoczątkowania projektu w 1996 roku.

Najnowsze publiczne wydanie jest dostępne do pobrania na [http://www.flightgear.org/Downloads/ http://www.flightgear.org/Downloads/] wraz z właściwymu wersjami dla Microsoft Windows (Win 32), Mac OS X, Linux, IRIX, i Solaris.

== Historia ==
{{main article|FlightGear History}}

Rozwój FlightGear rozpoczął się od propozycji w 1996 roku, w oparciu o własny kodu 3D. Rozwój wersji opartej na [[OpenGL]] rozpoczął w 1997 roku Curtis Olson. Wiele innych osób miało wkład w project od jego zapoczątkowania.

FlightGear włączył w projekt inne operogramowanie oparte na licencji open source, włączając w to model lotu NASA - LaRCsim jak również darmowy Numeryczny Model Terenu (DEM) Pierwsze wydanie binarne z kodem 3D opartym na OpenGL zostało udostępnione w 1997 roku.

[[File:FG-A-10.jpg|thumb|270px|Kokpit 3D Cockpit [[A-10]] w wersji 1.0.0 rok 2008]]

W 2008 roku wersja 1.9.0 FlightGear przeszła z biblioteki [[PLIB]] na [[OSG]] co spowodowało tymczasową utratę niektórych funkcji programu, takich jak wyświetlanie chmury 3D i cienie, za to nowo wprowadzone funkcje programu wprowadziły symulacje na nowy poziom realizmu.

== Program ==

Silnik symulacji we FlightGear to [[SimGear]]. Jest on używany zarówno jako aplikacja użytkownika końcowego jak i przy pracach badawczych w środowiskach akademickich w celu rozwoju zagadnień związanych z symulacją lotu.

Przykładem na możliwość zdolnośc dostosowywania FlightGear jest szeroki wachlarz modeli dostępnych statków powietrznych, od [[:Category:Gliders|glider]] do [[Helicopter]], przez [[:Category:Airliners|airliners]] do [[Military aircraft|fighter jets]]. Modele te zostałe wykonane i dodane do projektu przez wielu ochchotników ze społecznośći FlightGear.

Od wersji 0.9.10 statki powietrzne we FlightGear używaja jednego z trzech Modeli Danych Lotu (FDM), są to JSBSim, YAsim lub UIUC. Obecnie wyłącznie jeden silnik terenu jest w użyciu, jest to TerraGear. Dostępne efekty pogodowe to między innymi chmury 3D, efekty świetlne, pory dnia i nocy.

=== Modele Dynamiki Lotu ===
[[Flight Dynamics Models]] (FDM) odpowiada za to w jaki sposób w programie jest symulowany lot statku powietrznego. FlightGear korzysta z własnych oraz zewnętrznych projektów Modeli Dynamiki Lotu. Każdy statek powietrzny musi być tak zaprogramowany aby korzystać z jednego z dostępnych modeli dynamiki lotu. Obecnie FlightGear jest jedynym graficznym symulatorem lotu korzystającym ze wszystkich wspomnianych Modeli dynamiki Lotu, a UIUC and YASim zostały rozwinięte z myślą i w szczególności dla FlightGear.

Wczesne wersje programu używały FDM opartym na [[:aRCsim]] od NASA. który w kolejnych wersjach został zastąpiony przez bardziej elastyczne FDM

* [[JSBSim]] - Domyślny Model Dynamiki Lotu od 2000 roku.
* [[YASim]] - Inny FDM, używający odmiennych metod obliczeniowych. Wprowadzony od wersji 0.7.9 w 2002 roku.
* [[UIUC]] - Kolejny FDM, rozwinięty przez UIUC Applied Aerodynamics Group z Uniwersytetu w Illinois na Urbana-Champaign, jako podstawę użyty został LaRCsim.
* FlightGear może być tak skonfigurowany aby przyjmować dane z zewnętrznych źródeł FDM takich jak MatLab.
* Inne FDM zostały rozwinięte dla szczgólnych przypadków statków lotniczych takich jak balony i sterowce.

=== Zależności FlightGear ===

W przeciwieństwie do komercyjnych tytułów, głównym wynikim pracy projektu jest wydanie zestawu kodów źródłowych. Aby użyć programu należy skompulować udostępniony kod dla docelowej platfory na której ma pracować. Biblioteky użyte przez FlightGear były różne w zalężności od okresu. Główną biblioteką zależną jest [[SimGear]] która jest silnikiem symulacji dla FlightGear. [[TerraGear]] nie jest zależnością a raczej tylko nazwą dla domyślnego silnika odpowiadającego za generowanie terenu we FlightGear. OpenAL jest używany dla obsługi dzwięku, włączając wsparcie dla SDL ( od wrsji 0.9.5 ). PLIB jest użyte do obsługi sprzętowej, przed wprowadzeniem OpenAL także dla obsługo dzwięku. [[OpenGL]] jest użyty dla swoich funkcji 3D, DirectX nie jest wspierany. [[OpenSceneGraph]] jest również zintegrowany we FlightGear. Na koniec do kompilacji jest konieczna biblioteka Simple Direct Media Layer (SDL) Niektóre zależności mogą się różnić w zależności id tego na jaką platformę docelową jest kompilowany kod. Użytkownicy FlightGear powinni sami kompilować kod, lub jeżeli nie jest ona dostępna w ramach projektu, korzystać z wersji binarnej udostępnionej przez osoby trzecie.

== Sprzęt==

Sprzęt konieczny do uruchomienia FlightGear jest ograniczony do sprzętu który wspiera [[OpenGL]] i akceleracje 3D, przy czym najlepej wspierana jest NVIDIA. Wczesne wersje posiadały wsparcie dla kart 3dfx, jednak wsparcie to zostało wycofane wraz z zwiększającymi sie wymaganiami sprzętowymi.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]
== dodatki i dostosowywanie ==

Oprogramowanie może być zintegrowane z FlightGear poprzez zależności lub jest zewnętrzne współdziałające z nim. Oprogramowanie to może być cześcią projektu FlightGear, lub takie które jest rozwijane niezależnie ale udostępniane przez projekt FlightGear.

Ważnym dodatkowym oprogramowaniem jest interfejs graficzny służący do wykonania pliku startowego FlightGear. We wczesnych wersjach FlightGear był wykonywany jedynie poprzez [[comman line]], jednak w 2003 roku od wersji 0.9.3 FlightGear Launch Control został załączony z Front-Endem ""[[FG Launcher]]"".
Podobnym rolę spełnia ''[[KFreeFlight]]'' dla środowiska KDE. ''FGTools'' jest alternatywnym front-endem dla środowiska Windows. ''FGKicker'' jest używany dla GTK+.

Inne ważne oprogramowanie to edytory i projekty dla anych terenu. ''[[Atlas]]'' pozwala na wspieranie map we Flightear; ''[[Kelpie Flight Planner]]'' to rozwijane w Javie narzędzie do planowania lotów.
''[[FlightGear Scenery Designer]]'' to edytor scenerii pomocny przy pracy z anymi terenu. Project ''[[World Custom Scenery Project]]'' to projekt pomagający koordynować wspólne wysiłki na rzecz tworzenia scenerii. Na koniec edytor ''[[TaxiDraw]]'' do tworzenia nowych pasów startowych i dróg kołowania.

=== Statki Powietrzne ===
{{Main article|Table of models}}

Na początku FlightGear dysponował tylko jednym statkiem powietrznym, był to Navion zawarty w projekcie LaRCsim od NASA, który w 2000 roku został zastąpiony przez Cessne 172. Wprowadzenie i rozwój UIUC jak też JSBSim jak również poźniejsze wprowadzienie YAsim, ktory został głównym FDM projektu FlightGear zaowocowało wprowadzeniem do projektu kilka dodatkowych statków powietrznych. W projekcie 1.9.0 jest dostępnych ponad 230 statków powietrznych, jednak tylko część jest zawarta w głównej dystrybucji.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] zaparkowany w scenerii [[EHAM]] ]]

=== Sceneria ===
{{Main article|Scenery}}

Projekt [[WorldScenery]] dla FlightGear zawiera dane o wysokosci i klasie terenu całego świata.
Objekty takie jak terminale, wiatraki i mosty są zebrane w [[FlightGear Scenery Database|Scenery Database]].

=== Sieć i wiele monitorów ===

Istnieje kilka możliwośći które pozwalają kounikować się FlightGear z inna isnatncją FlightGear. Dostępny jest protokół [[Multiplayer Howto|multiplayer]] co umożliwia lot w formacji lub symulowanie kontroli ruchu lotniczego w sieci lokalnej. Protokół Multiplayer został wkrótce tak rozbudowany aby także pozwalał na pracę w internecie. Dodatkową cechą możłiwości sieciowych jest opcja podglądu innych graczy na mapach google.

Kilka instancji FlightGEar mogą zostać tak zsynchronizowane aby korzystać z wielu monitorów. Możliwe jest uzyskanie bardzo dobrej synchronizacji między monitorami jeżeli wszystkie instancje FlightGear będą pracować z tą samą częstotliwością wyświetlania klatek.

== Kod FlightGear vs wersja binarna ==

W przeciwieństwie do komercyjnego oprogramowania, data wydania dotyczy wyłącznie kodu źródłowego a nie do wersji binarnej. Aby stworzyć wykonywalny program, kod źródłowy musi zostać skompilowany, co wymaga kilku bibliotek, włączając w to kilka ogólnych oraz szczególnych dla poszczególnych platform, jednak
jest zbyt trudne zadanie dla wielu zwykłych użytkowników dlatego ochotnicy społeczności pracują aby udostępnić wersje binarne dla poszczególnych platform i systemów operacyjnych. Dystrybucje te różnią się poziomem stabilności, wydajnością, zależnościami a także tym jak aktualne one są w stosunku do kodu źródłowego. Dla przykładu, niektóre ze starszych wersji binarnych pracują poprawnie pod Mac OS9 ale nowsze wersje wymagają szczególnych wersji Mac OS X.

Inny przykład, najnowsza wersja kodu w 2007 roku to 0.9.11-pre1 (pre-release ) i 0.9.10 (finalna) Jednak dostępne wersje binarne znacznie się różniły. Otot kilka przykładów dostępnych wersji binarnych rok po udostępnieniu kodu 0.9.10:

* Win-32 pakiet ~138MB (v0.9.10) Dla Windows 98, 2000, ME, 32 bitowe XP )
* Linux - pakiety dla poszczególnych dystrybucji
** Pakiet Slackware (v0.9.10), Fedora Core 2,3,4 packages (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9)
* Pakiet Solaris packages dla SPARC lub procesorów x86.
** SPARC (v0.9.8), x86 (v0.9.9)
* Silicon Graphics IRIX
** Wersja binarna SGI binaries (v0.9.9)
* Mac OS X
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)
* Pakiet FreeBSD (v0.9.10)

== Recenzje FlightGear ==
{{Main article|FlightGear Reviews}}

== Łącza zewnętrzne ==
{{Main article|Links}}
* [http://www.flightgear.org Official website]
* [http://fgfs.i-net.hu/ Community website]
* [http://www.caballerosaguila.shialeweb.com/ Club website] (Spanish)
* [http://gallery.flightgear.org.uk/ Development screenshots]

== Źródłą ==
* [http://www.flightgear.org/proposal-3.0.1 Original Flight Gear Proposal] by David L. Murr (Revision 3.0.1)
* [http://en.wikipedia.org/wiki/FlightGear Wikipedia]

[[de:FlightGear]]
[[es:FlightGear]]
[[nl:FlightGear]]
[[pt:FlightGear]]
[[pl:FlightGear]]

FlightGear

2015-01-06T15:54:36Z

CaptB:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] in 0.9.9
| developedby = FlightGear Developers & Contributors
| initialrelease = July 17, 1997
| latestrelease = 3.2 (October 15, 2014)
| writtenin = C++
| os = Windows, Linux, Mac OS X, FreeBSD, Solaris or IRIX
| platform = Cross-platform
| developmentstatus = Active (1996-)
| type = Flight simulator
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/
}}[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]

'''FlightGear Flight Simulator''' (often shortened to '''FlightGear''' or '''FGFS''') is a sophisticated, free, and completely open-source flight simulator framework, created by volunteers. FlightGear is released under the terms of the [[GNU General Public License]]. FlightGear is mostly written in the C++ programming language.

Increasingly detailed and realistic versions of FlightGear have been released every year since the project was started in 1996.

The latest public release is available as a free download at [http://www.flightgear.org/download/ flightgear.org/download/], with easy to install packages for a variety of operating systems including Microsoft Windows, Mac OS X, and Linux.

== History ==
{{main article|FlightGear History}}

FlightGear development started with an online proposal in 1996, using custom 3D graphics code. Development of an [[OpenGL]] based version was spearheaded by Curtis Olson starting in 1997. Many people have contributed to the project in the years since its inception.

FlightGear incorporated other open-source resources, including the LaRCsim flight model from NASA, and freely available elevation data. The first working binaries, using OpenGL for 3D graphic code, came out in 1997. Enthusiastic development of newer versions for several years resulted in progressively more stable and advanced versions. By 2001, the team was releasing new beta versions regularly, and by 2005, the maturity of software lead to more widespread reviews, and increased popularity. 2007 marked a formal transition out of beta development with the release of version 1.0.0, ten years after FlightGear's first release in 1997.

[[File:FG-A-10.jpg|thumb|270px|3D Cockpit panel for [[A-10]] in version 1.0.0 in 2008]]

In 2008, version 1.9.0 of FlightGear included a major change from [[PLIB]] to [[OSG]], which caused the temporarily loss of some features like 3D clouds and shadows, while newly added features, such as particles, imparted another degree of realism to the simulation.

== Software ==

The simulation engine in FlightGear is called [[SimGear]]. It is used both as an end-user application and in academic and research environments, for the development and pursuit of flight simulation ideas.

This customizability of FlightGear is illustrated by the wide range of aircraft models that are available in FlightGear, from [[:Category:Gliders|glider]]s to [[Helicopter]]s, and from [[:Category:Airliners|airliners]] to [[Military aircraft|fighter jets]]. These aircraft models have been contributed by many different people.

The FlightGear aircraft in general use one of two main flight data models [[JSBSim]] and [[YAsim]]. Currently only one terrain engine is used, TerraGear. Weather effects include 3D clouds, lighting effects, and time of day.

=== Flight Dynamics Models ===
[[Flight Dynamics Models]] (FDM) are how the flight for an aircraft is simulated in the program. FlightGear uses a variety of internally written and imported flight model projects. Any aircraft must be programmed to use one of these models. Currently FlightGear is the only flight graphical flight simulator all the FDM are used for, and UIUC and YASim were developed specifically for FlightGear.

Early version used a FDM based on [[LaRCsim]] by NASA, which was replaced with more flexible FDM.

* [[JSBSim]] - the default flight dynamics model software since 2000.
* [[YASim]] - another FDM using different calculation method. Introduced starting in 0.7.9 in 2002.
* [[UIUC]] - developed by the UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign, also made use of LaRCsim. Once being widely used, it is nowadays longer included in FlightGear by default.
* FlightGear can also be setup to render using inputs from an external FDM source, such as from [[MATLAB]].
* Other custom FDM for a specific aircraft type have been written, such as for lighter than air aircraft.

=== FlightGear dependencies ===
Unlike commercial software titles, the main output of the project is simply the release of a collection of code. To turn it into a usable program it must be compiled for a given platform. The software libraries used to create FlightGear have varied over time. The main one is [[SimGear]], which is the underlying sim engine for FlightGear. [[TerraGear]] is not a dependency, but simply a name for the default terrain data program in FlightGear. OpenAL is used for sound/audio software, including support for SDL (since 0.9.5). PLIB is used for hardware support routines, formerly used for sound support also which was taken over by OpenAL. [[OpenGL]] is used for its integrated 3D graphics routines, and other hardware acceleration (namely DirectX) is not supported. [[OpenSceneGraph]] is also integrated into FlightGear. Finally, Simple DirectMedia Layer is a software library which is used for compiling. Some of the dependencies vary depending on which platform the code is being compiled for. FlightGear users must either compile the code themselves, or find a third party to release a binary, if it is not among the ones available from the project.

== Hardware ==
Hardware needed for FlightGear is narrow to machines that support [[OpenGL]] and 3D hardware acceleration, with NVIDIA hardware having better support. Early versions had support for 3dfx cards, though this dropped as hardware requirements increased.

[[File:Fgrun-page2.jpg|thumb|left|270px|The [[FlightGear Launch Control|FlightGear Launcher]]]]
== Add-ons and customization ==
There are programs that are either integrated into FlightGear (dependencies) or perform a function with it. Some of these are included in the release of FlightGear for a specific platform but made by the project, while others are independently distributed but are hosted by the FlightGear project.

One major additional software is the actual interface for launching an executable of FlightGear. For most of its early life FlightGear was only run through [[command line]] interfaces. However, [[FlightGear Launch Control]] has been included since 0.9.3 in 2003. ''[[KFreeFlight]]'' is a launcher/front-end for KDE. ''FGTools'' is an alternative windows launcher front-end. ''FGKicker'' is a GTK+ based front-end.

Other significant programs include editors and projects for terrain data. ''[[Atlas]]'' is a chart/map support for FlightGear; ''[[Kelpie Flight Planner]]'' is a Java based flight planner for FlightGear. Finally, ''[[WorldEditor]]'' is an editor for airport runways and taxiways.

=== Aircraft ===
{{Main article|Table of models}}

FlightGear started out with an aircraft included in NASA's LaRCsim, a Navion, which was replaced by a Cessna 172 by 2000. UIUC as well as JSBsim development brought several more aircraft with them, as did the development of YASim which have since become the main FDM used in FG. Over 400 aircraft in more than 900 unique liveries, are available for version 2.12, although only a few are included in the base package.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] docked in the [[EHAM]] scenery]]

=== Scenery ===
{{Main article|Scenery}}
FlightGears [[world scenery]] project contains elevation and landclass data of the enitre world. Objects -like terminals, windmills and bridges- are collected in the [[FlightGear Scenery Database|Scenery Database]].

=== Networking and multi-display ===
Several networking options allow FlightGear to communicate with other instances of FlightGear. A [[Multiplayer Howto|multiplayer]] protocol is available for using FlightGear on a local network in a multi aircraft environment. This could be used for formation flight or [[ATC|control tower]] simulation. Multiplayer was soon expanded to allow playing over the internet. Other features include a Google maps based moving up that allows users to observe where other players are.

Several instances of FlightGear can be synchronized to allow for a multi-monitor environment. If all instances are running at the same frame rate consistently, it is possible to get good and tight synchronization between displays.

== FlightGear code vs. binaries ==
Unlike most commercial software, the project release dates only apply to a release of code, not an executable program. To create a runnable program the code must be compiled, which requires several specific libraries, including some general ones and, in some cases some platform specific ones. However, since this too difficult for most mainstream users, other contributors will work to make binaries available for a specific platform and operating system. These packages vary in their stability, performance, dependencies, and how up to date they are with the code base. For example, some older binaries work on Mac OS 9 but newer releases require specific Mac OS X versions.

For example, by late 2012 the latest code release was 2.10 (pre-release) and 2.8.0 (final). Binaries are generally available for the last final code release on all major platforms. [http://www.flightgear.org/download/main-program/ Click here to proceed to the flightgear binaries download page]

Binaries for other platforms such as IRIX are no longer supported, although pre-1.0 releases may work and can be found in the [http://gitorious.org/fg/ git source code repo].

==Applications and usages==
{{Main article|Professional and educational FlightGear users}}
FlightGear has been used and is being used in a wide range of projects in academia, industry (including NASA) and home-built cockpits.

== Reviews ==
{{Main article|FlightGear Reviews}}

== External links ==
{{Main article|Links}}
* [http://www.flightgear.org Official website]
* [http://forum.flightgear.org/ Forums]
* [http://code.google.com/p/flightgear-bugs/ Bug tracker]

{{Appendix|all|
* {{cite web |url=http://www.flightgear.org/proposal-3.0.1 |title=Original FlightGear Proposal |last=Murr |first=David L. |date=11 September, 1998 }}
* {{cite web |url=http://en.wikipedia.org/wiki/FlightGear |title=FlightGear |publisher=Wikipedia }}
}}

[[Category:FlightGear| ]]

[[de:FlightGear]]
[[es:FlightGear]]
[[fr:FlightGear]]
[[it:FlightGear]]
[[nl:FlightGear]]
[[pl:FlightGear]]
[[pt:FlightGear]]

Pl/FlightGear Wiki

2015-01-06T15:38:22Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Liczba artykułów i statystyka oglądalności.]]
'''FlightGear Wiki''' jest oficjalnym wiki dla [[FlightGear]]. Powstał on w 2006 roku i obecnie zawiera szeroki zakres tematów dotyczących [[FlightGear]]. Zawiera stworzoną przez ochotników treść na licencji [[GPL]] dotyczącą rozwoju i użytkowania FlightGear oraz pokrewnych projektów, jak też ogólnych informacji dotyczących lotnictwa i [[:category:Software|oprogramowania]].

Główne dojścia do artykułów to portale [[pl/Portal:User|użytkownik]] i [[pl/Portal:Developer|developer]].

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

Pl/FlightGear Wiki

2015-01-06T15:36:41Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Liczba artykułów i statystyka oglądalności.]]
'''FlightGear Wiki''' jest oficjalnym wiki dla [[FlightGear]]. Powstał on w 2006 roku i obecnie zawiera szeroki zakres tematów dotyczących [[FlightGear]]. Zawiera stworzona przez ochotników treść na licencji [[GPL]] dotyczącą rozwoju i użytkowania FlightGear oraz spokrewnionych projektów, jak też ogólnych informacji dotyczących lotnictwa i [[:category:Software|oprogramowania]].

Główne dojścia do artykułów to portale [[pl/Portal:User|użytkownik]] i [[pl/Portal:Developer|developer]].

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

Pl/FlightGear Wiki

2015-01-06T15:36:10Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Liczba artykułów is statystyka oglądalności.]]
'''FlightGear Wiki''' jest oficjalnym wiki dla [[FlightGear]]. Powstał on w 2006 roku i obecnie zawiera szeroki zakres tematów dotyczących [[FlightGear]]. Zawiera stworzona przez ochotników treść na licencji [[GPL]] dotyczącą rozwoju i użytkowania FlightGear oraz spokrewnionych projektów, jak też ogólnych informacji dotyczących lotnictwa i [[:category:Software|oprogramowania]].

Główne dojścia do artykułów to portale [[pl/Portal:User|użytkownik]] i [[pl/Portal:Developer|developer]].

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

Sr/FlightGear Wiki

2015-01-06T15:34:29Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Broj stranica i statistika pregleda.]]
'''FlightGear Wiki''' je zvanični Wiki za [[FlightGear]].Pokrenut 2006. godine ,trenutno obuhvata širok spektar tema vezanih za [[FlightGear]] . Sastoji se od [[GPL]] licenciranih dokumenata ,pisanih od strane volontera ,a koji se odnose na [[FlightGear]] i njemu srodne projekte ,kao i opšte informacije koje se odnose na avijaciju i [[:category:Software|Software]].

Glavne stranice su [[En/Portal:User|Korisnik]] i [[Sr/Portal|Razvoj]] portali.

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[en:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]

Sr/FlightGear Wiki

2015-01-06T15:33:53Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Broj stranica i statistika pregleda.]]
'''FlightGear Wiki''' je zvanični Wiki za [[FlightGear]].Pokrenut 2006. godine ,trenutno obuhvata širok spektar tema vezanih za [[FlightGear]] . Sastoji se od [[GPL]] licenciranih dokumenata ,pisanih od strane volontera ,a koji se odnose na [[FlightGear]] i njemu srodne projekte ,kao i opšte informacije koje se odnose na avijaciju i [[:category:Software|Software]].

Glavne stranice su [[En/Portal:User|Korisnik]] i [[Sr/Portal:Razvoj]] portali.

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[en:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]

De/FlightGear Wiki

2015-01-06T15:32:44Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Article number and pageview statistics.]]
Das '''FlightGear Wiki''' ist das offiziele Wiki für [[FlightGear]]. Das Wiki wurde erstmals 2006 veröffentlich und deckt mittlerweile viele Bereiche und Themen von [[FlightGear]] ab. Es wird von freiwilligen Helfern nach den [[GPL]]-lizensierten Unterlagen zur Entwicklung und Verwendung von [[FlightGear]] und den verbundenen Projekten gepflegt und weiter ausgebaut [[:category:Software|Software]].

Die Hauptseiten sind [[De/Portal:Benutzer|Benutzer]]- und [[Portal:Developer|Developer]]-Portale.

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[en:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

Ca/FlightGear Wiki

2015-01-06T15:31:59Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Estadístiques del nombre d'articles i visites de pàgines.]]
El '''Wiki de FlightGear''' és el wiki oficial de [[FlightGear]]. Es va iniciar el 2006 i actualment cobreix una àmplia varietat de temes relacionats amb [[FlightGear]]. Es compon de voluntaris que escriuen documents amb llicència [[GPL]] en relació amb el desenvolupament i l'ús de FlightGear i els projectes connexos, així com informació general relacionada amb l'aviació i el [[:category:Software|programari]].

Les principals portes d'entrada als articles són els portals d'[[Portal:User|usuari]] i de [[Portal:Developer|desenvolupador]].

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[de:FlightGear Wiki]]
[[en:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

Pl/FlightGear Wiki

2015-01-06T15:29:03Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Article number and pageview statistics.]]
'''FlightGear Wiki''' jest oficjalnym wiki dla [[FlightGear]]. Powstał on w 2006 roku i obecnie zawiera szeroki zakres tematów dotyczących [[FlightGear]]. Zawiera stworzona przez ochotników treść na licencji [[GPL]] dotyczącą rozwoju i użytkowania FlightGear oraz spokrewnionych projektów, jak też ogólnych informacji dotyczących lotnictwa i [[:category:Software|oprogramowania]].

Główne dojścia do artykułów to portale [[pl/Portal:User|użytkownik]] i [[pl/Portal:Developer|developer]].

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

Pl/FlightGear Wiki

2015-01-06T15:28:11Z

CaptB: Created page with "Article number and pageview statistics. '''FlightGear Wiki''' jest oficjalnym wiki dla FlightGear. Powstał on w 2006 r..."

[[File:FlightGear wiki statistics.png|thumb|270px|Article number and pageview statistics.]]
'''FlightGear Wiki''' jest oficjalnym wiki dla [[FlightGear]]. Powstał on w 2006 roku i obecnie zawiera szeroki zakres tematów dotyczących [[FlightGear]]. Zawiera stworzona przez ochotniko treść na licencji [[GPL]] dotyczącą rozwoju i użytkowania FlightGear oraz spokrewnionych projektów, jak też ogólnych informacji dotyczących lotnictwa i [[:category:Software|oprogramowania]].

Główne dojścia do artykułów to portale [[pl/Portal:User|użytkownik]] i [[pl/Portal:Developer|developer]].

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]

FlightGear Wiki

2015-01-06T15:05:40Z

CaptB:

[[File:FlightGear wiki statistics.png|thumb|270px|Article number and pageview statistics.]]
The '''FlightGear Wiki''' is the official wiki for [[FlightGear]]. It was started in 2006 and currently covers a wide range of [[FlightGear]] related topics. It consists of volunteer written [[GPL]] licensed documents relating to developing and using FlightGear and its related projects, as well general information connected to aviation and [[:category:Software|software]].

The main gateways to articles are the [[Portal:User|user]] and [[Portal:Developer|developer]] portals.

[[Category:Documentation|Wiki]]
[[Category:Community|Wiki]]
[[Category:FlightGear|Wiki]]

[[ca:FlightGear Wiki]]
[[de:FlightGear Wiki]]
[[pl:FlightGear Wiki]]
[[sr:FlightGear Wiki]]