FlightGear wiki - User contributions [en]

FlightGear Newsletter April 2012

2012-04-25T04:18:47Z

Statto: /* Scenery corner */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

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

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===
==== Embraer 195 ====
A new [[Embraer 195]], developed by the group FGBr for Flightgear version 2.4 and 2.6 can soon be found at at: [http://www.grupofgbr.com.br grupofgbr.com.br].

[[File:Embraer - 195 em desenvolvimento (2)..jpg|400px]] [[File:Embraer - 195 em desenvolvimento..jpg|400px]]

[[File:Embraer - 195 em desenvolvimento (4)..jpg|400px]] [[File:Embraer - 195 em desenvolvimento (3)..jpg|400px]]

=== Updated aircraft ===
The Zivko Edge by Torsten Dreyer was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

[[MiG-21]]bis had a major update; 3D model is cleaned and remaped, new texture is added. Cockpit is remodeled and it has new instrument arangement. Aditional weapons are added with full [[Bombable]] support. Small fixes in FDM include more efficient flaps and hardpoint weights.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
[[File:Sea_Gulls_2.png|thumb|270px|Sea Gulls]]
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull.

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time? Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

=== Scenery Data ===
Data with the explicit use of being turned into FlightGear scenery has now been vectorized for almost all of California, western Oregon, parts of the Grand Canyon in Arizona, Las Vegas, Colorado, and northern New Mexico. This product is not yet available in terrain form, but represents good progress toward having nicer United States scenery data.

== Aircraft of the month ==

== Airport of the month ==
"Airport International Of Guarulhos (SBGR Sao Paulo)"

[[File:International_Airport_Of_Guarulhos.jpg|800px]]
[[File:International Airport Of Guarulhos (1).jpg|423px]][[File:International Airport Of Guarulhos (2).jpg|377px]]

International Airport Of Guarulhos In Sao Paulo City Brasil
In the site: www.grupofgbr.com.br

== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places. Please remember to categorise your file(s)!
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.
* A '''new editor''' provides a more extensive interface for editing articles online.
* '''Aircraft categories''' have been cleaned up and now match the categories on (the English) Wikipedia. Please see [[:Category:Aircraft]] for an overview of available categories, before categorising an aircraft article. ''No'' aircraft articles should be categorised in <code><nowiki>[[Category:Aircraft]]</nowiki></code>, use the subcategories instead!

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

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

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

Howto:Create custom terrain

2012-03-13T01:15:26Z

Statto: /* Working with QGIS */

'''Custom terrain''' in [[FlightGear]] is currently generated through processing shapefiles with [[TerraGear]]. In order to add custom scenery to FlightGear, you must create a custom shapefile.

A shapefile is a proprietary spatial information format. You can edit them with almost every GIS package. QGIS is quite a good package for this type of project.

Your goal for editing area data is to create a shapefile of a seamless layer of polygons which correspond to some type of land cover. This data is then fed into [http://mapserver.flightgear.org the mapserver] and, possibly, TerraGear to create new scenery.

=== Evaluating the current data ===
Before you begin, please make sure the area you want to improve doesn't already have good coverage. Just because it looks bad in FlightGear does not mean the area has not been improved. For this, you will need to check the Flightgear Mapserver, at [http://mapserver.flightgear.org/ mapserver.flightgear.org].

Let's take a look at the Finistère in Brittany, Western France: if you click [http://mapserver.flightgear.org/map/?lon=-4.41840585539649&lat=48.4484146908477&zoom=11&layers=0B000000FTTFFFFFTFT here], you will quickly see and understand how the Finistère county is known of FlightGear. Some towns/cities (red), a few forests (green), etc. Overall, it is not a very good resolution: a lot of angles, the detail level is not that good, some towns are missing. If you want a better definition on ground, there is some work to be done! The goal being to obtain something like this:

# [http://mapserver.flightgear.org/map/?lon=13.40385&lat=52.50199&zoom=11&layers=B0000000TFFFTFFFTFFFFFFF Berlin]
# [http://mapserver.flightgear.org/map/?lon=9.40368&lat=47.63699&zoom=11&layers=B0000000TFFFTFFFTFFFFFFF Bodensee surroundings]
# [http://mapserver.flightgear.org/map/?lon=-88.55704&lat=43.98436&zoom=11&layers=B0000000TFFFTFFFTFFFFFFF Oshkosh surroundings]
# [http://mapserver.flightgear.org/map/?lon=-62.87648&lat=17.69865&zoom=10&layers=B0000000TFFFTFFFTFFFFFFF Carribean Islands]

You will immediately notice the improvement to the ground. When flying, the difference is huge. Moreover, this enables the autogeneration of cities, trees, farmland, and so on.

=== Downloading the Landsat pictures ===
[[File:C31e36f2a2cbb278a1603dfe2ba91193.media.395x288.png|thumb|200px|Landsat Map Search]]
[[File:1c9334d970963364b5ce1bc3a166a4fa.media.426x192.png|thumb|200px|Preview and download Landsat image]]
Browse to [http://glcfapp.glcf.umd.edu:8080/esdi/index.jsp the Earth Science Data Interface interface] to grab your [http://en.wikipedia.org/wiki/Landsat Landsat] data.

# Click ''Map Search''.
# Tick the ETM+ box (left column).
# Click on ''Update Map'' on the right bottom of the map.
# Click on the ''Place'' tab on the upper side of the map, in order to do a search by place, or you can do a search by latitude/longitude.
# In the Place field, type ''Amsterdam, Netherlands'' for instance.
# Now click the button with the mouse and the small + sign. This will allow you to select image tiles. Select all images that cover your area of interest, in our example this is just one image.
# Click on ''Preview and download''. This bring you to a selection page were you can choose what image you want to download. It is likely that there are pictures available from different dates for your area. Picking the most recent one is best, for known reasons.
# Clicking the ID will not bring you directly to the download page, first you have to click the ''Download'' button.
# Download the _nn80.tif.gz file (if this is not available, try an older image). Note that Landsat images are separated in different bands. Band 1/2/3/4/5/7 have 30m/Pixel resolution while band 8 (_nn80.tif.gz) has 15 meters per pixel.
# Uncompress the ''.tif.gz'' files in the directory of your choice.

=== Working with QGIS ===
[[File:QGIS_texel_1.png|thumb|200px|QGIS with the TIFF image.]]
[[File:QGIS_texel_2.png|thumb|200px|Creating the class column.]]
[[File:QGIS_texel_3.png|thumb|200px|Toggle editing.]]
[[File:QGIS_texel_4.png|thumb|200px|Tracing the small island.]]
[[File:QGIS_texel_5.png|thumb|200px|The finished small island polygon.]]
Using a GIS software gives you the opportunity to realize a full range of interesting operations: modification of map data, updates on the ground classification, etc.

* QGIS Download for Linux/OSX/Windows [http://www.qgis.org/en/download/current-software.html]

The following is largely adapted from the [http://stattosoftware.com/flightgear/tutorial/index.html original QGIS scenery tutorial], which you may find of use.
# Launch QGIS.
# Click on <tt>Layer > Add a Raster layer</tt>.
# Modify the filter to search for *.tif files.
# Add the TIFF file you have just downloaded.
# Rightclick on the image in the layer sidebar and choose <tt>Set layer CRS</tt>, to select a projection model. This depends on the location of the area you're about to create. Look up your project's UTM coordinate through [http://upload.wikimedia.org/wikipedia/commons/e/ed/Utm-zones.jpg this image]. For Texel this is 31U, north of the equator, so we choose <tt>Projected Coordinate Systems > Universal Transverse Mercator (UTM) > WSG84 / UTM zone 31N</tt>. Always select 'WGS84', as that is the globe model used in FlightGear.
# Click on <tt>Layer > New > New Shapefile Layer</tt> or on the corresponding icon. A dialog should pop up.
## Make sure the vector type is set to polygon.
## Click the 'specify CRS' button, to select a projection model. This must be the same as we did for the tiff background image.
## You need to create a data column for this layer. Create a new attribute called 'class'. Make sure it is a 'text data' (string) column. Add it to the attribute list.
## The 'OK' button should now be available for you to select. Select 'OK'.
## There should be a dialog box prompting you to save your vector layer. Save it in your scenery directory with your GeoTIFF. (This is not required but significantly helps organization.)
# Your vector layer should appear in the left-hand toolbar. You are ready to begin digitizing.
# Select the newly created layer in the layer list, toggle editing (<tt>Layer > Toggle Editing</tt>) and finally select Capture Polygon from the same menu/toolbar.
# With your mouse, left-click on a point at the southwestern edge of the small island.
# We now want to trace the outline of the island. Move your mouse to another point below the first point and click it again. Your mouse should show a red line. The points should not be redundant - for instance, as long as the line between two points is straight, there is no need for another point in between the two.
# You will want to digitize features in a circular manner to avoid problems. You can always go back and add points later. With this in mind, move your mouse to a third point on the island. A small triangle should form, representing the polygon which would result if you decided you were done with the polygon.
# Continue outlining the island by clicking along its shoreline. When you are on your last point, instead of left-clicking, right-click. QGIS will finish the polygon.
# A dialog box will pop up, asking you to type in the value for 'class'. Since this is a shoal, existing of just sand, type in ''Sand''. This step is important - it is how you know what each polygon should be mapped to in our finished scenery. A list of "allowed" materials (and thus classes) is available [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail here].

Continue with tracing all shapes on the island: towns, industrial areas, grass, farmland etc.

===Snapping===
It is very important to enable "snapping" now.

Snapping means each polygon will fit together nicely, like a jigsaw puzzle. If snapping is not enabled, the polygons will not form a continuous layer, which has a number of different problems.

We don't want small holes in our scenery, nor do we want overlapping polygons. Snapping adjusts each point as you go by - you will miss occasionally and have to correct it - so you don't have to worry about lining the polygons up precisely.

# Open <tt>Settings > Snapping Options</tt>.
# Click the tickbox(es) in front of your layer(s) and set Tolerance to 20 (map units). A smaller tolerance will make it easier to work with very small and detailed layers, while a bigger value makes it easier to snap when zoomed out.
# Click OK to save the snapping options.

==== Distinguishing Land Class Types from LANDSAT data ====
You may Google Maps or Yahoo Maps running alongside your program to see what is what on the black/white image, but most areas are recognizable without use of the software. If you need help determining what part of the black-and-white image, please currently refer to the [http://stattosoftware.com/flightgear/tutorial/index.html#distinguishing original Stattosoftware Scenery Tutorial]. Instead of determining in a single band image you can also combine different ETM+ bands in a RGB file. Some information about different band combinations can be found here [http://web.pdx.edu/~emch/ip1/bandcombinations.html].

=== Exporting the shapefile ===
In order to turn the landclass into scenery we have to split it into seperate shapefiles for each landclass.

# Open the Attribute table (<tt>Layer > Open Attribute Table</tt>).
# Type "Sand" (or another class) into the search box and press the Search button. This will select all polygons that have the Sand class assigned.
# Go to <tt>Layer > Save Selection as vector file</tt> and save the sand shapefile somewhere on your computer.
# Do the same for all other classes.
# To make the difference between land and sea (landmass) we save the entiry shapefile (<tt>Layer > Save as...</tt>, ESRI Shapefile).

If you want to see these shapefiles integrated into the Custom Scenery database you can contact papillon81 and statto (through IRC or Forum). Please be remembered that your data has to be derived from freely available (public domain) sources. Other material can not be integrated due to legal issues.

=== Generating scenery ===
Please continue with [[TerraGear]] to generate the landclass into useable scenery.

== External links ==
* [http://www.custom-scenery.org Terragear-cs website]
* [http://wiki.qgis.org QGIS Wiki]
* [http://www.flightgear.org/forums/viewforum.php?f=5 Dedicated FlightGear forums for scenery enhancement]
* [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail OSGEO Wiki]

=== Resources ===
* [http://stattosoftware.com/flightgear/tutorial/index.html Tutorial by John Holden]
[[fr:Howto: Utilisé QGIS et images satellites]]

[[Category:Howto|Using QGIS and satellite pictures]]
[[Category:Scenery enhancement|Using QGIS and satellite pictures]]

FlightGear Newsletter April 2011

2011-04-24T00:23:06Z

Statto:

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

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

== Development news ==
=== Atmospheric scattering shader ===
Zan has been working very hard on an experimental atmospheric scattering [[shader]]. The shaders makes use of [http://sponeil.net/ Sean O'Neil's algorithm]. Altough there are some issues with the shader, it looks like it will have a promising future! Some screenshots are available at the forum thread [http://www.flightgear.org/forums/viewtopic.php?f=47&t=11274#p117813].

The shader does some simplifications, but basically tries to recreate physical phenomenom, so the look could be easily modified depending on environmental conditions. But since the values are not so easy to figure out, some testing would be needed for creating nice looking sky for misty weather, rainy weather, cold winter etc. After that, proper equations could be written to transform weather values to scattering parameters.

The shader is not production ready, it has some bugs and terrain (especially fog at horizon) does not match the looks of the skydome. This is a work in process, but might take some times, because the terrain shader is much harder than the skydome shader.

== Nasal for newbies ==
== New software tools and projects ==

== FlightGear addons and mods ==
== In the hangar ==
=== New instruments ===
The [[Boeing 777-200ER]]'s chronometer has been moved to the generic instruments directory (<tt>Aircraft/Instruments-3d/chronometer</tt>). This allows aircraft developers to easily implement this clock in their aircraft. All related Nasal code was included in the model xml file, so there's really just one file to be linked to! Some aircraft already make use of this clock, including the [[Boeing 747-400]] and [[Boeing 757-200|757-200]].

There are several advantages in moving instruments to the generic directory, some of which are:
* Easy to be re-used in other aircraft, all you need to do is link to (and position) the model and on some instruments link to a Nasal file.
* If someone extents the functionality of a generic instrument, it will be automatically extended in all the aircraft that use it.

=== New aircraft ===
=== Vostok-1 ===
[[Image:Vostok-1-Carrier-News.png|thumb|Vostok-1 Carrier]]
[[Image:Vostok-1-News.png|thumb|Vostok-1 Spacecraft]]
[[Image:Vostok-1-Interior-News.png|thumb|Vostok-1 Interior]]
To celebrate Yury Gagarin's historical flight, [[Vostok-1]] carrier and spacecraft were added to FlightGear. In heavy development still, it already allows full orbital flight from lift-off to landing, making it perform the first spaceflight in FlightGear.

Things that make it possible:
*[[JSBSim]] centrifugal force addition made the whole flight available.
*JSBSim property driven point masses, tanks and engines, and aerodynamic coefficients implementation allow stages changing. Each single stage of the flight has an independent mass scheme, propulsion system, and aerodynamics reactions, so simulation is more or less realistic.
*Datcom+ with "little wing" approach resolves carrier and spacecraft aerodynamics accurately enough to make flights on real fuel and oxidizer capacities with real g forces, orbit and deorbit paths.
*[[FlightGear Newsletter April 2011#Atmospheric scattering shader|Zan's shader]] makes the earth look pretty enough from high altitudes.
*FG improvement shifted practical flight ceiling from 80 to 160 kilometers.

In real life, the first human spaceflight was fully automated. In FlightGear, instead controls are completely manual to make it interesting, and to make you understand how it really works.

Authors and developers, since orbital flight is possible in FlightGear from now on, you are invited to make a FlightGear driven Mercury-Atlas project. Low earth orbit flights can be more exact and eyecandy in FlightGear than in any current simulator. And you can be sure it will be free for you and users in any case.

=== Doctor Who TARDIS ===
[[Image:Tardis colour.png|thumb|Doctor Who TARDIS]]
Vinura has started work on developing a [http://en.wikipedia.org/wiki/TARDIS#The_Doctor.27s_TARDIS Doctor Who TARDIS] for FlightGear. The exterior model is almost complete in SketchUp. Click [http://www.flightgear.org/forums/viewtopic.php?f=4&t=11738 here] for the development thread.

Currently, I still need to get the TARDIS colours right as I am only allowed to use 'Named Colours' from Google SketchUp as they can't claim copyright on colours.

=== Updated aircraft ===

=== Liveries ===
[[Image:Fgfs-screen-089.png|thumb|SriLankan Airlines' Boeing 767]]
Some [http://liveries.flightgear.org/airlines.php?id=231 SriLankan Airlines] liveries have been made by Vinura for the [[Boeing 767]] and [[Airbus A320]].

== Scenery corner ==
=== Terrain Creation ===
There are a couple different ways of creating shapefiles for terrain. Here is an overview and hopefully it will help those understand the scenery process a little bit better.

==== Create the shapefiles by hand ====
This method has been used for St. Maarten in the World Scenery or Rio de Janeiro custom scenery. In this way, you download a satellite photo or an aerial photo and create the shapefiles by hand by "drawing" on top of the photo.

==== Create the shapefiles using land cover data ====
Land cover data can be either vector like CORINE or raster like NOAA. However if the files are raster you will have to convert them into vector using a similar way described below. European CORINE scenery and most large-scale custom United States scenery such as Hawai'i or the Pacific Northwest were created using available third-party land cover data.

==== Create the land cover data yourself ====
There is Switzerland land cover data available for both Bodensee and for most of Switzerland which has been created using land cover classification techniques. In this scenery, the developer takes a satellite photo and, using raster manipulation software such as GRASS, manually classifies each pixel in the satellite as a land cover type. After refining the data, the data is turned into a vector format and cleaned again, removing oddities such as cloud cover. This is probably the most difficult type of scenery to create, but can cover a large area most efficiently.

A mix of the last two approaches is usually the most beneficial unless you are using an end-product such as CORINE. For instance, in the new Pacific Northwest sceneries, there are some oddities where rivers start falling under 30m wide. These need to be fixed by hand and then merged which can be a time-consuming process.

If you have any questions about creating your own land cover scenery feel free to ask on the forums.

=== New terrain ===
New third-party scenery for the USA's Pacific Northwest (Seattle and Portland, OR) and Rio de Janeiro is now available for download at http://www.stattosoftware.com/flightgear

=== New buildings ===
Once again, there are new Eastern Asian buildings !

* Saigon Center - Ho Chi Minh City - Vietnam
* Mode Gakuen Coccoon Tower - Tokyo - Japan
* Trade Tower - Seoul - South Korea
* Koryo Hotel - Pyongyang - North Korea
* The Center - Hong Kong - China
* Central Plaza - Hong Kong - China
* Citic Plaza - Guangzhou - China
* Menara Telekom - Kuala Lumpur - Malaysia

=== Airports ===
The generic Concourse C at KDEN was recently replaced with a much better, realistic working model featuring animated jetways. Please enjoy.

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==
SriLankan Airlines livery on an Airbus A320 taken at dusk.

[[File:Fgfs-screen-085.png|600px]]

== Suggested flights ==
Departing from Brisbane International Airport and heading towards Sydney International Airport at a heading of about 203, you will come across some beautiful scenery.
<gallery>
Image:Fgfs-screen-020.png
Image:Fgfs-screen-016.png
Image:Fgfs-screen-012.png
</gallery>

== Aircraft reviews ==

=== '''''The Good old Cessna Citation X''''' ===
I hope to do a monthly review of a specific aircraft. I can't guarantee that I will get to do it every month though because I do have other stuff to attend to.

The [[Cessna Citation X]] is by far one of my favourite little planes! Its reaction time is quite quick. The rudder control is very responsive, even the slightest move of your rudder pedals or the mouse and the aircraft's rudder moves. It accelerates quite fast down the runway, building up momentum and then, you lift your joystick up slightly and the nose lifts up just like you want it to.

Regarding the animations, they are extraordinary. They function quite well like for example the flaps, spoilers or the landing gear. The cockpit is quite well designed and has a lot of instruments, just like a real Citation would.

It has a tutorial system built in for people wanting to fly one. '''''This was the first jet plane that I could actually land properly in.''''' It also has several nice camera views, including views from the passenger seats.

<gallery>
Image:Cessna Citation X Cockpit.png
Image:Cessna Citation X Passenger View 1.png
Image:Cessna Citation X Passenger View 2.png
Image:Cessna Citation X - Screenshot 2.png
</gallery>

'''Recommendation:'''

I would recommend this plane to people who have already flown planes like the [[Cessna C172P]] or the [[Piper J3 Cub]] and want to progress into Jet aviation. This is a GREAT little starter plane to get you going.

This has to be one of the best planes that I have ever used in FlightGear!

Thanks for reading! :D

'''''Review By: Vinura'''''

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

== Community news ==
=== FlightGear on youtube ===

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===
==== FlyingClub Mayday 1 ====
The FGFC '''"Mayday 1: Manitoba Rescue"''' operation was held April 2nd, 2011 at CYAV, Winnipeg/St.Andrews, with seven pilots participating. The scenario stated two of Manitoba's major rivers were flooding, and people were stranded along both, so STOL and helicopter pilots were mustered at CYAV, received assignments from ATC, planned their flights, and notified ATC when they were ready to proceed. A total of twenty missions were assigned, sixteen of which were successfully completed in the space of three hours.

The scenario was based around the idea that pilots should have basic skills in addition to merely flying with an autopilot, and was designed to test both their actual flying ability by not having airports at their destinations, and providing no actual navigational data beyond a map or two. They were required to map their routes in territory unknown to them, then fly those routes in their chosen aircraft, land, report in, then return to CYAV to complete a "cycle." Points were awarded for cycle completion, and points deducted for aircraft crashes. FG Seg faults were not penalized.

Comments back about the operation from pilots have so far been positive. Watch the [http://www.flightgear.org/forums/viewforum.php?f=10&sid=381d9860a9183d143cd2fa8aee16099d Multiplayer Forums] for the next one; there will be one, but at this writing, it has not yet been decided.

* [[FlightGear Flying Club]]
* [http://flightgearfans.wordpress.com/about/ FGFC WordPress Site ]
* [http://www.flightgear.org/forums/viewtopic.php?f=10&t=11551 Mayday 1 Forum Pages]

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

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

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

=== Did you know ===
*...that you can fly backwards in a UFO? While holding the brake button down on your joystick or keyboard, increase engine throttle and you should start to fly backwards. A short video can be seen at [http://www.youtube.com/watch?v=F7U1bsO7g-EYouTube]

[[Category:FlightGear Newsletter|2011 04]]

FlightGear Newsletter April 2011

2011-04-07T19:38:53Z

Statto: /* Scenery corner */

FlightGear Newsletter April 2011

2011-04-04T02:28:13Z

Statto: /* Scenery corner */

FlightGear Newsletter March 2011

2011-03-30T22:46:59Z

Statto: /* Airport of the month */

{{newsletter}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== FlightGear events ==

== Development news ==

=== Local Weather v1.0 ===

After more than a year of development work, the Local Weather package has reached its full design functionality as described in [[A local weather system]] and is available for download as [http://www.phy.duke.edu/~trenk/files/local_weather_fgfsGITv1.0.tgz version 1.0]. The package works with Flightgear 2.0.0 and higher, though some extensions (marked with [GIT]) require a more recent binary.

Version 1.0 offers the following features:

* numerous types of clouds from Cirrus to Cumulonimbus, arranged in realistic patterns and size distributions, visible up to 80 km distance
* weather phenomena tied to location: rain only underneath clouds, dense clouds obscure sunlight [GIT], convective clouds develop according to terrain
* spatial interpolation of weather parameters like pressure, temperature, visibility, wind
* effect volumes controlling short-range turbulence, rain, snow, visibility and shadow [GIT]
* terrain-dependent modeling of boundary layer winds, gusts and turbulence
* complete offline weather system involving different airmass types and weather fronts
* integration of online METAR data [GIT]
* full support for soaring [GIT], thermals are automatically generated by the convective system
* optional dynamics: clouds drift in the wind, convective clouds are generated and decay, properties of thermals evolve in time
* backward compatibility to Flightgear 2.0.0

A feature gallery:
<gallery>
Image:local_weather_1.00_05.jpg| Realistic skies with multiple cloud types
Image:local_weather_1.00_06.jpg| Various different types of weather and clouds
Image:local_weather_1.00_11.jpg| Soaring beneath Cumulus clouds
Image:local_weather_1.00_12.jpg| Use both thermal and ridge lift
Image:local_weather_1.00_01.jpg| Stratocumulus layers
Image:local_weather_1.00_03.jpg| Cirrocumulus sheets
Image:local_weather_1.00_02.jpg| Altostratus layers
Image:local_weather_1.00_04.jpg| Dense Stratus obscuring the sunlight
Image:local_weather_1.00_07.jpg| Evening light...
Image:local_weather_1.00_09.jpg| ... and morning light
Image:local_weather_1.00_10.jpg| Multiple 3d cloud layers
Image:local_weather_1.00_08.jpg| Heavy rain
</gallery>

Fun facts:

* lines of Nasal code: 10135
* estimated coffee consumption during coding: 120 l
* estimated time spent watching and photographing the sky: 50 h

== Nasal for newbies ==
== New software tools and projects ==

=== Modeling a UAV with FlightGear and YASim ===
[[File:Blender-res.png|thumb]]
FlightGear can be a great tool for aerospace engineering. Here is an example of using the [[YASim]] physics engine in FlightGear to model a real world UAV based on the actual mass and geometry and performance of the airframe. There is a [[Blender]] plugin that can be used to visualize and validate the geometric data of the model. Once the simulation model is tuned and flying well, FlightGear can be used to do do simple design variation tests and predict how those changes will affect the stability of the design.

For more information: [http://www.flightgear.org/blogs/curt/uas/resolution/simulation-modelling/ Using FlightGear + YASim to model and test real world UAV]

== FlightGear addons and mods ==
== In the hangar ==
=== New aircraft ===

==== DG-101G ====
A new glider, the [[Glaser-Dirks DG-101G|DG-101G]] from Glaser-Dirks, has been added to Git. It utilizes a [[JSBSim]] FDM, tuned with data calculated with XFLR5. This model features winch start, aerotowing, a drag robot, water ballast and [[livery over MP]].

==== BK 117====
[[File:Fgfs-screen-221.jpg|thumb|Showing the exterior of the BK117.]]
Work on the BK117 helicopter has been started. The BK117 is a twin-engined medium utility–transport helicopter, produced in a coproduction between MBB/Eurocopter and Kawasaki. It uses the same rigid rotor system like Bo105, but is larger in size and has more power.
It is quite common in the world and very often used by emergency services and law enforcements.

The model features a realistic FlightDynamicModel based and calculated from NASA-reports, a detailed 3d-model with normalmap and reflection shaders, detailed rotor (thanks to Melchior!) and will be dynamically configurable in many variants.
It is planned to make it realistic as it can be and good or even better than the Ec130 B4.

Next steps are the interior modeling with a detailed 3d-cockpit.
Please follow the process in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=11431#p118700 the forum].

=== Updated aircraft ===

[[File:Nordstern-elevator-station.jpg|thumb|The elevator control station of the Zeppelin LZ 121 ''Nordstern''.]]
====LZ 121 ''Nordstern''====
The Zeppelin [[Zeppelin LZ 121 Nordstern|LZ 121 ''Nordstern'']] has been updated with a new gas and ballast control board by Anders.

====Concorde TCAS====
Chris (papillon81) took care of the Concorde's TCAS and converted it to the new generic system by ThorstenB. The old Concorde-specific one was implemented using NASAL and xml and he got rid of about 1800 LOC in the process. He also created a new glass instrument (the only one in the Concorde's cockpit), modeled according to some web sources. The new system works with both AI and multiplayer traffic.

=== Livery database reaches 400 ===
This month the [http://liveries.flightgear.org/ FlightGear livery database] welcomed its 400th livery! A big thank you to all those artists that contributed over the past two years. A special thank you is justified for [http://liveries.flightgear.org/authors.php?id=4 gooneybird], who saw his 150th livery commited this month, making him by far the top-contributer!

If you'd like to help us reach the 500 milestone, please see [[Howto: Edit a livery]] and/or the dedicated [http://flightgear.org/forums/viewforum.php?f=13 section of our forum].

== Scenery corner ==
[[File:Burj al Arab Dubai.png|thumb|270px|Burj al Arab, with one of the [[FlightGear Newsletter March 2010#Dubai is coming up|palm islands]] in the background.]]
One of world's most famous landmarks, the Taj Mahal in India, is now modeled and included in the scenery database. Dubai also welcomed a new model, the famous hotel Burj al Arab.

==== Eastern Asia ====
A bunch of new Asian buildings is added, including:
* Two International Finance Centre - Hong Kong - China
* International Commerce Center - Hong Kong - China
* Shanghai World Finance Center - Shanghai - China
* Jin Mao Tower - Shanghai - China
* Tuntex Sky Tower - Kaohsiung - Taïwan
* Northeast Asia Trade Tower - Incheon - South Korea
* 63 Building - Seoul - South Korea
* N Seoul Tower - Seoul - South Korea

=== Airports ===

== Full scale 747 simulator ==
As you might know, John Wojnaroski has been working for several years on a full-scale 747 simulator, powered by FlightGear. Recently he published two videos, showing the current status of the sim. Recent developments were focused on a panoramic display.
* [http://www.flickr.com/photos/61165268@N06/5570921779/ Low-flying through the San Andreas fault]
* [http://www.flickr.com/photos/61165268@N06/5572306558/ Landing at KSFO]

The projectors are (3) short throw 1200x800 native resolution units, mounted on the ceiling. Each projector is first mechanically aligned using the projector test pattern. Next a warping mesh based on projector location and screen dimensions is created and a test pattern using the mesh is produced by FlightGear. The warping mesh is then adjusted to tune the resultant image thrown on the screen as well as mechanical adjustments. And as a final step the "production" image is adjusted by setting the viewing heading for the side projectors for horizontal alignment and projector internals and mesh recalculations for the vertical as required.

The image warping software is contained in the CameraGroup.cxx based on the [[OSG]] code for a spherical panoramic display. Tim Moore adapted the source to run with the FlightGear camera group and I extended it to display a warping mesh for a cylindrical panoramic display. There is a stand alone utility to create a mesh warping file that can be tailored for each projector and is loaded at FG init time.

The edge blending is accomplished using gray scale polygons as textures. Further refinement is required to adjust the gamma function to handle pixel brightness based on RGB color values. The slight image flickering is an artifact of the projector and video camera sync mismatches and not observable by the human eye. The videos don't really capture the immersive quality of the wrap-around screen or sensation of motion.

The FG hosting machine is a quad-core Intel I5 with 4GB memory and three nVidia 9400GT graphics. Running FG on a single core produces a frame rate of 28fps using SDL and around 30fps with glut-3.7 with [[3D clouds]] enabled. A higher frame rate of 60-65fps is possible running three instances of fgfs on each core and using the internal localhost socket; however you lose the ability to sync features such as [[AI traffic]], clouds, or [[multiplayer]] aircraft.

More info and pictures about the build process are available at [http://www.lfstech.com John's website] and the [http://flightgear.org/Projects/747-JW/ FlightGear website].

== Aircraft of the month ==

== Airport of the month ==
Martin State Airport (KMTN) north of Baltimore, Maryland may be the best airport in FlightGear you've never heard of.

Make sure you have the object file downloaded, and if you don't have the Baltimore/Washington custom scenery, head over and download the terrain from [[User:statto|statto's]] FlightGear website. Install this properly and you are set to have a quality VFR flight experience!

To start out do a touch-and-go on runway 31. Start your turn over the pattern near the Anne Arundel Mall (a big asphalt blob in the middle of the farmland), then come in over the handcrafted terrain of the harbor.

For a cross-country flight, fly down Baltimore Harbor toward the well-modeled Baltimore-Washington Int'l Airport, then follow the railway and freeway past College Park. Overfly RFK Stadium and the Washington National Mall before turning and landing at Washington National Airport (KDCA).

The custom models combined with the custom scenery really sets this part of the world apart from the default areas in FlightGear - have a flight over Maryland today!

== Screenshot of the month ==

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

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

== Community news ==

=== FlightGear on YouTube ===
* [http://www.youtube.com/watch?v=lab-5tZOf-o Sim's video] features a nice aerobatic show, performed with a [[P-51D Mustang]].

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===

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

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

=== Call for volunteers ===
The [[OpenRadar]] project is looking for a new maintainer.

The [[TerraGear GUI]] project is looking for programmers to help create a GUI frontend for [[TerraGear]] [http://flightgear.org/forums/viewtopic.php?f=5&t=7485#p102005].

The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter|2011 03]]

User:Statto

2011-03-30T22:41:54Z

Statto: Created page with "Check out FlightGear custom scenery at !"

Check out FlightGear custom scenery at !

FlightGear Newsletter January 2011

2011-01-24T21:50:37Z

Statto: /* Suggested flights */

FlightGear Newsletter January 2011

2011-01-24T21:11:17Z

Statto: /* Scenery corner */

FlightGear Newsletter January 2011

2011-01-19T21:12:19Z

Statto: /* Scenery corner */

Next newsletter

2011-01-09T20:24:19Z

Statto: Forgot to change the year!

#REDIRECT[[FlightGear Newsletter January 2011]]

Next newsletter

2011-01-09T20:23:24Z

Statto: Changed redirect to January

#REDIRECT[[FlightGear Newsletter January 2010]]

Understanding FlightGear Scenery

2011-01-07T08:05:49Z

Statto:

If you want to develop scenery for FlightGear, great! FlightGear needs as much help as possible with modeling the world. This article is designed for someone who is interesting in creating FlightGear scenery for the first time and is meant to explain how FlightGear manages scenery and what quirks or nuances you need to know in order to best contribute.

==How Scenery is Generated==
There are three main types of data which make up FlightGear scenery - airports, objects and terrain.

All Airports and Terrain are generated using the [[TerraGear]] software. The vast majority of objects can be placed dynamically, using either the UFO aircraft model, or by finding the latitude and longitude of the object and placing it manually through text files.

All scenery which is included in the main FlightGear database should be derived from either license-free data or data which there is implicit permission to use. For instance, using USGS imagery, LANDSAT satellite imagery, or even Yahoo! Maps is okay for placing models or checking coordinates of airport runways. However, the FlightGear scenery project is copyright aware and typically does not accept objects or terrain created from copyrighted data, including, unfortunately, Google. (Yahoo! Maps has told OpenStreetMap deriving coordinates from their map data is not a copyright issue.) If you have a question about your source, do not hesitate to [http://flightgear.org/forums ask on the forum].

==How Scenery is Stored==
FlightGear manages scenery through a folder hierarchy representing square degrees for both Objects and Terrain. The purpose of separating scenery tiles by degree is to allow easy internet distribution and to provide boundaries for the generation of terrain, so polygons do not just go on for miles.

This means you need to know where your scenery project is in longitude and latitude. For instance, San Francisco's airport can be found under the folder w123n37.

==The Basic Format==
The /Scenery folder for FlightGear contains three subfolders - Airports, Objects and Terrain.

===Airports===
This folder contains various .xml files for the airports you have downloaded. You do not need to edit these!

If you are interested in contributing airport data, you will want to use [[TaxiDraw]]. Unfortunately TaxiDraw is not very robust at the moment, but it works. As of January 2010, FlightGear uses an older version of the X-Plane airport data. The kind people over at [http://scenemodels.flightgear.org the Scenery Model Database] accept updated airports in the X-Plane 8.10 format.

Because of the FlightGear feature which allows airports to undulate, or change elevation, all airports must be regenerated using [[TerraGear]] once [[TaxiDraw]] has been used.

===Objects===
Objects are possibly the easiest sceneries to create for FlightGear. All you need is to create an .ac model and place it using the ufo or manually using co-ordinates. You can also create an .xml file to create animations.

Objects are stored in a global database, the [http://scenemodels.flightgear.org/ FlightGear Scenery Model Database]. Once you have modeled your building, please make sure to send it into the database, as this is how your work gets distributed! Your work will be available to [[TerraSync]] users shortly after it is added.

Please note there is a difference between SHARED and STATIC objects. SHARED objects are objects which are included within the whole scenery, regardless of where you are. STATIC objects are specific objects, which appear a limited number of times (usually once) in the scenery. For instance, a house created to be auto-generated scenery would be a SHARED model, while the model of the tallest skyscraper in the country would be a STATIC model. SHARED models are typically to be avoided unless you know what you are doing, as they are loaded into memory when FlightGear starts up.

* [Howto:_Place_3D_objects_with_the_UFO]
* [Howto:_Add_shared_models_manually]

===Terrain===

Understanding FlightGear Scenery

2011-01-07T07:56:27Z

Statto: first edit

If you want to develop scenery for FlightGear, great! FlightGear needs as much help as possible with modeling the world. This article is meant to explain how FlightGear manages scenery and what quirks or nuances you need to know in order to best contribute.

==How Scenery is Generated==
There are three main types of data which make up FlightGear scenery - airports, objects and terrain.

All Airports and Terrain are generated using the [[TerraGear]] software. The vast majority of objects can be placed dynamically, using either the UFO aircraft model, or by finding the latitude and longitude of the object and placing it manually through text files.

All scenery which is included in the main FlightGear database should be derived from either license-free data or data which there is implicit permission to use. For instance, using USGS imagery, LANDSAT satellite imagery, or even Yahoo! Maps is okay for placing models or checking coordinates of airport runways. However, the FlightGear scenery project is copyright aware and typically does not accept objects or terrain created from copyrighted data, including, unfortunately, Google. (Yahoo! Maps has told OpenStreetMap deriving coordinates from their map data is not a copyright issue.) If you have a question about your source, do not hesitate to [http://flightgear.org/forums ask on the forum].

==How Scenery is Stored==
FlightGear manages scenery through a folder hierarchy representing square degrees for both Objects and Terrain. This is to allow scenery

==The Basic Format==
The /Scenery folder for FlightGear contains three subfolders - Airports, Objects and Terrain.

===Airports===
This folder contains various .xml files for the airports you have downloaded. You do not need to edit these!

If you are interested in contributing airport data, you will want to use [[TaxiDraw]]. Unfortunately TaxiDraw is not very robust at the moment, but it works. As of January 2010, FlightGear uses an older version of the X-Plane airport data. The kind people over at [http://scenemodels.flightgear.org the Scenery Model Database] accept updated airports in the 8.10 format.

Because of the FlightGear feature which allows airports to undulate, or change elevation, all airports must be regenerated using [[TerraGear]] once [[TaxiDraw]] has been used.

===Objects===

===Terrain===

Howto:Create custom terrain

2011-01-07T07:40:42Z

Statto:

Custom terrain in FlightGear is currently generated through processing shapefiles with [[TerraGear]]. In order to add custom scenery to FlightGear, you must create a custom shapefile.

A "shapefile" is a proprietary spatial information format. You can edit them with almost every GIS package. QGIS is quite a good package for this type of project.

Your goal for editing area data is to create a shapefile of a seamless layer of polygons which correspond to some type of land cover. This data is then fed into the mapserver and, possibly, TerraGear to create new scenery.

===Evaluating the current data===
Before you begin, please make sure the area you want to improve doesn't already have good coverage. Just because it looks bad in FlightGear does not mean the area has not been improved. For this, you will need to check the Flightgear Mapserver, at [http://mapserver.flightgear.org/ mapserver.flightgear.org].

Let's take a look at the Finistère in Brittany, Western France: if you click [http://mapserver.flightgear.org/map/?lon=-4.41840585539649&lat=48.4484146908477&zoom=11&layers=0B000000FTTFFFFFTFT here], you will quickly see and understand how the Finistère county is known of [[FlightGear]]. Some towns/cities (red), a few forests (green), etc. Overall, it is not a very good resolution: a lot of angles, the detail level is not that good, some towns are missing. If you want a better definition on ground, there is some work to be done! The goal being to obtain something like this:

#[http://mapserver.flightgear.org/map/?lon=13.40385&lat=52.50199&zoom=11&layers=000000BFFFFFFFFFTFFF Berlin]
#[http://mapserver.flightgear.org/map/?lon=9.40368&lat=47.63699&zoom=11&layers=B000000FFFFFFFFFTFFF Bodensee surroundings]
#[http://mapserver.flightgear.org/map/?lon=-88.55704&lat=43.98436&zoom=11&layers=000000BFFFFFFFFFTFFF Oshkosh surroundings]
#[http://mapserver.flightgear.org/map/?lon=-62.87648&lat=17.69865&zoom=10&layers=B000000FFFFFFFFFTFFF Carribs]

You will immediately notice the improvement to the ground. When flying, the difference is huge. Moreover, this enables the autogeneration of cities, trees, farmland, and so on.

=== Downloading the Landsat pictures ===
[[File:C31e36f2a2cbb278a1603dfe2ba91193.media.395x288.png|thumb|200px|Landsat Map Search]]
[[File:1c9334d970963364b5ce1bc3a166a4fa.media.426x192.png|thumb|200px|Preview and download Landsat image]]
Browse to [http://glcfapp.umiacs.umd.edu:8080/esdi/index.jsp the Earth Science Data Interface interface] ([http://glcfapp.glcf.umd.edu:8080/esdi/index.jsp mirror]) to grab your [http://en.wikipedia.org/wiki/Landsat Landsat] data.

# Click ''Map Search''.
# Tick the ETM+ box (left column).
# Click on ''Update Map'' on the right bottom of the map.
# Click on the ''Place'' tab on the upper side of the map, in order to do a search by place, or you can do a search by latitude/longitude.
# In the Place field, type ''Amsterdam, Netherlands'' for instance.
# Now click the button with the mouse and the small + sign. This will allow you to select image tiles. Select all images that cover your area of interest, in our example this is just one image.
# Click on ''Preview and download''. This bring you to a selection page were you can choose what image you want to download. It is likely that there are pictures available from different dates for your area. Picking the most recent one is best, for known reasons.
# Clicking the ID will not bring you directly to the download page, first you have to click the ''Download'' button.
# Download the _nn80.tif.gz file (if this is not available, try an older image). Note that Landsat images are separated in different bands. Band 1/2/3/4/5/7 have 30m/Pixel resolution while band 8 (_nn80.tif.gz) has 15 meters per pixel.
# Uncompress the ''.tif.gz'' files in the directory of your choice.

=== Working with QGIS ===
[[File:QGIS_texel_1.png|thumb|200px|QGIS with the TIFF image.]]
[[File:QGIS_texel_2.png|thumb|200px|Creating the class column.]]
[[File:QGIS_texel_3.png|thumb|200px|Toggle editing.]]
[[File:QGIS_texel_4.png|thumb|200px|Tracing the small island.]]
[[File:QGIS_texel_5.png|thumb|200px|The finished small island polygon.]]
Using a GIS software gives you the opportunity to realize a full range of interesting operations: modification of map data, updates on the ground classification, etc.

* QGIS Download for Linux/OSX/Windows [http://www.qgis.org/en/download/current-software.html]

The following is largely adapted from the [http://stattosoftware.com/flightgear/tutorial/index.html original QGIS scenery tutorial], which you may find of use.
# Launch QGIS.
# Click on <tt>Layer > Add a Raster layer</tt>.
# Modify the filter to search for *.tif files.
# Add the TIFF file you have just downloaded.
# Click on <tt>Layer > Add a new vector layer</tt> or on the corresponding icon. A dialog should pop up.
#* Make sure the file type is an ESRI Shapefile.
#* Make sure the vector type is set to polygon.
#* You need to create a data column for this layer. Create a column called 'class'. Make sure it is a string column. Add it to the attribute list by selecting the Add Values Manually button. The 'OK' button should now be available for you to select. Select 'OK'.
#* There should be a dialog box prompting you to save your vector layer. Save it in your scenery directory with your GeoTIFF. (This is not required but significantly helps organization.)
#* A projection box should pop up. Select 'WGS 1984'. After all, that is the globe model used in FlightGear.
# Your vector layer should appear in the left-hand toolbar. You are ready to begin digitizing.
#Select the newly created layer in the layer list, toggle editing (<tt>Layer > Toggle Editing</tt>) and finally select Capture Polygon from the same menu/toolbar.
# With your mouse, left-click on a point at the southwestern edge of the small island.
# We now want to trace the outline of the island. Move your mouse to another point below the first point and click it again. Your mouse should show a red line. The points should not be redundant - for instance, as long as the line between two points is straight, there is no need for another point in between the two.
# You will want to digitize features in a circular manner to avoid problems. You can always go back and add points later. With this in mind, move your mouse to a third point on the island. A small triangle should form, representing the polygon which would result if you decided you were done with the polygon.
# Continue outlining the island by clicking along its shoreline. When you are on your last point, instead of left-clicking, right-click. QGIS will finish the polygon.
# A dialog box will pop up, asking you to type in the value for 'class'. Since this is a shoal, existing of just sand, type in ''Sand''. This step is important - it is how you know what each polygon should be mapped to in our finished scenery. A list of "allowed" materials (and thus classes) is available [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail here].

Continue with tracing all shapes on the island: towns, industrial areas, grass, farmland etc.

It is imporant to enable "snaping" now. We don't want small holes in our scenery, nor do we want overlapping polygons. Snapping adjusts each point as you go by - you will miss occasionally and have to correct it - so you don't have to worry about lining the polygons up precisely.

# Open <tt>Settings > Project Properties</tt> and click the Snapping options... button.
# Click the tickbox(es) in front of your layer(s) and set Tolerance to 20 (map units). A smaller tolerance will make it easier to work with very small and detailed layers.
# Click OK to save the snapping options.

====Distinguishing Land Class Types from LANDSAT data====
You may Google Maps or Yahoo Maps running alongside your program to see what is what on the black/white image, but most areas are recognizable without use of the software. If you need help determining what part of the black-and-white image, please currently refer to the [http://stattosoftware.com/flightgear/tutorial/index.html#distinguishing original Stattosoftware Scenery Tutorial]. Instead of determining in a single band image you can also combine different ETM+ bands in a RGB file. Some information about different band combinations can be found here [http://web.pdx.edu/~emch/ip1/bandcombinations.html].

===Exporting the shapefile===
In order to turn the landclass into scenery we have to split it into seperate shapefiles for each landclass.

# Open the Attribute table (<tt>Layer > Open Attribute table</tt>).
# Type "Sand" (or another class) into the search box and press the Search button. This will select all polygons that have the Sand class assigned.
# Go to <tt>Layer > Save Selection as Shapefile</tt> and save the sand shapefile somewhere on your computer.
# Do the same for all other classes.
# To make the difference between land and sea (landmass) we save the entiry shapefile (<tt>Layer > Save as Shapefile</tt>).

We have been working with UTM coordinates so far. To generate scenery that can be used in FlightGear we need to convert the shapefiles to the latitude/longitude format.

* '''Windows'''
*# Download [http://www.forestpal.com/fgis.html fGIS] and install it as described.
*# Open an empty project and visit <tt>Utilities > Shapefile Projection Utility</tt>.
*# Look up your projects UTM coordinate through [http://upload.wikimedia.org/wikipedia/commons/e/ed/Utm-zones.jpg this image]. For Texel this is 31U, so we choose UTM31 in fGIS. If your project is located south of the equator, you tick the S box.
*# Set the Output Shapefile Project to <tt>Lat./Lon.</tt>.
*# Now click the Input Shapefile button to load the shapefile that we exported from QGIS.
*# Using the Output Shapefile button we decide where we want to store the lat/lon shapefile. This has to be a non-exisiting file, so remove before updating.
*# Click the Convert button.
*# Repeat this process for all shapefiles.

If you want to see these shapefiles integrated into the Custom Scenery database you can contact papillon81 and statto (through IRC or Forum). Please be remembered that your data has to be derived from freely available (public domain) sources. Other material can not be integrated due to legal issues.

===Generating scenery===
Please continue with [[TerraGear]] to generate the landclass into useable scenery.

== External links ==
* [http://www.custom-scenery.org Terragear-cs website]
* [http://wiki.qgis.org QGIS Wiki]
* [http://www.flightgear.org/forums/viewforum.php?f=5 Dedicated FlightGear forums for scenery enhancement]
* [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail OSGEO Wiki]

===Resources===
* [http://stattosoftware.com/flightgear/tutorial/index.html Tutorial by John Holden]

[[Category:Howto|Using QGIS and satellite pictures]]
[[Category:Scenery enhancement|Using QGIS and satellite pictures]]

[[fr:Howto: Utilisé QGIS et images satellites]]

Scenery

2011-01-07T07:28:08Z

Statto:

'''Scenery''' is the landscape in [[FlightGear]] (or any other simulator). The default version of FlightGear comes with 2 square degrees of scenery near San Francisco, California. The rest of the world is also available via download. Details and accuracy vary from place to place.

The scenery data is released as [[World Scenery]] collections, available through download in 10x10 degree chunks from the the FlightGear website. FlightGear users may also use [[TerraSync]], which downloads new scenery areas as you fly.

Some high-quality third-party scenery has also been released for FlightGear. However, because anyone may contribute models or terrain data to the official FlightGear scenery, third-party scenery add-ons are not as common as in other flight simulator projects.

==Recommended Scenery==
* [[Developed Airports]] - airports with at least one non-generic airport building placed
* [[Suggested Airports]] - airports ranked by scenery quality

==Scenery Projects==
* [[Brest]]
* [[Dublin (Scenery)|Dublin]]
* [[FlightGear NL]]
* [[Germany]]
* [[Custom France Scenery]]
* [http://gitorious.org/papillon81 papillon81's git repository for scenery (Frankfurt, Singapore)]

''See also [[FlightGear related projects]]

==See also==
* [[Landmark Wish List]]
* [[FlightGear Scenery Designer]]
* [[Installing Scenery]]
* [[Next Generation Scenery]]
* [[Image:Worldscenery-text.jpg]]

==External links==
* http://www.flightgear.org/Downloads/scenery-0.9.10.html
* http://www.flightgear.org/Downloads/scenery-1.0.0.html
* http://www.flightgear.org/Downloads/scenery-1.0.1.html

{{Terra}}

[[Category:Scenery]]

[[es:Escenario]]
[[fr:Scenery]]

Scenery

2011-01-07T07:27:29Z

Statto: rewrote this page to make it more descriptive and hopefully help more people

'''Scenery''' is the landscape in [[FlightGear]] (or any other simulator). The default version of FlightGear comes with 2 square degrees of scenery near San Francisco, California. The rest of the world is also available. Details and accuracy vary from place to place.

The scenery data is released as [[World Scenery]] collections, available through download in 10x10 degree chunks from the the FlightGear website. FlightGear users may also use [[TerraSync]], which downloads new scenery areas as you fly.

Some high-quality third-party scenery has also been released for FlightGear. However, because anyone may contribute models or terrain data to the official FlightGear scenery, third-party scenery add-ons are not as common as in other flight simulator projects.

==Recommended Scenery==
* [[Developed Airports]] - airports with at least one non-generic airport building placed
* [[Suggested Airports]] - airports ranked by scenery quality

==Scenery Projects==
* [[Brest]]
* [[Dublin (Scenery)|Dublin]]
* [[FlightGear NL]]
* [[Germany]]
* [[Custom France Scenery]]
* [http://gitorious.org/papillon81 papillon81's git repository for scenery (Frankfurt, Singapore)]

''See also [[FlightGear related projects]]

==See also==
* [[Landmark Wish List]]
* [[FlightGear Scenery Designer]]
* [[Installing Scenery]]
* [[Next Generation Scenery]]
* [[Image:Worldscenery-text.jpg]]

==External links==
* http://www.flightgear.org/Downloads/scenery-0.9.10.html
* http://www.flightgear.org/Downloads/scenery-1.0.0.html
* http://www.flightgear.org/Downloads/scenery-1.0.1.html

{{Terra}}

[[Category:Scenery]]

[[es:Escenario]]
[[fr:Scenery]]

Suggested airports

2011-01-07T07:21:41Z

Statto:

Here you will find Airports that are well developed and/or have an outstanding scenery. Thus they are "suggested" especially to be visited and/or used for Multi-player events like FlyIns, TGA, ATC, etc..
 
If you are searching for the '''development-status of Airports''' see the wiki [[Developed Airports]].
 For further suggestions see [[Suggested Scenery]] and [[Suggested Flights]]
 
The overall Airport-Rating (column "R") is based on the TerraSync-Status of the following characteristics:
{| border="0"
|-
! style="text-align:center"| * !!style="text-align:left"|     superior surrounding landscape - although the airport itself is not (yet) developed accordingly
|-
! style="text-align:center"| ** !!style="text-align:left"|     complex modeling of buildings
|-
! style="text-align:center"| *** !!style="text-align:left"|     complex modeling of buildings, taxiways, and aprons
|-
! style="text-align:center"| **** !!style="text-align:left"|     extensive modeling of airport and landscape and/or city
|}
 
Further columns to watch for are:
*'''S = Size:''' L= all aircraft, M= midium size aircraft, S= for small aircraft
*'''FGCOM:''' If available one FGCOM frequency is given, followed by the amount of the total available FGCOM frequencies
*'''Parking:''' amount of pre-defined Parking-Lots (otherwise see: [[Initial_Starting_Positions]])
*'''R/I:''' amount of runways and ILS (e.g. KROC has 3 runway: 04/22 has each 1 ILS, 10/28 has only one ILS on 28, 07/25 has no ILS)
 
{| class="wikitable sortable" border="0" cellspacing="0"
! width="40" | ICAO
! width="130" | Name
! width="80" | Country
! width="80" | Continent
! width="30" | R
! width="30" | S
! width="100" | FGCOM
! width="50" | Parking
! width="40" | R/I
! class="unsortable" style="background:#efefef" | Comment|
|-
| BKPR || Pristina || Kosovo || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 || very nice scenery
|-
| CYVR || Vancouver || Canada || America ||align="center"| * ||align="center"| L ||align="center"| 125.650 (6) ||align="center"| many ||align="center"| 5/5 || nice area
|-
| EDDF || [[Frankfurt am Main Airport|Frankfurt am Main]] || Germany || Europe || align="center" | **** || align="center" | L || align="center" | 127.320 (6) || align="center" | many ||align="center"| 2-4 || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown
|-
| EDDH || [[Hamburg_Airport|Hamburg]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 126.850 (7) ||align="center"| -- ||align="center"| 2/4 || Fully modeled, plus unique buildings downtown|-
|-
| EDDI || [[EDDI|Berlin Tempelhof]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 118.100 (10) ||align="center"| 1 ||align="center"| 2/0 || Fully modeled, especially also the City
|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (4) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled
|-
| EDDP || [[Leipzig/Halle_Airport|Leipzig]] || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.100 (5) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]
|-
| EDDT || [[Berlin_Tegel_Airport|Berlin Tegel]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.700 (11) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]
|-
| EDDV || [[EDDV|Hannover]] || Germany || Europe ||align="center"| * ||align="center"| L ||align="center"| 120.170 (3)) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled
|-
| EDDW || Bremen || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.500 (7) ||align="center"| -- ||align="center"| 2/2 || very nicely modeled
|-
| EDVE || Braunschweig || Germany || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.350 (2) ||align="center"| -- ||align="center"| 2/1 ||
|-
| EEKE || Kuressaare || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 ||
|-
| EFHF || Helsinki-Malmi || Finland || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 ||
|-
| EFHK || Helsinki || Finland || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.700 (5) ||align="center"| -- ||align="center"| 3/5 || Nice terminal and city landmarks
|-
| EEPU || Parnu || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU
|-
| EETN || Tallinn || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/2 || Nice triangle EETN-EETU-EEPU
|-
| EETU || Tartu || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU
|-
| EGFF || Cardiff || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 125.00 (3) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGGP || Liverpool || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.350 (4) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGGW || Luton || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.720 (6) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGKA || Shoreham || UK || Europe ||align="center"| *** ||align="center"| S ||align="center"| 125.400 (3) ||align="center"| -- ||align="center"| 3/0 ||
|-
| EGKK || London-Gatwick || UK || Europe ||align="center"| **** ||align="center"| M ||align="center"| 124.220 (8) ||align="center"| 6 ||align="center"| 1/2 ||
|-
| EGLL || London-Heathrow || UK || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.500 (14) ||align="center"| 3 ||align="center"| 2/4 ||
|-
| EGPH || Edinburgh || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (4) ||align="center"| -- ||align="center"| 2/2 ||
|-
| EGSH || Norwich || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 124.250 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| EHAM || Amsterdam || Netherlands || Europe ||align="center"| **** ||align="center"| L ||align="center"| 119.220 (1) ||align="center"| many ||align="center"| 6/6 ||One of the best modeled airports in the FlightGear world
|-
| EHEH || Eindhoven || Netherlands || Europe ||align="center"| ** ||align="center"| M ||align="center"| 131.000 (6) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EHLE || Eindhoven || Netherlands || Europe ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| 1 ||align="center"| 2/1 ||
|-
| EHVK || Volkel || Netherlands || Europe ||align="center"| ** ||align="center"| L ||align="center"| 123.170 (1) ||align="center"| many ||align="center"| 2/2 ||
|-
| EIDW || Dublin || Ireland || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.600 (7) ||align="center"| -- ||align="center"| 3/3 ||
|-
| ENAL || Alesund || Norway || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.100 (4) ||align="center"| -- ||align="center"| 1/1 ||
|-
| ENSD || Alesund || Norway || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||
|-
| ENVA || Trondheim || Norway || Europe ||align="center"| *** ||align="center"| L ||align="center"| 122.100 (6) ||align="center"| -- ||align="center"| 2/2 ||
|-
| ESPG || Göteborg || Sweden || Europe ||align="center"| ** ||align="center"| M ||align="center"| 129.100 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| FACT || Cape Town || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/2 ||nice area
|-
| FAJS || Johannisburg || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 121.900 (3) ||align="center"| many ||align="center"| 2/3 ||high (5000), in mountains
|-
| GCFV || Fuerteventura || Gran Canaria || Africa ||align="center"| * ||align="center"| L ||align="center"| 119.200 (4) ||align="center"| 9 ||align="center"| 1/1 ||nice island area
|-
| KABQ || Albuquerque || USA NM || America ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 ||
|-
| HECA || Cairo || Egypt || Africa ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 || near pyramids
|-
| KATL || Atlanta || USA GA || America ||align="center"| * ||align="center"| L ||align="center"| 119.550 (4) ||align="center"| many ||align="center"| 3/4 ||
|-
| KAUS || Austin || USA TX || America ||align="center"| *** ||align="center"| L ||align="center"| 121.00 (10) ||align="center"| -- ||align="center"| 2/4 ||
|-
| KBWI || Baltimore || USA MD || America ||align="center"| *** ||align="center"| L ||align="center"| 119.400 (10) ||align="center"| -- ||align="center"| 4/6 ||
|-
| KCGS || College Park || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| 119.850 (3) ||align="center"| -- ||align="center"| 2/0 ||
|-
| KDCA || Reagan National || USA VA || America ||align="center"| *** ||align="center"| M ||align="center"| 120.750 (7) ||align="center"| -- ||align="center"| 3/2 ||
|-
| KDEN || Denver || USA CO || America ||align="center"| ** ||align="center"| L ||align="center"| 133.300 (16) ||align="center"| -- ||align="center"| 6/12 ||
|-
| KDTW || Detroit || USA MI || America ||align="center"| ** ||align="center"| L ||align="center"| 118.400 (15) ||align="center"| -- ||align="center"| 6/8 ||
|-
| KFHR || Friday Harbor || USA WA || America ||align="center"| * ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||
|-
| KHAF || Half Moon Bay || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 122.800 (2) ||align="center"| 4 ||align="center"| 1/0 ||nice area - near KSFO
|-
| KHWD || Hayward || USA CA || America ||align="center"| ** ||align="center"| S ||align="center"| 122.500 (10) ||align="center"| 9 ||align="center"| 2/1 ||nice area - near KSFO
|-
| KIAD || Washington-Dulles || USA VA || America ||align="center"| * ||align="center"| L ||align="center"| 120.100 (14) ||align="center"| many ||align="center"| 4/3 ||
|-
| KIND || Indianapolis || USA IN || America ||align="center"| *** ||align="center"| L ||align="center"| 127.820 (7) ||align="center"| -- ||align="center"| 3/6 ||
|-
| KJAN || Jackson-Evers || USA MS || America ||align="center"| *** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 2/2 ||
|-
| KJFK || John F. Kennedy || USA NY || America ||align="center"| **** ||align="center"| L ||align="center"| 119.100 (18) ||align="center"| many ||align="center"| 4/5 ||
|-
| KLAS || Las Vegas || USA NV || America ||align="center"| **** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 4/3 || terminal and some casinos modeled
|-
| KLAX || Los Angeles || USA CA || America ||align="center"| *** ||align="center"| L ||align="center"| 133.900 (7) ||align="center"| many ||align="center"| 4/8 ||
|-
| KLSV || Nellis Air Force || USA NV || America ||align="center"| *** ||align="center"| L ||align="center"| 132.550 (6) ||align="center"| -- ||align="center"| 2/1 ||
|-
| KLWD || Lewistown || USA MT || America ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||
|-
| KMTN || Martin State || USA MD || America ||align="center"| ** ||align="center"| M ||align="center"| 121.300 (4) ||align="center"| -- ||align="center"| 2/2 || airport and terrain modeled
|-
| KNID || China Lake Naval || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 120.150 (2) ||align="center"| -- ||align="center"| 3/0 ||
|-
| KNUQ || Moffett Federal AFLD || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 119.550 (6) ||align="center"| -- ||align="center"| 2/2 ||
|-
| KOAK || Oakland || USA CA || America ||align="center"| ** ||align="center"| L ||align="center"| 127.200 (7) ||align="center"| many ||align="center"| 4/3 ||
|-
| KORD ||Chicago O'Hare || USA IL || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| many ||align="center"| 7/14 ||
|-
| KOSH || Wittman Rgl. || USA WI || America ||align="center"| ** ||align="center"| M ||align="center"| 118.500 (4) ||align="center"| -- ||align="center"| 4/1 ||
|-
| KOXB || Ocean City Muni. || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||
|-
| KPDX || Portland || USA OR || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 3/5 ||
|-
| KPHX || Phoenix || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 120.900 (6) ||align="center"| -- ||align="center"| 3/5 || most skyscrapers modeled
|-
| KRDU || Raleigh || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (12) ||align="center"| many ||align="center"| 3/4 ||nice for flying east-coast
|-
| KRNO || Reno/Tahoe || USA NZ || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (7) ||align="center"| -- ||align="center"| 3/2 ||High in Clouds
|-
| KSAN || San Diego || USA AZ || America ||align="center"| * ||align="center"| M ||align="center"| 118.300 (7) ||align="center"| many ||align="center"| 1/2 ||Interesting area at boarder to mexico
|-
| KSEA || Seattle Tacoma || USA WA || America ||align="center"| ** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 3/5 || basic terminal model, some skyscrapers modeled
|-
| KSFO || San Francisco || USA CA || America ||align="center"| **** ||align="center"| L ||align="center"| 120.500 (7) ||align="center"| many ||align="center"| 4/3 ||FGFS Default -- overcrowded
|-
| KSLC || Salt Lake City || USA UT || America ||align="center"| * ||align="center"| L ||align="center"| 118.300 (13) ||align="center"| -- ||align="center"| 4/6 ||very high in clouds (4227 ft)
|-
| KSJC || San Jose || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 124.00 (7) ||align="center"| 14 ||align="center"| 3/2 ||Bay-area near KSFO
|-
| LDZU || Udbina || Croatia || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||interesting airport high in Mountains - no ILS
|-
| LFFE || Enghien Moisselles || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| --- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just north of Paris
|-
| LFML || Marseille || France || Europa ||align="center"| * ||align="center"| M ||align="center"| 118.370 (4) ||align="center"| many ||align="center"| 2/2 ||Mediterranean coast
|-
| LFPG || Paris Charles de Gaulle || France || Europa ||align="center"| **** ||align="center"| L ||align="center"| 123.600 (23) ||align="center"| -- ||align="center"| 4/8 ||very detailed city of Paris near by
|-
| LFPH || Chelles Le Pin || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just south of Paris
|-
| LFPL || Lognes Emerainville || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||nice little airport just south of Paris
|-
| LFPO || Paris Orly || France || Europa ||align="center"| **** ||align="center"| M ||align="center"| 120.500 (13) ||align="center"| -- ||align="center"| 3/5 ||the older airport at Paris
|-
| LFPZ || St-Cry'Ecole || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little airport just west of Paris
|-
| LFRJ || Landivisiau || France || Europa ||align="center"| ** ||align="center"| M ||align="center"| 119.700 (2) ||align="center"| -- ||align="center"| 1/1 ||Naval Base
|-
| LFSB || Basel-Mulhouse || Swiss || Europa ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (7) ||align="center"| -- ||align="center"| 3/0 ||
|-
| LHBP || Budapest || Hungaria || Europa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/4 ||in-midst the typical Puszta-area
|-
| LILN || Venegono || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| 128.550 (1) ||align="center"| -- ||align="center"| 1/0 ||
|-
| LILV || Valbrembo || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||recreation area: Mountains, tennis, pool, etc.
|-
| LIMC || Milano Malpensa || Italy || Europa ||align="center"| *** ||align="center"| L ||align="center"| 119.000 (11) ||align="center"| -- ||align="center"| 2/3 ||
|-
| LIME || Bergamo || Italy || Europa ||align="center"| * ||align="center"| M ||align="center"| 120.500 (5) ||align="center"| -- ||align="center"| 2/1 ||nice mountain area
|-
| LIML || Milano Limate || Italy || Europa ||align="center"| *** ||align="center"| M ||align="center"| 119.250 (5) ||align="center"| -- ||align="center"| 2/1 ||
|-
| LQSA || Sarajewo || Bosnia || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.250 (3) ||align="center"| -- ||align="center"| 1/1 ||very nice mountain region: LQSA, LYTV, LYPG
|-
| LOWI || Innsbruck || Austria || Europe ||align="center"| **** ||align="center"| M ||align="center"| 120.100 (3) ||align="center"| -- ||align="center"| 1/1 || very nice and difficult approach, wonderful scenery
|-
| LROP || Bucharest || Romania || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.850 (3) ||align="center"| -- ||align="center"| 2/4 ||
|-
| LSGS || Sion || Swiss || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.217 (5) ||align="center"| -- ||align="center"| 1/1 ||Wonderful surrounded by high mountains
|-
| LSZH || Zürich-Kloten || Swiss || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.800 ||align="center"| many ||align="center"| 3/4 ||very nice mountain/lake area
|-
| LSZB|| Bern-Belp || Swiss || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.020 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| PANC|| Anchorage || USA Alaska || America ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (9) ||align="center"| -- ||align="center"| 3/3 ||interesting area
|-
| LYBE || Belgrad || Serbia || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 ||
|-
| LYPG || Podgorica || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.200 (2) ||align="center"| -- ||align="center"| 2/1 || very nice mountain region: LQSA, LYTV, LYPG
|-
| LYTV || Tivat || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.000 (1) ||align="center"| -- ||align="center"| 1/1 || very nice mountain region: LQSA, LYTV, LYPG
|-
| MUHA || Havana || Cuba || America ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 1/1 ||nice for island-hopping
|-
| NZAA || Auckland || New Zealand || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.700 ||align="center"| many ||align="center"| 2/2 ||nice for island-hopping
|-
| OMAA || Abu Dahbi || United AE || Asia ||align="center"| * ||align="center"| L ||align="center"| 119.200 ||align="center"| many ||align="center"| 1/2 ||interesting area
|-
| OOMS || Seeb || United AE || Asia ||align="center"| * ||align="center"| M ||align="center"| 118.400 (5) ||align="center"| many ||align="center"| 2/2 ||nice sea/mountain area
|-
| PHNL || Honolulu || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| 123.900 (5) ||align="center"| many ||align="center"| 4/2 ||wonderful island scenery
|-
| PHOG || Kahului || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| ||align="center"| ||align="center"| 2/1 ||wonderful island scenery
|-
| RJTT || Tokyo || Japan || Asia ||align="center"| **** ||align="center"| L ||align="center"| 126.200 (6) ||align="center"| -- ||align="center"| 3/3 ||interesting area
|-
| RKSI || Seoul || South Korea || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (6) ||align="center"| -- ||align="center"| 2/4 ||
|-
| RPLL || Manila || Philipines || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||
|-
| TDPD || Melville Hall || Dominica || America ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||nice area
|-
| TFFF || Le Lamentin || Martinique || America ||align="center"| *** ||align="center"| M ||align="center"| 118.500 (5) ||align="center"| -- ||align="center"| 1/1 ||nice area
|-
| TFFG || Grand Case || Anguilla || America ||align="center"| ** ||align="center"| S ||align="center"| 128.940 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TIST || Cyril E King || Virgin Islands || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 ||nice area
|-
| TJSJ || San Juan || Puerto Rico || America ||align="center"| *** ||align="center"| M ||align="center"| 132.050 (6) ||align="center"| -- ||align="center"| 2/2 ||nice area
|-
| TKPK || Saint Kitts || Guadeloupe || America ||align="center"| ** ||align="center"| M ||align="center"| 118.300 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TNCM || Princess Juliana || ST Maarten || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (2) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TQPF || Wallblake || Anquilla || America ||align="center"| ** ||align="center"| S ||align="center"| 18.500 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| VIDP || New Dehli || India || Asia ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (5) ||align="center"| many ||align="center"| 2/3 ||nice area
|-
| VHHH || Hong Kong || China || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.400 (16) ||align="center"| many ||align="center"| 2/4 ||very nice mountain/sea area
|-
| WSSS || Singapore Changi || Singapore || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.600 (8) ||align="center"| many ||align="center"| 2/3 ||
|-
| YBAS || Alice Springs || Australia NT || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.300 (2) ||align="center"| 26 ||align="center"| 3/1 ||Australian Back-Country
|-
| YPDN || Darwin || Australia NT || Australia ||align="center"| * ||align="center"| M ||align="center"| 133.100 (8) ||align="center"| many ||align="center"| 2/1 ||
|-
| YSCB || Canberra || Australia NSW || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.700 (5) ||align="center"| many ||align="center"| 2/1 ||High Mountain region (1800 ft)
|-
| YSSY || Sydney || Australia NSW || Australia ||align="center"| * ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||
|-
|}

Suggested airports

2011-01-07T07:20:51Z

Statto:

Here you will find Airports that are well developed and/or have an outstanding scenery. Thus they are "suggested" especially to be visited and/or used for Multi-player events like FlyIns, TGA, ATC, etc..
 
If you are searching for the '''development-status of Airports''' see the wiki [[Developed Airports]].
 For further suggestions see [[Suggested Scenery]] and [[Suggested Flights]]
 
The overall Airport-Rating (column "R") is based on the TerraSync-Status of the following characteristics:
{| border="0"
|-
! style="text-align:center"| * !!style="text-align:left"|     superior surrounding landscape - although the airport itself is not (yet) developed accordingly
|-
! style="text-align:center"| ** !!style="text-align:left"|     complex modeling of buildings
|-
! style="text-align:center"| *** !!style="text-align:left"|     complex modeling of buildings, taxiways, and aprons
|-
! style="text-align:center"| **** !!style="text-align:left"|     extensive modeling of airport and landscape and/or city
|}
 
Further columns to watch for are:
*'''S = Size:''' L= all aircraft, M= midium size aircraft, S= for small aircraft
*'''FGCOM:''' If available one FGCOM frequency is given, followed by the amount of the total available FGCOM frequencies
*'''Parking:''' amount of pre-defined Parking-Lots (otherwise see: [[Initial_Starting_Positions]])
*'''R/I:''' amount of runways and ILS (e.g. KROC has 3 runway: 04/22 has each 1 ILS, 10/28 has only one ILS on 28, 07/25 has no ILS)
 
{| class="wikitable sortable" border="0" cellspacing="0"
! width="40" | ICAO
! width="130" | Name
! width="80" | Country
! width="80" | Continent
! width="30" | R
! width="30" | S
! width="100" | FGCOM
! width="50" | Parking
! width="40" | R/I
! class="unsortable" style="background:#efefef" | Comment|
|-
| BKPR || Pristina || Kosovo || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 || very nice scenery
|-
| CYVR || Vancouver || Canada || America ||align="center"| * ||align="center"| L ||align="center"| 125.650 (6) ||align="center"| many ||align="center"| 5/5 || nice area
|-
| EDDF || [[Frankfurt am Main Airport|Frankfurt am Main]] || Germany || Europe || align="center" | **** || align="center" | L || align="center" | 127.320 (6) || align="center" | many ||align="center"| 2-4 || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown
|-
| EDDH || [[Hamburg_Airport|Hamburg]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 126.850 (7) ||align="center"| -- ||align="center"| 2/4 || Fully modeled, plus unique buildings downtown|-
|-
| EDDI || [[EDDI|Berlin Tempelhof]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 118.100 (10) ||align="center"| 1 ||align="center"| 2/0 || Fully modeled, especially also the City
|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (4) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled
|-
| EDDP || [[Leipzig/Halle_Airport|Leipzig]] || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.100 (5) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]
|-
| EDDT || [[Berlin_Tegel_Airport|Berlin Tegel]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.700 (11) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]
|-
| EDDV || [[EDDV|Hannover]] || Germany || Europe ||align="center"| * ||align="center"| L ||align="center"| 120.170 (3)) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled
|-
| EDDW || Bremen || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.500 (7) ||align="center"| -- ||align="center"| 2/2 || very nicely modeled
|-
| EDVE || Braunschweig || Germany || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.350 (2) ||align="center"| -- ||align="center"| 2/1 ||
|-
| EEKE || Kuressaare || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 ||
|-
| EFHF || Helsinki-Malmi || Finland || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 ||
|-
| EFHK || Helsinki || Finland || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.700 (5) ||align="center"| -- ||align="center"| 3/5 || Nice terminal and city landmarks
|-
| EEPU || Parnu || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU
|-
| EETN || Tallinn || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/2 || Nice triangle EETN-EETU-EEPU
|-
| EETU || Tartu || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU
|-
| EGFF || Cardif || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 125.00 (3) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGGP || Liverpool || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.350 (4) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGGW || London Luton || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.720 (6) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGKA || Shoreham || UK || Europe ||align="center"| *** ||align="center"| S ||align="center"| 125.400 (3) ||align="center"| -- ||align="center"| 3/0 ||
|-
| EGKK || London Gatwick || UK || Europe ||align="center"| **** ||align="center"| M ||align="center"| 124.220 (8) ||align="center"| 6 ||align="center"| 1/2 ||
|-
| EGLL || London Heathrow || UK || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.500 (14) ||align="center"| 3 ||align="center"| 2/4 ||
|-
| EGPH || Edinburgh || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (4) ||align="center"| -- ||align="center"| 2/2 ||
|-
| EGSH || Norwich || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 124.250 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| EHAM || Amsterdam || Netherlands || Europe ||align="center"| **** ||align="center"| L ||align="center"| 119.220 (1) ||align="center"| many ||align="center"| 6/6 ||One of the best modeled airports in the world
|-
| EHEH || Eindhoven || Netherlands || Europe ||align="center"| ** ||align="center"| M ||align="center"| 131.000 (6) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EHLE || Eindhoven || Netherlands || Europe ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| 1 ||align="center"| 2/1 ||
|-
| EHVK || Volkel || Netherlands || Europe ||align="center"| ** ||align="center"| L ||align="center"| 123.170 (1) ||align="center"| many ||align="center"| 2/2 ||
|-
| EIDW || Dublin || Ireland || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.600 (7) ||align="center"| -- ||align="center"| 3/3 ||
|-
| ENAL || Alesund || Norway || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.100 (4) ||align="center"| -- ||align="center"| 1/1 ||
|-
| ENSD || Alesund || Norway || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||
|-
| ENVA || Trondheim || Norway || Europe ||align="center"| *** ||align="center"| L ||align="center"| 122.100 (6) ||align="center"| -- ||align="center"| 2/2 ||
|-
| ESPG || Göteborg || Sweden || Europe ||align="center"| ** ||align="center"| M ||align="center"| 129.100 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| FACT || Cape Town || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/2 ||nice area
|-
| FAJS || Johannisburg || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 121.900 (3) ||align="center"| many ||align="center"| 2/3 ||high (5000), in mountains
|-
| GCFV || Fuerteventura || Gran Canaria || Africa ||align="center"| * ||align="center"| L ||align="center"| 119.200 (4) ||align="center"| 9 ||align="center"| 1/1 ||nice island area
|-
| KABQ || Albuquerque || USA NM || America ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 ||
|-
| HECA || Cairo || Egypt || Africa ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 || near pyramids
|-
| KATL || Atlanta || USA GA || America ||align="center"| * ||align="center"| L ||align="center"| 119.550 (4) ||align="center"| many ||align="center"| 3/4 ||
|-
| KAUS || Austin || USA TX || America ||align="center"| *** ||align="center"| L ||align="center"| 121.00 (10) ||align="center"| -- ||align="center"| 2/4 ||
|-
| KBWI || Baltimore || USA MD || America ||align="center"| *** ||align="center"| L ||align="center"| 119.400 (10) ||align="center"| -- ||align="center"| 4/6 ||
|-
| KCGS || College Park || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| 119.850 (3) ||align="center"| -- ||align="center"| 2/0 ||
|-
| KDCA || Reagan National || USA VA || America ||align="center"| *** ||align="center"| M ||align="center"| 120.750 (7) ||align="center"| -- ||align="center"| 3/2 ||
|-
| KDEN || Denver || USA CO || America ||align="center"| ** ||align="center"| L ||align="center"| 133.300 (16) ||align="center"| -- ||align="center"| 6/12 ||
|-
| KDTW || Detroit || USA MI || America ||align="center"| ** ||align="center"| L ||align="center"| 118.400 (15) ||align="center"| -- ||align="center"| 6/8 ||
|-
| KFHR || Friday Harbor || USA WA || America ||align="center"| * ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||
|-
| KHAF || Half Moon Bay || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 122.800 (2) ||align="center"| 4 ||align="center"| 1/0 ||nice area - near KSFO
|-
| KHWD || Hayward || USA CA || America ||align="center"| ** ||align="center"| S ||align="center"| 122.500 (10) ||align="center"| 9 ||align="center"| 2/1 ||nice area - near KSFO
|-
| KIAD || Washington-Dulles || USA VA || America ||align="center"| * ||align="center"| L ||align="center"| 120.100 (14) ||align="center"| many ||align="center"| 4/3 ||
|-
| KIND || Indianapolis || USA IN || America ||align="center"| *** ||align="center"| L ||align="center"| 127.820 (7) ||align="center"| -- ||align="center"| 3/6 ||
|-
| KJAN || Jackson-Evers || USA MS || America ||align="center"| *** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 2/2 ||
|-
| KJFK || John F. Kennedy || USA NY || America ||align="center"| **** ||align="center"| L ||align="center"| 119.100 (18) ||align="center"| many ||align="center"| 4/5 ||
|-
| KLAS || Las Vegas || USA NV || America ||align="center"| **** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 4/3 || terminal and some casinos modeled
|-
| KLAX || Los Angeles || USA CA || America ||align="center"| *** ||align="center"| L ||align="center"| 133.900 (7) ||align="center"| many ||align="center"| 4/8 ||
|-
| KLSV || Nellis Air Force || USA NV || America ||align="center"| *** ||align="center"| L ||align="center"| 132.550 (6) ||align="center"| -- ||align="center"| 2/1 ||
|-
| KLWD || Lewistown || USA MT || America ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||
|-
| KMTN || Martin State || USA MD || America ||align="center"| ** ||align="center"| M ||align="center"| 121.300 (4) ||align="center"| -- ||align="center"| 2/2 || airport and terrain modeled
|-
| KNID || China Lake Naval || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 120.150 (2) ||align="center"| -- ||align="center"| 3/0 ||
|-
| KNUQ || Moffett Federal AFLD || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 119.550 (6) ||align="center"| -- ||align="center"| 2/2 ||
|-
| KOAK || Oakland || USA CA || America ||align="center"| ** ||align="center"| L ||align="center"| 127.200 (7) ||align="center"| many ||align="center"| 4/3 ||
|-
| KORD ||Chicago O'Hare || USA IL || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| many ||align="center"| 7/14 ||
|-
| KOSH || Wittman Rgl. || USA WI || America ||align="center"| ** ||align="center"| M ||align="center"| 118.500 (4) ||align="center"| -- ||align="center"| 4/1 ||
|-
| KOXB || Ocean City Muni. || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||
|-
| KPDX || Portland || USA OR || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 3/5 ||
|-
| KPHX || Phoenix || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 120.900 (6) ||align="center"| -- ||align="center"| 3/5 || most skyscrapers modeled
|-
| KRDU || Raleigh || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (12) ||align="center"| many ||align="center"| 3/4 ||nice for flying east-coast
|-
| KRNO || Reno/Tahoe || USA NZ || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (7) ||align="center"| -- ||align="center"| 3/2 ||High in Clouds
|-
| KSAN || San Diego || USA AZ || America ||align="center"| * ||align="center"| M ||align="center"| 118.300 (7) ||align="center"| many ||align="center"| 1/2 ||Interesting area at boarder to mexico
|-
| KSEA || Seattle Tacoma || USA WA || America ||align="center"| ** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 3/5 || basic terminal model, some skyscrapers modeled
|-
| KSFO || San Francisco || USA CA || America ||align="center"| **** ||align="center"| L ||align="center"| 120.500 (7) ||align="center"| many ||align="center"| 4/3 ||FGFS Default -- overcrowded
|-
| KSLC || Salt Lake City || USA UT || America ||align="center"| * ||align="center"| L ||align="center"| 118.300 (13) ||align="center"| -- ||align="center"| 4/6 ||very high in clouds (4227 ft)
|-
| KSJC || San Jose || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 124.00 (7) ||align="center"| 14 ||align="center"| 3/2 ||Bay-area near KSFO
|-
| LDZU || Udbina || Croatia || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||interesting airport high in Mountains - no ILS
|-
| LFFE || Enghien Moisselles || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| --- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just north of Paris
|-
| LFML || Marseille || France || Europa ||align="center"| * ||align="center"| M ||align="center"| 118.370 (4) ||align="center"| many ||align="center"| 2/2 ||Mediterranean coast
|-
| LFPG || Paris Charles de Gaulle || France || Europa ||align="center"| **** ||align="center"| L ||align="center"| 123.600 (23) ||align="center"| -- ||align="center"| 4/8 ||very detailed city of Paris near by
|-
| LFPH || Chelles Le Pin || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just south of Paris
|-
| LFPL || Lognes Emerainville || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||nice little airport just south of Paris
|-
| LFPO || Paris Orly || France || Europa ||align="center"| **** ||align="center"| M ||align="center"| 120.500 (13) ||align="center"| -- ||align="center"| 3/5 ||the older airport at Paris
|-
| LFPZ || St-Cry'Ecole || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little airport just west of Paris
|-
| LFRJ || Landivisiau || France || Europa ||align="center"| ** ||align="center"| M ||align="center"| 119.700 (2) ||align="center"| -- ||align="center"| 1/1 ||Naval Base
|-
| LFSB || Basel-Mulhouse || Swiss || Europa ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (7) ||align="center"| -- ||align="center"| 3/0 ||
|-
| LHBP || Budapest || Hungaria || Europa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/4 ||in-midst the typical Puszta-area
|-
| LILN || Venegono || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| 128.550 (1) ||align="center"| -- ||align="center"| 1/0 ||
|-
| LILV || Valbrembo || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||recreation area: Mountains, tennis, pool, etc.
|-
| LIMC || Milano Malpensa || Italy || Europa ||align="center"| *** ||align="center"| L ||align="center"| 119.000 (11) ||align="center"| -- ||align="center"| 2/3 ||
|-
| LIME || Bergamo || Italy || Europa ||align="center"| * ||align="center"| M ||align="center"| 120.500 (5) ||align="center"| -- ||align="center"| 2/1 ||nice mountain area
|-
| LIML || Milano Limate || Italy || Europa ||align="center"| *** ||align="center"| M ||align="center"| 119.250 (5) ||align="center"| -- ||align="center"| 2/1 ||
|-
| LQSA || Sarajewo || Bosnia || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.250 (3) ||align="center"| -- ||align="center"| 1/1 ||very nice mountain region: LQSA, LYTV, LYPG
|-
| LOWI || Innsbruck || Austria || Europe ||align="center"| **** ||align="center"| M ||align="center"| 120.100 (3) ||align="center"| -- ||align="center"| 1/1 || very nice and difficult approach, wonderful scenery
|-
| LROP || Bucharest || Romania || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.850 (3) ||align="center"| -- ||align="center"| 2/4 ||
|-
| LSGS || Sion || Swiss || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.217 (5) ||align="center"| -- ||align="center"| 1/1 ||Wonderful surrounded by high mountains
|-
| LSZH || Zürich-Kloten || Swiss || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.800 ||align="center"| many ||align="center"| 3/4 ||very nice mountain/lake area
|-
| LSZB|| Bern-Belp || Swiss || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.020 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| PANC|| Anchorage || USA Alaska || America ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (9) ||align="center"| -- ||align="center"| 3/3 ||interesting area
|-
| LYBE || Belgrad || Serbia || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 ||
|-
| LYPG || Podgorica || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.200 (2) ||align="center"| -- ||align="center"| 2/1 || very nice mountain region: LQSA, LYTV, LYPG
|-
| LYTV || Tivat || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.000 (1) ||align="center"| -- ||align="center"| 1/1 || very nice mountain region: LQSA, LYTV, LYPG
|-
| MUHA || Havana || Cuba || America ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 1/1 ||nice for island-hopping
|-
| NZAA || Auckland || New Zealand || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.700 ||align="center"| many ||align="center"| 2/2 ||nice for island-hopping
|-
| OMAA || Abu Dahbi || United AE || Asia ||align="center"| * ||align="center"| L ||align="center"| 119.200 ||align="center"| many ||align="center"| 1/2 ||interesting area
|-
| OOMS || Seeb || United AE || Asia ||align="center"| * ||align="center"| M ||align="center"| 118.400 (5) ||align="center"| many ||align="center"| 2/2 ||nice sea/mountain area
|-
| PHNL || Honolulu || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| 123.900 (5) ||align="center"| many ||align="center"| 4/2 ||wonderful island scenery
|-
| PHOG || Kahului || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| ||align="center"| ||align="center"| 2/1 ||wonderful island scenery
|-
| RJTT || Tokyo || Japan || Asia ||align="center"| **** ||align="center"| L ||align="center"| 126.200 (6) ||align="center"| -- ||align="center"| 3/3 ||interesting area
|-
| RKSI || Seoul || South Korea || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (6) ||align="center"| -- ||align="center"| 2/4 ||
|-
| RPLL || Manila || Philipines || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||
|-
| TDPD || Melville Hall || Dominica || America ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||nice area
|-
| TFFF || Le Lamentin || Martinique || America ||align="center"| *** ||align="center"| M ||align="center"| 118.500 (5) ||align="center"| -- ||align="center"| 1/1 ||nice area
|-
| TFFG || Grand Case || Anguilla || America ||align="center"| ** ||align="center"| S ||align="center"| 128.940 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TIST || Cyril E King || Virgin Islands || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 ||nice area
|-
| TJSJ || San Juan || Puerto Rico || America ||align="center"| *** ||align="center"| M ||align="center"| 132.050 (6) ||align="center"| -- ||align="center"| 2/2 ||nice area
|-
| TKPK || Saint Kitts || Guadeloupe || America ||align="center"| ** ||align="center"| M ||align="center"| 118.300 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TNCM || Princess Juliana || ST Maarten || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (2) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TQPF || Wallblake || Anquilla || America ||align="center"| ** ||align="center"| S ||align="center"| 18.500 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| VIDP || New Dehli || India || Asia ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (5) ||align="center"| many ||align="center"| 2/3 ||nice area
|-
| VHHH || Hong Kong || China || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.400 (16) ||align="center"| many ||align="center"| 2/4 ||very nice mountain/sea area
|-
| WSSS || Singapore Changi || Singapore || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.600 (8) ||align="center"| many ||align="center"| 2/3 ||
|-
| YBAS || Alice Springs || Australia NT || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.300 (2) ||align="center"| 26 ||align="center"| 3/1 ||Australian Back-Country
|-
| YPDN || Darwin || Australia NT || Australia ||align="center"| * ||align="center"| M ||align="center"| 133.100 (8) ||align="center"| many ||align="center"| 2/1 ||
|-
| YSCB || Canberra || Australia NSW || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.700 (5) ||align="center"| many ||align="center"| 2/1 ||High Mountain region (1800 ft)
|-
| YSSY || Sydney || Australia NSW || Australia ||align="center"| * ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||
|-
|}

Suggested airports

2011-01-07T07:20:06Z

Statto:

Here you will find Airports that are well developed and/or have an outstanding scenery. Thus they are "suggested" especially to be visited and/or used for Multi-player events like FlyIns, TGA, ATC, etc..
 
If you are searching for the '''development-status of Airports''' see the wiki [[Developed Airports]].
 For further suggestions see [[Suggested Scenery]] and [[Suggested Flights]]
 
The overall Airport-Rating (column "R") is based on the TerraSync-Status of the following characteristics:
{| border="0"
|-
! style="text-align:center"| * !!style="text-align:left"|     superior surrounding landscape - although the airport itself is not (yet) developed accordingly
|-
! style="text-align:center"| ** !!style="text-align:left"|     complex modeling of buildings
|-
! style="text-align:center"| *** !!style="text-align:left"|     complex modeling of buildings, taxiways, and aprons
|-
! style="text-align:center"| **** !!style="text-align:left"|     extensive modeling of airport and landscape and/or city
|}
 
Further columns to watch for are:
*'''S = Size:''' L= all aircraft, M= midium size aircraft, S= for small aircraft
*'''FGCOM:''' If available one FGCOM frequency is given, followed by the amount of the total available FGCOM frequencies
*'''Parking:''' amount of pre-defined Parking-Lots (otherwise see: [[Initial_Starting_Positions]])
*'''R/I:''' amount of runways and ILS (e.g. KROC has 3 runway: 04/22 has each 1 ILS, 10/28 has only one ILS on 28, 07/25 has no ILS)
 
{| class="wikitable sortable" border="0" cellspacing="0"
! width="40" | ICAO
! width="130" | Name
! width="80" | Country
! width="80" | Continent
! width="30" | R
! width="30" | S
! width="100" | FGCOM
! width="50" | Parking
! width="40" | R/I
! class="unsortable" style="background:#efefef" | Comment|
|-
| BKPR || Pristina || Kosovo || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 || very nice scenery
|-
| CYVR || Vancouver || Canada || America ||align="center"| * ||align="center"| L ||align="center"| 125.650 (6) ||align="center"| many ||align="center"| 5/5 || nice area
|-
| EDDF || [[Frankfurt am Main Airport|Frankfurt am Main]] || Germany || Europe || align="center" | **** || align="center" | L || align="center" | 127.320 (6) || align="center" | many ||align="center"| 2-4 || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown
|-
| EDDH || [[Hamburg_Airport|Hamburg]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 126.850 (7) ||align="center"| -- ||align="center"| 2/4 || Fully modeled, plus unique buildings downtown|-
|-
| EDDI || [[EDDI|Berlin Tempelhof]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 118.100 (10) ||align="center"| 1 ||align="center"| 2/0 || Fully modeled, especially also the City
|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (4) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled
|-
| EDDP || [[Leipzig/Halle_Airport|Leipzig]] || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.100 (5) ||align="center"| -- ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]
|-
| EDDT || [[Berlin_Tegel_Airport|Berlin Tegel]] || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.700 (11) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled, inclusive [[Signs]]
|-
| EDDV || [[EDDV|Hannover]] || Germany || Europe ||align="center"| * ||align="center"| L ||align="center"| 120.170 (3)) ||align="center"| 4 ||align="center"| 2/4 || Tower and terminal modeled
|-
| EDDW || Bremen || Germany || Europe ||align="center"| ** ||align="center"| L ||align="center"| 118.500 (7) ||align="center"| -- ||align="center"| 2/2 || very nicely modeled
|-
| EDVE || Braunschweig || Germany || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.350 (2) ||align="center"| -- ||align="center"| 2/1 ||
|-
| EEKE || Kuressaare || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 ||
|-
| EFHF || Helsinki-Malmi || Finnland || Europe ||align="center"| ** ||align="center"| S ||align="center"| 119.700 (4) ||align="center"| -- ||align="center"| 2/0 ||
|-
| EFHK || Helsinki || Finnland || Europe ||align="center"| ** ||align="center"| L ||align="center"| 119.700 (5) ||align="center"| -- ||align="center"| 3/5 ||
|-
| EEPU || Parnu || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU
|-
| EETN || Tallinn || Estonia || Europe ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/2 || Nice triangle EETN-EETU-EEPU
|-
| EETU || Tartu || Estonia || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 || Nice triangle EETN-EETU-EEPU
|-
| EGFF || Cardif || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 125.00 (3) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGGP || Liverpool || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.350 (4) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGGW || London Luton || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 126.720 (6) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EGKA || Shoreham || UK || Europe ||align="center"| *** ||align="center"| S ||align="center"| 125.400 (3) ||align="center"| -- ||align="center"| 3/0 ||
|-
| EGKK || London Gatwick || UK || Europe ||align="center"| **** ||align="center"| M ||align="center"| 124.220 (8) ||align="center"| 6 ||align="center"| 1/2 ||
|-
| EGLL || London Heathrow || UK || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.500 (14) ||align="center"| 3 ||align="center"| 2/4 ||
|-
| EGPH || Edinburgh || UK || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (4) ||align="center"| -- ||align="center"| 2/2 ||
|-
| EGSH || Norwich || UK || Europe ||align="center"| *** ||align="center"| M ||align="center"| 124.250 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| EHAM || Amsterdam || Netherlands || Europe ||align="center"| **** ||align="center"| L ||align="center"| 119.220 (1) ||align="center"| many ||align="center"| 6/6 ||One of the best modeled airports in the world
|-
| EHEH || Eindhoven || Netherlands || Europe ||align="center"| ** ||align="center"| M ||align="center"| 131.000 (6) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EHLE || Eindhoven || Netherlands || Europe ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| 1 ||align="center"| 2/1 ||
|-
| EHVK || Volkel || Netherlands || Europe ||align="center"| ** ||align="center"| L ||align="center"| 123.170 (1) ||align="center"| many ||align="center"| 2/2 ||
|-
| EIDW || Dublin || Ireland || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.600 (7) ||align="center"| -- ||align="center"| 3/3 ||
|-
| ENAL || Alesund || Norway || Europe ||align="center"| ** ||align="center"| M ||align="center"| 118.100 (4) ||align="center"| -- ||align="center"| 1/1 ||
|-
| ENSD || Alesund || Norway || Europe ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||
|-
| ENVA || Trondheim || Norway || Europe ||align="center"| *** ||align="center"| L ||align="center"| 122.100 (6) ||align="center"| -- ||align="center"| 2/2 ||
|-
| ESPG || Göteborg || Sweden || Europe ||align="center"| ** ||align="center"| M ||align="center"| 129.100 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| FACT || Cape Town || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/2 ||nice area
|-
| FAJS || Johannisburg || South Africa || Africa ||align="center"| * ||align="center"| L ||align="center"| 121.900 (3) ||align="center"| many ||align="center"| 2/3 ||high (5000), in mountains
|-
| GCFV || Fuerteventura || Gran Canaria || Africa ||align="center"| * ||align="center"| L ||align="center"| 119.200 (4) ||align="center"| 9 ||align="center"| 1/1 ||nice island area
|-
| KABQ || Albuquerque || USA NM || America ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 ||
|-
| HECA || Cairo || Egypt || Africa ||align="center"| * ||align="center"| L ||align="center"| 120.300 (10) ||align="center"| -- ||align="center"| 4/2 || near pyramids
|-
| KATL || Atlanta || USA GA || America ||align="center"| * ||align="center"| L ||align="center"| 119.550 (4) ||align="center"| many ||align="center"| 3/4 ||
|-
| KAUS || Austin || USA TX || America ||align="center"| *** ||align="center"| L ||align="center"| 121.00 (10) ||align="center"| -- ||align="center"| 2/4 ||
|-
| KBWI || Baltimore || USA MD || America ||align="center"| *** ||align="center"| L ||align="center"| 119.400 (10) ||align="center"| -- ||align="center"| 4/6 ||
|-
| KCGS || College Park || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| 119.850 (3) ||align="center"| -- ||align="center"| 2/0 ||
|-
| KDCA || Reagan National || USA VA || America ||align="center"| *** ||align="center"| M ||align="center"| 120.750 (7) ||align="center"| -- ||align="center"| 3/2 ||
|-
| KDEN || Denver || USA CO || America ||align="center"| ** ||align="center"| L ||align="center"| 133.300 (16) ||align="center"| -- ||align="center"| 6/12 ||
|-
| KDTW || Detroit || USA MI || America ||align="center"| ** ||align="center"| L ||align="center"| 118.400 (15) ||align="center"| -- ||align="center"| 6/8 ||
|-
| KFHR || Friday Harbor || USA WA || America ||align="center"| * ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||
|-
| KHAF || Half Moon Bay || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 122.800 (2) ||align="center"| 4 ||align="center"| 1/0 ||nice area - near KSFO
|-
| KHWD || Hayward || USA CA || America ||align="center"| ** ||align="center"| S ||align="center"| 122.500 (10) ||align="center"| 9 ||align="center"| 2/1 ||nice area - near KSFO
|-
| KIAD || Washington-Dulles || USA VA || America ||align="center"| * ||align="center"| L ||align="center"| 120.100 (14) ||align="center"| many ||align="center"| 4/3 ||
|-
| KIND || Indianapolis || USA IN || America ||align="center"| *** ||align="center"| L ||align="center"| 127.820 (7) ||align="center"| -- ||align="center"| 3/6 ||
|-
| KJAN || Jackson-Evers || USA MS || America ||align="center"| *** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 2/2 ||
|-
| KJFK || John F. Kennedy || USA NY || America ||align="center"| **** ||align="center"| L ||align="center"| 119.100 (18) ||align="center"| many ||align="center"| 4/5 ||
|-
| KLAS || Las Vegas || USA NV || America ||align="center"| **** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 4/3 || terminal and some casinos modeled
|-
| KLAX || Los Angeles || USA CA || America ||align="center"| *** ||align="center"| L ||align="center"| 133.900 (7) ||align="center"| many ||align="center"| 4/8 ||
|-
| KLSV || Nellis Air Force || USA NV || America ||align="center"| *** ||align="center"| L ||align="center"| 132.550 (6) ||align="center"| -- ||align="center"| 2/1 ||
|-
| KLWD || Lewistown || USA MT || America ||align="center"| ** ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||
|-
| KMTN || Martin State || USA MD || America ||align="center"| ** ||align="center"| M ||align="center"| 121.300 (4) ||align="center"| -- ||align="center"| 2/2 || airport and terrain modeled
|-
| KNID || China Lake Naval || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 120.150 (2) ||align="center"| -- ||align="center"| 3/0 ||
|-
| KNUQ || Moffett Federal AFLD || USA CA || America ||align="center"| ** ||align="center"| M ||align="center"| 119.550 (6) ||align="center"| -- ||align="center"| 2/2 ||
|-
| KOAK || Oakland || USA CA || America ||align="center"| ** ||align="center"| L ||align="center"| 127.200 (7) ||align="center"| many ||align="center"| 4/3 ||
|-
| KORD ||Chicago O'Hare || USA IL || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| many ||align="center"| 7/14 ||
|-
| KOSH || Wittman Rgl. || USA WI || America ||align="center"| ** ||align="center"| M ||align="center"| 118.500 (4) ||align="center"| -- ||align="center"| 4/1 ||
|-
| KOXB || Ocean City Muni. || USA MD || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||
|-
| KPDX || Portland || USA OR || America ||align="center"| ** ||align="center"| L ||align="center"| -- ||align="center"| -- ||align="center"| 3/5 ||
|-
| KPHX || Phoenix || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 120.900 (6) ||align="center"| -- ||align="center"| 3/5 || most skyscrapers modeled
|-
| KRDU || Raleigh || USA AZ || America ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (12) ||align="center"| many ||align="center"| 3/4 ||nice for flying east-coast
|-
| KRNO || Reno/Tahoe || USA NZ || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (7) ||align="center"| -- ||align="center"| 3/2 ||High in Clouds
|-
| KSAN || San Diego || USA AZ || America ||align="center"| * ||align="center"| M ||align="center"| 118.300 (7) ||align="center"| many ||align="center"| 1/2 ||Interesting area at boarder to mexico
|-
| KSEA || Seattle Tacoma || USA WA || America ||align="center"| ** ||align="center"| L ||align="center"| 119.900 (9) ||align="center"| -- ||align="center"| 3/5 || basic terminal model, some skyscrapers modeled
|-
| KSFO || San Francisco || USA CA || America ||align="center"| **** ||align="center"| L ||align="center"| 120.500 (7) ||align="center"| many ||align="center"| 4/3 ||FGFS Default -- overcrowded
|-
| KSLC || Salt Lake City || USA UT || America ||align="center"| * ||align="center"| L ||align="center"| 118.300 (13) ||align="center"| -- ||align="center"| 4/6 ||very high in clouds (4227 ft)
|-
| KSJC || San Jose || USA CA || America ||align="center"| * ||align="center"| M ||align="center"| 124.00 (7) ||align="center"| 14 ||align="center"| 3/2 ||Bay-area near KSFO
|-
| LDZU || Udbina || Croatia || Europe ||align="center"| * ||align="center"| M ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||interesting airport high in Mountains - no ILS
|-
| LFFE || Enghien Moisselles || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| --- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just north of Paris
|-
| LFML || Marseille || France || Europa ||align="center"| * ||align="center"| M ||align="center"| 118.370 (4) ||align="center"| many ||align="center"| 2/2 ||Mediterranean coast
|-
| LFPG || Paris Charles de Gaulle || France || Europa ||align="center"| **** ||align="center"| L ||align="center"| 123.600 (23) ||align="center"| -- ||align="center"| 4/8 ||very detailed city of Paris near by
|-
| LFPH || Chelles Le Pin || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little Green-Field just south of Paris
|-
| LFPL || Lognes Emerainville || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 3/0 ||nice little airport just south of Paris
|-
| LFPO || Paris Orly || France || Europa ||align="center"| **** ||align="center"| M ||align="center"| 120.500 (13) ||align="center"| -- ||align="center"| 3/5 ||the older airport at Paris
|-
| LFPZ || St-Cry'Ecole || France || Europa ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 2/0 ||nice little airport just west of Paris
|-
| LFRJ || Landivisiau || France || Europa ||align="center"| ** ||align="center"| M ||align="center"| 119.700 (2) ||align="center"| -- ||align="center"| 1/1 ||Naval Base
|-
| LFSB || Basel-Mulhouse || Swiss || Europa ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (7) ||align="center"| -- ||align="center"| 3/0 ||
|-
| LHBP || Budapest || Hungaria || Europa ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 2/4 ||in-midst the typical Puszta-area
|-
| LILN || Venegono || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| 128.550 (1) ||align="center"| -- ||align="center"| 1/0 ||
|-
| LILV || Valbrembo || Italy || Europa ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/0 ||recreation area: Mountains, tennis, pool, etc.
|-
| LIMC || Milano Malpensa || Italy || Europa ||align="center"| *** ||align="center"| L ||align="center"| 119.000 (11) ||align="center"| -- ||align="center"| 2/3 ||
|-
| LIME || Bergamo || Italy || Europa ||align="center"| * ||align="center"| M ||align="center"| 120.500 (5) ||align="center"| -- ||align="center"| 2/1 ||nice mountain area
|-
| LIML || Milano Limate || Italy || Europa ||align="center"| *** ||align="center"| M ||align="center"| 119.250 (5) ||align="center"| -- ||align="center"| 2/1 ||
|-
| LQSA || Sarajewo || Bosnia || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.250 (3) ||align="center"| -- ||align="center"| 1/1 ||very nice mountain region: LQSA, LYTV, LYPG
|-
| LOWI || Innsbruck || Austria || Europe ||align="center"| **** ||align="center"| M ||align="center"| 120.100 (3) ||align="center"| -- ||align="center"| 1/1 || very nice and difficult approach, wonderful scenery
|-
| LROP || Bucharest || Romania || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.850 (3) ||align="center"| -- ||align="center"| 2/4 ||
|-
| LSGS || Sion || Swiss || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.217 (5) ||align="center"| -- ||align="center"| 1/1 ||Wonderful surrounded by high mountains
|-
| LSZH || Zürich-Kloten || Swiss || Europe ||align="center"| ** ||align="center"| L ||align="center"| 121.800 ||align="center"| many ||align="center"| 3/4 ||very nice mountain/lake area
|-
| LSZB|| Bern-Belp || Swiss || Europe ||align="center"| ** ||align="center"| M ||align="center"| 121.020 (3) ||align="center"| -- ||align="center"| 2/1 ||
|-
| PANC|| Anchorage || USA Alaska || America ||align="center"| *** ||align="center"| L ||align="center"| 118.300 (9) ||align="center"| -- ||align="center"| 3/3 ||interesting area
|-
| LYBE || Belgrad || Serbia || Europe ||align="center"| *** ||align="center"| M ||align="center"| 118.100 (2) ||align="center"| -- ||align="center"| 1/2 ||
|-
| LYPG || Podgorica || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.200 (2) ||align="center"| -- ||align="center"| 2/1 || very nice mountain region: LQSA, LYTV, LYPG
|-
| LYTV || Tivat || Montenegro || Europe ||align="center"| * ||align="center"| M ||align="center"| 118.000 (1) ||align="center"| -- ||align="center"| 1/1 || very nice mountain region: LQSA, LYTV, LYPG
|-
| MUHA || Havana || Cuba || America ||align="center"| * ||align="center"| L ||align="center"| 118.100 (4) ||align="center"| many ||align="center"| 1/1 ||nice for island-hopping
|-
| NZAA || Auckland || New Zealand || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.700 ||align="center"| many ||align="center"| 2/2 ||nice for island-hopping
|-
| OMAA || Abu Dahbi || United AE || Asia ||align="center"| * ||align="center"| L ||align="center"| 119.200 ||align="center"| many ||align="center"| 1/2 ||interesting area
|-
| OOMS || Seeb || United AE || Asia ||align="center"| * ||align="center"| M ||align="center"| 118.400 (5) ||align="center"| many ||align="center"| 2/2 ||nice sea/mountain area
|-
| PHNL || Honolulu || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| 123.900 (5) ||align="center"| many ||align="center"| 4/2 ||wonderful island scenery
|-
| PHOG || Kahului || USA Hawaii || America ||align="center"| * ||align="center"| M ||align="center"| ||align="center"| ||align="center"| 2/1 ||wonderful island scenery
|-
| RJTT || Tokyo || Japan || Asia ||align="center"| **** ||align="center"| L ||align="center"| 126.200 (6) ||align="center"| -- ||align="center"| 3/3 ||interesting area
|-
| RKSI || Seoul || South Korea || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (6) ||align="center"| -- ||align="center"| 2/4 ||
|-
| RPLL || Manila || Philipines || Asia ||align="center"| *** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||
|-
| TDPD || Melville Hall || Dominica || America ||align="center"| ** ||align="center"| L ||align="center"| 118.100 (5) ||align="center"| -- ||align="center"| 2/2 ||nice area
|-
| TFFF || Le Lamentin || Martinique || America ||align="center"| *** ||align="center"| M ||align="center"| 118.500 (5) ||align="center"| -- ||align="center"| 1/1 ||nice area
|-
| TFFG || Grand Case || Anguilla || America ||align="center"| ** ||align="center"| S ||align="center"| 128.940 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TIST || Cyril E King || Virgin Islands || America ||align="center"| ** ||align="center"| S ||align="center"| -- ||align="center"| -- ||align="center"| 1/1 ||nice area
|-
| TJSJ || San Juan || Puerto Rico || America ||align="center"| *** ||align="center"| M ||align="center"| 132.050 (6) ||align="center"| -- ||align="center"| 2/2 ||nice area
|-
| TKPK || Saint Kitts || Guadeloupe || America ||align="center"| ** ||align="center"| M ||align="center"| 118.300 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TNCM || Princess Juliana || ST Maarten || America ||align="center"| ** ||align="center"| M ||align="center"| 118.700 (2) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| TQPF || Wallblake || Anquilla || America ||align="center"| ** ||align="center"| S ||align="center"| 18.500 (3) ||align="center"| -- ||align="center"| 1/0 ||nice area
|-
| VIDP || New Dehli || India || Asia ||align="center"| ** ||align="center"| L ||align="center"| 119.300 (5) ||align="center"| many ||align="center"| 2/3 ||nice area
|-
| VHHH || Hong Kong || China || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.400 (16) ||align="center"| many ||align="center"| 2/4 ||very nice mountain/sea area
|-
| WSSS || Singapore Changi || Singapore || Asia ||align="center"| * ||align="center"| L ||align="center"| 118.600 (8) ||align="center"| many ||align="center"| 2/3 ||
|-
| YBAS || Alice Springs || Australia NT || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.300 (2) ||align="center"| 26 ||align="center"| 3/1 ||Australian Back-Country
|-
| YPDN || Darwin || Australia NT || Australia ||align="center"| * ||align="center"| M ||align="center"| 133.100 (8) ||align="center"| many ||align="center"| 2/1 ||
|-
| YSCB || Canberra || Australia NSW || Australia ||align="center"| * ||align="center"| M ||align="center"| 118.700 (5) ||align="center"| many ||align="center"| 2/1 ||High Mountain region (1800 ft)
|-
| YSSY || Sydney || Australia NSW || Australia ||align="center"| * ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||
|-
|}

Scenery

2011-01-07T07:14:49Z

Statto:

'''Scenery''' is the landscape in [[FlightGear]] (or any other simulator).

It includes airports, buildings, trees, mountains, valleys, vegetation, settlements and waterbodies.

The whole world is available for FlightGear, but details and accuracy vary from place to place. The data is released as [[World Scenery]] collections available from the the FlightGear website.

==Recommended Scenery==
* [[Developed Airports]] - airports with at least one non-generic airport building placed
* [[Suggested Airports]] - airports ranked by scenery quality

==Scenery Projects==
* [[Brest]]
* [[Dublin (Scenery)|Dublin]]
* [[FlightGear NL]]
* [[Germany]]
* [[Custom France Scenery]]
* [http://gitorious.org/papillon81 papillon81's git repository for scenery (Frankfurt, Singapore)]

''See also [[FlightGear related projects]]

==See also==
* [[Landmark Wish List]]
* [[FlightGear Scenery Designer]]
* [[Installing Scenery]]
* [[Next Generation Scenery]]
* [[Image:Worldscenery-text.jpg]]

==External links==
* http://www.flightgear.org/Downloads/scenery-0.9.10.html
* http://www.flightgear.org/Downloads/scenery-1.0.0.html
* http://www.flightgear.org/Downloads/scenery-1.0.1.html

{{Terra}}

[[Category:Scenery]]

[[es:Escenario]]
[[fr:Scenery]]

FlightGear Newsletter January 2011

2011-01-06T07:27:05Z

Statto: /* Scenery corner */

FlightGear Newsletter January 2011

2011-01-06T05:48:50Z

Statto: /* New York City */

FlightGear Newsletter January 2011

2011-01-06T05:47:01Z

Statto: /* Scenery corner */

Developed airports

2010-12-31T22:58:57Z

Statto: Redirected page to Developed Airports

#REDIRECT [[Developed Airports]]

FlightGear Newsletter December 2010

2010-12-29T07:46:21Z

Statto:

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

==2010 annual==
2010 was the year in which:
* FlightGear 2.0 was released.
* most of the existing virtual airlines were merged into [[Atlas Virtual Airlines]], making it the largest and by far most active FlightGear based airline.
* shaders started to be used all over the sim, introducing some new graphical eye candy as semi-realistic water reflections, 3D cities.
* the CVS servers broke down after a hardware failure, leading to our move to Git.
* detailed landclassing was created for various locations around the world.
* anaglyphic (3D) was introduced; making FlightGear the first flightsim with built-in 3D support.

== FlightGear events ==
== Call for volunteers ==
The [[OpenRadar]] project is looking for a new maintainer.

The [[TerraGear GUI]] project is looking for programmers to help create a GUI frontend for [[TerraGear]] [http://flightgear.org/forums/viewtopic.php?f=5&t=7485#p102005].

The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

== Development news ==
[[User:T3r|Torsten]] improved the handling of reduced visibility due to fog, mist or haze. The global weather now interprets weather phenomena causing reduced visibility. The code places a cloud layer starting at the ground and reaching up to a certain altitude. After climbing through this layer, visibility increases rapidly, just like in real life.
As a side effect, the opacity of 2d cloud layers are now settable via the property tree. Also accessible at the property tree are the decoded weather phenomena from METAR reports along with its descriptions and intensity.

== Nasal for newbies ==
== New software tools and projects ==

== FlightGear addons and mods ==
== In the hangar ==
=== New aircraft ===

====Bell AH-1 Cobra====
[[File:Cobra.jpg|200px|thumb|left|Cobra in action.]]
The Developers at [http://alphashangar.co.nr/ Alpha-J's Hangar] have started making the [[AH-1 Cobra|Bell AH-1 Cobra]]. Development is going well and can be tracked [http://www.flightgear.org/forums/viewtopic.php?f=4&t=10130 here.] The Bell AH-1 Cobra is a two-bladed, single engine attack helicopter manufactured by Bell Helicopter. It shares a common engine, transmission and rotor system with the older UH-1 Iroquois. The AH-1 is also referred to as the HueyCobra or Snake.

====AgustaWestland AW139====
[[File:AW139ln.jpg|200px|thumb|left|AW139-here in the LongNose-version]]
HHS started to make the AW139, an italian midclass helicopter in use in many countries like the Netherlands, Spain, Italia, Ireland and Japan.

This work has been started due to the fact that above-average number of datas about the flightdynamic has been found, and the systems are very similar like to other new helicopters like the EC130 B4.

So you can expect another accurate helicopter next year. As special feature it is planned to simulate the 4-axis autopilot as accurate as possible.
People who would like to follow the developement can watch it at: [http://www.gitorious.org/aw139 http://www.gitorious.org/aw139]

=== Updated aircraft ===

====F5E Tiger II====
[[File:Fgfs-screen-014.png|200px|thumb|left|F5E Tiger II.]]
Has many updated aspects, please follow the link : [http://flightgear.org/forums/viewtopic.php?f=4&t=10327]. For direct download: http://dl.dropbox.com/u/16442048/F-5Ev20101220.rar

====Short S.23 Empire flying boat====
[[File:Sperry_A-2.jpg|thumb|250px|The control unit of the Sperry A-2 automatic pilot in a Short S.23 Empire flying boat.]]

The [[Short Empire|Short Empire flying boat]] has been updated with a Sperry A-2 automatic pilot by Anders, filling one of the remaining empty spots on the dashboard.

====Lockheed L-1011 Tristar====
Fresh off a 1/10 rating, the [[Lockheed L-1011-500|TriStar]] is closer to having a working cockpit. Currently there are three working photorealistic instruments. A full cockpit update is planned to be sent to the repository soon.

====Eurocopter EC130 B4====
[[File:Ec130.10.jpg|200px|thumb|right|EC130 B4- latest development version]]
Not for beginners anymore- the EC130 has been updated and the latest developement is now available in Git. This includes a better and more accurate 3d-model with customized reflection effects, detailed mainrotor, 3d-cockpit and a more accurate fdm.
More interesting is the systems simulation: FADEC, FLI (FirstLimitIndicator) in the work, electrical systems, fuel, Force Trim Release....
This is all based on the original flight manual, and as there is no Autostart you have to follow the checklist to get this bird started. A first simple flightmanual is included.

There are still a lot of things left to do, which will be done in the next weeks and months:
* lighting
* bug fixing
* sound config
* paintkit with high detailed liveries
* completing the 3d-work
* failures
* better flightmanual

and some things more.

====Airbus A320====
[[File:A320-cockpit.jpg|200px|thumb|The 3d cockpit of the Airbus A320, under development]]
[[User:Skyop|Skyop]] has restarted development of the popular [[Airbus A320]] aircraft. The latest new features include:
* Improved UV map
* Ability to select the -111, -131, -211, or -231 series with different livery sets for each
* Improved door animations
* Improved flap and gear animations
* Improved autostart script

...and last but certainly not least, a ''drastically'' improved cockpit (see the screenshot on the right). In time, the A320 will be equipped with an overhead panel and a more advanced startup procedure; it is also hoped that fly-by-wire controls will be available at some point.

To keep up-to-date on the progress of this bird, see [http://flightgear.org/forums/viewtopic.php?t=9032 the FlightGear Forum development topic].

====Airbus A380====
After several months of remodelling and coding, the [[A380]] has been updated and committed to the general FGdata Git repository ready for the next release of FlightGear.

The A380 comes with three liveries
* Airbus House
* Singapore Airlines
* Qantas Airways
There are too many changes since the last "Milestone" release twelve months ago to list here. The [[Airbus A380]] wiki page details the list of items that have been completed or are still on the "To Do" list. The aircraft requires the latest Git build of FlightGear as it uses many features in the up coming release including digital filters in the autopilot, OSG Text animations and James Turners new GPS code.

=== Liveries ===

== Scenery corner ==
===Models===
New additions to the scenery model database this month include models of Wimbledon, a handful of skyscrapers from New York City and Montréal, the Great Orme lighthouse, and Trento and Asiago airports (discussed further below).

The database now has 1983 distinct models. Please consider contributing a model to the FlightGear scenery model database!

===Land Cover===
====Eastern Europe====
Detailed scenery is under development for the E20N40 area, with the following countries partly or fully covered:
* Albania
* Bulgaria
* Hungary
* Kosovo
* FYR Macedonia
* Poland
* Romania
* Serbia
* Slovakia
* Turkey

The scenery is using Corine land classification data, road and railroad data from OpenStreetMap and SRTM v4 elevation data from CGIAR.

[[File:E20n40.png|thumb|400px|left]]
 

==== New England ====
More New England coverage as western Massachusetts has been added to the map server and therefore has been made part of the default scenery package. The next scenery release will allow users to fly from New York John F. Kennedy Int'l to Burlington, Vermont without having to pass over any vmap0 (current) scenery. More coverage is planned as well. Also, at least four of the five boroughs of New York City should have land cover in the database by the start of the new year with the only other missing borough, Manhattan, to come in the very near future.

====Republic of Ireland====

Detailed scenery made from CORINE land cover data is now available for the Republic of Ireland. Road and railroad data is from OpenStreetMap, elevation data is SRTM v3. A nice feature of this scenery is that the coastline is rendered using the Corine shapes, so flying along the coast looks a lot prettier than the in the default vmap0 scenery. The scenery pack also contains a terminal building for Knock Ireland West Airport (EIKN) not previously seen.

See some screenshots [http://www.flightgear.org/forums/viewtopic.php?f=19&t=10326 here] and for further details see the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10354 forum announcement].

=== Airports ===
====Charlottesville Albemarle Airport (KCHO)====
[[File:DevelopmenofKCHOPart1.jpg|200px|thumb|left|KCHO under development]]I (Catchatyou) am currently working on making a new airport for FlightGear! It is Charlottesville Albemarle Airport (KCHO). I must say that I am new to Blender and FlightGear, but I am excited to be a part of it. I hope that my creation will eventually sprout into a beautiful product as time goes by. I have no set date on when this should be completed, but I hope that I can make it as soon as possible.

[[File:eddm tower.jpg|200px|thumb|right|Development version of EDDM tower]]I am not just making the airport building. I'm hoping to eventually add in the parking lot and other various objects.

Thank you for making contributing so easy.

====Franz Josef Strauss Airport Munich (EDDM)====
[[:User:D-79|D-79]] started modelling EDDM in October and is dedicated to make this the most detailed airport in Germany. So far, both terminals have been modelled, as well as most of the additional buildings on the aprons. One of the most difficult tasks proved to be setting up ground vehicles. But now they're running as an AI scenario of [http://www.youtube.com/watch?v=6GhGbV7n0Uk eight busses and trucks]. As soon as work is finished, the airport will be sent to Martin of the [[FlightGear Scenery Database]].

====Aeroporto "Gianni Caproni", Mattarello, Trento (Northern Italy) (LIDT)====
[[File:LIDT-Mattarello.jpg|200px|thumb|left|LIDT-Mattarello]]LIDT is a small touristic airport located in Mattarello, very close to Trento (Trentino Alto Adige-Sued Tyrol), and is dedicated to Giovanni Caproni, an Italian pioneer of aviation, born in Arco, near Trento.
Beside the terminal building there is an Aviation Museum containing some aircrafts built by the Caproni Factory in early XX century.

The LIDT airport is home to the [http://www.protezionecivile.tn.it/frame.asp?Site=11&Area=29&Sect=221&Subs=260 "Gruppo Elicotteri Vigili del Fuoco Trento"] (Trento Fire Dept Helicopter Group), involved in many rescue operations on the Alps.

Scighera has modeled the Main Building (Air Terminal, Tower and Aerhotel), the Caproni Aviation Museum and various hangars, including the one of the Fire Dept Helicopter Group.

The 3D models are available for download at [http://digilander.libero.it/scighera_fg/index.html scighera's Homepage] and are already available on [[TerraSync]].

====Aeroporto "Romeo Sartori", Asiago (LIDA)====
[[File:ZFoto_LIDA_Asiago_1.jpg|200px|thumb|left|LIDA-Asiago]]LIDA Asiago (Veneto, Italy) is another small touristic airport at the edge between the Po River Plains and the Eastern Alps, populated with a lot of gliders.
Scighera has modelled the few buildings there, including the "fancy" Terminal.

The few 3D models are avilable for download at [http://digilander.libero.it/scighera_fg/index.html scighera's Homepage] and have been issued to Martin for inclusion in the [[FlightGear Scenery Database]].(It has been included on Dec 13th 2010)

====Engiadina Airport, Semaden St.Murezzan (Svizra)(LSZS)====
[[File:Z_LSZS_Samedan1.jpg|200px|thumb|left|LSZS Semaden Terminal]]Or ... Engadiner Flughafen Samedan St. Moritz (Schweiz) claims to be the highest airport in Europe; in any case is strategically located in the middle of Raethian Alps !
Scighera has started the modelling of the buildings, beginning with the terminal 1 (actually the only one !)... in the meanwhile HHS provided the untextured .blend files of the south building, including the Terminal, the Tower and HeliBernina Hangar and Offices.

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

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

== Wiki updates ==
===Developed Airports===
So far we never had a list of all developed airports in FlightGear. This has now been changed. The [[developed airports]] article lists all aerodromes where at least one building has been placed, be it a static (unique) models or a shared model, but only if the objects are available from the [[FlightGear Scenery Database]]. This new list is meant to become the central site where we maintain an up-to-date list of all developed airports. For setting up this list, [[:User:D-79|D-79]] used the forum discussion [http://www.flightgear.org/forums/viewtopic.php?f=5&t=4700|List of Improved Airports in FlightGear].

===Video Tutorials===
Over the past year, more and more [[Video Tutorials]] have been produced for FlightGear, so that it seemed sensible to set up a special wiki site for them, sorted by categories. Feel free to 1) make more video tutorials and 2) add them to the list. When making a video tutorial, please try to keep a certain standard: Video tutorials should have a good video resolution so that users can see what's happening on the screen, and they should have text or voice comment so that users understand what's being done.

[[File:Asi.png|thumb|120px|Airspeed indicator]]

===More Hangars===
The wiki article [[FlightGear Hangars]] has been extended by longfly. Now there are over 47 hangars with interesting aircraft, liveries and scenery. [http://www.flightgear.bplaced.de/filemanager/flightgear/index.php/flugzeugliste Longfly's german hangar] for example has begun to create a list of all aircrafts available for FlightGear. There are currently 412, which must be insert. see also the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=10536 forum]

===Instrument glass reflection tutorial===
Horacio has written an excellent short tutorial to show how to add glass reflection effect to instruments, using graphic tools, so that the reflection effect is already contained in the main instrument image, and not depending on shaders meaning less CPU load. The result is widely satisfactory and very realistic.

[[Howto: Glass reflection effect for instruments]]

===Helipad category===
We have a new wiki [[:Category:Helipads|category for helipads]], as a sub-category of the [[:Category:Airports|airports category]]. So far, only the [[oil platforms]] can be found there, but others could be added, like hospital helipads or ANWB/ADAC/ÖAMTC heliports.

=== New tutorials and screencasts ===
Check out Zexe's video Tips and Tricks for Flightgear. Tips include how to Target-track, overlay instrument numbers, and so on. You can find them here on the wiki at [[Video Tutorials#Advanced options|Video Tutorials (advanced options)]] and on the [http://flightgear.org/forums/viewtopic.php?f=19&t=9811 forum].

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

== Community news ==
=== FlightGear on YouTube ===
* Oscar uploaded a nice video of a [http://www.youtube.com/watch?v=YKa3-jUWMKU 777 event at EHAM].

=== Forum news ===

=== Multiplayer ===
* Papabear is currently hosting an "event", where he is navigating the USS Vinson around the world! Visit [[Carrier over MP|here]] to find out how to activate the MP Carrier mode, and [http://www.flightgear.org/forums/viewtopic.php?f=10&t=10207#p103663 here] for the FG Forum Topic regarding this post. As of Dec. 26 at 12:00AM UTC, the Vinson is near the former Kai Tak airport of Hong Kong. All aircraft are welcome, even ones that usually should not land on carriers in reality. Enjoy landing and talking to other pilots that are present!

=== Virtual Airlines ===

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

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

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

=== Did you know ===
... that you can easily set [[anti-aliasing]] to improve FlightGear's graphic display?
[[Category:FlightGear Newsletter|2010 12]]

FlightGear Newsletter December 2010

2010-12-18T08:16:13Z

Statto: /* Scenery corner */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

==2010 annual==
2010 was the year in which:
* FlightGear 2.0 was released.
* most of the existing virtual airlines were merged into [[Atlas Virtual Airlines]], making it the largest and by far most active FlightGear based airline.
* shaders started to be used all over the sim, introducing some new graphical eye candy as semi-realistic water reflections, 3D cities.
* the CVS servers broke down after a hardware failure, leading to our move to Git.
* detailed landclassing was created for various locations around the world.
* anaglyphic (3D) was introduced; making FlightGear the first flightsim with built-in 3D support.

== FlightGear events ==
== Call for volunteers ==
The [[OpenRadar]] project is looking for a new maintainer.

The [[TerraGear GUI]] project is looking for programmers to help create a GUI frontend for [[TerraGear]] [http://flightgear.org/forums/viewtopic.php?f=5&t=7485#p102005].

The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

== Development news ==
[[User:T3r|Torsten]] improved the handling of reduced visibility due to fog, mist or haze. The global weather now interprets weather phenomena causing reduced visibility. The code places a cloud layer starting at the ground and reaching up to a certain altitude. After climbing through this layer, visibility increases rapidly, just like in real life.
As a side effect, the opacity of 2d cloud layers are now settable via the property tree. Also accessible at the property tree are the decoded weather phenomena from METAR reports along with its descriptions and intensity.

== Nasal for newbies ==
== New software tools and projects ==

== FlightGear addons and mods ==
== In the hangar ==
=== New aircraft ===

====Bell AH-1 Cobra====
[[File:Cobra.jpg|200px|thumb|left|Cobra in action.]]The Developers at [http://alphashangar.co.nr/ Alpha-J's Hangar] have started making the Bell AH-1 Cobra. Development is going well and can be tracked [http://www.flightgear.org/forums/viewtopic.php?f=4&t=10130 here.] The Bell AH-1 Cobra is a two-bladed, single engine attack helicopter manufactured by Bell Helicopter. It shares a common engine, transmission and rotor system with the older UH-1 Iroquois. The AH-1 is also referred to as the HueyCobra or Snake.

====AgustaWestland AW139====
[[File:AW139ln.jpg|200px|thumb|left|AW139-here in the LongNose-version]]
HHS started to make the AW139, an italian midclass helicopter in use in many countries like the Netherlands, Spain, Italia, Ireland and Japan.
This work has been started due to the fact that above-average number of datas about the flightdynamic has been found, and the systems are very similar like to other new helicopters like the EC130 B4.
So you can expect another accurate helicopter next year. As special feature it is planned to simulate the 4-axis autopilot as accurate as possible.
People who would like to follow the developement can watch it at: [http://www.gitorious.org/aw139 http://www.gitorious.org/aw139]

=== Updated aircraft ===

====F5E Tiger II====
[[File:Fgfs-screen-014.png|200px|thumb|left|F5E Tiger II.]]
Has many updated aspects, please follow the link : [http://flightgear.org/forums/viewtopic.php?f=4&t=10327] . For direct download: [http://www.mediafire.com/?h3i7otzhd69h84s]

====Short S.23 Empire flying boat====

[[File:Sperry_A-2.jpg|thumb|250px|The control unit of the Sperry A-2 automatic pilot in a Short S.23 Empire flying boat.]]

The [[Short Empire|Short Empire flying boat]] has been updated with a Sperry A-2 automatic pilot by Anders, filling one of the remaining empty spots on the dashboard.

====Lockheed L-1011 Tristar====
Fresh off a 1/10 rating, the TriStar is closer to having a working cockpit. Currently there are three working photorealistic instruments. A full cockpit update is planned to be sent to the repository soon.

====Eurocopter EC130 B4====
[[File:Ec130.10.jpg|200px|thumb|right|EC130 B4- latest development version]]
Not for beginners anymore- the EC130 has been updated and the latest developement is now available in GIT. This includes a better and more accurate 3d-model with customized reflection effects, detailed mainrotor, 3d-cockpit and a more accurate fdm.
More interesting is the systems simulation: FADEC, FLI (FirstLimitIndicator) in the work, electrical systems, fuel, Force Trim Release....
This is all based on the original flight manual, and as there is no Autostart you have to follow the checklist to get this bird started. A first simple flightmanual is included.
There are still a lot of things left to do, which will be done in the next weeks and months:

*lighting
*bug fixing
*sound config
*paintkit with high detailed liveries
*completing the 3d-work
*failures
*better flightmanual

and some things more.

====Airbus A380====
After several months of remodelling and coding, the A380 has been updated and committed to the general FGdata Git repository ready for the next release of FlightGear.
The A380 comes with three liveries;
* Airbus House
* Singapore Airlines
* Qantas Airways
There are too many changes since the last "Milestone" release twelve months ago to list here. The [[Airbus A380]] wiki page details the list of items that have been completed or are still on the "To Do" list. The aircraft requires the latest Git build of FlightGear as it uses many features in the up coming release including digital filters in the autopilot, OSG Text animations and James Turners new GPS code.

=== Liveries ===

== Scenery corner ==
===Cities===
At least four of the five boroughs of New York City should have land cover in the database by the start of the new year with the only other missing borough, Manhattan, to come in the very near future. The MetLife Building, the former Pan Am building, has been modeled as well, giving Manhattan its first non-generic skyscraper!

===Land Cover===
====Eastern Europe====
Detailed scenery is under development for the E20N40 area, with the following countries partly or fully covered:
* Albania
* Bulgaria
* Hungary
* Kosovo
* FYR Macedonia
* Poland
* Romania
* Serbia
* Slovakia
* Turkey

The scenery is using Corine land classification data, road and railroad data from OpenStreetMap and SRTM v4 elevation data from CGIAR.

[[File:E20n40.png|thumb|400px|left]]
 

==== New England ====
More New England coverage as western Massachusetts has been added to the map server and therefore has been made part of the default scenery package. The next scenery release will allow users to fly from New York John F. Kennedy Int'l to Burlington, Vermont without having to pass over any vmap0 (current) scenery. More coverage is planned as well.

====Republic of Ireland====

Detailed scenery made from CORINE land cover data is now available for the Republic of Ireland. Road and railroad data is from OpenStreetMap, elevation data is SRTM v3. A nice feature of this scenery is that the coastline is rendered using the Corine shapes, so flying along the coast looks a lot prettier than the in the default vmap0 scenery. The scenery pack also contains a terminal building for Knock Ireland West Airport (EIKN) not previously seen.

See some screenshots [http://www.flightgear.org/forums/viewtopic.php?f=19&t=10326 here] and for further details see the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10354 forum announcement].

=== Airports ===
====Charlottesville Albemarle Airport (KCHO)====
[[File:DevelopmenofKCHOPart1.jpg|200px|thumb|left|KCHO under development]]I (Catchatyou) am currently working on making a new airport for FlightGear! It is Charlottesville Albemarle Airport (KCHO). I must say that I am new to Blender and FlightGear, but I am excited to be a part of it. I hope that my creation will eventually sprout into a beautiful product as time goes by. I have no set date on when this should be completed, but I hope that I can make it as soon as possible.

[[File:eddm tower.jpg|200px|thumb|right|Development version of EDDM tower]]I am not just making the airport building. I'm hoping to eventually add in the parking lot and other various objects.

Thank you for making contributing so easy.

====Franz Josef Strauss Airport Munich (EDDM)====
[[:User:D-79|D-79]] started modelling EDDM in October and is dedicated to make this the most detailed airport in Germany. So far, both terminals have been modelled, as well as most of the additional buildings on the aprons. One of the most difficult tasks proved to be setting up ground vehicles. But now they're running as an AI scenario of [http://www.youtube.com/watch?v=6GhGbV7n0Uk eight busses and trucks]. As soon as work is finished, the airport will be sent to Martin of the [[FlightGear Scenery Database]].

====Aeroporto "Gianni Caproni", Mattarello, Trento (Northern Italy) (LIDT)====
[[File:LIDT-Mattarello.jpg|200px|thumb|left|LIDT-Mattarello]]LIDT is a small touristic airport located in Mattarello, very close to Trento (Trentino Alto Adige-Sued Tyrol), and is dedicated to Giovanni Caproni, an Italian pioneer of aviation, born in Arco, near Trento.
Beside the terminal building there is an Aviation Museum containing some aircrafts built by the Caproni Factory in early XX century.

The LIDT airport is home to the [http://www.protezionecivile.tn.it/frame.asp?Site=11&Area=29&Sect=221&Subs=260 "Gruppo Elicotteri Vigili del Fuoco Trento"] (Trento Fire Dept Helicopter Group), involved in many rescue operations on the Alps.

Scighera has modeled the Main Building (Air Terminal, Tower and Aerhotel), the Caproni Aviation Museum and various hangars, including the one of the Fire Dept Helicopter Group.

The 3D models are available for download at [http://digilander.libero.it/scighera_fg/index.html scighera's Homepage] and are already available on [http://wiki.flightgear.org/index.php/TerraSync Terrasync].

===Aeroporto "Romeo Sartori", Asiago (LIDA)===
[[File:ZFoto_LIDA_Asiago_1.jpg|200px|thumb|left|LIDA-Asiago]]LIDA Asiago (Veneto, Italy) is another small touristic airport at the edge between the Po River Plains and the Eastern Alps, populated with a lot of gliders.
Scighera has modelled the few buildings there, including the "fancy" Terminal.

The few 3D models are avilable for download at [http://digilander.libero.it/scighera_fg/index.html scighera's Homepage] and have been issued to Martin for inclusion in the [[FlightGear Scenery Database]].(It has been included on Dec 13th 2010)

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

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

== Wiki updates ==
===Developed Airports===
So far, we never had a list of all developed airports in FlightGear. This has now been changed. The [[Developed Airports]] article lists all aerodromes where at least one building has been placed, be it a static (unique) models or a shared model, but only if the objects are available from the [[FlightGear Scenery Database]]. This new list is meant to become the central site where we maintain an up-to-date list of all developed airports. For setting up this list, [[:User:D-79|D-79]] used the Forum discussion [http://www.flightgear.org/forums/viewtopic.php?f=5&t=4700|List of Improved Airports in FlightGear].

[[Developed Airports]]

===Video Tutorials===
Over the past year, more and more [[Video Tutorials]] have been produced for FlightGear, so that it seemed sensible to set up a special wiki site for them, sorted by categories. Feel free to 1) make more video tutorials and 2) add them to the list. When making a video tutorial, please try to keep a certain standard: Video tutorials should have a good video resolution so that users can see what's happening on the screen, and they should have text or voice comment so that users understand what's being done.

[[File:Asi.png|thumb|120px|Airspeed indicator]]

===More Hangars===
The wiki article [[FlightGear Hangars]] has been extended by longfly. Now there are over 47 Hangars with interesting aircrafts, liveries and scenery. [http://www.flightgear.bplaced.de/filemanager/flightgear/index.php/flugzeugliste Longfly's german hangar] for example has begun to create a list of all aircrafts available for FlightGear. There are currently 412, which must be insert.

===Instrument glass reflection tutorial===
Horacio has written an excellent short tutorial to show how to add glass reflection effect to instruments, using graphic tools, so that the reflection effect is already contained in the main instrument image, and not depending on shaders meaning less CPU load. The result is widely satisfactory and very realistic.

[[Howto: Glass reflection effect for instruments]]

===Helipad category===
We have a new wiki [[:Category:Helipads|category for helipads]], as a sub-category of the [[:Category:Airports|airports category]]. So far, only the [[oil platforms]] can be found there, but others could be added, like hospital helipads or ANWB/ADAC/ÖAMTC heliports.

[[:Category:Helipads]]

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

== Community news ==
=== FlightGear on youtube ===
=== New tutorials and screencasts ===
Check out Zexe's video Tips and Tricks for Flightgear. Tips include how to Target-track, overlay instrument numbers, and so on. You can find them here on the wiki at [[Video_Tutorials#Advanced_options|Video Tutorials (advanced options)]] and on the [http://flightgear.org/forums/viewtopic.php?f=19&t=9811 forum].

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===

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

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

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

=== Did you know ===

[[Category:FlightGear Newsletter|2010 12]]

FlightGear Newsletter December 2010

2010-12-07T00:15:51Z

Statto: /* New England */

FlightGear Newsletter December 2010

2010-12-07T00:14:58Z

Statto: /* Scenery corner */

FlightGear Newsletter December 2010

2010-12-07T00:12:57Z

Statto: /* Updated aircraft */

FlightGear Newsletter November 2010

2010-11-20T06:47:56Z

Statto: /* Scenery corner */

FlightGear Newsletter November 2010

2010-11-20T06:45:17Z

Statto:

FlightGear Newsletter November 2010

2010-11-20T06:41:26Z

Statto: FPS doesn't need to be in the wiki

FlightGear Newsletter October 2010

2010-10-04T02:48:33Z

Statto: /* In the hangar */

FlightGear Newsletter October 2010

2010-10-04T02:46:38Z

Statto: /* Suggested flights */

FlightGear Newsletter September 2010

2010-09-02T03:09:26Z

Statto: /* Suggested flights */

FlightGear Newsletter September 2010

2010-09-02T03:08:56Z

Statto: /* Suggested flights */

FlightGear Newsletter September 2010

2010-09-02T03:06:55Z

Statto: /* Suggested flights */

Frequently asked questions

2010-08-29T22:41:09Z

Statto: /* Flying */

Common help destinations: [[Aircraft]], [[Howto: Multiplayer|Multiplayer Help]], [[Installing Scenery]], and [[Flying the Helicopter]].

'''This FAQ has not been significantly updated since 2006.''' 

''' Feel free to make additions, changes, or corrections.'''

== The FAQ ==
=== Where can I get the latest version of this FAQ? ===
http://wiki.flightgear.org/index.php/FAQ

=== Who do I contact if I have comments about this FAQ? ===

Add your comment to this FAQ's discussion page [[Talk:FAQ]]

=== How old is this document? ===

Click the History button in the menu on the left.

=== What other important documentation should I read? ===

* [http://flightgear.org/Docs/getstart/getstart.html Getting Started Guide]
* [[New to FlightGear]]
* Also see the FlightGear/docs-mini/ directory in the source distribution for various other helpful documents.
* Also see the other [http://www.flightgear.org/Docs/FAQ.shtml FAQ]

== Distribution ==

=== Where can I get FlightGear? ===

The official download page is http://www.flightgear.org/Downloads/. Source code is our primary form of distribution, but precompiled binaries are available for Windows and SGI IRIX.

Alternatively, FlightGear is packaged for Linux by SuSE, Debian (sid), and Mandrake (Cooker) and can be directly installed through those distributions.

=== How do I install Flight Gear on Ubuntu? ===

Flight Gear can be installed directly from the Synaptic Package Manager.
Open Synaptic Package Manager, search for Flight Gear and follow instructions. For Ubuntu 9.10 you will be able to install Flight Gear 1.9.1

=== What is the password for the FTP server? ===

The FTP server uses standard anonymous login procedures. Login with the username "anonymous" and use your email address as the password. Most FTP clients and web browsers will do this automatically for you.

=== Why won't the FTP server let me in with the right login info? ===

This generally means that the server is at it's capacity. You should receive a message saying such, but your FTP client may be hiding it from you. Your options are to keep trying until a slot opens up or try connecting to one of our FTP mirrors listed at http://flightgear.org/mirrors.html.

=== Where can I find the latest development source code? ===

The latest development code is available for everyone through our CVS repository. See http://www.flightgear.org/cvsResources/ for details.

Otherwise, you can get relatively up-to-date snapshots of the development tree at ftp://flightgear.sourceforge.net/pub/flightgear/Devel/Snapshots/.

=== What is SimGear, and why do I need it? ===

[[SimGear]] is a library of supporting code. SimGear is only needed if you plan on compiling FlightGear -- it is not needed to run precompiled binaries. For more information see http://www.simgear.org/. Note: When compiling FlightGear it is very important to have the matching version of SimGear.

=== Where can I fly and where do I get the scenery? ===

While the base package only comes with scenery for the San Francisco Bay area, you can currently fly just about anywhere in the world. See the "Additional Scenery" section of http://www.flightgear.org/Downloads/ for more information or go directly to our graphical downloader at http://www.flightgear.org/Downloads/scenery-1.0.1.html

Also visit our "Places to Fly" section of the website (http://www.flightgear.org/Places/) for some help navigating to some awesome locations. (see also [[Installing Scenery]])

=== Where can I get different 3D models for my plane? ===

Official FlightGear aircraft can be found at http://www.flightgear.org/Downloads/aircraft/ . Other aircraft in development can be found on [[CVS]], and some other aircraft can be found on 3rd party [FlightGear hangars]].

=== How current is the data in FlightGear compared to the real world? ===

We use the same navaid and airport dataset that X-Plane uses. The current dataset can be found in the $FGROOT/Navaids/ and $FGROOT/Airports/ directories. If you have updates or corrections to the dataset, see http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html for instructions on contacting the database maintainer.

=== Where is the moving map? ===

A popular moving map display is available under a separate project called [[Atlas]] (See http://atlas.sf.net/) Also, [[MPmap]] is an online map for multiplayer.

If you like an alternative to Atlas with updated graphics and mapping provided by the openstreetmap project, then check out Flightgear Mapping [[http://rubyforge.org/projects/fgmap fgmapping]]

=== Why don't you charge money for this? ===

FlightGear can be downloaded for free from many locations including the FlightGear website, but can also be bought on a CD. Although we offer that service (see the website), we encourage other groups to redistribute it for their users, especially within an operating system distribution which makes installation even faster and easier for new users.

Occasionally you may see FlightGear for sale on auction sites or commercial websites under some other name. This can be done quite legitimately as long as the terms of the license are upheld and might be worth the cost if some value-added features such as additional scenery, aircraft or after-sale support are included. Unfortunately, most cases seen to date appear to be just someone trying to make money selling something that is free and providing no real added value.

===How can I get started with FlightGear===

FlightGear [[FlightGear 1.0.0|version 1.0]] can be downloaded at [http://www.flightgear.org/Downloads/ Download Central], but most [[aircraft]] need to be separately downloaded [http://www.flightgear.org/Downloads/aircraft/ Here] and installed manually (see also [[FlightGear 1.0 default aircraft]]). Be aware of system requirements! Also, check out [[New to FlightGear]].

== Compiling ==
{{main article|Building Flightgear}}

=== Why won't FlightGear compile? ===

Well, that depends. First make sure you are using the appropriate versions of FlightGear, [[SimGear]], plib, zlib. If any of the packages are out of sync with the others, compilation may fail. See also [[Building FlightGear]]

The FlightGear Downloads page (http://www.flightgear.org/Downloads/) should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Also ensure that you have some implementation of OpenGL with glut support with the appropriate header files. Linux users with nVidia cards should make sure you have the latest drivers from nVidia. Other Linux users make sure you have Mesa3D (http://mesa3d.org/) and your X server installed correctly.

If your problems persist, subscribe to our FlightGear-Users mailing list and let us know what problem you're having. See http://www.flightgear.org/mail.html for help with this.

=== I'm using RedHat 7, and ...? ===

Update your gcc packages. See http://redhat.com/errata/ to fix it and http://www.gnu.org/software/gcc/gcc-2.96.html for an explanation why.

== Configuring ==

=== How do I install new scenery? ===

The scenery archive files (ie. w100n30.tar.gz) should be untarred into the Scenery/Terrain directory in your $FG_ROOT.

=== How do I setup my joystick(s)? ===

FlightGear should come with a helpful program called `fgjs` that can help configure your joystick. Run `fgjs` and then copy the dot file it created into your home directory or add its contents to your existing rc file.

Also, see the README.Joystick file located in the FlightGear/docs-mini/ directory of the source distribution and the [[Joystick]]-page on the wiki.

=== What format should my personal .fgfsrc file be in? ===

Your .fgfsrc file should simply be a list of [[Command Line Parameters|command line options]] with one option per line. The file is not an XML file.

If you would rather use an [[XML]] configuration file, you can add something like the following in your .fgfsrc

<code> --config=/path/to/my/config.xml</code>

Almost every option corresponds to a property, so you can choose to use whichever method best suits your needs.

== Running ==

=== Why do I get an error loading libopenal.so.0? ===

With the default installation, libopenal.so.0 is installed into /usr/local/lib. You need to ensure that that path is listed in /etc/ld.so.conf, then run `ldconfig`as root.

=== Why do I get "ssgInit called without a valid OpenGL context"? ===

In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

Why do some other GL applications work though? Well, Steve Baker (Mr. PLIB) has explained this on the plib-users list (http://www.geocrawler.com/lists/3/SourceForge/1867/0/6470648/).

=== What happened to the panel, keyboard, etc? ===

The problem is almost certainly that your base package is out of sync with FlightGear. Many configurable parts of FlightGear are defined in [[XML]] files contained in the base package.

=== Why doesn't audio work properly under Irix? ===

FlightGear (as of June 2001) uses the Portable Libraries ([[PLIB]]) for playing audio. The audio queue implementation of PLIB is far from optimal (in fact it's just wrong). This seems to work on other platforms quite well, but Irix expects things to be programmed properly.

There has been discussion about using OpenAL (http://www.openal.org/) for the next release of both PLIB and FlightGear. Tests show that the OpenAL audio implementation does the job right, meaning that these audio problems should be gone by then. In the mean time it is best to disable audio on Irix completely (by adding --disable-sound either on the command line or to your $HOME/.fgfsrc file).

=== Why is FlightGear so slow? ===

FlightGear supports hardware acceleration, but it seems not to be activated. Make sure you have OpenGL libraries installed and configured properly and make sure you have the latest drivers for your video card.

Linux users: If you are an nVidia user, follow their directions on getting your card working. For most other users, make sure Mesa is installed property and ensure that you have the appropriate kernel device drivers for your card. Most people (and distributions) use modules for their video card device drivers; run `lsmod` as root to see what modules are loaded. You should also make sure that you are loading the appropriate modules in your XF86Config and that your video device section is correct. Now try running an OpenGL application (other than FlightGear) to see how it performs. You can try the gears demo from Mesa or something like Quake3.

=== Why is my SGI machine so slow? ===

First of all, one of the most common mistakes on SGI hardware is to forget to specify --fog-fastest. On most SGI machines the EXP2 shading model isn't hardware supported resulting in frame rates below 1 frame per second (fps).

FlightGear makes extensive use of the OpenGL z-buffer feature,which on most older SGI hardware is only supported in software. This means that the CPU has to do all the z-buffer calculations in addition to the other tasks FlightGear involves (flight dynamics, scenery tracking, pushing commands into the graphics queue, etc). The following features are software rendered on low-end SGI machines (like Indy and Indigo):

* stencil and accumulation buffer
* depth queuing and depth buffering
* fogging, lighting, clipping and transforms
* texturing

This means that running FlightGear with the following options may not even get the desired result:

<code> ./runfgfs --fog-disable --shading-flat --disable-skyblend --disable-textures --disable-clouds --disable-sound --disable-panel --enable-hud --disable-anti-alias-hud </code>

I could even imagine that adding --enable-wireframe doesn't work on these machines (I would be happy to be proven wrong though).

On a machine like O2 the following options give an acceptable result:
<code>./runfgfs --fog-fastest --disable-sound</code>

Since I don't have access to other SGI hardware I can't tell which options would be appropriate for your situation.

=== How do I see the frame rate? ===

On the menu select View, Rendering Options , then check the box
that says Show Frame Rate

=== How do I toggle panel settings? ===

There are two ways. One way is to hide the panel without the HUD showing. To hide the panel, use Shift+P; To make the HUD disappear, use H. The second way is to use the alternative HUD by Shift+I (Use I to switch back).

=== Stuck upside down after "crash"? ===

In his infinite wisdom the FlightGear Grand Master decided that planes were too valuable to allow them to be destroyed by novice pilots who seemed to crash a lot. The fact that nobody has bothered to model crashes may have something to do with it too. :-)

The result of this as you have noticed is that with a little practice an ingenuity you can trim the ship to fly inverted along the ground.

The quick answer is to hit Ctrl+U (with the default key bindings) to warp the plane up 1000ft.

For the stubborn people out there: The trick to learn is to roll back to normal (non inverted) do this by nursing the elevator to get to about 500 feet or so and use the ailerons to snap roll 180*. This is all good avionics except for the plane not destroying itself. Remember the controls work in reverse when you are inverted and keep that airspeed up!!!

=== Why does FlightGear die on startup saying "time zone reading failed"? ===

This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files.

=== Why won't the latest versions of some aircraft work in Flight Gear 9.10? ===

The latest FlightGear aircraft need to use some files such as new instrument files only released with [[FlightGear 1.0|version 1.0]]. If you are stuck with an older version of FlightGear you can try downloading an earlier version of the aircraft here : http://web.archive.org/web/20060204211745/www.flightgear.org/Downloads/aircraft/
or here:http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/

== Hacking ==

=== What language is FlightGear written in? ===

Mostly C++ with some supporting C code that's primarily contained within SimGear.

=== How do I design a flight dynamics model for a new aircraft? ===

To define an aircraft for FlightGear's primary FDM ([[JSBSIM]]), see http://jsbsim.sf.net/.

If you want a simpler FDM to work with, try your hand at [[YASim]], an alternative FDM. For an guide on creating a YASim aircraft, look in the FlightGear base package for Aircraft-yasim/README.yasim.

=== How do I import planes from Microsoft Flight Simulator? ===

You can import planes by using the 3D Convert utility which will convert
the MSFS 3d model to a format used by Flight Gear. You have to add the
animations and parts.

Also, although you can import the 3D model and textures, the flight dynamics (the .AIR file) must be completely redone for FlightGear.

If you wish to import a model made with gmax, you will need to convert it to .MDL format using Microsoft's MakeMDL SDK which is available at http://zone.msn.com/flightsim/FS02DevDeskSDK08.asp.

=== How do I import BGL scenery from Microsoft Flight Simulator? ===

See http://chiangt.virtualave.net/BGL/bgl_index.html.

=== How do I design or modify a panel? ===

See the README.xmlpanel file located in the FlightGear/docs-mini/ directory of the source distribution.
----

=== How do I place objects, like buildings, into FlightGear? ===

First, ensure that you have v0.7.7 or later, the scenery files where you plan to place the object, the actual model, and the longitude and latitude where you plan to place the object.

Now get the altitude for your point. If you don't want to calculate this yourself, start FlightGear at your location and take note of the altitude. Here's an example command:

fgfs --lat=45.50 --lon=-75.73 2>&1 | tee fgfs.log

The altitude is probably in feet, so divide the starting altitude by 3.28.

Search the output log file for the first occurrence of the string "Loading tile" and take note of the filename. In the above example, the output line looks like:

Loading tile /usr/local/Scenery/w080n40/w076n45/1712601

Copy a 3D model in a format that Plib understands to the same directory as the tile file. Edit the text file in that directory consisting of the tile name with the extension ".stg". The file will already exist if there is an airport on the tile; otherwise, you can create it from scratch. In our example, the filename is:

<code>/usr/local/Scenery/w080n40/w076n45/1712601.stg</code>

At the end of the file, add a new entry for your object, consisting of the word "OBJECT_STATIC" followed by the model name, the longitude in degrees, the latitude in degrees, the altitude in meters, and the heading in degrees. In our example the line looks like:

OBJECT_STATIC Towerax.ac -75.73 45.40 60 0

Save the changes to the .stg file, restart FlightGear, and enjoy.

NOTE: The above information was taken from the following mailing list post: http://www.geocrawler.com/archives/3/11854/2001/6/0/5991409/. See that page if this one doesn't make sense.

An alternative approach using PPE is described at http://mail.flightgear.org/pipermail/flightgear-devel/2001-December/002239.html by Norman Vine.

With Flightgear 0.9.10 there is an easy way for [[ Placing 3D Objects with the UFO ]]

See also [[ FlightGear Scenery Designer ]].

=== Where can I learn 3D programming and how do I get involved? ===

Contributing to the 2D panel doesn't require any coding at all, just a minimal knowledge of [[XML]] syntax (i.e. five minutes' worth) and good skills with drawing and/or paint programs. Every instrument on the current panel, with the partial exception of the magnetic compass, is defined entirely in XML with no custom C++ code. If you want to get started, take a look at John Check's excellent intro (http://rockfish.net/fg/README.xmlpanel).

Likewise, if you want to create a 3D cockpit for FlightGear, or to create buildings, external aircraft models, etc., your help is *desperately* needed. The only rule is to go easy on the triangles -- a model with 50,000 triangles probably won't be usable in FlightGear, and one with 5,000 triangles, only marginally. If you can design a nice 3D cockpit interior for in a 3D design program such as [[AC3D]] or [[PPE]], there may be coders who will be happy to add the support code in the C++.

If, on the other hand, you really want to get your hands dirty with C++ coding, you'll have to buy a good [[OpenGL]] book eventually. However, FlightGear uses a high-level library, [[PLIB]], that hides most of the details of OpenGL. To get started with 3D C++ coding, you can take a look at the plib documentation and learn only as much OpenGL as you need, when you need it.

=== How do I add an airport? ===

You can add your airport to the $FGROOT/Airports/default.apt.gz file, but to get the airport to show up visually, you will have to rebuild the scenery around the airport. The format of the default.apt file is documented at http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html.

=== Can I generate my own scenery? ===

Yes, though it can be a difficult task. FlightGear's scenery generation is handled by a sister project, [[TerraGear]]. For more details, see http://terragear.org/.

== Flying ==

=== Why won't my engine(s) start? ===

====Starting engine in single-engine aircraft====
Aircraft vary in their starting procedure. Some may have an auto-start sequence menu entry or instructions in the aircraft help menu (Press "?").

But in general to start the engine on a piston-engine type aircraft, you need:

# Fuel - You can run out of fuel, of course, but for certain aircraft, FlightGear may load it with no fuel, making it impossible to start the engines. Check this in the menu Equipment/Fuel and Payload.
# Correct mixture (generally "rich", ie red knob all the way in)
# Magnetos on (R, L, or both--generally select "both")
# Throttle (some engines start better with a little gas)
# Hold starter for sufficient time.

You may be able to do all these functions with the standard 2-D panel or your aircraft's built-in panel. However using the standard key bindings is more reliable:

# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set it somewhere besides full rich)
# Press "}}}" (three times) to set magneto to R, L, and finally "Both".
# Open throttle a little.
# Press "s" to run the starter. For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.

====Starting engine in multi-engine aircraft====
Starting all engines in a multi-engine aircraft is similar to the single engine--except you must follow the same start sequence for each and every engine. Flightgear provides a convenient way to do this for all engines at once.

Note that the default 2-D panel is connected to ''only one engine''. So if you try to start the engines using the 2-D panel controls you will most likely start only one engine.

Instead, use the keyboard to start all engines at once:

# Press "~" (select all engines)
# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set the mixture somewhere besides full rich)
# Press "}}}" (three times) to set magnetos to R, L, and finally "Both".
# Open throttle a little (it now controls all engines).
# Press "s" to run the starter (it now runs the starter on all engines). For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.
# Rev the engines a little with your throttle and check your tachometers and/or visually to be sure all engines are running.

If the engines won't start, make sure you have fuel. Some aircraft have switches to control which fuel tanks feed which engines, so check these.

Make sure each engine you want to start is connected to a tank that has fuel. Check fuel tanks in the menu Equipment/Fuel and Payload.

=== Where can I learn about instrument flying and navigation? ===

http://www.navfltsm.addr.com/ is a very good site for learning techniques for navigation.

[http://www.av8n.com/how/ See How It Flies] a very nice book by John S. Denker, freely accessible online

Please see [[Understanding Navigation]]

=== What is the difference between Aileron and Rudder? ===

There is a bit of info on aileron vs. rudder in the very same book...

=== Is there support for multi-player flying? ===

Yes. Both the Windows and *nix versions of FlightGear are capable of multi-player flying on FlightGear servers.

Wiki: [http://wiki.flightgear.org/flightgear_wiki/index.php?title=Multiplayer_Howto Multiplayer_Howto]

A map showing players aircraft online in real time is available:
[http://pigeond.net/flightgear/fg_server_map.html FlightGear Online Server Map] (see also [[MPmap]])

=== Where are the best places to fly in FlightGear? ===

FlightGear scenery covers the whole world, but thanks to the FlightGear user community, certain airports and areas are more detailed than others. For a full list of airports with buildings available in the default scenery, visit the forum's [http://flightgear.org/forums/viewtopic.php?f=5&t=4700&st=0&sk=t&sd=a|list of improved airports].

* There are a lot of high-quality scenery models around Paris, France.
* EHAM Amsterdam Schiphol, EGKK London Gatwick and LFPG Paris Charles de Gaulle are some of the highest quality airports in FlightGear.
* TNCM St. Maarten is a popular destination, and the surrounding islands (Anguilla, St. Eustatius, Saba, St. Barthélemy, St. Kitts, and Nevis) are all well-modeled.

=== Where can I find airport info and aeronautical charts online? ===
Airports:
* [http://www.airnav.com/airports/ AirNav.com]

Charts:
* [http://skyvector.com/ SkyVector.com]

=== Is there support for any military scenarios like dog fighting or bomb dropping? ===

Most of our developers are primarily interested and focused on civilian aviation. We aren't explicitly excluding these features -- we just haven't had anyone who has done much development in these areas until recently. Now there are third-party bombing scenarios for the [[A-10]] and other aircraft with armament, like the [[North American OV-10A Bronco]], [[General Dynamics F-16]] and [[F-117 Nighthawk]].

[http://flightgear.org/forums/viewtopic.php?f=2&t=5742 A new add-on (9/2009)] adds support for dogfighting (including multiplayer dogfighting) and bombing scenarios.

== FlightGear v0.7.6 ==

=== Why do I get an error in viewer.cxx about `exit' being undeclared? ===

This error cropped up after the release of v0.7.6. To fix the problem, add "#include <stdlib.h>" to the top of viewer.cxx.

== FlightGear v1.0.0 ==

=== How could I be ATC? ===
It's not yet possible to be an [[ATC]] with the stable version, you should download the CVS version.

[[es:Preguntas frecuentes]]
[[fr:Foire aux questions]]
[[pl:FAQ]]

Frequently asked questions

2010-08-29T22:17:06Z

Statto: /* How do I generate my own scenery? */

Common help destinations: [[Aircraft]], [[Howto: Multiplayer|Multiplayer Help]], [[Installing Scenery]], and [[Flying the Helicopter]].

'''This FAQ has not been significantly updated since 2006.''' 

''' Feel free to make additions, changes, or corrections.'''

== The FAQ ==
=== Where can I get the latest version of this FAQ? ===
http://wiki.flightgear.org/index.php/FAQ

=== Who do I contact if I have comments about this FAQ? ===

Add your comment to this FAQ's discussion page [[Talk:FAQ]]

=== How old is this document? ===

Click the History button in the menu on the left.

=== What other important documentation should I read? ===

* [http://flightgear.org/Docs/getstart/getstart.html Getting Started Guide]
* [[New to FlightGear]]
* Also see the FlightGear/docs-mini/ directory in the source distribution for various other helpful documents.
* Also see the other [http://www.flightgear.org/Docs/FAQ.shtml FAQ]

== Distribution ==

=== Where can I get FlightGear? ===

The official download page is http://www.flightgear.org/Downloads/. Source code is our primary form of distribution, but precompiled binaries are available for Windows and SGI IRIX.

Alternatively, FlightGear is packaged for Linux by SuSE, Debian (sid), and Mandrake (Cooker) and can be directly installed through those distributions.

=== How do I install Flight Gear on Ubuntu? ===

Flight Gear can be installed directly from the Synaptic Package Manager.
Open Synaptic Package Manager, search for Flight Gear and follow instructions. For Ubuntu 9.10 you will be able to install Flight Gear 1.9.1

=== What is the password for the FTP server? ===

The FTP server uses standard anonymous login procedures. Login with the username "anonymous" and use your email address as the password. Most FTP clients and web browsers will do this automatically for you.

=== Why won't the FTP server let me in with the right login info? ===

This generally means that the server is at it's capacity. You should receive a message saying such, but your FTP client may be hiding it from you. Your options are to keep trying until a slot opens up or try connecting to one of our FTP mirrors listed at http://flightgear.org/mirrors.html.

=== Where can I find the latest development source code? ===

The latest development code is available for everyone through our CVS repository. See http://www.flightgear.org/cvsResources/ for details.

Otherwise, you can get relatively up-to-date snapshots of the development tree at ftp://flightgear.sourceforge.net/pub/flightgear/Devel/Snapshots/.

=== What is SimGear, and why do I need it? ===

[[SimGear]] is a library of supporting code. SimGear is only needed if you plan on compiling FlightGear -- it is not needed to run precompiled binaries. For more information see http://www.simgear.org/. Note: When compiling FlightGear it is very important to have the matching version of SimGear.

=== Where can I fly and where do I get the scenery? ===

While the base package only comes with scenery for the San Francisco Bay area, you can currently fly just about anywhere in the world. See the "Additional Scenery" section of http://www.flightgear.org/Downloads/ for more information or go directly to our graphical downloader at http://www.flightgear.org/Downloads/scenery-1.0.1.html

Also visit our "Places to Fly" section of the website (http://www.flightgear.org/Places/) for some help navigating to some awesome locations. (see also [[Installing Scenery]])

=== Where can I get different 3D models for my plane? ===

Official FlightGear aircraft can be found at http://www.flightgear.org/Downloads/aircraft/ . Other aircraft in development can be found on [[CVS]], and some other aircraft can be found on 3rd party [FlightGear hangars]].

=== How current is the data in FlightGear compared to the real world? ===

We use the same navaid and airport dataset that X-Plane uses. The current dataset can be found in the $FGROOT/Navaids/ and $FGROOT/Airports/ directories. If you have updates or corrections to the dataset, see http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html for instructions on contacting the database maintainer.

=== Where is the moving map? ===

A popular moving map display is available under a separate project called [[Atlas]] (See http://atlas.sf.net/) Also, [[MPmap]] is an online map for multiplayer.

If you like an alternative to Atlas with updated graphics and mapping provided by the openstreetmap project, then check out Flightgear Mapping [[http://rubyforge.org/projects/fgmap fgmapping]]

=== Why don't you charge money for this? ===

FlightGear can be downloaded for free from many locations including the FlightGear website, but can also be bought on a CD. Although we offer that service (see the website), we encourage other groups to redistribute it for their users, especially within an operating system distribution which makes installation even faster and easier for new users.

Occasionally you may see FlightGear for sale on auction sites or commercial websites under some other name. This can be done quite legitimately as long as the terms of the license are upheld and might be worth the cost if some value-added features such as additional scenery, aircraft or after-sale support are included. Unfortunately, most cases seen to date appear to be just someone trying to make money selling something that is free and providing no real added value.

===How can I get started with FlightGear===

FlightGear [[FlightGear 1.0.0|version 1.0]] can be downloaded at [http://www.flightgear.org/Downloads/ Download Central], but most [[aircraft]] need to be separately downloaded [http://www.flightgear.org/Downloads/aircraft/ Here] and installed manually (see also [[FlightGear 1.0 default aircraft]]). Be aware of system requirements! Also, check out [[New to FlightGear]].

== Compiling ==
{{main article|Building Flightgear}}

=== Why won't FlightGear compile? ===

Well, that depends. First make sure you are using the appropriate versions of FlightGear, [[SimGear]], plib, zlib. If any of the packages are out of sync with the others, compilation may fail. See also [[Building FlightGear]]

The FlightGear Downloads page (http://www.flightgear.org/Downloads/) should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Also ensure that you have some implementation of OpenGL with glut support with the appropriate header files. Linux users with nVidia cards should make sure you have the latest drivers from nVidia. Other Linux users make sure you have Mesa3D (http://mesa3d.org/) and your X server installed correctly.

If your problems persist, subscribe to our FlightGear-Users mailing list and let us know what problem you're having. See http://www.flightgear.org/mail.html for help with this.

=== I'm using RedHat 7, and ...? ===

Update your gcc packages. See http://redhat.com/errata/ to fix it and http://www.gnu.org/software/gcc/gcc-2.96.html for an explanation why.

== Configuring ==

=== How do I install new scenery? ===

The scenery archive files (ie. w100n30.tar.gz) should be untarred into the Scenery/Terrain directory in your $FG_ROOT.

=== How do I setup my joystick(s)? ===

FlightGear should come with a helpful program called `fgjs` that can help configure your joystick. Run `fgjs` and then copy the dot file it created into your home directory or add its contents to your existing rc file.

Also, see the README.Joystick file located in the FlightGear/docs-mini/ directory of the source distribution and the [[Joystick]]-page on the wiki.

=== What format should my personal .fgfsrc file be in? ===

Your .fgfsrc file should simply be a list of [[Command Line Parameters|command line options]] with one option per line. The file is not an XML file.

If you would rather use an [[XML]] configuration file, you can add something like the following in your .fgfsrc

<code> --config=/path/to/my/config.xml</code>

Almost every option corresponds to a property, so you can choose to use whichever method best suits your needs.

== Running ==

=== Why do I get an error loading libopenal.so.0? ===

With the default installation, libopenal.so.0 is installed into /usr/local/lib. You need to ensure that that path is listed in /etc/ld.so.conf, then run `ldconfig`as root.

=== Why do I get "ssgInit called without a valid OpenGL context"? ===

In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

Why do some other GL applications work though? Well, Steve Baker (Mr. PLIB) has explained this on the plib-users list (http://www.geocrawler.com/lists/3/SourceForge/1867/0/6470648/).

=== What happened to the panel, keyboard, etc? ===

The problem is almost certainly that your base package is out of sync with FlightGear. Many configurable parts of FlightGear are defined in [[XML]] files contained in the base package.

=== Why doesn't audio work properly under Irix? ===

FlightGear (as of June 2001) uses the Portable Libraries ([[PLIB]]) for playing audio. The audio queue implementation of PLIB is far from optimal (in fact it's just wrong). This seems to work on other platforms quite well, but Irix expects things to be programmed properly.

There has been discussion about using OpenAL (http://www.openal.org/) for the next release of both PLIB and FlightGear. Tests show that the OpenAL audio implementation does the job right, meaning that these audio problems should be gone by then. In the mean time it is best to disable audio on Irix completely (by adding --disable-sound either on the command line or to your $HOME/.fgfsrc file).

=== Why is FlightGear so slow? ===

FlightGear supports hardware acceleration, but it seems not to be activated. Make sure you have OpenGL libraries installed and configured properly and make sure you have the latest drivers for your video card.

Linux users: If you are an nVidia user, follow their directions on getting your card working. For most other users, make sure Mesa is installed property and ensure that you have the appropriate kernel device drivers for your card. Most people (and distributions) use modules for their video card device drivers; run `lsmod` as root to see what modules are loaded. You should also make sure that you are loading the appropriate modules in your XF86Config and that your video device section is correct. Now try running an OpenGL application (other than FlightGear) to see how it performs. You can try the gears demo from Mesa or something like Quake3.

=== Why is my SGI machine so slow? ===

First of all, one of the most common mistakes on SGI hardware is to forget to specify --fog-fastest. On most SGI machines the EXP2 shading model isn't hardware supported resulting in frame rates below 1 frame per second (fps).

FlightGear makes extensive use of the OpenGL z-buffer feature,which on most older SGI hardware is only supported in software. This means that the CPU has to do all the z-buffer calculations in addition to the other tasks FlightGear involves (flight dynamics, scenery tracking, pushing commands into the graphics queue, etc). The following features are software rendered on low-end SGI machines (like Indy and Indigo):

* stencil and accumulation buffer
* depth queuing and depth buffering
* fogging, lighting, clipping and transforms
* texturing

This means that running FlightGear with the following options may not even get the desired result:

<code> ./runfgfs --fog-disable --shading-flat --disable-skyblend --disable-textures --disable-clouds --disable-sound --disable-panel --enable-hud --disable-anti-alias-hud </code>

I could even imagine that adding --enable-wireframe doesn't work on these machines (I would be happy to be proven wrong though).

On a machine like O2 the following options give an acceptable result:
<code>./runfgfs --fog-fastest --disable-sound</code>

Since I don't have access to other SGI hardware I can't tell which options would be appropriate for your situation.

=== How do I see the frame rate? ===

On the menu select View, Rendering Options , then check the box
that says Show Frame Rate

=== How do I toggle panel settings? ===

There are two ways. One way is to hide the panel without the HUD showing. To hide the panel, use Shift+P; To make the HUD disappear, use H. The second way is to use the alternative HUD by Shift+I (Use I to switch back).

=== Stuck upside down after "crash"? ===

In his infinite wisdom the FlightGear Grand Master decided that planes were too valuable to allow them to be destroyed by novice pilots who seemed to crash a lot. The fact that nobody has bothered to model crashes may have something to do with it too. :-)

The result of this as you have noticed is that with a little practice an ingenuity you can trim the ship to fly inverted along the ground.

The quick answer is to hit Ctrl+U (with the default key bindings) to warp the plane up 1000ft.

For the stubborn people out there: The trick to learn is to roll back to normal (non inverted) do this by nursing the elevator to get to about 500 feet or so and use the ailerons to snap roll 180*. This is all good avionics except for the plane not destroying itself. Remember the controls work in reverse when you are inverted and keep that airspeed up!!!

=== Why does FlightGear die on startup saying "time zone reading failed"? ===

This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files.

=== Why won't the latest versions of some aircraft work in Flight Gear 9.10? ===

The latest FlightGear aircraft need to use some files such as new instrument files only released with [[FlightGear 1.0|version 1.0]]. If you are stuck with an older version of FlightGear you can try downloading an earlier version of the aircraft here : http://web.archive.org/web/20060204211745/www.flightgear.org/Downloads/aircraft/
or here:http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/

== Hacking ==

=== What language is FlightGear written in? ===

Mostly C++ with some supporting C code that's primarily contained within SimGear.

=== How do I design a flight dynamics model for a new aircraft? ===

To define an aircraft for FlightGear's primary FDM ([[JSBSIM]]), see http://jsbsim.sf.net/.

If you want a simpler FDM to work with, try your hand at [[YASim]], an alternative FDM. For an guide on creating a YASim aircraft, look in the FlightGear base package for Aircraft-yasim/README.yasim.

=== How do I import planes from Microsoft Flight Simulator? ===

You can import planes by using the 3D Convert utility which will convert
the MSFS 3d model to a format used by Flight Gear. You have to add the
animations and parts.

Also, although you can import the 3D model and textures, the flight dynamics (the .AIR file) must be completely redone for FlightGear.

If you wish to import a model made with gmax, you will need to convert it to .MDL format using Microsoft's MakeMDL SDK which is available at http://zone.msn.com/flightsim/FS02DevDeskSDK08.asp.

=== How do I import BGL scenery from Microsoft Flight Simulator? ===

See http://chiangt.virtualave.net/BGL/bgl_index.html.

=== How do I design or modify a panel? ===

See the README.xmlpanel file located in the FlightGear/docs-mini/ directory of the source distribution.
----

=== How do I place objects, like buildings, into FlightGear? ===

First, ensure that you have v0.7.7 or later, the scenery files where you plan to place the object, the actual model, and the longitude and latitude where you plan to place the object.

Now get the altitude for your point. If you don't want to calculate this yourself, start FlightGear at your location and take note of the altitude. Here's an example command:

fgfs --lat=45.50 --lon=-75.73 2>&1 | tee fgfs.log

The altitude is probably in feet, so divide the starting altitude by 3.28.

Search the output log file for the first occurrence of the string "Loading tile" and take note of the filename. In the above example, the output line looks like:

Loading tile /usr/local/Scenery/w080n40/w076n45/1712601

Copy a 3D model in a format that Plib understands to the same directory as the tile file. Edit the text file in that directory consisting of the tile name with the extension ".stg". The file will already exist if there is an airport on the tile; otherwise, you can create it from scratch. In our example, the filename is:

<code>/usr/local/Scenery/w080n40/w076n45/1712601.stg</code>

At the end of the file, add a new entry for your object, consisting of the word "OBJECT_STATIC" followed by the model name, the longitude in degrees, the latitude in degrees, the altitude in meters, and the heading in degrees. In our example the line looks like:

OBJECT_STATIC Towerax.ac -75.73 45.40 60 0

Save the changes to the .stg file, restart FlightGear, and enjoy.

NOTE: The above information was taken from the following mailing list post: http://www.geocrawler.com/archives/3/11854/2001/6/0/5991409/. See that page if this one doesn't make sense.

An alternative approach using PPE is described at http://mail.flightgear.org/pipermail/flightgear-devel/2001-December/002239.html by Norman Vine.

With Flightgear 0.9.10 there is an easy way for [[ Placing 3D Objects with the UFO ]]

See also [[ FlightGear Scenery Designer ]].

=== Where can I learn 3D programming and how do I get involved? ===

Contributing to the 2D panel doesn't require any coding at all, just a minimal knowledge of [[XML]] syntax (i.e. five minutes' worth) and good skills with drawing and/or paint programs. Every instrument on the current panel, with the partial exception of the magnetic compass, is defined entirely in XML with no custom C++ code. If you want to get started, take a look at John Check's excellent intro (http://rockfish.net/fg/README.xmlpanel).

Likewise, if you want to create a 3D cockpit for FlightGear, or to create buildings, external aircraft models, etc., your help is *desperately* needed. The only rule is to go easy on the triangles -- a model with 50,000 triangles probably won't be usable in FlightGear, and one with 5,000 triangles, only marginally. If you can design a nice 3D cockpit interior for in a 3D design program such as [[AC3D]] or [[PPE]], there may be coders who will be happy to add the support code in the C++.

If, on the other hand, you really want to get your hands dirty with C++ coding, you'll have to buy a good [[OpenGL]] book eventually. However, FlightGear uses a high-level library, [[PLIB]], that hides most of the details of OpenGL. To get started with 3D C++ coding, you can take a look at the plib documentation and learn only as much OpenGL as you need, when you need it.

=== How do I add an airport? ===

You can add your airport to the $FGROOT/Airports/default.apt.gz file, but to get the airport to show up visually, you will have to rebuild the scenery around the airport. The format of the default.apt file is documented at http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html.

=== Can I generate my own scenery? ===

Yes, though it can be a difficult task. FlightGear's scenery generation is handled by a sister project, [[TerraGear]]. For more details, see http://terragear.org/.

== Flying ==

=== Why won't my engine(s) start? ===

====Starting engine in single-engine aircraft====
Aircraft vary in their starting procedure. Some may have an auto-start sequence menu entry or instructions in the aircraft help menu (Press "?").

But in general to start the engine on a piston-engine type aircraft, you need:

# Fuel - You can run out of fuel, of course, but for certain aircraft, FlightGear may load it with no fuel, making it impossible to start the engines. Check this in the menu Equipment/Fuel and Payload.
# Correct mixture (generally "rich", ie red knob all the way in)
# Magnetos on (R, L, or both--generally select "both")
# Throttle (some engines start better with a little gas)
# Hold starter for sufficient time.

You may be able to do all these functions with the standard 2-D panel or your aircraft's built-in panel. However using the standard key bindings is more reliable:

# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set it somewhere besides full rich)
# Press "}}}" (three times) to set magneto to R, L, and finally "Both".
# Open throttle a little.
# Press "s" to run the starter. For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.

====Starting engine in multi-engine aircraft====
Starting all engines in a multi-engine aircraft is similar to the single engine--except you must follow the same start sequence for each and every engine. Flightgear provides a convenient way to do this for all engines at once.

Note that the default 2-D panel is connected to ''only one engine''. So if you try to start the engines using the 2-D panel controls you will most likely start only one engine.

Instead, use the keyboard to start all engines at once:

# Press "~" (select all engines)
# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set the mixture somewhere besides full rich)
# Press "}}}" (three times) to set magnetos to R, L, and finally "Both".
# Open throttle a little (it now controls all engines).
# Press "s" to run the starter (it now runs the starter on all engines). For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.
# Rev the engines a little with your throttle and check your tachometers and/or visually to be sure all engines are running.

If the engines won't start, make sure you have fuel. Some aircraft have switches to control which fuel tanks feed which engines, so check these.

Make sure each engine you want to start is connected to a tank that has fuel. Check fuel tanks in the menu Equipment/Fuel and Payload.

=== Where can I learn about instrument flying and navigation? ===

http://www.navfltsm.addr.com/ is a very good site for learning techniques for navigation.

[http://www.av8n.com/how/ See How It Flies] a very nice book by John S. Denker, freely accessible online

Please see [[Understanding Navigation]]

=== What is the difference between Aileron and Rudder? ===

There is a bit of info on aileron vs. rudder in the very same book...

=== Is there support for multi-player flying? ===

Yes. Both the Windows and *nix versions of FlightGear are capable of multi-player flying on FlightGear servers.

Wiki: [http://wiki.flightgear.org/flightgear_wiki/index.php?title=Multiplayer_Howto Multiplayer_Howto]

A map showing players aircraft online in real time is available:
[http://pigeond.net/flightgear/fg_server_map.html FlightGear Online Server Map] (see also [[MPmap]])

=== Where can I find airport info and aeronautical charts online? ===
Airports:
* [http://www.airnav.com/airports/ AirNav.com]

Charts:
* [http://skyvector.com/ SkyVector.com]

=== Is there support for any military scenarios like dog fighting or bomb dropping? ===

Most of our developers are primarily interested and focused on civilian aviation. We aren't explicitly excluding these features -- we just haven't had anyone who has done much development in these areas until recently. Now there are third-party bombing scenarios for the [[A-10]] and other aircraft with armament, like the [[North American OV-10A Bronco]], [[General Dynamics F-16]] and [[F-117 Nighthawk]].

[http://flightgear.org/forums/viewtopic.php?f=2&t=5742 A new add-on (9/2009)] adds support for dogfighting (including multiplayer dogfighting) and bombing scenarios.

== FlightGear v0.7.6 ==

=== Why do I get an error in viewer.cxx about `exit' being undeclared? ===

This error cropped up after the release of v0.7.6. To fix the problem, add "#include <stdlib.h>" to the top of viewer.cxx.

== FlightGear v1.0.0 ==

=== How could I be ATC? ===
It's not yet possible to be an [[ATC]] with the stable version, you should download the CVS version.

[[es:Preguntas frecuentes]]
[[fr:Foire aux questions]]
[[pl:FAQ]]

FlightGear Newsletter June 2010

2010-06-23T17:53:46Z

Statto: /* Scenery corner */

{{newsletter}}
{{TOC_right}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone (with a wiki account, free to register) can edit the newsletter and every contribution is welcome.''

==Development news==
===SquawkGear: Bringing VATSIM to FlightGear!===
{{Main article|SquawkGear}}
SquawkGear is the much-awaited client that allows FlightGear users to connect to the largest and most realistic sim server in the world: [http://vatsim.net/ VATSIM]. VATSIM is simply a network that can, in theory, take any sim, although the current ones are X-Plane and Microsoft Flight Simulator. Using addons like SquawkBox for MSFS, pilots must adhere to strict rules about realism. A valid [[flight plan]] must always be submitted before takeoff, for instance. And pilots must contact [[Air Traffic Control]] before any actions.

SquawkGear brings this wonderful server to FlightGear. While installation is not as simple as that of VATSIM clients for MSFS, pilots are now able to connect to the VATSIM network and use chat and voice to communicate with other players and ATC. Since [[scenery]] is very different between sims, aircraft do not always appear where they are supposed to be; a MSFS user might see you hovering a few feet above the ground, for instance.

With its first release, SquawkGear is an excellent addon for pilots wishing to get on VATSIM without having to buy the payware sims. It is strongly recommended that you '''read all manuals''' before connecting to VATSIM; not only because installation is tricky, but also because there are certain rules to be followed on VATSIM. You will find that your [[KSFO]] on VATSIM is a thousand times more under control than your KSFO on one of the [[Howto: Multiplayer|mpservers]]!

''Special thanks to Ivan (Reed) for all of his work!''

===Bombable air combat add-on updated===
The [http://www.flightgear.org/forums/viewtopic.php?f=2&t=5742 Bombable air combat add-on to FlightGear] received a major update in June. Bombable now has these features:

* Dogfight against other FlightGear pilots over multiplayer with Sopwith Camel, SPAC VII, Fokker DR 1 Triplane, or A6M2 Zero
* Explode/burn when you crash
* Exceeding aircraft limitations (excess g-forces, overspeed) adds damage to your aircraft and finally leads to shutdown/crash
* Shootable/bombable moving AI tanks, jeeps, ships, and aircraft that catch fire, burn, explode, sink, crash, etc.
* AI scenarios that allow you to use FlightGear aircraft for air-to-ground, air-to-sea, and air-to-air combat missions against these targets

==In the hangar==
===Boeing 787 and CRJ-200===
''nickyivyca'' is currently working on the [[Boeing 787]]. He corrected the [[FDM]] and changed some details in the model.
More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8203 in the forums].

He has also been working in the [[CRJ-200]]:

''"The CRJ-200 and 787 were made with very similar systems and such. Neither had a 2.0 compatible AP. So, I found out what was wrong with the one for the 787 first, and made those changes to the CRJ here. Both worked. I also did some FDM improvements, like moving the engines to where they really are and adding gear smoke and contrails."'' - says he [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8329 in the forum thread].

===Cessna T-37===
''richter'' and ''snipey'' are working together in improving the Cessna T-37. Items that have been improved/created:

'''Model:'''
* Completely remodeled canopy;
* Main gear wheel wells and covers.
'''Sound:'''
* Interior-exterior sound level difference.
'''Instruments:'''
* Basic flight instruments.

More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8354 at the forum].

===CH-47 Chinook===
''MOJO'' is tuning the CH-47. He spent some time adding external cosmetics which main purpose is to add more detail to the Chinook. He added antenna and aerials, domed windows, pitot tubes, whinch, engine hub details and started with the internal cargo bay. He is going to be adding an animated refuel probe and will be doing some more liveries also, his main aim is to try and get the model more defined.

===Cirrus Vision SF50===
''Zexe'' created a SF50 model. It is still at a very early stage. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8352 here].

===MiG-15bis===
''vitos'' improved the MiG-15bis model, and released it. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7486 here].

===MB-339 PAN===
The MB-339 PAN aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8604 was updated by ''Albert''] to work with [[FlightGear]] version 2.0.0.

===San Antonio LPD17===
Browsing through the files, ''HHS'' [http://www.flightgear.org/forums/viewtopic.php?f=23&t=8351 found a rotorcraft carrier model] and made a scenario to run it, which is available on [[Git]].

==Scenery corner==
===Nighttime London Gatwick===
London Gatwick (EGKK) is being further improved and is in the second phase of development - night textures. All the buildings and features are currently being modified by ''karla'' to give suitable lighting and make London Gatwick even more attractive to FlightGear commercial flyers. Landing or taking off from Gatwick at night should add much to your enjoyment of the game - and most likely extend the hours you enter in your pilot's log.
Further improvements and many minor changes are also being made to the existing models and daytime textures.
The link shows an image of the part completed airport at night http://www.donlavelle.net/flightgear/flightgear19.html.

The new scenery will be released early in July.

===Dubai airport gets busy===
With the terrain updates that were discussed in the [[FlightGear Newsletter March 2010#Dubai is coming up|March edition]] still in our minds, we now have another feature for the area; taking it yet another step closer to a bussy and realistic representation of the real emirate!

After looking jealously at the greatly enhanced airport [[Amsterdam Airport Schiphol|Schiphol]] (EHAM) and the latest highlight Gatwick (EGKK) Mike ([[User:D-SKY1|D-SKY1]]) decided to create [[Interactive_Traffic|interactive traffic]] for [[Dubai International Airport]] (OMDB). Based on the existing airport layout in FlightGear the traffic pattern for taxiing between gates and runways has been created in [[TaxiDraw]] next to a timetable for runway usage.

Although no modelwork is done (yet) a big bunch of scheduled flights is now added to this important hub in the middle east. As Dubai is home port for Emirates Airlines (UAE) only Emirates flights are included. Within the next weeks more scheduled flights for AI traffic at Dubai will be added. During the process of creating AI traffic he tried to stay as close as possible to the real life timetable for Dubai International Airport querying several sources for double checking.

As Emirates Airlines (UAE) is one of the most important customers for the [[Airbus A380]] (UAE just ordered another 30 units of A380) the Emirates Airlines livery has been added to AI aircrafts A380. Additionally some minor errors in several traffic files concerning changed [[ICAO]] codes for some airports have been removed.

All changes are available via [[Git]]. Enjoy the enhancements; and always follow [[SID]]s and [[STAR]]s to prevent collisions.

===Meadows Field and FGSignMaker===
''skyop'' released his improvements to the Meadows Field (KBFL) scenery. Read [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8466 this topic] for more information.

He is also writing [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8596 FGSignMaker], a tool to generate taxiway sign codes wrote in JavaScript. It is still in alpha version as of 2010-06-22, but should be soon released.

===Landcover additions===
Connecticut, Oshkosh (Wisconsin, USA) and the Toronto Harbor have been added to the FlightGear mapserver. They will be released to the public with the next scenery build, or alternatively the shapefiles can be downloaded and compiled by the user.

This is in addition to the other numerous improvements to the land cover which are pending with the next scenery release, which includes (but is not limited to) France; Madrid, Spain; London, England; Bonn, Germany; Western Washington, USA; Northwest Oregon, USA; Phoenix, Arizona, USA; Washington, DC, and Baltimore, Maryland, USA; Rhode Island; Hawaii; and Long Island, New York, USA.

Land cover development is ongoing.

==Multiplayer News==
===Atlas Virtual Airlines' leaders recognised!===
[[Atlas Virtual Airlines]], FlightGear's most populated airline, has been a hit success in its inaugural months since opening in mid-April. The airline, however, couldn't have made it without the guidance of its two current leaders: ''MaverickAlex'' (Alex Park) and ''SkyWlf77'' (Jason Sheperd). Besides sinking their own cash into the airline for site domain and software, these two founding members have sorted out many mis-judgements of Atlas and helped to form a strong and community-bonding airline. Jason, the vice-chairman and moderator, helped revamp AVA's standing on the forums and turned many former anti-Atlas-ers into supporting members, which has been very beneficial for the FlightGear multiplayer community. Thanks to him, members can now feel confident to join an airline that was, just months ago, in the midst of intense controversy. Sheperd has taken a strong stand against arguments and flame wars on the Forums, intent on preventing the locked-topics and arguing members that degraded the VA Community during the VA "Dark Ages". But now, Atlas has flourised into a friendship-filled and happy organization that members find enjoyment and fun in.

Meanwhile, Alex, the current chairman and administrator, independently designed an awesome and top-of-the-line VA website for Atlas pilots. He has also worked with nightmares of coding to get drawing-board ideas implemented. And on top of it all, Alex is finishing up his Bombardier Dash-8 400Q, designed especially for Atlas Express flights. This very nicely modeled aircraft will also be available to the public, underlining how Atlas Virtual Airlines is really benefiting all of FlightGear. Alex is the brains behind it all that makes Atlas so sophisticated. His partner, Jason, has the ideas and people-person skills that gives Atlas the openess and fun that attracts its 50-plus members. So, from all of Atlas and those who follow it, thank you, Jason and Alex!

BRIEFS: Atlas celebrated its 50th member this month, a landmark achievement for a VA that is still newborn!

==Aircraft Review==
'''This month: B-25 Mitchell'''

[[Image:B-25.jpg|thumb|270px|A B-25 in the air near KATL]]
The [[B-25]] served in almost every theatre in World War II. From Europe to the Pacific, the Mitchell was there. One of the most famous missions accomplished by B-25s was the Doolittle Raid on Tokyo, when a group of 16 B-25s attacked the Japanese mainland, raising morale in the United States, and changing the priorities of the Imperial Japanese Navy, and possibly changing the direction of the war.

The flightgear model looks good on the outside. The author has done a lot of work on the textures, and this is improved even more by some excellent liveries made by Gooneybird that have been added to the B-25 base package by the author. The landing gear, engines and canopies are all carefully modelled, too.

The Cockpit is a little bit threadbare, with no chairs, two pilot figures, and the standard six instruments, which is more than enough to fly with. The only other issue I could come up with was the lack of weapons, but that is only an aesthetic problem. The B-25 handles nicely both on the ground and in the air. I can't talk about accuracy, however, as I have never flown in a B-25, so I don't know how it 'feels' in the air.

The Mitchell sounds great, too!

''Review by Armchair Ace''

==From the community==
===LinuxTAG===
Once again, a team of FlightGear enthusiasts operated a booth during the four days of this year's [http://www.linuxtag.org/ LinuxTAG], the most important place for Linux and open source software in Europe. Besides to it's main purpose of presenting FlightGear to a public audience, LinuxTag becomes more and more '''the''' place for a meeting of core FlightGear developers and users. A technical discussion between James, Alex and Matthias has the potential to become a ''FlightGear legend'' and will probably lead to a multithreaded processing within the simulator's core. Alex also held a public presentation about the integration of [http://www.linuxtag.org/2010/en/program/free-conference/all-events/details.html?talkid=329 "Android for pilots"] with fgfs. [http://www.linuxtag.org/2010/fileadmin/www.linuxtag.org/slides/Alex%20Perry%20-%20Android%20for%20Pilots%20-%20Integration%20with%20the%20FlightGear%20Flight%20Simulator.pdf]

An exciting first contact was initiated between FlightGear team members and a hardware vendor resulting in an idea to operate a shared presentation of powerful hardware running a powerful flight simulator at the next year's LinuxTAG - to proof the claim "where .com meets .org".

===FlightGear on YouTube===
* ''edubletooth'' captured a [http://www.youtube.com/watch?v=EeQUfnHLs_Q bunch of landings] at the airports with the world's most famous approach: [[Princess Juliana International Airport|Princess Juliana]] in the Netherlands Antilles. Make sure to bend when a 777-200 or maybe even a mighty [[Boeing 747|747]] is passing just meters over your head!
* [http://www.youtube.com/watch?v=nzCcqtkTUT8 This excellent video] proves that ''Howto'' Oscar (we already mentioned him last month) does more than creating howtos. Together with Don's extremely detailed simulation of Gatwick Airport (EGKK), Oscar's video angles make this an interesting and pleasant video to watch.

==And finally...==
===Your own Copilot===
How about having your own Copilot to help you fly your heavy metal? Imagine: You're at 3000 ft making a hand controlled descent to EGKK 26L in your [[Boeing 777-200|777-200ER]]: "flaps down"; check airspeed and altitude; you're now five miles out; "undercarriage down"; reduce speed a little more; "flaps down"; you seem to be slightly overspeed; "spoilers"; touch down "brakes" then "reverse thrust"; "flaps retract"; now take a look at the detailed scenery while taxying to your stand; "view" and "zoom out".

Those using Windows can employ '''Shoot''' - a free user-editable voice command utility. This may be used concurrently with FlightGear to recognize spoken words or phrases and carry out keyboard actions - including sequential or Shift/Alt/Ctrl... keying. Unfortunately Linux users do not have access to such a powerful utility.

[http://clans.gameclubcentral.com/shoot Download Shoot 1.6.4] and install it on your PC. You also need the Microsoft Speech API (SAPI) which is also free; the link is given on the Shoot website. The free Microsoft .NET should also be installed using the Shoot link.

Shoot may be edited to obey verbal commands such as "start engines", "maximum thrust", "undercarriage up", "flaps retract", "trim nose down", "deploy spoilers", "reverse thrust", "view exterior" - or whatever you choose. Try it and add more immersion to your flying.

[[Category:FlightGear Newsletter|2010 06]]

===Did you know?===

* ...that in version 2.0, fellow pilots' chat messages could be ignored on [[multiplayer]] by checking the ignore box in the pilot list?
For upcoming releases, pilots' aircraft will also be able to be ignored. This is part of a strong offensive against "trolling" that disrupts MP flying. 

* ...that the USS Nimitz [[Howto: Carrier|aircraft carrier]] has deck elevators that can be lowered/raised to go below deck?
Toggle them up/down in your ATC Options menu under Carrier; Check-Apply raises them, unchecked-apply lowers them.

* ...that FlightGear is made of roughly 3,000,000 lines of code and would cost more than $42,000,000 if created from scratch? (Metrics from [http://www.ohloh.net/p/flightgear/analyses/latest ohloh.net])

Howto:Make an airport

2009-12-02T13:59:01Z

Statto: /* What you need: */

For changing [[scenery]] and airports you needed [[TerraGear]], which was always very hard to use and only for Linux. With the [[FlightGear Scenery Designer]] it is also possible to make custom airports or to change existing airports in [[FlightGear]].

===What you need:===
* [[FlightGear Scenery Designer]] - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/fgsd-win32-20060423.zip
* [[TaxiDraw]] - ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/taxidraw-win32-20061010.zip
* Runway layout data - either from the USA Airport & Scenery Database or from other free imagery
* other data about the airport you want to make
* shapes for the whole earth - ftp://ftp.ihg.uni-duisburg.de/FlightGear/TGShapes
** But that's a lot of data, so there is a another possibility - http://mapserver.flightgear.org/download.psp
* Heightmaps - http://telascience.sdsc.edu/tela_data/SRTM/version2/SRTM3/Eurasia/
* Of course FlightGear - any version

[[Ubuntu]] users, can use the script in [[Ubuntu fg tools]].

=== Let's start with making the runway layout- taxidraw ===
At first we have to define the runways and taxiways. So we use [[TaxiDraw]]. A tutorial about using TaxiDraw could be find here: http://taxidraw.sourceforge.net/taxidraw/tutorial.html

So if we have done the airport in TaxiDraw, we save it as "airport.dat". That's the X-plane-fileformat, which is used by FlightGear too. Now we unpack apt.dat.gz in the data folder of FlightGear and paste and copy our new "airport.dat" into it. Don't use any special character like "/" - it could causes a 2h long troubleshooting on your pc system ;-) Now we pack it again to apt.dat.gz. For user of Linux it is easy, windows user can use [http://www-7-zip.org 7-zip].

=== Preparation for FGSD ===
#We create a file for the shapefiles like ./shapefiles.
#Now we download all the v0-layer and save them into the folder. Don't forget to unpack!
#Now we create a folder for the heightmap like./heightmap and download the required data. Here we don't need to unpack!
# Now we open FGSD and prepare it for our work "Tools" -> "Chop HGT-Files": Set the root to the file of the "heightmaps.zip" and change it to heightmaps.arr.gz by replacing ".zip" with ".arr.gz"
# Now set the roots in "Tools"-> "Option": General: ./flightGear/scenery Our new tile will be find there later.
# FlightGear: set the root to the data-file and the root for FlightGear Scenery to the file "shapefiles"

=== FGSD ===
We have now all what we need prepared for the work, so let's start:
In "File" we look for our requested ".arr.gz" and open the requested tile.
If we don't know the name, we can use the [[UFO from the 'White Project' of the UNESCO|UFO]] and place any object at the spot we want to have the new airport. We have to look now in the generated .xml-file and we see something like 3531408.stg. So we open in our case here the tile with the name 3531408.arr.gz.

You should see now your tile. If not, play a little bit with the buttons in the scenery toolbar. "Option" and "Landcover-DB" and check the required layers. You don't need the layer "v0landmass"

Sometimes you could only see the standart-layers, but we want to have our downloaded layers. So unckeck all, exit the program and launch it again. We have to order the layer and define which texture matches to the layer. ( so as an example the v0railroads really have the right texture). We also define the weidth.

The larger textures are always above the smaller one like that:

[x]mixcrop - ein grooßes polygon, größer als urban

[x]urban

[x]drycrop - ein grooßes polygon, größer als road

[x]road

Play a litte bit with it, so you can see how it works.
Now click "Simplify Terrain" in "Scenery" the heightmodel is now beeing simplified so we can use it in FlightGear. Click "embedded Curves" - the shapefiles will now being embedded and we can see our landclasses. Our airport is still missing - select "Tools" and "Select Airport" and choose our airport. You can see it now on the tile.

"Scenery"->"embeddes airports"

Ready!

Now we export it now: "File"->"Export"

We will find our airport in <tt>./FlightGear/Scenery</tt> and copy this into <tt>./data/scenery</tt>. If we have made a airport which was not yet existing in FlightGear, so put in the IACA-Code in <tt>./application data/flightgear.org/fgrun</tt> into the list.Now we launch FlightGear and start from our new made airport!

=== next time ===
Your preparations are saved, so the next time you have just to do following things:

# open "tile.arr.gz"
# Import curves
# simplify terrain
# embedded curves
# import airports
# embedded airports
# export!

Don't forget to send your new "airport.dat" to Robin Peel, so we all will benefit from!

===Sources of errors and FAQ===
*The new made airport has no lights, towers, beacons and windsocks?
**That's right - in the moment it is only possible with terragear. But you can place in FGSD the towers, beacons and windsocks with the object editor.
*I don't see any roads and rivers?
**You have to define the width: "Tools" - "landcover DB" -> "width" maybe. 10 for smaller ones and 20 for bigger ones.
*I only see the default-texture?
**Uncheck v0-landmass
*I see only red-white chequered surfaces in FlightGear?
**Look if you have used in taxidraw the textures: others- they don't work in FlightGear.
*I can't start FlightGear?
**Look if you used special characters in apt.dat.gz - No use of special characters!

== Thanks==
'''Thanks to:'''
* Vadym who discovered this function in FGSD and showed it on the devel-list!
* Frederic Bouvier, who wrote FGSD!
* Martin Spott and Ralf Gerlich for the Landcover DB!

[[Category:Howto|Make an airport]]
[[Category:Scenery enhancement|Make an airport]]

Howto:Create custom terrain

2009-11-17T17:14:53Z

Statto:

{{WIP}}

Look [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2147 here] an example of the achievable result.

Let's take a look at the Finistère in Brittany, Western France: if you click [http://mapserver.flightgear.org/map/?lon=-4.41840585539649&lat=48.4484146908477&zoom=11&layers=0B000000FTTFFFFFTFT|here], you will quickly see and understand how the Finistère county is know of [[FlightGear]]. Some towns/city (red), a few forests (green), etc. Overall, it is not a very good resolution: a lot of angles, the detail level is not that good, some towns are missing. If you want a better definition on ground, there is some work to be done! The goal being to obtain something like this:

#[http://mapserver.flightgear.org/map/?lon=13.40385&lat=52.50199&zoom=11&layers=000000BFFFFFFFFFTFFF Berlin]
#[http://mapserver.flightgear.org/map/?lon=9.40368&lat=47.63699&zoom=11&layers=000000BFFFFFFFFFTFFF Bodensee surroundings]
#[http://mapserver.flightgear.org/map/?lon=-88.55704&lat=43.98436&zoom=11&layers=000000BFFFFFFFFFTFFF Oshkosh surroundings]
#[http://mapserver.flightgear.org/map/?lon=-62.87648&lat=17.69865&zoom=10&layers=000000BFFFFFFFFFTFFF Carribs]

You will immediately notice the improvement to the ground. When flying, the difference is huge. Moreover, this enables the autogeneration of cities, trees, farmland, and so on.

=== Downloading the Landsat pictures ===
[[File:C31e36f2a2cbb278a1603dfe2ba91193.media.395x288.png|thumb|200px|Landsat Map Search]]
[[File:1c9334d970963364b5ce1bc3a166a4fa.media.426x192.png|thumb|200px|Preview and download Landsat image]]
Browse to [http://glcfapp.umiacs.umd.edu:8080/esdi/index.jsp the Earth Science Data Interface interface] to grab your [http://en.wikipedia.org/wiki/Landsat Landsat] data.

# Click ''Map Search''.
# Tick the ETM+ box (left column).
# Click on ''Update Map'' on the right bottom of the map.
# Click on the ''Place'' tab on the upper side of the map, in order to do a search by place, or you can do a search by latitude/longitude.
# In the Place field, type ''Amsterdam, Netherlands'' for instance.
# Now click the button with the mouse and the small + sign. This will allow you to select image tiles. Select all images that cover your area of interest, in our example this is just one image.
# Click on ''Preview and download''. This bring you to a selection page were you can choose what image you want to download. It is likely that there are pictures available from different dates for your area. Picking the most recent one is best, for known reasons.
# Clicking the ID will not bring you directly to the download page, first you have to click the ''Download'' button.
# Download the _nn80.tif.gz file (if this is not available, try an older image).
# Uncompress the ''.tif.gz'' files in the directory of your choice.

=== Working with QGIS ===
[[File:QGIS_texel_1.png|thumb|200px|QGIS with the TIFF image.]]
[[File:QGIS_texel_2.png|thumb|200px|Creating the class column.]]
[[File:QGIS_texel_3.png|thumb|200px|Toggle editing.]]
[[File:QGIS_texel_4.png|thumb|200px|Tracing the small island.]]
[[File:QGIS_texel_5.png|thumb|200px|The finished small island polygon.]]
Using a GIS software gives you the opportunity to realize a full range of interesting operations: modification of VMAP data, updates on the ground classification, etc...

* If you run GNU/Linux, you can install QGIS with your usual package repositery manager; see [http://www.qgis.org/en/download/binaries.html here]. The process is easy and not described here, but it is one the QGIS website.
* If you are running Windows, download QGIS from [http://www.qgis.org/en/download/binaries.html here] (Windows - Standalone).

The following is largely adapted from the [http://stattosoftware.com/flightgear/tutorial/index.html original QGIS scenery tutorial], which you may find of use.
# Launch QGIS.
# Click on <tt>Layer > Add a Raster layer</tt>.
# Modify the filter to search for *.tif files.
# Add the TIFF file you have just downloaded.
# Click on <tt>Layer > Add a new vector layer</tt> or on the corresponding icon. A dialog should pop up.
#* Make sure the file type is an ESRI Shapefile.
#* Make sure the vector type is set to polygon.
#* You need to create a data column for this layer. Create a column called 'class'. Make sure it is a string column. Add it to the attribute list by selecting the Add Values Manually button. The 'OK' button should now be available for you to select. Select 'OK'.
#* There should be a dialog box prompting you to save your vector layer. Save it in your scenery directory with your GeoTIFF. (This is not required but significantly helps organization.)
#* A projection box should pop up. Select 'WGS 1984'. After all, that is the globe model used in FlightGear.
# Your vector layer should appear in the left-hand toolbar. You are ready to begin digitizing.
#Select the newly created layer in the layer list, toggle editing (<tt>Layer > Toggle Editing</tt>) and finally select Capture Polygon from the same menu/toolbar.
# With your mouse, left-click on a point at the southwestern edge of the small island.
# We now want to trace the outline of the island. Move your mouse to another point below the first point and click it again. Your mouse should show a red line. The points should not be redundant - for instance, as long as the line between two points is straight, there is no need for another point in between the two.
# You will want to digitize features in a circular manner to avoid problems. You can always go back and add points later. With this in mind, move your mouse to a third point on the island. A small triangle should form, representing the polygon which would result if you decided you were done with the polygon.
# Continue outlining the island by clicking along its shoreline. When you are on your last point, instead of left-clicking, right-click. QGIS will finish the polygon.
# A dialog box will pop up, asking you to type in the value for 'class'. Since this is a shoal, existing of just sand, type in ''Sand''. This step is important - it is how you know what each polygon should be mapped to in our finished scenery. A list of "allowed" materials (and thus classes) is available [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail here].

Continue with tracing all shapes on the island: towns, industrial areas, grass, farmland etc.

It is imporant to enable "snaping" now. We don't want small holes in our scenery, nor do we want overlapping polygons. Snapping adjusts each point as you go by - you will miss occasionally and have to correct it - so you don't have to worry about lining the polygons up precisely.

# Open <tt>Settings > Project Properties</tt> and click the Snapping options... button.
# Click the tickbox(es) in front of your layer(s) and set Tolerance to 20 (map units). A smaller tolerance will make it easier to work with very small and detailed layers.
# Click OK to save the snapping options.

====Distinguishing Land Class Types from LANDSAT data====
You may Google Maps or Yahoo Maps running alongside your program to see what is what on the black/white image, but most areas are recognizable without use of the software. If you need help determining what part of the black-and-white image, please currently refer to the [http://stattosoftware.com/flightgear/tutorial/index.html#distinguishing original QGIS scenery tutorial].

===Exporting the shapefile===
In order to turn the landclass into scenery we have to split it into seperate shapefiles for each landclass.

# Open the Attribute table (<tt>Layer > Open Attribute table</tt>).
# Type "Sand" (or another class) into the search box and press the Search button. This will select all polygons that have the Sand class assigned.
# Go to <tt>Layer > Save Selection as Shapefile</tt> and save the sand shapefile somewhere on your computer.
# Do the same for all other classes.
# To make the difference between land and sea (landmass) we save the entiry shapefile (<tt>Layer > Save as Shapefile</tt>).

We have been working with UTM coordinates so far. To generate scenery that can be used in FlightGear we need to convert the shapefiles to the latitude/longitude format.

* '''Windows'''
*# Download [http://www.forestpal.com/fgis.html fGIS] and install it as described.
*# Open an empty project and visit <tt>Utilities > Shapefile Projection Utility</tt>.
*# Look up your projects UTM coordinate through [http://upload.wikimedia.org/wikipedia/commons/e/ed/Utm-zones.jpg this image]. For Texel this is 31U, so we choose UTM31 in fGIS. If your project is located south of the equator, you tick the S box.
*# Set the Output Shapefile Project to <tt>Lat./Lon.</tt>.
*# Now click the Input Shapefile button to load the shapefile that we exported from QGIS.
*# Using the Output Shapefile button we decide where we want to store the lat/lon shapefile. This has to be a non-exisiting file, so remove before updating.
*# Click the Convert button.
*# Repeat this process for all shapefiles.

If you want to see these shapefiles integrated into the Custom Scenery database you can contact papillon81 and statto (through IRC or Forum). Please be remembered that your data has to be derived from freely available (public domain) sources. Other material can not be integrated due to legal issues.

===Generating scenery===
Please continue with [[TerraGear]] to generate the landclass into useable scenery.

== External links ==
* [http://www.custom-scenery.org Terragear-cs website]
* [http://wiki.qgis.org QGIS Wiki]
* [http://www.flightgear.org/forums/viewforum.php?f=5 Dedicated FlightGear forums for scenery enhancement]
* [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail OSGEO Wiki]

===Resources===
* [http://stattosoftware.com/flightgear/tutorial/index.html Tutorial by John Holden]

[[Category:Howto|Using QGIS and satellite pictures]]
[[Category:Scenery enhancement|Using QGIS and satellite pictures]]

[[fr:Howto: Utilisé QGIS et images satellites]]

FlightGear Newsletter October 2009

2009-10-17T05:48:55Z

Statto: /* Scenery Corner */

Welcome to the fourth edition of the [[FlightGear]] Newsletter.

This is currently the skeleton newsletter for the next edition. Please feel free to contribute!

We're still looking for a permanent (or even a temporary) newsletter editor, so if you'd like to get involved, have a look on the [http://www.flightgear.org/forums/ Forums].

==What's new in CVS==
==In the hangar==
===737-900ER in Devel===
XSaint is currently developing a Boeing 737-900ER, a variant of the B737NG. Currently in general testing, the plane is estimated to be released between this November and next Ferbruary.

==Scenery Corner==
From New York state, '''Long Island''' and '''Staten Island''' have been submitted for inclusion in the repository.

Also, for those with TerraGear, the state of '''Hawaii''' is almost completely rendered in FlightGear.

==A living community==
===FS Weekend===
The [[FS Weekend]] is the largest flight simulator event in the world. Each year it takes place at the first or second weekend of November, this years event is held at '''7 and 8 November'''. The event is held in the Aviodrome musuem, located at [[Lelystad Airport]], the Netherlands. Since 2006 FlightGear has been represented each year, by a small team of enthusiastics, and this year will be no exception. If you like to join the team or if you happen to be around, write an email to the [http://flightgear.org/mail.html mailinglist].

===ADC Contests enters the FG Community?===
This year, alphaMedia proposed an extension of the prestegious [[ADC Contests]] into the developing community of FlightGear. The ADC is a contest to create the best 3D aircraft models in the general internet, with almost 600 models included in the two years it has been held. Starting as a simple contest in [[SketchUp]], the ADC has become the second largest regular-basis modeling contest on Google and become the parent project of [[Skynet Virtual]]. AM is currently negotiating the extension with the developers of the new [[Boeing 737]] creators. More information can be found below:
* [http://sketchup.google.com/3dwarehouse/cldetails?mid=5fa1e771a5fe644b73d31fb3d707307e ADC 2010 Contest Site]
* [http://alphamedia.webs.com/adccontests.htm ADC Info on alphaMedia]

==Addons==
===Airport Diagram Generator===
Ever wondered how pilots know what exit to take on the runway, how to get from the gate to the runway and how the tower can tell them what route to follow? Well, they use maps, like you and I use in daily life when we need to find an adress. Instead of streetnames, the run- and taxiways have numbers and a letter of the alphabet (eg. 28L, S1).

The [[Airport Diagram Generator]] is a Java application capable of generating [[:Category:Airports|airport]] diagrams using FlightGear data only. These diagrams are [[GNU GPL]] and can be used for all kinds of purposes whether you are [[ATC]]ing or flying. The diagrams contain a schematic layout of the airport (taxiways and runways), ([[ILS]]) frequencies, navaids and so on.

==Useful links==
Budd Davisson is a long time aviation journalist in the USA. His [http://www.airbum.com website] includes a huge archive of [http://www.airbum.com/pireps.html pilot reports] from lots of different aircraft, many of which are modeled in FG. It's a great resource for those wanting to get an impression of what flying the real aircraft is like, and also often contains useful information on how to actually fly them.

==Virtual Community==
Coastal Air Systems, with its seemingly endless continue growth in expansion, creates its own Board of Directors. Late in the evening on October 15, 2009, the head of the virtual company sent emails congratulating the first 5 members on the newly formed Board of Directors. Each person in CAS' Board of Directors has specific duties that will ultimately help Coastal Air Systems function and become better oriented into serving, promoting, and expanding the Flight Gear community. Truthfully not every new member of the BoD for CAS knew that they were involved in the selection. Yes, being a little embarrassed, that includes me. However, not only me but I am sure the rest of the newly selected members are proud of the announcement. This is Wookierabbit, and I will keep you posted on the most updated details throughout the month in this small section.

Currently, a majority of virtual airlines are in high demand for more pilots. A few newly developed alliances are in high demand for more virtual airlines to join.

'''List of Airlines/Alliances in high demand'''

Airlines:
Americair Airlines,
Aurelen Europe Airlines

Alliances:
Sky Alliance (Partner of Star Alliance)

Begin your search here:
---
[http://www.flightgear.org/forums/index.php Flight Gear Forum]

-By Wookierabbit

==And finally....==

[[Category:FlightGear Newsletter|2009 10]]

Landmark Wish List

2009-10-05T15:10:31Z

Statto:

This page provides a list of important landmarks which are not currently in FlightGear Scenery that the community would like to see modeled. If you are a FlightGear modeler and are looking for something to model, please consider something on this list.

Feel free to add to this list.

If you are modeling a landmark, please change the "Completed" column from "No" to "Claimed".

{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" | Landmark
! style="background:#efefef" | City
! style="background:#efefef" | Country
! style="background:#efefef" | Completed
|-
|Brooklyn Bridge || New York || USA || No
|-
|Empire State Building || New York || USA || No
|-
|Chrysler Building || New York || USA || No
|-
|United Nations Headquarters || New York || USA || No
|-
|White House || Washington, D.C. || United States of America || No
|-
|Burj Dubai || Dubai || United Arab Emirates || No
|-
|Burj al Arab || Dubai || United Arab Emirates || No
|-
|Big Ben || London || England || '''Yes'''
|-
|Petronas Towers || Kuala Lumpur || Malaysia || No
|-
|Christ the Redeemer || Rio de Janeiro || Brazil || No
|-
|Westminster Abbey || London || England || '''Yes'''
|-
|Sydney Opera House || Sydney || Australia || No
|-
|Colosseum || Rome || Italy || No
|-
|Sky Tower || Auckland || New Zealand || No
|-
|Bank of China Tower || Hong Kong || Hong Kong || No
|-
|CCTV Tower || Beijing || China || No
|-
|Space Needle || Seattle || USA - Washington || '''Yes'''
|-
|Navy Pier || Chicago || USA || No
|-
|Adler Planetarium || Chicago || USA || No
|-
|Soldier Field || Chicago || USA || No
|-
|McCormick Place || Chicago || USA || No
|-
|U.S. Cellular Field || Chicago || USA || No
|-
|Wrigley Field || Chicago || USA || No
|-
|Shedd Aquarium || Chicago || USA || No
|-
|Union Station || Chicago || USA || No
|-
|Oglivie Transportation Center || Chicago || USA || No
|-
|Smurfit-Stone Building || Chicago || USA || No
|-
|Marina City || Chicago || USA || No
|-
|Millenium Park || Chicago || USA || No
|-
|United Center || Chicago || USA || No
|-
|Milwaukee Art Museum || Milwaukee || USA || No
|-
|Zwischenahner Meer || Zwischenahn, Niedersachsen || Germany || No
|-
|Porta Westfalica/Hermans-Denkmal || Bückeburg (ETHB), Minden || Germany || No
|-
|Lapan || Oldenburg, Niedersachsen || Germany || No
|-
|Schloss || Oldenburg || Germany || No
|}

==Related==

===Internal links===
*[[FlightGear Scenery Designer]]
*[[FlightGear Scenery Database]]
*[[UK_Scenery_Wish_List]]
===External links===
* [http://www.flightgear.org/forums/viewtopic.php?f=5&t=2390 The forum topic]
*See [http://scenemodels.flightgear.org/ FGFS Scenery Object Database], for more on models for [[Scenery]]

[[Category:Scenery]]
[[Category:Community]]

FlightGear Newsletter September 2009

2009-09-15T04:27:20Z

Statto: /* Scenery Corner */

Welcome to the third edition of the [[FlightGear]] Newsletter. This edition is still being written, so feel free to contribute,

The newsletter is still a bit thin on contributions, so if you'd like to contribute, please feel free to log onto the wiki and start editing the next edition [[FlightGear Newsletter October 2009| here]]. We're still looking for a permanent (or even a temporary) newsletter editor, so if you'd like to get involved, have a look on the [http://www.flightgear.org/forums/ Forums].

==What's new in CVS==
===New shaders===
{| cellpadding="4" cellspacing="0" align="right" style=""
|-
| align="left" style="background:#fafafa; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" | [[Image:SnowAtAltitude1.jpg|200px|Image:SnowAtAltitude1.jpg]]
| align="left" style="background:#fafafa; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" border-top:1px solid #CCCCCC;| [[Image:SnowAtAltitude2.jpg|200px|Image:SnowAtAltitude2.jpg]]
|-
| align="center" colspan="2" style="background:#fafafa; font-size: 85%; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-bottom:1px solid #CCCCCC;"|
Scenery around [[LFLJ]] with the snow effect disabled (left) and enabled (right).
|}

Recently new [[shaders]] have upgraded the visual realism of FlightGear. Thanks to the hard work of Till Busch and Tim Moore, we now see snow at high peaks and reflections in the water.

The new effects can be enabled through the <tt>View > Rendering Options</tt> dialog.

==New wiki articles ==

==In the hangar==

==Scenery Corner==
{| cellpadding="4" cellspacing="0" align="right" style=""
|-
| align="left" style="background:#fafafa; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" | [[Image:Maui03.jpg|200px|Image:Maui03.jpg]]
| align="left" style="background:#fafafa; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" border-top:1px solid #CCCCCC;| [[Image:Maui10.jpg|200px|Image:Maui10.jpg]]
|-
| align="center" colspan="2" style="background:#fafafa; font-size: 85%; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-bottom:1px solid #CCCCCC;"|Screenshots from the beta build of the new, still unreleased Maui scenery.
|}

The official FlightGear scenery land cover database now has new custom Hawai'i data. Generated from NOAA land cover data, FlightGear now has high quality coverage for six of the eight islands of Hawai'i (Kauai, Oahu, Molokai, Lanai, Maui, and Kahoolawe). The south coast of Oahu, including Honolulu, also features incredibly accurate coastline and land cover data created Unfortunately, with the exception of Maui, the data has not yet been turned into scenery, but Maui has produced some stunning visuals so far! Hawai'i soon will be a popular scenery area for fans of both civil and military aircraft.

New landmarks are always being added to the [http://scenemodels.flightgear.org scenery object repository]. New recent landmarks include the Ho Chi Minh mausoleum in Vietnam to Carrow Road in Norfolk England, the stadium for Norwich City Football Club. Lighthouses from around the UK continue to pop up. Modelers continue to focus on airports, and there are new buildings at EDDP Leipzig, Germany; KNUQ Moffatt Field (in the default scenery!); and KJAN Jackson, Mississippi. Next time you're looking for a place to fly, keep these places in mind!

==A living community==
===TransGear Airways===
[[TransGear Airways]] is a new group of people from the FlightGear community, gathering once a month. At coordinated times, each pilot will depart from his/her respective home base on the "spokes" of TransGears airway network, and convene together at its "hub", before exchanging passengers and flying back to their home base. While realism is one of the aims of the gatherings, everyone is welcome, as long as one is trying to follow more or less realistic procedures.

The first upcoming gathering will take place at September 12th at [[KBWI]]. Check [http://www.flightgear.org/forums/viewtopic.php?f=10&t=5789 the forum] for more information and registration.

==Useful links==

==And finally...==

[[Category:FlightGear Newsletter|2009 9]]

FlightGear Newsletter September 2009

2009-09-15T04:26:30Z

Statto: /* Scenery Corner */

Welcome to the third edition of the [[FlightGear]] Newsletter. This edition is still being written, so feel free to contribute,

The newsletter is still a bit thin on contributions, so if you'd like to contribute, please feel free to log onto the wiki and start editing the next edition [[FlightGear Newsletter October 2009| here]]. We're still looking for a permanent (or even a temporary) newsletter editor, so if you'd like to get involved, have a look on the [http://www.flightgear.org/forums/ Forums].

==What's new in CVS==
===New shaders===
{| cellpadding="4" cellspacing="0" align="right" style=""
|-
| align="left" style="background:#fafafa; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" | [[Image:SnowAtAltitude1.jpg|200px|Image:SnowAtAltitude1.jpg]]
| align="left" style="background:#fafafa; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" border-top:1px solid #CCCCCC;| [[Image:SnowAtAltitude2.jpg|200px|Image:SnowAtAltitude2.jpg]]
|-
| align="center" colspan="2" style="background:#fafafa; font-size: 85%; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-bottom:1px solid #CCCCCC;"|
Scenery around [[LFLJ]] with the snow effect disabled (left) and enabled (right).
|}

Recently new [[shaders]] have upgraded the visual realism of FlightGear. Thanks to the hard work of Till Busch and Tim Moore, we now see snow at high peaks and reflections in the water.

The new effects can be enabled through the <tt>View > Rendering Options</tt> dialog.

==New wiki articles ==

==In the hangar==

==Scenery Corner==
{| cellpadding="4" cellspacing="0" align="right" style=""
|-
| align="left" style="background:#fafafa; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" | [[Image:Maui03.jpg|200px|Image:Maui03.jpg]]
| align="left" style="background:#fafafa; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" border-top:1px solid #CCCCCC;| [[Image:Maui10.jpg|200px|Image:Maui10.jpg]]
|-
| align="center" colspan="2" style="background:#fafafa; font-size: 85%; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-bottom:1px solid #CCCCCC;"|Screenshots from the beta build of the new Maui scenery. This should be available to the public soon.|}

The official FlightGear scenery land cover database now has new custom Hawai'i data. Generated from NOAA land cover data, FlightGear now has high quality coverage for six of the eight islands of Hawai'i (Kauai, Oahu, Molokai, Lanai, Maui, and Kahoolawe). The south coast of Oahu, including Honolulu, also features incredibly accurate coastline and land cover data created Unfortunately, with the exception of Maui, the data has not yet been turned into scenery, but Maui has produced some stunning visuals so far! Hawai'i soon will be a popular scenery area for fans of both civil and military aircraft.

New landmarks are always being added to the [http://scenemodels.flightgear.org scenery object repository]. New recent landmarks include the Ho Chi Minh mausoleum in Vietnam to Carrow Road in Norfolk England, the stadium for Norwich City Football Club. Lighthouses from around the UK continue to pop up. Modelers continue to focus on airports, and there are new buildings at EDDP Leipzig, Germany; KNUQ Moffatt Field (in the default scenery!); and KJAN Jackson, Mississippi. Next time you're looking for a place to fly, keep these places in mind!

==A living community==
===TransGear Airways===
[[TransGear Airways]] is a new group of people from the FlightGear community, gathering once a month. At coordinated times, each pilot will depart from his/her respective home base on the "spokes" of TransGears airway network, and convene together at its "hub", before exchanging passengers and flying back to their home base. While realism is one of the aims of the gatherings, everyone is welcome, as long as one is trying to follow more or less realistic procedures.

The first upcoming gathering will take place at September 12th at [[KBWI]]. Check [http://www.flightgear.org/forums/viewtopic.php?f=10&t=5789 the forum] for more information and registration.

==Useful links==

==And finally...==

[[Category:FlightGear Newsletter|2009 9]]

FlightGear Newsletter September 2009

2009-09-15T04:25:56Z

Statto: /* Scenery Corner */

Welcome to the third edition of the [[FlightGear]] Newsletter. This edition is still being written, so feel free to contribute,

The newsletter is still a bit thin on contributions, so if you'd like to contribute, please feel free to log onto the wiki and start editing the next edition [[FlightGear Newsletter October 2009| here]]. We're still looking for a permanent (or even a temporary) newsletter editor, so if you'd like to get involved, have a look on the [http://www.flightgear.org/forums/ Forums].

==What's new in CVS==
===New shaders===
{| cellpadding="4" cellspacing="0" align="right" style=""
|-
| align="left" style="background:#fafafa; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" | [[Image:SnowAtAltitude1.jpg|200px|Image:SnowAtAltitude1.jpg]]
| align="left" style="background:#fafafa; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" border-top:1px solid #CCCCCC;| [[Image:SnowAtAltitude2.jpg|200px|Image:SnowAtAltitude2.jpg]]
|-
| align="center" colspan="2" style="background:#fafafa; font-size: 85%; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-bottom:1px solid #CCCCCC;"|
Scenery around [[LFLJ]] with the snow effect disabled (left) and enabled (right).
|}

Recently new [[shaders]] have upgraded the visual realism of FlightGear. Thanks to the hard work of Till Busch and Tim Moore, we now see snow at high peaks and reflections in the water.

The new effects can be enabled through the <tt>View > Rendering Options</tt> dialog.

==New wiki articles ==

==In the hangar==

==Scenery Corner==
{| cellpadding="4" cellspacing="0" align="right" style=""
|-
| align="left" style="background:#fafafa; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" | [[Image:Maui03.jpg|200px|Image:SnowAtAltitude1.jpg]]
| align="left" style="background:#fafafa; border-right:1px solid #CCCCCC; border-top:1px solid #CCCCCC;" width="150px" border-top:1px solid #CCCCCC;| [[Image:Maui10.jpg|200px|Image:SnowAtAltitude2.jpg]]
|-
| align="center" colspan="2" style="background:#fafafa; font-size: 85%; border-left:1px solid #CCCCCC; border-right:1px solid #CCCCCC; border-bottom:1px solid #CCCCCC;"|
Screenshots from the beta build of the new Maui scenery. This should be available to the public soon.|}
The official FlightGear scenery land cover database now has new custom Hawai'i data. Generated from NOAA land cover data, FlightGear now has high quality coverage for six of the eight islands of Hawai'i (Kauai, Oahu, Molokai, Lanai, Maui, and Kahoolawe). The south coast of Oahu, including Honolulu, also features incredibly accurate coastline and land cover data created Unfortunately, with the exception of Maui, the data has not yet been turned into scenery, but Maui has produced some stunning visuals so far! Hawai'i soon will be a popular scenery area for fans of both civil and military aircraft.

New landmarks are always being added to the [http://scenemodels.flightgear.org scenery object repository]. New recent landmarks include the Ho Chi Minh mausoleum in Vietnam to Carrow Road in Norfolk England, the stadium for Norwich City Football Club. Lighthouses from around the UK continue to pop up. Modelers continue to focus on airports, and there are new buildings at EDDP Leipzig, Germany; KNUQ Moffatt Field (in the default scenery!); and KJAN Jackson, Mississippi. Next time you're looking for a place to fly, keep these places in mind!

==A living community==
===TransGear Airways===
[[TransGear Airways]] is a new group of people from the FlightGear community, gathering once a month. At coordinated times, each pilot will depart from his/her respective home base on the "spokes" of TransGears airway network, and convene together at its "hub", before exchanging passengers and flying back to their home base. While realism is one of the aims of the gatherings, everyone is welcome, as long as one is trying to follow more or less realistic procedures.

The first upcoming gathering will take place at September 12th at [[KBWI]]. Check [http://www.flightgear.org/forums/viewtopic.php?f=10&t=5789 the forum] for more information and registration.

==Useful links==

==And finally...==

[[Category:FlightGear Newsletter|2009 9]]

File:Maui10.jpg

2009-09-15T04:24:04Z

Statto: Screenshot of new Maui scenery north of the Volcano

Screenshot of new Maui scenery north of the Volcano

File:Maui03.jpg

2009-09-15T04:23:41Z

Statto: Screenshot of new Maui scenery

Screenshot of new Maui scenery