FlightGear wiki - User contributions [en]

Canary Islands Custom Scenery

2017-07-05T14:07:55Z

Popolon: /* Development */

[[File:Las-Palmas-Apron.png|thumb|The fully modeled Las Palmas de Gran Canaria airport at dusk]]
The Canary Islands Custom Scenery project is an ambitious project of pilots, developers and supporters of the Canary Islands region. Its aim is to provide the region in a scenery quality as high and as detailed as possible. Other branches of this project take care about a more realistic local AI traffic, multiplayer events and local airlines.

The project is currently under development, with an increasing number of contributors and steady updated contents.

== History ==
The whole project started in June 2016, when passionate developers and former residents of the archipelago started several threads in the FlightGear-Forum. Scenery and model developers started to work on the textures, as well as on the terrain, the objects, the sea traffic and obviously on the airports. Within hours and days, a whole re-texturing of all seven major islands took place. Soon after that, the first 3D models for local urban areas were published and shared, and airports had been developed. Developers who had worked on one or two islands before, now shared their experiences and work with others. By now, the development is going on, already having several islands and airports modeled, but there is still a lot of work to do...

== Area description ==
The Canary Islands are an archipelago in the east Atlantic, off the coast of Morocco. While geographically belonging to Africa, their political status is that of an autonomous region of Spain.

Being called the "Islands of eternal spring", their climate is mostly warm, with an average temperature of 25°C. This makes all seven Islands perfect for tourism, so that this is the region's main income. Because of this very high tourist level, there are airports on all islands. Except for the airport of El Hierro (GCHI), every island has an international airport.
The weather is excellent for flying nearly all the time, some winds could make it a challenge, especially in smaller planes.
Aside from general air traffic, there are many touristic flights from central Europe, mostly from the Uk and Germany. Connections to the spanish mainland are provided by Vueling and Iberia.

Very interesting is the regional carrier sector, operated by the Canarian regional airline Binter Canarias.

== Why fly to the Canary Islands? ==
Having eight regional and international airports in such a small region is a very big advantage. This makes it very easy for pilots to improve their skills, especially takeoffs, approaches and landings.

The nicely-modeled scenery is worth a special look, so you really can enjoy your flight. A whole lot of people had visited the Islands for their holiday, so now you are able to really get that holiday feeling, when touching down at one of the nicely modeled airports.
The airports themselves are very different in style, conception, use and their level of difficulty. From the international airport of Las Palmas de Gran Canaria, where you can easily perform a landing with a 747 or A380 to the small one of El Hierro, where it can be difficult to have a touch down even with small regional turboprops, or the notorious Tenerife Norte - Los Rodeos, there are sites for every kind of aviator.

== Development ==
This custom scenery is currently under development. We are still working on the project, making it better and more realistic. It's not planned to publish it via [[TerraSync]] by now, maybe we are going to do that later. Actual and updated versions are accessible via {{github url|user=D-ECHO|repo=Canarys}}.

In March, 5 2017, building and roads have been added from OpenStreetMap using [[Osm2city.py]]. See [[FlightGear_Newsletter_May_2017#New OSM2City areas|May 2017 Newsletter]] and [https://forum.flightgear.org/viewtopic.php?f=5&t=32062&hilit=paju1986 forum topic]

A [https://drive.google.com/open?id=0B5TeZxXfefn3NUp4NkM2b1hPVDQ custom scenary zip can ben downloaded here].

== Status of the Project ==
The whole region is re-textured according to the actual vegetation and look.

You can see the airport development in the list below:

{| class="wikitable"
|-
! Airport !! Airport layout !! Airport buildings and furniture
|-
| GCRR || YES || NOT YET
|-
| CGFV || YES || NOT YET
|-
| GCLP || YES || YES
|-
| GCTS || YES || NOT YET
|-
| GCXO || YES || YES
|-
| GCGM || YES || YES
|-
| GCLA || YES || YES
|-
| GCHI || YES || YES
|}

== Things to contribute to ==
The following things need to be added or improved. Your help is appreciated! If you want to take care of one of the listed topics below, please leave a comment in the forum: https://forum.flightgear.org/viewtopic.php?f=5&t=29773

This avoids double processing, and gives us a notice what we can expect in the near term.

* Airport buildings and furniture for GCFV (Fuerteventura)
* Airport buildings and furniture for GCRR (Lanzarote)
* Airport buildings and furniture for GCTS (Tenerife Sur)
* regional AI Traffic (Binter Canarias Airline)
* Contributors to multiplayer events

[[Category:Scenery enhancement projects]]

Canary Islands Custom Scenery

2017-07-05T13:52:14Z

Popolon: /* Development */ +march 2017 improvements (OSM2city.py

[[File:Las-Palmas-Apron.png|thumb|The fully modeled Las Palmas de Gran Canaria airport at dusk]]
The Canary Islands Custom Scenery project is an ambitious project of pilots, developers and supporters of the Canary Islands region. Its aim is to provide the region in a scenery quality as high and as detailed as possible. Other branches of this project take care about a more realistic local AI traffic, multiplayer events and local airlines.

The project is currently under development, with an increasing number of contributors and steady updated contents.

== History ==
The whole project started in June 2016, when passionate developers and former residents of the archipelago started several threads in the FlightGear-Forum. Scenery and model developers started to work on the textures, as well as on the terrain, the objects, the sea traffic and obviously on the airports. Within hours and days, a whole re-texturing of all seven major islands took place. Soon after that, the first 3D models for local urban areas were published and shared, and airports had been developed. Developers who had worked on one or two islands before, now shared their experiences and work with others. By now, the development is going on, already having several islands and airports modeled, but there is still a lot of work to do...

== Area description ==
The Canary Islands are an archipelago in the east Atlantic, off the coast of Morocco. While geographically belonging to Africa, their political status is that of an autonomous region of Spain.

Being called the "Islands of eternal spring", their climate is mostly warm, with an average temperature of 25°C. This makes all seven Islands perfect for tourism, so that this is the region's main income. Because of this very high tourist level, there are airports on all islands. Except for the airport of El Hierro (GCHI), every island has an international airport.
The weather is excellent for flying nearly all the time, some winds could make it a challenge, especially in smaller planes.
Aside from general air traffic, there are many touristic flights from central Europe, mostly from the Uk and Germany. Connections to the spanish mainland are provided by Vueling and Iberia.

Very interesting is the regional carrier sector, operated by the Canarian regional airline Binter Canarias.

== Why fly to the Canary Islands? ==
Having eight regional and international airports in such a small region is a very big advantage. This makes it very easy for pilots to improve their skills, especially takeoffs, approaches and landings.

The nicely-modeled scenery is worth a special look, so you really can enjoy your flight. A whole lot of people had visited the Islands for their holiday, so now you are able to really get that holiday feeling, when touching down at one of the nicely modeled airports.
The airports themselves are very different in style, conception, use and their level of difficulty. From the international airport of Las Palmas de Gran Canaria, where you can easily perform a landing with a 747 or A380 to the small one of El Hierro, where it can be difficult to have a touch down even with small regional turboprops, or the notorious Tenerife Norte - Los Rodeos, there are sites for every kind of aviator.

== Development ==
This custom scenery is currently under development. We are still working on the project, making it better and more realistic. It's not planned to publish it via [[TerraSync]] by now, maybe we are going to do that later. Actual and updated versions are accessible via {{github url|user=D-ECHO|repo=Canarys}}.

In March, 5 2017, building and roads have been added from OpenStreetMap using [[Osm2city.py]]. See [[FlightGear_Newsletter_May_2017#New OSM2City areas|May 2017 Newsletter]] and [https://forum.flightgear.org/viewtopic.php?f=5&t=32062&hilit=paju1986 forum topic]

== Status of the Project ==
The whole region is re-textured according to the actual vegetation and look.

You can see the airport development in the list below:

{| class="wikitable"
|-
! Airport !! Airport layout !! Airport buildings and furniture
|-
| GCRR || YES || NOT YET
|-
| CGFV || YES || NOT YET
|-
| GCLP || YES || YES
|-
| GCTS || YES || NOT YET
|-
| GCXO || YES || YES
|-
| GCGM || YES || YES
|-
| GCLA || YES || YES
|-
| GCHI || YES || YES
|}

== Things to contribute to ==
The following things need to be added or improved. Your help is appreciated! If you want to take care of one of the listed topics below, please leave a comment in the forum: https://forum.flightgear.org/viewtopic.php?f=5&t=29773

This avoids double processing, and gives us a notice what we can expect in the near term.

* Airport buildings and furniture for GCFV (Fuerteventura)
* Airport buildings and furniture for GCRR (Lanzarote)
* Airport buildings and furniture for GCTS (Tenerife Sur)
* regional AI Traffic (Binter Canarias Airline)
* Contributors to multiplayer events

[[Category:Scenery enhancement projects]]

FlightGear Newsletter June 2016

2016-06-14T13:15:16Z

Popolon: /* GTA V Washington */

FlightGear Newsletter June 2016

2016-06-14T13:12:45Z

Popolon: /* Scenery corner */ syntax error, internal link

FlightGear Newsletter May 2016

2016-06-08T15:38:38Z

Popolon: /* Revamping TerraSync */ minor error

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

{{Newsletter-header|May 2016}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
[[#FlightGear v2016.2 released|FlightGear v2016.2 released]] 
[[#Revamping TerraSync|Revamping TerraSync]] 
[[#Sound expressions|New Sound expressions]] 
{{Newsletter-cover-header|In the hangar}} 
[[#c172p|c172p]] 
[[#ICARO Laminar 13 MRX|ICARO Laminar 13 MRX]] 
[[#Powered Paraglider|Powered Paraglider]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>

== Development news ==
=== FlightGear v2016.2 released ===
The FlightGear development team is delighted to announce the v2016.2 "Barcelona" release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include the Space Shuttle, ALS filters, a new HTTP TerraSync system, and improvements to our automatic ATIS.

A list of major changes can be found at [[Changelog 2016.2]]. FlightGear v2016.2 is available for a variety of operating systems from http://www.flightgear.org/download/.

=== Revamping TerraSync ===
Terrasync started out as a standalone rsync-based utility. However, there doesn't appear to be any good/robust multi-platform librsync available for our use. We wanted to embed terrasync right into the core code so we could better coordinate downloading tiles and then loading them immediately into the sim (versus sometimes running into no tiles or partial tiles if an external tool was running rsync.)<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35061363/
|title = <nowiki>Re: [Flightgear-devel] The future of terrasync</nowiki>
|author = <nowiki>Curtis Olson</nowiki>
|date = May 3rd, 2016
|added = May 4th, 2016
|script_version = 0.31
}}
</ref>

as some of you have probably noticed, some coding is currently happening in the terrasync corner, mostly by James and some small parts by Torsten. The main intention is to get rid of the SVN protocol to distribute scenery but use easier to implement protocols. The idea is to use plain HTTP as the access method for files required by terrasync. This should make it much easier for hosts to set up a mirror, probably enables us to use a CDN for load balancing and also makes the client code slim. We already have three mirrors of the complete scenery online, one at sourceforge and two at privately owned servers. The sourceforge mirror receives daily updates from the main scenery export from http://scenery.flightgear.org/ and all other mirrors pull their data from the sourceforge server. We decided to drop the previous method of telling the client about it's nearest mirror by querying a web service ( http://scenery.flightgear.org/svn-server) in favour of using a more stable service provider of the internet: the domain name service (DNS) system. The fgfs client will query a fancy resource record (RR) type of NAPTR (network authority pointer, https://en.wikipedia.org/wiki/NAPTR_record) for the dns name terrasync.flightgear.org and analyse the entries to find the best terrasync mirror. Those entries are already configured and can be examined here: https://toolbox.googleapps.com/apps/dig/#ANY/terrasync.flightgear.org This technique should enable us to provide different sets of scenery, eventually even for only parts of the world in a much easier fashion that it would have been the case with SVN. It also spares many gigabytes on the scenery mirror as they don't have to keep all the 50,000+ revisions we already carry around. I'll start adding the required code over the next couple of days to have it running hopefully for the 2016.2 release. I'll post a message to this list when I flip the final switch and enable the new terrasync. In the mean time, you might see some build failures on Jenkins or other hickups of the system. I promise to fix those as quick as possible. BTW: If you use terrafs, you already receive your data from the new http mirrors, although not use the DNS service resolver.<ref>{{cite web
|url = http://sourceforge.net/p/flightgear/mailman/message/35057670/
|title = <nowiki>[Flightgear-devel] The future of terrasync</nowiki>
|author = <nowiki>Torsten Dreyer</nowiki>
|date = May 2nd, 2016
|added = May 2nd, 2016
|script_version = 0.28
}}
</ref>

the http download method will function very much as before where only the changed files (if any) are downloaded. The svn method requires 2x the actual space because of the way svn works under the hood. Git typically requires that you download every version ever created to get the latest copy (there are work arounds if you just want the most recent version.) So the end result for the average user that just wants to download and use the scenery is that the http method will be lighter weight overall. It also simplifies the code inside FlightGear quite a bit and should make the synchroniation more robust. And as mentioned before, it should simplify the task of setting up a scenery mirror for those that wish to do that. As before, power users will have multiple options for updating scenery or mixing and matching from different sources if they choose. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35061856/
|title = <nowiki>Re: [Flightgear-devel] The future of terrasync</nowiki>
|author = <nowiki>Curtis Olson</nowiki>
|date = May 4th, 2016
|added = May 4th, 2016
|script_version = 0.31
}}
</ref>

The technique of the http repository is much simpler than that of the svn repository and it will be pretty simple to create a local mirror or to download chunks of data. With a bit of to-be-developed scripting (python e.g.) there is no need to download existing data again. I don't know how terramaster works but I am sure it is easy to adapt to the new http access method. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35062543/
|title = <nowiki>Re: [Flightgear-devel] The future of terrasync</nowiki>
|author = <nowiki>Torsten Dreyer</nowiki>
|date = May 4th, 2016
|added = May 4th, 2016
|script_version = 0.31
}}
</ref>

The goal is to completely remove SVN and only use the HTTP repository. I'd like to reach that goal better sooner than later as we currently have two single-points of failure for the SVN-service. The first is the http://scenery.flightgear.org/svn-service web service (runs on a private web server) and the second is the one-and-only svn-server available for public access, also hosted on a private server. If either on of those fails, the SVN-terrasync is dead. I have learned the hard way that not having a fallback is a bad idea.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35062543/
|title = <nowiki>Re: [Flightgear-devel] The future of terrasync</nowiki>
|author = <nowiki>Torsten Dreyer</nowiki>
|date = May 4th, 2016
|added = May 4th, 2016
|script_version = 0.31
}}
</ref>

<references/>

=== Sound expressions ===
New support for expressions was added in the volume and pitch sections of audio configuration files<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35126638/
|title = <nowiki> [Flightgear-devel] New XML Sound feature </nowiki>
|author = <nowiki> Erik Hofman </nowiki>
|date = May 31st, 2016
|added = May 31st, 2016
|script_version = 0.40
}}</ref>.

It works as follows:
# If an expression is found in <pitch/> or <volume/> it gets processed and the rest is ignored.
# If an expression was defined in a volume or pitch definition of a sound-section then all other volume or pitch sections containing a property are ignored.
# Sections with <internal/> are always processed so timed sounds are still available.

This way you can add volume and/or pitch sections with an expression
before all other sections and keep backward and forward compatibility.
But you could, for example, make the expression section more complex for
newer versions of FlightGear.

An example would be:

{{collapsible script
| type = XML code
| title = Expressions in a sound configuration file
| lang = XML
| script =
<engine>
<name>engine</name>
<mode>looped</mode>
<path>Aircraft/paraglider/Sounds/wasp.wav</path>
<property>engines/engine/running</property>
<volume version="2.0">
<expression>
<product>
<min>
<max>
<product>
<property>engines/engine/mp-osi</property>
<value>0.23</value>
</product>
<value>1.0</value>
</max>
<value>0.3</value>
</min>
<min>
<max>
<log> <property>orientation/alpha-deg</property> </log>
<value>1.2</value>
</max>
<value>1.0</value>
</min>
</product>
</expression>
</volume>
<pitch version="2.0">
<expression>
<min>
<max>
<sum>
<value>0.4</value>
<product>
<property>engines/engine/rpm</property>
<value>0.0001</value>
</product>
</sum>
<value>1.2</value>
</max>
<value>0.4</value>
</min>
</expression>
</pitch>

<volume>
<property>engines/engine/mp-osi</property>
<factor>0.23</factor>
<min>0.3</min>
<max>1.0</max>
</volume>
<volume>
<property>orientation/alpha-deg</property>
<type>log</type>
<min>1.0</min>
<max>1.2</max>
</volume>
<pitch>
<property>engines/engine/rpm</property>
<factor>0.0001</factor>
<min>0.4</min>
<max>1.2</max>
<offset>0.4</offset>
</pitch>

</engine>
| bgcolor = #e0f2ff
}}

== In the hangar ==
=== Cessna 172P ===
The Cessna 172P team has just created a new branch called "release/2016.2" with the latest developments from the last few months: https://github.com/Juanvvc/c172p-detailed/tree/release/2016.2 These include:
* Decreased rudder authority
* Added propwash effect for 180 HP version
* Improvements to the irradiance effect
* Better oil dialog
* Flap lever is now dragable and scrollable
* Added normal map to wheels and other objects
* Improvements to the heading indicator
* Correct rudder pedal animation
* Updated tutorial to Barcelona
* Changed "Autostart" menu item to actually start the engine as well
* Split instrument light knob into a knob that two knobs: one that controls the instruments, and one that controls the radio's <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35095319/
|title = <nowiki> [Flightgear-devel] c172p ready for the Barcelona release </nowiki>
|author = <nowiki> Gilberto Agostinho </nowiki>
|date = May 17th, 2016
|added = May 17th, 2016
|script_version = 0.40
}}</ref>

=== ICARO Laminar 13 MRX ===
There is a new aircraft model in [[FGAddon]]: The '''[[Icaro Laminar 13 MRX]]'''. It is an advanced weight-shift controlled hanglider build by ICARO in the early 2000s.

The aim of this project is to provide a very realistic hang glider which shows all the specific properties of a real hang glider. In particular the unique flight dynamic behavior (compared to common aircraft) is focused on.

=== Powered Paraglider ===
David's paraglider model has had a major FDM and 3d update. The FDM is of true ram-air type, a small engine has been added and the parachute itself is now animated.
Warining: a bug prevents the Paraglider from loading properly at the current default airport Barcelona. Any other airport does not seem to cause a problem.

<gallery mode="packed">
Paragliding in the_mountains.jpg|Paragliding in the mountains
Icaro MRX13 Laber.jpeg|Soaring with the Laminar 13 MRX
</gallery>

== Scenery corner ==

== Community news ==

== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki braucht noch Hilfe für sie in verschiedene Sprachen zu übersetzen. Wenn Sie bei der Herstellung der FlightGear Wiki mehrsprachiger interessiert sind, können Sie, indem Sie auf [[:de:Help:Übersetzen|Help:Übersetzen]] beginnen.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|}

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

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

==== Screenshot of the Month ====
FlightGear's Screenshot of the Month May 2016 is ''Landing in Frankfurt's 25L'' by Ambro
[[File:Landing in Frankfurt's 25L.jpg|900px|center|Landing in Frankfurt's 25L by Ambro]]

If you want to participate in the screenshot contest of June 2016, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=29720 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=29720#p287514 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of June 2016.

[[Category:FlightGear Newsletter|2016 05]]
[[Category:Changes after 2016.2]]

[[de:FlightGear Newsletter Mai 2016]]

File:Cub@MountRoraima.jpg

2015-08-16T10:27:40Z

Popolon: add french

=={{int:filedesc}}==
{{Information
|description={{en|1=Piper cub with the new liveries at {{Wikipedia|Mount Roraima|noicon=1}}, South America}} 
{{fr|1=Piper cub avec les nouvelles livrées au {{Wikipedia|fr:Mont Roraima|Mont Roraima|noicon=1}}, en Amérique du Sud}}
|date=2015-08-01 18:36:41
|source=forum.flightgear.org
|author=lomar
|permission=
|other versions=
}}

=={{int:license-header}}==
{{subst:Custom license marker added by UW}}
Published with the express purpose of being used by me (Adam, else MIG29pilot) on this website.

[[Category:Screenshots]]

Fr/L'aéroport de Courchevel

2014-01-20T00:51:58Z

Popolon: corrige un peu le français, correction typo.

{{infobox Airport
|name = Courchevel Airport
|image = LFLJ.jpg
|iata = CVF
|icao = LFLJ
|type =
|owner =
|Ville = Courchevel, France
|Pistes= 05/23
|length= 525 m
|matériaux= congloméré/Asphalte
|siteweb =
}}
'''L'aéroport de Courchevel''' a un petit côté « infâme » dans le monde de l'aviation, considéré comme le foyer d'une des pistes les plus courtes du monde, avec une longueur de 525 mètres et une inclinaison de 18,5% afin de ralentir les avions lors de l’atterrissage. L'[[:Category:Airports|aéroport]] a une approche dangereuse, à travers une grande vallée, qui ne peut être réalisé que par des pilotes certifiés. Lors de l’atterrissage, contrairement à la plupart des aéroport, il n'est pas nécessaire d'effectuer de tours - L'aéroport est situé sur le flan d'une colline très raide qui a vu quelques incidents depuis son ouverture.
[[en:Courchevel Airport]]

[[Category:Airports in France]]

List of developed airports

2013-10-28T12:41:53Z

Popolon: +LKPR (Cech Republic)

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

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

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

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

== Airports ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=7.531611&lat=47.599621&zoom=14 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of Terminal. Be aware: The In-game navigation data is wrong. Use the [http://www.vacc.ch/en/airports_and_charts/LFSB charts]

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

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

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

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=14.26&lat=50.100833&zoom=15&layers=B000000TFFFFTFFFTTFFF LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|}

{{Suggested}}

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

Template:Location/ExternalLink

2013-10-22T10:49:26Z

Popolon: +Flightgear map server

{{#switch: {{{1|}}}

|Flightgear Mapserver|FGFS = [http://mapserver.flightgear.org/popmap/?lat={{{3|0}}}&lon={{{4|0}}}&zoom=16&layers=B00FFTTTTT]

|GoogleMaps|GM = {{#switch: {{{2|}}}
|Mars = [http://www.google.com/mars/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Moon = [http://www.google.com/moon/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Earth|E = {{#switch: {{{5|}}}
|es|eu|gl = [http://maps.google.es/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}}&ie=UTF8 {{{6}}}]
|cn = [http://ditu.google.cn/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=cn {{{6}}}]
|ja = [http://maps.google.co.jp/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=ja {{{6}}}]
|pl = [http://mapy.google.pl/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=pl {{{6}}}]
|de|fr|it|nl = [http://maps.google.{{{5}}}/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}} {{{6}}}]
|en|#default = [http://maps.google.com/maps?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5|en}}} {{{6}}}]
}}
}}
|GoogleEarth|GE = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/earth.php|latdegdec={{{3|0}}}&londegdec={{{4|0}}}&scale=10000&commons=1}} {{{6}}}] }}
|Proximityrama|PR = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/proximityrama|latlon={{{3|0}}},{{{4|0}}}}} {{{6}}}] }}
<nowiki><!--|OpenStreetMap|OSM = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~kolossos/openlayers/commons-on-osm.php|zoom=16&lat={{{3|0}}}&lon={{{4|0}}}}} {{{6}}}] }} ==></nowiki>
|OpenStreetMap|OSM = [http://www.openstreetmap.org/#map=10/{{{3|0}}}/{{{4|0}}} {{{6}}}]
}}<noinclude>
Template for formating external links to mapping websites. Used by {{tl|location/layout}}. 
Input Parameters:
# <nowiki>{{{1}}}</nowiki> - name of external website: GoogleMap (aka GM), GoogleEarth (aka GE), Proximityrama (aka PR), OpenStreetMap (aka OSM)etc.
# <nowiki>{{{2}}}</nowiki> - name of the globe: earth, mars, moon
# <nowiki>{{{3}}}</nowiki> - latitude
# <nowiki>{{{4}}}</nowiki> - longitude
# <nowiki>{{{5}}}</nowiki> - language code: en, pl, de, etc.
# <nowiki>{{{6}}}</nowiki> - Link text
</noinclude>

