FlightGear wiki - User contributions [en]

Talk:Airport data (apt.dat) update

2013-02-28T11:09:46Z

Papillon81: /* Independent apt.dat source */

==Independent apt.dat source==
I would like to suggest to use an independent, community based source for apt.dat data, such as [http://github.com/mcantsin/x-plane-navdata/wiki this project on github].
[[User:Mcantsin|Mcantsin]] 01:57, 28 February 2013 (UTC)
:: Then maybe you can explain what is not independent and community based on Robin's data? It's GPL and a new release is around the corner. --[[User:Papillon81|Papillon81]] 11:09, 28 February 2013 (UTC)

User talk:Papillon81

2013-02-26T13:13:24Z

Papillon81:

== FGTour AfD addition in 01/2013 ==
Hi, referring to your edit at [http://wiki.flightgear.org/index.php?title=FGtour&oldid=57036]. I got a heads-up sent by Michat regarding your AfD addition. Frankly, I also don't know what exactly all this is about, but looking at the quality of the edits and the content, I'm having a hard time finding your harsh comments ("WTF") warranted. In general, we encourage people not to use abusive language, while this cannot be enforced on the devel list and other decentralized channels like IRC, it can (and usually is) discouraged on the forum and the wiki, where we have moderators and/or admins. In addition, finding such harsh words to describe an obviously time-consuming contribution is extremely discouraging. Please keep in mind that we are all volunteering our time here. As you undoubtedly know, FlightGear doesn't just need a single type of talent (or even personality). So even if you yourself should not appreciate the effort put into pages like the [[FGtour]] pages, that cannot necessarily be said for other '''users'''. Finally, the quality of the [[FGtour]] pages, the layout and the content easily exceeds that of 90% of our wiki articles here, which is part of the wiki process obviously, because everything needs to be considered "in progress" until it matures. So, please: let's give contributors the benefit of the doubt (and especially time) so that they can work, without directly questioning new contributions like you have done - it's not like there's some nonsense C++ code added to the next branch causing segfaults, right ? Thanks - all the best, --[[User:Hooray|Hooray]] 12:57, 26 February 2013 (UTC)

: Well, first of all i'm not alone with my opinion: [http://wiki.flightgear.org/Talk:Portal:FGembassyTour], secondly, this page(s) certainly were a lot of work, but inventing other peoples statements and using pictures of dubious origin is not what we want here. --[[User:Papillon81|Papillon81]] 13:13, 26 February 2013 (UTC)

Release plan

2013-01-23T12:57:50Z

Papillon81: /* 2.10 */ Add a suggestion for source snapshots pre-release

{{GitStatus}}

This page contains details about how to release a new version of [[FlightGear]] into the wild. It is a continous work in progress to be improved with every new release.

[[File:ReleasePlan.jpg|thumb|250px|The original plan]]
This '''release plan''' was originally developed by Mathias Fröhlich, Martin Spott, Thorsten Brehm and Torsten Dreyer during LinuxTag 2011.

If you think you have something to contribute to the release process, feel free to [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} edit this page]. In particular, improvements should be based on [[Release plan#Lessons learned]] from past releases. Please discuss this concept at the mailing-list.

=== General release concept ===
New FlightGear releases are scheduled twice a year. The magic number to remember is 17 (we tried 42, but that didn't turn out so well. 17 is perfect: 1 is not a prime, 7 is a prime and so is 17). On the 17th of January (1) and July (7) a new release branch is created for [[SimGear]], FlightGear and FGDATA.

After branching, there is one month for bug fixing in the release branch, so building and packing of the binaries and FGDATA takes place around February, 18th and August, 18th. Allowing a few days for distribution of the files, new versions should be publically available around the 20th of February and August.

The development stream of SimGear, FlightGear and FGDATA is set into a frozen state one month before the branch-day (17th), to let the dust of development settle and to allow fixing the most annoying bugs in the code. During this period, developers should not add any new features, subsystems, and the like. Immediately after the stream has branched for the release, development in the main stream (next/master) is open for major changes until one month before the next branch-day. This results in a duty cycle of 5 month developing and 1 month thinking.

=== Version numbers ===
FlightGear version numbers exist of three digits, seperated by dots:
* '''Major''' (2.4.1): is only increased after significant changes to the functionality of the software, i.e. 1.X.X => 2.0.0 (due to switch to OSG).
* '''Minor''' (2.4.1): has two applications:
** '''Stable releases''' always have ''even numbers'', i.e. 2.6.0, 2.8.0, 3.0.0.
** The '''development stream''' (''latest Git version'') uses an ''odd number'', increasing the minor number of the latest stable release's version by one. I.e., when the latest release is 2.8.0, the current development stream is 2.9.0.
* '''Revision''' (2.4.1): is increased by bugfix releases, i.e. 2.8.1, 2.8.2, 2.8.3.

=== Detailed time schedule and checklist ===
# '''Dec/Jun 17th:''' Development stream is declared "frozen" or "yellow"
##Send a mail to the flightgear-devel mailing-list to announce the state
##Create a "release preperations" topic at the forum and make it a "Global Announcement"
##Change the content of wiki template at [[Template:GitStatus]] to <code><nowiki>{{GitStatus:frozen}}</nowiki></code>
##Bump up the version-number of simgear/next, flightgear/next and fgdata/master to an even number (2.9.0 -> 3.0.0)
##modify options.cxx to bump the hard-coded base package version number in [http://gitorious.org/fg/flightgear/commit/bffb5589215182cb21ab2b2697ae7bf000db1412/diffs/ddc2a745c67d138b34e3d95948d341341c85965d]
##Compile and test drive FlightGear with the new version-number
##Commit the new version number to next (flightgear+simgear) and master(fgdata)
##Tag (annotated) flightgear, simgear and fgdata with <tt>version/3.0.0</tt>
##:''git tag -a version/3.0.0'' (Enter a wise comment)
##Push the branches next/master '''and''' the tags upstream
##:for flightgear and simgear: ''git push origin next''
##:for fgdata: ''git push origin master''
##:for the tags (all repos): ''git push origin version/3.0.0''
# '''Jan/Jul 17th:''' Create new release branch, assign new version number to dev-stream, re-open streams

##Pull current Git, create the release branches (for sg/fg/fgdata):
##:''git pull
##:''git branch release/3.0.0
##On the next/master branches, bump up the version-number of simgear, flightgear and fgdata to an odd number (3.0.0 -> 3.1.0)
##Compile and test drive FlightGear with the new development version number
##Commit the changes of version-number to next/master
##Tag (annotated) flightgear, simgear and fgdata with "version/2.9.0"
##:''git tag -a version/2.9.0'' (Enter a wise comment)
##Push the branches next/master '''and''' release/3.0.0 '''and''' the tags upstream
##:for flightgear, simgear and fgdata: ''git push origin release/3.0.0''
##:for flightgear and simgear: ''git push origin next''
##:for fgdata: ''git push origin master''
##:for the tags (all repos): ''git push origin version/3.1.0''
##Declare dev-streams "open" or "green"
##: Ask a wiki admin to change the content of wiki template at [[Template:GitStatus]] to <code><nowiki>{{GitStatus:open}}</nowiki></code>
##:Send a mail to the flightgear-devel mailing-list to announce the state.
## Trigger James for the Jenkins-builds and Curt for a snapshot release and ThorstenB for the OpenSuse build
# '''Feb/Aug 1st:''' Start preparing the release notes and a press announcement
# '''Feb/Aug 17th:''' Create binaries/installers, pack fgdata, publish files, announce new version, close the release-branch.
## Generate latest '''getstart.pdf''', push the PDF to fgdata/master - and cherry-pick to the '''release branch'''. Generate latest '''getstart''' HTML, push PDF and HTML to the MapServer site.
##Tag the release/3.00 branches of simgear, flightgear and fgdata and push the tags.
##:for flighgear, simgear and fgdata: ''git tag version/3.0.0-final''
##:for flighgear, simgear and fgdata: ''git push origin version/3.0.0-final''
##Merge the branch release/3.0.0 into '''master''' ('''NOT''' next) for flightgear and simgear and push the branch
##:We don't have a next branch for fgdata, no merging of the release branch here.
##:for flighgear and simgear:
##:''git checkout -b master origin/master'' or ''git checkout master'' if you already have the local branch
##:''git merge version/3.0.0-final
##:''git push origin master''
##Core developers and other contributors should be invited to add their release related experiences (i.e. suggestions for improvements) to the wiki to help update and improve the release plan (i.e. this page) accordingly.

=== To bump up the version number ===
* fgdata
** edit the ''version'' file
* SimGear
** edit the ''version'' file
* FlightGear
** edit the ''version'' file

=== Definition of repository states ===
{| class="wikitable"
!
! State
! Description
|-
! [[File:Traffic light green.png|20px]]
! Open/Green
| Normal development of the code base and fgdata. Unrestricted (well, sort of) access to the streams. This state lasts for five month after the release branches were created.
|-
! [[File:Traffic light yellow.png|20px]]
! Frozen/Yellow
| No new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches.

It's a good idea for aircraft developers to adhere to this rule. However, aircraft in fgdata may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Also, aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in that period.
|-
! [[File:Traffic light red.png|20px]]
! Closed/Red
| Nothing shall be pushed to the development streams (simgear, flightgear and fgdata). This state is for creating the release branches. It lasts for just a few hours on Jan 17th and Jul 17th around 12:00 UTC.
|}

=== Bug fix committing policy ===
Fixes for bugs during the shakedown test of the release branch may be applied to the branches next or release/2.8.0.
A fix goes into release/2.8.0 if the development of next has moved forward and this fix does not apply there. It also goes into the release branch if there will be a better fix for next.
A fix goes into next if it is also solves an issue for the next version. Cherry-pick this commit into the release/2.8.0 branch.

'''DO NOT''' merge next into release/2.8.0 or vice versa. Most likely, there will be commits that are not welcome in or even break the other branch.

=== Bug tracking ===
The [http://flightgear-bugs.googlecode.com bugtracker] will be our primary source for the bug fixing period. Bugs reported on the mailing list or forum will not be tracked! Reporters shall be requested to file a bug report at the bugtracker. Bugs shall be assigned a priority and a keyword to make the assignment to a developer easier. Bug reports that can't be confirmed or need more input from the reporter to get fixed will be assigned a new state "stalled" and only processed after more information has been provided. Bugs assigned a high priority will be downgraded, if no progress has been made over a certain amount of time. This is to prevent the release from being blocked by a bug that no developer is able (or willing) to fix. The only exception is "does not compile for one of the major platforms", which certainly is a release-blocker.

Bugs that were present in the latest stable release, and now considered "fixed", should be assigned a milestone label, corresponding with the upcoming stable release number. By doing so, they'll end up in [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=label%3AMilestone-2.8.0 the list of fixed bugs].

=== Tasks and owners ===

The following table should be updated and augmented after each release, according to the [[Release plan#Lessons learned|Lessons learned]] section below.

{|class="wikitable"
!
! width="500px" | Task
! Owner(s)
! Status for [[Changelog 2.10.0|2.10.0]]
|-
! rowspan="6" |
| Announce the state-change of the dev-streams
| TorstenD
| {{Done}}
|-
| Create/maintain the git branches
| TorstenD
| {{Done}}
|-
| Track the bugs on the tracker, trigger developers, adjust bug-priorities
| ThorstenB, Gijs, James, ...
|-
| Beta testing
| '''EVERYBODY'''
|-
| Update documentation: [[FAQ]], [https://www.gitorious.org/fg/getstart/ The Manual], wiki
| Stuart, Gijs and anyone else
|-
| Pack RC and final version of FGDATA
|
|-
! rowspan="5" | Create the RC and final version
| Source-tarball
| Curt
|-
| Linux
| ThorstenB (for openSUSE)
|-
| Windows
| Curt
|-
| MacOS
| Tat
|-
| Distribute files to download servers
| Curt
|-
! rowspan="2" | Make adjustments on the web-site
| Collect/make screenshots for the gallery
| Curt
|-
| Generate aircraft page
| Curt, Gijs
|-
! rowspan="2" | Announce the new version to the public
| Write a changelog: [[Changelog 3.0.0]]
| All developers
|-
| Contact flightsim websites and send them/link them to the "press announcement". See [[release promotion]] for a list of already-contacted and yet-to-contact websites/magazins.
| '''EVERYBODY'''
|}

=== Open items, questions ===
* Automate the creation of Windows and Mac installers
* Automate the creation of FGDATA distribution
* Possibly try to find a way to automate testing of updated jsbsim code, so that the chance for breakage is reduced by running scripted tests [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39109.html]

=== Lessons learned ===
This is a list of lessons learned from the previous releases, things that turned out well and should be kept for the next release as well as thing that didn't turn out so well and should be changed for future releases. Ideally, the release plan should be updated and augmented so that the lessons learned are incorporated accordingly.

==== 2.10 ====
* {{Thumbs up}} Walking through the list of "lessons learned" as part of the "Upcoming release" announcement was useful [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38749.html]
* {{Thumbs up}} Posting the link to the changelog for the upcoming release helped writing the changelog early, this should also be done for the [[Hardware Recommendations]] and [[Notebooks known to run FlightGear]] pages probably?
* perform a sync with JSBSim sources before the feature freeze.
* {{Thumbs up}} The changelog can be easily written by using "git log", searching the issue tracker and by going through the last 6 newsletters published since the previous release.
* GLSL shaders and effects should be treated like core code, and should be tested on different platforms before being enabled by default (NVIDIA, ATI/AMD, Intel) [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39120.html]
* New/updated Nasal scripts contributed to the base package should be checked to properly support important features like simulator reset, this also applies to Nasal scripts used by aircraft, Nasal scripts that fail these criteria, end up breaking existing features! [https://code.google.com/p/flightgear-bugs/issues/detail?id=956]
* there were a number of navcache/SQLite related issues reported via the issue tracker and the forum/devel list [https://code.google.com/p/flightgear-bugs/issues/detail?id=894]
* a little irritation/frustration was caused due to the conflicting review statements concerning the new radio propagation code [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38905.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38825.html] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33692.html] - some of this boiled down to coding style related issues, highlighting the fact that different core developers have different "coding styles" and requirements when reviewing merge requests, because we still lack an official "FlightGear coding style guide" [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38958.html]
* the [https://gitorious.org/fg/flightgear/blobs/next/scripts/python/nasal_api_doc.py nasal_api_doc.py] script in $FG_SRC/scripts/python should be run as part of the release process, to create an updated doc file for $FG_ROOT/Docs and ship it with each release [http://flightgear.org/forums/viewtopic.php?f=30&t=15133]
* We've already got a fairly extensive lead-in time for the release. More testers on more platforms would seem to be the answer. Perhaps we should advertize for testers of those platforms that aren't adequately covered by developers running git? Making a complete package available, not just the binaries would help, as testers wouldn't need to be git-aware. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38764.html]
* The main area to improve is to distribute release candidates for all platforms earlier - preferably starting immediately after the freeze. That would already give us more time for testing - without extending the actual freeze period.[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38765.html]
* How about having a test run a week or two in advance, just to make sure we can indeed produce release installers for Win+Mac - and then release the first RC on December 17th/18th or 19th [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38765.html]
** When releasing RC's do not limit them to Win/Mac binaries, but also create source snapshots so that distros can already work on the next package versions.
* To get to the 3.0 goal sometime in the near future, it's probably a good idea to create a backlog of open items in the wiki and link the release plan document to that. As usual, we don't have to be perfect for a new major release number. But the new features being the reason for the new major number should work reasonably correct. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38888.html] (also see [[:Category:Developer Plans]])
* A normal Linux user has practically no chance to get last stable on his box running if it isn't in his distro - a normal Windows user gets everything nice and streamlined. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38817.html]
* According to the issue tracker there were 3-5 different contributors who provided C++ patches that didn't end up reviewed/merged, which caused some irritation.
* it may make sense to also allow art work contributors to contribute new splash screen images for use in the upcoming release. The screen shot contest should provide plenty of options [http://www.flightgear.org/forums/viewtopic.php?f=28&t=16795].

==== 2.8 ====
* {{Thumbs down}} Lack of stress-testing: A number of users reported severe memory growth issues (with fgfs consuming as much as 14gb of RAM), many directly related to new features, such as random buildings: [http://flightgear.org/forums/viewtopic.php?f=17&t=16758&p=160765&hilit=vegetation#p160747] [http://flightgear.org/forums/viewtopic.php?f=17&t=17249] [http://flightgear.org/forums/viewtopic.php?f=68&t=17114&start=15#p163829] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38007.html] These could have probably been identified earlier by running FG for extended periods of time, and testing the shipped aircraft with the default KSFO scenery, and new features such as random buildings enabled.
* {{Thumbs down}} Lack of graceful feature scaling: Several users with old graphics cards reported not being able to run FG 2.8 without crashing during startup, because the FG defaults didn't scale for old hardware [http://flightgear.org/forums/viewtopic.php?f=17&t=17308]
* {{Thumbs down}} According to noaa.gov it seems that the NOAA metar source got phased out in 04/2012 and moved to a new URL[http://weather.noaa.gov/weather/coded.html], some users reported issues related to this[http://flightgear.org/forums/viewtopic.php?f=17&t=17457&p=165784&hilit=metar#p165784]. However, the metar URL is currently hard-coded in the fgfs/metar source code - in addition, the default format is no longer a plain text dump [http://www.aviationweather.gov/adds/metars/]. It would make sense to make the URL a string property that can be put into preferences.xml and then use a Nasal listener to parse the resulting XML/HTML and set a plain text property instead, that can be processed by the existing metar code.
* {{Thumbs down}} [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38113.html Broken OSX downloads]
* {{Thumbs down}} [http://flightgear.org/forums/viewtopic.php?f=21&p=165841#p165841 the OSX 10.8 release and code signing caused some irritation]
* {{Thumbs down}} [http://flightgear.org/forums/viewtopic.php?f=47&t=14883&start=330#p166062 After the 2.8 release a number of users on the forums reported seeing GLSL related errors, because some of the 2.8 shaders used GLSL features only supported by more recent GLSL compilers/drivers - it would probably make sense to test all shader settings on all 3 platforms and check if they cause any errors (and "backport" shaders as necessary). Apple/Mac OSX seems to be more problematic]
* {{Thumbs down}} [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38121.html Microsoft Redistributables were apparently not shipped with the Windows installer ?]
* {{Thumbs down}} [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38089.html The changelog should be written as early as possible]
* The code freeze could probably be lifted for patches that are not normally enabled/used by any default code paths (or shipped aircraft) in a FlightGear release. This probably involves Nasal extension functions, fgcommands, telnet commands, but also custom hard coded instruments or instrumentation-related APIs (think Canvas). Basically, whenever there's no chance to break a release by committing a certain patch, because the code path will not be executed by default without explicitly enabling it. For 2.8, this also meant that the Nasal [[Canvas]] API could not be included due to the code freeze, which however wasn't used by any systems or aircraft - so that there would have been zero chance for breakage [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37622.html] [http://flightgear.org/forums/viewtopic.php?f=71&t=17397#p165413].
* The wiki contains a number of resources to help new users with hardware decisions, such as [[Hardware Recommendations]] [[Notebooks known to run FlightGear]] and [[Supported Video Cards]] - these should probably be updated for each release several weeks in advance.

==== 2.6 ====
* {{Thumbs up}} feature freeze in general
*: helped a lot during release management. Kept the commit traffic low and thus helped identifying those commits required to pick into the release.
* {{Thumbs down}} feature freeze for aircraft
*: Technically, a feature freeze for aircraft is not necessary as long as this aircraft is not part of the base distribution and no common parts are affected. If it's guaranteed that the changes remain in FGDATA/Aircraft/MyAircraft and no other files are touched, these updates should be OK up to shortly before the release.
* {{Thumbs down}} switching to a new version of supporting libraries like OSG.
*: The move to OSG 3.x introduced some major issues. If at all possible, switch to a new library early in the development cycle.
* {{Thumbs down}} manual creation of release candidates and the release binaries
*: It's preferable to have equal numbers for release candidates for all O/S and probably a git-tag for each candidate.
* {{Thumbs down}} release date/time frame
*: It took several days to release all the subparts. Might be better to upload all files and pages to hidden folders and publish them all at once (or at least within a couple of hours). That'll have several advantages:
*:* no big difference between releases for the various OS.
*:* the website will switch to the new release state quickly. With 2.6.0, the aircraft page was published before the setup. The release announcement was published even later.

[[Category:Core developer documentation]]
[[Category:FlightGear]]

FlightGear Newsletter January 2013

2013-01-09T12:28:14Z

Papillon81: /* Development news */ Some news from the terragear side

This is a template for future [[FlightGear Newsletter|newsletters]], please feel free to edit/improve!

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

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

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

=== Random Buildings ===


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


=== High Level Architecture ===
=== FlightGear on Android ===

=== Procedural Terrain Texturing ===

For users with powerful graphics cards, a much improved version of [[Procedural Texturing]] of the Flightgear terrain (which is as of now implemented under the [[Atmospheric light scattering]] framework) is currently being developed. This generates highly detailed visuals of the terrain seen from close-up (the smallest structures generated are of 1 cm scale), including a gentle bump-mapping, grain overlay and optional sparse-dot noise generated rocks or grass patches.

[[File:hires_terrain01.jpg|300px|Hires terrain - Lanai shrub cover]]
[[File:hires_terrain02.jpg|300px|Hires terrain - Oahu hill vegetation ]]
[[File:hires_terrain03.jpg|300px|Hires terrain - Lanai green ]]

[[File:hires_terrain04.jpg|300px|Hires terrain - Kauai shrub cover]]
[[File:hires_terrain05.jpg|300px|Hires terrain - Mojave desert ]]
[[File:hires_terrain06.jpg|300px|Hires terrain - Falkland islands in snow ]]

The texturing procedure is easily configurable via materials.xml and combined with regional texturing allows for a much improved experience for low-level flights or helicopter trips away from airfields.

Note that this feature will not be available for the 2.10 release, as it requires still some testing.

=== Terragear ===
The master branch of terragear has recently seen more enhancements and cleanup.
Most of the functionality has been put into a single terragear library for reuse in all tools.
Furthermore, all essential parts of the toolchain now support multithreading. The multiprocess support for genapts has been removed in favour of threading as well.

Work continues on the elevation tools. GDALchop has been re-activated and should become the prior tool to chop up elevation source files into buckets. As it relies on the well-established codebase of GDAL, it takes away the task of opening and reading the different kinds of elevation files from the terragear developers. Supported formats can be seen here: http://www.gdal.org/formats_list.html

=== Usability Improvements ===

=== Mailing list digest ===

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

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===

Please see [[Howto:Start core development]]

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

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

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

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

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

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

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

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

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

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

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

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

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2013 01]]

User:Aepcam/Portal:FGembassy

2013-01-08T15:24:46Z

Papillon81: Those pages are nothing to put into the official wiki area

{{afd}}

{{Main page/Header
|title=FlightGear, your experience is our reward
|subtitle=''Know your Rights!''
|introduction=Please visit [http://flightgear.org/forums our forum] if you cannot find what you're looking for.

|rightbox=

|rightcolumn1= </div>

KNOW YOUR RIGHTS 

[[New to FlightGear]] · [[FlightGear Manual]] 
[[Frequently asked questions]]
|rightcolumn2= </div>
TROUBLESHOOTING 

[[Howto: Understand console output|Common errors]] 
[[Howto: Improve framerates|Improving framerates]]
|rightcolumn3= </div>
[[File:Freeride.jpg]]
[[File:Chimpmunk.png|158px]]

FLYING 

[[Howto: Aerial refueling|Aerial refueling]]

[[Howto: Carrier|Aircraft carrier operations]] 
[[Flying Warbirds|Flying warbirds]]
[[Howto: Fly a helicopter|Flying helicopters]] 
[[Howto: Multiplayer|Multiplayer]]
[[Howto: Be a controller|Be an air traffic controller]]
[[Dual control|Multi-crew]] 
[[Soaring]] · [[Weather]] 
[[Avionics and instruments]] · [[Aircraft lighting]] 
[[Altitude]] · [[Aircraft speed|Speed]]

[[Understanding Propeller Torque and P-Factor|Propeller torque and P-factor]] 
[[Understanding Navigation|Navigation]]
[[Creating a flightplan]] 
[[List of abbreviations]]
[[File:Magagazine.png]]
|rightcolumn4= </div>
[[File:Chimpmunk.png|158px]]
HARDWARE 

[[Joystick|Joystick, yoke and rudder]]
[[Howto: Configure camera view windows|Multiple displays]] 
[[Hardware Recommendations|Recommendations]]
|rightcolumn5= </div>

[[File:Chimpmunk.png|158px]]

SUGGESTED 

[[Suggested Aircraft|Aircraft]] · [[Suggested Airports/Scenery|Airports/Scenery]] 
[[Suggested Flights|Flights]] · [[Challenging Airports]] 
[[Suggested Software|Software]] 
|rightcolumn6= </div>

[[File:Chimpmunk.png|158px]]

ADDITIONAL TOOLS 

[[FGo!]] · [[FGRun]] · [[KFreeFlight]] 
[[FGCOM]] · [[TerraSync]] 
[[Atlas]] · [[Airport Diagram Generator]]
|rightcolumn7= </div>

[[File:Chimpmunk.png|158px]]

PROMOTION 
[[Unique Features]] · [[FlightGear Reviews|Reviews]] 
[[FlightGear Videos|Videos]] · [[Howto:Make nice screenshots|Making nice screenshots]] 
[[Presentation Recipe|Presentation recipe]] · [[FlightGear Expo Checklist|Expo checklist]]
}
{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Development repository status]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}


|sections=

{{Main page/Leftbox|title=Devoted of freesoftware
|contents=

BOMBABLE ADDON INSTALLER

AWESOME FG PERFORMANCE

We recently reached the drafting bombable installer for windows created by felipe uruguayol team. (FlightGear-Team.UY)
}}

{{Main page/Leftbox|title=News
|contents=

Together in freedom is better. 

Sinonimous of Freedom our GPL is our ethical statement.FlightGear
runs with same guaranty that Privative software.
Nothing, or almost Nothing.
However we offer better assistance 24X7X365.

1

Wiki - Forum - IRC - FAQ's - Bug Tracker

REVIEW

Visiting Helijah's Hangar

A review of the aircraft that have marked the history of aviation pioneers 

A brainy innovation takes flight

A team of Northeastern University engineering students has developed a system that allows a pilot to fly a simulated airplane using nothing more than his or her brainwaves — a program that has piqued military and private-sector interest.

“Typically, a pilot has a joystick and a throttle and those allow him or her to do a myriad of things,” said Nedoroscik, the team leader. “We were able to identify the absolute essential controls and write them into the software. We’ve been able to achieve up to eight commands, which allowed us to fly the plane and do a couple of flight maneuvers.”

The group was supervised by Waleed Meleis, an associate professor of electrical and computer engineering, and worked closely with Assistant Professor Deniz Erdogmus, a brain-computer interface expert. During the two semesters they spent working on the project, Erdogmus gave the group access to his equipment, which allows a user to control computers or robots with signals from different parts of the body.

Using an open-source flight simulator called FlightGear, the group was able to design a computer system that could distinguish between eight commands at a rate of two seconds per command, achieving accurate results about 80 percent of the time.

This entry was posted in Campus & Community, Science & Technology and tagged airplane, Boston, capstone, computers, electrical and computer engineering, engineering, experiential learning, flight, grant, research, robots, simulator, students. Bookmark the permalink. 

PHOTO Curt: "Unable to look back" 

New version of FlightGear meteorological model Ver 1.0 by Torsthen
El crecimiento de la masa critica ha impresionado a todos los participantes.
We modify the way the weather affects ouu dinamics

University of Atlanta, Georgia has it's own dinamic model

Now everyone can feel the cloud's drift, and head winds moving humidity to your fuselage.

DIYDRONES

Using Arduino compatibility and GPS integration

Through a proxy server.
Now everyone can feel the cloud's drift, and head winds moving humidity to your fuselage.

FG friendly hardware - Arduino

FG friendly projects - Watch on video - Find more information

REMBRANDT

A huge project that give light to the FG project

A review of the aircraft that have marked the history of aviation pioneers 

[[File:magagazine.png|100px]][[File:magagazine.png|100px]][[File:magagazine.png|100px]][[File:magagazine.png|100px]]
}}
{{Main page/Leftbox|title=External links
|contents=

FligtGear is Freesoftware, know it's advantages 

Users enjoy the best simulation software as investigate and learn useful skills to contribute in a fair and free strong capable 

1
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]

REVIEW

Visiting Helijah's Hangar
A review of the aircraft that have marked the history of aviation pioneers 
}}

{{Main page/Leftbox|title=External links
|contents=
Curt Olson warns of FlightGear spectacular growth for 2013.
The growth of critical mass has impressed all participants.We will win the battle of ideas 

PHOTO Curt: "Unable to look back" 

FligtGear is Freesoftware, know it's advantages 

Users enjoy the best simulation software as investigate and learn useful skills to contribute in a fair and free strong capable 

1
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]

REVIEW

Visisting Helijah's Hangar
A review of the aircraft that have marked the history of aviation pioneers 
}}

{{Main page/Leftbox|title=External links
|contents=
Curt Olson warns of FlightGear spectacular growth for 2013.
The growth of critical mass has impressed all participants.We will win the battle of ideas 

PHOTO Curt: "Unable to look back" 

FligtGear is Freesoftware, know it's advantages 

Users enjoy the best simulation software as investigate and learn useful skills to contribute in a fair and free strong capable 

1
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]

REVIEW

Visisting Helijah's Hangar
A review of the aircraft that have marked the history of aviation pioneers 
}}
{{Main page/Leftbox|title=FG Museum Program
|contents=
* [Curtis Olson R.C. Museum]
* [Veridian Engineering Division, Buffalo, NY]
* [MathWorks]
* [NASA/Ames Human Centered System Lab]
* [Pragolet s.r.o.]
* [ATC Flight Simulator Company]
* [ActiveFly]
* [Robert Heffley Engineering]
* [Aeronautical Radio, Incorporated (ARINC)]
* [RWTH Aachen]
}}
{{Main page/Leftbox|title=FGUP FlightGear University Program
|contents=
{{{!}}
{{!}} valign="top" {{!}}
* [[Howto: Install aircraft|University of Naples]]
* [[Howto: Install scenery|University of Illinois]]
* [[Howto: Install scenery|Simon Fraser University]]
* [[Howto: Install scenery|Iowa State University]]
* [[Howto: Install scenery|University of Minnesota]]
* [[Howto: Install scenery|University of Wales]]
* [[Howto: Install scenery|Delft University of Technology]]
* [[Howto: Install scenery|University of Tennessee]]
* [[Howto: Install scenery|Pennsylvania State University]]
* [[Howto: Install scenery|Northeastern University]]
* [[Howto: Install scenery|University of Argentina]]
* [[Howto: Install scenery|Arizona State University]]
* [[Howto: Install scenery|Universiti Teknologi Malaysia]]
* [[Howto: Install scenery|French Aerospace Lab (ONERA)]]
* [[Howto: Install scenery|University of Toulouse]]
* [[Howto: Install scenery|University of New Hampshire]]
* [[Howto: Install scenery|University of Wales]]
* [[Howto: Install scenery|University of Wales]]
{{!}} valign="top" {{!}}
* [[FlightGear hangars]]
{{!}}}
}}
{{Main page/Leftbox|title=FG Friendly Companies
|contents=
* [Aeronautical Development Agency, Bangalore India]
* [Veridian Engineering Division, Buffalo, NY]
* [MathWorks]
* [NASA/Ames Human Centered System Lab]
* [Pragolet s.r.o.]
* [ATC Flight Simulator Company]
* [ActiveFly]
* [Robert Heffley Engineering]
* [Aeronautical Radio, Incorporated (ARINC)]
* [RWTH Aachen]
}}

{{Main page/Leftbox|title=External links
|contents=

FligtGear is Freesoftware, know it's advantages 

Users enjoy the best simulation software as investigate and learn useful skills to contribute in a fair and free strong capable 

1
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]

REVIEW

Visisting Helijah's Hangar
A review of the aircraft that have marked the history of aviation pioneers 

}}

}}

{{Main page/Leftbox|title=Freedom our strenght
|contents=
* To Use-To Copy-To Modify-To Share-To Flight-To Teach-To Learn-To build-To program!
* With unmatched multiplatform software capable to run on more than 6: O.S GNU/Linux -Mac-Win
* [http://flightgear.org/forums our forum] if you cannot find what you're looking for.
* [Curtis Olson R.C. Museum]
* [Veridian Engineering Division, Buffalo, NY]

}}

{{Main page/Leftbox|title=FG DIY
|contents=
* [https://sites.google.com/site/mf2012theviper/ Team Viper]
* [John Wojnaroski's 747 cockpit]
* [Gery's MD80 cockpit]
}}

{{Main page/Leftbox|title=FG Friendly Hardware
|contents=
* [http://freechecklists.net/ Arduino]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]
}}

{{Main page/Leftbox|title=FG Friendly Software
|contents=
* [http://freechecklists.net/ EditPad++] Edit your code easily.
* [http://www.faa.gov/library/manuals/ MediaGoblin federate your own media server or use a free service ready to use]. Share, video, audio and 3D
* [http://www.gcmap.com/ OpenAl our great sound engine]
* [http://www.blender.org/ Blender] 3-d Modeling.
* [http://www.smartcockpit.com The Gimp] Editing liveries-textures.
* [http://www.worldaerodata.com/ Inscape] Editing liveries-textures.
}}

{{Main page/Leftbox|title=External links1
|contents=
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]
}}

{{Main page/Leftbox|title=External links2
|contents=
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]
}}

{{Main page/Leftbox|title=External links3
|contents=
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]
}}

{{Main page/Leftbox|title=External links4
|contents=
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]
}}

[[Category:Portals]]

[[fr:Portal:FGEmbassy]]
[[es:Portal:FGEmbassy]]

User:Aepcam/FGembassyTour

2013-01-08T15:23:43Z

Papillon81: Please do such tests in your user-page, not in the official wiki area...

{{afd}}

---------------------------------------------------------------------------------------------------
UNIVERSITY
+ MUSEUM
+ COCKPIT
+ SOFTWARE
+ HARDWARE
+ COCKPITS
+ DIYDRONES
+ FAA
+ COMPANIES
+ YOUR FG PROJECT
---------------------------------------------------------------------------------------------------

15

YEARS
with you 

FlightGear

FlightGear is a project where [http://wiki.flightgear.org/GPLFreedom Matters]

[[File:Screenfg.jpg|300x250px|thumb]]

Fast, free and incredibly realistic, the FlightGear Free. 

 Flight Simulator
powers millions of desktop PCs,laptops 

and servers around the world. FlightGear will work with 

your existing O.S, joysticks, pedals, several GPS, cameras 

and Android smartphones - and it doesn't needs 

 downloading thousands of apps.. 

[http://wiki.flightgear.org/FGtour Take the tour>]

or follow our

No panic Tour i.e:if you come from privative Sims >

Used by...

{|
|-
| Professional || Academics || People like you
|-
| Used by professionals, startups, enterpreneurs || Used by professionals, startups, enterpreneurs || Used by professionals, startups, enterpreneurs
|-
| who develop real friendly products, improving || who develop real friendly products, improving || who develop real friendly products, improving
|-
| their real aviation world... || GNU/Linuxtheir real aviation world... || GNU/Linux - Win32/64 - Mac...
|-
| see success cases > || learning more > || the way we fly > || Enter into Fg's world >

|}

Prefered by Freedom Experts

[[File:Diapo.jpg|200x200px]] [[File:Diaposcenery.jpg|200x200px]]
[[File:Diapomp.jpg|200x200px]] [[File:Diapoatc.jpg|200x200px]]

+450 FREE Aircraft | Entire World scenery | Free MPservers | VatSim capable 

{|
|-
| Features
|}

{|
|-
| Source code || MP servers || MP Map || Real weather || Cloud drifting ||
|-
| Multi Joystick || MP Map || MP chat || NASAL Script || Cloud drifting 
|-
| Multi Screen || Multiplatform || MP Voice || Radio range || Dual Control 
|-
| 3D Anaglyph || Aerotow || Carriers || Thermals || Dual Control 
|-
| Awesome connectivity || GPS || Arduino || Android || Avionics 
|-
| More amazing features... >
|}

[[File:Downloadbutton.jpg|thumb|Gratis]]
Get FlighGear

Download FlightGear ultimate and

unleash the freedom pilot you have inside

FlighGear is unlimited, has no DRM and is free

Be a part of it... >

NOTE:

There is always a good reason to use FG. Please consider sharing FlighGear with your best friends.

 If you have any problem installing FlightGear - Watch on video - Find help and more information 

{|
|-
|GNU/Linux ||- Mac ||- Win32/64 || - IRIX || - Solaris || - FG SHOP 
|}

---------------------------------------------------------------------------------------------------
UNIVERSITY
+ MUSEUM
+ COCKPIT
+ SOFTWARE
+ HARDWARE
+ COCKPITS
+ DIYDRONES
+ FAA
+ COMPANIES
+ YOUR FG PROJECT
---------------------------------------------------------------------------------------------------
[[Category:Portals]]

[[fr:Portal:FGEmbassy]]
[[es:Portal:FGEmbassy]]

Building Flightgear - Gentoo

2012-11-29T17:47:10Z

Papillon81: /* Build and install */ terragear name

= HowTo build on Gentoo =

The stable releases can be obtained directly from the official Gentoo portage tree.

== Installing GIT versions ==
There is a gaming overlay available which contains ebuilds for FG from GIT, including Terragear-cs and other things:

http://git.overlays.gentoo.org/gitweb/?p=proj/gamerlay.git;a=summary

Instructions on how to add an overlay to Gentoo can be found [http://www.gentoo.org/proj/en/overlays/userguide.xml here]

== Build and install ==

The overlay contains live ebuilds (meaning ebuilds that install programs from an GIT repository) for

* Flightgear
* [[FlightGear Launch Control|fgrun]]
* [[TerraGear|Terragear]]
* [[Taxidraw]]

including all dependencies.

To install a program, all that's needed is i.e.:

emerge -av flightgear

Another benefit is the possibility to do automatic updates of all installed "live" ebuilds:

emerge -a1v @live-rebuild

Alternately you can use '''smart-live-rebuild''', a tool that rebuilds live packages only if there have been updates to the repository.

First you need to install '''smart-live-rebuild''':

emerge smart-live-rebuild

Then you can tell '''smart-live-rebuild''' to check the packages you want i.e :

smart-live-rebuild -f simgear flightgear

TerraGear

2012-11-29T11:35:25Z

Papillon81: /* Platform specific */

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** [http://www.cgal.org/ CGAL] - For high accuracy geometric calculations
** [http://www.gdal.org/ libgdal]

=== Building ===
cmake . [options]
make install
<tt>cmake</tt> options:
-DCMAKE_PREFIX_PATH="/path/to/lib/install/prefix"

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear in Ubuntu 910 (32- or 64-bit)]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:TerraGear| ]]

[[es:TerraGear]]
[[fr:TerraGear]]

TerraGear

2012-11-29T10:06:08Z

Papillon81: /* Dependencies */ Poco is gone now :)

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** [http://www.cgal.org/ CGAL] - For high accuracy geometric calculations
** [http://www.gdal.org/ libgdal]

=== Building ===
cmake . [options]
make install
<tt>cmake</tt> options:
-DCMAKE_PREFIX_PATH="/path/to/lib/install/prefix"

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu 64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:TerraGear| ]]

[[es:TerraGear]]
[[fr:TerraGear]]

TerraGear

2012-11-29T10:04:46Z

Papillon81: /* Pre-compiled builds */ remove old builds. not a good idea to still use them

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** [http://www.cgal.org/ CGAL] - For high accuracy geometric calculations
** [http://pocoproject.org/ POCO] - For multicore support
** [http://www.gdal.org/ libgdal]

=== Building ===
cmake . [options]
make install
<tt>cmake</tt> options:
-DCMAKE_PREFIX_PATH="/path/to/lib/install/prefix"

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu 64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:TerraGear| ]]

[[es:TerraGear]]
[[fr:TerraGear]]

TerraGear

2012-11-05T22:49:01Z

Papillon81: /* Building */ We are using CMAKE as a build system and the terragear docs are outdated as hell

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** [http://www.cgal.org/ CGAL] - For high accuracy geometric calculations
** [http://pocoproject.org/ POCO] - For multicore support
** [http://www.gdal.org/ libgdal]

=== Building ===
cmake . [options]
make install
<tt>cmake</tt> options:
-DCMAKE_PREFIX_PATH="/path/to/lib/install/prefix"

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu 64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]
[[fr:TerraGear]]

TerraGear

2012-11-05T22:45:55Z

Papillon81: /* Compilation */ Remove newmat and GPC deps. They are gone. Also clean indirect deps brought in by other packages. Not the place to list them here

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/download/scenery/ official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resolution vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs! (simgear-dev package)
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** [http://www.cgal.org/ CGAL] - For high accuracy geometric calculations
** [http://pocoproject.org/ POCO] - For multicore support
** [http://www.gdal.org/ libgdal]

=== Building ===
Please, have a look at [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] and/or [http://mapserver.flightgear.org/git/?p=terragear;a=blob;f=README.cygwin;h=d0436ec0371dd9fa255a8a560a388818432600d6;hb=HEAD README.cygwin] of the TerraGear sources.
./autogen.sh
./configure [options]
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install
<tt>./configure</tt> options:
--prefix=/path/to/install-dir
I am missing reliable data here. Please, revise/complete the list if you have more info!
--with-gdal=/path/to/gdal-config
--with-gpc=/path/to/libgenpolyclip.a
--with-newmat=/path/to/libnewmat.a
--with-plib=/path/to/libplib*.a
--with-simgear=/path/to/libsg*.a
--with-osg=/path/to/OSGinstallation

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu 64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]
[[fr:TerraGear]]

WorldEditor

2012-10-29T09:27:02Z

Papillon81: /* External links */ Correct linking

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

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

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

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

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)

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

WorldEditor

2012-10-29T09:25:34Z

Papillon81: /* External links */ Add WED compile link

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

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

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

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

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development] (How to compile WED)

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

List of file formats

2012-08-11T13:16:00Z

Papillon81: remove runway signs

== *.ac ==
This is the native format for 3D graphics written by the [http://www.ac3d.org/ AC3D] application (payware with free trial version). These files contains meshes, UV-mappings, texture paths and material definitions. The format is FlightGear's preferred (i.e. best supported) format. It's ASCII text and easy to edit by hand or via scripts. Many applications are able to import and/or export this format:

=== [http://www.blender3d.org/ Blender] ===
See File->Import/Export->AC3d (*.ac). [[Blender]] is a free and very powerful (some say: too powerful) 3D editor.

=== [http://www.openscenegraph.org/ Open Scenegraph Library] ===
The <tt>osgviewer</tt> demo is very useful for quickly looking at models.

=== [http://prettypoly.sourceforge.net/ ppe] ===
This is an unmaintained object editor that uses the same graphics library as FlightGear (plib). This has the advantage that objects look very much like in FlightGear (minus shader effects and shadows). Compiling ppe may be a challenge, though, and it's only useful for viewing, but hardly for editing objects.

=== threedconvert ===
This is a converter for all plib supported 3D formats and comes with FlightGear (see utils/Modeller/3dconvert.cxx). It can read and write <tt>*.ac</tt> files, but a written file may lack UV mapping or have other defects.

== *.rgb ==
These files are texture files in [http://en.wikipedia.org/wiki/Silicon_Graphics SGI] Image Format. This format supports multiple layers, transparency, compression, indexed colors, 8 bits and 16 bits per plane. Files of this format use different extensions, often to indicate the image properties, but in fact it's always the same format. The "official" extensions is <tt>*.sgi</tt>. Images with one layer are usually black/white (<tt>*.bw</tt>) or a mere alpha layer (<tt>*.a</tt>), with two layers black/white with alpha, with three layers red/green/blue (<tt>*.rgb</tt>), and with four layers red/green/blue/alpha (<tt>*.rgba</tt>). This, however, is only a convention and not mandated by the SGI image specification. SGI images can be uncompressed or [http://en.wikipedia.org/wiki/Run-length_encoding RLE-compressed], which is a lossless compression method.

FlightGear uses [http://plib.sourceforge.net/ plib] to read SGI images. They must not use 16 bits per plane and must have side lengths of 2nx2m (powers of 2), the size must be at least 4 pixels when using compressed textures (automatic feature in the osg branch). For example: 64x64, 256x256 or 128x2048 (but textures have '''square''' size inside the graphic card so a 16x1024 texture is really a 1024x1024 texture). Note that other sizes will '''not''' work, and FlightGear will use a red/white chequered texture instead! FlightGear textures ''shall'' be RLE-compressed, and as 'aggressively' as possible.

All better graphics applications should be able to read and write the format, but often they load SGI images without problems, but only write them properly when the <tt>*.sgi</tt> extension is used. Here are some free applications that create SGI images, along with some usage notes:

=== [http://www.gimp.org/ GIMP] ===
Either save the image with extension <tt>*.sgi</tt> and rename it afterwards, or choose in the file dialog "Select Filetype" -> "Silicon Graphics IRIS image". Save with "Aggressive RLE". (The remark about SGI not supporting that is wrong. This is compliant with the file specification from SGI itself.)

=== krita/kolourpaint ([http://www.kde.org/ KDE]) ===
KDE supports reading and writing of SGI images on the base library level, so ''all'' applications that can read/write images in general can also read/write SGI images. They are automatically saved in highest possible compression (more aggressive than GIMP :-)

=== convert ([http://www.imagemagick.org/ ImageMagick]/[http://www.graphicsmagick.org/ GraphicsMagick]) ===
Like with [[GIMP]], it's necessary to either call the target file <tt>*.sgi</tt> or to specify the file type explicitly via <tt>sgi:</tt> prefix:

$ convert foo.png foo.sgi # RIGHT
$ convert foo.png sgi:foo.rgb # RIGHT
$ convert foo.png foo.rgb # WRONG! This doesn't create an SGI image!

This creates SGI images with RLE compression by default.

Here is a bash script that you can run in the ./FlightGear/Aircraft directory to generate SGI image files for all of the PNG format files you have:

#!/bin/sh
for PNG in $(find -name '*.png')
do
SUBDIR=$(dirname $PNG)
FILEBASE=$(echo $PNG |awk -F / '{s=$(NF); n=split(s, sa, "."); delete sa[n]; for(sk in sa) {printf("%s.",sa[sk])}}')
RGB="$SUBDIR/${FILEBASE}rgb"
if [ ! -f $RGB ]
then
convert $PNG sgi:$RGB
fi
done

== *.stg ==
<div id="STG"></div>
This entry is copied from $FG_ROOT/Docs/README.scenery, which is part of FlightGear >0.9.10.

stg files ("static terragear") define the static elements of a scenery "tile", including the terrain elevation data, airport geometry, and all static objects placed on this tile. Four of the available key words are followed by a string and four numbers. The meaning of these numbers is always the same and described under OBJECT_SHARED.

=== OBJECT_BASE ===
specifies the terrain elevation data file. These files are generated by the [http://www.terragear.org/ TerraGear] using the [[BTG File Format|BTG file format]], and have file extension ".btg" ("binary terragear"; there used to be an "*.atg" file, too, where
the 'a' stood for ASCII).

Example:

OBJECT_BASE 942050.btg

The entry may be anywhere in the 942050.stg file, on a separate line.

=== OBJECT ===
specifies an airport geometry 'drop-in' file. The scenery elevation file has cut out holes for airports, that are filled with such objects. They are usually called after the airport ICAO id:

Example:

OBJECT KSFO.btg

These files are, again, created by TerraGear tools and are usually gzipped, so you'll find that file stored as KSFO.btg.gz.

=== OBJECT_SHARED ===
add static object to the tile.

Example:

OBJECT_SHARED Models/Airport/tower.xml -122.501090 37.514830 15.5 0.00

Syntax:

OBJECT_SHARED <object-path> <longitude> <latitude> <elevation-m> <heading-deg> <pitch-deg> <roll-deg>

The <object-path> is relative to the data directory (FG_ROOT). <elevation-m> is in meter and relative to mean sea-level (in the fgfs world). <heading-deg> is in degree, counter-clockwise with North being 0.0. <pitch-deg> and <roll-deg> are in degree and optional. Note that this differs from about every other place in FlightGear, most notably the /orientation/heading-deg entry in the property system, which is clockwise. OBJECT_SHARED models are cached and reused. They are only once in memory and never freed. (See also the next section.)

=== OBJECT_STATIC ===
add static objects to the tile, just like OBJECT_SHARED. There are three differences to OBJECT_SHARED (apart from the name):

* the path is relative to the tile directory where the *.stg file with this entry is located. For example, relative to 130n30/w123n37/. This usually means that all 3D object files, textures, and XML animation files are in this tile directory, too.

* these objects are *not* cached and kept loaded, but rather freed with the tile (that is, when you leave that area).

* the animation XML files may contain Nasal blocks <nasal><load> and <nasal><unload> which are executed on loading/unloading.

Example:

OBJECT_STATIC ggb-fb.xml -122.4760494 37.81876042 0 105

=== OBJECT_SIGN ===
{{main article|Signs}}
defines taxiway or runway sign. The syntax is like that of OBJECT_SHARED entries, except that the path is replaced with a sign contents specification. This specification will probably be changed. Look at $FG_ROOT/Docs/README.scenery if you need to use this entry.

== apt.dat ==
See [http://data.x-plane.com/file_specs/Apt810.htm X-Plane data file definitions - Airport data (apt.dat) 810 version]

[[Category:List]]
[[Category:Software]]

Suggested airports

2012-08-04T07:18:41Z

Papillon81: EDDF runway numbers

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 International Airport|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"| 4/6 || 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
|-
| EDDK || [[EDDK|Köln/Bonn]] || Germany || Europe ||align="center"| **** ||align="center"| L ||align="center"| 124.97 (5) ||align="center"| -- ||align="center"| 3/3 || Fully modeled airport and surroundings
|-
| 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, terminal B and large DHL-area modeled, inclusive [[Signs]]
|-
| EDDS || Stuttgart || Germany || Europe ||align="center"| *** ||align="center"| L ||align="center"| 118.800 (8) ||align="center"| -- ||align="center"| 1/2 || Tower, terminal and [[Signs]] are fully modeled
|-
| 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 Airport|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 Airport|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 Airport Schiphol|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; most dense AI traffic.
|-
| EHEH || Eindhoven || Netherlands || Europe ||align="center"| ** ||align="center"| M ||align="center"| 131.000 (6) ||align="center"| -- ||align="center"| 1/2 ||
|-
| EHLE || [[Lelystad Airport|Lelystad]] || Netherlands || Europe ||align="center"| *** ||align="center"| S ||align="center"| -- ||align="center"| 1 ||align="center"| 2/1 || Basic scenery models, home of [[FSweekend]].
|-
| EHVK || [[Volkel Air Base|Volkel]] || Netherlands || Europe ||align="center"| ** ||align="center"| L ||align="center"| 123.170 (1) ||align="center"| many ||align="center"| 2/2 ||
|-
| EIDW || [[Dublin Airport|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 International Airport|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 International Airport|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 International Airport|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 Base|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 ||[[O'Hare International Airport|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 International Airport|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 International Airport|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 International Airport|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 ||
|-
| LIMW || Aosta || Italy || Europa ||align="center"| * ||align="center"| M ||align="center"| 119.950 (1) ||align="center"| -- ||align="center"| 1/0 ||in a valley in high mountain area
|-
| LQSA || Sarajewo || Bosnia || Europe ||align="center"| * ||align="center"| S ||align="center"| 118.250 (3) ||align="center"| -- ||align="center"| 1/1 ||very nice mountain region: LQSA, LYTV, LYPG
|-
| LOWI || [[Innsbruck Airport|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 ||
|-
| LSZS|| Samedan || Swiss || Europe ||align="center"| *** ||align="center"| M ||align="center"| 135,320 (3) ||align="center"| -- ||align="center"| 1/0 || Very nice high mountain region, AP at 5600 ft
|-
| 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 Haneda International Airport|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 International Airport|Princess Juliana]] || ST Maarten || America ||align="center"| **** ||align="center"| M ||align="center"| 118.700 (2) ||align="center"| -- ||align="center"| 1/0 ||very 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
|-
| YSSY || Brisbane || Australia NSW || Australia ||align="center"| *** ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||
|-
| 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 International Airport|Sydney]] || Australia NSW || Australia ||align="center"| * ||align="center"| L ||align="center"| 120.500 (11) ||align="center"| many ||align="center"| 3/6 ||
|-
|}

[[Category:Suggested]]
[[Category:Airports]]

Marble

2012-08-03T11:37:32Z

Papillon81: one more screenshot

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

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

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

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

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

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

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

Marble

2012-08-03T11:35:21Z

Papillon81: Add a screenshot

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

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

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

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

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

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

File:Marble and FG session.png

2012-08-03T11:33:38Z

Papillon81:

=={{int:filedesc}}==
{{Information
|description={{en|1=Marble showing the track of an FG flight}}
|date=2012-08-03
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

File:Marble showing FG track.png

2012-08-03T11:33:36Z

Papillon81:

=={{int:filedesc}}==
{{Information
|description={{en|1=Overview over the track from FG}}
|date=2012-08-03
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

Marble

2012-08-03T10:57:51Z

Papillon81: Initial article with basic info

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

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

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

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

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

Building FlightGear - Debian

2012-08-02T18:47:44Z

Papillon81: Article is outdated. TG doesn't use autotools anymore

{{out of date}}

HowTo build FlightGear [[Changelog_2.6.0|2.6.0]] or bleeding edge development version, hereinafter simply called ''[[GIT]]'', on GNU/Linux [http://www.debian.org/ Debian] '''Stable''' 6.x (Squeeze) and '''Testing''' (Wheezy).

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

== Requirements and Preparations ==
You need more than just an [[OpenGL]] capable graphics card including a proper installed driver supporting direct rendering. 
Also a bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install automake bzip2 cmake fluid g++ gcc git make \
subversion tar"
: cmake: At least version 2.6.0-5 required!
: fluid: needed for [[FlightGear_Admin_Wizard|fgadmin]] only.

; Libs
su -c "apt-get install libalut-dev libboost1.42-dev libc6-dev \
libcurl4-openssl-dev libfltk1.1-dev libgl1-mesa-dev freeglut3-dev \
libgtkglext1-dev libopenal-dev libpng12-dev librsvg2-dev libsvn-dev \
libtiff4-dev libxml2-dev"
: libfltk1.1-dev: needed for fgadmin only.
: Add libudev-dev if you need FG's feature <code>-DEVENT_INPUT=ON</code>.
: [[File:Zeichen_144_icon.png|21px]]During installation packages simgear-dev and openscenegraph-dev ''must not'' be installed. They can safely be re-installed after compilation.
: If you prefer you might replace libcurl4-openssl-dev by libcurl4-gnutls-dev.


== Build and install ==
Because we are going to install versions different to the ones in the repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-2.6.0</code> or <code>$HOME/FG-2.6.0</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make install</code> commands. We'll use <code>$prefix</code> as a placeholder for this directory. 
Another placeholder will be <code>$srcdir</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the following instructions, you have to replace these with the local paths or even <code>export</code> them during the process:
export prefix=$HOME/FG-2.6.0 && mkdir $prefix
export srcdir=$HOME/src && mkdir $srcdir

Have in mind that the data is a relatively large download (GIT about 4.4 GB and 2.6.0 540 MB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources.

For some basic info on git commands for FlightGear users we have a [[Git#For dummies|git for dummies]] section.

=== libopenal ===

Lenny only! The libopenal-dev package in Lenny is too old for [[fgcom]]. For FlightGear it does work but not all features (like doppler) are available, so installing an up to date version is recommended anyway.
cd $srcdir
wget http://kcat.strangesoft.net/openal-releases/openal-soft-1.11.753.tar.bz2
tar xjf openal-soft-1.11.753.tar.bz2
cd openal-soft-1.11.753/build
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" ..
make install

=== [[plib]] ===
2.6.0 and GIT:
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended], yet package plib1.8.5-dev for Squeeze does work as well.
cd $srcdir
svn co https://plib.svn.sourceforge.net/svnroot/plib/trunk plib
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$prefix
make install

=== [[OpenSceneGraph]] ===
GIT users, especially developers, may want to use the latest release or even bleeding edge code here instead. 
2.6.0 and GIT:
cd $srcdir
svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.0.1 OpenSceneGraph
mkdir osg-build && cd osg-build
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
-D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph
make install

=== [[SimGear]] ===
2.6.0 and GIT:
cd $srcdir
git clone git://mapserver.flightgear.org/simgear

2.6.0 only:
cd simgear
git checkout -b 2.6.0 origin/release/2.6.0

2.6.0 and GIT:
mkdir $srcdir/sg-build && cd $srcdir/sg-build
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/simgear
make install

=== FlightGear source ===
2.6.0 and GIT:
cd $srcdir
git clone git://mapserver.flightgear.org/flightgear

2.6.0 only:
cd flightgear
git checkout -b 2.6.0 origin/release/2.6.0

2.6.0 and GIT:
mkdir $srcdir/fg-build && cd $srcdir/fg-build
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/flightgear
make install

=== FlightGear data ===
2.6.0 only: Please have a look at the [http://flightgear.org/mirrors.html mirror list] for a server close to your location.
cd $prefix
wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.6.0.tar.bz2
tar xjf FlightGear-data-2.6.0.tar.bz2

GIT only:
For slow/unstable internet connections it is recommended to download the [[Git#fgdata.bundle|fgdata.bundle]] instead of cloning the data. 
cd $prefix
git clone git://mapserver.flightgear.org/fgdata data

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH
$prefix/bin/fgfs --fg-root=$prefix/data
Have in mind that <code>fgfs</code> need to find our self compiled libraries and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting.

To avoid the need to give the path to the <code>fgfs</code> command in the second line, you might consider to create a symlink to a place that is listed in $PATH:
ln -s $prefix/bin/fgfs $HOME/bin/fgfs

For the future, if you want to start FlightGear from command line have a look at [[fgfsrc]], if you prefer a graphical user interface continue with [[#fgrun|compiling fgrun]] or check [[FGo!]].

== Optional Software ==
[[File:Zeichen_101_icon.png|21px]] Many of the below instructions are most likely not up to date. Please feel free to revise them.

Feel free to add the commands to install other FlightGear related projects.

=== [[Atlas]] ===
cd $srcdir
cvs -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas login
#CVS passwd: [Enter]
cvs -z3 -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas co Atlas
cd Atlas
./autogen.sh
./configure --prefix=$prefix
make install

=== fgcom ===
For [[fgcom]] unfortunately there is one more dependency which cannot be solved with packages on Lenny, see [[#libopenal|libopenal]].
cd $srcdir
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom
cd fgcom/src
make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \
PLIB_PREFIX=$prefix [OPENAL_PREFIX=$prefix] install
Create an .alsoftrc file as shown in [[FGCOM_Testing#Special_for_Linux_.28.alsoftrc.29|FGCOM Testing]].

=== fgrun ===
To build [[fgrun]] one more package is required:
* libfltk1.1-dev
cd $srcdir
svn co http://fgrun.svn.sourceforge.net/svnroot/fgrun/trunk fgrun
cd fgrun/fgrun/
./autogen.sh
./configure --prefix=$prefix
make install

=== TaxiDraw ===
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
* either libcurl4-gnutls-dev or libcurl4-openssl-dev for curl.h
* wx2.8-headers (at least, maybe even more than just that one. Please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $srcdir
git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$prefix
make install

=== TerraGear ===

==== Automatic Installation ====

If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script : http://clemaez.fr/flightgear/terragear_download_and_compile.sh
This script is similar to Brisa script (only usable for Debian/Ubuntu/Mint...). Thi script install terragear-cs, genapt850 en terragear-gui.

''How to use it ?''
sh terragear_download_and_compile.sh -j 2 ALL

-j 2 option is for Dual Core, you can tune it as you want. (personnaly I have Quad Core and I use -j 12 but I need to accept to don't use my aircraft during compilation ;) )

''Need some helps ?''
Looks at forum topics : http://www.flightgear.org/forums/viewtopic.php?f=20&t=14849

==== Basic Installation ====

To resolve some of the dependencies of [[TerraGear]] the GIT sections of steps [[#plib|plib]], [[#OpenSceneGraph|OpenSceneGraph]] and [[#SimGear|SimGear]] have to be done first. Additionally some packages and their dependencies have to be installed:
* libgdal1-dev, gdal-bin
* libproj-dev, libogdi3.2-dev (probably even more, please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!)
Wheezy: As of June 2nd there is a bug ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617240 #617240]) in package libmysqlclient16 which causes compilation to fail. If it is not fixed by the time you're building TerraGear, upgrade to the version from Sid.

cd $srcdir
git clone git://mapserver.flightgear.org/terragear-cs

Two of the dependencies have to be installed manually (See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] and [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for details.):

# gpc install
mkdir $srcdir/gpc232 && cd $srcdir/gpc232
wget ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc232-release.zip
unzip gpc232-release.zip
sed s/DBL_EPSILON/0.000001/ -i gpc.h
grep -A 18 '# Unix/Linux makefile' $srcdir/terragear-cs/README.gpc > Makefile
sed "s|/usr/local/lib|$prefix/lib|" -i Makefile
sed "s|/usr/local/include|$prefix/include|" -i Makefile
make install

# newmat install
mkdir $srcdir/newmat11 && cd $srcdir/newmat11
wget http://www.robertnz.net/ftp/newmat11.tar.gz
tar xzfv newmat11.tar.gz
make -f nm_gnu.mak
cp libnewmat.a $prefix/lib
mkdir $prefix/include/newmat
cp *.h $prefix/include/newmat

Finally TerraGear itself (See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] for details.):
cd $srcdir/terragear-cs
./autogen.sh
./configure --prefix=$prefix
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install

{{Building}}

[[de:FlightGear bauen - Debian]]

Airwave Xtreme 150

2012-08-02T07:49:24Z

Papillon81:

{{infobox Aircraft
|ready = thermal
|image = Airwave Xtreme 150 Innsbruck.png
|name = Airwave Xtreme 150
|type = Hang glider
|fdm = JSBSim
|status =
|fgname = airwaveXtreme150
|authors = Michael Selig, Captain Slug, D-NXKT
}}

== Recommended flying sites ==
A very beautiful site is the real life hang gliding launch "Seegrube" which is located near LOWI (--lon=11.377417 --lat=47.30525 --heading=180 --on-ground). Choose 15kt wind from 180deg for all altitudes and soar up to the summits.

A more challenging flight is "Fort Funston" near KSFO. It's a famous hang gliding site located at the coast with an altitude difference of only (250ft). Unfortunately directly at "Fort Funston" the FlightGear terrain is too smeared to produce sufficient ridge lift but a little bit further south (--lon=-122.4942234 --lat=37.6980674 --heading=270 --on-ground) ridge lift works perfectly. Choose wind with 20kt from 270deg. Be careful with the angle of attack on ground. Turn left after launch and fly very close to the cliff. Play with the performance settings to explore their influence on sink rate and wind-penetration.

== External links ==
A [http://www.flightgear.org/forums/viewtopic.php?f=19&t=16744 nice flight] with the Airwave Xtreme

[[Category:Delta-wing aircraft]]
[[Category:Hang gliders]]

TerraGear

2012-08-01T10:32:13Z

Papillon81: /* Dependencies */ Add more info

<div style="padding-left:20px;">''Not to be confused with [[TerraSync]], a tool to download scenery on-the-fly.''</div>

[[File:TerraGear The Hague wireframe.png|thumb|270px|A wireframe view of detailed [[CORINE]] and [[OSM]] scenery, generated by TerraGear.]]
'''TerraGear''' is a collection of open-source tools and rendering libraries which can transform publically available GIS data in 3D representations (i.e. 3D models or 3D maps) of the earth for use in real time rendering projects. TerraGear can import 3D data sets such as DEM terrain grids, 2D polygon data sets such as coastlines, city outlines, lake outlines, and 2D raster data sets such as the 1 km NAOO land use/land cover data. It also has tools for generating realistic [[airport]]s, runways, and lighting based on available FAA data.

TerraGear is the primary tool used to generate the [[scenery]] for the [[FlightGear]] project.

== Introduction ==
For a variety of reasons you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to create or modify an airport layout, you might wish to see how that modified airport would look in the Scenery before deciding you're happy with the results. And normally, to see and use the airport in the scenery, it's necessary to submit the modifications to the FlighGear scenery staff and then wait untill the next update of the scenery of that area is available via [[TerraSync]] or in the [http://www.flightgear.org/Downloads/scenery.html official FlightGear Scenery] build. If you can build terrain yourself, you can start using it right away.

Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher resultion vector data (vmap1, Tiger) to get better roads/rivers. For all these reasons learning how to use TerraGear is a good idea.

== Getting TerraGear ==
=== Pre-compiled builds ===
* [http://flightgear.simpits.org:8080/job/TerraGear-Win-Cmake/lastSuccessfulBuild/artifact/*zip*/archive.zip Latest Windows build], built by the [[FlightGear Build Server]].
* [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Windows builds] (old)

=== Source ===
The source is hold in a [[git]] repository at Gitorious.
git clone git://git.gitorious.org/fg/terragear-cs.git

== Compilation ==
=== Dependencies ===
* TerraGear
** [[SimGear]] - '''Not''' simgear-cs!
*** SimGear can be compiled without OSG support thus eliminating many deps, like OSG. Use "-DSIMGEAR_HEADLESS=YES" for a minimal build.
** libnewmat - at least version newmat11 (which is beta at the time of writing) See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for info on how to obtain and install it.
** gpc - See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] for info on how to obtain and install it.
** POCO - For multicore support
** libgdal
** libproj
** libogdi
** libexpat
** Feel free to add more required libs here!

=== Building ===
Please, have a look at [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] and/or [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.cygwin;h=d0436ec0371dd9fa255a8a560a388818432600d6;hb=HEAD README.cygwin] of the terragear-cs sources.
./autogen.sh
./configure [options]
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install
<tt>./configure</tt> options:
--prefix=/path/to/install-dir
I am missing reliable data here. Please, revise/complete the list if you have more info!
--with-gdal=/path/to/gdal-config
--with-gpc=/path/to/libgenpolyclip.a
--with-newmat=/path/to/libnewmat.a
--with-plib=/path/to/libplib*.a
--with-simgear=/path/to/libsg*.a
--with-osg=/path/to/OSGinstallation

=== Platform specific ===
* Debian: [[Building FlightGear - Debian#TerraGear]]
* Gentoo: <tt>emerge -av terragear-cs</tt> See [[Building Flightgear - Gentoo]].
* Ubuntu: [[Building terragear-cs in Ubuntu_64]]

== GUI Tool ==
A [[TerraGear GUI]] is available for those that would like to use TerraGear without knowing/using the command line options.

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]
* [[TerraGear Documentation]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

[[es:TerraGear]]

Airwave Xtreme 150

2012-07-31T12:21:28Z

Papillon81: Remove obsolete todos

{{infobox Aircraft
|ready = thermal
|image = Airwave Xtreme 150 Innsbruck.png
|name = Airwave Xtreme 150
|type = Hang glider
|fdm = JSBSim
|status =
|fgname = airwaveXtreme150-JSBSim
|authors = Michael Selig, Captain Slug, D-NXKT
}}

== Recommended flying sites ==
A very beautiful site is the real life hang gliding launch "Seegrube" which is located near LOWI (--lon=11.377417 --lat=47.30525 --heading=180 --on-ground). Choose 15kt wind from 180deg for all altitudes and soar up to the summits.

A more challenging flight is "Fort Funston" near KSFO. It's a famous hang gliding site located at the coast with an altitude difference of only (250ft). Unfortunately directly at "Fort Funston" the FlightGear terrain is too smeared to produce sufficient ridge lift but a little bit further south (--lon=-122.4942234 --lat=37.6980674 --heading=270 --on-ground) ridge lift works perfectly. Choose wind with 20kt from 270deg. Be careful with the angle of attack on ground. Turn left after launch and fly very close to the cliff. Play with the performance settings to explore their influence on sink rate and wind-penetration.

== External links ==
A [http://www.flightgear.org/forums/viewtopic.php?f=19&t=16744 nice flight] with the Airwave Xtreme

[[Category:Delta-wing aircraft]]
[[Category:Hang gliders]]

Airwave Xtreme 150

2012-07-31T11:57:25Z

Papillon81: /* Recommended flying sites */ fixed another hyphen

{{infobox Aircraft
|ready = thermal
|image = Airwave Xtreme 150 Innsbruck.png
|name = Airwave Xtreme 150
|type = Hang glider
|fdm = JSBSim
|status =
|fgname = airwaveXtreme150-JSBSim
|authors = Michael Selig, Captain Slug, D-NXKT
}}

== Recommended flying sites ==
A very beautiful site is the real life hang gliding launch "Seegrube" which is located near LOWI (--lon=11.377417 --lat=47.30525 --heading=180 --on-ground). Choose 15kt wind from 180deg for all altitudes and soar up to the summits.

A more challenging flight is "Fort Funston" near KSFO. It's a famous hang gliding site located at the coast with an altitude difference of only (250ft). Unfortunately directly at "Fort Funston" the FlightGear terrain is too smeared to produce sufficient ridge lift but a little bit further south (--lon=-122.4942234 --lat=37.6980674 --heading=270 --on-ground) ridge lift works perfectly. Choose wind with 20kt from 270deg. Be careful with the angle of attack on ground. Turn left after launch and fly very close to the cliff. Play with the performance settings to explore their influence on sink rate and wind-penetration.

== Development status/Issues/Todo ==
'''Outside:'''
* 3d model is bumpy
* man in the hang glider needs some running animation when starting from the ground

'''3D cockpit:'''
* 3d cockpit is not available ( i don't know how you call those rods of a hang glider)

'''General:'''
* engine sound in cockpit does not differ from outside engine sound (the plane has no engine and there is no inside)
* aircraft is not set on the correct elevation when starting flightsgear, lowest part of the aircraft is approximately 0.40 m below the ground

== External links ==
A [http://www.flightgear.org/forums/viewtopic.php?f=19&t=16744 nice flight] with the Airwave Xtreme

[[Category:Delta-wing aircraft]]
[[Category:Hang gliders]]

Airwave Xtreme 150

2012-07-31T11:56:01Z

Papillon81: /* Recommended flying sites */ fixed hyphen

{{infobox Aircraft
|ready = thermal
|image = Airwave Xtreme 150 Innsbruck.png
|name = Airwave Xtreme 150
|type = Hang glider
|fdm = JSBSim
|status =
|fgname = airwaveXtreme150-JSBSim
|authors = Michael Selig, Captain Slug, D-NXKT
}}

== Recommended flying sites ==
A very beautiful site is the real life hang gliding launch "Seegrube" which is located near LOWI (--lon=11.377417 --lat=47.30525 --heading=180 --on-ground). Choose 15kt wind from 180deg for all altitudes and soar up to the summits.

A more challenging flight is "Fort Funston" near KSFO. It's a famous hang gliding site located at the coast with an altitude difference of only (250ft). Unfortunately directly at "Fort Funston" the FlightGear terrain is too smeared to produce sufficient ridge lift but a little bit further south (--lon=-122.4942234 --lat=37.6980674 --heading=270 –-on-ground) ridge lift works perfectly. Choose wind with 20kt from 270deg. Be careful with the angle of attack on ground. Turn left after launch and fly very close to the cliff. Play with the performance settings to explore their influence on sink rate and wind-penetration.

== Development status/Issues/Todo ==
'''Outside:'''
* 3d model is bumpy
* man in the hang glider needs some running animation when starting from the ground

'''3D cockpit:'''
* 3d cockpit is not available ( i don't know how you call those rods of a hang glider)

'''General:'''
* engine sound in cockpit does not differ from outside engine sound (the plane has no engine and there is no inside)
* aircraft is not set on the correct elevation when starting flightsgear, lowest part of the aircraft is approximately 0.40 m below the ground

== External links ==
A [http://www.flightgear.org/forums/viewtopic.php?f=19&t=16744 nice flight] with the Airwave Xtreme

[[Category:Delta-wing aircraft]]
[[Category:Hang gliders]]

Airwave Xtreme 150

2012-07-31T07:57:58Z

Papillon81: /* Recommended flying sites */ little correction

{{infobox Aircraft
|ready = thermal
|image = Airwave Xtreme 150 Innsbruck.png
|name = Airwave Xtreme 150
|type = Hang glider
|fdm = JSBSim
|status =
|fgname = airwaveXtreme150-JSBSim
|authors = Michael Selig, Captain Slug, D-NXKT
}}

== Recommended flying sites ==
A very beautiful site is the real life hang gliding launch "Seegrube" which is located near LOWI (--lon=11.377417 --lat=47.30525 –heading=180 --on-ground). Choose 15kt wind from 180deg for all altitudes and soar up to the summits.

A more challenging flight is "Fort Funston" near KSFO. It's a famous hang gliding site located at the coast with an altitude difference of only (250ft). Unfortunately directly at "Fort Funston" the FlightGear terrain is too smeared to produce sufficient ridge lift but a little bit further south (--lon=-122.4942234 --lat=37.6980674 --heading=270 –on-ground) ridge lift works perfectly. Choose wind with 20kt from 270deg. Be careful with the angle of attack on ground. Turn left after launch and fly very close to the cliff. Play with the performance settings to explore their influence on sink rate and wind-penetration.

== Development status/Issues/Todo ==
'''Outside:'''
* 3d model is bumpy
* man in the hang glider needs some running animation when starting from the ground

'''3D cockpit:'''
* 3d cockpit is not available ( i don't know how you call those rods of a hang glider)

'''General:'''
* engine sound in cockpit does not differ from outside engine sound (the plane has no engine and there is no inside)
* aircraft is not set on the correct elevation when starting flightsgear, lowest part of the aircraft is approximately 0.40 m below the ground

== External links ==
A [http://www.flightgear.org/forums/viewtopic.php?f=19&t=16744 nice flight] with the Airwave Xtreme

[[Category:Delta-wing aircraft]]
[[Category:Hang gliders]]

Airwave Xtreme 150

2012-07-19T13:05:11Z

Papillon81: Updated FDM. Added some useful info from the ML announcement

{{infobox Aircraft
|ready = thermal
|image = Airwave Xtreme 150 Innsbruck.png
|name = Airwave Xtreme 150
|type = Hang glider
|fdm = JSBSim
|status =
|fgname = airwaveXtreme150-JSBSim
|authors = Michael Selig, Captain Slug, D-NXKT
}}

== Recommended flying sites ==
A very beautiful site is the real life hang gliding launch "Hafelekar" which is located near LOWI (--lon=11.377417 --lat=47.30525 –heading=180 --on-ground). Choose 15kt wind from 180deg for all altitudes and soar up to the summits.
A more challenging flight is "Fort Funston" near KSFO. It's a famous hang gliding site located at the coast with an altitude difference of only (250ft). Unfortunately directly at "Fort Funston" the FlightGear terrain is too smeared to produce sufficient ridge lift but a little bit further south (--lon=-122.4942234 --lat=37.6980674 --heading=270 –on-ground) ridge lift works perfectly. Choose wind with 20kt from 270deg. Be careful with the angle of attack on ground. Turn left after launch and fly very close to the cliff. Play with the performance settings to explore their influence on sink rate and wind-penetration.

== Development status/Issues/Todo ==
'''Outside:'''
* 3d model is bumpy
* man in the hang glider needs some running animation when starting from the ground

'''3D cockpit:'''
* 3d cockpit is not available ( i don't know how you call those rods of a hang glider)

'''General:'''
* engine sound in cockpit does not differ from outside engine sound (the plane has no engine and there is no inside)
* aircraft is not set on the correct elevation when starting flightsgear, lowest part of the aircraft is approximately 0.40 m below the ground

[[Category:Delta-wing aircraft]]
[[Category:Hang gliders]]

Changelog 2.8.0

2012-07-18T10:42:53Z

Papillon81: /* Some of the major changes include: */ Airport signs

{{Draft|changelog|}}

==FlightGear 2.8.0 ChangeLog==

The [[FlightGear]] development team is happy to announce the v2.8.0 release of FlightGear, the free, open-source flight simulator.
This new version contains many exciting new features, enhancements and bugfixes.

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create
the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world
by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a worldwide multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2.8.0 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!

=== Some of the major changes include: ===

'''Aircraft operations'''

'''AI system'''

'''AI Traffic'''
* Improved aircraft models and textures.

'''Flight dynamics'''
* Synced with the JSBSim project.

'''Environment'''
* Random objects are only placed within certain areas of a terrain texture.
* Airport signs with full apt.dat 850 syntax support. Models are rendered in 3D now, with support for double-sided signs.
* Random 3D buildings for urban areas, complete with lighting at night.

'''Interface'''
* Support for menu translations.

'''Highlighted new and improved aircraft'''
* [[Airwave Xtreme 150]]: complete new (JSBSim) flight dynamics, new model, advanced pilot animations.
* [[Cessna 337G Skymaster]]

'''Project infrastructure'''
* Various improvements to our scenery database have made it easier than ever to add, delete or update objects to the FlightGear world.

'''Visual effects'''
* A new, experimental renderer, named after the famous painter Rembrandt, is included for testing purposes.
* Easy selection of material files.

'''Other'''
* Additional joysticks and rudder pedals are supported out-of-the-box:
** InterLink Elite
** Qware USB
** Saitek Cyborg X (F.L.Y. 5)
** Saitek Pro Flight Trim Wheel
** Saitek Pro Flight Yoke
** Speedlink Defender

'''Bug fixes'''
* See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.8.0 our bugtracker] for an extensive list of the bugs fixed in this release.

[[Category:FlightGear changelogs]]

TerraGear Documentation

2012-07-15T20:57:53Z

Papillon81: /* hgtfit */ correct name to terrafit

There has been a lot of questions relating to scenery generation tools. This page is an attempt to document each of the tools I use. I will also document the design, and what each tool is actually doing.

My hope is to attract more developers to work on the tools to make it easier to create better scenery for [[FlightGear]].

== Toolchain ==
=== hgtchop ===
hgtchop is responsible for cropping height data files into SimGear buckets (or tiles). Most height data is published in fairly large data files that cover 1 square degree. For SRTM-1 data, there are 3601 x 3601 data points per file. For SRTM-3 data, there are 1201 x 1201 data points per file. SRTM datafiles are named by their southwestern most point.

When TerraGear tools need to query elevation data, they do so expecting the data to be located in a standard SimGear folder structure as follows:

{| class="wikitable"
|-
! Format !! Example
|-
|''10 deg x 10 deg folder''|| ''w070n10''
|-
|— ''1 degree by 1 degree subfolder ''||— ''w065n17''
|-
|—— ''bucket file ''||—— ''1891048.arr.gz ''
|}

hgtchop will create this directory structure in the work folder, and create sgbucket.arr.gz files within.

==== command options ====
hgtchop <resolution> <hgt_file> <work_dir>

'''resolution''' 
Each file created contains ALL of the data points for the simgear tile. For SRTM-1 data, the resultant grid (for tiles near the equator) is 450 x 450 points. For SRTM-3 data, the grid is 150 x 150 points. The resolution parameter tells hgtcop the distance between sampled points. Note that tile width varies with latitude. So 'square' tiles really only exist between 22 degrees N - 22 degrees S. The tile widths are explained here: [[Tile_Index_Scheme|Tile Index Scheme]]

'''hgt_file''' 
The source file. Usually, the source files are 1 degree by 1 degree, and have enough data to create 64 simgear buckets (near the equator).

'''work_dir''' 
This is where hgt-chop will generate the elevation directory structure described above.

==== notes ====
#zip files : In TGHgt::open, if the file extension is '.zip', then unzip executable is executed through system(). If the host system doesn't have unzip, then hgtchop will fail. The unzip should be performed via SimGear - Investigation needed 
 

=== terrafit ===

terrafit is responsible for taking the raw heightfield data for one bucket, and picking the most important points to generate a triangle mesh. It uses [http://mgarland.org/archive/cmu/scape/terra.html Terra] to perform the work. The output is not a triangulation, but rather a list of nodes that can be fed to a triangulation routine. The quality of FlightGear's terrain is directly related to what parameters are fed into terrafit.

==== command options ====
terrafit [options] <file | path>

{| class="wikitable"
|-
! Option !! Default !! Description
|-
| -m ''or'' --minnodes||50||smallest number of nodes to produce. For a mostly flat tile, more nodes are wasteful.
|-
| -x ''or'' --maxnodes||1000||largest number of nodes to produce. For a very complex tile, limiting this will reduce the detail of the resulting mesh.
|-
| -e ''or'' --maxerror||40||While picking points, and we have at least minnodes, but not yet maxnodes, the mesh will be completed if any of the remaining points maximum elevation error drops below this value.
|}

As you can see, the default parameters are pretty conservative. At most, we will output 1,000 nodes. The input data for SRTM-1 contains 202,500 nodes, so we are only keeping 0.5% of the source data (or for SRTM-3, with 22,500 nodes, we keep ~5% of the source data)

For my experiments, I've increased maxnodes to 20,000, and decreased max error to 10 meters, and didn't see a major frame rate hit).

If you consider the number of nodes added when using detailed landclass, it's unfortunate that the height lookup for these points will be based on such an inaccurate mesh. 
 

=== ogr-decode ===

=== genapts / genapts850 ===

==== design ====
:Step 1 : Parse

:Step 2 : Clip

:Step 3 : Clean

:Step 4 : Elevation

:Step 5 : Output

=== fgfs-construct ===

== Related content ==
* [[Using Terragear]]
* [[TerraGear CORINE]]

{{Terra}}
{{Building}}

[[Category:Scenery enhancement]]

Taxiway signs

2012-07-01T13:08:17Z

Papillon81: /* Taxiway Signs */ Improve description

Taxiway signs add a great deal of realism and information to an airport. FlightGear supports the apt.dat 850 signs specification.

Users interested in helping to improve the scenery are extremely welcome to read the [[#Placing_signs|Placing signs]] section of this article. [[FGSignMaker]], a tool to generate taxiway sign codes, is a tool that can make placing taxiway signs easier.

== Explanation of signs ==
There are many types of signs on airfields. The following table explains the used syntax.

=== Taxiway Signs ===
{| style="background: white; text-align: left; border: 1px silver solid; border-collapse: collapse; margin-left:1em;" cellpadding="3" border="1"
||[[File:Sign_27-33.jpg|x32px]]
|'''Black lettering on a yellow background: direction sign:''' Gives directions to other installations: "Runways 27 and 33 are to your right".
|<tt>OBJECT_SIGN {@Y}27-33{^r}</tt>
|-
|[[File:Sign_A.jpg|x32px]]
|'''Yellow lettering on a black background: location sign:''' Indicates the taxiway you are on.
|style="width:200px"|<tt>OBJECT_SIGN {@L}A</tt>
|-
||[[File:Sign_15-33.jpg|x32px]]
|'''Holding position sign:''' Hold here. From your position on the taxiway at midfield, the threshold for Runway 15 is to your left and the threshold for Runway 33 is to your right. This sign is located next to the yellow holding position markings painted on the taxiway pavement.
|<tt>OBJECT_SIGN {@R}15-33</tt>
|-
||[[File:Sign_ILS.jpg|x32px]]
|'''ILS holding position sign:''' ATC may hold you at this sign when the instrument landing system is being used at the airport. Aircraft taxiing beyond this point may interfere with the ILS signal to approaching aircraft.
|<tt>OBJECT_SIGN {@R}ILS</tt>
|-
||[[File:Sign_15-APCH.jpg|x32px]]
|'''Holding position sign for approach areas:''' Hold here unless cleared to cross. Taxiing past this sign may interfere with arriving or departing aircraft to Runway 15.
|<tt>OBJECT_SIGN {@R}15-APCH</tt>
|-
||[[File:Sign safety.png|x32px]]
|'''Runway boundary sign:''' This sign faces the runway and is visible to pilots exiting the runway. Taxi past this sign (dash past the dashed lines) to be sure you are clear of the runway.
|<tt>OBJECT_SIGN {safety}</tt>
|-
||[[File:Sign critical.png|x32px]]
|'''ILS critical area boundary sign:''' Seen when exiting the runway, this sign marks the boundary of the ILS critical area. When ILS approaches are in use, be sure your aircraft has passed beyond this sign before stopping on the taxiway.
|<tt>OBJECT_SIGN {critical}</tt>
|-
||[[File:Sign hazard.png|x32px]]
|'''End of taxiway:''' Seen when a taxiway ends and a left/right turn has to be performed instead.
|<tt>OBJECT_SIGN {hazard}</tt>
|-
|[[File:Sign_no-entry.jpg|x32px]]
|'''No entry sign:''' Do not enter this area. Aircraft are prohibited. This sign would be found at the entrance to a one-way taxiway or at the intersection of a road intended for vehicles.
<del>'''Note that this sign needs the red color (@R) prefix in FlightGear!'''</del>
|<tt>OBJECT_SIGN {no-entry}</tt>
|}

== Placing signs ==
Signs can be placed by obtaining the lat/lon coordinates from a [[GNU GPL]] licensed source.

You can also [[Howto: Place 3D objects with the UFO|use the UFO]] for easier positioning. Load (by pressing the l-key) the <tt>[[$FG ROOT]]/Aircraft/UFO/Models/sign.ac</tt> model to find the correct headings. After dumping the data, replace OBJECT_SHARED by OBJECT_SIGN and add the sign codes instead of <tt>Aircraft/UFO/Models/sign.ac</tt>.

=== Sign types ===
These instructions specify sign types. They refer to the sign names in the FAA specification:

{| class="prettytable" border="0" cellspacing="2"
! style="background:#efefef; text-align: center" | Name
! style="background:#efefef; text-align: center" | Instructions
! style="background:#efefef; text-align: center" | Description
|-
|L858-Y
| style="text-align: center" |<tt>@Y</tt>
|"Direction, Destination, Boundary" sign (black on yellow) 
|-
|L858-R
| style="text-align: center" |<tt>@R</tt>
|"Mandatory Instruction" sign (white on red with black outline)
|-
|L858-L
| style="text-align: center" |<tt>@L</tt>
|"Location" sign (yellow text and frame on black)
|-
|L858-B
| style="text-align: center" |<tt>@B</tt>
|"Runway Distance Remaining" sign (white on black)
|}

These sign type specifiers are used to request FAA signs L858-Y, L858-R, L858-L and L858-B of unspecified size. It is up to the implementation to choose a default size. If the size is known, then a size digit is appended, which also refers to the FAA standard:

{| class="prettytable" border="0" cellspacing="2" style="text-align: center;"
! style="background:#efefef; text-align: center" |
! style="background:#efefef; text-align: center" |Size 1 0.460 m
! style="background:#efefef; text-align: center" |Size 2 0.610 m
! style="background:#efefef; text-align: center" |Size 3 0.760 m
! style="background:#efefef; text-align: center" |Size 4 1.220 m
! style="background:#efefef; text-align: center" |Size 5 0.760 m
|-
! style="background:#efefef; text-align: center" |L858-Y
|<tt>@Y1</tt>
|<tt>@Y2</tt>
|<tt>@Y3</tt>
|
|
|-
! style="background:#efefef; text-align: center" |L858-R
|<tt>@R1</tt>
|<tt>@R2</tt>
|<tt>@R3</tt>
|
|
|-
! style="background:#efefef; text-align: center" |L858-L
|<tt>@L1</tt>
|<tt>@L2</tt>
|<tt>@L3</tt>
|
|
|-
! style="background:#efefef; text-align: center" |L858-B
|
|
|
|<tt>@B4</tt>
|<tt>@B5</tt>
|}

=== Multi-Letter Glyph Names ===
{| border=1 cellspacing=0 cellpadding=5
|<tt>^u</tt>
|up arrow
|-
|<tt>^d</tt>
|down arrow
|-
|<tt>^l</tt>
|left arrow
|-
|<tt>^r</tt>
|right arrow
|-
|<tt>^lu</tt>
|left-up arrow
|-
|<tt>^ru</tt>
|right-up arrow
|-
|<tt>^ld</tt>
|left-down arrow
|-
|<tt>^rd</tt>
|right-down arrow
|-
|<tt>r1</tt>
|roman numeral I
|-
|<tt>r2</tt>
|roman numeral II
|-
|<tt>r3</tt>
|roman numeral III
|-
|<tt>no-entry</tt>
|no-entry sign (white circle with horizontal bar on red background)
|}

Note that diagonal arrows always have the right/left letter first, as is common in Cartesian coordinate systems. So it's <tt>ru</tt> (right up), not <tt>ur</tt>.

=== Examples ===
* <tt>OBJECT_SIGN {@Y,@l}S7{@L}B{@Y}S8{@ru} -22.592 63.985 46 72</tt>
* <tt>OBJECT_SIGN {@Y}MAX_SPAN_52M -22.592 63.985 46 72</tt>
* <tt>OBJECT_SIGN {@R,no-entry} -22.592 63.985 46 72</tt>
* <tt>OBJECT_SIGN {@L}V2{@R}06-24 -22.592 63.985 46 72</tt>

== Related content ==
* [[FGSignMaker]]
* [[Sign Specification Proposal]]

== External links ==
* [http://www.aopa.org/asf/publications/taxi/taxi_signage.html AOPA Airport and Taxiway Signage]

[[Category:Scenery enhancement]]

Taxiway signs

2012-07-01T12:53:13Z

Papillon81: Improve syntax, update textures

Taxiway signs add a great deal of realism and information to an airport. FlightGear supports the apt.dat 850 signs specification.

Users interested in helping to improve the scenery are extremely welcome to read the [[#Placing_signs|Placing signs]] section of this article. [[FGSignMaker]], a tool to generate taxiway sign codes, is a tool that can make placing taxiway signs easier.

== Explanation of signs ==
There are many types of signs on airfields. The following table explains the used syntax.

=== Taxiway Signs ===
{| style="background: white; text-align: left; border: 1px silver solid; border-collapse: collapse; margin-left:1em;" cellpadding="3" border="1"
|[[File:Sign_A.jpg|x32px]]
|'''Taxiway location sign:''' Indicates the taxiway you are on.
|style="width:200px"|<tt>OBJECT_SIGN {@L}A</tt>
|-
||[[File:Sign_15-33.jpg|x32px]]
|'''Holding position sign:''' Hold here. From your position on the taxiway at midfield, the threshold for Runway 15 is to your left and the threshold for Runway 33 is to your right. This sign is located next to the yellow holding position markings painted on the taxiway pavement.
|<tt>OBJECT_SIGN {@R}15-33</tt>
|-
||[[File:Sign_ILS.jpg|x32px]]
|'''ILS holding position sign:''' ATC may hold you at this sign when the instrument landing system is being used at the airport. Aircraft taxiing beyond this point may interfere with the ILS signal to approaching aircraft.
|<tt>OBJECT_SIGN {@R}ILS</tt>
|-
||[[File:Sign_15-APCH.jpg|x32px]]
|'''Holding position sign for approach areas:''' Hold here unless cleared to cross. Taxiing past this sign may interfere with arriving or departing aircraft to Runway 15.
|<tt>OBJECT_SIGN {@R}15-APCH</tt>
|-
||[[File:Sign safety.png|x32px]]
|'''Runway boundary sign:''' This sign faces the runway and is visible to pilots exiting the runway. Taxi past this sign (dash past the dashed lines) to be sure you are clear of the runway.
|<tt>OBJECT_SIGN {safety}</tt>
|-
||[[File:Sign critical.png|x32px]]
|'''ILS critical area boundary sign:''' Seen when exiting the runway, this sign marks the boundary of the ILS critical area. When ILS approaches are in use, be sure your aircraft has passed beyond this sign before stopping on the taxiway.
|<tt>OBJECT_SIGN {critical}</tt>
|-
||[[File:Sign hazard.png|x32px]]
|'''End of taxiway:''' Seen when a taxiway ends and a left/right turn has to be performed instead.
|<tt>OBJECT_SIGN {hazard}</tt>
|-
|[[File:Sign_no-entry.jpg|x32px]]
|'''No entry sign:''' Do not enter this area. Aircraft are prohibited. This sign would be found at the entrance to a one-way taxiway or at the intersection of a road intended for vehicles.
<del>'''Note that this sign needs the red color (@R) prefix in FlightGear!'''</del>
|<tt>OBJECT_SIGN {no-entry}</tt>
|-
||[[File:Sign_MIL.jpg|x32px]]
|'''Inbound destination sign:''' The military installation is to your right. Other information signs are Cargo, Term (Terminal), Ramp, etc.
|<tt>OBJECT_SIGN {@Y}MIL{^r}</tt>
|-
||[[File:Sign_27-33.jpg|x32px]]
|'''Outbound destination sign to different runways:''' Runways 27 and 33 are to your right.
|<tt>OBJECT_SIGN {@Y}27-33{^r}</tt>
|}

== Placing signs ==
Signs can be placed by obtaining the lat/lon coordinates from a [[GNU GPL]] licensed source.

You can also [[Howto: Place 3D objects with the UFO|use the UFO]] for easier positioning. Load (by pressing the l-key) the <tt>[[$FG ROOT]]/Aircraft/UFO/Models/sign.ac</tt> model to find the correct headings. After dumping the data, replace OBJECT_SHARED by OBJECT_SIGN and add the sign codes instead of <tt>Aircraft/UFO/Models/sign.ac</tt>.

=== Sign types ===
These instructions specify sign types. They refer to the sign names in the FAA specification:

{| class="prettytable" border="0" cellspacing="2"
! style="background:#efefef; text-align: center" | Name
! style="background:#efefef; text-align: center" | Instructions
! style="background:#efefef; text-align: center" | Description
|-
|L858-Y
| style="text-align: center" |<tt>@Y</tt>
|"Direction, Destination, Boundary" sign (black on yellow) 
|-
|L858-R
| style="text-align: center" |<tt>@R</tt>
|"Mandatory Instruction" sign (white on red with black outline)
|-
|L858-L
| style="text-align: center" |<tt>@L</tt>
|"Location" sign (yellow text and frame on black)
|-
|L858-B
| style="text-align: center" |<tt>@B</tt>
|"Runway Distance Remaining" sign (white on black)
|}

These sign type specifiers are used to request FAA signs L858-Y, L858-R, L858-L and L858-B of unspecified size. It is up to the implementation to choose a default size. If the size is known, then a size digit is appended, which also refers to the FAA standard:

{| class="prettytable" border="0" cellspacing="2" style="text-align: center;"
! style="background:#efefef; text-align: center" |
! style="background:#efefef; text-align: center" |Size 1 0.460 m
! style="background:#efefef; text-align: center" |Size 2 0.610 m
! style="background:#efefef; text-align: center" |Size 3 0.760 m
! style="background:#efefef; text-align: center" |Size 4 1.220 m
! style="background:#efefef; text-align: center" |Size 5 0.760 m
|-
! style="background:#efefef; text-align: center" |L858-Y
|<tt>@Y1</tt>
|<tt>@Y2</tt>
|<tt>@Y3</tt>
|
|
|-
! style="background:#efefef; text-align: center" |L858-R
|<tt>@R1</tt>
|<tt>@R2</tt>
|<tt>@R3</tt>
|
|
|-
! style="background:#efefef; text-align: center" |L858-L
|<tt>@L1</tt>
|<tt>@L2</tt>
|<tt>@L3</tt>
|
|
|-
! style="background:#efefef; text-align: center" |L858-B
|
|
|
|<tt>@B4</tt>
|<tt>@B5</tt>
|}

=== Multi-Letter Glyph Names ===
{| border=1 cellspacing=0 cellpadding=5
|<tt>^u</tt>
|up arrow
|-
|<tt>^d</tt>
|down arrow
|-
|<tt>^l</tt>
|left arrow
|-
|<tt>^r</tt>
|right arrow
|-
|<tt>^lu</tt>
|left-up arrow
|-
|<tt>^ru</tt>
|right-up arrow
|-
|<tt>^ld</tt>
|left-down arrow
|-
|<tt>^rd</tt>
|right-down arrow
|-
|<tt>r1</tt>
|roman numeral I
|-
|<tt>r2</tt>
|roman numeral II
|-
|<tt>r3</tt>
|roman numeral III
|-
|<tt>no-entry</tt>
|no-entry sign (white circle with horizontal bar on red background)
|}

Note that diagonal arrows always have the right/left letter first, as is common in Cartesian coordinate systems. So it's <tt>ru</tt> (right up), not <tt>ur</tt>.

=== Examples ===
* <tt>OBJECT_SIGN {@Y,@l}S7{@L}B{@Y}S8{@ru} -22.592 63.985 46 72</tt>
* <tt>OBJECT_SIGN {@Y}MAX_SPAN_52M -22.592 63.985 46 72</tt>
* <tt>OBJECT_SIGN {@R,no-entry} -22.592 63.985 46 72</tt>
* <tt>OBJECT_SIGN {@L}V2{@R}06-24 -22.592 63.985 46 72</tt>

== Related content ==
* [[FGSignMaker]]
* [[Sign Specification Proposal]]

== External links ==
* [http://www.aopa.org/asf/publications/taxi/taxi_signage.html AOPA Airport and Taxiway Signage]

[[Category:Scenery enhancement]]

File:Sign hazard.png

2012-07-01T12:43:49Z

Papillon81:

=={{int:filedesc}}==
{{Information
|description={{en|1=Hazard sign}}
|date=2012-07-01
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

File:Sign critical.png

2012-07-01T12:43:48Z

Papillon81:

=={{int:filedesc}}==
{{Information
|description={{en|1=Critical sign}}
|date=2012-07-01
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

File:Sign safety.png

2012-07-01T12:43:46Z

Papillon81:

=={{int:filedesc}}==
{{Information
|description={{en|1=Safety sign}}
|date=2012-07-01
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

FlightGear Newsletter June 2012

2012-06-23T12:22:55Z

Papillon81: /* Taxiway signs support improved */ special signs added

{{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 ==
=== 2.8.0 release preparations ===
{{Main article|Release plan}}
Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted.

Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released.

=== Rembrandt controls ===
[[File:Rembrandt dialog.png|thumb|left]]
A special [[Project Rembrandt|Rembrandt]] dialog has been created, to give the user full control over Rembrandt's rich feature set. The dialog can be reached via <tt>View > Rendering Options</tt>. By adjusting the various options, the framerate impact can be decreased.

=== Taxiway signs support improved ===
Flightgear does now better support the taxiway signs syntax of the apt.dat 850 spec.
Christian implemented the new specs and got rid of some old cruft along the way. The signs are also rendered now with a 3D case around and we support double sided signs as well!
[[File:3d sign front.png|320px|left|Taxiway sign, front side]]
[[File:3d sign back.png|320px|right|Taxiway sign, back side]]
Emilian updated the signs textures to have some shading on top, which improves the overall appearance a lot. Also, Now it is possible to make use of new special types, such as {critical}, {safety}, {no-entry} and {hazard}. See the [[Signs|Signs entry]] for more details.
[[File:3d sign special.png|320px|left|special sign variants]]

James was able to improve the rendering code considerably. The signs are now rendered per stg file into one geometry. This reduces the amount of geodes a lot.

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

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===

Please see [[Howto:Start core development]]

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

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

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

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

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice monthly). These snapshots 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 ==

Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google).

http://almien.co.uk/flightgear/map/multiplayer/

[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]

OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos.

Features available in this map include:
* Historical tracks ("breadcrumbs") showing movement of aircraft over time
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them

== FlightGear add-ons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===
==== Glaser-Dirks DG-101G ====
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.

=== Liveries ===

== Scenery corner ==
=== Airports ===
====London Gatwick in 850====
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.

[[File:Gatwick-850-version.png|640px]]

Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].

====Berlin-Tempelhof (EDDI/THF)====
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.

The Berlin Tempelhof airport was opened officially on 8 October 1923, but there was aviation activity in this area before. In 1909 the Wright brothers showed their flyer there. During the 1920's it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during the Second World War. Work on the modern building was started in 1936, but was not finished until the end of the war, when it became a U.S. military base. It became famous during the Berlin airlift of 1948-49. In the 1950's it was opened to civilian flights, and in 1993 it ceased to be a military base. The airport was closed on 30 October 2008.

Tempelhof airbase was not only an airport, but also a small independent town in the city of Berlin. It had its own power plant, waterworks, garbage incinerator, a railway siding, sporting facilities, barbecue area, and plant nursery. The aim is to have the airport area and the adjacent surroundings as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities have been modelled and send to the repository. The main building is in work. It's modeled partly based on original construction drawings and it is textured with photos of the real thing.

If you ever had the opportunity to arrive there by plane, you may remember the impressive experience of rolling with your plane under this mighty roof construction and walking away freely on the apron, even as a normal passenger. This gives a good impression of what aviation was like in former days.

Since you can't have this experience any longer in real life, maybe we will have it in FlightGear someday. But be patient: since it claims to be among the twenty largest buildings of the world, it will take some time to finish it.

Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].

[[File:EDDI3.jpg|640px]]
[[File:EDDI1.jpg|640px]]
[[File:EDDI2.jpg|640px]]

===Düsseldorf International (EDDL)===
[[Düsseldorf International Airport]] is Germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings. The scenery was generated with corine and openstreetmap.

[[File:EDDL-generic1.jpg|640px]]
[[File:EDDL-night.jpg|640px]]

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

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

== Wiki updates ==
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.

In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by clicking the Edit button at the top of the page.
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).

===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 ===
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt>

Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.

=== Virtual airlines ===
=== FlightGear events ===
==== FlightGear at the National Museum of Flight, Scotland ====
[[File:FlightGear demo at museum.jpg|thumb|FlightGear at the Museum of Flight, Scotland]]
Stuart Buchanan (stuart on the forum), ran a booth showing off FlightGear at the "Robots Live" event at the National Museum of Flight at East Fortune, Scotland, on Sunday 17th May. About 100 people tried landing an F-35C on a carrier, lots of flyers were handed out, and many compliments were received on the quality of the simulator. Demoing FG at an event at your local aviation museum is a great way to spread the word about FG. See our [[FlightGear Expo Checklist]] for guidance on how you can go about it.

==== FSweekend 2012 ====
With still several months to go, the FlightGear FSweekend team got the confirmation that [[FSweekend 2012]], the world's largest flight simulation event, will take place on '''3 and 4 November 2012''', at the usual location: Aviodrome museum ([[Lelystad Airport]], the Netherlands).

[[File:FSweekend banner 2012.jpg|left|270px]]
Until recently it was unsure whether the event would take place this year, because the museum announced its bankruptcy the Monday after last year's weekend. Aviodrome closed its doors by the end of 2011. Luckily a company was found that took over the museum and its collection; leading to the reopening earlier this year. The reopened museum is more attractive for children, as well as the average person (not just the true aviation enthusiastic).

The museum entrance fee gives you access to both the FSweekend and the museum. So when you've seen enough virtual stuff, there are plenty of real aircraft to discover. The FlightGear team would appreciate it if you are able to travel to Lelystad!

Facebook users can join [http://www.facebook.com/events/315742308452348 the event's page] to stay up to date and connect to other visitors.

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

File:3d-sign-special.png

2012-06-23T12:20:02Z

Papillon81: moved File:3d-sign-special.png to File:3d sign special.png: no dashes

#REDIRECT [[File:3d sign special.png]]

File:3d sign special.png

2012-06-23T12:20:02Z

Papillon81: moved File:3d-sign-special.png to File:3d sign special.png: no dashes

=={{int:filedesc}}==
{{Information
|description={{en|1=special variants for 3D signs}}
|date=2012-06-23
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

File:3d sign special.png

2012-06-23T12:19:29Z

Papillon81:

FlightGear Newsletter June 2012

2012-06-23T12:07:22Z

Papillon81: /* Taxiway signs support improved */ renamed the images

{{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 ==
=== 2.8.0 release preparations ===
{{Main article|Release plan}}
Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted.

Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released.

=== Rembrandt controls ===
[[File:Rembrandt dialog.png|thumb|left]]
A special [[Project Rembrandt|Rembrandt]] dialog has been created, to give the user full control over Rembrandt's rich feature set. The dialog can be reached via <tt>View > Rendering Options</tt>. By adjusting the various options, the framerate impact can be decreased.

=== Taxiway signs support improved ===
Flightgear does now better support the taxiway signs syntax of the apt.dat 850 spec.
Christian implemented the new specs and got rid of some old cruft along the way. The signs are also rendered now with a 3D case around and we support double sided signs as well!
[[File:3d sign front.png|320px|left|Taxiway sign, front side]]
[[File:3d sign back.png|320px|right|Taxiway sign, back side]]
Emilian updated the signs textures to have some shading on top, which improves the overall appearance a lot. Also, Now it is possible to make use of new special types, such as {critical}, {safety}, {no-entry} and {hazard}. See the [[Signs|Signs entry]] for more details.

James was able to improve the rendering code considerably. The signs are now rendered per stg file into one geometry. This reduces the amount of geodes a lot.

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

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===

Please see [[Howto:Start core development]]

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

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

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

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

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice monthly). These snapshots 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 ==

Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google).

http://almien.co.uk/flightgear/map/multiplayer/

[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]

OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos.

Features available in this map include:
* Historical tracks ("breadcrumbs") showing movement of aircraft over time
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them

== FlightGear add-ons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===
==== Glaser-Dirks DG-101G ====
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.

=== Liveries ===

== Scenery corner ==
=== Airports ===
====London Gatwick in 850====
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.

[[File:Gatwick-850-version.png|640px]]

Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].

====Berlin-Tempelhof (EDDI/THF)====
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.

The Berlin Tempelhof airport was opened officially on 8 October 1923, but there was aviation activity in this area before. In 1909 the Wright brothers showed their flyer there. During the 1920's it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during the Second World War. Work on the modern building was started in 1936, but was not finished until the end of the war, when it became a U.S. military base. It became famous during the Berlin airlift of 1948-49. In the 1950's it was opened to civilian flights, and in 1993 it ceased to be a military base. The airport was closed on 30 October 2008.

Tempelhof airbase was not only an airport, but also a small independent town in the city of Berlin. It had its own power plant, waterworks, garbage incinerator, a railway siding, sporting facilities, barbecue area, and plant nursery. The aim is to have the airport area and the adjacent surroundings as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities have been modelled and send to the repository. The main building is in work. It's modeled partly based on original construction drawings and it is textured with photos of the real thing.

If you ever had the opportunity to arrive there by plane, you may remember the impressive experience of rolling with your plane under this mighty roof construction and walking away freely on the apron, even as a normal passenger. This gives a good impression of what aviation was like in former days.

Since you can't have this experience any longer in real life, maybe we will have it in FlightGear someday. But be patient: since it claims to be among the twenty largest buildings of the world, it will take some time to finish it.

Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].

[[File:EDDI3.jpg|640px]]
[[File:EDDI1.jpg|640px]]
[[File:EDDI2.jpg|640px]]

===Düsseldorf International (EDDL)===
[[Düsseldorf International Airport]] is Germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings. The scenery was generated with corine and openstreetmap.

[[File:EDDL-generic1.jpg|640px]]
[[File:EDDL-night.jpg|640px]]

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

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

== Wiki updates ==
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.

In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by clicking the Edit button at the top of the page.
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).

===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 ===
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt>

Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.

=== Virtual airlines ===
=== FlightGear events ===
==== FlightGear at the National Museum of Flight, Scotland ====
[[File:FlightGear demo at museum.jpg|thumb|FlightGear at the Museum of Flight, Scotland]]
Stuart Buchanan (stuart on the forum), ran a booth showing off FlightGear at the "Robots Live" event at the National Museum of Flight at East Fortune, Scotland, on Sunday 17th May. About 100 people tried landing an F-35C on a carrier, lots of flyers were handed out, and many compliments were received on the quality of the simulator. Demoing FG at an event at your local aviation museum is a great way to spread the word about FG. See our [[FlightGear Expo Checklist]] for guidance on how you can go about it.

==== FSweekend 2012 ====
With still several months to go, the FlightGear FSweekend team got the confirmation that [[FSweekend 2012]], the world's largest flight simulation event, will take place on '''3 and 4 November 2012''', at the usual location: Aviodrome museum ([[Lelystad Airport]], the Netherlands).

[[File:FSweekend banner 2012.jpg|left|270px]]
Until recently it was unsure whether the event would take place this year, because the museum announced its bankruptcy the Monday after last year's weekend. Aviodrome closed its doors by the end of 2011. Luckily a company was found that took over the museum and its collection; leading to the reopening earlier this year. The reopened museum is more attractive for children, as well as the average person (not just the true aviation enthusiastic).

The museum entrance fee gives you access to both the FSweekend and the museum. So when you've seen enough virtual stuff, there are plenty of real aircraft to discover. The FlightGear team would appreciate it if you are able to travel to Lelystad!

Facebook users can join [http://www.facebook.com/events/315742308452348 the event's page] to stay up to date and connect to other visitors.

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

File:3d-sign-back.png

2012-06-23T12:06:33Z

Papillon81: moved File:3d-sign-back.png to File:3d sign back.png: no dashes allowed

#REDIRECT [[File:3d sign back.png]]

File:3d sign back.png

2012-06-23T12:06:33Z

Papillon81: moved File:3d-sign-back.png to File:3d sign back.png: no dashes allowed

=={{int:filedesc}}==
{{Information
|description={{en|1=Back side of a new 3D sign at EBAW}}
|date=2012-06-23
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

File:3d-sign-front.png

2012-06-23T12:06:08Z

Papillon81: moved File:3d-sign-front.png to File:3d sign front.png: no dashes allowed

#REDIRECT [[File:3d sign front.png]]

File:3d sign front.png

2012-06-23T12:06:08Z

Papillon81: moved File:3d-sign-front.png to File:3d sign front.png: no dashes allowed

=={{int:filedesc}}==
{{Information
|description={{en|1=Front side of a new 3D sign at EBAW}}
|date=2012-06-23
|source={{own}}
|author=[[User:Papillon81|Papillon81]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

FlightGear Newsletter June 2012

2012-06-23T11:46:53Z

Papillon81: /* Taxiway signs support improved */ Add some screens. Mode deatils

{{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 ==
=== 2.8.0 release preparations ===
{{Main article|Release plan}}
Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted.

Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released.

=== Rembrandt controls ===
[[File:Rembrandt dialog.png|thumb|left]]
A special [[Project Rembrandt|Rembrandt]] dialog has been created, to give the user full control over Rembrandt's rich feature set. The dialog can be reached via <tt>View > Rendering Options</tt>. By adjusting the various options, the framerate impact can be decreased.

=== Taxiway signs support improved ===
Flightgear does now better support the taxiway signs syntax of the apt.dat 850 spec.
Christian implemented the new specs and got rid of some old cruft along the way. The signs are also rendered now with a 3D case around and we support double sided signs as well!
[[File:3d-sign-front.png|320px|left|Taxiway sign, front side]]
[[File:3d-sign-back.png|320px|right|Taxiway sign, back side]]
Emilian updated the signs textures to have some shading on top, which improves the overall appearance a lot. Also, Now it is possible to make use of new special types, such as {critical}, {safety}, {no-entry} and {hazard}. See the [[Signs|Signs entry]] for more details.

James was able to improve the rendering code considerably. The signs are now rendered per stg file into one geometry. This reduces the amount of geodes a lot.

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

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===

Please see [[Howto:Start core development]]

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

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

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

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

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice monthly). These snapshots 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 ==

Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google).

http://almien.co.uk/flightgear/map/multiplayer/

[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]

OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos.

Features available in this map include:
* Historical tracks ("breadcrumbs") showing movement of aircraft over time
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them

== FlightGear add-ons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===
==== Glaser-Dirks DG-101G ====
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.

=== Liveries ===

== Scenery corner ==
=== Airports ===
====London Gatwick in 850====
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.

[[File:Gatwick-850-version.png|640px]]

Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].

====Berlin-Tempelhof (EDDI/THF)====
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.

The Berlin Tempelhof airport was opened officially on 8 October 1923, but there was aviation activity in this area before. In 1909 the Wright brothers showed their flyer there. During the 1920's it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during the Second World War. Work on the modern building was started in 1936, but was not finished until the end of the war, when it became a U.S. military base. It became famous during the Berlin airlift of 1948-49. In the 1950's it was opened to civilian flights, and in 1993 it ceased to be a military base. The airport was closed on 30 October 2008.

Tempelhof airbase was not only an airport, but also a small independent town in the city of Berlin. It had its own power plant, waterworks, garbage incinerator, a railway siding, sporting facilities, barbecue area, and plant nursery. The aim is to have the airport area and the adjacent surroundings as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities have been modelled and send to the repository. The main building is in work. It's modeled partly based on original construction drawings and it is textured with photos of the real thing.

If you ever had the opportunity to arrive there by plane, you may remember the impressive experience of rolling with your plane under this mighty roof construction and walking away freely on the apron, even as a normal passenger. This gives a good impression of what aviation was like in former days.

Since you can't have this experience any longer in real life, maybe we will have it in FlightGear someday. But be patient: since it claims to be among the twenty largest buildings of the world, it will take some time to finish it.

Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].

[[File:EDDI3.jpg|640px]]
[[File:EDDI1.jpg|640px]]
[[File:EDDI2.jpg|640px]]

===Düsseldorf International (EDDL)===
[[Düsseldorf International Airport]] is Germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings. The scenery was generated with corine and openstreetmap.

[[File:EDDL-generic1.jpg|640px]]
[[File:EDDL-night.jpg|640px]]

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

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

== Wiki updates ==
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.

In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by clicking the Edit button at the top of the page.
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).

===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 ===
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt>

Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.

=== Virtual airlines ===
=== FlightGear events ===
==== FlightGear at the National Museum of Flight, Scotland ====
[[File:FlightGear demo at museum.jpg|thumb|FlightGear at the Museum of Flight, Scotland]]
Stuart Buchanan (stuart on the forum), ran a booth showing off FlightGear at the "Robots Live" event at the National Museum of Flight at East Fortune, Scotland, on Sunday 17th May. About 100 people tried landing an F-35C on a carrier, lots of flyers were handed out, and many compliments were received on the quality of the simulator. Demoing FG at an event at your local aviation museum is a great way to spread the word about FG. See our [[FlightGear Expo Checklist]] for guidance on how you can go about it.

==== FSweekend 2012 ====
With still several months to go, the FlightGear FSweekend team got the confirmation that [[FSweekend 2012]], the world's largest flight simulation event, will take place on '''3 and 4 November 2012''', at the usual location: Aviodrome museum ([[Lelystad Airport]], the Netherlands).

[[File:FSweekend banner 2012.jpg|left|270px]]
Until recently it was unsure whether the event would take place this year, because the museum announced its bankruptcy the Monday after last year's weekend. Aviodrome closed its doors by the end of 2011. Luckily a company was found that took over the museum and its collection; leading to the reopening earlier this year. The reopened museum is more attractive for children, as well as the average person (not just the true aviation enthusiastic).

The museum entrance fee gives you access to both the FSweekend and the museum. So when you've seen enough virtual stuff, there are plenty of real aircraft to discover. The FlightGear team would appreciate it if you are able to travel to Lelystad!

Facebook users can join [http://www.facebook.com/events/315742308452348 the event's page] to stay up to date and connect to other visitors.

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

File:3d sign front.png

2012-06-23T11:34:28Z

Papillon81:

File:3d sign back.png

2012-06-23T11:34:26Z

Papillon81:

FlightGear Newsletter June 2012

2012-06-23T11:12:34Z

Papillon81: Signs: move to correct place

{{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 ==
=== 2.8.0 release preparations ===
{{Main article|Release plan}}
Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted.

Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released.

=== Rembrandt controls ===
[[File:Rembrandt dialog.png|thumb|left]]
A special [[Project Rembrandt|Rembrandt]] dialog has been created, to give the user full control over Rembrandt's rich feature set. The dialog can be reached via <tt>View > Rendering Options</tt>. By adjusting the various options, the framerate impact can be decreased.

=== Taxiway signs support improved ===
Flightgear does now better support the taxiway signs syntax of the apt.dat 850 spec.
Christian implemented the new specs and got rid of some old cruft along the way. The signs are also rendered now with a 3D case around and we support double sided signs as well!
James was able to reduce the amount of geodes used for the signs considerably.

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

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===

Please see [[Howto:Start core development]]

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

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

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

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

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice monthly). These snapshots 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 ==

Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google).

http://almien.co.uk/flightgear/map/multiplayer/

[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]

OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos.

Features available in this map include:
* Historical tracks ("breadcrumbs") showing movement of aircraft over time
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them

== FlightGear add-ons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===
==== Glaser-Dirks DG-101G ====
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.

=== Liveries ===

== Scenery corner ==
=== Airports ===
====London Gatwick in 850====
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.

[[File:Gatwick-850-version.png|640px]]

Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].

====Berlin-Tempelhof (EDDI/THF)====
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.

The Berlin Tempelhof airport was opened officially on 8 October 1923, but there was aviation activity in this area before. In 1909 the Wright brothers showed their flyer there. During the 1920's it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during the Second World War. Work on the modern building was started in 1936, but was not finished until the end of the war, when it became a U.S. military base. It became famous during the Berlin airlift of 1948-49. In the 1950's it was opened to civilian flights, and in 1993 it ceased to be a military base. The airport was closed on 30 October 2008.

Tempelhof airbase was not only an airport, but also a small independent town in the city of Berlin. It had its own power plant, waterworks, garbage incinerator, a railway siding, sporting facilities, barbecue area, and plant nursery. The aim is to have the airport area and the adjacent surroundings as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities have been modelled and send to the repository. The main building is in work. It's modeled partly based on original construction drawings and it is textured with photos of the real thing.

If you ever had the opportunity to arrive there by plane, you may remember the impressive experience of rolling with your plane under this mighty roof construction and walking away freely on the apron, even as a normal passenger. This gives a good impression of what aviation was like in former days.

Since you can't have this experience any longer in real life, maybe we will have it in FlightGear someday. But be patient: since it claims to be among the twenty largest buildings of the world, it will take some time to finish it.

Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].

[[File:EDDI3.jpg|640px]]
[[File:EDDI1.jpg|640px]]
[[File:EDDI2.jpg|640px]]

===Düsseldorf International (EDDL)===
[[Düsseldorf International Airport]] is Germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings. The scenery was generated with corine and openstreetmap.

[[File:EDDL-generic1.jpg|640px]]
[[File:EDDL-night.jpg|640px]]

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

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

== Wiki updates ==
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.

In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by clicking the Edit button at the top of the page.
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).

===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 ===
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt>

Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.

=== Virtual airlines ===
=== FlightGear events ===
==== FlightGear at the National Museum of Flight, Scotland ====
[[File:FlightGear demo at museum.jpg|thumb|FlightGear at the Museum of Flight, Scotland]]
Stuart Buchanan (stuart on the forum), ran a booth showing off FlightGear at the "Robots Live" event at the National Museum of Flight at East Fortune, Scotland, on Sunday 17th May. About 100 people tried landing an F-35C on a carrier, lots of flyers were handed out, and many compliments were received on the quality of the simulator. Demoing FG at an event at your local aviation museum is a great way to spread the word about FG. See our [[FlightGear Expo Checklist]] for guidance on how you can go about it.

==== FSweekend 2012 ====
With still several months to go, the FlightGear FSweekend team got the confirmation that [[FSweekend 2012]], the world's largest flight simulation event, will take place on '''3 and 4 November 2012''', at the usual location: Aviodrome museum ([[Lelystad Airport]], the Netherlands).

[[File:FSweekend banner 2012.jpg|left|270px]]
Until recently it was unsure whether the event would take place this year, because the museum announced its bankruptcy the Monday after last year's weekend. Aviodrome closed its doors by the end of 2011. Luckily a company was found that took over the museum and its collection; leading to the reopening earlier this year. The reopened museum is more attractive for children, as well as the average person (not just the true aviation enthusiastic).

The museum entrance fee gives you access to both the FSweekend and the museum. So when you've seen enough virtual stuff, there are plenty of real aircraft to discover. The FlightGear team would appreciate it if you are able to travel to Lelystad!

Facebook users can join [http://www.facebook.com/events/315742308452348 the event's page] to stay up to date and connect to other visitors.

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

FlightGear Newsletter June 2012

2012-06-23T11:10:24Z

Papillon81: /* Scenery corner */ WIP: signs improvements

{{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 ==
=== 2.8.0 release preparations ===
{{Main article|Release plan}}
Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted.

Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released.

=== Rembrandt controls ===
[[File:Rembrandt dialog.png|thumb|left]]
A special [[Project Rembrandt|Rembrandt]] dialog has been created, to give the user full control over Rembrandt's rich feature set. The dialog can be reached via <tt>View > Rendering Options</tt>. By adjusting the various options, the framerate impact can be decreased.

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

=== Forum digest ===

=== Git digest ===

=== Getting involved as a programmer ===

Please see [[Howto:Start core development]]

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

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

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

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

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice monthly). These snapshots 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 ==

Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google).

http://almien.co.uk/flightgear/map/multiplayer/

[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]

OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos.

Features available in this map include:
* Historical tracks ("breadcrumbs") showing movement of aircraft over time
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them

== FlightGear add-ons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===
==== Glaser-Dirks DG-101G ====
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.

=== Liveries ===

== Scenery corner ==
=== Taxiway signs support improved ===
Flightgear does now better support the taxiway signs syntax of the apt.dat 850 spec.
Christian implemented the new specs and got rid of some old cruft along the way. The signs are also rendered now with a 3D case around and we support double sided signs as well!
James was able to reduce the amount of geodes used for the signs considerably.
=== Airports ===
====London Gatwick in 850====
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.

[[File:Gatwick-850-version.png|640px]]

Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].

====Berlin-Tempelhof (EDDI/THF)====
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.

The Berlin Tempelhof airport was opened officially on 8 October 1923, but there was aviation activity in this area before. In 1909 the Wright brothers showed their flyer there. During the 1920's it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during the Second World War. Work on the modern building was started in 1936, but was not finished until the end of the war, when it became a U.S. military base. It became famous during the Berlin airlift of 1948-49. In the 1950's it was opened to civilian flights, and in 1993 it ceased to be a military base. The airport was closed on 30 October 2008.

Tempelhof airbase was not only an airport, but also a small independent town in the city of Berlin. It had its own power plant, waterworks, garbage incinerator, a railway siding, sporting facilities, barbecue area, and plant nursery. The aim is to have the airport area and the adjacent surroundings as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities have been modelled and send to the repository. The main building is in work. It's modeled partly based on original construction drawings and it is textured with photos of the real thing.

If you ever had the opportunity to arrive there by plane, you may remember the impressive experience of rolling with your plane under this mighty roof construction and walking away freely on the apron, even as a normal passenger. This gives a good impression of what aviation was like in former days.

Since you can't have this experience any longer in real life, maybe we will have it in FlightGear someday. But be patient: since it claims to be among the twenty largest buildings of the world, it will take some time to finish it.

Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].

[[File:EDDI3.jpg|640px]]
[[File:EDDI1.jpg|640px]]
[[File:EDDI2.jpg|640px]]

===Düsseldorf International (EDDL)===
[[Düsseldorf International Airport]] is Germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings. The scenery was generated with corine and openstreetmap.

[[File:EDDL-generic1.jpg|640px]]
[[File:EDDL-night.jpg|640px]]

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

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

== Wiki updates ==
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.

In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by clicking the Edit button at the top of the page.
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).

===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 ===
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt>

Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.

=== Virtual airlines ===
=== FlightGear events ===
==== FlightGear at the National Museum of Flight, Scotland ====
[[File:FlightGear demo at museum.jpg|thumb|FlightGear at the Museum of Flight, Scotland]]
Stuart Buchanan (stuart on the forum), ran a booth showing off FlightGear at the "Robots Live" event at the National Museum of Flight at East Fortune, Scotland, on Sunday 17th May. About 100 people tried landing an F-35C on a carrier, lots of flyers were handed out, and many compliments were received on the quality of the simulator. Demoing FG at an event at your local aviation museum is a great way to spread the word about FG. See our [[FlightGear Expo Checklist]] for guidance on how you can go about it.

==== FSweekend 2012 ====
With still several months to go, the FlightGear FSweekend team got the confirmation that [[FSweekend 2012]], the world's largest flight simulation event, will take place on '''3 and 4 November 2012''', at the usual location: Aviodrome museum ([[Lelystad Airport]], the Netherlands).

[[File:FSweekend banner 2012.jpg|left|270px]]
Until recently it was unsure whether the event would take place this year, because the museum announced its bankruptcy the Monday after last year's weekend. Aviodrome closed its doors by the end of 2011. Luckily a company was found that took over the museum and its collection; leading to the reopening earlier this year. The reopened museum is more attractive for children, as well as the average person (not just the true aviation enthusiastic).

The museum entrance fee gives you access to both the FSweekend and the museum. So when you've seen enough virtual stuff, there are plenty of real aircraft to discover. The FlightGear team would appreciate it if you are able to travel to Lelystad!

Facebook users can join [http://www.facebook.com/events/315742308452348 the event's page] to stay up to date and connect to other visitors.

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