FlightGear wiki - User contributions [en]

FlightGear Newsletter June 2015

2015-06-02T13:04:37Z

Sa7k: fix typo

{{draft|newsletter|Please feel free to add content you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter May 2015]].}}

{{Newsletter-header|June 2015}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}} 
[[#Space Shuttle|Space Shuttle developement]] 
{{Newsletter-cover-header|Scenery Corner}} 
[[#Großenhain Airfield|Großenhain Airfield]] 
{{Newsletter-cover-header|Community News}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]]
|}</div>

== Development News ==

== In the Hangar ==
=== Space Shuttle ===
Jajpreja is now modelling the landing gear for the Shuttle.
[[File:Spaceshuttlegear.png|200px|center]]

== Scenery Corner ==

=== Großenhain Airfield ===
[[File:FGFS_EDAK_APRON_2015.jpg|600px|Apron of [[Grossenhain_Airfield|Großenhain Airfield]]]] 
Custom [http://www.mediafire.com/download/d0rb8ko7864t4cu/FGscenery_Saxony.zip FGscenery_Saxony] package has new content. For [[Grossenhain Airfield]] (EDAK) the package contains a custom airport layout (scenery tile), static buildings and airport data. You can download this custom scenery file from the [[Grossenhain_Airfield#Scenery_Add-on|Grossenhain Airfield]] wiki page. 
We wish you happy flying! 

=== New Regional Textures ===
This project aims to create new regional textures, particularly for the Southern Hemisphere. Currently, the whole Africa (desert, savanna, rainforest and Mediterranean regions) as well as parts of South America (rainforest) and Southeast Asia (rainforest) have new textures and materials (including new urban textures). Repository link: https://github.com/gilbertohasnofb/new-regional-textures and development thread: http://forum.flightgear.org/viewtopic.php?f=5&t=26031
[[File:New_Regional_Textures.jpg|900px|center]]

== Community News ==

== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

[[Category:FlightGear Newsletter|2015 05]]
[[Category:Changes after 3.4]]

FlightGear Newsletter May 2015

2015-06-02T13:02:06Z

Sa7k: fix typo

{{Newsletter-header|May 2015}}
<div style="border-bottom: 3px double #bbb;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
[[#Exhaust flames|Exhaust flames]] 
[[#Automated checklist execution|Automated checklist execution]] 
[[#Submodel enhancements|Submodel enhancements]] 
[[#Sound position fixes|Sound position fixes]] 
[[#Nasal/Canvas: A simple tiled map|Nasal/Canvas: A simple tiled map]] 
[[#New ATC-pie release|New ATC-pie release]] 
[[#Cross-compiling FlightGear|Cross-compiling FlightGear]]
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}} 
[[#Amphibious variant of the C172p|Amphibious variant of the C172p]] 
{{Newsletter-cover-header|Scenery Corner}} 
[[#Scenery Project Elba|Scenery Project Elba]] 
[[#SVMI Release 1.0|SVMI Release 1.0]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]]
|}</div>

== Development News ==
=== Exhaust flames ===
The latest addition to the Atmospheric Light Scattering framework is a procedural shader effect to render thruster and afterburner exhaust flames. This effect integrates over a 3d-distribution of glowing emitters in a bounding box, which means that it doesn't generate sharp edges in the visuals.

Flame color, density, distribution of shock diamonds and widening in thin atmosphere are all runtime configurable, allowing to account realistically for changes in thrust or ambient pressure.

In the example application for the [[SpaceShuttle - Project Overview|Space Shuttle]] main engine below, note how the exhaust plume is narrow and shows pronounced shock diamonds early on, while it widens in the thin upper atmosphere.

''Find out more at [[ALS technical notes#The exhaust flame effect]]…''

[[File:Shuttle flame05.jpg|400px|Space Shuttle main engine flames during early ascent]]
[[File:Shuttle flame06.jpg|400px|Space Shuttle main engine flames during late ascent]]

=== Automated checklist execution ===
{{FGCquote
|As part of the development of the Lockheed 1049h Constellation, I created a comprehensive set of checklists based on the crew operating manual with other items added sufficient to take the aircraft through all stages of flight. Rather than hand-code an autostart script I wrote a more generic script to run checklist bindings in sequence. This script is now available in FGDATA and can be used on other aircraft: 
 
[[Aircraft_Checklists#Automated_checklist_execution|Wiki: Automated Checklist Execution]] 
 
If you are thinking about writing an autostart menu, you might want to consider using this script and driving the autostart from the checklists. It's not restricted to autostart, you can essentially run any sequence of checklists from any piece of Nasal code. 
 
You can see the script in action in the latest [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/Lockheed1049h/ Lockheed 1049h]. Note that you need a recent copy of [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/ FGDATA] for this to work. The autostart in this case is intelligent enough to run different checklist sequences depending on whether you are starting on a runway, at the terminal or in the air and also uses automated checklist execution to run an "After Landing" checklist from a keyboard shortcut during that busy time of rollout and taxi.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=241203&sid=4bad6d92dab1d411ea46e6efb1b8850c#p241203
|title=<nowiki>Automated Checklist Execution</nowiki>
|author=<nowiki>sanhozay</nowiki>
|date=<nowiki>Fri May 01</nowiki>
}}
}}

=== Submodel enhancements ===
Thanks to some brilliant work on the [[Submodels|submodel]] system by Onox, it is now possible to adjust various offsets, including heading and pitch, during runtime. Furthermore, the x, y, and z offsets are also now defined in metric units. Finally, the randomness of the azimuth (heading), elevation (pitch), Cd (Coefficient of drag), and life can be defined. You can find out more at [[Howto:Add submodels]].

[[File:Submodel-offset.png|800px|A Phalanx CIWS shooting at an extraterrestrial weather balloon. The orange tracer bullets are submodels. The red line is a scaled model representing the aiming orientation of the Phalanx.]]

=== Sound position fixes ===
The sound subsystem has been given some fixes so that the distance between the position of the current view and the sound's position is now computed more correctly.

=== Nasal/Canvas: A simple tiled map ===
Using the [[Canvas GUI]] and the Nasal HTTP module, you can make a simple tiled map (shown below) using images downloaded on the fly. You can find out more at [[Canvas Snippets#A simple tile map]].

[[File:Canvas - Tile map demo.png|800px|A simple, Canvas-based tile map which is centered around the aircraft.]]

=== New ATC-pie release ===
[[File:ATC-pie-logo.png|200px|left|ATC-pie logo.]]
[[ATC-pie]] now provides a '''solo training mode''' for ATCs. Using the same interface as the [[multiplayer]] game mode and an additional instruction pane, you can choose to play offline and control virtual aircraft as Tower, Approach, Departure, or any combination of those positions. As MP traffic still can be scarce in many occasions on our network, this new game mode can be a solution for you not to give up on a planned session and give yourself some challenge. Also, you may learn from it enough to make your own MP sessions more popular over the network!

The main features are:
* Free combination choice of APP, TWR and DEP control positions for custom training
* Handovers to and from virtual ATCs
* Instruction interface and pilot read back
* Adjustable difficulty (traffic density)
* Departure/arrival and [[ILS]]/visual balance options
* Configurable runways in use, entry and exit points

=== Cross-compiling FlightGear ===

{{FGCquote
|During the last two weeks, hamzaalloush and saiarcot895 have been making lots of progress using mxe/mingw to build Windows binaries on Linux. The mid-term goal here is to provide FG/osgEarth binaries for Windows end-users via cross-compiling on Linux, so that end-users no longer need to be able to patch & build FG from source, but can just download pre-compiled binaries for 3.4 (and probably 3.6 in a few months time).

We're looking for people with access to Linux/Windows to help with testing/developing cross-compiled binaries for Windows on Linux using the mxe toolchain.

If anybody wants to get involved, please leave your system specs (OS, distro) here - so that we can grow a list of people familiar with both, Linux and Windows (alternatively, emulation/virtualization via VirtualBox/Qemu etc) - for now, we are primarily looking for people familiar with building FG from source, and ideally also familiar with using git.

Note that most testing/development is currently taking place on Ubuntu 14.04 - so people on a different distro should be prepared to do some integration/porting work (e.g. matching packages etc).

Currently, we're able to cross-compile OpenSceneGraph and osgEarth on Linux for Windows and run most OSG/OsgEarth examples:
{{#ev:youtube|ddYyH5CYhAo|400|center}}
{{#ev:youtube|mTHhHMlTSAo|400|center}}
{{#ev:youtube|sfWVo5u_7lw|400|center}}

The next steps ahead are getting osgEarth.mk to compile/link via mxe, and creating corresponding simgear.mk/flightgear.mk for mxe, at which point we will investigate porting poweroftwo's autobuilder to use mxe for building a patched version of sg/fg including osgEarth support.

People familiar with cmake/autotools or gcc internals are obviously also invited to get involved :D

For details and updates, please refer to: [[Building_FlightGear_-_Cross_Compiling]]
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=244898#p244898
|title=<nowiki>Dual Linux/Windows users:Cross-compiling FG/osgEarth for Win</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun May 31</nowiki>
}}
}}

== In the Hangar ==
=== Amphibious variant of the C172p ===
The development of the c172-detailed continues; a new variant has been added with pontoons (optionally with wheels) so that it can land on water. This stunning aircraft will replace the old [[C172p]] in the upcoming FlightGear [[Changelog 3.6|3.6]]. You can follow the c172-detailed's progress on the forum [http://forum.flightgear.org/viewtopic.php?f=4&t=25157 development thread]

[[File:C172p-amphibious.jpg|800px|An amphibious variant of the C172p.]]

== Scenery Corner ==
=== Scenery Project Elba ===
The Scenery Project Elba has been started, aiming at improving the scenery of Elba, an island west of Italy. You can find out more on the [[Scenery Project Elba|wiki page]] and the forum [http://forum.flightgear.org/viewtopic.php?f=5&t=26138 development thread]. Contributions are welcome!

[[File:Elba.jpg|800px|center]]

=== SVMI Release 1.0 ===
[[Aeropuerto Internacional Simon Bolivar]] (SVMI) has been undergoing development since January by {{usr|legoboyvdlp}}, and now release 1.0 has arrived. This release features:
* New apt.dat 850 layout
* Corrected terrain (the hill north of 10/28 is now correct)
* Static planes
* Working [[Jetway|jetways]] (by viveFG)
* Beautiful models (by viveFG)
This project is released under the [[GNU GPL]], and will hopefully be included in World Scenery 2.0 via TerraSync! This airport may be downloaded from [https://www.github.com/legoboyvdlp/ProjectFlightGearScenery GitHub] along with [[TNCM]] which has been fixed by legoboyvdlp with a quick-n-dirty hack to stop flooding.

== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

[[Category:FlightGear Newsletter|2015 05]]
[[Category:Changes after 3.4]]

FlightGear Newsletter February 2014

2014-03-01T13:42:03Z

Sa7k: Fix some typos.

{{newsletter}}
{{TOC_right|limit=2}}

{{Newsletter being written}}
== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].

=== Advanced Weather ===

The Advanced Weather system has received a major upgrade, giving it the capability to draw clouds to whatever range is needed to the visible horizon (largest distance tested was 750 km from low Earth orbit).

The technique used for this utilizes so-called impostors, simple pre-generated texture sheets showing the contents of a 40x40 km weather tile from above in low resolution. Based on the current weather situation, impostors fill the range from the edge of the region where 3d clouds are simulated to the currently selected visibility range / cloud drawing range (whatever is lower). Since the impostors themselves are very simple models, the framerate impact is minimal and independent of the number of apparently visible clouds. A dedicated shader for Atmospheric Light Scattering takes care of matched lighting in low sun conditions.

On systems which can draw 3d clouds up to 80 km and support visibilities larger than that, this improves visuals at high altitude quite a bit.

[[File:Farclouds02.jpg|300px|[ Impostors for overcast clouds]]
[[File:Farclouds07.jpg|300px|[ Impostors for scattered clouds]]
[[File:Farclouds10.jpg|300px|[ Impostors for Cumulus clouds]]

The functionality is currently in an advanced proof of concept stage - METAR mode is not yet fully supported, and the placement algorithms may still be refined.

=== Point Lights exposed to Effects ===
Stuart committed a change that (finally) brings surface lights, including VASI/PAPI/taxi/runway etc. into the xml-defined Effects
framework. Kudos to Tim Moore for his original Effects work - it made it very straightforward to enhance with support for point sprites and a custom texture generator required.

The relevant effect is data/Effects/surface-lights.eff. It should allow development of ALS and Rembrandt variants.

Stuart also replaced some OSG color/normal binding calls that were removed in OSG3.2.0, apparently because they were slow. So, if your build fails, please check you've got a recent OSG build installed.

Please let us know if you see any issues with either change. And while at it, Stuart also fixed one of the longest-standing scenery glitches in FlightGear history[http://forum.flightgear.org/viewtopic.php?f=47&t=22168&p=202063#p202060].
Stuart and Thorsten also fixed the black halo that could previously be seen around point lights [https://gitorious.org/fg/fgdata/commit/eaaf816b772649d5b0826a1d0bdd166dbc5b968f].

A suitable ALS version of the runway lights is now well under way which fogs runway lighting consistently with the rest of the scene. Having the lights inside the shader has additional benefits - it allows to make them more responsive to the environment, in particular the lights are rendered harder and with a sparkle effect, the distance out to which they are visible changes with the level of ambient lights, and in fog lights acquire a halo due to Mie forward scattering.

[[File:Lights_als05.jpg|300px|[ Runway lights for ALS]]
[[File:Lights_als06.jpg|300px|[ Runway lights for ALS]]

=== osg::Simplifier ===
Stuart has just committed a new rendering option, which allow simplification of the terrain mesh at runtime using the osgUtil::Simplifier node
visitor. Many thanks to Clement for discovering this and providing the initial patch.

Driving by a new set of control properties under /sim/rendering/terrain/simplifier/ (some of which are exposed via the Rendering dialog), the Simplifier goes through the OSG terrain representation and simplifies the mesh. The idea is that frame-rates can be increased by reducing the terrain vertex count - I've seen the
total vertex count on startup at KRHV drop from 18M to 11M using the Simplifier.

You can configure the Simplifier to run on none, all, or far terrain (i.e. beyond /sim/rendering/static-log/rough).

As there's no such thing as a free lunch, you should be aware of the following quite significant limitations:
* Simplifying the mesh costs CPU. On my laptop it increases the load time for complex tiles around KSFO by up to 20 seconds _per_tile_.
* If you enable it for all terrain, you may notice that the height of objects is incorrect, as they are based on the real tile mesh rather than the simplified one. Depending on the Simplifier configuration and the terrain mesh, this may or may not be obvious!
* If you enable it only for far terrain, the tile is reloaded when you get within /sim/rendering/static-lod/rough of the tile edge. This
shouldn't affect your frame-rate, as it's done by the same PagedLOD that loads random objects, lights and trees.

Stuart didn't see any frame-rate increase using this method, but we know that some people are concerned about the memory-occupancy of the scene-graph with Scenery 2.0, and this may provide some benefit.

The option is not switched on by default - you shouldn't see any impact unless you decide to switch it on in the Rendering dialog.

If this provides a significant frame-rate improvement for people, it might be worth looking into generating the simplified mesh offline or caching it to disk.

===ATIS updates and a new comm-radio subsystem ===
Torsten has pushed a somewhat bigger patch to replace the current ATIS subsystem by something more configurable.
Along with that comes a new comm-radio subsystem to provide some information about the received station.

* With the new ATIS system it is now possible to code region and even airport specific atis styles. These styles are defined in FGDATA/ATC/atis.xml and FTDATA/ATC/atis/*.xml.

* The phraseology is no longer hardcoded but stored as localized strings in FGDATA/Translations/*/atc.xml (Currently, only english phraseology is
implemented).

* The ATIS is no longer generated from the weather at the current aircraft position but encoded from the METAR data for the tuned ATIS
station. For that, real-weather (live data in the gui) has to be selected. As a fallback, if no live weather data is configured, Torsten will
add the old behaviour soon.

* The comm-radio subsystem provides some geographic and station specific information about the nearest station for the given frequency. The
property tree under /instrumentation/comm[x] now shows e.g. distance, station name, station type, bearing, and airport id.

To make use of the new features, I have added a comm radio subsystem to
the generic instrumentation file at
FGDATA/Aircraft/Generic/generic-instrumentation.xml - however, if an
aircraft has defined it's own instrumentation set, please add the following
<syntaxhighlight lang="xml">
<comm-radio>
<name>comm</name>
<number>0</number>
</comm-radio>
</syntaxhighlight>
for the first comm radio and eventually more with increasing numbers.

Please report, if there are any broken features.

Torsten is planning to merge the radio implementation of the comm radio, the navradio and the newnavradio code so they all use the same codebase
wherever possible. Eventually, I'll also touch ATC/trafficcontrol.?xx to better integrate that into the radio code and remove the hardcoded phraseology.

Torsten is also planning to use parts of the radio propagation code from Adrian to provide a better computation of the signal quality.

=== Revised Nasal APIs: getprop()/setprop() ===

As of FlightGear 3.1, getprop()/setprop() arguments (those that form a path) can now be numeric to specify a index, so:
<syntaxhighlight lang="nasal">
getprop("canvas/by-index", "texture", 1, "name");
</syntaxhighlight>
: is now the same as:
<syntaxhighlight lang="nasal">
getprop("canvas/by-index/texture[1]/name");
</syntaxhighlight>
: (see [https://gitorious.org/fg/flightgear/commit/5eee5e42ae4f5cf56283b3bf5a3be46efc2b51c4 merge request 54] and [https://gitorious.org/fg/flightgear/commit/34ed79e5f88ffdfc5e651a1fe3e639cb8f4d3353 actual commit])

== Canvas: 2 years later ==

[[File:Anniversary4.png|left|600px|left]]

According to [https://www.gitorious.org/fg/flightgear/merge_requests/26 gitorious merge request #26], it's been 2 years now that [[Canvas]] (our property-driven 2D rendering API) made it into FlightGear, back in early 2012. Time to recap:

First of all, we'd like to use the opportunity to express our thanks to all the people involved in making it happen, first of all, obviously TheTom and Zakalawe the canvas core developers, who are going out of their way to ensure that base package developers can easily and efficiently use the Canvas, while also being extremely responsive on the forums whenever it comes to feature requests, or those -very rare- bug reports.

But then, let's also say thanks to all the early-adopters who are contributing to Canvas already, who are helping develop features that could previously only be developed by writing C++ code and rebuilding FlightGear from code, while still fully realizing that things may not yet be very stable, but very much evolving still.

As can be seen, Canvas is really boosting FlightGear development in many areas where FlightGear was previously lacking, no matter if it's GUI development or glass cockpit efforts like the recent ND and PFD efforts initiated by Gijs.

Back in early 2012, the Canvas prototype contained only support for osgText - meanwhile, it's been extended to support other rendering primitives, so called "Canvas Elements", such as OpenVG paths (vector graphics via ShivaVG), raster images and even a dedicated charting mode based on concepts borrowed from [[J661]]/ARINC 661, mithrandir3, as the J661 lead developer, and member of the ARINC 661 committee, is also to be thanked here, for going out of his way whenever we had questions about J661 and ARINC 661 and being so responsive.

Since then, Canvas has been extended to cover additional use-cases, such as for example dedicated event handling support - which will come in handy once we modernize our integrated GUI to get finally rid of PUI and all its limitations.

So, it's been two pretty intense years actually, we've seen some fairly significant contributions to the base package with as many as half a dozen of contributors working towards the same goals, e.g. a generic [[NavDisplay]] framework initiated by Gijs & Hyde, but also the generic [[MapStructure]] framework created by Philosopher. All of which really started out with Stuart's original adaption of the airport selection dialog, that added support for taxiway/runway overlays using Canvas, and which has meanwhile been refactored and generalized to come up with a totally aircraft-agnostic framework for creating reusable mapping layers, which can now even be used in GUI dialogs easily, typically requiring only a few lines of Nasal code.

And while these efforts are still very much in progress, their results are pretty tangible already - in fact, we've seen a handful of aircraft already adopting these new frameworks, and "early-birds" providing regular feedback via various channels. And FlightGear's Canvas system is even getting promoted in other places, including even the [http://forum.outerra.com/index.php?topic=2154.0 Outerra forum].

And then there were several other amazing contributions that didn't yet make it into dedicated frameworks, but that were at least very interesting prototypes, such as for example kuifje09's 2D plotting tool [[FGPlot]], which also solves a long-standing problem and feature request, i.e. plotting inside FlightGear, without requiring any external tools - which should come in handy for anybody interested in doing AP/FDM tuning. We do hope to also generalize things there, so that we can provide a framework dedicated to 2D plotting. And more recently, Philosopher has created a fairly impressive Nasal/Canvas piece of work: a fully interactive Nasal console, with a "Read Evaluate Print-Loop" (REPL).

Taking a step back, it's becoming obvious pretty quickly that [[Canvas]] is having a massive impact and touching many areas that were previously only really accessible to people familiar with C++, the FlightGear code base, OpenGL/OSG programming and, last but not least, git. We've seen additions to legacy GUI/instrumentation features that haven't really been maintained in over half a decade, so this is very encouraging, because such features are suddenly accessible to middleware developers, so that core development is no longer the bottleneck when it comes to adding new GUI/instrumentation features.

[[File:Anniversary3.png|right|600px]]

After doing some research in the archives of the devel list, it seems that the original "canvas properties" idea dates back to early 2003/late 2004 (shortly after Nasal scripting had been added), it was originally brought up by Harald Johnsen who was working on a dedicated FMC/CDU back then, and who was looking for a way to implement such features without having to rebuild FlightGear from source [http://www.mail-archive.com/flightgear-devel%40flightgear.org/msg26123.html] [http://www.mail-archive.com/flightgear-devel%40flightgear.org/msg26124.html].

In the years to come, the idea kept being brought up, rediscovered and even re-invented by several people - which goes to show that good ideas seem to prevail ultimately. According to the devel list archives, for over a decade, glass cockpit support in FlightGear has been described as "lacking" by even the most senior contributors back then, like David Megginson or Jim Wilson, and our existing PLIB/PUI based GUI described as "archaic at best". All this has now changed thanks to Canvas.

And appropriately enough, even today, the back-end in Canvas used for creating and rendering to an offscreen texture, is still based on the very "ODGauge" code that Harald Johnsen originally came up with, 10 years ago, when he coined the term "Owner-Drawn Gauge".

Thus, it's only fair that this particular newsletter covers quite a few Canvas related additions - the original goals of Canvas (making hardware accelerated 2D drawing possible without recompilation) have been pretty much accomplished already, probably 80-90% of our 2D drawing needs for cockpit/gui/HUD purposes can be implemented without having to go through any C++ changes or recompilation, and Canvas can be considered pretty much "feature-complete" there.

And even the new GUI is well on its way, and once there are some examples and tutorials available, it is foreseeable -given the impressive rate of growth of the wiki's Canvas portal- that we'll have base package developers ready and willing to step in to help with the implementation of GUI widgets.

In fact, we have now even started exploring new interesting ideas, such as using shaders and effects via Canvas, which may eventually even make it possible to implement cloud shadows outside [[Rembrandt]] by using a Nasal/Canvas/Effects approach for example.

Likewise, having support for effects/shaders would also mean that night vision effects could be implemented, as well as quite a few other things that weren't previously possible easily.

[[File:CanvasOverview02-2014.png|thumb]]

Besides, we've also been discussing exposing camera views (e.g. scenery view manager) or even the underlying rendering stages to Canvas, which is based on ideas originally brought up by FredB and Zan on the devel list when they were talking about exposing the Rembrandt renderer to Tim Moore's effects framework[http://www.mail-archive.com/flightgear-devel%40lists.sourceforge.net/msg36481.html], a feature which would make all kinds of fancy things possible via Canvas.

Another interesting idea that was recently raised on the forums was running Canvas on embedded hardware platforms like Raspberry PI by supporting OpenGL ES[http://forum.flightgear.org/viewtopic.php?f=71&t=21964], which could mean that all Canvas based systems (PFD, ND, HUDs, EICAS, dialogs) may eventually be supported on such devices (maybe in another 2 years from now ?).

Some of the things we'll be working on in the time to come include:

{{Canvas Frameworks}}

In addition, sooner or later, we'll need to look into writing a few parsers for our existing 2D panels code, HUDs and GUI dialogs, to turn those existing PropertyList XML files into Canvases. If you'd like to get involved in some way, please get in touch via the Canvas sub forum: {{forum|71|Canvas}}

However, even people interested in doing C++ development may want to check out Canvas, we've started a fairly comprehensive article on extending the Canvas system via custom C++ classes to add new features: [[Canvas Development]]

To sum it up, these are very exciting times for anybody interested in doing 2D graphics stuff with FlightGear, no matter if it's GUIs, MFDs or -soon- even effects and shaders. The last two years have brought immense novelties to FlightGear contributed by people who would not be able to contribute these features via C++ code.

We've probably seen more 2D rendering related novelties and future potential added via base package contributions in the last two years than in the previous decade of FlightGear development, all thanks to Canvas obviously. Due to the property-tree centric nature of Canvas, we also finally have a feasible approach towards supporting glass cockpits in multi-instance FlightGear setups such as those that are typically demonstrated during FSWeekend or LinuxTag, possibly using a simple Property Tree/HLA wrapper, maybe even just using the generic protocol or telnet for starters.

And maybe 2 years from now, things won't be restricted to 2D rendering anymore, but we may even be able to use Camera views as Canvas elements ? Just some food for thought ... Don't forget: In FlightGear you can '''be''' the change you want to see. Thanks to everybody involved in making it happen, and special thanks to Michat for creating two awesome anniversary logos !

=== Philosopher's fully interactive Nasal Console REPL ===
Philosopher has created a very cool [[Canvas]]-based, fully-interactive, Nasal Console with a real [http://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop REPL interpreter (Read-eval-print loop)]. See his gitorious clone (branch "nasal-console") for the code: [https://gitorious.org/fg/philosophers-fgdata/source/nasal-console:Nasal/console] - it's currently one file (which can even be copied into the existing [[Nasal Console]]) with a menubar entry (under "Debug") for easy access. You can also uncomment the [https://gitorious.org/fg/philosophers-fgdata/source/022bef27f05d4837d720f63c6507b47466ff2a59:Nasal/console/repl.nas#L436 last line] of the file to open it immediately. The dialog accepts user input in lines, and if it detects the user has completed a snippet, it executes the last code it's seen and prints a result of the expression on the same area. The most common way to continue input onto another line is to have an unclothed pair of braces/brackets/parentheses, but this REPL is unique in allowing unfinished expressions: blocks (e.g. just plain "if" on one line -- no condition, no body -- or "foreach (var e; list)" -- no body of the loop) and binary/prefix operators (e.g. "1 >", since that doesn't have a right side of the ">"). This however needs some work and tweaking, so it's always a WIP. The other big issue is the text styling -- the latest optimization leads to overlapping if a line of input/output is more than one line when wrapped. The output of print()/printlog()/etc. still goes to the startup OS terminal instead of the dialog. However, it still is useful for experimenting quickly -- ''quam celerrime revera''.

[[File:Interactive-Nasal-Console-REPL.png|600px|Philosopher's interactive Nasal console REPL]]
[[File:Interactive-Nasal-Console-REPL-Transparent-KSFO.png|600px|Now at KSFO with transparency enabled (no title bar/styling).]]

=== Copy & Paste Programming: A Compass Widget using Nasal/Canvas ===

Inspired by a a recent forum discussion, we thought that creating a compass widget would be a neat little project for someone interested in learning a bit more about Nasal and Canvas coding, and it should be possible to accomplish with less than 50-80 lines of code actually - there's a ton of stuff that you could reuse (SVG compass rose or an existing 2D panel texture), we have quite a few tutorials on Nasal, Canvas and Image processing (check the wiki). Furthermore, we have the long-term plan to eventually phase out the old 2D panel code and used a modernized [[Canvas]]-based version to help with [[Unifying the 2D rendering backend via canvas]]. Continue reading at [[Howto:Parsing 2D Instruments using the Canvas]]...

[[File:Canvas-Compass-Widget.png|thumb|A Nasal/Canvas based compass widget]]

Paste this into your [[Nasal Console]] and click Execute:
<syntaxhighlight lang="nasal">
var CanvasApplication = {
##
# constructor
new: func(x=300,y=200) {
var m = { parents: [CanvasApplication] };
m.dlg = canvas.Window.new([x,y],"dialog");
m.canvas = m.dlg.createCanvas().setColorBackground(1,1,1,0.5);
m.root = m.canvas.createGroup();
m.timer = maketimer(0.1, func m.update() );
m.init();
return m;
},

del: func me.timer.stop(),

update: func() {
var hdg=getprop("/orientation/heading-deg");
me.compass.setRotation(-hdg*D2R);
},

init: func() {
var filename = "/Aircraft/Instruments/gyro.xml";
var temp= io.read_properties(getprop("/sim/fg-root") ~ filename);
var layers = temp.getValues().layers.layer;

var z=100;
foreach(var layer; layers ) {
print("new layer:", layer.name);

# if it's not a texture, skip
if (!contains(layer, "texture")) continue;

# get a handle to the texture of the layer
var texture = layer.texture;

# create an image child for the texture
var child=me.root.createChild("image")
.setFile( texture.path )
.setSourceRect( texture.x1, texture.x2, texture.y1, texture.y2 )
.setSize(layer.w,layer.h)
.setTranslation(20,20)
.set("z-index", z +=1 )
.setScale(2.5);

if (layer.w != nil and layer.h != nil)
child.setCenter(layer.w/2, layer.h/2);

if (layer.name=="compass rose") {
print("Found compass layer");
# child.setCenter(55,55);
me.compass = child;
}
} # foreach

me.timer.start();
},
}; # end of CanvasApplication

var InstrumentWidget = {
new: func(x,y) {
var m = CanvasApplication.new(x:x,y:y);
},
};

var compass = InstrumentWidget.new(x:300, y:300);

print("Compass Loaded...!");
</syntaxhighlight>

=== Canvas & Shaders: A match made in Heaven ? ===

For quite a while, we've been thinking that at some point, the [[Canvas]] system could probably benefit from being also able to also use FlightGear's Effects/Shader framework, so that canvas textures can also be processed via effects and shaders optionally, before they get drawn. That should make all sorts of fancy effects possible, such as night vision cameras or thermal view, rendered to canvas textures/groups.

That would then disable the default rendering pipeline for those canvas textures and use shaders.

Basically, anything that's not directly possible via the core canvas system or via its Nasal wrappers, would then be handled via effects/shaders. So we would gain lots of flexibility, and performance benefits.

So if people really want to create really fancy textures or camera views, they could use effects/shaders then, which would keep the design truly generic, and it would ensure that there's no bloat introduced into the main canvas system.

We did have some discussions about supporting per-canvas (actually per canvas::Element) effects and shaders via properties recently, TheTom even mentioned a while ago that he is interested in supporting this at some point, especially given the number of projects that could be realized like that (FLIR, night vision, thermal imaging etc).

At the time of writing this (02/2014) the Canvas does not yet include any support for applying custom effects or [[Shaders]] to canvas elements or the whole canvas itself - however, supporting this is something that's been repeatedly discussed over time, so we're probably going to look into supporting this eventually[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37210.html].

Some very basic prototyping has already taken place and looks pretty encouraging:

<gallery mode=packed widths=150px heights=150px>
Canvas-glsl-support.png|airport selection dialog with a greyscale fragment shader applied to the canvas
Canvas-Fragment-Shader-red.png|a trivial fragment shader applied to a canvas (the original colors used in the Nasal code were not changed!)
Canvas-Fragment-Shader-circles.png|unmodified airport selection canvas with fragment shader applied
Canvas-Fragment-Shader-experiments.png|more canvas fragment shading experiments

</gallery>

Continue reading at [[Canvas_Development#Effects_.2F_Shaders|Canvas & Shaders]]

=== A MapStructure Debugger ===

[[File:MapStructure-ND-Profiling.png|thumb|MapStructure Debugger running a [[NavDisplay]] and profiling a few layers.]]

[[MapStructure]] is a [[Nasal]]-space framework (designed and maintained by Philosopher) for managing layers of symbols in Nasal/[[Canvas]]-based mapping displays, which can be used in both aircraft MFDs/instruments like the [[NavDisplay]] (ND) and GUI dialogs, like the airport selection or [[Map]] dialogs. MapStructure is all about separating the visualization of the map from the visualized data itself, and the way it is shown to, and controlled by, the user. MapStructure is designed as a Model/View/Controller (MVC) framework.

The MapStructure debugger is a simple GUI dialog intended to be used for debugging and benchmarking MapStructure-based charting layers. In its current form, it simply shows a NavDisplay inside the dialog with several layers enabled, including a 2D graph to benchmark each individual layer (such as APT, DME, FIX, TFC).
Currently, the dialog is fairly simple and pretty crude, the plotting code is entirely based on [[FGPlot]] and needs to be further generalized eventually (see Canvas Plotting Framework). However, so far it's actually working nicely and can help determine where time is spent, i.e. which layers are "expensive" compared to others.
In addition, the MapStructure debugger dialog can be used to easily test MapStructure-based maps/charts like Gijs' NavDisplay, without having to start up a complex aircraft like the 747-400 or 777-200ER. In other words, the ND can be easily tested by using the ufo or ogeL - which are usually up and running within ~10 seconds.

Continue reading at [[MapStructure Debugger]]...

=== Canvas System ===

The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&t=22014 FG Forum Topic]

=== JSBSim Ground Effects ===
This is a heads up for JSBSim aircraft maintainers that user their own
ground detection and handling code.
As of today JSBSim, just like YASim, supports ground effects like
bumpiness, solid-ground detection and adjusting of friction actors.

Actually JSBSim supports an extra feature, BOGEY contact points sink in
a non-solid ground surface but STRUCTURE contact point do not, making it
easy to define floats using STRUCTURE contact points.

In order not to pollute /fdm/jsbim too much I've added the following
properties:

/sim/fdm/surface/override-level
A user defined property which if defined and set to a something higher
than 0 will disable the JSBSim ground reactions code completely and the
following properties are set to false:
/sim/fdm/surface/active
/sim/fdm/surface/valid

Otherwise the following applies:
/sim/fdm/surface/active
* is set to true

/sim/fdm/surface/valid
* is set to true if there is a valid material available or set to false
otherwise (the material defaults are set).

The following properties are set to their respective values:

/fdm/jsbsim/ground/solid
* flag which defines if the surface is solid not

/fdm/jsbsim/ground/bumpiness
* defines the bumpiness factor

/fdm/jsbsim/ground/maximum-force-lbs
* maximum allowed force for this surface

/fdm/jsbsim/ground/rolling_friction-factor
* rolling friction factor - applies to rolling friction

/fdm/jsbsim/ground/static-friction-factor
* static friction factor - applies to static friction and dynamic friction

These properties are also set for the appropriate gear and contact units.

If you want to keep your old behaviour just set
sim/fdm/surface/override-level to 1 somewhere in the configuration
files, for Nasal this becomes:
setprop("sim/fdm/surface/override-level", 1);

I've updated the Nasal code for the following aircraft in the base package:
Aircraft/Alouette-III/Systems/terrain.nas
Aircraft/Cap10C/Nasal/cap10c.nas
Aircraft/DR400-dauphin/Nasal/dr400.nas
Aircraft/DR400/Nasal/dr400.nas
Aircraft/F-8E-Crusader/Systems/terrain.nas
Aircraft/JA37/Nasal/crash.nas
Aircraft/MiG-15/Nasal/MiG-15bis.nas
Aircraft/Noratlas/Systems/terrain.nas
Aircraft/P-38-Lightning/Systems/terrain.nas
Aircraft/PBY-Catalina/Systems/terrain.nas
Aircraft/PC-6/Nasal/pc6-b2h4.nas
Aircraft/SR71-BlackBird/Systems/terrain.nas
Aircraft/VMX22-Osprey/Nasal/terrain_under.nas
Aircraft/Short_Empire/Systems/mooring.nas

Not that some of these might actually be YASim aircraft but YASim will
just ignore the property.

=== Random Buildings ===

=== Project Rembrandt ===
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].

=== High Level Architecture ===

=== Usability Improvements ===

=== Getting involved as a programmer ===
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.

If you are interested in contributing as a core developer, please see [[Howto:Start core development]].

If you interested in other developing, i.e. not C++ but [[Nasal]] scripting and/or XML, there are some articles listed at [[:Category:Popular Community Requests]] that have been suggested, but not fully or partially implemented, and are "mentored efforts". That means that the community is looking for a hand in implementing them -- help from ''you'' -- but will also have more experienced developers willing to help you, for example by having tailored tutorials or even code snippets written for you. As mentioned in each page, please get in touch if you would like to help with one of those projects. In comparison to C/C++, Nasal is simpler and easier to learn quickly. It also doesn't require recompiling, which means that you can test and develop changes with a standard FlightGear release, i.e. off of the main download page. As long as you can run FlightGear, you can also run Nasal code and contribute. Many tutorials covering a wide range of projects are listed at [[Nasal]], so if you know a programming/scripting language already, or would like to try something new, go ahead: read, write, try and get involved! When it comes to Nasal scripting, playing around with different tutorials and code snippets is more important than being an experienced coder.

Of course, you're also free to work on whatever you want -- FlightGear as a community-driven doesn't tell people what to do, but welcomes any contributions from anybody, as long as they have acceptable quality and are free to be licensed under the GNU GPL. So if you have something you would like to contribute back to FlightGear, please get in touch! (Preferably using Gitorious for larger merge requests, and the forums or (core-) developer's mailing list to inform the developers of what you want to contribute back.) Changes contributed 6-8 weeks before a release will usually appear in the next release, so your changes can be spread across the world.

== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== '''Junkers Ju 390''' ====
'''Emmanuel BARANGER, (helijah)'''

The Junkers Ju 390 was a German aircraft intended to be used as a heavy transport, maritime patrol aircraft, and long-range bomber, a long-range derivative of the Ju 290. It was one of the aircraft designs submitted for the abortive Amerika Bomber project, along with the Messerschmitt Me 264, the Focke-Wulf Ta 400, the Heinkel He 277 (source Wikipedia)

[[File:Ju390-17.png|200px|The tail gets up during the opening of the bay]]
[[File:Ju390-18.png|200px|above the sea]]
[[File:Ju390-19.png|200px|flying]]
[[File:Ju390-20.png|200px|flying 2]]

You can now find it in my hangar and on GIT hoping that you like as much as I enjoyed doing it.

==== '''Aichi M6A "Seiran"''' ====
'''Emmanuel BARANGER, (helijah)'''

The Aichi M6A Seiran (晴嵐?, "Clear Sky Storm" or "Mist on a Fair Day") was a submarine-launched attack floatplane designed for the Imperial Japanese Navy during World War II. It was intended to operate from I-400 class submarines whose original mission was to conduct aerial attacks against the United States. (source Wikipedia)

[[File:Aichi M6A "Seiran".png|200px|On the water]]

You can now find it in my hangar and on GIT hoping that you like as much as I enjoyed doing it.

=== Updated aircraft ===

==== '''Sikorsky SH-60 Bravo Seahawk''' ====
'''James Cusick, (X7cusick8X)'''

[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]

The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast.

Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk!
The updates include:

Integrated Pushback

Selectable payloads

95% complete folding animation for carrier deck transit

New Liveries

FDM Fixes

and more

=== Liveries ===

== Scenery corner ==
A great work has been done this month for Spain, such as the city of Barcelona, with the addition of landmarks such as Sagrada Familia, Agbar tower and its airport. These updates are available using Terrasync.

=== Airports ===
List of updated airports (mostly in Spain, Brazil, and France):
* LEAB Albecete
* LEAT Alfes
* LEBG Burgos
* LEBL Barcelona - El Prat
* LECD La Cerdenya
* LECI Santa Cilia-Los Pirineos
* LECN Pinar de Castellon
* LEDA Lleida
* LEGE Girona
* LEHC Huescas/Pirineos
* LELL Sabadell
* LELN Leon
* LEPP Pamplona
* LERE Requena
* LESB Son Bonet
* LESL San Luis
* LESO San Sebastian
* LESU Seo de Urgel
* LETL Teruel Plata
* LEVD Valladollid
* LFLG Le Versoud
* LFRB Brest Bretagne
* LFRN Rennes St Jacques
* PHNL Honolulu Intl
* SBNF Ministro Victor Konder
* SBPK Pelotas
* SBRJ Santos Dumont Airport
* SBUR Uberaba
* SPAF Camana

=== Regional texturing ===

New regional texture definitions are now available on GIT for Ireland in the CORINE-landcover based WorldScenery 2.0. Enjoy the boglands of Connemara, or the hills and lakes of Kerry. With hires scenery and special textures, the Green Isle is now quite a nice place to explore.

The Ireland texture definitions have full support for procedural texturing and for the autumn coloring effect of ALS.

[[File:Eire02.jpg|300px| Connemara bog]]
[[File:Eire04.jpg|300px| Dingle peninsula]]
[[File:Eire05.jpg|300px| Kenmare bay]]

=== Models optimizations ===
Since a few months, works have been done on the scenery to clean existing models to make them lighter but keeping or even improving the overall quality. Among the tasks are deleting unseen faces, making face singled-sided, reducing texture size or removing unused alpha from texture.

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
== Aircraft reviews ==

== Wiki updates ==
=== Translators required ===
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}

== Community news ==
=== FlightGear on YouTube ===
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.

=== New tutorials and screencasts ===

=== FlightGear &diams; Cross-Country Tutorial II &diams; a VFR guide ===
[[File:Coverwiki2.jpg|250px|thumb|left]]
 It's almost been a year since the first release of Cross-Country Tutorial II. 
Now with '''version three point zero''' the document is better than ever in many aspects. 
Go to the respective FG Forum thread: http://forum.flightgear.org/viewtopic.php?f=72&t=19600 where you can: 
*download this tutorial
**find out more about it
***'''post your comments and suggestions'''
 coming up soon is the X-Country 2's own wiki page!
 
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].

=== YASim looking for a new maintainer ===

{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.

Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)

So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too,
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch.
Suggestions for that means in practice, are most welcome!

Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|James Turner}}

{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my
latencies here are measured in weeks.
Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=YASim and documentation
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}</ref>|Andy Ross}}

<references/>

=== Call for volunteers ===
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support

=== Did you know ===

[[Category:FlightGear Newsletter]]


[[Category:Changes after 3.00]]

FlightGear Git: data developers

2014-02-06T12:35:16Z

Sa7k: /* Authentication */ fix typo

{{Git}}
Anyone contributing data to FlightGear, like aircraft models, dialogs or textures, is a '''data developer'''. This article helps those in setting up a correct workflow, to ease the inclusion of their work into the simulator.

== Preparations ==
The steps described in this section are only required once, at the initialization of your development environment.

=== Cloning the repository ===
The first thing to do as a prospective developer is to [https://gitorious.org/users/new register at Gitorious] if you haven't already done so. This will enable you to publish your edits and have them incorporated into the main project.

After logging in, you can create a personal "clone" of the data repository. This clone is where you will be working in, without touching the main repository. To create a clone, navigate to the fgdata repository on https://gitorious.org/fg/ and click the [http://gitorious.org/fg/fgdata/clone Clone repository] button. In general the default name is fine, but you can change it to whatever you like. Gitorious will now clone the data repository. Due to the size of our repository, this can take some time.

=== Obtaining the data ===
Before you can start editing, you first need to retrieve the data to your computer. There are two ways to do this. At the time of writing the data repository is over 5 GB. Continuing an interrupted cloning of a repository is not supported within Git. Therefore, if you have a slow or unstable connection to the internet, it is recommended to [[#Bundle|download the bundle]].

For both approaches, Git must be installed. There is a lot of software available, but the following are often used:
* '''Mac:''' [http://code.google.com/p/git-osx-installer/ Git for OS X]
* '''Windows:''' [http://msysgit.github.io/ msysGit]

==== Single clone ====
# Create a directory on your computer where you'll be storing the data.
# Change into that folder.
# Clone the repository with the following command. This will create a <tt>/fgdata</tt> subfolder and put all the contents of the repository in there.
#:<code><nowiki>git clone git://gitorious.org/fg/fgdata.git</nowiki></code>

==== Bundle ====
For the FlightGear-data there is a [http://www.kernel.org/pub/software/scm/git/docs/git-bundle.html git-bundle] (snapshot) [http://mxchange.org:23456/file?info_hash=%BF%FF%AB%0C%16%BF%8Eg%B8%A0%CFw%01%0A%5D%8F%3F%81%96y torrent] ([http://mxchange.org:23456/ tracker]; [http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.md5 md5]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha1 sha1]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha512 sha512]) available. This way you can resume interrupted downloads. After unpacking it only a comparatively small amount of data has to be transferred from the git server to synchronize your repository. See also the Develop sections in [[FlightGear Git on Windows]].

# Create a directory on your computer where you'll be storing the data.
# Change into that folder.
# Do the following steps to extract the bundle and bring the repository up to date:
#:<code>git clone fgdata.bundle fgdata</code>
#:<code>cd fgdata</code>
#:<code>git checkout -b master-tmp</code>
#:<code>git remote rm origin</code>
#:<code><nowiki>git remote add origin git://mapserver.flightgear.org/fgdata</nowiki></code>
#:<code>git fetch origin</code>
#:<code>git branch --track master origin/master</code>
#:<code>git checkout master</code>
#:<code>git branch -D master-tmp</code>

You should be suspicious if based on the printed progress you estimate the data download during the fetch will exceed 1GB (assuming the bundle is not terribly outdated).

=== Authentication ===
In order to publish edits on Gitorious, you need to generate a secret key so you can be correctly identified.

# Navigate to your newly created fgdata directory and run:
#: <code>ssh-keygen</code>
# Enter the name of the file in which you prefer to save the key and press Enter.
# Enter your password/passphrase and press Enter. You'll have to do this twice.
# Your key is now being generated. Open the .pub file with an editor and copy the content.
# Visit your dashboard at Gitorious and navigate to "Manage SSH keys".
# Click the "Add SSH key" button and paste the content of the .pub file. Follow the instructions on the screen.
# Now run the following, again in your fgdata directory, with ''<url>'' as the line that you get by clicking SSH on your fgdata clone page at Gitorious (something like ''git@gitorious.org:~your/fg/yours-fgdata.git''):
#: <code>git remote set-url origin <url></code>

=== Obtaining the simulator ===
In order to test your work, you'll need the FlightGear version that matches the data. Since FlightGear is under constant development, data from Git does not work with previous releases. Fortunately obtaining the latest development version of the simulator is fairly straightforward for most operating systems.

* '''Mac:''' Download [http://flightgear.simpits.org:8080/job/FlightGear-mac/ the .dmg]
* '''Windows:''' Download the [http://flightgear.simpits.org:8080/job/Win32-installer-Cmake 32-bits] or [http://flightgear.simpits.org:8080/job/Win64-installer-Cmake 64-bits] installer and follow its instructions. Let it install the binary into a clean directory.

Point [[$FG_ROOT]] to your freshly obtained fgdata directory. When using [[FlightGear Launch Control|the launcher]], this can be done on the first page, previous from the aircraft selection.

== Making edits ==
It is recommended to split your new fgdata clone into separate local branches for your work. For instance, if you're working on the Boeing 747-400 and the aircraft reflection shader, you might create 2 branches named "747-400" and "reflect-shader". To do this, run the following commands:
:<code>git checkout master</code>
:<code>git checkout -b <branch name></code>
Then you can make your changes to the new local branch(es), which will make merge requests easier for both yourself and committers. To switch in between branches, simply use
:<code>git checkout <branch name></code>

== Publishing edits ==
To push local updates to your fgdata clone on Gitorious, perform the following steps:
# Switch to the branch that contains your edits:
#:<code>git checkout <branch name></code>
# List all the changed files:
#:<code>git status -- .</code>
# Now it's time to commit the changed files.
#* If you want to commit all changed files, run the following and type your commit message.
#*: <code>git commit -a</code>
#* If you only want to commit a selection of files, run the following:
#*: <code>git add <path/to/file></code> (for single files)
#*: <code>git add --all <path/to/folder></code> (to add all files within a certain folder)
#*: <code>git rm <path/to/file></code> (to remove files that you've removed)
#: Followed by
#:: <code>git commit -m "<commit message>"</code>
# Check if everything went fine, by loading Gitk:
#: <code>gitk</code>
# Finally, push the commit to your fgdata cloon Gitorious with the following command. Replace <code>YourUID</code> with your Gitorious account:
#: <code>git push git@gitorious.org:~YourUID/fg/YourUIDs-fgdata.git</code>

== Requesting edits to be merged ==
[[File:Create merge request at Gitorious.png|thumb|270px|Creating a merge request at Gitorious.]]
# Click the "Request merge" button on your fgdata clone page. Loading the next page can take a while, as it will list all commits of the past years!
# Once again write a short summary (could be the same as used with git commit), but this time, also write an explanation of your merge request (what does it do?). Make sure you set the target repository to fgdata, target branch to master and source branch to the local branch with your updates.
# Tick the box in front of your commit and click the "Create merge request" button.
# Everyone can see the pending request, but in order to make sure that your request gets looked at, you may contact a contributor. You can find a list of people on the right side of the [https://gitorious.org/fg/fgdata repository page].

Creating merge requests using this method literally means merging an entire branch into fgdata; this may not be desirable for some situations, such as small changes that only require one little commit. There's a neat method to only push certain commits to a merge request discussed by Anders Gidenstam [http://forum.flightgear.org/viewtopic.php?f=4&t=10392&start=45#p115747 on the FlightGear Forums].

[[Category:Git]]

World Scenery 2.0

2013-12-24T20:25:31Z

Sa7k: TerraSync has all the files now.

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

== 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 (LEVT, 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.

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

Template talk:LangSwitch

2013-11-28T19:11:58Z

Sa7k:

== Do this template change the way translation is done? ==
Hi, thanks Johan_G for your work. I would like to know if this template changes the way pages should be translated or I must just follow the instructions here [[Help:Translate]]. Thanks. [[User:Sa7k|Sa7k]] ([[User talk:Sa7k|talk]]) 12:45, 28 November 2013 (UTC)
: Hi,
: the translation process is still the same. This template should only be used in templates that are included on various (translated) pages. By using the switch, we can for example have a single {{tl|News}}, rather than {{tl|Fr/News}}, {{tl|Nl/News}} etc.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 14:24, 28 November 2013 (UTC)
: PS: I've just updated {{tl|News}} to use this template, so you can check it for a live example ;-)

::Thanks for bringing this confusion up, so we can clarify it. :-)

::I added a hatnote to the top of [[Help:Translate]] with a link to [[Help:Templates#Translating templates]] as well as tried to make it more clear in the template's documentation that the template is mainly meant for template translation.

::If you have any further questions, please do not hesitate to ask.
::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:18, 28 November 2013 (UTC)

::: Aaah, ok. Thanks both for explaining. [[User:Sa7k|Sa7k]] ([[User talk:Sa7k|talk]]) 19:11, 28 November 2013 (UTC)

Template talk:LangSwitch

2013-11-28T12:45:26Z

Sa7k: Question about translation workflow.

Hi, thanks Johan_G for your work. I would like to know if this template changes the way pages should be translated or I must just follow the instructions here [[http://wiki.flightgear.org/Help:Translate]]. Thanks. [[User:Sa7k|Sa7k]] ([[User talk:Sa7k|talk]]) 12:45, 28 November 2013 (UTC)

Pilatus PC-9M

2013-11-14T08:57:50Z

Sa7k: Fix link.

{{infobox Aircraft
|image = PC-9.png
|name = Pilatus PC-9
|type = basic/advanced trainer aircraft
|fdm = JSBSim
|status-fdm = 1
|status-systems = 2
|status-cockpit = 3
|status-model = 4
|authors = Petar Jedvaj, Ernest Teuscher, Hyde Yamakawa, David Culp and Erik Hoffman
|fgname = PC-9M
|download = http://www.fguk.eu/fguk-hangar/summary/4-military-piston/236-pilatus-pc-9m
|
}}
Pilatus PC-9M is a single-engine, low-wing tandem-seat turboprop training aircraft designed by Pilatus Aircraft in Switzerland.
{|
|__TOC__
|}

== Performance Data ==

Maximum Speed: 368 mph

Cruise Speed: 343 mph

Rate of climb: 4,090 ft/min

Service Ceiling: 37,992 ft

Stall Speed Gear/Flaps Up: 88 mph, Gear/Flaps Down: 77 mph

Range: 990 mi

== Aircraft help ==
* '''c''' - Canopy
* '''m''' - Nose wheel steering
* '''Ctrl+b''' - Air brake
* Click on engine panel to Start/Run/Abort or use Autostart in menu

== Liveries ==
* Bulgarian Air Force 664
* Croatian Air Force 051
* Croatian Air Force 057
* Irish Air Corps 264
* Mexican Air Force HB-HRI
* Royal Air Force of Oman
* Royal Canadian Air Force 123
* Slovenian Air Force 64

[[File:PC-9M-cockpit.png|thumb|250px|PC-9M cockpit]]
{{#ev:youtube|8HImjsaLutI}}

== Development status/Issues/Todo ==

Development status - IN DEVELOPMENT

* Detailed 3D model & textures
* Pilot models
* External animations
* Lights
* Particle system
* Crash detect system

Issues

* Rembrandt only version

Todo

* Cockpit textures
* Authentic instruments
* HUD implementation and weapon system (modernisation to Hudournik standard)

== External links ==
* [http://www.pilatus-aircraft.com Pilatus Aircraft]
* [http://en.wikipedia.org/wiki/Pilatus_PC-9 Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=10341 FlightGear Forum]

{{Pilatus Aircraft}}

[[Category:Military aircraft]]

Template talk:Affected by HLA

2013-10-19T22:38:40Z

Sa7k: Inquiry about word.

If this was not by Hooray I would have corrected. I'm probably wrong but I think in this case it would be "deprecated" and not "depreciated".
http://www.catb.org/~esr/jargon/html/D/deprecated.html [[User:Sa7k|Sa7k]] ([[User talk:Sa7k|talk]]) 22:38, 19 October 2013 (UTC)

Soaring

2013-10-02T19:04:44Z

Sa7k: Fix FAA link

[[File:Aerotow2.jpg|thumb|270px|[[Bocian]] being towed by a [[Piper J3 Cub]].]]
'''Gliding''' or '''soaring''' is a recreational activity and competitive air sport in which pilots fly unpowered [[aircraft]] known as gliders or sailplanes using naturally occurring currents of rising air in the atmosphere to remain airborne.<ref>{{cite web |url=http://en.wikipedia.org/wiki/Gliding |title=Gliding |work=Wikipedia }}</ref>

In a broader sense, this article covers how to enjoy flights with gliders, motorgliders, hanggliders and paragliders by understanding how to plan unpowered flights, how to set uo weather conditions for reasonable lift, how to launch gliders and how to make use of lifting airmasses.

Note on units: In many areas of the world, glider pilots use metric units and instruments show altitude in meters and velocity in m/s - we will in this article follow this convention.

== Basics of glider flight ==

Any aircraft in flight at constant airspeed must balance thrust against drag and lift against gravity. Usually, the engine supplies the required energy. A glider instead uses its altitude (i.e. potential energy) to overcome drag and gravity. Thus, from any given altitude, a glider can only get so far. The glide ratio determines how far a glider gets for losing altitude. A high-performance plane with a glide ratio of 1:50 for instance can cover 50 m for every meter altitude lost.

The glide ratio isn't a constant however but depends on the airspeed. Each glider has an optimum airspeed at which the glide ratio is maximal (usually between 90 and 120 km/h). The glider can fly faster, but this increases the sinkrate. The glider can also fly slower, and this decreases the sinkrate, but since the airspeed also drops, the glide ratio can still deviate from the optimum. In still air, a glider must thus be flown at its best glide ratio for best performance.

=== Influence of wind ===

Wind has a crucial influence on the glide ratio that can be achieved. Usually a glider pilot is interested if he will reach a certain location on the ground (a good airfield to land, a mountain pass to cross a range,...). Suppose we have 1000 m altitude to spare and an optimum glide ratio of 1:40 at 110 km/h - this means we would reach an airfield 40 km away. However, with a 40 km/h headwind our groundspeed will just be 70 km/h and thus the effective glide ratio will be reduced by 70/110 to about 1:25 even maintaining the optimum airspeed.

This can have dramatic consequences for hanggliders with much lower optimum speeds - a hangglider flying at 35 km/h against a 35 km/h headwind remains stationary in the air and has an effective glide ratio of zero - in order to get anywhere, it must fly faster. For slow gliders, it is crucial to factor in the wind direction and strength into any decision.

In general, in order to have the best effective glide ratio, one must fly somewhat above optimum speed against the wind and below optimum speed with the wind.

=== Influence of lift and sink ===

The vertical motion of air has likewise a pronounced influence on the effective glide ratio. Assume we're in an airmass rising at 0.5 m/s flying again at 110 km/h. This increases the glide ratio by 1/0.5 to 1:80 because we're actually sinking only 0.5 m/s. However, we can do better - suppose we reduce the airspeed to 70 km/h to get the sinkrate to 0.7 m/s. In still air, this would correspond to a glide ratio of 1:36, i.e. not worth doing. But since the air rises, efectively we sink only 0.2 m/s now, and so the glide ratio goes to about 1:125. The opposite is true in sinking air.

The rules derived from these examples are: Fly slower than optimum speed in rising air, faster than optimum speed in sinking air. If your minimum sinkrate is equal to the lift, you do not lose any energy at all. Consequently, in any airmass providing net lift, the glider is flown at the velocity of minimum sinkrate (which is always lower than the optimum speed) to maximize the altitude gain. This makes it also easier to fly tight turns in small thermals.

In practice, wind and lift tend to be variable and one doesn't calculate the glide ratio but just estimates based on experience.

== Sources of lift ==

There are three main sources of lift for gliders: Thermals, ridge lift and wave lift. All of them are (in principle) available in FlightGear, when using the [[A local weather system|advanced weather system]] (previously called "local weather").

=== Thermals ===

Convective clouds form when the sun heats up a thin layer of air in contact with the ground. As warm air is lighter than cold air, eventually the situation becomes unstable and pockets of air start rising, creating a column of lifting air, a thermal. If this column reaches above the condensation level, a Cumulus cap cloud forms, marking its position.

Glider pilots can enter the thermals and circle in them to gain altitude. A good thermal might have a radius of about 1000 m and provide 1 - 3 m/s of lift. However, where there is lift, there is also sink: thermals are usually surrounded by a region of sinking airmass, and the convective upward motion of air also creates turbulence.

[[File:Soaring_thermals01.jpg|400px|Strong Cumulus development indicating good thermals]]
[[File:Soaring_thermals02.jpg|400px|Entering a cap cloud reduces visibility dramatically]]

While the lift column reaches deep inside the cap cloud, a glider can usually only climb to the cloudbase. Entering the cap cloud is quite dangerous, as the visibility deteriorates rapidly and orientation can be completely lost. The Cumulonimbus clouds characteristic for thunderstorms have very powerful updrafts of air, but for obvious reasons (strong turbulence, possibility of hail and icing,...) they should not be used by glider pilots.

=== Ridge lift ===

When a sufficiently strong wind meets rising terrain, the airstream is forced upward and thus a lift component is created at the windward slopes of a range. However, behind the ridge, the airstream turns down into the valley, and thus at the leeward side of a range a strong sink appears. For sufficient ridge lift conditions, winds stronger than 10 kt need to be perpendicular to a slope. Stronger winds create stronger lift, but make flight planning in general more difficult (see above).

The region of lift is usually very close to the ground, so one has to stay dangerously close to possibly rugged terrain in order to get good ridge lift conditions.

[[File:Ridge_lift01.jpg|400px|Riding the ridge]]
[[File:Ridge_lift02.jpg|400px|Staying close to the ground to get ridge lift]]

=== Wave lift ===

When, in strong winds, the air descends behind a mountain range, it can 'bounce back' from the ground and form a pattern of rising and falling waves in the lee of a mountain range. These waves provide lift with almost no turbulence which can reach very high - more than 10 km altitude have been reached in waves.

Typically waves form well behind a significant mountain range in winds of 30 kt and above when the wind is roughly perpendicular to the mountain range. At the leading edge of the wave is a very turbulent 'rotor' region, and lense-shaped Lenticularis clouds indicate often the top region of the wave (the region of maximum lift is found before the Lenticularis).

Wave lift is difficult to find, but easy to fly - the region of lift is huge, there is no turbulence and one can simply hold the glider almost stationary against the wind while rising far above terrain and clouds.

== Setting up a glider flight ==

With a glider, it is a good idea to have a firm idea what you want to do before starting FlightGear, since you have to make some choices in the commandline. It's also not a bad idea to think about what type of lift you want to utilize - ridge lift is only available in mountain regions, you need to be able to reach it from your starting location and thermal lift is strongest in the afternoon and not available over open water.

=== Choosing the glider ===
[[FlightGear]] has several glider models

{{Gallery
|AirwaveXtreme150.jpg|[[Airwave Xtreme 150]]
|Bocian.jpg|[[SZD-9bis Bocian-1E|Bocian]]
|DG-101G_001.jpg|[[Glaser-Dirks DG-101G]]
|DG-300.jpg|[[Glaser-Dirks DG-300]]
|Paraglider.jpg|[[Paraglider]]
|Asw20.jpg|[[ASW-20 sailplane|Schleicher ASW-20]]
|Sgs233.jpg|[[Schweizer 2-33]]
|Ask13.jpg|[[ASK-13 sailplane|Schleicher ASK-13]]
}}

and in addition with the Scheibe "Falke" 25b also a motorglider.

=== Starting location ===

Not every glider can be started from a runway, so you may need to add extra statements to the commandline. One possibility is to start the glider in the air by adding altitude and airspeed like

--altitude=3000 --vc=70 --heading=180

to the commandline (this will initialize the glider at 3000 ft with a velocity of 70 kt with a heading of 180 degrees - note that the altitude is absolute altitude rather than above ground level and adjust as needed!).

Hanggliders and paragliders launch from mountains by running down a steep mountain slope till enough lift is generated. This means that you need to scout the terrain before and find a good loaction. A typical starting position may then be defined like

--lon=-122.4942234 --lat=37.6980674 --heading=270 –on-ground

(this is close to Half Moon Bay in the default scenery around San Francisco).

=== Launch methods ===

Most available gliders do not need to be initialized in the air but can be launched as in reality by either winch or aerotow.

==== Winch launches ====
Winch launches are currently available with the [[SZD-9bis Bocian-1E|Bocian]], the [[Schleicher ASK 21|ASK21]], the [[ASK-13 sailplane|ASK-13]] and the [[Glaser-Dirks_DG-101G|DG-101G]]. With the Bocian, it is possible to click in the scenery on a point where you would like to place a winch; with both, you can use Ctrl-w to place a winch directly in front of the glider. Press w to start the launch (in the ASK you need to hold it down) and, once at the top of the tow, release the cable with W. Refer to the aircraft-specific help for details.

==== Aerotows ====
For aerotows, two types are possible - AI or human pilot (via [[Howto: Multiplayer|multiplayer]]). To get an AI aerotow, select either the ASK, Bocian or DG-101G, choose KRHV as your airport and select the KRHV_towing_demo in the "Scenario" list box in [[FGRun]]. You should see a J3 Cub wobble its way towards you from a nearby taxiway, and pause close to your aircraft. Press control-o to hook on to it, and hold tight... the O key releases the cable.

For a multiplayer aerotow, you obviously need to arrange a tow with a human pilot - full instructions are available at [[doing aerotow over the net]].

The DG-101G implements a third type for aerotowing: a drag robot. To setup the drag robot press D. Then use the key sequenze as for AI aerotowing to attach to the drag robot. Then press d to start the robot.

==== From the ground ====

The JSBSim version of the airwaveXtreme is launched from the ground by running down a steep slope. Refer to the aircraft documentation and help for details.

==== In air ====

Gliders that use the [[UIUC]] FDM are not (yet) capable of winch or aerotow launches. For such gliders it is necessary to start in the air.

== Setting the weather ==

The next step is to configure weather. In reality, you would take a look at the weather and decide what is possible to do with a glider. In Flightgear, it is possible to choose the weather based on what you would like to do. Dependent on the weather system used, the steps are a bit different. In general, it is recommended to use Advanced Weather for glider flights.

=== Basic Weather ===

[[File:Pinzgauer.jpg|thumb|270px|[[Schleicher ASK 21]] gliding in the [[Pinzgauer Spaziergang]] thermals scenario]]
In Basic Weather, thermals and sinks can be used but must be defined individually in a thermal scenario file. To see how this is done it would be best to examine the file called <tt>[[$FG ROOT]]/AI/thermal_demo.xml</tt>, which sets up 11 thermals and 6 sinks around San Francisco Bay. To learn more about AI scenarios in general, see the related article called [[AI Systems]]. Note that the thermals and sinks exist independently of FlightGear's Basic Weather system, so it's possible to have cloud layers that don't match your thermal heights or thermals which do not move with the wind. To prevent this you may want to manually set the cloud layers to match your thermals and match AI-defined winds with the winds set in the weather. Also, cap clouds do not match the default clouds in shape.
If you'd like to discover the Austrian alpine region with AI thermals, you might want to read [[Pinzgauer Spaziergang]].

Ridge lift works well with Basic Weather. Typically winds should be chosen to be perpendicular to a slope between 10 and 20 kt for good ridge lift conditions. When using the wind layer interface, it is important to set not only the aloft winds but also the boundary layer winds to this value. This makes for a nasty landing, as the winds even close to touchdown in the valleys blow at full strength, but since ridge lift is only strong close to the terrain, a glider using ridge lift is almost always in the boundary layer zone, and if the boundary layer winds are reduced to get the landing conditions in the valleys right, ridge lift on the slopes collapses as well.

=== Advanced Weather ===

The [[A local weather system |Local Weather]] package (for Flightgear 2.0.x and 2.4.x) or Advanced Weather (2.6.x) has the option to automatically generate thermals along with the convective clouds. For this, the checkbox 'generate thermals' has to be selected. The slider 'thermal properties' modifies the behaviour of the thermals - for 'low convection' it will generate little turbulence, thermals with a large radius and only modest lift, for 'rough day' it will generate strong lift and turbulence in narrow thermals.

The convective cloud system generates rather realistic results:

* the number of thermals is maximal around noon and the strength of thermals is maximal in the early afternoon
* the probability to find a thermal depends on terrain - elevated points and surfaces which heat up well are more likely to generate thermals than ice or open water
* not every cloud has a thermal associated, not every thermal is usable
* sometimes blue thermals (i.e. without a cap cloud) are created

As a result, you will almost never find good soaring conditions early in the morning or strong thermals over the sea. Any 'high pressure' weather situation will generate at least some amount of convective clouds, low pressure situations usually do not.

In order to set up ridge lift, select wind model 'constant' and set the wind perpendicular to the slope with 10-20 kt. Advanced Weather computes the boundary layer dynamically dependent on terrain, as a result there will be a realistic reduction of windspeed for a landing in the valley but not at mountain slopes.

Advanced Weather has a working model for wave lift, but so far no way of automatically detecting the conditions which lead to a lee wave, thus in order to use it, some Nasal coding is required.

== Learn the theory ==
For those wishing to gain a more in-depth knowledge of correct glider operation, the [http://www.faa.gov/regulations_policies/handbooks_manuals/aircraft/glider_handbook/ FAA glider handbook] makes good reading.

== Related content ==
* [[Improving Glider Realism]]

{{Appendix}}

Talk:IAR 80

2013-08-29T19:41:01Z

Sa7k: Opinion

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

List of developed airports

2013-08-25T15:58:24Z

Sa7k: Fix grupofgbr links and typo

This page lists developed airports which are included in FlightGear if two conditions are fulfilled. Airports are listed here if
* at least one building or [[Signs|taxi signs]] have been placed
* the respective objects are represented in the [[FlightGear Scenery Database]].
Every improvement listed here can be downloaded using [[TerraSync]] and it will also be included in the next [[World Scenery]] release.

If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].

The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see
* the current airport layout with runways, taxiways and aprons
* red dots: static objects in the scenery database made especially for this airport
* dark red dots: shared models in the scenery database placed at this airport
* green dots: [[Signs|taxi signs]] placed at the airport

'''Note:''' You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.

== Airports ==

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Name !! style="background:#efefef" | Country !! style="background:#efefef" | Continent !! class="unsortable" style="background:#efefef" | Comment

|-
| [http://mapserver.flightgear.org/map/?lon=13.76716&lat=51.13277&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDC] || [[Dresden Airport]] || Germany || Europe || some models: tower, terminal, animated hangars etc. ''Everything published via TerraSync''

|-
| [http://mapserver.flightgear.org/map/?lon=8.56293&lat=50.03795&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

|-
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown

|-
| [http://mapserver.flightgear.org/map/?lon=13.40379&lat=52.47502&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Tower and terminal

|-
| [http://mapserver.flightgear.org/map/?lon=11.78609&lat=48.35378&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [http://mapserver.flightgear.org/map/?lon=12.23603&lat=51.42262&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modeled with [[Signs]]

|-
| [http://mapserver.flightgear.org/map/?lon=13.28992&lat=52.55917&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars

|-
| [http://mapserver.flightgear.org/map/?lon=10.71706&lat=53.80496&zoom=15&layers=B000000TFFFFTFFFTTFFF EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]

|-
| [http://mapserver.flightgear.org/map/?lon=7.16278&lat=50.76767&zoom=15&layers=B000000TFFFFTFFFTTFFF EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modeled

|-
| EEKE || Kuressaare Airport || Estonia || Europe ||

|-
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe ||

|-
| EETU || Tartu Airport || Estonia || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=25.04487&lat=60.25318&zoom=15&layers=B000000TFFFFTFFFTTFFF EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=24.95253&lat=60.3206&zoom=14&layers=B000000TFFFFTFFFTTFFF EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=22.26281&lat=60.51412&zoom=14&layers=B000000TFFFFTFFFTFFFF EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled

|-
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility

|-
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe ||

|-
| EGGW || London Luton Airport || United Kingdom || Europe ||

|-
| EGKA || Shoreham Airport || United Kingdom || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=-0.19224&lat=51.14869&zoom=14&layers=B000000TFFFFTFFFTTFFF EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network

|-
| [http://mapserver.flightgear.org/map/?lon=-0.46095&lat=51.47139&zoom=14&layers=B000000TFFFFTFFFTTFFF EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

|-
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models

|-
| [http://mapserver.flightgear.org/map/?lon=1.28469&lat=52.67713&zoom=15&layers=B000000TFFFFTFFFTTFFF EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.

|-
| [http://mapserver.flightgear.org/map/?lon=4.75487&lat=52.31296&zoom=14&layers=B000000TFFFFTFFFTTFFF EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

|-
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=5.51885&lat=52.45717&zoom=15&layers=B000000TFFFFTFFFTTFFF EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

|-
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.

|-
| EIDW || [[Dublin Airport]] || Ireland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=6.11017&lat=62.56037&zoom=15&layers=B000000TFFFFTFFFTTFFF ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=6.10949&lat=61.83027&zoom=15&layers=B000000TFFFFTFFFTTFFF ENSD] || Sandane Airport || Norway || Europe ||

|-
| ENVA || Trondheim Værnes Airport || Norway || Europe ||

|-
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=-106.60912&lat=35.04021&zoom=14&layers=B000000TFFFFTFFFTTFFF KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=-84.42809&lat=33.63672&zoom=14&layers=B000000TFFFFTFFFTTFFF KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| KAUS || Austin-Bergstrom Airport, TX || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-76.66833&lat=39.17535&zoom=14&layers=B000000TFFFFTFFFTTFFF KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [http://mapserver.flightgear.org/map/?lon=-76.92254&lat=38.98062&zoom=15&layers=B000000TFFFFTFFFTTFFF KCGS] || College Park Airport, MD || USA || America ||

|-
| KDCA || Reagan National Airport, VA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-104.67318&lat=39.86166&zoom=13&layers=B000000TFFFFTFFFTTFFF KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

|-
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only

|-
| KFHR || Friday Harbor Airport, WA || USA || America ||

|-
| KIND || Indianapolis Airport, IN || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-90.07589&lat=32.31118&zoom=14&layers=B000000TFFFFTFFFTTFFF KJAN] || Jackson-Evers Airport, MS || USA || America ||

|-
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America ||

|-
| KLAS || Las Vegas McCarran Airport, NV || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-118.40809&lat=33.9425&zoom=14&layers=B000000TFFFFTFFFTTFFF KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

|-
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-109.4667&lat=47.04924&zoom=14&layers=B000000TFFFFTFFFTTFFF KLWT] || Lewistown Municipal Airport, MT || USA || America ||

|-
| KMCI || Kansas City Airport, MO || USA || America || Basic development only

|-
| KMTN || Martin State Airport, MD || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-117.69181&lat=35.68565&zoom=14&layers=B000000TFFFFTFFFTTFFF KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.04918&lat=37.4162&zoom=15&layers=B000000TFFFFTFFFTTFFF KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-122.22062&lat=37.7214&zoom=14&layers=B000000TFFFFTFFFTTFFF KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

|-
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-88.55704&lat=43.98436&zoom=14&layers=B000000TFFFFTFFFTTFFF KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-75.12398&lat=38.31045&zoom=14&layers=B000000TFFFFTFFFTTFFF KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.59751&lat=45.58871&zoom=14&layers=B000000TFFFFTFFFTTFFF KPDX] || Portland Airport, OR || USA || America ||

|-
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America ||

|-
| KRNO || Reno/Tahoe Airport, NV || USA || America ||

|-
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.3749&lat=37.61897&zoom=14&layers=B000000TFFFFTFFFTTFFF KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.

|-
| KSLC || Salt Lake City International Airport, UT || USA || America ||

|-
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America ||

|-
| LDSP || Split Airport || Croatia || Europe || Basic development only

|-
| LEBB || Bilbao || Spain || Europe || Fully modeled

|-
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled

|-
| LFEA || Belle-Ile || France || Europe ||

|-
| LFEQ || Quiberon || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=-3.66479&lat=48.05247&zoom=15&layers=B000000TFFFFTFFFTTFFF LFES] || Guiscriff Scaër || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=2.35465&lat=49.04626&zoom=15&layers=B000000TFFFFTFFFTTFFF LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=4.8264&lat=45.25226&zoom=15&layers=B000000TFFFFTFFFTTFFF LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=13.76716&lat=51.13277&zoom=15&layers=B000000TFFFFTFFFTTFFF LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=0.08816&lat=49.53404&zoom=14&layers=B000000TFFFFTFFFTTFFF LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=5.36736&lat=43.50499&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=2.60632&lat=48.89629&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| LFPL || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPO || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPZ || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=-4.41785&lat=48.44413&zoom=12&layers=B00000000000FTFFTFFTFFFTFFFF LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [http://mapserver.flightgear.org/map/?lon=-4.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [http://mapserver.flightgear.org/map/?lon=-4.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| LFRQ || Quimper || France || Europe ||

|-
| LFRU || Morlaix || France || Europe ||

|-
| LFSB || Basel-Mulhouse || Switzerland || Europe ||

|-
| LILN || Venegono Airport || Italy || Europe || Developed airport

|-
| LILQ || Massa Cinquale Airport || Italy || Europe ||

|-
| LILV || Valbrembo Airport || Italy || Europe ||

|-
| LIMC || Milano-Malpensa Airport || Italy || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=9.70741&lat=45.66952&zoom=14&layers=B000000TFFFFTFFFTTFFF LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=9.27521&lat=45.44776&zoom=14&layers=B000000TFFFFTFFFTTFFF LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=7.36789&lat=45.73857&zoom=15&layers=B000000TFFFFTFFFTTFFF LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=11.34397&lat=47.26023&zoom=15&layers=B000000TFFFFTFFFTTFFF LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

|-
| LROP || Bucharest Otopeni || Romania || Europe ||

|-
| LSGS || Sion Airport || Switzerland || Europe || Basic development only

|-
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only

|-
| PANC || Ted Stevens Anchorage International Airport || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=136.80541&lat=34.85841&zoom=14&layers=B000000TFFFFFFFFTTFFF RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [http://mapserver.flightgear.org/map/?lon=139.78114&lat=35.5533&zoom=14&layers=B000000TFFFFTFFFTTFFF RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=126.45051&lat=37.46909&zoom=14&layers=B000000TFFFFTFFFTTFFF RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=121.01349&lat=14.51024&zoom=14&layers=B000000TFFFFTFFFTTFFF RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-
| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America ||

|-
| TDPD || Melville Hall Airport || Dominica || America ||

|-
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America ||

|-
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America ||

|-
| TIST || Cyril E. King Airport || US Virgin Islands || America ||

|-
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America ||

|-
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America ||

|-
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain

|-
| TNCS || Juancho E. Yrausquin Airport || Saba || America || Fully modeled

|-
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-49.17201&lat=-25.53101&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBCT] || Afonso Pena International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [http://mapserver.flightgear.org/map/?lon=-46.65768&lat=-23.62558&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBSP] || Congonhas Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [http://mapserver.flightgear.org/map/?lon=-46.46864&lat=-23.43351&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBGR] || Guarulhos International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [http://mapserver.flightgear.org/map/?lon=-48.54304&lat=-27.6685&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| VIDP || Indira Gandhi International Airport || India || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=113.9183&lat=22.308&zoom=14&layers=B000000TFFFFTFFFTTFFF VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

|-
| [http://mapserver.flightgear.org/map/?lon=-90.13769&lat=43.83872&zoom=15&layers=B000000TFFFFTFFFTTFFF 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-89.02545&lat=44.50485&zoom=15&layers=B000000TFFFFTFFFTTFFF 68C] || Iola Central County Airport, WI || USA || America ||

|}

{{Suggested}}

[[Category:List]]
[[Category:Airports]]

Embraer EMB-121 Xingu

2013-08-25T15:51:07Z

Sa7k: Fix download link

{{non-stable}}

{{infobox Aircraft
|image = EMB-121.png
|name = Embraer EMB-121 Xingu
|type = Airliner
|livery = white
|authors = Bruno Reichert, Aurino Neves and Isaías V. Prestes
|fdm = JSBSim
|status-fdm = 2
|status-systems = 1
|status-cockpit = 3
|status-model = 4
|fgname = EMB-121
|download = http://djrick1.wix.com/grupofgbr/avioes#!__avioes/vstc2=embraer-121
}}
The '''Embraer EMB 121 Xingu''' (pronounced "shingoo") is a twin-turboprop fixed-wing [[aircraft]] built by the Brazilian aircraft manufacturer, [[Embraer]]. The design of this plane is based on the EMB 110 Bandeirante, using its wing and engine design merged with an all-new fuselage. The EMB 121 first flew on 10 October 1976.

== Work in Progress ==
* Reliable electric system
* Liveries

== External links ==
* [http://www.centrohistoricoembraer.com.br/en/historia-aeronaves/emb-121-xingu.htm EMBRAER website for EMB-121 Xingu]
* [http://en.wikipedia.org/wiki/EMB-121_Xingu Wikipedia]

{{Embraer}}

[[Category:Airliners]]

FlightGear hangars

2013-08-25T15:48:10Z

Sa7k: Fix grupofgbr link

{{cleanup}}

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

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

Be careful with external links!

== Official hangars ==
=== Aircraft ===
* [http://www.flightgear.org/download/aircraft-2-10-filterable/ FlightGear Official 2.10 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-8/ FlightGear Official 2.8 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear Official 2.6 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-4/ FlightGear Official 2.4 Hangar] (Legacy site)
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar] (Legacy site)
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Liveries]

== Unofficial sites ==
=== Aircraft hangars ===
* [http://www.gitorious.org/fg-airbus-a332 Airbus A330-200 Series Development Git] (A330-203, A330-223, A330-243 - FGAirbus/theOmegaHangar)
* [http://www.gitorious.org/fg-airbus-a333 Airbus A330-300 Series Development Git] (A330-303, A330-323, A330-343 - FGAirbus/theOmegaHangar)
* [https://www.gitorious.org/airbus-aircraft Airbus Aircraft Development Git] (A320, A330, A340-300, A380 - various authors)
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] with [http://gitorious.org/anders-hangar aircraft repositories at gitorious].
* [http://andinogonthaeler.wordpress.com/ Andino's Hangar] (Boeing 707-3J9C and 707-320C, 777-200LR).
* [http://flighthgearcolombia.jimdo.com/ Hangar colombiano] Colombian airlines and militaries aircraft FAC.
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a YASim intro)
* <s>[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]</s>{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)
* <s>[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]</s>{{dead link|2012-04}} (a few well made aircraft)
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}} (Blog format)
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons)
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (164+ original aircraft)
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles)
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)
* [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar] Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
* [http://flightgear.bplaced.de/ longfly's hangar] (not only German!)
** [http://flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts] (under development)
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)
* <s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
* [http://theomegahangar.flymerlion.org/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)
* [http://pjedvaj.eu5.org/ pjedvaj's Hangar] (MiG-21bis, PC-9M, PC-21, T-50, Harrier GR.1, F-35B, RAH-66)
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)
* <s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many Brazilian aircraft articles)
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
* <s>[http://sydhangar.daffodil.uk.com/ Syd's Hangar ]</s>{{dead link|2012-04}} (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]
* [http://acjza-hangers.webs.com/ ACJZA's Hanger] (A310, BAe 146, C-Series)
* [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar] (JA-37, scenario)
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]

=== Old Hangars ===
* [http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)

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

=== Homepages, blogs, etc. ===
* [http://www.jaunty.bplaced.net/flightgear/index.php A small FlightGear page]
* <s>[http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]</s>{{dead link|2013-01}}
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]
* [http://helldiversquadron.wordpress.com/ Helldiver Squadron Offensive Tactical Force Homepage]
* [http://djrick1.wix.com/grupofgbr Grupo FGBR Brazilian Portal] (Broken site - only accesible with flash player)
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)
* [http://flightgear2009.blogspot.com/ FlightGear Brasil 2009] (non-english)
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)
* [http://flightgearcorner.tk The FlightGear Corner] (News, Downloads, Tutorials and more)
* [http://www.fguk.eu/ FlightGear United Kingdom]
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]
* <s>[http://tehwarlock.tk/ Tehwarlock Blog]</s>{{dead link|2012-04}}
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)
* [http://flightgear.mxchange.org/ Quix0r's FlightGear Website] Simple tutorials and fgdata.bundle
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]

=== Other FlightGear repositories/mirrors ===
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery)
* [http://www.flightgearplanes.com Flightgear Planes Website]
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]
* [http://lukeafg.com/ LukeaFG] (FlightGear tutorials and developments)
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]

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

[[Category:List]]

Embraer 195

2013-08-25T15:41:27Z

Sa7k: Fix download link

{{non-stable}}

{{infobox Aircraft
|image =Embraer195.png
|name =Embraer 195
|type =Airliner
|livery =Azul, FAB, JetBlue
|authors = Isaias V. Prestes, Group FGBR - Brazil
|fdm =JSBSim
|status =Under development
|fgname =Embraer-195
|download =http://djrick1.wix.com/grupofgbr/avioes#!__avioes
}}
The '''[[Embraer]] 195''' is a larger stretch of the E-170 model fitted with a new, larger wing and a new engine, the [[GE CF34-10E]], rated at 18,500 lb (82.30 kN). Being in the 100-seat range, it competes with smaller jets including the [[Bombardier]] [[CRJ-1000]], [[Boeing 717]]-200 and [[Boeing 737|737-600]] as well as the [[Airbus]] [[Airbus A318|A318]].

The first flight of the E-195 was in December 2004. European low cost carrier Flybe launched the E-195 with 14 orders and 12 options.

As the 190/195 family is of mainline [[aircraft]] size, many airlines will operate them as such, fitting them with a business class section and operating them themselves, instead of having them flown by a commuter airline partner. For example, Air Canada operates 45 [[Embraer 190|E-190]] aircraft fitted with 9 business-class and 84 economy-class seats as part of their primary fleet.

== Specifications ==
{| class="prettytable"
| '''Weights''' || '''STD & LR versions''' || '''AR version'''
|-
| '''Maximum Take Off Weight''' || STD 107,563lb 48,790kg || 115,279lb 52,290kg
|-
| || LR 111,972lb 50,790kg || ||
|-
| '''Maximum Landing Weight''' || 99,208lb 45,000kg || 100,971lb 45,800kg
|-
| '''Maximum Zero Fuel Weight''' || 93,696lb 42,500kg || 93,916lb 42,600kg
|-
| '''Basic Operating Weight''' || 63,603lb 28,850kg || 63,824lb 28,950kg
|-
| '''Maximum Payload''' || 30,093lb 13,650kg || 30,093lb 13,650kg
|-
| '''Maximum Fuel''' || 28,596lb 12,971kg || 28,596lb 12,971kg
|}

== External Links ==
* [http://www.embraercommercialjets.com.br/english/content/ejets/emb_195.asp Embraer 195 official webpage]
* [http://en.wikipedia.org/wiki/Embraer_195#E-190.2F195 Wikipedia (source)]

{{Embraer}}

[[Category:Airliners]]

Talk:Embraer EMB-120 Brasilia

2013-08-25T15:36:48Z

Sa7k:

== Broken download link ==
This page can be deleted -> Download link doesnt work

{{unsigned|14:08, 25 August 2013‎ |Flightgearex}}

: Hi,
: Please fill in the deletion request form, as explained at {{tl|delete}}.
: Cheers,
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:41, 25 August 2013 (UTC)
: PS: Please sign messages on wiki talk pages with four tildes (<code><nowiki>~~~~</nowiki></code>)

:: I fixed the link to grupo-fg brazil so you don't need to delete the page.
:: I also tried to add a direct download link in "external links" so anyone can get the link without going to a horrible page that only works with flash installed but the spam filter does not like 4shared and I can't do it. [[User:Sa7k|Sa7k]] ([[User talk:Sa7k|talk]]) 15:36, 25 August 2013 (UTC)

Embraer EMB-120 Brasilia

2013-08-25T15:30:21Z

Sa7k: Fix download link

{{non-stable}}

''This includes the following models: EMB-120, EMB-120ER''

{{infobox Aircraft
|image = EMB-120.png
|name = Embraer EMB-120 Brasilia
|type = Airliner
|livery = aluminum, white, RioSul, Interbrasil, United
|authors = Isaias V. Prestes and Aurino Neves
|fdm = YAsim
|status-fdm = 3
|status-systems = 1
|status-cockpit = 3
|status-model = 4
|fgname = EMB-120
|download = http://djrick1.wix.com/grupofgbr/avioes#!__avioes/vstc2=embraer-120
}}
The '''Embraer EMB 120 ''Brasilia''''' is a twin-turboprop commuter airliner, produced by [[Embraer]] of Brazil. Originally called the Araguaia, the name was changed to Brasilia in 1979 at the official launching of the project. The design retained the T-tail and supercritical wing of the [[Embraer EMB-121 Xingu|EMB-121 Xingu]], but with the capacity for 30 seats. Originally designed to utilise the new 1500SHP Pratt & Whitney Canada PW115 Turboprop, this was later upgraded to the 1892 ESHP PW118.

== External links ==
* [http://http://www.centrohistoricoembraer.com.br/en/historia-aeronaves/emb-120-brasilia.htm EMBRAER website for EMB-120 Brasilia]
* [http://http://en.wikipedia.org/wiki/Embraer_EMB_120_Brasilia Wikipedia]

{{Embraer}}

[[Category:Airliners]]

FlightGear Newsletter August 2013

2013-08-23T19:23:11Z

Sa7k: typos fix

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.''

== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].
=== FlightGear 2.12 holding ===
[[File:Delayed2.12-fb 0.jpg|400px|2.12 delayed]]

Due to real life constraints and the low number of active core developers, we've hit a fluctuation where pretty much everyone is occupied with
something else at the moment. As everybody seems to be caught in some real life trouble, we can't see a better way to get the release out than delaying it for a while.
Also, it seems that it will take longer than usual to address any issues found in the RCs. Thus, we have agreed to postpone the upcoming FlightGear 2.12 release by a month, to provide sufficient time to handle release candidates and process end-user feedback. <ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40568.html</ref>
<references/>

=== Independent Ramp Marshall ===

Omega95 has been working on a [[Nasal]]-based Ramp Marshall script. That was a prototype only to test the general script and the animations. He's now working on a larger system similar to the animated jetways to generalize this and make the animations independent.

{{#ev:youtube | c_KEbyv_h5A}} {{#ev:youtube | Hz4WU8nsdls}}

Continue reading at [[Ramp Marshall]]...

=== Random Buildings ===


=== Project Rembrandt ===
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].

=== Canvas System ===


=== High Level Architecture ===
=== FlightGear an Android ===

=== Usability Improvements ===

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.

If you are interested in contributing as a core developer, please see [[Howto:Start core development]].

== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Translators required ==
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===
Among others, there is a new livery by Frank Göldner for the DC-3/C-47 operated from October 1970 until November 1972 for the British Kestrel Airways.
Download it at [http://liveries.flightgear.org/liveries.php?id=1004 the FlightGear Livery Database]

== Scenery corner ==
=== Scenery model update forms ===
After a few (but long) months of waiting, it is finally possible to update the existing 3D scenery models using the webforms! The form can be found there: [http://scenemodels.flightgear.org/submission/static/index_model_update.php Update a model]

This means that from now, '''you are able to improve the models''', such as adding details, fixing wrong scale, or even making them lighter and '''improve FlightGear performance'''! Some models indeed had some unseen vertices/faces/meshes or had useless two-sided faces, and fixing this mistakes won't affect overall details '''BUT''' will certainly improve performance!

Your changes will then be updated to Terrasync.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
== Aircraft reviews ==

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on YouTube ===

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
==== Web tools for ATC sessions extended to entire World ====
The web tool for ATC sessions at [http://lenny64.free.fr lenny64.free.fr] which was previously mentioned in the [[FlightGear Newsletter May 2013#Web tools for ATC sessions in Europe|April Newsletter]] has had a few extensions made on August 5th. The changes include:
* It is now possible to schedule an ATC session anywhere in the World.
* ATCs can now ask to receive an email when a flightplan is filed to or from his airport.
* Filed flightplans are now listed at the end of the page.

In addition to that filling in flight plans have been simplified and there is now also an API for filing flight plans which, when registered for an individual API key, allows filing flight plans though HTTP GET requests (in essence through an URL with lots of parameters).

=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].

=== Call for volunteers ===
* The [[Flightgear On Android]] team is looking for testers
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter]]


[[Category:Changes after 2.10]]

Custom Spain and Portugal scenery

2013-06-27T18:33:18Z

Sa7k: /* Distribution */ Update some file sizes.

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (111MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (350MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The next map shows the improved airports in the scenery: https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code:

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Aeronautical information publication

2013-05-02T19:19:57Z

Sa7k: Fix Brazil AIS link.

The '''aeronautical information publication''' ('''AIP''') contains all of the information about the regulations, air ways, navigation aids etc. in a nations air space. The AIP is published by that nations air authority or agency at regular intervals and together with notices to air men (NOTAMs) it contains all the information needed, except for the weather, for flying in that airspace unless it states otherwise.

== Main contents ==
The AIP consists of three main parts, ''General'' (''GEN''), containing some general information, ''En route'' (''ENR''), containing information about the airspace, air routes and navigation aids, and ''Aerodromes'' (''AD''), with information about the airports, airfields and helipads. Sometimes there is also amendments and supplements, and the AIP can also point to other sources for example for aerodrome information and charts.

=== GEN ===
* '''GEN 1.''' National aviation authorities, national regulations regarding entry and exit of the air space and required instrumentation and radios
* '''GEN 2.''' Measuring systems, time zones, abbreviations, map legends, lists with positions of fixes and navigation aids, conversion and sunrise/sunset tables
* '''GEN 3.''' Aeronautical information, air traffic communication and meteorological services, where to get maps and search and rescue routines
* '''GEN 4.''' Fees and charges

An important section is GEN 1.7, ''Differences from ICAO Standards, recommended practices and procedures'', as there can sometimes be important differences between countries.

=== ENR ===
* '''ENR 1.''' Instrument and visual flight rules (IFR and VFR), altimeter setting procedures, flight planning and filing of flight plans, and time zones
* '''ENR 2.''' ATC air spaces
* '''ENR 3.''' Air routes
* '''ENR 4.''' Navigation aids
* '''ENR 5.''' Prohibited, restricted and dangerous areas, military training areas, bird migration areas and other hazards

=== AD ===
* '''AD 1.''' Everything about airports, taxi procedures, traffic patterns, lightening etc.
* '''AD 2.''' Listings of public airports, airfields and helipads together with charts and other information

== Related content ==
* [[Navigation references]]
* [[Getting aeronautical charts]]

== External links ==
A complete list of European AIPs can be found [http://www.eurocontrol.int/aim/public/standard_page/web_eur.html here].

* [http://www.aisweb.aer.mil.br/index.cfm?i=home&lingua=en Brazil]
* [http://www.slv.dk/Dokumenter/dscgi/ds.py/View/Collection-94 Denmark] (also includes Greenland and the Faeroe Islands)
* [http://www.sia.aviation-civile.gouv.fr/aip/enligne/fr/home.htm France]
* [http://www.ais.fi/ais/eaip/en/ Finland]
* [http://www.ais-netherlands.nl/aim/index.html the Netherlands]
* [http://www.lfv.se/en/FPC/IAIP/ Sweden]
* [http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=165&Itemid=3.html United Kingdom]

WorldEditor

2013-02-26T20:49:02Z

Sa7k: Fix version

{{Infobox Software
| title = WorldEditor
| image = WorldEditor_EHAM.png
| alt = [[Amsterdam Airport Schiphol|Amsterdam Schiphol]] in WED.
| developedby = Ben Supnik, Cristiano Maggi
| initialrelease = 2007
| latestrelease =
| os = GNU/Linux, Windows, MacOS X
| website = http://scenery.x-plane.com/tools.php
| license = [[GNU General Public License]]
}}
'''WorldEditor''' ('''WED''') is a CAD-like graphic editor that lets you create custom airport layouts. It is designed for X-Plane, and works with [[apt.dat]] version 850 and higher.

== Obtaining WorldEditor ==
=== Mac/Windows ===
Stable WED binaries for Windows and Mac can be downloaded from [http://scenery.x-plane.com/tools.php scenery.x-plane.com]. A development version is available through: [http://dev.x-plane.com/download/tools/ dev.x-plane.com].

In order to work with WED without installing X-Plane, one needs to create a special <tt>Custom Scenery</tt> directory, for example <tt>X-Plane/Custom Scenery</tt>. When launching WED for the first time, click the "Choose X-Plane folder" directory and select the folder that your <tt>Custom Scenery</tt> houses in (in our example: <tt>X-Plane</tt>).

=== Linux ===
Because there is no (stable) binary available for Linux based operating systems, the user has to compile it from source. Don't be afraid of that, since it brings most of its dependencies along, it is not hard. However, some things need to be provided by the user's system:
* binutils and binutils-devel
* [[git]]
* GNU coreutils
* GNU make
* libmpfr-devel
* mesa-libGL-devel and mesa-libGLU-devel
* qt4-devel

Downloading WED's source (about 170 MiB) is done via <tt>git</tt>:
git clone http://dev.x-plane.com/git/xptools.git xptools.git
cd xptools.git

Afterwards WED's dependencies have to be downloaded (about 260 MiB) and compiled. These steps have to be done only once, before compiling WED the first time:
git submodule update --init
cd libs
make -j2
cd ..

Compiling WED:
conf=release_opt make -j2 WED

As on [[#Mac/Windows|Mac/Windows]] WED needs a certain working directory <tt>some_name/Custom Scenery</tt>. Assuming your self made scenery stuff lives (/is going to be) in <tt>~/FGscenery-workbench</tt>, create a directory:
mkdir -p ~/FGscenery-workbench/Custom\ Scenery

Choose <tt>FGscenery-workbench</tt> as "X-PLANE FOLDER" the first time you start WED:
build/Linux/release_opt/WED

You may now copy the file <tt>build/Linux/release_opt/WED</tt> to <tt>~/bin</tt> or another location within your $PATH environment variable:
cp build/Linux/release_opt/WED ~/bin

There is a beta binary of WorldEditor 1.2 which is quite usable but you have to be careful and save your work often because it could crash and make you lose your work. Note that this binary works only on 64 bit linux systems. [http://developer.x-plane.com/tools/worldeditor/ developer.x-plane.com]

== Related content ==
* [[TaxiDraw]], editor for [[Interactive traffic#Ground networks|groundnetworks]] and apt.dat below version 850.

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)
* [http://xsimreviews.com/2012/12/16/x-plane-scenery-design-tutorial-4-wed-pt1/ WED tutorial part one] (Xsimreviews blog)
* [http://xsimreviews.com/2013/02/03/x-plane-scenery-design-tutorial-5-wed-part-ii/ WED tutorial part two] (Xsimreviews blog)

[[Category:Software]]
[[Category:Scenery enhancement]]

WorldEditor

2013-02-26T20:45:34Z

Sa7k: Fix versions

{{Infobox Software
| title = WorldEditor
| image = WorldEditor_EHAM.png
| alt = [[Amsterdam Airport Schiphol|Amsterdam Schiphol]] in WED.
| developedby = Ben Supnik, Cristiano Maggi
| initialrelease = 2007
| latestrelease =
| os = GNU/Linux, Windows, MacOS X
| website = http://scenery.x-plane.com/tools.php
| license = [[GNU General Public License]]
}}
'''WorldEditor''' ('''WED''') is a CAD-like graphic editor that lets you create custom airport layouts. It is designed for X-Plane, and works with [[apt.dat]] version 850 and higher.

== Obtaining WorldEditor ==
=== Mac/Windows ===
Stable WED binaries for Windows and Mac can be downloaded from [http://scenery.x-plane.com/tools.php scenery.x-plane.com]. A development version is available through: [http://dev.x-plane.com/download/tools/ dev.x-plane.com].

In order to work with WED without installing X-Plane, one needs to create a special <tt>Custom Scenery</tt> directory, for example <tt>X-Plane/Custom Scenery</tt>. When launching WED for the first time, click the "Choose X-Plane folder" directory and select the folder that your <tt>Custom Scenery</tt> houses in (in our example: <tt>X-Plane</tt>).

=== Linux ===
Because there is no (stable) binary available for Linux based operating systems, the user has to compile it from source. Don't be afraid of that, since it brings most of its dependencies along, it is not hard. However, some things need to be provided by the user's system:
* binutils and binutils-devel
* [[git]]
* GNU coreutils
* GNU make
* libmpfr-devel
* mesa-libGL-devel and mesa-libGLU-devel
* qt4-devel

Downloading WED's source (about 170 MiB) is done via <tt>git</tt>:
git clone http://dev.x-plane.com/git/xptools.git xptools.git
cd xptools.git

Afterwards WED's dependencies have to be downloaded (about 260 MiB) and compiled. These steps have to be done only once, before compiling WED the first time:
git submodule update --init
cd libs
make -j2
cd ..

Compiling WED:
conf=release_opt make -j2 WED

As on [[#Mac/Windows|Mac/Windows]] WED needs a certain working directory <tt>some_name/Custom Scenery</tt>. Assuming your self made scenery stuff lives (/is going to be) in <tt>~/FGscenery-workbench</tt>, create a directory:
mkdir -p ~/FGscenery-workbench/Custom\ Scenery

Choose <tt>FGscenery-workbench</tt> as "X-PLANE FOLDER" the first time you start WED:
build/Linux/release_opt/WED

You may now copy the file <tt>build/Linux/release_opt/WED</tt> to <tt>~/bin</tt> or another location within your $PATH environment variable:
cp build/Linux/release_opt/WED ~/bin

There is a beta binary of WorldEditor 1.2 which is quite usable but you have to be careful and save your work often because it could crash and make you lose your work. Note that this binary works only on 64 bit linux systems. [http://developer.x-plane.com/tools/worldeditor/ developer.x-plane.com]

== Related content ==
* [[TaxiDraw]], editor for [[Interactive traffic#Ground networks|groundnetworks]] and apt.dat below version 850.

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)
* [http://xsimreviews.com/2012/12/16/x-plane-scenery-design-tutorial-4-wed-pt1/ WED 1.2 tutorial part one] (Xsimreviews blog)
* [http://xsimreviews.com/2013/02/03/x-plane-scenery-design-tutorial-5-wed-part-ii/ WED 1.2 tutorial part two] (Xsimreviews blog)

[[Category:Software]]
[[Category:Scenery enhancement]]

WorldEditor

2013-02-26T12:22:07Z

Sa7k: Add some info for WED 1.1, binary and tutorial.

{{Infobox Software
| title = WorldEditor
| image = WorldEditor_EHAM.png
| alt = [[Amsterdam Airport Schiphol|Amsterdam Schiphol]] in WED.
| developedby = Ben Supnik, Cristiano Maggi
| initialrelease = 2007
| latestrelease =
| os = GNU/Linux, Windows, MacOS X
| website = http://scenery.x-plane.com/tools.php
| license = [[GNU General Public License]]
}}
'''WorldEditor''' ('''WED''') is a CAD-like graphic editor that lets you create custom airport layouts. It is designed for X-Plane, and works with [[apt.dat]] version 850 and higher.

== Obtaining WorldEditor ==
=== Mac/Windows ===
Stable WED binaries for Windows and Mac can be downloaded from [http://scenery.x-plane.com/tools.php scenery.x-plane.com]. A development version is available through: [http://dev.x-plane.com/download/tools/ dev.x-plane.com].

In order to work with WED without installing X-Plane, one needs to create a special <tt>Custom Scenery</tt> directory, for example <tt>X-Plane/Custom Scenery</tt>. When launching WED for the first time, click the "Choose X-Plane folder" directory and select the folder that your <tt>Custom Scenery</tt> houses in (in our example: <tt>X-Plane</tt>).

=== Linux ===
Because there is no (stable) binary available for Linux based operating systems, the user has to compile it from source. Don't be afraid of that, since it brings most of its dependencies along, it is not hard. However, some things need to be provided by the user's system:
* binutils and binutils-devel
* [[git]]
* GNU coreutils
* GNU make
* libmpfr-devel
* mesa-libGL-devel and mesa-libGLU-devel
* qt4-devel

Downloading WED's source (about 170 MiB) is done via <tt>git</tt>:
git clone http://dev.x-plane.com/git/xptools.git xptools.git
cd xptools.git

Afterwards WED's dependencies have to be downloaded (about 260 MiB) and compiled. These steps have to be done only once, before compiling WED the first time:
git submodule update --init
cd libs
make -j2
cd ..

Compiling WED:
conf=release_opt make -j2 WED

As on [[#Mac/Windows|Mac/Windows]] WED needs a certain working directory <tt>some_name/Custom Scenery</tt>. Assuming your self made scenery stuff lives (/is going to be) in <tt>~/FGscenery-workbench</tt>, create a directory:
mkdir -p ~/FGscenery-workbench/Custom\ Scenery

Choose <tt>FGscenery-workbench</tt> as "X-PLANE FOLDER" the first time you start WED:
build/Linux/release_opt/WED

You may now copy the file <tt>build/Linux/release_opt/WED</tt> to <tt>~/bin</tt> or another location within your $PATH environment variable:
cp build/Linux/release_opt/WED ~/bin

There is a beta binary of WorldEditor which is quite usable but you have to be careful and save your work often because it could crash and make you lose your work. Note that this binary works only on 64 bit linux systems. [http://dev.x-plane.com/download/tools/wed_lin_110b4.zip dev.x-plane.com]

== Related content ==
* [[TaxiDraw]], editor for [[Interactive traffic#Ground networks|groundnetworks]] and apt.dat below version 850.

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)
* [http://xsimreviews.com/2012/12/16/x-plane-scenery-design-tutorial-4-wed-pt1/ WED 1.1 tutorial part one] (Xsimreviews blog)
* [http://xsimreviews.com/2013/02/03/x-plane-scenery-design-tutorial-5-wed-part-ii/ WED 1.1 tutorial part two] (Xsimreviews blog)

[[Category:Software]]
[[Category:Scenery enhancement]]

Airbus A330-300 Series

2013-02-08T21:10:57Z

Sa7k: Fix videos which failed because of missing alignment

{{infobox Aircraft
|image = A333-splash.png
|name = Airbus A330-300 Series
|type = Wide-body Airliner
|fdm = JSBSim
|status = Git Development Version
|authors = Narendran M, Chris M, Zhuang T, Geir M, Kyle D, A330-200 Developers
|fgname = A330-303, A330-323, A330-343
|download = https://gitorious.org/fg-airbus-a333/airbus-a330-300-main/archive-tarball/master
|development = https://gitorious.org/fg-airbus-a333/airbus-a330-300-main
}}

This aircraft package is now rembrandt compatible! (Simply checkout the rembrandt branch from the git repository to get it)

The '''Airbus A330-300 series''' project consists of the '''Airbus A330-303''' (A330-300 with ''General Electric CF6-80E1 Engines''), '''Airbus A330-323''' (A330-300 with ''Pratt and Whitney PW4000 Engines'') and the '''Airbus A330-343''' (A330-300 with ''Rolls Royce Trent 772B-60 Engines''). The project uses theOmegaHangar's new [[Airbus A320neo|Airbus A320/30/40]] cockpit and systems and new Airbus A330-300 models. The A330-300 series aircraft have been converted from the same developers' Airbus A330-200 series aircraft. The following changes have been made:

* Fuselage Length Increased (6 fuselage sectional frames in front of the wings and 4 behind)
* Rudder Height Decreased (to be precise, by 0.59 meters)
* Textures Re-mapped and new paintkits created (to accommodate to the extended models)
* Animations fixed (nose and tail, due to extensions)
* Minor FDM Changes made (CoG, Weights, Fuel, Contact Points, Metrics (VStab Area and HTail Arm))
* New Liveries (see below)

Feel free to start a discussion in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 the forum topic] if you'd like to contribute to the project.

==Airbus Systems==

===Airbus Fly-By-Wire===
The Airbus fly-by-wire (adapted from the Airbus A320neo fly-by-wire) is a system which continuously takes in the pilot's stick input, uses them as Pitch/Roll-Rate commands, and calculates the required surface deflection to achieve the commanded rate. The fly-by-wire also provides flight envelope protection and the soft/hard bank feature.

====Pitch/Roll-Rate and G-Force Command====
For the Roll Axis, the stick all the way to the left commands a negative 30 degrees roll rate and all the way to the right commands a positive 30 degrees roll rate.

As for the Pitch Axis, the commands are divided according to the airspeed of the aircraft. If the Airspeed is under 210 knots, pitch-rate is used and over 210 knots, g-force is used. Under 210 knots, pulling the stick all the way to the back commands a 30 degrees pitch rate and pushing it all the way forward commands a negative 30 degrees pitch rate. Over 210 knots, pulling the stick all the way to the back commands a 2.75G acceleration and pushing it all the way forward commands a -0.75G acceleration.

====Flight Envelope Protection====
For the Roll Axis, having the stick less than half way deflected either side, you get what's called a ''soft bank''. With a soft bank, the aircraft can't exceed 33 degrees of bank to either side. If the stick is deflected more than half way, you get a hard bank and the aircraft can be banked up till 67 degrees to either side.

For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.

=== Hydraulics System ===
The Airbus A320, A330 and [[Airbus A340|A340]] series have similar hydraulic systems. There are three hydraulic systems on the aircraft, each having it's own reservoir- the '''GREEN''' system, the '''YELLOW''' system and the '''BLUE''' system.

The Green system is powered by the Left Engine's Hydraulic Pump, the yellow by the Right Engine's Hydraulic Pump and the Blue System with an Electric Pump. During normal operation, each hydraulic system should have their hydraulic pressure between 2500 and 3000 PSI. (Pounds per Square Inch) The engine systems control the surfaces, stabilizers, flaps/slats and landing gears while the electric pump system connect to only the surfaces and stabilizers. In case a system fails, an alternate system can be used. The yellow system also has an electric pump which can be used to power the hydraulics using external power when the aircraft is on the ground.

The Yellow and Green Hydraulic systems have a power transfer unit which is used to transfer hydraulic pressure between the pumps in case there is a 500 PSI difference between the pressures in the green and yellow systems.

All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.

'''MORE SYSTEMS INFORMATION COMING SOON'''

== Example Flight(s) ==

=== Custom Emirates Flight from Frankfurt to Munich ===

This flight was requested by Detlef N. (MIA0283), and video tutorials were recorded for different sections of the flight. The videos can be viewed below or in the ''FlightGear Airbus'' YouTube channel. Thank you for watching!

''NOTE that these tutorials have been meant for the Airbus A330-200 series aircraft but are applicable to the A320neo and A330-300 series too. This is because of the shared flightdeck and systems on board most A3XX aircraft.''

==== Flight Planning ====

{{#ev:youtube|R66q_10dwKw|480|auto|Part 1: Flight Planning}}

==== Manual Start-up ====

{{#ev:youtube|8TI14RJDn2k|480|auto|Part 2: Manual Start-up}}

==== Take-off and Climb ====

{{#ev:youtube|IpkdhebC4-o|480|auto|Part 3: Take-off and Climb}}

''NOTE: Cruise skipped due to the fact that it may be '''boring'''''...

==== Descent and Autoland ====

{{#ev:youtube|NeX3samzrqU|480|auto|Part 4: Descent and Autoland}}

== Liveries ==
The Airbus A330-300 series have liveries for each variant (303, 323 an 343) and are managed by Chris Mueffelmann. Please let us know if you're creating a livery by changing the status on the livery below so that duplicates are avoided.

=== Airbus A330-303 Liveries ===

{|
| valign="top" |
* KLM
* Qantas - '''COMPLETE'''
| valign="top" |
* Qatar
|}

=== Airbus A330-323 Liveries ===

{|
| valign="top" |
* Air Caraibes
* Asiana Airlines
* Delta - '''COMPLETE'''
* Korean Air - '''COMPLETE'''
| valign="top" |
* Malaysia - '''DEVEL''' (''Chris'')
* Thai Airways International - '''COMPLETE'''
* US Airways
|}

=== Airbus A330-343 Liveries ===

{|
| valign="top" |
* Aeroflot
* Air Canada (Star Alliance) - '''COMPLETE'''
* Air China - '''DEVEL''' (''Chris'')
* AirAsia X
* Air Transat
* Cathay Pacific - '''COMPLETE'''
* China Eastern - '''COMPLETE'''
* China Southern - '''COMPLETE'''
* Corsair International
* Dragonair - '''COMPLETE'''
* Edelweiss Air - '''COMPLETE'''
* EgyptAir - '''DEVEL''' (''Chris'')
* Etihad - '''DEVEL''' (''Chris'')
* Hainan - '''DEVEL''' (''Chris'')
* Lufthansa - '''COMPLETE'''
| valign="top" |
* Oman Air - '''DEVEL''' (''Sam C.'')
* Orbest Orizonia
* Ryan International Airlines
* Saudi Arabian
* SAS - '''COMPLETE'''
* SAS (Star Alliance) - '''COMPLETE'''
* Singapore Airlines - '''COMPLETE'''
* Swiss International - '''COMPLETE'''
* Thai Airways International - '''COMPLETE'''
* Thomas Cook Airlines Scandinavia - '''COMPLETE'''
* Turkish Airlines - '''COMPLETE''' (''Chris'')
* Virgin Atlantic
* XL Airways (Orbest)
|}

==Default Flight Database==

The Airbus A330-300 series do NOT have an airline's flight database. It's open for users to add their own routes. Nevertheless, a few Singapore Airlines A330-300 routes might be added to the default database in the near future.

== External link ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]

{{Airbus}}

[[Category:Airliners]]

Airbus A330-200 (Old)

2013-02-08T20:57:04Z

Sa7k: Fix videos which failed because of missing alignment

{{non-GPL}}

{{infobox Aircraft
|image = A332-splash.png
|name = Airbus A330-200 Series
|type = Wide-body Airliner
|fdm = JSBSim
|status = v2.0, Git Development Version
|authors = Narendran M, Chris M, Zhuang T, Geir M, Kyle D, A320neo Developers
|fgname = A330-203, A330-223, A330-243
|download = http://theomegahangar.yolasite.com/aircraft.php
|development = https://gitorious.org/fg-airbus-a332/airbus-a330-200-main
}}
This aircraft package is now rembrandt compatible! (Simply checkout the rembrandt branch from the git repository to get it)

The '''Airbus A330-200 series''' project consists of the '''Airbus A330-203''' (A330-200 with ''General Electric CF6-80E1 Engines''), '''Airbus A330-223''' (A330-200 with ''Pratt and Whitney PW4000 Engines'') and the '''Airbus A330-243''' (A330-200 with ''Rolls Royce Trent 772B-69 Engines''). The project uses theOmegaHangar's new [[Airbus A320neo|Airbus A320/30/40]] cockpit and systems and new Airbus A330-200 models. Feel free to start a discussion in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 the forum topic] if you'd like to contribute to the project.

==Airbus Systems==

===Airbus Fly-By-Wire===
The Airbus fly-by-wire (adapted from the Airbus A320neo fly-by-wire) is a system which continuously takes in the pilot's stick input, uses them as Pitch/Roll-Rate commands, and calculates the required surface deflection to achieve the commanded rate. The fly-by-wire also provides flight envelope protection and the soft/hard bank feature.

====Pitch/Roll-Rate and G-Force Command====
For the Roll Axis, the stick all the way to the left commands a negative 30 degrees roll rate and all the way to the right commands a positive 30 degrees roll rate.

As for the Pitch Axis, the commands are divided according to the airspeed of the aircraft. If the Airspeed is under 210 knots, pitch-rate is used and over 210 knots, g-force is used. Under 210 knots, pulling the stick all the way to the back commands a 30 degrees pitch rate and pushing it all the way forward commands a negative 30 degrees pitch rate. Over 210 knots, pulling the stick all the way to the back commands a 2.75G acceleration and pushing it all the way forward commands a -0.75G acceleration.

====Flight Envelope Protection====
For the Roll Axis, having the stick less than half way deflected either side, you get what's called a ''soft bank''. With a soft bank, the aircraft can't exceed 33 degrees of bank to either side. If the stick is deflected more than half way, you get a hard bank and the aircraft can be banked up till 67 degrees to either side.

For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.

=== Hydraulics System ===
The Airbus A320, A330 and [[Airbus A340|A340]] series have similar hydraulic systems. There are three hydraulic systems on the aircraft, each having it's own reservoir- the '''GREEN''' system, the '''YELLOW''' system and the '''BLUE''' system.

The Green system is powered by the Left Engine's Hydraulic Pump, the yellow by the Right Engine's Hydraulic Pump and the Blue System with an Electric Pump. During normal operation, each hydraulic system should have their hydraulic pressure between 2500 and 3000 PSI. (Pounds per Square Inch) The engine systems control the surfaces, stabilizers, flaps/slats and landing gears while the electric pump system connect to only the surfaces and stabilizers. In case a system fails, an alternate system can be used. The yellow system also has an electric pump which can be used to power the hydraulics using external power when the aircraft is on the ground.

The Yellow and Green Hydraulic systems have a power transfer unit which is used to transfer hydraulic pressure between the pumps in case there is a 500 PSI difference between the pressures in the green and yellow systems.

All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.

'''MORE SYSTEMS INFORMATION COMING SOON'''

== Example Flights ==

We'll show 2 example flights- a flight that uses a company route from the default flight database and a custom planned flight.

=== MIA134 from Brisbane to Singapore (Company Route) ===

MIA134 is one of merlion's alternate-day flights from Brisbane to Singapore. We'll just be using this as an example and you can use the same procedures from any route from the company database. (Take a look at our database flights below) Flight MIA134 is flown with an Airbus A330-243 (Rolls Royce Trent 772B-60 Engines) virtually registered S-QDAZ.

First, start-up at any of the parking ramps at Brisbane's (YBBN) International Apron. As Brisbane doesn't have parking positions at the moment, start-up on runway 01 and taxi-to (best using pushback) a parking gate in the International Apron.

==== Pre-Flight Planning ====

To start with the pre-flight planning, we need electrical power. For Airports that provide external power, we can use that and for other airports, the APU can provide power. At Brisbane, external power is available, so make sure your ground services dialog has external power box enabled and turn on '''EXT PWR''' from the ''Overhead Panel''. (View)

Before we start anything, let's make sure everything's how they should be. Make sure only the following Overhead panel buttons have OFF showing on them- HYD YELLOW ELEC PUMP, ENG1, ENG2 and CTR TNK LTK FUEL PUMPS 1 AND 2, BAT1, BAT2, GEN1, GEN2 and APU GEN. EXT PWR should show ON. Now, look at the Pedestal and make sure both engine master switches are at OFF, the throttle is at idle, the engine mode is set to NORM, the speed-brakes are at 0, the parking brake is ON and the Flaps Lever is at 0. Let's now start with the pre-flight planning.

* Turn to the ''FMGC/mCDU View'' and turn on the Airbus mCDU by rotating (scroll) the BRT knob to full.

* Click on DATA and then A/C STATUS. Make sure the ACTIVE NAV DATABASE is ''27MAY-26AUG MIADatav3.1''. If not, please re-download the ''Database/Company/routes.xml'' file from gitorious.

* Now, click on INIT to head to the routes initialization page. You can initialize the company route by entering the company route ID (reference below) or the departure and arrival ICAOs. I normally enter the departure and arrival ICAOs as that way, it gives you all available routes you can choose from. So enter '''YBBN/WSSS''' and click on the LSK (Line Selector Key) next to FROM/TO.

* The mCDU will show 2 available routes (MIABNESIN1 and MIABNESIN2) which you can scroll through using the left and right arrow keys on the mCDU keypad. We'll be using MIABNESIN2 for this flight, so view that and click on the LSK next to INSERT. Once you do that, you should see that MIASINBNE2 would be written under CO_RTE and YBBN/WSSS would be written under FROM/TO.

* Enter the Flight Number '''MIA134''' and click on the LSK next to FLT NUM. '''(OPTIONAL)'''

* If you want, you can also enter a COST INDEX for the flight (normally between 25 and 40). '''(OPTIONAL)'''

* If you have an alternate route (not supported atm), you can enter the Alternate airport ICAO and RTE ID in the ALTN/CO_RTE Field.

* The final step in the INIT A page is your cruise altitude and Temperature. We'll be cruising at Flight Level 360 (FL360/36,000 ft) and checking the ''Environment>Weather Dialog'', it's about -55 degrees at that altitude, so enter '''360/-55''' and hit the LSK next to CRZ ALT/TEMP.

''NOTE: To get the '''-''', press on the '''+/-''' key in the keypad twice.''

* After INIT A is complete, let's proceed to INIT B (aka. FUEL PREDICTION Page), click on the RIGHT ARROW KEY on the keypad to go there.

''NOTE: Please skip the next 2 steps for the moment as this part requires fixing.''

* Once there, the trip fuel/time should show about 120 blocks of fuel (atm, it shows 24 but it will be fixed soon) required for the flight. The Aircraft can hold a maximum of 172.5 Blocks (1 Block = 804 KG JET-A Fuel). It should also show that the total flight will be about 442 minutes long using the initialized route. That is 8 hours and 22 minutes, a decent time for about 4000 miles.

* We'll take 10% fuel with us for reserves, so enter '''0/10''' and hit the LSK next to RSV. The mCDU will automatically calculate our extra fuel, TOW (Take-off Weight) and LW (Landing Weight).

* Now, click on F-PLN to go to the Primary Flight-plan Management Page. Here, you'll see the automatically initialized flight plan which you can scroll through using the up and down arrow keys on the keypad. Atm, we don't need to make any changes to our flight-plan as the company route sets everything perfect for us. We'll come back to F-PLN Lateral Revision (LAT REV) in the next custom planned example flight.

* We need to select a DEPARTURE and ARRIVAL procedure for our flight. To select a DEPARTURE Terminal Procedure, click on the LSK next to YBBN (Right above F-PLN DISCONTINUITY) and click on the LSK next to DEPARTURE.

* I'll be using runway 19 for departure (Currently Winds are 200@9), so I click on the LSK next to 19.

* Our first waypoint (after YBBN) is WOODY, so I want a DEPARTURE PROCEDURE that'll take me to WOODY. A procedure available for Runway 19 is ''WODY2A.19'' (at the end of the list). Select that and hit the LSK next to INSERT.

* Now, for the arrival procedure, you want to find your last waypoint before WSSS, so go to the F-PLN page and scroll to the end. With this route, ''REPOV'' is the last waypoint. (With MIABNESIN1, LAVAX is the last waypoint.

* Scroll back up and click on the LSK next to DEST WSSS and then select ARRIVAL.

* We'll be landing on Runway 20R (usually the default intl. runway at WSSS), so I select 20R. For the Arrival Procedure, select and INSERT REME6B.20R as that procedure starts at REPOV.

''NOTE: Small sections based on the PERF, DIR and PROG pages are remaining but we'll get back to that once it's completely functional.''

We have completed out basic flight-planning. We will focus on Radio Navigation later. Let's now fuel up for the flight. As we entered in the mCDU, we'll be starting with 130 blocks of fuel for this 8 and a half hour flight. That's 104,500 KG JET-A fuel. Open the Fuel Truck dialog, enable to truck, connect it to the aircraft, enter '''104500''' in hte REQUEST KG and Start Filling up the aircraft. Once the fueling is complete, we can disconnect the fuel truck and proceed to starting up the aircraft. Remember to first disconnect all ground services and remove the chokes.

==== Manual Engines Start-Up Procedure ====

* Turn on the Beacon Lights from the Lighting Control Panel.

* Look up at the overhead panel and turn on the APU by turning on the APU MASTER SW and the START button. You should hear the APU spooling. Once it's started, turn off the APU START switch and turn on the APU GEN.

* To get fuel to the engines, you need to turn on the LTK PUMPS, so turn on all the ENG1, ENG2 and CTR TNK FUEL PUMPS.

* Switch to Pedestal View and in the throttle quadrant, set the Engine MODE to START, and then turn both engine master switches to ON.

* Keep an eye on the Upper ECAM. When both Engine N1% exceeds 25%, the engines are started and running. Turn the Engine MODE back to NORM and turn off the APU.

* Turn on the Navigation Lights.

Release Parking Brakes and use 2 notches of Flaps for take-off. Pushback and taxi to the runway as usual. While taxiing, you could set your autopilot and other preferences. For autopilot, I'm going to make sure everything is disarmed and then set speed to IAS:250|MACH:0.72, altitude to 36000 ft (switch the black knob in behind the ALT knob to 1000 for easier scrolling, V/S to 2200 and finally click on the HDG knob to turn it to ''Managed'' Mode. You can also set ND and Lower ECAM Display Pages- I use the NAV page on the ND with 40 nm range (VORD, NDB and ARPT selected), and normally keep the FUEL page on the Lower ECAM. If you need to check another system, you can use the switching panel to change to that display.

Finally, remember to set your altimeter setting. Get your altimeter setting from Environment>Weather and scroll the altimeter setting knob on the Glare-shield panel to that reading.

''NOTE: Managed Mode means the FMGC tells the computer where the plane should go. This is equivalent to LNAV on Boeing aircraft.''

==== Take-off and Cruise ====

Once you're holding short, revise your reference speeds. At this weight, they'd be- V1:140, Vr:150, V2:156.

When the runway is clear (and/or you have ATC's permission), taxi on to the runway and turn on the Strobe Lights. Power up the throttle all the way, and rotate at Vr and make sure you're airborne by V2. Retract your gears and when you reach the respective flaps extension speeds (PRINTED ON THE MAIN PANEL), retract the respective flaps. Once you've maintained a steady climb, turn on the A/THR and AP1 from the Glare-shield panel.

The autopilot will automatically fly the departure procedure you entered and then transition to the F-PLN (flight-plan) from the Company Route. Once over 10000 ft, switch to 280 KIAS Speed and keep climbing, Around 18000 ft, switch to mach (setting at 0.72) and reduce the V/S to around 1800 fpm.

Once you're over FL260 (26000 ft), reduce your V/S to 1000 fpm and increase mach to 0.78. Then sit back and relax (or go do something else) while the computer automatically takes you to your destination.

'''REST COMING UP SOON'''

=== Custom Emirates Flight from Frankfurt to Munich ===

This flight was requested by Detlef N. (MIA0283), and video tutorials were recorded for different sections of the flight. The videos can be viewed below or in the ''FlightGear Airbus'' YouTube channel. Thank you for watching!

==== Flight Planning ====

{{#ev:youtube|R66q_10dwKw|480|auto|Part 1: Flight Planning}}

==== Manual Start-up ====

{{#ev:youtube|8TI14RJDn2k|480|auto|Part 2: Manual Start-up}}

==== Take-off and Climb ====

{{#ev:youtube|IpkdhebC4-o|480|auto|Part 3: Take-off and Climb}}

''NOTE: Cruise skipped due to the fact that it may be '''boring'''''...

==== Descent and Autoland ====

{{#ev:youtube|NeX3samzrqU|480|auto|Part 4: Descent and Autoland}}

== Liveries ==
The Airbus A330-200 series have liveries for each variant (203, 223 an 243) and are managed by Chris Mueffelmann. Please let us know if you're creating a livery by changing the status on the livery below so that duplicates are avoided.

=== Airbus A330-203 operators ===
{|
| valign="top" |
* Afriqiyah Airways - '''COMPLETED'''
* Air Algérie - '''COMPLETED'''
* Air Caledonie International (Aircalin)
* Air Europa - '''COMPLETED'''
* Air France - '''COMPLETED'''
* EVA Air - '''COMPLETED'''
* EVA Air (Hello Kitty) - '''COMPLETED'''
| valign="top" |
* Jet Airways - '''COMPLETED'''
* Jetstar Airways
* KLM Royal Dutch Airline - '''COMPLETED'''
* Qantas Airways - '''COMPLETED'''
* Qatar Airways - '''COMPLETED'''
* TAM Linhas Aereas - '''COMPLETED'''
* Turkish - '''COMPLETED'''
|}

=== Airbus A330-223 operators ===
{|
| valign="top" |
* Air Berlin - '''COMPLETED'''
* Air Caraibes
* Air Greenland - '''COMPLETED'''
* Air India - '''COMPLTED'''
* Atlasjet - '''COMPLETED'''
* Brussels Airlines - '''COMPLETED'''
* China Southern - '''COMPLETED'''
* Delta Airlines - '''COMPLETED'''
* Edelweiss Air - '''COMPLETED'''
| valign="top" |
* Eurofly - '''COMPLETED'''
* Hong Kong Airlines - '''COMPLETED'''
* Korean Air - '''COMPLETED'''
* Malaysia Airlines - '''COMPLETED'''
* Royal Jordanian - '''COMPLETED'''
* Swiss International Air Lines - '''COMPLETED'''
* TAM Linhas Aereas- '''COMPLETED'''
* TAP Portugal - '''COMPLETED'''
* Vietnam Airlines - '''COMPLETED'''
|}

===Airbus A330-243 operators===
{|
| valign="top" |
* Aeroflot
* Air China - '''COMPLETED'''
* Air Europa - '''COMPLETED'''
* Air Nigeria
* Air Transat - '''COMPLETED'''
* Avianca - '''COMPLETED'''
* China Eastern - '''COMPLETED'''
* Corsairfly - '''COMPLETED'''
* Cyprus Airways - '''COMPLETED'''
* Egyptair - '''COMPLETED'''
* Emirates - '''COMPLETED'''
* Etihad - '''COMPLETED'''
* Garuda Indonesia - '''COMPLETED'''
* Gulf Air
* Hainan Airlines
* Hawaiian Air
| valign="top" |
* Hi Fly - '''COMPLETED'''
* Hong Kong Airlines - '''COMPLETED'''
* Jet Airways - '''COMPLETED'''
* Middle East Airlines
* Monarch Airways - '''COMPLETED'''
* Oman Air - '''DEVEL''' (''Sam C.'')
* Sichuan Airlines - '''COMPLETED'''
* South African Airways - '''COMPLETED'''
* SriLankan Airlines - '''COMPLETED'''
* Thomas Cook Airlines - '''COMPLETED'''
* Thomas Cook Scandinavia - '''COMPLETED'''
* US Airways
* Virgin Australia
* XL Airways
* Yemenia Airlines - '''COMPLETED'''
|}

==Default Flight Database==

The Default Flight Database contains [[Merlion Virtual Airlines]] Airbus A330-200 Routes. This database can be used by anyone, whether he/she is a merlion pilot or not. The example flight above explains how to use routes from the Flight Database.

If you fly for a different Virtual Airline which uses the Airbus A330-200 (203/223/243), please contact your staff for the flight database.

* Current Active Database - '''MIA_Data_v3.1''' ''(27MAY-26AUG)''
* Previous (Standby) Database - '''MIA_Data_v3.0''' (DOES NOT EXIST YET)

===Available Routes Tables===

''The following routes are complete and available.''

{| class="wikitable sortable"
|-
! FLT NO !! DEP ARPT !! ARR ARPT !! A/C REG !! RTE_ID(s)
|-
| MIA131 || WSSS || YBBN || S-QDAZ || MIASINBNE1, MIASINBNE2
|-
| MIA132 || YBBN || NZAA || S-QDAZ || MIABNEAKL1
|-
| MIA133 || NZAA || YBBN || S-QDAZ || MIAAKLBNE1
|-
| MIA134 || YBBN || WSSS || S-QDAZ || MIABNESIN1, MIABNESIN2
|-
| MIA135 || WSSS || FAJS || S-QDBZ || MIASINJNB1
|-
| MIA136 || FAJS || SBGR || S-QDBZ || MIAJNBGRU1
|-
| MIA137 || SBGR || FAJS || S-QDBZ || MIAGRUJNB1
|-
| MIA138 || FAJS || WSSS || S-QDBZ || MIAJNBSIN1
|-
| MIA139 || WSSS || RJGG || S-QDCZ || MIASINNGO1
|-
| MIA140 || RJGG || KLAX || S-QDCZ || MIANGOLAX1
|-
| MIA141 || KLAX || RJGG || S-QDCZ || MIALAXNGO1
|-
| MIA142 || RJGG || WSSS || S-QDCZ || MIANGOSIN1, MIANGOSIN2
|}

The Rest of Merlion's Flight Database is available for merlion pilots from the website Downloads section.

==Important developments remaining==

''We have completed the highest priority developments on the list, if you'd like us to do anything for the aircraft, please make a note below.''

==Important Recently Completed Developments==

* Modeled the Rolls Royce Trent 772B-60 Engines for the A330-243
* Animated Flaps, Speed-brakes and Parking Brake Levers (NOT PICK, ONLY TRANS/ROTATE)
* Animated the Throttle Quadrant (incl. Engine cutoffs - REQUIRED FOR MANUAL START-UP) - ''Manual Start-up is now possible''
* Fixed the '''Blue''' Hydraulic System
* Completed Separate Engine Sounds for the each variant

== External link ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16438 Development topic]

{{Airbus}}

[[Category:Airliners]]

FlightGear hangars

2013-01-24T18:57:33Z

Sa7k: Dead links

{{cleanup}}

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

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

Be careful with external links!

== Official hangars ==
=== Aircraft ===
* [http://www.flightgear.org/download/aircraft-v2-8/ FlightGear Official 2.8 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear Official 2.6 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-4/ FlightGear Official 2.4 Hangar] (Legacy site)
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar] (Legacy site)
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Liveries]

== Unofficial sites ==
=== Aircraft hangars ===
* [http://www.gitorious.org/fg-airbus-a332 Airbus A330-200 Series Development Git] (A330-203, A330-223, A330-243 - FGAirbus/theOmegaHangar)
* [http://www.gitorious.org/fg-airbus-a333 Airbus A330-300 Series Development Git] (A330-303, A330-323, A330-343 - FGAirbus/theOmegaHangar)
* [https://www.gitorious.org/airbus-aircraft Airbus Aircraft Development Git] (A320, A330, A340-300, A380 - various authors)
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] with [http://gitorious.org/anders-hangar aircraft repositories at gitorious].
* [http://andinogonthaeler.wordpress.com/ Andino's Hangar] (Boeing 707-3J9C and 707-320C, 777-200LR).
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a YASim intro)
* <s>[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]</s>{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)
* <s>[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]</s>{{dead link|2012-04}} (a few well made aircraft)
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}} (Blog format)
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons)
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (164+ original aircraft)
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles)
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)
* [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar] Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
* [http://flightgear.bplaced.de/ longfly's hangar] (not only German!)
** [http://flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts] (under development)
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)
* <s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
* [http://theomegahangar.yolasite.com/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)
* [http://pjedvaj.eu5.org/ pjedvaj's Hangar] (MiG-21bis, PC-9M, PC-21, T-50, Harrier GR.1, F-35B, RAH-66)
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)
* <s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many Brazilian aircraft articles)
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
* <s>[http://sydhangar.daffodil.uk.com/ Syd's Hangar ]</s>{{dead link|2012-04}} (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]
* [http://acjza-hangers.webs.com/ ACJZA's Hanger] (A310, BAe 146, C-Series)

=== Old Hangars ===
* [http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)

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

=== Homepages, blogs, etc. ===
* [http://www.jaunty.bplaced.net/flightgear/index.php A small FlightGear page]
* <s>[http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]</s>{{dead link|2013-01}}
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]
* <s>[http://www.grupofgbr.com.br/ Grupo FGBR Brazilian Portal]</s>{{dead link|2013-01}}
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)
* [http://flightgear2009.blogspot.com/ FlightGear Brasil 2009] (non-english)
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)
* [http://flightgearcorner.tk The FlightGear Corner] (News, Downloads, Tutorials and more)
* [http://www.fguk.eu/ FlightGear United Kingdom]
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]
* <s>[http://tehwarlock.tk/ Tehwarlock Blog]</s>{{dead link|2012-04}}
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)
* [http://flightgear.mxchange.org/ Quix0r's FlightGear Website] Simple tutorials and fgdata.bundle

=== Other FlightGear repositories/mirrors ===
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery)
* [http://www.flightgearplanes.com Flightgear Planes Website]
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]

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

[[Category:List]]

FlightGear Newsletter November 2012

2012-11-29T16:12:44Z

Sa7k: Fix link

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and the changelog of the upcoming release.''

== Release preparations ==
The next FlightGear version will be released around February 17, 2013. In order to provide a stable and smooth release we've set up a [[release plan]]. We keep you up to date with our current state through various channels, including the [[mailing list]], [http://flightgear.org/forums forum] and [http://facebook.com/FlightGear Facebook page].

Coming December 17, our [[Git]] repository will be declared "frozen". This means that no new features or major changes shall be pushed. This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches (January 17).

Aircraft in fgdata may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in the upcoming period.

Keep in mind that the people that are able to commit your stuff are just as busy finishing their own work as you are! Therefore it is important that you create merge requests for everything that you'd like to see included in the upcoming release, as soon as possible. This includes new aircraft and updates to existing aircraft. This will also give everyone more time to check for bugs.

<div style="width: 400px">{{GitStatus}}</div>

== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog of the upcoming release: [[Changelog_3.0.0]].

=== Random Buildings ===


=== Project Rembrandt ===
=== Canvas System ===


=== High Level Architecture ===
=== FlightGear an Android ===

=== Usability Improvements ===

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===

Please see [[Howto:Start core development]]

== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Translators required ==
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.

=== New aircraft ===

=== Updated aircraft ===
'''Mudry Cap10B :''' New update of the [[Mudry_Cap10b|Cap10B]] by PAF team. Full Rembrandt compatibility (lights, transparency, 3D), full dual control (perfect for aerobatic learning), rating system, new texture, new shader... 
Download available on [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar PAF team hangar]

=== Liveries ===

== Scenery corner ==
=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
[[Image:Drivinghorses.jpeg‎|thumb|Driving horse in FlightGear]]
A proposal for funny flight experiences with [http://www.marc-kraus.de/fg| The Lake of Constance Hangar] Awesome contributions.

===Driving horses with helicopter===
[[Image:Antenna-polar.png|thumb|Antenna far-field gain plot]]
Yes, you've heard it clear. The lake of Constance Hangar runs by incredible D-MKF1 offers you the opportunity to drive a horse by helicopter, yeah¡ ride it on through vastness of FlightGear.

===Radio Range - Direction Finder Navigation over Dual Control===
For those whose pervades the vintage's way to fly, the radio finder navigation over MP will satisfy your dream to fly, live back into the golden years of aviation, flashback guarantied.

Just try the [http://www.marc-kraus.de/fg| DO-X] from the Lake of Constance Hangar with your friends over dual control. We recommend Saint Martin TNCM - Saint Barth's area.

Your mission is to fly the area, training pilot-copilot quick coordination, improve your visual orientation because once you are out of island visual range you'll need to be ready to use the radio finder as a real copilot. Our goal is that you'll improved your real nav skills, getting back to the roots of radio. The radio range - Direction Finder Navigation age.

Have you tried it with a couple of aircrafts on Mode42 - Four friends two planes?

No matter is you are on 42, 15, 35, 60 or 91 years old. You must try.

... Are you still missing in the middle of the Caribbean Sea?
follow the <Beep.. Beep....Beeep> audio signal in code Morse of the selected radio station.
The more accurate is your radio tuning operator the more accurate will be your heading.

Do you know that [http://wiki.flightgear.org/Radio_propagation Radio and propagation] can also
affect your Radio Range?

Long Life to The Radio Range for FlightGear.

=== Flying Banana Co. Container Stevedore===
Searching for skilled pilots. The "famous Flying Banana Co" air freighter need pilots for their annual banana's harvest campaign at the end of year.

Became in a Bananaco pilot, your task is to move containers. You can use CH47, H-21C their famous flying bananas also called "Bananacos" a word that means Huge Bananas.

They'll pay well for your skills.
Only FG pilots.
Flying Banana Co. a company where freedom to fly matter operates in Saint Barth's.

===Ferry MP on a lake===
So far to be a normal lake. We are in the epicenter of creativeness.

MP-LODI-TABOR Demo for "ferry" action on the "Lake of Constance"

the last and funny action by [http://marc-kraus.de/fg| The Lake of Constance Hangar]

== Aircraft reviews ==

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FSweekend 2012 ===
For the seventh year in a row, a team of FlightGear developers represented FlightGeat at the largest anual flight simulator weekend in the world. [[FSweekend 2012]] was another succes.

* [http://www.flickr.com/photos/durktalsma/sets/72157631936384731/ Photo gallery #1]
* [http://www.flickr.com/photos/70866411@N05/sets/72157631926925511/ Photo gallery #2]

=== FlightGear on YouTube ===
{{#ev:youtube|1kB5KqaSRGo|400||Who said you need a yoke to fly? With a little DIY-ing, you can control an aircraft with your bare hands!}}

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===
=== Review of Flightgear ===
A new user of Flightgear blogged a review.
Read it here [http://shallowreviews.blogspot.dk/ Shallow Reviews].

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten.

=== Call for volunteers ===
* The [[FGRadar]] project (standalone ATC client) is looking for people to join the project, give ideas, requests or opinions.
* The [[Flightgear On Android]] team is looking for testers
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.
* The [http://mpserver15.flightgear.org FGTracker Web] is looking for a web programmer. Details are [http://mpserver15.flightgear.org/modules/news/article.php?storyid=14 here].

=== Did you know ===

[[Category:FlightGear Newsletter|2012 11]]

Es/Marble

2012-09-23T02:49:27Z

Sa7k:

[[File:Marble and FG session.png|thumb|270px|Marble mostrando el recorrido de la sesión de FG]]

== Introducción ==
Marble es un programa de KDE o Qt que muestra una representación en 3D del globo terráqueo y tiene la posibilidad de superponer diferentes capas.
En la versión lanzada con KDE 4.9 es posible mostrar la posición del avión tomada de Flightgear y mostrarla en el mapa elegido.

== Uso ==
Arrancar Marble (la versión 1.4 o superior) y habilitar en el menú Vista la opción "Posición actual".

Luego seleccione en la pestaña "Posición actual" como seguimiento de posición "Flightgear".

Ahora iniciemos una sesión de Flightgear con la opción extra "--nmea=socket,out,5,localhost,5500,udp" para hacer que su aeronave se muestre en Marble.

[[File:Marble showing FG track.png|thumb|400px|Ventana de Marble con visualización del recorrido]]

[[Category:Software]]
[[Category:GPL software]]
[[en:Marble]]

Marble

2012-09-23T02:48:52Z

Sa7k: Add ES translation

[[File:Marble and FG session.png|thumb|270px|Marble showing the track of the running FG session]]

== Introduction ==
Marble is a KDE application that shows a 3D representation of the world and has the ability to overlay different layers.
Since KDE 4.9 it is capable of getting the aircraft's position from Flightgear and showing it on the map.

== Usage ==
Start up Marble (version 1.4 at least) and enable under View the "Current Location" checkbox.

Then select in the "Current Location" tab "Flightgear" as Position Tracking.

Now you can start up a Flightgear session with the additional option "--nmea=socket,out,5,localhost,5500,udp" to make your aircraft show up in Marble.

[[File:Marble showing FG track.png|thumb|400px|Marble window with track overview]]

[[Category:Software]]
[[Category:GPL software]]
[[Es:Marble]]

Es/Marble

2012-09-23T02:46:58Z

Sa7k: Traducción al castellano