FlightGear wiki - User contributions [en]

FlightGear Mac OS X Launcher

2014-04-06T22:45:21Z

EmmanuelFrance:

{{stub}}

'''FlightGear Mac OS X Launcher''' is a graphical front end for [[FlightGear]], included in official Mac binaries of [[FlightGear 0.9.10]], [[FlightGear 1.0|1.0.0]], [[Flightgear 1.9.0|1.9.0]], and [[FlightGear 2.0.0|2.0.0]]. The launcher allows one to choose options more easily than with the command line. (see also [[FlightGear 1.0 aircraft names for command line]])

[[File:FlightGear Mac OS X Screenshot.png|right]]

JSBSim Buoyant forces

2014-04-06T21:10:24Z

EmmanuelFrance: /* Modelling added mass */

[[JSBSim]] has support for buoyant gas cells. This page will attempt to explain how to configure them for a JSBSim aircraft.

== FGGasCell and FGBallonet ==

A gas cell models one container (cell) of buoyant gas. It may contain zero or more ballonets (i.e. containers of air). All gas cells in a FDM configuration are declared in the <buoyant_forces> section.

The physical model for FGGasCell and FGBallonet is based on the general gas law.

=== Configuration File Format ===
<syntaxhighlight lang="xml">
<buoyant_forces>
<gas_cell type="{HYDROGEN | HELIUM | AIR}">
<location unit="{M | IN | ...}">
<x> {number} </x>
<y> {number} </y>
<z> {number} </z>
</location>
<x_width unit="{M | IN | ...}"> {number} </x_width>
<y_width unit="{M | IN | ...}"> {number} </y_width>
<z_width unit="{M | IN | ...}"> {number} </z_width>
<x_radius unit="{M | IN | ...}"> {number} </x_radius>
<y_radius unit="{M | IN | ...}"> {number} </y_radius>
<z_radius unit="{M | IN | ...}"> {number} </z_radius>
<max_overpressure unit="{PA | PSI | ...}"> {number} </max_overpressure>
<valve_coefficient unit="{M4*SEC/KG | FT4*SEC/SLUG}"> {number} </valve_coefficient>
<fullness> {number} </fullness>
<heat>
{heat transfer coefficient functions} [lbs ft / sec]
</heat>
<ballonet>
<location unit="{M | IN | ...}">
<x> {number} </x>
<y> {number} </y>
<z> {number} </z>
</location>
<x_width unit="{M | IN | ...}"> {number} </x_width>
<y_width unit="{M | IN | ...}"> {number} </y_width>
<z_width unit="{M | IN | ...}"> {number} </z_width>
<x_radius unit="{M | IN | ...}"> {number} </x_radius>
<y_radius unit="{M | IN | ...}"> {number} </y_radius>
<z_radius unit="{M | IN | ...}"> {number} </z_radius>
<max_overpressure unit="{PA | PSI | ...}"> {number} </max_overpressure>
<valve_coefficient unit="{M4*SEC/KG | FT4*SEC/SLUG}"> {number} </valve_coefficient>
<fullness> {number} </fullness>
<heat>
{heat transfer coefficient functions} [lb ft / (sec Rankine)]
</heat>
<blower_input>
{input air flow function} [ft^3 / sec]
</blower_input>
</ballonet>
</gas_cell>
</buoyant_forces>
</syntaxhighlight>

=== Parameter definitions ===
{| class="prettytable"
|Gas cell element
|
|-
|type
|type of gas in the cell. One of HYDROGEN, HELIUM or AIR.
|-
|location
|location of the centre of the cell in the structural frame of the aircraft. This is were the forces and mass of the cell are applied.
|-
|{x/y/z}_radius
|radius of both ends of the cell in the respective direction.
|-
|{x/y/z}_width
|width (excluding the radius) of the cell in the respective direction.
|-
|fullness
|initial fullness of the cell, normally between 0 and 1. Values above 1 initialize the cell at pressure.
|-
|max_overpressure
|maximum pressure in the cell. In case of excessive pressure gas is automatically valved off.
|-
|valve_coefficient
|the capacity of the manual gas valve. The valve is considered to be located at the top of the cell. The valve coefficient determine the flow out of the cell according to dVolume/dt = ValveCoefficient * DeltaPressure.
|-
|heat
|zero or more FGFunction:s describing the heat flow from the atmosphere into the gas cell. Unit: [lb ft / (sec Rankine)]. If there are no heat transfer functions at all the cell temperature will always be equal that of the surrounding atmosphere. A constant function returning 0 results in adiabatic behaviour, i.e. no heat transfer at all.
|-
|Ballonet element
|
|-
|
|There can be zero or more ballonets in a gas cell.
|-
|location
|location of the centre of the ballonet in the structural frame of the aircraft. This is were the forces and mass of the ballonet are applied.
|-
|{x/y/z}_radius
|radius of both ends of the ballonet in the respective direction.
|-
|{x/y/z}_width
|width (excluding any radius) of the ballonet in the respective direction.
|-
|max_overpressure
|maximum pressure in the ballonet. In case of excessive pressure air is automatically valved off to the atmosphere.
|-
|valve_coefficient
|the capacity of the exit valve between the ballonet and the atmosphere. The valve coefficient determine the flow out of the ballonet according to dVolume/dt = ValveCoefficient * DeltaPressure.
|-
|heat
|zero or more FGFunction:s describing the heat flow from the enclosing gas cell into the ballonet. Unit: [lb ft / (sec Rankine)]. The heat flowing to the ballonet will be deducted from the enclosing gas cell.
|-
|blower_input
|one FGFunction describing the air flow into the ballonet. Unit: [ft3 / sec] at the temperature and pressure of the ballonet.
|}

=== Notes ===
* Gas cell and ballonet shape
** The shape of a cell or ballonet must be specified. It determines the maximum volume of the cell or ballonet and its inertia properties.
** The supported cell and ballonet shapes are ellipsoid (3 radii given) and cylindrical (2 equal radii and one width given). For other combinations the inertia reverts to that of a point mass.

== Examples ==

There are several different types of buoyant aircraft that can be simulated, among them unpressurized and pressurized gas balloons, rigid (unpressurized) airships and pressure airships (blimps and semi-rigid airships).