Template:Location/ExternalLink

2013-10-22T10:41:38Z

Popolon: still one space to remove :)

{{#switch: {{{1|}}}
|GoogleMaps|GM = {{#switch: {{{2|}}}
|Mars = [http://www.google.com/mars/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Moon = [http://www.google.com/moon/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Earth|E = {{#switch: {{{5|}}}
|es|eu|gl = [http://maps.google.es/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}}&ie=UTF8 {{{6}}}]
|cn = [http://ditu.google.cn/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=cn {{{6}}}]
|ja = [http://maps.google.co.jp/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=ja {{{6}}}]
|pl = [http://mapy.google.pl/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=pl {{{6}}}]
|de|fr|it|nl = [http://maps.google.{{{5}}}/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}} {{{6}}}]
|en|#default = [http://maps.google.com/maps?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5|en}}} {{{6}}}]
}}
}}
|GoogleEarth|GE = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/earth.php|latdegdec={{{3|0}}}&londegdec={{{4|0}}}&scale=10000&commons=1}} {{{6}}}] }}
|Proximityrama|PR = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/proximityrama|latlon={{{3|0}}},{{{4|0}}}}} {{{6}}}] }}
<nowiki><!--|OpenStreetMap|OSM = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~kolossos/openlayers/commons-on-osm.php|zoom=16&lat={{{3|0}}}&lon={{{4|0}}}}} {{{6}}}] }} ==></nowiki>
|OpenStreetMap|OSM = [http://www.openstreetmap.org/#map=10/{{{3|0}}}/{{{4|0}}} {{{6}}}]
}}<noinclude>
Template for formating external links to mapping websites. Used by {{tl|location/layout}}. 
Input Parameters:
# <nowiki>{{{1}}}</nowiki> - name of external website: GoogleMap (aka GM), GoogleEarth (aka GE), Proximityrama (aka PR), OpenStreetMap (aka OSM)etc.
# <nowiki>{{{2}}}</nowiki> - name of the globe: earth, mars, moon
# <nowiki>{{{3}}}</nowiki> - latitude
# <nowiki>{{{4}}}</nowiki> - longitude
# <nowiki>{{{5}}}</nowiki> - language code: en, pl, de, etc.
# <nowiki>{{{6}}}</nowiki> - Link text
</noinclude>

Template:Location/ExternalLink

2013-10-22T10:40:56Z

Popolon:

{{#switch: {{{1|}}}
|GoogleMaps|GM = {{#switch: {{{2|}}}
|Mars = [http://www.google.com/mars/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Moon = [http://www.google.com/moon/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Earth|E = {{#switch: {{{5|}}}
|es|eu|gl = [http://maps.google.es/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}}&ie=UTF8 {{{6}}}]
|cn = [http://ditu.google.cn/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=cn {{{6}}}]
|ja = [http://maps.google.co.jp/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=ja {{{6}}}]
|pl = [http://mapy.google.pl/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=pl {{{6}}}]
|de|fr|it|nl = [http://maps.google.{{{5}}}/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}} {{{6}}}]
|en|#default = [http://maps.google.com/maps?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5|en}}} {{{6}}}]
}}
}}
|GoogleEarth|GE = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/earth.php|latdegdec={{{3|0}}}&londegdec={{{4|0}}}&scale=10000&commons=1}} {{{6}}}] }}
|Proximityrama|PR = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/proximityrama|latlon={{{3|0}}},{{{4|0}}}}} {{{6}}}] }}
<nowiki><!--|OpenStreetMap|OSM = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~kolossos/openlayers/commons-on-osm.php|zoom=16&lat={{{3|0}}}&lon={{{4|0}}}}} {{{6}}}] }} ==></nowiki>
|OpenStreetMap|OSM = [ http://www.openstreetmap.org/#map=10/{{{3|0}}}/{{{4|0}}} {{{6}}}]
}}<noinclude>
Template for formating external links to mapping websites. Used by {{tl|location/layout}}. 
Input Parameters:
# <nowiki>{{{1}}}</nowiki> - name of external website: GoogleMap (aka GM), GoogleEarth (aka GE), Proximityrama (aka PR), OpenStreetMap (aka OSM)etc.
# <nowiki>{{{2}}}</nowiki> - name of the globe: earth, mars, moon
# <nowiki>{{{3}}}</nowiki> - latitude
# <nowiki>{{{4}}}</nowiki> - longitude
# <nowiki>{{{5}}}</nowiki> - language code: en, pl, de, etc.
# <nowiki>{{{6}}}</nowiki> - Link text
</noinclude>

Template:Location/ExternalLink

2013-10-22T10:40:14Z

Popolon:

{{#switch: {{{1|}}}
|GoogleMaps|GM = {{#switch: {{{2|}}}
|Mars = [http://www.google.com/mars/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Moon = [http://www.google.com/moon/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Earth|E = {{#switch: {{{5|}}}
|es|eu|gl = [http://maps.google.es/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}}&ie=UTF8 {{{6}}}]
|cn = [http://ditu.google.cn/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=cn {{{6}}}]
|ja = [http://maps.google.co.jp/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=ja {{{6}}}]
|pl = [http://mapy.google.pl/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=pl {{{6}}}]
|de|fr|it|nl = [http://maps.google.{{{5}}}/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}} {{{6}}}]
|en|#default = [http://maps.google.com/maps?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5|en}}} {{{6}}}]
}}
}}
|GoogleEarth|GE = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/earth.php|latdegdec={{{3|0}}}&londegdec={{{4|0}}}&scale=10000&commons=1}} {{{6}}}] }}
|Proximityrama|PR = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/proximityrama|latlon={{{3|0}}},{{{4|0}}}}} {{{6}}}] }}
<nowiki><!--|OpenStreetMap|OSM = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~kolossos/openlayers/commons-on-osm.php|zoom=16&lat={{{3|0}}}&lon={{{4|0}}}}} {{{6}}}] }} ==></nowiki>
|OpenStreetMap|OSM = [ http://www.openstreetmap.org/#map=10/{{{3|0}}}/{{4|0}}} {{{6}}}]
}}<noinclude>
Template for formating external links to mapping websites. Used by {{tl|location/layout}}. 
Input Parameters:
# <nowiki>{{{1}}}</nowiki> - name of external website: GoogleMap (aka GM), GoogleEarth (aka GE), Proximityrama (aka PR), OpenStreetMap (aka OSM)etc.
# <nowiki>{{{2}}}</nowiki> - name of the globe: earth, mars, moon
# <nowiki>{{{3}}}</nowiki> - latitude
# <nowiki>{{{4}}}</nowiki> - longitude
# <nowiki>{{{5}}}</nowiki> - language code: en, pl, de, etc.
# <nowiki>{{{6}}}</nowiki> - Link text
</noinclude>

Template:Location/ExternalLink

2013-10-22T10:39:12Z

Popolon:

{{#switch: {{{1|}}}
|GoogleMaps|GM = {{#switch: {{{2|}}}
|Mars = [http://www.google.com/mars/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Moon = [http://www.google.com/moon/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Earth|E = {{#switch: {{{5|}}}
|es|eu|gl = [http://maps.google.es/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}}&ie=UTF8 {{{6}}}]
|cn = [http://ditu.google.cn/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=cn {{{6}}}]
|ja = [http://maps.google.co.jp/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=ja {{{6}}}]
|pl = [http://mapy.google.pl/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=pl {{{6}}}]
|de|fr|it|nl = [http://maps.google.{{{5}}}/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}} {{{6}}}]
|en|#default = [http://maps.google.com/maps?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5|en}}} {{{6}}}]
}}
}}
|GoogleEarth|GE = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/earth.php|latdegdec={{{3|0}}}&londegdec={{{4|0}}}&scale=10000&commons=1}} {{{6}}}] }}
|Proximityrama|PR = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/proximityrama|latlon={{{3|0}}},{{{4|0}}}}} {{{6}}}] }}
<nowiki><!--|OpenStreetMap|OSM = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~kolossos/openlayers/commons-on-osm.php|zoom=16&lat={{{3|0}}}&lon={{{4|0}}}}} {{{6}}}] }} ==></nowiki>
|OpenStreetMap|OSM = [ http://www.openstreetmap.org/#map=10/{{{3|0}}}/{{4|0}}} {{6}}]
}}<noinclude>
Template for formating external links to mapping websites. Used by {{tl|location/layout}}. 
Input Parameters:
# <nowiki>{{{1}}}</nowiki> - name of external website: GoogleMap (aka GM), GoogleEarth (aka GE), Proximityrama (aka PR), OpenStreetMap (aka OSM)etc.
# <nowiki>{{{2}}}</nowiki> - name of the globe: earth, mars, moon
# <nowiki>{{{3}}}</nowiki> - latitude
# <nowiki>{{{4}}}</nowiki> - longitude
# <nowiki>{{{5}}}</nowiki> - language code: en, pl, de, etc.
# <nowiki>{{{6}}}</nowiki> - Link text
</noinclude>

Template:Location/ExternalLink

2013-10-22T10:37:33Z

Popolon:

{{#switch: {{{1|}}}
|GoogleMaps|GM = {{#switch: {{{2|}}}
|Mars = [http://www.google.com/mars/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Moon = [http://www.google.com/moon/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Earth|E = {{#switch: {{{5|}}}
|es|eu|gl = [http://maps.google.es/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}}&ie=UTF8 {{{6}}}]
|cn = [http://ditu.google.cn/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=cn {{{6}}}]
|ja = [http://maps.google.co.jp/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=ja {{{6}}}]
|pl = [http://mapy.google.pl/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=pl {{{6}}}]
|de|fr|it|nl = [http://maps.google.{{{5}}}/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}} {{{6}}}]
|en|#default = [http://maps.google.com/maps?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5|en}}} {{{6}}}]
}}
}}
|GoogleEarth|GE = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/earth.php|latdegdec={{{3|0}}}&londegdec={{{4|0}}}&scale=10000&commons=1}} {{{6}}}] }}
|Proximityrama|PR = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/proximityrama|latlon={{{3|0}}},{{{4|0}}}}} {{{6}}}] }}
<nowiki><!--|OpenStreetMap|OSM = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~kolossos/openlayers/commons-on-osm.php|zoom=16&lat={{{3|0}}}&lon={{{4|0}}}}} {{{6}}}] }} ==></nowiki>
|OpenStreetMap|OSM = {{#switch: {{{2|}}}|[ http://www.openstreetmap.org/#map=10/{{{3|0}}}/{{4|0}}} {{6}}] }}
}}<noinclude>
Template for formating external links to mapping websites. Used by {{tl|location/layout}}. 
Input Parameters:
# <nowiki>{{{1}}}</nowiki> - name of external website: GoogleMap (aka GM), GoogleEarth (aka GE), Proximityrama (aka PR), OpenStreetMap (aka OSM)etc.
# <nowiki>{{{2}}}</nowiki> - name of the globe: earth, mars, moon
# <nowiki>{{{3}}}</nowiki> - latitude
# <nowiki>{{{4}}}</nowiki> - longitude
# <nowiki>{{{5}}}</nowiki> - language code: en, pl, de, etc.
# <nowiki>{{{6}}}</nowiki> - Link text
</noinclude>

Template:Location/ExternalLink

2013-10-22T10:35:29Z

