FlightGear wiki - User contributions [en]

Blender

2016-05-22T11:42:22Z

Paul Richter: link to ac3d import/export

'''Blender''' is a open source 3D content creation suite available for all major operating systems under the [[GNU General Public License]] and available for free. <sup>[http://www.blender.org/]</sup> Many [[FlightGear]] developers use Blender, and there are a lot of articles on the FlightGear Wiki about using it.

'''Note:''' An [[Blender_AC3D_import_and_export|importer/exporter]] for FlightGear's most common 3D format (AC3D, .ac) is only included in Blender version 2.49b or older. For later versions you have to install it manually:
* [http://forum.flightgear.org/viewtopic.php?f=18&t=13442 Forum thread]
* [https://github.com/majic79/Blender-AC3D AC3D Blender plugin: Stable version (Github)]
* [https://github.com/majic79/Blender-AC3D/tree/bl-svn AC3D Blender plugin: Experimental version for Blender svn version (Github)]

== Related content ==
=== Blender related articles ===
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender]]
* [[Howto: Modeling Ground Signs with Blender]]
* Aircraft modeling tutorial (flightgear-specific)
** by Helijah: Breguet Br-761 "Deux ponts"
*** [http://helijah.free.fr/flightgear/Creation/Creation-fr.htm In French]
*** [http://helijah.free.fr/flightgear/Creation/Creation-en.htm In English]
* Aircraft modeling tutorial (non-flightgear-specific)
** by Kevin Jongen: [http://www.websitetoolbox.com/tool/post/felixdk/vpost?id=2283400 Nieuport 11] and [http://www.military-meshes.com/forums/showthread.php?t=2232 additional discussion]
** by Samo: [http://forums.cgsociety.org/showthread.php?f=91&t=252648&highlight=blender+aircraft Policarpov I-15 Chato]
** by Witold Jaworski: [http://airplanes3d.net/wm-000_e.xml E-book "Virtual Modeling" ] on P-40B. With over 3600 pictures and 1112 pages. Currently only in Polish (no English). But you can try machine translation plus the use of many pictures :-)
* Aircraft modeling video tutorial
** How to model Me163 Komet (Blender 2.64): [http://www.youtube.com/watch?feature=player_embedded&v=0et7lFsIf5E#! youtube]
** How to model an airliner (Blender 2.5): [http://www.youtube.com/watch?v=a5pva-Meu7E youtube]
** Blender 2.5 Tutorial- Introduction to Modeling in Blender: [http://www.youtube.com/watch?v=BGfJLsm54ho&feature=related youtube]
** Blender 2.59 Airplane Modeling Timelapse [http://www.youtube.com/watch?v=hC5pzvBbyQw&feature=relmfu youtube]
** Modeling an X-Wing in Blender 3D (Blender 2.4): [https://www.youtube.com/watch?v=BGfJLsm54ho&feature=related youtube]
** Blender 2.49b Reference Image Setup for Modeling workflow. [http://www.youtube.com/watch?v=SSedXO00H1c youtube] (Setting up the reference images as textured flat objects visible not only in orthographic views)

=== Also related to modeling and Blender ===
* [[GMax2AC]]
* [[Howto: Illuminate faces|Illuminate faces]]
* [[Howto: Make a helicopter|Make a helicopter]]
* [[Model Import and Export]]
* [[Modeling - FAQ]]
* [[Modeling - Getting Started]]
* [[Modeling - SketchUp]]
* [[Normals and Transparency Tutorial]]
* [[SketchUp to AC3D exporter]]

== External links ==
* [http://www.blender.org/ Official website]
* [http://wiki.blender.org/index.php/Main_Page Official wiki]
* [http://www.blender.org/download/get-blender/ Get Blender]

{{3d}}

[[Category:Modeling]]
[[Category:Software]]
[[Category:GPL software]]

Grumman Albatross

2011-11-04T06:38:37Z

Paul Richter: not attack aircraft

{{stub}}

{{infobox Aircraft
|image =Grumman_Albatross.jpg
|name =Grumman Albatross
|type =Search and Rescue Flying Boat
|authors =Detlef Faber
|fdm =YASim
|status =Development
|fgname =Albatross
|download= http://www.flightgear.org/Downloads/aircraft-2.0.0/#Albatross
}}
The '''Grumman HU-16 Albatross''' is a large twin-radial engine amphibious flying boat. Originally designated '''SA-16''', it was renamed HU-16 in 1962.

== External links ==
* [http://en.wikipedia.org/wiki/HU-16_Albatross Albatross on Wikipedia

{{Grumman}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Seaplanes and flying boats]]

Cessna T-37

2011-10-26T13:54:23Z

Paul Richter: /* Development status/Issues/Todo */ wheels and canopy (coming soon)

{{infobox Aircraft
|image = T-37-splash.png
|name = Cessna T-37
|type = Military Aircraft
|authors = Erik Hofman, Paul Richter
|fdm = JSBSim
|status = beta
|fgname = t37
}}

The '''Cessna T-37 Tweet''' is a basic jet trainer that first flew in 1954 and served in the U.S. and other air forces. It seats two in a side-by-side arrangement.

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* engine turbines do not rotate or are not visible (engine bay could be a little darker)
* no aircraft light available
* aircraft has no shadow
* no jetstream visible
* No speedbrakes available
* wheels do not spin
* canopy does not open/close

3d Cockpit:
* no cockpit light at night available
* no switches and levers available
* no elevator trim control available
* cockpit is not textured
* cockpit window has no windscreen wipers

General:

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]

Cessna T-37

2011-10-26T13:53:15Z

Paul Richter: HUD available

{{infobox Aircraft
|image = T-37-splash.png
|name = Cessna T-37
|type = Military Aircraft
|authors = Erik Hofman, Paul Richter
|fdm = JSBSim
|status = beta
|fgname = t37
}}

The '''Cessna T-37 Tweet''' is a basic jet trainer that first flew in 1954 and served in the U.S. and other air forces. It seats two in a side-by-side arrangement.

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* engine turbines do not rotate or are not visible (engine bay could be a little darker)
* no aircraft light available
* aircraft has no shadow
* no jetstream visible
* No speedbrakes available

3d Cockpit:
* no cockpit light at night available
* no switches and levers available
* no elevator trim control available
* cockpit is not textured
* cockpit window has no windscreen wipers

General:

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]

Cessna T-37

2011-10-26T13:52:48Z

Paul Richter: fgname t37 (lowercase)

{{infobox Aircraft
|image = T-37-splash.png
|name = Cessna T-37
|type = Military Aircraft
|authors = Erik Hofman, Paul Richter
|fdm = JSBSim
|status = beta
|fgname = t37
}}

The '''Cessna T-37 Tweet''' is a basic jet trainer that first flew in 1954 and served in the U.S. and other air forces. It seats two in a side-by-side arrangement.

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* engine turbines do not rotate or are not visible (engine bay could be a little darker)
* no aircraft light available
* aircraft has no shadow
* no jetstream visible
* No speedbrakes available

3d Cockpit:
* no cockpit light at night available
* no switches and levers available
* no elevator trim control available
* cockpit is not textured
* cockpit window has no windscreen wipers

General:

* no hud available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]

Howto:Animate models

2011-10-26T13:36:16Z

Paul Richter: /* Emission */ sp

The real world is full of motion. To simulate this in [[FlightGear]], '''models must be animated'''.

This document provides basic information for all kind of animations. For more complex animations, you are advised to check the available [[aircraft]] for examples.

== A note about animation order ==
{{stub}}

Animations are executed by FlightGear in the order that they are read in the model's .xml file. Therefore, it is very important to pay attention to the order, especially when multiple animations are applied to the same object(s).

== Special code parts ==
=== Axis ===
An axis part is required in every animation that involves a rotating or moving thing.

<source>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</source>

The axis are similar to the ones of the 3D model. There is a difference between rotation and translation:
* In rotation animations, the axis part defines around what axis the object rotates. Negative/positive values make the difference between counterclockwise and clockwise rotations.
* In translate animations, the part defines along what axis the object moves. If the x-axis is poiting backwards, an x-value of -1 will result in forward motion.

You could also define two points, between which FlightGear will calculate the correct axis. This makes the use of a [[#Center|<nowiki><center></nowiki>]] tag redundant! Such coordinates are extremely useful for animating control surfaces (rudder, elevators etc.).

<source>
<axis>
<x1-m> 4.9</x1-m>
<y1-m> 7.1</y1-m>
<z1-m>-1.0</z1-m>
<x2-m> 5.9</x2-m>
<y2-m>11.2</y2-m>
<z2-m>-0.5</z2-m>
</axis>
</source>

=== Center ===
Various animations ([[#Rotate|rotate]], [[#Spin|spin]]) move around a center point.

<source>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
</source>

The axis are similar to the ones of the 3D model, so finding coordinates is easily done in 3D modeling software.

=== Conditions ===
Multiple animations can make use of a conditional. Check <tt>$FGDATA/Docs/README.conditions</tt> for some more details.

* '''equals:''' property value (or second property) is equal to value/(first)property.
* '''greater-than:''' property value (or second property) is larger than value/(first)property.
* '''greater-than-equals:''' property value (or second property) is greater than or equal to value/(first)property.
* '''less-than:''' property value (or second property) is smaller than value/(first)property.
* '''less-than-equals:''' property value (or second property) is smaller than or equal to value/(first)property.

The example below is true when n1 has a value greater than 25.
<source>
<condition>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
</condition>
</source>

Then there are some special tags:

* '''and:'''
* '''not:'''
* '''or:'''

In the example below, the condition is true when either n1 is greater than 25% or equal to 0%.
<source>
<condition>
<or>
<greater-than>
<property>engines/engine[1]/n1</property>
<value>25</value>
</greater-than>
<equals>
<property>engines/engine[1]/n1</property>
<value>0</value>
</equals>
</or>
</condition>
</source>

An example of implementation into an animation looks as follows:

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>suface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<condition>
<greater-than>
<property>suface-positions/left-aileron-pos-norm</property>
<value>10</value>
</greater-than>
</condition>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

=== Interpolation ===
For non-fixed factors, an interpolation "table" can be created.

<source>
<interpolation>
<entry>
<ind> 0.0</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 0.667</ind>
<dep> 0.0</dep>
</entry>
<entry>
<ind> 1.0</ind>
<dep> 0.5</dep>
</entry>
</interpolation>
</source>

The lines above represent the following table:

{|
!Input
!Output
|-
|0.0
|0.0
|-
|0.667
|0.0
|-
|1.0
|0.5
|}

You can add as many entries as you need. Interpolation tables are often used for gear animations (eg. to open doors during gear-movements and close them again once the gear is either retracted or fully extended).

=== Name ===
With a name animation, you can group multiple objects.

<source>
<animation>
<name>Collection1</name>
<object-name>Object1</object-name>
<object-name>Object2</object-name>
<object-name>Object3</object-name>
</animation>
</source>

The example above creates a "virtual object" with the name Collection1. In animation, we can animate this group of objects, by using:

<source>
<object-name>Collection1</object-name>
</source>

=== Object-name ===
These names are set in the 3D model. Each single object has a unique name; for easy identification it is advised to use descriptive names (LeftElevator, Rudder etc.). Animations are only applied to those objects that are mentioned in an object-name line (one object per line!). Animations lacking those, will be applied to the entire model.

== Animation types ==
=== Alpha-test ===
<source>
<animation>
<type>alpha-test</type>
<object-name>Object</object-name>
<alpha-factor>0.01</alpha-factor>
</animation>
</source>

=== Billboard ===
This faces an object towards the viewer. Often used on 2D objects, like clouds, trees and lights.

<source>
<animation>
<type>billboard</type>
<object-name>Object</object-name>
<spherical type="bool">true</spherical>
</animation>
</source>

* '''spherical:'''

=== Dist-scale ===
Used to scale an object, based on the distance to the viewer.

<source>
<animation>
<type>dist-scale</type>
<object-name>Object</object-name>
<interpolation>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>300</ind>
<dep>4</dep>
</entry>
<entry>
<ind>1500</ind>
<dep>8</dep>
</entry>
</interpolation>
</animation>
</source>

=== Enable-hot ===
Scenery objects are automatically defined as solid by FlightGear, meaning that an aircraft can taxi on them and/or crash when touching. For certain objects (groundmarkings, beacon light-beams etc.) this might be an unwanted feature. The solidness can be disabled with the following animation:

<source>
<animation>
<object-name>Object</object-name>
<enable-hot type="bool">false</enable-hot>
</animation>
</source>

* '''enable-hot:''' can be either true or false. Remember that objects are automatically solid, so it should not be nesecarily to set this at all when wanting solidness.

=== Flash ===
<source>
<animation>
<type>flash</type>
<object-name>Object</object-name>
<offset>0.0</offset>
<factor>1.0</factor>
<power>2</power>
<two-sides type="bool">false</two-sides>
<min>0.0</min>
<max>1.0</max>
<center>
<x-m>0.0</x-m>
<y-m>0.0</y-m>
<z-m>0.0</z-m>
</center>
<axis>
<x>0.0</x>
<y>-1</y>
<z>0.1</z>
</axis>
</animation>
</source>

* '''offset:'''
* '''factor:'''
* '''power:'''
* '''two-sides:'''
* '''min:'''
* '''max:'''

=== Interactions ===
<source>
<animation>
<type>interaction</type>
<object-name>Object</object-name>
<interaction-type>carrier-wire</interaction-type>
</animation>
</source>

* '''interaction-type:''' can have the following values:
** '''carrier-catapult:'''
** '''carrier-wire:''' makes the object act as an arresting wire, as used on [[aircraft carrier]]s.

=== Material ===
An animation type that can be used in various ways. Of course you can combine the below mentiond systems into one (big) animation.

<source>
<animation>
<type>material</type>
<object-name>Object</object-name>
<property-base>sim/model/c172p/material</property-base>
<global type="bool">true</global>
...
lines as mentioned below
...
</animation>
</source>

'''Optional:'''
* '''property-base:''' when using prop(erties), you might want to set a property-base. All props will be relative to this path.
* '''global:''' by setting this to <tt>true</tt>, all objects using the same material as the defined object(s) (via <tt><object-name></tt>) will be affected by the animation. This is preferred to listing several objects in <object-name> tags. It's not only faster, but also doesn't break animations by forcing objects together.

'''Notes:'''
* Numbers are clamped to 0.0-1.0, except "shininess", which is clamped to 0-128.
* By appending <tt>-prop</tt> each of the material properties can read its value from another property.

==== Ambient ====
<source>
<ambient>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</ambient>
</source>

==== Diffuse ====
<source>
<diffuse>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</diffuse>
</source>

==== Emission ====
{{Main article|Howto: Illuminate faces}}
<source>
<emission>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
<factor-prop>controls/lighting/panel-norm</factor-prop>
</emission>
</source>

Emission colors are multiplied by the factor-prop value. 1 is maximum color intensity, while 0 is the minimum. Colors are calculated according to the [http://en.wikipedia.org/wiki/RGB_color_model RGB color model].

==== Shininess ====
Shininess is clamped to 0-128.
<source>
<shininess>105</shininess>
</source>

==== Specular ====
<source>
<specular>
<red>1.0</red>
<green>0.2</green>
<blue>0.0</blue>
</specular>
</source>

==== Texture ====
Used for the [[Livery over MP]] system.

<source>
<property-base>sim/model/livery</property-base>
<texture-prop>engine</texture-prop>
<texture>KLM.png</texture>
</source>

==== Transparency ====
<source>
<transparency>
<alpha-prop>rotors/tail/rpm</alpha-prop>
<factor>-0.0015</factor>
<offset>1</offset>
</transparency>
</source>

==== Threshold ====
<source>
<threshold>0.001</threshold>
</source>

=== Noshadow ===
<source>
<animation>
<type>noshadow</type>
<object-name>Object</object-name>
</animation>
</source>

=== Pick ===
{{Main article|Howto: Make a clickable panel#Pick}}

=== Range ===
To prevent objects -like instruments- being drawn when the aircraft is actually too far away for them to be seen anyway, a range animation is used.

<source>
<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</source>

* '''min-m:''' the shortest distance (in meters) from the object center at which it is visible.
* '''max-m:''' the largest distance (in meters) from the object center at which it is visible.

You could also use the generic level of detail (LOD) properties, which can be set by the user through View > Adjust LOD rangers:
* <tt>/sim/rendering/static-lod/bare</tt> distance at which only a rough exterior model is required.
* <tt>/sim/rendering/static-lod/rough</tt> distance at which most should be visible.
* <tt>/sim/rendering/static-lod/detailed</tt> distance at which all details should be visible.

The animation code will look like this:
<source>
<animation>
<type>range</type>
<min-m>0</min-m>
<max-property>sim/rendering/static-lod/bare</max-property>
</animation>
</source>

You can have both ranges (max and min) bound to a property, or just one of them.
* '''min-property:'''
* '''max-property:'''

=== Rotate ===
One of the most important and frequently used animations of all. It rotates an object to an absolute position in degrees, as provided by the property-value.

<source>
<animation>
<object-name>Object</object-name>
<type>rotate</type>
<property>suface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.

=== Scale ===
A scale animation scales (resizes) an object. This can be either property-value dependant (first example) or a fixed scale (second example).

<source>
<animation>
<type>scale</type>
<object-name>Object</object-name>
<property>sim/time/sun-angle-rad</property>
<x-min>1.0</x-min>
<y-min>1.0</y-min>
<z-min>1.0</z-min>
<x-factor>1.4</x-factor>
<y-factor>1.4</y-factor>
<z-factor>2.0</z-factor>
</animation>
</source>

* ?-min: the mimimum scale factor for each axis. If the property value would result in a smaller factor than this setting, the scale animation will hold.
* ?-factor: the scale factor for each axis (factor*property=scale factor).

<source>
<animation>
<type>scale</type>
<x-offset>0.5</x-offset>
<y-offset>0.5</y-offset>
<z-offset>0.5</z-offset>
</animation>
</source>

* x.offset: the scale factor.

=== Select ===
This animation selects (or unselects) objects when certain conditions are true (or false). The example below shows the object when the n1 of engine[1] is higher than 25%.

<source>
<animation>
<object-name>Object</object-name>
<type>select</type>
<condition>
<greater-than>
<property>engines/engine[0]/n1</property>
<value>25</value>
</greater-than>
</condition>
</animation>
</source>

=== Shader ===
<source>
<animation>
<type>shader</type>
<shader>chrome</shader>
<texture>chrome2.png</texture>
<object-name>Object</object-name>
</animation>
</source>

* '''shader:'''
* '''texture:''' path to the texture used by the shader.

=== Spin ===
Very similar to [[#Rotate|rotate]], but the property provides a value in revolutions per minute (RPM) rather than an absolute position in degrees, and offset cannot be used.

<source>
<animation>
<object-name>Object</object-name>
<type>spin</type>
<property>engines/engine[0]/n1</property>
<factor>25</factor>
<center>
<x-m>-1.50</x-m>
<y-m> 1 </y-m>
<z-m> 0.25</z-m>
</center>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:''' is optional.

=== Textranslate ===
A very important animation for cockpits! This animation moves textures over a surface.

<source>
<animation>
<type>textranslate</type>
<object-name>Object</object-name>
<property>autopilot/settings/target-speed-kt</property>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

* '''factor:'''
* '''step:'''
property * factor * step * texture width/height = the amount of pixels that the texture should be translated. If your texture is 256 pixels, an textranslate of 0.1 will result in the texture moving with 26 pixels, into the direction specified by the axis settings.

=== Timed ===
Swtiches between objects at specified intervals. This example switches between a lights-on model and a lights-off model. Lights on are shown 0.2 seconds, while lights off are displayed for 0.8 seconds.

<source>
<animation>
<type>timed</type>
<object-name>BacklightOn</object-name>
<object-name>BacklightOff</object-name>
<use-personality type="bool">true</use-personality>
<branch-duration-sec>0.8</branch-duration-sec>
<branch-duration-sec>0.2</branch-duration-sec>
</animation>
</source>

=== Translate ===
The same as [[#Textranslate|textranslate]], but this animation moves a whole object (so including fixed textures). The example below will move an object 5 meters in the y-direction.

<source>
<animation>
<type>translate</type>
<object-name>Object</object-name>
<property>controls/seat/pilot/position-norm</property>
<factor>5</factor>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</animation>
</source>

==References==
* [http://www.opensubscriber.com/message/flightgear-devel@flightgear.org/958955.html "material" animation (and the bo105 as an example)]
by Melchior Fanz, March 22 2005.

[[Category:Aircraft enhancement|Animate models]]
[[Category:Howto|Animate models]]
[[Category:Modeling|Animate models]]
[[Category:Scenery enhancement|Animate models]]

Howto:Lightmap

2011-10-26T13:33:13Z

Paul Richter: proper teminology

[[File:Boeing_747-400_lightmap_cockpit.png|thumb|270px|[[Boeing 747-400|Boeing 744]] cockpit with several lightmapped panels.]]
[[File:Boeing_747-400_lightmap_exterior.png|thumb|270px|[[Boeing 747-400|Boeing 744]] exterior with lightmapped fuselage and tail.]]
A '''lightmap''' is a texture that contains the brightness of surfaces in a computer graphic. The darker a pixel on the lightmap, the less emissive the correpsonding pixel will be on the color/photo texture.

Some reasons why lightmaps are useful:
* they allow us to light surfaces without the need for creating alpha layers (like formerly used on many aircraft).
* we can edit the colors of a texture, without interfering with the lighting. Useful if you want to add some dirt to your panels, later on.
* lights look realistic at all times of day. Unlike a textranslate animation, where you change between day/night textures (often being too dark during dawn/dusk).

== Lightmaps in FlightGear ==
'''<font color="red">There is limited support for lightmaps as of FlightGear 2.4.0. Gijs is working on further support for it.</font>'''

'''Note:''' material shaders must be enabled in the <tt>View > Rendering options</tt> dialog for lightmaps to work.

=== The lightmap ===
You'll have to create a lightmap for every single texture that is meant to be lightmapped. This can be done by hand, or via some 3D Software, like [[Blender]] (which will be used in the example on this page).

# Open/import your model in Blender.
# Go to <tt>Add > Lamp</tt>, and select on of the lamp types. The light will be created in the model's origin.
#* '''Lamp:''' spreads light in all directions. Can be used for anti-collision lights, navigation lights etc.
#* '''Area:''' long/large lamp areas, like instrument panel lighting where fluorescent lamps are used.
#* '''Spotlight:''' for lights in a specific area/direction. Used for landing lights.
# Move/rotate the lamp to the prefered location/orientation. '''Note:''' leave the scale tools untouched, scaling the lamp does NOT affect the lightmap.
# Select the lamp (right mouse click) and open the Shading menu (F5). This is where we can edit the lamp. Some of the more important settings:
#* '''Dist:''' the distance (in meter) at which the light intensity is half as intense as at the source.
#* '''Energy:''' intensity of the light.
#* '''R/G/B:''' the color of the light. Yes, lightmaps support colors!
#* '''SpotSi:''' width of the spotlight beam in degrees.
#* '''SpotBl:''' softness of the spotlight edge. Softer edges create a more natural look for most aircraft lights.
# Select the object you'd like to create the lightmap for. Go into editing mode and then back to object mode (to load the object's texture).
# Go to the Scene menu (F10) and open the Bake tab. Select Full render and click the big Bake button. Blender will now start generating your lightmap.
# Change your mainwindow (or add an extra window) to UV/Image editor. You will see the lightmap being created bit by bit.
# When the lightmap is finished, click <tt>Image > Save as...</tt> and save the image in your aircraft's directory.

That's it! Now, you probably want to see how it looks on your aircraft, which is explaind in the next paragraph. If you are not yet satisfied with the result, you can edit your lamp's settings (step 4) and add more lamps to see what effect that has on the result.

=== The xml ===
In your model's .xml file, add the following block of code:

<syntaxhighlight lang="xml">
<effect>
<inherits-from>Effects/lightmap</inherits-from>
<parameters>
<texture n="1">
<image>Aircraft/747-400/Models/Effects/lightmap.png</image>
</texture>
<condition><use>/controls/lighting/logo-lights</use></condition>
<factor><use>/controls/lighting/panel-norm</use></factor>
</parameters>
<object-name>fuselage</object-name>
</effect>
</syntaxhighlight>
In which:
* '''image:''' [[#The lightmap|the lightmap itself]]
* '''condition:''' when this property is greater than or equal to 1, the lightmap will be enabled.
* '''factor:''' can be used to control the intensity of the light, on a 0-1 scale.

Remember that such a block is required for each single texture that you want to lightmap. You can have multiple objects per effect, but not multiple effects per object.

== Known problems ==
* FlightGear does not support multiple shaders per object. Therefore, you'll have to choose between the [[Howto: Aircraft Reflection Shader|reflection]] or [[Howto: Use the normal map effect in aircraft|normalmap]] shaders and the lightmap.
A combination of all three shader together is currently in a experimental state and under testing.
* there is no flexible way to (de)select lightmaps on a per-object base. Currently it only listens to one per-object defineable property.

[[Category:Aircraft enhancement|Lightmap]]
[[Category:Howto|Lightmap]]
[[Category:Modeling|Lightmap]]

Livery

2011-10-18T05:40:35Z

Paul Richter: make all the examples consistent

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<klm-747-texture>Liveries/KLM.png</klm-747-texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft; the texture path is relative to the model's xml in which it is used.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/747/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/747/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>klm-747-texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery to be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the appropriate livery.

<file type="string">KLM</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<texture-fuselage>KLM-Livery-fuselage.png</texture-fuselage>
<texture-wings>KLM-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>

=== Models/....xml ===
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>KLM-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>KLM-Livery-wings.png</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Livery

2011-10-18T04:54:38Z

Paul Richter: /* ...-set.xml */ sp

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<klm-747-texture>Liveries/KLM.png</klm-747-texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft; the texture path is relative to the model's xml in which it is used.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>klm-747-texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery to be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the appropriate livery.

<file type="string">KLM</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture-fuselage>ANA-Livery-fuselage.png</texture-fuselage>
<texture-wings>ANA-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>

=== Models/....xml ===
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>ANA-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>ANA-Livery-wings.png</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Livery

2011-10-18T04:52:01Z

Paul Richter: /* Models/Liveries */ Remove "Remember explanation". If you understood from the first example that the texture-prop statement defines a tag, it should be obvious.

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<klm-747-texture>Liveries/KLM.png</klm-747-texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft; the texture path is relative to the model's xml in which it is used.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>klm-747-texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the approperiate livery.

<file type="string">ANA</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture-fuselage>ANA-Livery-fuselage.png</texture-fuselage>
<texture-wings>ANA-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>

=== Models/....xml ===
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>ANA-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>ANA-Livery-wings.png</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Livery

2011-10-18T04:48:02Z

Paul Richter: /* Models/Liveries */ remove stuff about paths - there is no reason livery files should not be in the same or sub-directory as the livery XML.

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<klm-747-texture>Liveries/KLM.png</klm-747-texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft; the texture path is relative to the model's xml in which it is used.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>klm-747-texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the approperiate livery.

<file type="string">ANA</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture-fuselage>ANA-Livery-fuselage.png</texture-fuselage>
<texture-wings>ANA-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>

Remember the names (<texture-fuselage> and <texture-wings>), as you will need them in the model file in the next step.

=== Models/....xml ===
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>ANA-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>ANA-Livery-wings.png</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Livery

2011-10-18T04:43:26Z

Paul Richter: /* Models/....xml */ Change "texture" to "klm-747-texture" to emphasize that this tag is user-defined

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<klm-747-texture>Liveries/KLM.png</klm-747-texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft.

Note that the texture path is relative to the model's xml in which it is used. If your aircraft's model.xml is located in <tt>Aircraft/../XML/</tt> for example, you'll have to use
<klm-747-texture>/../Models/Liveries/KLM.png</klm-747-texture>
The <tt>/../</tt> indicates the FlightGear should "move" one directory up. You can add more than one of these, depending on your directory structure.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>klm-747-texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the approperiate livery.

<file type="string">ANA</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture-fuselage>ANA-Livery-fuselage.png</texture-fuselage>
<texture-wings>ANA-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>

Remember the names (<texture-fuselage> and <texture-wings>), as you will need them in the model file in the next step.

=== Models/....xml ===
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>ANA-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>ANA-Livery-wings.png</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Livery

2011-10-18T04:42:41Z

Paul Richter: /* Models/Liveries */ Change "texture" to "klm-747-texture" to emphasize that this tag is user-defined

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<klm-747-texture>Liveries/KLM.png</klm-747-texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft.

Note that the texture path is relative to the model's xml in which it is used. If your aircraft's model.xml is located in <tt>Aircraft/../XML/</tt> for example, you'll have to use
<klm-747-texture>/../Models/Liveries/KLM.png</klm-747-texture>
The <tt>/../</tt> indicates the FlightGear should "move" one directory up. You can add more than one of these, depending on your directory structure.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the approperiate livery.

<file type="string">ANA</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture-fuselage>ANA-Livery-fuselage.png</texture-fuselage>
<texture-wings>ANA-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>

Remember the names (<texture-fuselage> and <texture-wings>), as you will need them in the model file in the next step.

=== Models/....xml ===
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>ANA-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>ANA-Livery-wings.png</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Livery

2011-10-18T04:35:05Z

Paul Richter: multiple texture example - use clearer names

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<texture>Liveries/KLM.png</texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft.

Note that the texture path is relative to the model's xml in which it is used. If your aircraft's model.xml is located in <tt>Aircraft/.../XML/</tt> for example, you'll have to use
<texture>/../Models/Liveries/KLM.png</textures>
The <tt>/../</tt> indicates the FlightGear should "move" one directory up. You can add more than one of these, depending on your directory structure.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the approperiate livery.

<file type="string">ANA</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture-fuselage>ANA-Livery-fuselage.png</texture-fuselage>
<texture-wings>ANA-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>

Remember the names (<texture-fuselage> and <texture-wings>), as you will need them in the model file in the next step.

=== Models/....xml ===
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>ANA-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>ANA-Livery-wings.png</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Tokyo Haneda International Airport

2011-10-12T08:45:23Z

Paul Richter: update

{{infobox Airport
|name = Tokyo Haneda International Airport
|image =RJTT.jpg
|alt =Screenshot of Haneda Airport
|iata =HND
|icao =RJTT
|type =Public
|owner =Tokyo Aviation Bureau
|city =Ota Ward, Tokyo, Japan
|runway= 16R/34L
|length= 3000 m
|material= Asphalt
|runway2= 16L/34R
|length2= 3000 m
|material2= Asphalt
|runway3= 04R/22
|length3= 2500 m
|material3= Asphalt
|website =http://www.tokyo-airport-bldg.co.jp
}}
Tokyo Haneda International Airport, formally '''Tokyo International Airport''' (東京国際空港)(IATA: '''HND''', ICAO: '''RJTT'''), is the main domestic airport of Japan, as well as some nearby Asian cities including Seoul, Shanghai, Hong Kong and soon Beijing. The name "Haneda" is used to distinguish the airport from its international counterpart in the countryside, Narita International Airport. Haneda handled 66,735,587 passengers on 2008, making it the busiest airport in Japan and the fourth busiest in the world. To accomondate the growth, a new fourth runway and international terminal were completed in 2010.

== Airlines ==
While used mainly for Japanese airlines, a growing number of international airlines have started using Haneda's new international facilities.

=== Airlines with Hubs at Haneda ===
* All Nippon Airways
* Japan Airlines Group
* Skynet Asia Airways
* Skymark Airlines
* Hokkaido International Airways
* StarFlyer

=== Airlines Serving Haneda ===
* Air China
* Asiana
* China Eastern Airlines
* Korean Air
* MIAT Mongolian Airlines
* Shanghai Airlines

[[Category:Airports in Japan]]

Cessna T-37

2011-10-12T08:34:12Z

Paul Richter: update image

{{infobox Aircraft
|image = T-37-splash.png
|name = Cessna T-37
|type = Military Aircraft
|authors = Erik Hofman, Paul Richter
|fdm = JSBSim
|status = beta
|fgname = T37
}}

The '''Cessna T-37 Tweet''' is a basic jet trainer that first flew in 1954 and served in the U.S. and other air forces. It seats two in a side-by-side arrangement.

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* engine turbines do not rotate or are not visible (engine bay could be a little darker)
* no aircraft light available
* aircraft has no shadow
* no jetstream visible
* No speedbrakes available

3d Cockpit:
* no cockpit light at night available
* no switches and levers available
* no elevator trim control available
* cockpit is not textured
* cockpit window has no windscreen wipers

General:

* no hud available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]

File:T-37-splash.png

2011-10-12T08:33:23Z

Paul Richter: Splash screen from current T-37

Splash screen from current T-37

Cessna T-37

2011-10-12T08:32:06Z

Paul Richter: update author, status items

{{infobox Aircraft
|image = Cessna_T-37.jpg
|name = Cessna T-37
|type = Military Aircraft
|authors = Erik Hofman, Paul Richter
|fdm = JSBSim
|status = beta
|fgname = T37
}}

The '''Cessna T-37 Tweet''' is a basic jet trainer that first flew in 1954 and served in the U.S. and other air forces. It seats two in a side-by-side arrangement.

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* engine turbines do not rotate or are not visible (engine bay could be a little darker)
* no aircraft light available
* aircraft has no shadow
* no jetstream visible
* No speedbrakes available

3d Cockpit:
* no cockpit light at night available
* no switches and levers available
* no elevator trim control available
* cockpit is not textured
* cockpit window has no windscreen wipers

General:

* no hud available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]

Aircraft speed

2011-10-12T08:26:18Z

Paul Richter: fix cap and link

Speed combines two factors, the ''distance'' travelled in a certain amount of ''time''. In aviation speed is most often expressed in '''knots''' (kt). One knot is one nautical mile per hour. In aircraft the speed is "measured" with a [[#Pitot tube|pitot tube]], the result is not the speed of the aircraft, it is the speed of the air flowing around the aircraft, the [http://en.wikipedia.org/wiki/Airspeed '''airspeed'''].

In older planes, notably German WW II fighter planes, the airspeed is indicated in kilometres per hour (km/h), which is still used in present-day European glider planes. The conversion factor is 1.852, i.e. you can roughly divide a reading in km/h by two in order to get the value in knot.

If the speed is indicated in knot, sometimes a 'K' is put before the acronym, so KEAS stands for 'equivalent airspeed in knot'.

For (near-)supersonic planes the speed can be expressed in Mach.

==Expressing speed==
=== Ground speed ===
*[http://en.wikipedia.org/wiki/Ground_speed '''Ground''' speed (GS)] is the horizontal speed in which the aircraft moves relative to a fixed point on the ground.

One needs to know the GS in order to see how long a flight from A to B actually takes. Nowadays GS can be directly measured using a GPS system, and some aircraft equipped with such a system have a GS indicator. The GS can be calculated from TAS by correcting it for the prevailing wind at altitude or by measuring the time between passing two points on the ground [[radio beacons]] with a known distance, but in Flightgear you can always cheat and get it from the property browser under <tt>velocities/groundspeed-kt</tt>.

GS is the velocity in the horizontal direction of the aircraft. I.e. in a steep dive, the aircraft can move very fast, but because the motion is chiefly vertical, the ground-speed can be very small at the same time. This is where the GS differs from the ground-speed of a car.

=== True airspeed ===
*[http://en.wikipedia.org/wiki/True_airspeed '''True''' airspeed (TAS)] is the speed in which the aircraft moves relative to the surrounding air.

The difference between TAS and GS is that the air itself may move with respect to the ground (that's wind), and dependent on course relative to the wind direction a discrepancy between TAS and GS is induced. TAS can't really be measured directly but needs to be calculated.

Knowing TAS during flight is surprisingly useless - for navigation, ground speed is needed, and aerodynamic limits do not depend on TAS but rather IAS. The chief value of TAS is as a measure of aircraft performance and in pre-flight planning before the wind effect is taken into account.

The TAS can be calculated from CAS, air temperature and [[Altitude#Pressure altitude|pressure altitude]] and is the second step to calculate the GS from IAS for navigation.

Often TAS and GS are assumed (confused) to be the same, they are not.

=== Indicated airspeed ===

*[http://en.wikipedia.org/wiki/Indicated_airspeed '''Indicated''' airspeed (IAS)] is the number displayed on the [http://en.wikipedia.org/wiki/Airspeed_indicator airspeed indicator].

Airspeed is usually measured with a [[#Pitot tube]] at the front of the aircraft. The IAS can be the CAS. The IAS is not the TAS since the pressure differs greatly with [[altitude]] (more specific the density of the air). The higher the [[altitude]] the lower the IAS while flying the same TAS.

In spite of this dependence on [[altitude]], IAS is a very useful quantity in flight. Many aerodynamical properties, for example drag, lift, the stress on the airframe, stall speed or the forces on control surfaces depend on the dynamic pressure generated by the airstream, not on the actual aircraft speed. The stall speed of an aircraft at sea level is very different from the stall speed (in TAS) at 30.000 ft - but they correspond to the same IAS reading.

At sea level, a IAS of 400 knot roughly corresponds to 400 knot TAS. At 80.000 feet (the cruising altitude of a [[SR-71]]), the IAS of 400 knot corresponds to a TAS in excess of 1600 knot (..that corresponds with about Mach 3 at that altitude).

=== Calibrated airspeed ===

*[http://en.wikipedia.org/wiki/Calibrated_airspeed '''Calibrated''' airspeed (CAS)] is calculated from the [[#Pitot tube]] measurement and correcting it for standard errors.

Modern equipment can most often can indicate the CAS. For navigation the CAS is the first step to calculate the GS.

=== Equivalent airspeed ===

*[http://en.wikipedia.org/wiki/Equivalent_airspeed '''Equivalent''' airspeed (EAS)] takes into account another correction (above [[#Calibrated airspeed]], this time having to do with air properties rather than sensor errors.

At high altitude, the compressibility of air changes, so even CAS becomes more and more unreliable. For the [[SR-71]] Blackbird with a ceiling of 85.000 feet, the CAS becomes very unreliable and the plane has to be flown based on a EAS. For more conventional aircraft, EAS is not used. Thus, EAS is what a perfect dynamic pressure sensor would show when properly calibrated for the air compressibility at the current altitude. The EAS is the calculated result from the ram pressure (measured by the [[#Pitot tube]]) and the static pressure (measured by the [[altimeter]]).

=== Mach number ===

*The [http://en.wikipedia.org/wiki/Mach_number '''Mach number''' (M)] is the speed of the aircraft divided by the speed of sound (at that altitude). It is a calculated number without a unit.

The aircraft's behaviour at Mach 1 at sea level is about the same as the behaviour of the aircraft at an altitude of 60000 feet.
A Mach number below 1 means that the plane moves subsonic. A Mach number above 1 indicates supersonic flight. The Mach number is critical because a number of phenomena take place just around Mach 1 (transonic speed), for example a sudden increase in drag induced by shock-wave generation (sonic-boom). Aircraft that are not designed to fly supersonic will break up at Mach 1. The shape of the aircraft can cause parts of the aircraft being at or above Mach 1 while the fuselage is subsonic. Flying near Mach 1 can be quite dangerous, for most fast (but subsonic) aircraft Mach 0.83 is the limit. High flying aircraft, like passenger aircraft, can reach that limit easy while descending.

The speed of sound changes with the compressibility (and hence temperature) of air, the Mach number is dependent on [[altitude]] (as the air temperature drops at higher altitudes). This implies that Mach 2 at sea level corresponds to a faster TAS than Mach 2 at 30.000 ft. The precise relation between TAS, Mach number and altitude is a complicated formulae and depends in essence on the local weather pattern determining the pressure and temperature gradients in the atmosphere.
The Mach number is measured/calculated from the same information as the EAS ([[#Pitot tube]] and [[altimeter]])

==V speeds==
For the complete V speed "definitions" list please visit [http://en.wikipedia.org/wiki/V_speeds Wikipedia]. Here a small abstract. Note that V speed definitions can depend of local [[Flight rules]]. Most V speeds depend on the aircraft configuration (how much it weights etc.) so must be calculated forehand and must be included in the flight-plan. V speeds are used to compare aircraft performance and will be mentioned in the aircraft flight manual (AFM).
*M speeds are expressed in Mach.

{|
|- valign="top"
|V<sub>1</sub> || Take-off decision speed & Critical engine failure recognition speed.
During take-off the speed at which the aircraft safely can take-off even when one (of more) engine fails ("eats a bird"). The co-pilot (FO) will call out V<sub>1</sub> during take-off, the pilot will check if all engines are running and decides to continue or abort take-off.
|- valign="top"
|V<sub>R</sub> ||Nose-wheel take off speed.
The speed at which the nose-wheel leaves (should leave) the ground. As the speed increases the yokes will be pulled at V<sub>r</sub>. It is also the speed at which the aircraft still can be stopped if there is a critical failure. The co-pilot (FO) will call out "rotate" during take off. V<sub>R</sub> is very similar to V<sub>ROT</sub> and V<sub>REF</sub>.
|-
|V<sub>2</sub> || Take-off safety speed.
|-
|V<sub>3</sub> || Flap retraction speed.
|-
|V<sub>A</sub>||Design manoeuvring speed. Above this speed it is a bad idea to make sudden manoeuvres.
|-
|V<sub>LO</sub> ||Maximum landing gear operating speed.
|-
|V<sub>LE</sub> || Maximum landing gear extended speed.
|-
|V<sub>FE</sub> || Maximum flap extended speed.
|-
|V<sub>C</sub> || Design cruising speed, also known as the optimum cruise speed, is the most efficient speed in terms of distance, speed and fuel usage.
|- valign="top"
|V<sub>S</sub> ||Stall speed or minimum steady flight speed for which the aircraft is still controllable.
|- valign="top"
|V<sub>S<sub>0</sub></sub> || Stall speed or minimum flight speed in landing configuration.
|-
|V<sub>S<sub>R</sub></sub>|| Reference stall speed.
|-
|V<sub>MO</sub> || Maximum operating limit speed.
|-
|V<sub>NE</sub> || Never exceed speed.
|-
|V<sub>NO</sub> || Maximum structural cruising speed or maximum speed for normal operations.
|}
*Not knowing the (complete list of) V speeds has caused dramatic accidents. It has occurred that the pilot and co-pilot were not aware of the minimal speed of an aircraft during landing with one engine damaged causing loss of control just before touch-down (the pilot gave full throttle hoping to gain speed expecting to get back control causing the left-over engine push the aircraft to one side).

==Pitot tube==
The [http://en.wikipedia.org/wiki/Pitot_tube pitot tube] is the tool to measure the airspeed. It is a tube directed forwards, exposed to the airstream. The air is being pushed inwards (rammed) by the motion of the aircraft and the (ram) pressure is measured. The measured pressure is corrected indicating the airspeed. The ram pressure is also called the dynamic pressure opposite the static pressure that us used to indicate [[altitude]]. Bigger aircraft have two pitot tubes and the indicator displays the average of the two. However, most often only one pitot tube is used to control the autopilot, even when the indicator is connected with two.

The pitot tube can be blocked easy, once blocked, or worse, partially blocked the IAS will have no relation with the speed of the aircraft. This situation is enhanced if the pitot tube controlling the autopilot is blocked.

Ice is a known cause of blockage of the pitot tube hence there are pitot heaters that should prevent forming of ice. Another known cause of blockage are insects. Blockage of pitot tubes is a known cause of some very dramatic accidents and every pilot should learn how to deal with strange behaving speed indicators and autopilots.

==Additional information==

*Velocity: A vector combining speed and (angle of) direction. Often used as synonym of speed.
*[[Understanding Supersonic Flight]]

[[Category:Aviation]]

Scripted Compilation on Linux Debian/Ubuntu

2011-07-28T08:40:01Z

Paul Richter: /* Instructions */ make directory name consistent

==Description==
The following script takes care of downloading and compiling Flightgear from the git repositories with just one command execution for both 32-bit and 64-bit Debian based systems (Debian, Ubuntu). Pre-existing installed version (if any) of Flightgear are not touched at all since the script builds and installs everything under the directory in which it is launched.

Necessary packages are installed via the apt-get system while libraries not included in the repositories are downloaded and compiled on the fly (i.e. [[Plib]], [[Simgear]] and [[OSG]]).

=== List of compiled programs ===
The script is able to download and compile:
* Flightgear (And all the data needed to use it)
* [[Fgrun]]
* [[FGCOM]]
* [[FGComGui]]
* [[Atlas]]
* [[Terrasync]]

== Download ==
You can download the script here: [http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh download_and_compile.sh]

The script is maintained in the FlightGear main repository. Remember to update this script whenever a new FlightGear version is released, so that you'll be able to download the latest stable revision.

There is also another option for building FG and all its dependencies in an automated fashion, please refer to: http://geoffmclane.com/fg/fgfs-052.htm

== Instructions ==
To run download_and_compile.sh, just save it in a directory called for example: ~/fgfs
then execute it (no need to execute it as root).

Here is for example a sequence of commands to get the script and launch it in a new folder.
<pre>
mkdir ~/fgfs
cd ~/fgfs
wget http://www.gitorious.org/fg/fgmeta/blobs/raw/master/download_and_compile.sh
chmod 755 download_and_compile.sh
sh download_and_compile.sh
</pre>
Once all will be finished, you will sucessfully get all the programs installed in the ~/fgfs directory.

=== Launching FlightGear ===
To run your new git installation of Flightgear you have to launch the ''run_fgfs.sh'' command under the same folder, for example:
<pre>
cd ~/fgfs
sh run_fgfs.sh
</pre>

=== Launching Fgrun ===
For many users it's more comfortable having Flightgear launched by the graphical utiliy Fgrun which is installed as well in the same folder. You have to launch the ''run_fgrun.sh'' command, for example:
<pre>
cd ~/fgfs
sh run_fgrun.sh
</pre>

=== Launching FGCOM ===
FGCOM is the system used by flightgear to simulate radio communications between users. Launch it using the ''run_fgcom.sh'' command:
<pre>
cd ~/fgfs
sh run_fgcom.sh -cs
</pre>

=== Launching FGComGui ===
FgComGui is a GUI wrapper to launch fgcom.
<pre>
cd ~/fgfs
sh run_fgcomgui.sh
</pre>

=== Launching Atlas ===
Atlas provides a map for Flightgear, use it launching: ''run_atlas.sh''
<pre>
cd ~/fgfs
sh run_fgatlas.sh
</pre>

=== Launching Terrasync ===
Your Flightgear compilation comes with the Terrasync program too, so if you want to use it:
<pre>
cd ~/fgfs
sh run_terrasync.sh -S -p 5500 -d /folder/with/sceneries
</pre>
Where: ''/folder/with/sceneries'' is the folder containing the sceneries data.

Then launch fgfs with the '''--fg-scenery=/folder/with/sceneries --atlas=socket,out,5,localhost,5500,udp''' option

== Troubleshooting ==

=== Compilation errors ===
Here we are, no fear, if you wish to use programs from the cvs/svn/git repositories, you might face compilation errors that will prevent you to have a working copy of one or more of the programs provided by this script. What can be the causes that prevent us from a successful compiling? As far as I know those:
# Software developers introduce a new functionality with a new piece of code that prevents the compilation under your architecture, this can happen working with cvs/svn/git sources.
# The program refuses to compile because of a divergence in the libraries it depends. For example Flightgear might not compile because OSG has been modified, while OSG itself compiles fine, FG won't.
# One or more repositories are down and you can't get the library you need. (Both from cvs/svn/git or apt-get)

There is a simple solution to the above errors: wait and relaunch the script after some time (hours or days), if (and generally happens) software developers repair or synchronize their code with the newly updated libraries, your Flightgear will compile fine as if the previous error never took place.

Sometimes it happens that the script fails to compile only fgrun,fgcom or atlas, if you then see the run_fgfs.sh file it means that Flightgear installation was successful and you can safely run it.

== Options ==
The script by default (without any option) will only compile Flightgear and Fgrun. To make it compile all, you need to launch the script with the ''ALL'' parameter. i.e.:
<pre>
sh download_and_compile.sh ALL
</pre>

=== Compiling only one program ===
If you wish to recompile only one of the programs you can launch the script with one of the following parameters:
* PLIB (to compile and install only plib)
* OSG (to compile and install only OpenSceneGraph)
* SIMGEAR (to compile and install only Simgear)
* FGFS (to compile and install only FlightGear)
* DATA (to download / update only data files for FlightGear)
* FGRUN (to compile and install only Fgrun)
* FGCOM (to compile and install only Fgcom)
* FGCOMGUI (to compile and install only FgComGui)
* ATLAS (to compile and install only Atlas)

=== Fast updating ===
There is a second parameter ''UPDATE'' that allows you to just update your installation. i.e.:
This will only update FGFS
<pre>
sh download_and_compile.sh FGFS UPDATE
</pre>

=== Compiling last stable versions (Experimental) ===
Event if the script fetches data and sources from bleeding edge developers repositories (which sometimes do not compile), you can still force the script to download latest know versions of the software that was compiling successfully adding the -s option.
<pre>
sh download_and_compile.sh -s
</pre>

How it works ? Inside the script there is a small list with lates known versions of successfully compiling revisions, it will download from svn/git that specific revisions, which have been found able to compile together.

=== Advanced options ===
* Skip download of packages using '''-p n''' option
* Skip compilation of programs using '''-c n''' option
* Skip retrieving software updates using '''-d n''' option
* Skip reconfigure (make clean) using '''-r n''' option

For example, if you a developer and wish to fast recompile and reinstall only modification for FlightGear do this:
<pre>
sh download_and_compile.sh -p n -d n -r n FGFS
</pre>

this will only recompile modifications and reinstall them.

=== Multicore Acceleration ===
Using the option '''-j x''' (where x is the number of your CPU-Cores you wish to assign to the job) will speed up the whole compilation process considerably.

== Disk usage ==
Having both compiled program, source codes and data from git requires some hard disk space: It will take you something like 7 GB of space.
If you don't have a fast machine, it will require you also some hours of compilation time.

[[nl:Compileren met een Script op Linux Debian/Ubuntu]]

Atlas

2011-06-28T02:28:29Z

Paul Richter: /* Creating the Maps */ Rewrite explanation of paths with spaces

[[File:Atlas.jpg|thumb|270px|Map view of the San Francisco bay area]]

''"Atlas aims to produce and display high quality charts of the World for users of FlightGear"'' - [http://atlas.sourceforge.net Atlas website]

== Introduction ==
The '''Atlas''' program lets FlightGear users display a real-time "moving-map" of their flight. Atlas is an independent software project, distributed under the same free (GPL) software license as FlightGear.

== Installation ==

=== Installing on Windows ===
To install Atlas on Windows, download the "installer" version of Atlas from the [http://atlas.sourceforge.net/index.php?page=download Download Page]

For example, download '''atlas-0.3.0-win32-setup.exe''', and run it. The installer will prompt you for the FlightGear directory. If you installed FlightGear in the default directory, "C:\Program Files\FlightGear", accept the default setting. If you don't know your FlightGear directory, you can right-click your FlightGear icon, click properties then look at the "target". Your root FlightGear directory is the part of the target before the text "\bin\win32\fgrun.exe")

After finishing the install wizard, but before running Atlas, the next step is to create the actual maps used by Atlas.

=== Installing on Linux ===

If you are lucky, you might find that Atlas is available from your distribution's repository.

It could be called fgfs-atlas or similar so you'd just type in the following (or use synaptic or some other package installation program):-

apt-get install fgfs-atlas

If you distribution doesn't include a current version of Atlas (0.3.1 as of writing), you may elect to compile Atlas from source. The source code can be retrieved from http://sourceforge.net/projects/atlas/files/. Please select the latest tarball. The process of compiling the program is consider out of scope for this wiki page. Please ask on the mailing list or search this wiki for the details.

=== Creating the Maps ===
Atlas puts together the whole map display from smaller pieces of the map, called "tiles". Before running Atlas for the first time, all of the map tiles used by Atlas must be created from the scenery data installed in FlightGear. The program used to create the tiles is called "map", and it is installed automatically as part of the Atlas installation.

Depending on the amount of scenery involved, and the level of detail requested, running the "map" process take anywhere from a few seconds to a few hours. Fortunately, this process does not need to be done often, only right after Atlas is installed, or after new scenery is added to FlightGear.

Here is an example of how to run "map" on Windows:

This example uses the default FlightGear directory for Windows, C:\Program Files\FlightGear. If you have FlightGear installed somewhere else, substitute your directory in the instructions below.

Start the Command Prompt...to do this click start>Run ...type cmd and hit enter.
Type...
cd C:\Program Files\FlightGear\bin\win32
Now Type...
set FG_ROOT=C:\Program Files\FlightGear\data
Now type...
set FG_SCENERY=C:\Program Files\FlightGear\Data\Scenery;C:\Program Files\FlightGear\Scenery
Notice that the scenery directories are separated with a semi-colon (";").
Now type
map --size=256 --atlas=C:\Program Files\FlightGear\data\Atlas
This puts the files in <tt>C:\Program Files\FlightGear\data\Atlas</tt>. If you want the files in a different location just replace <tt>C:\Program Files\FlightGear\data\Atlas</tt> with the location you want.

The --size=256 gives a certain resolution in Atlas, meaning that each map generated will be 256x256 pixels. For higher resolutions you would use =512 or =1024 or =2048, for lower resolutions you would use =64 or =128.

Therefore, to create low resolution maps type...
map --size=64 --atlas=C:\Program Files\FlightGear\data\Atlas\lowres

The map program has a lot commands-line options. To see them type...
map --help
To see this message
<tt>
MAP - FlightGear mapping utility
Usage:
--lat=xx.xx Start at latitude xx.xx (deg., south is neg.)
--lon=xx.xx Start at longitude xx.xx (deg., west is neg.)
--size=pixels Create map of size pixels*pixels (default 256)
--scale=x Kilometers from top to bottom of map (default 100)
--autoscale Automatically set scale to 1x1 degree tile
--light=x, y, z Set light vector for shading
--airport-filter=string Display only airports with id beginning 'string'
--output=name Write output to given file name (default 'map.png')
--fg-root=path Overrides FG_ROOT environment variable
--fg-scenery=path Overrides FG_SCENERY environment variable
--enable-airports Show airports
--enable-navaids Show navaids
--flat-shading Don't do nice shading of the terrain
--atlas=path Create maps of all scenery, and store them in path
--verbose Display information during processing
--singlebuffer Use single buffered display
--headless Don't display output (render into an off-screen buffer)
--glutfonts Use GLUT built-in fonts
--palette=path Set the palette file to use
--smooth-color Make smooth color heights
--jpeg Create JPEG images with default quality (75)
--jpeg=integer Create JPEG images with specified quality
--aafactor=integer Do antialiasing on image (factor must be a power of two)
</tt>

* '''Note 1:''' The map process can be much faster on some PC's using '''--headless''' option, which does not display the maps as they are being created. However, on other PC's, this causes an error, and the process will not run. Remove the '''--headless''' option if you get such an error.
* '''Note 2:''' On Windows systems, Atlas may not be able to handle paths for <tt>--atlas</tt> with spaces in them. In such a case, replace "Program Files" with "PROGRA~1". Or move the FG directory and Atlas directory to the desktop (works best with windows 7).

You could condense this into a small batch file that can be repeatedly used. Write:
cd c:\Program Files\Atlas\bin\win32
map --size=512 --atlas=c:\Program Files\Atlas\data\Atlas --fg-scenery=c:\Program Files\FlightGear\data\Scenery --palette=c:\Program Files\Atlas\data\AtlasPalette --glutfonts

Then save it as a .bat or .cmd file to your computer. If your computer turns off the screen / hard drive after a set time and don't want to change this permanently, download caffeine. Search for caffeine for windows on Google and select the first link.

=== Run Atlas ===
Atlas can be run by clicking on the shortcut set up by the install wizard, or from the command line. From the command prompt in Windows, enter:
"C:\Program Files\FlightGear\bin\win32\atlas.exe" "--fg-root=C:\Program Files\FlightGear\Data" "--path=C:\Program Files\FlightGear\data\Atlas" --udp=5500

In the [[FlightGear Wizard]] where you select settings before starting FlightGear, on the page after selecting your airport there is a check box option for Atlas, check it. In the "port" box enter 5500. If Atlas is running on the same computer as FlightGear, you can use the IP address 127.0.0.1 If Atlas is running on another computer, enter the IP address of that computer. (To look up the IP address of a computer, open the command prompt, and enter "ipconfig" as a command to display the IP address).

Once you have Atlas and FlightGear set to use the same port number (5500 by default), run FlightGear. As you fly around in FlightGear, Atlas will update your position on the map several times per second.

===Running Atlas Over A Network===
If you installed atlas on a computer, but want to run it from a different one, follow this procedure:
For Windows, on your first computer (the one with FlightGear and Atlas) enable file sharing. After doing this, if you have a firewall, go to your second computer and open the Command Prompt (Windows + R, then type "CMD") and type:
"ipconfig"
and note the IPv4 Address (along the lines of 192.168.1.XX) and add a firewall rule on your first computer to let that IP address through the firewall. Then set up the files for file sharing. Go to your FlightGear program files folder (C:\Program Files (x86)\FlightGear) and right click and select properties. Select the "Sharing" tab and click "Advanced Sharing". Click the checkbox for "Share this folder" and push "OK" on both windows. Do the same for the Atlas program folder (C:\Program Files (x86)\Atlas).

On your first computer, open the CMD and do "ipconfig" and note the IPv4 address. Go to your second computer and right click the "My Computer" and select "Map Network Drive". Leave the drive setting alone, Windows will configure that itself. In the "Path" box, type without the "":
"\\XXX.XXX.X.XX\FlightGear"
The "X" representing the numbers of the first computers IPv4 address.
Repeat this for the Atlas folder by changing "\FlightGear" to "\Atlas". Also note the \\. It is REQUIRED you do that and not //.

Once you have done this write a ".CMD" file in Notepad which would read:

title Atlas.exe
cls
@echo off
cls
ipconfig
pause
"W:\bin\win32\atlas.exe" "--fg-root=X:\Data" "--path=W:\data\Atlas" --udp=5500

The "W" drive is the Atlas folder in this example, change it to whatever Windows sets as your Atlas drive.
The "X" drive is the FlightGear folder in this example, change it to whatever Windows sets as your FlightGear drive.

The first line sets the CMD window name. The second line clears the window. The third line turns off the echo (if it was left on, the CMD would repeat what the batch file tells it, for example, if it was off, the cmd would run and say C:\Documents and Settings\User> title atlas.exe). The fourth line clears the window. The fifth line gives the IP address. The sixth line pauses and reads "Push any key to continue...". The seventh line executes the atlas program with the specified settings.

Once you are done with the script, click "File>Save As..." and save it as Start Atlas.bat (or .cmd).

You will need the scenery analyzed by the map.exe first. So if that is done, execute the file and wait for it to tell you the IPv4 address. Go to your first computer and configure your flight. On the final page, select the Atlas checkbox and enter the IPv4 address of the second computer and the UDP (default "5500") to what you set as the final part of the seventh line of coding. On the second computer, push any key and the Command Prompt will load the Atlas database can take some time if you are using all of the scenery maps. When the atlas window opens, activate the flight on the second computer and you have the second computer tracking the flight of the first. (don't worry the FlightGear App defaults to the e0 n0 co-ordinates at startup without loading the map graphics.)

=== Keys ===
You can control the Atlas Map display with the following keys:

{|
|-
| width="70px" | + || Zoom in
|-
| - || Zoom out
|-
| a/A || Show/hide Airports
|-
| C || Toggle auto-centering
|-
| c || Center map on Aircraft
|-
| d/D
| Hide/show the info interface and the graphs window
|-
| f/F
| Select next (f) or previous (F) flight track
|-
| j/J || Toggle search interface
|-
| L || Show the next downloading tile
|-
| l
| Schedule/de-schedule tile at current lat/lon
|-
| n/N || Show/hide navaids
|-
| o/O || Open flight file
|-
| s/S || Save flight file
|-
| t/T
| Toggle showing the bitmap overlay (yes, that's the maps!)
|-
| w/W
| Close the current track (Warning, this terminates live aircraft tracking over network for good!)
|-
| u/U
| Unattach current flight trac, ie start a new track
|-
| v/V
| Show/hide names of airports/navaids
|-
| Space || Show/hide main interface
|}

'''Enjoy Playing!!!'''

== Similar Software ==
* [http://rubyforge.org/projects/fgmap Flightgear Mapping]

== External links ==
* [http://atlas.sourceforge.net The Atlas website]
[[fr:Atlas]]

[[Category:Software]]
[[Category:GPL]]

Building TerraGear

2011-05-05T08:42:45Z

Paul Richter: remove spam

{{Out of date}}
{{UpdateToGit}}

''This article is about [[TerraGear]]''
== Introduction ==

The terrain used in [http://flightgear.org FlightGear] -- the land over which one flies, its texturing (by land usage type), the rivers and lakes and so forth -- are generated by software from a sister project called [http://terragear.org TerraGear]. TerraGear is used to read in geographical data -- descriptions of ground elevations, land cover (usage) information, airport locations and layouts, and so forth -- and output terrain over which one can fly.

For a variety of reasons, you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [http://taxidraw.sourceforge.net/ TaxiDraw] to modify/improve information about an airport's taxiway/apron layout, you might wish to see how that modified airport would look in the scenery before deciding you're happy with the results. And normally to see and use the airport in the scenery, it's necessary to [http://www.x-plane.org/home/robinp/#Updates submit the changes to Robin Peel], have him sign off on the changes, have the changes appear in the next [http://www.x-plane.org/home/robinp/ official apt.dat], and then wait for the next [http://www.flightgear.org/Downloads/scenery.html official FlightGear scenery] build; if you can build terrain yourself, you can start using it right away. Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher-resultion vector data (vmap1, Tiger) to get better roads/streams. For all these reasons, learning how to use TerraGear is a good idea.

There's existing documentation for TerraGear in at least three places: in the source code tree when you fetch it, on the website, and [http://cvs.terragear.org/cgi-bin/viewcvs/viewcvs.cgi/*checkout*/www/docs/scenery-tutorial/fg-scenery-tutorial.html?rev=1.3&cvsroot=TerraGear-0.0 in the CVS tree for the website]. The latter is the most current, and really needs to replace the version on the website; but all three are out of date in various ways. When I tried to use the most current documentation to use TerraGear, I ran into all sorts of problems: some I figured out on my own, and others various people helped me with (thanks especially Ralf and Frederic). I'm writing this stuff to detail what I had to do to use TerraGear to build scenery. I am not trying to rewrite the documentation; this should be considered an adjunct/supplement to the TerraGear docs, something you read along with the TerraGear docs. The docs can steer you wrong, or miss something; this is my effort to address those issues.

So here I'll describe what you have to do to get TerraGear up and running; a separate page details [[Using Terragear|how to use TerraGear]] to build the terrain for a particular area. A word of caution, however: I use Linux, so this description will be Linux-centric. I hope instructions for other OSes will be similar, but I really don't know. In particular, I don't have easy access to a Windows machine, so I don't know how what I say will differ for those on Windows. In fact, I don't even know if TerraGear can be built/used on Windows. Hopefully it'll work, under directions not too different from here. If not, hopefully someone else will edit this page to clarify how to do it (if it's possible).

== Building TerraGear ==

Go to the [http://www.terragear.org/ TerraGear website], select "CVS Resources", and check out a copy of the current sourcecode from CVS using the instructions at the top of the page. Once you've done that, you can try to build the source code. First, though, TerraGear depends on some other libraries you'll need. If you look in source/, you'll see a bunch of README files. Read them. In particular, note the ones with names like "README.somesoftwarename"; those describe software you'll need to be able to build and run TerraGear. Cygwin I ignored because that's for Windows and I'm not running Windows. plib and SimGear I already had from their CVS repositories, because I track FlightGear CVS; but it's a good idea to go ahead and update those two to current CVS, just in case the current TerraGear CVS depends on something that's been checked into plib or SimGear since the last time you updated them (yes, that means you'll have to update and rebuild FlightGear as well, sorry). If you don't track CVS for any of these things, you can still try to build TerraGear against whatever copies of SimGear and plib you have installed; but if you run into problems (unresolved symbols or whatever), that'd be the first place I'd look.

Some comments on the other libraries you need:

* GPC. The instructions for what to do are in source/README.gpc. That file says the current version is 3.21; in fact, it's 3.22. Don't forget that editing step described in the README. When you run the makefile, it'll create a library called libgenpolyclip.a; make install will put it in /usr/local/lib/ or wherever else you want it to go.
* GTS. I didn't build this -- I use Debian and got it by installing the Debian packages (libgts-0.7-1 and libgts-dev, both version 0.7.3-2 at this writing). So I can't comment on the instructions in source/README.gts.
* newmat. This is a bunch of matrix manipulation utilities, it looks like. The file source/README.newmat tells you what to do, except for the fact that it sends you to the wrong webpage (an info page) to download the file you need. Once on that info page, to actually find the file you want to download, click on "to home page" near the top, then on the link for downloading files. You'll see links for newmat downloads (I downloaded the current newmat11). Once you've got it, just follow the step by step instructions in the source/README.newmat file.
* nurbs++.

Once you have all of the above installed, you can proceed with configuring the TerraGear build, and building TerraGear. The TerraGear CVS Resources page that told you how to check out a copy of the source code tells you what to do to build it: run autogen.sh, then run configure, then make, then make install. However, first, autogen.sh comes out of CVS not-executable. So you'll need to make it executable first with chmod +x autogen.sh

Next, when you run configure, it takes arguments telling it where to find the libraries you need. I don't know what those arguments default to, but just for show, if they're all in /usr/local/lib, you could run configure like this: configure w/ args

$ ./configure --with-gts=/usr/local/lib/ --with-gpc=/usr/local/lib/
--with-newmat=/usr/local/lib/ --with-plib=/usr/local/lib/
--with-simgear=/usr/local/lib/

Next comes running make to build all the executables. The instructions in source/README tell you that you want to "compile the /Libs/TriangleJRS code without optimization (-O2)". However, that's not the path to those files. Go to source/src/Lib/TriangleJRS. There, edit Makefile -- remove "-O2" from the two locations it appears (CFLAGS and CXXFLAGS).

At that point, you're ready to run "make", then "make install". Unless you gave an option to configure telling it that TerraGear should be installed somewhere other than /usr/local, you'll probably need to be root to do "make install" successfully.

I ran into no problems with the above -- everything built and installed OK. This was the most pain-free part of the whole experience.

Hopefully, you now have a working copy of the TerraGear tools, and are ready to [[Using Terragear|use TerraGear]] to make scenery!

{{Terra}}
{{Building}}

Landmark Wish List

2011-02-05T09:02:08Z

Paul Richter: /* America */ Brasilia Congress in fgsdb

This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.

Feel free to add to this list.

If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".

=== Africa ===
{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" | Landmark
! style="background:#efefef" | City
! style="background:#efefef" | Country
! style="background:#efefef" | Completed
|-
|}
=== America ===
{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" | Landmark
! style="background:#efefef" | City
! style="background:#efefef" | Country
! style="background:#efefef" | Completed
|-
|National Congress || Brasilia || Brazil || '''Yes'''
|-
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Yes'''
|-
|Navy Pier || Chicago || USA || No
|-
|Adler Planetarium || Chicago || USA || No
|-
|Soldier Field || Chicago || USA || No
|-
|McCormick Place || Chicago || USA || No
|-
|U.S. Cellular Field || Chicago || USA || No
|-
|Wrigley Field || Chicago || USA || No
|-
|Shedd Aquarium || Chicago || USA || No
|-
|Union Station || Chicago || USA || No
|-
|Oglivie Transportation Center || Chicago || USA || No
|-
|Smurfit-Stone Building || Chicago || USA || No
|-
|Marina City || Chicago || USA || No
|-
|Millenium Park || Chicago || USA || No
|-
|United Center || Chicago || USA || No
|-
|Brooklyn Bridge || New York || USA || '''Claimed'''
|-
|Empire State Building || New York || USA || '''Yes'''
|-
|Chrysler Building || New York || USA || '''Claimed'''
|-
|United Nations Headquarters || New York || USA || '''Yes'''
|-
|Verizon Center || Washington, D.C. || USA || No
|-
|White House || Washington, D.C. || USA || No
|-
|Space Needle || Seattle || USA || '''Yes'''
|-
|Milwaukee Art Museum || Milwaukee || USA || No
|}

=== Asia ===
{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" | Landmark
! style="background:#efefef" | City
! style="background:#efefef" | Country
! style="background:#efefef" | Completed
|-
|Bank of China Tower || Hong Kong || China || '''Yes'''
|-
|CCTV Tower || Beijing || China || '''Yes'''
|-
|Taj Mahal || Agra || India || No
|-
|Akashi Kaikyo bridge || Kobe || Japan || '''Yes'''
|-
|Petronas Towers || Kuala Lumpur || Malaysia || '''Yes'''
|-
|Ryugyong Hotel || Pyongyang || North Korea || '''Yes'''
|-
|Burj Khalifa || Dubai || UAE || '''Yes'''
|-
|Burj al Arab || Dubai || UAE || No
|-
|Bitexco Financial Tower || Ho Chi Minh City || Vietnam || '''Yes'''
|}
=== Europe ===
{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" | Landmark
! style="background:#efefef" | City
! style="background:#efefef" | Country
! style="background:#efefef" | Completed
|-
|Stade de France || Saint-Denis || France || No
|-
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''
|-
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No
|-
|Lapan || Oldenburg, Niedersachsen || Germany || No
|-
|Schloss || Oldenburg || Germany || No
|-
|Colosseum || Rome || Italy || No
|-
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''Yes'''
|-
|Big Ben || London || UK || '''Yes'''
|-
|Westminster Abbey || London || UK || '''Yes'''
|}
=== Oceania ===
{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" | Landmark
! style="background:#efefef" | City
! style="background:#efefef" | Country
! style="background:#efefef" | Completed
|-
|Sydney Opera House || Sydney || Australia || '''Yes'''
|-
|Sky Tower || Auckland || New Zealand || '''Claimed'''
|}

==Related==

===Internal links===
*[[FlightGear Scenery Designer]]
*[[FlightGear Scenery Database]]
*[[UK_Scenery_Wish_List]]
===External links===
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]

[[Category:Scenery]]
[[Category:Community]]

FlightGear hangars

2010-12-29T06:53:51Z

Paul Richter: /* Other hangars (2) */ riktov's hangar contents

''See [[Links]] for an overall listing of FlightGear related external websites''

FlightGear has many [[aircraft]] available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version.

Be careful with external links!

===Official Hangars===
*[http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar]
*[http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)
*[http://liveries.flightgear.org FlightGear Liveries]

===Other hangars (1)===
*[http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (142+ original aircraft!)
*[http://fgnl.freehostia.com/ Gijs Hangar]
*[http://members.cox.net/davidculp/hangar.html Dave's Hangar] (also [http://daveshangar.blogspot.com/ Dave's Hangar Blog])
*[http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar]
*[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]
*[http://sydhangar.daffodil.uk.com/ Syd's Hangar]
*[http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar]
*[http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (also with Mac OS related content)
*[http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]

===Other hangars (2)===
*[http://www.AAliveries.yolasite.com/ AA Liveries] (Aircraft Modifications and liveries)
*[http://flightgear.bplaced.de/filemanager/flightgear/index.php longfly's german hangar] (DE)
**[http://www.flightgear.bplaced.de/filemanager/flightgear/index.php/flugzeugliste Flugzeugliste] (List of aircraft)
*[http://alphashangar.co.nr/ Alpha-J's Hangar] (Aircraft, Liveries, Scenery, AI, etc.)
*[http://skyopshangar.byethost17.com/ Skyop's FlightGear Hangar]
*[http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]
*[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]
*[http://ltts.crlt.indiana.edu/grn/flightgear/ Buckaroo's Hangar] (also with yasim introduction)
**Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81
*[http://presteshangar.wikidot.com/start Prestes Hangar]
*[http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]
*[http://sites.google.com/site/pjedvajflightgear/ pjedvaj's Hangar]
**Ilyushin Il-96-400, Mikoyan-Gurevich MiG-21bis, Pilatus PC-21, Pilatus PC-9M, Tupolev Tu-214
*[http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (x-wing)
*[http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)
*[http://vicmar.weebly.com/ FlightGear VicMar]
**Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack
*[http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)
*[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]
*[http://bravosflightgear.yolasite.com/ Bravo's FlightGear] (Airbus A318-100)
*[http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]
*[http://theomegahangar.webs.com SanFrancisco Pilots' OMEGA HANGAR]
*[http://flier95-flightgear.blogspot.com/ Flier95's Hangar] (Blog format)

====Livery Hangar only====
*[http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]
*[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]
*[http://berwickskins.yolasite.com/ Berwick-skins]
*[http://mojos-hangar.webs.com/ Mojo's Flightgear Livery Hangar]
*[http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]

====Homepages, blogs, etc.====

*[http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]
*[http://geoffmclane.com/fg/index.htm FlightGear Build Centre]
*[http://www.fguk.co.nr/ FlightGear United Kingdom]
*[http://www.flightgear-germany.de/ FlightGear Germany] (DE)
*[http://flightgear2009.blogspot.com/ Flight Gear Brasil 2009] (non-english)
*[http://www.shialeweb.com/caballerosaguila/news.php Caballeros Aguila] (non-english)
*[http://tehwarlock.tk/ Tehwarlock Blog]
*[http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)

===Other FlightGear repositories===
*[http://www.unitedfreeworld.com/ unitedfreeworld] (scenery, plane models, and livery)
*[http://www.flightgearplanes.com Flightgear Planes Website]

===Outdated Hangars===
*[http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar]
*[http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]

===Related content===
*[[Table of models]]
*[[Aircraft]] - [[Helicopter]] - [[Vehicle]]

[[Category:List]]

FlightGear Git

2010-12-13T03:13:35Z

Paul Richter: grammar

{{FlightGearGitOn}}
'''Git''' is a version control system used by the [[FlightGear]] project to store all of the files required to build FlightGear, as well as data (mainly [[aircraft]]). Git tracks updates to every file as developers around the world work together concurrently to create new versions.

While new FlightGear features and additions are in development, they are available from Git before they are available in the standard release version. Using Git allows a user to build the newest possible version of FlightGear from the latest source files, to experiment with new aircraft or other features. However, it's not a beginner's tool. Using Git can expose the user to unstable features that show ugly error messages, or crash the computer.

In May 2010, after a hardware failure on the [[CVS]] servers, the FlightGear project changed version control system from CVS to Git. The Git repositories are located at [http://gitorious.org/fg Gitorious] and at the [http://mapserver.flightgear.org/git/?p=fgdata;a=summary Mapserver].

Due to the "recent" switch, we are currently doing our best on providing manuals for obtaining FlightGear through Git. The following articles are work in progress:
* '''Mac OS X:''' [[FlightGear Git on Mac OS X]]
* '''Windows:''' [[FlightGear Git on Windows]]

== Motivation ==
Much has been written on the advantages of Git over CVS. For us, some advantages are:
* Much better support for branches and merging branches. This is especially important for creating bug-fix releases for major releases while still allowing work on the next major release to continue. It is also very nice for a developer's personal workflow.
* Easier path for contributors to submit changes and developers to integrate them;
* Much better support for everyday tasks like searching the project history for changes, viewing changes, bisecting the project history to find the original source of a bug.

Also, as noted before, the CVS servers had a hardware failure on May 2010, speeding up FlightGear's change to Git.

== Repositories and Branches ==
For historical reasons there continue to be separate repositories for SimGear and FlightGear source. There are 3 interesting branches in the repositories. Listed in order from least stable to most:
* <tt>next</tt> The current tip of new development. This branch should always compile and run, but various things could be broken.
* <tt>master</tt> The tip of stable, tested new features. If we were to make a new release today, we would start from the tip of this branch. New features that have been "cooking" in the <tt>next</tt> branch for a few days or weeks will be merged here.
* <tt>maint</tt> Bug fixes for the most recently released Flightgear. When a release is made from <tt>master</tt>, this branch is reset to it.

This arrangement follows the scheme used by the Git maintainers.
[http://www.kernel.org/pub/software/scm/git/docs/howto/maintain-git.txt This description] is very technical; you will surely have achieved git-fu if completely understand it. However, the idea of maintaining several branches of different stability is common in collaborative software projects.

== Clone and handle Repositories ==
=== Quick checkout ===
# Check on gitorious for valid projects: http://gitorious.org/fg
# Cloning Simgear
# Cloning FlightGear
# Cloning FGData

By default you will be checking out the <tt>next</tt> branch of SimGear and FlightGear. This is probably what you want if you want to assist with reporting bugs and the like before they are release as a proper release version.

=== For dummies ===
Some basic git commands on how to clone, update and handle local git repositories. Except the initial ''git clone'' for each repository all commands have to be executed from within the ''target'' folder.<BR>

==== Cloning SimGear ====
;<code>git clone git://gitorious.org/fg/simgear.git [target]</code>
: the folder ''target'' will be created and a clone of the SimGear repo stored inside it. If no ''target'' is given the new folder's name is <code>simgear</code>.

<b><code>cd</code></b> into the new folder. You are then inside the ''working tree'' of this git repo. The repo itself is stored inside the subfolder <tt>.git</tt>, which we mustn't edit manually. Git will take care of that.

;<code>git branch</code>
: will show the active [[FlightGear_and_Git#Repositories and Branches|branch]]. Right after download this will be <tt>* next</tt>, that means the content of the ''working tree'' is the bleeding edge of SimGear's source code.
:;<code>git branch -a</code>
:: will list all branches of a git repository. The one marked with an asterisk (*) is the active one.

;<code>git checkout master</code>
: will change the active [[FlightGear_and_Git#Repositories_and_Branches|branch]] to <tt>master</tt>. Means, that the content of the ''working tree'' will be changed to that state.

:;<code>git checkout v2.0.0</code>
:: will activate the state of the code inside the <tt>master</tt> branch at the time FG 2.0.0 was released.
:;<code>git tag</code>
:: will show all tags of the history of the active branch.

;<code>git pull</code>
: will update the local repo from the remote one.

==== Cloning FlightGear ====
Except for the initial clone command this is identic to [[FlightGear_and_Git#Cloning_SimGear|Cloning SimGear]].
;<code>git clone git://gitorious.org/fg/flightgear.git [target]</code>
To successfully compile <code>fgfs</code> Flight- and SimGear's ''working tree'' must have the same state.

==== Cloning fgdata ====
At the time of writing the data repository is about ''2.6 GB''. Continuing an interrupted cloning of a repository is <b>not supported</b> with git. Therefore, if you have a slow or unstable connection to the internet, it is recommended to download the [[FlightGear_and_Git#fgdata.bundle|fgdata.bundle]].

Also have in mind, that the repository plus the ''working tree'' will be more than twice the size of the download on your local filesystem.

There is neither a <tt>next</tt> branch nor any tags in that repository. If you want to build FlightGear 2.0.0 you may fetch the data (FlightGear-data-2.0.0.tar.bz2) at one of the [http://flightgear.org/mirrors.html mirrors].

;<code>git clone git://mapserver.flightgear.org/fgdata/ [target]</code>
: if no ''target'' is given the new folder's name is <tt>fgdata</tt>
<b><code>cd</code></b> into the new directory and verify it's state with <b><code>git branch</code></b>. If it isn't <tt>* master</tt>, do a <b><code>git checkout master</code></b>.

==== Local Branch ====
To make individual changes, like editing a joystick file or add a plane to fgdata or patch the source code, it is recommended to create a local branch inside that repository. The following commands will describe a way to achieve this. But have in mind, that this is very basic and only suits for users who have minor changes.

<b><code>cd</code></b> into the repositories folder, e.g. fgdata:
;<code>git checkout -b master.local master</code>
: a new branch <tt>master.local</tt> is created out of the <tt>master</tt> branch and set as the active one. You may now apply your individual stuff there and start FlightGear to verify the changes are propper.

If you conclude they are, you have to tell git about those changes:
;<code>git status</code>
: will give you a list of files that have been altered or that are new.

;<code>git add -i</code>
: will show the files that have been altered and give you options on what to do next. <code>git add</code> does not actually add the changes to ''master.local'' but adds them to the ''index''.
: <b><tt>[a]dd</tt></b> will add new paths/files (called ''untracked'' in status) from the ''working tree'' to the ''index''. This has to be done only if you have added paths/files, like an aircraft, to the ''working tree''.
: If git finds more than one ''untracked'' file/path, it will give you a numbered list and prompt to select which ones should be added. An empty input will exit this mode. See "Interactive mode" in [http://www.kernel.org/pub/software/scm/git/docs/git-add.html man git add] for more details.
: <b><tt>[u]pdate</tt></b> is the next step and will update the altered and ''tracked'' files to the index in the same manner as explained in <tt>add</tt> untracked paths above.
;<code>git commit</code>
: will commit the ''indexed'' updates to the ''master.local'' branch. It opens a list of the updates in your standard editor. You may add a comment to that file describing the object of the commit. Save and exit the editor. You have now commited your changes inside the ''working tree'' to your personal branch.

To update that personal branch from the remote one do the following steps:
git checkout master # switch to master branch
git pull # update it
git checkout master.local # switch back to the individual branch
git rebase master # update it

==== Some more helpful commands ====
;<code>git help</code>
;<code>git help [commad]</code>
;<code>git apply</code>
: apply a patch to files and/or to the index http://www.kernel.org/pub/software/scm/git/docs/git-apply.html
;<code>git checkout -f</code>
: may be used to throw away any local changes to the ''working tree''. Use with care, as any option that name is <tt>-f</tt> or <tt>--force</tt>, and only after reading <code>git checkout help</code>!

=== fgdata.bundle ===
For the FlightGear-data there are also bundles (snapshots) available that can be retrieved with your favourite download manager. This way you can resume interrupted downloads. After unpacking only a comparatively small amount of data has to be transferred from the git server to synchronize your repository.

Download the bundle from
$ wget http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle
or
$ wget http://peter-server.homelinux.net/fgdata/fgdata/fgdata.bundle

The bundle may be periodically updated and bundles from different sources need not be the same. The file size for the above bundle dated 2010-06-09 is 2394168314, while the md5 checksum is
$ md5sum fgdata.bundle
2996221bd2b8ab7740f332f49396cf56 fgdata.bundle

Do the following steps to extract the bundle and bring the repository up to date:
$ git clone fgdata.bundle fgdata
Initialized empty Git repository in fgdata/.git/
warning: unrecognized header: -deg" - /orientation/roll += "-deg" - /position/altitude += "-ft" - /position/altitude-agl += "-ft" - /position/latitude += "-deg" --/position/longitude += "-deg" - /radios/adf/frequencies/selected += "-khz" - /radios/adf/frequencies/
warning: remote HEAD refers to nonexistent ref, unable to checkout.
$ cd fgdata
$ git branch master-tmp origin/master
Branch master-tmp set up to track remote branch refs/remotes/origin/master.
$ git remote rm origin
$ git remote add origin git://gitorious.org/fg/fgdata
$ git fetch origin
remote: Counting objects: 5596, done.
remote: Compressing objects: 100% (2919/2919), done.
remote: Total 4266 (delta 2540), reused 2166 (delta 1297)
Receiving objects: 100% (4266/4266), 117.93 MiB | 1374 KiB/s, done.
Resolving deltas: 100% (2540/2540), completed with 628 local objects.
From git://gitorious.org/fg/fgdata
* [new branch] PRE_OSG_PLIB_20061029 -> origin/PRE_OSG_PLIB_20061029
* [new branch] master -> origin/master
* [new tag] last-cvs -> last-cvs
* [new tag] mapserver -> mapserver
$ git branch -D master-tmp
Deleted branch master-tmp.
$ git branch --track master origin/master
Branch master set up to track remote branch refs/remotes/origin/master.
$ git checkout

If you get an error at <b><code>git fetch origin</code></b> try:
$ git remote rm origin
$ git remote add origin git://mapserver.flightgear.org/fgdata/
$ git fetch origin

For future updates just do a <b><code>git pull</code></b>.

==External links==
=== Git tutorials and resources ===
* Git [http://git-scm.com/documentation documentation and tutorials]
* Git as a [http://tomayko.com/topics/git way of life].
* The [https://git.wiki.kernel.org/index.php/GitCheatSheet Git Cheat Sheet] and the [http://jan-krueger.net/development/git-cheat-sheet-extended-edition Git Cheat Sheet Extended Edition]
* [http://wiki.github.com/bogolisk/egg Egg], a cool Git emacs mode.
* A guide to [http://nathanj.github.com/gitguide/ using Git on Windows]
* [http://kylecordes.com/2008/04/30/git-windows-go/ Git on Windows Go!] (Setting up msysgit on Windows)
* [http://gitcasts.com/posts/git-on-windows Git on Windows (webcast)]
* [http://sourceforge.net/projects/qgit qgit - interactive git repository viewer and frontend]
* Additional [[Resources WRT running git on Win32]]

{{Building}}

[[Category:FlightGear]]

File:P51d-mustang.png

2010-06-29T05:14:46Z

Paul Richter: uploaded a new version of "File:P51d-mustang.png": Reverted to version as of 05:12, 18 December 2009 which actually shows the plane better

Screenshot of P51D

File:A-10.jpg

2010-06-29T05:13:06Z

Paul Richter: uploaded a new version of "File:A-10.jpg": Reverted to version as of 12:20, 15 August 2006 Who the hell is Fahim?

Fairchild A-10 Thunderbolt II

File:Hawker Seahawk.jpg

2010-06-29T05:10:29Z

Paul Richter: uploaded a new version of "File:Hawker Seahawk.jpg": Reverted to version as of 12:12, 9 October 2007 - let's just stick to a clean, illustrative image.

Screenshot of Hawker Seahawk

North American P-51 Mustang

2010-06-29T05:06:01Z

Paul Richter: /* Development status/Issues/Todo */ vertical tail texture is mirrored

{{infobox Aircraft
|image = P51d-mustang.png
|name = P51D Mustang
|type = Military aircraft
|fdm = YASim
|status =
|authors = Jim Wilson
|fgname = <tt>p51d</tt>
|download = http://www.flightgear.org/Downloads/aircraft/#p51
|
}}

The P-51D is a piston single engine fighter [[aircraft]];a well-developed warbird for FG v1.0.0.
{|
|__TOC__
|}
==Aircraft Help==
=== Flying Hints ===

NOTE: the yasim config file for this aircraft currently starts up with the booster in 1st stage.

==== Take Off ====

*Set prop pitch to full increased rpm.
*Start engine with throttle at idle.
*Set BOOST stage one (CTRL-b keybinding cycles through stage 0 (off),1, and 2). Default startup for p51-d should have stage one already on.

*Set throttle to 40 inHG Manifold Pressure (MP).

*Be ready to actuate rudder. When the tail first lifts, the torque will pull the nose to the left.
*After tail lifts off slowing move throttle to full open which with stage 1 booster engaged should be about 61 inHG Manifold Pressure.
*Hang on. Stay on top of rudder control with small adjustments or you'll do a ground loop.
*Rotate at 150 mph or so.

==== Climb ====

*Back off MP to 46 inHG. *Adjust propeller pitch to 2700 rpm.
*Keep adding throttle as you climb to maintain 46 inHG until you hit full throttle.
*At 18,000 feet turn on second stage (hit CTRL-b) and back off throttle to 46 inHG.

==== Flying ====

*Trim and Cruise at about 2400 rpm.
*Do not exceed 2700 rpm sustained.
*Do not exceed 3000 rpm military power (aerobatics)
*Do not exceed 3500 rpm in dives.
*Do not exceed 61 inHG Mainfold Pressure (military power), except 71 inHG for maximum of 7 minutes (war emergency power). Note that war emergency power is not for flying fast, rather it is for dogfighting at < 200mph.

==== Landing ====

*A single long sweeping turn from the downwind leg into a short approach seems to work best. Make sure you are below 250mph before starting the turn. Use forward slip as necessary to bleed off speed and altitude at the same time.
* Start applying flaps at 250mph, gear at 175mph, and full flaps at 165mph or less.
*Excessive braking can cause you to nose over. Some recommend raising flaps immediately after touchdown.

=== Performance Data ===

This information is gleaned from various sources:
Maximum Speed: 437 mph

Cruise Speed: 363 mph

Landing Speed: 100 mph

Initial Climb Rate: 3475 feet per minute
Sustained Climb Speed: 175 mph

Service Ceiling: 41,900 (with 2nd Stage booster).

Stall Speed (9000lbs) Gear/Flaps Up: 102mph Gear/Flaps Down: 95mph

== Development status/Issues/Todo ==
Outside:

* front wheels rotate even when airplane is standing still
* when flaps are lowered, you can see inside the 3d model were the flaps where before
* no cockpit light at night visible
* propeller rotates in wrong direction from some view points
* aircraft has no shadow
* landing lights and strobe lights are missing
* aircraft has no wheel well area for the landing gears

3d Cockpit:

* no cockpit light at night available
* no rudder control pedals available
* switches and levers can't be controlled with mouse
* cockpit is only partly textured (sidewalls and cockpit fron have no textures)
* no pilot present in cockpit

General:

* engine sound in cockpit does not differ from outside engine sound
* no hud available

Texture:
* Vertical tail texture is mirrored

== Related lists ==
* [[Aircraft]]
* [[Aircraft Todo]]
* [[Table of models]]
* [[FlightGear 1.0 default aircraft]]

==External links==
*[http://www.vectorsite.net/avp51.html The North American P-51 Mustang (vectorsite.net)]

{{North American}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Understanding Propeller Torque and P-Factor

2010-06-29T05:01:45Z

Paul Richter: /* Prop wash */ rm redundant

This is an attempt to answer the frequent question "Why is my aircraft turning left all the time?"

This occurs only in aircraft with propellers at the front of the aircraft. And, yes, it does occur in real life. Three distinct phenomena cause the effect, all causing the aircraft to turn in the same direction. They are:

==Prop wash==
A propeller pushes air not just horizontally to the back, but more in a twisting helix around the [http://en.wikipedia.org/wiki/Fuselage fuselage] (clockwise as seen from the cockpit). As the air whirls around the fuselage it pushes against the left side of the vertical tail (assuming it is located above the propeller's axis), causing the plane to yaw to the left. The prop wash effect is at its greatest when the airflow is flowing more around the fuselage than along it, i.e., at high power and low airspeed, which is the situation when starting the takeoff run.

==Propeller Torque Effect==

Torque effect is the influence of engine torque on aircraft movement and control. It is generally exhibited as a left turning tendency in piston single engine propeller driven aircraft.

According to Newton's law, "for every action there is an equal and opposite reaction," such that the propeller, if turning clockwise (when viewed from the cockpit), imparts a tendency for the aircraft to rotate counterclockwise. Since most single engine aircraft have propellers rotating clockwise, they rotate to the left, pushing the left wing down.

Typically, the pilot is expected to counter this force through the control inputs. To counter the aircraft roll left, the pilot applies right aileron.

It is important to understand that torque is a movement about the roll axis. Aileron controls roll. Prop torque is not countered by moving the rudder or by setting rudder trim. It is countered by moving or trimming the aileron.

This correction induces adverse yaw, which is corrected by moving or trimming the rudder (right rudder).

On aircraft with contrarotating propellers (propellers that rotate in opposite directions) the torque from the two propellers cancel each other out, so that no compensation is needed.

Further Reading: [http://www.aerospaceweb.org/question/dynamics/q0015a.shtml Propeller Torque Factor]

== P-Factor ==

P-factor is the term for asymmetric propeller loading, causes the airplane to yaw to the left when at high angles of attack.

The descending right side of the propeller (as seen from the rear) has a higher angle of attack than the upward-moving blade on the left side and provides more thrust. This occurs only when the propeller is not meeting the oncoming airflow head-on, for example when an aircraft is moving down the runway at a nose-high attitude (i.e. at a high angle of attack), as is the case with tail-draggers. Aircraft with tricycle landing gear maintain a level attitude on the takeoff roll run, so there is little P-factor during takeoff roll until lift off. In all cases, though, the effect is weaker than prop wash.

According to What You Need to Know About Aerodyanics... by Franklin Gutierrez.

== Gyroscopic Precession ==

This is the tendency of a spinning object to precess or move about its axis when disturbed by a force. The engine and propeller act as a big gyroscope. However, gyroscopic precession is likely to be minimal in a typical aircraft.

Gyroscopic precession is frequently confused with p-factor.

One author maintains p-factor is caused by a combination of factors unrelated to gyroscopic precession http://home.earthlink.net/~x-plane/FAQ-Theory-PFactor.html

== External Links ==

* [http://www.auf.asn.au/groundschool/umodule11.html#tophenomena Engine effects and aerodynamic phenomena] Recreational Aviation Australia Ground School article on "prop wash," prop torque, gyro precession, p-factor and other similar factors affecting taildraggers.

* [http://www.americanparagliding.com/propellerforces.htm http://www.americanparagliding.com/propellerforces.htm] The forces of P-factor, gyro precession and asymmetric blade thrust act with particular intensity in powere parachute gliders (paragliders), as this article relates.

{{Understanding}}

Understanding Propeller Torque and P-Factor

2010-06-29T05:01:14Z

Paul Richter: /* Prop wash */ vert-tail above prop axis

This is an attempt to answer the frequent question "Why is my aircraft turning left all the time?"

This occurs only in aircraft with propellers at the front of the aircraft. And, yes, it does occur in real life. Three distinct phenomena cause the effect, all causing the aircraft to turn in the same direction. They are:

==Prop wash==
A propeller pushes air not just horizontally to the back, but more in a twisting helix around the [http://en.wikipedia.org/wiki/Fuselage fuselage] (clockwise as seen from the cockpit). As the air whirls around the fuselage it pushes against the left side of the vertical tail (assuming that the vertical tail is located above the propeller's axis), causing the plane to yaw to the left. The prop wash effect is at its greatest when the airflow is flowing more around the fuselage than along it, i.e., at high power and low airspeed, which is the situation when starting the takeoff run.

==Propeller Torque Effect==

Torque effect is the influence of engine torque on aircraft movement and control. It is generally exhibited as a left turning tendency in piston single engine propeller driven aircraft.

According to Newton's law, "for every action there is an equal and opposite reaction," such that the propeller, if turning clockwise (when viewed from the cockpit), imparts a tendency for the aircraft to rotate counterclockwise. Since most single engine aircraft have propellers rotating clockwise, they rotate to the left, pushing the left wing down.

Typically, the pilot is expected to counter this force through the control inputs. To counter the aircraft roll left, the pilot applies right aileron.

It is important to understand that torque is a movement about the roll axis. Aileron controls roll. Prop torque is not countered by moving the rudder or by setting rudder trim. It is countered by moving or trimming the aileron.

This correction induces adverse yaw, which is corrected by moving or trimming the rudder (right rudder).

On aircraft with contrarotating propellers (propellers that rotate in opposite directions) the torque from the two propellers cancel each other out, so that no compensation is needed.

Further Reading: [http://www.aerospaceweb.org/question/dynamics/q0015a.shtml Propeller Torque Factor]

== P-Factor ==

P-factor is the term for asymmetric propeller loading, causes the airplane to yaw to the left when at high angles of attack.

The descending right side of the propeller (as seen from the rear) has a higher angle of attack than the upward-moving blade on the left side and provides more thrust. This occurs only when the propeller is not meeting the oncoming airflow head-on, for example when an aircraft is moving down the runway at a nose-high attitude (i.e. at a high angle of attack), as is the case with tail-draggers. Aircraft with tricycle landing gear maintain a level attitude on the takeoff roll run, so there is little P-factor during takeoff roll until lift off. In all cases, though, the effect is weaker than prop wash.

According to What You Need to Know About Aerodyanics... by Franklin Gutierrez.

== Gyroscopic Precession ==

This is the tendency of a spinning object to precess or move about its axis when disturbed by a force. The engine and propeller act as a big gyroscope. However, gyroscopic precession is likely to be minimal in a typical aircraft.

Gyroscopic precession is frequently confused with p-factor.

One author maintains p-factor is caused by a combination of factors unrelated to gyroscopic precession http://home.earthlink.net/~x-plane/FAQ-Theory-PFactor.html

== External Links ==

* [http://www.auf.asn.au/groundschool/umodule11.html#tophenomena Engine effects and aerodynamic phenomena] Recreational Aviation Australia Ground School article on "prop wash," prop torque, gyro precession, p-factor and other similar factors affecting taildraggers.

* [http://www.americanparagliding.com/propellerforces.htm http://www.americanparagliding.com/propellerforces.htm] The forces of P-factor, gyro precession and asymmetric blade thrust act with particular intensity in powere parachute gliders (paragliders), as this article relates.

{{Understanding}}

Landmark Wish List

2010-06-29T00:19:40Z

Paul Richter: Christ the Redeemer statue claimed by Paul Richter

This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.

Feel free to add to this list.

If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".

{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" | Landmark
! style="background:#efefef" | City
! style="background:#efefef" | Country
! style="background:#efefef" | Completed
|-
|Sydney Opera House || Sydney || Australia || No
|-
|National Congress || Brasilia || Brazil || '''Claimed'''
|-
|Christ the Redeemer || Rio de Janeiro || Brazil || '''Claimed'''
|-
|Bank of China Tower || Hong Kong || China || No
|-
|CCTV Tower || Beijing || China || No
|-
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || '''CS done'''
|-
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No
|-
|Lapan || Oldenburg, Niedersachsen || Germany || No
|-
|Schloss || Oldenburg || Germany || No
|-
|Taj Mahal || Agra || India || No
|-
|Colosseum || Rome || Italy || No
|-
|Petronas Towers || Kuala Lumpur || Malaysia || No
|-
|Sky Tower || Auckland || New Zealand || '''Claimed'''
|-
|Ryugyong Hotel || Pyongyang || North Korea || No
|-
|Oeresund Bridge || Copenhagen-Malmo || Scandinavia || '''yes'''
|-
|Burj Dubai || Dubai || UAE || No
|-
|Burj al Arab || Dubai || UAE || No
|-
|Big Ben || London || UK || '''Yes'''
|-
|Westminster Abbey || London || UK || '''Yes'''
|-
|Navy Pier || Chicago || USA || No
|-
|Adler Planetarium || Chicago || USA || No
|-
|Soldier Field || Chicago || USA || No
|-
|McCormick Place || Chicago || USA || No
|-
|U.S. Cellular Field || Chicago || USA || No
|-
|Wrigley Field || Chicago || USA || No
|-
|Shedd Aquarium || Chicago || USA || No
|-
|Union Station || Chicago || USA || No
|-
|Oglivie Transportation Center || Chicago || USA || No
|-
|Smurfit-Stone Building || Chicago || USA || No
|-
|Marina City || Chicago || USA || No
|-
|Millenium Park || Chicago || USA || No
|-
|United Center || Chicago || USA || No
|-
|Brooklyn Bridge || New York || USA || No
|-
|Empire State Building || New York || USA || '''Claimed'''
|-
|Chrysler Building || New York || USA || No
|-
|United Nations Headquarters || New York || USA || No
|-
|White House || Washington, D.C. || USA || No
|-
|Space Needle || Seattle || USA || '''Yes'''
|-
|Milwaukee Art Museum || Milwaukee || USA || No
|}

==Related==

===Internal links===
*[[FlightGear Scenery Designer]]
*[[FlightGear Scenery Database]]
*[[UK_Scenery_Wish_List]]
===External links===
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]

[[Category:Scenery]]
[[Category:Community]]

Livery

2010-06-28T05:46:18Z

Paul Richter: /* Models/Liveries */ Rescue -> KLM

[[Image:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

==Files==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

===Models/Liveries===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<texture>Liveries/KLM.png</texture>
</livery>
</model>
</sim>
</PropertyList>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft.

===Models/....xml===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>

===Nasal/liveries.nas===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

===...-set.xml===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the approperiate livery.

<file type="string">ANA</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

==Multiple texture files per livery==
Some models use multiple textures file (eg. seperate files for wings and fuselage). Every texture needs it own property. You can add as many textures as you like.

===Nasal/liveries.nas===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

===Models/Liveries===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture>ANA-Livery.png</texture>
<lights>ANA-Lights.rgb</lights>
</livery>
</model>
</sim>
</PropertyList>

Remember the names (<texture> and <lights>), as you will need them in the model file in the next step.

===Models/....xml===
<animation>
<type>material</type>
<object-name>wipers</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>ANA-Livery.rgb</texture>
</animation>

<animation>
<type>material</type>
<object-name>lightedfin_0</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>lights</texture-prop>
<texture>ANA-Lights.rgb</texture>
</animation>

Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

===...-set.xml===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

==Performance Improvements==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

==Testing==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

==Sharing your liveries==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

Aircraft

2010-06-10T23:52:32Z

Paul Richter: Move Saab 35 to Modern

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for FlightGear 1.9.0, but gives a visual sampling of the different types of aircraft and genres of aircraft officially available. See [[Table of models]] for the comprehensive list. See also [[FlightGear hangars]] for non-official hangars (or [[Helicopters]], or [[Vehicles]] for more visual examples)

The examples listed here are officially available from the FlightGear project, and can be downloaded at [http://www.flightgear.org/Downloads/aircraft/ FlightGear.org Aircraft], with installation typically requiring an unzipping program, and manual installation in the FlightGear aircraft directory (if they are not already [[FlightGear 1.0 default aircraft|included]]).

FlightGear aircraft features, quality, and compatibility vary significantly;their development is dependent on the volunteers who worked on them, with exception of some University and Government funded projects.

Remember this list is merely a sampling of the many aircraft and variants available for FlightGear!

===Light civilian aircraft===
The Cessna 172 is the default aircraft in FGFS 1.0. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Gallery|
[[Aerostar 700]]|Aerostar_700.jpg|
[[B&F FK9 Mark 2]]|FK9MK2.jpg|
[[Cessna C172|Cessna 172P]] (1982)|Cessna_172P.jpg|
[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]] (1946) |Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]|Piper_SenecaII.jpg|
[[Robin DR400]]|dr400.jpg|
[[Rallye-MS893E]]|Rallye-MS893.jpg
}}

===Modern Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]). In addition, avionics in real life is geared towards those with professional pilots licenses and special certifications. However, the simplifications of FG make it much easier to fly in the simulation.

====Narrowbody & Midsize====
{{Gallery|
[[Airbus A320]]|FirstChoice02.jpg|
[[Concorde]]|Concorde.jpg|
[[Boeing 757]]|757-2002.jpg|
[[Boeing 707]]|707.jpg|
[[Boeing 717]]|717_development.jpg|
[[Boeing 737-100]]|737-100.png|
[[Boeing 727-230]]|727-230.2.jpeg
}}

====Widebody & Jumbo Airliners====

{{Gallery|
[[Airbus A340-600]]|Airbus2.jpg|
[[Airbus A380]]|A380.jpg|
[[Boeing 777-200]]|777-200.jpg|
[[Boeing 767-300]]|Shadow.png|
[[Boeing 747-400]]|747-400.jpg|
[[Boeing 787]]|787.jpg|
[[Airbus A350]]|A350.png|
[[IL-96-400 Long Ranger(T)]]|1z5hr43.bmp
}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Gallery|
[[Eurocopter Bo105|MBB Bo 105]]|FlightGearNL-9.jpg|
[[Eurocopter EC135|Eurocopter EC-135]]|Ec135.png|
[[CH-47 Chinook Helicopter|Boeing CH-47 Chinook]]|CH-47_Chinook.jpg|
[[Sikorsky S58|Sikorsky S-58]]|S58.jpg
}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying gliders or sailplanes using thermals (see [[Soaring]]) can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Gallery|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Dragonfly|Moyes Dragonfly]]|Dragonfly-towing.jpg|
[[Paraglider]]|Paraglider.jpg|
[[GDT Hornet (autogyro)]]|Hornet.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[ASW-20 sailplane|Schleicher ASW-20]]|Asw20.jpg|
[[Glaser-Dirks DG-300|Glaser-Dirks DG-300]]|DG-300.jpg
}}

===Warbirds===
FG includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Gallery|
[[Bristol Beaufighter]]|Beaufighter.png|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[P-51D Mustang]]|P51d-mustang.png|
[[A6M2 Zero‎]]|A6M2.gif|
[[Nakajima Ki-84‎]]|ki-84.jpg|
[[Focke-Wulf Fw 190]]|Fw190.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Supermarine Spitfire]]|Spitfire.jpg
}}

===Carrier-borne aircraft===
FG supports landing on and taking off from carriers (2 are available in FG 1.0.0).

{{Gallery|
[[Grumman A-6E|Grumman A-6E Intruder]]|A-6E.jpg|
[[Blackburn Buccaneer]]|Buccaneer.jpg|
[[Grumman F-14 Tomcat]]|F-14.jpg|
[[Hawker Seahawk|Hawker Seahawk FGA6]]|Hawker_Seahawk.jpg
}}

===Modern military aircraft===
FG has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the the venerable KC-135 and the ability to simulate A-10 ordnance release.

{{Gallery|
[[Fairchild A-10]]|A-10.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[Boeing E-3 Sentry]]|E-3B.jpg|
[[F-15C Eagle]]|F-15C.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Cessna T-37]]|Cessna T-37.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg|
[[Saab J 35Ã– Draken|Saab J35Ö Draken]]|Saab_J35.jpg|
[[HAL Tejas]]|LCA.jpeg
}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Gallery|
[[Couzinet 70]]|Couzinet70.jpg|
[[De Havilland D.H. 91 Albatross]]|dh91.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Lockheed 1049|Lockheed Constellation]]|Lockheed_1049.jpg|
[[Boeing 314]]|314.jpg|
[[de Havilland Canada DHC-3 Otter]]|DHC-3.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg
}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Gallery|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]|V22Osprey.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg
}}

===Lighter than air aircraft (Available from version 1.9.0)===

These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.

{{Gallery|
[[Zeppelin NT]]|Zeppelin_NT.jpg|
[[ZF Navy free balloon]]|ZF_Navy_free_balloon.jpg|
[[Submarine Scout]]|Submarine_Scout.jpg
}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Gallery|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Bluebird]]|bluebird_hovercraft.jpg
}}

==Related==
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]
*[[Howto: Multiplayer]], [[Installing Scenery]], and [[Flying the Helicopter]].

[[Category:List]]

[[es:Avión]]
[[fr:Avions]]
[[pt:Avião]]

Aircraft

2010-06-10T23:43:46Z

Paul Richter: /* NATO military aircraft */ -> Modern ; no reason to limit it to NATO

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for FlightGear 1.9.0, but gives a visual sampling of the different types of aircraft and genres of aircraft officially available. See [[Table of models]] for the comprehensive list. See also [[FlightGear hangars]] for non-official hangars (or [[Helicopters]], or [[Vehicles]] for more visual examples)

The examples listed here are officially available from the FlightGear project, and can be downloaded at [http://www.flightgear.org/Downloads/aircraft/ FlightGear.org Aircraft], with installation typically requiring an unzipping program, and manual installation in the FlightGear aircraft directory (if they are not already [[FlightGear 1.0 default aircraft|included]]).

FlightGear aircraft features, quality, and compatibility vary significantly;their development is dependent on the volunteers who worked on them, with exception of some University and Government funded projects.

Remember this list is merely a sampling of the many aircraft and variants available for FlightGear!

===Light civilian aircraft===
The Cessna 172 is the default aircraft in FGFS 1.0. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Gallery|
[[Aerostar 700]]|Aerostar_700.jpg|
[[B&F FK9 Mark 2]]|FK9MK2.jpg|
[[Cessna C172|Cessna 172P]] (1982)|Cessna_172P.jpg|
[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]] (1946) |Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]|Piper_SenecaII.jpg|
[[Robin DR400]]|dr400.jpg|
[[Rallye-MS893E]]|Rallye-MS893.jpg
}}

===Modern Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]). In addition, avionics in real life is geared towards those with professional pilots licenses and special certifications. However, the simplifications of FG make it much easier to fly in the simulation.

====Narrowbody & Midsize====
{{Gallery|
[[Airbus A320]]|FirstChoice02.jpg|
[[Concorde]]|Concorde.jpg|
[[Boeing 757]]|757-2002.jpg|
[[Boeing 707]]|707.jpg|
[[Boeing 717]]|717_development.jpg|
[[Boeing 737-100]]|737-100.png|
[[Boeing 727-230]]|727-230.2.jpeg
}}

====Widebody & Jumbo Airliners====

{{Gallery|
[[Airbus A340-600]]|Airbus2.jpg|
[[Airbus A380]]|A380.jpg|
[[Boeing 777-200]]|777-200.jpg|
[[Boeing 767-300]]|Shadow.png|
[[Boeing 747-400]]|747-400.jpg|
[[Boeing 787]]|787.jpg|
[[Airbus A350]]|A350.png|
[[IL-96-400 Long Ranger(T)]]|1z5hr43.bmp
}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Gallery|
[[Eurocopter Bo105|MBB Bo 105]]|FlightGearNL-9.jpg|
[[Eurocopter EC135|Eurocopter EC-135]]|Ec135.png|
[[CH-47 Chinook Helicopter|Boeing CH-47 Chinook]]|CH-47_Chinook.jpg|
[[Sikorsky S58|Sikorsky S-58]]|S58.jpg
}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying gliders or sailplanes using thermals (see [[Soaring]]) can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Gallery|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Dragonfly|Moyes Dragonfly]]|Dragonfly-towing.jpg|
[[Paraglider]]|Paraglider.jpg|
[[GDT Hornet (autogyro)]]|Hornet.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[ASW-20 sailplane|Schleicher ASW-20]]|Asw20.jpg|
[[Glaser-Dirks DG-300|Glaser-Dirks DG-300]]|DG-300.jpg
}}

===Warbirds===
FG includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Gallery|
[[Bristol Beaufighter]]|Beaufighter.png|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[P-51D Mustang]]|P51d-mustang.png|
[[A6M2 Zero‎]]|A6M2.gif|
[[Nakajima Ki-84‎]]|ki-84.jpg|
[[Focke-Wulf Fw 190]]|Fw190.jpg|
[[Saab J 35Ã– Draken|Saab J35Ö Draken]]|Saab_J35.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Supermarine Spitfire]]|Spitfire.jpg
}}

===Carrier-borne aircraft===
FG supports landing on and taking off from carriers (2 are available in FG 1.0.0).

{{Gallery|
[[Grumman A-6E|Grumman A-6E Intruder]]|A-6E.jpg|
[[Blackburn Buccaneer]]|Buccaneer.jpg|
[[Grumman F-14 Tomcat]]|F-14.jpg|
[[Hawker Seahawk|Hawker Seahawk FGA6]]|Hawker_Seahawk.jpg
}}

===Modern military aircraft===
FG has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the the venerable KC-135 and the ability to simulate A-10 ordnance release.

{{Gallery|
[[Fairchild A-10]]|A-10.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[Boeing E-3 Sentry]]|E-3B.jpg|
[[F-15C Eagle]]|F-15C.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Cessna T-37]]|Cessna T-37.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg|
[[HAL Tejas]]|LCA.jpeg
}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Gallery|
[[Couzinet 70]]|Couzinet70.jpg|
[[De Havilland D.H. 91 Albatross]]|dh91.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Lockheed 1049|Lockheed Constellation]]|Lockheed_1049.jpg|
[[Boeing 314]]|314.jpg|
[[de Havilland Canada DHC-3 Otter]]|DHC-3.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg
}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Gallery|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]|V22Osprey.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg
}}

===Lighter than air aircraft (Available from version 1.9.0)===

These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.

{{Gallery|
[[Zeppelin NT]]|Zeppelin_NT.jpg|
[[ZF Navy free balloon]]|ZF_Navy_free_balloon.jpg|
[[Submarine Scout]]|Submarine_Scout.jpg
}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Gallery|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Bluebird]]|bluebird_hovercraft.jpg
}}

==Related==
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]
*[[Howto: Multiplayer]], [[Installing Scenery]], and [[Flying the Helicopter]].

[[Category:List]]

[[es:Avión]]
[[fr:Avions]]
[[pt:Avião]]

Aircraft

2010-06-10T23:41:04Z

Paul Richter: /* Warbirds */ Fw190

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for FlightGear 1.9.0, but gives a visual sampling of the different types of aircraft and genres of aircraft officially available. See [[Table of models]] for the comprehensive list. See also [[FlightGear hangars]] for non-official hangars (or [[Helicopters]], or [[Vehicles]] for more visual examples)

The examples listed here are officially available from the FlightGear project, and can be downloaded at [http://www.flightgear.org/Downloads/aircraft/ FlightGear.org Aircraft], with installation typically requiring an unzipping program, and manual installation in the FlightGear aircraft directory (if they are not already [[FlightGear 1.0 default aircraft|included]]).

FlightGear aircraft features, quality, and compatibility vary significantly;their development is dependent on the volunteers who worked on them, with exception of some University and Government funded projects.

Remember this list is merely a sampling of the many aircraft and variants available for FlightGear!

===Light civilian aircraft===
The Cessna 172 is the default aircraft in FGFS 1.0. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Gallery|
[[Aerostar 700]]|Aerostar_700.jpg|
[[B&F FK9 Mark 2]]|FK9MK2.jpg|
[[Cessna C172|Cessna 172P]] (1982)|Cessna_172P.jpg|
[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]] (1946) |Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]|Piper_SenecaII.jpg|
[[Robin DR400]]|dr400.jpg|
[[Rallye-MS893E]]|Rallye-MS893.jpg
}}

===Modern Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]). In addition, avionics in real life is geared towards those with professional pilots licenses and special certifications. However, the simplifications of FG make it much easier to fly in the simulation.

====Narrowbody & Midsize====
{{Gallery|
[[Airbus A320]]|FirstChoice02.jpg|
[[Concorde]]|Concorde.jpg|
[[Boeing 757]]|757-2002.jpg|
[[Boeing 707]]|707.jpg|
[[Boeing 717]]|717_development.jpg|
[[Boeing 737-100]]|737-100.png|
[[Boeing 727-230]]|727-230.2.jpeg
}}

====Widebody & Jumbo Airliners====

{{Gallery|
[[Airbus A340-600]]|Airbus2.jpg|
[[Airbus A380]]|A380.jpg|
[[Boeing 777-200]]|777-200.jpg|
[[Boeing 767-300]]|Shadow.png|
[[Boeing 747-400]]|747-400.jpg|
[[Boeing 787]]|787.jpg|
[[Airbus A350]]|A350.png|
[[IL-96-400 Long Ranger(T)]]|1z5hr43.bmp
}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Gallery|
[[Eurocopter Bo105|MBB Bo 105]]|FlightGearNL-9.jpg|
[[Eurocopter EC135|Eurocopter EC-135]]|Ec135.png|
[[CH-47 Chinook Helicopter|Boeing CH-47 Chinook]]|CH-47_Chinook.jpg|
[[Sikorsky S58|Sikorsky S-58]]|S58.jpg
}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying gliders or sailplanes using thermals (see [[Soaring]]) can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Gallery|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Dragonfly|Moyes Dragonfly]]|Dragonfly-towing.jpg|
[[Paraglider]]|Paraglider.jpg|
[[GDT Hornet (autogyro)]]|Hornet.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[ASW-20 sailplane|Schleicher ASW-20]]|Asw20.jpg|
[[Glaser-Dirks DG-300|Glaser-Dirks DG-300]]|DG-300.jpg
}}

===Warbirds===
FG includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Gallery|
[[Bristol Beaufighter]]|Beaufighter.png|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[P-51D Mustang]]|P51d-mustang.png|
[[A6M2 Zero‎]]|A6M2.gif|
[[Nakajima Ki-84‎]]|ki-84.jpg|
[[Focke-Wulf Fw 190]]|Fw190.jpg|
[[Saab J 35Ã– Draken|Saab J35Ö Draken]]|Saab_J35.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Supermarine Spitfire]]|Spitfire.jpg
}}

===Carrier-borne aircraft===
FG supports landing on and taking off from carriers (2 are available in FG 1.0.0).

{{Gallery|
[[Grumman A-6E|Grumman A-6E Intruder]]|A-6E.jpg|
[[Blackburn Buccaneer]]|Buccaneer.jpg|
[[Grumman F-14 Tomcat]]|F-14.jpg|
[[Hawker Seahawk|Hawker Seahawk FGA6]]|Hawker_Seahawk.jpg
}}

===NATO military aircraft===
FG has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the the venerable KC-135 and the ability to simulate A-10 ordnance release.

{{Gallery|
[[Fairchild A-10]]|A-10.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[Boeing E-3 Sentry]]|E-3B.jpg|
[[F-15C Eagle]]|F-15C.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Cessna T-37]]|Cessna T-37.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg|
[[HAL Tejas]]|LCA.jpeg
}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Gallery|
[[Couzinet 70]]|Couzinet70.jpg|
[[De Havilland D.H. 91 Albatross]]|dh91.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Lockheed 1049|Lockheed Constellation]]|Lockheed_1049.jpg|
[[Boeing 314]]|314.jpg|
[[de Havilland Canada DHC-3 Otter]]|DHC-3.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg
}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Gallery|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]|V22Osprey.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg
}}

===Lighter than air aircraft (Available from version 1.9.0)===

These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.

{{Gallery|
[[Zeppelin NT]]|Zeppelin_NT.jpg|
[[ZF Navy free balloon]]|ZF_Navy_free_balloon.jpg|
[[Submarine Scout]]|Submarine_Scout.jpg
}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Gallery|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Bluebird]]|bluebird_hovercraft.jpg
}}

==Related==
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]
*[[Howto: Multiplayer]], [[Installing Scenery]], and [[Flying the Helicopter]].

[[Category:List]]

[[es:Avión]]
[[fr:Avions]]
[[pt:Avião]]

Aircraft

2010-06-10T23:38:32Z

Paul Richter: /* Warbirds */ A6M2

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for FlightGear 1.9.0, but gives a visual sampling of the different types of aircraft and genres of aircraft officially available. See [[Table of models]] for the comprehensive list. See also [[FlightGear hangars]] for non-official hangars (or [[Helicopters]], or [[Vehicles]] for more visual examples)

The examples listed here are officially available from the FlightGear project, and can be downloaded at [http://www.flightgear.org/Downloads/aircraft/ FlightGear.org Aircraft], with installation typically requiring an unzipping program, and manual installation in the FlightGear aircraft directory (if they are not already [[FlightGear 1.0 default aircraft|included]]).

FlightGear aircraft features, quality, and compatibility vary significantly;their development is dependent on the volunteers who worked on them, with exception of some University and Government funded projects.

Remember this list is merely a sampling of the many aircraft and variants available for FlightGear!

===Light civilian aircraft===
The Cessna 172 is the default aircraft in FGFS 1.0. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Gallery|
[[Aerostar 700]]|Aerostar_700.jpg|
[[B&F FK9 Mark 2]]|FK9MK2.jpg|
[[Cessna C172|Cessna 172P]] (1982)|Cessna_172P.jpg|
[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]] (1946) |Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]|Piper_SenecaII.jpg|
[[Robin DR400]]|dr400.jpg|
[[Rallye-MS893E]]|Rallye-MS893.jpg
}}

===Modern Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]). In addition, avionics in real life is geared towards those with professional pilots licenses and special certifications. However, the simplifications of FG make it much easier to fly in the simulation.

====Narrowbody & Midsize====
{{Gallery|
[[Airbus A320]]|FirstChoice02.jpg|
[[Concorde]]|Concorde.jpg|
[[Boeing 757]]|757-2002.jpg|
[[Boeing 707]]|707.jpg|
[[Boeing 717]]|717_development.jpg|
[[Boeing 737-100]]|737-100.png|
[[Boeing 727-230]]|727-230.2.jpeg
}}

====Widebody & Jumbo Airliners====

{{Gallery|
[[Airbus A340-600]]|Airbus2.jpg|
[[Airbus A380]]|A380.jpg|
[[Boeing 777-200]]|777-200.jpg|
[[Boeing 767-300]]|Shadow.png|
[[Boeing 747-400]]|747-400.jpg|
[[Boeing 787]]|787.jpg|
[[Airbus A350]]|A350.png|
[[IL-96-400 Long Ranger(T)]]|1z5hr43.bmp
}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Gallery|
[[Eurocopter Bo105|MBB Bo 105]]|FlightGearNL-9.jpg|
[[Eurocopter EC135|Eurocopter EC-135]]|Ec135.png|
[[CH-47 Chinook Helicopter|Boeing CH-47 Chinook]]|CH-47_Chinook.jpg|
[[Sikorsky S58|Sikorsky S-58]]|S58.jpg
}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying gliders or sailplanes using thermals (see [[Soaring]]) can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Gallery|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Dragonfly|Moyes Dragonfly]]|Dragonfly-towing.jpg|
[[Paraglider]]|Paraglider.jpg|
[[GDT Hornet (autogyro)]]|Hornet.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[ASW-20 sailplane|Schleicher ASW-20]]|Asw20.jpg|
[[Glaser-Dirks DG-300|Glaser-Dirks DG-300]]|DG-300.jpg
}}

===Warbirds===
FG includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Gallery|
[[Bristol Beaufighter]]|Beaufighter.png|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[P-51D Mustang]]|P51d-mustang.png|
[[A6M2 Zero‎]]|A6M2.gif|
[[Nakajima Ki-84‎]]|ki-84.jpg|
[[Saab J 35Ã– Draken|Saab J35Ö Draken]]|Saab_J35.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Supermarine Spitfire]]|Spitfire.jpg
}}

===Carrier-borne aircraft===
FG supports landing on and taking off from carriers (2 are available in FG 1.0.0).

{{Gallery|
[[Grumman A-6E|Grumman A-6E Intruder]]|A-6E.jpg|
[[Blackburn Buccaneer]]|Buccaneer.jpg|
[[Grumman F-14 Tomcat]]|F-14.jpg|
[[Hawker Seahawk|Hawker Seahawk FGA6]]|Hawker_Seahawk.jpg
}}

===NATO military aircraft===
FG has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the the venerable KC-135 and the ability to simulate A-10 ordnance release.

{{Gallery|
[[Fairchild A-10]]|A-10.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[Boeing E-3 Sentry]]|E-3B.jpg|
[[F-15C Eagle]]|F-15C.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Cessna T-37]]|Cessna T-37.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg|
[[HAL Tejas]]|LCA.jpeg
}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Gallery|
[[Couzinet 70]]|Couzinet70.jpg|
[[De Havilland D.H. 91 Albatross]]|dh91.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Lockheed 1049|Lockheed Constellation]]|Lockheed_1049.jpg|
[[Boeing 314]]|314.jpg|
[[de Havilland Canada DHC-3 Otter]]|DHC-3.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg
}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Gallery|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]|V22Osprey.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg
}}

===Lighter than air aircraft (Available from version 1.9.0)===

These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.

{{Gallery|
[[Zeppelin NT]]|Zeppelin_NT.jpg|
[[ZF Navy free balloon]]|ZF_Navy_free_balloon.jpg|
[[Submarine Scout]]|Submarine_Scout.jpg
}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Gallery|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Bluebird]]|bluebird_hovercraft.jpg
}}

==Related==
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]
*[[Howto: Multiplayer]], [[Installing Scenery]], and [[Flying the Helicopter]].

[[Category:List]]

[[es:Avión]]
[[fr:Avions]]
[[pt:Avião]]

Aircraft

2010-06-10T23:37:07Z

Paul Richter: /* NATO military aircraft */ T-37

This list is not updated to include all the official [[GNU General Public License|GPL licensed]] aircraft for FlightGear 1.9.0, but gives a visual sampling of the different types of aircraft and genres of aircraft officially available. See [[Table of models]] for the comprehensive list. See also [[FlightGear hangars]] for non-official hangars (or [[Helicopters]], or [[Vehicles]] for more visual examples)

The examples listed here are officially available from the FlightGear project, and can be downloaded at [http://www.flightgear.org/Downloads/aircraft/ FlightGear.org Aircraft], with installation typically requiring an unzipping program, and manual installation in the FlightGear aircraft directory (if they are not already [[FlightGear 1.0 default aircraft|included]]).

FlightGear aircraft features, quality, and compatibility vary significantly;their development is dependent on the volunteers who worked on them, with exception of some University and Government funded projects.

Remember this list is merely a sampling of the many aircraft and variants available for FlightGear!

===Light civilian aircraft===
The Cessna 172 is the default aircraft in FGFS 1.0. These aircraft typically have 1-2 piston engines, props, and avionics geared towards those with civilian pilot licenses.
{{Gallery|
[[Aerostar 700]]|Aerostar_700.jpg|
[[B&F FK9 Mark 2]]|FK9MK2.jpg|
[[Cessna C172|Cessna 172P]] (1982)|Cessna_172P.jpg|
[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]] (1946) |Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]|Piper_SenecaII.jpg|
[[Robin DR400]]|dr400.jpg|
[[Rallye-MS893E]]|Rallye-MS893.jpg
}}

===Modern Airliners===
These typically have 2-4 turbofan engines and some of the more complicated takeoff and landing procedures (such as multiple [[flaps]]). In addition, avionics in real life is geared towards those with professional pilots licenses and special certifications. However, the simplifications of FG make it much easier to fly in the simulation.

====Narrowbody & Midsize====
{{Gallery|
[[Airbus A320]]|FirstChoice02.jpg|
[[Concorde]]|Concorde.jpg|
[[Boeing 757]]|757-2002.jpg|
[[Boeing 707]]|707.jpg|
[[Boeing 717]]|717_development.jpg|
[[Boeing 737-100]]|737-100.png|
[[Boeing 727-230]]|727-230.2.jpeg
}}

====Widebody & Jumbo Airliners====

{{Gallery|
[[Airbus A340-600]]|Airbus2.jpg|
[[Airbus A380]]|A380.jpg|
[[Boeing 777-200]]|777-200.jpg|
[[Boeing 767-300]]|Shadow.png|
[[Boeing 747-400]]|747-400.jpg|
[[Boeing 787]]|787.jpg|
[[Airbus A350]]|A350.png|
[[IL-96-400 Long Ranger(T)]]|1z5hr43.bmp
}}

===Helicopters===
{{Main article|Helicopter}}

Helicopters have fundamentally different controls than fixed wing aircraft (see ''[[Flying the Helicopter]]''). Modern helicopter typically feature 1-2 turbine engines, which power a main rotor with 2-6 blades.
{{Gallery|
[[Eurocopter Bo105|MBB Bo 105]]|FlightGearNL-9.jpg|
[[Eurocopter EC135|Eurocopter EC-135]]|Ec135.png|
[[CH-47 Chinook Helicopter|Boeing CH-47 Chinook]]|CH-47_Chinook.jpg|
[[Sikorsky S58|Sikorsky S-58]]|S58.jpg
}}

===Gliders, Sailplanes, & Ultralights===
These typically have the simplest controls, with minimal avionics. Flying gliders or sailplanes using thermals (see [[Soaring]]) can provide more complicated experience. Ultralights on the other hand are among the simplest aircraft in FG.
{{Gallery|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Dragonfly|Moyes Dragonfly]]|Dragonfly-towing.jpg|
[[Paraglider]]|Paraglider.jpg|
[[GDT Hornet (autogyro)]]|Hornet.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[ASW-20 sailplane|Schleicher ASW-20]]|Asw20.jpg|
[[Glaser-Dirks DG-300|Glaser-Dirks DG-300]]|DG-300.jpg
}}

===Warbirds===
FG includes a wide variety of vintage military aircraft. Complexity and realism is typically tied to the level of development work with a specific aircraft.
{{Gallery|
[[Bristol Beaufighter]]|Beaufighter.png|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[P-51D Mustang]]|P51d-mustang.png|
[[Nakajima Ki-84‎]]|ki-84.jpg|
[[Saab J 35Ã– Draken|Saab J35Ö Draken]]|Saab_J35.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Supermarine Spitfire]]|Spitfire.jpg
}}

===Carrier-borne aircraft===
FG supports landing on and taking off from carriers (2 are available in FG 1.0.0).

{{Gallery|
[[Grumman A-6E|Grumman A-6E Intruder]]|A-6E.jpg|
[[Blackburn Buccaneer]]|Buccaneer.jpg|
[[Grumman F-14 Tomcat]]|F-14.jpg|
[[Hawker Seahawk|Hawker Seahawk FGA6]]|Hawker_Seahawk.jpg
}}

===NATO military aircraft===
FG has a wide variety of modern and retired military jets available, highlighted by features such as air-to-air refueling from the the venerable KC-135 and the ability to simulate A-10 ordnance release.

{{Gallery|
[[Fairchild A-10]]|A-10.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[Boeing E-3 Sentry]]|E-3B.jpg|
[[F-15C Eagle]]|F-15C.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Cessna T-37]]|Cessna T-37.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg|
[[HAL Tejas]]|LCA.jpeg
}}

===Historical===
Many obscure to famous older aircraft of varying quality are available.
{{Gallery|
[[Couzinet 70]]|Couzinet70.jpg|
[[De Havilland D.H. 91 Albatross]]|dh91.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Lockheed 1049|Lockheed Constellation]]|Lockheed_1049.jpg|
[[Boeing 314]]|314.jpg|
[[de Havilland Canada DHC-3 Otter]]|DHC-3.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg
}}

===Experimental & Unique===
Experimental and special purpose aircraft.
{{Gallery|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]|V22Osprey.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg
}}

===Lighter than air aircraft (Available from version 1.9.0)===

These aircraft take advantage of lighter than air gas to become buoyant. In addition to typical aircraft control methods such as elevator, rudder and engine throttle, ballast and control of gas volume and pressure become options.

{{Gallery|
[[Zeppelin NT]]|Zeppelin_NT.jpg|
[[ZF Navy free balloon]]|ZF_Navy_free_balloon.jpg|
[[Submarine Scout]]|Submarine_Scout.jpg
}}

===Science Fiction===
Alternative models provide a diversion of realistic simulation, but can also be useful for exploring scenery.
{{Gallery|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Bluebird]]|bluebird_hovercraft.jpg
}}

==Related==
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]
*[[Howto: Multiplayer]], [[Installing Scenery]], and [[Flying the Helicopter]].

[[Category:List]]

[[es:Avión]]
[[fr:Avions]]
[[pt:Avião]]

Landmark Wish List

2009-12-16T08:36:57Z

Paul Richter: an obvious one

Antonov AN-225

2009-12-16T06:42:13Z

Paul Richter: moved Antonov AN-225 to Antonov An-225 over redirect: proper naming

#REDIRECT [[Antonov An-225]]

Antonov An-225 Mriya

2009-12-16T06:42:13Z

Paul Richter: moved Antonov AN-225 to Antonov An-225 over redirect: proper naming

{{infobox Aircraft
|image =Antonov_AN-255.jpg
|name =Antonov AN-225
|type = Transport
|authors = Lee Elliott
|fdm = YASim
|status = beta
|fgname = AN-225
|download =http://www.flightgear.org/Downloads/aircraft/#AN-225
}}

== Development status/Issues/Todo ==
'''Outside:'''
* no cockpit light at night visible
* no pilot/co-pilot in cockpit visible
* turbine does not rotate
* no aircraft light available
* no jetstream visible
* nozzle do not change shape when changing thrust
* there are no flaps when using reverse thrust

'''3d Cockpit:'''
* no cockpit light at night available
* no rudder/stick control in 3d cockpit available - no ruder control pedals available - no switches and leverls available - no elevator trim control available - no cockpit instruments available - cockpit is not textured - no pilot and co-pilot present in
* cockpit window has no windscreen wipers

'''General:'''
* engine sound in cockpit does not differ from outside engine sound
* engines can't be turned off
* hud can't be turned off

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Antonov}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Civilian aircraft]]
[[Category:Transport aircraft]]

Dornier Do 335

2009-12-16T06:40:04Z

Paul Richter: what country? what era?

{{stub}}

{{infobox Aircraft
|image =do-335.jpg
|name =Dornier Do 335
|type = 2-engine piston
|livery =
|fdm =YASim
|status =
|authors = Emmanuel Baranger (3D/FDM), Pierre Geoffroy (FDM)
|fgname =do335, do335-yasim
|download =http://www.flightgear.org/Downloads/aircraft/
}}The '''Dornier Do 335''' was a twin engined [[:Category:Military aircraft|fighter]] [[aircraft]], in pusher-pull configuration (engines at nose and tail) that saw limited service in the Luftwaffe in the latter years of WWII.

A surviving Do 335 is exhibited at the [[National Air and Space Museum]].

{{Dornier}}

[[Category:Aircraft]]
[[Category:Historical aircraft]]
[[Category:Military aircraft]]
[[Category:Twin Engine Piston]]

Lockheed F-104 Starfighter

2009-12-16T06:37:15Z

Paul Richter: brief description

{{infobox Aircraft
|image =Lockheed_F104.jpg
|name =Lockheed F-104 Starfighter
|type =Military aircraft
|fdm =
|status =beta
|authors =Erik Hofman
}}

The '''Lockheed F-104 Starfighter''' is a single-engine one-man supersonic jet fighter developed after the Korean War. Unforgiving to fly and sometimes called the "missile with a man it it", its career in the USAF was short, but it served at length in the air forces of West Germany, Japan, and Italy, among others.

There are several F-104 at the [[Luftwaffe Museum Berlin-Gatow]].

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* flaps are in wrong position by default on startup
* flaps can't be triggered
* no cockpit light at night visible
* no pilot visible
* wings are not textured
* engine turbines do not rotate or are not visible
* aircraft has no shadow
* no aircraft light available
* aircraft has no wheel well area for the landing gears
* baydoors for gears are missing
* no jetstream visible
* nozzle do not change shape when changing thrust
* there are no flaps when using reverse thrust

3d Cockpit:

* no cockpit light at night available
* no rudder/stick control in 3d cockpit available
* no ruder control pedals available
* no switches and levers available
* no elevator trim control available
* no cockpit instruments available
* cockpit is not textured
* no pilot and co pilot present
* cockpit window has no windscreen wipers

General:

* engine sound missing during flight and on ground
* hud is not available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Cessna T-37

2009-12-16T06:30:27Z

Paul Richter: /* Development status/Issues/Todo */ landing gear covers, wheel wells

{{infobox Aircraft
|image = Cessna_T-37.jpg
|name = Cessna T-37
|type = Military Aircraft
|authors = Erik Hofman
|fdm = JSBSim
|status = beta
|fgname = <tt>T37</tt>
}}

The '''Cessna T-37 Tweet''' is a basic jet trainer that first flew in 1954 and served in the U.S. and other air forces. It seats two in a side-by-side arrangement.

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* no pilot/co-pilot in cockpit visible
* wings are not textured
* engine turbines do not rotate or are not visible (engine bay could be a little darker)
* no aircraft light available
* landing gears are not animated
* no landing gear covers or wheel wells
* aircraft has no shadow
* no jetstream visible
* <strike>nozzle do not change shape when changing thrust</strike> (actually this type of aircraft doesn't have a nozzle)
* <strike>there are no flaps when using reverse thrust</strike> (This type of aircraft doesn't have reverse thrust)
* No speedbrakes available

3d Cockpit:
* no cockpit light at night available
* no switches and leverls available
* no elevator trim control available
* no cockpit instruments available
* cockpit is not textured
* no pilot present in 3d cockpit
* cockpit window has no windscreen wipers

General:

* engine sound in cockpit does not differ from outside engine sound
* no hud available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]

Landmark Wish List

2009-12-13T01:23:17Z

Paul Richter: Ryugyong Hotel

Landmark Wish List

2009-12-13T01:20:44Z

Paul Richter: default sort on country, city, landmark

Landmark Wish List

2009-12-13T01:12:04Z

Paul Richter: Brasilia Congress claimed

Tupolev Tu-154 (YASim)

2009-12-05T16:20:10Z

Paul Richter: description, reword

{{infobox Aircraft
|image =Tu154.jpg
|name =Tupolev 154
|type =Airliner
|fdm =YASim
|status =
|authors =Ilia Pavlenko, Ilja Moderau, Denis Okan and Mike Savchenko
|fgname = <tt>tu154</tt>
}}

The '''Tupolev Tu-154''' is a Russian medium-range jet airliner.

FlightGear's Tu-154 was converted by Ilia Pavlenko from a model originally designed for Microsoft Flight Simulator.

==Aircraft help==
===Climb===
* 200 kts

== Development status/Issues/Todo ==
'''Outside:'''
* cockpit and passenger windows are not transparent
* engine turbine does not rotate
* no aircraft light available
* aircraft has no wheel well area for the landing gears
* wheels rotate backwards when plane is stopped
* no jet stream visible

'''3D Cockpit:'''
* 3D cockpit is not available

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]

Tupolev 154

2009-12-05T16:16:55Z

Paul Richter: moved Tupolev 154 to Tupolev Tu-154: Use standard naming for Soviet aircraft

#REDIRECT [[Tupolev Tu-154]]

Tupolev Tu-154 (YASim)

2009-12-05T16:16:55Z

Paul Richter: moved Tupolev 154 to Tupolev Tu-154: Use standard naming for Soviet aircraft

{{infobox Aircraft
|image =Tu154.jpg
|name =Tupolev 154
|type =Airliner
|fdm =YASim
|status =
|authors =Ilia Pavlenko, Ilja Moderau, Denis Okan and Mike Savchenko
|fgname = <tt>tu154</tt>
}}
The originally for Microsofts Flight Simulator created aircraft has been converted for FlightGear by Ilia Pavlenko.

==Aircraft help==
===Climb===
* 200 kts

== Development status/Issues/Todo ==
'''Outside:'''
* cockpit and passenger windows are not transparent
* engine turbine does not rotate
* no aircraft light available
* aircraft has no wheel well area for the landing gears
* wheels rotate backwards when plane is stopped
* no jet stream visible

'''3D Cockpit:'''
* 3D cockpit is not available

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]