* '''Unpressurized gas balloons'''. The pressure in the gas cell is kept at that of the atmosphere and the cell's volume will vary with the surrounding air pressure. If the maximum volume of the gas cell is exceeded gas will be lost to the atmosphere. Example: [[ZF Navy free balloon]].
* '''Pressurized gas balloons'''. The gas pressure may exceed that of the surrounding atmosphere (e.g. when the maximum volume has been reached or due to stretching of the envelope). Example: [http://jsbsim.cvs.sourceforge.net/viewvc/jsbsim/JSBSim/aircraft/weather-balloon/ weather balloon].
* '''Rigid (unpressurized) airships'''. The gas cells are kept at atmosphere pressure and vary in volume. The rigid outer shape of the hull maintains its shape regardless of the volume of the gas cells. Example: [[Zeppelin LZ 121 Nordstern]].
* '''Pressure airships'''. The gas cells are kept at a higher pressure than the surrounding atmosphere by means of ballonets (air bladders inside the gas cell) that compensate for volume changes of the lifting gas. As a result the envelope (the outer skin of the gas cells) is kept at its maximum volume and maintains its shape. Examples: [[Submarine Scout]], [[Zeppelin NT]], [http://gitorious.org/anders-hangar/znp-k US Navy ZNP-K / Goodyear K-type airship].

=== Modelling added mass ===

When a body immersed in a fluid accelerates its inertia is not only determined by its inherent mass properties but also by some of the fluid that surrounds the body. If the density of the body is not significantly larger than that of the fluid this effect, usually called [http://en.wikipedia.org/wiki/Added_mass added or virtual mass], needs to be taken into account.

For buoyant aircraft in JSBSim added mass can be modelled using external forces and the [http://gitorious.org/fg/fgdata/source/Aircraft/Generic/JSBSim/Systems/airship_added_mass.xml airship_added_mass.xml] system available in fgdata/Aircraft/Generic/JSBSim/Systems/.
This model is based on NACA report 184 [http://naca.central.cranfield.ac.uk/reports/1924/naca-report-184.pdf (Max M. Munk, "Aerodynamic forces on airship hulls", 1924)].

To use this system a set of external forces need to be defined which will be used to transmit forces and moments due to added mass.
A template for the forces needed follows below:
<syntaxhighlight lang="xml">
<external_reactions>
<force name="added-mass-bx" frame="BODY">
<location unit="">
{ AERORP }
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-by" frame="BODY">
<location unit="">
{ AERORP }
</location>
<direction>
<x> 0.0 </x>
<y> 1.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-bz" frame="BODY">
<location unit="">
{ AERORP }
</location>
<direction>
<x> 0.0 </x>
<y> 0.0 </y>
<z> 1.0 </z>
</direction>
</force>
<force name="added-mass-pitch[0]" frame="BODY">
<location unit="">
<x> AERORP X </x>
<y> AERORP Y </y>
<z> AERORP Z - 0.3048 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-pitch[1]" frame="BODY">
<location unit="M">
<x> AERORP X </x>
<y> AERORP Y </y>
<z> AERORP Z + 0.3048 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-yaw[0]" frame="BODY">
<location unit="M">
<x> AERORP X </x>
<y> AERORP Y - 0.3048 </y>
<z> 0.0 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-yaw[1]" frame="BODY">
<location unit="M">
<x> AERORP X </x>
<y> AERORP Y + 0.3048 </y>
<z> 0.0 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
</external_reactions>
</syntaxhighlight>

The added mass system is configured with the total volume of the hull (aero/constants/volume-ft3), the sum of the squares of the length and maximum diameter of the hull (aero/constants/length-diameter-ft2) and three coefficients (aero/constants/added-mass/k-axial, aero/constants/added-mass/k-traverse and aero/constants/added-mass/k-rotational). The coefficients are set based on the fitness ratio of the hull (length over diameter) and can be interpolated from the table last in [http://naca.central.cranfield.ac.uk/reports/1924/naca-report-184.pdf (Max M. Munk, "Aerodynamic forces on airship hulls", NACA report 184, 1924)]. '''Note that the coefficients entered for this system should have reversed sign compared to those in the report (i.e. be negative).'''

A typical setup of the added mass system looks like this (from [http://gitorious.org/anders-hangar/znp-k US Navy ZNP-K / Goodyear K-type airship]):
<syntaxhighlight lang="xml">
<system name="constants">

<property value="249.20"> aero/constants/length-ft </property>
<property value="57.85"> aero/constants/diameter-ft </property>
<property value="65447.3"> aero/constants/length-diameter-ft2 </property>
<property value="425000.0"> aero/constants/volume-ft3 </property>

<property value="-0.08"> aero/constants/added-mass/k-axial </property>
<property value="-0.88"> aero/constants/added-mass/k-traverse </property>
<property value="-0.65"> aero/constants/added-mass/k-rotational </property>
</system>
<system file="airship_added_mass"/>
</syntaxhighlight>

=== Modelling heat transfer ===

As seen in the list of parameters above, buoyant forces puts the burden of modelling heat the transfer between the gas cell and the environment and between the gas cell and any ballonets on the user. This is due to various configurations having different properties and leaving the possibilities open is JSBSim's approach.

One general but somewhat simplified view of heat transfer would divide it into the following parts:
* Heat transfer through conduction. The heat transferred per time unit is the product of the conductivity of the envelope material, the surface area between the gas and the atmosphere and the difference in temperature between the gas and the atmosphere.
* Heat transfer through black body radiation. The heat transferred per time unit is the product of Stefan-Boltzmann's constant, the emissivity of the envelope material, the surface area between the gas and the atmosphere and the difference between atmosphere temperature to the power of 4 and the the gas temperature to the power of 4.

The formulation of both parts ignore conduction within the gas cell.

For an airship with a single ellipsoid gas cell (like most pressure airships) this could be expressed as follows (from [http://gitorious.org/anders-hangar/znp-k US Navy ZNP-K / Goodyear K-type airship]):
<syntaxhighlight lang="xml">
<heat>
<function name="buoyant_forces/gas-cell/dU_conduction">
<product>
<value> 35685.00 </value> < !-- Surface area [ft2] -- >
<value> 0.05 </value> < !-- Conductivity [lb / (K ft sec)] (Guess) -- >
<difference>
<property> atmosphere/T-R </property>
<property> buoyant_forces/gas-cell/temp-R </property>
</difference>
</product>
</function>
<function name="buoyant_forces/gas-cell/dU_radiation">
<product>
<value> 0.1714e-8 </value> < !-- Stefan-Boltzmann's constant
[Btu / (h ft^2 R^4)] -- >
<value> 0.2 </value> < !-- Emissivity [0,1] (Guess) -- >
<value> 35685.0 </value> < !-- Surface area [ft2] -- >
<difference>
<pow>
<property> atmosphere/T-R </property>
<value> 4.0 </value>
</pow>
<pow>
<property> buoyant_forces/gas-cell/temp-R </property>
<value> 4.0 </value>
</pow>
</difference>
</product>
</function>
</heat>
</syntaxhighlight>

For the ballonets a similar formulation can be used, but with the gas cell temperature instead of the atmosphere temperature.

For a traditional rigid airship with several cylindrical gas cells a first approximation would be to only use the surface area towards the atmosphere in the formulation above and ignore heat exchange with the neighbouring gas cells.

== Sources ==
* http://jsbsim.sourceforge.net/JSBSim/classJSBSim_1_1FGGasCell.html
* http://jsbsim.sourceforge.net/JSBSim/classJSBSim_1_1FGBallonet.html

{{JSBSim}}

JSBSim Buoyant forces

2014-04-06T21:08:12Z

EmmanuelFrance: /* Modelling added mass */

[[JSBSim]] has support for buoyant gas cells. This page will attempt to explain how to configure them for a JSBSim aircraft.

== FGGasCell and FGBallonet ==

A gas cell models one container (cell) of buoyant gas. It may contain zero or more ballonets (i.e. containers of air). All gas cells in a FDM configuration are declared in the <buoyant_forces> section.

The physical model for FGGasCell and FGBallonet is based on the general gas law.

=== Configuration File Format ===
<syntaxhighlight lang="xml">
<buoyant_forces>
<gas_cell type="{HYDROGEN | HELIUM | AIR}">
<location unit="{M | IN | ...}">
<x> {number} </x>
<y> {number} </y>
<z> {number} </z>
</location>
<x_width unit="{M | IN | ...}"> {number} </x_width>
<y_width unit="{M | IN | ...}"> {number} </y_width>
<z_width unit="{M | IN | ...}"> {number} </z_width>
<x_radius unit="{M | IN | ...}"> {number} </x_radius>
<y_radius unit="{M | IN | ...}"> {number} </y_radius>
<z_radius unit="{M | IN | ...}"> {number} </z_radius>
<max_overpressure unit="{PA | PSI | ...}"> {number} </max_overpressure>
<valve_coefficient unit="{M4*SEC/KG | FT4*SEC/SLUG}"> {number} </valve_coefficient>
<fullness> {number} </fullness>
<heat>
{heat transfer coefficient functions} [lbs ft / sec]
</heat>
<ballonet>
<location unit="{M | IN | ...}">
<x> {number} </x>
<y> {number} </y>
<z> {number} </z>
</location>
<x_width unit="{M | IN | ...}"> {number} </x_width>
<y_width unit="{M | IN | ...}"> {number} </y_width>
<z_width unit="{M | IN | ...}"> {number} </z_width>
<x_radius unit="{M | IN | ...}"> {number} </x_radius>
<y_radius unit="{M | IN | ...}"> {number} </y_radius>
<z_radius unit="{M | IN | ...}"> {number} </z_radius>
<max_overpressure unit="{PA | PSI | ...}"> {number} </max_overpressure>
<valve_coefficient unit="{M4*SEC/KG | FT4*SEC/SLUG}"> {number} </valve_coefficient>
<fullness> {number} </fullness>
<heat>
{heat transfer coefficient functions} [lb ft / (sec Rankine)]
</heat>
<blower_input>
{input air flow function} [ft^3 / sec]
</blower_input>
</ballonet>
</gas_cell>
</buoyant_forces>
</syntaxhighlight>

=== Parameter definitions ===
{| class="prettytable"
|Gas cell element
|
|-
|type
|type of gas in the cell. One of HYDROGEN, HELIUM or AIR.
|-
|location
|location of the centre of the cell in the structural frame of the aircraft. This is were the forces and mass of the cell are applied.
|-
|{x/y/z}_radius
|radius of both ends of the cell in the respective direction.
|-
|{x/y/z}_width
|width (excluding the radius) of the cell in the respective direction.
|-
|fullness
|initial fullness of the cell, normally between 0 and 1. Values above 1 initialize the cell at pressure.
|-
|max_overpressure
|maximum pressure in the cell. In case of excessive pressure gas is automatically valved off.
|-
|valve_coefficient
|the capacity of the manual gas valve. The valve is considered to be located at the top of the cell. The valve coefficient determine the flow out of the cell according to dVolume/dt = ValveCoefficient * DeltaPressure.
|-
|heat
|zero or more FGFunction:s describing the heat flow from the atmosphere into the gas cell. Unit: [lb ft / (sec Rankine)]. If there are no heat transfer functions at all the cell temperature will always be equal that of the surrounding atmosphere. A constant function returning 0 results in adiabatic behaviour, i.e. no heat transfer at all.
|-
|Ballonet element
|
|-
|
|There can be zero or more ballonets in a gas cell.
|-
|location
|location of the centre of the ballonet in the structural frame of the aircraft. This is were the forces and mass of the ballonet are applied.
|-
|{x/y/z}_radius
|radius of both ends of the ballonet in the respective direction.
|-
|{x/y/z}_width
|width (excluding any radius) of the ballonet in the respective direction.
|-
|max_overpressure
|maximum pressure in the ballonet. In case of excessive pressure air is automatically valved off to the atmosphere.
|-
|valve_coefficient
|the capacity of the exit valve between the ballonet and the atmosphere. The valve coefficient determine the flow out of the ballonet according to dVolume/dt = ValveCoefficient * DeltaPressure.
|-
|heat
|zero or more FGFunction:s describing the heat flow from the enclosing gas cell into the ballonet. Unit: [lb ft / (sec Rankine)]. The heat flowing to the ballonet will be deducted from the enclosing gas cell.
|-
|blower_input
|one FGFunction describing the air flow into the ballonet. Unit: [ft3 / sec] at the temperature and pressure of the ballonet.
|}

=== Notes ===
* Gas cell and ballonet shape
** The shape of a cell or ballonet must be specified. It determines the maximum volume of the cell or ballonet and its inertia properties.
** The supported cell and ballonet shapes are ellipsoid (3 radii given) and cylindrical (2 equal radii and one width given). For other combinations the inertia reverts to that of a point mass.

== Examples ==

There are several different types of buoyant aircraft that can be simulated, among them unpressurized and pressurized gas balloons, rigid (unpressurized) airships and pressure airships (blimps and semi-rigid airships).

* '''Unpressurized gas balloons'''. The pressure in the gas cell is kept at that of the atmosphere and the cell's volume will vary with the surrounding air pressure. If the maximum volume of the gas cell is exceeded gas will be lost to the atmosphere. Example: [[ZF Navy free balloon]].
* '''Pressurized gas balloons'''. The gas pressure may exceed that of the surrounding atmosphere (e.g. when the maximum volume has been reached or due to stretching of the envelope). Example: [http://jsbsim.cvs.sourceforge.net/viewvc/jsbsim/JSBSim/aircraft/weather-balloon/ weather balloon].
* '''Rigid (unpressurized) airships'''. The gas cells are kept at atmosphere pressure and vary in volume. The rigid outer shape of the hull maintains its shape regardless of the volume of the gas cells. Example: [[Zeppelin LZ 121 Nordstern]].
* '''Pressure airships'''. The gas cells are kept at a higher pressure than the surrounding atmosphere by means of ballonets (air bladders inside the gas cell) that compensate for volume changes of the lifting gas. As a result the envelope (the outer skin of the gas cells) is kept at its maximum volume and maintains its shape. Examples: [[Submarine Scout]], [[Zeppelin NT]], [http://gitorious.org/anders-hangar/znp-k US Navy ZNP-K / Goodyear K-type airship].

=== Modelling added mass ===

When a body immersed in a fluid accelerates its inertia is not only determined by its inherent mass properties but also by some of the fluid that surrounds the body. If the density of the body is not significantly larger than that of the fluid this effect, usually called [http://en.wikipedia.org/wiki/Added_mass added or virtual mass], needs to be taken into account.

For buoyant aircraft in JSBSim added mass can be modelled using external forces and the [http://gitorious.org/fg/fgdata/source/Aircraft/Generic/JSBSim/Systems/airship_added_mass.xml airship_added_mass.xml] system available in fgdata/Aircraft/Generic/JSBSim/Systems/.
This model is based on NACA report 184 [http://naca.central.cranfield.ac.uk/reports/1924/naca-report-184.pdf (Max M. Munk, "Aerodynamic forces on airship hulls", 1924)].

To use this system a set of external forces need to be defined which will be used to transmit forces and moments due to added mass.
A template for the forces needed follows below:
<syntaxhighlight lang="xml">
<external_reactions>
<force name="added-mass-bx" frame="BODY">
<location unit="">
{ AERORP }
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-by" frame="BODY">
<location unit="">
{ AERORP }
</location>
<direction>
<x> 0.0 </x>
<y> 1.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-bz" frame="BODY">
<location unit="">
{ AERORP }
</location>
<direction>
<x> 0.0 </x>
<y> 0.0 </y>
<z> 1.0 </z>
</direction>
</force>
<force name="added-mass-pitch[0]" frame="BODY">
<location unit="">
<x> AERORP X </x>
<y> AERORP Y </y>
<z> AERORP Z - 0.3048 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-pitch[1]" frame="BODY">
<location unit="M">
<x> AERORP X </x>
<y> AERORP Y </y>
<z> AERORP Z + 0.3048 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-yaw[0]" frame="BODY">
<location unit="M">
<x> AERORP X </x>
<y> AERORP Y - 0.3048 </y>
<z> 0.0 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
<force name="added-mass-yaw[1]" frame="BODY">
<location unit="M">
<x> AERORP X </x>
<y> AERORP Y + 0.3048 </y>
<z> 0.0 </z>
</location>
<direction>
<x> 1.0 </x>
<y> 0.0 </y>
<z> 0.0 </z>
</direction>
</force>
</external_reactions>
</syntaxhighlight>

The added mass system is configured with the total volume of the hull (aero/constants/volume-ft3), the sum of the squares of the length and maximum diameter of the hull (aero/constants/length-diameter-ft2) and three coefficients (aero/constants/added-mass/k-axial, aero/constants/added-mass/k-traverse and aero/constants/added-mass/k-rotational). The coefficients are set based on the fitness ratio of the hull (length over diameter) and can be interpolated from the table last in [http://naca.central.cranfield.ac.uk/reports/1924/naca-report-184.pdf (Max M. Munk, "Aerodynamic forces on airship hulls", NACA report 184, 1924)]. '''Note that the coefficients entered for this system should have reversed sign compared to those in the report (i.e. be negative).'''

A typical setup of the added mass system looks like this (from [http://gitorious.org/anders-hangar/znp-k US Navy ZNP-K / Goodyear K-type airship]):
<syntaxhighlight lang="xml">
<system name="constants">

<property value="249.20"> aero/constants/length-ft </property>
<property value="57.85"> aero/constants/diameter-ft </property>
<property value="65447.3"> aero/constants/length-diameter-ft2 </property>
<property value="425000.0"> aero/constants/volume-ft3 </property>

<property value="-0.08"> aero/constants/added-mass/k-axial </property>
<property value="-0.88"> aero/constants/added-mass/k-traverse </property>
<property value="-0.65"> aero/constants/added-mass/k-rotational </property>
</system>
<system file="airship_added_mass"/>
</syntaxhighlight lang="xml">

=== Modelling heat transfer ===

As seen in the list of parameters above, buoyant forces puts the burden of modelling heat the transfer between the gas cell and the environment and between the gas cell and any ballonets on the user. This is due to various configurations having different properties and leaving the possibilities open is JSBSim's approach.

One general but somewhat simplified view of heat transfer would divide it into the following parts:
* Heat transfer through conduction. The heat transferred per time unit is the product of the conductivity of the envelope material, the surface area between the gas and the atmosphere and the difference in temperature between the gas and the atmosphere.
* Heat transfer through black body radiation. The heat transferred per time unit is the product of Stefan-Boltzmann's constant, the emissivity of the envelope material, the surface area between the gas and the atmosphere and the difference between atmosphere temperature to the power of 4 and the the gas temperature to the power of 4.

The formulation of both parts ignore conduction within the gas cell.

For an airship with a single ellipsoid gas cell (like most pressure airships) this could be expressed as follows (from [http://gitorious.org/anders-hangar/znp-k US Navy ZNP-K / Goodyear K-type airship]):
<heat>
<function name="buoyant_forces/gas-cell/dU_conduction">
<product>
<value> 35685.00 </value> < !-- Surface area [ft2] -- >
<value> 0.05 </value> < !-- Conductivity [lb / (K ft sec)] (Guess) -- >
<difference>
<property> atmosphere/T-R </property>
<property> buoyant_forces/gas-cell/temp-R </property>
</difference>
</product>
</function>
<function name="buoyant_forces/gas-cell/dU_radiation">
<product>
<value> 0.1714e-8 </value> < !-- Stefan-Boltzmann's constant
[Btu / (h ft^2 R^4)] -- >
<value> 0.2 </value> < !-- Emissivity [0,1] (Guess) -- >
<value> 35685.0 </value> < !-- Surface area [ft2] -- >
<difference>
<pow>
<property> atmosphere/T-R </property>
<value> 4.0 </value>
</pow>
<pow>
<property> buoyant_forces/gas-cell/temp-R </property>
<value> 4.0 </value>
</pow>
</difference>
</product>
</function>
</heat>

For the ballonets a similar formulation can be used, but with the gas cell temperature instead of the atmosphere temperature.

For a traditional rigid airship with several cylindrical gas cells a first approximation would be to only use the surface area towards the atmosphere in the formulation above and ignore heat exchange with the neighbouring gas cells.

== Sources ==
* http://jsbsim.sourceforge.net/JSBSim/classJSBSim_1_1FGGasCell.html
* http://jsbsim.sourceforge.net/JSBSim/classJSBSim_1_1FGBallonet.html

{{JSBSim}}

Json Properties

2014-03-28T23:44:47Z

EmmanuelFrance:

== Abstract ==
Beginning with the developer version 3.1 and the indroduction of the advanced internal web server, the access to internal properties via web services have been introduced. The properties are represented as [http://www.json.org/ JSON]. This Article contains the format description of JSON properties.

=== Example ===
This is an example of the /sim/time subtree:

<syntaxhighlight>
{
"path": "/sim/time",
"name": "time",
"type": "-",
"index": 0,
"nChildren": 12,
"children": [{
"path": "/sim/time/cur-time-override",
"name": "cur-time-override",
"value": "0",
"type": "long",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/delta-sec",
"name": "delta-sec",
"value": "0.01666666667",
"type": "double",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/warp",
"name": "warp",
"value": "-28320",
"type": "int",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/warp-delta",
"name": "warp-delta",
"value": "0",
"type": "int",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/delta-realtime-sec",
"name": "delta-realtime-sec",
"value": "0.01666666667",
"type": "double",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/local-offset",
"name": "local-offset",
"value": "3600",
"type": "int",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/utc",
"name": "utc",
"type": "-",
"index": 0,
"nChildren": 8
}, {
"path": "/sim/time/real",
"name": "real",
"type": "-",
"index": 0,
"nChildren": 7
}, {
"path": "/sim/time/elapsed-sec",
"name": "elapsed-sec",
"value": "7072.525",
"type": "double",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/gmt",
"name": "gmt",
"value": "2014-03-27T13:25:10",
"type": "string",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/gmt-string",
"name": "gmt-string",
"value": "13:25:10",
"type": "string",
"index": 0,
"nChildren": 0
}, {
"path": "/sim/time/sun-angle-rad",
"name": "sun-angle-rad",
"value": "0.9883239645",
"type": "double",
"index": 0,
"nChildren": 0
}]
}
</syntaxhighlight>

== Definitions ==
* JavaScript Object Notation (JSON), and the terms object, name, value, array, and number, are defined in [http://www.ietf.org/rfc/rfc4627.txt IETF RTC 4627].
* The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [http://www.ietf.org/rfc/rfc2119.txt IETF RFC 2119].

== Property Objects ==
A Property Object always consist of a single object. This object represents a single property node or a complete (sub) tree of nodes.

* Each object must have a member with the name ''path''. The members value is a string naming the absolute path of the node in the property tree. Example: '''/engines/engine[1]'''
* Each object must have a member with the name ''name''. The members value is a string that determines the name of the node. Example: '''engine'''
* Each object may have a member with the name ''value''. The members value contains the property nodes value. The current server implementation returns property node values by using the getStringValue() function.
* Each object must have a member with the name ''type''. The members value must be on of "-" (for no type), "alias", "bool", "int", "long", "float", "double", "string", "unspecified", "extended", "vec3d" or "vec4d".
* Each object may have a member with the name ''index''. The members value determines the index of the node in the parents node. Example: For a node /engines/engine[1] this would be 1. A missing ''index'' attribute results in an index of 0 (zero).
* Each object may have a member with the name ''ts''. The members value represents the time when the server read node from the property tree. This is the time of /sim/time/elapsed-sec.
* Each object may have a member with the name ''nChildren''. The members value determines the number of children under this node. It is optional to actually display the children itself within the JSON object.
* Each object may have a member with the name ''children''. The members value is an array of JSON Property Objects.

== Accessing the Property Tree ==
=== The web service ===
A simple web service provides read-only access to the property tree. This web service can be reached at the URL http://localhost:port/json
where port is the portnumber provided to the -httpd= startup option. Path elements following that URL are interpreted as a property path, so http://localhost:port/json/sim/time returnes the JSON representation of the property node /sim/time and its immediate children (see example above).
The service understands the following request parameters:
* i - if the request parameter i is set to 'y', the output will be indented to make it more readable by humans. If the parameter is missing or assigned any other value, the output will be compressed.
* t - if the request parameter t is set to 'y', the returned properties will be time stamped with the value of simulation time
* d - the recursion depth of the resulting tree. The default and minimum depth is implemented as 1 resulting in the node itself and - if existing - the immediate children of the node. A value of 2 would return the node itself, it's children and their children. A very high value combined with a request for the root node returns a complete dump of the property tree (use this with caution!)

=== The /PropertyListener websocket ===
The property change listener websocket also sends property objects as change events for the subscribed nodes.

== Pitfalls ==
* calling http://localhost:port/json results in a 404 (Not found) error. Use http://localhost:port/json/ to access the root node.
* asking for a nonexistant node returns an empty object ''{}''

FGPlot

2014-03-02T20:26:39Z

EmmanuelFrance:

{{infobox subsystem
|image =FgPlot.jpg
|name =FGPlot
|started= 05/2013
|description = Provide plotting support inside FlightGear using the [[Canvas]]
|status = Under active development as of 05/2013
|developers = kuifje09 (since 05/2013),

|topic-fgdata= [https://gitorious.org/fg/canvas-hackers-fgdata canvas-hackers team clone] (topics/fgplot)
|subforum= http://forum.flightgear.org/viewforum.php?f=71
}}

{{Note|Contributors wanting to use FGPlot, need to check out the topics/canvas-radar fgdata branch, using these 3 steps:
# git add remote canvas-hackers git@gitorious.org:fg/canvas-hackers-fgdata.git
# git fetch canvas-hackers
# git checkout --track -b fgplot canvas-hackers/topics/fgplot

This will give you a local branch named '''fgplot''' (tracking topics/fgplot), so that you can easily pull/push changes.
When pulling, it makes sense to pull with --rebase.
The fgplot dialog can be found in the ''Equipment'' menu.
}}

== Objective ==
Provide a built-in plotting tool to help with autopilot/FDM tuning, and other efforts that profit from native plotting capabilities.

== Status / Changelog ==
kuifje09 is now working on an updated version of FGPlot, called "FGPlot 2" which will be implemented using just Nasal scripting and the canvas subsystem, as a Nasal submodule.

* 07/2013: consider creating dialogs/windows dynamically [http://forum.flightgear.org/viewtopic.php?f=71&t=20024&p=186527#p186526] {{Progressbar|50}}
** fullscreen mode, see [[Howto:Creating fullscreen Canvas applications]] {{progressbar|50}}
** provide support for zooming/panning {{progressbar|40}}
** consider using a Nasal submodule for fgplot ? {{Done}} (in FGPlot2)
** consider adding a time marker [http://forum.flightgear.org/viewtopic.php?f=71&t=20024&p=186527#p186470] {{Done}}
** New support for saving/loading plotting profiles with property sets {{Done}}
* 06/2013: kuijfe09 has finished porting his original C code to use [[Nasal]] scripting and the [[Canvas]] system {{Done}}

== Roadmap ==

== Feature Requests & Ideas ==
* add tooltip support {{Not done}}
* try to use widgets provided by the canvas system {{Not done}}
* consider making min/max axis dimensions configurable based on properties (alt, speed, vs) {{Not done}}
* consider adding support for property-profiles (name, list of properties - e.g. "FDM", "AP", "Approach (altitude vs. terrain)") {{Not done}}
* consider supporting additional plotting modes, e.g. altitude for FDM developers {{Not done}}
* consider generalizing the code, so that a "graph widget" can be created for all sorts of property-driven graphs {{Not done}}
* '''C++''': provide a new Nasal API to serialize a canvas texture (or better a group) to an osg::Image in $FG_HOME, so that graphs can be easily saved and shared/posted online without users having to take full screen shots and then having to manually extract the graph [http://forum.flightgear.org/viewtopic.php?f=49&t=17540&hilit=gnuplot#p166472] {{Not done}}
* '''C++''': expose cppbind hooks to access flight recorder/replay data [http://forum.flightgear.org/viewtopic.php?f=71&t=19371#p178997] {{Not done}}

== FGPlot ==

FGPlot is being developed as a conventional XML dialog, for the time being with a <canvas> section for 2D rendering. Once PUI will be phased out, this will be ported to use a native canvas window instead.

To FlightGear, fgplot is just an XML file with embedded Nasal code.

[[File:FgPlot.jpg]]

* [http://forum.flightgear.org/viewtopic.php?f=71&t=20024 kuifje09's FGPlot Development]
* [[Howto:Adding a canvas to a GUI dialog]]
* [[Howto:Creating a Canvas graph widget]]
* [http://www.mail-archive.com/flightgear-users@lists.sourceforge.net/msg04253.html Plot flight path]

== Background ==

{{cquote|I was just thinking today that it might be cool to have a built in grapher for simple / quick graphing needs.

With the property system it would be trivial to pick an arbitrary property from the property tree and graph it over time -- superimposed on top of everything else.

Things get a bit trickier if you want to control scaling, how much time history get's graphed, multiple values, etc., but even graphing a single value (or maybe just two values) over time could be of some use.

I thought I'd toss this out there in case someone thought it was worth while enough to tackle.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg03651.html |title=idea ... (?)|author=Curtis Olson |date=Fri, 08 Mar 2002 07:43:35 -0800}}</ref>|Curtis Olson}}

{{cquote|Yes, this would be no substitute for data logging and post processing, but if you know what you are looking for, I do think it could be
useful.
The immediate thing that comes to my mind is this:

As a side project I'm working on integrating a 'commercial' fdm with FlightGear via a network interface. One of the things this code
supports is control loading. The hardware guys are chomping on the bit wanting to know what range of values the software is going to kick out.

Something like a quick and dirty embedded graphing program would be pretty nifty.

"cout" probably works just as well, but it's not as pretty. :-) And once you had the basic graphing mechanism in place, it would be
trivial to let the user specify which property(ies) to graph.

Maybe we could even hook up the GUI prop-picker to specify which values we want rather than forcing the user to type them all in.

FWIW, I think it's important for the FDM guys to frequenty fly their code in real time. In real time with visuals attached, various
incorrect effects and behaviors can really jump out at you ... stuff that you'd never notice when looking through tabular data, or even a
graph. Sometimes the trend is correct, but the scale or the sign is way off.

I would think that being able to fly in real time, and see some key graphical data output would be an immensly useful debugging tool.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg03654.html |title=idea ... (?)|author=Curtis Olson |date=Fri, 08 Mar 2002 07:43:35 -0800}}</ref>|Curtis Olson}}

{{cquote|we can spend all day pointing out situations where realtime graphing wouldn't be helpful, but if there are some situations where
it would be helpful, and in fact preferable to post processing, then doesn't that make it worth doing?<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg03664.html |title=idea ... (?)|author=Curtis Olson |date=Fri, 08 Mar 2002 07:43:35 -0800}}</ref>|Curtis Olson}}

{{cquote|Sure, you could use it to graph the value of any flight gear property over time ... not just FDM values. This could be useful for all sorts
of stuff ... debugging panel actions, 3d model animations, environment modeling, etc.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg03671.html |title=idea ... (?)|author=Curtis Olson |date=Fri, 08 Mar 2002 07:43:35 -0800}}</ref>|Curtis Olson}}

<references/>

[[Category:Developer Plans]]

Fr/Changelog 2.8.0

2014-03-02T13:50:29Z

EmmanuelFrance: ortho

{{Changelog translation|2.8.0|http://www.flightgear.org/news/flightgear-v2-8-0-released/}}

L'équipe de développement de FlightGear est heureuse de vous annoncer la sortie de la version 2.8.0 de FlightGear, le simulateur de vol libre et gratuit. Cette nouvelle version comprend de nouvelles fonctionnalités passionnantes, des améliorations et des corrections de bogues. Les principales améliorations par rapport à la version 2.6.0 sont des aéronefs IA (intelligence artificielle) améliorés, une mise à jour permettant de bénéficier des toutes dernières améliorations du modèle de vol JSBSim, la prise en charge de textures spécifiques par région, de meilleurs immeubles aléatoires 3D, un meilleur positionnement des objets aléatoires, des signes d'aéroport en 3D, un passage des textures d'hiver aux textures d'été directement commutable depuis le simulateur. Le code source de FlightGear prend maintenant en charge un système de rendu 2D très souple qui permet de modéliser de manière fidèle les tableaux de bord "tout écran" et autres instruments complexes. Il y a de nombreux avions nouveaux ou améliorés à explorer. Un nouveau système automatisé est à présent en place pour que les utilisateurs puissent soumettre des objets qui seront alors automatiquement intégrés dans notre système de distribution des scènes afin que chacun puisse en profiter. La version 2.8 propose également une modélisation améliorée de la diffusion atmosphérique de la lumière, une meilleure brume de terrain et des nuages 3D améliorés.

Un nouvel ajout très innovant est connu sous le nom de “Projet Rembrandt”. Il est toujours considéré comme expérimental et par conséquent non activé par défaut. Mais lorsque vous l'activerez, vous obtiendrez des ombres temps-réel, la prise en charge de sources de lumière multiples (phares d'atterrissage, lumières des instruments, éclairages de sol directionnels et même les balises lumineuses rotatives qui illumineront enfin les environs correctement). En complément, le projet Rembrandt offre toute une palette d'effets visuels divers, comme la vision de nuit, l'effet de grain que l'on voit parfois sur les vieux films, les effets de profondeur de vue, les distorsions liées aux lentilles (comme le grand angle) — le tout en temps réel.

Créé en 1997, FlightGear a célébré le 15ème anniversaire de sa première version officielle en juillet dernier. FlightGear est développé par un groupe mondial de volontaires, qui se rejoignent autour d'une même ambition : celle de créer le simulateur de vol le plus réaliste possible, gratuit et libre d'utilisation, de modification et de distribution. FlightGear est utilisé dans le monde entier par des amateurs de simulation de vol, par la recherche universitaire et le monde de l'éducation, pour une variété de travaux d'ingénierie aéronautique et de travaux de visualisation dans le monde de l'industrie et même pour des expositions interactives dans les musées.

FlightGear propose plus de 400 aéronefs, une base de données des scènes mondiale, un environnement mondial multijoueurs, une modélisation détaillée du ciel, un système de modélisation des aéronefs ouvert et flexible, des options de réseau variées, une prise en charge des configuration multi-écrans, un langage de script puissant et une architecture ouverte. Mieux encore, étant libre, le simulateur appartient à la communauté et chacun est encouragé à contribuer.

Téléchargez FlightGear v2.8.0 gratuitement à l'adresse [http://www.flightgear.org FlightGear.org]

FlightGear - Volez librement !

=== Quelques-unes des modifications majeures : ===

'''Trafic Intelligence Artificielle'''
* Modèles et textures des aéronefs améliorés.

'''Dynamique de vol'''
* FlightGear a été synchronisé avec le projet JSBSim.

'''Environnement'''
* Des textures de terrain spécifiques à chaque région sont utilisées pour l'Europe et Hawaï. Maintenant, les villes en Europe sont différentes des villes aux Etats-Unis.
* Les villes et villages sont dorénavant plus réalistes grâce à la présence de bâtiments 3D aléatoires, couplés avec un éclairage de nuit.
* Les scènes ont l'air plus réalistes grâce au placement amélioré des objets aléatoires, des bâtiments et des arbres.
* La signalisation aéroportuaire est dorénavant rendue en 3D, avec la prise en charge d'une signalisation à double face. L'implémentation de la syntaxe apt.dat 850 est complète.
* Vous pouvez dorénavant basculer entre l'été et l'hiver directement à partir du simulateur.

'''Instruments et collimateurs tête-haute'''
* Un nouveau système de rendu 2D particulièrement souple a été conçu pour les instruments complexes comme les CDU, MFD, EICAS, HUD et autres tableaux de bord "tout écran". [[Canvas]] permet aux concepteurs d'aéronefs de construire aisément des instruments complexes sans avoir besoin de code C++ spécifique.

'''Interface'''
* La prise en charge de la traduction du menu principal dans des langues autres que l'anglais (une traduction française du menu principal et des options en ligne de commande est intégrée).
* Une interface Nasal est disponible, permettant un accès aux données de navigation et du gestionnaire de route.

'''Soulignons particulièrement quelques aéronefs mis à jour'''
* [[Airwave Xtreme 150]] : dynamique de vol totalement revue (JSBSim), nouveau modèle, animations avancées du pilote.
* [[Cessna 337G Skymaster]]

'''Infrastructure du projet'''
* Diverses améliorations à notre base de données des scènes permettent de faciliter grandement l'ajout, la suppression ou la mise à jour d'objets dans le monde FlightGear.
* La nouvelle page de téléchargement des aéronefs vous permet de trouver facilement des aéronefs de qualité, en les filtrant par les indications sur leur statut.

'''Effets visuels'''
* Simulation améliorée de la diffusion atmosphérique de la lumière avec la brume de terrain.
* Un système de rendu expérimental, nommé d'après le peintre bien connu Rembrandt, est inclus à des fins d'essais. Le système de rendu du [[Fr/Projet Rembrandt]] prend en charge des sources de lumière multiples (phares d'atterrissage, lumières des instruments), les ombres en temps réel et l'occlusion d'ambiance entre les aéronefs et les scènes pour une expérience visuelle bien plus réaliste.

'''Autres'''
* De nouveaux palonniers et joysticks sont directement pris en charge :
** InterLink Elite
** Microsoft Xbox 360 Controller
** Qware USB
** Saitek Cyborg X (F.L.Y. 5)
** Saitek Pro Flight Cessna Yoke
** Saitek Pro Flight Cessna Trim Wheel
** Saitek Pro Flight Cessna Rudder Pedals
** Speedlink Defender
* Une traduction française partielle du manuel FlightGear est dorénavant disponible.

'''Correction de bogues'''
* Voir [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.8.0 notre outil de suivi] pour une liste exhaustive des bogues corrigés dans cette version.

[[Category:FlightGear changelogs]]

[[en:Changelog 2.8.0]]
[[nl:Changelog 2.8.0]]

FlightGear Flight Academy

2014-03-02T13:37:22Z

EmmanuelFrance:

{{WIP|The Academy was revived in October, 2012 and this article will be updated and expanded in the coming weeks.}}

The '''FlightGear Flight Academy''' is a virtual school that teaches how to control an [[aircraft]], read maps and charts, use navigation facilities and instruments, do standard procedures and everything else needed by a pilot.

== Contacts ==
* [http://forum.flightgear.org/viewtopic.php?f=10&t=2525 The Forum Topic]
* [[IRC]] channel '''#fg_school''' on '''irc.flightgear.org'''

Check [[FlightGear IRC channel]] on how to join an IRC channel.

== What you need ==
* '''Aircraft:''' ''[[Cessna C172|Cessna C172P]] (with [[Dual control]])''
* '''Scenery with the airport ''(specify)'' where the flightschool is based:''' ''(which scenery square?)''

== How lessons are performed ==

== Reading materials ==
* [http://www.faa.gov/library/manuals/aircraft/airplane_handbook/ FAA Airplane Flying Handbook]
* [http://www.faa.gov/Library/manuals/aviation/pilot_handbook/ Pilot's Handbook of Aeronautical Knowledge]
* [http://www.navfltsm.addr.com/ Flight Simulator Navigation]
* [http://www.flightgear.org/Docs/Tutorials/crosscountry/tutorial.html FlightGear VFR Cross Country Tutorial]
* [http://www.flightgear.org/Docs/getstart/getstartch9.html#x15-1570009 FlightGear IFR Cross Country Tutorial]
* [http://www.luizmonteiro.com/Learning.aspx Examples For Various Flight Instruments]
* [http://www.faa.gov/library/manuals/aircraft/glider_handbook/media/faa-h-8083-13.pdf FAA Glider Flying Handbook]
* [http://www.faa.gov/library/manuals/aircraft/media/faa-h-8083-21.pdf FAA Rotorcraft Flying Handbook]
* [http://www.faa.gov/library/manuals/aviation/instrument_flying_handbook/ FAA Instrument Flying Handbook]

== Studying plan ==
=== Private Pilot Lessons ===
* [[Aerodynamics]]
* [[Emergency Descent]]
* [[Slow Flight (Minimum Controllable Airspeed)]]
* [[Rectangular Course]]
* [[Soft Field Landing]]
* [[Steep Turns]]
* [[Take Off]]
* [[Emergency Approach]]
* [[Go Around]]
* [[Normal Landing]]
* [[Short Field Landing]]
* [[Stalls and Spin Awareness]]
* [[S-Turns]]
* [[Turns About a Point]]

== Schedule ==

[[Category:FlightGear Flight Academy| ]]

Current events

2014-03-02T13:03:05Z

EmmanuelFrance:

This page lists events directly, or indirectly, related to [[FlightGear]]. Please note that FlightGear is not being advertised at all of these events, but feel free to spread the word when you visit an event ;)

Upcoming and past [[multiplayer]] events can be found in the [http://www.flightgear.org/calendar.html FlightGear MP Event calendar].

'''Feel free to add events that are linked to FlightGear.'''

== Upcoming events ==
* '''2014'''

== Past events ==
* '''2013'''
** '''November 2+3 2013:''' [[FSweekend 2013]] at [[Aviodrome]] ([[Lelystad Airport]], the Netherlands)
* '''2012'''
** '''November 3+4 2012:''' [[FSweekend 2012]] at [[Aviodrome]] ([[Lelystad Airport]], the Netherlands)
* '''2011'''
** '''November 5+6 2011:''' [[FSweekend 2011]] at [[Aviodrome]] ([[Lelystad Airport]], the Netherlands)
*** [[FlightGear Newsletter November 2011#FSweekend 2011|Event report]]
** '''May 11-14:''' [http://www.linuxtag.org/ LinuxTag Berlin] at the ''Messegelände unter dem Funkturm'', Berlin, Germany.
*** [[FlightGear Newsletter May 2011#LinuxTag 2011|Event report]]
* '''2010'''
** '''November 6+7:''' [[FSweekend 2010]] at [[Aviodrome]] ([[Lelystad Airport]], the Netherlands)
*** [[FlightGear Newsletter November 2010#FSweekend|Event report]]
*** [http://www.dropbox.com/gallery/7455889/1/FSWeekend2010?h=0e9825 Pictures]
** '''August 28+29:''' [http://www.astrasimexpo.co.uk/ Summer Sim 2010] at the Royal Air Force Museum, Cosford, United Kingdom
** '''July 6-11:''' [http://2010.rmll.info/?lang=en Libre Software Meeting] in Bordeaux, France
** '''June 9-12:''' [http://www.linuxtag.org/ LinuxTag Berlin] at the ''Messegelände unter dem Funkturm'', Berlin, Germany
** '''May 15+16:''' [http://www.fscweston.co.uk/ Flight Simulator Convention 2010] at the Helicopter Museum in Weston Super Mare, North Somerset, United Kingdom
* '''2009'''
** '''November 7+8:''' [[FSweekend 2009]] at [[Aviodrome]] ([[Lelystad Airport]], the Netherlands)
*** [[FlightGear Newsletter November 2009#FSweekend|Event report]]
*** [http://www.xs4all.nl/~dtalsma/FSWeekend/web/ Pictures] {{dead link|2012-3}}
** '''June 24-27:''' [http://www.linuxtag.org/ LinuxTag Berlin] at the Messegelände unter dem Funkturm, Berlin, Germany
* '''2008'''
** '''November 1+2:''' [[FSweekend]] at [[Aviodrome]] ([[Lelystad Airport]], the Netherlands)
*** [http://www.t3r.de/flightpics/fsweekend2008/ Pictures]
** '''May 28-31:''' [http://www.linuxtag.org/2008 LinuxTag] at Berlin's Messezentrum unter dem Funkturm. The world's No. 1 Linux Expo and Conference since 1996
*** [http://www.t3r.de/linuxtag/ Pictures]
*** [http://durktalsma.xs4all.nl/LinuxTag2008/web/index.html Pictures] {{dead link|2012-3}}
** '''February 8-10:''' [http://www.socallinuxexpo.org Southern California Linux Expo] in The Westin Hotel (Los Angeles, CA, United States)
* '''2007'''
** '''November 3+4:''' [[FSweekend]] at Aviodrome (Lelystad Airport, the Netherlands)
*** [http://durktalsma.xs4all.nl/FSWeekend2007/web/index.html Pictures] {{dead link|2012-3}}
** '''May 30-June 2:''' [http://www.linuxtag.org/2007 LinuxTag] at Berlin's Messezentrum unter dem Funkturm. The world's No. 1 Linux Expo and Conference since 1996
* '''2006'''
** '''November 4+5:''' [[FSweekend]] at Aviodrome (Lelystad Airport, the Netherlands)

[[Category:List]]
[[Category:Community]]
[[Category:Events]]

Eurocopter EC130 B4

2014-03-02T12:26:55Z

EmmanuelFrance:

{{infobox Aircraft
|image = EC130.jpg
|name = Eurocopter EC130 B4
|type = Civilian helicopter
|fdm = YASim
|authors = Heiko Schulz (Basic 3d-model, FDM, Nasal Scripts) Melchior Franz (Nasal) Michael Habarta (Model details, Animations, Liveries, Configuration Menu, Debugging) FlightGear Community (help and support)
|fgname = ec130
|status-fdm = 4
|status-systems = 4
|status-cockpit = 4
|status-model = 5
|download =http://www.flightgear.org/download/aircraft-v2-12/
|development =https://gitorious.org/ec130
}}
This is a model of a '''Eurocopter EC130 B4''', a single engine light [[helicopter]] based and developed from the [[Ecureuil AS 350 Helicopter|AS350]]'s.

=== The Real Thing ===

Indeed “EC130 B4” is just a marketing name by [[Eurocopter]], now known as Airbus Helicopters, the real name is still AS350 B4. It is a widebody variant of the AS350 B3 with a completely new designed passenger cabin and fuselage and rotor and hydraulics system from the AS355. It is also equipped with a fan tail (fenestron) instead of the conventional two-blade tailrotor. With this the EC130 B4 is much less noisier than other helicopters of this class.

The helicopter was designed especially for tours, so it features a great visibility, a left-seated pilot and plenty of space inside. The EC130 B4 is also used by the police in Long Beach/CA and by several medical services.

The EC130 B4 has been built until 2013. Now it is replaced by the improved EC130 T2, with a new and more powerfull Turbomeca Arriel 2D engine and a 70% modified airframe. The exterior, cockpit and interior has been also modified.<ref>{{cite web |url=http://www.airbushelicopters.com/site/en/ref/Characteristics_1180.html |title=EC130 T2 |publisher=www.airbushelicopters.com }}</ref>
<references/>

=== The FlightGear Model===

The model of the EC130 B4 was built using very detailed drawings, the Pilots Flight Manual and pilot reports.

[[Image:Rembrandtready.png|link=Rembrandt]]
[[Image:Tutorialready.png|link=Tutorials]]
[[Image:Checklistready.png|link=Aircraft Checklists]]

== Features ==
This model is a try and a WIP to get a realistic and complete simulation of a helicopter.

By using [[Nasal]]-scripting nearly all main systems have been simulated to a degree which wasn't available at this time on [[FlightGear]]'s helicopters. The [[flight dynamics model]] is custom made and though a lot of values could only be estimated, it should give an good impression on how the real one flies.
Systems and Procedures are based on the real Flight Manual so the helicopter can be started and shutdown by using the checklist.

The exterior model is detailed and accurate and originally based on accurate drawings, using high-resolution textures and the latest [[Howto: Aircraft Reflection Shader|Reflect-Bump-Spec-Shader]].

The mainrotor is detailed and animated including blade-flex-bend.

[[Livery over MP|Livery-over-mp]] including dynamic configurable external stores like skibox, deployable emergency floats, FLIR's etc. which affects CoG, weight and drag.
[[File:EC130 MedFlight N130NE.jpg|thumb|280px|right|The "new" EMS variant of EC130-B4, as used by MedFlight, Ohio, USA]]

=== Goals ===

* Fully usable cockpit with controls
* Complete startup procedure
* system failures and engine fire

=== Issues ===
See latest version in the [https://gitorious.org/ec130/ec130/source/381894383a2461b137721edfcb1b846edfb1de6a: hangar at gitorious]

* GTX328 and GNS430 only dummies
* bad autorotation behavior?? at high speed above 110 ktn
* Nasal error with Mouse handling of Twist Grip, but works
* Nasal error after crash
* GSDI (is not switched if only livery is changed) (FG 3.0 only, fixed in development version)
* Texture of N130NE (Medflight) is too large (4096x2048px), may cause ressource problems if used/switched (Rembrandt) (FG 3.0 only, fixed in development version)

== Pilot Flight Manual ==
=== Panel Overview ===

The FlightGear model of the EC130 B4 features the standard panel delivered ex works without any additional customer whishes.

Some caution lights on the panel itself like the one for the Landinglight aren't working yet, and the GTX328 and GNS430 are currently only dummies. Also the ETL on the central panel isn't working yet. Apart from that it is a fully working helicopter cockpit.

[[File:EC130B4Panel wiki.jpg|800px|Panel of the EC130 B4 showing all the instruments]]
=== Limitations ===
'''Type of Operation:'''
Helicopter is approved to operate Day and Night VFR only.

'''The following is not allowed:'''
* Aerobatics maneuvers
* in flight engine power reduction except for engine failure trainings and other emergency procedure trainings

'''Occupants'''

Minimum flight crew:..................................................................................1 pilot (left seated)

Maximum number of occupants:...................................................................7- 8 passengers

'''Weight and Balance Limitations'''

Minimum weight:.........................................................................................3307lbs (1500kg)

Maximum weight:........................................................................................5350lbs (2427kg)

'''Airspeed limitations'''

VNE Power on:...........................................................................................................155 ktn

VNE Power off:...........................................................................................................125 ktn

'''Altitude Limitations'''

Maximum operating flight altitude:...............................................................23000ft (7000m)

'''Main rotor Limits'''

<170 rpm:............................................................................................ rotor brake operation

320 rpm.....................................................................................minimum rotor rpm power off

320- 375 rpm..................................................................................................Caution Range

375-405 rpm....................................................................................normal Operating Range

405-430 rpm...................................................................................................Caution Range

430 rpm …...............................................................................maximum rotor rpm power off

'''Low Rotor rpm aural warning < 360 rpm ''' (available in Git version)

'''High Rotor rpm aural warning > 410 rpm ''' (available in Git version)

=== Warning Panel ===
Still uncompleted and especially failures indicated on the panel keeps mostly without any follow-up.
Here some important warnings:
* '''ENG P''' lights up: low Oil pressure - check gauge
* '''TWT GRIP''' lights up: twist grip not in flight position- engine idles. Drag mouse up until you get 100% and the light goes off
(currently not yet supported on Mac...) New: in Git version Twist Grip on collective is animated
* '''MGB P''' lights up: Main gear box oil pressure- check gauge - land as soon as possible
* '''FUEL''' lights up: low fuel - approx. 15min of flight time remain
* '''FUEL P''' lights up: fuel pressure- switch on Boost pump

== Updates as of FG 3.0 Version ==
[[File:EC130 Grand Canyon Helicopters.jpg|thumb|New Livery of Grand Canyon Helicopters]]
[[File:EC130-B4 Blue Hawaiian at coast of Kalaupapa.jpg|thumb|New Livery of Blue Hawaiian Helicopters]]
[[File:EC130 MedFlight N130NE.jpg|thumb|The EMS variant of EC130-B4, used by MedFlight, Ohio, USA]]
[[File:EC130-B4 MAC rescue.jpg|thumb|New Livery of MAC rescue (South Australia)]]
[[File:EC130-B4 ZS-HOY.jpg|thumb|New Livery of ZS-HOY Starlite Helicopters (South Africa)]]
[[File:EC130-B4 F-GOLH Geneva.jpg|thumb|New Livery of beautiful F-GOLH]]
[[File:EC130 Mainrotor front.png|thumb|Closeup of EC130 Mainrotor, fully animated in all details]]
[[File:EC130-B4 MedFlight using SX-16 Nightsun.jpg|thumb|EC130 Helicopter using the SX-16 Nightsun searchlight]]

The [[Eurocopter EC130 B4]] helicopter is on short final for a new major upgrade.
The existing model, which already had been of very high quality, has been refined in various aspects with lots of effort by '''mhab'''. The outside model has been enriched to a degree which should justify a '''''5*''''' rating and the overall status of the aircraft improves to "'''''production'''''".

The '''Rotorhead''' has been brought to a new level of detail, a full detailed '''Fenestron''' was added and animations were introduced to all moving parts.

'''Cockpit''' was enriched for Pilot/Copilot controls, seats are textured now and a variable cabin configuration allows to set up 5 or 6 seats or an '''Emergency Medical Services (EMS) variant''' with 4 seats and a stretcher.

'''New Liveries:'''
* '''N155GC''' of '''Grand Canyon Helicopters''', colorful painting in red/gold, 6 seats
* '''N11QC''' of '''Blue Hawaiian Helicopters''', 6 seats
* '''N130NE''' of ''' MedFlight''' based in Ohio, EMS rescue configuration, 4 seats
* '''VH-OSA''' of '''MAC rescue''' based in South Australia, EMS configuration, 4 seats
* '''F-GOLH''' a beautiful new livery of a private french model for those who want to travel in style
* '''ZS-HOY''' of '''Starlite Helicopters''' based in South Africa, variation of F-GOLH, 6 seats

A lot of '''equipment''' (most of which was there already but hidden) can now be used, including a full blown '''SX16-Nightsun searchlight'''.

All of this has been brought together in a fully integrated configuration dialog which allows to set-up livery, fuel, extra views, weights, cabin setup and equipment.

Extra gimmics include a fully animated pilot, glass reflection on windows and front shield and variable rotor wakes depending on the strength of the downwash.

<gallery>
File:EC130 Fenestron.jpg|A closeup of the full detailed fenestron
File:EC130 snowshoes hook.jpg|EC130 fitted with snowshoes and hook
File:EC130 pilot.jpg|EC130 pilot controls
File:EC130 stretcher.png|EC130 cabin configuration (EMS) with stretcher
File:EC130 luggage door back.jpg|EC130 luggage door
File:EC130 Pilot window.jpg|Even the pilot window can be opened now
File:EC130B4Samedan.png|EC130B4 at Samedan/ Switzerland
File:EC130B4 Snow.jpg|EC130B4 above snowy landscape
File:Ec130B4 mountains.jpg|EC130B4 flying in the mountains
File:EC130-B4 F-GOLH Lake Geneva.jpg|F-GOLH landing in Lake Geneva with floats inflated
File:EC130-B4 Blue Hawaiian near ship.jpg|Blue Hawaiian Helicopter near Kalaupapa
</gallery>

'''Some of the most interesting changes:'''
* '''Flight Model''' tremendously improved (CoG and agility much more realistic) (fix by HHS)
* '''Mainrotor''' fully animated and adapted to original
* '''Fenestron''' fully designed and animated, incl. control rod
* '''Cockpit Controls''' added: Stick, Collective, Pedals, Co-Pilot Controls (optional)
* '''Compass (magn.)''' added (HHS)
* '''Doors''' movable
* '''Searchlight'''
* '''Snowshoes'''
* '''Hoist/Hook'''
* '''Checklists''' implemented with conditional display
* '''Pilot''': ''fully animated''
* '''Autostart/Autoshutdown''' enabled after 15 flights
* '''Rotor-Wakes''' off-low-medium-high cyclable
* '''Sound improved''' (doors moving, low/high rotor rpm, overspeed warning, and noise inside depends on open doors/window)

'''Configuration Dialogs and Help Screens:'''

<gallery>
File:EC130 Config new.jpg|EC130 fully integrated configuration dialog
File:EC130 Help.jpg|EC130 Help screen with all shortcuts and additional info
File:EC130 Config Help 2.jpg|EC130 Config Help with explanation of dependencies
File:EC130 Options.jpg|EC130 Simulation Options
</gallery>

== Helpful Usage Hints ==
As of FG 3.0 there are comfortable configuration and help dialogs, new checklists based on pilot handbook and after 15 flights Autostart/Autoshutdown possibility.

== Updates after FG 3.0 release ==
[[File:EC130-B4 Maverick.jpg|thumb|EC130-B4 of Maverick Helicopters (Grand Canyon) at LOWI]]
[[File:EC130-B4 Broward County Sheriff 2.jpg|thumb|EC130-B4 Broward County Sheriff in flight near Miami]]

Development continues after FG 3.0 release. If you are interested in the newest features see [https://gitorious.org/ec130/ec130/ '''Git development repository''']

'''What's new after FG 3.0'''

'''New Liveries:'''
* '''N812MH Maverick''' Helicopters (Grand Canyon)
* '''N156BC Sheriff''' Broward County Florida

<gallery>
File:EC130-B4 Broward County Sheriff.jpg|EC130-B4 of Broward County Sheriff (Florida)
File:EC130-B4 Maverick LOWI in summer.jpg|EC130-B4 of Maverick Helicopters (Grand Canyon) at LOWI airport
</gallery>

{{Eurocopter}}

[[Category:Helicopters]]

Understanding Rembrandt

2014-03-02T11:18:51Z

EmmanuelFrance: fps -> FPS

== Background ==
Many of us are wondering why Rembrandt is so slow for us, despite having fairly powerful computers.

== Objective ==
Try to better understand -and document- Rembrandt internals, so that we can better troubleshoot performance issues.

Ok, I just tried Rembrandt again (after spending 5 minutes reading the wiki article), and while my computer is much less powerful than yours, I am also getting roughly ~15 FPS at ksfo with the ufo - and looking at those OSG stats, there's a hell lot of stuff going on obviously, i.e. we have 10 different cameras 3 of them extremely busy (0,1 and 5)

The performance is actually decent, though ALS with all goodies maxed out gets 25 FPS for the same scene under Linux (there's the grass shader needing lots of noise calls for instance). I don't get a huge green bar.

The big hit comes when I try to see Las Vegas (with the Urban shader) - that drives me down to 3 FPS. Or when I try to activate filtering and switch it to 3 - then my framerate likewise dives down to 4.

So I remember how this went - the base performance of Rembrandt without shadows was actually pretty decent on my box under Windows, 30 FPS or so. Switching shadows on cost me some of that but was still flyable, but the shadows were flickering so much that I got a headache after 5 minutes, so I needed to switch the filtering to max. to be able to look at it - and that killed the framerate for good.

If this is something that we really want to investigate more closely, I guess it would be a good idea to read the "deferred rendering" paper that Fred linked to in the article - at least those parts describing the 3 cameras that seem really busy (geometry/shadows/lighting)

== Scene Complexity ==
Purely from a troubleshooting standpoint, I would like to know what kind of effect/impact we can expect from discarding vertices/triangles and quads from all three cameras (having 10 FPS even at night time seems very odd), i.e. if discarding those translate into any proportional/tangible performance gains

Actually, the base idea of deferred rendering is that it should be pretty insensitive to the amount of vertices you feed to it because it really has a minimal geometry shader (computationally cheaper than default even, it basically only notes where stuff is on the screen and stores the non-projected position in a buffer) and all the actual work of lighting etc. is done in the fragment pipelines. So I'd be very surprised if it responds at all to changes of the vertex load.

I sort of see this on my card - if I'm fragment-limited, it switches to synchronized framrates, I get either 25 or 30 or 60 FPS, but not 33 or 47. Completely different when the vertex shader jams, then I get to see arbitrary numbers. Which is a neat first-look diagnostics. Rembrandt is clearly fragment-dominated on my box.

The thing is, it only takes a few errors in the C++ code that could massively inflate the amount of primitives sent to effects/shaders. And Rembrandt is obviously not well understood now that Fred is not maintaininig it currently. So there might be some low-hanging fruits there, but I am not going to spend hours going through the code unless I see tangible results.

As far as I understand the wiki article, most stages are XML configurable, so we can probably customize things a bit there, or even disable certain cameras/stages - which would make sense to see if each camera's stage looks sane.

For starters, I would probably start up at night time above sea - i.e. "minimal startup profile" and see what Rembrandt is doing then in each stage.
The number of vertices etc. should be fairly minimal then, shouldn't it ?

ok, when going to zero-scenery places, I am getting rock-solid 60 FPS/25ms here (daytime), with Rembrandt running with aircraft shadows, even with maxed out settings.
Can we work with that ? What about you ?
I remember your "orbitview" (?) project where you placed a huge sphere into the scenery. Could this help us to do some troubleshooting, i.e. using Nasal to place a few models (and possibly light sources) and see what's having an impact ?

the other thing I noticed is that CPU load doesn't seem to decrease despite AGL/ASL attitude being too high to realistically cast shadows - would these be things that we could add to the effects/shaders to reduce rembrandt workload a bit ?

== Reducing Complexity ? ==

What would be involved in editing effects/shaders to simply discard 50% of all vertices ? I just want to see for myself if that's having an effect here or not ?

In a vertex shader it's fairly difficult to do. To effectively discard a vertex, you need to evaluate some criterion based on its coordinates/attributes and then if that criterion is true move it out of the view frustrum and return, so you run a 'minimal' set of operations.

The obvious thing to do if you want to test response to vertex numbers is to set visibility lower so that terrain is simply not showing up at the vertex shader at all in a controllable way. A theoretically elegant way if you can is to set random numbers as vertex attributes and to move the vertex out of the view frustrum if the random number is smaller than a threshold. But in passing attributes, you're of course changing the pipeline in a substantial way...

If you want to test scaling of fragment shaders, that's much easier to do - evaluate another criterion in the first line which is true half of the time (say whether you're in the right half of the screen, you can test against gl_FragCoord which is the fragment position on the screen) and then insert a discard; if you want to dump the fragment without computing anything.

== Profiling ==
I am going to check what the C++ runtime profile looks like in comparison to the classical renderer.

Okay, I left rembrandt running for 10 minutes with the profiler enabled: fgcommand("profiler-start") - for some reason, the profile showed that "osgParticles" were eating up /some/ resources despite being not enabled - I tried to explicitly disable them, but that would still not change anything, so I removed the corresponding subsystem from src/Main/fg_init.cxx, which gave me +8 FPS:
<syntaxhighlight lang="diff">
diff --git a/src/Main/fg_init.cxx b/src/Main/fg_init.cxx
index 86494da..04d6f42 100644
--- a/src/Main/fg_init.cxx
+++ b/src/Main/fg_init.cxx
@@ -635,9 +635,11 @@ void fgCreateSubsystems(bool duringReset) {
// Initialize the scenery management subsystem.
////////////////////////////////////////////////////////////////////

+#if 0
globals->get_scenery()->get_scene_graph()
->addChild(simgear::Particles::getCommonRoot());
simgear::GlobalParticleCallback::setSwitch(fgGetNode("/sim/rendering/particles", true));
+#endif

////////////////////////////////////////////////////////////////////
// Initialize the flight model subsystem.
@@ -1077,8 +1079,10 @@ void fgStartNewReset()

simgear::clearEffectCache();
simgear::SGModelLib::resetPropertyRoot();
-
+
+#if 0
simgear::GlobalParticleCallback::setSwitch(NULL);
+#endif

globals->resetPropertyRoot();
fgInitConfig(0, NULL, true);

</syntaxhighlight>

== Shadows at night time ==
Well, something seems a bit odd there, because rembrandt is doing shadows, right ? And when I switch to night time mode, I am still just getting 10-15 FPS and seeing similar subsystem/osg activity.

as far as I know it's doing shadows at night just as well. If you drive your ufo to a Rembrandt-defined light source, I think it will cast a shadow also at night. I don't think the shadow part is off just because the sun is down.

The conceptual beauty of shadows in Rembrandt is that they're not faked, there's actually a physics computation going on where light in the scene reaches and where it doesn't. The downside is that unless there's a huge amount of filtering going on, that computation is suffering from numerical accuracy so much that it flickers all over the place.

the thing about rembrandt & light sources is true, I remember seeing screen shots - but I cannot imagine that the amount of computations for a handful of airports light should be equal to have a "central" light source illuminating everything (aka the sun) ?

Basically, it seems there's no "LOD for shadows" taking place, i.e. computations are heavy/complex despite having any light souces in your vicinity that could have an effect realistically. I would have expected that the corresponding shaders/effects specifically look for light source so that the computations kick in, but otherwise don't - unless, rembrandt is even doin moonlight shadow ?

== Zero Scenery Tests ==
Using '''--aircraft=ufo - --enable-rembrandt --prop:/sim/rendering/shadows/map-size=8192 --prop:/sim/rendering/shadows/num-cascades=4'''
I can even get way beyond 60 FPS when there's not scenery to be displayed, it would be interesting to check what Fred did there, i.e. if there are heuristics in place to recognize this ? We would probably want to add a few static models to the scenery and see what the performance impact is like.

I think through roughly a dozen different test cases like these, one could incrementally understand rembrandt and its stages - obviously, one would now need to edit some of the XML files and maybe some effects/shaders to see how things are affected

Santos-Dumont 14-bis

2014-03-02T11:14:19Z

EmmanuelFrance:

{{Infobox Aircraft
|image = 14bis.jpg
|name = 14-bis
|type =
|livery =
|fdm = YASim
|status =
|authors = Emmanuel Baranger
|fgname = 14bis
|download = http://helijah.free.fr/flightgear/hangar.htm
}}

== Information ==
The 14-bis (Quatorze-bis), also known as {{lang|fr|Oiseau de proie}} ("bird of prey" in French), was a pioneer era canard biplane designed and built by Brazilian engineer Alberto Santos-Dumont. On 23 October 1906, in Paris, France, it performed the first officially witnessed unaided takeoff and flight by a heavier-than-air aircraft. It was powered by an Antoinette V-8 engine with a 2-blade propeller and won a French aviation prize. Controversy exists between supporters of the Wright Brothers and Santos Dumont about which aircraft, the 14-bis or [[Wright Flyer 1903|the 1903 Wright Flyer]] , was the first true airplane.
[[Wright Flyer 1903|The 1903 Wright Flyer]] used a launch rail and undercarriage skids. After 1903 the Wrights added a catapult to assist most takeoffs of their 1904 and 1905 airplanes. The Santos-Dumont 14-bis did not use a catapult and ran on wheels. The Fédération Aéronautique Internationale ("International Federation of Aeronautics"), founded in France in 1905 to "regulate the sport of flying", keeping track of aviation records and other aeronautical activities in the Western world, stated among its rules that an aircraft should be able to take off under its own power in order to qualify for a record. Therefore, some claim the 14-bis must be considered the first operational fixed-wing aircraft. Supporters of the Wright brothers emphasise that their aircraft made controlled, sustained, manoeuvring flights a few years before Santos Dumont made his first takeoff. What this means is that, if you really want to fly the first aircraft on FlightGear, you should try both the [[wright flyer 1903 | Wright Flyer]] and this plane.

== Real-life Specifications ==
General characteristics
* Crew: one pilot
* Length: 9.70 m (31 ft 10 in)
* Wingspan: 11.20 m (36 ft 9 in)
* Height: 3.40 m (11 ft 2 in)
* Wing area: 52 m² (560 ft²)
* Loaded weight: 300 kg (661 lb)
* Powerplant: 1 × Antoinette 8V V-8 piston engine, 37 kW (50 hp)
* Performance
* Maximum speed: 40 km/h (25 mph/21 kts)
* Range: more than 220 m (720 ft)demonstrated
* Wing loading: 5.7 kg/m² (1.2 lb/ft²)
* Power/mass: 0.12 kW/kg (0.075 hp/lb)

[[Category:Biplane aircraft]]
[[Category:Canard aircraft]]
[[Category:Experimental aircraft]]
[[Category:Propeller aircraft]]
[[Category:Pusher aircraft]]
[[Category:Single-engine aircraft]]

Airbus A330-200

2014-03-02T11:10:41Z

EmmanuelFrance: ->list

{{infobox Aircraft
|image = Airbus A330-200.png
|name = Airbus A330-200
|type = Airliner
|livery = JetStar, Virgin Australia, Strategic Airlines, Air Berlin, Airbus House
|liverydbid = 86
|authors = Sam Clancy, Omega Pilot
|fdm = YASim
|status = Under development
|fgname = a330-200
}}
The Airbus A330-200 is a shortened, longer-range variant of the [Airbus A330], which entered service in 1998. Typical range with 253 passengers in a three-class configuration is 13,400 km (7,200 nmi). The A330-200 is ten fuselage frames shorter than the original −300, with a length of 58.82 m (193 ft 0 in). In mid-2012, Airbus proposed another version of the −200 with the maximum gross weight increased by 2 t to 240 t. This version will have its range extended by 270 nmi and will carry 2.5 t more payload. It will see engine and aerodynamic improvements reducing its fuel burn by about 2%. It is planned to enter the service by mid-2015. In November 2012, it was announced that the gross weight is to be further increased to 242 t with the range extended by 350 mmi (over 238 t version).
As of January 2014, 588 of the −200s had been ordered, 524 of which had been delivered, with 517 aircraft in operation. The 2011 list price is $200.8 million. The −200 competes with the [[Boeing 767-300ER]] and to a lesser extent the 767-400ER as well as with new [[787 Dreamliner]]. The A330-200 is also available as an ultra-long-range corporate jet as the A330-200 Prestige.

==Real-life Specifications==

Dimensions
* Length (m) 59.0
* Wingspan (m) 60.3
* Height (m) 17.9
* Wing area (m2) 361.6
Weight
* Maximum take-off weight (kg) 230 000 - 233 000
* Maximum landing weight (kg) 182 000
* Operating empty weight (kg) 120 500
* Maximum zero fuel weight (kg) 170 000
* Maximum payload (kg) 49 500
* Standard fuel capacity (litres) 139 000
Performance
* Range with max payload (km) 12 100
* Cruise speed (km/h) 870
* Maximum operating altitude (m) 12 500
* Take-off field length (m) 2 220
* Landing field length (m) 1 750
Engines
* GE CF6-80E1A3,
* 2 x 72000 lb
* P&W PW4168A,
* 2 x 68000 lb
* R-R Trent 772,
* 2 x 71100 lb
Cabin Data
* Passengers (1-class) 406
* Passengers (2-class) 293
* Passengers (3-class) 253
* Cabin width (m) 5.28

{{Airbus}}

[[Category:Airliners]]

Bad graphics performance under KDE

2014-03-02T10:46:27Z

EmmanuelFrance:

{{infobox KB
|fgversion = All versions
}}

== Problem ==
When starting Flightgear under KDE, the graphics performance is very bad, i.e. low framerates, while running Flightgear in a different window manager shows better performance.

== Reason ==
It is likely that "compositing" is activated. KDE includes a large number of various effects which use OpenGL. This might degrade the performance of applications that use OpenGL heavily.

== Recommended Solution ==
For KDE 4.9+:

You can import a so called '''window rule''':

Save the following as '''''flightgear.kwinrule''''', then open KDE's '''System Settings''', go to '''Window Behaviour''', then '''Window Rules'''. From the right select '''import rule''', then navigate to where you saved '''''flightgear.kwinrule''''', select it then press '''Open'''. You will be returned to the '''Window Rules''' tab. Press '''Apply''' and then close the '''System Settings''' window.

Next time you start Flightgear (''or osgviewer for that matter'') kwin will block compositing as long as Flightgear is running, then restore compositing when you close Flightgear, regardless if you start Flightgear in windowed or fullscreen mode.

<syntaxhighlight lang="ini">
[Application settings for osgviewer]
Description=Application settings for osgviewer
blockcompositing=true
blockcompositingrule=2
types=4294967295
wmclass=osg osgviewer
wmclasscomplete=true
wmclassmatch=1
</syntaxhighlight>

== Solution for older KDE versions ==

Disable compositing permanently or temporarily in the KDE settings, via the assigned hotkey (normally Shift + Alt + F12) or via a script.

== Caveats ==
With compositing disabled, KDE desktop effects don't work anymore.

== Example ==
'''WARNING:''' This method is obsolete, and is only left here as a convenience for those using very old versions of KDE.

This example by i4dnf deactivates compositing, starts Flightgear and reactivates compositing after Flightgear ended.
<syntaxhighlight lang="bash">
#!/bin/sh
qdbus org.kde.kwin /KWin toggleCompositing && /usr/games/bin/fgfs $@ && qdbus org.kde.kwin /KWin toggleCompositing
</syntaxhighlight>

== See also / related ==
* [http://forum.flightgear.org/viewtopic.php?f=37&t=15390&p=152496#p152488 Forum post by i4dnf]

[[Category:Knowledge_Base|Graphics, bad performance, KDE]]

User talk:Gijs

2014-03-01T21:25:43Z

EmmanuelFrance: /* Template:Lang */ new section

{{Archives|[[/Archive 2008-2011|2008-2011]] [[/Archive 2012|2012]]}}

=="Talk:Eurocopter EC135" (Author request: Author blanked page)==

Did I miss something? Can't remember seen that...
Can you tell what it was about?
Cheers --[[User:HHS|HHS]] 12:24, 17 February 2013 (UTC)

: Hi,
: F-JJTH wrote " Heiko, is V1.0 full "Rembrandt compatible" ?" on the page but blanked it shortly thereafter. I think he found the answer already... So all I did was delete that blank page.
: [[User:Gijs|Gijs]] 16:08, 17 February 2013 (UTC)

==About the wiki..==
Hi Gijs, hope all is well. I was stopping by because I noticed the words "Please post only encyclopedic information that can be verified by external sources. Please maintain a neutral, unbiased point of view. " in the editor. Its really not right to say this, because the FlightGear wiki has to be a "primary source". The contributions are typically original writing, and it specifically includes opinions (such as reviews), as well as first-hand accounts. Thank you. [[User:Fg|Fg]] 20:19, 17 July 2013 (UTC)

The wiki is mostly a primary source, saying "Please post only encyclopedic information that can be verified by external sources. .. " makes no sense. Most of what is written here is orginal content, and it does not make sense to have this in the edit box. Also, I don't agree with many of the articles you have deleted. These are small issues in view of your large contributions to the project, and I want to thank you for those, but I must also bring up these issues. Thanks again. [[User:Fg|Fg]] ([[User talk:Fg|talk]]) 20:32, 28 October 2013 (UTC)
: Hi,
: You're right about the "external sources" statement. That was just a default from MediaWiki but is not very applicable to our wiki. I've removed it now. Thanks for notifying me!
: What is it that you don't agree with? Is it the airport articles? Those were not deleted yet, they were only marked for deletion. The notice mentioned why I think they should be deleted. Feel free to share your arguments that make you think they should be kept. As the template stated "Do not remove this tag until the discussion is closed.", so I've placed the templates back and am looking forward to your (argued) opinion.
: Cheers,
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 17:47, 31 October 2013 (UTC)
::Great, thanks for fixing that! Come to think of it "Please maintain a neutral, unbiased point of view." may also be unneeded, as we have sections for reviews (with opinions) of aircraft, etc. but I will leave that up to you. I will check out the articles for deletion again. Thank you. [[User:Fg|Fg]] ([[User talk:Fg|talk]]) 22:57, 4 December 2013 (UTC)

== Adding the village pump to the sidebar or not ==

I have been pondering adding the village pump to the sidebar. I would probably add it between Recent changes and Random page. I have read in a bit on the sidebar on the MediaWiki help pages, but before I actually do it I want to ask you about your opinion about doing that.

The biggest pros and cons as I see it is that anyone will find it so it will be used a bit more, but at the same time that those that will not even read a few sentences of text (including people not comfortably reading English) sometimes will go there for help on using the simulator itself instead of going to the forum.

So what do you think about it?

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 09:00, 5 January 2014 (UTC)

: Hi,
: how about creating a "Wiki" header that contains the "Recent changes" and "Help" links? It could then also have a link to the village pump. I don't think we should call it "Village pump" though, as probably no-one will guess that's a place to talk about the wiki ;-) Something like "Wiki discussions" or so is more descriptive...
: Cheers, [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:52, 5 January 2014 (UTC)

:: I have been thinking of changing the name of that page as well. "Village pump" is used on WikiMedia Commons, the Swedish Wikipedia (though translated) and probably a few other wikis so someone coming from one of those places would be at home with it, but not everyone are from those places.
:: I have in the past considered suggesting changing it into say "Editor lounge" or rather something aviation related, but for instance "Pilot lounge" would have been so horribly misleading. ;-)
:: A "Wiki" header will help organise the contents but might hide contents by default, but hopefully people are curious enough to spend a few seconds looking around.
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:19, 5 January 2014 (UTC)

== Template:Lang ==

Hi,

could you explain what {{tl|lang}} is supposed to do? It doesn't seem to do anything in the French changelog, does it? If you just want to display {{en}}, there's <code><nowiki>{{en}}</nowiki></code> that you can use ;-)

Cheers,
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:36, 1 March 2014 (UTC)
:Hi,
:It's for say (in HTML code) the lang of the text. It's for web accessibility (and for bots).
:See http://en.wikipedia.org/wiki/Template:Lang#Rationale and http://en.wikipedia.org/wiki/Web_accessibility
:--[[User:EmmanuelFrance|EmmanuelFrance]] ([[User talk:EmmanuelFrance|talk]]) 21:24, 1 March 2014 (UTC)

User talk:EmmanuelFrance

2014-03-01T21:24:42Z

EmmanuelFrance: response

== Template:Lang ==

Hi,

could you explain what {{tl|lang}} is supposed to do? It doesn't seem to do anything in the French changelog, does it? If you just want to display {{en}}, there's <code><nowiki>{{en}}</nowiki></code> that you can use ;-)

Cheers,
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:36, 1 March 2014 (UTC)
:Hi,
:It's for say (in HTML code) the lang of the text. It's for web accessibility (and for bots).
:See http://en.wikipedia.org/wiki/Template:Lang#Rationale and http://en.wikipedia.org/wiki/Web_accessibility
:--[[User:EmmanuelFrance|EmmanuelFrance]] ([[User talk:EmmanuelFrance|talk]]) 21:24, 1 March 2014 (UTC)

OpenRadarGuide

2014-03-01T19:29:55Z

EmmanuelFrance:

[[OpenRadar|Back to mainpage]]

=='''''Preface'''''==
[[OpenRadar]] is a prototype to support Flight-Simulator ATCs in their work on our airports.

Some words to our project targets:
* '''Realism:''' That means we show all the data a real lisve ATC would need. For instance we simulate a radar antenna and perform one position update per antenna rotation. But we don't have professional ATCs, neither do we have professional pilots contacting our ATCs. So we have to make some compromises...
* '''Usability:''' The application should be handy, behave consistently, and require almost no training. The ATC has other things to do than to fight with the application

We hope that we met your needs and are happy to get feedback!

'''Important:''' We support you with tooltip texts, that appear when you hover over an active area with your mouse. They shall remind you of possible interactions that you may have forgotten. Try pointing your mouse everywhere - maybe there is something available that you missed until now...
 
----
=='''''Prerequisites'''''==
===Internet===
Of course you need an uninterrupted Internet access to exchange data between You and your clients/targets. The requirements for that connection are not very high -- but they must be uninterrupted!

===Communication===
We urge you to always offer your services as well in typing (MPchat) as also in speaking (Radio).
You will soon discover, that using a Radio-application makes it much easier to communicate
*as well for you ''(who hopefully will control many pilots at the same time)''
*as also for the pilots ''(who need both hands to control their plane)''.
There may not be enough time for typing!

*'''MPchat''' is an integral part of FGFS and OpenRadar and needs no further installations. (ref.: http://wiki.flightgear.org/Howto:Multiplayer ) - so it is always available for communication between you and all pilots.
*A '''Radio''' is not directly integrated into OpenRadar but must be installed in addition. Right now there are 2 versions in use:
**'''FGcom''' is the more realistic Radio-operation with realistic frequencies for each function and a limited work-range based on frequency.
:::If FGCOM is not yet installed, you need to install a "standalone version of FGCom 3.0", which then can be controlled directely from within OpenRadar. For installation see http://wiki.flightgear.org/FGCom_3.0, item "3 FGCom standalone".
:*'''Mumble''' is an easier to handle application, that provides "named groups" that people with the same reason move/change into. Thus Mumble is not limited by range and much easier to use for defining by "groups" which people will communicate with each other.
:::If Mumble is not installed you may install it according to http://mumble.sourceforge.net/Installing_Mumble.
:::To activate it see http://mumble.sourceforge.net/Mumbleguide
:::The most used Mumble-server is "mumble.allfex.org"

=== Java V7 ===
Make sure you have installed at least Version 7 of Java. Verify and or Download the installation packages from: http://www.java.com/en/download/index.jsp

=== OpenRadar ===
For the currently available Prototype of OpenRadar see http://wagnerw.de/OpenRadar.zip. Extract the content of this ZIP to a place where it is easy to find. Make sure you have read and write permissions for that directory.
 
If you did already work with an OpenRadar installation you may want to
* RENAME your current OpenRadar-directory (i.e. to "OpenRadar-BU")
* then download and extract the new version into a newly created directory with the name of the old one (without the "-BU")
* now you can replace all data in the new "OpenRadar/data" directory with the ones in the "OpenRadar-BU/data"
** if you expect changes in the scenery etc. do not copy the the Airport (ICAO) directories
* delete the BU-version only after you are sure you verified that all your personal data were transferred, i.e. still accessible!

== '''''Startup''''' ==
Inside the downloaded OpenRadar base-directory you will find start-scripts. See
* for Windows: OpenRadar.bat
* for Linux: OpenRadar.sh
* for OSX: OpenRadar.jar
At Startup you will always be welcomed by the “OpenRadar – Welcome”. That window presents 3 TABs to define your preferences:
{|
|-
|[[File:OpenRadar - Welcome-Linux.png|thumb|Welcome ''(Linux)'']] || [[File:OpenRadar- Settings-linux.png|thumb|Settings tab ''(Linux)'']] || [[File:OpenRadar - Tweaks.png|thumb|Tweaks tab ''(Linux)'']]
|}
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start.
 
If this is the very first time you start OpenRadar, then you have to verify your “Settings” first, thus click onto the “Settings”-tab:

=== OpenRadar-Welcome - Settings ===
These settings are grouped into 3 parts:
===='''1) FGcom'''====
:OpenRadar can support up to 4 instances of FGcom in 2 ways:
:#It can start and control FgCom instances that operate in the background as sub-tasks of OpenRadar (except for OSX where FgCom must be run in a separate Terminal window)
:#or just control manually started FgCom-sessions.

:You select these modes of operation by the “'''FgComMode'''” selection:
 
:'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar
::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used:
::'''Path:''' Here you define where your FGcom is installed.
:::In the following some examples:

:::{| class="wikitable" style="text-align:center"
!type
!Windows
!Linux
!OSX
|-
|a standard installation || C:\Programs\FGcom ||/home/''YourName''/fgcom ||*)
|-
|on another disk || D:\FlighGear_2.6\FGcom || /media/''DiskName''/FGFS/fgcom ||*)
|-
|on a LAN-server || \\''ServerName''\Central\FGFS || /home/YourName//.gvfs/fgfs on nas-server/fgcom||*)
|}
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar'''

::'''Executable:''' Here you define the program-name that shall be started
:::*For Windows: "fgcom.exe" or "anyName.bat"
:::*for Linux: "fgcom" or "anyName.sh"
:::*OSX: ''again for OSX this doe not apply''
::'''Server:''' There are 2 FGcom-servers available as of today:
::*delta384.server4you.de ''(we do suggest this one)''
::*fgcom.flightgear.org
::'''Client:''' must always be “localhost”
::'''FGcom Ports:''' The here defined values are crucial for the operation because:
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !!
::*They also define how many “Radio Units” (COM0, COM1, etc.) are generated within OpenRadar
::Simply provide a coma separated list of UDP Ports to be used by FGcom. But be warned: More than two are hard to handle!
:::::e.g. 16661,16662
 
:'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port.
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.:
::*'''Client:''' localhost
::::If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s,
:::::e.g. "fgcom -Sdelta384.server4you.de -p16662 -i1 -o1 -s192.168.178.23" 
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)''
 
:'''c) OFF:''' No FGcom support
::That means that You do not want to work with FGcom during your ATC-session – thus you do not need to define any of the fields and there will not be defined any Radio (e.g. COM0) in OpenRadar. This mode is not suggested!

===='''2) FG Multiplayer'''====
:Here you find the server and connection port of FlightGears multiplayer server. It delivers the radar contact position informations and is used for chat. You won't have to change the settings, as long as the server won't change.
:In case you experience problems with the outside you may check and/or choose any "'''''Server'''''" that is listed in http://mpmap01.flightgear.org/mpstatus/: Look for a server nearest to your location that has a status of "OK" and shows the most "totals".
:'''''PLEASE NOTE:''''' The "'''''Client port'''''" is the port used by your computer to talk with that server. If you want to use FlightGears internal chat parallel to OpenRadar, you must use a different port than FlightGear. Because of that, the default port of OpenRadar is 5001 ''(in order to differentiate it to the 5000 used in FGFS)''.

===='''3) METAR'''====
:OpenRadar retrieves the weather information via METAR messages from a server in the INTERNET. This information is being displayed and used to calculate the usability of runways and the air speed of the radar contacts.
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source!

Please click on the verify button to have your settings checked prior to returning to the left/primary tab:

===Select Airport===
This is always the first window that you will see after starting OpenRadar.

But at first, the available airport list (e.g. EDDF, KOAK,..) in the center will be empty. So at first define a location:

In order to '''define a new work-location''' simply enter the airport code (ICAO) or a part of the name into the search field and hit “search”: The list below then shows the results found in the airport database delivered with OpenRadar. There may be found several, so click on the one wanted and then activate the button "Download Scenery". Be patient and watch the Info-Field at the bottom: This first download of the required scenery will take some time before you see a "Ready"!

'''If the airport wanted does already exist''', it will be shown in the big center-field, with an "(exists)" at the end.
Double click onto the one wanted (or select it with one click and then click onto start) and you are in the ATC seat.

== '''''Operating''''' ==
[[File:OpenRadar Prototype.png|thumb|270px|Oakland international used in new OpenRadar]]
'''Note: As of this version when the main screen starts in OSX it is completely minimized at the bottom left corner of the screen and you must expand this window.'''

The OpenRadar main screen is divided into three regions:
#Top left you see the big '''Radar Map''' showing the airport, its surrounding, the navaids and the radar targets.
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature.
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are
##'''Status Information'''
##'''COM-Radios''' ''(only if you have defined one or more)''
##'''Runway Manager''' to set up runways used
##the '''Flight Strip Manager''', where you can manage your radar targets.
Please notice in the following description the lightblue background at some items, indicating changes that may not yet be available in your version of the OpenRadar!

==== Radar Map ====
The radar map is the most complex part of OpenRadar, thus you have many options to zoom in on any area you are interested in. You can:
* set four functional zoom levels by clicking onto '''''GROUND, TOWER, APP and SECTOR.'''''
* zoom in and out using your mouse wheel ''(Mac: hold your right mousebutton pushed while moving over the radar-background in NorthWest respectively SouthEast)''
* adjust the map-center by dragging it with your mouse (click-hold left and drag)

* a double mouse-click onto the scope will move that point into the center of the scope
* a double right mouse-click will center the scope back to your location

You may assign any current settings to any of the 4 zoom levels (GROUND, TOWER, APP and SECTOR) by a right mouse-click onto the wanted level''
 
[[File:OpenRadar-Approach.png|thumb|right|250px|A typical tower operation]]
The '''''Radar-targets'''''
*do have a label attached with the following informations
:{| class="wikitable" style="text-align:center"
|-
|UID||heading direction
|-
|Flight Level||Airspeed
|}
*and are displayed in 5 different colors:
::''(See also the chapter "Flight Strip Manager")''
:{| class="wikitable"
|-
|align="center"|white||always the currently selected target, it's UID is also shown in the MPchat inputline (e.g. see "D-Leon" who just is getting his "clear to land")
|-
|align="middle"|blue||targets who's Flight-Stripe is placed to the left (e.g. see "Side" (just started) and "D-AHGM" just going to intercept the ILS: These 2 PLUS the white "D-LEON" are actively controlled right then!)
|-
|align="center"|yellow||targets who's Flight-Stripe is placed in the middle (e.g. could be assigned to "jomo2" as an indication that we wait for him to "wake up" soon - because then he may become a danger to others when taxiing uncontrolled)
|-
|align="center"|green||targets who's Flight-Stripe is placed to the right (e.g. see "jomo2" just parking - not actively controlled right now)
|-
|align="center"|gray||a neglected target or one for which there were no refresh data received from the MPserver for some time. In those cases the aircraft-type will be replaced by either "neglected" or by the time that elapsed since the last MPserver-update.
|}

[[File:OpenRadar-GND.png|thumb|right|250px|A GND layout with active PPN's]]
The radar map has so many details to display, that it is impossible to display all at once. Because of that we display details depending on the zoom level. For instance we hide Fixes and/or Runway Numbers etc. at a certain level of zoom. Thus OpenRadar features an adaptive detail level. In addition you can hide types of data by the following buttons:
{| class="wikitable"
|-
| '''''FIX''''' || Show/NoShow FIX's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''NDB''''' || Show/NoShow NDB's (they will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''VOR''''' || Show/NoShow VOR's
|-
| '''''APT''''' || Show/NoShow Airports, inclusive their groundlayout (You may double-click onto a wanted airport and zoom in to see the layout)
|-
| '''''CIRC''''' || Show/NoShow circles at distinct distances around your present location. The distance between the circles shown depends on the chosen zoom-factor!
|-
| '''''GSH''''' || Show/NoShow Glide-Slope-Heights along the centerline of the runway for landings. They will automatically be set "NoShow" above distinct scale-settings!)
|-
| '''''PPN''''' || Show/NoShow the "Park Position Numbers", ''those may not yet be available on all airports!''. The PPNs will automatically be set "NoShow" above distinct scale-settings!)
|- style="background:lightblue"
| '''''StP''''' || Show/NoShow the "Selected (target) To Pointer" ''(doggy)'', an attachment to the mousepointer, showing some data about the relation of the selected target to the location of the mouse-pointer (similar to line 3 in the "Status Informations", see above)
|}

The "Runway Manager" (on the right side of the screen) allows you to define which runway(s) should be used for landing and/or starting. This status is shown with little green/red dots at the runway end. See in the picture "A typical tower operation" above:
*25L, 25R, and 18 are active (see the green and red dots at the ends)
*25L has in addition the blue approach center line and funnel, i.e. it is assigned for landings. This center line is drawn out for 100mi, helping you to align the arriving airplanes with the runway. In addition there is shown some kind of a funnel in a definable distance that may help you to align the planes coming via a base-leg for landing.

==== MPchat area ====
[[File:OpenRadar-MPchat.png|thumb|right|270px|The MPchat area]]
This area allows you to enter chat messages, view the chat history and filter it.
 
In the '''''entry-line''''' atop you define your messages to any radar-target by:
*Manually typing a message:
**A '''''left''''' mouse-click onto a Flight-Stripe or onto a Radar-Target will place the Target-UID at the beginning of the entry-line
**Then you may type or copy/past anything behind that - and send it out by ENTER
*Generate a standard message:
**A '''''right''''' mouse-click onto a Flight-Stripe or onto a Radar-Target ''(or the TAB-key if the target is already active)'' will open a list with the available messages - select one with a left mouse-click
**That will place the message into the entry-line - you may now review/edit it and then send it out by ENTER
*OpenRadar will always set the ATC-name (as it appears on the very top of the service area - see the following chapter) in front of the message.

Below that entry-line is the '''''scrollable list''''' of exchanged MPchat-messages. In that list the messages related to the selected target are colored cyan. With the button "'''''SEL'''''" you set a filter to show only the messages related to the selected target. This filter will be reset as soon as you select another target - or by clicking onto "'''''ALL'''''".

You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care!

==== Service Area ====
This column at the right side of the screen is for setting up the base-data for the operation, display needed data for traffic-guidance, and provide tools for guiding the pilots.

=====Status Informations=====
[[File:OpenRadar-Status_2.png|thumb|right|200px|The general Status Informations]]

This area shows in 4 lines the most used status-informations:
<ol><li>A text box that allows you to see and change your MP-callsign. So you can quickly change it, if a second ATC takes another role at the same airport (TW/APP/GND/RADAR, etc). At the right of it is placed a clock with the UTC-time. Because you probably will always have international guests you should refer to that modern "Coordinated Universal Time" (replacing nowadays the formerly used "Greenwich Mean Time" (GMT))
</li><li>In the second line you see the ICAO (the international Code for airports) and the long name of your airport. In addition you see on the right the currently selected radar contact (e.g. "jomo").
</li><li>The third line lets you predict several values for that "radar contact" (e.g. "jomo"). Whenever you place your mousepointer somewhere on the Radar Map, the third line will give you several informations about that target:
*StP = "Selection to Pointer": That is the compass direction between the target and the mousepointer, in both ways (TO/FROM)
*Miles: The distance between the target and the mouspointer.
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. (For help ref to http://wiki.flightgear.org/METAR#METAR). Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic...
</li></ol>

====='''COM-Radios'''=====
[[File:OpenRadar-COM_2.png|thumb|right|200px|The COM-Setting (that can be none or up to 4)]]
According to the amount of FGcom-Ports you defined during setup (compare chapter "3.1.1 FGcom") you find here as many COM-Units (COM0 to max COM3). Each of them has a PopUp-List of Radio-frequencies available for the airport you are located on. You may
*choose a frequency out of the list by clicking onto the arrow at the right of the input-field
*or empty the field by a right mouseclick and enter any other frequency wanted.
At the right of that field you find a "Push To Talk" (PTT) button that you can operate by mouseclick -- or you can use the shortcuts given in the following table.
:{| class="wikitable" style="text-align:center"
!COMx
!left on keyboard
!right on keyboard
|-
|COM0||Ctrl||NumOff+Num0
|-
|COM1||SHIFT||NumOff+Num1
|-
|COM2|| ||NumOff+Num2
|-
|COM3|| ||NumOff+Num7
|}
Please watch the color change of the PTT buttons to know, when you can speak.

In case you operate the FGcom in the "'''''controlled by OpenRadar'''''" mode (compare the "FGComMode" in chapter "Startup"), then
*the radio label turns to red when FGcom is unable to establish a connection on this frequency. (Remember: OpenRadar has more frequencies available than FGcom knows of!!)
*you have an additional "'''''Restart'''''"-button: In case the communication becomes chopped or interrupted, you may click here to restart the FGCOM-program.

====='''Runway Settings'''=====
[[File:OpenRadar-Runways_2.png|thumb|right|200px|The Runway Manager]]
[[File:OpenRadar-Runway-Settings.png|thumb|right|200px|The Runway Manager Settings]]
Here you define the major variables for your airport operations: That are the assignments of the runways! For this purpose OpenRadar gives you a lot of precalculated and or default values to support your decisions findings and/or informations pilots may ask you about. See e.g. the pictures on the right:
*From top to bottom OpenRadar lists all runways available for that airport. For each runway you may define unique operating/display values. For these values see the picture "OpenRadar-Runway-Settings" below, e.g. see the 07C ''(you open that by a right mouseclick onto the runway-name (07C))'':
**In the header line you see left the now chosen runway to be edited, and at the left a button "'''''Copy to All'''''". With this switch you can copy the settings you make here to all the other runways - so e.g. for EDDF with its 8 settings you can save a lot! Only the values will be changed - all the selection-markers will remain as are in each unique setting table! These settings will then be saved separately for each unique airport in you private settings.
**With "'''''Main switches'''''" you define which functions may be available for that runway. Usually you can define for each runway as well a "Starting" as also a "Landing" function. In the given example for EDDF there is a complication: Per Law you are forbidden
:::to use runway 36 at all --> thus disable both lines: All data for that runway disappear
:::to use runway 18 for "Landing" only --> thus disable only "Landing": Just the Land-Option disappears
:::''(How do you know those details? Well, as a good ATC you prepare yourself by reading the official airport data (or look for something like e.g. http://en.wikipedia.org/wiki/Frankfurt_Airport, see on that page in the right column)''.
:*The "'''''Extended center line'''''" is the line you see in the above picture ''"A typical tower operation"'' at the right. If you want that line you may define how long it should be. Some people do not want it reaching over the whole screen. We suggest to limit it to the MPserver-range of 100 mi. It will only be visible for the runways defined for "Landing"!
:*The "'''''Distance markers'''''" are measurement markers on that "Extended center line". Here you define from were to were you want to have such markers ''(they may restrain your eyes if you use them all over!)''.
:*"'''''Vectoring and base leg'''''" define that funnel that you also see in the above picture ''"A typical tower operation"''. Also this will be shown only for the "Landing" runways.
:One tip to the handling of the "Landing" runways: Those are always shown in the "ATIS" message. If you define two (or even more) - in that "ATIS" message appear all those with the ILS data, etc.! So if you use mainly one we suggest to define only one - and activate more if you actually assign an additional one. Otherwise the pilots may become confused of that many informations and you yourself may have problems to differentiate which line the target should follow!

*From left to right you see the following informations for each runway (if available):
:*The runway-name
:*Check-boxes to define if that runway is used at all, may be just for landings or just for starts or for both. The program prevents you from assigning a runway in both directions (e.g. 25R and 07L)
:*A graphical display of the cross winds and and gusts: They are green from 0-5kn, orange 5-10kn and red above. When there are significant gusts that color-bar is divided into two. Typically the gusts then will be represented by the longer bar!
:*Above that bar you see the fractions of head- and crosswind. You may use especially the crosswind-fraction to warn pilots if those are => 10 kn! (Remember: You find the normal wind values in the METAR-data further up in the Status Informations)
:*To the right follows
::*in the upper line the exact runway heading (as needed for older type autopilots)
::*in the lower line the length and width of the runway in feet!
:*Then follow the ILS informations, if ILS is available for that runway. The data shown are: the ILS-beacon-name, the frequency, the glideslope, and the altitude at the threshold.

====='''Flight Strip Manager'''=====
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]]
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are:
:{| class="wikitable" style="text-align:center"
|-
|Target UID||Aircraft Type||colspan="2"|direction to it from ATC
|-
|distance to it||IAS+GND speed||Altitude (FL)||current heading
|}
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These additional lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd line examples:

"ILS VOR FGC NRW || GED MTR"
 This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.

"ILS VOR FGC NRW || KJFK 280° f510"
 This pilot also can use ILS, VOR, FGcom, NRW || and will depart to JFK on a straight course of 280° on FL510"

You are absolutely free to define your own codes and whatever. To do so
*enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click ''(Mac: Alt + right mouse-click)'' while pressing onto the stripe
*add additional lines by Strg+ENTER (remember: Not more than 2, please!)
*Always exit that Editor with the ENTER-key in order to transfer the data to the stripe!
*At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target.

You can '''''manipulate the listing''''' of the flight strips:
* New radar-targets will always appear at the end of the list on the right side
* You can move the stripes in vertical order by drag and drop
* You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes ''(you may double-click to move directly from one side to the other)''
* with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages!
* The radar-targets will change their color according to the horizontal position of their stripe:
** the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized!
** the radar-targets for stripes in the center will be '''yellow'''
** the radar-targets for stripes at the left side will be '''cyan'''
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones!

You cannot change these combinations of color and position -- but you might define your own definition of what the positions mean! We suggest the following:
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.)
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled!
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!)
Again: That is a proposal - you can define your on assignments!

You can apply the following mouse-actions onto the stripes as well as onto the radar-targets:
*a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition
**its listed messages in the MPchat-list become colored cyan
**and the "doggy" at the mouse-pointer displays data about the relation between that target and the mouse-pointer
*a '''''double left''''' mouse-click helps you to find the target by highlighting the target on the scope. It also changes the radar-range to show both: The Target and your location. The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center!
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above)
*a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views.

=='''''Flight-Plan & Flight-Management'''''==
There is now a Flight-Plan feature inside OpenRadar. With this you can define internal Flight-Plans that get distributed to all ATC's within the range of the target, as it moves from area to area. Thus every ATC can decide on first sight whether that flight affects his duties and how. This Flight-Plan can only be generated and/or edited by the ATC that is actually controlling the target at the given time.
In future there will be added a common interface to existing Flight-Plan-Programs, so that the pilot himself can pre-define his flights – and OpenRadar takes over that data automatically in its internal Flight-Plan.

==='''Define/Edit a Flight-Plan:'''===
[[File:OpenRadar-Flightplanning.png|thumb|270px|The Flightplanning feature input sheet for OpenRadar]]

You open the Flight-Plan for a target by clicking with the “center mouse-button”
*onto the Flight-Strip of the target
*or the target on the radar-screen
You can also open the "active" target by the '''^'''-key

'''Controlling the ownership:''' 
You can only define/edit a Flight-Plan for a target that is under your Control. i.e. the field
“Controlled/Uncontrolled" must state “controlled by me”!

* If it is “'''uncontrolled'''” click onto “control” and that field will indicate your “ownership” and avoid others to change

*If it is “'''Controlled by …..'''” you must wait till the ATC controlling it now will
**either remove his “ownership” by
***clicking onto “Handover to” and selecting
****another ATC for takeover
****or the “blank” for just removing his control.
***or clicking onto the button “UnControl”
**or the target gets outside the range of the indicated “Owner”. In that case the Flight-Plan will be set to “Uncontrolled” automatically
**or you send the controlling ATC a mail asking him to release the target

*If it shows “'''Controlled by me'''” you can release the target
**by clicking onto “Handover to” and selecting another ATC (or “blank”) for takeover
**or you grab the Flight-Strip with the mouse and move it to the left into the radar-scope and select an ATC (or “blank”)
**or you move the Flight-Strip all the way to the right – that will just remove your ownership

'''Mandatory fields of the OR-Flight-Plan:'''
*'''Contact''' is the FGFS-UID of the target (will be set automatically)
*'''Aircraft''' is the model-code of the target (will be set automatically)
*'''Departure''' is the departure Airport (will be set automatically to your airport if on GND - or manual)
*'''Destination''' needs the IATA-code of the destination (e.g. EDDF for Frankfurt)
*'''ETA''' is the “Estimated Time of Arrival” - that is automatically calculated based on the given aircraft type, altitude (CrsgAlt) and speed (Crsg.TAS) (You might override it if you know/want it more realistic)

'''Optional fields of the OR-Flight-Plan:'''
*'''native language''' is per default “en” for English. If you choose another language, then all your selected MPchat advises to that target will be sent in English and then repeated in that chosen “native language”
*'''FgCom''' indicates that target can use Radio (FGCom or Mumble)
*'''Squawk''' shows the Squake-Code you assigned to the target
*'''Assgnd RWY''' shows the runway assigned to that target, as well for landing as for starting. You assign the runway either by the PullDown or by DoubleClick onto the runway number in the “Runway Settings”
*'''Route''' defines the SID, STAR, etc. assigned
*'''Altitude''' as assigned by ATC from time to time (not the planned/constant "Crsg.Alt"! (compare below))
*'''Code''' will be used in future when given by a more professional Flight-Planning system
*'''IFR/VFR''' may be defined by the PullDown
*'''Route''' can be used to document a preplanned route
*'''Crsg.Alt.:''' Define the planned cruising altitude en route (usually in FL)
*'''Crsg.TAS.:''' Define the planned TAS en route (usually as GND-speed)
*'''Alt.Airports''' can be defined as a needed deviation in case of bad weather etc. at the planned airport
*'''Comments''' here you enter comments that will be kept together with the Flight-Plan - and are visible to all ATCs en-route
*'''Private notes''' are comments that remain with the ATC making these (stored then in the local file OpenRadar/settings/atcComments.xml). The will always be re-inserted whenever that target is visible to the unique ATC, independent of if he is the “active controller” or not.

==='''Flight-management:'''===
Open the wanted Flight-Plan
* by a center-mouse-click onto the radar-target or the FlightStrip
* you can also use the '''^'''-key to open the FlightPlan of the active target.
Then continue as described in the following scenarios:
''(In these scenarios only the "Simulation" labels are shown - to see all possibilities see the summary at the end)''

'''''1. A target appears on your airport'''''
:[[File:OpenRadar-Flightplanning-lables-1.png|500px]]
:There are no data filled in yet into the flight-plan from any ATC, and there is no ATC assigned yet. Thus
:*the text in the tag-color is “green” - i.e. you did not yet take controll
:*the flight-strip background color is light green, in order to indicate that you did not yet do anything with it - i.e. it asks for attention from you to decide what to do with it
:*a simple mouse-click or any other action will remove the green background.

'''''2. You define a new Flight Plan'''''
*Pull the Flight-stripe all the way to the left (mouse-drag or double click left of the FlightStrip). ''(If there is still another ATC the owner, then you cannot take over prior that the other ATC released or transferred that target!)''
*'''Generate the Flight-Plan:'''
:Compare the Informations given in the target-label and the stripe:
::''e.g. when there is defined (just below the scope) in “map → data mode → Simulation (Transponder enabled)”''
:[[File:OpenRadar-Flightplanning-lables-2.png|400px]]
::{| class="wikitable"
|-
|jomo
|the pilot FGFS-UID
|-
|160°
|the current heading (now on ramp!)
|-
|HeadSet-sign
|that pilot uses radio (FGCom or Mumble)
|-
|CONC
|the FGFS-model is the Concorde
|-
|KJFK
|is the planned destination
|-
|260°
|is the straight heading EDDF (departure) to KJFK (destination)
|-
|BIBTI
|is the SID planned for departure (on arrival here would be the STAR)
|-
|RW25C
|is the runway assigned for departure (or for arrival)
|-
|0400*
|is the current altitude (on GND in EDDF!)
|-
|00
|is the speed (still parking!)
|}
 
*'''Departing:'''
**GND will use the data as shown above, to bring the plane to the HoldingPoint
**TWR will take over
**The runway-assignment will be removed automatically after Take-Off
 
*'''Transfer Control to next ATC (or blank) '''
::[[File:OpenRadar-Flightplanning-lables-3.png|500px]]
*grab-move the FlightStrip left into the Scope and select the next ATC ''(or open the Flight-plan and select at “Handover to:”)''.
*if there is no “next ATC” available select the blank entry – the target is then free to be picked by another ATC en-route.
*the FlightStrip will indicate the pending transfer by showing
:::“current ATC” => “next ATC”
:The FlightStrip on the console of the “next ATC” will change the background-color to yellow – to grab his attention!
*as soon as the “next ATC” has taken over the Flight-Strip will turn back to normal – indicating the “next ATC” is active -- and you cannot do any more changes!

'''''3. A target appears in your airspace:'''''
*take over the control if there is no ATC assigned or the FlightStrip indicates that the current ATC wants you to take over the control ''(i.e. move the Flight-Strip all the way to the left)''
*if the target has no owner yet and is just crossing your airspace and tells you his destination, you may open the FlightPlan and insert that destination so that all the other ATCs know about it.
*If the target lands on your airport:
**assign a STAR and/or RW
**the needed GND-traffic (Taxiways, Parkinglots, Gates, etc) is not part of the FlightPlan. ''(But you can always add your remarks for your own usage).''

'''''4. A ATC forgets to “reassign” or “free” a target:'''''
*The ownership will automatically be removed as soon as the targets gets out of the rang of that ATC (~100mi). After that any other ATC may take over.
 
==='''Summery of Flight-Strips and Target-Tags'''===
Depending on what you selected in "map" -> "data mode" ''(see the menu above the MPchat entry-line, at the very left)'' the Radar labels may look different. See the summary in the following table:
{| class="wikitable"
|+
!width="30%"|Status
!width="30%"|FlightStrip
!width="20%"|Traditional
(no transponder interaction)
!width="20%"|Simulation
(Transponder enabled)
!width="20%"|Pure Simulation
(Transponder enforced)
|-
|'''''Target appears on EDDF airport:'''''
no ATC and no Flight-Data are assigned yet
|align="center"|[[File:OpenRadar-target-lables-10.png]]
|align="center"|[[File:OpenRadar-target-lables-11.png]]
|align="center"|[[File:OpenRadar-target-lables-12.png]]
|align="center"|[[File:OpenRadar-target-lables-13.png]]
|-
|'''''jomoATC inputs a Flightplan:'''''
from EDDF to KJFK via SID BIBTI straight hdg EDDF -> KJFK 260° on Cruise Alt. FL250
Rw for TakeOff 25C
|align="center"|[[File:OpenRadar-target-lables-20.png]]
|align="center"|[[File:OpenRadar-target-lables-21.png]]
|align="center"|[[File:OpenRadar-target-lables-22.png]]
|align="center"|[[File:OpenRadar-target-lables-23.png]]
|-
|'''''After TakeOff:'''''
notice that RW25C is canceled
|align="center"|[[File:OpenRadar-target-lables-30.png]]
|align="center"|[[File:OpenRadar-target-lables-31.png]]
|align="center"|[[File:OpenRadar-target-lables-32.png]]
|align="center"|[[File:OpenRadar-target-lables-33.png]]
|}
'''''EDDF forwards target to EDDK:'''''
{| class="wikitable"
|-
|'''in EDDK''' it appears with a yellow background to enforce attantion
after ATC-EDDK has taken over, that yellow will disappear
and the "lastATC ==> "newATC" will be replaced by "currentATC"
and the "private Notes" will be replaced with those of the newATC (if he has some)
|align="center"|[[File:OpenRadar-target-lables-41.png]]
|-
|'''in EDDF''' that private notes remain,
but the new ATC is shown, indicating “no changes any more accepted from EDDF!”
|align="center"|[[File:OpenRadar-target-lables-42.png]]
|align="center"|[[File:OpenRadar-target-lables-43.png]]
|}

== '''''Useful Features''''' ==
'''Radar Map'''
* On contact
:* '''left''' click '''selects''' and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click opens the '''ATC messages''' selection box

* '''left double''' click on map to '''center''' it '''on airport''' (return to airport)
* middle click on zoom level defines the current view as new center and zoom setting (stored in a file)
* a click on the texts, on the lower left, toggle display of FIX, NDB, VOR,...

'''Flight Strip Area'''
* On flight strip
:* '''left''' click '''selects''' the contact and sets cursor into the chat input field
:* '''middle''' click opens the radar '''contact settings''' (ATC note and native language)
:* '''right''' click ''(or the TAB-key)'' opens the '''ATC messages selection''' box 

:* '''left double''' click '''centers''' radar '''map on''' the '''contact''' (to find contact)
:* '''CTRL+left''' click sets the contact to be '''neglected'''

* a click beside the flight strips moves the flight strips between the three columns (right, middle, left)

'''Runway area'''
* '''right''' click '''on runway number''' opens the '''runway settings dialog''' to define the centerline and vectoring settings
* If at least one runway is active you may '''double click''' the runway panel '''background to hide the inactive runways''' (frees space for flight strips)

'''Radios'''
* a '''right''' click '''on the frequency list''' changes the input to be '''editable''', so you can define the frequencies by yourself

''' Shortcuts '''
{| class="wikitable"
|-
! Shortcut !! Action
|-
| '''ESC''' || Close all open dialogs and cancel the text input (reset chat input field)

|-
| ALT + L || Toggle FGCom Log Window (only if you run FgCom started by OpenRadar)

|-
| '''Left CTRL''' || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| NUM off: Num0 || PTT Radio COM0 (if it has been activated via Port in Settings)
|-
| '''Left SHIFT''' || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num1 || PTT Radio COM1 (if it has been activated via Port in Settings)
|-
| NUM off: Num2 || PTT Radio COM2 (if it has been activated via Port in Settings)
|-
| NUM off: Num3 || PTT Radio COM3 (if it has been activated via Port in Settings)
|}

== Related content ==
* [[OpenRadar|The Design-Rules for OpenRadar]]
* [[OpenRadar: Editing routes|Editing STAR/SID routes]]
* [[OpenRadarKnownIssues|FAQ / Known Issues]]

[[Category:Air Traffic Control]]
[[Category:Java]]
[[Category:OpenRadar| ]]
[[Category:OpenRadar|Guide]]

Lockheed U-2S

2014-03-01T18:56:02Z

EmmanuelFrance:

{{infobox Aircraft
|image = U-2S at high altitude.png
|name = Lockheed U-2S
|type = High-altitude reconnaissance
|authors = Cem Aydin
|fdm = YASim/JSBSim
|status-fdm = 1
|status-systems = 1
|status-cockpit = 0
|status-model = 2
|fgname = U-2S
|download =
}}
The famous U-2 spyplane, for FlightGear.

The FlightGear aircraft described here, features the latest, modern variant of the U-2, the U-2S.

''Currently (2014-01-07) I'm reworking this aircraft.''

''The previously released version can still be downloaded from: http://cem.square7.ch/U-2S_20120710.zip''

''The current development version (suggested) can be downloaded from: https://github.com/rebootl/U-2S-git/archive/master.zip'' ''(The very latest is in the devel branch of above repo.)''

''Be aware that neither version can be considered finished.''

''Biggest missing is the cockpit/instrumentation which I'm working on now. Furthermore there might be broken things in the git version.''

''Below description refers to the mentioned git development version.''

The FDM has switched from YASim to JSBSim.

== Aircraft help ==

[[File:U-2S-ext-lights.png|thumb|U-2S, exterior view w/ Rembrandt lights.]]

The simulation starts with the engine off, the aircraft is fueled to about 2/3 capacity. The APU can be thought as connected and the electrics powered on. Currently there is no custom electrical system. External lights are on.

=== Engine start ===

A simplified startup sequence is provided.

* Press and hold "s". This is thought to simulate the APU powering on.
* After about 5 seconds, when 5% of n1 are reached, put the throttle to idle. By pressing } or middle mouse click on the throttle.
* The engine will increase to 60% of n2 and then start. Release "s".

The engine can be started by windmilling, when there is enough altitude to bring the engine to the needed n values. Use above procedure but without pressing "s". This is not (yet) a customized system but the default JSBSim behaviour.

=== Takeoff ===

* Close the canopy (Shift-c) and release the parking brake.
* Throttle to full.
* After a short time the pogos will fall off, keep the wings level.
* At about 80 kt the tail will start to rise. Try to keep the two point position.

=== Climb ===

* Try to keep 160 kt up to 50,000 ft by adjusting pitch.
* Between 50,000 and 70,000 ft decrease the speed gradually to 105 kt.

=== Descent ===

* Throttle to idle.
* Extend the speedbrake (Ctrl-b) and lower the gear.
* Descent with speeds from 105 to 160 kt.
* Below 50,000 ft speed may be increased up to 220 kt.

=== Landing ===

* Full flaps.
* Throttle as needed.
* Threshold should be passed 10 ft above ground.
* Touchdown should be made on main and tail gear together. To do this the aircraft is stalled at 1 ft above ground. At this point the main and tail gear should be aligned to the flight direction.
* Try to keep the wings level as long as possible.
* At 60 kt brakes can be applied gently and at 30 kt fully. (Currently the braking force is reduced in the FDM to provide a better handling with a button controller.)
* You can restore the pogos by pressing Shift-r (appropriately when the aircraft has stopped completely).

Have fun!

== Development status ==

=== Resources ===

Due to the lack of available data I'm using the flight manual of the original U-2. (See external links below.) I'm aware that this is somewhat a different aircraft but I believe it's still a valuable resource. Below I will use "FM" referring to it. Further I'm using images, drawings and flight reports.

=== JSBSim FDM ===

Based on a model created using aeromatic:

==== General ====

* adapted metrics, gears and structural positions, tanks, payload (stub) and gear control
* added custom throttle and fuel system

Open:

* cleanup is really needed, though currently I'm leaving things in as hints for further development

==== Aerodynamics ====

* polars generated for the main wing (and the hstab) using XFOIL and extended it by Javafoil and commonsense

Open:
* the [[DATCOM]] stuff needs to be redone w/ the information gained (from XFOIL and in general)
* further tuning of flight characteristics acc. to FM

Currently I'm using a "special" configuration that includes the horizontal tail for the pitching moment. Though I'm not convinced that this is best, so it might be subject to change.

==== Fuel system ====

A JSBSim fuel system is modelled. Only missing is the tank pressurization.

The fuel cross-transfer and dump system is fully functional but since the cockpit isn't finished there are no controls yet.

The respective properties are under /controls/fuel.

(For detailed information see Systems/fuel.xml.)

Estimations were made for the tank capacities.

==== Engine (GE-F118-101) ====

* changed tsfc
* manually extended the tables to higher altitudes
* bypassratio 2.0 <ref>Only found one source for this by now: http://wiki.scramble.nl/index.php/General_Electric_F101)</ref>
* corrected milthrust to 17,000.0 lb

(See Engine/GE-F118-101.xml.)

=== Model ===

==== Exterior ====

* complete model w/ animated control surfaces, gear and textures
* added lights (supporting Rembrandt, evtl. some finetuning needed)

Open:
* correct the tail gear steering animation
* the texturing and UV-mapping should be reworked (to simplify livery generation)
* add more details (to the gears, inside of the gear-/speedbrake box)
* evtl. correct some positions (e.g. speedbrake)
* evtl. create a normal map
* evtl. add selectable configurations (nose, senior span/spear)
* livery support, add more liveries (e.g. NASA ER-2)

==== Cockpit ====

[[File:U-2S-cockpit-wip.png|thumb|U-2S cockpit, current development state.]]

Currently I'm working on this. (See the image on the right.)

* reworked the interior w/o instruments
* added throttle and gearbox

Open:
* add instruments/controls (evtl. using the canvas system)
* texturing/UV-mapping
* add more details to the interior

=== Sound ===

The sound is taken from FG base package for now.

(Reworked 2013-12-17, see Sounds/U-2S-sounds.xml.)

=== Issues ===

* Currently there seems to be a bug in the ejection seat that prevents the pilot loading.

== References ==

<references />

== External links ==

* [[:wikipedia:Lockheed U-2|Lockheed U-2]] English wikipedia article.
* https://www.cia.gov/library/center-for-the-study-of-intelligence/utility-flight-hb-1-Mar-1959.pdf The Flight Manual of the original U-2.
* http://www.clubhyper.com/reference/u2sdwa_1.htm Excellent closeup photo reference, intended for aircraft modellers.
* http://www.barryschiff.com/high_flight.htm A flight report.
* http://www.youtube.com/watch?v=1PmYItnlY5M James May in a U-2...

{{Lockheed}}

[[Category:Military reconnaissance aircraft]]

Fr/Antonov An-2 description du tableau de bord

2014-03-01T18:53:25Z

EmmanuelFrance:

Il s'agit d'une description rapide pour les instruments et les commandes du cockpit de l'Antonov.

[[File:Antonov_AN-2_reference_left.jpg|thumb|left|cockpit 2D]]
[[File:Antonov_AN-2_reference_right.jpg|thumb|right|cockpit 3D (disponibles pour la version 2.0)]]
 

Les commandes de l'Antonov AN-2 :
# Horizon artificiel AGK-47 B.
# Compas Magnétique (gyroinduction) GIK-1 avec indicateur ADF.
# Gyrocompas GPK-48.
# Anémomètre US-450.
# Altimètre UVO.
# Variomètre VAR-10.
# Altimètre radio RV-UM.
# Warning altitude selector of RV-UM.
# Sélecteur de réservoir à carburant. Gauche (Left), droite (right), Les deux réservoirs (both tank) ou aucun (cutoff).
# Indicateur de niveau de carburant SBESS-1447.
# Thermomètre de l'entrée d'air. Chauffage de l'air d'admission n'est pas encore simulé, alors la jauge indique la température extérieur.
# Engine EMI-3K gauge. Fuel pressure meter, oil pressure and oil temperature indicator.
# Cylinder head termometer TCT-2.
# Tachymètre TE-45.
# Indicateur de pression d'admission MV-16u
# Ampèremètre A-1. Il mesurer l'intensité du courant du générateur principal.
# Volt-Ampèremètre VA-3. Il mesure le voltage et l'intensité du courant de la batterie.
# Position of oil cooler damper.
# Position of engine air damper. This gauge absent on real plane, pilot ought to control air dampers position visually.
# Indicateur de position des volets.
# ACHS-2 air clock. Extended scale of flight timers not implemented cause small size of gauge.
# Outboard termometer TUE-48.
# Magneto switch PM-1.
# Interrupteur de démarrage principal.
# Starter selector: spinup - start.
# GIK-1 compass fast adjust button.
# Pilot cabin window heat switch. Not implemented yet.
# Fuel meter selector: left - both - right fuel tank level.
# Audio alarm switch - min fuel level and min altitude. Not implemented yet.
# Min altitude lamp - RV-UM altimeter.
# Left and right fuel tank min level lamp. Work only if fuel meter SBESS-1447 is serviceable. Min level is 50 l of fuel.
# Charge battery lamp. Off if generator charge battery.
# PO-500 alternator failure lamp. Failure system not implemented, so it not work in 2d. In 3d cockpit, blue lamp indicated extending of automatic slats.
# Marker beacon lamp.
# Rudder trimmer neutral position lamp. There are hotspots on trimmer lamps for set trimmer to neutral.
# Elevator trimmer neutral position lamp.
# Aileron trimmer neutral position lamp.
# Elevator trimmer switch.
# Interrupteur des volets.
# Rudder trimmer switch.
# Aileron trimmer switch.
# Oil cooler damper switch.
# Cylinder head damper switch.
# Interrupteur des feux de navigation.
# Taxi light switch. Work only on patched sim.
# Landing light switch. Work only on patched sim.
# Main generator switch.
# Interrupteur de la batterie principale.
# GIK-1 alternator switch.
# AGK-47B alternator switch.
# Fuel meter SBESS-1447 switch.
# EMI-3K gauge switch.
# Flaps gauge switch.
# Termometers TUE-48 switch.
# Airspeed indicator heat switch.
# Panel UV light switch.
# COM radio switch.
# ADF radio switch.
# Marker beacon switch.
# Radio altimeter RV-UM main switch.
# Throttle handle. Not operate from mouse.
# Propeller pitch handle.
# Standby/operate selector for ADF.
# PO-500 alternator switch.
# Automatic altitude mixture corrector handle. In real aircraft, this handle should stay in rear position for automatic correction. Shift handle by front will be lean mixture.
# Intake heating handle. System not implemented yet.
# Stop engine handle. System not implemented yet.
# ADF bearing indicator for second pilot.
# ADF sound switch.
# ADF volume control.
# Lamp for main ("osnovnoj") ADF channel.
# Lamp for standby ("rezervnyj") ADF channel.
# Frequency control for main ADF channel. There are hotspots above and below frequency digits.
# Frequency control for standby ADF channel. There are hotspots above and below frequency digits.
# S-meter for ADF. It's not real signal power, cause sim not count ADF range.
# Rezerved, no-op.
# Rezerved, no-op.
# External panel lighting. Experimental. You can adjust color and brightness of panel lighting by set (manually, by setprop() or from XML file ) property "/an2/controls/light/ext-red-stanby", "/an2/controls/light/ext-green-standby", "/an2/controls/light/ext-blue-standby". All of color value should be 0.0-1.0.
# Internal instrument lighting. Experimental. Operate like external lighting. Name of property - "/an2/controls/light/int-red-standby" etc.
# Short wave radio "Yadro" ("Kernel") switch. Rezerved. "Yadro" control panel stay in bottom part of second pilot panel. Not implemented in sim.

= Related content =
* [[Antonov An-2]]

[[en:Antonov An-2 Panel Reference]]

[[Category:Aircraft documentation]]

Fr/Antonov An-2 description du tableau de bord

2014-03-01T18:51:56Z

EmmanuelFrance:

Il s'agit d'une description rapide pour les instruments et les commandes du cockpit de l'Antonov.

= Les commandes de l'Antonov AN-2 =
[[File:Antonov_AN-2_reference_left.jpg|thumb|left|cockpit 2D]]
[[File:Antonov_AN-2_reference_right.jpg|thumb|left|cockpit 3D (disponibles pour la version 2.0)]]
 

# Horizon artificiel AGK-47 B.
# Compas Magnétique (gyroinduction) GIK-1 avec indicateur ADF.
# Gyrocompas GPK-48.
# Anémomètre US-450.
# Altimètre UVO.
# Variomètre VAR-10.
# Altimètre radio RV-UM.
# Warning altitude selector of RV-UM.
# Sélecteur de réservoir à carburant. Gauche (Left), droite (right), Les deux réservoirs (both tank) ou aucun (cutoff).
# Indicateur de niveau de carburant SBESS-1447.
# Thermomètre de l'entrée d'air. Chauffage de l'air d'admission n'est pas encore simulé, alors la jauge indique la température extérieur.
# Engine EMI-3K gauge. Fuel pressure meter, oil pressure and oil temperature indicator.
# Cylinder head termometer TCT-2.
# Tachymètre TE-45.
# Indicateur de pression d'admission MV-16u
# Ampèremètre A-1. Il mesurer l'intensité du courant du générateur principal.
# Volt-Ampèremètre VA-3. Il mesure le voltage et l'intensité du courant de la batterie.
# Position of oil cooler damper.
# Position of engine air damper. This gauge absent on real plane, pilot ought to control air dampers position visually.
# Indicateur de position des volets.
# ACHS-2 air clock. Extended scale of flight timers not implemented cause small size of gauge.
# Outboard termometer TUE-48.
# Magneto switch PM-1.
# Interrupteur de démarrage principal.
# Starter selector: spinup - start.
# GIK-1 compass fast adjust button.
# Pilot cabin window heat switch. Not implemented yet.
# Fuel meter selector: left - both - right fuel tank level.
# Audio alarm switch - min fuel level and min altitude. Not implemented yet.
# Min altitude lamp - RV-UM altimeter.
# Left and right fuel tank min level lamp. Work only if fuel meter SBESS-1447 is serviceable. Min level is 50 l of fuel.
# Charge battery lamp. Off if generator charge battery.
# PO-500 alternator failure lamp. Failure system not implemented, so it not work in 2d. In 3d cockpit, blue lamp indicated extending of automatic slats.
# Marker beacon lamp.
# Rudder trimmer neutral position lamp. There are hotspots on trimmer lamps for set trimmer to neutral.
# Elevator trimmer neutral position lamp.
# Aileron trimmer neutral position lamp.
# Elevator trimmer switch.
# Interrupteur des volets.
# Rudder trimmer switch.
# Aileron trimmer switch.
# Oil cooler damper switch.
# Cylinder head damper switch.
# Interrupteur des feux de navigation.
# Taxi light switch. Work only on patched sim.
# Landing light switch. Work only on patched sim.
# Main generator switch.
# Interrupteur de la batterie principale.
# GIK-1 alternator switch.
# AGK-47B alternator switch.
# Fuel meter SBESS-1447 switch.
# EMI-3K gauge switch.
# Flaps gauge switch.
# Termometers TUE-48 switch.
# Airspeed indicator heat switch.
# Panel UV light switch.
# COM radio switch.
# ADF radio switch.
# Marker beacon switch.
# Radio altimeter RV-UM main switch.
# Throttle handle. Not operate from mouse.
# Propeller pitch handle.
# Standby/operate selector for ADF.
# PO-500 alternator switch.
# Automatic altitude mixture corrector handle. In real aircraft, this handle should stay in rear position for automatic correction. Shift handle by front will be lean mixture.
# Intake heating handle. System not implemented yet.
# Stop engine handle. System not implemented yet.
# ADF bearing indicator for second pilot.
# ADF sound switch.
# ADF volume control.
# Lamp for main ("osnovnoj") ADF channel.
# Lamp for standby ("rezervnyj") ADF channel.
# Frequency control for main ADF channel. There are hotspots above and below frequency digits.
# Frequency control for standby ADF channel. There are hotspots above and below frequency digits.
# S-meter for ADF. It's not real signal power, cause sim not count ADF range.
# Rezerved, no-op.
# Rezerved, no-op.
# External panel lighting. Experimental. You can adjust color and brightness of panel lighting by set (manually, by setprop() or from XML file ) property "/an2/controls/light/ext-red-stanby", "/an2/controls/light/ext-green-standby", "/an2/controls/light/ext-blue-standby". All of color value should be 0.0-1.0.
# Internal instrument lighting. Experimental. Operate like external lighting. Name of property - "/an2/controls/light/int-red-standby" etc.
# Short wave radio "Yadro" ("Kernel") switch. Rezerved. "Yadro" control panel stay in bottom part of second pilot panel. Not implemented in sim.

= Related content =
* [[Antonov An-2]]

[[en:Antonov An-2 Panel Reference]]

[[Category:Aircraft documentation]]

Antonov An-2 panel reference

2014-03-01T18:50:19Z

EmmanuelFrance:

This is a quick reference to the instruments and controls in the Antonov's cockpit.
= The Controls of the Antonov AN-2 =
[[File:Antonov_AN-2_reference_left.jpg|thumb|left|2D cockpit]]
[[File:Antonov_AN-2_reference_right.jpg|thumb|left|3D cockpit (avialable for version 2.0)]]
 

# Attitude indicator AGK-47 B.
# Magnetic (gyroinduction) compass GIK-1 with ADF indication.
# Gyrocompass GPK-48.
# Airspeed indicator US-450.
# Altimeter UVO.
# Variometer VAR-10.
# Radio altimeter RV-UM.
# Warning altitude selector of RV-UM.
# Fuel selector. Left, right, both tank or cutoff fuel.
# Fuel level indicator SBESS-1447.
# Intake air termometer. Heating of intake air not implemented yet, so gauge show outboard temperature.
# Engine EMI-3K gauge. Fuel pressure meter, oil pressure and oil temperature indicator.
# Cylinder head termometer TCT-2.
# Tachometer TE-45.
# Manifold pressure meter MV-16u
# Ampermeter A-1. It measure main generator current.
# Volt-ampermeter VA-3. It measure voltage and current of battery.
# Position of oil cooler damper.
# Position of engine air damper. This gauge absent on real plane, pilot ought to control air dampers position visually.
# Flaps position gauge.
# ACHS-2 air clock. Extended scale of flight timers not implemented cause small size of gauge.
# Outboard termometer TUE-48.
# Magneto switch PM-1.
# Main starter switch.
# Starter selector: spinup - start.
# GIK-1 compass fast adjust button.
# Pilot cabin window heat switch. Not implemented yet.
# Fuel meter selector: left - both - right fuel tank level.
# Audio alarm switch - min fuel level and min altitude. Not implemented yet.
# Min altitude lamp - RV-UM altimeter.
# Left and right fuel tank min level lamp. Work only if fuel meter SBESS-1447 is serviceable. Min level is 50 l of fuel.
# Charge battery lamp. Off if generator charge battery.
# PO-500 alternator failure lamp. Failure system not implemented, so it not work in 2d. In 3d cockpit, blue lamp indicated extending of automatic slats.
# Marker beacon lamp.
# Rudder trimmer neutral position lamp. There are hotspots on trimmer lamps for set trimmer to neutral.
# Elevator trimmer neutral position lamp.
# Aileron trimmer neutral position lamp.
# Elevator trimmer switch.
# Flaps button.
# Rudder trimmer switch.
# Aileron trimmer switch.
# Oil cooler damper switch.
# Cylinder head damper switch.
# Nav lights switch.
# Taxi light switch. Work only on patched sim.
# Landing light switch. Work only on patched sim.
# Main generator switch.
# Main battery switch.
# GIK-1 alternator switch.
# AGK-47B alternator switch.
# Fuel meter SBESS-1447 switch.
# EMI-3K gauge switch.
# Flaps gauge switch.
# Termometers TUE-48 switch.
# Airspeed indicator heat switch.
# Panel UV light switch.
# COM radio switch.
# ADF radio switch.
# Marker beacon switch.
# Radio altimeter RV-UM main switch.
# Throttle handle. Not operate from mouse.
# Propeller pitch handle.
# Standby/operate selector for ADF.
# PO-500 alternator switch.
# Automatic altitude mixture corrector handle. In real aircraft, this handle should stay in rear position for automatic correction. Shift handle by front will be lean mixture.
# Intake heating handle. System not implemented yet.
# Stop engine handle. System not implemented yet.
# ADF bearing indicator for second pilot.
# ADF sound switch.
# ADF volume control.
# Lamp for main ("osnovnoj") ADF channel.
# Lamp for standby ("rezervnyj") ADF channel.
# Frequency control for main ADF channel. There are hotspots above and below frequency digits.
# Frequency control for standby ADF channel. There are hotspots above and below frequency digits.
# S-meter for ADF. It's not real signal power, cause sim not count ADF range.
# Rezerved, no-op.
# Rezerved, no-op.
# External panel lighting. Experimental. You can adjust color and brightness of panel lighting by set (manually, by setprop() or from xml file ) property "/an2/controls/light/ext-red-stanby", "/an2/controls/light/ext-green-standby", "/an2/controls/light/ext-blue-standby". All of color value should be 0.0-1.0.
# Internal instrument lighting. Experimental. Operate like external lighting. Name of property - "/an2/controls/light/int-red-standby" etc.
# Short wave radio "Yadro" ("Kernel") switch. Rezerved. "Yadro" control panel stay in bottom part of second pilot panel. Not implemented in sim.

= Related content =
* [[Antonov An-2]]

[[fr:Antonov An-2 description du tableau de bord]]

[[Category:Aircraft documentation]]

Howto:Add aircraft lights

2014-03-01T18:48:13Z

EmmanuelFrance:

In order to '''add''' (the right) '''lights to your aircraft''', you need to know what kind of lights [[Aircraft|planes]] are equipped with. Therefore it is suggested to read [[aircraft lighting]] first.

== Anti-Collision Beacon lights ==
=== Nasal ===
<source lang="javascript">
var beacon_switch = props.globals.getNode("controls/switches/beacon", 2);
var beacon = aircraft.light.new( "/sim/model/lights/beacon", [0, 3], "/controls/lighting/beacon" );
</source>

=== Model ===
<source lang="xml">
<animation>
<type>select</type>
<object-name>Light</object-name>
<condition>
<property>/sim/model/lights/beacon/state</property>
</condition>
</animation>
</source>

== Strobe lights ==
=== Nasal ===
<source lang="javascript">
var strobe_switch = props.globals.getNode("controls/switches/strobe", 2);
var strobe = aircraft.light.new( "/sim/model/lights/strobe", [0, 3], "/controls/lighting/strobe" );
</source>

=== Model ===
<source lang="xml">
<animation>
<type>select</type>
<object-name>Light</object-name>
<condition>
<property>/sim/model/lights/strobe/state</property>
</condition>
</animation>
</source>

== Landing lights ==
=== Model ===
<source lang="xml">
<animation>
<type>select</type>
<object-name>Light</object-name>
<condition>
<property>controls/lighting/landing-light</property>
</condition>
</animation>
</source>

If the lights are located on the nosegear, use the one below instead. It will only show the lights when the landinggear is out. Change the value to make the light switch on when gear is out (vary from plane to plane, you can use the [[property browser]] to find the right value).
<source lang="xml">
<animation>
<type>select</type>
<object-name>Light</object-name>
<condition>
<and>
<property>controls/lighting/landing-light</property>
<greater-than>
<property>gear/gear/position-norm</property>
<value>0.05</value>
</greater-than>
</and>
</condition>
</animation>
</source>

[[Category:Nasal howto|Aircraft lights add]]

Fr/Cessna Citation X

2014-03-01T18:43:19Z

EmmanuelFrance: /* Contenu associé */

{{infobox Aircraft
|image = CessnaCitationX.jpg
|name = Cessna Citation X
|type = Jet privé
|status-fdm = 3
|status-systems = 3
|status-cockpit = 3
|status-model = 3
|livery = Stripes
|authors = Syd Adams
|fdm = YASim
|status = Développement
|fgname = CitationX
}}
Le '''Cessna Citation X''' (X pour le chiffre romain dix, et non pour la lettre) est un avion d'affaire à grand rayon d'action. Le X est actuellement le jet civil le plus rapide avec une vitesse maximale de Mach 0.92 (703 mph). Ce qui en fait le jet d'affaire le plus rapide de l'histoire. Le Citation X est propulsé par deux turboréacteur Rolls-Royce et est construit par la [[Cessna Aircraft Company]] à Wichita au Kansas. La catégorie de jet d'affaire comprend six différentes «familles» de l'avion. Bien que basé sur le modèle précédent Citation III, VI et VII, le Citation X est un avion très différent. Il utilise une conception totalement nouvelle des ailes, des moteurs et comprend Planche de bord tout écran.

== Contenu associé ==
* [[FlightGear Newsletter April 2011#Aircraft reviews|Présentation du Cessna Citation X]]
{{Cessna}}

[[Category:Business aircraft]]

[[de:Cessna Citation X]]
[[en:Cessna Citation X]]
[[es:Cessna Citation X]]
[[it:Cessna Citation X]]

TerraMaster

2014-03-01T18:41:50Z

EmmanuelFrance:

{{Infobox Software
|title = TerraMaster
|logo =
|image = TerraMaster r32 - Global view.png
|developedby = reeed
|initialrelease = {{ISOdate|2011-07-18}}
|latestrelease = r32, {{ISOdate|2012-12-02}}
|writtenin = Java
|os =
|platform = crossplatform
|developmentstatus =
|type = Scenery manager
|license =
|website = http://code.google.com/p/terramaster
}}
'''TerraMaster''' is a graphical [[scenery]] manager that gives you a quick overview of your scenery and makes it easier to maintain that scenery. TerraMaster is a cross platform stand alone application written in Java that synchronises [[TerraSync]] scenery tiles you select with the FlightGear Scenery Database. You can delete scenery tiles if the TerraSync scenery directory takes too much space, and you can also search for airports.

== Overview ==
=== Map ===
When TerraMaster starts it will show a map of the Earth. The map can be zoomed and one or more 1 x 1 degree tiles can be selected before they are synced or deleted. All the airports within a tile can be shown, and airports can be searched for and be shown.

=== Icons ===
The top row contains a status field, two groups of icon buttons, a search field and a sync progress bar. The icons will be grayed out when they can not be used. For more detailed directions, see the section ''Using'' below. From left to right:
* ''Status field''. Shows the name of the tile that was last selected.

* ''Sync icon''. Syncs the tiles currently selected.
* ''Trash can icon''. Deletes the currently selected tiles.
* ''Eye icon''. Shows all airports in the first selected tile of the currently selected tiles.
* ''Stop button''. Currently does not work.

* ''Empty paper''. Hides all shown airports.
* ''Globe icon''. Zooms out to the global view.
* ''Gear icon''. Opens a dialogue to select the location of the TerraSync scenery directory.

* ''Search field''. Used to search for airports.

* ''Sync progress bar''. Only visible during syncing.

=== Tile border colours ===
The tiles are colour coded to represent the state of the tiles:

* '''Green''' tiles have both terrain and objects.
* '''Amber/Yellow''' tiles has terrain but no objects. (And are possibly unsyncable - see "Bug", below.)
* '''Red''' tiles are currently selected for synchronisation.
* '''Blue''' tiles are currently being synchronised.

The blue tiles that are being synced will change colour to green or amber/yellow as they are synced. Tiles that get no border after they have been synced don't contain terrain or objects and are usually located in open seas.

== Using ==
[[File:TerraMaster r32 - Mouse hint.png|thumb|Tile information pop-up when holding the mouse pointer over a tile.]]
[[File:TerraMaster r32 - Airports in selected tile.png|thumb|Showing all airports in a selected tile using the "eye" button.]]
[[File:TerraMaster r32 - Searching for an airport.png|thumb|Searching for an airport.]]

=== Zooming and panning ===
TerraMaster with the global view. Left-clicking will zoom you in on an area.

'''Zoom''' using the scroll wheel.

'''Pan''' around by dragging the map while pressing the right mouse button.

Get '''back to global view''' by clicking the "globe" icon.

=== Showing tile information ===
To get some information about a downloaded tile, hold the mouse pointer over it.

A pop-up box will show the name of that tile, if there are terrain and objects in it and what airports it contains. This only works if a tile has been synced, either with Terrasync or TerraMaster.

=== Syncing tiles ===
To '''select just one tile''' left-click it. The scenery for download is available in 1x1 degree tiles.

To '''select more tiles''' press the Ctrl key while left-clicking or left-dragging over the wanted tiles. If you accidentally selected a tile to many, '''deselect tiles''' using it Ctrl+left-click. You can also deselect several tiles using Ctrl+left-click and dragging.

'''Start the update and/or download''' clicking the "sync" icon. The tiles will be downloaded starting from the first tile you selected and proceed in order of distance from it. If you are downloading tiles for a long flight you should then begin by selecting a tile close to the departure airport.

=== Deleting tiles ===
You can delete files from the TerraSync scenery by selecting the tiles you want to delete and click the "trash can" icon.

=== Showing all airports in a tile ===
To show all airports in a tile, select it and click on the "eye" icon. To hide the airports again, click the "empty paper" icon.

=== Searching for an airport ===
You can search for airports using the search field and pressing enter. The airports location an ICAO code will be shown in white on the map. If you don't see it, zoom out. ICAO airport codes works best, but sometimes the airport's name also work. To hide the airports again, click the "empty paper" icon.

Be warned that the search function is rather slow as it uses a web query to mpmap.flightgear.org and that it also doesn't tell if there was no airports found.

== Tips ==
* '''Before [[multiplayer]] events''' it might be an idea to sync the related tiles, even more so if you know that someone has crated new buildings etc. and got them into the [[FlightGear Scenery Database|scenery database]].
* If you have very little hard drive space left you can delete tiles you rarely or never fly within.
* Starting TerraMaster in a console window will let you see the sync process, which can be useful if the sync stalls for unknown reasons.
* If you already have a synchronisation running and want to add more tiles to be synced, just mark more tiles as above with Ctrl + leftclick and drag to mark more tiles and press the sync button again.

== Installing ==
Before installing, make sure you have Java 6 or higher, as it is needed.

# Download the newest version of TerraMaster from the [http://code.google.com/p/terramaster/downloads/list download page].
# Unzip all the files in a suitably named and placed folder.
# Create a shortcut or script that runs <code>java -jar terramaster.jar</code>.
# When running TerraMaster the first time, click the "gear" icon and select the folder where your TerraSync scenery is located. On some machines you might have to manually edit the property file to have it pointing to the TerraSync directory.
# Done!

== Possible bug ==
It can happen that if you try to sync a tile with no airports TerraMaster will fail to run the next time you open it. Keep a copy of the ''terramaster.properties'' file and, when that happens, copy it over the one in the folder where you placed the TerraMaster files. You will have to click the "gear" icon again to specify the path to the Terrasync folder. You can go to [http://code.google.com/p/terramaster/issues/list TerraMaster Issues] and check the Status of Issue 2 to see if it is fixed.

"Un-syncable" tiles will stay yellow.

== Models ==
Don't forget that the contents of /terrasyn/Models will have to be coped to [[$FG_ROOT]]/Models for them to be visible.

== Related content ==
* [[FlightGear Admin Wizard]]

== External link ==
* [http://forum.flightgear.org/viewtopic.php?f=5&t=12050 TerraMaster: a new scenery manager] topic on the FlightGear forum.

[[Category:Scenery software]]
[[Category:Java]]

FlightGear World Scenery 2.0

2014-03-01T18:39:20Z

EmmanuelFrance:

:''Follow the dedicated forum thread: [http://forum.flightgear.org/viewtopic.php?f=5&t=21294 FG Worldwide scenery 2.0 - Return of experience]''

The '''FlightGear World Scenery 2.0''' was released during [[FSweekend]] November 2013. This new scenery reflects a major improvement over the existing default world scenery and has taken over five years to complete. A [http://mapserver.flightgear.org/map/?lon=14.56652&lat=-25.18458&zoom=1&layers=B00000000000FTFFTFFTFFFFFFFF much higher level of detail] and internal consistency characterizes this new release, in addition to the fact that it will serve as a stepping-stone for further incremental refinements.

== Source data ==
This FlightGear World Scenery was compiled from:
* ViewFinderPanoramas elevation model by Jonathan de Ferranti (using 20m accuracy with terrafit.py -e 20),
* VMap0 Ed.5 Worldwide Land Cover
* CORINE Land Cover 2006v16 for Europe (Source : European Union, SOeS, CORINE Land Cover, 2006 - [http://www.ifen.fr/index.php?id=88]). See [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail|here] for the correspondance between CORINE and FG textures
* Several custom land cover enhancements (to be listed here...)
* The latest airports (2013.10), maintained by Robin Peel of X-Plane
* Road, rail and rivers courses line data by OpenStreetMap [http://www.openstreetmap.org]

== Distribution ==
World Scenery 2.0 is available through the usual channels:
* [[TerraSync]]
* [http://terasaur.org/item/downloads/flightgear-v2-12/6697 Torrent]
* FlightGear main website
* [[TerraSync by hand using svn]]

== Side note ==
Note that all objects elevation were recomputed. Thus, if some objects were defined with a bad elevation or bad offset, they may have taken a bit of elevation. Use [http://scenemodels.flightgear.org our webforms], if necessary, to fix this.

== Screenshots ==

== Known bugs and limitations ==
# clipping of OSM roads on water showing height glitches (due to bad coast/river lines definitions and bad clipping): clip roads against landmass or add landmass where required? Should roads over bridges get removed, even in places where a 3D bridge model is missing?
# some z-fighting (clipper is generating the correct number of contours, but the airport hole is wound as a boundary, not a hole) and/or triangles on airports (LFRH, EDWJ (partially submerged)...);
# some troubles on very dense cities (such as Paris) leading to grey-white triangles on cities - see also yellow lines @LFPG;
# some line issues on small airfield with LTA specific runways (LFNH, LFLI...) - the small centerlines on the runways are "floating" over the runway (20 cm to 1m), leading to some gear destructions ;-) (they didn't use lines, but surfaces that are defined as transparent and borders defined as the line type. This way you limit the number of "line features"). Probably "hot" = false would solve it. See [http://uppix.net/y1H1NB.png 1] [http://uppix.net/sMdg17.png 2] [http://uppix.net/kAXrdF.png 3] [http://uppix.net/vYuReF.png 4] [http://uppix.net/DQ4NHr.png 5]. Thanks Clément for noticing;
# airport being located over two different tiles sometimes renders bad, leading to z-fighting (LEJR, UKKE...);
# on sharp cliffs, water sometimes climb over the cliffs (see e000n40/e000n49/2958056 and [http://img809.imageshack.us/img809/2082/9n96.jpg this picture] for instance). Thanks clm76 for reporting;
# terrain and ocean z-fighting such as [http://mapserver.flightgear.org/map/?lon=12.73312&lat=55.60834&zoom=15 east of EKCH]. See tile 3155042 and EDWJ;
# clipping between river and terrain is somewhat strange, making the river "climb" over the terrain, noticeably under bridges - probably due to the presence of the roads. See [http://img809.imageshack.us/img809/2082/9n96.jpg this example];
# the Moss Landing airport (on the coast a little bit south of KSFO) is partly submerged into the water and the airport's north end is elevated above the terrain around it. There is an area on the coast just to the north of the Moss Landing airport that is above sea level if you are up above 1000ft but is covered in water is you are on the deck. When flying over this you can see trees sticking up out of the water so the code that is placing random trees thinks this is above sea level. The old scenery didn't have either of these problems. Also if you fly over this at just the right altitude you can see this area switching back and forth between being water and land (thanks hvengel);
# on many airports where the taxiway signs are now taken from the apt.dat and put in the Terrain folder, the old signs still remain in the Object folder. See EDDF, ELLX;
# on ELLX there are some problems with "holes" in the pavement that flicker between grass and tarmac. I saw this (if I remember correctly) with an older development version of terragear, but this was fixed some time ago.
# on EHAM some vertice seems to be inverted [http://uppix.net/AVUaZt.jpg see this picture]
# at LFLI the taxiway is not correctly drawn
# the taxiway signs are not rendered correctly with transition shader set to its maximum in ALS. Quoting ThorstenB, "It occurs because you're using the terrain shader effect on something that isn't part of the terrain but in reality an artificial object placed onto the terrain. The terrain shader effect concludes correctly that a natural vertical surface cannot be anything but rock, so it replaces the default texture with the default steep gradient texture - which is rock. In my view, the proper solution would be to *not* render signs as part of the terrain but to let a different effect handle them (model-default.eff should do the trick for instance, but one could also run a lower quality terrain shader). If that is not acceptable a workaround is to declare the gradient texture for the signs as void.png as described in http://wiki.flightgear.org/Procedural_Texturing#The_gradient_texture which continues to use the terrain-specific effect but instructs the shader not to use a separate texture for steep gradients."
# sometimes some strange water width transitions, like [http://i217.photobucket.com/albums/cc283/oliunterderbruecke/flightgear/TG%20bugs/fgfs2013-11-0822-18-06-03_zpsf3527850.jpg for the Rhein] - reported by ot-666
# triangle winding appears inconsistent - especially when a vertex is shared by 4+ edges. Issue can be visualized here: [https://dl.dropboxusercontent.com/u/29968727/fgfs-screen-116.png messed up binormals and tangents] This may be the root cause of the urban shader issue - reported by i4dnf. Issue understood - Winding is not the issue, duplicate nodes per triangle (zero area triangles) are possible when converting the CGAL exact triangle back to nodes using double floats.
# In a few airports (LEVT, LEGE are two examples), taxiways are defined in using a stack of layers: the bottom layer for the asphalt surface and the upper layer (defined as transparent) is only used to define the lines. Current tools do not support stacks of layers and the upper layer is "transparent" all the way down to the ground. See [http://i.imgur.com/AkOd5Zo.png 1] and [http://forum.flightgear.org/viewtopic.php?f=5&t=21294&p=201132#p201126 2] This is easily fixable in the data by changing transparent layers to asphalt, but it involves a manual intervention in each airport and sending the data back to Robin. And actually, there is not anything wrong with the original data. Other airports such as LFLR do take advantage of transparent taxiways.

Fixed:
* [FIXED] near EHAM there is a pylon under terrain [http://uppix.net/7rFkTR.jpg see this picture]
* [FIXED] # glacier landcover is missing, leading to some holes in high moutains, as seen in Switzerland (SW [http://mapserver.flightgear.org/map/?lon=8.12304&lat=46.07741&zoom=9&layers=B00000000000FTFFTFFTFFFFFFFF LSMM]), Austria ([http://mapserver.flightgear.org/map/?lon=11.3527&lat=47.25782&zoom=10&layers=B00000000000FTFFTFFTFFFFFFFF south of LOWI]) and Northern Norway (i.e. [http://mapserver.flightgear.org/map/?lon=14.210&lat=65.974&zoom=9&layers=B00000000000FTFFTFFTFFFFFFFF near ENMS]);

== Features enhancement ==
# enhance landcover data for the rest of the world (OSM? vectorize US-American NLCD2006?) and add more custom scenery and fixes;
# complete CORINE coverage, fix overlaps in CLC2000 and merge with CLC2006;
# use latest ViewFinderPanoramas DEM's;
# find a new svn hosting solution;
# compute the next terrain with textures-lines option;
# add some more OSM data (secondary...);
# descent airports priority below roads, so roads and railroads can be shown over airports; have a proper solution for roads running over terrain classified as airfield, maybe extract administrative boundaries from apt.dat;
# retry multi-thread;
# enhance the "random" tree and builds placement to take OSM into account;
# .SPT file support - push Mathias' LOD ideas forward;
# landclass border blurring - Several ideas on this - It would be really nice to be able to do it;
# osm motorway_link (and the other _link) roads should probably have their own width. Perhaps grouped into a separate shapefile, or handled in ogr-decode - single lane is most likely;
# osm line data simplification / preprocessing. - We've done some experimenting, and the results are promising. This should reduce the number of triangles generated. It could create longer continuous roads, which allows better control of the generated texture coordinates - so we could, theoretically, populate the roads with traffic in the future.

== External link ==
* World Scenery 2.0 release announcement on the forum: [http://forum.flightgear.org/viewtopic.php?f=5&t=21226& FlightGear World Scenery 2.0 released]

[[Category:Scenery]]

Beechcraft Model 99

2014-03-01T18:34:28Z

EmmanuelFrance:

{{infobox Aircraft
|image =Beech99.jpg
|name =Beechcraft Model 99
|type =
|fdm =YASim
|status =
|authors =Chuck Dome, Michael Selig (FDM)
}}
The Beechcraft Model 99 is a civilian aircraft produced by the Beechcraft. It is also known as the Beech 99 Airliner and the Commuter 99. The 99 is a twin-engine, unpressurised, 17-seat/15-passenger turboprop aircraft, derived from the earlier Beechcraft King Air and Queen Air, using the wings of the Queen Air, and the engines and nacelles of the King Air, and sub-systems from both, and with a unique nose structure used only on the 99. It was designed in the 1960s as a replacement for the Beechcraft Model 18 and its first flight was in July 1966.

== Real-life Specifications (Model 99A)==

General characteristics
* Crew: One
* Capacity: Normally 15 passengers (8-seat 'Business Executive' model available) [[Portal:Developer]]
* Length: 44 ft 6¾ in (13.58 m)
* Wingspan: 45 ft 10½ in (13.98 m)
* Height: 14 ft 4⅓ in (4.37 m)
* Wing area: 279.7 ft² (25.99 m²)
* Empty weight: 5,533 lb (varies depending upon equipment and configuration) (2,515 kg)
* Loaded weight: <!10400 lb (99 and 99A) l 10900 lb (B99 and aircraft modified with Beech Kit 99-5014); 11300 lb (C99)> ()
* Max. takeoff weight: 10,400, 10,900, or 11,300 lb – see above (4,727 kg)
* Powerplant: 2 × Pratt & Whitney PT6A-20, -27. or -36 turboprop Hartzell constant speed, feathering, and reversing, 550, 680, or 715 eshp depending upon model/mod status (please fix) each
Performance
* Cruise speed: 205 knots (380 km/h) at 10,000 ft (3,050 m)
* Range: 910 nm (1,048 mi, 1,686 km)at 216 mph (347 km/h) at 8,000 ft (2,440 m)
* Service ceiling: 26,200 ft (7,988 m)
* Rate of climb: 1,700 ft/min (8.63 m/s)

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

* I'm currently in the building a new 3d model with windows and everything. It will be finished someday, but not yet :). A screenshot can be found at: [http://www.kcid.nl/planes/beech99_new1.jpg New Beech99]

* Flaps, ailerons and pitch elevator are not animated totally correct, slightly out of pitch
* Aircraft has no shadow
* Only aircraft light available is the Beacon.
* No jet-stream visible
* Nozzles do not change shape when changing thrust
* There are no flaps when using reverse thrust

3D Cockpit:
* 3D cockpit is not yet in finished, I'm currently working on the throttle quadrant.

General:
* Engine sound in cockpit does not differ from outside engine sound
* Engines can't be turned off
* HUD is not available

{{Beechcraft}}

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

Boeing 737-9 MAX

2014-03-01T18:31:49Z

EmmanuelFrance:

{{infobox Aircraft
|image = 7378maxpreview.jpg
|alt =Boeing 737-9 MAX in AC3D
|name =Boeing 737-9 MAX
|type =Airliner
|livery =No
|authors =Krb1
|fdm =JSBSim
|status =Development
|fgname =737-9 MAX
|download = NO
}}
'''Ready'''
* 3D Model
* A part of XML

'''Doing'''
* 3D Cockpit
* Avionics

'''To Do'''
* A lot

<gallery>
File:1747max.png|Energie
File:2747max.png|MAX series from the 3D camera in [[AC3D]]
File:3747max.png|MAX series from the right side
File:4747max.png|MAX series from the front side
</gallery>

[[Category:Boeing]]

Boeing 737-9 MAX

2014-03-01T18:30:59Z

EmmanuelFrance:

{{infobox Aircraft
|image = 7378maxpreview.jpg
|alt =Boeing 737-9 MAX in AC3D
|name =Boeing 737-9 MAX
|type =Airliner
|livery =No
|authors =Krb1
|fdm =JSBSim
|status =Development
|fgname =737-9 MAX
|download = NO
}}
'''Ready'''
* 3D Model
* A part of XML

'''Doing'''
* 3D Cockpit
* Avionics

'''To Do'''
* A lot

<gallery>
File:1747max.png|Energie
File:2747max.png|MAX series from the 3D camera in ac3d
File:3747max.png|MAX series from the right side
File:4747max.png|MAX series from the front side
</gallery>

[[Category:Boeing]]

Boeing 737-400

2014-03-01T18:28:52Z

EmmanuelFrance: /* ILS */

{{infobox Aircraft
|image =737-400.png
|alt =Boeing 737-400 at Frankfurt Main EDDF
|name =Boeing 737-400
|type =Airliner
|livery =Aerolineas Argentinas, Avior Airlines, China Southern, EasyJet, FlightGear iEspana, Hapag-Lloyd Express, HLX-TMobile, Iberia, LAN Chile, Lufthansa, MALEV, Malaysia Airlines, Mexicana, Ryanair, Scandanavian Airlines, Southwest, Turkish, United Airlines, Viasa, Virgin Blue, Virgin Express, Volaris
|authors =David Culp, Innis Cunningham, FlightGear Iespaña Team
|fdm = [[JSBSim]]
|status =In-Development
|fgname =737-400
|download = http://flightgear.iespana.es (dead link)
}}
The '''Boeing 737-400''' was launched in 1985 as a stretched [[737-300]], primarily for use by charter airlines.

== Download ==
You have to download two files, since the model and the sounds come in two different packages and go into two different directories.

Note: Divshare may not function on Windows 7 Laptops.

In November 2009, the direct links are:
* Model: http://www.divshare.com/download/7242443-cb1 (--> unpack to FGROOT\data\aircraft)
* Sounds: http://www.divshare.com/download/5256565-2c4 (--> unpack to FGROOT\data)
You can find the newest version of both on http://flightgear.iespana.es/

== Aircraft help ==
For information on engine startup, livery selection, auto brake, reject take off etc. press "?" or "Help --> Aircraft Help" when the simulation is running.

== Navigation ==
As far as I know, out of all airliners the 737-400 has the best modelled navigation panels available in FlightGear. You can set almost all frequencies and Autopilot settings from the 3D cockpit, and very detailed information is given back to you on the screens and instruments. Here are some features:

=== TCAS ===
The TCAS ([http://en.wikipedia.org/wiki/Traffic_Collision_Avoidance_System Traffic Alert and Collision Avoidance System]) displays other aircraft on the main screen. The radar has a range of 20nm. Each bar on the white line in the middle marks 5nm. To use TCAS, you have to switch it on:

[[File:Tcas1.png|200px]]

TCAS off.

[[File:Tcas2.png|200px]]

TCAS on. Blue triangles: Other multiplayer pilots. White triangles: AI aircraft. (This screenshot was taken at an airport.)

[[File:Tcas3.png|200px]]

Switch on TCAS in the middle console. A voice will say "TCAS system test okay".
=== FMC (Flight Management Computer) ===
For example, I have set up the [[Route Manager]] to follow the fixes OMOGI, OKAVO, AKONI and OBERO.

[[File:RoutemanB7341.png|200px]]

Once route is programmed, it's displayed in the middle console. The distance to the next waypoint OMOGI is 13.5 nm. The total distance to the last waypoint is 31.9 nm.

[[File:RoutemanB7342.png|200px]]

The next waypoint is displayed on the screen as a yellow dot.

=== VOR ===
[[VHF Omni-directional Radio Range|VOR]] arrows (vectors) are blue if in NAV1 and green if in NAV2. They point in the direction of the [[VHF Omni-directional Radio Range|radial]] you defined in the radio settings (Equipment --> Radio Settings). In the 737-400, when are 20 nm or closer, the VOR will show up on the screen. In the following screenshot, a VOR, for which you have set a radial of 080, is 10 nm away from you and you are flying directly to it. Note that there is traffic at your 5 o'clock.

[[File:B734vor1.png|200px]]

=== NDB ===
[[List of abbreviations#N|NDB]] arrows are dark yellowish. The long one points in the direction of the NDB, i.e. tells you where the NDB is relative to you. The short arrow indicates the radial you defined in the radio settings dialogue.

[[File:B734ndb1.png|200px]]

The NDB is at a heading of approximately 267 from you (long arrow), but you want to approach it at a radial of 250 (short arrow). Fly a little to the right to align both arrows:

[[File:B734ndb2.png|200px]]

=== ILS ===
[[ILS]] appear in the same way as VORs, as blue or green arrows. The thick dot in their center is the beginning of the runway. In the following example you approach runway 25R at EDDF from southwest. On the map you see several navaids:

[[File:B734ils3.png|200px]]

On the extended runway, apart from the ILS localizer, there are also the VOR Frankfurt FFM and the NDB Frankfurt FR. In the two following screenshots, you use more than one navaid.

* Left image: ILS localizer and NDB (radial 250).
* Right image: You add the VOR (radial 250).

[[File:B734ils1.png|200px]] [[File:B734ils2.png|200px]]

''Have fun flying this cool plane and feel free to improve this article!''

{{Boeing}}

[[Category:Airliners]]

[[fr:Boeing 737-400]]

Fr/Boeing 737-400

2014-03-01T18:27:37Z

EmmanuelFrance:

{{infobox Aircraft
|image =737-400.png
|alt =Boeing 737-400 at Frankfurt Main EDDF
|name =Boeing 737-400
|type =Airliner
|livery =Aerolineas Argentinas, Avior Airlines, China Southern, EasyJet, FlightGear iEspana, Hapag-Lloyd Express, HLX-TMobile, Iberia, LAN Chile, Lufthansa, MALEV, Malaysia Airlines, Mexicana, Ryanair, Scandanavian Airlines, Southwest, Turkish, United Airlines, Viasa, Virgin Blue, Virgin Express, Volaris
|authors =David Culp, Innis Cunningham, FlightGear Iespaña Team
|fdm = [[JSBSim]]
|status =In-Development
|fgname =737-400
|download = http://flightgear.iespana.es
}}
Le '''Boeing 737-400''' a été lancé en 1985 comme une extension du [[737-300]], il est principalement utilisé par des compagnies charter.

== Téléchargement ==
Vous devez télécharger deux fichiers, puisque le modèle et les sons viennent de deux paquets et vont dans deux répertoires différents

Remarque: DivShare peut ne pas fonctionner sur les ordinateurs portables sous Windows 7.

En Novembre 2009, les liens directs sont :
* Model: http://www.divshare.com/download/7242443-cb1 (--> unpack to FGROOT\data\aircraft)
* Sounds: http://www.divshare.com/download/5256565-2c4 (--> unpack to FGROOT\data)
Vous pouvez trouver la dernière version ici http://flightgear.iespana.es/

== Aide de l'avion ==
Pour plus d'informations sur le démarrage des moteurs, la sélection des livrés, le freinage automatique etc... faites "?" ou "Help --> Aircraft Help" quand le simulateur est lancé.

== Navigation ==
Autant que je sache, de tous les avions, le 737-400 a les meilleurs panneaux de navigation modélisés de FlightGear. Vous pouvez régler presque toutes les fréquences et les réglages du pilote automatique depuis le cockpit 3D, et des informations très détaillées sont fournies sur les écrans et les instruments. Voici quelques caractéristiques :
TCAS

=== TCAS ===
Le TCAS ([[:wikipedia:Traffic_Collision_Avoidance_System|Traffic Alert and Collision Avoidance System]]]) affiche les autres avions sur l'écran principal. Le radar a une portée de 20nm. Chaque barre sur la ligne blanche du milieu marquent les 5nm. Pour mettre en route le TCAS, vous devez l'activer ici :

[[File:Tcas1.png|200px|TCAS hors tension]]

TCAS hors tension

[[File:Tcas2.png|200px|TCAS sous tension]]

TCAS sous tension

* Triangles bleus : Les autres pilotes en ligne.
* Triangles blanc : Avion AI. (La capture d'écran a été prise dans un aéroport.)

[[File:Tcas3.png|200px]]

Activez le TCAS au milieu de la console centrale. Une voix dira "TCAS system test okay".

=== FMC (Flight Management Computer) ===
Pour l'exemple, j'ai activé le [[Route Manager]] pour suivre les waypoints OMOGI, OKAVO, AKONI et OBERO.

[[File:RoutemanB7341.png|200px]]

Une fois que la route est programmée, elle est affichée dans la console centrale. La distance jusqu'au prochain waypoint OMOGI est de 13,5 nm. La distance totale avec le dernier waypoint est de 31,9 nm.

[[File:RoutemanB7342.png|200px]]

Le prochain waypoint est affiché sur l'écran comme un point jaune.

=== VOR ===
Les flèches (vecteurs des [[VHF Omni-directional Radio Range|VOR]] sont bleu sur le NAV 1 et vertes sur le NAV2. Ils pointent la direction de la [[VHF Omni-directional Radio Range|radiale]] que vous avez définie dans les paramètres radio ({{lang|en|Equipment --> Radio Settings}}). Dans le 737-400, quand il y a une balise proche de 20nm, le VOR va apparaître à l'écran. Dans la capture d'écran suivante, le VOR pour lequel vous avez défini une radiale de 080, est à une distance de 10nm de vous et vous volez directement à lui. Notez qu'il y a du trafic à vos 05 heures.

[[File:B734vor1.png|200px]]

=== NDB ===
Les flèches indiquant les balises [[List of abbreviations#N|NDB]] sont jaunes foncé. La plus longe pointe la direction relative de la balise NDB par rapport à vous. La petite flèche vous indique la radiale définie dans les paramètres radio.

[[File:B734ndb1.png|200px]]
La balise NDB est à un cap d'environ 267 de vous (flèche longue), mais vous voulez l'approcher avec une radiale de 250 (flèche courte). tourner un peu à droite pour aligner les deux flèches :

[[File:B734ndb2.png|200px]]

=== ILS ===
L'[[ILS]] apparaît de la même manière que les VOR, avec une flèche bleu ou verte. Le point en son centre est le début de la piste. Dans l'exemple suivant vous vous approchez de la piste 25R à EDDF du sud-ouest. Sur la carte que vous voyez plusieurs aides à la navigation :

[[File:B734ils3.png|200px]]
Sur la piste prolongée, en dehors de l'alignement de l'ILS, il y a aussi le VOR Francfort FFM et le NDB Francfort FR. Dans les deux captures d'écran suivantes, vous utilisez plus d'une aide à la navigation.

* Image de gauche : ILS piste et NDB (radial 250).
* Image de droite : Vous ajoutez le VOR (radial 250).

[[File:B734ils1.png|200px]] [[File:B734ils2.png|200px]]

''Ayez beaucoup de plaisir à piloter ce formidable avion et n'hésitez pas à améliorer cet article.''

{{Boeing}}

[[Category:Airliners]]

[[en:Boeing 737-400]]

Boeing 787-8 Dreamliner

2014-03-01T18:13:57Z

EmmanuelFrance:

{{infobox Aircraft
|ready = aircraftmonth
|image = Boeing-787-8-splash.png
|name = Boeing 787-8 Dreamliner
|type = Airliner
|livery = Default: BOE, ANA, MIA ; The UVMap has not changed, so the old 787-8's liveries can also be used.
|liverydbid = 11
|fdm = JSBSim
|status = In Development
|authors = Omega95, Redneck, Awexome, Bicyus, ScottH1, Hooray, Zan, NickyIvyCA, Jentron, Thorsten, OT-666, Tikibar and Joshua Wilson (See Authors.txt for more info)
|fgname = 787-8
|status-fdm = 4
|status-systems = 5
|status-cockpit = 4
|status-model = 4
|download = http://wiki.flightgear.org/Boeing_787-8_Dreamliner#Downloading_the_787-8
|development = http://forum.flightgear.org/viewtopic.php?f=4&t=15333
}}
The '''Boeing 787-8 Dreamliner''' project was aimed at improving the systems and [[cockpit]] of the [[Boeing 787|old Boeing 787]]. Initially undertaken by Omega95 and Redneck, the project led to a major overhaul and redevelopment of the predecessor model, with only the main aircraft model and liveries yet to be modified. An interesting change and key feature of the new model is the impementation of a new [[Flight Dynamics Model]] based on the [[JSBSim]]. This was created using much data from [http://www.lissys.demon.co.uk/samp1/desmis.html -- the Piano tool]. Other interesting new features include the development of a 'cool' glass cockpit with highly detailed Boeing 787-8 instruments; and many advanced systems such as the Hydraulics, Pneumatics, Heating, Fuel System and Fly-By-Wire functionality.

The first trace of the project on the forum was from the development of the Boeing 787-8's CDU and since then, it has turned into a community project. A lot of developers and forum users have contributed to make this successful. Another key feature is that whenever findings or innovations have been made, they have gone on to the forum and soon, a lot of wiki HowTo tutorials have been created so that these may help other developers too.

=Innovations=

==New Control Display Unit==
[[File:Omega95-cdu-boeing-787-8.jpeg|300px|thumb|Boeing 787-8 Dreamliner Control Display Unit]]

A new [[Control Display Unit]] (CDU) specifically built for the Boeing 787-8 replaces the generic Boeing CDU and lets you control many of the configurations and settings on the aircraft like VNAV Cruise Settings, the flight plan (with VNAV altitudes,jump to, activate and remove features), Fly-By-Wire Configuration, Departure/Arrival Settings, Electronic Flight Bag (EFB) input etc.

The forum topic for the Boeing 787-8 CDU development can be found in [http://forum.flightgear.org/viewtopic.php?f=18&t=15082 this forum topic].

'''Functions Accessible through the Control Display Unit:'''
*Electronic Flight Bag Input
*Fly-by-wire Configuration
*Vertical Navigation Configuration
*Flight(plan) Management Computer
*Automatic Hold Configuration
*Set Terminal Procedures
*Flight Logging System
*Take-off and Approach Reference Speeds (keeps calculation according to weight)

==Vertical Situation Display==

[[File:Omega95-vsd-instrument.jpeg|300px|thumb|Boeing 787-8 Vertical Situation Display]]

A Vertical Situation Display [http://hoeprr.home.xs4all.nl/DreamHC/Download/B737_VSD_Briefing.pdf] is an instrument, part of the Navigational Display (on the MFDs) that show the aircraft's Vertical Navigation Altitudes, Vertical Profile and projects the terrain in front of you. In the Boeing 787-8, it shows approaching terrain for up to 50 miles and also color codes the terrain regions on the basis of danger (red - increase altitude immediately; orange/yellow - advisory; white - safe). The view the Vertical Situation Display, go to the NAV page on any of the MFDs. Note that the VSD is not available on the full-screen ND (NAV page on 2 adjacent MFDs). The VSD is uses a series of Nasal and XML files (which some core developers make like to call 'Hacks') to get functionality of hard coded instruments.

The forum topic for the Vertical Situation Display Development can be found here. [http://forum.flightgear.org/viewtopic.php?f=30&t=15200]
Hooray is also working on a Wiki HowTo on implementing the VSD in nasal. [[Howto: Implement a Vertical Situation Display in Nasal]]

==New Navigation Display==

The Boeing 787-8 features a new Navigation Display (ND) which features the ability to plot the waypoints and connect them, like in the real ND. [[User:zakalawe]] has been working on a hard coded version of such a display but as we didn't get it at the time, we designed this instrument completely with nasal and XML interactions. Another feature on the Boeing 787-8 is the ability to show a larger Navigation display when both pages are set to NAV on the co-pilot's side MFDs. The larger full screen MFD shows more waypoints and the range can be adjusted between 1 nautical mile and 250 nautical miles. It also shows the airport diagram of the nearest airport positioned and rotated in the right configuration and can be seen better when the range is less than 10 nautical miles.

Another feature of the Boeing 787-8's Navigation Display is a very functional TCAS (Traffic Alert and Collision Avoidance System) which has also been designed completely in Nasal and XML and does not require wxradar to work.

==Electronic Flight Bag==

[[File:Omega95-efb-787.jpeg|300px|thumb|Boeing 787-8 Dreamliner Electronic Flight Bag]]

The Electronic Flight Bag (EFB) as the name says is like an electronic database of handy documents and charts. The Electronic Flight Bag on board the Boeing 787-8 can calculate the required amount of fuel for your flight, show any airport's (you can search using the EFB INPUT page on the CDU) information, like elevation, metar and runway information like heading, length, ILS frequency), connect to Virtual Star Alliance's Automatic PIREP System for more functionality, connect to Redneck's FGFSCopilot for logging, show the GPS settings (your position on the world map, course and true headings to your next way-point and distance to your next waypoint. It also has realistic checklists for every phase of the flight, and an operating manual explaining basic maneuvers. You can also "INSTALL" airport diagrams and charts into the '/787-8/EFB-DB' folder which allows you to view them on the CDU (searchable using the EFB INPUT page on the CDU).

===Quick Guide to install and view airport Diagrams===

> Download diagrams from any source, convert them to *.jpg format and rename them '<icao>.jpg'. Then, place them in the EFB-DB folder. Then, use the 'EFB INPUT' page on the CDU to enter the airport ICAO and it displays the diagram on the EFB.

===Quick Guide to install and view SIDs, STARs and IAPs===

* Download the chart you need from any source (I use http://www.airnav.com for US charts and http://www.opennav.com for others), and convert the chart to *.jpg format. (if it's pdf, a good idea is to open it in full view and take a screenshot :wink: )
* If the airport and chart type folder doesn't yet exist inside the EFB-DB/Charts folder, create them like (for example I want to install the 25L-ILS IAP chart for KLAX) /EFB-DB/Charts/KLAX/IAP/
* Now, rename your *.jpg file to the chart name (eg. 25L-ILS.jpg) and place it inside the '/EFB-DB/Charts/KLAX/IAP/' folder.
* Now, open the /EFB-DB/ChartsList.xml file and add in your chart data (use the older charts' data for the format)
* Start up the 787, go to the 'Airport Charts' page on the EFB, go to the 'EFB INPUT' page on the CDU and
** Enter the Airport ICAO and press on the button next to 'Airport ICAO (Enter)' label (or the space under it on the touch-screen CDU)
** Click on the button next to the 'Chart Type (Select)' label to cycle through SID, STAR and IAP
** Click on the button next to the 'Chart ID (select)' label to cycle through available charts.
** Now, hit the 'DISPLAY >' button on the CDU and look at the EFB to see your chart.

Note that for some charts, the orientation may be land-scape and not portrait. But to overcome that, I've put a 'ROTATE' option on the EFB which rotates the chart when you click it.

''The Above has been taken from the forum topic.''

===''Third-Party'' EFB Software===

The Electronic Flight Bag is also meant to provide and interface third-party and/or operating airline softwares. These are not present in the Flight Management Computer by default but we're working on a couple of ''softwares'' for the EFB. This is not ''unrealistic'' because this is one of the main purposes of the Electronic Flight Bag. Here're the ''softwares'' we're working on for the EFB.

====FGFSCopilot Logger====

The [[FGFSCopilot]] is a java program that can do almost everything required from taking off till landing the plane at your destination. The Boeing 787-8 has an FGFSCopilot Log page in the EFB which shows it's connection status and every log message the FGFSCopilot sends to FlightGear.

====VNAV Automatic Altitudes Generator====

The VNAV AutoGen is a third party software on the EFB that automatically calculates ideal vnav altitudes for the active route. To use it, simply create/load a flightplan, copy it to the active route, go to the VNAV Altitudes Gen page on the EFB and click on ''AUTOGEN >''. That would generate altitudes for you which're displayed on the EFB. You can scroll through the waypoints using ''SCROLL UP >'' and ''SCROLL DOWN >''. Finally, if you're happy with the automatically generated altitudes, click on ''COPY TO RTE >'' to move them to the active route.

==Fly-By-Wire System==

The Boeing 787-8 Dreamliner is FlightGear's first Airliner to feature a complete Fly-by-wire system. The idea behind this fly-by-wire is to get it the pilot's controls (/fdm/jsbsim/fcs/x-cmd-norm : where x can be aileron, rudder or elevator) and work with it and give out another output property (/fdm/jsbsim/fcs/x-fbw-output) which is read by the FDM and control surface animators. The throttles don't have a chain such as the other surfaces so that the pilot can easily override the fly-by-wire (one of Boeing's "philosophies"). At this stage, the fly-by-wire can protect the aircraft from extreme bank angles (flight envelope protection- roll) where the bank angle limit can be set by the pilot in the CDU's 'FBW CONFIG' page, protect the aircraft from extreme alpha angles (flight envelope protection- alpha), calculate the throttle required and set it accordingly to maintain profile on turns, reduce throttle to stay under limits and finally auto-stabilize the plane and maintain the current profile when the yoke is brought back to the center. The Fly-by-wire also dampens the control to prevent any sudden motion. Fly-by-wire can be toggled from the CDU's 'FBW CONFIG' page.

NOTE : To be able to activate alpha-protection, roll-protection and auto-stabilizer, you need to be atleast higher than 3500 feet. This is so that the fly-by-wire doesn't interrupt your approach.

We've also created a tutorial which shows how you can implement the fly-by-wire we wrote for your aircraft : [[Howto: Implement a Fly-By-Wire System for Airliners]]

==Automatic Vertical Navigation==

I've seen a lot of wiki pages on aircraft autopilot and always noticed that next to 'VNAV -' the author writes either he doesn't know what it is, or it doesn't do anything or he hasn't tested it yet. Well, for a change, here I'm telling you what the VNAV does.

We have designed the autopilot route manager in the CDU to be able to accept VNAV altitudes for each (or whichever you want) waypoint. On the Dialog Route Manager, enter your waypoint in the format 'WP@ALT' for example, 'KSFO@9000'. So let's say you have different altitudes according to your SID/STAR/IAP till cruise altitude and then different altitudes for your waypoints when you land. Let's assume your flight plan to be:
DEP, WP1@3500, WP2@10000, WP3@18000, WP4@26000, WP5, WP6, WP7, WP8, WP9, WP10, WP11@20000, WP12@12000, WP13@8500, WP14@4000, DEST

You doesn't have to enter altitudes for WP5 to WP10 because you'll start cruising at WP5 (say you want to cruise FL360 aka. 36000 ft) and stay at 36000 ft till WP10. That means WP11 will be your 'End Cruise' Waypoint, where you aim at when you're out of the cruise.

To set cruise settings, go to the CDU's 'VNAV' page and enter cruise altitude in the respective area. Then enter your cruise start altitude (in this case, WP5) and cruise end altitude (in this case, WP11) in their respective places (there're labels).

Once you're ready, finish other checklists, take off and turn on 'LNAV' and 'VNAV' on the Autopilot. The VNAV is designed to automatically calculate the required/ideal climb/descent rate to get to your waypoint just in time. Out of all the tests we've conducted, the VNAV is VERY accurate at the moment.

==Flight-plan Management System==

[[File:787-8-fpm.jpeg|300px|thumb|Boeing 787-8 Flightplan Manager]]

In the Feb 25th, 2012 git commit, a new flight-plan management system has been written for the Flight Management Computer(s). The new system, like the real one lets you put in 2 flight-plans (with altitudes), and an alternate airport. You can do everything that you can to the route manager on these 2 flightplans. Boeing likes to call them '''Primary Flightplan''' and '''Secondary Flightplan'''. Once you enter your primary and/or secondary flight-plan, the respective flight-plan's status will show ''READY'' on the flight-plan management page. Then, a new option, ''COPY TO RTE'' will appear under the respective flight-plan and on clicking that, that plan will be moved to the active route. To make any changes to the route, you can either make them to the flight-plan and copy them to the route again or simply work with the active route by clicking on the '''ACTIVE ROUTE''' option in the Flight-plan Management page. An alternate airport is recommended to be entered in the CDU so that in case there's a problem during flight, the plane can be automatically be diverted (by the FMC) without you having to do anything other than pressing the ''DIVERT'' option on the Flight-plan management page. Note that using the ''DIVERT'' button to divert to your alternate airport clears your active route and sets the aircraft on a direct flight to the Alternate Airport.

==Automatic Holding Pattern==

[[File:Boeing-787-8-auto-hold.jpeg|300px|thumb|Boeing 787-8 Automatic Holding as seen in the FlightGear Tracker]]

The Boeing 787-8 now features an automatic holding pattern system where you enter the hold fix/navaid, hold radial and hold leg time and the aircraft automatically, flies in a holding pattern there. (as described in real Instrument Flight Rules Rating Course (IFR) textbooks) This feature is still being developed at the moment and is not perfected, but it still does the basic thing for you.

We have tested this feature from KIAH (George Bush Intercontinental Airport, Houston) holding at the VOR, LOA (LEONA VORTAC, about 70 miles north-west of KIAH) at a hold radial of 0, and hold leg time 120 seconds. We've been able to hold and re-trace the hold path every lap, but we get a strange shape due to the pid-controller. We're still working on it.

==Traffic Alert and Collision Avoidance System==

[[File:787-8-TCAS.jpeg|300px|thumb|Boeing 787-8 Dreamliner TCAS]]

The Boeing 787-8 Dreamliner (as of February 21st, 2012 on GIT) features a brand new TCAS (Traffic Alert and Collision Avoidance System) which has a capability of showing 30 Multiplayer aircraft and 20 AI Aircraft on it! Now, you won't have to complain about not seeing all aircraft on VATSIM ;) We're still working on increasing it's capability to 50 each multi-player and AI.

The TCAS has 3 different symbols for each aircraft and 4 different color codes. Each aircrafts' callsign, altitude and true airspeed will also be written next to the sprite.

*The '''Diamond Shaped''' Aircraft sprite shows that the aircraft is ''flying level''.
*The '''Box with Up Arrow''' shows that the aircraft is ''climbing''.
*The '''Box with Down Arrow''' shows that the aircraft is ''descending''.

*A '''Cyan or Blue''' Colored Sprite shows that the aircraft is at a safe distance.
*A '''Yellow''' Colored sprite shows that you need to be aware of traffic nearby.
*A '''Orange''' Colored sprite shows that you need to either change altitude or course, consult ATC. It is an advisory.
*A '''Red''' Colored sprite shows that you are in danger and immediately need to follow the TCAS instructions.

The TCAS is configured to sound voice alerts according to the situation. The TCAS voice alerts needs to be followed over the ATC's instruction if they contradict. The TCAS will alert you if you are in danger of collision with MP or AI Aircraft.

''NOTE: The TCAS voice alerts have been confirmed working on FlightGear git (2.7, as of February 19th, 2012) but don't seem to work in FlightGear 2.4.''

==Terrain Map and Weather Radar==

[[File:787-8-terrain-map.jpeg|300px|thumb|Boeing 787-8 Dreamliner Terrain Map]]

The Boeing 787-8 Dreamliner (git version as of February 21st, 2012) features a terrain radar which creates a terrain map on the MFD when the Navigational Display is set to TERR mode (you can change the mode from the buttons on both sides of the Mode Control Panel). Click on WXR to view the WXRadar (Collins WXR-2100), TERR to view the Terrain Map and CLR to clear the ND. The weather radar is still under development and a working version is not available, but the terrain map uses a 'get little and interpolate' method to create smooth terrain mapping.

==World Map and Flight Path Plotter==

[[File:787-8-wmap.jpeg|300px|thumb|Boeing 787-8 Satellite Imaging]]

Another option to put on the ND is the world map. It's not exactly a terrain map, but rather like satellite imaging. The plane is shown (it's zoomed in) on the map and the plane's path is marked with fading red dots. You can get your ND to show the satellite maps by pressing the WMAP button on the ND mode panel. Note that you can have any 1 of WXR, TERR or WMAP on and to remove them, press the 'CLR' button.

==Airline Flight Management Computer==

[[File:787-8-fmc.jpeg|300px|thumb|Boeing 787-8 Flight Management Computer - FLIGHT INFO]]

The Boeing 787-8 Dreamliner is an Airliner and we can't leave out some of the key features airline manufacturers put in their aircraft. There're 2 major sections in the Flight Management Computer (it's a part of the CDU) - the ROUTE and DEP/ARR. Both pages are accessed from the CDU(s). The Route is directly connected to the Route Manager and doesn't do anything 'special', but the DEP/ARR page lets you work with preset routes, SIDs, STARs, IAPs etc. You can enter the flight number (this is meant for virtual airlines: By default, Merlion's Boeing 787-8 Routes are included in the Database but I'll make a tutorial on how other airlines can put in their data) and be able to search for the flight information. If the airline has specified a Route and/or VNAV Altitudes and Configuration, you can load up those preset routes and altitudes by pressing the 'SET ROUTE >' menu. If a preset route doesn't exist, the FMS will generate a route automatically. A pilot does not have to worry about preset/generated routes. Another feature in the FMC is Scott Hamilton's LevelD-767 NAVDATA Parser, which gets SID/STAR/IAP Data and automatically puts them in the right place in the route manager for you to be able to fly them. This data can be managed from the PROCEDURES option in the DEP/ARR page.

''A much more detailed tutorial of how to use preset routes and automatically set terminal procedures is available in the wiki sub-page: [[Boeing 787-8 Dreamliner: Flightplan and Procedures Tutorial]]''

''We'll also be creating a video tutorial (Dreamliner Tutorial #6) on the Flight Management Computer.''

===FMS Navigational and Terminal Procedures Data===

The Boeing 787-8 Dreamliner and the Airbus A380 (being developed by Scott Hamilton) uses Scott's Level-D 767 NAVDATA Parser to get Navigational Data and Terminal Procedures into the aircraft's Flight Management Computer (Flight Management System on the A380). The FMS Data can be downloaded as an extractable '''*.exe''' file from http://www.filestube.com/source.html?token=f6f36bf2e8d20ecb03ea but we also have FMS Data files for individual airports on Git with the Boeing 787-8 Project. Download specific Airport NavData XML files from the source tree of the ''git://gitorious.org/fg-boeing-787-8/fms-data.git'' repository. You can also download master as a '''*.tar.gz''' from https://gitorious.org/fg-boeing-787-8.

By default, the 787-8 contains navigational data for the following airport - WSSS, YBBN, KLAX, KJFK, EGKK for testing purposes and as the Flight Management Computer Tutorial is a flight from KLAX to KJFK.

== Work on the C++ front ==
The capabilities provided by this aircraft touch many parts of FlightGear, that will benefit from modifications to the C++ code, this is an attempt at documenting useful C++ work. Most of this should probably be posted to the issue tracker, too.

===Camera/Video Surveillance Instrument===

The Aircraft doesn't 'yet' have a camera/video surveillance instrument but the team is working on it. We are creating a Wiki [[Howto: Use a Camera View in an Instrument]] while working on it so our progress can help other aircraft developers. The basic idea is the render the camera view to texture and get flightgear to display it on the instrument. As this instrument includes work in C++, it will NOT be available in FlightGear 2.4.0 or 2.6.0, and not even git at the moment.

=== Creating a 2D drawing API ===
Also see [[Howto: Create a 2D drawing API for FlightGear]].

=== Increasing the range of geodinfo() ===

Fix geodinfo() so that it may provide access to tiles not yet loaded, i.e. tiles that are not "visible" (which is the limiting factor currently). This will also be useful for the local weather system and probably a number of related scripts.

{{cquote|The tile manager is capable of satisfying multiple requests. Anyone can give it a position, range and a timeout. It will then try to load all tiles in the range specified. And it will stop loading them after the timeout - unless you have updated the request with a new timeout. So you could tell it every 5 seconds that you're interested in a certain area around the aircraft, and use a timeout of 5,01 seconds. A matter of memory and loading speed though.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33348.html |title=Future Weather System |last=Brehm |first=Thorsten |work=FlightGear-devel mailinglist |date 1 August 2011}}</ref>|Thorsten Brehm}}

=Glass Cockpit=

[[File:Omega95-cockpit.jpeg|300px|thumb|Boeing 787-8 Glass Cockpit]]

The Boeing 787-8 Dreamliner has a very complete and realistic modern glass cockpit based of the real Boeing 787-8 cockpit. Almost all of the instruments (excl. Weather radar which is currently coming up, and the voice comm.) are functional and work like the real thing. Multiple views have been created (like the OHP, CDU, EFB, Full Cockpit Views) so that pilots can easily work on different parts without looking away and adjusting view position.

That's all I can say about the cockpit now... You better test it out to judge it.

=Systems Overview=

==Electrical System==

The Boeing 787-8 Dreamliner uses a modified version of Syd Adam's Jet Electrical System. Backup Generators have been added, a Ram Air Turbine Generator has been implemented and the APU loop has been modified. There are 5 major power sources available are:
* Engine Generators (L1 and R1 are main generators and L2 and R2 are backup)
* Battery
* Primary and Secondary External Power
* APU Generators (Auxiliary Power Unit must be started and running for the APU Generators to provide power)
* Ram Air Turbine (used in case of dual engine failures to provide just enough power for Central Hydraulic Systems (C1 and C2) and Instruments.

To Understand the Electrical System better, take a look at the 'ELEC' page on any of the MFDs on board.

==Hydraulic System==

The Hydraulic System on-board is very advanced and does the job it's supposed to do.
There are 3 basic Hydraulic Systems - Left Engine Hydraulics, Right Engine Hydraulics and Central Electrical Hydraulics. Both Left and Right Engine Hydraulic Systems are pressurized by Engine pumps which require the engines to be running. These pumps pressurize the L and R systems that are connected to the flaps, spoilers, brakes and landing gears. Therefore, you need atleast 1 of the 2 Engine pumps to be running to be able to use these. But, the landing gear has an 'alternate gravity drop system' which you can use to get your gear down in case of a hydraulic failure.
The Central System has 2 electric pumps that control pressure to the hydraulic system that controls the ailerons, rudder and elevators. Only 1 of the 2 pumps have to be turned on at a time, and the other can be used as backup in case of a failure. The hydraulic pumps can overheat and fault if not adequately cooled, refer to the 'Pneumatics and Air Conditioning System' for more information on this.

To Understand the Hydraulic System better, take a look at the 'HYD' page on any of the MFDs on board.

==Pneumatic System==

The Boeing 787-8's pneumatic and Air-conditioning system controls bleed and flow of air through packs (and trim) which are then used to cool the equipment on board. The pneumatic system is pretty simple, you have 2 packs, 2 trim air controls, a gasper, and engines and APU bleed. The 787's systems automatically control bleed according to what is required and available, but you'll have to control the trim and packs. Equipment Cooling is an option on the Pneumatics panel which passes cool air into the hydraulic and fuel pumps to prevent them from overheating. When a pump overheats, you get a warning and if you do not either turn it off or switch on equipment cooling, the pump can fault. The 'PNEU' page on the MFDs show you more information on equipment temperatures and Pneumatic settings.

==Fuel Control System==

The Fuel Control System let's you control the 7 fuel pumps on board the 787-8 Dreamliner (2 Left Tank Pumps, 2 Central Tank Pumps, 2 Right Tank Pumps and a Crossfeed pump). The left tank and central tank pumps pump fuel from these tanks to the left engine, while the right tank and central tank pumps pump fuel from these tanks to the right engine. In case of a fuel imbalance, you can turn on the crossfeed pumps to transfer fuel from the tank with excess fuel to the one with low fuel.

===Fuel Jettison===

The Aircraft has a complete fuel jettison system where you can select which wing nozzle to jettison from, arm jettison and use a knob to define the dump rate. If the Left Nozzle is activated and Fuel Jettison is armed, you dump fuel from the left and central tanks, and the same for the right nozzle. Note that the 787 will NOT let you dump fuel if you have less than a critical value.

==Heating System==

[[File:Omega95-window-heating.jpeg|300px|thumb|Ice starts building up on the windows if temperature is sub-zero and window heating is turned off.]]

The Heating System on board controls 4 different heating equipment. First of all, let's get into "natural icing".

===Natural Icing at certain Conditions===

If your TAT (Total Air Temperature) value is under 10, your wings, engines and wind shield can start picking up ice. Window Ice simply forms on the window and obstructs your view out of the cockpit. Whereas, wing ice actually affects your lift and drag in the FDM! As for engine ice, if you have extremely high amounts of ice, the engines can fault and you might have to cool and then restart them.

Note that Engine surges are NOT due to ice build up. If you get an engine surge while flying, you might either be flying over Vne, or in extreme weather conditions with N1 above safe limit in those conditions.

===The Aircraft's way of Taking care of Ice===

The '''Window Heating''' switches on the overhead panel enables a heater to start melting the ice on the windshield letting you see outside clearly.

The '''Anti-Ice''' knobs (2 engine knobs and a wing anti-ice knob) let you control the heating equipment on the respective areas.

The 'HEAT' page on the MFD should have more information on the Heating Systems.

==Gear System==

The Boeing 787-8 dreamliner has 3 retractable gear units, the nose gear has 2 tires, and the main landing gears have 4 each in a square layout. The gear system manages gear compression and failures (stuck, tires burst and break off) on the basis of airspeed, wow and compression.

The gears system can be monitored from the 'GEAR' page on the MFD(s).

==Ground Service Controls==

[[File:787-ground.jpeg|300px|thumb|Boeing 787-8 Ground Service Controls]]

[[File:787-ground_1.jpeg|300px|thumb|Boeing 787-8 Ground Services (Right)]]

[[File:787-ground_2.jpeg|300px|thumb|Boeing 787-8 Ground Services (Left)]]

===Fuel Truck===

The fuel truck (MENU: Boeing 787-8 > Fuel Truck Controls) can be enabled/disabled and connected/disconnected from the aircraft's fuel value under the wing. You can enter an amount of fuel in the request fuel quantity input and ask the truck to re-fuel the aircraft to that quantity. You can also ask it to drain the fuel tanks.

===De-icing Truck===

The de-icing truck along with the other ground services can be controls from the ''Ground Services Controls'' menu (MENU: Boeing 787-8 > Ground Services Controls). The de-icing truck can be enabled/disabled and you can also de-icing the aircraft. The de-icing process includes the truck animations and actually de-icing the aircraft!

===External Power Box===

The External Power box is a stand-alone generator that provides external power to the aircraft. When enabled, it is connected to the external power socked under the aircraft's left wing. Note that this needs to be enabled so that you get external power. When you start FlightGear, the external power will be enabled by default.

===Landing Gear Chokes===

Landing Gear chokes are triangular prism shaped blocks that're placed in front of and behind the landing gears to prevent the aircraft from moving. These chokes will also prevent the aircraft from moving in FlightGear and are enabled by default on start up. Note that to get the aircraft moving, you need to remove the parking brakes and chokes.

===Catering Truck===

The catering truck can be enabled/disabled and toggled. The ''Toggle Catering'' option is to lift/lower the catering box and connect to the the R1 Door. It doesn't do anything else.

===Baggage Ramp and Trailers===

These're just models and don't do anything at the moment.

==System Failure Simulation==

[[File:787-failures.jpeg|300px|thumb|Boeing 787-8 Failure Simulator]]

The aircraft has a built-in failure simulation dialog where you can get different systems to fail in different ways. The failure simulation dialog can do the following:
* Flame-out any of the engines
* Fail any of the engines
* Set any of the engines on fire
* Burst any of the Wheel Tyres
* Have a gear unit ''break-off''
* Stuck a gear unit in it's current position
* Fail individual hydraulic systems
* Overheat any of the hydraulic or fuel pumps
* Fault any of the hydraulic or fuel pumps

Other general failures like Electrical, Static etc. have not been implemented in this dialog as they can already be controlled with FlightGear's Generic System Failures dialog.

''NOTE: When you flame-out an engine, it can be restarted, but not in the case of a failure. Faults just means that the pump is too hot to function, but it can be restarted when cooled.''

'''IMPORTANT!'''
*In case of an engine surge, (this cannot be toggled by user as it requires certain weather conditions and N1 to occur) immediately reduce throttle and get the N1 under 65%. If you're flying too fast, try to slow down and avoidance extreme weather (heavy rain and snow) would be a nice idea if you want to prevent surges.
*In case of an engine fire, pull the respective engine's fire extinguisher lever (it's right behind the throttle quadrant) and cutoff fuel to that engine. If the fire persists and you don't extinguish it, the engine may face an explosion and severe damage will be inflicted, leaving that engine unusable (basically, you can't restart it)

=Virtual Copilot=

Johan G posted in the Boeing 787-8 Dreamliner Forum Topic:
''I really see why there could be a real need to have a copilot along when "flying in" the aircraft during pilot conversion.''

Basically, the systems are very complex that it might be difficult for just 1 person to control the plane and manage the systems. As an immediate solution, the virtual copilot can announce ref. speeds, control flap lever, control gear lever, control heating and pneumatics, set altimeter setting and engage thrust reverser's and spoilers on touchdown. You can select exactly what you want ''him'' to do in the Virtual Copilot Settings Dialog.

On the other hand, we're working on a new advanced dual control system which allows the copilot to completely control the aircraft and see all instruments over multiplayer.

=Downloading the 787-8=

The Boeing 787-8 Dreamliner is hosted in GIT and has been made into different kinds of releases so that users can download it according to what they need. In the Boeing 787-8's Git Project page [https://gitorious.org/fg-boeing-787-8], you can find 3 different Repositories:

==fg-boeing-787-8-main==

This is the main Aircraft repository on gitorious. It includes the bleeding edge version (''master'' branch), and different types of releases of the latest stable version (''stable_d'', ''stable_e'', and ''stable_f'' branches).

===master ''Bleeding Edge''===

The '''master''' branch on the fg-boeing-787-8-main repository contains the latest development version of the Aircraft. This contains everything that's there in the
authors' aircraft folder from when a commiter last pushed his changes.

'''Download master as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/master

===stable_d ''Default Database''===

The '''stable_d''' branch (''d'' for ''default database'') contains the latest stable release with the selected airport diagrams, charts and FMC navigation data. This is recommended for everyone but you can get the other releases according to your needs too.

'''Download stable_d as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_d

===stable_e ''Empty Database''===

The '''stable_e''' branch (''e'' for ''empty database'') contains the latest stable release of just the basic aircraft, including models, nasal, systems etc. but the EFB and FMC databases are empty. This is recommended for those with slow internet connections. If you get a better connection later, you can download the whole database only from the ''fg-boeing-787-8-data'' repository.

'''Download stable_e as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_e

===stable_f ''Full Database''===

The '''stable_f''' branch (''f'' for ''full database'') contains the latest stable release of the aircraft, default diagrams and charts and the complete FMC Datbase. This release especially features FMC navigation data for 3808 airports (all we have so far)! It's recommended only if you have a very good internet connection. (WARNING! 280+ MB)

'''Download stable_f as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_f

==fg-boeing-787-8-data==

The Data Repository contains all the available EFB and FMC Database files. All these files are also included in the ''stable_f'' releases, so if you have a ''stable_f'' release, you don't need to worry about this.

'''Download master as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-data/archive-tarball/master

==fg-boeing-787-8-devel==

If you're interested in helping develop this aircraft and join the team, you can download the files in this repository. These are not required for the running of the aircraft but include some files like wxradar files, dual control files etc.

'''Download master as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-devel/archive-tarball/master

==Cloning and Pulling==

Cloning and Pulling the 787-8 repositories are the same like every other git repository, including FlightGear. Once you clone/pull, you can select the branch you want using ''git checkout <master/stable_d/stable_e/stable_f>''

More information on using git is available at [[FlightGear And Git]].

=Aircraft of the month!=

{{#ev:youtube|WlzEoCsJvz4|480|auto}}

Thanks to Oscar [http://www.youtube.com/user/osjcag] for the amazing ''Aircraft of the Month Review Video'' for the Boeing 787-8 Dreamliner.

=Boeing 787-8 Wiki Sub-Pages=

* [[Boeing 787-8 Dreamliner: Operating Manual and Checklists]]
* [[Boeing 787-8 Dreamliner: Video Tutorials]]
* [[Boeing 787-8 Dreamliner: Control Display Unit Reference Manual]]
* [[Boeing 787-8 Dreamliner: Flightplan and Procedures Tutorial]]

=Aircraft Status and ToDo List=

==Flight Dynamics Model: 4==

* The Boeing 787-8 has a JSBSim FDM matching a lot of results from http://www.lissys.demon.co.uk/samp1/desmis.html
* We don't have more detailed test results. so we can't test everything yet. Once we get that, we need to tune the FDM further.

==Aircraft Systems: 5==

* The Aircraft has very advanced systems imitating realistic systems from the real 787.
* Random/Checkable Failures purposely haven't been implemented as random is never realistic. But Engine failures, ice etc. occur in the appropriate conditions.
* The 787-8 has very advanced instruments, flight management computer, hydraulic, electric, pneumatic, heating, fuel etc. systems.

==Cockpit and Instruments: 4==

* The cockpit is very detailed and most buttons are there and functional.
* The instrument displays are very advanced and functional, the ND could be replaced by a hard coded version though.
* A Camera View instrument is supposed to be there but isn't, but we're working on a hard coded camera view instrument.
* The aircraft uses textures extracted from pictures and ambient occlusions created with blender.
* The complete cockpit has been light-mapped and looks very good at night too.

==Model: 4==

* The model is still from the old 787-8, there's the basic model without a cabin, rods aren't yet complete either.
* The landing gears have been re-done and look a lot better now, but the model has a much better scope of improvement.
* The Model Rating has been taken right out of the old Boeing 787-8

=Related content=
There are plenty of tutorials and code snippets that were specifically created for this project, this is a list of all things related:

{{Appendix|all|
* {{Cite web|url=http://www.bristol.ac.uk/aerospace/msc/avadi/units/projects/ub2009f/group7/7878summarysheet.pdf |title=787-8 Summary Sheet |date=21 January 2009 |publisher=Department of Aerospace Engineering, University of Bristol }}
* {{Cite web|url=http://www.wpafb.af.mil/shared/media/document/AFD-090121-023.pdf |title=The Boeing 787 Aircraft |work=Air Force HSI |publisher=Wright-Patterson Air Force Base }}
* {{Cite web|url=http://www.boeing.com/commercial/aeromagazine/articles/qtr_4_07/AERO_Q407.pdf |title=AERO Quarterly |date=2007 |publisher=Boeing}}
----
{{references}}

'''Weather radar (wxradar)'''
* {{Cite web|url=http://www.smartcockpit.com/data/pdfs/flightops/aircraft/Collins_WXR-2100_Operator%27s_Guide.pdf |title=Collins WXR-2100 MultiScan™ Radar Fully Automatic Weather Radar |date=2003 |publisher=Rockwell Collins }}
* {{Cite web|url=http://www.ll.mit.edu/publications/journal/pdf/vol12_no2/12_2weatherradar.pdf |title=Weather Radar Development and Application Programs |last=Evans |first=James E. |coauthors=Weber, Mark E. |date=2000 |work=Lincoln Laboratory Journal}}
}}

[[File:787-8-cockpit-panorama.jpeg|800px|Panoramic View of the 787-8 Dreamliner Cockpit]]
{{boeing}}

[[Category:Airliners]]

Airbus A330-200

2014-03-01T18:04:45Z

EmmanuelFrance:

{{infobox Aircraft
|image = Airbus A330-200.png
|name = Airbus A330-200
|type = Airliner
|livery = JetStar, Virgin Australia, Strategic Airlines, Air Berlin, Airbus House
|liverydbid = 86
|authors = Sam Clancy, Omega Pilot
|fdm = YASim
|status = Under development
|fgname = a330-200
}}
The Airbus A330-200 is a shortened, longer-range variant of the [Airbus A330], which entered service in 1998. Typical range with 253 passengers in a three-class configuration is 13,400 km (7,200 nmi). The A330-200 is ten fuselage frames shorter than the original −300, with a length of 58.82 m (193 ft 0 in). In mid-2012, Airbus proposed another version of the −200 with the maximum gross weight increased by 2 t to 240 t. This version will have its range extended by 270 nmi and will carry 2.5 t more payload. It will see engine and aerodynamic improvements reducing its fuel burn by about 2%. It is planned to enter the service by mid-2015. In November 2012, it was announced that the gross weight is to be further increased to 242 t with the range extended by 350 mmi (over 238 t version).
As of January 2014, 588 of the −200s had been ordered, 524 of which had been delivered, with 517 aircraft in operation. The 2011 list price is $200.8 million. The −200 competes with the [[Boeing 767-300ER]] and to a lesser extent the 767-400ER as well as with new [[787 Dreamliner]]. The A330-200 is also available as an ultra-long-range corporate jet as the A330-200 Prestige.

==Real-life Specifications==

Dimensions
Length (m) 59.0
Wingspan (m) 60.3
Height (m) 17.9
Wing area (m2) 361.6
Weight
Maximum take-off weight (kg) 230 000 - 233 000
Maximum landing weight (kg) 182 000
Operating empty weight (kg) 120 500
Maximum zero fuel weight (kg) 170 000
Maximum payload (kg) 49 500
Standard fuel capacity (litres) 139 000
Performance
Range with max payload (km) 12 100
Cruise speed (km/h) 870
Maximum operating altitude (m) 12 500
Take-off field length (m) 2 220
Landing field length (m) 1 750
Engines
GE CF6-80E1A3,
2 x 72000 lb
P&W PW4168A,
2 x 68000 lb
R-R Trent 772,
2 x 71100 lb
Cabin Data
Passengers (1-class) 406
Passengers (2-class) 293
Passengers (3-class) 253
Cabin width (m) 5.28

{{Airbus}}

[[Category:Airliners]]

Supported Video Cards

2014-03-01T18:02:18Z

EmmanuelFrance:

{{Stub}}

= Video cards for flight simulation =

== General considerations ==

!!! Note: Legacy '''integrated 3D GPUs or video cards using less than 512MB of dedicated video memory for 3D graphics should be avoided''' for any high-end 3D simulations or hardcore gaming !!!

This page is meant to provide a list of those '''video cards''' that are known to have good [[OpenGL]] support to run the latest versions of [[FlightGear]], based on contents taken from [[Hardware Recommendations]]. Please help maintain this list so that fellow FlightGear users can more easily make hardware decisions.

When buying or updating a graphics card for a computer system, over 512MB of dedicated video memory (i.e. VRAM) is preferred for advanced 3D gaming, with at least 1024MB being recommended as of 08/2012.

Basically, you should be fine with any Nvidia or AMD/ATI products having 512-1024MB of *dedicated* video memory for 3D graphics. However, you need to take into account that some of the newer features in FlightGear may not work as expected or may not even work altogether with older hardware, especially Intel-based graphics card (GMA).

== Support for Unix-like operating systems ==

If you are using FlightGear with a Unix-like operating system (i.e. Linux, BSD, Solaris, SGI, etc.), check for the latest video driver that fully supports your graphics card or integrated GPU. When using free and open source drivers, support is generally better with AMD graphics cards than with nVidia products, because of differences in the manufacturers' policies towards providing documentation for their hardware. [https://en.wikipedia.org/wiki/Graphics_hardware_and_FOSS] [http://www.phoronix.com/scan.php?page=article&item=amd_nvidia_15way&num=1] As progress on the free drivers has been significant in recent months, try to stay as up to date as possible to get the best results. That means use most recent distribution versions instead of long term supported ones.
Given the fact that there are such alternate "proprietary" vs. "free" implementations, please mention the one you are using when adding cards to the list below.

== Graphic Cards recommended for FlightGear 2.10+ ==
=== NVIDIA ===
* Quadro K5000M
* Quadro K4000M
* Quadro K3000M
* Quadro 5010M
* Quadro 4000M
* Quadro 3000M
* Quadro K5000
* Quadro K4000
* Quadro K2000D
* Quadro K2000
* Quadro K600
* Quadro 6000
* Quadro 5000
* Quadro 4000
* Quadro 2000
* Quadro 600
* Quadro FX 5800
* Quadro FX 5600
* Quadro FX 4800
* Quadro FX 4600
* Quadro FX 3800
* Quadro FX 3700
* Quadro CX
* Quadro VX 200
* GeForce GTX TITAN
* GeForce GTX 780M
* GeForce GTX 770
* GeForce GTX 690
* GeForce GTX 680
* GeForce GTX 670
* GeForce GTX 660
* GeForce GTX 650
* GeForce GTX 590
* GeForce GTX 580
* GeForce GTX 570
* GeForce GTX 560
* GeForce GTX 555
* GeForce GTX 550 Ti
* GeForce GTX 480
* GeForce GTX 470
* GeForce GTX 465
* GeForce GTX 460
* GeForce GTS 450
* GeForce GTX 295
* GeForce GTX 285
* GeForce GTX 275
* GeForce GTX 260
* GeForce GTS 250
* GeForce 9800 GTX
* GeForce 8800 GTX

=== AMD/ATI ===
* FirePro S10000
* FirePro S9000
* FirePro S7000
* FirePro W9000
* FirePro W8000
* FirePro W7000
* FirePro W5000
* FirePro W600
* FirePro R5000
* FirePro V7900
* FirePro V5900
* FirePro V4900
* Radeon HD 7990
* Radeon HD 7970
* Radeon HD 7950
* Radeon HD 7870
* Radeon HD 7850
* Radeon HD 7770
* Radeon HD 7750
* Radeon HD 6990
* Radeon HD 6970
* Radeon HD 6950
* Radeon HD 6930
* Radeon HD 5970
* Radeon HD 5870
* Radeon HD 5850
* Radeon HD 5830
* Radeon HD 5670 (with free radeon driver, kernel 3.13, Mesa 10.1)
* Radeon HD 4870 X2
* Radeon HD 4850 X2
* Radeon HD 4870
* Radeon HD 4860
* Radeon HD 4850
* Radeon HD 4830
* Radeon HD 4770
* Radeon HD 4730
* Radeon X1950 (runs smoothly with free Radeon driver, version 6.14.4)

== Troubleshooting Rendering Issues ==

If you get strange visuals, disable shaders in the View > Rendering Options dialog.

For problems with graphics cards or GPUs, see [http://forum.flightgear.org/viewforum.php?f=37 FlightGear's Graphics support forum]

==== External links ====
* [[:wikipedia:Comparison of NVIDIA Graphics Processing Units|Comparison of NVIDIA Graphics Processing Units]]
* [[:wikipedia:Comparison of ATI Graphics Processing Units|Comparison of ATI Graphics Processing Units]]
* [[:wikipedia:Comparison of Intel graphics processing units|Comparison of Intel graphics processing units]]

== Related content ==
* [[Howto: Improve Framerates]]

[[Category:Hardware]]

Fr/Changelog 2.10

2014-03-01T17:57:37Z

EmmanuelFrance:

==Liste des changements de FlightGear 2.10==

L'équipe de développement de FlightGear est heureuse de vous annoncer la sortie de la version 2.10 de FlightGear, le simulateur de vol libre et gratuit. Cette nouvelle version comprend de nouvelles fonctionnalités passionnantes, des améliorations et des corrections d'anomalies. Les principales améliorations de cette version comprennent une plus grande facilité d'utilisation, un meilleur rendu du terrain et un système de rendu 2D complètement exploitable à partir de scripts.

Créé en 1997, FlightGear est développé par un groupe mondial de volontaires, qui se rejoignent autour d'une même ambition : celle de créer le simulateur de vol le plus réaliste possible, gratuit et libre d'utilisation, de modification et de distribution. FlightGear est utilisé dans le monde entier par des amateurs de simulation de vol, par la recherche universitaire et lors d'expositions interactives dans les musées.

FlightGear propose plus de 400 aéronefs, une base de données des scènes mondiale, un environnement multijoueurs, une modélisation détaillée du ciel, un système de modélisation des aéronefs ouvert et flexible, des options de réseau variées, une prise en charge des configurations multi-écrans, un langage de script puissant et une architecture ouverte. Mieux encore, étant libre, le simulateur appartient à la communauté et chacun est encouragé à contribuer.

Téléchargez FlightGear v2.10 gratuitement à l'adresse [http://www.flightgear.org FlightGear.org]

FlightGear - Volez librement !

=== Principales avancées dans cette version ===

'''Modularité avancée'''

Les améliorations de l'architecture introduits dans cette version signifient que les sous-systèmes comme le gestionnaire de trafic peuvent être arrêtés et redémarrés dynamiquement au sein d'une session de simulation. Dans les version futures, il est attendu que de plus en plus de sous-systèmes prendront en charge cette fonction, rendant FG plus évolutif et flexible pour des simulateurs distribués entre plusieurs machines.

'''Diffusion de la lumière atmosphérique'''

[[File:Light_scattering_dec12_05.jpg|thumb|400px|Au-dessus des Alpes en F-14b au crépuscule]]

La diffusion de la lumière atmosphérique ([[Atmospheric light scattering]]) est un cadre de rendu alternatif, mettant en oeuvre un brouillard dépendant de l'environnement exceptionnellement réaliste et des calculs d'illumination pour les nuages et le terrain. La simulation inclue les modèles d'illumination suivants :
* Rayleigh, Mie et diffusion multiple et diffuse de la lumière dans l'atmosphère, sur la brume et les nuages, pour une illumination atmosphérique plus réaliste.
* Simulation de la brume de sol volumétrique, qui varie en épaisseur horizontalement et verticalement..
* Courbes de lumière diffuse et ambiante réaliste pour les conditions de l'aube et du crépuscule, rendant les vols crépusculaires plus réalistes.
* Amélioration du vol VFR de nuit grâce à un modèle d'illumination lié à la lumière de la Lune.

Utilisé en combinaison avec la météo avancée, il fonctionne comme une simulation intégrée de l'environnement, au sein de laquelle les éléments individuels s'influencent mutuellement. Par exemple :
* les nuages et les vents sont influencés par la distribution de l'élévation du terrain
* les vents prédominants, les courbures du terrain et la stabilité des couches basses de l'atmosphère déterminent la forme des nuages visibles
* les couches nuageuses et la brume influencent la couleur et l'intensité des réflexions de la lumière
* les vents influencent les motifs des vagues sur l'eau
* la lumière au lever et au coucher du soleil dépendent de l'altitude et de la position, permettant l'apparition de phénomènes comme le reflet des Alpes ou des nuages fortement illuminés à haute altitude alors que le sol est sombre.

Pour les cartes graphiques les plus puissantes, le cadre de rendu comprend une texturation procédurale du terrain, ce qui apporte les fonctionnalités suivantes :
* Texturation du terrain dépendant de la pente du terrain, de manière à ce que les scènes donnent un meilleur rendu, avec moins d'artefacts liées au tuilage.
* Effets haute-résolution pour les textures en vue près du sol avec une résolution offrant jusqu'à 10 cm de détail et un effet de bosses pour les vols à basse altitude et une meilleure résolution de la profondeur.
* Les effets dus à l'environnement, comme l'humidité du terrain (y compris les flaques), la présence de poussières, de mousses et et neige. Le tout ajustable par l'utilisateur et respectant la pente du terrain lorsque cela est nécessaire.

''' Performances améliorées, occupation réduite de la mémoire'''

Le temps de démarrage et l'occupation de la mémoire ont été réduits grâce à l'implémentation d'un cache des données de navigation. Des réductions complémentaires de la mémoires ont été obtenues par une amélioration des bâtiments aléatoires. Le nombre d'images par secondes a été amélioré lors de l'utilisation des nuages 3D, particulièrement dans des conditions couvertes.

''' Facilité d'utilisation '''
[[File:Joystick Configuration Dialog.jpg|thumb|400px|Interface de configuration du joystick]]

Améliorer la facilité d'utilisation de FlightGear a été au centre des intérêts de plusieurs développeurs pour cette version. Les changements incluent :
* Un nouvel outil permettant la configuration du joystick directement depuis le simulateur, facilitant la configuration des joysticks pour les nouveaux utilisateurs comme ils le souhaitent et leur permettant de voler rapidement !
* La console Nasal a été améliorée pour permettre le copier/coller et faciliter le développement des scripts Nasal.
* La boîte de dialogue « A propos de » inclue dorénavant des informations système complémentaires, et la possibilité de copier l'information vers le bloc notes, facilitant et accélérant le diagnostic à distance des problèmes des utilisateurs.
* L'option de choix des aéroports affiche dorénavant une vue en hauteur de l'aéroport choisi. Ainsi, les utilisateurs peuvent prévisualiser leur futur emplacement, et cela facilite le choix de la bonne piste ou de la bonne position de parking.
* Les check-lists ont été introduites pour un certain nombre d'aéronefs.
* Un navigateur de documentation inclus dans le simulateur est dorénavant inclus, de manière à ce que les utilisateurs puissent visualiser de manière plus simple toute la documentation disponible dans le paquetage de base.
* Les interfaces utilisateur de configuration de la météo on été fusionnées et rationalisées en une seule interface météo, facilitant le choix d'un vol VFR par beau temps, ou une approche CAT III plus compliquée.
* Le suivi du vol peut dorénavant être affiché dans la carte présente dans le simulateur.
* Il est maintenant possible de sauvegarder les rejeux du vol dans un enregistreur de vol, l'éditer de manière externe pour ajouter un commentaire, et le rejouer comme un tutoriel, avec la possibilité pour l'utilisateur d'en prendre le contrôle à n'importe quelle phase.
* Le dialogue de configuration multijoueurs inclue dorénavant une liste générée dynamiquement de serveur multijoueurs actifs, facilitant l'accès à l'environnement multijoueurs mondial de FlightGear.

''' Internationalisation '''

FlightGear continue à profiter de contributions de par le monde.
* Le manuel FlightGear est dorénavant inclus en anglais et en français.
* Les messages système au démarrage sont disponibles en huit langues, tout comme les menus de premier niveau du simulateur.

''' Planification des vols et gestionnaires de routes '''

* Le gestionnaire de routes a dorénavant une meilleure prise en charge des procédures Navigraph.
* Les procédures SIDs et STARs générées automatiquement sont disponibles pour les aéroports pour lesquels les véritables procédures ne sont pas disponibles. Cela génère des approches directes plausibles et des points de cheminements réalistes basés sur la route d'approche.
* La fonction d'extension Nasal « Plan de vol » a été améliorée, permettant la récupération d'une représentation du plan de vol stocké dans le gestionnaire de routes. Il est maintenant possible d'afficher directement une image SVG pour chaque point de cheminement et de les connecter en utilisant des chemins OpenVG.

'''Système Canvas'''

[[File:Airport-selection-dialog.png|thumb|400px|Dialogue de sélection de l'aéroport, en utilisant Canvas pour rendre le diagramme de l'aéroport]]

Le système « Canvas » est le système de rendu 2D complètement scriptable de FlightGear, ce qui permet aux utilisateurs de créer facilement de nouveaux instruments, des collimateurs tête-haute et même des fenêtre de dialogue et des interfaces personnalisées en utilisant le langage intégré de FlightGear, le [[Nasal]] (qui ressemble beaucoup au JavaScript). Canvas peut également être utilisé pour la création d'affichages de cockpits « tout écran » comme les afficheurs de navigation et les autres MFD. Aucune de ces actions ne nécessite de reconstruire FlightGear à partir du code source ou d'écrire du code C++.

Les améliorations de Canvas dans cette version comprennent :
* une mise à jour du rendu mis à jour pour améliorer la performance dans des situations où une texture n'a pas besoin d'être redessinée ;
* la création de fenêtres d'interface, qui comprend des menus « popup » et des barres de menus ;
* fonction copier/coller native via deux fonctions d'extension [[Nasal]] ;
* des canevas intégrés, où un canevas peut comprendre des images créées par d'autres textures de canevas ;
* empilement de fenêtres ;
* images raster (les images vectorisées étaient déjà prises en charge)
* une gestion des événements d'interface graphique améliorée en utilisant osgGA
* un nouveau système de gestion des événements basée sur DOM

'''Rembrandt'''
[[File:Fgfs-rembrandt-old-timer.jpg|thumb|400px|Le style vieux film de Rembrandt]]

* Le [[Project Rembrandt|système de rendu Rembrandt]] a été étendu avec plusieurs filtres de post-traitement :
** une vision de nuit comprenant un grainage d'amplification et un champ de vision restreint
** un effet cinéma comprenant :
*** le vignettage
*** le décalage de couleurs, le sépia étant la valeur par défaut
*** la distorsion radiale (distorsion en « pelote à épingles » et « tonneau », avec compensation d'échelle)
*** L'aberration chromatique latérale (purple fringing)
*** Simulation de film ancien
* Des aéronefs additionnels ont été mis à jour pour prendre en charge les effets Rembrandt.

'''Améliorations liées au système d'intelligence artificielle'''
* Les décollages et atterrissages des aéronefs IA sont maintenant plus réalistes.
* Les ravitailleurs peuvent maintenant être localisés en utilisant le marqueur de cible du collimateur tête haute.

''' Textures régionales '''

En se basant sur le travail réalisé en 2.8.0, les zones suivantes ont maintenant des ensembles de textures particularisées aux régions pour un terrain plus réaliste.
* Caraïbes
* Europe occidentale
* Islande
* Amérique du sud tropicale

'''Mise en avant d'aéronefs nouveaux ou améliorés'''
* Le Boeing 777 a un cockpit amélioré, comprenant un PFD et un affichage de navigation.
* Le Dassault Mirage 2000-5 a reçu diverses améliorations au niveau des instruments, du HUD et de l'armement.
* Le Douglas A-4F Skyhawk a vu son FDM et son cockpit amélioré, comprenant un ordinateur de navigation et de suivi de terrain.
* Le Hawker Hurricane a un cockpit et un FDM amélioré.
* Le Mudry Cap 10B, un grand classique français d'acrobatie aérienne à deux sièges a été ajouté par l'équipe PAF.

'''Autres'''
* De nouveaux joysticks et des pédaliers sont prises en charge par défaut.

'''Correction d'anomalies'''
* Voir [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.10.0 notre outil de suivi d'anomalies] pour une liste exhaustive, bien qu'incomplète, de toutes les anomalies corrigées dans cette version.

[[Category:FlightGear changelogs]]

Fr/Changelog 3.0

2014-03-01T12:14:45Z

EmmanuelFrance:

{{Changelog 3.0}}
L'équipe de développement de FlightGear est ravie de vous annoncer la sortie de FlightGear version 3.0, le simulateur de vol libre et gratuit. Cette version contient de nombreuses nouvelles fonctionnalités qui valent le détour, ainsi que des améliorations et des corrections d'anomalies. Les principales évolutions de cette version sont l'intégration du client de communications vocales [[FGCom]] au sein du simulateur, l'amélioration du rendu de terrain, un chargement plus rapide du terrain et une plus grande facilité d'utilisation. Cette version correspond également à la sortie de la version 2.01 des scènes mondiales de FlightGear - des scènes grandement améliorées couvrant l'ensemble de la planète et comprenant les données routières issues du projet OpenStreetMap et des informations de terrain détaillées issues de différentes sources.

Depuis la sortie de FlightGear version 2.0.0 il y a exactement quatre ans, FlightGear a fortement développé :
* le système de rendu Rembrandt, qui offre des ombres et un éclairage rendus en temps réel
* une modélisation améliorée du ciel, comprenant le brouillard, et la brume proche du ciel
* un rendu du terrain grandement amélioré, avec un rendu du terrain particulier en fonction des régions, des bâtiments aléatoires, des effets de shader et un positionnement plus réaliste des objets et des arbres
* une simulation avancée des conditions météorologiques, comprenant des systèmes de fronts, de thermiques, d'ascendance et de formation des nuages se basant sur le relief des montagnes
* un chargement à la volée du terrain, inutile de charger le terrain avant votre vol
* un système multijoueurs intégré et des communications vocales permettant aux utilisateurs de rejoindre et quitter des sessions multijoueurs depuis le simulateur
* une plus grande facilité d'utilisation, avec une interface de configuration des joysticks intégrée, une carte
* un système de rendu en 2D sous forme de scripts, facilitant la création d'interfaces utilisateurs complexes, les cockpits entièrement numériques, et autres.

Créé en 1997, FlightGear est développé par un groupe mondial de volontaires, rassemblés ensemble par l'ambition commune de créer le simulateur de vol le plus réaliste possible, libre et gratuit d'utilisation, de modification et de distribution. FlightGear est utilisé dans le monde entier par les amateurs de simulation de vol, pour la chercher dans les universités et pour les expositions interactives dans les musées.

FlightGear comprend plus de 400 aéronefs, une base de données des scènes mondiale, un environnement multijoueurs, une modélisation détaillée du ciel, un système de modélisation des aéronefs flexible et ouvert, diverses options variées, une prise en compte des affichages multiples, un langage de script puissant et une architecture ouverte. Cerise sur le gâteau, étant un logiciel libre, le simulateur est la propriété de la communauté et chacun est invité à participer.

Télécharger FlightGear v3.0 gratuitement à l'adresse [http://www.flightgear.org FlightGear.org]

FlightGear - Volez en toute liberté !

=== Améliorations principales de cette version ===

'''Modélisation des aéronefs'''
* Tous les planeurs disposent maintenant de variomètres compensés d'énergie totale.

'''Rendu de l'environnement'''
* La couleurs de la mer est plus réaliste, grâce à l'utilisation d'une carte globale de la mer pour rendre l'eau peu profonde d'une couleur différente.
* Amélioration des textures des bâtiments aléatoires
* Améliorations au rendu Atmospheric Light Scattering (ALS) comprenant :
** un travail significatif pour obtenir une apparence plus naturelle des couches de brume ou de brouillard prenant en compte les variations d'altitude
** le rendu de l'atmosphère sous la couche la plus basse du brouillard prend maintenant la visibilité correspondante en considération, ce qui entraîne un horizon diffus
** la ligne d'horizon est dorénavant rendue avec des variations angulaires, simulant différentes extensions verticales de couches d'air au loin dans l'atmosphère
** le shader des vagues offrant un rendu du sillage généré par un navire a été porté vers ALS

'''Performance'''
* Le temps de chargement du terrain a été amélioré en différant le chargement des objets dans les scènes.

'''Facilité d'utilisation'''
* La touche Tab est utilisée pour passer d'un mode de souris à l'autre : contrôle de l'aéronef, de la vue, neutre
* [[TerraSync]] est pré-configuré et fonctionne tel quel sans configuration nécessaire de la part de l'utilisateur
* [[FGCom]], le client de communication vocale multijoueurs est dorénavant intégré dans FlightGear

''' Internationalisation '''
* Traduction en italien du manuel FlightGear.

''' Scènes'''
* Les scènes version 2.01 sont dorénavant disponibles, améliorant la précision de l'élévation, des routes et du terrain
* Mise à jour des données de navigation
* Des définitions de textures régionales ont été ajoutée pour la Scandinavie, la Corse et l’île d'Ascension.

'''Système Canvas'''

{{lang|en|FlightGear's fully scriptable 2D rendering system now includes improved APIs for creating maps and navigation displays amongst many other improvements.
People no longer need to have programming experience to add a working ND to their aircraft, it can now be all done by copying and pasting 30 lines of text and customizing a few properties. The so called MapStructure back-end handles efficient updating of all ND layers transparently.}}

'''Langage de script [[Nasal]]'''
* Des recherches spatiales complexes plus rapides
* Associations HTTP
* Une nouvelle librairie Nasal a été ajoutée pour prendre en charge des instruments de vol libre spécifiques. La librairie prend actuellement en charge les variomètres compensés d'énergie totale ainsi que les variomètres Netto, Super Netto (Relative) et de commande de vitesse.

'''Documentation'''
* La documentation au format PDF/LaTeX des entrailles du moteur Nasal (en langage C) a été ajoutée à [[$FG_ROOT]]/Docs.
* Une traduction en italien du manuel FlightGear est dorénavant disponible.

'''Aéronefs nouveaux à tester absolument : '''
* [[Robin DR400 Dauphin|Robin DR400 Dauphin 180ch]]
* CAP10C
* Boeing 707
* North American P-51D
* Boeing 777

'''Autres : '''
* De nouveaux joysticks et palonniers sont prise en charge directement :
** Logitech Flight System G940 (joystick, pédalier et manettes)

'''Correction d'anomalies'''

* Consultez [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D3.0 notre outil de gestion d'anomalies] pour une liste étendue, bien qu'incomplète, des anomalies corrigées dans cette version.

[[Category:FlightGear changelogs|3.0]]

Fr/Changelog 3.0

2014-03-01T12:11:55Z

EmmanuelFrance: use lang template, minor fixes, add links

{{Changelog 3.0}}
L'équipe de développement de FlightGear est ravie de vous annoncer la sortie de FlightGear version 3.0, le simulateur de vol libre et gratuit. Cette version contient de nombreuses nouvelles fonctionnalités qui valent le détour, ainsi que des améliorations et des corrections d'anomalies. Les principales évolutions de cette version sont l'intégration du client de communications vocales [[FGCom]] au sein du simulateur, l'amélioration du rendu de terrain, un chargement plus rapide du terrain et une plus grande facilité d'utilisation. Cette version correspond également à la sortie de la version 2.01 des scènes mondiales de FlightGear - des scènes grandement améliorées couvrant l'ensemble de la planète et comprenant les données routières issues du projet OpenStreetMap et des informations de terrain détaillées issues de différentes sources.

Depuis la sortie de FlightGear version 2.0.0 il y a exactement quatre ans, FlightGear a fortement développé :
* le système de rendu Rembrandt, qui offre des ombres et un éclairage rendus en temps réel
* une modélisation améliorée du ciel, comprenant le brouillard, et la brume proche du ciel
* un rendu du terrain grandement amélioré, avec un rendu du terrain particulier en fonction des régions, des bâtiments aléatoires, des effets de shader et un positionnement plus réaliste des objets et des arbres
* une simulation avancée des conditions météorologiques, comprenant des systèmes de fronts, de thermiques, d'ascendance et de formation des nuages se basant sur le relief des montagnes
* un chargement à la volée du terrain, inutile de charger le terrain avant votre vol
* un système multijoueurs intégré et des communications vocales permettant aux utilisateurs de rejoindre et quitter des sessions multijoueurs depuis le simulateur
* une plus grande facilité d'utilisation, avec une interface de configuration des joysticks intégrée, une carte
* un système de rendu en 2D sous forme de scripts, facilitant la création d'interfaces utilisateurs complexes, les cockpits entièrement numériques, et autres.

Créé en 1997, FlightGear est développé par un groupe mondial de volontaires, rassemblés ensemble par l'ambition commune de créer le simulateur de vol le plus réaliste possible, libre et gratuit d'utilisation, de modification et de distribution. FlightGear est utilisé dans le monde entier par les amateurs de simulation de vol, pour la chercher dans les universités et pour les expositions interactives dans les musées.

FlightGear comprend plus de 400 aéronefs, une base de données des scènes mondiale, un environnement multijoueurs, une modélisation détaillée du ciel, un système de modélisation des aéronefs flexible et ouvert, diverses options variées, une prise en compte des affichages multiples, un langage de script puissant et une architecture ouverte. Cerise sur le gâteau, étant un logiciel libre, le simulateur est la propriété de la communauté et chacun est invité à participer.

Télécharger FlightGear v3.0 gratuitement à l'adresse [http://www.flightgear.org FlightGear.org]

FlightGear - Volez en toute liberté !

=== Améliorations principales de cette version ===

'''Modélisation des aéronefs'''
* Tous les planeurs disposent maintenant de variomètres compensés d'énergie totale.

'''Rendu de l'environnement'''
* La couleurs de la mer est plus réaliste, grâce à l'utilisation d'une carte globale de la mer pour rendre l'eau peu profonde d'une couleur différente.
* Amélioration des textures des bâtiments aléatoires
* Améliorations au rendu Atmospheric Light Scattering (ALS) comprenant :
** un travail significatif pour obtenir une apparence plus naturelle des couches de brume ou de brouillard prenant en compte les variations d'altitude
** le rendu de l'atmosphère sous la couche la plus basse du brouillard prend maintenant la visibilité correspondante en considération, ce qui entraîne un horizon diffus
** la ligne d'horizon est dorénavant rendue avec des variations angulaires, simulant différentes extensions verticales de couches d'air au loin dans l'atmosphère
** le shader des vagues offrant un rendu du sillage généré par un navire a été porté vers ALS

'''Performance'''
* Le temps de chargement du terrain a été amélioré en différant le chargement des objets dans les scènes.

'''Facilité d'utilisation'''
* La touche Tab est utilisée pour passer d'un mode de souris à l'autre : contrôle de l'aéronef, de la vue, neutre
* [[TerraSync]] est pré-configuré et fonctionne tel quel sans configuration nécessaire de la part de l'utilisateur
* [[FGCom]], le client de communication vocale multijoueurs est dorénavant intégré dans FlightGear

''' Internationalisation '''
* Traduction en italien du manuel FlightGear.

''' Scènes'''
* Les scènes version 2.01 sont dorénavant disponibles, améliorant la précision de l'élévation, des routes et du terrain
* Mise à jour des données de navigation
* Des définitions de textures régionales ont été ajoutée pour la Scandinavie, la Corse et l’île d'Ascension.

'''Système Canvas'''

{{lang|en|FlightGear's fully scriptable 2D rendering system now includes improved APIs for creating maps and navigation displays amongst many other improvements.
People no longer need to have programming experience to add a working ND to their aircraft, it can now be all done by copying and pasting 30 lines of text and customizing a few properties. The so called MapStructure back-end handles efficient updating of all ND layers transparently.}}

'''Langage de script [[Nasal]]'''
* Des recherches spatiales complexes plus rapides
* Associations HTTP
* Une nouvelle librairie Nasal a été ajoutée pour prendre en charge des instruments de vol libre spécifiques. La librairie prend actuellement en charge les varios compensés d'énergie totale ainsi que les variomètres Netto, Super Netto (Relative) et de commande de vitesse.

'''Documentation'''
* La documentation au format PDF/LaTeX des entrailles du moteur Nasal (en langage C) a été ajoutée à $FG_ROOT/Docs.
* Une traduction en italien du manuel FlightGear est dorénavant disponible.

'''Aéronefs nouveaux à tester absolument : '''
* [[Robin DR400 Dauphin|Robin DR400 Dauphin 180ch]]
* CAP10C
* Boeing 707
* North American P-51D
* Boeing 777

'''Autres : '''
* De nouveaux joysticks et palonniers sont prise en charge directement :
** Logitech Flight System G940 (joystick, pédalier et manettes)

'''Correction d'anomalies'''

* Consultez [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D3.0 notre outil de gestion d'anomalies] pour une liste étendue, bien qu'incomplète, des anomalies corrigées dans cette version.

[[Category:FlightGear changelogs|3.0]]

Template:Lang

2014-03-01T12:10:40Z

EmmanuelFrance: - categories (and documentation)

{{{2}}}

Template:Lang

2014-03-01T12:07:26Z

EmmanuelFrance: create this template frow en:wikipedia

{{{2}}}{{category handler
|main = [[Category:Articles containing {{#switch:{{{1|}}}
|en|eng = explicitly cited English
|#default = {{#ifexist:Category:Articles containing {{ISO 639 name|{{{1|}}}}}-language text
|{{ISO 639 name|{{{1|}}}}}
|non-English
}}
}}-language text]]
|nocat = {{{nocat|}}}
}}