FlightGear wiki - User contributions [en]

FlightGear Newsletter July 2012

2012-07-28T17:37:13Z

Condor:

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

== Development news ==

=== Adopting the new Canvas 2D rendering system ===

As of July 2012, FlightGear core developers agreed to adopt Tom's new [[Canvas]] 2D rendering system which is purely property-driven and handles all [[Original Canvas Proposal|2D drawing via the FlightGear property tree]]. Initially, the idea will be to replace the current GUI toolkit (PUI/PLIB, which has shown many limitations over time) and use a purely [[Canvas]]-based implementation instead, which will be mostly implemented in scripting space using Nasal and merely use the Canvas system as its rendering backend. The implementation details are covered at [[Canvas Widgets]].
This step will make it eventually possible for end users to easily customize the FlightGear GUI and its appearance by creating custom GUI styles (themes/skins), but also by creating completely new GUI widgets using an SVG editor like Inkscape.

Currently (07/2012) only drawing inside an existing (PUI) dialog is possible, but the idea is to slowly implement the current functionally in Nasal and get rid of the hardcoded PUI widgets. Only some code for mouse/keyboard interaction with Nasal will be needed.

In contrary to using some hardcoded GUI system (PUI, osgWidget, etc.) this approach would give much more flexibility and also the means of modifying and creating new widgets without the need to touch any core code.

With the Canvas system every type of widget would be possible, so that also things like submenus can be realized.
Another advantage of the Canvas approach is that it is heavily using the property tree and therefore is already fully accessible from Nasal code and also configurable with the existing xml formats.

The point of the canvas widget demo is to demonstrate how powerful and flexible the new canvas system really is, i.e. it cannot just be used for aircraft scripting (instruments, MFDs), but also for GUI scripting - which means that using the canvas system would unify the 2D rendering backend (all can be handled via canvas), while reducing the amount of C++ code we have doing these things, which would mean that the GUI system could be entirely maintained in scripting space, i.e. as part of the base package, by people who don't need to know C++ - some basic Nasal knowledge will do.

Basically, adopting the new canvas system for such and similar purposes, will mean that tons of old/oudated C++ code can be phased out and replaced by a single consistent implementation in C++, that is using modern C++/OSG code - which ultimately also means that OSG itself can make more assumptions about what's being rendered, so that more optimizations (= better frame rates) can be more easily accomplished by using OSG coding patterns and protocols, instead of outdated/custom/3rd party libraries which would need to be manually baked into the existing FG/SG/OSG eco system.

Now what's cool about the canvas system is that it's integrated in such a fashion that it will keep working with the old GUI code still in place.In addition, all of the exsting GUI features (layouting, XML processing) are implicitly supported due to the way the canvas system is implemented. These are real roadblocks when implementing a new GUI library next to PUI, because all of the existing stuff would need to be explicitly ported (either in C++ space or by converting tons of XML files).
Overall, the canvas system will give us all of this "for free", and it will mean less C++ code in the source tree, too - i.e. better maintainability.

Also, once the standalone [[FGCanvas]] becomes available, it would also be possible to run the GUI in multiple windows or even in separate processes.

In addition, by using the canvas system for GUI widgets, it would also be possible to render aircraft instruments, MFDs, HUDs etc '''inside''' GUI dialogs, too.