Popolon: +direct osm link (and comment actual ref to wikipedia tools (as it's not linked for now)

{{#switch: {{{1|}}}
|GoogleMaps|GM = {{#switch: {{{2|}}}
|Mars = [http://www.google.com/mars/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Moon = [http://www.google.com/moon/#lat={{{3|0}}}&lon={{{4|0}}}&zoom=8 {{{6}}}]
|Earth|E = {{#switch: {{{5|}}}
|es|eu|gl = [http://maps.google.es/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}}&ie=UTF8 {{{6}}}]
|cn = [http://ditu.google.cn/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=cn {{{6}}}]
|ja = [http://maps.google.co.jp/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=ja {{{6}}}]
|pl = [http://mapy.google.pl/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl=pl {{{6}}}]
|de|fr|it|nl = [http://maps.google.{{{5}}}/?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5}}} {{{6}}}]
|en|#default = [http://maps.google.com/maps?ll={{{3|0}}},{{{4|0}}}&spn=0.01,0.01&t=k&q=http://toolserver.org/~para/GeoCommons/GeoCommons-simple.kml&hl={{{5|en}}} {{{6}}}]
}}
}}
|GoogleEarth|GE = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/earth.php|latdegdec={{{3|0}}}&londegdec={{{4|0}}}&scale=10000&commons=1}} {{{6}}}] }}
|Proximityrama|PR = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~para/GeoCommons/proximityrama|latlon={{{3|0}}},{{{4|0}}}}} {{{6}}}] }}
<nowiki><!--|OpenStreetMap|OSM = {{#switch: {{{2|}}}| Earth|E = - [{{fullurl:tools:~kolossos/openlayers/commons-on-osm.php|zoom=16&lat={{{3|0}}}&lon={{{4|0}}}}} {{{6}}}] }} ==></nowiki>
|OpenStreetMap|OSM = [http://www.openstreetmap.org/#map=10/{{{3|0}}}/{{4|0}}}]
}}<noinclude>
Template for formating external links to mapping websites. Used by {{tl|location/layout}}. 
Input Parameters:
# <nowiki>{{{1}}}</nowiki> - name of external website: GoogleMap (aka GM), GoogleEarth (aka GE), Proximityrama (aka PR), OpenStreetMap (aka OSM)etc.
# <nowiki>{{{2}}}</nowiki> - name of the globe: earth, mars, moon
# <nowiki>{{{3}}}</nowiki> - latitude
# <nowiki>{{{4}}}</nowiki> - longitude
# <nowiki>{{{5}}}</nowiki> - language code: en, pl, de, etc.
# <nowiki>{{{6}}}</nowiki> - Link text
</noinclude>

De Havilland DH.88 Comet

2013-06-17T10:46:46Z

Popolon: +fgname

{{aero-stub}}

{{infobox Aircraft
|image = DH-88.jpg
|name =De Havilland DH 88 Coment
|type = 2-piston engine racer
|livery =
|fdm =
|status = Git only
|authors =
|fgname = dh88
|download =
}}

The de Havilland DH.88 Comet was 2 engine piston racer of the 1930s. Won the MacRobertson race.

[http://upload.wikimedia.org/wikipedia/commons/7/7c/TMA45_de_Havilland_Comet.jpg Public domain postcard of DH.88 (wikimedia.org)]

[http://www.xs4all.nl/~tozu/dh88/index.htm DH.88 info]

[[Table of models]]

{{de Havilland}}

[[Category:Twin Engine Piston]]
[[Category:Racing aircraft]]

Es/Cessna 337G Skymaster

2013-06-17T10:41:01Z

Popolon: +fgname +link fr:

{{infobox Aircraft
|image = Cessna337_01.png
|name = Cessna 337G Skymaster
|type = Avioneta civil a pistón
|fdm = JSBsim
|fgname = Cessna337
|status-fdm = 3
|status-systems = 2
|status-cockpit = 5
|status-model = 5
|authors = Fernando Espinosa, Pavel Cueto
|download = http://www.vivefg.org/index.php?option=com_content&view=article&id=48:cessna-337-skymaster&catid=35:hangar&Itemid=40
}}

La '''Cessna 337''' es un avión bimotor construido en una configuración "push pull" (tira/empuja). En lugar de tener los motores montados en las alas, uno de ellos va montado en la nariz y otro en la parte de atrás del fuselaje. Los estabilizadores van montados sobre soportes que emergen por detrás de las alas. El Cessna 337 tiene un tren retráctil, lo cual le otorga un poco de velocidad extra.

La combinación de motores de tracción y empuje produce un sonido único.

== Ayuda del avión ==

=== Atajos de teclado ===

* '''d''' - Abre/cierra puerta de la cabina
* '''c''' - Abre/cierra cowl flaps delanteros
* '''C''' - Abre/cierra cowl flaps traseros
* '''m/M''' - Ajuste de mezcla de combustible
* '''n/N''' - Ajusta el speed governor (ángulo de la hélice)

=== Límites ===

* '''VNE:''' 198 KIAS ''(Velocidad de nunca exceder)''
* '''VNO:''' 167 KIAS ''(Max.velocidad para operaciones normales)''
* '''VA:''' 140 KIAS ''(Velocidad de maniobra)''
* '''VFE:''' 109 KIAS ''(Max.velocidad con flaps extendidos a tope)''
* '''VLE:''' 200 KIAS ''(Max.velocidad con el tren de aterrizaje extendido)''
* '''VLO:''' 140 KIAS ''(Max.velocidad para bajar o levantar el tren de aterrizaje)''
* '''Velocidad de pérdida, flaps a tope:''' 61 KIAS
* '''Velocidad de pérdida, sin flaps:''' 70 KIAS
* '''Peso máximo:''' 4630 lbs. ''(2100 kg)''
* '''Techo de servicio (con los 2 motores):''' 18,000 ft ''(5.486 mts)''
* '''Carrera de despegue:''' 1,000 ft ''(304 mts)''
* '''Ground roll for landing''' 700 ft ''(213mts)''

== Procedimientos normales ==
[[File:Cessna337-cockpit.png|thumb|250px|General view of the Skymaster cockpit]]
[[File:Cessna337-details.png|thumb|250px|The model is pretty detailed, and users can select between 5 HQ liveries]]
[[File:Cessna337-night.png|thumb|250px|Nice view of the Skymaster cockpit at night]]

=== Encendido ===
* Encender batería y alternadores (generadores) frontal y trasero
* Encender el botón master de aviónica (panel del muro izquierdo)
* Encender la aviónica (Radios COM/NAV, DME, ADF...)
* Encender bombas de combustible (aún sin implementar)
* Encender Pitot Heat, y las luces que se requieran
* Abrir cowl flaps delanteros y traseros
* Encender magnetos (rueda del mouse) y starter (botón izquierdo del mouse) del motor trasero.
* Encender magnetos y starter del motor delantero.

=== Despegue ===
* Checkear cowl flaps delanteros y traseros abiertos, para evitar sobrecalentamiento
* Checkear mezcla rica, y RPM máximas del speed governor (palanca de pitch)
* Acelerador a tope, soltar frenos
* Rotar a 60 KIAS
* Recoger tren de aterrizaje

=== Vuelo crucero ===
La Cessna 337 Skymaster posee una hélice de velocidad constante; por lo tanto, el piloto puede incrementar el ángulo de la hélice para conseguir una mayor velocidad, pero a costa de una pérdida de RPM y potencia del motor.
* Reducir acelerador hasta la potencia deseada.
* Disminuir RPM con el speed governor (palanca de pitch)
* Ajustar mezla dependiendo de la altitud de vuelo (5.000 pies o más). Chequear EGT para una mezcla óptima.
* Cerrar los cowl flaps

=== Aterrizaje ===
* Abrir los cowl flaps
* Aumentar RPM al máximo con el speed governor (palanca de pitch)
* Reducir potencia con el acelerador
* Bajar tren de aterrizaje
* Desplegar gradualmente los flaps a partir de 110 KIAS
* Tocar tierra a 75/60 KIAS, dependiendo del peso del avión

== Sistemas ==
[[File:Cessna337-avionics.png|thumb|250px|Detail of the avionics panel]]

La Cessna 337 continúa en desarrollo, pero tiene algunos sistemas útiles. Los sistemas eléctricos, de succión y combustible funcionan, pero sin tener aún un sistema de fallos modelado. Los usuarios pueden ajustar tanto el combustible en cada estanque como el peso en cada uno de los asientos del avión. Casi todos los botones, conmutadores, perillas y palancas son funcionales y se encuentran adecuadamente animados, y todos los instrumentos están etiquetados para una correcta identificación.

En cuanto a las perillas, use la rueda del mouse para ajustes mayores, y los botones izquierdo y central para un ajuste fino. Cuando esté seteando frecuencias de radio, la rueda del mouse ajustará números enteros, en tanto los botones ajustarán los decimales. Intente este mismo método para ajustar los demás instrumentos, interruptores de cowl flaps, controles de trim, magentos, etc.

=== Aviónica ===

Nuestra versión de la Skymaster está provista de un pack de aviónica Bendix/King, habilitados para una completa navegación IFR nocturna:
* 2 radios COMM/NAV KX-155, conectadas a un par de localizadores VOR KI-206
* Receptor DME KN-62A (en desarrollo, trabaja sólamente con NAV 1)
* Receptor ADF KR-87, conectado a un localizador ADF KI-227
* Panel de audio KMA-24 (sin utilidad en FlightGear)
* Transponder KT-76A (sin utilidad en FlightGear)
* Altímetro de radar KI-250, habilitado para marcar altura de decisión en aterrizajes con escasa visibilidad

=== ELT ===

El [[ELT]] (acrónimo de "Emergency Locator Transmitter", o Transmisor de localización de emergencia), es un dispositivo que envía un mensaje automático en caso de accidente del avión. Este mensaje contiene información acerca del modelo del avión, dueño del mismo, y coordenadas aproximadas del avión accidentado, y está pensado para solicitar servicios SAR (Search and Rescue, también llamado "Servicio Aéreo de Rescate"). La Cessna Skymaster es el primer avión en FlightGear en ser equipado con un ELT funcional.

== Links externos ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=12733 Cessna 337G official forum post]
* [http://www.youtube.com/watch?v=-ijJa0G5NgQ Video Cessna 337G MPG HD]

[[Category:Aviones]]
[[Category:Aviones civiles]]

[[en:Cessna 337G Skymaster‎‎]]
[[fr:Cessna 337G Skymaster]]

Fr/Cessna 337G Skymaster

2013-06-17T10:40:02Z

Popolon: +fgname

{{infobox Aircraft
|image = Cessna337_01.png
|name = Cessna 337G Skymaster
|type = Piston, avion civil
|fdm = JSBsim
|fgname = Cessna337
|status-fdm = 3
|status-systems = 2
|status-cockpit = 5
|status-model = 5
|authors = Fernando Espinosa, Pavel Cueto
|download = http://www.vivefg.org/index.php?option=com_content&view=article&id=48:cessna-337-skymaster&catid=35:hangar&Itemid=40
}}
Le '''Cessna 337''' est un [[Fr/Avions|avion]] bi-moteur construit en configuration push-pull. Plutôt que de monter les moteurs sur les ailes, l'un est placé sur le nez et l'autre à l'arrière du fuselage en nacelle. Les dérives sont montées sur les poutres elles-mêmes rattachées aux ailes

Le Skymaster possède un train d'atterrissage rétractable qui lui apporte un petit gain de vitesse supplémentaire.

La combinaison d'un moteur tracteur et propulseur produit un son unique

== Aide de l'avion ==

=== Commandes de l'avion ===

* '''d''' - Ouvrir/fermer la porte du cockpit
* '''c''' - Ouvrir/fermer les volets de capots avant
* '''C''' - Ouvrir/fermer les volets de capot arrière
* '''m/M''' - Réglez le mélange de carburant
* '''n/N''' - Pas de l'hélice

=== Limites ===

* '''VNE:''' 198 KIAS ''(Vitesse à ne jamais exéder)''
* '''VNO:''' 167 KIAS ''(vitesse maximum pour des opérations courantes)''
* '''VA:''' 140 KIAS ''(vitesse de manœuvre)''
* '''VFE:''' 109 KIAS ''(vitesse maximum avec volets complètement sortis)''
* '''VLE:''' 200 KIAS ''(Vitesse maximum avec train sorti)''
* '''VLO:''' 140 KIAS ''(Vitesse maximum pour rentrer/sortir le train d'atterrissage)''
* '''Vitesse de décrochage''', volets complètement sortis: 61 KIAS
* '''Vitesse de décrochage''' sans volets : 70 KIAS
* '''Mpoids maximum:''' 4630 lbs. ''(2100 kg)''
* '''Plafond pratique (deux moteurs):''' 18,000 ft
* '''Distance de décollage:''' 1,000 ft
* '''Distance d'atterrissage''' 700 ft

== Procédures normales ==
[[File:Cessna337-cockpit.png|thumb|250px|Vue générale du cockpit du Skymaster]]
[[File:Cessna337-details.png|thumb|250px|Le modèle est très détaillé et l'utilisateur a le choix entre 5 livrées haute qualité]]
[[File:Cessna337-night.png|thumb|250px|Magnifique vue du cockpit du Symaster à minuit]]

=== Démarrage ===
* Allumer la batterie et les générateurs avant et arrières
* Turn on master avionics button (left wall panel)
* Turn on the avionics (NAV/COMM Radios, DME, ADF...)
* Allumer les pompes à carburant (non fonctionnel pour le moment)
* Allumer les lumières requises et le réchaufage des sondes pitot
* Ouvrir les volets de capot avant et arrière
* Mettre en marche les magneto arrières(molette de la souris), continuer à tourner le bouton pour démarrer (bouton de gauche)
* Mettre en marche les magneto avant, continuer à tourner le bouton pour démarrer

=== Décollage ===
* Vérifier que les volets de capot avants et arrières soient ouvert pour éviter la surchauffe
* Vérifier la mixture et le pas de l'hélice
* Retirer le frein de parc, plein gaz
* Rotation à 60 KIAS
* Rentrer le train

=== Croisière ===
Le Cessna 337 Skymaster possède une hélice à vitesse constante, donc vous pouvez augmenter le pas de l'hélice pour obtenir plus de vitesse, mais avec une perte de régime du moteur et de puissance.
* Diminution des gaz à la puissance désirée
* Diminution des RPM avec la gouverne de vitesse (manette de pas de l'hélice)
* Régler le mélange en fonction de l'altitude de vol (pour 5000 pieds ou plus). Vérifiez l'EGT pour le meilleur mélange.
* Fermez les volets de capot

=== Atterrissage ===
* Ouvrez les volets de capot
* Augmenter les RPM avec la gouverne de vitesse (manette de pas de l'hélice) au maximum
* Réduire la puissance avec la manette des gazs
* Sortir le train d'atterrissage
* Déployer les volets graduellement en dessous de 110 KIAS
* toucher à 75/60 KIAS, en fonction du chargement de l'avion

== Systèmes ==
[[File:Cessna337-avionics.png|thumb|250px|Detail of the avionics panel]]
Le Cessna 337 est encore en développement, mais il présente plusieurs systèmes fonctionnels. Les systèmes électriques, la pompe à vide et le Système de carburant fonctionnent, mais aucun système de panne n'a été simulé pour le moment. Les utilisateurs peuvent ajuster le poids de chaque passagers de l'avion et la quantité de fuel embarquée. Presque tous les boutons leviers et manettes sont fonctionnels et animés, et tous les instruments sont étiquetés pour une identification adéquate.

About knobs, use scroll mouse for gross adjustments, and left-central buttons for fine tunning. When setting radio frequencies, the mouse scroll will adjust integral numbers, and buttons will tune decimals. Try that method with instruments, cowl flap switches, trim levers, magnetos, etc.

=== Avionics ===

Our Skymaster release is provided with a working Bendix/King avionics pack, capable to full IFR night navigation:
* 2 KX-155 COMM/NAV Radios, attached to a pair of KI-206 VOR locators
* KN-62A DME receiver (in development, attached to NAV1 only)
* KR-87 ADF receiver, attached to a KI-227 ADF locator
* KMA-24 Audio panel (not useful in FlightGear yet)
* KT-76A Transponder (not useful in FlightGear yet)
* KI-250 Radar altimeter, capable to mark decision height for low-visibility landings

=== ELT ===

The [[ELT]] (Emergency Locator Transmitter) is a device which send a message in case of aircraft crash. That message contains info about aircraft model, owner and approximate coordinates of the crashed plane, and it is made to request SAR (Search and Rescue) services. The Cessna Skymaster is the first plane equiped with a functional ELT on FlightGear; however, it's not very useful yet due a bug in the aircraft wich made it unable to be crashed. We hope it will be fixed soon.

== Liens externes ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=12733 Cessna 337G official forum post]
* [http://www.youtube.com/watch?v=-ijJa0G5NgQ Video Cessna 337G MPG HD]

{{Cessna}}

[[Category:Civil utility aircraft]]
[[Category:Push-pull aircraft]]
[[Category:Twin boom aircraft]]

[[es:Cessna 337G Skymaster]]
[[en:Cessna 337G Skymaster]]

Cessna 337G Skymaster

2013-06-17T10:12:17Z

Popolon: +fgname

{{infobox Aircraft
|image = Cessna337_01.png
|name = Cessna 337G Skymaster
|type = Piston, civilian aircraft
|fdm = JSBsim
|fgname = Cessna337
|status-fdm = 3
|status-systems = 2
|status-cockpit = 5
|status-model = 5
|authors = Fernando Espinosa, Pavel Cueto
|download = http://www.vivefg.org/index.php?option=com_content&view=article&id=48:cessna-337-skymaster&catid=35:hangar&Itemid=40
}}
The '''Cessna 337''' is a twin-engine [[aircraft]] built in a push-pull configuration. Instead of the engines being mounted on the wings, one is mounted on the nose and the other at the rear of the pod-style fuselage. The stabilizers are mounted on booms that extend from the wings. The Skymaster has a retractable undercarriage that gives it that little bit of extra speed.

The combination of a tractor and a pusher engine produces a unique sound.

== Aircraft help ==

=== Aircraft keys ===

* '''d''' - Open/close cockpit door
* '''c''' - Open/close front cowl flaps
* '''C''' - Open/close rear cowl flaps
* '''m/M''' - Adjust fuel mixture
* '''n/N''' - adjust speed governor (propeller pitch)

=== Limits ===

* '''VNE:''' 198 KIAS ''(Never exceed speed)''
* '''VNO:''' 167 KIAS ''(Max. speed for normal operations)''
* '''VA:''' 140 KIAS ''(Design maneuvering speed)''
* '''VFE:''' 109 KIAS ''(Max. full flap extended speed)''
* '''VLE:''' 200 KIAS ''(Max. landing gear extended speed)''
* '''VLO:''' 140 KIAS ''(Max. landing gear extend/retract speed)''
* '''Stall''' speed, full flaps: 61 KIAS
* '''Stall''' speed, zero flaps: 70 KIAS
* '''Max. weight:''' 4630 lbs. ''(2100 kg)''
* '''Service ceiling (two engines):''' 18,000 ft
* '''Ground run for takeoff:''' 1,000 ft
* '''Ground roll for landing''' 700 ft

== Normal procedures==
[[File:Cessna337-cockpit.png|thumb|250px|General view of the Skymaster cockpit]]
[[File:Cessna337-details.png|thumb|250px|The model is pretty detailed, and users can select between 5 HQ liveries]]
[[File:Cessna337-night.png|thumb|250px|Nice view of the Skymaster cockpit at night]]

=== Startup ===
* Turn ON battery and front and rear generators
* Turn ON master avionics button (left wall panel)
* Turn ON the avionics (NAV/COMM Radios, DME, ADF...)
* Turn ON fuel pumps (not implemented yet)
* Turn ON required lights and pitot heat
* Open front and rear cowl flaps
* Turn ON rear magnetos (mouse wheel), continue turning the knob for starter (left button)
* Turn ON front magnetos, continue turning the knob for starter

=== Takeoff ===
* Check open front & rear cowl flaps to avoid overheating
* Check rich mixture and high RPM speed governor (propeller pitch)
* Full trhottle, release brakes
* Rotate at 60 KIAS
* Retract gear

=== Cruise ===
The Cessna 337 Skymaster has a constant-speed propeller; so, you can increase propeller pitch to get more airspeed, but with a loss of engine RPM and power.
* Decrease throttle to desired power
* Decrease RPM with speed governor (propeller pitch)
* Adjust mixture depending on flight altitude (for 5000ft or more). Check EGT for best mixture.
* Close cowl flaps

=== Landing ===
* Open cowl flaps
* Increase RPM with speed governor (propeller pitch) to maximum
* Reduce power with throttle
* Open landing gear
* Deploy flaps gradually under 110 KIAS
* Touchdown at 75/60 KIAS, depending on aircraft weight

== Systems ==
[[File:Cessna337-avionics.png|thumb|250px|Detail of the avionics panel]]

The Cessna 337 still in development, but it has some suitable systems. Electrical, vacuum and fuel system are working, but they have no failure system modelled yet. Users can adjust the weight of each seat on the plane and fuel amount. Almost all buttons, knobs and levers are functional and properly animated, and all instruments are labeled for a properly identification.

About knobs, use scroll mouse for gross adjustments, and left-central buttons for fine tunning. When setting radio frequencies, the mouse scroll will adjust integral numbers, and buttons will tune decimals. Try that method with instruments, cowl flap switches, trim levers, magnetos, etc.

=== Avionics ===

Our Skymaster release is provided with a working Bendix/King avionics pack, capable to full IFR night navigation:
* 2 KX-155 COMM/NAV Radios, attached to a pair of KI-206 VOR locators
* KN-62A DME receiver (in development, attached to NAV1 only)
* KR-87 ADF receiver, attached to a KI-227 ADF locator
* KMA-24 Audio panel (not useful in FlightGear yet)
* KT-76A Transponder (not useful in FlightGear yet)
* KI-250 Radar altimeter, capable to mark decision height for low-visibility landings

=== ELT ===

The [[ELT]] (Emergency Locator Transmitter) is a device which send a message in case of aircraft crash. That message contains info about aircraft model, owner and approximate coordinates of the crashed plane, and it is made to request SAR (Search and Rescue) services. The Cessna Skymaster is the first plane equiped with a functional ELT on FlightGear.

== External links ==
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=12733 Cessna 337G official forum post]
* [http://www.youtube.com/watch?v=-ijJa0G5NgQ Video Cessna 337G MPG HD]

{{Cessna}}

[[Category:Civil utility aircraft]]
[[Category:Push-pull aircraft]]
[[Category:Twin boom aircraft]]

[[es:Cessna 337G Skymaster]]
[[fr:Cessna 337G Skymaster]]

FlightGear high-level architecture support

2013-06-12T07:24:03Z

Popolon: /* What is HLA/RTI */

{{Template:Non-stable}}

{{infobox subsystem
|name = HLA Support
|started= 05/2009
|description = Implementing support for the High Level Architecture to modularize FlightGear
|status = Under active development (2009-2013)
|developers = Mathias Fröhlich, James Turner
|folders =
* [https://gitorious.org/openrti OpenRTI]
* [https://gitorious.org/fg/simgear/trees/next/simgear/hla HLA in SimGear]
* [https://gitorious.org/fg/flightgear/trees/next/src/Network/HLA HLA in FlightGear]

}}

= Objective =
Also see [[Developing with HLA]].

Document the ongoing HLA effort, to help people better understand how this affects a number of related FlightGear efforts and projects (particularly related to [[Modularizing, parallelizing and distributing FlightGear|improved modularization, concurrency support]] and the [[Distributed Interactive Simulation|multiplayer]]/[[Decoupling the AI Traffic System|AI system]]). FlightGear related limitations have been extensively discussed over the years, for a comprehensive summary, please see [[Modularizing, parallelizing and distributing FlightGear]].

Although the FlightGear design fairly modular it's provided as a single binary. Everyone who wants to create a new I/O module must patch the FlightGear sources and compile the FlightGear binary from scratch. This may discourage those who want to use FlightGear as a tool and extend it in some way. Moreover, it's not always possible to include all functions in a single binary. Some functions may be mutually exclusive.

The plan is to use HLA/RTI as an aid to parallellize flightgear on a local machine. The basic advantage is that each federate is strictly programmed single threaded. All the thread syncronization is handled by the rti library and hidden in that thing. The trick is that each of these threads must be done in a way that you can just compile that alternatively in a single standalone binary and run the same component in a networked rti - the LinuxTag booth for example.

Basically, better HLA support will make it possible for FlightGear to be split into "components" (each running in a dedicated process or in separate thread within the main FlightGear process), making better use of multi-core architectures (SMP), while decoupling the flight simulation from the "viewer" part (i.e. visualization), so that steady/reliable frame rates can be achieved (see [[FGViewer]]), but also to formalize the concept of master/slave instances and synchronizing state among multiple instances (think AI traffic/weather).

{{cquote|I will provide a different renderer sometime in the future where I aim to provide better isolation of this kind of renderer options so that people with very different aims can probably coexist better.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39180.html |title=Color-shifts for textures|author=Mathias Fröhlich |date= Sun, 27 Jan 2013 08:45:22 -0800}}</ref>|Mathias Fröhlich}}

{{cquote|supporting the option of different viewer / rasteriser front-ends is by far the best solution here, since there are different requirements for different use-cases and target users. Plenty of people are interested in the kind of effects Thorsten's uber-shader and atmospheric model can provide, but plenty of others care more about a solid 60Hz (or even higher), and still others would prefer a solution that works with the fixed-funtion pipeline. And then there's Rembrandt as yet another rendering configuration. My plan in parallel with / after 2.12 is to work with Mathias' HLA code to make
this separation possible, unless of course he beats me to it :)<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39181.html |title=Color-shifts for textures|author=James Turner |date=Sun, 27 Jan 2013 09:35:43 -0800}}</ref>|James Turner}}

{{cquote|There's a larger issue here, that 'soon' (likely during the summer) I want to start restructuring the codebase into multiple processes, so we can support different rendering architectures (and use multiple CPUs) better. That's Mathias Fröhlich's HLA/RTI work, and indeed he has done the recent work on extending fgviewer to test changes to the current terrain system. <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39693.html |title=Generating ground textures on the fly?|author=James Turner |date=Mon, 11 Mar 2013 15:24:07 -0700}}</ref>|James Turner}}

{{cquote|concerning the larger issue of different rendering pipelines / approaches, my opinion is, and remains, that the long-term solution is separate viewer codebases - while a plethora would be bad, we would already benefit from a 'fixed-function, no shaders' renderer codebase distinct from a Rembrandt renderer and modern, forward-rendering OpenGL 3.x pipeline. This needs the viewer to be cleanly split out from the simulation backend, via HLA, which is exactly what Mathias (and soon, myself) are working towards, but slowly.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39922.html |title=Atmospheric Light Scattering|author=James Turner |date=Thu, 25 Apr 2013 08:09:08 -0700}}</ref>|James Turner}}

<references/>

= Status 04/2013 =
Simgear already has some RTI abstraction library that should help to implement HLA federates. Both, SimGear and FlightGear need to be configured/rebuilt with -DENABLE_RTI (after first installing openRTI).

Flightgear git already has an alternative multiplayer implementation in place that uses HLA. But that is only thought as a proof of concept. The next step is probably to provide a seperate hla federate that runs the [[Decoupling the AI Traffic System|AI traffic]] and feeds that into an rti federation (see the fgai section below).

Also see:
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32045.html
* http://www.mail-archive.com/search?q=fgai&l=flightgear-devel%40lists.sourceforge.net
* https://gitorious.org/fg/flightgear/commit/d79b2385b4f4a64a2460c32e6123ea399bfa83d6
* https://gitorious.org/fg/flightgear/trees/next/utils/fgai

Also see [[FlightGear CIGI Support (Common Image Generator Interface)]].

= Background =
When you start up FlightGear on a 8-12-core machine, you'll find that most cores aren't really utilized at all. This is in stark contrast to X-Plane for example. There are many computations being run as part of the FG main loop, that don't stricly belong there, and which could obviously run outside the main loop, either in a separate thread or a dedicated process.

We have been adding more and more threading to FG because of this, but we are also seeing more and more segfaults related to multithreaded code in FG. Just look at some of the recently reported bugs (issue tracker), many of them are directly related to concurrency issues and multiple threads doing things in a fashion which isn't threadsafe.

Fixing this is something that requires explicit re-architecting, it cannot be just delegated to OSG assuming that it will just magically work. OSG parallelization is specifically related to rendering and following certain coding patterns and protocols, it will not directly help you otherwise. Even if you could run 99% of the rendering work asynchronously, that will not have any positive effect, because obviously it's our main loop that's becoming the showstopper here.

The HLA approach is different and more promising in that a process-based parallelization effort actually forces people to think about the problem at hand. Also, using an existing industry standard (such as i.e. HLA or CIGI) is going to make FlightGear increasingly relevant and attractive to industry leaders.

The idea is to divide parts of the FlightGear architecture such that multiple simulations collaborate and can be run in different threads or even processes. Basically, you would not have a single monolithic FG application with a conventional main loop, but rather a handful of modules (FDM, AI, weather/environment, scripting) that get to communicate with each other by using a central managing component, called a "Real-Time Infrastructure".

Normally, a process-based modularization strategy would inevitably mean that modules need to be run as separate processes, but Mathias mentioned a clever scheme to directly run certain "component subsystems" in worker threads, which would then be a part of the main FG process, while still using HLA and a central RTI to handle the communications across all HLA federates.

For professional users, it is extremely important to guarantee reliable frame rates, ideally separating the visualization from the underlying computation, so that separate computers can be used for different systems [http://flightgear.org/forums/viewtopic.php?f=18&t=15755&p=153295&hilit=hla+relevant#p153288].

== OSG Threading vs. HLA ==
Distributed multi-process configurations are in fact exactly the way professional simulators work, too: They are distributed and communicate using sockets. Mathias' ongoing HLA work is going to make that increasingly feasible.

OSG threading is neat and dandy, but obviously it is only directly useful for rendering related parallelization and related work. On the other hand, none of this comes for free. OSG's threading support really is impressive, but all those OSG threads must be kept busy. Properly. That's exactly the work that FlightGear is responsible for in its main loop.

OSG's multithreading support doesn't just come "automagically", just because FlightGear uses OSG. The multithreading support in OSG must be explicitly supported by following certain OSG coding patterns and coding protocols. Otherwise, you won't benefit at all.

Obviously, OSG really is extremely powerful and also pretty good at parallelizing things, but you cannot necessarily see that when running FlightGear now, but there is other OSG-based software which is making really good use of this.

Correct multithreading is incredibly hard to get right in any non-trivial application.

Especially in complex systems like FlightGear. This holds even more true because FlightGear is implemented in C and C++, none of which has language-level support for concurrency and parallelism.

Basically, there's no language-level support for multithreading in the C-family of languages. Everything needs to be built and emulated using library-functions and classes such as Boost (this is less so in Java).

Still, coding a threaded design in C or C++ with more than 3-5 threads is incredibly tricky to get right (this will also be a problem once more threading will be used in Nasal code, because it also lacks language-level threading support).

There are languages far better suited for multithreaded programming, such as Ada - because they have language-level primitives to create "tasks" and "protected types".

== What is HLA/RTI ==

HLA/RTI is message distribution API used for distributed and paralell real time simulation systems. There are
a few API variants out there where the newest two ones are an IEEE standard known as rti1516 and rti1516e. This api is used in some open source simulation systems and in plenty simulation systems you can buy on the market. The api might look difficult at the first time, but it provides a carefully designed set of communication methods that avoid communication latencies - the worst problem in real time simulations - for a distributed simulation system.

The API is standardized by an IEEE standard and used with commercial simulation systems as well, and depending on the RTI implementation, available with different language bindings like C++, java, ada. Additionally there are implementations hooking on to of those given ones for matlab, python, fortran and probably more. This should also extend the abilities to communicate with components using the tools and languages we cannot handle currently in any sensible way.

== HLA vs. Shared Memory/IPC ==
The nice thing is that the ipc is hidden behind something that is also able to distribute this across multiple machines. A local network connect is mostly sufficient. But doing the same by an infniband connect is possible too. Experimenting with shared memory did not bring notable improovements over a system local network connect. At least not on linux...

In any case I think this could be fast enough to do this stuff.

Also this stuff is based on a standard that is probably enables us to be a little more connective in the end. At least this is a slight hope from me.

While the interface is providing more than you need today, I think the major benefit is that it shields away a lot of synchronization stuff from you in a
way that you can still program your local component in a single threaded way. The coupling of components *can* be that tight so that you can get deterministic time slicing for some of the components. Say you want to simulate glider towing you can do that with each fdm running in its own process while still deterministically exchanging simulation results at a the fdm's rate and st time step boundaries.
The same goes for components within the aircraft which I consider a possible use case for your kind of application.
In contrast to that, You can still run the viewers asynchronously to the simulatoin core providing hopefully 60 stable frames without being disturbed
by synchonization needs of specific components.

So, you might have an Idea how to to that by ipc directly, and trust me I have considered this at some time. But what this standdard provides is really
driven by exactly those problems that need to be solved once you dig into such kind of implementation. So one of the benefits is that you gain a encapsulated communication library that does what you need. This library can be tested independently of such an application beast like flightgear. And this is IMO a huge benefit.

== Benefits ==
the RTI c++ interface is defined in a way that you do not need to recompile anything. Everyting is done with pure virtual classes and factories to get them. So however this is implemented in the shared object/dll you should just need to get a 'standard' implementation dependent RTI header and compile with that. So you should in theory be able to change the RTI library of an already compiled binary. For the case that a particular RTI implementation does not follow this rule, you need to compile flightgear explicitly for this particular library.

The spatial indices implemented in the RTI regions will be a huge benefit, since you will only recieve the messages that are relevant near the region of your interest.

Also the way an RTI provides time management and time stamped messages, is benefitial. This enables hard syncronized HLA federates, exchanging data at relatively high rates with the least possible communication latency.

Regarding the ongoing threading discussion and the amount of cores an average cpu has today, an RTI will provide a way to implement components of the simulation in a single threaded way, living in its own process.

This can be done while still having a deterministic and tight coupling with other federates simulating in the same federation. This kind of coupling is required for example for a good simulation of glider towing.

The communications infrastructure based on RTI provides a huge potential to split the simulation into components that run on different cores or even machines but still being tight coupled.

Major benefits would be to move some code, such as the [[Decoupling the AI Traffic System|AI code out of the main loop]] - may be even
into a seperate process/thread. Also runnig one instance of that [[Decoupling the AI Traffic System|AI traffic]] for installations like we used to have at the linux tag booth would be a major advantage there.

Anyway, I also consider an RTI a possible multiplayer replacement. Even if we would handle local RTI federations different than internet wide stuff. But yes, an RTI provides almost all we would need to get that right.

What is to be commited is in this step is an alternative to the multiplayer protocol which does not cover really all what the multiplayer protocol can do today. But there is a proof of concept and some playground to start with.
The current implementation in flightgear is flexible enough to adapt to the needs of very different simulation systems. The default object model that you get is adapted to the needs of flightgear, but the implementation is
flexible enough to change the object model to the AviationSim object model for example at startup time.

So, this should not only provide a way to distribute flightgears simulation systems across cpus or may be machines, this should also provide a way to increase connectivity of flightgear to other simulation systems.

Also included is an RTI variant abstraction layer inside simgear to help with some common tasks that are often needed in an HLA/RTI implementation. One of the design goals of this layer was to provide a framework where
interaction with the RTI api consumes as little overhead as possible.

In particular, this means that indies (fast mappings) are used wherever possible and allocations are minimized.

Currently the only implemented RTI variant is the old nonstandard HLA-1.3 api, which was the only api I had available from an open source project at the time I began with that work. But it should be straight forward to extend that to the two IEEE standard RTI variants.

I personally think that there are still too much opportunities to break stuff. Well, with break I do not mean that it does not run or compile. With break I mean that people just put something together that works either for their private needs and they do not care further, or break in the sense that if you would know the bigger picture it would already be very clear that this cannot scale for the kind of use that will most probably happen in the not so distant future.
I can really observe this in the scene and model area. I have really seen incredibly fast osg applications with stable framerates and nifty looking
models. But the way we use osg and put together models leaves osg and below that the driver only little chance to be fast. Which leaves only little
headroom for sensible further development.

Getting back to components: Latencies are a critical part of running in multiple threads/applications. This is not a particular problem of hla, this
is a generic problem when running real time applications in parallel. I know a lot of really smart people who can even understand complex environments very well, but have no clue about the problems introduced by round trips. Seen this, this is the reason why I started that hla stuff, since this provides a framework which supports and even encourages a programming model that is able to hide latencies as good as possible. Anyway, there is a chance that you even use this api in a way that really hurts in this corner. And this is actually the really bad thing I want to avoid: If you are the first component that does not get that right you might just notice little to nothing - especially if you are running on extrem fast hardware. But when the next kind of problem is introduced this really starts to hurt more and more. And most people do not have any chance to see what happens and why.

= Use Cases =

== Weather Simulation ==
We can have a completely independent weather module using the HLA stuff that runs in an own process/thread. So, at that time you might be able to do more sophisticated stuff. May be it will then be possible to do a full cfd for subparts of the scene. That might be a good thing for a glider scene where you might want to have a more detailed fluid behaviour ...

A weather module running in a different process/thread/machine that computes positions for clouds that are consistenly displayed on each attached viewer.
That being a module that is exchangable. The simple version just interploates metars like today, but more sphisticated versions might do a local weather
simulation to get good results for thermals in some small area. The same goes for every component you can think of splitting out.

== AI Traffic ==
A simple [[Decoupling the AI Traffic System|AI model]] does just the trick what it does today. But more sophisticated modules might contain an own fdm so that these machines really live in the same fluid that the weather module provides data for.Note that the RTI API already provides a subsriber model that ensures that you don't feed data to participants that dont' need that.May ba a radar controller screen that can be attached there to see the machines in this word. But sure that radar screen is not interrested in flap animations for the aircraft ...

For over a decade, we've been talking about moving the AI traffic subsystem out of the fgfs main loop, not just to free computing resources, but also to make it easier to synchronize AI traffic with multiple instances, i.e. using multiplayer or master/slave setups with possibly dozens of computers (see [[Decoupling the AI Traffic System]]) and the link at [http://wiki.flightgear.org/images/1/1e/New_FG_architecture.pdf]. This requirement has been also extensively discussed over at the fgms project, and in the [[Distributed Interactive Simulation]] article.

The [https://gitorious.org/fg/flightgear/trees/next/utils/fgai fgai proof-of-concept], is just a brief sketch chat could be done in that corner. It already contains most if what is needed in complex infrastructure. You can inject vehicles and you can now get ground queries. I am for a long time running here also a brief python script which does about the same than [https://gitorious.org/fg/flightgear/trees/next/utils/fgai fgai]. While a scripting language is not fast enough to drive a lot of ai traffic, it is rather nice to do only a few such objects without much worries.

The basic idea to have an external component that drives ai traffic, or at least a thread that does the same is a good one I think. For the long term I do not care about the multiplayer protocol since it has severe limitations that would require a very similar solution that one the OpenRTI implementation does. For the short term, I am not sure if we are already at the point where I can just switch over. Therefore this bridge component bridging the mp protocol with hla. For the ADS-B traffic, packing this into a module that you can attach to your simulation instead of an artificial traffic component is an nice addition. Having

Whatever happens here, if you are really driving a lot of ai models it requires a huge amount of thoughts to get that scalable. Updates to specific
models as well as specific parts of those need to be updated in an sparse and intelligent way to make this somehow work. This includes the basic part of the [https://gitorious.org/fg/flightgear/trees/next/utils/fgai fgai] implementation which aims to have steady and differentiable movements. This is at this time not made use of so much, but the classes that I called something like *Physics* in there are mostly there to make sure that all components can see and even extrapolate the same steady movements than the originating component does. There is also infrastructure there to play some tricks with timing so that nobody needs to wait for ai traffic updates to arrive - they should just already be there.

There is also a small gatweay application translating between the old multiplayer and hla that might go into the utils directory past the next
release.

== Standalone Viewers ==
Or take the viewers (also see [[FGViewer]]), if you just exchange data by a shared memory segment, you are limited to a single machine. So that's nice for the 3-chanel thing you have. But I know of installs with 9 chanels I have been visiting some few time ago. They run flightgear on that beast by the way. Or I know of installs that currently run 14 or 16 chanels within a single view. For that reason I thought: better have a technology that is also extensible for this kind of installs instead of programming everything on top of something limited machine local.

== Standalone GUIs / Managers ==
In thinking about it a bit and being reminded of the existing HLA interface that FlightGear has, I'm leaning toward proposing something built with Python and the PyQT4 GUI library. Both components are cross-platform and there is a Python binding for the CERTI HLA library (PyHLA).

The idea here is to create a stand-alone application that replaces all the built-in GUI functionality and communicates with FlightGear via the HLA
interface. When the manager application meets that goal, the existing GUI can be either removed completely or simply "unbound" at compile time so
it's not available.

Such a gui manager application must be included somehow in the basic set of functionality that is still running in the threaded mode. You would just
control your simulation with that component. May be restart with a different aircraft by just shutting down the running federate and start up a new one
with a different fdm.
And as such, doing this core component in python is something I am not sure about.

So, python in the area of *optional* rti components, is a great tool. If I remember well, you do have some bigger install at home that might benefit
from such components very much! And in fact this is one reasons I am pushing this direction.

Python also has one major problem with threads. There is the big interpreter lock in python which makes python essentially single threaded. While this is
not a problem when such a component runs in its own process, python in core components that need to run in threaded mode is essentially a no go.

== Instructor Station ==
The management application wouldn't be running any of the sub-systems, just "observing" them. One of the issues that caught me up short was the requirement to sift through the chosen aircrafts configuration and Nasal files in order to take into account all the little custom menu items and controls that would have to be replicated on the manager interface. That was pretty discouraging all by itself.

My initial concept would essentially perform the same functions as the instructor console in a commercial FFS. You could tweak any parameter of the simulator from that point, including aircraft selection, position, configuration, etc. This app wouldn't be running on the same machine as the simulator & scene generator itself. (What would be neat is a three machine setup - one for the scene generator, one for the flight/systems model and one for the instructor/manager console.)

== FDM Server ==

[http://wiki.flightgear.org/flightgear_wiki/images/1/1e/New_FG_architecture.p We've toyed with the idea of an FDM server for a while], and there was even some work done on JSBSim towards making that happen. Recently, HDWysong has added the capability to use FlightGear as a visual front end for JSBSim as a separate, scripted application. It certainly would be a huge paradigm shift.

== Multiplayer ==
The author of fgms would be pretty much interrested to implement fgms as part of a HLA infrastructur. What detained me from going that way is, that I found no free (as is free beer) documentation on HLA specifications and the quite complex structure (too complex for a one-man-show). Additionaly I'm not sure about license issues involed. Are we allowed to publish all parts of (our) HLA infrastructur under the GPL (which will kind of undermine cash-flow of documentation providers like the IEEE)?

Regarding the multiplayer in FlightGear I see two options: 1) Either to implement a FlightGear proprietary protocol for multiplayer with a
gateway to HLA, or 2) to actually use native HLA as a multiplayer protocol.

The solution 1) means a new protocol and a new server (updated fgms) needs to be implemented, but the implementation requires no IEEE standards and the
solution doesn't depend on a 3rd party framework.The solution 2) doesn't require any new protocol nor HLA gateway to be implemented (HLA RTI will be used instead of fgms), but introduces an additional dependency on a 3rd party software.

I see no point in implementing our own protocol and an additional gateway, when we can directly use HLA. As long as we can implement and redistribute the federate code under GPL (or compliant license) we can make flightgear act as a HLA federate and use an open-source RTI (instead of fgms).

I also consider an RTI a possible multiplayer replacement. Even if we would handle local RTI federations different than internet wide stuff. But yes, an RTI provides almost all we would need to get that right.

I have thought about the use cases and needs for communication that I can see. I came to the conclusion that the RTI abstracts away the communication stuff in a way that is highly matching exactly the needs of a distributed simulation. Where distributed is just the same if it's distributed across processes, threads or machines. That's the reason I did prepare the groundwork by starting that own project with OpenRTI. So this project is purely driven by distributing flightgear across more computation power.

What will come in the shorter term is a standalone viewer (see [[FGViewer]] that can sit on any of the configured views. There are beginnings of that checked in but there is a lot more in preparation.

= OpenRTI =
Source: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg32973.html

The RTI implementation from www.certi.org was used most of the time during development.
While this one works somehow, it is sometimes difficult to handle and relatively slow.

Meanwhile, this has been replaced almost entirely with [https://gitorious.org/openrti/openrti OpenRTI], a new RTI from https://gitorious.org/openrti/openrti that is way easier to set up and use and that provides way more features we might make use of with flightgear.

OpenRTI provides one mode where you can just access a process local federation from multiple threads. There is no network configuration needed and you do not setup any server in this operation mode (sure it also provides the usual networking mode). So the plan is to use this mode as an aid to paralellize flightgear on a local machine. The basic advantage is that each federate is strictly programmed single threaded. All the thread syncronization is handled by the rti library and hidden in that thing. The trick is that each of these threads must be done in a way that you can just compile that alternatively in a single standalone binary and run the same component in a networked rti - the LinuxTag booth for example.

= Testing =
What do you need:
* Latest simgear and flightgear as well as the data package.
* An RTI-1.3 implementation (such as [[OpenRTI]])

libHLA is part of simgear (see simgear/hla). To build flightgear with "-D ENABLE_RTI=ON", you'll first need to build simgear with "-D ENABLE_RTI=ON". Before building SG and FG, you should build and install OpenRTI.

So, the implementation in flightgear does not make any assumptions about some internal features of the RTI implementation, except the way the rti is configured to connect to its federation server. That means,
that you can use any RTI implementation you like, if you care for the apropriate connection setup. But for the default setup that we might choose, I intent to provide a configuration that makes use of some
properties of OpenRTI. So in theory, you should not need to know anything about that, until you make sophisticated use of these features.

Start flightgear with '''--hla=bi,<hz>,<federateType>,<federationName>,<profile>",''' where <hz> is the communication frequency, <federateType> is the name of your federate - note that this must be unique with certi - and <federationName> is the federation you want to join. The <profile> argument defaults to the top level configuration file mp-aircraft.xml, which defines some flightgear adapted RTI/HLA federation definition. But there is already an alternate av-
aircraft.xml top level configuration file that should enable flightgear being used in an AviationSim federation that is the c++ hardcoded federation type of the other flightgear hla implementation out there.

You still can use the the --hla= commands, but there is a shortcut --hla-local which optimizes away a lot of successive ,,, in the command line that I
usually had. So, --hla-local=rti://localhost/FlightGear is a shortcut for a longer --hla= line.

= Additional info =
Just search the archives (list/forum) for "HLA" or "RTI":

* http://www.mail-archive.com/search?q=hla&l=flightgear-devel%40lists.sourceforge.net
* http://flightgear.org/forums/search.php?st=0&sk=t&sd=d&sr=posts&keywords=hla
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39181.html

= Related =
* http://wiki.flightgear.org/images/1/1e/New_FG_architecture.pdf
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16023.html
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37646.html
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37647.html
* http://virtualair.sourceforge.net/flightgear.html
* http://www.chromium.org/developers/design-documents/multi-process-architecture
* http://blog.chromium.org/2008/09/multi-process-architecture.html
* http://news.softpedia.com/news/Multi-Processes-in-Browsers-Chrome-Internet-Explorer-Firefox-and-WebKit-140535.shtml
* http://blog.mozilla.org/products/2011/07/15/goals-for-multi-process-firefox/

[[Category:HLA]]
[[Category:Core development projects]]

List of developed airports

2013-05-02T09:42:05Z

Popolon: /* Airports */ +coords LFMA + LFOH + LFLR + LFES

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

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

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

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

== Airports ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=9.70741&lat=45.66952&zoom=14&layers=B000000TFFFFTFFFTTFFF LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully 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=113.9183&lat=22.308&zoom=14&layers=B000000TFFFFTFFFTTFFF VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

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

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

|}

{{Suggested}}

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

List of developed airports

2013-05-02T09:33:05Z

Popolon: /* Airports */ +LFMA (Aérodrome d'Aix - Les Milles)

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

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

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

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

== Airports ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|-
| LFES || Guiscriff Scaër || France || Europe ||

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

|-
| LFLR || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| LFMA || Aérodrome d'Aix - Les Milles || France || Europe || Fully modeled, high resolution textures

|-
| LFOH || Le Havre Octeville Airport || 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.41785&lat=48.44413&zoom=12&layers=B00000000000FTFFTFFTFFFTFFFF LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

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

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

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

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

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

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=9.70741&lat=45.66952&zoom=14&layers=B000000TFFFFTFFFTTFFF LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully 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=113.9183&lat=22.308&zoom=14&layers=B000000TFFFFTFFFTTFFF VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

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

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

|}

{{Suggested}}

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

Fr/FlightGear Launch Control

2013-04-25T08:10:27Z

Popolon:

{{Infobox Software
| title = FlightGear Launch Control
| image = Fgrun-page2.jpg
| alt = The second (aircraft selection) page of FGRun.
| developedby = Bernie Bright, Frederic Bouvier
| initialrelease = 0.3.2 (24 octobre 2003)
| latestrelease = 1.6.2 (2 septembre 2012)
| writtenin = C++
| os = All 32-bit MS Windows (95/98/NT/2000/XP) All POSIX (Linux/BSD/UNIX-like)
| developmentstatus = Actif (2002-)
| license = [[GNU General Public License]]
| website = http://sourceforge.net/projects/fgrun
}}
'''FlightGear Launch Control''' ('''FGRun''') est une interface graphique pour [[FlightGear]], distribué et mis au point séparément sur [http://sourceforge.net/projects/fgrun|SourceForge]. Toutefois, il a été inclus dans les binaires distribués officiellement pour FlightGear, même si elle n'est pas techniquement une partie du programme de FlightGear, comme plusieurs autres interfaces (voir aussi [[FlightGear related projects|projets connexes de FlightGear]]). FGRun permet de choisir des options plus facilement qu'avec la [[Command Line Parameters|ligne de commande]].

L'application comporte deux parties principales :
* Un assistant pour choisir les options communes
* Une section avancée où toutes les options sont disponibles pour les utilisateurs expérimentés.

Les options choisies sont automatiquement enregistrées dans un fichier et sont réutilisées au prochain lancement de FGRun.

Pour plus d'informations sur la compilation de ce logiciel consultez [[Building FlightGear Launch Control]].

== L'assistant ==
L'assistant apparaît à l'utilisateur lorsque FGRun est lancé. La première fois, quand aucun chemin n'est définies, la première page est affichée, sinon, il saute directement à la deuxième page, mais le premier onglet est toujours accessible en appuyant sur le bouton "Précédent".

=== Barre de navigation ===
Le bas de l'assistant montre six boutons. De gauche à droite :
* '''Remise à Zéro''' : en cas de besoin, efface toutes les options et initialise les chemins comme définis lors de l'installation.
* '''Charger''' : charge des options préalablement sauvegardées.
* '''Sauver sous...''' : enregistre les options dans un fichier.
* '''Précédent''' : aller à la page précédente de l'assistant.
* '''Suivant''' : aller à la page suivante de l'assistant. Ce boutton est remplacé par un boutton '''Lancer''' sur la dernière page pour démarrer FlightGear.
* '''Quitter''' : termine l'assistant (et termine [[:fr:TerraSync|terrasync]] s'il a été lancé par fgrun).

=== Première page - Les chemins ===
[[File:fgrun-page1.jpg|thumb]]
Dans la première page, les chemins nécessaires à FGRun sont rappelés et peuvent être définis. Si FGRun a été installé avec un paquet binaire, soit sous Windows ou Linux, ces chemins sont normalement initialisés par la procédure d'installation.

La zone 'exécutable' est le chemin complet du programme FlightGear. On peut le choisir directement en utilisant la boîte de dialogue de sélection de fichier qui apparaît lorsqu'on pousse le bouton de dossier.

Le répertoire '[[$FG ROOT|FG_ROOT]]' est le chemin complet vers l'installation d'origine de FlightGear (répertoire de données). Si ce chemin est mauvais, aucun [[Aircraft|avion]] ne sera affiché et FlightGear ne fonctionnera pas.

La liste de répertoires '[[FG SCENERY]]' est la liste des répertoires contenant des [[scenery|décors]]. Ces dossiers ont généralement un sous répertoire 'Terrain', et facultativement un sous répertoire 'Objects'. On ajoute un nouveau chemin avec le bouton 'Ajouter ...'. La priorité parmi les répertoires sont gérés avec les flèches haut et bas.

Le champ 'Fichier cache des aéroports' montre l'emplacement du fichier qui stocke les identifiants [[:Category:Airports|d'aéroports]] trouvés dans les décors. Il est plus rapide d'accéder à ce fichier que de scanner les répertoires paysages pour construire la liste des aéroports. Il est possible de supprimer ce fichier si les choses tournent mal. Cela va forcer un nouveau scan lorsque la troisième page sera affichée.

: '''Astuce'''
:Si les choses tournent mal et FlightGear ne peut plus démarrer et que vous voulez recommencer à zéro avec une installation simplifiée, supprimer ou renommer le fichier nommé 'fgrun.prefs' situé dans le répertoire parent du fichier de cache d'aéroports. Vous devrez entrer de nouveaux chemins d'accès à la main, mais les options erronées que vous auriez pu saisir seront supprimés.

=== Page deux - Choisir un aèronef ===
[[File:fgrun-page2.jpg|thumb]]
La deuxième page, le plus souvent la première page vue par les utilisateurs lors du démarrage de fgrun, est la page de sélection des avions. Il montre la liste des aéronefs présents dans <tt>[[$FG ROOT]]/Aircraft</tt> et le modèle de l'avion sélectionné.

=== Page trois - Choisi une position ===
[[File:fgrun-page3.jpg|thumb]]
La troisième page est la page de sélection de l'aéroport et de la piste. Il ne montre que le contenu du fichier de cache des aéroports (voir Page un), qui devrait être le reflet du contenu des dossiers des paysages. Si un nouveau paysage a été installé et n'apparaît pas, ou si un vieux décor a été supprimé et que son aéroport est encore là, cliquez sur le bouton "Rafraichîr" pour réanalyser les répertoires paysages. Le scan se produit au premier lancement de fgrun ou lorsque le cache Aéroport a été supprimé.

La liste de l'aéroport ne semble pas apparaître (ou pire il disparaît) lorsque le bouton de rafraîchissement est pressé. Reconstruiser cette liste en copiant le fichier <tt>[[$FG ROOT]]/Aircraft/metar.dat.gz</tt> sur le fichier airports de fgrun :

zcat /usr/share/FlightGear/Airports/metar.dat.gz > \${HOME}/.fltk/flightgear.org/fgrun/airports.txt

=== Page quatre - Options et lancement ===
[[File:fgrun-page4.jpg|thumb]]
La dernière page affiche les options courantes qui ne nécessitent pas de passer à la section avancée.

:'''Astuce'''
: Habituellement, de nouveaux utilisateurs de FlightGear devraient s'en tenir là et essayer une vol simple avant d'aller à la section avancée. De cette façon, il sera plus facile de diagnostiquer le problème si, par accident, FlightGear ne pourrait pas se lancer ou fonctionner correctement. Souvent, les problèmes viennent des options incohérentes choisies, et il n'y a pas de garde-fou contre cela. Si FG ne s'exécute quand même, il sera temps de regarder la configuration matérielle.

La ligne de commande est utile aux personnes désireuses de diagnostiquer un problème.

Le bouton 'Lancer' démarre FlightGear avec les options indiquées dans la boîte de ligne de commande

== Options avancées ==
La boîte de dialogue des options avancées peut être ouvert en cliquant avec le bouton 'Avancé...' sur la dernière (quatrième) la page du lanceur.

=== Général ===
[[File:fgrun-wiki-a01.jpg|thumb|Général]]
* '''FG_SCENERY :''' Liste des répertoires contenant les [[scenery|paysages]]
* '''Contrôle :''' Quel commande utilisez-vous (voir aussi [[Joystick]]) ?
* '''Aéroport :''' Votre aéroport de départ.
* '''Piste :''' Piste de départ sur l'aéroport de départ.
* '''Aéronef :''' Votre [[aircraft|avion]].
* '''Langue :''' La langue utilisée par FlightGear.

=== Caractéristiques ===
[[File:fgrun-wiki-a02.jpg|thumb|Caractéristiques]]
* '''Mode de jeu :''' Pour se mettre en plein écran.
* '''Objets aléatoires :''' active les éléments de [[scenery|décors]] aléatoires.
* '''Son :''' Active les effets sonores comme le bruit des moteurs.
* '''Affichage Tête Haute :''' active l'affichage tête haute [[HUD]].
* '''Trafic d'IA :''' Active le [[AI traffic|trafic d'IA]].

=== Modèle de vol ===
[[File:fgrun-wiki-a03.jpg|thumb|Modèle de vol]]

=== Pause ===
[[File:fgrun-wiki-a04.jpg|thumb|Pause]]
* '''Pause :''' Lance le simulateur en mode pause.

=== Position initiale ===
[[File:fgrun-wiki-a05.jpg|thumb|Position initiale]]
* '''Longitude :''' Quelle est votre longitude ?
* '''Latitude :''' Quelle est votre latitude ?
* '''Altitude :''' Quelle est votre altitude ?
* '''Cap :''' La direction de l'appareil (degrés magnétiques).
* '''Vitesse :''' La vitesse de l'appareil en [http://fr.wikipedia.org/wiki/N%C5%93ud_(unit%C3%A9)]noeuds.

=== Rendu graphique ===
[[File:fgrun-wiki-a06.jpg|thumb|Rendu graphique]]
* '''Nuages :''' Y at-il des nuages dans l'air ?
* '''Nuages 3D :''' Les nuages sont-ils dessinés en 3D ?
* '''Plein écran :''' Voulez-vous jouer en plein écran ?
* '''Fil de fer :''' Voulez vos un rendu en fil de fer pour les [[scenery|décors]] et votre [[aircraft|avion]] ?
* '''Visibilité :''' La distance visible en mètres ou miles.
* '''Bpp :''' Le nombre de bits par pixel pour afficher les couleurs.
* '''Angle de vue :''' L'ouverture angulaire de la caméra en degrés.
* '''Fichier des matières :''' Le fichier XML des matériaux à utiliser (materials.xml par défaut, peut être modifié par materials-dds.xml pour utiliser les textures DDS).

=== Heure ===
[[File:fgrun-wiki-a07.jpg|thumb|Heure]]
* '''Heure locale :''' Synchronisize l'heure de simulation avec l'heure locale.
* '''Heure réelle :''' Quelle heure est-il ?

=== Réseau ===
[[File:fgrun-wiki-a08.jpg|thumb|Réseau]]
* '''Indicatif :''' Votre indicatif (callsign) sur le réseau. Il est utilisé pour reconnaître les autres pilotes et pour le suivi de vos vols.

'''voir :''' [[:fr:Howto:_Multijoueur|Multiplayer Howto]]

=== Entrée/Sortie ===
[[File:fgrun-wiki-a09.jpg|thumb|Entrée/Sortie]]

=== Avionique ===
[[File:fgrun-wiki-a10.jpg|thumb|Avionique]]

=== Propriétés ===
[[File:fgrun-wiki-a11.jpg|thumb|Propriétés]]
Ici vous pouvez modifier ou ajouter de nouvelles [[Property|propriétés]]. C'est comme ajouter <tt>--prop:...</tt> sur [[Command Line Parameters|la ligne de commande]].

=== Deboguage ===
[[File:fgrun-wiki-a12.jpg|thumb|Deboguage]]
* '''Niveau de messages :''' De 'alerte' ou ne s'affiche que les erreurs graves à 'tout-venant' qui va tracer toute l'activité de Flightgear (et qui va ralentir l'exécution du programme).
* '''Tracer les propriétés lues :'''
* '''Tracer les propriétés écrites :'''
=== Environnement ===
[[File:fgrun-wiki-a13.jpg|thumb|Environnement]]

=== Météo ===
[[File:fgrun-wiki-a14.jpg|thumb|Météo]]
* '''Direction du vent :''' Direction du vent.
* '''Cap :''' Direction de laquelle vient le vent.
* '''Vitesse :''' Vitesse du vent en noeuds (kts).
* '''Météo réelle :''' Utilise les information de météo réelle [[METAR#METAR|METAR]].

=== Nuages ===
[[File:fgrun-wiki-a15.jpg|thumb|Nuages]]
* '''Altitude :''' A quelle hauteur (en pieds) se trouvent les nuages ?
* '''Epaisseur :''' Quelle est l'epaisseur (en pieds) de la couche de nuages ?

== Contenu connexe ==
* [[FGo!]], un lanceur avec une interface graphique simple pour FlightGear écrit en Python
* [[JFlightWizard]], une autre interface graphique
* [[FlightGear related projects]] différents projets relatifs à FlightGear

[[de:FlightGear Launch Control]]
[[en:FlightGear Launch Control]]

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

Fr/FlightGear Launch Control

2013-04-25T08:08:15Z

Popolon: /* Contenu connexe */ +lien FlightGear related projects

{{Infobox Software
| title = FlightGear Launch Control
| image = Fgrun-page2.jpg
| alt = The second (aircraft selection) page of FGRun.
| developedby = Bernie Bright, Frederic Bouvier
| initialrelease = 0.3.2 (October 24, 2003)
| latestrelease = 1.5.2 (February 6, 2010)
| writtenin = C++
| os = All 32-bit MS Windows (95/98/NT/2000/XP) All POSIX (Linux/BSD/UNIX-like)
| developmentstatus = Active (2002-)
| license = [[GNU General Public License]]
| website = http://sourceforge.net/projects/fgrun
}}
'''FlightGear Launch Control''' ('''FGRun''') est une interface graphique pour [[FlightGear]], distribué et mis au point séparément sur [http://sourceforge.net/projects/fgrun|SourceForge]. Toutefois, il a été inclus dans les binaires distribués officiellement pour FlightGear, même si elle n'est pas techniquement une partie du programme de FlightGear, comme plusieurs autres interfaces (voir aussi [[FlightGear related projects|projets connexes de FlightGear]]). FGRun permet de choisir des options plus facilement qu'avec la [[Command Line Parameters|ligne de commande]].

L'application comporte deux parties principales :
* Un assistant pour choisir les options communes
* Une section avancée où toutes les options sont disponibles pour les utilisateurs expérimentés.

Les options choisies sont automatiquement enregistrées dans un fichier et sont réutilisées au prochain lancement de FGRun.

Pour plus d'informations sur la compilation de ce logiciel consultez [[Building FlightGear Launch Control]].

== L'assistant ==
L'assistant apparaît à l'utilisateur lorsque FGRun est lancé. La première fois, quand aucun chemin n'est définies, la première page est affichée, sinon, il saute directement à la deuxième page, mais le premier onglet est toujours accessible en appuyant sur le bouton "Précédent".

=== Barre de navigation ===
Le bas de l'assistant montre six boutons. De gauche à droite :
* '''Remise à Zéro''' : en cas de besoin, efface toutes les options et initialise les chemins comme définis lors de l'installation.
* '''Charger''' : charge des options préalablement sauvegardées.
* '''Sauver sous...''' : enregistre les options dans un fichier.
* '''Précédent''' : aller à la page précédente de l'assistant.
* '''Suivant''' : aller à la page suivante de l'assistant. Ce boutton est remplacé par un boutton '''Lancer''' sur la dernière page pour démarrer FlightGear.
* '''Quitter''' : termine l'assistant (et termine [[:fr:TerraSync|terrasync]] s'il a été lancé par fgrun).

=== Première page - Les chemins ===
[[File:fgrun-page1.jpg|thumb]]
Dans la première page, les chemins nécessaires à FGRun sont rappelés et peuvent être définis. Si FGRun a été installé avec un paquet binaire, soit sous Windows ou Linux, ces chemins sont normalement initialisés par la procédure d'installation.

La zone 'exécutable' est le chemin complet du programme FlightGear. On peut le choisir directement en utilisant la boîte de dialogue de sélection de fichier qui apparaît lorsqu'on pousse le bouton de dossier.

Le répertoire '[[$FG ROOT|FG_ROOT]]' est le chemin complet vers l'installation d'origine de FlightGear (répertoire de données). Si ce chemin est mauvais, aucun [[Aircraft|avion]] ne sera affiché et FlightGear ne fonctionnera pas.

La liste de répertoires '[[FG SCENERY]]' est la liste des répertoires contenant des [[scenery|décors]]. Ces dossiers ont généralement un sous répertoire 'Terrain', et facultativement un sous répertoire 'Objects'. On ajoute un nouveau chemin avec le bouton 'Ajouter ...'. La priorité parmi les répertoires sont gérés avec les flèches haut et bas.

Le champ 'Fichier cache des aéroports' montre l'emplacement du fichier qui stocke les identifiants [[:Category:Airports|d'aéroports]] trouvés dans les décors. Il est plus rapide d'accéder à ce fichier que de scanner les répertoires paysages pour construire la liste des aéroports. Il est possible de supprimer ce fichier si les choses tournent mal. Cela va forcer un nouveau scan lorsque la troisième page sera affichée.

: '''Astuce'''
:Si les choses tournent mal et FlightGear ne peut plus démarrer et que vous voulez recommencer à zéro avec une installation simplifiée, supprimer ou renommer le fichier nommé 'fgrun.prefs' situé dans le répertoire parent du fichier de cache d'aéroports. Vous devrez entrer de nouveaux chemins d'accès à la main, mais les options erronées que vous auriez pu saisir seront supprimés.

=== Page deux - Choisir un aèronef ===
[[File:fgrun-page2.jpg|thumb]]
La deuxième page, le plus souvent la première page vue par les utilisateurs lors du démarrage de fgrun, est la page de sélection des avions. Il montre la liste des aéronefs présents dans <tt>[[$FG ROOT]]/Aircraft</tt> et le modèle de l'avion sélectionné.

=== Page trois - Choisi une position ===
[[File:fgrun-page3.jpg|thumb]]
La troisième page est la page de sélection de l'aéroport et de la piste. Il ne montre que le contenu du fichier de cache des aéroports (voir Page un), qui devrait être le reflet du contenu des dossiers des paysages. Si un nouveau paysage a été installé et n'apparaît pas, ou si un vieux décor a été supprimé et que son aéroport est encore là, cliquez sur le bouton "Rafraichîr" pour réanalyser les répertoires paysages. Le scan se produit au premier lancement de fgrun ou lorsque le cache Aéroport a été supprimé.

La liste de l'aéroport ne semble pas apparaître (ou pire il disparaît) lorsque le bouton de rafraîchissement est pressé. Reconstruiser cette liste en copiant le fichier <tt>[[$FG ROOT]]/Aircraft/metar.dat.gz</tt> sur le fichier airports de fgrun :

zcat /usr/share/FlightGear/Airports/metar.dat.gz > \${HOME}/.fltk/flightgear.org/fgrun/airports.txt

=== Page quatre - Options et lancement ===
[[File:fgrun-page4.jpg|thumb]]
La dernière page affiche les options courantes qui ne nécessitent pas de passer à la section avancée.

:'''Astuce'''
: Habituellement, de nouveaux utilisateurs de FlightGear devraient s'en tenir là et essayer une vol simple avant d'aller à la section avancée. De cette façon, il sera plus facile de diagnostiquer le problème si, par accident, FlightGear ne pourrait pas se lancer ou fonctionner correctement. Souvent, les problèmes viennent des options incohérentes choisies, et il n'y a pas de garde-fou contre cela. Si FG ne s'exécute quand même, il sera temps de regarder la configuration matérielle.

La ligne de commande est utile aux personnes désireuses de diagnostiquer un problème.

Le bouton 'Lancer' démarre FlightGear avec les options indiquées dans la boîte de ligne de commande

== Options avancées ==
La boîte de dialogue des options avancées peut être ouvert en cliquant avec le bouton 'Avancé...' sur la dernière (quatrième) la page du lanceur.

=== Général ===
[[File:fgrun-wiki-a01.jpg|thumb|Général]]
* '''FG_SCENERY :''' Liste des répertoires contenant les [[scenery|paysages]]
* '''Contrôle :''' Quel commande utilisez-vous (voir aussi [[Joystick]]) ?
* '''Aéroport :''' Votre aéroport de départ.
* '''Piste :''' Piste de départ sur l'aéroport de départ.
* '''Aéronef :''' Votre [[aircraft|avion]].
* '''Langue :''' La langue utilisée par FlightGear.

=== Caractéristiques ===
[[File:fgrun-wiki-a02.jpg|thumb|Caractéristiques]]
* '''Mode de jeu :''' Pour se mettre en plein écran.
* '''Objets aléatoires :''' active les éléments de [[scenery|décors]] aléatoires.
* '''Son :''' Active les effets sonores comme le bruit des moteurs.
* '''Affichage Tête Haute :''' active l'affichage tête haute [[HUD]].
* '''Trafic d'IA :''' Active le [[AI traffic|trafic d'IA]].

=== Modèle de vol ===
[[File:fgrun-wiki-a03.jpg|thumb|Modèle de vol]]

=== Pause ===
[[File:fgrun-wiki-a04.jpg|thumb|Pause]]
* '''Pause :''' Lance le simulateur en mode pause.

=== Position initiale ===
[[File:fgrun-wiki-a05.jpg|thumb|Position initiale]]
* '''Longitude :''' Quelle est votre longitude ?
* '''Latitude :''' Quelle est votre latitude ?
* '''Altitude :''' Quelle est votre altitude ?
* '''Cap :''' La direction de l'appareil (degrés magnétiques).
* '''Vitesse :''' La vitesse de l'appareil en [http://fr.wikipedia.org/wiki/N%C5%93ud_(unit%C3%A9)]noeuds.

=== Rendu graphique ===
[[File:fgrun-wiki-a06.jpg|thumb|Rendu graphique]]
* '''Nuages :''' Y at-il des nuages dans l'air ?
* '''Nuages 3D :''' Les nuages sont-ils dessinés en 3D ?
* '''Plein écran :''' Voulez-vous jouer en plein écran ?
* '''Fil de fer :''' Voulez vos un rendu en fil de fer pour les [[scenery|décors]] et votre [[aircraft|avion]] ?
* '''Visibilité :''' La distance visible en mètres ou miles.
* '''Bpp :''' Le nombre de bits par pixel pour afficher les couleurs.
* '''Angle de vue :''' L'ouverture angulaire de la caméra en degrés.
* '''Fichier des matières :''' Le fichier XML des matériaux à utiliser (materials.xml par défaut, peut être modifié par materials-dds.xml pour utiliser les textures DDS).

=== Heure ===
[[File:fgrun-wiki-a07.jpg|thumb|Heure]]
* '''Heure locale :''' Synchronisize l'heure de simulation avec l'heure locale.
* '''Heure réelle :''' Quelle heure est-il ?

=== Réseau ===
[[File:fgrun-wiki-a08.jpg|thumb|Réseau]]
* '''Indicatif :''' Votre indicatif (callsign) sur le réseau. Il est utilisé pour reconnaître les autres pilotes et pour le suivi de vos vols.

'''voir :''' [[:fr:Howto:_Multijoueur|Multiplayer Howto]]

=== Entrée/Sortie ===
[[File:fgrun-wiki-a09.jpg|thumb|Entrée/Sortie]]

=== Avionique ===
[[File:fgrun-wiki-a10.jpg|thumb|Avionique]]

=== Propriétés ===
[[File:fgrun-wiki-a11.jpg|thumb|Propriétés]]
Ici vous pouvez modifier ou ajouter de nouvelles [[Property|propriétés]]. C'est comme ajouter <tt>--prop:...</tt> sur [[Command Line Parameters|la ligne de commande]].

=== Deboguage ===
[[File:fgrun-wiki-a12.jpg|thumb|Deboguage]]
* '''Niveau de messages :''' De 'alerte' ou ne s'affiche que les erreurs graves à 'tout-venant' qui va tracer toute l'activité de Flightgear (et qui va ralentir l'exécution du programme).
* '''Tracer les propriétés lues :'''
* '''Tracer les propriétés écrites :'''
=== Environnement ===
[[File:fgrun-wiki-a13.jpg|thumb|Environnement]]

=== Météo ===
[[File:fgrun-wiki-a14.jpg|thumb|Météo]]
* '''Direction du vent :''' Direction du vent.
* '''Cap :''' Direction de laquelle vient le vent.
* '''Vitesse :''' Vitesse du vent en noeuds (kts).
* '''Météo réelle :''' Utilise les information de météo réelle [[METAR#METAR|METAR]].

=== Nuages ===
[[File:fgrun-wiki-a15.jpg|thumb|Nuages]]
* '''Altitude :''' A quelle hauteur (en pieds) se trouvent les nuages ?
* '''Epaisseur :''' Quelle est l'epaisseur (en pieds) de la couche de nuages ?

== Contenu connexe ==
* [[FGo!]], un lanceur avec une interface graphique simple pour FlightGear écrit en Python
* [[JFlightWizard]], une autre interface graphique
* [[FlightGear related projects]] différents projets relatifs à FlightGear

[[de:FlightGear Launch Control]]
[[en:FlightGear Launch Control]]

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

List of developed airports

2013-04-22T15:40:57Z

Popolon: /* Airports */ +Hong Kong International Airpot (VHHH)

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

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

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

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

== Airports ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|-
| [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=113.9183&lat=22.308&zoom=14&layers=B000000TFFFFTFFFTTFFF VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

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

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

|}

{{Suggested}}

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

Howto:Improve framerates

2013-04-01T16:10:06Z

Popolon: /* Texture compression */

Anything below about 15 frames per second (fps) is close to unusable, or at least, will not be enjoyable. In fact, you'll probably want to aim for 25-35 fps minimum, and a maximum frame spacing (latency) of ~50 ms.

Additionally, the more the framerate decreases, the more other features of the simulation will suffer. The current [[FlightGear]] software architecture is such that long rendering times (slow framerates) may prevent other parts of the flight simulator, such as the autopilot, from having sufficient CPU time to respond correctly in the context of the simulation.

FlightGear's framerate is influenced by various factors, including:

* [[scenery]] complexity (terrain, clouds, trees, particles, random 3D objects, multiplayer/AI traffic, animated jetways)
* [[cockpit]] complexity (2D vs. 3D)
* environmental options (eg. visibility, precipitation)
* [[FDM]] update interval
* AI scenarios
* [[aircraft]] speed (scenery paging)
* rendering options
* debugging level

You can disable most features that often adversely affect framerate. Here is a collection of settings that you may change to improve your framerate. Please note that some of these will only take effect if they're specified at startup and cannot be changed after the simulation has started.

If you are seeing FlightGear crashing, please see [[Howto:Debugging FlightGear Crashes]] (also take a look at this if you find that enabling certain features slows down the simulator considerably).
If you are experiencing system lockups, please see [[System Crashes]].

== Analyzing lag properly (frame spacing and worst case latency) ==

In FlightGear => 2.60, use the menu option Debug => Monitor System Performance to analyze stutters.

In a perfect world, min/max/mean values should be almost identical for every subsystem - and standard deviation should be almost 0. Larger differences / high standard deviations result in a sloppy simulation and stuttering movements, though they'll hardly influence the frames-per-second value at all.

Also, imagine a system producing 100 frames in 0.5 seconds, then blocking completely for another 0.5 seconds. The fps display would still show "100fps", which seems great. But the 0.5 second stutter cause the visual performance to be terrible. That's why I prefer to display "(worst-case) frame spacing" instead of fps (View => Display Options => Show frame spacing). The frame spacing for the previous example would show "500ms", while a system producing 100 frames with perfectly even spacing would show "10ms".

So, frame spacing is a much better property to judge visual quality than just watching fps.

For more info, please see [[Howto: Use the system monitor]].

== Hints for users ==
=== Shaders ===
As of FlightGear 2.0.0, a growing number of [[shaders]] is being implemented into FlightGear. While these do make your flights visually appealing, they tend to have quite an impact on most computers. Luckily you can easily disable shaders in the <tt>View > Rendering Options</tt> dialog. As of FlightGear 2.6.0 an advanced shader options dialog is available, in which you can adjust every single shader's setting. To disable the shaders on startup, run FlightGear with:
--prop:/sim/rendering/shaders/quality-level=0
Leave out the <code>--prop:</code> prefix when adding the command via <tt>Advanced > Properties</tt> on the last page of FGRun.

It requires some testing to find out what settings are best for your computer, but it's defenitely worth spending some time on!

Starting with FG >= 2.10, FlightGear releases will default to shader quality level 0 for these reasons.

=== Other windows/programs ===
Don't run FlightGear while also running another application, except if you need it. The two programs are competing for the CPU's proccessing power. As a basic rule, try to minimize the amount of programs open, so FlightGear can have the biggest portion of the CPU Times. Graphics-intensive programs also drain the GPU/graphics card, so you may be able to add a few frames.

=== AI traffic ===
[[Interactive Traffic|AI-traffic]] is computer controlled traffic, which includes traffic over the [[Howto: Multiplayer|MP network]]. By turning off this function you're not able to see other aircraft.

Most stuttering, or lag, in FlightGear is caused by AI traffic. Especially heavy models need quite some time to load, eg the [[Grumman F-14 Tomcat|F-14]] or the [[Rockwell B-1B Lancer|B-1B]]. Every time a new aircraft enters your local area, your computer has to load the model for that particular aircraft. The time required to read the data from the drive creates a stutter, or lag, which can range from a minor annoyance to a crash. The busier the place you fly, the more lag you'll get; eg flying around KSFO will generate more lag than a flight near EGLL, since there is more traffic near KSFO.

Turning off just the computer-generated aircraft (leaving the MP traffic visible), can be done by adding a command to your commandline:
--prop:/sim/traffic-manager/enabled=0
Or via [[FGRun]] through Advanced > Properties, add a new property with <tt>/sim/traffic-manager/enabled=0</tt>

=== Operating system specific ===
Many newer Linux distributions, like openSUSE 11.2, come with KDE4 as a desktop environment. While it allows some fancy desktop effects, it is known to consume enough computing power from the CPU and the graphics card to slow FlightGear down by 10 frames per second or even more. Choosing another window manager from the login screen, like xfce results in higher FlightGear performance. Setting "Compositing" to "off" in KDE4 might also help.

=== Debugging/log level ===
The more FlightGear has to write out to the log, the more framerates will be sacrificed. On normal usage, one is best of with the highest log level, which is ''alert''. In FGRun this can be set via <tt>Advanced > Debugging</tt>, on a commandline you'll use <tt>--log-level=alert</tt> (or simply remove an existing --log-level command, as alert is the default).

=== Optimus Technology ===
Most notebooks that run Windows 7 have the so called [http://www.nvidia.com/object/optimus_technology.html Optimus Technology] (NVidia) or Hybrid Graphics technology (ATI) onboard. This is meant to increase battery life, by automatically switching of the powerfull graphics card when it's not needed. However, FlightGear needs it all the time, even if Optimus says it doesn't! This miscommunication results in low framerates (because your computer will run Flightgear on the weak onboard processor) and often FlightGear will quit with the following error:
Unknown exception in the main loop. Aborting...
Possible cause: Not enough space

==== nVidia ====
To make use of the powerful graphics card, perform the following steps:
# Go to the NVidia control panel. Probably located in the Windows Control Panel.
# Open the 3D Settings tab. Now there's two options you can take:
#* On the "General settings tab", set "Prefered graphics processor" to NVidia. The NVidia card will now be used for all software. This can decrease battery life significantly.
#* On the "Programm settings" tab, locate <tt>fgfs.exe</tt> (eg. <tt>C:/Program Files/FlightGear/bin/win32/fgfs.exe</tt>) and assign the NVidia card to it. From now on the NVidia card will be used for FlightGear.

=== Texture compression ===
It is possible that texture compression is not handled correctly by the graphic card or the driver, causing stuttering (usually when turning left/right or when loading new tiles).
Compression can be disabled by adding
--prop:/sim/rendering/texture-compression=off
on the command line (or in FGRUN options). This is for nVidia and ATI cards [1]. And usefull for Intel integrated chips with MesaGL, that suffer from bugs with texture compression and fgfs.

== Hints for developers ==
=== 3D models ===
Contrary to what many people believe, the impact of high vertex-count models on framerate is fairly minimal. In addition, for graphics hardware built after 2004 and intended for games (example: Nvidia GeForce 6 series), textures are close to, or completely, free. Today (in 2010), the major graphics bottleneck is between the CPU and the GPU. The goal in optimizing models is to store as much as possible on the GPU and reduce the number of rendering commands sent to the GPU. For graphic artists, the key things to remember are:

* Reduce the number of different textures used on a model to a minimum. It's better to use a few (or one!) big textures than many little ones.
* Avoid mixing textured and untextured geometry in the same model. Build the coloring into the texture map instead.
* Within your modeling tool, try work with large meshes instead of groups of small meshes - but please don't mistake this as a request for grouping multiple, distinct buildings into a single AC3D file. I know that this can result in a very unpleasant workflow; we are working on optimizations in FlightGear that will combine mesh parts automatically.
* Textures containing alpha cause various problems. In order to be rendered correctly, translucent geometry must be sorted by distance on the CPU. Furthermore, geometry is sorted on a course level (basically by mesh), so you may see various artifacts. If you have some transparent parts of a model, you should violate the first rule above and assign those parts to their own texture.
* Don't assign an RGBA texture to a model that is completely opaque!

== Related content ==
* [[Settings for slower graphics cards]]

== External links ==
[http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_15286 Optimizing file size, performance and streaming of 3D content]

[1] http://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg56181.html

[[Category:Howto|Framerates Improve]]
[[Category:Performance_tuning]]

Ryan NYP

2013-03-04T22:34:54Z

Popolon: +fgname

{{infobox Aircraft
|image = Ryan-SoSL.jpg
|name = ''Spirit of St Louis'' Ryan NYP
|type = Long-range aircraft
|livery =
|fdm = YASim
|status = Alpha
|authors = Emmanuel Baranger (3D), Pierre Geoffroy (FDM), Laurent Hayvel (texture)
|fgname = ryan-sosl
|download = http://www.flightgear.org/Downloads/aircraft-2.0.0/#Ryan-SoSL
}}
The '''Spirit of St. Louis''' is the custom-built single engine, single seat monoplane that was flown solo by Charles Lindbergh on May 20–21, 1927, on the first non-stop flight from New York to Paris.

The SoSL is currently on display at the [[National Air and Space Museum]].

[[Category:High wing aircraft]]
[[Category:Propeller aircraft]]
[[Category:Single-engine aircraft]]
[[Category:Special-purpose aircraft]]

Ogel

2013-03-04T21:50:20Z

Popolon: +fgname

{{aero-stub}}

{{infobox Aircraft
|image = Ogel.jpg
|name = Ogel
|type = fantasy
|livery = yes
|fdm = JSBSim
|status-fdm = 5
|status-systems = 5
|status-cockpit = 5
|status-model = 5
|authors =Torsten Dreyer
|fgname = ogel
|download =
}}
ogeL experimental aircraft.
Make your kids happy.

[[Category:Fictional aircraft]]

British Aerospace Sea Harrier

2013-03-04T21:48:13Z

Popolon: +fgname

{{infobox Aircraft
|image =Harrier.jpg
|name =Sea Harrier FA2
|type =V/STOL Fighter Jet
|fdm =Yasim
|status=released
|authors =Andy Ross, Steve Havlir
|fgname = harrier
}}

== Development status/Issues/Todo ==
3d Cockpit To Do List:
* Add more instruments to panel
* Add seat

Features that would be nice, but I do not have time to do:
* working weapons

[[Category:Attack aircraft]]
[[Category:Carrier-based aircraft]]
[[Category:Experimental aircraft]]
[[Category:Fighter aircraft]]
[[Category:VTOL aircraft]]

Fr/Changelog 2.10

2013-02-22T13:43:50Z

Popolon: /* Principales avancées dans cette version */ typo

==Liste des changements de FlightGear 2.10==

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

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

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

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

FlightGear - Volez librement !

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

'''Modularité avancée'''

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

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

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

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

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

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

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

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

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

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

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

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

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

'''Système Canvas'''

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

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

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

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

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

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

''' Textures régionales '''

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

'''Mise en avant d'aéronefs nouveaux ou améliorés'''

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

'''Autres'''

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

'''Correction d'anomalies'''

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

[[Category:FlightGear changelogs]]

Manual Compilation on Ubuntu Linux

2012-10-06T23:28:48Z

Popolon: /* Obtaining and Building the Sources */ configure => cmake for simgear/flightgear +libglut.so problem on 64 bits platforms

{{WIP}}

== Disclaimer ==

'''''This is work in progress. Please do not follow this instructions yet and do not link to this page from more general instructions (see right below).'''''

I actually try out the instructions I write on fresh installs of all four relevant system. This takes some time.
Expect this page to be "released" within 2 or 3 weeks, that is by mid february 2010. I will then also link to it from other
relevant pages.

{{Main article|Building_FlightGear_-_Linux}}

This section describes how to build the current developer (git) version of FlightGear on an Ubuntu Linux System.

If you are not an Ubuntu user you will find more generic instructions on building Flightgear on Linux in [[Building FlightGear - Linux]].

As an Ubuntu user I also suggest you consider using the automated build script as described in [[Scripted Compilation on Linux Debian/Ubuntu]] before you start following this instructions.

== Introduction ==

'''Ubuntu binary packages'''

Ubuntu offers binary packages of FlightGear that can be installed from the Software Center in your main application menu. Unfortunatelly, these packages contain a rather obsolete
version of Flightgear. This instuctions describe how to obtain and compile the current developer version of FlightGear. Please remember that using the developer version has both advantages and disadvantages. While great new features are often present in this version months before they are incorporated into the next official release, some things might also occasionally be broken in the developer version. It might even happen every now and then that the sources you obtain from git might not compile at all and you will have to try again a couple of days later. If you are experiencing problems compiling or using the developer version please keep that in mind.

These instructions are tested on both the current release (10.10) and the last LTS release (10.4) of Ubuntu, both in their 64 bit and 32 bit incarnations. If you are still using an older version I suggest you consider [https://help.ubuntu.com/community/UpgradeNotes upgrading your system].

To be able to follow these Instructions you should have opened a Terminal before and you should have some very basic knowledge of the Linux ''command line''. It you know how to navigate between directories
and how to create a new subdirectory this should be enough.

== Requirements ==

''' Removal of Ubuntu package '''

In case you have installed the binary FlightGear packages provided by Ubuntu I suggest you remove them before moving on to your own compilation.
While it is theoretically no problem to have several versions of flightgear installed at different locations on your system if you know what you're doing, this often causes strange problems for beginners.
You can remove the Ubuntu packages using the Software Center, but I suggest to get you into the right mood for later you start using the command line now and enter:
<pre>
sudo apt-get remove flightgear simgear openscenegraph
</pre>

''' Installing the dependencies '''

<pre>
sudo apt-get update
sudo apt-get install git-core cvs build-essential cmake automake libboost-dev
sudo apt-get install libfreetype6-dev libpng-dev libjpeg-dev libtiff-dev libgif-dev libopenal-dev
sudo apt-get install libxml2-dev libcurl4-openssl-dev libx11-dev libgl1-mesa-dev
sudo apt-get install libalut-dev libplib-dev
</pre>

== Obtaining and Building the Sources ==

''' Creating a build directory '''

I suggest you create some folder off your home where you download the sources of FlightGear and its dependencies to.
<pre>
mkdir build
cd build
</pre>

''' Checking out the sources '''

Now obtain the sources of simgear and flightgear. You can skip over the first line, since we will use
openscenegraph from the ubuntu repository. The line is kept here for reference.
<pre>
git clone git://gitorious.org/openscenegraph/osg.git
git clone git://gitorious.org/fg/simgear.git
git clone git://gitorious.org/fg/flightgear.git
</pre>

The atlas sources are not hosted with git. The developers use cvs instead.
The cvs login command will ask you for a password. Just press enter (empty password) to go on.
<pre>
cvs -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas login
cvs -z3 -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas co Atlas
</pre>

If you are not suffering from lack of harddisk space you do not have to remove the source folders after you are
done installing everything. If you keep the source folders you can save a lot of time and bandwidth next time you
want to update your installation of FlightGear. To upgrade the state of the source directories to the most recent,
enter each of the 3 git source folders and type "git pull". Only changes since the last time you cloned or upgraded
will be fetched from the server. For the atlas entering "cvs co" from within the source directory will
accompish the same.

''' Creating a directory for the installed components '''

You can install FlightGear and all the dependencies that you have compiled yourself into a common subfolder of /opt.
This makes it easier to remove everything flightgear related later by just deleting that single folder. If you
want to do this, create that directory now:
<pre>
sudo -p mkdir /opt/flightgear
</pre>

''' Building OpenSceneGraph '''

As of February 2011 simgear can not be built against the latest git version of openscenegraph. You should
use ubuntu's version of openscenegraph instead:
<pre>
sudo apt-get install libopenscenegraph-dev
</pre>

Now skip ahead over the OSG build instructions to building the other packages :)

The build process of OSG is somewhat different from all the other packages. You should not build OSG in the source
directory that you obtained but you should make a separate build directory right next to the sources:
<pre>
mkdir osg_build
cd osg_build
cmake -D CMAKE_BUILD_TYPE="Release" -D CMAKE_CXX_FLAGS="-O3 -march=native" CMAKE_C_FLAGS="-O3 -march=native" \
-D CMAKE_INSTALL_PREFIX:PATH="/usr" ../osg
make -j2
sudo make install
cd ..
</pre>

The '''''-j2''''' option tells make to use two independend threads for compilation,
thus speeding up the build process on multi-core systems. If you have a quad-core CPU,
you might want to use '''''-j4''''' instead, to utilize all four cores.

''' Building the other packages '''

For the other three packages the build process is basically the standard build
process of most any unix software when building from a developer tree.

The '''''-j2''''' option that is given to make below tells it to use two independend threads
for compilation, thus speeding up the build process on multi-core systems. If you have a
quad-core CPU, you might want to use '''''-j4''''' instead, to utilize all four cores.

Build simgear, flightgear and atlas in this order:

<pre>
cd simgear
sudo cmake -D CMAKE_INSTALL_PREFIX=/usr .
make -j2
sudo make install
cd ..
</pre>

<pre>
cd flightgear
sudo cmake -D CMAKE_INSTALL_PREFIX=/usr .
make -j2
sudo make install
cd ..
</pre>

On 64 bits OS you could have compilation problems with libglut.so at make time, in this case type in the flightgear source dir :

sed -i 's/libglut.so/x86_64-linux-gnu\/libglut.so/' utils/fgpanel/CMakeFiles/fgpanel.dir/build.make

and restart

<pre>
make -j2
sudo make install
cd ..
</pre>

Should works fine.

<pre>
cd atlas
./autogen.sh
./configure --prefix=/opt/flightgear
make -j2
sudo make install
cd ..
</pre>

In the end you might want to create symlinks ("shortcuts") of the installed executables
to /usr/bin for easier terminal work :)

<pre>
sudo ln -s /opt/flightgear/bin/* /usr/bin/
</pre>

== Obtaining the Data Folder ==

I suggest you put the FlightGear data folder to /usr/share/flightgear, since this is the place where FlightGear looks for it by default with no $FG_ROOT environment variable set.

'''Obtaining fgdata for the first time'''

If you want to obtain the data folder for the first time you have to clone the current state of the git repository to your local computer. Open a new terminal and enter
<pre>
cd /usr/share
sudo git clone git://mapserver.flightgear.org/fgdata/ flightgear
</pre>
Please be patient, this can take a '''''long''''' time.

'''Updating your local copy of fgdata that you obtained earlier'''

If you already have a local copy of the data directory that you got from the git repository in the way described above (this will not work with data directories downloaded any other way), you shoud not
download the whole 4 or 5 GB again! This costs you a lot of time and the FlightGear server a lot of bandwidth! Instead you simply upgrade your local copy. To do this, open a new terminal and enter
<pre>
cd /usr/share/flightgear
sudo git pull
</pre>
Depending on how much changed on the server since you last obtained or updated your local copy this can be finished really quickly or it could take quite some time.

Be aware that, without some additional precautions, the update might fail if you changed any file in your local copy of the data folder since your last upgrade. If you are not helping to develop FlightGear you should therefor not edit any configuration files in you data folder. Make personal copies of any file you want to edit in your home folder and edit these instead.

== Moving on ... ==

Flightgear is now installed on your system. You can test it by running
<pre>
fgfs
</pre>

If you don't like working from a terminal you should try one of the available gui's for launching flightgear.
I think the most common is [[fgrun]], but personally I prefer [[FGo!]].

Howto:Illuminate faces

2012-09-09T11:04:10Z

Popolon:

'''WARNING: This method will give weird results in Rembrandt rendering, use [[Howto:Lightmap]] instead. This is airplane oriented but will work with building too. You should use model-combined.eff, documentation is in FGDATA/Docs/model-combined.eff/'''

Imagine you see a skyline with a countless amount of lights. Somewhere in front of you there's a stretched row of lights. That's the runway you will land on. That's how you will experience a flight in the dark of the night. In reality. But in [[FlightGear]] there aren't much illuminated buildings. So here's a [[:Category:Howto|howto]] that teaches you how to make lights and illuminated buildings. Enjoy!

== Basics ==
To make something of your building, airport, plane or what else illuminate we need an .xml file. In that .xml file we will place some stuff. Every animation (lighting is an animation) starts with the <animation> tag. Followed by the type of animation. For illumination we use the material-type.
Now comes a very important part: the objects. Here we need to place the objects that should react on the animation. If we have a building with a antenne on top of it and we only want the antenna to illuminate we need to make that a separate object. So every part that you want to be illuminated should be separated. You could do that in Blender, SketchUp or any other software you're using. Last part is the emission part. The emission will tell FlightGear in what color the object should be illuminated. By combining the three primary colors (red, green and blue) you can create any color you want. If we did everything as described above with a red light we will get something like:
<animation>
<type>material</type>
<object-name>Light1</object-name>
<object-name>Light2</object-name>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

=== Blender users ===
==== White lights ====
[[File:Blender-emit-property.jpg|thumb|right|Blender emit property location]]
[[Blender]] users may create illuminated faces directly from blender itself. But what makes a face to be illuminated in Flightgear ? Well, Flightgear can not take full advantage of all the properties a blender surface can take (fgfs is not a full featured rendering program nor wants to be), there is anyway a method to make faces in blender emit light by their own. First of all we have to remember that whatever program we are using to model an object if we want to use it in Flightgear we have to export it in AC3D format. Materials in AC3D format have line like this one:
<pre>
MATERIAL "MaterialName" rgb 1 0 0 amb 0.5 0.5 0.5 emis 0 0 0 spec 1 0.9999 0.9999 shi 32 trans 0
</pre>
Look at the 3 numbers after the emis word (0 0 0). this tells that this material does not emit any light by itself. This is the common row we get when exporting an object in AC3D format from blender. If we wish to illuminate it we can take advantage of the '''Emit''' material property under the ''Shaders'' panel. If we want a slight emission we can give a value like 0.4 to it. We will get a surface that will emit white light:
<pre>
MATERIAL "MaterialName" rgb 1 0 0 amb 0.5 0.5 0.5 emis 0.4 0.4 0.4 spec 1 0.9999 0.9999 shi 32 trans 0
</pre>

Using the blender emit property we can obtain always illuminated surfaces without using any xml configuration file. Just remember that this surface will always emit light in every moment of the day. Also see [[AC files: Basic changes to textures and colors]].

==== Colored lights ====
Colored lights can be obtained from blender using a trick of the ac3d default exporter script. We will not use the emit property anymore, but we will use the ''mirror color'' of a material as emission color. So after having set the material mirror color to the considered value we have to teach the exporter to use it and convert it to an emis property. This is done by setting the property '''MIRCOL_AS_EMIS''' to '''True''' under the Blender registry. The Blender registry is a folder generally located in $HOME/.blender/bpydata/config . Here you will probably find an ac3d_export.cfg file. Edit it and change the row:
<pre>
'MIRCOL_AS_EMIS': False,
</pre>
to
<pre>
'MIRCOL_AS_EMIS': True,
</pre>
Now every time you will export to AC3D format all the materials will get the emis property the same value as their mirror color. 
''Attention !'' Generally blender creates new material setting mirror property to white color (1 1 1), before exporting you have to set all the non illuminating surfaces material mirror color to black (0 0 0) otherwise all the object will be like a big white thing in your scene. 
''Warning !'' The import from an ac3d file does not take in consideration of the MIRCOL_AS_EMIS set to True. Blender will make a media of the values and set it to the emis property (Instead of the mirror color). Fortunately this will be fixed with upcoming Blender version 2.49. Meanwhile blender 2.48 users can use [http://brisa.homelinux.net/fgfs/ac3d_import.py update version of the importer] script that fix the import problem and setting:
<pre>
'EMIS_AS_MIRCOL': False,
</pre>
to
<pre>
'EMIS_AS_MIRCOL': True,
</pre>
in the ac3d_import.cfg config file.

== Variations ==
The light we made above is always illuminated. Below I placed some variations that make the light only illuminate at dark or in changing colors.

=== Illuminate during dark ===
If you want a face to illuminate during dark we use the sun angle property (/sim/time/sun-angle-rad). The value is expressed in radians from the zenith, so a common value where our face should start illuminate is pi/2, or 1.57, right on the horizon. But you could change the value if you want to illuminate earlier or later. Depends on your needs.

'''To turn lights on if the sky is dark:'''
<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<greater-than>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</greater-than>
</condition>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

'''And to turn the lights off during day: This bit is not needed anymore since FG version 1.9.1. The light is switched off automatically when the above condition is no longer true.'''
<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<less-than-equals>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</less-than-equals>
</condition>
<emission>
<red>0</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

=== Changing illumination color ===
Sometimes there are lights that change colours every now and then. It's not very hard to implement this in FlightGear. There are multiple ways to do this, but we will use the /sim/time/utc/ property. The example below changes color from red, green to blue every. We specified that the color should be red at every time behind 0 second. So if the time is 15:20:05 the color will be red. But at 22:01:21 color will be changed to green. Using this you could even make the lighting color be different every second of the day. Another possibility is a light that illuminates only between two specified times like from 21:00:00 till 6:30:00.

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>0</value>
</equals>
</condition>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>20</value>
</equals>
</condition>
<emission>
<red>0</red>
<green>1</green>
<blue>0</blue>
</emission>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>40</value>
</equals>
</condition>
<emission>
<red>0</red>
<green>0</green>
<blue>1</blue>
</emission>
</animation>

=== Changing texture if illuminated ===
To change the texture of an illuminated face we add one single row to the file.

'''NOTE: This does not work with versions between GIT/2.2.0 snapshot releases and 1.0.0!'''

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<greater-than>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</greater-than>
</condition>
<emission>
<red>1</red>
<green>1</green>
<blue>1</blue>
</emission>
<texture>Light_lit.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<less-than-equals>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</less-than-equals>
</condition>
<emission>
<red>1</red>
<green>1</green>
<blue>1</blue>
</emission>
<texture>Light.png</texture>
</animation>

=== Switch to another part of texture if illuminated ===
For v1.9 or later, the way to change textures is the textranslate animation, which lets you "slide" across a texture map. This animation is applied to a single image which has the daytime and nighttime textures placed next to each other.

The width in pixels of texture map (if it is being moved sideways) should be an integral power of two (eg. 20=1, 21=2, 22=4, 23=8, 24=16 and so on). For this example, this texture map has two sides that are each 256 pixels wide. The '''left side''' is for day-time textures, the '''right side''' is for night-time textures. Each night-time texture is positioned exactly 256 pixels to the right of the day-time texture. Here is an example taken from the shared model [http://scenemodels.flightgear.org/modeledit.php?id=1570 German village house - grey roof]:
[[File:Germanvillagehouse1_day.png|thumb|day-time textures]]
[[File:Germanvillagehouse1_night.png|thumb|night-time textures]]

[[File:Germanvillagehouse1.png]]

When you have made that texture map, you apply the day-time textures as default textures to the model in your favourite modeling software (e.g. [[Blender]] or [[SketchUp]]).

Finally you have to add two bits of code to the XML file:
# Code that tells FG to move the texture to the left during night-time
# Code that illuminates the model during night-time

The following code tells FlightGear to translate the texture halfway across horizontally at nightfall (setting <tt>y</tt> instead would translate it vertically):

<syntaxhighlight lang="xml">
<animation>
<type>textranslate</type>
<object-name>germanvillagehouse1</object-name>
<property>/sim/time/sun-angle-rad</property>
<step> 1.57 </step>
<factor>0.318471338</factor>
<axis>
<x> -1 </x>
<y> 0 </y>
</axis>
</animation>
</syntaxhighlight>

The 3d object (the house) which "wears" the texture is called <tt>germanvillagehouse1</tt> here. This name refers to the name given to the respective object in the AC file. For more information on object names, see [[AC files: Understanding and changing .ac code#Identifying an object|AC files: identifying an object]].

In order to illuminate the object during dark, add the block of code introduced above: [[Howto: Illuminate faces#Illuminate during dark|Illuminate during dark]]. Finally you will have two blocks of code: One that moves the texture at dusk and one that illuminates the object at dusk. Make sure both of them use the right object name. The light will be switched off and the texture will be switched back to day-time texture when the sun rises above an angle of 1.57. Two essential tags here are <step> and <factor>.
* '''<step>''' indicates that the texture should be translated in a single step only when the value passes 1.57 or a multiple thereof; without it the texture would be translated continuously.
* '''<factor>''' is equal to 0.5/1.57, which normalizes the sun angle in radians to a value between 0 and 1 for translating the texture.

=== Flashing light ===
To make a flashing light we need to create two objects. One containing the (emitted) light and one containing the light as it would be shown when disabled/turned off. Then we add the following code to our .xml file:

<animation>
<type>timed</type>
<object-name>LightsOn</object-name>
<object-name>LightsOff</object-name>
<use-personality type="bool">true</use-personality>
<branch-duration-sec>
<random>
<min>2.9</min>
<max>3.1</max>
</random>
</branch-duration-sec>
<branch-duration-sec>
<random>
<min>1.9</min>
<max>2.1</max>
</random>
</branch-duration-sec>
</animation>

You can set the values (time in seconds that a certain object is shown) to your needs. The upper ones are for the LightsOn object, the lower ones for the LightsOff object.

== Related content ==
* [[Howto: Lightmap|Lightmap effect]], allows for easy and nice looking lighting, without switching textures.

[[Category:Howto|Illuminate faces]]
[[Category:Scenery enhancement|Illuminate faces]]

Category:Scenery enhancement

2012-08-15T11:07:45Z

Popolon: /* Models */

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

==== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ===
* [[XML]] XML format of the Models, basics 3d models are in AC3D files format (.ac) and fgfs XML define their behavior, this page describe general XML format syntax and common usage and one example to insert NASAL script code inside.
* [[FlightGear_Newsletter_August_2012#Scenery_corner]] web forms and tools to import/modify/delete models in the official scenery database.

==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Normals and Transparency Tutorial]]: Tutorial about how to use Blender 2.4x, to create model with transparency and normals information compatible with Flightgear AC3D and exporting them.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces ('''Warning: Old method, would give weird result with Rembrandt renderer''')
* [[Howto:Lightmap]]: The new way to have illuminating faces ([[Es/Howto: Lightmap|full spanish translation]])
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.
* [[Modeling - FAQ]]: ('''stub''') really few question should be filled and perhaps be used as references on other articles ?
* [[Modeling Resources]]: Lot of external ressources about modeling 3d objects and animate them, '''some redunduncies with [[Aircraft information resources]], probably to dispatch'''
* [[Modeling_-_Getting_Started]]: Nice general starting page with categories and link to other important informations about modeling for Flightgear.

===== Aircrafts =====
(see also : [[:Category:Aircraft enhancement]] and [[Portal:Developer/Aircraft]]
* [[Howto:3D Aircraft Models]]: Create aircraft model.
* [[Aircraft information resources]]: Lot of usefull links about aircrafts information resources.
* [[Howto:Animate gear scissors]]: Animate gear scissors, include nasal example script and xml definition.
* [[3D Model Rotates Around Nose]]: Simple explanation of the mistake to define nose as centroid and how to place it the right way.
* [[Creating instruments for FG]]: Create panel instruments for an airplane, no 3d modeling part, only about XML definition of the instrument to get it usable in flightgear.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model
* [[Livery over MP]]: Add a livery dialog in the flightgear menu ([[Es/Livery_over_MP|Full spanish translation]]).

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.
** [[Modeling - SketchUp]]: Redirect to [[SketchUp to AC3D exporter]]. The source of this page contains some information about modeling with Sketchup but is commented as deprecated and Blender is considered a more appropriate and compatible tool.
* [[GMax2AC]]: Script for converting GMax models to AC3D format used in Flightgear.
* [[Model import and export]]: General import/export page, with some external models (Blender and GMax) '''Marked as need cleanup'''

===== Modelers =====
* [[Blender]]: Interesting links to internal pages and externals tutorials about using Blender to enhance Flightger.
* [[Wings 3D]]: Few explanation lines some external docs and tutorials links
** [[Modeling - Wings 3D]] : tutorial about modeling with Wings 3d.
* [[K-3D]]: Only one line with a link to the project itself.
* [[Pretty Poly 3D Modeller]]: Only one line with two links to the project itself
* [[AC3D]]: Proprietary modler with limited trial version. Only one line with link to the site.

===== Modeling palette=====
* To populate :
{{3d}}

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Category:Scenery enhancement

2012-08-10T20:38:53Z

Popolon: /* Models */ add more articles description

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

==== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ===
* [[XML]] XML format of the Models, basics 3d models are in AC3D files format (.ac) and fgfs XML define their behavior, this page describe general XML format syntax and common usage and one example to insert NASAL script code inside.

==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Normals and Transparency Tutorial]]: Tutorial about how to use Blender 2.4x, to create model with transparency and normals information compatible with Flightgear AC3D and exporting them.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces ('''Warning: Old method, would give weird result with Rembrandt renderer''')
* [[Howto:Lightmap]]: The new way to have illuminating faces ([[Es/Howto: Lightmap|full spanish translation]])
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.
* [[Modeling - FAQ]]: ('''stub''') really few question should be filled and perhaps be used as references on other articles ?
* [[Modeling Resources]]: Lot of external ressources about modeling 3d objects and animate them, '''some redunduncies with [[Aircraft information resources]], probably to dispatch'''
* [[Modeling_-_Getting_Started]]: Nice general starting page with categories and link to other important informations about modeling for Flightgear.

===== Aircrafts =====
(see also : [[:Category:Aircraft enhancement]] and [[Portal:Developer/Aircraft]]
* [[Howto:3D Aircraft Models]]: Create aircraft model.
* [[Aircraft information resources]]: Lot of usefull links about aircrafts information resources.
* [[Howto:Animate gear scissors]]: Animate gear scissors, include nasal example script and xml definition.
* [[3D Model Rotates Around Nose]]: Simple explanation of the mistake to define nose as centroid and how to place it the right way.
* [[Creating instruments for FG]]: Create panel instruments for an airplane, no 3d modeling part, only about XML definition of the instrument to get it usable in flightgear.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model
* [[Livery over MP]]: Add a livery dialog in the flightgear menu ([[Es/Livery_over_MP|Full spanish translation]]).

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.
** [[Modeling - SketchUp]]: Redirect to [[SketchUp to AC3D exporter]]. The source of this page contains some information about modeling with Sketchup but is commented as deprecated and Blender is considered a more appropriate and compatible tool.
* [[GMax2AC]]: Script for converting GMax models to AC3D format used in Flightgear.
* [[Model import and export]]: General import/export page, with some external models (Blender and GMax) '''Marked as need cleanup'''

===== Modelers =====
* [[Blender]]: Interesting links to internal pages and externals tutorials about using Blender to enhance Flightger.
* [[Wings 3D]]: Few explanation lines some external docs and tutorials links
** [[Modeling - Wings 3D]] : tutorial about modeling with Wings 3d.
* [[K-3D]]: Only one line with a link to the project itself.
* [[Pretty Poly 3D Modeller]]: Only one line with two links to the project itself
* [[AC3D]]: Proprietary modler with limited trial version. Only one line with link to the site.

===== Modeling palette=====
* To populate :
{{3d}}

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Aircraft information resources

2012-08-10T20:05:59Z

Popolon: /* Gas Turbine Data */ add 3d palette, as this article is defined inside...

Please note that as of 04/2009, the section about "Avionics Documents" has been moved to a new page that is to be found at [[Avionics Development Resources]].
Also the section on aircraft operating manuals/handbooks has now been moved to a new dedicated page: [[Aircraft Manuals]].

== Definitions ==
Useful for all aircraft:
* [http://www.goodyearaviation.com/img/pdf/definitions.pdf Tire name size classification]

== Aircraft Resources ==
=== General ===
* [http://www.airlinercafe.com/list.php?c=walkarounds Airlinercafe] Detailed and high resolution pictures of major components on airliners. ('''Recommended''')
* [http://www.aftd.com/Library.html Aeroflight Tech Data Aeronautical Library]
* [http://www.bh.com/companions/034074152X/appendices/default.htm Civil Jet Aircraft Design]
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/ Dimension data for various aircraft]
* [http://www.meriweather.com/ Meriweather's flightdeck simulations & photo/video gallery]
* [http://www.myairplane.com/databases/airspec/ Specifications for various aircraft]
* [http://www.smartcockpit.com/ Smart Cockpit]
* http://www2.nlr.nl/public/hosted-sites/hybridge/documents/R5.6%20061_HSCC2005.pdf
* [http://www.flightlevel400.com/manuals.html Numerous Manuals and other Data ] ('''Recommended ''')
* [http://simviation.com/designresources.htm Simviation- lots of 3-views]
=== Diagrams and 3-views ===
''See also:[[Modeling Resources]]''
* http://www.umt.fme.vutbr.cz/~ruja/modely/podklady.htm Lots of 3 views of early to mid 20th century aricraft.
* http://www.seawings.co.uk/reference.htm Diagrams and other data on seaplanes
* http://www.history.navy.mil/branches/org4-4.htm Navy aircraft
* http://www.aircraftdesign.com/acpix.html Lots of 3-views on prototype and experimental
* http://www.aviastar.org/index.html only helicopters

=== Airbus ===
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable1.xls Dimension data for all Airbus aircraft]
* '''A300'''
** [http://www.aftd.com/TCDS_PDFS/A35EU_19.pdf A300 Type certificate]
* '''A320'''
**
** http://www.airbusdriver.net
** http://www.e-flight.com/a320.htm
** http://meriweather.com/320/fd-320.html
* '''A330'''
** [http://www.aftd.com/TCDS_PDFS/A46NM_9.pdf A330 Type certificate]
** [http://www.ntsb.gov/events/2001/AA587/exhibits/306430.pdf Partial wind tunnel data]
* '''A340'''
** [http://www.aftd.com/TCDS_PDFS/A43NM_3.pdf A340 Type certificate]
** http://www.a340.net/
** http://www.planningchart.de/340_loc1.gif
** http://www.planningchart.de/340_loc2.gif
** http://meriweather.com/340/340-fd.html
* '''A380'''
** http://www.gillesvidal.com/blogpano/cockpit1.htm

=== Boeing ===
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable2.xls Dimension data for all variants of Boeing 707, 717, 727, and 737]
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable3.xls Dimension data for all variants of Boeing 747, 757, and 767]
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable4.xls Dimension data for all variants of Boeing 777]
* '''737'''
** http://www.737cockpit.com/
** http://www.737ng.co.uk/technical.htm 737's cockpit measurments
** http://www.b737.org.uk/
** http://www.boeing.com/commercial/737family/
** http://www.smartcockpit.com/
* '''747'''
** http://www.geocities.com/CapeCanaveral/Launchpad/1916/index.htm
** http://meriweather.com/747/fd-747.html
** [http://video.google.com/videoplay?docid=5141036042437868499 747-400 Flight Deck/EFIS Intro] (video)
* '''757'''
** http://www.757.org.uk
** http://www.artietheairplane.com/redbox.htm
* '''767'''
** http://www.757.org.uk/767/index.html
** http://meriweather.com/767/767-fd.html
* '''777'''
** http://www.planesimulation.com/777a.htm
** http://meriweather.com/777/fd-777.html

=== Cessna ===
* '''C152'''

** [http://www.ginecoweb.com/Piloto%20Privado/Cessna152Manual.pdf Cessna C152 Manual]
** [http://www.fmfa.org/docs/c152_checklist.pdf Checklist]
** [http://www.fmfa.org/docs/c152_emergency.pdf Emergency Checklist]
** [http://www.fmfa.org/docs/c152_complete.pdf Combined Checklist]

** [http://www.texins.org/flyingclub/reference/ApolloGX_QuickReference.pdf 1976 C150 Quick Reference]
** [http://www.texins.org/flyingclub/reference/ApolloGX_UserManual.pdf 1976 C150 User Manual]
* '''C172'''
* [http://www.servantairministries.org/multimedia/C172M_POH_N5141R.pdf C712M Pilot Operating Handbook]
* [http://www.pacificcoastflyers.org/files/POH/C172N_POH.pdf C172N Pilot Operating Handbook]

** http://www.fortmeadeflyingactivity.org/docs/c172p180_n9871fm_combined_procedures_checklist.pdf
** http://www.sierra.aero/Files/172%20RG%20POH%20FULL.pdf
** [http://www.fmfa.org/docs/c172p180_poh_addendum.pdf C172p180 POH Addendum]
** [http://www.fmfa.org/docs/c172p180_n9871fm_standard_procedures_checklist.pdf Standard Procedures Checklist]
** [http://www.fmfa.org/docs/c172p180_n9871fm_emergency_procedures_checklist.pdf Emergency Procedures Checklist]
** [http://www.fmfa.org/docs/c172p180_n9871fm_combined_procedures_checklist.pdf Combined Checklist]

* '''T-41C (military training version of c172)'''
** [http://www.fmfa.org/docs/t41c_poh.pdf Aircraft Manual]
** [http://www.fmfa.org/docs/t41c_checklist.pdf Aircraft Checklist]
** [http://www.fmfa.org/docs/t41c_usaf_checklist.pdf USAF Checklist]
** [http://www.fmfa.org/docs/t41c_emergency.pdf Emergency Procedures]
** [http://www.fmfa.org/docs/t41c_complete.pdf Combined Checklist]

=== Cirrus ===
* '''Cirrus SR 20'''
** http://www.centerlineflight.com/Cirrus%20SR20%20Departure%20Checklist.pdf
** http://www.centerlineflight.com/Cirrus%20SR20%20Takeoff-Cruise%20Checklist.pdf
** http://www.avidyne.com/techpubs2/brochures/AV814_Envision_Cirrus_v01.pdf
** http://servicecenters.cirrusdesign.com/TechPubs/pdf/POH/SR20-003/pdf/13999-003InfoManual.pdf
** http://www.dominicganz.de/dominic/aviation/checklist_cirrus_sr20.pdf
** http://www.ginecoweb.com/Piloto%20Privado/Cessna152Manual.pdf
** http://servicecenters.cirrusdesign.com/TechPubs/pdf/POH/International/OnlineBR21400-001.pdf

=== Diamond ===
''' DA20 Katana '''
** http://www.diamondaircraft.com/library/16/10/DA20-A1-AFM-inc-Rev17.pdf

=== Fokker ===
** http://www.fokkerpilot.net/

=== Dornier ===
* [http://www.awi-bremerhaven.de/Logistics/Aircraft/nuhabu96.pdf Dornier DO 228]

=== Grob ===
* http://freechecklists.net/Resources/Grob/G-115/

=== Lockheed Martin ===
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable6.xls Dimension data for L1011 (last column)]

=== Iyushin ===
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable6.xls Dimension data for all variants of Il-62, Il-86, and Il-96]

=== McDonnell Douglas ===
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable5.xls Dimension data for all variants of DC8, DC9, MD-81, MD-82, MD-83, and MD-87]
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable6.xls Dimension data for all variants of MD-90, DC-10, MD-11, and MD-12]

=== Mil ===
* Fantastic detail on most aspects of the Mi-2 and Mi-8 including detailed cockpit photos, system diagrams and descriptions from a former pilot (in German). Also excellent sections full of diagrams on aerodynamic theory for both fixed and rotary wing. http://nva-flieger.de/

=== Piper ===
* '''Piper Archer'''
** http://home.stny.rr.com/bkw/ace/PA-28-181-POH.pdf
* '''Piper Arrow'''
** [http://www.fmfa.org/docs/pa28r_checklist.pdf pa28r Checklist]
** [http://www.fmfa.org/docs/pa28r_emergency.pdf Emergency Procedures]
** [http://www.fmfa.org/docs/pa28r_complete.pdf Combined Checklist]

=== Tupolev ===
* [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Aircraft%20data/atable7.xls Dimension data for all variants of Tu-134, Tu-154, Tu-200, Tu-204, and Tu-334]

== Gas Turbine Data ==
* '''General'''
** [http://www.aircraftenginedesign.com/custom.html1.html Gas Turbine Engine Data]
** [http://www.jet-engine.net/civtfspec.html Civilian Turbojet/Turbofan Specifications]
** [http://www.jet-engine.net/miltfspec.html Military Turbojet/Turbofan Specifications]
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/ More gas turbine data]
** [http://www.caa.co.uk/default.aspx?catid=702&pagetype=68 Aircraft Engine Emissions] (also includes more useful data, like fuel consumption)

* '''CFM'''
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/btable1.xls Gas turbine data for CFM56-3C1, CFM56-5A1, CFM56-5A2, and CFM56-7B20]

* '''International Aero Engines'''
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/btable3.xls Gas turbine data for the following engines by General Electric: CF34-3A, CF34-3B, CF6-80A2, CF6-80C2-A5, CF6-80C2-B1F, CF6-80C2-B2, CF6-80E1A2, and GE90-85B]

* '''International Aero Engines'''
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/btable1.xls Gas turbine data for IAEV2500, IAEV2522, IAEV2533, and IAE2525]

* '''Pratt & Whitney'''
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/btable2.xls Gas turbine data for JT8D-219, PW2037, PW4052, PW4056, PW4152, PW4168, and PW4084]

* '''Rolls Royce'''
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/btable4.xls Gas turbine data for the following engines by Rolls Royce: RB-183-555-15P, RB-211-524H, RB-211-E4/E4-B, SPEY 511-8, TRENT 772, TRENT 892, TAY 611, and TAY 651]

* '''Miscellaneous Engine Manufacturers'''
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/btable5.xls Gas turbine data for ALLIEDSIG LF507, ALLIEDSIG LF502R-5, ALLISON AE3007, CFE CFE738, P&W CANADA JT15D, and P&W CANADA PW305B]
** [http://www.soton.ac.uk/~jps7/Aircraft%20Design%20Resources/Lloyd%20Jenkinson%20data/Gas%20turbine%20data/btable6.xls Gas turbine data for BMW:RR BR710, BMW:RR B715-55, WILL:RR FJ44, JASC AVIA D-30KU II, JASC AVIA PS-90A, ZMKB D-18T, and ZMKB D-436T1]

{{3d}}

[[Category:Aircraft Resources]]
[[Category:List]]
[[Category:Resource]]

Howto:Lightmap

2012-08-10T07:30:10Z

Popolon: /* FlightGear 2.6.0 and onwards */

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

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

== Lightmaps in FlightGear ==

=== FlightGear 2.6.0 and onwards ===
See [[FlightGear Newsletter December 2011#Shaders]].

'''Effect/lightmap''' in the .xml must be replaced by '''Effect/model-combined-deferred''' (or '''Effect/Building''' for buildings), see $FGDATA/Docs/model-combined.eff/ for some explanations

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

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

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

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

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

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

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

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

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

Howto:Lightmap

2012-08-10T07:26:52Z

Popolon: /* FlightGear 2.6.0 and onwards */

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

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

== Lightmaps in FlightGear ==

=== FlightGear 2.6.0 and onwards ===
See [[FlightGear Newsletter December 2011#Shaders]].

Effect/lightmap in the .xml must be replaced by Effect/model-combined-deferred or Effect/Building (for buildings), see $FGDATA/Docs/model-combined.eff/ for some explanations

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

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

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

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

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

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

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

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

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

Howto:Lightmap

2012-08-10T07:26:28Z

Popolon: /* FlightGear 2.6.0 and onwards */

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

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

== Lightmaps in FlightGear ==

=== FlightGear 2.6.0 and onwards ===
See [[FlightGear Newsletter December 2011#Shaders]]
Effect/lightmap in the .xml must be replaced by Effect/model-combined-deferred or Effect/Building (for buildings), see $FGDATA/Docs/model-combined.eff/ for some explanations

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

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

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

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

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

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

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

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

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

Category:Scenery enhancement

2012-08-10T07:05:44Z

Popolon: /* Creating or enhancing models */

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

==== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ===
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Normals and Transparency Tutorial]]: Tutorial about how to use Blender 2.4x, to create model with transparency and normals information compatible with Flightgear AC3D and exporting them.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces ('''Warning: Old method, would give weird result with Rembrandt renderer''')
* [[Howto:Lightmap]]: The new way to have illuminating faces ([[Es/Howto: Lightmap|full spanish translation]])
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.
* [[Modeling - FAQ]]: ('''stub''') really few question should be filled and perhaps be used as references on other articles ?

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.
* [[GMax2AC]]: Script for converting GMax models to AC3D format used in Flightgear.

===== Modelers =====
* [[Blender]]: Interesting links to internal pages and externals tutorials about using Blender to enhance Flightger.
* [[Wings 3D]]: Few explanation lines some external docs and tutorials links
* [[K-3D]]: Only one line with a link to the project itself.
* [[Pretty Poly 3D Modeller]]: Only one line with two links to the project itself
* [[AC3D]]: Proprietary modler with limited trial version. Only one line with link to the site.

===== Modeling palette=====
* To populate :
{{3d}}

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Howto:Illuminate faces

2012-08-09T22:52:14Z

Popolon: add warning + link to Howto:Lightmap, the new method.

'''WARNING: This method will give weird results in Rembrandt rendering, use [[Howto:Lightmap]] instead. This is airplane oriented but will work with building too'''.

Imagine you see a skyline with a countless amount of lights. Somewhere in front of you there's a stretched row of lights. That's the runway you will land on. That's how you will experience a flight in the dark of the night. In reality. But in [[FlightGear]] there aren't much illuminated buildings. So here's a [[:Category:Howto|howto]] that teaches you how to make lights and illuminated buildings. Enjoy!

== Basics ==
To make something of your building, airport, plane or what else illuminate we need an .xml file. In that .xml file we will place some stuff. Every animation (lighting is an animation) starts with the <animation> tag. Followed by the type of animation. For illumination we use the material-type.
Now comes a very important part: the objects. Here we need to place the objects that should react on the animation. If we have a building with a antenne on top of it and we only want the antenna to illuminate we need to make that a separate object. So every part that you want to be illuminated should be separated. You could do that in Blender, SketchUp or any other software you're using. Last part is the emission part. The emission will tell FlightGear in what color the object should be illuminated. By combining the three primary colors (red, green and blue) you can create any color you want. If we did everything as described above with a red light we will get something like:
<animation>
<type>material</type>
<object-name>Light1</object-name>
<object-name>Light2</object-name>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

=== Blender users ===
==== White lights ====
[[File:Blender-emit-property.jpg|thumb|right|Blender emit property location]]
[[Blender]] users may create illuminated faces directly from blender itself. But what makes a face to be illuminated in Flightgear ? Well, Flightgear can not take full advantage of all the properties a blender surface can take (fgfs is not a full featured rendering program nor wants to be), there is anyway a method to make faces in blender emit light by their own. First of all we have to remember that whatever program we are using to model an object if we want to use it in Flightgear we have to export it in AC3D format. Materials in AC3D format have line like this one:
<pre>
MATERIAL "MaterialName" rgb 1 0 0 amb 0.5 0.5 0.5 emis 0 0 0 spec 1 0.9999 0.9999 shi 32 trans 0
</pre>
Look at the 3 numbers after the emis word (0 0 0). this tells that this material does not emit any light by itself. This is the common row we get when exporting an object in AC3D format from blender. If we wish to illuminate it we can take advantage of the '''Emit''' material property under the ''Shaders'' panel. If we want a slight emission we can give a value like 0.4 to it. We will get a surface that will emit white light:
<pre>
MATERIAL "MaterialName" rgb 1 0 0 amb 0.5 0.5 0.5 emis 0.4 0.4 0.4 spec 1 0.9999 0.9999 shi 32 trans 0
</pre>

Using the blender emit property we can obtain always illuminated surfaces without using any xml configuration file. Just remember that this surface will always emit light in every moment of the day. Also see [[AC files: Basic changes to textures and colors]].

==== Colored lights ====
Colored lights can be obtained from blender using a trick of the ac3d default exporter script. We will not use the emit property anymore, but we will use the ''mirror color'' of a material as emission color. So after having set the material mirror color to the considered value we have to teach the exporter to use it and convert it to an emis property. This is done by setting the property '''MIRCOL_AS_EMIS''' to '''True''' under the Blender registry. The Blender registry is a folder generally located in $HOME/.blender/bpydata/config . Here you will probably find an ac3d_export.cfg file. Edit it and change the row:
<pre>
'MIRCOL_AS_EMIS': False,
</pre>
to
<pre>
'MIRCOL_AS_EMIS': True,
</pre>
Now every time you will export to AC3D format all the materials will get the emis property the same value as their mirror color. 
''Attention !'' Generally blender creates new material setting mirror property to white color (1 1 1), before exporting you have to set all the non illuminating surfaces material mirror color to black (0 0 0) otherwise all the object will be like a big white thing in your scene. 
''Warning !'' The import from an ac3d file does not take in consideration of the MIRCOL_AS_EMIS set to True. Blender will make a media of the values and set it to the emis property (Instead of the mirror color). Fortunately this will be fixed with upcoming Blender version 2.49. Meanwhile blender 2.48 users can use [http://brisa.homelinux.net/fgfs/ac3d_import.py update version of the importer] script that fix the import problem and setting:
<pre>
'EMIS_AS_MIRCOL': False,
</pre>
to
<pre>
'EMIS_AS_MIRCOL': True,
</pre>
in the ac3d_import.cfg config file.

== Variations ==
The light we made above is always illuminated. Below I placed some variations that make the light only illuminate at dark or in changing colors.

=== Illuminate during dark ===
If you want a face to illuminate during dark we use the sun angle property (/sim/time/sun-angle-rad). The value is expressed in radians from the zenith, so a common value where our face should start illuminate is pi/2, or 1.57, right on the horizon. But you could change the value if you want to illuminate earlier or later. Depends on your needs.

'''To turn lights on if the sky is dark:'''
<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<greater-than>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</greater-than>
</condition>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

'''And to turn the lights off during day: This bit is not needed anymore since FG version 1.9.1. The light is switched off automatically when the above condition is no longer true.'''
<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<less-than-equals>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</less-than-equals>
</condition>
<emission>
<red>0</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

=== Changing illumination color ===
Sometimes there are lights that change colours every now and then. It's not very hard to implement this in FlightGear. There are multiple ways to do this, but we will use the /sim/time/utc/ property. The example below changes color from red, green to blue every. We specified that the color should be red at every time behind 0 second. So if the time is 15:20:05 the color will be red. But at 22:01:21 color will be changed to green. Using this you could even make the lighting color be different every second of the day. Another possibility is a light that illuminates only between two specified times like from 21:00:00 till 6:30:00.

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>0</value>
</equals>
</condition>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>20</value>
</equals>
</condition>
<emission>
<red>0</red>
<green>1</green>
<blue>0</blue>
</emission>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>40</value>
</equals>
</condition>
<emission>
<red>0</red>
<green>0</green>
<blue>1</blue>
</emission>
</animation>

=== Changing texture if illuminated ===
To change the texture of an illuminated face we add one single row to the file.

'''NOTE: This does not work with versions between GIT/2.2.0 snapshot releases and 1.0.0!'''

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<greater-than>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</greater-than>
</condition>
<emission>
<red>1</red>
<green>1</green>
<blue>1</blue>
</emission>
<texture>Light_lit.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<less-than-equals>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</less-than-equals>
</condition>
<emission>
<red>1</red>
<green>1</green>
<blue>1</blue>
</emission>
<texture>Light.png</texture>
</animation>

=== Switch to another part of texture if illuminated ===
For v1.9 or later, the way to change textures is the textranslate animation, which lets you "slide" across a texture map. This animation is applied to a single image which has the daytime and nighttime textures placed next to each other.

The width in pixels of texture map (if it is being moved sideways) should be an integral power of two (eg. 20=1, 21=2, 22=4, 23=8, 24=16 and so on). For this example, this texture map has two sides that are each 256 pixels wide. The '''left side''' is for day-time textures, the '''right side''' is for night-time textures. Each night-time texture is positioned exactly 256 pixels to the right of the day-time texture. Here is an example taken from the shared model [http://scenemodels.flightgear.org/modeledit.php?id=1570 German village house - grey roof]:
[[File:Germanvillagehouse1_day.png|thumb|day-time textures]]
[[File:Germanvillagehouse1_night.png|thumb|night-time textures]]

[[File:Germanvillagehouse1.png]]

When you have made that texture map, you apply the day-time textures as default textures to the model in your favourite modeling software (e.g. [[Blender]] or [[SketchUp]]).

Finally you have to add two bits of code to the XML file:
# Code that tells FG to move the texture to the left during night-time
# Code that illuminates the model during night-time

The following code tells FlightGear to translate the texture halfway across horizontally at nightfall (setting <tt>y</tt> instead would translate it vertically):

<syntaxhighlight lang="xml">
<animation>
<type>textranslate</type>
<object-name>germanvillagehouse1</object-name>
<property>/sim/time/sun-angle-rad</property>
<step> 1.57 </step>
<factor>0.318471338</factor>
<axis>
<x> -1 </x>
<y> 0 </y>
</axis>
</animation>
</syntaxhighlight>

The 3d object (the house) which "wears" the texture is called <tt>germanvillagehouse1</tt> here. This name refers to the name given to the respective object in the AC file. For more information on object names, see [[AC files: Understanding and changing .ac code#Identifying an object|AC files: identifying an object]].

In order to illuminate the object during dark, add the block of code introduced above: [[Howto: Illuminate faces#Illuminate during dark|Illuminate during dark]]. Finally you will have two blocks of code: One that moves the texture at dusk and one that illuminates the object at dusk. Make sure both of them use the right object name. The light will be switched off and the texture will be switched back to day-time texture when the sun rises above an angle of 1.57. Two essential tags here are <step> and <factor>.
* '''<step>''' indicates that the texture should be translated in a single step only when the value passes 1.57 or a multiple thereof; without it the texture would be translated continuously.
* '''<factor>''' is equal to 0.5/1.57, which normalizes the sun angle in radians to a value between 0 and 1 for translating the texture.

=== Flashing light ===
To make a flashing light we need to create two objects. One containing the (emitted) light and one containing the light as it would be shown when disabled/turned off. Then we add the following code to our .xml file:

<animation>
<type>timed</type>
<object-name>LightsOn</object-name>
<object-name>LightsOff</object-name>
<use-personality type="bool">true</use-personality>
<branch-duration-sec>
<random>
<min>2.9</min>
<max>3.1</max>
</random>
</branch-duration-sec>
<branch-duration-sec>
<random>
<min>1.9</min>
<max>2.1</max>
</random>
</branch-duration-sec>
</animation>

You can set the values (time in seconds that a certain object is shown) to your needs. The upper ones are for the LightsOn object, the lower ones for the LightsOff object.

== Related content ==
* [[Howto: Lightmap|Lightmap effect]], allows for easy and nice looking lighting, without switching textures.

[[Category:Howto|Illuminate faces]]
[[Category:Scenery enhancement|Illuminate faces]]

Category:Scenery enhancement

2012-08-09T22:50:23Z

Popolon: /* Creating or enhancing models */

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

==== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ===
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces ('''Warning: Old method, would give weird result with Rembrandt renderer''')
* [[Howto:Lightmap]]: The new way to have illuminating faces.
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Category:Scenery enhancement

2012-08-09T22:41:07Z

Popolon: /* Creating or enhancing models */ Warning, about deprecated method for Howto:Illuminate faces => could give weird results with Rembrandt renderer

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

==== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ===
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces ('''Warning: Old method, would give weird result with Rembrandt renderer''')
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Howto:Illuminate faces

2012-08-09T22:38:19Z

Popolon:

'''WARNING: This method will give weird results in Rembrandt rendering'''

Imagine you see a skyline with a countless amount of lights. Somewhere in front of you there's a stretched row of lights. That's the runway you will land on. That's how you will experience a flight in the dark of the night. In reality. But in [[FlightGear]] there aren't much illuminated buildings. So here's a [[:Category:Howto|howto]] that teaches you how to make lights and illuminated buildings. Enjoy!

== Basics ==
To make something of your building, airport, plane or what else illuminate we need an .xml file. In that .xml file we will place some stuff. Every animation (lighting is an animation) starts with the <animation> tag. Followed by the type of animation. For illumination we use the material-type.
Now comes a very important part: the objects. Here we need to place the objects that should react on the animation. If we have a building with a antenne on top of it and we only want the antenna to illuminate we need to make that a separate object. So every part that you want to be illuminated should be separated. You could do that in Blender, SketchUp or any other software you're using. Last part is the emission part. The emission will tell FlightGear in what color the object should be illuminated. By combining the three primary colors (red, green and blue) you can create any color you want. If we did everything as described above with a red light we will get something like:
<animation>
<type>material</type>
<object-name>Light1</object-name>
<object-name>Light2</object-name>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

=== Blender users ===
==== White lights ====
[[File:Blender-emit-property.jpg|thumb|right|Blender emit property location]]
[[Blender]] users may create illuminated faces directly from blender itself. But what makes a face to be illuminated in Flightgear ? Well, Flightgear can not take full advantage of all the properties a blender surface can take (fgfs is not a full featured rendering program nor wants to be), there is anyway a method to make faces in blender emit light by their own. First of all we have to remember that whatever program we are using to model an object if we want to use it in Flightgear we have to export it in AC3D format. Materials in AC3D format have line like this one:
<pre>
MATERIAL "MaterialName" rgb 1 0 0 amb 0.5 0.5 0.5 emis 0 0 0 spec 1 0.9999 0.9999 shi 32 trans 0
</pre>
Look at the 3 numbers after the emis word (0 0 0). this tells that this material does not emit any light by itself. This is the common row we get when exporting an object in AC3D format from blender. If we wish to illuminate it we can take advantage of the '''Emit''' material property under the ''Shaders'' panel. If we want a slight emission we can give a value like 0.4 to it. We will get a surface that will emit white light:
<pre>
MATERIAL "MaterialName" rgb 1 0 0 amb 0.5 0.5 0.5 emis 0.4 0.4 0.4 spec 1 0.9999 0.9999 shi 32 trans 0
</pre>

Using the blender emit property we can obtain always illuminated surfaces without using any xml configuration file. Just remember that this surface will always emit light in every moment of the day. Also see [[AC files: Basic changes to textures and colors]].

==== Colored lights ====
Colored lights can be obtained from blender using a trick of the ac3d default exporter script. We will not use the emit property anymore, but we will use the ''mirror color'' of a material as emission color. So after having set the material mirror color to the considered value we have to teach the exporter to use it and convert it to an emis property. This is done by setting the property '''MIRCOL_AS_EMIS''' to '''True''' under the Blender registry. The Blender registry is a folder generally located in $HOME/.blender/bpydata/config . Here you will probably find an ac3d_export.cfg file. Edit it and change the row:
<pre>
'MIRCOL_AS_EMIS': False,
</pre>
to
<pre>
'MIRCOL_AS_EMIS': True,
</pre>
Now every time you will export to AC3D format all the materials will get the emis property the same value as their mirror color. 
''Attention !'' Generally blender creates new material setting mirror property to white color (1 1 1), before exporting you have to set all the non illuminating surfaces material mirror color to black (0 0 0) otherwise all the object will be like a big white thing in your scene. 
''Warning !'' The import from an ac3d file does not take in consideration of the MIRCOL_AS_EMIS set to True. Blender will make a media of the values and set it to the emis property (Instead of the mirror color). Fortunately this will be fixed with upcoming Blender version 2.49. Meanwhile blender 2.48 users can use [http://brisa.homelinux.net/fgfs/ac3d_import.py update version of the importer] script that fix the import problem and setting:
<pre>
'EMIS_AS_MIRCOL': False,
</pre>
to
<pre>
'EMIS_AS_MIRCOL': True,
</pre>
in the ac3d_import.cfg config file.

== Variations ==
The light we made above is always illuminated. Below I placed some variations that make the light only illuminate at dark or in changing colors.

=== Illuminate during dark ===
If you want a face to illuminate during dark we use the sun angle property (/sim/time/sun-angle-rad). The value is expressed in radians from the zenith, so a common value where our face should start illuminate is pi/2, or 1.57, right on the horizon. But you could change the value if you want to illuminate earlier or later. Depends on your needs.

'''To turn lights on if the sky is dark:'''
<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<greater-than>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</greater-than>
</condition>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

'''And to turn the lights off during day: This bit is not needed anymore since FG version 1.9.1. The light is switched off automatically when the above condition is no longer true.'''
<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<less-than-equals>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</less-than-equals>
</condition>
<emission>
<red>0</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

=== Changing illumination color ===
Sometimes there are lights that change colours every now and then. It's not very hard to implement this in FlightGear. There are multiple ways to do this, but we will use the /sim/time/utc/ property. The example below changes color from red, green to blue every. We specified that the color should be red at every time behind 0 second. So if the time is 15:20:05 the color will be red. But at 22:01:21 color will be changed to green. Using this you could even make the lighting color be different every second of the day. Another possibility is a light that illuminates only between two specified times like from 21:00:00 till 6:30:00.

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>0</value>
</equals>
</condition>
<emission>
<red>1</red>
<green>0</green>
<blue>0</blue>
</emission>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>20</value>
</equals>
</condition>
<emission>
<red>0</red>
<green>1</green>
<blue>0</blue>
</emission>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<equals>
<property>/sim/time/utc/second</property>
<value>40</value>
</equals>
</condition>
<emission>
<red>0</red>
<green>0</green>
<blue>1</blue>
</emission>
</animation>

=== Changing texture if illuminated ===
To change the texture of an illuminated face we add one single row to the file.

'''NOTE: This does not work with versions between GIT/2.2.0 snapshot releases and 1.0.0!'''

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<greater-than>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</greater-than>
</condition>
<emission>
<red>1</red>
<green>1</green>
<blue>1</blue>
</emission>
<texture>Light_lit.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>Light</object-name>
<condition>
<less-than-equals>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</less-than-equals>
</condition>
<emission>
<red>1</red>
<green>1</green>
<blue>1</blue>
</emission>
<texture>Light.png</texture>
</animation>

=== Switch to another part of texture if illuminated ===
For v1.9 or later, the way to change textures is the textranslate animation, which lets you "slide" across a texture map. This animation is applied to a single image which has the daytime and nighttime textures placed next to each other.

The width in pixels of texture map (if it is being moved sideways) should be an integral power of two (eg. 20=1, 21=2, 22=4, 23=8, 24=16 and so on). For this example, this texture map has two sides that are each 256 pixels wide. The '''left side''' is for day-time textures, the '''right side''' is for night-time textures. Each night-time texture is positioned exactly 256 pixels to the right of the day-time texture. Here is an example taken from the shared model [http://scenemodels.flightgear.org/modeledit.php?id=1570 German village house - grey roof]:
[[File:Germanvillagehouse1_day.png|thumb|day-time textures]]
[[File:Germanvillagehouse1_night.png|thumb|night-time textures]]

[[File:Germanvillagehouse1.png]]

When you have made that texture map, you apply the day-time textures as default textures to the model in your favourite modeling software (e.g. [[Blender]] or [[SketchUp]]).

Finally you have to add two bits of code to the XML file:
# Code that tells FG to move the texture to the left during night-time
# Code that illuminates the model during night-time

The following code tells FlightGear to translate the texture halfway across horizontally at nightfall (setting <tt>y</tt> instead would translate it vertically):

<syntaxhighlight lang="xml">
<animation>
<type>textranslate</type>
<object-name>germanvillagehouse1</object-name>
<property>/sim/time/sun-angle-rad</property>
<step> 1.57 </step>
<factor>0.318471338</factor>
<axis>
<x> -1 </x>
<y> 0 </y>
</axis>
</animation>
</syntaxhighlight>

The 3d object (the house) which "wears" the texture is called <tt>germanvillagehouse1</tt> here. This name refers to the name given to the respective object in the AC file. For more information on object names, see [[AC files: Understanding and changing .ac code#Identifying an object|AC files: identifying an object]].

In order to illuminate the object during dark, add the block of code introduced above: [[Howto: Illuminate faces#Illuminate during dark|Illuminate during dark]]. Finally you will have two blocks of code: One that moves the texture at dusk and one that illuminates the object at dusk. Make sure both of them use the right object name. The light will be switched off and the texture will be switched back to day-time texture when the sun rises above an angle of 1.57. Two essential tags here are <step> and <factor>.
* '''<step>''' indicates that the texture should be translated in a single step only when the value passes 1.57 or a multiple thereof; without it the texture would be translated continuously.
* '''<factor>''' is equal to 0.5/1.57, which normalizes the sun angle in radians to a value between 0 and 1 for translating the texture.

=== Flashing light ===
To make a flashing light we need to create two objects. One containing the (emitted) light and one containing the light as it would be shown when disabled/turned off. Then we add the following code to our .xml file:

<animation>
<type>timed</type>
<object-name>LightsOn</object-name>
<object-name>LightsOff</object-name>
<use-personality type="bool">true</use-personality>
<branch-duration-sec>
<random>
<min>2.9</min>
<max>3.1</max>
</random>
</branch-duration-sec>
<branch-duration-sec>
<random>
<min>1.9</min>
<max>2.1</max>
</random>
</branch-duration-sec>
</animation>

You can set the values (time in seconds that a certain object is shown) to your needs. The upper ones are for the LightsOn object, the lower ones for the LightsOff object.

== Related content ==
* [[Howto: Lightmap|Lightmap effect]], allows for easy and nice looking lighting, without switching textures.

[[Category:Howto|Illuminate faces]]
[[Category:Scenery enhancement|Illuminate faces]]

Category:Scenery enhancement

2012-08-09T22:35:36Z

Popolon: /* = Technical concepts and experimental generation tools */

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

==== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ===
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces.
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Category:Scenery enhancement

2012-08-09T22:35:16Z

Popolon: /* Models = */

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

===== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ===
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces.
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Category:Scenery enhancement

2012-08-09T22:35:00Z

Popolon: /* Stubs */

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

===== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

==== Stubs ====
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ====
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces.
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Category:Scenery enhancement

2012-08-09T22:32:48Z

Popolon: /* Description of the content of the articles by categories */

'''Pages in this category still are at the bottom of the page'''

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

===== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

=== Stubs ===
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ====
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces.
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

Category:Scenery enhancement

2012-08-09T22:31:52Z

Popolon: describe brievly each article of this category in the goal of reorganize or at least to have a common page describing existing docs.

== Description of the content of the articles by categories ==
This part is probably temporary, to help reorganize documents about scenery enhancement. If you add Feel free to add the description of your page.

=== General scenery ===
* [[Next Generation Scenery]]: Brainstorm page about possible feature/enhancements in scenery (terrain, textures, LOD of the objects, etc...) and links to mailing list discussions and related projects & efforts.
* [[Tile Index Scheme]]: How work the scenery tile system and calculate the tile index.
* [[World Custom Scenery Project]]: ('''october, 16 2008 stub''') Tools used for the World Custom Scenery Project.

=== Terrain ===
* [[BTG file format]]: Description of the file format used in flightgear to describe terrains.
* [[CORINE to materials mapping]]: Table of relations between [[Coordination of Information on the Environment|Corine database]] and textures used in Flightgear.
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates.
* [[Experimental terrain generation with GRASS]] '''(WIP)''': About current (summer 2012) experiments using GRASS (Geographic Information System) for terrain generation.
* [[Geographic Coordinate Systems]]: Explaination of the WGS84 Ellipsoid systems used in Flightgear to compute coordinates.
* [[Howto:Create_custom_terrain]]: Create a custom shapefile to add custom scenery to FlightGear.
* [[Using TerraGear]]: How to use Terragear. ([[Fr/Utiliser TerraGear|french full translation]])
* [[TerraGear CORINE]]: How to use France Corine database, SRTM v4 datas and OSM to improve European terrain ([[Fr/TerraGear CORINE|french full translation]])

==== Terrain building tools ====
* [[Terragear]]: Building/installing Terragear ([[Es/TerraGear[spanish 3 lines translation]])
* [[TerraGear_Documentation]]: Description of Terragear toolchain, tool by tool.
* [[TerraGear_GUI]]: GUI to use Terragear toolchain. Installation and usage.

===== Technical concepts and experimental generation tools ====
* [[TerraGear support for transition polygons]]: Explanation of the new technique used for landclasses transitions in Terragear (for developers).
* [[TerraGear texmapped line data]]: About newconstruct, allowing to automatically mapping textures folliwing the line of roads, rivers and railways.

==== Terrain databases ====
* [[Coordination of Information on the Environment]] France Corine datavase, one of the sources of the flightgear terrain
* [[OpenStreetMap]], Can be used as source of terrain and some kind of scenery objects.

=== Airport ===
* [[About_Scenery/Airports]]: This article gives an introduction to the $FG_SCENERY/Airports folder.
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''lot of details about general object placement'')).
* [[Howto:Test your airport layout: quick and easy]]: Testing the airport
* [[Blender and BTG]]: Creating airports terrains BTG files with Blender.
* [[Howto:Animated jetways]]: Adding jetways (path connecting airplane to airport terminal gates) into airports, add informations requirement to aircraft models for using them.

==== Airport signs ====
* [[Blender Ground Signs Tutorial]]: Creating airport signs and adding them on the airport using Blender.
* [[Signs]]: Description of common airport signs and stg file signs syntax for adding them.

==== Heliport/helipad ====
* [[Howto:Make a helipad]] : Creating an helipad object, the apt.dat to define it as heliport, testing and distributing it.
* [[FlightGear User Created Helipad List]]: Raw list of helipads created by users (ICAO code and coordinates).

==== Airport design tools ====
* [[WorldEditor]]: State of the art X-plane apt.dat 850 format and better airport creation tool.
* [[TaxiDraw]]: Free taxiway editor for FlightGear and previously x-plane ('''Deprecated, use WorldEditor now''')
* [[AirportEditor]]: Java-based AI ground network editor for FlightGear
* [[FGSignMaker]]: is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate taxiway sign

=== Stubs ===
This articles are stubs, not modified since long time and should probaby be dispatched, if there are really interesting informations ? :
* [[Howto:Airport modeling]]: Stub (30 november 2010, marked as merget to [[Howto: Make an airport]] in april 2012) giving some simple tips about aiport modeling. Is it usefull ? Could be dispatched in relevent pages or replaced by a main page with existing articles as subsection''')
* [[Howto:Step-by-step_Scenery]]: Stub (january 29, 2012), some tips about creation, should
* [[Howto:Make an airport]]: '''little page with link to some relevant pages and good structure, could be a used as base for main guideline ?'''

=== Models ====
==== Creating or enhancing models ====
* [[Howto:Decrease_the_number_of_faces]]: Decrease the number of faces of the model to avoid slowdown Flightgear with non-visible details.
* [[Howto:Illuminate faces]]: How to make building or objects visible by night by illuminating their faces.
* [[Howto:Animate models]]: Add animation to a model using model description .xml files
* [[Howto:Nasal in scenery object XML files]]: Embed [[Nasal_scripting_language]] in object .xml description for interaction and animation.

===== Textures =====
* [[AC files: Basic changes to textures and colors]] How to change colors and textures of a model by editing model ac file.
* [[Howto:Texture a building]]: Texturing the differents elements of a building using UV maps with Blender and Gimp.
* [[Textures & Texture Maps in SketchUp]]: How to embed your own textures into a SketchUp (SU) model

===== Importing =====
* [[SketchUp to AC3D exporter]]: Tool converting objects from SketchUp (used in Google Earth) to AC3D. Installation and usage.

==== Populating scenery models ====
* [[Howto:Calculate elevations]]: Know the elevation of the ground at given coordinates (for placing an object).
* [[FlightGear Scenery Database]]: Overview of the FG Scenery database, statistiques and link to [http://scenemodels.flightgear.org/contribute.php guidelines] and [http://scenemodels.flightgear.org/submission/ online submission forms].
* [[Howto:Add shared models manually]]: Full process of adding existing shared model in scenery
* [[Howto:Convert objects from X-Plane]]: Convert ''X-Plane scenery objects'' and MS ® ''Flight Simulator scenery objects'' to FlightGear AC3D models format and STG models position files.
* [[Howto:Get a number of elevation offsets for a number of objects]]: Get (relative to ground) eleveation offset to reuse them when terrain change.
* [[OpenStreetMap_buildings]]: Building can be highly detailed in OSM, link to OSM buildings documentation and how-to (including existing tools) to convert them to flightgear scenery.
[[Howto:Place_3D_objects_with_the_UFO]]: Using the UFO flightgear airplane to interactivly place existing models in scenery ([[Fr/Placer des objets 3D avec UFO|french full translation]])
* [[Howto:Add details to your airport]]: Placing objects in airport (same than in other place), but with more airport specific signs placements (''The goal was airport builiding, but there is lot of details about general object placement and can be used to understand how to place models elsewhere'')).

[[Category:Modeling]]
[[Category:Scenery]]
[[Category:Development]]

TerraGear

2012-08-01T22:59:51Z

Popolon: /* Dependencies */ add links to several libs sites

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/Downloads/scenery.html official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resultion vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear-cs.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs!
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** libnewmat - at least version newmat11 (which is beta at the time of writing) See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for info on how to obtain and install it.
** gpc - See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] for info on how to obtain and install it.
** [http://pocoproject.org/ POCO] - For multicore support
** [http://www.gdal.org/ libgdal]
** [http://trac.osgeo.org/proj/ libproj]
** [http://ogdi.sourceforge.net/ libogdi]
** [http://epsilon-project.sourceforge.net/ libepsilon] - for ogr-decode
** libexpat
** Feel free to add more required libs here!

=== Building ===
Please, have a look at [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] and/or [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.cygwin;h=d0436ec0371dd9fa255a8a560a388818432600d6;hb=HEAD README.cygwin] of the terragear-cs sources.
./autogen.sh
./configure [options]
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install
<tt>./configure</tt> options:
--prefix=/path/to/install-dir
I am missing reliable data here. Please, revise/complete the list if you have more info!
--with-gdal=/path/to/gdal-config
--with-gpc=/path/to/libgenpolyclip.a
--with-newmat=/path/to/libnewmat.a
--with-plib=/path/to/libplib*.a
--with-simgear=/path/to/libsg*.a
--with-osg=/path/to/OSGinstallation

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear-cs</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu_64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]

TerraGear

2012-08-01T22:51:11Z

Popolon: /* Dependencies */

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/Downloads/scenery.html official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resultion vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear-cs.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs!
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** libnewmat - at least version newmat11 (which is beta at the time of writing) See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for info on how to obtain and install it.
** gpc - See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] for info on how to obtain and install it.
** POCO - For multicore support
** libgdal
** libproj
** libogdi
** libepsilon - for ogr-decode
** libexpat
** Feel free to add more required libs here!

=== Building ===
Please, have a look at [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] and/or [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.cygwin;h=d0436ec0371dd9fa255a8a560a388818432600d6;hb=HEAD README.cygwin] of the terragear-cs sources.
./autogen.sh
./configure [options]
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install
<tt>./configure</tt> options:
--prefix=/path/to/install-dir
I am missing reliable data here. Please, revise/complete the list if you have more info!
--with-gdal=/path/to/gdal-config
--with-gpc=/path/to/libgenpolyclip.a
--with-newmat=/path/to/libnewmat.a
--with-plib=/path/to/libplib*.a
--with-simgear=/path/to/libsg*.a
--with-osg=/path/to/OSGinstallation

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear-cs</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu_64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]