FlightGear wiki - User contributions [en]

Howto:Animate models

2018-07-18T10:45:41Z

I4dnf: /* Material animation */

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

FlightGear allows you to animate models in response to property changes: for example, the propellers can spin when the engine is on and the elevators can move up and down with your controller. There is no fixed limit on what parts can be animated: the only requirements are that the part is named in the 3D model file, and that there is a property in the main tree that you can use to get the positioning information.

This document provides basic information for all kind of animations. When animating your model, it is very helpful to find an aircraft with parts similar to yours and use it as an example. Cut and paste the code into your wrapper file and then edit to suit.

== Notes ==
=== File name of main model and animation XML file ===
{{main article|Aircraft-set.xml#Not used for loading multiplayer aircraft}}
The file name of the main model and animation XML file, or the .ac file if there is no XML file, (in essence the property <code>/sim/model/path</code>) will be the name of the aircraft that is transmitted when using [[multiplayer]] and will also be used for loading multiplayer aircraft.

There is also a mechanism to substitute a full aircraft model with a simpler AI aircraft model if one is available at the same file path (including for example <code>Models/Boeing-797-800.xml</code>), but in <code>[[$FG_ROOT]]/'''AI'''/Aircraft/</code> instead of <code>$FG_ROOT/Aircraft/</code>.

=== .ac files ===
{{Main article|AC files: Understanding and changing .ac code#Identifying an object}}

When referring to an .ac file in your xml animation, it is important that the <code><object name></code> exactly matches the object named in the .ac file (this includes cases!).

'''Note for SketchUp users:''' The spatial reference X/Y/Z used in animation to locate an object or a point are different from the ones in AC3D ie X values are the same in both but Y in animation must be matched to AC3D's -Z (Z value but opposite sign) and Z value in animation must be matched to AC3D's Y value.

'''Note for SketchUp users:''' when exporting to AC3D in Sketchup, the .ac file will name the objects in your model to "blah" by default. You need to amend the relevant object names in your .ac file using text edit, so that the xml will work.

=== Animation order ===
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).

== Tags used in most animations ==
=== 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.

=== Property ===
Each animation must be associated with exactly one property from the main FlightGear property tree (remember that the properties in the wrapper file are not part of the main tree), using <code><property></code> to provide the property path:

<source>
<animation>
<type>rotate</type>
<object-name>Rudder</object-name>
<property>controls/rudder</property>
</animation>
</source>

Note the omission of the leading slash '/' when reffering to the property. This assures that when the model is used for AI or multiplayer traffic the animations will follow that of the AI controller instead of that of the user.

=== 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]], [[#Scale|scale]]) 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.

=== Using a geometry object for axis and centre (2017.2) ===

Added in V2017.2 is support to allow a geometry object (a line segment with two vertices) that is used to define both the centre and the axis for an animation. This will work with rotate, translate and the knob animations.

The syntax for this is
<source>
<axis>
<object-name>some-object</object-name>
</axis>
</source>

Once the object-name used for the axis has been processed the geometry object will be hidden. This also allows a visual check for any axis objects that are not yet assigned.

It is possible to reuse the same object definition multiple times within a single XML file.

[[File:Canopy-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for a canopy]]

[[File:Gauges-knobs-animation-axis-object.png|small|Illustration of where an axis object (2017.2) can be placed for cockpit elements]]

== Additional tags that can be used in most animations ==
=== 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).

=== Expressions ===
For some animations it is possible to define complex animations by using [[Expressions|Expressions]]. This even allows to drive the animation from multiple properties without the need for additional Nasal scripts. Here is an example for a translate animation depending on two properties and the cosine function:
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<expression>
<product>
<property>/my/factor-property</property>
<cos>
<deg2rad>
<property>/my/angular-property</property>
</deg2rad>
</cos>
</product>
</expression>
[..]more elements[..]
</animation>
</syntaxhighlight>

Animations which can utilize [[Expressions|Expressions]] are:
* [[Howto:Animate_models#Translate|Translate]]
* [[Howto:Animate_models#Rotate|Rotate]]
* [[Howto:Animate_models#Scale|Scale]]
* [[Howto:Animate_models#Range|Range]]
* [[Howto:Animate_models#Blend|Blend]]

See more detailed info at [[Expressions|Expressions]]

== Object animations ==
=== Alpha-test ===
<source>
<animation>
<type>alpha-test</type>
<object-name>Object</object-name>
<alpha-factor>0.01</alpha-factor>
</animation>
</source>
This "animation" is a way to set an alpha test on a model branch. The effect is to avoid depth buffer writing of pixel that are not seen because they are transparent. This is particulary useful when modeling a metallic structure or a tree with a billboard. The threshold of transparency is set with the <alpha-factor> element. See also [[Pixel testing in effects]].

=== Blend ===
Blends an object with the surrounding. Comparable to a translucency animation. A value of 0 corresponds to no transparency, i.e. and ordinary solid object, and a value of 1 makes the object fully transparent, i.e., not visible at all.

<source>
<animation>
<type>blend</type>
<property>/velocities/airspeed-kt</property>
<factor>0.00025</factor>
<min>0.2</min>
<max>0.7</max>
</animation>
</source>

* '''property:'''
* '''factor:'''
* '''min:'''
* '''max:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

Note that when using the Project Rembrandt renderer, all transparent and translucent objects must be registered to display properly. [[Project_Rembrandt#Registering_all_translucent_surfaces|More information here.]]

=== 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>

You can optionally add [[#Center|<center>]] coordinates, to scale the object around that point.

=== Flash ===

Used to scale an object based on the cosine of the angle between the axis provided in the animation and the view vector.

<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:''' if false, nothing is drawn if the cosine is negative.
* '''min:'''
* '''max:'''

scale = factor * pow( cosine, power ) + offset

scale is then clamped between min and max.

and this scale factor is applied to the object, from the center specified. It works best if scale is less than 1. Otherwise, there will be clipping issues.

=== Noshadow ===
This animation is used to make sure an object will cast no shadow.

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

=== Range ===
: ''See also [[Modeling - Getting Started#Level of Detail (LOD)]].''

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.

<syntaxhighlight lang="xml">
<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</syntaxhighlight>

* '''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:
{| class="wikitable"
! Property
! Description
! Default value
|-
|<tt>/sim/rendering/static-lod/bare</tt>
| only a rough exterior model
| 30,000 m
|-
|<tt>/sim/rendering/static-lod/rough</tt>
| most should be visible
| 9,000 m
|-
|<tt>/sim/rendering/static-lod/detailed</tt>
| all details should be visible
| 1,500 m
|}

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

You can have both ranges (max and min) bound to a property, or just one of them.
* '''min-property:'''
* '''max-property:'''
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== 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>surface-positions/left-aileron-pos-norm</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<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.
* '''offset-deg:''' is optional. Offset in degrees.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

=== 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.
* Add [[#Center|<center>]] coordinates, to scale the object around that point.
* '''You can optionally use an [[Howto:Animate_models#Expressions|expression]] in the <factor> or <offset> inputs.''' For more details see [[Expressions|Expressions]]

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

=== 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>

=== Tracking ===
The new (in 2.11) [[Tracking animation|'''locked-track animation''']] can do exactly the same thing as the [http://wiki.blender.org/index.php/Doc:2.6/Manual/Constraints/Tracking/Locked_Track Locked Track constraint] available in Blender. However it can also be used to simulate simple inverse kinematic systems consisting of two bones connected with a revolute joint (aka hinge). See [[Tracking animation|detailed explanantion]]

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

{| class="wikitable" border="0" cellspacing="0"
!Property value
!Output
|-
| -1
| -2.5
|-
| 0
| 2.5
|-
| 1
| 7.5
|}

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

When using interpolation tables such as:
<source>
<interpolation>
<entry><ind>0.0</ind><dep> 0</dep></entry>
<entry><ind>0.666</ind><dep>0.18</dep></entry>
<entry><ind>1.0</ind><dep>0.27</dep></entry>
</interpolation>
</source>
The first figure (<ind> refers to the value of the property associated with the object and the second figure (in <dep>) refers to the amount that the object moves in metres. For example, in this case, the object moves 18cm when the value reads 0.66 and 27cm when the value is 1.

'''IF used WTIHOUT property''' : The object is placed at some (Value of Offset) meters away from its original position, along the virtual axis formed by said original position and the point with coordinates x/y/z defined in the <axis> tag.
Mathematically, assuming the Object to translate is (in the model space) placed at point A (x1, y1, z1) and you want to relocate it to point B (x2, y2, z2) then x2,y2,z2 are the values in the <axis> tag of the Translate animation and <offset> can be computed as SQRT((x2-x1)^2+(y2-y1)^2+(z2-z1)^2)

* '''factor:''' is optional.
* '''offset-m:''' is optional. Offset in meters.
* '''[[Howto:Animate_models#Expressions|expression]]:''' is optional. For more details see [[Expressions|Expressions]]

== Material animation ==
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 (deprecated):''' 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. This tag is no longer supported

'''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>

== Texture Animations ==

Applying different matrix transformations to the textures of an object.

=== 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>
<bias>0.0001</bias>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>0</x>
<y>1</y>
</axis>
</animation>
</source>

* '''bias:''' Adds an offset to the property before factor/step. A small value is needed to compensate for [http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems floating point accuracy].
* '''factor:''' property * factor * 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.
* '''step:''' the step size at which the texture is translated. If this is set to 0.1, the texture will only be translated at 0.1, 0.2, 0.3 etc.
* '''axis:''' the direction in which the texture is translated. Y is up/down, while X is left/right.

=== Texrotate ===

<source>
<animation>
<object-name>Object</object-name>
<type>texrotate</type>
<property>some/property/path</property>
<factor>25</factor>
<offset-deg>25</offset-deg>
<center>
<x>0.5</x>
<y>0.5</y>
<z>0</z>
</center>
<axis>
<x>0</x>
<y>0</y>
<z>1</z>
</axis>
</animation>
</source>

=== Textrapezoid ===

<source>
<animation>
<type>textrapezoid</type>
<object-name>HUD.l.canvas</object-name>
<property>/hud/trapezoid-correction</property>
<side>bottom</side>
</animation>
</source>

* '''side''': side of quad which should be scaled (''top'' (default)/''right''/''bottom''/''left'')

=== Texmultiple ===

Only one texture matrix can be applied to each object. With ''textmultiple'' multiple texture animations can be combined into a single matrix, applied to the specified object.

<source>
<animation>
<type>texmultiple</type>
<object-name>HUD.l.canvas</object-name>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-x</property>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textranslate</subtype>
<property>/hud/offset-y</property>
<axis>
<x>0</x>
<y>1</y>
<z>0</z>
</axis>
</transform>
<transform>
<subtype>textrapezoid</subtype>
<property>/hud/trapezoid-correction</property>
</transform>
</animation>
</source>

== Object interaction animations ==
=== 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 necessary to set this at all when wanting solidness.

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

== Direct manipulation animations ==
=== Knob / slider (v. 2.11-) ===
{{Main article|Knob / slider animation}}

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

=== Touch ===

The touch animation provides the normalized coordinates of a touch (or click) event on a 2d surface. The coordinates are passed in the argument and can be accessed using cmdarg() in Nasal.

<animation>
<type>touch</type>
<visible>true</visible>
<object-name>VSDImage</object-name>
<action>
<touch>0</touch>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>print("touch input (",cmdarg().getNode("x").getValue(),",",cmdarg().getNode("y").getValue())</script>
</binding>
</action>
</animation>

== Shadow Handling ==
There exist several possibilites for handling of shadows. 
See '''[[ALS_technical_notes|ALS Technical Notes]]''' and more specific '''[[ALS_technical_notes#ALS_fuselage_shadow_effect|Fuselage Shadow Effect with ALS]]''' for a relatively simple shadow handling. 
See '''[[Project Rembrandt]]''' which - amongst other functionality - implements a very realistic shadow mapping.

== References ==
{{Appendix|all|
* {{cite web |url=http://www.opensubscriber.com/message/flightgear-devel@flightgear.org/958955.html |title="material" animation (and the bo105 as an example) |first=Melchior |last=Franz |date=22 March 2005 |work=FlightGear-devel mailinglist }}
* {{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg01546.html |title=flash animation |first=Frederic |last=Bouvier |date=22 Feb 2006 |work=FlightGear-devel mailinglist }}
}}

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

IAR 80/info

2018-03-24T09:41:07Z

I4dnf:

<includeonly>{{infobox aircraft
| name = IAR 80
| hangar = emilianh
| aircraft = IAR80
| image = Iar80-flight.jpg
| alt = The IAR 80 in its the default livery.
| image2 = Iar80-cockpit-dusk.jpg
| alt2 = The IAR 80's cockpit as dusk
| type = Fighter aircraft
| config = Low wing aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Industria Aeronautică Română (IAR)
| authors = Emilian Huminiuc (3D model, textures, YASim FDM)/Ron Jensen (JSBSim FDM)
| fdm = YASim/JSBSim
| fgname = IAR80-YASim
| status-fdm = 5
| status-systems = 4
| status-cockpit = 5
| status-model = 5
| license = CC-BY-NC-ND 4.0/GPLv2
| note = The JSBSim FDM is in beta
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[IAR 80]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Howto:Syntax highlighting for Nasal

2017-08-13T21:42:58Z

I4dnf: /* KDE Editors */

There's '''[[Nasal]] syntax-highlighting''' support available for some editors, which is a big advantage, as it makes Nasal coding much easier.

Syntax highlighting can often point to syntax errors and so reduce the number of tedious time-consuming and unproductive [[FlightGear]] runs. It can also be a sort of "guide" to the language, highlighting functions or keywords that are builtin, so you can quickly check if it is "type" or "typeof" by typing each. In addition makes understanding other people's code easier, since you have all of the parts visually separated out, like loops, strings, constants, and builtin functions.

== Atom ==
Script is available from [https://github.com/www2000/atom-language-nasal Github] and can also be found in the [https://atom.io/packages/language-nasal Atom's packages repository].

Manual installation:

# Download the latest release from https://github.com/www2000/atom-language-nasal
# Unpack the tar.bz2
# Copy/move the language-nasal package to ~/.atom/packages

For installation from atom's packages repository:

# Open Atom
# Go to Preferences Edit -> Preferences or {{key press|Ctrl|+}},
# Click on packages and search for nasal
# Click install for Language Nasal

== gedit ==
[[File:Philosopher's nasal highlighting in gEdit.jpeg|400px|thumb|Screen shot illustrating syntax highlighting in gedit]]

'''Philosopher''' on the FlightGear Forum has created syntax highlighting for gedit, a popular and simple text editor for Mac OS X, Linux, and Windows.


To install, copy the ''nasal.lang'' file  from the first post of the forum topic [http://www.flightgear.org/forums/viewtopic.php?f=30&t=17265#p164133] and:

* If you use Mac, move it into your ''Applications/gedit/Contents/Resources/share/gtksourceview-X.0/language specs'' folder.
* For Linux, move it into your ''/usr/share/gtksourceview-X.0/language-specs'' folder.

In the same post given above, there are instructions for how to edit ''xml.lang'' (in the same directory) to add the embedded XML content support (with this minor edit, Nasal highlighting will be used inside of certain tags, instead of plain text).

For "snippets" support, nasal.xml from the above post has to be moved into ''/usr/share/gedit/plugins/snippets/'' folder or installed using the "import" feature. See this image for more details:

[[:File:Install nasal snippets in gedit.png|how to import Nasal snippets]].
{{-}}

== jEdit ==
There's a syntax highlighting mode for jEdit, programmer's text editor

Included are some of Nasal's internal functions and those functions currently implemented in NasalSys.cxx
To use, add the content of the catalog inside your own catalog (do NOT overwrite the file) and nasal.xml in /home/USER/.jedit/modes

Restart jEdit and you can use it. Current extension is .nas, you can add your own extension and functions.
This mode is heavily based on the Javascript mode.

Get it here: https://sourceforge.net/projects/fgscheduleview/files/jedit/catalog.zip/download

== KDE Editors ==
There's a highlighting definition for nasal available at '''opendesktop.org''' (https://www.opendesktop.org/p/1187022/)

Download the file and copy it into:
:~/.kde4/share/apps/katepart/syntax/ (for KDE4)
:or
:~/.local/share/katepart5/syntax/ (for KF5 pre 5.29)
:or
:~/.local/share/org.kde.syntax.highlighting/syntax/ (for current KF5 versions)

(you can create the folders if they don't exist yet).

Note that the syntax highlighting in KDE doesn't set colors, it just identifies structural elements, colors are defined by the '''schemas''' used by each editor, thus you get consistent highlighting between different languages.

The highlighting file should work with all editors based on the katepart: KWrite, Kate, and the editor component of KDevelop.

== Notepad++ ==
[[File:Highlight parse.png|400px|thumb|Screenshot of Nasal support for Notepad++]]
Provides comprehensive syntax highlighting and a function list parser with support for hierarchical display of both inline and out-of-body class member functions.
* [http://github.com/Slaiyer/nasal-npp GitHub repository for download and instructions]

'''Alternative (syntax highlighting only):'''
* [http://dl.dropbox.com/u/1463693/nasal.xml Download here]
** [http://superuser.com/questions/62474/notepad-custom-syntax-highlighting-setting-where-to-look-for-it Instructions are here]
{{-}}

== Sublime Text 2 ==
[[File:Sublime Text 2 syntax highlighting.png|400px|thumb|Sublime Text 2 syntax highlighting]]

Scripts and installation instructions are here: https://github.com/freevryheid/nasal
{{-}}

== Vim ==
[[File:Vim-nasal-syntax-highlighting.png|400px|thumb|Screen shot illustrating syntax highlighting in Vim]]

One such editor is the free vim or its GUI variant gvim.

It's not for everyone but it's free, and testing it doesn't hurt: http://www.vim.org/.

The syntax definition file comes with the FlightGear code ({{flightgear file|scripts/syntax/nasal.vim}}). Highlighting works even for Nasal embedded in XML files (type ":set ft=nasal", where ft stands for file-type)

Here's an example, which demonstrates a short code segment with three syntax errors as well as the highlighting of a matching pair of parentheses (yellow) and trailing spaces (blue x). (The leading blue dots aren't on by default. They help to spot tab crimes.)
{{-}}

== Other editors ==
Nasal being syntactically very close to other programming languages like C, Php or JavaScript, you can get some usable highlighting even without real Nasal support:

* TextMate [http://flightgear.org/forums/viewtopic.php?f=30&t=12495&p=128116&hilit=syntax+nasal#p127828]
* SciTe [http://flightgear.org/forums/viewtopic.php?f=30&t=9260&p=94521&hilit=syntax+nasal#p94521]

== FlightGear Wiki ==
{{Note|As of 02/2016, we do not currently have a dedicated Nasal module available [http://wiki.flightgear.org/FlightGear_wiki:Village_pump#Nasal_Syntaxhighlighting]}}
{{main article|Help:Formatting#Syntax highlighting}}

Using the <syntaxhighight> tag with a lang="nasal" attribute, we can have highlighting right here on the wiki. Use enclose="div" to wrap the text, if it happens to be particularly wide.

<nowiki><syntaxhighlight lang="nasal">
# hello.nas
print('Hello World!');
</syntaxhighlight></nowiki>

Which renders into:
<syntaxhighlight lang="nasal">
# hello.nas
print('Hello World!');
</syntaxhighlight>

== Syntax highlighting test ==
Just a collection of keywords, etc. to test whether highlighting works (you can copy this to test your own highlighting):
<syntaxhighlight lang="nasal">
# this is a comment
# operators (if applicable):
!a ? a+b - c/d*e : f~g; expr1 and expr2 or expr3;
# Builtin functions, strings
print('Hello World!');
die("We have an error, Houston!", arg[0]);
cmdarg().getNode("setting").getValue();
streq(typeof(id(keys(hash))),10);
# Loopoids
foreach (var a; ["haha", {command:"NASAL!"}, me]) {
if(0) break;
elsif(1) continue;
else return;
while(1) sprintf("%s%s\n%s=%f", "Spam", "spam", "spam", 0e-0);
for (var i=0; i < 0.00; i += 0x0) printf("%d", int(i));
forindex(var o; a) (func {
var o = o;
setlistener("/", func print(o), 1, 2);
})();
}
# String escaping stress tests:
'\a\b\c\"\\\?' # none of these
"\e\?\'\f\a" # none of these
'\'' # this one
"\"\r\n\t\\\t" # and all of these
# And optionally string formatting:
"%s%%s%.0f%8d" # the second "s" shouldn't be highlighted, otherwise everything else
# Syntax error!:
%$@&^|\`
</syntaxhighlight>

== Related content ==
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=17265&p=164155#p164155
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=12495
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=15972
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=9812

[[Category:Nasal howto]]

Howto:Syntax highlighting for Nasal

2017-08-13T21:40:42Z

I4dnf: /* KDE Editors */

There's '''[[Nasal]] syntax-highlighting''' support available for some editors, which is a big advantage, as it makes Nasal coding much easier.

Syntax highlighting can often point to syntax errors and so reduce the number of tedious time-consuming and unproductive [[FlightGear]] runs. It can also be a sort of "guide" to the language, highlighting functions or keywords that are builtin, so you can quickly check if it is "type" or "typeof" by typing each. In addition makes understanding other people's code easier, since you have all of the parts visually separated out, like loops, strings, constants, and builtin functions.

== Atom ==
Script is available from [https://github.com/www2000/atom-language-nasal Github] and can also be found in the [https://atom.io/packages/language-nasal Atom's packages repository].

Manual installation:

# Download the latest release from https://github.com/www2000/atom-language-nasal
# Unpack the tar.bz2
# Copy/move the language-nasal package to ~/.atom/packages

For installation from atom's packages repository:

# Open Atom
# Go to Preferences Edit -> Preferences or {{key press|Ctrl|+}},
# Click on packages and search for nasal
# Click install for Language Nasal

== gedit ==
[[File:Philosopher's nasal highlighting in gEdit.jpeg|400px|thumb|Screen shot illustrating syntax highlighting in gedit]]

'''Philosopher''' on the FlightGear Forum has created syntax highlighting for gedit, a popular and simple text editor for Mac OS X, Linux, and Windows.


To install, copy the ''nasal.lang'' file  from the first post of the forum topic [http://www.flightgear.org/forums/viewtopic.php?f=30&t=17265#p164133] and:

* If you use Mac, move it into your ''Applications/gedit/Contents/Resources/share/gtksourceview-X.0/language specs'' folder.
* For Linux, move it into your ''/usr/share/gtksourceview-X.0/language-specs'' folder.

In the same post given above, there are instructions for how to edit ''xml.lang'' (in the same directory) to add the embedded XML content support (with this minor edit, Nasal highlighting will be used inside of certain tags, instead of plain text).

For "snippets" support, nasal.xml from the above post has to be moved into ''/usr/share/gedit/plugins/snippets/'' folder or installed using the "import" feature. See this image for more details:

[[:File:Install nasal snippets in gedit.png|how to import Nasal snippets]].
{{-}}

== jEdit ==
There's a syntax highlighting mode for jEdit, programmer's text editor

Included are some of Nasal's internal functions and those functions currently implemented in NasalSys.cxx
To use, add the content of the catalog inside your own catalog (do NOT overwrite the file) and nasal.xml in /home/USER/.jedit/modes

Restart jEdit and you can use it. Current extension is .nas, you can add your own extension and functions.
This mode is heavily based on the Javascript mode.

Get it here: https://sourceforge.net/projects/fgscheduleview/files/jedit/catalog.zip/download

== KDE Editors ==
There's a highlighting definition for nasal available at '''opendesktop.org''' (https://dl.opendesktop.org/api/files/download/id/1502659914/nasal.xml)

Download the file and copy it into:
:~/.kde4/share/apps/katepart/syntax/ (for KDE4)
:or
:~/.local/share/katepart5/syntax/ (for KF5 pre 5.29)
:or
:~/.local/share/org.kde.syntax.highlighting/syntax/ (for current KF5 versions)

(you can create the folders if they don't exist yet).

Note that the syntax highlighting in KDE doesn't set colors, it just identifies structural elements, colors are defined by the '''schemas''' used by each editor, thus you get consistent highlighting between different languages.

The highlighting file should work with all editors based on the katepart: KWrite, Kate, and the editor component of KDevelop.

== Notepad++ ==
[[File:Highlight parse.png|400px|thumb|Screenshot of Nasal support for Notepad++]]
Provides comprehensive syntax highlighting and a function list parser with support for hierarchical display of both inline and out-of-body class member functions.
* [http://github.com/Slaiyer/nasal-npp GitHub repository for download and instructions]

'''Alternative (syntax highlighting only):'''
* [http://dl.dropbox.com/u/1463693/nasal.xml Download here]
** [http://superuser.com/questions/62474/notepad-custom-syntax-highlighting-setting-where-to-look-for-it Instructions are here]
{{-}}

== Sublime Text 2 ==
[[File:Sublime Text 2 syntax highlighting.png|400px|thumb|Sublime Text 2 syntax highlighting]]

Scripts and installation instructions are here: https://github.com/freevryheid/nasal
{{-}}

== Vim ==
[[File:Vim-nasal-syntax-highlighting.png|400px|thumb|Screen shot illustrating syntax highlighting in Vim]]

One such editor is the free vim or its GUI variant gvim.

It's not for everyone but it's free, and testing it doesn't hurt: http://www.vim.org/.

The syntax definition file comes with the FlightGear code ({{flightgear file|scripts/syntax/nasal.vim}}). Highlighting works even for Nasal embedded in XML files (type ":set ft=nasal", where ft stands for file-type)

Here's an example, which demonstrates a short code segment with three syntax errors as well as the highlighting of a matching pair of parentheses (yellow) and trailing spaces (blue x). (The leading blue dots aren't on by default. They help to spot tab crimes.)
{{-}}

== Other editors ==
Nasal being syntactically very close to other programming languages like C, Php or JavaScript, you can get some usable highlighting even without real Nasal support:

* TextMate [http://flightgear.org/forums/viewtopic.php?f=30&t=12495&p=128116&hilit=syntax+nasal#p127828]
* SciTe [http://flightgear.org/forums/viewtopic.php?f=30&t=9260&p=94521&hilit=syntax+nasal#p94521]

== FlightGear Wiki ==
{{Note|As of 02/2016, we do not currently have a dedicated Nasal module available [http://wiki.flightgear.org/FlightGear_wiki:Village_pump#Nasal_Syntaxhighlighting]}}
{{main article|Help:Formatting#Syntax highlighting}}

Using the <syntaxhighight> tag with a lang="nasal" attribute, we can have highlighting right here on the wiki. Use enclose="div" to wrap the text, if it happens to be particularly wide.

<nowiki><syntaxhighlight lang="nasal">
# hello.nas
print('Hello World!');
</syntaxhighlight></nowiki>

Which renders into:
<syntaxhighlight lang="nasal">
# hello.nas
print('Hello World!');
</syntaxhighlight>

== Syntax highlighting test ==
Just a collection of keywords, etc. to test whether highlighting works (you can copy this to test your own highlighting):
<syntaxhighlight lang="nasal">
# this is a comment
# operators (if applicable):
!a ? a+b - c/d*e : f~g; expr1 and expr2 or expr3;
# Builtin functions, strings
print('Hello World!');
die("We have an error, Houston!", arg[0]);
cmdarg().getNode("setting").getValue();
streq(typeof(id(keys(hash))),10);
# Loopoids
foreach (var a; ["haha", {command:"NASAL!"}, me]) {
if(0) break;
elsif(1) continue;
else return;
while(1) sprintf("%s%s\n%s=%f", "Spam", "spam", "spam", 0e-0);
for (var i=0; i < 0.00; i += 0x0) printf("%d", int(i));
forindex(var o; a) (func {
var o = o;
setlistener("/", func print(o), 1, 2);
})();
}
# String escaping stress tests:
'\a\b\c\"\\\?' # none of these
"\e\?\'\f\a" # none of these
'\'' # this one
"\"\r\n\t\\\t" # and all of these
# And optionally string formatting:
"%s%%s%.0f%8d" # the second "s" shouldn't be highlighted, otherwise everything else
# Syntax error!:
%$@&^|\`
</syntaxhighlight>

== Related content ==
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=17265&p=164155#p164155
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=12495
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=15972
* http://www.flightgear.org/forums/viewtopic.php?f=30&t=9812

[[Category:Nasal howto]]

Howto talk:Add effects to an aircraft

2017-06-25T16:07:56Z

I4dnf:

==== Some Disagreement ====

Quote: '' "Generally it is a good idea for textured models to use a white diffuse color (1,1,1) in the material and a grey ambient with a value of 0.3 to 0.5 according to the desired darkness of shadows. The specular color should usually be white (1,1,1) too, unless there's a compelling reason not to (a metallic material where specular color should match the diffuse color, or a lighter shade thereof). The most common mistake for beginners is to neglect the ambient channel, in which case shadows tend to appear too bright,..."''

I have to disagree to the text above here.

1.) textured objects and especially untextured objects need the same ambient color as the diffuse color. A white diffuse color (1,1,1) with a different ambient color like (0.3,0.3,0.3) will appear grey when model shader is not applied. With model shader applied I don't see any difference on shadows with different ambient color setting. Since we support three different renderer, and an aircraft should at least support the two active maintained renderer DEFAULT and ALS with or without model shader applied, an ambient color of (1,1,1) for textured objects and equal diffuse color for untextured objects is recommended.

2.) the color of the specular can be used to simulate dull, matt painted surfaces like we will find on military aircraft or when the aircraft is getting dirty. The specular color should be than less than 0.5.

--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 09:30, 25 June 2017 (EDT)

I'm not sure this has anything to do with the model shader - ambient white color just gives me very bad appearance of unlit surfaces, regardless the renderer or the quality level.

I don't see why a white diffuse color with a grey ambient color would appear grey when the model shader is not applied. The default shader does a standard Blinn-Phong, and lit surfaces will get color values above 1 in all renderers - the lighting is very intensity saturated (in all renderers)

(Heck, I actually agree with you that conceptually the ambient color *should* be equal to the diffuse color and that the ambient light value should take care of everything... the problem is that the renderer has to come up with an ambient light value that renders /most/ models okay, and that has determined the ambient light we apply. If we would convert all models to unit ambient lighting, I could dial down the light in the renderers, and we'd be fine again. The situation is a mess as it stands, and I am very unhappy with it and am just trying to make the best out of it).

[[User:Thorsten|Thorsten]] ([[User talk:Thorsten|talk]]) 10:46, 25 June 2017 (EDT)

:Here is the effect with model-shader en-/disabled, with ALS on/ off. I only set the model-shader to zero, everything else is higher than zero!
:You can see the settings, the upper three values are the ambient color settings, which can be set per runtime on the c182s. The airport is Pennridge Airport KCKZ
:[[File:AmbientColorSetting.jpg|800px|Shows the effect of the ambient color settings with model shader applied en-/disabled, with ALS or Default.It does not show when shader-effects generally are disabled.]]

:When shader-effects equal zero and ALS OFF you get the effect you described:
:[[File:AmbientColorSettings disabledShaders.jpg|800px|Ambient Color settings with shader effects equal zero, ALS off]]
:(Funny sidenote: ''shader-effects = zero and ALS OFF'' gives less fps than ''shader-effects = zero and ALS ON'')

:--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 11:43, 25 June 2017 (EDT)

:: That's because texture is multiplied by ambient in the default shader[s]:
:: default.vert:
:: ''vec4 constant_term = gl_FrontMaterial.emission + ambient_color * (gl_LightModel.ambient + gl_LightSource[0].ambient);''
:: ''gl_FrontColor.rgb = constant_term.rgb; gl_FrontColor.a = 1.0;''
:: default.frag:
:: ''vec4 color = gl_Color;'' this is gl_FrontColor set in the .vert.
:: ''fragColor = color * texel + specular;''

:: As for the specular, even then it is white, but multiplied with an intensity factor (for example that's how you'd set it up in blender, and the exporter would convert it by multiplying the color setting with the intensity). I meant to emphasize that '''only''' metallic materials might have a "coloured" specular component.

::[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 12:01, 25 June 2017 (EDT)

Howto talk:Add effects to an aircraft

2017-06-25T16:02:41Z

I4dnf:

==== Some Disagreement ====

Quote: '' "Generally it is a good idea for textured models to use a white diffuse color (1,1,1) in the material and a grey ambient with a value of 0.3 to 0.5 according to the desired darkness of shadows. The specular color should usually be white (1,1,1) too, unless there's a compelling reason not to (a metallic material where specular color should match the diffuse color, or a lighter shade thereof). The most common mistake for beginners is to neglect the ambient channel, in which case shadows tend to appear too bright,..."''

I have to disagree to the text above here.

1.) textured objects and especially untextured objects need the same ambient color as the diffuse color. A white diffuse color (1,1,1) with a different ambient color like (0.3,0.3,0.3) will appear grey when model shader is not applied. With model shader applied I don't see any difference on shadows with different ambient color setting. Since we support three different renderer, and an aircraft should at least support the two active maintained renderer DEFAULT and ALS with or without model shader applied, an ambient color of (1,1,1) for textured objects and equal diffuse color for untextured objects is recommended.

2.) the color of the specular can be used to simulate dull, matt painted surfaces like we will find on military aircraft or when the aircraft is getting dirty. The specular color should be than less than 0.5.

--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 09:30, 25 June 2017 (EDT)

I'm not sure this has anything to do with the model shader - ambient white color just gives me very bad appearance of unlit surfaces, regardless the renderer or the quality level.

I don't see why a white diffuse color with a grey ambient color would appear grey when the model shader is not applied. The default shader does a standard Blinn-Phong, and lit surfaces will get color values above 1 in all renderers - the lighting is very intensity saturated (in all renderers)

(Heck, I actually agree with you that conceptually the ambient color *should* be equal to the diffuse color and that the ambient light value should take care of everything... the problem is that the renderer has to come up with an ambient light value that renders /most/ models okay, and that has determined the ambient light we apply. If we would convert all models to unit ambient lighting, I could dial down the light in the renderers, and we'd be fine again. The situation is a mess as it stands, and I am very unhappy with it and am just trying to make the best out of it).

[[User:Thorsten|Thorsten]] ([[User talk:Thorsten|talk]]) 10:46, 25 June 2017 (EDT)

:Here is the effect with model-shader en-/disabled, with ALS on/ off. I only set the model-shader to zero, everything else is higher than zero!
:You can see the settings, the upper three values are the ambient color settings, which can be set per runtime on the c182s. The airport is Pennridge Airport KCKZ
:[[File:AmbientColorSetting.jpg|800px|Shows the effect of the ambient color settings with model shader applied en-/disabled, with ALS or Default.It does not show when shader-effects generally are disabled.]]

:When shader-effects equal zero and ALS OFF you get the effect you described:
:[[File:AmbientColorSettings disabledShaders.jpg|800px|Ambient Color settings with shader effects equal zero, ALS off]]
:(Funny sidenote: ''shader-effects = zero and ALS OFF'' gives less fps than ''shader-effects = zero and ALS ON'')

:--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 11:43, 25 June 2017 (EDT)

:: That's because texture is multiplied by ambient in the default shader[s]:
:: default.vert:
:: ''vec4 constant_term = gl_FrontMaterial.emission + ambient_color * (gl_LightModel.ambient + gl_LightSource[0].ambient);''
:: ''gl_FrontColor.rgb = constant_term.rgb; gl_FrontColor.a = 1.0;''
:: default.frag:
:: ''vec4 color = gl_Color;'' this is gl_FrontColor set in the .vert.
:: ''fragColor = color * texel + specular;''

:: As for the specular, even then it is white, but multiplied with an intensity factor (for example that's how you'd set it up in blender, and the exporter would convert it by multiplying the color setting with the intensity). I meant to emphasize that _only_ metallic materials might have a "coloured" specular component.

::[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 12:01, 25 June 2017 (EDT)

Howto:Add effects to an aircraft

2017-06-22T11:39:16Z

I4dnf: Correct specular color reccomendation, specualr highlights are usually white for non-metallic materials.

{{WIP}}

This article is an introduction how to use the Flightgear Effect framework as a contributor - mainly for aircraft, but in principle also for scenery models.

== What are effects? ==

Simply put, effects are instructions for the graphics card how a given surface is rendered. In FG, most effects can be seen as something like configuration files for [[Shaders] (i.e. GLSL code that is directly executed on the graphics card).

Per default, all meshes are processed using a [https://en.wikipedia.org/wiki/Blinn–Phong_shading_model Blinn-Phong shading model] which uses a combination of ambient, diffuse and specular lighting. This looks generally acceptable, but does not really capture the properties of many materials.

GLSL shaders on the other hand can (and do) solve much more complicated lighting equations than Blinn-Phong does, taking into account things like environment reflections, Fresnel small angle reflections, diffuse irradiance from skylight, etc. In addition, shaders can also process additional information on structures not captured by the 3d mesh triangles, for instance via normal maps.

To get a visual idea, compare the following two images (you may have to magnify them to fullscreen to appreciate the details). The first one is processed by a default Blinn-Phong scheme.

[[File:Effect demo01.jpg|600px|The EC 130 rendered in a Blinn-Phong shading model]]

The second one is processed by a shader which utilizes among other things normal and irradiance mapping:

[[File:Effect demo02.jpg|600px|The EC 130 rendered using the model-combined effect]]

The differences are perhaps subtle, but combine to a much more realistic impression. Thus, effects are what turns a good 3d model into a great 3d model.

== Useful concepts ==

It's worth looking into some things which are specified already at the creation stage of a 3d model (i.e. set by blender or ac3d).

=== Materials ===

Materials belong to the Blinn-Phong scheme and tell how a surface looks like when rendered in the scheme. A material is comprised of four different colors, each as (rgb) triplets. The ambient color channel is multiplied with the scene ambient light and determines what in what color surfaces in shadow appear. The diffuse color channel is multiplied with the scene diffuse color and determined how surfaces in light appear, and the specular color channel is multiplied with the scene specular color and determines the color of specular highlights. Finally, the emissive color channel determines a color independent of the scene light.

In addition, a material has a transparency which determines to what degree one can see through the surface and a shininess which determines how glossy the surface looks (i.e. how narrow the specular highlights appear).

The end color of a pixel in Blinn-Phong is determined by summing all channels and multiplying with the texture color. Thus, textured models should not use colored materials (or the texture won't appear in its natural color). Generally it is a good idea for textured models to use a white diffuse color (1,1,1) in the material and a grey ambient with a value of 0.3 to 0.5 according to the desired darkness of shadows. The specular color should usually be white (1,1,1) too, unless there's a compelling reason not to (a metallic material where specular color should match the diffuse color, or a lighter shade thereof). The most common mistake for beginners is to neglect the ambient channel, in which case shadows tend to appear too bright, or to assign an emissive color which makes the model glow at night.

The way Flightgear treats models, each surface (face) can have one (and only one) material assigned - make sure you understand what it is and how to alter it in the 3d modeling tool of your choice.

=== Objects ===

Objects are parts of a 3d model which are grouped together. They consist of a mesh, material[s] assigned to the faces of that mesh and, optionally, the texture associated with it. They have a unique name assigned. In the FG effect framework, an effect is always assigned to an object.

The relevance of grouping into objects is that the graphics card processes models in so-called draw calls. Before each draw call, the so-called state set needs to be prepared (mainly texture sheets, material parameters and positioning matrices configured by animations) and this costs some time. The net effect is that it is far faster to render a million vertices in one draw than in thousand draws a thousand vertices each.
Due to the limitations of the AC3D model format used by FlightGear, different parts of an object cannot be assigned to different texture sheets, thus for each extra texture sheet there will be an extra object and ultimately an extra draw call, having as a result that four 1k texture sheets are less efficient than the same data on a single 2k texture sheet because there's 4x less draw calls.

Thus, anything that can be combined into one object also should be combined into one object, and the number of texture sheets used should be as low as possible.

Make sure you understand how to group things into objects and assign object names in the 3d modeling tool of your choice.

Howto:Add effects to an aircraft

2017-06-22T11:33:13Z

I4dnf: Correct the object->mesh ierarchy. Correct the attributes the object has, correct the cause for the delay for multiple vs single texture.

{{WIP}}

This article is an introduction how to use the Flightgear Effect framework as a contributor - mainly for aircraft, but in principle also for scenery models.

== What are effects? ==

Simply put, effects are instructions for the graphics card how a given surface is rendered. In FG, most effects can be seen as something like configuration files for [[Shaders] (i.e. GLSL code that is directly executed on the graphics card).

Per default, all meshes are processed using a [https://en.wikipedia.org/wiki/Blinn–Phong_shading_model Blinn-Phong shading model] which uses a combination of ambient, diffuse and specular lighting. This looks generally acceptable, but does not really capture the properties of many materials.

GLSL shaders on the other hand can (and do) solve much more complicated lighting equations than Blinn-Phong does, taking into account things like environment reflections, Fresnel small angle reflections, diffuse irradiance from skylight, etc. In addition, shaders can also process additional information on structures not captured by the 3d mesh triangles, for instance via normal maps.

To get a visual idea, compare the following two images (you may have to magnify them to fullscreen to appreciate the details). The first one is processed by a default Blinn-Phong scheme.

[[File:Effect demo01.jpg|600px|The EC 130 rendered in a Blinn-Phong shading model]]

The second one is processed by a shader which utilizes among other things normal and irradiance mapping:

[[File:Effect demo02.jpg|600px|The EC 130 rendered using the model-combined effect]]

The differences are perhaps subtle, but combine to a much more realistic impression. Thus, effects are what turns a good 3d model into a great 3d model.

== Useful concepts ==

It's worth looking into some things which are specified already at the creation stage of a 3d model (i.e. set by blender or ac3d).

=== Materials ===

Materials belong to the Blinn-Phong scheme and tell how a surface looks like when rendered in the scheme. A material is comprised of four different colors, each as (rgb) triplets. The ambient color channel is multiplied with the scene ambient light and determines what in what color surfaces in shadow appear. The diffuse color channel is multiplied with the scene diffuse color and determined how surfaces in light appear, and the specular color channel is multiplied with the scene specular color and determines the color of specular highlights. Finally, the emissive color channel determines a color independent of the scene light.

In addition, a material has a transparency which determines to what degree one can see through the surface and a shininess which determines how glossy the surface looks (i.e. how narrow the specular highlights appear).

The end color of a pixel in Blinn-Phong is determined by summing all channels and multiplying with the texture color. Thus, textured models should not use colored materials (or the texture won't appear in its natural color). Generally it is a good idea for textured models to use a white diffuse color (1,1,1) in the material and a grey ambient with a value of 0.3 to 0.5 according to the desired darkness of shadows. The specular color should usually match the diffuse color, unless there's a compelling reason not to. The most common mistake for beginners is to neglect the ambient channel, in which case shadows tend to appear too bright, or to assign an emissive color which makes the model glow at night.

The way Flightgear treats models, each surface (face) can have one (and only one) material assigned - make sure you understand what it is and how to alter it in the 3d modeling tool of your choice.

=== Objects ===

Objects are parts of a 3d model which are grouped together. They consist of a mesh, material[s] assigned to the faces of that mesh and, optionally, the texture associated with it. They have a unique name assigned. In the FG effect framework, an effect is always assigned to an object.

The relevance of grouping into objects is that the graphics card processes models in so-called draw calls. Before each draw call, the so-called state set needs to be prepared (mainly texture sheets, material parameters and positioning matrices configured by animations) and this costs some time. The net effect is that it is far faster to render a million vertices in one draw than in thousand draws a thousand vertices each.
Due to the limitations of the AC3D model format used by FlightGear, different parts of an object cannot be assigned to different texture sheets, thus for each extra texture sheet there will be an extra object and ultimately an extra draw call, having as a result that four 1k texture sheets are less efficient than the same data on a single 2k texture sheet because there's 4x less draw calls.

Thus, anything that can be combined into one object also should be combined into one object, and the number of texture sheets used should be as low as possible.

Make sure you understand how to group things into objects and assign object names in the 3d modeling tool of your choice.

User talk:PSVA Airlines

2017-06-07T07:01:18Z

I4dnf: /* Deletion reasons */ new section

[[User:PSVA Airlines|PSVA Airlines]] ([[User talk:PSVA Airlines|talk]]) 04:35, 18 January 2017 (EST) Welcome to talk page! Any questions?

== Deletion reasons ==

Hi

Separate, individual, Virtual Airlines pages aren't permitted on the wiki. You should add your details to the Virtual Airlines page instead.

Masking a VA page as a user page doesn't fly either.

Regards,

[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 03:01, 7 June 2017 (EDT)

User:PSVA Airlines

2017-06-07T06:58:31Z

I4dnf: Add deletion notice

{{Delete
|reason=Individual Virtual Airlines pages aren't permitted on this wiki
|day=07
|month=06
|year=2017
}}

'''Welcome on the Wiki page of Pavlin Stanchev Virtual Airlines.''' [[File:PSVA Airlines official symbol.jpg|thumb|This image is a official symbol of the VA. Also it has a presents to every livery on the VA's Livery package.]]
On this page you will find livery package and schedule of the airline.
The aircraft fleet is only boeing 777 family for the master.
Enyone interested add more aircrafts to the fleet must recreate the livery package for the plane he wants to use.

== '''<big>About the master</big>''' ==

My name is Pavlin Stanchev and I live and work in Sofia, Bulgaria.
I create this Virtual Airline company with my dearest friend Jason John Allen from Auckland, New Zealand.
As a pilot I has huge amount of flying with boeing 777-200ER model in Flightgear Flight Simulator. Also having all 777 family amount of flying. I've been trying other models but I found that the only plane I can make a comfortable flying and flight is the 777.
The main hub of the Virtual Airliner PSVA Airlines is LBSF / Sofia, Bulgaria/ witch is my hometown airport. Second important airport is NZAA - Auckland INTL At New Zealand, the airport of Jason town.
== '''<big>Flights of the VA</big>''' ==
Currently the VA will do only 3 flights but on 2 or 3 different transitions. For info look this table:

{| class="wikitable"
|-
! Number !! Flight !! Parts of the flight !! Information
|-
| PSVA 1 || LBSF-PHOG || 1. LBSF-EHAM
2. EHAM-CYVR
3. CYVR-PHOG
| 1. LBSF- EHAM: Gate: 3 RWY for takeoff: 27. Aircraft: Boeing 777-200LR. Cruise Alt: 26000 feet. RWY for landing: 18C. Gate: G6.waiting for 4 hours.
2. EHAM-CYVR. Gate: G6. RWY for takeoff: 18C. Aircraft: Boeing 777-200ER. Cruise ALT: 33000 feet. RWY for landing: 26L. Gate: on your disposal.
3. CYVR- PHOG. Gate: on your disposal. RWY for takeoff: 26L. Cruise ALT: 26000 feet. RWY for landing: 02. Gate: on your disposal.
|-
| PSVA 2 || LBSF-KJFK || 1.LBSF-LFPG
2.LFPG-KJFK
| 1. LBSF-LFPG. Gate: 3. RWY for takeoff: 27. Aircraft: 777-200. Cruise ALT: 26000 feet. RWY for landing: 26R. Gate: A43. Waiting for 1 hour.
2. LFPG-KJFK. Gate: A43. RWY for takeoff: 26R. Aircraft: Boeing 777-300. Cruise ALT: 31000 feet. RWY for landing: 04R. Gate: At your disposal.
|-
| PSVA 3 || LBSF-NZAA || 1.LBSF-OMDB
2.OMDB-NZAA
| 1. LBSF- OMDB. Gate: 3 . RWY for takeoff: 09 . Aircraft: boeing 777-300ER. Cruise ALT: 33000 feet. RWY for landing: 12R. Gate: on your disposal. Waiting for one day and 1 hour.
2. OMDB - NZAA. Gate: On your disposal. RWY for takeoff: 12R. Akircraft: boeing 777-200LR. Cruise ALT: 38000 feet. RWY for landing: 05R. Gate: On Your disposal.
|}

The flights will be with default SID and APP. No specific routes needed. Enyone wants to do this flights with the common aircraft like Airbus planes or another it's free to do it. Here's a table of the aircrafts that makes this flights in real world:
{| class="wikitable"
|-
! Flight number !! parts with aircrafts
|-
| PSVA 1 || 1. LBSF- EHAM. Aircraft: A320
2. EHAM-CYVR. Aircraft: A330
3. CYVR-PHOG. Aircraft: 777-300
|-
| PSVA 2 || 1.LBSF-LFPG. Aircraft: Embraer 190
2.LFPG- KJFK. Aircraft: A330-300
|-
| PSVA 3 || 1. LBSF- OMDB. Aircraft: Boeing 737-800.
2.OMDB- NZAA. Aircraft: A380-800
|}

We will support all aircrafts listed in this tables with the livery package. We want you to know, that our custum livery is not 1. We has a different livery for every different flight in this listings. For crossing the Atlantic Ocean flights we has Livery, called PSVA Ocean. For the smollest flights aroud Europe we make a livery PSVA Local. The main livery can be used in every flight, but that is not necessary.

== '''<big>Small local flights</big>''' ==

The VA will make also a smaller flights from Europe countries to Sofia and other city's in Bulgaria. All smaller flights will be on PSVA Local Livery. For more information of the destinations airports on Europe see this map:
[https://drive.google.com/open?id=1l4OYyRjoFOIQqPc359RDXoOe8Us&usp=sharing PSVA Airlines smaller flights map]

== '''<big>Details</big>''' ==

This virtual company is dedicated on the quality passengers flying. So for every takeoff, taxi operations, startup, turn off or any operations, dedicated to the creation and making of local or internationals flights it have to be saved. The VA has a google account, witch can be accessed by members of the VA. So every pilot has a dedication to safe his flight recorded tapes for inspection and rewards. Rewards are:

* Pilot of the mount - for most hight quality percentige of the pilot for the mount, calculated on the base of the flights, that this pilot has do for the mount
* Pilot of the year - reward of the hight quality percentige of flying on a pilot for the whole year
* Challenger service - special reward of a pilot with hight skills of takeoff, landing etc in bad wether conditions or challenging airport like VQPR or another.
* Dedication price - reward for most dedicated pilot in a mount or a year. No need of quality rate to calculate.

The company will do also a multiplayer flight events. For more information you can connect the founders of the VA.
A sign form for participation of the VA you can find on this link:
[https://docs.google.com/forms/d/e/1FAIpQLSdTyyTGvE3PO08CU-VXnxvBsHt_1PkMSgMg7bJhBOjb4sx3nw/viewform Sighn form]

Any pilot wanna join is welcome. We are open to make any type of teaching of skills for the VA flights. Or ATC controller. Or development.

The VA currently is unactive. We need recruits. The website is in progress, the creator of it is bisy with oter staff right now. There is a temporary website in progress right now.

Airbus A310-300

2017-06-03T07:40:48Z

I4dnf: Undo revision 106583 by Flightgearnoob (talk)

{{infobox Aircraft
|image = A310-snap.png
|name = Airbus A310-300
| hangar = bermuda
|type = Airliner
|livery = Air Transat, PIA
|authors = Icecode and Star and ACJZA
|fdm = YAsim
|status-fdm = 3
|status-systems = 4
|status-cockpit = 3
|status-model = 0
|fgname = A310-300
}}'''This aircraft is in develoment by ACJZA'''

The '''Airbus A310-300''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Launched in July 1978, it was the second aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now owned by EADS. The A310 is a shortened derivative of the [[A300]], the first twin-engined widebody airliner.

== Aircraft help ==
{| class="keytable"
!Key
!Function
|-
|{{key press|Ctrl|b}}
|Speedbrakes
|-
|{{key press|Del}}
|Reverse thrust
|}

== External links ==
* [http://icestar-fghangar.web44.net/web/ A310 development progress can be viewed here]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=12790 A310 topic in Flightgear forum]
* [http://en.wikipedia.org/wiki/Airbus_A310 Airbus A310 Wikipedia article]

{{Airbus}}

[[Category:Airliners]]

Airbus A350 XWB/info

2017-06-03T07:37:50Z

I4dnf: Undo revision 107982 by Flightgearnoob (talk)

<includeonly>{{infobox aircraft
| name = Airbus A350
| image = a350picture.png
| type = Airliner
| config = Wide-body aircraft/Low wing aircraft
| propulsion = Jet aircraft
| manufacturer = Airbus
| authors = ACJZA/Sbyx/Pakistan-1/jormapaappa1235/Ho Zong Xi (MIA2000)/dtlan201
| author1 = Joshua Davidson (it0uchpods/411)
| fdm = JSBSim
| fgname = A350-800/A350-900/A350-1000
| status = Under development
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Airbus A350]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Boeing 737-400/info

2017-05-19T15:36:59Z

I4dnf: Undo revision 106336 by Flightgearnoob (talk)

<includeonly>{{infobox aircraft
| name = Boeing 737-400
| image = 737-400.png
| alt = Boeing 737-400 at Frankfurt Main EDDF
| type = Airliner
| config = Narrow-body aircraft/Low wing aircraft
| propulsion = Jet aircraft
| manufacturer = Boeing
| authors = David Culp/Innis Cunningham/FlightGear Iespaña Team
| fdm = JSBSim
| fgname = 737-400
| status = In-Development
| download = https://web.archive.org/web/20110906175841/http://flightgear.iespana.es/
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Boeing 737-400]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Airbus A350 XWB/info

2017-05-19T15:32:51Z

I4dnf: Undo revision 106729 by Flightgearnoob (talk)

YASim

2017-03-20T08:43:36Z

I4dnf: Fix fdm tag <aircraf>t-><airplane>, fix spelling

'''YASim''' is one of two [[flight dynamics model]]s commonly used in [[FlightGear]]. The flight dynamics model (FDM) determines how the [[aircraft]] moves and flies.

Gary Neely wrote in his [http://www.buckarooshangar.com/flightgear/ introduction to YASim]:

:''The FDM is the mathematical model that controls the physics of flight within the simulator. The physical 3D aircraft model has nothing to do with flight dynamics-- in essence it's just a picture to look at. It's the FDM that dictates how the model flies.''

:''Why YASim? YASim uses the geometry of the aircraft to generate the base flight characteristics. While this suggests a 'realistic' or out-of-the-box approach, it is a only rough approximation that will require much tweaking before you get a result that approaches realism. If you have solid flight data for your aircraft such as wind-tunnel data or you are looking to eventually generate a hyper-realistic simulation, JSBSim is probably a better approach. If you lack such data but know the geometry of the aircraft and have access to the same flight characteristics and limits as a real pilot would, then YASim can provide a solution that is more than sufficient for most simulation needs.''

== Coordinate system notes ==
All positions specified are in metres (which is weird, since all other units in the file are English). The X axis points forward, Y is left, and Z is up. Take your right hand, and hold it like a gun. Your first and second fingers are the X and Y axes, and your upwards-pointing thumb is the Z. This is slightly different from the coordinate system used by [[JSBSim]]. Sorry. The origin can be placed anywhere, so long as you are consistent. I use the nose of the aircraft.

(In the [[JSBSim_Aerodynamics#Frames|JSBSim coordinate system]], X and Z are the same as in YASim, but Y points to the right instead of left.)

== XML Elements ==

=== airplane ===
The top-level element for the file. It contains the following attributes:
* '''mass:''' The empty (no fuel) weight, in pounds. It does include the weight of the engine(s), so when you add the engine weight in its tag, it acts just like a ballast.
* '''version:''' The version attribute is used to maintain compatibility when updating yasim (e.g. bugfixes). If this attribute i not given, the original version will be used. Several bugfixes to YASim were implemented in FlightGear 3.2 (see [[FlightGear Newsletter April 2014]]), some more are fixed in FlightGear 2017.2.
Available versions are:
* <code>YASIM_VERSION_ORIGINAL</code> explicitly use the old buggy calculations (same as no version attribute at all)
* <code>YASIM_VERSION_32</code> enable bugfixes up to version 3.2
* <code>2017.2</code> enable bugfixes up to version 2017.2
* <code>YASIM_VERSION_CURRENT</code> use latest version compiled into the users FlightGear. This might be dangerous in case of future changes.

=== approach ===
The approach parameters for the aircraft. The solver will generate an aircraft that matches these settings. The element can (and should) contain <control> elements indicating pilot input settings, such as flaps and throttle, for the approach.
* '''speed:''' The approach airspeed, in knots TAS.
* '''aoa:''' The approach angle of attack, in degrees
* '''fuel:''' Fraction (0-1) of fuel in the tanks. Default is 0.2.
=== cruise ===
The cruise speed and altitude for the solver to match. As above, this should contain <control> elements indicating aircraft configuration. Especially, make sure the engines are generating enough thrust at cruise!
* '''speed:''' The cruise speed, in knots TAS.
* '''alt:''' The cruise altitude, in feet MSL.
* '''fuel:''' Fraction (0-1) of fuel in the tanks. Default is 0.2.
=== cockpit ===
The location of the cockpit (pilot eyepoint).
* '''x,y,z:''' eyepoint location (see coordinates note)

=== fuselage ===
This defines a tubelike structure. It will be given an even mass and aerodynamic force distribution by the solver. You can have as many as you like, in any orientation you please.
* '''ax,ay,az:''' One end of the tube (typically the front)
* '''bx,by,bz:''' The other ("back") end.
* '''width:''' The width of the tube, in metres.
* '''taper:''' The approximate radius at the "tips" of the fuselage expressed as a fraction (0-1) of the width value.
* '''midpoint:''' The location of the widest part of the fuselage, expressed as a fraction of the distance between A and B.
* '''idrag:''' Multiplier for the "induced drag" generated by this object. Default is one. With idrag=0 the fuselage generates only drag.
* '''cx,cy,cz:''' Factors for the generated drag in the fuselages "local coordinate system" with x pointing from end to front, z perpendicular to x with y=0 in the aircraft coordinate system. E.g. for a fuselage of a height of 2 times them width you can define cy=2 and (due to the doubled front surface) cx=2.

=== Surfaces ===
==== wing ====
This defines the main wing of the aircraft. You can have only one (but see below about using vstab objects for extra lifting surfaces). The wing should have a <stall> subelement to indicate stall behavior, control surface subelements (flap0, flap1, spoiler, slat) to indicate what and where the control surfaces are, and <control> subelements to map user input properties to the control surfaces.
* '''x,y,z:''' The "base" of the wing, specified as the location of the mid-chord (not leading edge, trailing edge, or aerodynamic center) point at the root of the LEFT (!) wing.
* '''length:''' The length from the base of the wing to the midchord point at the tip. Note that this is not the same thing as span.
* '''chord:''' The chord of the wing at its base, along the X axis (not normal to the leading edge, as it is sometimes defined).
* '''incidence:''' The incidence angle at the wing root, in degrees. Zero is level with the fuselage (as in an aerobatic plane), positive means that the leading edge is higher than the trailing edge (as in a trainer).
* '''twist:''' The difference between the incidence angle at the wing root and the incidence angle at the wing tip. Typically, this is a negative number so that the wing tips have a lower angle of attack and stall after the wing root (washout).
* '''taper:''' The taper fraction, expressed as the tip chord divided by the root chord. A taper of one is a hershey bar wing, and zero would be a wing ending at a point. Defaults to one.
* '''sweep:''' The sweep angle of the wing, in degrees. Zero is no sweep, positive angles are swept back. Defaults to zero.
* '''dihedral:''' The dihedral angle of the wing. Positive angles are upward dihedral. Defaults to zero.
* '''idrag:''' Multiplier for the "induced drag" generated by this surface. In general, low aspect wings will generate less induced drag per-AoA than high aspect (glider) wings. This value isn't constrained well by the solution process, and may require tuning to get throttle settings correct in high AoA (approach) situations.
* '''effectiveness:''' Multiplier for the "normal" drag generated by the wing. Defaults to 1. Arbitrary, dimensionless factor.
* '''camber:''' The lift produced by the wing at zero angle of attack, expressed as a fraction of the maximum lift produced at the stall AoA.

==== hstab ====
These defines the horizontal stabilizer of the aircraft. Internally, it is just a wing object and therefore works the same in XML. You are allowed only one hstab object; the solver needs to know which wing's incidence to play with to get the aircraft trimmed correctly.

==== vstab ====
A "vertical" stabilizer. Like hstab, this is just another wing, with a few special properties. The surface is not "mirrored" as are wing and hstab objects. If you define a left wing only, you'll only get a left wing. The default dihedral, if unspecified, is 90 degrees instead of zero. But all parameters are equally settable, so there's no requirement that this object be "vertical" at all. You can use it for anything you like, such as extra wings for biplanes. Most importantly, these surfaces are not involved with the solver computation, so you can have none, or as many as you like.

==== mstab ====
A mirrored horizontal stabilizer. Exactly the same as wing, but not involved with the solver computation, so you can have none, or as many as you like.

==== stall ====
A subelement of a wing (or hstab/vstab/mstab) that specifies the stall behavior.
* '''aoa:''' The stall angle (maximum lift) in degrees. Note that this is relative to the wing, not the fuselage (since the wing may have a non-zero incidence angle).
* '''width:''' The "width" of the stall, in degrees. A high value indicates a gentle stall. Low values are viscious for a non-twisted wing, but are acceptable for a twisted one (since the whole wing will not stall at the same time).
* '''peak:''' The height of the lift peak, relative to the post-stall secondary lift peak at 45 degrees. Defaults to 1.5. This one is deep voodoo, and probably doesn't need to change much. Bug me for an explanation if you're curious.

==== flap0, flap1, slat, spoiler ====
These are subelements of wing/hstab/vstab objects, and specify the location and effectiveness of the control surfaces.
* '''start:''' The position along the wing where the control surface begins.Zero is the root, one is the tip.
* '''end:''' The position where the surface ends, as above.
* '''lift:''' The lift multiplier for a flap or slat at full extension. One is a no-op, a typical aileron might be 1.2 or so, a giant jetliner flap 2.0, and a spoiler 0.0. For spoilers, the interpretation is a little different -- they spoil only "prestall" lift. Lift due purely to "flat plate" effects isn't affected. For typical wings that stall at low AoA's essentially all lift is pre-stall and you don't have to care. Jet fighters tend not to have wing spoilers, for exactly this reason. This value is not applicable to slats, which affect stall AoA only.
* '''drag:''' The drag multiplier, as above. Typically should be higher than the lift multiplier for flaps.
* '''aoa:''' Applicable only to slats. This indicates the angle by which the stall AoA is translated by the slat extension.

=== Engine ===
==== Thruster ====
A very simple "thrust only" engine object. Useful for things like thrust vectoring nozzles. All it does is map its THROTTLE input axis to its output thrust rating. Does not consume fuel, etc...
* '''thrust:''' Maximum thrust in pounds
* '''x,y,z:''' The point on the airframe where thrust will be applied.
* '''vx,vy,vy:''' The direction of the thrust in airframe coordinates. The vector will be normalized automatically, so any non-zero vector will work fine.

==== Jet ====
A turbojet/fan engine. It accepts a <control> subelement to map a property to its throttle setting, and an <actionpt> subelement to place the action point of the thrust at a different position than the mass of the engine.
* '''x,y,z:''' The location of the engine, as a point mass. If no actionpt is specified, this will also be the point of application of thrust.
* '''mass:''' The mass of the engine, in pounds.
* '''thrust:''' The maximum sea-level thrust, in pounds.
* '''afterburner:''' Maximum total thrust with afterburner/reheat, in pounds [defaults to "no additional thrust"].
* '''rotate:''' Vector angle of the thrust in degrees about the Y axis [0].
* '''n1-idle:''' Idling low pressure core / fan speed [55].
* '''n1-max:''' Maximum low pressure core / fan speed [102].
* '''n2-idle:''' Idling high pressure core speed [73].
* '''n2-max:''' Maximum high pressure core speed [103].
* '''tsfc:''' Thrust-specific fuel consumption [0.8]. This should be considerably lower for modern turbofans.
* '''atsfc:''' (version >= 2016.3.1) Thrust specific fuel consumption with afterburner on. When set to zero defaults to older behaviour where it is calculated from dry fuel consumption [0].
* '''egt:''' Exhaust gas temperature at takeoff in K [1050].
* '''epr:''' Engine pressure ratio at takeoff [3.0].
* '''exhaust-speed:''' The maximum exhaust speed in knots [~1555].
* '''spool-time:''' Time, in seconds, for the engine to respond to 90% of a commanded powersetting.

==== Propeller ====
A propeller. This element requires an engine subtag. Currently <piston-engine> and <turbine-engine> are supported.
* '''x,y,z:''' The position of the mass (!) of the engine/propeller combination. If the point of force application is different (and it will be) it should be set with an <actionpt> subelement.
* '''mass:''' The mass of the engine/propeller, in pounds.
* '''moment:''' The moment, in kg-metres^2. This has to be hand calculated and guessed at for now. A more automated system will be forthcoming. Use a negative moment value for counter-rotating ("European" -- CCW as seen from behind the prop) propellers. A good guess for this value is the radius of the prop (in metres) squared times the mass (kg) divided by three; that is the moment of a plain "stick" bolted to the prop shaft.
* '''radius:''' The radius, in metres, or the propeller.
* '''cruise-speed:''' The max efficiency cruise speed of the propeller. Generally not the same as the aircraft's cruise speed.
* '''cruise-rpm:''' The RPM of the propeller at max-eff. cruise.
* '''cruise-power:''' The power sunk by the prop at cruise, in horsepower.
* '''cruise-alt:''' The reference cruise altitude in feet.
* '''takeoff-power:''' The takeoff power required by the propeller...
* '''takeoff-rpm:''' ...at the given takeoff RPM.
* '''min-rpm:''' The minimum operational RPM for a constant speed propeller. This is the speed to which the prop governor will seek when the blue lever is at minimum. The coarse-stop attribute limits how far the governor can go into trying to reach this RPM.
* '''max-rpm:''' The maximum operational RPM for a constant speed propeller. See above. The fine-stop attribute limits how far the governor can go in trying to reach this RPM.
* '''fine-stop:''' The minimum pitch of the propeller (high RPM) as a ratio of ideal cruise pitch. This is set to 0.25 by default -- a higher value will result in a lower RPM at low power settings (e.g. idle, taxi, and approach).
* '''coarse-stop:''' The maximum pitch of the propeller (low RPM) as a ratio of ideal cruise pitch. This is set to 4.0 by default -- a lower value may result in a higher RPM at high power settings.
* '''gear-ratio:''' The factor by which the engine RPM is multiplied to produce the propeller RPM. Optional (defaults to 1.0).
* '''contra:''' When set (contra="1"), this indicates that the propeller is a contra-rotating pair. It will not contribute to the aircraft's net gyroscopic moment, nor will it produce asymmetric torque on the aircraft body. Asymmetric slipstream effects, when implemented, will also be zero when this is set.
* '''piston-engine:''' A piston engine definition. This must be a subelement of an enclosing <propeller> tag.
* '''eng-power:''' Maximum BHP of the engine at sea level.
* '''eng-rpm:''' The engine RPM at which eng-power is developed
* '''displacement:''' The engine displacement in cubic inches.
* '''compression:''' The engine compression ratio.

=== Landing gear ===
==== gear ====
Defines a landing gear. Accepts <control> subelements to map properties to steering and braking. Can also be used to simulate floats. Although the coefficients are still called ..fric, it is calculated in fluids as a drag (proportional to the square of the speed). In fluids gears are not considered to detect crashes (as on ground).
* '''x,y,z:''' The location of the fully-extended gear tip.
* '''compression:''' The distance in metres along the "up" axis that the gear will compress.
* '''initial-load:''' The initial load of the spring in multiples of compression. Defaults to 0. (With this parameter a lower spring-constants will be used for the gear-> can reduce numerical problems (jitter)) '''Note:''' the spring-constant is varied from 0% compression to 20% compression to get continuous behavior around 0 compression. (could be physically explained by wheel deformation)
* '''upx/upy/upz:''' The direction of compression, defaults to vertical (0,0,1) if unspecified. These are used only for a direction -- the vector need not be normalized, as the length is specified by "compression".
* '''sfric:''' Static (non-skidding) coefficient of friction. Defaults to 0.8.
* '''dfric:''' Dynamic friction. Defaults to 0.7.
* '''spring:''' A dimensionless multiplier for the automatically generated spring constant. Increase to make the gear stiffer, decrease to make it squishier.
* '''damp:''' A dimensionless multiplier for the automatically generated damping coefficient. Decrease to make the gear "bouncier", increase to make it "slower". Beware of increasing this too far: very high damping forces can make the numerics unstable. If you can't make the gear stop bouncing with this number, try increasing the compression length instead.
* '''on-water:''' if this is set to "0" the gear will be ignored if on water. Defaults to "0"
* '''on-solid:''' if this set to "0" the gear will be ignored if not on water. Defaults to "1"
* '''speed-planing:'''
* '''spring-factor-not-planing:''' At zero speed the spring factor is multiplied by spring-factor-not-planing. Above speed-planing this factor is equal to 1. The idea is, to use this for floats simulating the transition from swimming to planing. speed-planing defaults to 0, spring-factor-not-planing defaults to 1.
* '''reduce-friction-by-extension:''' at full extension the friction is reduced by this relative value. 0.7 means 30% friction at full extension. If you specify a value greater than one, the friction will be zero before reaching full extension. Defaults to "0"
* '''ignored-by-solver:''' with the on-water/on-solid tags you can have more than one set of gears in one aircraft, If the solver (who automatically generates the spring constants) would take all gears into account, the result would be wrong. E. G. set this tag to "1" for all gears, which are not active on runways. Defaults to "0". You can not exclude all gears in the solving process.

==== Launchbar ====
Defines a catapult launchbar or strop.
* '''x,y,z:''' The location of the mount point of the launch bar or strop on the aircraft.
* '''length:''' The length of the launch bar from mount point to tip
* '''down-angle:''' The max angle below the horizontal the launchbar can achieve.
* '''up-angle:''' The max angle above the horizontal the launchbar can achieve.
* '''holdback-{x,y,z}:''' The location of the holdback mount point on the aircraft.
* '''holdback-length:''' The length of the holdback from mount point to tip. Note: holdback up-angle and down-angle are the same as those defined for the launchbar and are not specified in the configuration.

=== Fuel ===
==== tank ====
A fuel tank. Tanks in the aircraft are identified numerically (starting from zero), in the order they are defined in the file. If the left tank is first, "tank[0]" will be the left tank.
* '''x,y,z:''' The location of the tank.
* '''capacity:''' The maximum contents of the tank, in pounds. Not gallons -- YASim supports fuels of varying densities.
* '''jet:''' A boolean. If present, this causes the fuel density to be treated as Jet-A. Otherwise, gasoline density is used. A more elaborate density setting (in pounds per gallon, for example) would be easy to implement. Bug me.

=== Center of Gravity ===
==== Ballast ====
This is a mechanism for modifying the mass distribution of the aircraft. A ballast setting specifies that a particular amount of the empty weight of the aircraft must be placed at a given location. The remaining non-ballast weight will be distributed "intelligently" across the fuselage and wing objects. Note again: this does NOT change the empty weight of the aircraft.
* '''x,y,z:''' The location of the ballast.
* '''mass:''' How much mass, in pounds, to put there. Note that this value can be negative. I find that I often need to "lighten" the tail of the aircraft.

==== Weight ====
This is an added weight, something not part of the empty weight of the aircraft, like passengers, cargo, or external stores. The actual value of the mass is not specified here, instead, a mapping to a property is used. This allows external code, such as the panel, to control the weight (loading a given cargo configuration from preference files, dropping bombs at runtime, etc...)
* '''x,y,z:''' The location of the weight.
* '''mass-prop:''' The name of the fgfs property containing the mass, in pounds, of this weight.
* '''size:''' The aerodynamic "size", in metres, of the object. This is important for external stores, which will cause drag. For reasonably aerodynamic stuff like bombs, the size should be roughly the width of the object. For other stuff, you're on your own. The default is zero, which results in no aerodynamic force (internal cargo).
* '''solve-weight:''' Subtag of approach and cruise parameters. Used to specify a non-zero setting for a <weight> tag during solution. The default is to assume all weights are zero at the given performance numbers.
* '''idx:''' Index of the weight in the file (starting with zero).
* '''weight:''' Weight setting in pounds.

=== Controls ===
==== control-input ====
This element manages a mapping from fgfs properties (user input) to settable values on the aircraft's objects. Note that the value to be set MUST (!) be valid on the given object type. This is not checked for by the parser, and will cause a runtime crash if you try it. Wing's don't have throttle controls, etc... Note that multiple axes may be set on the same value. They are summed before setting.
* '''axis:''' The name of the double-valued fgfs property "axis" to use as input, such as "/controls/flight/aileron".
* '''control:''' Which control axis to set on the objects. It can have the following values:
** THROTTLE - The throttle on a jet or propeller.
** MIXTURE - The mixture on a propeller.
** REHEAT - The afterburner on a jet
** PROP - The propeller advance
** BRAKE - The brake on a gear.
** STEER - The steering angle on a gear.
** INCIDENCE - The incidence angle of a wing.
** FLAP0 - The flap0 deflection of a wing.
** FLAP1 - The flap1 deflection of a wing.
** SLAT - The slat extension of a wing.
** SPOILER - The spoiler extension for a wing.
** CYCLICAIL - The "aileron" cyclic input of a rotor
** CYCLICELE - The "elevator" cyclic input of a rotor
** COLLECTIVE - The collective input of a rotor
** ROTORENGINEON - If not equal zero the rotor is rotating
** WINCHRELSPEED - The relative winch speed
** {... and many more, see ControlMap.cpp ...}
* '''invert:''' Negate the value of the property before setting on the object.
* '''split:''' Applicable to wing control surfaces. Sets the normal value on the left wing, and a negated value on the right wing.
* '''square:''' Squares the value before setting. Useful for controls like steering that need a wide range, yet lots of sensitivity in the center. Obviously only applicable to values that have a range of [-1:1] or [0:1].
* '''src0/src1/dst0/dst1:''' If present, these define a linear mapping from the source to the output value. Input values in the range src0-src1 are mapped linearly to dst0-dst1, with clamping for input values that lie outside the range.

==== control-output ====
This can be used to pass the value of a YASim control axis (after all mapping and summing is applied) back to the property tree.
* '''control:''' Name of the control axis. See above.
* '''prop:''' Property node to receive the value.
* '''side:''' Optional, for split controls. Either "right" or "left"
* '''min/max:''' Clamping applied to output value.

==== control-speed ====
Some controls (most notably flaps and hydraulics) have maximum slew rates and cannot respond instantly to pilot input. This can be implemented with a control-speed tag, which defines a "transition time" required to slew through the full input range. Note that this tag is semi-deprecated, complicated control input filtering can be done much more robustly from a Nasal script.
* '''control:''' Name of the control axis. See above.
* '''transition-time:''' Time in seconds to slew through input range.

==== control-setting ====
This tag is used to define a particular setting for a control axis inside the <cruise> or <approach> tags, where obviously property input is not available. It can be used, for example, to inform the solver that the approach performance values assume full flaps, etc...
* '''axis:''' Name of the control input (i.e. a property name)
* '''value:''' Value of the control axis.

=== Winch and Aerotow ===
==== hitch ====
A hitch, can be used for winch-start (in gliders) or aerotow (in gliders and motor aircraft) or for external cargo with helicopter. You can do aerotow over the net via multiplayer (see j3 and bocian as an example).
* '''name:''' the name of the hitch. must be aerotow if you want to do aerotow via multiplayer. You will find many properties at /sim/hitches/name. Most of them are directly tied to the internal variables, you can modify them as you like. You can add a listener to the property "broken", e. g. for playing a sound.
* '''x,y,z:''' The position of the hitch
* '''force-is-calculated-by-other:''' if you want to simulate aerotowing over the internet, set this value to "1" in the motor aircraft. Don't specify or set this to zero in gliders. In a LAN the time lag might be small enough to set it on both aircraft to "0". It's intended, that this is done automatically in the future.
==== tow ====
The tow used for aerotow or winch. This must be a subelement of an enclosing <hitch> tag.
* '''length:''' upstretched length in metres
* '''weight-per-meter:''' in kg/metre
* '''elastic-constant:''' lower values give higher elasticity
* '''break-force:''' in N
* '''mp-auto-connect-period:''' the every x seconds a towed multiplayer aircraft is searched. If found, this tow is connected automatically, parameters are copied from the other aircraft. Should be set only in the motor aircraft, not in the glider
==== winch ====
The tow used for aerotow or winch. This must be a subelement of an enclosing <hitch> tag.
* '''max-tow-length:''' in m
* '''min-tow-length''': in m
* '''initial-tow-length:''' in m. The initial tow length also defines the length/search radius used for the mp-autoconnect feature
* '''max-winch-speed:''' in m/s
* '''power:''' in kW
* '''max-force:''' in N

== Visualization ==
[[File:Yasim_visualisation_dc6.png|thumb|dc6 fdm in Blender]]To make the programmed aircraft visible it is possible to load and compare it with the 3D model within [[Blender]]. The applaud for this ''very'' usefull script goes to M. Franz, thank you very much!

For Blender versions <= 2.4 the script is located in FlightGears source code [http://mapserver.flightgear.org/git/?p=flightgear;a=blob_plain;f=utils/Modeller/yasim_import.py;hb=HEAD utils/Modeller/yasim_import.py].

For Blender versions newer than 2.4, please see [[Blender YASim import]].

The howto, taken from inside the script:

yasim_import.py loads and visualizes a YASim FDM geometry
=========================================================

It is recommended to load the model superimposed over a greyed out and immutable copy of the aircraft model:

(0) put this script into ~/.blender/scripts/
(1) load or import aircraft model (menu -> "File" -> "Import" -> "AC3D (.ac) ...")
(2) create new *empty* scene (menu -> arrow button left of "SCE:scene1" combobox -> "ADD NEW" -> "empty")
(3) rename scene to yasim (not required)
(4) link to scene1 (F10 -> "Output" tab -> arrow button left of text entry "No Set Scene" -> "scene1")
(5) now load the YASim config file (menu -> "File" -> "Import" -> "YASim (.xml) ...")

This is good enough for simple checks. But if you are working on the YASim configuration, then you need a
quick and convenient way to reload the file. In that case continue after (4):

(5) switch the button area at the bottom of the blender screen to "Scripts Window" mode (green python snake icon)
(6) load the YASim config file (menu -> "Scripts" -> "Import" -> "YASim (.xml) ...")
(7) make the "Scripts Window" area as small as possible by dragging the area separator down
(8) optionally split the "3D View" area and switch the right part to the "Outliner"
(9) press the "Reload YASim" button in the script area to reload the file

If the 3D model is displaced with respect to the FDM model, then the <offsets> values from the
model animation XML file should be added as comment to the YASim config file, as a line all by
itself, with no spaces surrounding the equal signs. Spaces elsewhere are allowed. For example:

<offsets>
<x-m>3.45</x-m>
<z-m>-0.4</z-m>
<pitch-deg>5</pitch-deg>
</offsets>

becomes:



Possible variables are:

x ... <x-m>
y ... <y-m>
z ... <z-m>
h ... <heading-deg>
p ... <pitch-deg>
r ... <roll-deg>

Of course, absolute FDM coordinates can then no longer directly be read from Blender's 3D view.
The cursor coordinates display in the script area, however, shows the coordinates in YASim space.
Note that object names don't contain XML indices but element numbers. YASim_hstab#2 is the third
hstab in the whole file, not necessarily in its parent XML group. A floating point part in the
object name (e.g. YASim_hstab#2.004) only means that the geometry has been reloaded that often.
It's an unavoidable consequence of how Blender deals with meshes.

Elements are displayed as follows:

cockpit -> monkey head
fuselage -> blue "tube" (with only 12 sides for less clutter); center at "a"
vstab -> red with yellow flaps
wing/mstab/hstab -> green with yellow flaps/spoilers/slats (always 20 cm deep);
symmetric surfaces are only displayed on the left side
thrusters (jet/propeller/thruster) -> dashed line from center to actionpt;
arrow from actionpt along thrust vector (always 1 m long);
propeller circle
rotor -> radius and rel_len_blade_start circle, direction arrow,
normal and forward vector, one blade at phi0
gear -> contact point and compression vector (no arrow head)
tank -> cube (10 cm side length)
weight -> inverted cone
ballast -> cylinder
hitch -> circle (10 cm diameter)
hook -> dashed line for up angle, T-line for down angle
launchbar -> dashed line for up angles, T-line for down angles
A note about step (0) for Windows users: the mentioned path is inside the folder where Blender lives, something like <code>C:\Program Files\Blender Foundation\Blender\.blender\scripts</code>.

== Command Line ==
=== Windows ===
By using the standard command line, we can see what the YASim solver is calculating. First, open up Command Prompt, enter in the location of yasim.exe, and then the location of the YASim XML file. For example, here's what you would type in for a standard Windows [[Changelog_2.12|FlightGear 2.12.0]] installation, and viewing the [[F-14_Tomcat|F-14B's]] YASim file.
{{Note|You can copy & paste the examples into Command Prompt by right-clicking on the title and navigate to Edit > Paste. Then, click Enter to execute.}}

<code>"C:\Program Files\FlightGear\bin\Win32\yasim.exe" "C:\Program Files\FlightGear\data\Aircraft\f-14b\f-14b-yasim.xml"</code>

The results will give many different values.

* '''Drag Coefficient:''' The drag coefficient of the aircraft.
* '''Lift Ratio:''' The lift ratio of the aircraft.
* '''Cruise AoA:''' The cruise AoA, from conditions at [[YASim#cruise|<cruise>]] in the xml file.
* '''Tail Incidence:''' The incidence angle of the tail, "solved" by YASim as a way to stabilize the aircraft.
* '''Approach Elevator:''' The approach elevator, from conditions at [[YASim#approach|<approach>]] in the xml file.
* '''CG:''' Center of gravity of the aircraft in coordinates. Unless it's supposed to be offset, it should always have a Y value of 0.

The YASim standalone solver also has some command line flags that change it's behaviour.

<code>"C:\Program Files\FlightGear\bin\Win32\yasim.exe" "C:\Program Files\FlightGear\data\Aircraft\f-14b\f-14b-yasim.xml" -g -a 1000 -s 490</code>

* '''-g:''' Instructs YASim to generate space-separated tabular data instead of the usual solver output. This can be redirected to a file and used in various plotting programs to visualize the actual lift, drag, L/D curves. The columns of the output from left to right are: AoA, Lift, Drag, L/D. (aoa in degrees, lift and drag in G's).
* '''-a <altitude in meter:>''' Run the solver at the given altitude in meter.
* '''-s <speed in knots>:''' Also run at the given airspeed in knots.

{{Note|The values generated by this method are for the aircraft taken as a whole, as solved by YASim, so they differ from the values of the wing airfoil.}}

To get the tabular output for the example above at 1000 m and 150 knots, and to redirect this to a file, one would issue:

<code>"C:\Program Files\FlightGear\bin\Win32\yasim.exe" "C:\Program Files\FlightGear\data\Aircraft\f-14b\f-14b-yasim.xml" -g -a 1000 -s 150 > "C:\Program Files\FlightGear\yasim.txt"</code>

== YASim design notes ==
Andy Ross's original design notes for YASim can be found in [ftp://ftp.uni-duisburg.de/FlightGear/Docs/YASim-simnotes.pdf this PDF file]. These provide some useful background for how YASim works.

== New features and bugfixes in version 2017.2 ==
The following is under development and hopefully finds its way into FG version 2017.2

=== XML parser support for metric and imperial units ===
To make live easier for aircraft developers, the parser supports new additional attributes with a unit suffix, e.g. speed-kt for knots and speed-kmh for kilometer per hour.
* <code><airplane {mass, mass-lbs, mass-kg}="12345" ></code>
* <code><approach {speed, speed-kt, speed-kmh}="123" ></code>
* <code><cruise {speed, speed-kt, speed-kmh}="123" ></code>
* <code><solve-weight {weight, weight-lbs, weight-kg}="123" ></code>
* <code><jet {mass, mass-lbs, mass-kg}="1234" ></code>
* <code><tank {capacity, capacity-lbs, capacity-kg}="12345" ></code>
* <code><ballast {mass, mass-lbs, mass-kg}="1234" ></code>

'''Please note:''' aircraft using this new attibutes will not run on older versions of flightgear, so it is probably wise to publish those only after a reasonable number of users switched version 2017.2 or newer.

=== Export of YASim internals to property tree ===
Ever wondered what is going on inside yasim. Lots of information will be available in the property tree soon
in <code> /fdm/yasim/ </code>.
Some information is static and shows what yasim has compiled from your XML.
Other information is "run-time" like forces, speed, acceleration, c.g., mass you-name-it
(2DO: write details here)

=== Aircraft developer helpers ===
The command line utility got some new options. For some strange reason, the -a parameter expects altitude in meters instead of ft. This is now visible in the usage message but left unchanged for compatibility.
<syntaxhighlight>Usage:
yasim <aircraft.xml> [-g [-a meters] [-s kts] [-approach | -cruise] ]
yasim <aircraft.xml> [-d [-a meters] [-approach | -cruise] ]
yasim <aircraft.xml> [-m]
-g print lift/drag table: aoa, lift, drag, lift/drag
-d print drag over TAS: kts, drag
-a set altitude in meters!
-s set speed in knots
-m print mass distribution table: id, x, y, z, mass</syntaxhighlight>

=== Bugfixes ===
The following bugfixes require <airplane version="2017.2"> for backward compatibility
* Ground effect: corrected the calculation of the height where g.e. ends
* Stall parameters were set wrong for wings with camber=0

== Related content ==
* [[Howto:Make a helicopter#XML Elements]] – Rotor and rotorgear YASim elements

== External links ==
* [http://www.buckarooshangar.com/flightgear/yasimtut.html Gary "Buckaroo" Neely's guide to YASim] – Very helpful guide

{{FDM}}

[[Category:Flight Dynamics Model]]

[[fr:YASim]]

Command line options

2016-10-18T14:05:26Z

I4dnf: /* General Options */ clarify AI models/traffic related options

'''Command line options''' are a common way to tell applications what to do/how to act on startup. With [[FlightGear]] they are used for many things, from simple ones like selecting an aircraft up to complex stuff like network traffic and weather parameters.

The easiest way to handle those options for FlightGear (''fgfs'') is using a tool with a graphical user interface like ''[[fgrun]]'' on Windows and GNU/Linux or the Mac OS X GUI-Launcher ("fgfs --launcher"). This way one don't have to bother 'bout them at all. 
However, there are users who don't want or are not able to run a GUI and therefore are interested in this. Those who need them or just want to learn more about FlightGear, but have no idea what we are talking about, may read the wiki page on the general usage of the [[command line]].

A good place to store the personal options is a file called [[fgfsrc]]. This file is read by ''fgfs'' on each startup.

The following lists show the options for ''fgfs'' including a short description and sorted by categories. Please have in mind that keeping those lists up to date on the wiki is not an easy task. Also there are different versions of FlightGear out there which don't share exactly the same options. Therefore you better also check your versions ones with <code>fgfs --help --verbose</code>. If this command fails, you may add the option <code>--fg-root=[path]</code> as well, see below. 
It is sad but true, not even this command is, at least in Git, up to date all the time. At the time of writing at least one option which is supported is not shown with <code>fgfs --help --verbose</code>. So if you have serious issues with an option, the source code is, as always, also the best source for info. In the file ''src/Main/options.cxx'' all the options are listed with their hard coded ''default'' setting and type. 
The file [[$FG_ROOT]]/options.xml is used to generate the output for <code>fgfs --help [--verbose]</code>. That's the reason why <code>--fg-root=[path]</code> has to be added to this, if it is not set as environmental variable or as option in fgfsrc.

Usage: <code>fgfs [OPTION [OPTION ...]]</code>

==== General Options ====

--help, -h Show the most relevant command line options
--verbose, -v Show all command line options when combined
with --help or -h
--fg-root=path Specify the root data path
--fg-scenery=path[:path...] Specify the base scenery path;
Defaults to [[$FG_ROOT]]/Scenery
(--language=code Select the language for this session
*Not* supported in 1.9.1 and Git atm!)
--launcher Enable Qt launcher
--disable-fullscreen Disable full-screen game mode
--enable-fullscreen Enable full-screen game mode
--disable-splash-screen Disable splash screen
--enable-splash-screen Enable splash screen
--disable-mouse-pointer Disable extra mouse pointer
--enable-mouse-pointer Enable extra mouse pointer
(i.e. for full screen Voodoo based cards)
--disable-random-objects Exclude random scenery objects
(buildings, etc.)
--enable-random-objects Include random scenery objects
(buildings, etc.)
--disable-ai-models Disable the AI subsystem.
(This also disables showing the models of other
multiplayer aircraft)
--enable-ai-models Enable the AI subsystem.
--disable-ai-traffic Disable the autogenerated traffic subsystem.
--enable-ai-traffic Enable the autogenerated traffic subsystem.
--disable-freeze Start in a running state
--enable-freeze Start in a frozen state
--disable-fuel-freeze Fuel is consumed normally
--enable-fuel-freeze Fuel tank quantity forced to remain constant
--disable-clock-freeze Clock advances normally
--enable-clock-freeze Do not advance clock
--enable-auto-coordination Enable auto coordination - rudder and
ailerons will be controlled together
--disable-auto-coordination Disable auto coordination (default)
--browser-app=path Specify path to your web browser
--prop:name=value Set property to
--config=path Load additional properties from path
--units-feet Use feet for distances
--units-meters Use meters for distances
--ai-sc

==== Features ====

--disable-panel Disable instrument panel
--enable-panel Enable instrument panel
--disable-sound Disable sound effects
--enable-sound Enable sound effects
--disable-hud Disable Heads Up Display (HUD)
--enable-hud Enable Heads Up Display (HUD)
--disable-anti-alias-hud Disable anti-aliased HUD
--enable-anti-alias-hud Enable anti-aliased HUD
--disable-hud-3d Disable 3D HUD
--enable-hud-3d Enable 3D HUD
--ai-scenario=scenario Add and enable a new scenario. Multiple options
are allowed. Scenarios are in /[[$FG_ROOT]]/AI/.

==== Aircraft ====

--aircraft=name Select an aircraft profile as defined by a top
level -set.xml
--aircraft-dir=path Specify the exact directory to use for the
aircraft (normally not required, but may be
useful). Interpreted relatively to the
current directory. Causes the <path-cache>
from autosave_X_Y.xml, as well as
--fg-aircraft options and the FG_AIRCRAFT
environment variable to be bypassed.
--show-aircraft Print a list of the currently available
aircraft types

==== Flight Model ====

--fdm=name Select the core flight dynamics model
Can be one of jsb, larcsim, yasim, magic,
balloon, ada, external, or null
--aero=name Select aircraft aerodynamics model to load
--model-hz=n Run the FDM this rate (iterations per second)
--speed=n Run the FDM 'n' times faster than real time
--notrim Do NOT attempt to trim the model
(only with fdm=jsbsim)
--on-ground Start at ground level (default)
--in-air Start in air (implied when using --altitude)
--wind=DIR@SPEED Specify wind coming from DIR (degrees) at SPEED
(knots)
--turbulence=0.0 to 1.0 Specify turbulence from 0.0 (calm) to 1.0
(severe)
--ceiling=FT_ASL[:THICKNESS_FT]
Create an overcast ceiling, optionally with a
specific thickness (defaults to 2000 ft).

==== Initial Position and Orientation ====

--airport=ID Specify starting position relative to an
airport
--runway=rwy_no Specify starting runway (must also specify an
airport)
--vor=ID Specify starting position relative to a VOR
--ndb=ID Specify starting position relative to an NDB
--fix=ID Specify starting position relative to a fix
--airport=ID Specify airport (e.g. KOAK)
--parkpos=NAME Specify a gate at the airport (e.g. 747d11)
--offset-distance=nm Specify distance to reference point (statute
miles)
--offset-azimuth=degrees Specify heading to reference point
--lon=degrees Starting longitude (west = -)
--lat=degrees Starting latitude (south = -)
--altitude=value Starting altitude
(in feet unless --units-meters specified)
--heading=degrees Specify heading (yaw) angle (Psi)
--roll=degrees Specify roll angle (Phi)
--pitch=degrees Specify pitch angle (Theta)
--uBody=units_per_sec Specify velocity along the body X axis
(in feet unless --units-meters specified)
--vBody=units_per_sec Specify velocity along the body Y axis
(in feet unless --units-meters specified)
--wBody=units_per_sec Specify velocity along the body Z axis
(in feet unless --units-meters specified)
--vc=knots Specify initial airspeed
--mach=num Specify initial mach number
--glideslope=degrees Specify flight path angle (can be positive)
--roc=fpm Specify initial climb rate (can be negative)

==== Rendering Options ====

--bpp=depth Specify the bits per pixel
--fog-disable Disable fog/haze
--fog-fastest Enable fastest fog/haze
--fog-nicest Enable nicest fog/haze
--disable-horizon-effect Disable celestial body growth illusion near the
horizon
--enable-horizon-effect Enable celestial body growth illusion near the
horizon
--disable-enhanced-lighting Disable enhanced runway lighting
--enable-enhanced-lighting Enable enhanced runway lighting
--season=winter Enable snow covered scenery
--disable-distance-attenuation
Disable runway light distance attenuation
--enable-distance-attenuation
Enable runway light distance attenuation
--disable-specular-highlight
Disable specular reflections on textured
objects
--enable-specular-highlight Enable specular reflections on textured objects
--enable-clouds Enable 2D (flat) cloud layers
--disable-clouds Disable 2D (flat) cloud layers
--enable-clouds3d Enable 3D (volumetric) cloud layers
--disable-clouds3d Disable 3D (volumetric) cloud layers
--fov=degrees Specify field of view angle
--disable-fullscreen Disable fullscreen mode
--enable-fullscreen Enable fullscreen mode
--shading-flat Enable flat shading
--shading-smooth Enable smooth shading
--disable-wireframe Disable wireframe drawing mode
--enable-wireframe Enable wireframe drawing mode
--geometry=WxH Specify window geometry (640x480, etc)
--view-offset=value Specify the default forward view direction as
an offset from straight ahead. Allowable values
are LEFT, RIGHT, CENTER, or a specific number
in degrees
--visibility=meters Specify initial visibility
--visibility-miles=miles Specify initial visibility in miles

==== Hud Options ====

--hud-tris Hud displays number of triangles rendered
--hud-culled Hud displays percentage of triangles culled

==== Time Options ====

--timeofday={dawn,noon,dusk,midnight}
Specify a time of day
--time-offset=[+-]hh:mm:ss Add this time offset
--time-match-real Synchronize time with current time at chosen airport
--time-match-local Synchronize time with system time of computer
--start-date-sys=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
system time
--start-date-gmt=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Greenwich Mean Time
--start-date-lat=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Local Aircraft Time

==== Network Options ====

--httpd=port Enable http server on the specified port
--telnet=port Enable telnet server on the specified port
--jpg-httpd=port Enable screen shot http server on the specified
port

==== MultiPlayer Options ====

--callsign assign a unique name to a player
--multiplay={in|out},hz,address,port
Specify multipilot communication settings
multiple instances can be used

==== Route/Way Point Options ====

--wp=ID[@alt] Specify a waypoint for the GC autopilot;
multiple instances can be used
--flight-plan=file Read all waypoints from a file

==== IO Options ====

--generic=params Open connection using a predefined
communication interface and a preselected
communication protocol
--garmin=params Open connection using the Garmin GPS protocol
--joyclient=params Open connection to an Agwagon joystick
--jsclient=params Open connection to a remote joystick
--native-ctrls=params Open connection using the FG Native Controls
protocol
--native-fdm=params Open connection using the FG Native FDM
protocol
--native=params Open connection using the FG Native protocol
--nmea=params Open connection using the NMEA protocol
--opengc=params Open connection using the OpenGC protocol
--props=params Open connection using the interactive property
manager (LEGACY/DEAD DO NOT USE same as --telnet)
--pve=params Open connection using the PVE protocol
--ray=params Open connection using the Ray Woodworth motion
chair protocol
--rul=params Open connection using the RUL protocol
--atc610x Enable atc610x interface

Under Windows, you must use a special escape sequence if you need to specify a COM port higher than 9.

Example: --generic=\\.\COM10,out,1,/tmp/data.xml,myproto

This is per the Microsoft KB article here: http://msdn.microsoft.com/en-us/library/aa363858%28v=vs.85%29.aspx

==== Avionics Options ====

--nav1=[radial:]frequency Set the NAV1 radio frequency, optionally
preceded by a radial.
--nav2=[radial:]frequency Set the NAV2 radio frequency, optionally
preceded by a radial.
--adf=[rotation:]frequency Set the ADF radio frequency, optionally
preceded by a card rotation.
--dme={nav1|nav2|frequency} Slave the ADF to one of the NAV radios, or set
its internal frequency.

==== Environment Options ====

--disable-real-weather-fetch
Disable METAR based real weather fetching
--enable-real-weather-fetch Enable METAR based real weather fetching (this
requires an open internet connection)
--disable-horizon-effect Disable celestial body growth illusion near the
horizon
--enable-horizon-effect Enable celestial body growth illusion near the
horizon
--enable-clouds Enable 2D (flat) cloud layers
--disable-clouds Disable 2D (flat) cloud layers
--enable-clouds3d Enable 3D (volumetric) cloud layers
--disable-clouds3d Disable 3D (volumetric) cloud layers
--visibility=meters Specify initial visibility
--visibility-miles=miles Specify initial visibility in miles
--wind=DIR@SPEED Specify wind coming from DIR (degrees) at SPEED
(knots)
--turbulence=0.0 to 1.0 Specify turbulence from 0.0 (calm) to 1.0
(severe)
--ceiling=FT_ASL[:THICKNESS_FT]
Create an overcast ceiling, optionally with a
specific thickness (defaults to 2000 ft).
--random-wind

==== Situation Options ====

--failure={pitot|static|system|vacuum}
Fail the pitot, static, vacuum, or electrical
system (repeat the option for multiple system
failures).

==== Debugging Options ====

--log-level={bulk|debug|info|warn|alert}
Set the logging level for this session.
0=verbose, 5=alerts only
--pid=/pathto/some/file.pid Write current PID into file.
--trace-read=property Trace the reads for a property;
multiple instances can be used
--trace-write=property Trace the writes for a property;
multiple instances can be used

[[FlightGear 1.0 aircraft names for command line]] can be useful depending on what version and aircraft are installed.

== Related content ==
=== Wiki articles ===
* [[Command line]]

=== Source files ===
* {{fgdata file|options.xml}}
* {{flightgear file|src/Main/options.hxx}}
* {{flightgear file|src/Main/options.cxx}}

[[Category:Lists]]

[[de:Command Line Options]]
[[fr:Options de ligne de commande]]

IAR 80/info

2016-07-17T23:06:51Z

I4dnf: gplv2 not later

<includeonly>{{User:Bugman/Infobox Aircraft
| name = IAR 80
| image = Iar80-flight.jpg
| alt = The IAR 80 in its the default livery.
| image2 = Iar80-cockpit-dusk.jpg
| alt2 = The IAR 80's cockpit as dusk
| type = Fighter aircraft
| config = Low wing aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Industria Aeronautică Română (IAR)
| authors = Emilian Huminiuc (3D model, textures, YASim FDM)/Ron Jensen (JSBSim FDM)
| fdm = YASim/JSBSim
| fgname = IAR80-YASim
| status-fdm = 5
| status-systems = 4
| status-cockpit = 5
| status-model = 5
| download = {{gitlab zip file|user=emilianh|repo=IAR80}}
| license = CC-BY-NC-ND 4.0/GPLv2
| note = The JSBSim FDM is in beta
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[IAR 80]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Lockheed Model 10 Electra/info

2016-07-17T23:05:55Z

I4dnf: gplv2 not later

<includeonly>{{User:Bugman/Infobox Aircraft
| name = Lockheed Model 10 Electra
| hangar = emilianh
| aircraft = Lockheed-L10-Electra
| image = L10-glamour.jpg
| alt = Waiting For Amelia
| image2 = Electra 2.jpg
| alt2 = Lockheed Model 10 Electra in flight
| type = Airliner/Light airliner
| config = Low wing aircraft
| propulsion = Propeller aircraft/Twin-engine aircraft
| manufacturer = Lockheed
| authors = Emilian Huminiuc
| fdm = YASim
| fgname = Lockheed-L10-Electra
| status-fdm = 2
| status-systems = 1
| status-cockpit = 1
| status-model = 3
| license = CC-BY-NC-ND 4.0/GPLv2
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Lockheed Model 10 Electra]].
[[Category:Aircraft infobox documentation]]
</noinclude>

User talk:Bugman

2016-07-15T14:55:38Z

I4dnf:

== The collapsible script template ==
Noticed the {{tl|collapsible script}} template. That will probably come in handy in many places.

I had no idea that there was such a thing as <code>{{obr}}#'''tag''': {{cbr}}</code>. That may be useful later when I have played around with it.

Hmm, I see the template defaults to Dec Vadic's Imperial Arem Star. lol ;-)

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:12, 16 October 2015 (EDT)

: There are quite a few places in the wiki cluttered up by long scripts or code segments. I guess it is mainly Nasal, though some other parts could benefit from other templates using collapsible NavFrame elements. The <code>{{obr}}#'''tag''': {{cbr}}</code> concept is quite useful for programmatically adding tags in templates, avoiding the initial HTML parsing, but it isn't perfect. Anyway, I can see it spreading on the wiki already :) As for the template default, I hope no one is curious and tries it out!

:[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:14, 18 October 2015 (EDT)

: Let me add that <code>{{obr}}#'''tag''': {{cbr}}</code> allows for transclusion within any HTML tag, which is normally not possible.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:51, 19 October 2015 (EDT)

: ''The newsletter template discussion was moved to [[FlightGear wiki:Village pump#Newsletter templates]] ([http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=88787#Newsletter_templates perm]).''

== German FGAddon translation ==

Hi Edward,

are you still working on the [[De/FGAddon|German translation of the FGAddon article]]? If not, should I go ahead with the translation?

Cheers

[[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 05:32, 7 April 2016 (EDT)

: Hi! I'm on holiday and have been distracted by other work. Go for it!
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 23:52, 11 April 2016 (EDT)

:: Okay, thank you.
::[[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 00:10, 12 April 2016 (EDT)

== Lockheed P-38 Lightning ==
thanks for renaming that file... i can't believe that i misspelled that like that... sometimes the fingers think they know what the brain is trying to write :lol:
[[User:Wkitty42|Wkitty42]] ([[User talk:Wkitty42|talk]]) 11:16, 1 June 2016 (EDT)

: No problems! I often have the same problem :) Anyway, if you need any pages or files moved, just say.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:19, 1 June 2016 (EDT)

== The <aircraft>/info template ==

Hi,

It seems the new template for the aircraft info box or <aircraft>/info page doesn't show '_' (underscore) in the --aircraft= field. The old info box template did so it is probably a bug? [[User:AndersG|AndersG]] ([[User talk:AndersG|talk]]) 15:21, 23 June 2016 (EDT)

: Thanks for spotting that! I can see that that is a problem with the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23titleparts #titleparts] function: "All underscores are automatically replaced with spaces". That is rather annoying. I might then create {{param|fgname1}} to {{param|fgname10}} as an alternative, as the number of <code>*-set.xml</code> files with underscores is very low.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:38, 23 June 2016 (EDT)

== The so caled "Emilianh H's hangar" ==

Hi,

While I appreciate your efforts, I would also appreciate it if this labeling would be possibly omitted, also not directly linked to.

I would also had appreciated some sort of preliminary discussion/warning prior to such labeling/linking if it would have taken place.

Thanks for your understanding

[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:07, 15 July 2016 (EDT)

: No problems. I'm just experimenting with this, to allow for automated link creation for the new aircraft infobox template (see [[User:Bugman/Infobox Aircraft]]). This also includes the important note that the aircraft is {{tl|non-GPL}}. Note that in the end, all wiki aircraft pages will be identified by hangar when available. But for the <code>| hangar = emilianh</code> parameter value, the heading "Emilian H's Hangar" has been removed. See [[User:Bugman/Infobox Aircraft#IAR 80]].

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:16, 15 July 2016 (EDT)

:: Thanks, however unfortunatley link to "website" still shows. How about "Aircraft by $Name" instead of "$Name's hangar" ? what happens if $Name has n aircraft hosted in m places?

:: Regards,

::[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:22, 15 July 2016 (EDT)

::: I don't quite follow, but we should be able to expand on the [[User:Bugman/Infobox Aircraft]] to match all aircraft author's needs. That is the aim of this new template to replace {{tl|infobox aircraft}}. Click on the 'Edit' link, and then search for <code>emilianh</code> to see all the customisations I have made. We can change this to anything, to help automate the infobox creation. I thought I'd use your aircraft as a testing example for improving GitLab support in [[User:Bugman/Infobox Aircraft]] and [[:Category:Repository link templates]].

::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:30, 15 July 2016 (EDT)

::::The [[User:Bugman/Infobox Aircraft]] still displays the website and the devel-repo links. I, personally, for my aircraft, would prefer it if those were not ever shown, and only the download link was available. However I now noticed that on the actual [[IAR 80]] page it is properly hidden.
::::As for the second part of my previous question, what happens if I had say the iar80 hosted on github, the l10 on gitlab, and some other aircraft hosted on somesite.somwhere.else, to what does the "hangar" point to?
::::I understand that in this particular case you were using it to improve an example gitlab based "hangar".
::::Regards, [[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 10:55, 15 July 2016 (EDT)

User talk:Bugman

2016-07-15T14:22:54Z

I4dnf:

User talk:Bugman

2016-07-15T14:07:38Z

I4dnf: /* The so caled "Emilianh H's hangar" */ new section

IAR 80/info

2016-07-15T14:00:31Z

I4dnf: removed hangar, not a hangar, not intended to be a hangar, nor directly linked to. If the "hangar" feature can be used solely to ease maintainenace and not be displayed at all feel free to adapt. Thanks.

<includeonly>{{User:Bugman/Infobox Aircraft
| name = IAR 80
| image = Iar80-flight.jpg
| alt = The IAR 80 in its the default livery.
| image2 = Iar80-cockpit-dusk.jpg
| alt2 = The IAR 80's cockpit as dusk
| type = Fighter aircraft
| config = Low wing aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Industria Aeronautică Română (IAR)
| authors = Emilian Huminiuc (3D model, textures, YASim FDM)/Ron Jensen (JSBSim FDM)
| fdm = YASim/JSBSim
| fgname = IAR80-YASim
| status-fdm = 5
| status-systems = 4
| status-cockpit = 5
| status-model = 5
| download = {{gitlab zip file|user=emilianh|repo=IAR80}}
| license = CC-BY-NC-ND 4.0/GPLv2+
| note = The JSBSim FDM is in beta
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[IAR 80]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Howto:Install aircraft

2016-05-17T11:11:01Z

I4dnf: Undo revision 98286 by Taohu (talk)

{{installing}}

The latest official [[aircraft]] can be downloaded at [http://www.flightgear.org/download/ FlightGear.org Aircraft], which then usually require unzipping software to extract from a compressed file format. Then these must be manually installed in a FlightGear software installation to use. The details depend on the method of download, operating system, and user setup. Alternatively if you are using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], or you wish to manage your aircraft collection using version control tools, the aircraft can be obtained directly from the [[FGAddon|official FlightGear aircraft repository - FGAddon]].

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

=== Macintosh OS X ===
{{out of date}}

# Open GUI Launcher for FlightGear Mac
# Click on "Others" tab at middle right of launcher
# Click "Install Add-On Data" link at bottom of launcher
# Select aircraft folder from menu, and click "Open"
# Click OK on pop-up box.

Please note: For Mac users, the above will not work if you have not installed FG to the applications folder. If you do not want to put your version of FG in your applications folder, you can place it in a separate folder of your own creation. That will allow the above aircraft (& scenery) installation method to work correctly/

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

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

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

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

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

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

To fix this on Linux try this:

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

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

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

== For developers ==
Help develop the [[FlightGear Package Manager]] which is intended to support automatic aircraft and scenery installation, currently in alpha development and in need of testing.

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

[[Category:Howto|Install aircraft]]

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

Talk:Mumble

2016-04-24T07:58:55Z

I4dnf: /* Protect page request */

== Protect page request ==
Given the recent actions of a certain group of users, and given that their preferred method of evangelising is via mumble, I wonder if this page could be protected to edits, and any servers listed here could receive some minimal vetting.

[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 03:58, 24 April 2016 (EDT)

Talk:Mumble

2016-04-24T07:56:58Z

I4dnf: Created page with "== Protect page request == Given the recent actions of a certain group of users, and given that their preferred method of evangelising is via mumble, I wonder if this page cou..."

Mumble

2016-04-24T07:49:17Z

I4dnf: Chnaged server order to avoid confusion and missinformation.

{{Infobox Software
| title = Mumble
| logo =
| image =
| alt =
| developedby = Various
| initialrelease = 2005
| latestrelease = 1.2.15 (stable)
| writtenin = C++
| os = Windows, OS X, Linux, Android, iOS
| platform = PC, Mac, smartphones
| developmentstatus =
| developmentprogress =
| type = Voice chat software
| license = [https://github.com/mumble-voip/mumble/blob/master/LICENSE Open source]
| website = http://wiki.mumble.info/wiki/Main_Page
}}

[http://wiki.mumble.info/wiki/Main_Page Mumble] is a free, open source VoIP software used by some ATCs and pilots on the multiplayer network.

== Installation and configuration ==
# Download Mumble from its [http://wiki.mumble.info/wiki/Main_Page official website] (choose the links from the ''Stable Release'' column. If you're on Linux, you can usually install it using your package manager.
# Start it and follow the instructions on your screen to configure the program.
{{tip|We suggest to choose the '''Push-To-Talk''' mode in the '''Voice Activity Detection''' step; if you choose another mode, make sure to calibrate the volume levels correctly (follow the on-screen instructions carefully). This way, your voice will be transmitted only when you mean to, and there will be less background noise on the channel.}}

== Connecting ==

==Mumble Server==
<ol>
<li>Click on '''Server'''->'''Connect'''.</li>
<li>If this is the first time you connect to the FlightGear Mumble server, click on '''Add New...''' at the bottom of the window and input the following parameters, then click '''OK''':
{| class="wikitable"
|-
| '''Label'''
| <tt>FlightGear ATC</tt> (or another descriptive name of your choice)
|-
| '''Address'''
| <tt>mumble.allfex.org</tt>
|-
| '''Port'''
| <tt>64738</tt> (the default value)
|-
| '''Username'''
| A username (callsign) of your choice
|}</li>
<li>Select '''FlightGear ATC''' from the server list and click '''Connect'''.</li>
</ol>

====Other Flighgear Related Servers====
<ol>
<li>Click on '''Server'''->'''Connect'''.</li>
<li>Click on '''Add New...''' at the bottom of the window and input the following parameters, then click '''OK''':
{| class="wikitable"
|-
| '''Label'''
| <tt>Alternate FlightGear Server</tt> (or another descriptive name of your choice)
|-
| '''Address'''
| <tt>mumble-us.cleanvoice.com</tt>
|-
| '''Port'''
| <tt>39506</tt> (You must change it)
|-
| '''Username'''
| A username (callsign) of your choice
|}</li>
<li>Select '''Alternate FlightGear Server''' or whatever you chose from the server list and click '''Connect'''.</li>
</ol>

== Using Mumble ==
When you are connected, Mumble will show a hierarchical list of channels on the right side of the main window.
* To enter an existing channel, right click on it and choose '''Join Channel'''.
* To create a new channel (e.g. if you're acting as a controller), right click on the ''FlightGear'' channel and choose '''Add'''. Input a name and (optionally) a description, then click '''OK'''.
{{note|The new channel is temporary and will be deleted when the last person in it exits the channel.}}
* To mute yourself, click the '''Mute''' button in the main toolbar.

== OpenRadar flickering when using Mumble ==
If you're using Mumble and OpenRadar at the same time, you might notice that the OpenRadar screen flickers. A solution is disabling the Mumble overlay (in Mumble, click on '''Configure''' -> '''Settings''', open the '''Overlay''' section, deselect '''Enable Overlay''' and click '''OK''').

[[Category:Air Traffic Control]]
[[Category:Software]]

Howto:Install aircraft

2016-04-18T16:34:31Z

I4dnf: Removed wrong assumption, Folder name does not have to match $aircraft-set.xml name. Added proper explanation.

Modelling guidelines

2016-01-08T19:55:01Z

I4dnf: Undo revision 78754 by Legoboyvdlp (talk)

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

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

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

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

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

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

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

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

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

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

[[Category:Modeling]]

Howto:Aircraft reflection shader

2015-10-07T00:14:07Z

I4dnf: raised notice severity

{{stub}}
{{forum|47|Effects & Shaders}}

[[File:B29 shader.jpg|thumb|270px|Reflection Shader applied to the [[Boeing B-29 Superfortress|B-29]]. It shows a shiny, high-reflective blank metal.]]
Within [[Flightgear]] GIT and later, a reflection [[Shaders|shader]] effect is available. A lot of aircraft make already use of it, but much more will be expected soon.

== Reflection-Shaders - different kinds, different uses ==
We have currently different Reflection-Shaders, with different features and for different uses:

=== reflect.eff ===

{{warning|This shader is deprecated, and should not be used by new development. It is left in due to the vast amount of aircraft relying on it that need to be upgraded to model-combined-deferred/model-combined-transparent.
Use model-combined-deferred/model-combined-transparent instead
}}

It all began with a simple ReflectionShader, which simply adds a spherical map on the surface of the object. This shader works on not-UVmapped surfaces. Ideal for simple chrome parts.

'''Example Aircraft:''' B29

=== reflect-bump-spec.eff ===

{{warning|This shader is deprecated, and should not be used by new development. It is left in due to compatibility reasons.
Use model-combined-deferred/model-combined-transparent instead
}}

Later it had been enhanced by a [[Howto: Use the normal map effect in aircraft|Normalmap]]. This makes the surface appear "bumpy" depending on the used normalmap. The alpha channel of the normalmal also defines the specularity of the surface. This shader works only on UVmapped surfaces!

=== model-combined-deferred.eff and model-combined-transparent.eff ===
These shaders had been enhanced even more. You have now: reflections, normalmap and specularity map, dirt, lightmaps with 4 simulated lights per object in Default and [[Project Rembrandt|Rembrandt]]. In [[Atmospheric light scattering FAQ|ALS]] you will get in addition also a grain/ rain effect and the darkmap. This shader works only on UVmapped surfaces!
This shader inherits from [[Model-combined_effect|model-combined.eff]], an effect which should never be directly used, since it holds only the definition of the common parts of the two effects.
The model-combined-transparent.eff has the same features but has the necessary changes to correctly support transparent objects which represents transparent surfaces like glass.

'''Example Aircraft:''' EC 130 B4, EC 135 P2

=== What will be reflected on the surfaces? ===
All of these effects use Cubemaps and Cubecrosses from data/Aircraft/Generic/Effects which contains the image of the environment which will be visible as Reflection. Depending on which you choose, the appearance of the model will later change dramatically.

== How to implement the simple ReflectionShader: reflect.eff ==
=== the simple and quick Method ===

This is a simple and quick method for the simple ReflectionShader, but gives not the freedom to change the later appearance of the aircraft like setting the strength of the reflection or choosing a different cubemap.

Inside the <tt>Aircraft/AircraftName/Models</tt> folder, there should be a main xml file, which usually is <tt>AircraftName.xml</tt>. This file should be the one holding all information on visuals used in the aircraft. As such, we need to indicate which are to be reflectable!

Inside the <tt>AircraftName.xml</tt>, we need to put the following lines of code, shortly after or before other <animation> tag entries:

<nowiki></nowiki>
<effect>
<inherits-from>Aircraft/Generic/Effects/Fuselagereflect</inherits-from>
<object-name>Fuselage</object-name>
<object-name>RFdoor</object-name>
<object-name>LFdoor</object-name>
<object-name>LRdoor</object-name>
<object-name>RRdoor</object-name>
<object-name>Rmain.geardoor</object-name>
<object-name>Lmain.geardoor</object-name>
<object-name>Engines</object-name>
<object-name>Reversers</object-name>
<object-name>Tail</object-name>
<object-name>Rudder</object-name>
<object-name>RHstab</object-name>
<object-name>LHstab</object-name>
<object-name>LHelevator</object-name>
<object-name>RHelevator</object-name>
</effect>

Note that for each <object-name> tag, you need to indicate the aircraft's objects. If you are not the original aircraft author and do not know which parts to enter, or how they are named, use the other animations tags object names which indicate the pieces you require to be reflected (such as <object-name>fuselage</object-name> is an obvious one). Obviously do not enter things which you don't want to be reflected!

To see them in sim, ensure your View > Rendering options > Effects & shaders options are checked.
As an example the C160 Transall by helijah makes use of this simple method.

=== a bit more difficult Method- but more freedom! ===

The next method describes how to add the effect of a customized simple ReflectionShader, which allows more freedom.

You'll still need to use the code above in your file but this time, you'll use your own effect shader (below). The difference is you'll replace:
<inherits-from>Aircraft/Generic/Effects/Fuselagereflect</inherits-from>
with
<inherits-from>Aircraft/YourAircraftName/Effects/foo_reflect</inherits-from>
Now we'll create this foo_reflect file.

Create a Folder inside your Models-folder called "Effects".
Now you create a new .eff file named: foo_reflect.eff and save it to the "Effects" folder:

<nowiki></nowiki>
<PropertyList>
<name>Effects/foo_reflect</name>
<inherits-from>Effects/reflect</inherits-from>
<parameters>
<texture n="5">
<type>cubemap</type>


<images>
<positive-x>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_px.png</positive-x>
<negative-x>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_nx.png</negative-x>
<positive-y>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_py.png</positive-y>
<negative-y>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_ny.png</negative-y>
<positive-z>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_pz.png</positive-z>
<negative-z>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_nz.png</negative-z>
</images>
</texture>
<texture n="6">
<image>Aircraft/Generic/Effects/Rainbow.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
<texture n="7">
<image>Aircraft/Generic/Effects/FresnelLookUp.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
<texture n="8">
<image>Aircraft/foo/Models/Effects/greymap.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
<rendering-hint>transparent</rendering-hint>
<shade-model>smooth</shade-model>
<rainbowiness type="float">0.01</rainbowiness>
<fresneliness>0.0</fresneliness>
<noisiness>0.0</noisiness>
<refl_correction>0.0</refl_correction>
<ambient_correction>0.0</ambient_correction>
<reflect_map>1</reflect_map>
</parameters>
</PropertyList>

'''Explanation:'''

The tags at the bottom:

* <rainbowiness> = adds a nice Rainbow-effect to the reflection. Perfect for the modern Airliner-windows or modern coatings.
* <fresneliness> = adds some black stripes to the reflection.
* <noisiness> = adds noise to the reflection. Usefull for dirt etc...
* <ambient_correction> = correct the appearance of the reflection at shadowed parts.
* <reflect_map> = enables the use of a greymap. If enabled the greymap will controll the strength of the reflection. Black = zero reflection, White = full reflection. For modern aircraft coatings a grey of 75-90% is usefull, for chromish parts about 10-25%.
* <refl_correction> = another parameter for controlling the strength of the reflection. Reflect_map and refl_correction are working together.
* ''"texture= n5"'' is the path to the image wich will be later the reflection. You can choose between cubemaps with 6 single images or a cubecross. You can take the one included in ''data/Aircraft/Generic/Effects'' or you can use your own.
* ''"texture= n6"'' is the path to the rainbow-texture.
* ''"texture= n7"'' path to the fresnel-texture.
* ''"texture= n8"''is the path to the greymap.

[[Category:Aircraft enhancement|Aircraft Reflection Shader]]
[[Category:Howto|Aircraft Reflection Shader]]
[[Category:Shader development]]

Howto:Aircraft reflection shader

2015-10-06T23:03:25Z

I4dnf: add warning against using reflect.eff and reflect-bump-spec in new work. clarify model-combined-* usage

{{stub}}
{{forum|47|Effects & Shaders}}

[[File:B29 shader.jpg|thumb|270px|Reflection Shader applied to the [[Boeing B-29 Superfortress|B-29]]. It shows a shiny, high-reflective blank metal.]]
Within [[Flightgear]] GIT and later, a reflection [[Shaders|shader]] effect is available. A lot of aircraft make already use of it, but much more will be expected soon.

== Reflection-Shaders - different kinds, different uses ==
We have currently different Reflection-Shaders, with different features and for different uses:

=== reflect.eff ===

{{note|This shader is deprecated, and should not be used by new development. It is left in due to the vast amount of aircraft relying on it that need to be upgraded to model-combined-deferred/model-combined-transparent}}

It all began with a simple ReflectionShader, which simply adds a spherical map on the surface of the object. This shader works on not-UVmapped surfaces. Ideal for simple chrome parts.

'''Example Aircraft:''' B29

=== reflect-bump-spec.eff ===

{{note|This shader is deprecated, and should not be used by new development. It is left in due to compatibility reasons}}

Later it had been enhanced by a [[Howto: Use the normal map effect in aircraft|Normalmap]]. This makes the surface appear "bumpy" depending on the used normalmap. The alpha channel of the normalmal also defines the specularity of the surface. This shader works only on UVmapped surfaces!

=== model-combined-deferred.eff and model-combined-transparent.eff ===
These shaders had been enhanced even more. You have now: reflections, normalmap and specularity map, dirt, lightmaps with 4 simulated lights per object in Default and [[Project Rembrandt|Rembrandt]]. In [[Atmospheric light scattering FAQ|ALS]] you will get in addition also a grain/ rain effect and the darkmap. This shader works only on UVmapped surfaces!
This shader inherits from [[Model-combined_effect|model-combined.eff]], an effect which should never be directly used, since it holds only the definition of the common parts of the two effects.
The model-combined-transparent.eff has the same features but has the necessary changes to correctly support transparent objects which represents transparent surfaces like glass.

'''Example Aircraft:''' EC 130 B4, EC 135 P2

=== What will be reflected on the surfaces? ===
All of these effects use Cubemaps and Cubecrosses from data/Aircraft/Generic/Effects which contains the image of the environment which will be visible as Reflection. Depending on which you choose, the appearance of the model will later change dramatically.

== How to implement the simple ReflectionShader: reflect.eff ==
=== the simple and quick Method ===

This is a simple and quick method for the simple ReflectionShader, but gives not the freedom to change the later appearance of the aircraft like setting the strength of the reflection or choosing a different cubemap.

Inside the <tt>Aircraft/AircraftName/Models</tt> folder, there should be a main xml file, which usually is <tt>AircraftName.xml</tt>. This file should be the one holding all information on visuals used in the aircraft. As such, we need to indicate which are to be reflectable!

Inside the <tt>AircraftName.xml</tt>, we need to put the following lines of code, shortly after or before other <animation> tag entries:

<nowiki></nowiki>
<effect>
<inherits-from>Aircraft/Generic/Effects/Fuselagereflect</inherits-from>
<object-name>Fuselage</object-name>
<object-name>RFdoor</object-name>
<object-name>LFdoor</object-name>
<object-name>LRdoor</object-name>
<object-name>RRdoor</object-name>
<object-name>Rmain.geardoor</object-name>
<object-name>Lmain.geardoor</object-name>
<object-name>Engines</object-name>
<object-name>Reversers</object-name>
<object-name>Tail</object-name>
<object-name>Rudder</object-name>
<object-name>RHstab</object-name>
<object-name>LHstab</object-name>
<object-name>LHelevator</object-name>
<object-name>RHelevator</object-name>
</effect>

Note that for each <object-name> tag, you need to indicate the aircraft's objects. If you are not the original aircraft author and do not know which parts to enter, or how they are named, use the other animations tags object names which indicate the pieces you require to be reflected (such as <object-name>fuselage</object-name> is an obvious one). Obviously do not enter things which you don't want to be reflected!

To see them in sim, ensure your View > Rendering options > Effects & shaders options are checked.
As an example the C160 Transall by helijah makes use of this simple method.

=== a bit more difficult Method- but more freedom! ===

The next method describes how to add the effect of a customized simple ReflectionShader, which allows more freedom.

You'll still need to use the code above in your file but this time, you'll use your own effect shader (below). The difference is you'll replace:
<inherits-from>Aircraft/Generic/Effects/Fuselagereflect</inherits-from>
with
<inherits-from>Aircraft/YourAircraftName/Effects/foo_reflect</inherits-from>
Now we'll create this foo_reflect file.

Create a Folder inside your Models-folder called "Effects".
Now you create a new .eff file named: foo_reflect.eff and save it to the "Effects" folder:

<nowiki></nowiki>
<PropertyList>
<name>Effects/foo_reflect</name>
<inherits-from>Effects/reflect</inherits-from>
<parameters>
<texture n="5">
<type>cubemap</type>


<images>
<positive-x>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_px.png</positive-x>
<negative-x>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_nx.png</negative-x>
<positive-y>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_py.png</positive-y>
<negative-y>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_ny.png</negative-y>
<positive-z>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_pz.png</positive-z>
<negative-z>Aircraft/Generic/Effects/CubeMaps/real.blue-sky/fair-sky_nz.png</negative-z>
</images>
</texture>
<texture n="6">
<image>Aircraft/Generic/Effects/Rainbow.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
<texture n="7">
<image>Aircraft/Generic/Effects/FresnelLookUp.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
<texture n="8">
<image>Aircraft/foo/Models/Effects/greymap.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
<rendering-hint>transparent</rendering-hint>
<shade-model>smooth</shade-model>
<rainbowiness type="float">0.01</rainbowiness>
<fresneliness>0.0</fresneliness>
<noisiness>0.0</noisiness>
<refl_correction>0.0</refl_correction>
<ambient_correction>0.0</ambient_correction>
<reflect_map>1</reflect_map>
</parameters>
</PropertyList>

'''Explanation:'''

The tags at the bottom:

* <rainbowiness> = adds a nice Rainbow-effect to the reflection. Perfect for the modern Airliner-windows or modern coatings.
* <fresneliness> = adds some black stripes to the reflection.
* <noisiness> = adds noise to the reflection. Usefull for dirt etc...
* <ambient_correction> = correct the appearance of the reflection at shadowed parts.
* <reflect_map> = enables the use of a greymap. If enabled the greymap will controll the strength of the reflection. Black = zero reflection, White = full reflection. For modern aircraft coatings a grey of 75-90% is usefull, for chromish parts about 10-25%.
* <refl_correction> = another parameter for controlling the strength of the reflection. Reflect_map and refl_correction are working together.
* ''"texture= n5"'' is the path to the image wich will be later the reflection. You can choose between cubemaps with 6 single images or a cubecross. You can take the one included in ''data/Aircraft/Generic/Effects'' or you can use your own.
* ''"texture= n6"'' is the path to the rainbow-texture.
* ''"texture= n7"'' path to the fresnel-texture.
* ''"texture= n8"''is the path to the greymap.

[[Category:Aircraft enhancement|Aircraft Reflection Shader]]
[[Category:Howto|Aircraft Reflection Shader]]
[[Category:Shader development]]

Talk:FGMEMBERS

2015-09-22T20:06:38Z

I4dnf:

== Keep this page (09/2015)? ==
In light of the recent developments, maybe this page should be temporarily removed then replaced by the statement currently being formulated on the mailing list?

[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 12:36, 17 September 2015 (EDT)

: No. It is still alive. Add the "statement" to a new page, but LEAVE THIS ONE ALONE (you could add it as a section?)
: [[User:Legoboyvdlp|Legoboyvdlp]] ([[User talk:Legoboyvdlp|talk]]) 16:13, 17 September 2015 (EDT)

:: I blanked the page and protected it until further notice[http://sourceforge.net/p/flightgear/mailman/message/34460509], if anybody still needs any of the original content, please use the article's history to retrieve an older version. The article may be restored/replaced once a consensus is reached. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 04:46, 21 September 2015 (EDT)

::: you blanked the page ? Thats like burning books. Blocking users. Deleting pages. Deleting Forum posts. This all makes me very sad/sick. [[User:Laserman|Laserman]] ([[User talk:Laserman|talk]]) 12:51, 21 September 2015 (EDT)

:::: I beg to differ, it's all still there, not just in the history, but on the actual page (just view the source to see for yourself). Anyway, it seems that a number of key contributors have come to the conclusion that fgmembers proponents are better off setting up, and using, their own infrastructure given how this has evolved over time. So I haven't deleted anything. Originally, I suggested to set up a dedicated wiki article and to move fgmembers related discussions to a dedicated sub-forum, and preferably, document the whole effort in a neutral/factual way on the wiki, instead of spamming the forum/devel list. Obviously, this wasn't particularly fruitful - but originally I was one of the few proponents to give this a try, and even the creator of this article, long before anybody else. And according to the history of the article it took those fgmembers proponents 4+ months to actually contribute to this article. As can be read on the forum, I don't necessarily agree with what's going on on the forum, but to be absolutely fair, I am neither paying for the forum infrastructure, nor the wiki - so it is frankly not my call, and if/when some consensus is reached, we are well-advised to accept/enforce that for the sake of the project, whatever that means.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 13:20, 21 September 2015 (EDT)

: Looking at the list of private hangars at [[FlightGear_hangars#Aircraft_hangars]], no other hangar has its own dedicated article on the FG wiki. Independent of the action taken, I highly recommend that FGMEMBERS set up a Mediawiki-based wiki and copy all of this content for the benefit of FGMEMBERS users. [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:21, 22 September 2015 (EDT)

:: Agreed, just to be on the safe side, I copied the latest version, so that everything is now also preserved at: http://codepad.org/Vf1SfSzo Note that are there tons of free mediawiki-based hosting services [https://www.mediawiki.org/wiki/Hosting_services]. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 10:56, 22 September 2015 (EDT)

===Latest edit by Hooray (23 sept 2015) ===
I don't think this hide-and-seek game helps. Nor Flightgear reacting to any of their actions or inactions. Let them speak whatever on their forum, there's far worse stuff in there than the FUD that caused this reversal.

[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 16:05, 22 September 2015 (EDT)

Talk:IAR 80

2015-09-17T17:06:39Z

I4dnf:

I think the page should not be deleted, and also the plane should be included again. The deletion mostly hurts the romanian plane enthusiasts who had a nice exponent of their history available and now it's gone. [[User:Sa7k|Sa7k]] ([[User talk:Sa7k|talk]]) 19:41, 29 August 2013 (UTC)

:: Agreed, an aircraft being discontinued is no reason to remove it, or to remove its wiki article - in fact, it's probably pretty safe to say that over 95% of our aircraft are not actively maintained (or "discontinued"), and it's also pretty safe to say that 99% of the aircraft in FlightGear are not as well modeled/developed as the IAR80 - again, I don't get the point of retracting your contributions from FlightGear, regardless of community disagreements over time - we're all here to make it better in some way or form. There's an increasing number of people who think that they can simply retract their contributions once they disagree with the project, but that's not how open source works - sorry to say it so bluntly, but if you were a core developer, we also wouldn't be removing your source code from the repositories. You guys are just doing that because it's a self-contained piece of work, and because you can simply remove the download and ask any related resources to be deleted. It's really unfortunate how the most productive and the most talented contributors seem to think that they can simply retract all their contributions once they no longer agree with the way the project is working/heading. That's a luxury that we simply don't have - by behaving like this you are putting more harm to the project than the people you are disagreeing with, because of whom you are engaging in this public debate.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 01:35, 30 August 2013 (UTC)

::Discussion closed with the outcome "Keep". [[User:Fg|Fg]] ([[User talk:Fg|talk]]) 01:05, 5 December 2013 (UTC)

Could the FGMEMBERS reference be removed or shifted towards the bottom? This is a good disclaimer, but unfortunately it also acts as strong advertising! [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:51, 17 September 2015 (EDT)

:: Done, also on the l10 page that had the same warning
::[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 13:06, 17 September 2015 (EDT)

Lockheed Model 10 Electra

2015-09-17T17:05:16Z

I4dnf: reduce advertising potential of fgmembers warning, also deactivate page link until that is sorted.

{{non-GPL}}

{{Infobox aircraft
|image = L10-glamour.jpg
|alt= Waiting For Amelia
|image2 = Electra 2.jpg
|alt2 = Lockheed Model 10 Electra in flight
|name = Lockheed Model 10 Electra
|type = Light airliner
|fdm = [[YASim]]
|status-fdm = 2
|status-systems = 1
|status-cockpit = 1
|status-model =3
|fgname = Lockheed-L10-Electra
|authors = Emilian Huminiuc
|development = https://gitlab.com/emilianh/Lockheed-L10-Electra/
|download = https://gitlab.com/emilianh/Lockheed-L10-Electra/repository/archive.zip
}}

The '''Lockheed Model 10 Electra''' was a twin-engine, all-metal monoplane airliner developed by the Lockheed Aircraft Corporation in the 1930s to compete with the Boeing 247 and Douglas DC-2. The type gained considerable fame as one was flown by Amelia Earhart on her ill-fated around-the-world expedition in 1937

== L10A Gallery ==
{|
| [[File:L10-beauty-shot.jpg|256px|Lockheed L10 Electra sitting on the runway]]
| [[File:L10-cockpit-WIP.jpg|256px|WiP Shot of the L10 Cockpit]]
|-
| [[File:L10-cabin-back.jpg|256px|WiP Lockheed L10 Electra Cabin from the back towards the pointy end]]
| [[File:L10-cabin-front.jpg|256px|WiP Lockheed L10 Electra Cabin from the front towards the tail end]]
|-
| [[File:Electra 1.jpg|256px|Old WiP Lockheed L10 Electra in flight]]
|}

== Amelia Earhart Special Model Gallery ==
{|
| [[File:L10e-AE-rwy1.jpg|256px|L10e Electra "Amelia Earhart Special" on the runway]]
| [[File:L10e-AE-rwy2.jpg|256px|L10e Electra "Amelia Earhart Special" on the runway]]
|-
| [[File:L10e-AE-inflight1.jpg|256px|L10e Electra "Amelia Earhart Special" in flight]]
| [[File:L10e-AE-inflight2.jpg|256px|L10e Electra "Amelia Earhart Special" in flight]]
|-
| [[File:L10e-AE-inflight-close.jpg|256px|L10e Electra "Amelia Earhart Special" in flight]]
|}

{{note|The package available in the [[FGMembers|FGMEMEBERS]] repository is a crippled variant, based on a very old version of this project, and unrelated to this project.}}
== External links ==
* {{Wikipedia|Lockheed Model 10 Electra|Wikipedia|noicon=1}}

{{Lockheed}}

[[Category:Airliners]]
[[Category:Propeller aircraft]]
[[Category:Twin-engined aircraft]]

IAR 80

2015-09-17T17:03:38Z

I4dnf: reduce advertising potential of fgmembers warning, also deactivate page link until that is sorted.

{{non-GPL}}

{{Infobox aircraft
|name = IAR 80
|image = Iar80-flight.jpg
|alt = The IAR 80 in its the default livery.
|type = Fighter aircraft
|fdm = [[YASim]], [[JSBSim]] (beta)
|authors =
* Emilian Huminiuc (3D model, textures, YASim [[FDM]])
* Ron Jensen (JSBSim FDM)
|status-fdm = 5
|status-systems = 4
|status-cockpit = 5
|status-model = 5
|fgname = IAR80-YASim
|download = https://gitlab.com/emilianh/IAR80/repository/archive.zip?ref=latest
}}

The '''IAR 80''' was a Romanian World War II [[:Category:Low wing aircraft|low-wing]], monoplane, all-metal monocoque [[:Category:Fighter aircraft|fighter]] and [[:Category:Attack aircraft|ground-attack]] [[aircraft]]. When it first flew, in 1939, it was comparable to contemporary designs such as the German [[Messerschmitt Bf 109|Messerschmitt Bf 109B]], the British [[Hawker Hurricane|Hawker Hurricane Mk.I]], and the American Curtiss P-40B/Tomahawk Mk.I and superior to the Dutch Fokker D.XXI and Polish PZL P.24. Production problems and lack of available armament delayed entry of the IAR 80 into service until 1941. It remained in front-line use until 1944.

== Features ==
{{note|The package available in the FGMEMEBERS repository is a crippled variant, based on a very old version of this project, and unrelated to this project.}}
=== Liveries ===
The IAR 80 has three liveries:
* Royal Romanian Air Force (''default'')
* Bare metal
* Romanian Air Club (''fictional'')

Changing livery also changes the reflectiveness of the material — the default one is rather matte, while the other two are more reflective. Livery textures are DDS files, which improves loading time when switching between liveries.

=== Shaders effects ===
The IAR 80 uses the [[model-combined effect]] shader to show a high level of detail. It uses the dirt/grit feature of this shader to add oil staining to the fuselage as engine wear increases. The aircraft also supports the [[Howto:Use the normal map effect in aircraft|normal map]] feature of the same shader, and uses textures in the DDS format to improve the detail and appearance.

=== Particle effects ===
* Engine smoke, changing colour and density with the thrust, mixture, and engine wear.
* Particle [[Howto: Add contrails|contrails]]
* Wingtip vortices when near stall {{Abbr|AoA|Angle of Attack}}
* Spiral splipstream when on the ground or at low altitude

=== View effects ===
By use of [[Nasal]] scripting, the internal view shakes when rolling on the runway and simulates the buffeting experienced when approaching stall AoA.

=== Controls Filter ===
Via a Nasal script, the control input is filtered, resulting in decreased input to the control surfaces due to the airflow over them (this was necessary as the elevator has dynamic compensator tabs).

=== Guns ===
The guns are fully simulated using [[submodels]], with particle smoke, sounds and recoil.

=== Advanced engine startup and management ===
The [[#Startup|startup]] procedure is rather realistic, from a "dark and cold" state. While flying you have to [[#Engine management precautions|take care]] of the engine (see the [[#Aircraft help|help]] section below).

=== Engine sputter ===
* The engine sputters when overheated/worn due to incorrect management or when low on fuel.

== Aircraft help ==
=== Keyboard control ===
{|
| {{Key press|Ctrl|d}} || Toggle canopy open/closed.
|-
| {{Key press|r}} || Open the cowling flaps.
|-
| {{Key press|Shift|r}} || Close the cowling flaps.
|-
| {{Key press|e}} || Fire guns
|}

{{Note|Throttle direction is reversed.}}

=== Cockpit reference ===
You'll find a quick-reference PDF file in the <tt>''[[$FG_ROOT]]/Aircraft/IAR80/doc''</tt> folder.

When pressing {{Key press|Ctrl|c}} to show hotspots, you will also get labels on all instruments, switches and levers that are active.

=== Clickable levers and sliders ===
All the levers and sliders in the cockpit are clickable. You use the {{Abbr|LMB|left mouse button}} to increase value/position and the {{Abbr|MMB|middle mouse button}} to decrease the value/position. Alternately, you can use the scroll wheel to make finer adjustments.

=== Startup ===
# Turn the master switch (the big hexagonal button over the pilot's right shoulder) on.
# Set the mixture to rich (mixture lever to forward position).
# Set some throttle.
# Prime 6–9 times.
# Set propeller pitch to middle position.
# Set magnetos to both.
# Open the cowl flaps ({{Key press|r}} key).
# Engage starter button and hope it will start.
# Optional: if want you can turn the position lights on.

If the engine doesn't start and just sputters, it usually means you have not primed enough. To check if that is the case, keep an eye on the fuel-pressure gauge (left panel, right needle on gauge with two needles) — it should increase when you engage the starter. Also, when priming, make sure the lever reaches the forward end of travel, otherwise that push doesn't register.

=== Warm-up ===
# Increase the propeller pitch for minimum revs (towards the rear).
# Increase the throttle until boost pressure reaches about 400 (engine rpm will stabilize at about 1,250–1,300 rpm).
# Wait until the oil pressure gets over 1 and oil temperature reaches 60.

=== Taxi ===
# Set propeller pitch to middle position.
# Adjust the seat position to a higher setting, for better visibility.
# Use the differential brakes to steer the plane.

=== Takeoff ===
# Close canopy if you have not done so yet.
# ''On short runways:'' Set flaps to position 2 (30 degrees).
# Set propeller pitch to maximum (fully forward).
# Set throttle to have about 950 boost pressure.
# Release brakes and be prepared to correct the aircraft's tendency to yaw to the right by either braking (at low speeds) or by using opposite rudder.
# Pull forward a little on the stick until the tail lifts off the ground.
# Maintain the stick position (just enough to keep the plane level) until about 150–160 km/h when the plane should take off.
# Retract the landing gear.
# Retract the flaps at about 200 km/h.

=== Cruise ===
# Set prop pitch so that the needles of the indicator form a V around the 11:05 position.
# Set mixture lever at about the apex of the bend in the lever guard. (about 0.6–0.7 mixture).
# Cowl flaps at position 4/8.

=== Landing ===
# Reduce throttle.
# Open the cowl flaps.
# At about 300 km/h start extending full flaps.
# At about 250 km/h extend gear.
# Touchdown at about 150 km/h.

=== Emergency ===
If you lose the engine during flight the hydraulic system loses pressurization making it inoperable. Although flaps and brakes become inoperable there is an emergency landing gear deployment procedure that you can use:
# Set the gear safety knob to the safe position.
# Check the air pressure gauge.
# There needs to be enough air pressure for gear deployment (above 70).
# If air pressure is too low, pump using the manual pump on the right of the cockpit.
# Check airspeed below 250 km/h.
# Release the gear emergency lever on your left side.
# Check gear down and locked as indicated by the gear indicator.

== Notes ==
=== Limits ===
* '''VFE (maximum flap extended speed):''' 300 km/h. If exceeded, the flaps will jam; can be reset by the failure manager.
* '''VLE (maximum landing gear extended speed):''' 250 km/h. If exceeded, the gear will jam; can be reset by the failure manager.
* '''VNE (never exceed speed):''' 750 km/h [[IAS]]. If exceeded, the ailerons/elevators/rudder will tear off, depending on their position; can be reset by the failure manager.
* '''Maximum positive g-force:''' 7 g. If exceeded, the wing(s) will bend, resulting in bad aerodynamic behavior; can be reset by the IAR 80 menu.
* '''Maximum negative g-force:''' -4 g. If exceeded, the same as above will apply.

=== Engine management precautions ===
The engine will exhibit increased wear signs and will eventually stop if you do not follow these guidelines:
* Do not exceed 950 boost (except occasionally on take-off/in emergency).
* Keep below 1,500 rpm until engine warm-up complete.
* Keep below 2,800 rpm in normal flight.
* Keep the oil temperature below 120° C.

=== Gunnery controls ===
By default, the weapons are not armed. If you desire, you might set their corresponding switches to your pleasure.

== Gallery ==
<gallery mode="packed">
Iar80-cockpit-dusk.jpg|The IAR 80's cockpit as dusk
Iar80-cockpit-pano.jpg|A [[Howto: Make full spherical panorama|panorama]] of the IAR 80's cockpit
Iar80-dusk.jpg|The IAR 80 at dusk
Iar80-metal.jpg|The IAR 80 in bare metal livery
Iar80-ocean.jpg|IAR 80 over the ocean
IAR80-wing-detail.jpg|Detail of the IAR 80's wing
Iar80-angry.jpg|IAR 80 in the air
IAR80-onrwy.jpg|IAR 80 on the ground
</gallery>

{{#ev:youtube|gtYMvNQHuEA|||Video of a flight in the IAR 80 ({{itip|Turn up to 720p HD}})|frame}}

== External links ==
* {{Wikipedia|IAR 80|Wikipedia|noicon=1}}

[[Category:Fighter aircraft]]
[[Category:Low wing aircraft]]
[[Category:Propeller aircraft]]
[[Category:Single-engine aircraft]]

Talk:FGMEMBERS

2015-09-17T16:36:22Z

I4dnf: Suggest replacement of content with the statement by the core team

In light of the recent developments, maybe this page should be temporarily removed then replaced by the statement currently being formulated on the mailing list?

[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 12:36, 17 September 2015 (EDT)

Spangdahlem Air Base

2015-09-03T16:13:06Z

I4dnf: Let's keep (geo)political issues out of this wiki, although I also question the over detailed history itself, and its benefits in a FlightGear context

{{Infobox Airport
| name = Spangdahlem Air Base
| image =
| alt =
| iata = SPM
| icao = ETAD
| type = Military
| owner = U.S. Air Force
| city = Spangdahlem, Trier, Germany
| website = http://www.spangdahlem.af.mil/
| runway = 05/23
| length = 10,007 ft (3,050 m)
| material = Asphalt
| scenerytile = e006n49
| terrasync = No
| download = https://github.com/IHAM-COL/ETAD-fgCustomScenery
}}

'''Spangdahlem Air Base''' is a U.S. Air Force base constructed between 1951 and 1953 and located near the small German town of {{wikipedia|Spangdahlem}}, approximately 30 km NNE of the city of Trier, Rhineland-Palatinate. It is home of the [https://en.wikipedia.org/wiki/52nd_Fighter_Wing 52nd Fighter Wing], which maintains, deploys and employs Lockheed Martin Block 50 [[F-16CJ]]. In total, 4,800 military personnel, 840 German nationals and 200 US contractors are working at the base.

== History ==
With the creation of NATO in response to Cold War tensions in Europe, USAFE wanted its vulnerable fighter units in West Germany moved west of the Rhein River to provide greater air defense warning time. France agreed to air base sites within its zone of occupation in the Rheinland-Palatinate. Spangdahlem base was constructed between 1951 and 1953 at a cost of roughly $27,000,000 using French and German contractors, working under the supervision of a French government agency. The initial USAF military presence began on 1 September 1952 with the arrival of the 7352d Air Base Squadron on 1 September 1952 from Fürstenfeldbruck Air Base near Munich. The mission of the 7532d ABS was to prepare the facility for an operational wing.

Many units were assigned along the years to Spangdahlem, such as the 10th Tactical Reconnaissance Wing, the 49th Tactical Fighter Wing and the 7149th/36th Tactical Fighter Wing with their aircrafts and roles but on the 31 December 1971 the 52d Tactical Fighter Wing was transferred without personnel or equipment from Suffolk County AFB, New York to Spangdahlem. The unit had been a sort of personal National Guard wing for top WW2 P-47 ace Frank Grabeski. Inactivated then reactivated as a new USAFE wing, the new Wing Commander was to be the first black USAFE Wing CO Col Thomas E Clifford who had been 35th TFW DCO at Da Nang AB Viet Nam. Upon activation in Germany, the 52 TFW assumed control of the two squadrons the 36 TFW had located at Spangdahlem: 23d Tactical Fighter (F-4D, Tail Code: SP, blue tail stripe) and 39th Tactical Electronic Warfare (EB-66E/C, Tail Code: SP, yellow tail stripe).

During warm seasons in 1970 and 1971 operations shifted back to Bitburg while the runway was resurfaced at Spang. During this period the hardened NATO "TAB-V" shelters were constructed at both bases while operations around them continued. EB-66s were too large and remained parked around the ramp at the large hangar. End of runway alert aircraft F4s and EB-66's were under shelter for weather protection only. "V" or Victor Alert denoted nuclear forces from the British bombers Victor and Vulcan beginning with that letter. "E" Alert was for ECM.
The 52 TFW gained its third fighter squadron with the activation of the 480th Tactical Fighter Squadron on 15 November 1976. On 1 January 1977, the 52 TFW had the following operational squadrons: 23d Tactical Fighter Squadron (F-4D w/ blue tail stripe, tail code: SP) "Fighting Hawks", 81st Tactical Fighter Squadron (EF-4C w/ yellow tail stripe, tail code: SP) "Wild Weasels" and 480th Tactical Fighter Squadron (F-4D w/ red tail stripe, tail code: SP) "Warhawks".

A complete reorganization of wing aircraft and aircrews occurred in November 1983, transforming the 52d TFW into the first and only all-defense suppression wing outside of the United States. Under this configuration, each of the wing’s three fighter squadrons flew E and G model F-4s paired together into Wild Weasel "hunter/killer" teams capable of locating and destroying enemy radar-guided, surface-to-air threats in all weather.

In April 1987, the 52d began changing with the times and replaced its aging Phantoms with Block 30/32 F-16C/D Fighting Falcons for the 23d and 480th TFSs. These were later replaced with Block 50 versions beginning in 1993. The last USAF operational model F-4E Phantom II aircraft departed Spangdahlem AB in December 1987.

On 1 October 1991, the 52 TFW was redesignated the 52d Fighter Wing as part of a sweeping, Air Force-wide restructure.
The 510th Fighter Squadron was moved to Spangdahlem with the closure of RAF Bentwaters UK on 4 January 1993 as the lone A-10 Thunderbolt II squadron in USAFE. Also in early 1993, the 81st FS was reorganized to fly a mixture of F-4Gs and Block 30 F-16C/Ds.
The F-4Gs were withdrawn and sent to AMARC in February 1994. With the withdrawal of the Phantoms, the 510th Fighter Squadron was replaced by the 81st FS at Spangdahlem AB and was transferred to Ramstein Air Base to absorb the F-16 assets of the 512th FS there.

In February 1994, the 53d Fighter Squadron relocated to Spangdahlem from Bitburg after its closure with F-15C/Ds. The 480 FS was also inactivated during October 1994, being replaced by the 22d Fighter Squadron from Bitburg. The 606th Air Control Squadron was also assigned to the 52d Fighter Wing but remained at Bitburg until September 1995 before moving to Spangdahlem.
After the restructuring and the closure of Bitburg and transfer of 36 FW squadrons to Spangdahlem, the operational squadrons of the 52d Fighter Wing were: 23d Fighter (F-16CJ/D Blue tail stripe, Code: SP), 22d Fighter (F-16CJ/D Red tail stripe, Code: SP), 53d Fighter (F-15C/D Yellow and black tail stripe (Tiger stripes), Code: SP) and 81st Fighter (A/OA-10A Yellow tail stripe, Code: SP).

During the second quarter of Fiscal Year '99, the 52nd witnessed the inactivation of the 53rd Fighter Squadron. The 53d had called Spangdahlem Air Base home since February 1994 when the squadron moved from Bitburg AB. As the squadron prepared for its inactivation in March 1999, all of the F-15s were transferred to the 1st Fighter Wing at Langley AFB, Virginia (USA), or to the 48th Fighter Wing at RAF Lakenheath, United Kingdom.

In April 2010, the wing's strength was reduced by one third. 20 F-16Cs from the 22nd Fighter Squadron were flown to the 148th Fighter Wing, Minnesota Air National Guard and one F-16 was transferred to Edwards Air Force Base, California. As a result of the drawdown of F-16s, the 22d and 23d Fighter Squadrons were inactivated on 13 August 2010 and formed a single "new" squadron, the 480th Fighter Squadron. In February 2012, it was announced that the 81st Fighter Squadron would be inactivated in 2013, leaving the 52d Fighter Wing with just one squadron.

On 8 January 2015 the U.S. Secretary of Defense announced the results of the European Infrastructure Consolidation (EIC) review, which will realign several missions in USAFE and AFAFRICA. Under the EIC, the DoD will make changes to the mission at Spangdahlem Air Base, including the relocation of the 606th Air Control Squadron to [[Aviano Air Base]], Italy, in order to free up requisite space and infrastructure for future inclusion of the 352d Special Operations Group from RAF Mildenhall, United Kingdom which is scheduled to be closed in 2022.

In February 2015, the 354th Fighter Squadron was deployed from Davis-Monthan AFB to Spang in support of Operation Atlantic Resolve with twelve A-10Cs and approximately 300 airmen. The unit will train alongside NATO allies and deploy to locations in Eastern European NATO nations to further enhance interoperability. The A-10s were the first of several theater security package deployments to Europe, U.S. Air Force officials said, adding that rotations generally will last six months, depending on mission and United States European Command requirements.

On 30 July 2015, it was announced that the 480th Fighter Squadron would deploy to Incirlik Air Base in support of Operation Inherent Resolve.
Recently, 4 [[F-22]]A Raptor from Tyndall AFB were deployed to Spangdahlem for the first time in Europe, in support of Operation Atlantic Resolve.

== Technical characteristics ==
=== Runway ===
The airport has only one runway (048°/228°), 3,050 m long and 45 m wide. Both runways 05 and 23 will have got two BAK-12 [http://en.wikipedia.org/wiki/Arresting_gear#Land-based_systems aircraft arresting systems] for emergency landings and training in the beta version.

=== Communications ===
==== FGCom frequencies ====
(''The following table takes into account some frequencies available only in the current development version.'')
{|
|+ '''COMM'''
|-
! style="background:#efefef; text-align: center" | ATIS
| 143.425
|-
! style="background:#efefef; text-align: center" | TWR
| 122.200
|-
! style="background:#efefef; text-align: center" | GND
| 138.8
|-
! style="background:#efefef; text-align: center" | CLNC DEL
| 308.850
|-
! style="background:#efefef; text-align: center" | LANGEN RADAR
| 125.600
|-
! style="background:#efefef; text-align: center" | AMC AIRLIFT
| 131.975
|}

==== Navaids ====

{|
|+ '''TACAN'''
|-
! style="background:#efefef; text-align: center" | SPA
| 032X,
| 00 NM
|}

== Custom scenery ==
[[User:J Maverick 16|J Maverick 16]] and IAHM-COL are currently redesigning the airport so that the [[scenery]] is as faithful as possible to the real air base. A first preview of the beta can be found on [https://github.com/IHAM-COL/ETAD-fgCustomScenery GitHub] (work in progress).

=== Progress ===
''The following table takes into account improvements available only in the current development version on GitHub.''

{| class="wikitable"
! scope="col"| Task
! scope="col"| Progress
! scope="col"| Remarks
|-
| Runway, beacon, PAPI, Tower
| {{done}}
|
|-
| Taxiway layouts
| {{done}}
|
|-
| Taxi signs
| {{progressbar|40}}
| For now there are only the most important ones, more have to be added.
|-
| Aprons
| {{done}}
|
|-
| Buildings
| {{progressbar|20}}
|
|-
| Parking positions and ground net
| {{progressbar|70}}
| All the ground net is present, have to add the parking positions.
|-
| Comprehensive air base scenery
| {{progressbar|40}}
|
|}

== ATC services (USAF_SP) ==
[[ATC]] service is provided with [[OpenRadar]] regularly on Fridays, using also [[Mumble]] and [[FGCom]] - check [http://flightgear-atc.alwaysdata.net/ Lenny's website] for the exact times and dates, but usually on Friday evenings, . For further informations about ETAD, you can download the chart on the right, use [http://skyvector.com/airport/ETAD/Spangdahlem-Airport SkyVector] and [http://www.gcmap.com/airport/SPM GCMAP].
To avoid pilot/ATC misunderstandings see the [[ATC_best_practices#Minimum_list_of_best_practices|minimum list of best practices]], and don't simulate an emergency or found an excuse to land/take-off from Spangdahlem only because it is controlled in that moment, especially for airliners (e.g. terrorists on board, engine faliture, passenger with cardiac arrest, President on board, very top secret mission, ...).

== USAFE Livery Pack for F-16C and F-15C ==
[[User:J Maverick 16|J Maverick 16]] and Gary Brown have created a some liveries for FGUK's F-16C and F-15C of the past and present U.S. Air Forces Europe aircrafts, containing Spangdahlem, Ramstein and RAF Lakenheath liveries. It can be found [http://www.fguk.eu/index.php/hangar/viewdownload/12-liveries/508-usafe-liveries-for-f-15-and-f-16 here].

== External Links ==
*[https://www.facebook.com/SpangdahlemAirBase Spangdahlem AB on Facebook]
*[http://kaiserlautern.afneurope.net/ AFN Kaiserlautern]
*[http://www.52fss.com/ 52nd Force Support Squadron]
*[http://www.spangdahlem.af.mil/units/ Spangdahlem AB units]
*[http://www.usafe.af.mil/ U.S. Air Forces in Europe]
*[http://www.spangdahlem.af.mil/units/726thairmobilitysquadronpassengerterminal.asp Spangdahlem Passenger Terminal]

[[Category:Airports in Germany]]

Lockheed Model 10 Electra

2015-07-12T23:29:19Z

I4dnf: Added L10e "Amelia Earhart Special" model gallery

{{non-GPL}}

{{note|The package available in the [[FGMembers|FGMEMEBERS]] repository is based on a very old version of this project, and unrelated to this project.}}

{{Infobox aircraft
|image = L10-glamour.jpg
|alt= Waiting For Amelia
|image2 = Electra 2.jpg
|alt2 = Lockheed Model 10 Electra in flight
|name = Lockheed Model 10 Electra
|type = Light airliner
|fdm = [[YASim]]
|status-fdm = 2
|status-systems = 1
|status-cockpit = 1
|status-model =3
|fgname = Lockheed-L10-Electra
|authors = Emilian Huminiuc
|development = https://gitlab.com/emilianh/Lockheed-L10-Electra/
|download = https://gitlab.com/emilianh/Lockheed-L10-Electra/repository/archive.zip
}}

The '''Lockheed Model 10 Electra''' was a twin-engine, all-metal monoplane airliner developed by the Lockheed Aircraft Corporation in the 1930s to compete with the Boeing 247 and Douglas DC-2. The type gained considerable fame as one was flown by Amelia Earhart on her ill-fated around-the-world expedition in 1937

== L10A Gallery ==
{|
| [[File:L10-beauty-shot.jpg|256px|Lockheed L10 Electra sitting on the runway]]
| [[File:L10-cockpit-WIP.jpg|256px|WiP Shot of the L10 Cockpit]]
|-
| [[File:L10-cabin-back.jpg|256px|WiP Lockheed L10 Electra Cabin from the back towards the pointy end]]
| [[File:L10-cabin-front.jpg|256px|WiP Lockheed L10 Electra Cabin from the front towards the tail end]]
|-
| [[File:Electra 1.jpg|256px|Old WiP Lockheed L10 Electra in flight]]
|}

== Amelia Earhart Special Model Gallery ==
{|
| [[File:L10e-AE-rwy1.jpg|256px|L10e Electra "Amelia Earhart Special" on the runway]]
| [[File:L10e-AE-rwy2.jpg|256px|L10e Electra "Amelia Earhart Special" on the runway]]
|-
| [[File:L10e-AE-inflight1.jpg|256px|L10e Electra "Amelia Earhart Special" in flight]]
| [[File:L10e-AE-inflight2.jpg|256px|L10e Electra "Amelia Earhart Special" in flight]]
|-
| [[File:L10e-AE-inflight-close.jpg|256px|L10e Electra "Amelia Earhart Special" in flight]]
|}

== External links ==
* {{Wikipedia|Lockheed Model 10 Electra|Wikipedia|noicon=1}}

{{Lockheed}}

[[Category:Airliners]]
[[Category:Propeller aircraft]]
[[Category:Twin-engined aircraft]]

File:L10e-AE-inflight1.jpg

2015-07-12T23:20:58Z