{{#ev:youtube|CIS8UyuJLgM}}

Future plans include reimplementing the current HUD and 2D panel systems using the Canvas system. In addition, the canvas system will provide an opportunity to increasingly unify the 2D rendering backend in FlightGear in the months to come: [[Unifying the 2D rendering backend via canvas]]. Furthermore, the canvas system provides a novel way to abstract away the creation of fully interactive and dynamic moving map displays and GUI widgets for charting using so called [[Canvas Maps]].

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

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

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

=== A new hangar: Lukas' hangar ===

A new hangar for Flightgear has opened: Lukas' hangar. There you can find some Liveries and Scenery projects, inter alia airports of the Balearic and Canary Islands. The best is that you have a look in [http://lukashangar.jimdo.com/ Lukas' hangar].

== Comunity news ==
FlightGear
=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Tools ===
FlightGear made it again. For the first time in flight simulators history, it's never been that easy to contribute to scenery! If you have already copy/pasted once in your life, then you are able to contribute to FG scenery! A direct copy/paste of new objects lines (STG format) in a webform now allows you to update scenery objects all over the world for all FG users using Terrasync.
Add your email address to be informed of the progress of the update. Import should happen soon (let's say between 24 and 72 hours, but it depends on the poor scenery maintainer(s) workload!).

Want to try it in production? Click [http://scenemodels.flightgear.org/submission/ here] then choose mass import, or via the scenemodels website menu (Contribute => Mass shared object position insertion).

Please note:
* You must only import new objects, not the whole STG file you're working on!
* Don't add models not present in the FG scenemodels database, nor (yet) OBJECT_SIGN nor OBJECT_STATIC.
* Don't add forest or other items linked to the landcover. Those items have to be generated based on the landcover, not on objects! The only trees accepted will be those located on airport boundaries, for example.
* The data you're asking for import should be based for elevation on the terrain shipped with FlightGear/Terrasync, and not on a terrain you could have downloaded or compiled yourself. Else, your objects could appear floating or sunk in the terrain...
* Finally, the import is limited to 100 lines per submission (let's think about the poor scenery maintainer(s)...)
* The import is quite sensitive about the data in entry, which goes through quite a lot of checkings, including humans, before insertion.

Next step is the import script for 3D models. It's on its way, finished to approximately 90%. Be patient, it's quite a complex tool to achieve.

=== Mapserver ===
[[File:Mapserver - Update and Delete links.png|thumb|Mapserver showing update and deletion links.]]
Some mapserver news here, as we have not been talking about this very useful tool for a while. Mapserver has been going through updates this month, one of the most useful being the possibility to view details on a object and to edit/delete it directly from the map. This has never been so easy to update/delete a shared object directly from the map (see the screenshot). Note that you need to have a sufficient zoom factor (>=16) to see the red arrows appear, then you can click on them. Special thanks to Martin, Julien and Gijs for updating and testing this tool.
To use it, please have a look [http://mapserver.flightgear.org/popmap/?lat=52.47492&lon=13.38199&zoom=16&layers=B00FFTTTTT here].

=== Manhattan shapefile ===
[[File:Manhattan v0 vs cs-osm.png|thumb|270px|Custom scenery with OSM line data (left) versus v0 landclassing.]]
Gijs' handmade shapefile for Manhatten, New York is finally available at [http://mapserver.flightgear.org the mapserver]. Compared to the current (v0) shapefiles, the custom shapes are much more accurate and have a higher level of detail. The most obvious improvements are the additional parks and the islands, including Liberty Island.

Those of you that know how to use [[TerraGear]] can build Manhattan, others will see it in a next scenery build.

=== OpenStreetMap license update ===
As you will probably know, [[OpenStreetMap]] is changing its license. When the license change is completed, we will be able to use OSM data in the official FlightGear scenery. As not all OSM contributors agreed to the new license, data from those sources had to be removed. This "redaction process" is completed as of the end of July. Even tough this is a big step forward, ''the license hasn't changed yet''. See the OSM blog for updates and latest news on the matter: http://blog.osmfoundation.org/

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

Fallen- revisited his old style video recording flying from San Francisco Int. to the Nimitz carrier, but at night with the new Rembrandt enabled F-14 Tomcat with new lights coming to FlightGear.

FlightGear 2.8 Night with Rembrandt
{{#ev:youtube|q951rsP0DBk}}

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
Two more multiplayer servers have been setup:<br />
*'''mpserver15.flightgear.org''' (''North Point, Hong Kong'')
:Courtesy of Hazuki Amamiya
*'''mpserver16.flightgear.org''' (''Dallas, TX, USA'')
:Courtesy of Rob Dosogne ([http://www.flightgear.org/forums/ucp.php?i=pm&mode=compose&u=9926 truthsolo])
:Also hosts a new [http://mpserver16.flightgear.org/ Server Status] page.

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

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter|2012 07]]

FlightGear hangars

2012-07-28T16:05:12Z

Condor: /* Aircraft hangars */

{{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-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://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)
* [http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar] (a few well made aircraft)
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-04}} (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] (Mikoyan-Gurevich MiG-21bis, Pilatus PC-9M, Pilatus PC-21, Hawker Siddeley Harrier GR.1, Boeing-Sikorsky RAH-66)
* <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]

=== 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]
* [http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]
* [http://www.grupofgbr.com.br/ Grupo FGBR Brazilian Portal]
* [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://lukeaflightg.blogspot.co.uk/ FlightGear Blog] (Daily development updates, news, video tutorials and more)

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

De/Howto: Edit a livery

2012-07-22T22:24:48Z

Condor:

In diesem [[:Category:Howto|howto]] findet man eine Anleitung zum Bearbeiten einer Livery (Lackierung) eines Flugzeugs in Flightgear.

==Was ist eine Livery?==
Eine Livery ist die Art ein Muster z.B.:einer Fluggesellschaft auf ein Flugzeug zu bringen. Andere Flugsimulatoren nennen das "paint" oder "repaint". Solch eine Livery besteht aus einer oder mehreren Texturen welche das 3D-Modell des Flugzeugs umgibt. Die meisten Flugzeuge in Flightgear kommen als ZIP-Datei, welche ein wenig Text, 3d-Model und Bilddatein in mehreren Ordnern enthält. In dieser Struktur gibt es eine oder mehrere Liveries und ein Paar Textdatein, XML-Datein, die die Verwendung beschreibt. Die Lackierungen findet man in der Regel in dem Models/Liveries-Verzeichnid oder einem anderen Verzeichnis, je nachdem, wie der Autor die Dateien und Verzeichnisse organisiert.

==Allgemeiner Arbeitsablauf==
Es gibt ein Paar Möglichkeiten, um eine neue Lackierung zu erstellen. Zuerst schaut man in der[http://liveries.flightgear.org/ Livery database] nach, ob die gewünschte Lackierung von einem bestimmtem Flugzeug bereits existiert, wenn ja, dann macht man eine andere. Außerdem kann man Vorlagen für Lackierungen, genannt Paintkits, für ein paar Flugzeuge dort finden, aber manchmal sind Paintkits enthalten mit dem Flugzeug enthalten.
Beim Erstellen der Lackierung ist der Arbeitsablauf im Grunde in dieser Reihenfolge:
# Überprüfen Sie die FlightGear Liveries database, um doppelte Arbeit zu vermeiden
# Finden von Originalbildern,
# wenn möglich ein Paintkit besorgen,
# die Lackierung erstellen,
# die Lackierung öffentlich teilen

==Suche nach Originalbildern==
Beim Erstellen einer Lackierung, basierend auf realem Flugzeug, sollte man zunächst Originalbilder betrachten. Man braucht Bilder des Flugzeugs mit der Lackierung von beiden Seiten, evtl unten und oben. Stellen Sie sicher, dass Sie auch Bilder von einem bestimmtem Winkel haben. Ein Drei-Wege-Zeichnen kann hilfreich sein, wenn man z.B. Nieten hinzufügen möchte oder kein Paintkit existiert. Stellen Sie sicher, dass Sie viele gute Originalbilder von der Lackierung des Flugzeugs haben. Am Ende dieses Artikels finden Sie eine Liste von Webseiten, die solche Bilder enthalten.

==Bearbeiten der Lackierung==
[[File:Vector vs Raster Graphics.png|150px|thumb|right|Hier sieht man den Unterschied zwischen Vektor und Raster: links ist eine Vektor- und rechts eine Rastergraphik.]]
[[File:Livery layers in Inkscape (Slovenian PC-9M).png|150px|thumb|right|Inkscape-Schicht-Dialog. Die vier oberen Schichten sind das Paintkit, während der Rest der Schichten die Lackierung sind.]]
[[File:Finished Slovenian PC-9M livery (3DViewer screenshot).png|150px|thumb|right|3DViewer Bildaufnahme von einer fertigen Lackierung über das Modell drapiert.]]
[[File:Finished Slovenian PC-9M livery (in-game screenshot).png|150px|thumb|right|FlightGear 2.0.0 Im-Spiel-Bildaufnahme mit der fertigen Lackierung.]]
Sollte das Speichern der bearbeiteten Lackierung anhand des Ablageortes nicht möglich sein, so verschiebt/kopiert man die Lackierung an einen anderen Ort, wo sie sich speichern lässt.

===Vektor oder Raster===
Es gibt im Allgemeinen zwei Möglichkeiten, die Lackierung zu bearbeiten: zum Einem Raster-Grafik-Bearbeitungsprogramm wie GIMP (empfehlenswert) oder Photoshop oder ein Vektor-Graphik-Bearbeitungsprogramm wie Inkscape oder Paint. GIMP und Inkscape sind beide freie und open-Source-Software. Wenn man keine Erfahrung mit einem Vektor-Graphik-Bearbeitungsprogramm ist das Ganze eine bisschen Lernarbeit, aber kurzer Zeit kann man schon Drehen, Skalieren und natürlich Zeichnen. Vektor-Bilder haben auch den großen Vorteil, die Möglichkeit später eine höhere Auflösung der Lackierung zu machen.

===Verwenden von Ebenen===
Beim Bearbeiten der Lackierung haben Sie die Vorlage in einer oder mehreren Schicht das Hinzufügen der Elemente von dem Flottendesign in anderen Schichten. Einzelne Elemente als separate Ebenen um sie ggf. bewegen zu können, ist eine weitere gute Idee, wenn Sie einen Raster-Bearbeitungsprogramm verwenden.

===Speichern der Datein===

Starten Sie die Arbeit mit dem Speichern der noch leeren Lackierung. Auf diese Weise gehen Sie sicher das Speichern später nicht zu vergessen und stundenlange Arbeit zu verlieren. Die Datei sollte normalerweise eine Größe von 1024 * 1024 Pixel haben, aber jedes Rechteck mit n² Pixel, zum Beispiel 256, 512 und 2048 Pixel werden es auch tun. Größere Bildgrößen sind detaillierter, aber Flightgear läuft auch langsamer.

Beachten Sie, dass alle Bemalungen für ein bestimmtes Flugzeug das gleiche Seitenverhältnis haben muss. Also, wenn eine bestehende Lackierung 1024 * 2048 ist, kann Ihre Lackierung 512 * 1024 sein, aber nicht 512 * 512.

Wenn Sie mit Raster-Datein arbeiten, denken Sie daran ,während der Arbeit an der Lackierung eine zwei-oder viermal so große Größe zu verwenden, falls Sie später eine Lackierung in einer größeren Größe brauchen. Wenn Sie fertig sind können Sie eine Version in der richtigen Größe speichern. Speichern Sie die Datei in einem größeren Format auch beim Erstellen eines Raster-Image-paintkit von Grund auf neu.

Während der Arbeit an der Lackierung speichern Sie die Datei in verschiedenen Versionen, während Sie neue Funktionen hinzufügen, sodass Sie am Ende nicht Ihre Datei nur aus Versehen durcheinander bringen. Kopieren Sie die Datei, mit der richtigen Größe, in das Aircraft-Models Verzeichnis oder Models/Liveries Verzeichnis, je nachdem, wie der ursprüngliche Autor des Flugzeugs die Ordner organisiert und benennen Sie es Default.png.

===Anschauen der Lackierung in 3D===

Während Sie auf der Lackierung arbeiten, ist es eine gute Idee, es in eine 3D-Viewer zu laden, drehen Sie das Modell um und vergleichen Sie es mit Ihrer Referenzbilder in regelmäßigen Abständen.

Um die Lackierung an einem Modell zu überprüfen gibt es drei Möglichkeiten, Sie können verwenden:
* '''[[FGRun]]'s''' Betrachter erreicht auf der Flugzeug-Auswahl-Seite das Modell, das eher langsam sucht.
* '''3DViewer''', ein ordentlicher, kleiner und schneller Betrachter.
* den 3D Modellier'''[[Blender]]''', welches eine steile Lernkurve hat.

Die Empfehlung ist der 3DViewer, da es klein und schnell ist.

===Benennung der Lackierung===

Schließlich, wenn Sie fertig sind, gebe Sie ihrer Lackierung einen richtigen Namen. Für Hinweise auf Flugzeuge usw. werfen Sie einen Blick auf die [http://liveries.flightgear.org/contribute.php livery database's contribute page]. Es ist normalerweise eine gute Idee, Flugzeugmodelle und Airlines zu haben, das möglicherweise auch Jahre lang in den Dateinamen verwendet wurde.

Details on the XML work needed here.

==Teilen Ihrer Arbeit==

Wie wär 's wenn Sie Ihre Arbeit im Forum, und in dem Fall ist es eine echte Lackierung und hat nicht Teile der nicht-freien Bildern, auch die Livery Database unter der GPL Lizenz veröffentlichen.

===Zeigen Sie Ihre Lackierung im Flightgear Forum===

this article hasn't finished yet.

[[Category:Aircraft enhancement|Edit a livery]]
[[Category:Howto|Edit a livery]]

[[en:Howto: Edit a livery]]

De/Howto: Edit a livery

2012-07-22T22:20:34Z

Condor:

In diesem [[:Category:Howto|howto]] findet man eine Anleitung zum Bearbeiten einer Livery (Lackierung) eines Flugzeugs in Flightgear.

==Was ist eine Livery?==
Eine Livery ist die Art ein Muster z.B.:einer Fluggesellschaft auf ein Flugzeug zu bringen. Andere Flugsimulatoren nennen das "paint" oder "repaint". Solch eine Livery besteht aus einer oder mehreren Texturen welche das 3D-Modell des Flugzeugs umgibt. Die meisten Flugzeuge in Flightgear kommen als ZIP-Datei, welche ein wenig Text, 3d-Model und Bilddatein in mehreren Ordnern enthält. In dieser Struktur gibt es eine oder mehrere Liveries und ein Paar Textdatein, XML-Datein, die die Verwendung beschreibt. Die Lackierungen findet man in der Regel in dem Models/Liveries-Verzeichnid oder einem anderen Verzeichnis, je nachdem, wie der Autor die Dateien und Verzeichnisse organisiert.

==Allgemeiner Arbeitsablauf==
Es gibt ein Paar Möglichkeiten, um eine neue Lackierung zu erstellen. Zuerst schaut man in der[http://liveries.flightgear.org/ Livery database] nach, ob die gewünschte Lackierung von einem bestimmtem Flugzeug bereits existiert, wenn ja, dann macht man eine andere. Außerdem kann man Vorlagen für Lackierungen, genannt Paintkits, für ein paar Flugzeuge dort finden, aber manchmal sind Paintkits enthalten mit dem Flugzeug enthalten.
Beim Erstellen der Lackierung ist der Arbeitsablauf im Grunde in dieser Reihenfolge:
# Überprüfen Sie die FlightGear Liveries database, um doppelte Arbeit zu vermeiden
# Finden von Originalbildern,
# wenn möglich ein Paintkit besorgen,
# die Lackierung erstellen,
# die Lackierung öffentlich teilen

==Suche nach Originalbildern==
Beim Erstellen einer Lackierung, basierend auf realem Flugzeug, sollte man zunächst Originalbilder betrachten. Man braucht Bilder des Flugzeugs mit der Lackierung von beiden Seiten, evtl unten und oben. Stellen Sie sicher, dass Sie auch Bilder von einem bestimmtem Winkel haben. Ein Drei-Wege-Zeichnen kann hilfreich sein, wenn man z.B. Nieten hinzufügen möchte oder kein Paintkit existiert. Stellen Sie sicher, dass Sie viele gute Originalbilder von der Lackierung des Flugzeugs haben. Am Ende dieses Artikels finden Sie eine Liste von Webseiten, die solche Bilder enthalten.

==Bearbeiten der Lackierung==
[[File:Vector vs Raster Graphics.png|150px|thumb|right|Hier sieht man den Unterschied zwischen Vektor und Raster: links ist eine Vektor- und rechts eine Rastergraphik.]]
[[File:Livery layers in Inkscape (Slovenian PC-9M).png|150px|thumb|right|Inkscape-Schicht-Dialog. Die vier oberen Schichten sind das Paintkit, während der Rest der Schichten die Lackierung sind.]]
[[File:Finished Slovenian PC-9M livery (3DViewer screenshot).png|150px|thumb|right|3DViewer Bildaufnahme von einer fertigen Lackierung über das Modell drapiert.]]
[[File:Finished Slovenian PC-9M livery (in-game screenshot).png|150px|thumb|right|FlightGear 2.0.0 Im-Spiel-Bildaufnahme mit der fertigen Lackierung.]]
Sollte das Speichern der bearbeiteten Lackierung anhand des Ablageortes nicht möglich sein, so verschiebt/kopiert man die Lackierung an einen anderen Ort, wo sie sich speichern lässt.

===Vektor oder Raster===
Es gibt im Allgemeinen zwei Möglichkeiten, die Lackierung zu bearbeiten: zum Einem Raster-Grafik-Bearbeitungsprogramm wie GIMP (empfehlenswert) oder Photoshop oder ein Vektor-Graphik-Bearbeitungsprogramm wie Inkscape oder Paint. GIMP und Inkscape sind beide freie und open-Source-Software. Wenn man keine Erfahrung mit einem Vektor-Graphik-Bearbeitungsprogramm ist das Ganze eine bisschen Lernarbeit, aber kurzer Zeit kann man schon Drehen, Skalieren und natürlich Zeichnen. Vektor-Bilder haben auch den großen Vorteil, die Möglichkeit später eine höhere Auflösung der Lackierung zu machen.

===Verwenden von Ebenen===
Beim Bearbeiten der Lackierung haben Sie die Vorlage in einer oder mehreren Schicht das Hinzufügen der Elemente von dem Flottendesign in anderen Schichten. Einzelne Elemente als separate Ebenen um sie ggf. bewegen zu können, ist eine weitere gute Idee, wenn Sie einen Raster-Bearbeitungsprogramm verwenden.

===Speichern der Datein===

Starten Sie die Arbeit mit dem Speichern der noch leeren Lackierung. Auf diese Weise gehen Sie sicher das Speichern später nicht zu vergessen und stundenlange Arbeit zu verlieren. Die Datei sollte normalerweise eine Größe von 1024 * 1024 Pixel haben, aber jedes Rechteck mit n² Pixel, zum Beispiel 256, 512 und 2048 Pixel werden es auch tun. Größere Bildgrößen sind detaillierter, aber Flightgear läuft auch langsamer.

Beachten Sie, dass alle Bemalungen für ein bestimmtes Flugzeug das gleiche Seitenverhältnis haben muss. Also, wenn eine bestehende Lackierung 1024 * 2048 ist, kann Ihre Lackierung 512 * 1024 sein, aber nicht 512 * 512.

Wenn Sie mit Raster-Datein arbeiten, denken Sie daran ,während der Arbeit an der Lackierung eine zwei-oder viermal so große Größe zu verwenden, falls Sie später eine Lackierung in einer größeren Größe brauchen. Wenn Sie fertig sind können Sie eine Version in der richtigen Größe speichern. Speichern Sie die Datei in einem größeren Format auch beim Erstellen eines Raster-Image-paintkit von Grund auf neu.

Während der Arbeit an der Lackierung speichern Sie die Datei in verschiedenen Versionen, während Sie neue Funktionen hinzufügen, sodass Sie am Ende nicht Ihre Datei nur aus Versehen durcheinander bringen. Kopieren Sie die Datei, mit der richtigen Größe, in das Aircraft-Models Verzeichnis oder Models/Liveries Verzeichnis, je nachdem, wie der ursprüngliche Autor des Flugzeugs die Ordner organisiert und benennen Sie es Default.png.

===Anschauen der Lackierung in 3D===

Während Sie auf der Lackierung arbeiten, ist es eine gute Idee, es in eine 3D-Viewer zu laden, drehen Sie das Modell um und vergleichen Sie es mit Ihrer Referenzbilder in regelmäßigen Abständen.

Um die Lackierung an einem Modell zu überprüfen gibt es drei Möglichkeiten, Sie können verwenden:
* '''[[FGRun]]'s''' Betrachter erreicht auf der Flugzeug-Auswahl-Seite das Modell, das eher langsam sucht.
* '''3DViewer''', ein ordentlicher, kleiner und schneller Betrachter.
* den 3D Modellier'''[[Blender]]''', welches eine steile Lernkurve hat.

Die Empfehlung ist der 3DViewer, da es klein und schnell ist.

===Benennung der Lackierung===

Schließlich, wenn Sie fertig sind, gebe Sie ihrer Lackierung einen richtigen Namen. Für Hinweise auf Flugzeuge usw. werfen Sie einen Blick auf die [http://liveries.flightgear.org/contribute.php livery database's contribute page]. Es ist normalerweise eine gute Idee, Flugzeugmodelle und Airlines zu haben, das möglicherweise auch Jahre lang in den Dateinamen verwendet wurde.

Details on the XML work needed here.

[[Category:Aircraft enhancement|Edit a livery]]
[[Category:Howto|Edit a livery]]

[[en:Howto: Edit a livery]]

De/Howto: Edit a livery

2012-07-22T22:14:29Z

Condor:

In diesem [[:Category:Howto|howto]] findet man eine Anleitung zum Bearbeiten einer Livery (Lackierung) eines Flugzeugs in Flightgear.

==Was ist eine Livery?==
Eine Livery ist die Art ein Muster z.B.:einer Fluggesellschaft auf ein Flugzeug zu bringen. Andere Flugsimulatoren nennen das "paint" oder "repaint". Solch eine Livery besteht aus einer oder mehreren Texturen welche das 3D-Modell des Flugzeugs umgibt. Die meisten Flugzeuge in Flightgear kommen als ZIP-Datei, welche ein wenig Text, 3d-Model und Bilddatein in mehreren Ordnern enthält. In dieser Struktur gibt es eine oder mehrere Liveries und ein Paar Textdatein, XML-Datein, die die Verwendung beschreibt. Die Lackierungen findet man in der Regel in dem Models/Liveries-Verzeichnid oder einem anderen Verzeichnis, je nachdem, wie der Autor die Dateien und Verzeichnisse organisiert.

==Allgemeiner Arbeitsablauf==
Es gibt ein Paar Möglichkeiten, um eine neue Lackierung zu erstellen. Zuerst schaut man in der[http://liveries.flightgear.org/ Livery database] nach, ob die gewünschte Lackierung von einem bestimmtem Flugzeug bereits existiert, wenn ja, dann macht man eine andere. Außerdem kann man Vorlagen für Lackierungen, genannt Paintkits, für ein paar Flugzeuge dort finden, aber manchmal sind Paintkits enthalten mit dem Flugzeug enthalten.
Beim Erstellen der Lackierung ist der Arbeitsablauf im Grunde in dieser Reihenfolge:
# Überprüfen Sie die FlightGear Liveries database, um doppelte Arbeit zu vermeiden
# Finden von Originalbildern,
# wenn möglich ein Paintkit besorgen,
# die Lackierung erstellen,
# die Lackierung öffentlich teilen

==Suche nach Originalbildern==
Beim Erstellen einer Lackierung, basierend auf realem Flugzeug, sollte man zunächst Originalbilder betrachten. Man braucht Bilder des Flugzeugs mit der Lackierung von beiden Seiten, evtl unten und oben. Stellen Sie sicher, dass Sie auch Bilder von einem bestimmtem Winkel haben. Ein Drei-Wege-Zeichnen kann hilfreich sein, wenn man z.B. Nieten hinzufügen möchte oder kein Paintkit existiert. Stellen Sie sicher, dass Sie viele gute Originalbilder von der Lackierung des Flugzeugs haben. Am Ende dieses Artikels finden Sie eine Liste von Webseiten, die solche Bilder enthalten.

==Bearbeiten der Lackierung==
[[File:Vector vs Raster Graphics.png|150px|thumb|right|Hier sieht man den Unterschied zwischen Vektor und Raster: links ist eine Vektor- und rechts eine Rastergraphik.]]
[[File:Livery layers in Inkscape (Slovenian PC-9M).png|150px|thumb|right|Inkscape-Schicht-Dialog. Die vier oberen Schichten sind das Paintkit, während der Rest der Schichten die Lackierung sind.]]
[[File:Finished Slovenian PC-9M livery (3DViewer screenshot).png|150px|thumb|right|3DViewer Bildaufnahme von einer fertigen Lackierung über das Modell drapiert.]]
[[File:Finished Slovenian PC-9M livery (in-game screenshot).png|150px|thumb|right|FlightGear 2.0.0 Im-Spiel-Bildaufnahme mit der fertigen Lackierung.]]
Sollte das Speichern der bearbeiteten Lackierung anhand des Ablageortes nicht möglich sein, so verschiebt/kopiert man die Lackierung an einen anderen Ort, wo sie sich speichern lässt.

===Vektor oder Raster===
Es gibt im Allgemeinen zwei Möglichkeiten, die Lackierung zu bearbeiten: zum Einem Raster-Grafik-Bearbeitungsprogramm wie GIMP (empfehlenswert) oder Photoshop oder ein Vektor-Graphik-Bearbeitungsprogramm wie Inkscape oder Paint. GIMP und Inkscape sind beide freie und open-Source-Software. Wenn man keine Erfahrung mit einem Vektor-Graphik-Bearbeitungsprogramm ist das Ganze eine bisschen Lernarbeit, aber kurzer Zeit kann man schon Drehen, Skalieren und natürlich Zeichnen. Vektor-Bilder haben auch den großen Vorteil, die Möglichkeit später eine höhere Auflösung der Lackierung zu machen.

===Verwenden von Ebenen===
Beim Bearbeiten der Lackierung haben Sie die Vorlage in einer oder mehreren Schicht das Hinzufügen der Elemente von dem Flottendesign in anderen Schichten. Einzelne Elemente als separate Ebenen um sie ggf. bewegen zu können, ist eine weitere gute Idee, wenn Sie einen Raster-Bearbeitungsprogramm verwenden.

===Speichern der Datein===

Starten Sie die Arbeit mit dem Speichern der noch leeren Lackierung. Auf diese Weise gehen Sie sicher das Speichern später nicht zu vergessen und stundenlange Arbeit zu verlieren. Die Datei sollte normalerweise eine Größe von 1024 * 1024 Pixel haben, aber jedes Rechteck mit n² Pixel, zum Beispiel 256, 512 und 2048 Pixel werden es auch tun. Größere Bildgrößen sind detaillierter, aber Flightgear läuft auch langsamer.

Beachten Sie, dass alle Bemalungen für ein bestimmtes Flugzeug das gleiche Seitenverhältnis haben muss. Also, wenn eine bestehende Lackierung 1024 * 2048 ist, kann Ihre Lackierung 512 * 1024 sein, aber nicht 512 * 512.

Wenn Sie mit Raster-Datein arbeiten, denken Sie daran ,während der Arbeit an der Lackierung eine zwei-oder viermal so große Größe zu verwenden, falls Sie später eine Lackierung in einer größeren Größe brauchen. Wenn Sie fertig sind können Sie eine Version in der richtigen Größe speichern. Speichern Sie die Datei in einem größeren Format auch beim Erstellen eines Raster-Image-paintkit von Grund auf neu.

Während der Arbeit an der Lackierung speichern Sie die Datei in verschiedenen Versionen, während Sie neue Funktionen hinzufügen, sodass Sie am Ende nicht Ihre Datei nur aus Versehen durcheinander bringen. Kopieren Sie die Datei, mit der richtigen Größe, in das Aircraft-Models Verzeichnis oder Models/Liveries Verzeichnis, je nachdem, wie der ursprüngliche Autor des Flugzeugs die Ordner organisiert und benennen Sie es Default.png.

===Anschauen der Lackierung in 3D===

Während Sie auf der Lackierung arbeiten, ist es eine gute Idee, es in eine 3D-Viewer zu laden, drehen Sie das Modell um und vergleichen Sie es mit Ihrer Referenzbilder in regelmäßigen Abständen.

Um die Lackierung an einem Modell zu überprüfen gibt es drei Möglichkeiten, Sie können verwenden:
* '''[[FGRun]]'s''' Betrachter erreicht auf der Flugzeug-Auswahl-Seite das Modell, das eher langsam sucht.
* '''3DViewer''', ein ordentlicher, kleiner und schneller Betrachter.
* den 3D Modellier'''[[Blender]]''', welches eine steile Lernkurve hat.

Die Empfehlung ist der 3DViewer, da es klein und schnell ist.

[[Category:Aircraft enhancement|Edit a livery]]
[[Category:Howto|Edit a livery]]

[[en:Howto: Edit a livery]]

De/Howto: Edit a livery

2012-07-22T21:58:48Z

Condor: /* Speichern der Datein */

In diesem [[:Category:Howto|howto]] findet man eine Anleitung zum Bearbeiten einer Livery (Lackierung) eines Flugzeugs in Flightgear.

==Was ist eine Livery?==
Eine Livery ist die Art ein Muster z.B.:einer Fluggesellschaft auf ein Flugzeug zu bringen. Andere Flugsimulatoren nennen das "paint" oder "repaint". Solch eine Livery besteht aus einer oder mehreren Texturen welche das 3D-Modell des Flugzeugs umgibt. Die meisten Flugzeuge in Flightgear kommen als ZIP-Datei, welche ein wenig Text, 3d-Model und Bilddatein in mehreren Ordnern enthält. In dieser Struktur gibt es eine oder mehrere Liveries und ein Paar Textdatein, XML-Datein, die die Verwendung beschreibt. Die Lackierungen findet man in der Regel in dem Models/Liveries-Verzeichnid oder einem anderen Verzeichnis, je nachdem, wie der Autor die Dateien und Verzeichnisse organisiert.

==Allgemeiner Arbeitsablauf==
Es gibt ein Paar Möglichkeiten, um eine neue Lackierung zu erstellen. Zuerst schaut man in der[http://liveries.flightgear.org/ Livery database] nach, ob die gewünschte Lackierung von einem bestimmtem Flugzeug bereits existiert, wenn ja, dann macht man eine andere. Außerdem kann man Vorlagen für Lackierungen, genannt Paintkits, für ein paar Flugzeuge dort finden, aber manchmal sind Paintkits enthalten mit dem Flugzeug enthalten.
Beim Erstellen der Lackierung ist der Arbeitsablauf im Grunde in dieser Reihenfolge:
# Überprüfen Sie die FlightGear Liveries database, um doppelte Arbeit zu vermeiden
# Finden von Originalbildern,
# wenn möglich ein Paintkit besorgen,
# die Lackierung erstellen,
# die Lackierung öffentlich teilen

==Suche nach Originalbildern==
Beim Erstellen einer Lackierung, basierend auf realem Flugzeug, sollte man zunächst Originalbilder betrachten. Man braucht Bilder des Flugzeugs mit der Lackierung von beiden Seiten, evtl unten und oben. Stellen Sie sicher, dass Sie auch Bilder von einem bestimmtem Winkel haben. Ein Drei-Wege-Zeichnen kann hilfreich sein, wenn man z.B. Nieten hinzufügen möchte oder kein Paintkit existiert. Stellen Sie sicher, dass Sie viele gute Originalbilder von der Lackierung des Flugzeugs haben. Am Ende dieses Artikels finden Sie eine Liste von Webseiten, die solche Bilder enthalten.

==Bearbeiten der Lackierung==
[[File:Vector vs Raster Graphics.png|150px|thumb|right|Hier sieht man den Unterschied zwischen Vektor und Raster: links ist eine Vektor- und rechts eine Rastergraphik.]]
[[File:Livery layers in Inkscape (Slovenian PC-9M).png|150px|thumb|right|Inkscape-Schicht-Dialog. Die vier oberen Schichten sind das Paintkit, während der Rest der Schichten die Lackierung sind.]]
[[File:Finished Slovenian PC-9M livery (3DViewer screenshot).png|150px|thumb|right|3DViewer Bildaufnahme von einer fertigen Lackierung über das Modell drapiert.]]
[[File:Finished Slovenian PC-9M livery (in-game screenshot).png|150px|thumb|right|FlightGear 2.0.0 Im-Spiel-Bildaufnahme mit der fertigen Lackierung.]]
Sollte das Speichern der bearbeiteten Lackierung anhand des Ablageortes nicht möglich sein, so verschiebt/kopiert man die Lackierung an einen anderen Ort, wo sie sich speichern lässt.

===Vektor oder Raster===
Es gibt im Allgemeinen zwei Möglichkeiten, die Lackierung zu bearbeiten: zum Einem Raster-Grafik-Bearbeitungsprogramm wie GIMP (empfehlenswert) oder Photoshop oder ein Vektor-Graphik-Bearbeitungsprogramm wie Inkscape oder Paint. GIMP und Inkscape sind beide freie und open-Source-Software. Wenn man keine Erfahrung mit einem Vektor-Graphik-Bearbeitungsprogramm ist das Ganze eine bisschen Lernarbeit, aber kurzer Zeit kann man schon Drehen, Skalieren und natürlich Zeichnen. Vektor-Bilder haben auch den großen Vorteil, die Möglichkeit später eine höhere Auflösung der Lackierung zu machen.

===Verwenden von Ebenen===
Beim Bearbeiten der Lackierung haben Sie die Vorlage in einer oder mehreren Schicht das Hinzufügen der Elemente von dem Flottendesign in anderen Schichten. Einzelne Elemente als separate Ebenen um sie ggf. bewegen zu können, ist eine weitere gute Idee, wenn Sie einen Raster-Bearbeitungsprogramm verwenden.

===Speichern der Datein===

Starten Sie die Arbeit mit dem Speichern der noch leeren Lackierung. Auf diese Weise gehen Sie sicher das Speichern später nicht zu vergessen und stundenlange Arbeit zu verlieren. Die Datei sollte normalerweise eine Größe von 1024 * 1024 Pixel haben, aber jedes Rechteck mit n² Pixel, zum Beispiel 256, 512 und 2048 Pixel werden es auch tun. Größere Bildgrößen sind detaillierter, aber Flightgear läuft auch langsamer.

Beachten Sie, dass alle Bemalungen für ein bestimmtes Flugzeug das gleiche Seitenverhältnis haben muss. Also, wenn eine bestehende Lackierung 1024 * 2048 ist, kann Ihre Lackierung 512 * 1024 sein, aber nicht 512 * 512.

Wenn Sie mit Raster-Datein arbeiten, denken Sie daran ,während der Arbeit an der Lackierung eine zwei-oder viermal so große Größe zu verwenden, falls Sie später eine Lackierung in einer größeren Größe brauchen. Wenn Sie fertig sind können Sie eine Version in der richtigen Größe speichern. Speichern Sie die Datei in einem größeren Format auch beim Erstellen eines Raster-Image-paintkit von Grund auf neu.

Während der Arbeit an der Lackierung speichern Sie die Datei in verschiedenen Versionen, während Sie neue Funktionen hinzufügen, sodass Sie am Ende nicht Ihre Datei nur aus Versehen durcheinander bringen. Kopieren Sie die Datei, mit der richtigen Größe, in das Aircraft-Models Verzeichnis oder Models/Liveries Verzeichnis, je nachdem, wie der ursprüngliche Autor des Flugzeugs die Ordner organisiert und benennen Sie es Default.png.

[[Category:Aircraft enhancement|Edit a livery]]
[[Category:Howto|Edit a livery]]

[[en:Howto: Edit a livery]]

De/Howto: Edit a livery

2012-06-08T23:18:22Z

Condor: /* Bearbeiten der Lackierung */

De/Howto: Edit a livery

2012-06-08T23:15:43Z

Condor: /* Bearbeiten der Lackierung */

De/Howto: Edit a livery

2012-06-03T20:04:54Z

Condor: /* Bearbeiten der Lackierung */

De/Howto: Edit a livery

2012-06-03T20:02:52Z

Condor: /* Speichern der Datein */

De/Howto: Edit a livery

2012-06-03T20:02:09Z

Condor: /* Bearbeiten der Lackierung */

De/Howto: Edit a livery

2012-06-03T19:57:56Z

Condor:

FlightGear Newsletter May 2012

2012-05-28T13:26:18Z

Condor: /* FlightGear on YouTube */

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

== Development news ==

=== Preparing a new release ===
In preperation for the next FlightGear release, repositories will be frozen as of June 17. This means that no new features or major changes shall be pushed onto the development streams (neither source nor data). The repository remains open for aircraft developments till the day of the release, with the exception of base package aircraft that should not receive major changes from June 17 onwards.

See our [[release plan]] for more details.

=== Language Support ===
For a long time, FlightGear's multi-language support for the menus was broken. The language feature has been restored now, so it is again possible to translate the menu into different languages. Currently, only plain [http://en.wikipedia.org/w/index.php?title=American_Standard_Code_for_Information_Interchange&section=5#ASCII_printable_characters ASCII] characters and its [http://en.wikipedia.org/wiki/Latin1 Latin1/ISO-8859-1] extension are supported though, which covers Western European languages only (Portuguese to German, Italian to Norwegian).

Please see [[Howto:Translate FlightGear]] if you are interested in helping to translate FlightGear. We're currently looking for someone volunteering to update the existing, but incomplete '''Spanish''', '''French''' and '''Italian''' language resources. Also, you're welcome to add support for additional languages (e.g. Portuguese, Swedish, ...).

If your language isn't supported by FlightGear's limited character set yet (i.e. Japanese, Chinese, Russian, ...) then please be patient - a rework of the GUI library, which will also improve support for arbitrary fonts and character sets, is already in progress.

== Interview with a contributor (Jon Berndt) ==
''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!''

'''[http://www.flightgear.org/contributors/ Read previous interviews at our website's archive].'''
[[File:Jon B..jpg|thumb|Jon Berndt, JSBSim Development Coordinator]]
* '''How long have you been involved in FlightGear?'''
For over ten years. I'm the development coordinator (and occasionally accused of being the BDFL) for [[JSBSim]]. It's been just a few months more than ten years since JSBSim became the default flight model for FlightGear - although it should be said that in these days a "default" flight model has less (or no) meaning compared to back then.
* '''What are your major interests in FlightGear?'''
Flight dynamics and control, but I really like the whole aspect of specifying a model in XML (and other) files - a truly data-driven simulation.
* '''What project are you working on right now?'''
Continued development of JSBSim. There are always things to tweak. Recently, I extended the PID (Proportional-Integral-Derivative) control component in JSBSim to support some work I have been doing.
* '''What do you plan on doing in the future?'''
Writing more documentation. Adding more features to JSBSim as needed. And trying to get an official v1.0 release out.
* '''Are you happy with the way the FlightGear project is going?'''
I really enjoy seeing the progress being made in the visuals (as a spectator) - in particular I find the Rembrandt project fascinating.
* '''What do you enjoy most about developing for FlightGear?'''
Since JSBSim is a standalone project, there are other applications that use it such as Outerra, OpenEaagles, and others. However, FlightGear has the longest history with JSBSim and the most active developer community. It has been both enlightening and exciting to see developers stretch the limits of JSBSim, and use it within FlightGear in ways that were not foreseen previously. For instance, the P-51D that Hal Engel has been developing over the past couple of years (or more?) is very good. Also, the recently published skydiver flight model was an instance of a commercial use of FlightGear with JSBSim that resulted in code being shared with us in the spirit of the GPL. With that said, the most exciting part for me of working with the FlightGear community is seeing the very real strengths of open source development on display, and contributing to that effort.
* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
There are many features that are not hidden, but are not known about because they are not yet part of our reference manual.
* '''What is your background in Flight Simulation?
I was graduated from the University of Minnesota (as was FlightGear Development Coordinator Curt Olson). I earned a degree in Aerospace Engineering there and in 1987 I went to work for Link Flight Simulation. I wrote the flight control simulation code for the F-16 as it was migrating from an analog control system to a digital control system. In the years following that I supported the Engineering Directorate at NASA Johnson Space Center in Houston, working with flight simulators almost continuously since then. Most recently, I went to work for Sierra Nevada Corporation to do simulation and analysis work, as well as supporting some wind tunnel testing, all for the Dream Chaser lifting body project. I have been a member of the AIAA Modeling and Simulation Technical Committee along with Bruce Jackson, author of LaRCSim.
* '''What else do you enjoy doing, besides coding in C++ late at night?
I enjoy playing acoustic guitar (fingerstyle), photography, hiking along the Colorado Front Range, playing catch/fetch with my dogs, tending to a 150 gallon saltwater aquarium, and doing various home remodeling projects. But what I really need is more sleep!
'''[http://www.flightgear.org/contributors/ Read previous interviews at our website's archive].'''

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

== Nasal for newbies ==

== New software tools and projects ==
=== FlightGearMap ===
[[File:FlightGearMap map and simple panel at KSFO.png|thumb|270px|FlightGearMap with [[OpenStreetMap]] map and simple panel at [[San Francisco International Airport|KSFO]].]]
[[FlightGearMap]] is a new Android application that displays live FlightGear data in the form of some basic instruments and a moving map. User can choose between various [[OpenStreetMap]] maps and different display styles (just the map/panel, or both). It's still under development, but already worth downloading from [https://play.google.com/store/apps/details?id=com.juanvvc.flightgear Google Play] (Android app store).

== 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 ===
The [[livery database]] got a search engine implemented, allowing users to find that specific livery they've been looking for. Searches can be filtered per aircraft, airline and/or author.

Check it out at http://liveries.flightgear.org/search.php

== Scenery corner ==
=== Airports ===
==== V.C. Bird Intl Airport ====
V.C. Bird Intl Airport (TAPA) is the only airport on the island of Antigua. More can be found [http://www.flightgear.org/forums/viewtopic.php?f=5&t=16413 here in the forum].
{{Gallery
|TAPA 1.jpg|The terminal of TAPA
|TAPA 4.png|The terminal at night
|TAPA 3.png|In front of the terminal
|TAPA 10.jpg|The LIAT hangar/head office
}}

== 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 ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

=== New tutorials and screencasts ===
=== 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]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-28T13:24:11Z

Condor: /* FlightGear on YouTube */

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

== Development news ==

=== Preparing a new release ===
In preperation for the next FlightGear release, repositories will be frozen as of June 17. This means that no new features or major changes shall be pushed onto the development streams (neither source nor data). The repository remains open for aircraft developments till the day of the release, with the exception of base package aircraft that should not receive major changes from June 17 onwards.

See our [[release plan]] for more details.

=== Language Support ===
For a long time, FlightGear's multi-language support for the menus was broken. The language feature has been restored now, so it is again possible to translate the menu into different languages. Currently, only plain [http://en.wikipedia.org/w/index.php?title=American_Standard_Code_for_Information_Interchange&section=5#ASCII_printable_characters ASCII] characters and its [http://en.wikipedia.org/wiki/Latin1 Latin1/ISO-8859-1] extension are supported though, which covers Western European languages only (Portuguese to German, Italian to Norwegian).

Please see [[Howto:Translate FlightGear]] if you are interested in helping to translate FlightGear. We're currently looking for someone volunteering to update the existing, but incomplete '''Spanish''', '''French''' and '''Italian''' language resources. Also, you're welcome to add support for additional languages (e.g. Portuguese, Swedish, ...).

If your language isn't supported by FlightGear's limited character set yet (i.e. Japanese, Chinese, Russian, ...) then please be patient - a rework of the GUI library, which will also improve support for arbitrary fonts and character sets, is already in progress.

== Interview with a contributor (Jon Berndt) ==
''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!''

'''[http://www.flightgear.org/contributors/ Read previous interviews at our website's archive].'''
[[File:Jon B..jpg|thumb|Jon Berndt, JSBSim Development Coordinator]]
* '''How long have you been involved in FlightGear?'''
For over ten years. I'm the development coordinator (and occasionally accused of being the BDFL) for [[JSBSim]]. It's been just a few months more than ten years since JSBSim became the default flight model for FlightGear - although it should be said that in these days a "default" flight model has less (or no) meaning compared to back then.
* '''What are your major interests in FlightGear?'''
Flight dynamics and control, but I really like the whole aspect of specifying a model in XML (and other) files - a truly data-driven simulation.
* '''What project are you working on right now?'''
Continued development of JSBSim. There are always things to tweak. Recently, I extended the PID (Proportional-Integral-Derivative) control component in JSBSim to support some work I have been doing.
* '''What do you plan on doing in the future?'''
Writing more documentation. Adding more features to JSBSim as needed. And trying to get an official v1.0 release out.
* '''Are you happy with the way the FlightGear project is going?'''
I really enjoy seeing the progress being made in the visuals (as a spectator) - in particular I find the Rembrandt project fascinating.
* '''What do you enjoy most about developing for FlightGear?'''
Since JSBSim is a standalone project, there are other applications that use it such as Outerra, OpenEaagles, and others. However, FlightGear has the longest history with JSBSim and the most active developer community. It has been both enlightening and exciting to see developers stretch the limits of JSBSim, and use it within FlightGear in ways that were not foreseen previously. For instance, the P-51D that Hal Engel has been developing over the past couple of years (or more?) is very good. Also, the recently published skydiver flight model was an instance of a commercial use of FlightGear with JSBSim that resulted in code being shared with us in the spirit of the GPL. With that said, the most exciting part for me of working with the FlightGear community is seeing the very real strengths of open source development on display, and contributing to that effort.
* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
There are many features that are not hidden, but are not known about because they are not yet part of our reference manual.
* '''What is your background in Flight Simulation?
I was graduated from the University of Minnesota (as was FlightGear Development Coordinator Curt Olson). I earned a degree in Aerospace Engineering there and in 1987 I went to work for Link Flight Simulation. I wrote the flight control simulation code for the F-16 as it was migrating from an analog control system to a digital control system. In the years following that I supported the Engineering Directorate at NASA Johnson Space Center in Houston, working with flight simulators almost continuously since then. Most recently, I went to work for Sierra Nevada Corporation to do simulation and analysis work, as well as supporting some wind tunnel testing, all for the Dream Chaser lifting body project. I have been a member of the AIAA Modeling and Simulation Technical Committee along with Bruce Jackson, author of LaRCSim.
* '''What else do you enjoy doing, besides coding in C++ late at night?
I enjoy playing acoustic guitar (fingerstyle), photography, hiking along the Colorado Front Range, playing catch/fetch with my dogs, tending to a 150 gallon saltwater aquarium, and doing various home remodeling projects. But what I really need is more sleep!
'''[http://www.flightgear.org/contributors/ Read previous interviews at our website's archive].'''

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

== Nasal for newbies ==

== New software tools and projects ==
=== FlightGearMap ===
[[File:FlightGearMap map and simple panel at KSFO.png|thumb|270px|FlightGearMap with [[OpenStreetMap]] map and simple panel at [[San Francisco International Airport|KSFO]].]]
[[FlightGearMap]] is a new Android application that displays live FlightGear data in the form of some basic instruments and a moving map. User can choose between various [[OpenStreetMap]] maps and different display styles (just the map/panel, or both). It's still under development, but already worth downloading from [https://play.google.com/store/apps/details?id=com.juanvvc.flightgear Google Play] (Android app store).

== 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 ===
The [[livery database]] got a search engine implemented, allowing users to find that specific livery they've been looking for. Searches can be filtered per aircraft, airline and/or author.

Check it out at http://liveries.flightgear.org/search.php

== Scenery corner ==
=== Airports ===
==== V.C. Bird Intl Airport ====
V.C. Bird Intl Airport (TAPA) is the only airport on the island of Antigua. More can be found [http://www.flightgear.org/forums/viewtopic.php?f=5&t=16413 here in the forum].
{{Gallery
|TAPA 1.jpg|The terminal of TAPA
|TAPA 4.png|The terminal at night
|TAPA 3.png|In front of the terminal
|TAPA 10.jpg|The LIAT hangar/head office
}}

== 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 ===
In this video you can see a cockpit landing at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Flightgear-Landing at Tenerife North with an A330-200 }}

=== New tutorials and screencasts ===
=== 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]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

List of developed airports

2012-05-22T20:08:45Z

Condor: /* Airports */

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

|-
| EDDC || Dresden Airport || Germany || Europe || One building: hangar/terminal

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

|-
| [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=2.56241&lat=49.00972&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.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

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

|-
| [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 || Junacho 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://www.grupofgbr.com.br/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://www.grupofgbr.com.br/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://www.grupofgbr.com.br/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://www.grupofgbr.com.br/aeroportos#!__aeroportos Site Group FGBR]

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

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

List of developed airports

2012-05-22T20:07:22Z

Condor: /* Airports */

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

|-
| EDDC || Dresden Airport || Germany || Europe || One building: hangar/terminal

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

|-
| [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=2.56241&lat=49.00972&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.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

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

|-
| [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 || 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 || Junacho 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://www.grupofgbr.com.br/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://www.grupofgbr.com.br/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://www.grupofgbr.com.br/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://www.grupofgbr.com.br/aeroportos#!__aeroportos Site Group FGBR]

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

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

FlightGear Newsletter May 2012

2012-05-20T14:50:40Z