FlightGear wiki - User contributions [en]

Switching default texture format to DDS

2014-10-02T02:39:51Z

OO ZVY: /* NVIDIA proprietary driver */

The FG development team is considering to '''switch the default format for textures from png to DDS'''. This would offer a number of significant advantages:

* DDS is a more compact format than png, hence the download size of the FG base package may be decreased
* Compressed DDS can be directly used by many graphics cards, reducing also GPU memory consumption
* DDS stores all texture resolution levels, in essence no lower resolution levels have to be generated when the texture is used, hence it loads much faster into memory
* The resolution levels ('mipmaps') can be customized, allowing for some interesting effects at no performance cost

Practically all commercial simulations use DDS for these reasons.

== Feedback needed - should FlightGear switch the defaults to DDS format for terrain texturing? ==
However, the DDS compression algorithm is patented, which means that it is not readily available for open source graphics drivers used by Linux distributions. Dependent on the specific hardware, this may or may not be a problem (modern graphics cards typically do not need the driver to process DDS, for older graphics cards there are non-patented workarounds available which decompress the DDS on the software level). The development team is concerned about making the FlightGear experience pleasant for all users, hence we would like to gather feedback how many users would be affected by a change in practice.

{{FGCquote
|let's collect some some feedback [on DDS usage in FlightGear] until late November and restart this topic. We probably know by then what we do for the next release. "Somebody" needs to collect the feedback, however.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32791750/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-03</nowiki>
}}
}}

If there are no problems reported, FG will change defaults to textures in DDS format with the 3.4 release, and then phase out the use of png textures.
In other words, a lack of feedback from end users might very well mean that future FlightGear versions may require DDS support and may not necessarily work for people with outdated hardware - so if you care about backward compatibility, please do get involved, test DDS support and provide feedback!

=== What we need you to do? ===
FlightGear already provides the simple option to test a DDS texture set. If you are running on Linux and use an open source graphics driver, please take 5 minutes to help during your next FG session:

# Open the dialog under View -> Rendering
# Under 'Terrain texture scheme', change the default 'Region-specific' to 'Global alternative (DDS format)'
# Press 'Okay' - FG will reload the terrain
# Do you see proper textures on the terrain (they may look different and may also not fit the location perfectly)? If yes, you're fine. If you see monochromatic, or even bright/pink, colors or other rendering artifacts, your system may have problems with DDS.
# Change back to the texture scheme you like best
# Enter your experiences in the list below

Thanks for your help!

== Tested hardware and graphics drivers ==
=== NVIDIA proprietary driver ===
{| class="wikitable sortable"
!Card
!Driver
!DDS ok
!Reported by
|-
|GeForce GTX 670M
|310.19
|{{yes}}
|ThorstenR
|-
|N13M-NS Optimus
|340.32
|{{yes}}
|Tom_ch
|-
|GeForce GT 640
|343.13
|{{yes}}
|lumni1968
|-
|GeForce GTX 780 Ti
|340.52
|{{yes}}
|Avionyx
|-
|GeForce GT 750M
|331.38
|{{yes}}
|Dutchguy
|-
|GeForce GT 620 OEM
|331.38
|{{yes}}
|C-GGKV
|-
|GeForce GTX 650
|331.20
|{{yes}}
|dany93
|-
|GeForce 210
|304.117
|{{yes}}
|Jean-Philippe
|-
|GeForce GT 520
|332.21
|{{yes}}
|cossack90
|-
|GeForce GTX 260
|304.117
|{{yes}}
|Lann
|-
|GeForce GTS 250
|331.38
|{{yes}}
|Madbyte
|-
|GeForce GTS 450
|340.32
|{{yes}}
|chris_blues
|-
|GeForce 8600 GT
|340.32
|{{yes}}
|szpajder
|-
|GeForce GTX 460 SE
|331.38
|{{yes}}
|f-jjth
|-
|GeForce GTX 560 Ti
|319.32
|{{yes}}
|PATTEN
|-
|GeForce 8600 GT
|331.38
|{{yes}}
|attila
|-
|GeForce GTX 750 ti
|340.32
|{{yes}}
|f-toro
|-
|GeForce GT 650M
|Apple OS 10.9.4
|{{No}}
|dersh
|-
|GeForce 9800GTX
|304.117
|{{yes}}
|ctec356
|-
|GeForce GT 220
|331.38
|{{yes}}
|D-ABEK
|-
|GeForce GTX 760M
|331.38
|{{yes}}
|f-ojac
|-
|GeForce GTX 560
|319.32
|{{yes}}
|[http://fr.flightgear.org/forums/viewtopic.php?pid=28721#p28721 Clm76]

|-
|Quadro FX 770M
|304.88
|{{yes}}
|OO ZVY
|}

=== NVIDIA open source driver (Nouveau)===
{| class="wikitable sortable"
!Card
!Driver
!DDS ok
!Reported by
|-
|GeForce GT 630
|
|{{no}}
|[https://plus.google.com/111978238381658236898/posts/VYSusMLRiH2 Jakub Klawiter]
|-
|GeForce GT 220
|
|{{no}}
|D-ABEK
|-
|GeForce GTX460
|
|{{no}}
|[[User:T3r]]
|-
|}

=== Intel proprietary driver ===

=== Intel open source driver ===
{| class="wikitable sortable"
!Card
!Driver
!libtxc_dxtn installed?
!DDS ok
!Reported by
|-
|HD Graphics 3000 (i7-2600K)
|10.2.6
|{{n/a}}
|{{yes}}
|cdesai
|-
|HD Graphics 3000 (i3-2330M)
|10.2.2
|{{n/a}}
|{{yes}}
|Flyhigh/saiarcot895
|-
|HD Graphics Sandy Bridge (Pentium B980)
|10.1.0
|{{no}}
|{{yes}}
|f-jjth
|-
|HD Graphics 4000 Ivy Bridge
|10.3.0
|{{no}}
|{{yes}}
|onox
|}

=== ATI/AMD proprietary driver ===
{| class="wikitable sortable"
!Card
!Driver
!DDS ok
!Reported by
|-
|ATI Radeon HD 6310
|14.6-1
|{{yes}}
|ZLSA
|-
|AMD Radeon R9 200 Series
|14.4
|{{yes}}
|Richi
|-
|Radeon HD 4850/4870
|legacy 8.97.100.7-4
|{{yes}}
|Jano
|}

=== ATI/AMD open source driver ===
{| class="wikitable sortable"
!Card
!Driver
!libtxc_dxtn installed?
!DDS ok
!Reported by
|-
|AMD Radeon HD 6570
|10.1.3
|{{yes}}
|{{yes}}
|fgjosh
|-
|-
|AMD Radeon HD 6770
|10.2.5
|{{no}}
|{{no}}
|Mongrol
|-
|AMD Radeon HD 7950
|10.2.1
|{{yes}}
|{{yes}}
|Saga
|-
|AMD Radeon R9 270X
|10.3~git20140805
|{{no}}
|{{no}}
|nine
|-
|AMD Radeon R9 270X
|10.3~git20140805
|{{yes}}
|{{yes}}
|nine
|}

== Sample test ==
=== DDS Test at the airport of Orio (Bergamo - Italy) ===
[[File:Terrain texture scheme DDS 01-2000.jpg|800px|thumb|Comparison of texture in relation to the three possible choices in "Rendering Options" -> "Terrain texture scheme"]]The final result, with all the "Shader Options" active, is not very satisfactory, I would say very poor. Apparently not check on any improvement in the speed of image loading. I think on modern machines with quad-core processors 16 GB, with latest graphics cards (NVIDIA 870) 6 GB, the loading of these images is not really a "bottleneck". I propose to insert the DDS functionality, but in a transparent way, ie convert "on the fly" the images before inserting them into the temporary memory, for example using the convert function of ImageMagick. However, I do not know if it really is a useful feature, I think there are many other things to do before this.<BR>These are the parameters used by the startup script "run_fgrun.sh":
{{Note|To reproduce this test, you can use the following [[Fgfsrc]] file - you should set up [[$FG_ROOT]] and [[$FG_SCENERY]] specifically for your own system though.}}
<code>
--airport=LIME
--aircraft=757-200-PW2040
--disable-random-objects
--enable-horizon-effect
--enable-enhanced-lighting
--enable-distance-attenuation
--enable-ai-models
--disable-ai-traffic
--disable-real-weather-fetch
--enable-clouds3d
--bpp=32
--texture-filtering=16
--prop:/sim/rendering/multi-sample-buffers=1
--prop:/sim/rendering/multi-samples=4
--timeofday=noon
--enable-terrasync
--httpd=5500
--props=5501
--jpg-httpd=5502
--multiplay=out,10,,0
--multiplay=in,10,,0
--disable-fgcom
</code>

== Excerpts from the ongoing discussion ==
{{FGCquote
|Here is my suggestion how to proceed:

* Let's do your 1) and 2) on as many information channels we have.
* Collect the responses on a public place, I'd suggest a wiki page
* Do this for a well defined time frame. Is three month too much/too short?
* If we have the impression, it's safe to switch to DDS, define the dds texture sets as default, keeping the png sets as a fallback and publish how to use this fallback
* Keep this for one release.
* Depending on the feedback we get, keep it that way or move entirely to DDS.

Does that sound reasonable for everybody?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32788459/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Misc ==
{{FGCquote
|I'd propose [...] this process:
# Get out the information first that one can change materials files, where to do it and what the characteristics of the different sets are.
# Ask users (especially those running with ATI or Intel on Linux) nicely to do a quick check whether dds works fine.

I think we have an information management problem in relation to the user base - a frequent forum situation is that a user requests something that's already there, but the information is just not out. So if we even envision such a change, I would start spreading the relevant information basically yesterday.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787957/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== DDS Debate in 2012 ==
=== Legalities ===
{{See also|Talk:Switching default texture format to DDS#Using patented algorithms}}

{{FGCquote
|These kind of precompressed images limits their usage to a specific set of <br/>
drivers. And no, due to the patent issues no open source code including ours <br/>
is allowed to implement compression/decompression code for these image <br/>
formats. Even if this is easy implementation wise.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28604650/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-29</nowiki>
}}
}}

{{FGCquote
|t is technically incorrect to provide these s3 patent <br/>
precompressed textures to a driver that does not announce the apropriate <br/>
extension and since we are not allowed to code something that deompresses <br/>
this, I think we should avoid using this compression for all the provided <br/>
models/textures.<br/>
<br/>
I think of a warning that is issued from the image loader in flightgear that <br/>
detects when these precompressed textures are seen. So even people using <br/>
drivers that just offer this extension have a chance to see that the provided <br/>
textures will not work for others.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28612879/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-01</nowiki>
}}
}}

=== Portability Concerns ===
{{FGCquote
|These kind of precompressed images limits their usage to a specific set of <br/>
drivers. And no, due to the patent issues no open source code including ours <br/>
is allowed to implement compression/decompression code for these image <br/>
formats. Even if this is easy implementation wise.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28604650/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-29</nowiki>
}}
}}

{{FGCquote
|And this is what I try to do now:<br/>
Object against using these patented compression algorithms.<br/>
I do not care for the on disk format of any image file we have. But the problem <br/>
is that some kind of precompression that can be stored in these dds files <br/>
cannot be used with other drivers than the closed ati and nvidia ones.<br/>
As long as these patented compression techiques are not used, every OpenGL <br/>
driver can use this and displays this fine.<br/>
<br/>
Think: Intel has the hugest marketshare in graphics today. If I remember <br/>
right, they sell more than ati and nvidia together (*). This kind of change in <br/>
effect rules out the majority of users as intel cannot work with these files.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28604650/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-29</nowiki>
}}
}}

{{FGCquote
|It's not limited to dds. If you use osgconv xxx.dds xxx.ivs you will probably <br/>
have the same effect. So I think simply ommitting DDS is ok?<br/>
<br/>
Also, much more important, the comment is not about 'your video driver'. It is <br/>
in your (Vivian) case even wrong. Your driver will display this fine.<br/>
So, in the end I do not care if it is 'your particular video driver' that does <br/>
not like this. You will just see this in the best case as the models look <br/>
wrong, and in the worst case fgfs just crashes the driver if these textures <br/>
are used.<br/>
What I really care about is that these files are expected not to work on a huge <br/>
amount of graphics boards out there. The point is to tell people doing <br/>
textures that they should omit compression so that this message disapears.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678235/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

{{FGCquote
|I would like to have a flightgear that is by default just running on every <br/>
average system. Having this run faster on a special configured system with some <br/>
better configuration options and hand tuned hardware and drivers is very fine.<br/>
But without tuning it must at least work in an acceptable way.<br/>
<br/>
I have checked in a change to flightgear to make the use of the compressed <br/>
internal formats a starttime configuration option.<br/>
I am still interrested if we have that hangs also with texture compression <br/>
disabled and without providing precompressed dds textures?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28602775/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-29</nowiki>
}}
}}

{{FGCquote
|this is the reason for the message. If your machine would refuse to display this you, <br/>
developing that, would probably just say 'nice try, but it does not work' <br/>
before you check in something. In the case it displays fine, you probably say <br/>
'it works here, so I assume it works also for others, lets do'.<br/>
And the message tells you, 'despite of just seeing this working on this <br/>
current machine, it does not work for others'.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678784/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

{{FGCquote
|Seriously, I think plenty people not being on this list today and probably <br/>
never will be in touch with anybody here, will run into this issue.<br/>
People here are those few guys from the power users that want to develop this <br/>
stuff.<br/>
<br/>
I am not going to discuss the patent stuff. Please search the mesa-dev archives <br/>
for the discussion and see there why they think that the nvidia tools and <br/>
other stuff out there cannot be used. Really - it is not that the code for that <br/>
is too dificult or unavailable. I am not a lawyer and I cannot change this <br/>
world - even if I would like to in this regard.<br/>
<br/>
I agree that techically for drivers/gpus supporting these compression formats <br/>
it would be best to use these precompressed files.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678784/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

{{FGCquote
|Seriously, I think plenty people not being on this list today and probably <br/>
never will be in touch with anybody here, will run into this issue.<br/>
People here are those few guys from the power users that want to develop this <br/>
stuff.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678784/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

{{FGCquote
|Your driver will display this fine.<br/>
So, in the end I do not care if it is 'your particular video driver' that does <br/>
not like this. You will just see this in the best case as the models look <br/>
wrong, and in the worst case fgfs just crashes the driver if these textures <br/>
are used.<br/>
What I really care about is that these files are expected not to work on a huge <br/>
amount of graphics boards out there. The point is to tell people doing <br/>
textures that they should omit compression so that this message disapears.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678235/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

=== Approaches ===
{{FGCquote
|Well, the default f16 does not work anymore for example.<br/>
I have also never tried the new textures, but I assume that these also contain <br/>
precompressed data? Also you claimed that the old texture files start to bitrot <br/>
comared to the new ones which makes me think that the new standard should be <br/>
the dds files. This together makes me think that the dds files should replace <br/>
the traditional image files.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28604650/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-29</nowiki>
}}
}}

{{FGCquote
|Hmm, regarding dds.<br/>
I have to say, that not all OpenGL drivers support texture compression, and <br/>
the models with dds files, are those that I cannot display, because of that.<br/>
And in fact this will not happen to the open source drivers before something <br/>
about 2020 because of patent issues.<br/>
<br/>
Sorry to step in this so late - probably way too late - but is there a reason <br/>
that the on disk format must be compressed?<br/>
The previous strategy to have on disk an format that everybody can read and to <br/>
make the driver compress them as needed/possible is better I think?<br/>
<br/>
So, for me the f16 lost its livery lately - where I can live with this for the <br/>
f16, I hope that this does not happen to flightgear as a whole ...
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28594472/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-27</nowiki>
}}
}}

{{FGCquote
|Well, I hope that we can get rid of the compression.<br/>
Can somebody with the apropriate tools convert the compressed textures to non <br/>
compressed ones? That could still be dds, but dds without these compressions <br/>
that produce the warning. So no problem with cubemaps in dds as long as the <br/>
compression is not there.<br/>
Then *everybody* is again able to use this stuff.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678109/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

{{FGCquote
|I can see several approaches:<br/>
<br/>
* Just do not use the patented compression stuff. The precomputed mipmaps could <br/>
probably do the job of avoiding the hangs (hopefully? to be checked?). May be <br/>
we could lower disk space usage by providing a dds.gz or similar wrapper?<br/>
<br/>
* If it's just the mipmaps. May be we can precompute the mipmaps using the cpu <br/>
in the database loader thread. This would help all textures not only the ones <br/>
that could be converted. May be this is the most generic solution.<br/>
<br/>
* Implement some kind of image lookup order that knows if the compressed files <br/>
could be handled or not. On loading an image in case of available compression <br/>
first try to find a dds file with the same name of the original one. That <br/>
involves some 'magic' which often leads to problems but that could at least <br/>
work.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28606576/
|title=<nowiki>[Flightgear-devel] DDS texures (Was: Improving random trees &
buildings)</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-30</nowiki>
}}
}}

{{FGCquote
|Next step is to make sure that compression is not required to avoid the hangs.<br/>
My favorite bet would be that then the new configure option regarding texture <br/>
compression needs to be set to none.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28606576/
|title=<nowiki>[Flightgear-devel] DDS texures (Was: Improving random trees &
buildings)</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-30</nowiki>
}}
}}

=== Precomputed mipmaps ===
{{FGCquote
|Could we do dds files without compression but with precomputed mipmaps?<br/>
<br/>
So at next, can you try out which combination of compression/provided <br/>
mipmaps/forced simgear compression still work fine?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28603114/
|title=<nowiki>Re: [Flightgear-devel] Improving random trees & buildings</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2011-12-29</nowiki>
}}
}}

{{FGCquote
|The 4. Method that I can imagine is to precompute the mipmaps in the loader.<br/>
IIRC tests with some of the guys suffering from this problem, providing <br/>
premipmapped but uncompressed dds files had helped to get a fluent viewer.<br/>
The argument against providing these dds files in general was that these files <br/>
are really huge because of not including any compression and having all the <br/>
mipmaps.<br/>
But that means we could at the point where the warning happens compute the <br/>
mipmap levels on the cpu in the loader thread. osg::gluScaleImage could be <br/>
used to do this I think (or something similar not requireing a context). This <br/>
one is an imported version of the original glu function that is included in <br/>
osg for running on an EGL stack which no longer provides GLU.<br/>
That is take the image scale this to the 1st mipmap, take the 1.st mipmap and <br/>
scale this to the 2. mipmap and so forth.<br/>
<br/>
This would have the advantage that the png's do not deviate from the dds files <br/>
over time.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/29571679/
|title=<nowiki>Re: [Flightgear-devel] DDS usage in effects files</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-07-21</nowiki>
}}
}}

{{FGCquote
|I think then, computing mipmaps for any texture file on the CPU in the loader <br/>
thread should globally improove the situation.<br/>
Also avoiding the compression already in the files should help every use case. <br/>
Except that the on disk memory consumption is higher.<br/>
Well and except that the database loader has more work to do on the CPU.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28612897/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-01</nowiki>
}}
}}

{{FGCquote
|Doing that differently will provide some overhead that could be kept at a <br/>
minimum I think:<br/>
For the disk usage, I think gzip compressing these will work sufficiently fine.<br/>
Ram usage of the images should not hurt too much. Sure the images are bigger <br/>
in memory. But fgfs is not just about images - far from that.<br/>
On the GPU, you can still use compression for the textures as the internal <br/>
format. This is what flightgear tries to do if the extension is supported <br/>
(checked by osg).<br/>
<br/>
The major point is that there are several ways that use slightly more <br/>
resources to get around this problem.<br/>
But once the patented compression is on disk, there is *no* way back for <br/>
people not having this feature.<br/>
<br/>
If you have better ideas that do not rule out intel and the oss drivers, you <br/>
are welcome!
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678784/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

{{FGCquote
|On unix I usually get the gzip plugin installed by osg (osgdb_gz.so). Is this <br/>
also the case for the default win32 case? Is there a osgdb_gz.dll or something <br/>
along the lines in the directory containing the plugins?<br/>
<br/>
If yes, we can already tackle the size problem of the uncompressed dds files on <br/>
disk by just gzip compressing these makging a xxx.dds.gz from a xxx.dds and <br/>
just refering to xxx.dds.gz instead of xxx.dds. At least this works fine here. <br/>
And I assume that this works fine for all unix like operating systems including <br/>
mac?!<br/>
James?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28678235/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees &</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-01-15</nowiki>
}}
}}

{{FGCquote
|What about solution 6 with (uncompressed premipmapped dds).gz?<br/>
On linux this should work as long as you have zlib installed which could be <br/>
regarded as a system library there.<br/>
Can we rely on zlib being compield into our osg distributions on win32? We do <br/>
need zlib in any case, it's mostly about teaching osg that it finds our zlib on <br/>
configure and build the gz plugin.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/29571819/
|title=<nowiki>Re: [Flightgear-devel] DDS usage in effects files</nowiki>
|author=<nowiki>Mathias Fröhlich</nowiki>
|date=<nowiki>2012-07-21</nowiki>
}}
}}

{{FGCquote
|I implemented a mipmap control and generation tool in effects when I last updated<br/>
the urban shader. For the moment, it relies on hardware when the average operator <br/>
is used for all texture channels but it could easily be modified to compute <br/>
all mipmap on the CPU. look the <mipmap-control> effect option and <br/>
mipmap.[ch]xx in SG material lib
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/28606692/
|title=<nowiki>Re: [Flightgear-devel] DDS texures (Was: Improving random trees
& buildings)</nowiki>
|author=<nowiki>Frederic Bouvier</nowiki>
|date=<nowiki>2011-12-30</nowiki>
}}
}}

== Implementation ==
{{FGCquote
|As has been previously pointed out, the current DDS texture set is not<br/>
simply the global png texture set converted.<br/>
<br/>
For our own sanity and those of the users, we need to ensure that there's<br/>
an apples-to-apples comparison being made when we change the default. I<br/>
therefore think we need to create a DDS version of the current default<br/>
texture set.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32797669/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Stuart Buchanan</nowiki>
|date=<nowiki>2014-09-04</nowiki>
}}
}}

{{FGCquote
|2) If we go down this path, we probably want to separate the underlying<br/>
texture format from the materials.xml definition entirely. For example, we<br/>
could simply remove the extention from the materials definition, and have<br/>
the C++ code append the appropriate extension based on a separate property.<br/>
This has a couple of advantages:<br/>
a) Makes testing easier and materials definitions less error-prone.<br/>
Assuming we have some batch job in place to generate dds textures, those<br/>
working on materials definitions could continue to work with png textures,<br/>
and only convert to dds as a final step (or indeed as part of the "make<br/>
release" jobs).<br/>
a) Avoids duplication of materials definitions. Having just spent quite a<br/>
bit of time making the materials definitions more efficient, I'd like to<br/>
avoid making it worse again!<br/>
<br/>
I'm quite happy to do the C++ coding required for this in the materials<br/>
loader - it's probably pretty straightforward.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32797669/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Stuart Buchanan</nowiki>
|date=<nowiki>2014-09-04</nowiki>
}}
}}

{{FGCquote
|That does leave the issue of what happens to the existing dds texture<br/>
definitions where there are special mipmap layers. I'd suggest that we<br/>
have some Clever Script (tm) that is able to work out whether the DDS or<br/>
PNG version of a texture is the master, and then generate the other version<br/>
from it. I admit that the PNG conversion of the DDS will lose some<br/>
information in this process, but it would allow those without DDS support<br/>
to at least use the textures.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32797669/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Stuart Buchanan</nowiki>
|date=<nowiki>2014-09-04</nowiki>
}}
}}

{{FGCquote
|3) We need a sensible process for dealing with aircraft, which has been<br/>
identified as a significant issue. Again, I think more aircraft developers<br/>
find .png easier to deal with, and there are a lot of aircraft out there<br/>
that would need conversion. It feels like we need some build scripts to<br/>
"compile" aircraft to use DDS textures.<br/>
<br/>
A more far-fetched idea might be to have a cache of dds textures that are<br/>
generated on-the-fly, or when aircraft are loaded by the aircraft center.<br/>
Clearly that impacts initial load time the first time a new aircraft is<br/>
loaded, and would increase the size of .fgfs/ directories massively, but it<br/>
would remove the need for any work by aircraft/scenery developers and could<br/>
be made optional.<br/>

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32797669/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Stuart Buchanan</nowiki>
|date=<nowiki>2014-09-04</nowiki>
}}
}}

== Challenges ==
{{FGCquote
|"dds on an open source driver (radeon and intel) I was forced to use radeon at some time, and it was fun, the planes were pink :) once libtxc-dxtn installed, dds were loaded fine again, so it can be used on open source if you are ok to use the lib."<br/>
<br/>
Unless there's some way to make sure Linux users have that lib installed automatically, I'd say that's a no. We can't have a random user guess what additional packages to install. And maybe someone can educate me - googling the lib, this appears to be working for mesa - which usually is what we try to avoid if users do 3d rendering via mesa for performance reasons?<br/>
<br/>
Also, what does 'If you are okay to use the lib' mean precisely? If that's some piece of code which circumvents a patented thing and isn't exactly legal and needs to be obtained from special servers outside the normal repo (sort of like the DVD decryption under Linux), then I doubt that's an option. Can anyone clarify?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32786414/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Another potential option would be to convert regions to .dds but keep <br/>
both global-png and global-dds, but making that user-friendly would <br/>
require a way to automatically detect lack of .dds support.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787117/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|On my system (Intel Ivybridge), DDS works with or without libtxc, but <br/>
this may not be true of all Intel hardware.<br/>

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787117/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|You can specify the dependency on libtxc_dxtn, but then distributions like <br/>
openSUSE cannot ship FlightGear anymore. libtxc_dxtn implements S3 texture <br/>
compression which is patented in many parts of the world. Linux distributions <br/>
therefore cannot ship it. You can easily find it in add-on repositories, but <br/>
as I said, distributions would not be able to include FlightGear creating a <br/>
huge hurdle to installation for users.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787143/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Stefan Seifert</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Debian/Ubuntu's libtxc is libtxc-dxtn-s2tc, which claims to avoid the <br/>
patent at a small cost in visual quality: <br/>
https://github.com/divVerent/s2tc/wiki/libtxc_dxtn<br/>
That site also states that modern hardware doesn't need this software <br/>
fallback anyway (and hence won't hit either this quality loss or the <br/>
slowness of any software decoder), but doesn't define "modern hardware".
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787296/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|The dds textures seem to have some advantages over our png textures and <br/>
using them is tempting.<br/>
But the points from Thorsten R. are good points and if there is any <br/>
chance to have a step-wise transition to the new format, I'd prefer that <br/>
path.<br/>
<br/>
Don't we have an alternate dds texture set already in fgdata that is <br/>
enabled with an option? What about making this the default, keeping the <br/>
png texture set as an alternate. That would get us reports from users <br/>
unable to run dds textures and provide an easy fallback method.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787378/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|We currently have regions-png, global-png and global-dds; as I noted <br/>
earlier, switching to regions-dds, global-png and global-dds has the <br/>
issue that while changing the texture set is easy (dropdown in View > <br/>
Rendering Options), knowing that one needs to do so may not be.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787717/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Can we invert the logic in, say, preferences.xml so xxx-dds is enabled <br/>
by default and switching to xxx-png has to be done in rendering options?<br/>
<br/>
Torsten
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787787/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|Changing the default (which is in preferences.xml) is easy: the problem <br/>
is how do users with non-.dds-supporting hardware (if this exists) know <br/>
they need to change back.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787851/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Rebecca Palmer</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Conversion ==
Also see [[DDS texture conversion]].

{{FGCquote
|the script take the .dds and not convert the png again if both exist(I remember having manually used "compare" to check if both the dds and the png looks the same, and if not i changed some names)<br/>
<br/>
notice that the normal maps are a particular case as you need to tell the effect the texture is dds with a line like:<br/>
<br/>
1<br/>
<br/>
<br/>
just be sure to include this in the normal map effects with png and it will be easier:<br/>
<br/>
0<br/>
<br/>
<br/>
about FG doing the dds conversion , nvcompress is told to be gpl compatible, but i'm not an expert here:<br/>
<br/>
http://nvidia-texture-tools.googlecode.com/svn/trunk/NVIDIA_Texture_Tools_README.txt<br/>

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32799214/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>jean pellotier</nowiki>
|date=<nowiki>2014-09-05</nowiki>
}}
}}

{{FGCquote
|I think this is an inheritance from some other game engine using a different convention, and therefore from the authoring tools that were developed for such an engine (photoshop exporter plugins and the like). If indeed the FGFS DDS textures are only meant to be used in FGFS then this should be fixed at the conversion time. Otherwise, if we want other applications to easily reuse the FGFS textures then it would be better to stick to the most common convention. But I think we all agree that the source for any DDS texture should be kept, which pretty much precludes importing ready made DDS textures from 3rd party sources. Incidentally I think importing DDS artwork from other sources should be discouraged, since it will most likely run afoul of the licensing terms of the original copyright owner.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32799324/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>TDO Brandano</nowiki>
|date=<nowiki>2014-09-05</nowiki>
}}
}}

Nothing as exotic. Just a different "origin" between OpenGL and Direct3D image conventions. OpenGL image origin is located in the lower-left corner, while Direct3D (hence DDS too) considers the top-left as the origin, resulting in a DDS image to appear vertically flipped when read in an OpenGL context. This has repercussions in the way normal-map decoded normals appear (hence the flag in the effects, which signals to the shader to flip the decoded normals). The rest is simply a matter of workflow: either use flipped coordinates and skewed/reversed conventions throughout your whole workflow, or just flip the image and (eventually) set a flag for the shader at "publish" time (said flag could be automatically set by the code on DDS texture load). ''(the latter seems more pragmatic/appealing)''

{{FGCquote
|Automatic conversion script is welcome indeed. Also I'm pretty sure that we have some people here ready to convert a PNG to DDS as soon as you say "Hey boys I created a new PNG file, can you convert this file for me please ?" :-)
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785592/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|A few world about the conversion: once a png/rgb/jpg found, the script <br/>
try to guess the suitable dds format: with or without alpha channel, <br/>
bumpmap, if a .dds is allready found we just erase the png one, if not <br/>
we use nvcompress to get the dds. After we change the textures name <br/>
called in the differents files and that's it. There's a way to tell the <br/>
script what to do for each file, if the automatic mode is a failure.<br/>
<br/>
I guess speaking theorically is not the best to make an opinion, so if <br/>
some of you are interested to make a test, I will make a 3.2 minimal dds <br/>
fgdata this we, once on my FG pc.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785602/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>jean</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Pros ==
{{FGCquote
|I always got a loading problem with png textures, large textures take <br/>
seconds to load and convert, and that ruin my close flight where you <br/>
can't afford to take pause in the air.<br/>
that's why i did a batch script to convert to dds ALL the textures in <br/>
the data, not only the matérial set, but everything. Now i only flight a <br/>
dds version of flightgear, and am quite happy with it, that's why i <br/>
propose to provide a dds fgdata for test, and maybe to make it an <br/>
alternate download possibility.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32785602/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>jean</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

== Cons ==
{{FGCquote
|FG actually runs with dds textures, it just doesn't render anything reasonable, I believe you get monochromatic colors. But I don't expect the menu to be affected, it doesn't use textures.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787957/
|title=<nowiki>Re: [Flightgear-devel] .dds textures (was Unused and/or sourceless textures‏)</nowiki>
|author=<nowiki>Renk Thorsten</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

{{FGCquote
|If it's relevant, I recall having S2TC compression problems when running Flightgear, and updating this package to a newer version manually (outside of the main repos) fixed the issue. I'm on an Intel HD 3000, but I'm guessing that Intel HD 4000 doesn't have this problem, since it seems to have better OpenGL and OpenCL support.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32787875/
|title=<nowiki>Re: [Flightgear-devel] Download size,
and hardware support (was .dds textures)</nowiki>
|author=<nowiki>Saikrishna Arcot</nowiki>
|date=<nowiki>2014-09-02</nowiki>
}}
}}

[[Category:Core development projects]]

FlightGear Newsletter May 2012

2012-05-29T11:57:40Z

OO ZVY: /* YASIM */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

== YASIM ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :http://dl.dropbox.com/u/18438878/propellersource.zip

video of engine feathering and unfeathering on the Pond racer.http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-29T11:54:44Z

OO ZVY: /* New software tools and projects */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

== YASIM ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-29T11:52:57Z

OO ZVY: /* New software tools and projects */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

== YASIM ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-29T11:50:18Z

OO ZVY: /* FlightGear addons and mods */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

[[File:Exemple.jpg]]== FlightGear addons and mods ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-29T11:49:54Z

OO ZVY: /* FlightGear addons and mods */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

[[File:Exemple.jpg]]== FlightGear addons and mods ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-29T11:49:12Z

OO ZVY: /* FlightGear addons and mods */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

[[File:Exemple.jpg]]== FlightGear addons and mods ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-29T11:48:30Z

OO ZVY: /* FlightGear addons and mods */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

[[File:Exemple.jpg]]== FlightGear addons and mods ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|left]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

FlightGear Newsletter May 2012

2012-05-29T11:46:30Z

OO ZVY: /* FlightGear addons and mods */

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

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

== Development news ==

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

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

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

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

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

== Interview with a contributor (Jon Berndt) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter!''

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

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

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

== Nasal for newbies ==

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

[[File:Exemple.jpg]]== FlightGear addons and mods ==

YASIM aircraft ( engine feather )[[File:Pondfeather.png|thumb|]]

With a tiny modification of the propeller.ccp file, it is possible to feather engines on Yasim aircrafts.

Download beta version of the modification via this link for testing :[[propeller ccp and hpp|http://dl.dropbox.com/u/18438878/propellersource.zip]]

video of engine feathering and unfeathering on the Pond racer.[[Yasim feather demo|http://www.youtube.com/watch?v=1NVQJJ36yCg&feature=youtu.be]]

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

=== New aircraft ===

=== Updated aircraft ===

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

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

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

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

== Screenshot of the month ==

== Suggested flights ==
===Origin of the Amazon River===
[[Image:SPRF-001.png|thumb|left|high altitude]]
[[Image:SPRF-002.png|thumb|right|high altitude]]
Peru. For this [[IFR]] tour (with [[VFR]] parts) we take off from the highest airfield in the world to discover the origin of the [http://en.wikipedia.org/wiki/Amazon_River Amazon river] in South America. I promise spectacular mountains and valleys. The total length of this trip is about 175 NM.

Place your aircraft on the airfield SPRF, San Rafael. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

Equipment preparation: Set [[NAV1]] to [http://en.wikipedia.org/wiki/Arequipa Arequipa] VOR-DME at 113.7 with a radial of 176° (magnetic). Set [[NAV2]] to [http://en.wikipedia.org/wiki/Cusco Cusco] VOR-DME at 114.9 also with a radial of 176°.
Set [[QNH]] and during flight keep correcting it, it's a bad idea to use [[Pressure altitude]] during this flight. Set the [[heading bug]] to 250°. Arm the [[autopilot]] and set the initial [[altitude]] to 16,000 feet.

The airfield SPRF, San Rafael has an [[elevation]] of 14,422 feet. That altitude will cause problems during take-off. It takes a lot longer for the aircraft to gain sufficient speed for take-off, also the take-off speed that is needed is higher as you would expect. Perhaps an additional notch of flaps is needed.

Take-off, avoid the bumps (there are plenty) and fly a course of 250°. After about 80 NM you will fly over the radial of NAV1. Intercept the radial towards Arequipa. At a distance of 75 NM towards NAV1 you will have to increase altitude to 19,000 feet.

At a distance of 50 NM towards NAV1 and 118 NM from NAV2 you will see and cross over the mountain [http://en.wikipedia.org/wiki/Nevado_Mismi Nevado Mismi] with an altitude of 18,362 ft. The rains and water on the area to the right until Nevado Mismi will leave towards the Atlantic ocean through the Amazon river. Anything to the left and after Nevado Mismi will leave towards the Pacific ocean.

After Nevado Mismi you are tempted to descend. Don't. Just before the airfield is [http://en.wikipedia.org/wiki/Chachani Mt.Chachani] with an altitude of 19,872 feet and to the East is the active volcano [http://en.wikipedia.org/wiki/El_Misti El Misti] with an altitude of 19,101 feet. You can either increase the altitude and fly over the airfield or keep the altitude, even descend and fly between the mountains, your choice depends on the visibility.

Fly using the heading bug and set NAV1 to [[ILS]] 109.7 with a radial of 93.2°. We will land at airfield [http://en.wikipedia.org/wiki/Rodr%C3%ADguez_Ball%C3%B3n_International_Airport SPQU, Rodriguez ballon], that has an elevation of 8,405 feet. There is a reason this airfield has just one ILS. The area South-West of the airfield is below 11,405 feet and is safe to navigate.

Position the aircraft in front of the runway at an altitude of 11,405 feet, catch the [[glidescope]] at a distance of 9.5 NM and land your aircraft. After landing and parking your aircraft crawl into the tower to look around.

Happy flying!

For more amazing flights see [[Suggested Flights]].

====Airports and coordinates====
[[Image:SPQU-001.png|thumb|left|pre - landing]]
[[Image:World-SPRF.png|thumb|right|Latitude: -14.267 Longitude: -70.467]]
* [[SPRF|SPRF - San Rafael]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPRF.pdf chart]
* [[SPQU|SPQU - Rodriguez Ballon]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SPQU.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w020s80.tar.gz
<div style="clear:both;"></div>

====Suggested aircraft====
[[Image:SPQU-002.png|thumb|right|landed]]
I recomend a powerful jet angine airplane, but not too heavy !
* [[Cessna 550 Citation II]]

<div style="clear:both;"></div>

====FlightGear launching====
fgfs --airport=SPRF --aircraft=Citation-II
<div style="clear:both;"></div>

== Aircraft reviews ==

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

== Community news ==
=== FlightGear on YouTube ===
In this video you can see a cockpit landing with an A330-200 at Tenerife North (GCXO).
{{#ev:youtube|MHwbw04bKjI|400|Landing at Tenerife North with an A330-200 }}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 05]]

File:Pondfeather.png

2012-05-29T11:44:25Z

OO ZVY:

=={{int:filedesc}}==
{{Information
|description={{fr|1=mise en drapeau sur avion YASIM}}
|date=2012-05-29
|source={{own}}
|author=[[User:OO ZVY|OO ZVY]]
|permission=
|other_versions=
|other_fields=
}}

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

FlightGear videos

2012-04-06T11:55:57Z

OO ZVY: /* Aircraft */

Feel free to add your (own) videos.

'''A collection of all [[FlightGear]] related videos on YouTube can be seen at [http://www.youtube.com/view_play_list?p=3B31CCD15245D0AA this location].'''

== Addons ==
* [http://nl.youtube.com/watch?v=fyjHLV-SGhg FlightGear AirRace Narita addon]

== Aircraft ==

=== [[Airbus A380]] ===
* [http://www.youtube.com/watch?v=7yLZVddbXVo Landing at EHAM]

=== [[Boeing 737-300]] ===
* [http://www.youtube.com/watch?v=Pl9NFvPZuLU&feature=PlayList&p=3B31CCD15245D0AA&index=11 SBGR-SBGL Flight]
* [http://www.youtube.com/watch?v=d2wwkeGrvD4 New Boeing 737-300 testflight]
=== [[Boeing 747-400]] ===
* [http://nl.youtube.com/watch?v=mb8VdBh-IE4&feature=channel Landing at TNCM]
* [http://www.youtube.com/watch?v=VogfMnI0j3s A flight from TNCM to EHAM]

=== [[British Aerospace Harrier]] (VSTOL) ===
* [http://www.youtube.com/watch?v=IrmCFIBymcc Hovering KSFO]
* [http://www.youtube.com/watch?v=zg_Pbcfhx98 Vertical Take-Off and Landing (VSTOL)]

=== [[Douglas DC-3-C47]] (Touch and go) ===
* [http://www.youtube.com/watch?v=88wNoWTuk18 LFLG Touch and go]

=== [[F5E Tiger II]] ===
* [http://www.youtube.com/watch?v=lYhVJEw7Ae8 Prestes F5E Tiger II Original Model]
* [http://www.youtube.com/watch?v=E1PeLQL840s Prestes F5E Tiger II Update]
* [http://www.youtube.com/watch?v=lS4joH8ETz0 F5E Tiger II Sonic Boom Fly-by with shock wave effect]

=== [[Fairchild A-10|Fairchild A-10 Thunderbolt II]] ===
* [http://www.youtube.com/watch?v=SCViR6oOQ6A Bombing Run]

=== [[Grumman A-6E]] ===
* [http://www.youtube.com/watch?v=4BoN4u4anrU Carrier Landing]

=== [[Grumman G-21 Goose]] ===
* [http://www.youtube.com/watch?v=BBGsRGovWhQ Flying Buckaroo's Goose]

=== [[Piper J3 Cub]] ===
* [http://www.youtube.com/watch?v=Pg3Bvx2ZnFw&context=C333bf3aADOEgsToPDskL92iCIKUc_3GCmByBwAV71 Landing at TNCM]

=== [[Zlin 50 lx]] ===
* [http://www.youtube.com/watch?v=nD4yMaszdQk Zlin basic aerobatic program]

== Helicopters ==
* [http://www.youtube.com/watch?v=j7aHqDkCzCw Who needs a helipad? (Eurocopter BO105)]
* [http://www.youtube.com/watch?v=AM-JfdNzmlM Eurocopter EC135]
* [http://www.youtube.com/watch?v=e_oy111Wm9I Boeing CH-47 Chinook]
* [http://www.youtube.com/watch?v=Rw13yLgunz0 Flying SCVM (New cockpit EC BO-105)]

== Development ==
* [http://nl.youtube.com/watch?v=xkkIMdqAuC0 FlightGear new trees]
* [http://www.youtube.com/watch?v=k4oMOFnD6bw New clouds]
* [http://www.youtube.com/watch?v=EKELqBGVsqw Dynamic water effect]
* [http://www.youtube.com/watch?v=PYwlfZSHJpo Early morning red sky effect]
* [http://www.youtube.com/watch?v=GPtd6Np3u8Q Urban effect]
== Simulators ==
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15935.html A FlightGear-driven Flight & Navigation Procedures Trainer (FNPT)]
* [http://nl.youtube.com/watch?v=Y1-siAMojSM FlightGear Virtual Cockpit build]

== UAV related ==
* http://baron.flightgear.org/~curt/tmp/20080710.AVI

== Tutorials ==
Please see the separate [[Video Tutorials]] page.

__NOTOC__

[[Category:List]]

FlightGear videos

2012-04-06T11:52:36Z

OO ZVY: /* Aircraft */

Feel free to add your (own) videos.

'''A collection of all [[FlightGear]] related videos on YouTube can be seen at [http://www.youtube.com/view_play_list?p=3B31CCD15245D0AA this location].'''

== Addons ==
* [http://nl.youtube.com/watch?v=fyjHLV-SGhg FlightGear AirRace Narita addon]

== Aircraft ==

=== [[Airbus A380]] ===
* [http://www.youtube.com/watch?v=7yLZVddbXVo Landing at EHAM]

=== [[Boeing 737-300]] ===
* [http://www.youtube.com/watch?v=Pl9NFvPZuLU&feature=PlayList&p=3B31CCD15245D0AA&index=11 SBGR-SBGL Flight]
* [http://www.youtube.com/watch?v=d2wwkeGrvD4 New Boeing 737-300 testflight]
=== [[Boeing 747-400]] ===
* [http://nl.youtube.com/watch?v=mb8VdBh-IE4&feature=channel Landing at TNCM]
* [http://www.youtube.com/watch?v=VogfMnI0j3s A flight from TNCM to EHAM]

=== [[British Aerospace Harrier]] (VSTOL) ===
* [http://www.youtube.com/watch?v=IrmCFIBymcc Hovering KSFO]
* [http://www.youtube.com/watch?v=zg_Pbcfhx98 Vertical Take-Off and Landing (VSTOL)]

=== [[DC 3]] (Touch and go) ===
* [http://www.youtube.com/watch?v=88wNoWTuk18 LFLG Touch and go]

=== [[F5E Tiger II]] ===
* [http://www.youtube.com/watch?v=lYhVJEw7Ae8 Prestes F5E Tiger II Original Model]
* [http://www.youtube.com/watch?v=E1PeLQL840s Prestes F5E Tiger II Update]
* [http://www.youtube.com/watch?v=lS4joH8ETz0 F5E Tiger II Sonic Boom Fly-by with shock wave effect]

=== [[Fairchild A-10|Fairchild A-10 Thunderbolt II]] ===
* [http://www.youtube.com/watch?v=SCViR6oOQ6A Bombing Run]

=== [[Grumman A-6E]] ===
* [http://www.youtube.com/watch?v=4BoN4u4anrU Carrier Landing]

=== [[Grumman G-21 Goose]] ===
* [http://www.youtube.com/watch?v=BBGsRGovWhQ Flying Buckaroo's Goose]

=== [[Piper J3 Cub]] ===
* [http://www.youtube.com/watch?v=Pg3Bvx2ZnFw&context=C333bf3aADOEgsToPDskL92iCIKUc_3GCmByBwAV71 Landing at TNCM]

=== [[Zlin 50 lx]] ===
* [http://www.youtube.com/watch?v=nD4yMaszdQk Zlin basic aerobatic program]

== Helicopters ==
* [http://www.youtube.com/watch?v=j7aHqDkCzCw Who needs a helipad? (Eurocopter BO105)]
* [http://www.youtube.com/watch?v=AM-JfdNzmlM Eurocopter EC135]
* [http://www.youtube.com/watch?v=e_oy111Wm9I Boeing CH-47 Chinook]
* [http://www.youtube.com/watch?v=Rw13yLgunz0 Flying SCVM (New cockpit EC BO-105)]

== Development ==
* [http://nl.youtube.com/watch?v=xkkIMdqAuC0 FlightGear new trees]
* [http://www.youtube.com/watch?v=k4oMOFnD6bw New clouds]
* [http://www.youtube.com/watch?v=EKELqBGVsqw Dynamic water effect]
* [http://www.youtube.com/watch?v=PYwlfZSHJpo Early morning red sky effect]
* [http://www.youtube.com/watch?v=GPtd6Np3u8Q Urban effect]
== Simulators ==
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15935.html A FlightGear-driven Flight & Navigation Procedures Trainer (FNPT)]
* [http://nl.youtube.com/watch?v=Y1-siAMojSM FlightGear Virtual Cockpit build]

== UAV related ==
* http://baron.flightgear.org/~curt/tmp/20080710.AVI

== Tutorials ==
Please see the separate [[Video Tutorials]] page.

__NOTOC__

[[Category:List]]

FlightGear videos

2012-04-06T11:52:17Z

OO ZVY: /* Aircraft */

Feel free to add your (own) videos.

'''A collection of all [[FlightGear]] related videos on YouTube can be seen at [http://www.youtube.com/view_play_list?p=3B31CCD15245D0AA this location].'''

== Addons ==
* [http://nl.youtube.com/watch?v=fyjHLV-SGhg FlightGear AirRace Narita addon]

== Aircraft ==

=== [[Airbus A380]] ===
* [http://www.youtube.com/watch?v=7yLZVddbXVo Landing at EHAM]

=== [[Boeing 737-300]] ===
* [http://www.youtube.com/watch?v=Pl9NFvPZuLU&feature=PlayList&p=3B31CCD15245D0AA&index=11 SBGR-SBGL Flight]
* [http://www.youtube.com/watch?v=d2wwkeGrvD4 New Boeing 737-300 testflight]
=== [[Boeing 747-400]] ===
* [http://nl.youtube.com/watch?v=mb8VdBh-IE4&feature=channel Landing at TNCM]
* [http://www.youtube.com/watch?v=VogfMnI0j3s A flight from TNCM to EHAM]

=== [[British Aerospace Harrier]] (VSTOL) ===
* [http://www.youtube.com/watch?v=IrmCFIBymcc Hovering KSFO]
* [http://www.youtube.com/watch?v=zg_Pbcfhx98 Vertical Take-Off and Landing (VSTOL)]

=== [[DC 3]] (Touch and go) ===
* [http://www.youtube.com/watch?v=88wNoWTuk18 LFLG Touch and go]

=== [[F5E Tiger II]] ===
* [http://www.youtube.com/watch?v=lYhVJEw7Ae8 Prestes F5E Tiger II Original Model]
* [http://www.youtube.com/watch?v=E1PeLQL840s Prestes F5E Tiger II Update]
* [http://www.youtube.com/watch?v=lS4joH8ETz0 F5E Tiger II Sonic Boom Fly-by with shock wave effect]

=== [[Fairchild A-10|Fairchild A-10 Thunderbolt II]] ===
* [http://www.youtube.com/watch?v=SCViR6oOQ6A Bombing Run]

=== [[Grumman A-6E]] ===
* [http://www.youtube.com/watch?v=4BoN4u4anrU Carrier Landing]

=== [[Grumman G-21 Goose]] ===
* [http://www.youtube.com/watch?v=BBGsRGovWhQ Flying Buckaroo's Goose]

=== [[Piper J3 Cub]] ===
* [http://www.youtube.com/watch?v=Pg3Bvx2ZnFw&context=C333bf3aADOEgsToPDskL92iCIKUc_3GCmByBwAV71 Landing at TNCM]

=== [[Zlin 50 lx]] ===
* [http://www.youtube.com/watch?v=nD4yMaszdQk Zlin basic aerobatic program]

== Helicopters ==
* [http://www.youtube.com/watch?v=j7aHqDkCzCw Who needs a helipad? (Eurocopter BO105)]
* [http://www.youtube.com/watch?v=AM-JfdNzmlM Eurocopter EC135]
* [http://www.youtube.com/watch?v=e_oy111Wm9I Boeing CH-47 Chinook]
* [http://www.youtube.com/watch?v=Rw13yLgunz0 Flying SCVM (New cockpit EC BO-105)]

== Development ==
* [http://nl.youtube.com/watch?v=xkkIMdqAuC0 FlightGear new trees]
* [http://www.youtube.com/watch?v=k4oMOFnD6bw New clouds]
* [http://www.youtube.com/watch?v=EKELqBGVsqw Dynamic water effect]
* [http://www.youtube.com/watch?v=PYwlfZSHJpo Early morning red sky effect]
* [http://www.youtube.com/watch?v=GPtd6Np3u8Q Urban effect]
== Simulators ==
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15935.html A FlightGear-driven Flight & Navigation Procedures Trainer (FNPT)]
* [http://nl.youtube.com/watch?v=Y1-siAMojSM FlightGear Virtual Cockpit build]

== UAV related ==
* http://baron.flightgear.org/~curt/tmp/20080710.AVI

== Tutorials ==
Please see the separate [[Video Tutorials]] page.

__NOTOC__

[[Category:List]]

Lancair 235

2012-01-29T18:55:11Z

OO ZVY:

{{infobox Aircraft
|name = Lancair 235
|image = Lancair 235.png
|alt =
|type = Civilian Aircraft
|livery =
|authors = Emmanuel Baranger & PAF Team
|status-fdm = 3
|status-systems = 2
|status-cockpit = 4
|status-model = 4
|fdm = YASIM
|fgname = lancair235
|status = Development
|download = http://clemaez.fr/flightgear/PAF/Lancair-235.tar.gz
|development = http://http://equipe-flightgear.forumactif.com/t794p150-lancair-235
}}

<center> </center>

<center>[[File:Lancaircock.png|300px]] [[File:Lancairvol.png|300px]]</center>

<center>[[File:Lancairphare.png|300px]] [[File:Lancairsmoke.png|300px]]</center>

== Features ==

=== Autopilot KAP 140 ===
Fully operational

=== GPS ===
Garmin 196 -optional- and
ZKV 500

=== KNS80 ===
Fully operational -> HSI

=== Options ===
Smoke generator on both wing tips.

=== Divers ===
VOR 2 and ADF receiver -> RMI
=== Speeds & limits ===

''Speeds in KIAS (Knots indicated airspeed) : airspeed indicated''
* Vso (Vitesse de décrochage en configuration d'atterrissage) : TBN
* VS1 ( ) : TBN
* VMC (Vitesse minimale de contrôle) : TBN
* V1/V2 ( vitesse de décision/sécurité) : TBN
* VR (Vitesse de rotation) : TBN
* VX (vitesse d'angle de montée optimale) : TBN
* VXse (VX avec un seul moteur) : TBN
* VY (Vitesse de taux de montée optimale) : TBN
* VLO (vitesse maxi en manoevre train sorti):TBN
* VA (vitesse maximale en manœuvre) : TBN
* VNO (Vitesse maximale en croisière) : TBN
* VNE (Vitesse à ne jamais dépasser) : TBN
* VLE (Vitesse maximale train sorti) : TBN
* VF (Vitesse maximale avec 1/2 volets) : TBN
* VF (Vitesse maximale volets sorti) : TBN

=== Links ===

{{Lancair 235}}

[[fr:Lancair 235]]
[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]
[[Category:Single Engine Piston]]

Lancair 235

2012-01-29T18:54:10Z

OO ZVY:

{{infobox Aircraft
|name = Lancair 235
|image = Lancair 235.png
|alt =
|type = Civilian Aircraft
|livery =
|authors = Emmanuel Baranger & PAF Team
|status-fdm = 3
|status-systems = 2
|status-cockpit = 4
|status-model = 4
|fdm = YASIM
|fgname = lancair235
|status = Development
|download = http://clemaez.fr/flightgear/PAF/Lancair-235.tar.gz
|development = http://http://equipe-flightgear.forumactif.com/t794p150-lancair-235
}}

<center> </center>

<center>[[File:Lancaircock.png|300px]] [[File:Lancairvol.png|300px]]</center>

<center>[[File:Lancairphare.png|300px]] [[File:Lancairsmoke.png|300px]]</center>

== Features ==

=== Autopilot KAP 140 ===
Fully operational

=== GPS ===
Garmin 196 -optional- and
ZKV 500

=== KNS80 ===
Fully operational -> HSI

=== Options ===
Smoke generator on both wing tips.

=== Divers ===
VOR 2 and ADF receiver -> RMI
=== Speeds & limits ===

''Speeds in KIAS (Knots indicated airspeed) : airspeed indicated''
* Vso (Vitesse de décrochage en configuration d'atterrissage) : TBN
* VS1 ( ) : TBN
* VMC (Vitesse minimale de contrôle) : TBN
* V1/V2 ( vitesse de décision/sécurité) : TBN
* VR (Vitesse de rotation) : TBN
* VX (vitesse d'angle de montée optimale) : TBN
* VXse (VX avec un seul moteur) : TBN
* VY (Vitesse de taux de montée optimale) : TBN
* VLO (vitesse maxi en manoevre train sorti):TBN
* VA (vitesse maximale en manœuvre) : TBN
* VNO (Vitesse maximale en croisière) : TBN
* VNE (Vitesse à ne jamais dépasser) : TBN
* VLE (Vitesse maximale train sorti) : TBN
* VF (Vitesse maximale avec 1/2 volets) : TBN
* VF (Vitesse maximale volets sorti) : TBN

=== Links ===

{{Lancair 235}}

[[fr:Lancair 235]]

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]
[[Category:Single Engine Piston]]

Lancair 235

2012-01-29T18:52:01Z

OO ZVY:

{{infobox Aircraft
|name = Lancair 235
|image = Lancair 235.png
|alt =
|type = Civilian Aircraft
|livery =
|authors = Emmanuel Baranger & PAF Team
|status-fdm = 3
|status-systems = 2
|status-cockpit = 4
|status-model = 4
|fdm = YASIM
|fgname = lancair235
|download = http://clemaez.fr/flightgear/PAF/Lancair-235.tar.gz
|development = http://http://equipe-flightgear.forumactif.com/t794p150-lancair-235
}}

<center> </center>

<center>[[File:Lancaircock.png|300px]] [[File:Lancairvol.png|300px]]</center>

<center>[[File:Lancairphare.png|300px]] [[File:Lancairsmoke.png|300px]]</center>

== Features ==

=== Autopilot KAP 140 ===
Fully operational

=== GPS ===
Garmin 196 -optional- and
ZKV 500

=== KNS80 ===
Fully operational -> HSI

=== Options ===
Smoke generator on both wing tips.

=== Divers ===
VOR 2 and ADF receiver -> RMI
=== Speeds & limits ===

''Speeds in KIAS (Knots indicated airspeed) : airspeed indicated''
* Vso (Vitesse de décrochage en configuration d'atterrissage) : TBN
* VS1 ( ) : TBN
* VMC (Vitesse minimale de contrôle) : TBN
* V1/V2 ( vitesse de décision/sécurité) : TBN
* VR (Vitesse de rotation) : TBN
* VX (vitesse d'angle de montée optimale) : TBN
* VXse (VX avec un seul moteur) : TBN
* VY (Vitesse de taux de montée optimale) : TBN
* VLO (vitesse maxi en manoevre train sorti):TBN
* VA (vitesse maximale en manœuvre) : TBN
* VNO (Vitesse maximale en croisière) : TBN
* VNE (Vitesse à ne jamais dépasser) : TBN
* VLE (Vitesse maximale train sorti) : TBN
* VF (Vitesse maximale avec 1/2 volets) : TBN
* VF (Vitesse maximale volets sorti) : TBN

=== Links ===

{{Lancair 235}}

[[fr:Lancair 235]]

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]
[[Category:Single Engine Piston]]

Lancair 235

2012-01-29T18:51:24Z

OO ZVY:

{{infobox Aircraft
|name = Lancair 235
|image = Lancair 235.png
|alt =
|type = Civilian Aircraft
|livery =
|authors = Emmanuel Baranger & PAF Team
|status-fdm = 3
|status-systems = 2
|status-cockpit = 4
|status-model = 4
|fdm = YASIM
|fgname = lancair235
|download = http://clemaez.fr/flightgear/PAF/Lancair-235.tar.gz
|development = http://http://equipe-flightgear.forumactif.com/t794p150-lancair-235
}}

<center> </center>

<center>[[File:Lancaircock.png|300px]] [[File:Lancairvol.png|300px]]</center>

<center>[[File:Lancairphare.png|300px]] [[File:Lancairsmoke.png|300px]]</center>

== Features ==

=== Autopilot KAP 140 ===
Fully operational

=== GPS ===
Garmin 196 -optional- and
ZKV 500

=== KNS80 ===
Fully operational -> HSI

=== Options ===
Smoke generator on both wing tips.

=== Divers ===
VOR 2 and ADF receiver -> RMI
=== Speeds & limits ===

''Speeds in KIAS (Knots indicated airspeed) : airspeed indicated''
* Vso (Vitesse de décrochage en configuration d'atterrissage) : TBN
* VS1 ( ) : TBN
* VMC (Vitesse minimale de contrôle) : TBN
* V1/V2 ( vitesse de décision/sécurité) : TBN
* VR (Vitesse de rotation) : TBN
* VX (vitesse d'angle de montée optimale) : TBN
* VXse (VX avec un seul moteur) : TBN
* VY (Vitesse de taux de montée optimale) : TBN
* VLO (vitesse maxi en manoevre train sorti):TBN
* VA (vitesse maximale en manœuvre) : TBN
* VNO (Vitesse maximale en croisière) : TBN
* VNE (Vitesse à ne jamais dépasser) : TBN
* VLE (Vitesse maximale train sorti) : TBN
* VF (Vitesse maximale avec 1/2 volets) : TBN
* VF (Vitesse maximale volets sorti) : TBN

=== Links ===

{{Lancair 235}}

[[fr:Lancair 235]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]
[[Category:Single Engine Piston]]

Lancair 235

2012-01-29T18:46:27Z

OO ZVY: Created page with "{{infobox Aircraft |name = Lancair 235 |image = Lancair 235.png |alt = |type = Civilian Aircraft |livery = |authors = Emmanuel Baranger & PAF Team |status-fdm =..."

{{infobox Aircraft
|name = Lancair 235
|image = Lancair 235.png
|alt =
|type = Civilian Aircraft
|livery =
|authors = Emmanuel Baranger & PAF Team
|status-fdm = 3
|status-systems = 2
|status-cockpit = 4
|status-model = 4
|fdm = YASIM
|fgname = lancair235
|download = http://clemaez.fr/flightgear/PAF/Lancair-235.tar.gz
|development = http://http://equipe-flightgear.forumactif.com/t794p150-lancair-235
}}

<center> </center>

<center>[[File:Lancaircock.png|300px]] [[File:Lancairvol.png|300px]]</center>

<center>[[File:Lancairphare.png|300px]] [[File:Lancairsmoke.png|300px]]</center>

== Features ==

=== Autopilot KAP 140 ===
Fully operational

=== GPS ===
Garmin 196 -optional- and
ZKV 500

=== KNS80 ===
Fully operational -> HSI

=== Options ===
Smoke generator on both wing tips.

=== Divers ===
VOR 2 and ADF receiver -> RMI
=== Speeds & limits ===

''Speeds in KIAS (Knots indicated airspeed) : airspeed indicated''
* Vso (Vitesse de décrochage en configuration d'atterrissage) : TBN
* VS1 ( ) : TBN
* VMC (Vitesse minimale de contrôle) : TBN
* V1/V2 ( vitesse de décision/sécurité) : TBN
* VR (Vitesse de rotation) : TBN
* VX (vitesse d'angle de montée optimale) : TBN
* VXse (VX avec un seul moteur) : TBN
* VY (Vitesse de taux de montée optimale) : TBN
* VLO (vitesse maxi en manoevre train sorti):TBN
* VA (vitesse maximale en manœuvre) : TBN
* VNO (Vitesse maximale en croisière) : TBN
* VNE (Vitesse à ne jamais dépasser) : TBN
* VLE (Vitesse maximale train sorti) : TBN
* VF (Vitesse maximale avec 1/2 volets) : TBN
* VF (Vitesse maximale volets sorti) : TBN

=== Links ===

{{Lancair 235}}

[[fr:Lancair 235]]

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]
[[Category:Single Engine Piston]]

File:Lancairsmoke.png

2012-01-29T18:38:07Z

OO ZVY: Lancair 235 smoke

Lancair 235 smoke

File:Lancairphare.png

2012-01-29T18:35:56Z

OO ZVY: Lancair 235 landing light

Lancair 235 landing light

File:Lancairvol.png

2012-01-29T18:33:57Z

OO ZVY: Lancair 235 en vol

Lancair 235 en vol

File:Lancaircock.png

2012-01-29T18:32:43Z

OO ZVY: Cockpit Lancair 235

Cockpit Lancair 235

File:Lancair 235.png

2012-01-29T18:27:13Z

OO ZVY: Lancair 235

Lancair 235

Bugatti 100P

2012-01-28T08:38:10Z

OO ZVY:

{{infobox Aircraft
|image =bugatti100p.jpg
|name = Bugatti 100P
|type =
|livery = blue
|fdm =YASim
|status = Development
|authors = Emmanuel Baranger (3D/FDM), Pierre Geoffroy (FDM)
|fgname = bugatti, bugatti-yasim
|download =http://flightgear.org/Downloads/aircraft/#Bugatti
}}
Tragically the '''Bugatti 100P''' [[aircraft|airplane]] never flew, the Germans invaded Paris before it was 100% ready. The airplane surprisingly survived the war, and still exists. The airplane is now in the [[EAA AirVenture Museum|EAA museum]] in Oshkosh, USA. Both engines exist, and were built into Bugatti race-cars.

<center> wing flaps in high speed configuration </center>
<center>[[File:bugatti100p.png|400px]] [[File:bugatti100pspeed.png|400px]] </center>

[http://www.youngeagles.org/wallpaper/bugatti_wallpaper1600.jpg 1600 by 1200 wallpaper with the Bugatti] (from [http://www.youngeagles.org/wallpaper/ here])

'''Some of the airplane´s characteristics:'''
* Extremely streamlined design, made possible by placing the two engines behind the cockpit.
* Forward swept wings
* A sandwich-construction in wood, where balsa wood between two layers of hard wood makes a very light, very strong ans stiff construction.
* Propulsion by two counter-rotating propellers, driven from the two engines by axles under the pilot´s elbow.
* The airplane was equipped with ground adjustable propellers. Propellers with in-flight adjustable pitch were being developed
* The engines were special developments of racecar engines, 8 cylinder 4.9 litre with compressor and many magnesium parts, approx. 450hp.
* Automatic wing-flaps, that changed the wingprofile for extra lift or less drag. Adjustment automatic according to airspeed, throttle etc.
* This system was also capable of acting as an airbrake, or be used during dives. The same system also automatically lowered and raised the retractable landing gear.
* Special cooling system with radiators in the fuselage, air entering at the leading edge of the stabilisers. The air flowed through the fuselage to the front, exiting at the trailing edge of the wing.
* "Y" tail.

=== Related content ===
* [[Table of models]]

== External links ==
[[File:Helijah_Hangar_logo.png|top|link=http://helijah.free.fr]]
* [http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar]
* [http://www.bugattiaircraft.com/plane.htm Bugatti Aircraft Association]
[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Racer]]

File:Bugatti100pspeed.png

2012-01-28T08:34:52Z

OO ZVY: bugatti 100p ( high speed configuration )

bugatti 100p ( high speed configuration )

File:Bugatti100p.png

2012-01-28T08:30:27Z

OO ZVY: Bugatti 100P

Bugatti 100P

Douglas C-47 Skytrain

2012-01-28T08:03:54Z

OO ZVY:

{{infobox Aircraft
|name = Douglas DC-3 C-47
|image = Dc-3-splash.png
|alt =
|type = Civilian / Military Aircraft
|livery =
|authors = Emmanuel Baranger & PAF Team
|status-fdm = 4
|status-systems = 4
|status-cockpit = 4
|status-model = 4
|fdm = YASIM
|fgname = dc-3<br />dc-3-copilot<br />dc-3-psg1<br />dc-3-psg2<br />dc-3-psg3<br />dc-3-psg4
|download = http://clemaez.fr/flightgear/PAF/Douglas-Dc3.tar.gz
|development = http://equipe-flightgear.forumactif.com/t756-douglas-dc-3-c-47-part-2-2
}}

The '''Douglas DC3 C-47''' is the military version of the famous DC3 transport aircraft. Shortly before the Allied invasion, the factories of the Douglas Aircraft Company produced two of them, every hour. At the end of World War II, over 10,000 C-47 rolled from the factory.

<center>[[File:Dc3c47-01.png|300px]] [[File:Dc3c47-02.png|300px]] [[File:Dc3c47-03.jpg||300px]]</center>

<center>[[File:DC3Swissairlines.png|300px]] [[File:DC3engineout.png|300px]]</center>
== Features ==

=== Dual Control ===
With the DC-3, dual control is highly developed. It allows to many users to connect to one aircraft in same time.
There is one place for copilot (--aircraft=dc-3-copilot) which allows to control <u>entirely</u> the DC-3. All switches and controls are available for the copilot.
Then there is 4 places for passenger (--aircraft=dc-3-psg1, --aircraft=dc-3-psg2, --aircraft=dc-3-psg3, --aircraft=dc-3-psg4) which doesn't allows control of the DC-3. You are just onboard et fly with him.

=== Hydraulic system ===
[[File:dc3c47-hydraulic.png|160px|right|thumb|Le groupe hydraulique]]

Hydraulic system of the DC-3 is very complete. He has been create as closely respecting the constructor documentation. The hydraulic system is used for these equipments :
* Brakes
* Landing gears
* Cowl-Flaps
* Flaps
* Wipers

In order to use one of these equipment, you need to have at least one engine running in order to have an hydraulic pressure.

=== Fuel system ===
Le DC-3 est équipé de 2 réservoirs principaux et 2 réservoirs auxiliaires. Comme dans la réalité, les 2 réservoirs auxiliaires ne sont pas reliés aux réservoirs principaux. Donc si vous n'avez plus de carburant dans les réservoirs principaux il vous faudra passer sur les réservoirs auxiliaires à l'aide des sélecteurs de réservoirs situé sur le piédestal.
Vous pouvez observer la quantité de carburant restant dans chacun des réservoirs à l'aide de la jauge à carburant et de son sélecteur situé côté copilote.

=== Electric system ===
The electric system simule the charge and discharge of battery. When engines are running, batteries are charging. More you use electric equipment, more batteries are discharging.

=== Paratroopers ===
Le DC-3 a été longtemps utilisé pour le largage de parachutistes, il était donc important qu'ils soient présent.
Pour larguer les parachutistes il faut ouvrir la porte cargo (Ctrl + D), puis engager le switch "Parachute signal" situé sur l'overhead côté pilote.

=== Options ===
[[File:Dc3c47-options.png|300px|right|thumb|Le menu du DC-3 C47]]

The DC-3 has a menu of options to customize it to your liking. To make it appear click on "Douglas DC3/C47" menu, then "Options."
Options are :
*Show Yokes = Show/hide Yokes
*Show Pilot = Show/hide pilot
*Show Copilot = Show/hide copilot
*Details High = Show/hide 3D details (rideaux, engines, lights, extincteurs...)
*Glass reflection = Show/hide reflect shader of windshield
*Landing light cone = Switch between light cone and plane light about landing light
*Autostart = Setup DC-3 to start engines. Click on "Autostart" then press key "s" in order to start engines
*Select version = Choose interior themes
*Immatriculation = Set aircraft immatriculation

=== Divers ===
* Many animation
* 3D Cabine
* Tutorials
* Real sound of DC-3
* More than 25 liveries

== Aircraft help ==
=== Startup ===
# Turn Master Battery ON (situated on the left of the overhead)
# Set selectors tanks on their respective main tank (rotate switch situated on the pedestal)
# Engage Boost Pump left and right (situated on the right of the overhead)
# Set magneto at "both" (situated at the middle of the overhead)
# Engage left starter switch then right starter switch (situated on the right of the overhead)
# Desengage break parking (Shift + b)

You are ready to align yourself on the runway

=== Take-off ===

# Go to the runway threshold
# Make sure the flaps are retracted
# Set Cowl-Flaps valves on "Trail" (to the right of copilot)
# Release the parking brake (Shift + b)
# Align yourself with the track -''Make sure you're aligned face to the wind!''-. You can unlock the tail wheel by flipping the lever at the bottom of the pedestal from right to left ( l )
# Lock the tail wheel by flipping the lever at the bottom of the pedestal from left to right ( l )
# Set the mixture on "Auto Rich"
# Increase to maximum the propeller pitch
# Set full throttle
# Tirez légèrement le manche afin que la queue de l'appareil reste au sol quelques secondes afin de le diriger dans les premiers mètres d'accélération
# During taking speed you will be very focused to correct the path of the DC-3.
# Arrived at 55/60 kts release the handle, the tail will rise.
# Maintenant que la queue est levée soyez extrêmement concentré sur la trajectoire à suivre et corrigez la moindre petite déviation. Utilisez le palonnier pour cela, et si besoin le frein gauche ou droit. - ''Cette étape est très délicate mais avec un peu d’entraînement c'est réalisable'' -
# Continue to take speed to 70 kts and then gently pull on the handle.
# You begin to leave the ground, begin immediately to increase the trim to facilitate your ascension

=== Climb ===

=== Croisière ===

=== Landing ===

=== Speeds & limits ===

''Speeds in KIAS (Knots indicated airspeed) : airspeed indicated''

* Vso (Vitesse de décrochage en configuration d'atterrissage) : 64 KIAS
* VS1 ( ) : 68 KIAS
* VMC (Vitesse minimale de contrôle) : 76 KIAS
* V1/V2 ( vitesse de décision/sécurité) : 84 KIAS
* VR (Vitesse de rotation) : 84 KIAS
* VX (vitesse d'angle de montée optimale) : 84 KIAS
* VXse (VX avec un seul moteur) : 84 KIAS
* VY (Vitesse de taux de montée optimale) : 91 KIAS
* VYse (VY avec un seul moteur) : 95 KIAS
* VLO (vitesse maxi en manoevre train sorti):84 KIAS
* VA (vitesse maximale en manœuvre) : 120 KIAS
* VNO (Vitesse maximale en croisière) : 158 KIAS
* VNE (Vitesse à ne jamais dépasser) : 190 KIAS
* VLE (Vitesse maximale train sorti) : 148 KIAS
* VF (Vitesse maximale avec 1/4 volets) : 135 KIAS
* VF (Vitesse maximale avec 1/2 volets) : 99 KIAS
* VF (Vitesse maximale volets sorti) : 97 KIAS

=== Links ===
* http://www.thedc-3network.com/download.htm

{{Douglas}}

[[fr:Douglas DC-3-C47]]

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]
[[Category:Twin Engine Piston]]

File:DC3engineout.png

2012-01-28T07:57:36Z

OO ZVY: DC3 engine failure

DC3 engine failure

File:DC3Swissairlines.png

2012-01-28T07:54:12Z

OO ZVY: DC3 mont blanc

DC3 mont blanc

FlightGear Newsletter December 2011

2011-12-24T12:43:52Z

OO ZVY: /* Screenshot of the month */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

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

=== Feature freeze for the 2.6.0 release ===
(placeholder) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34864.html and http://flightgear.org/forums/viewtopic.php?f=11&t=14627

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

http://imageshack.us/photo/my-images/571/fgfsscreen011.jpg/

http://imageshack.us/f/859/fgfsscreen013.jpg/

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

http://imageshack.us/photo/my-images/189/fgfsscreen024.jpg/

http://imageshack.us/photo/my-images/703/fgfsscreen025.jpg/

http://imageshack.us/photo/my-images/6/fgfsscreen026.jpg/

http://imageshack.us/photo/my-images/18/fgfsscreen027.jpg/

http://imageshack.us/f/525/fgfsscreen020.jpg/

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

=== New terrain textures ===
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository.
More info and screenshots in this forum [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread]. This is still work in progress, of course.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''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?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== CASA C-101 Aviojet ====
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===
====Learjet 35-A====
The [[Learjet 35-A]] has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it and take your favorite plane. There are some really nice areas just perfect for long VFR routes!<br>
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]<br><br>

Download! (none yet)

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html the mailinglist].

=== EBAW (Antwerpen - Deurne) ===

Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)

This scenery, is sadly enough, not yet available with terrasync. You can download it from the [https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery Belgian scenery git repo].

[[File:Ebaw_textured_01.jpg|200px]][[File:Ebaw_textured_02.jpg|200px]][[File:Ebaw_textured_03.jpg|200px]]

Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit and the request is done!

The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
[[File:LOWI december.jpg|600 px]]

Merry X-mas!

== Screenshot of the month ==

P.A.F. ( LFLG home base ) wish you a Merry X-mas!
[[File:LFLG Lancair Chrismas.png|1200 px]]

Merry X-mas!

PAF link : http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===Updated articles===
*[[Learjet 35-A]] is updated matching the true Aircraft flight manual (with FlightGear limitations). On the Wiki it is one of the best described aircraft.
*[[Unique Features]] now contains a massive list of what makes [[FlightGear]] unique.
*[[De/Flughöhe]] is close to complete matching the English version.
===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 Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|2eGOdBsd8Os|400|F-4E formation training at TFFG}} (Also see [[Toward real close formation flight]])

=== New tutorials and screencasts ===
=== Forum news ===
The headers on [http://flightgear.org/forums the forum] have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2011 12]]

FlightGear Newsletter December 2011

2011-12-24T12:43:37Z

OO ZVY: /* Screenshot of the month */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

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

=== Feature freeze for the 2.6.0 release ===
(placeholder) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34864.html and http://flightgear.org/forums/viewtopic.php?f=11&t=14627

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

http://imageshack.us/photo/my-images/571/fgfsscreen011.jpg/

http://imageshack.us/f/859/fgfsscreen013.jpg/

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

http://imageshack.us/photo/my-images/189/fgfsscreen024.jpg/

http://imageshack.us/photo/my-images/703/fgfsscreen025.jpg/

http://imageshack.us/photo/my-images/6/fgfsscreen026.jpg/

http://imageshack.us/photo/my-images/18/fgfsscreen027.jpg/

http://imageshack.us/f/525/fgfsscreen020.jpg/

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

=== New terrain textures ===
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository.
More info and screenshots in this forum [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread]. This is still work in progress, of course.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''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?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== CASA C-101 Aviojet ====
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===
====Learjet 35-A====
The [[Learjet 35-A]] has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it and take your favorite plane. There are some really nice areas just perfect for long VFR routes!<br>
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]<br><br>

Download! (none yet)

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html the mailinglist].

=== EBAW (Antwerpen - Deurne) ===

Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)

This scenery, is sadly enough, not yet available with terrasync. You can download it from the [https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery Belgian scenery git repo].

[[File:Ebaw_textured_01.jpg|200px]][[File:Ebaw_textured_02.jpg|200px]][[File:Ebaw_textured_03.jpg|200px]]

Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit and the request is done!

The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
[[File:LOWI december.jpg|600 px]]

Merry X-mas!

== Screenshot of the month ==

P.A.F. ( LFLG home base ) wish you a Merry X-mas!

[[File:LFLG Lancair Chrismas.png|1200 px]]

Merry X-mas!
PAF link : http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===Updated articles===
*[[Learjet 35-A]] is updated matching the true Aircraft flight manual (with FlightGear limitations). On the Wiki it is one of the best described aircraft.
*[[Unique Features]] now contains a massive list of what makes [[FlightGear]] unique.
*[[De/Flughöhe]] is close to complete matching the English version.
===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 Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|2eGOdBsd8Os|400|F-4E formation training at TFFG}} (Also see [[Toward real close formation flight]])

=== New tutorials and screencasts ===
=== Forum news ===
The headers on [http://flightgear.org/forums the forum] have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2011 12]]

FlightGear Newsletter December 2011

2011-12-24T12:39:33Z

OO ZVY: /* Screenshot of the month */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

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

=== Feature freeze for the 2.6.0 release ===
(placeholder) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34864.html and http://flightgear.org/forums/viewtopic.php?f=11&t=14627

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

http://imageshack.us/photo/my-images/571/fgfsscreen011.jpg/

http://imageshack.us/f/859/fgfsscreen013.jpg/

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

http://imageshack.us/photo/my-images/189/fgfsscreen024.jpg/

http://imageshack.us/photo/my-images/703/fgfsscreen025.jpg/

http://imageshack.us/photo/my-images/6/fgfsscreen026.jpg/

http://imageshack.us/photo/my-images/18/fgfsscreen027.jpg/

http://imageshack.us/f/525/fgfsscreen020.jpg/

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

=== New terrain textures ===
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository.
More info and screenshots in this forum [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread]. This is still work in progress, of course.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''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?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== CASA C-101 Aviojet ====
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===
====Learjet 35-A====
The [[Learjet 35-A]] has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it and take your favorite plane. There are some really nice areas just perfect for long VFR routes!<br>
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]<br><br>

Download! (none yet)

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html the mailinglist].

=== EBAW (Antwerpen - Deurne) ===

Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)

This scenery, is sadly enough, not yet available with terrasync. You can download it from the [https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery Belgian scenery git repo].

[[File:Ebaw_textured_01.jpg|200px]][[File:Ebaw_textured_02.jpg|200px]][[File:Ebaw_textured_03.jpg|200px]]

Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit and the request is done!

The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
[[File:LOWI december.jpg|600 px]]

Merry X-mas!

== Screenshot of the month ==

P.A.F. ( LFLG home base ) wish you a Merry X-mas!

[[File:LFLG Lancair Chrismas.png|1200 px]]

Merry X-mas!

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===Updated articles===
*[[Learjet 35-A]] is updated matching the true Aircraft flight manual (with FlightGear limitations). On the Wiki it is one of the best described aircraft.
*[[Unique Features]] now contains a massive list of what makes [[FlightGear]] unique.
*[[De/Flughöhe]] is close to complete matching the English version.
===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 Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|2eGOdBsd8Os|400|F-4E formation training at TFFG}} (Also see [[Toward real close formation flight]])

=== New tutorials and screencasts ===
=== Forum news ===
The headers on [http://flightgear.org/forums the forum] have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2011 12]]

FlightGear Newsletter December 2011

2011-12-24T12:37:41Z

OO ZVY: /* Screenshot of the month */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

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

=== Feature freeze for the 2.6.0 release ===
(placeholder) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34864.html and http://flightgear.org/forums/viewtopic.php?f=11&t=14627

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

http://imageshack.us/photo/my-images/571/fgfsscreen011.jpg/

http://imageshack.us/f/859/fgfsscreen013.jpg/

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

http://imageshack.us/photo/my-images/189/fgfsscreen024.jpg/

http://imageshack.us/photo/my-images/703/fgfsscreen025.jpg/

http://imageshack.us/photo/my-images/6/fgfsscreen026.jpg/

http://imageshack.us/photo/my-images/18/fgfsscreen027.jpg/

http://imageshack.us/f/525/fgfsscreen020.jpg/

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

=== New terrain textures ===
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository.
More info and screenshots in this forum [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread]. This is still work in progress, of course.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''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?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== CASA C-101 Aviojet ====
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===
====Learjet 35-A====
The [[Learjet 35-A]] has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it and take your favorite plane. There are some really nice areas just perfect for long VFR routes!<br>
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]<br><br>

Download! (none yet)

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html the mailinglist].

=== EBAW (Antwerpen - Deurne) ===

Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)

This scenery, is sadly enough, not yet available with terrasync. You can download it from the [https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery Belgian scenery git repo].

[[File:Ebaw_textured_01.jpg|200px]][[File:Ebaw_textured_02.jpg|200px]][[File:Ebaw_textured_03.jpg|200px]]

Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit and the request is done!

The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
[[File:LOWI december.jpg|600 px]]

Merry X-mas!

== Screenshot of the month ==

[[File:LFLG Lancair Chrismas.png|1200 px]]

Merry X-mas!

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===Updated articles===
*[[Learjet 35-A]] is updated matching the true Aircraft flight manual (with FlightGear limitations). On the Wiki it is one of the best described aircraft.
*[[Unique Features]] now contains a massive list of what makes [[FlightGear]] unique.
*[[De/Flughöhe]] is close to complete matching the English version.
===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 Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|2eGOdBsd8Os|400|F-4E formation training at TFFG}} (Also see [[Toward real close formation flight]])

=== New tutorials and screencasts ===
=== Forum news ===
The headers on [http://flightgear.org/forums the forum] have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2011 12]]

File:LFLG Lancair Chrismas.png

2011-12-24T12:33:12Z

OO ZVY: uploaded a new version of "File:LFLG Lancair Chrismas.png": Christmas Banner towing above LFLG with Lancair 235

Chrimas Banner towing above LFLG with Lancair 235

File:LFLG Lancair Chrismas.png

2011-12-24T12:32:16Z

OO ZVY: Chrimas Banner towing above LFLG with Lancair 235

Chrimas Banner towing above LFLG with Lancair 235

FlightGear videos

2011-12-20T10:24:46Z

OO ZVY: /* Aircraft */

Feel free to add your (own) videos.

'''A collection of all [[FlightGear]] related videos on YouTube can be seen at [http://www.youtube.com/view_play_list?p=3B31CCD15245D0AA this location].'''

== Addons ==
* [http://nl.youtube.com/watch?v=fyjHLV-SGhg FlightGear AirRace Narita addon]

== Aircraft ==

=== [[Airbus A380]] ===
* [http://www.youtube.com/watch?v=7yLZVddbXVo Landing at EHAM]

=== [[Boeing 737-300]] ===
* [http://www.youtube.com/watch?v=Pl9NFvPZuLU&feature=PlayList&p=3B31CCD15245D0AA&index=11 SBGR-SBGL Flight]
* [http://www.youtube.com/watch?v=d2wwkeGrvD4 New Boeing 737-300 testflight]
=== [[Boeing 747-400]] ===
* [http://nl.youtube.com/watch?v=mb8VdBh-IE4&feature=channel Landing at TNCM]
* [http://www.youtube.com/watch?v=VogfMnI0j3s A flight from TNCM to EHAM]

=== [[British Aerospace Harrier]] (VSTOL) ===
* [http://www.youtube.com/watch?v=IrmCFIBymcc Hovering KSFO]
* [http://www.youtube.com/watch?v=zg_Pbcfhx98 Vertical Take-Off and Landing (VSTOL)]

=== [[F5E Tiger II]] ===
* [http://www.youtube.com/watch?v=lYhVJEw7Ae8 Prestes F5E Tiger II Original Model]
* [http://www.youtube.com/watch?v=E1PeLQL840s Prestes F5E Tiger II Update]
* [http://www.youtube.com/watch?v=lS4joH8ETz0 F5E Tiger II Sonic Boom Fly-by with shock wave effect]

=== [[Fairchild A-10|Fairchild A-10 Thunderbolt II]] ===
* [http://www.youtube.com/watch?v=SCViR6oOQ6A Bombing Run]

=== [[Grumman A-6E]] ===
* [http://www.youtube.com/watch?v=4BoN4u4anrU Carrier Landing]

=== [[Grumman G-21 Goose]] ===
* [http://www.youtube.com/watch?v=BBGsRGovWhQ Flying Buckaroo's Goose]

=== [[Zlin 50 lx]] ===
* [http://www.youtube.com/watch?v=nD4yMaszdQk Zlin basic aerobatic program]

== Helicopters ==
* [http://www.youtube.com/watch?v=j7aHqDkCzCw Who needs a helipad? (Eurocopter BO105)]
* [http://www.youtube.com/watch?v=AM-JfdNzmlM Eurocopter EC135]
* [http://www.youtube.com/watch?v=e_oy111Wm9I Boeing CH-47 Chinook]
* [http://www.youtube.com/watch?v=Rw13yLgunz0 Flying SCVM (New cockpit EC BO-105)]

== Development ==
* [http://nl.youtube.com/watch?v=xkkIMdqAuC0 FlightGear new trees]
* [http://www.youtube.com/watch?v=k4oMOFnD6bw New clouds]
* [http://www.youtube.com/watch?v=EKELqBGVsqw Dynamic water effect]
* [http://www.youtube.com/watch?v=PYwlfZSHJpo Early morning red sky effect]
* [http://www.youtube.com/watch?v=GPtd6Np3u8Q Urban effect]
== Simulators ==
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15935.html A FlightGear-driven Flight & Navigation Procedures Trainer (FNPT)]
* [http://nl.youtube.com/watch?v=Y1-siAMojSM FlightGear Virtual Cockpit build]

== UAV related ==
* http://baron.flightgear.org/~curt/tmp/20080710.AVI

== Tutorials ==
Please see the separate [[Video Tutorials]] page.

__NOTOC__

[[Category:List]]

FlightGear Newsletter October 2011

2011-10-15T09:03:36Z

OO ZVY: /* Reminder: FSweekend */

FlightGear Newsletter October 2011

2011-10-15T09:02:48Z

OO ZVY: /* FlightGear on youtube */

FlightGear Newsletter October 2011

2011-10-15T09:01:57Z

OO ZVY: /* Reminder: FSweekend */

File:EHLE DC-3 panorama.png

2011-10-15T08:56:27Z

OO ZVY:

FlightGear Newsletter October 2011

2011-10-12T06:51:04Z

OO ZVY: /* Aircraft of the month */

FlightGear Newsletter October 2011

2011-10-11T11:38:29Z

OO ZVY: /* Aircraft of the month */

File:Fgfs-screen-026.png

2011-10-11T11:37:00Z

OO ZVY:

File:Astir.png

2011-10-11T11:28:19Z

OO ZVY:

FlightGear Newsletter October 2011

2011-10-11T11:25:44Z

OO ZVY: /* Aircraft of the month */

File:Diamond Da42.png

2011-10-11T11:22:20Z

OO ZVY: Diamond Da42

Diamond Da42

Places to fly

2011-09-18T09:56:00Z

OO ZVY: /* GRENOBLE Le-Versoud */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

Remember to give a look at the [[Suggested Airports]] page, where you can find a comprensive list of high quality airports in FlightGear.

'''Remove before flight!'''

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

{{TOC limit|3}}

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:World-O09.png|thumb|right|Latitude: 39.790156 Longitude: -123.266403]]
* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:KGCN-001.png|thumb|left|Grand Canyon]]
[[Image:KGCN-002.png|thumb|right|Grand Canyon]]
These airports are in the vicinity of the Grand Canyon. From [[KGCN]] head north. From [[1Z1]] head south. From [[1G4]] head north (I think.) From AZ38 head north.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KGCN-003.png|thumb|left|Grand Canyon]]
[[Image:World-KGCN.png|thumb|right|Latitude: 35.952361 Longitude: -112.146972]]
* [[KGCN|KGCN - GRAND CANYON NATIONAL PARK]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KGCN.pdf chart]
* [[1Z1|1Z1 - GRAND CANYON BAR TEN AIRSTRIP]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1Z1.pdf chart]
* [[1G4|1G4 - GRAND CANYON WEST]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1G4.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KGCN-004.png|thumb|left|Grand Canyon]]

................

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KGCN
<div style="clear:both;"></div>

==Ranger Creek Airport==
[[Image:6WA8-002.png|thumb|left|landing 1]]
[[Image:6WA8-008.png|thumb|right|landing 2]]
Greenwater, WA. This airport is wedged into the bottom of a steep canyon. You definitely need to be on your toes to get in and out of here. I'd hate to think about what the wind would do to you in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-6WA8.png|thumb|right|Latitude: 47.01305555 Longitude: -121.534444451]]

* [[6WA8|6WA8 - Ranger Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/6W8A.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:6WA8-009.png|thumb|left|landing 3]]
* [[Piper PA-18 Super Cub|pa 18]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=6WA8 --aircraft=pa18
<div style="clear:both;"></div>

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==GRENOBLE Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( GRENOBLE Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://clemaez.fr/flightgear/pattentextures_maj24082011.tar.gz
----

=Asia=
=Africa=
=Australia=
=Antarctica=

Places to fly

2011-09-18T09:44:38Z

OO ZVY: /* Europe */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

Remember to give a look at the [[Suggested Airports]] page, where you can find a comprensive list of high quality airports in FlightGear.

'''Remove before flight!'''

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

{{TOC limit|3}}

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:World-O09.png|thumb|right|Latitude: 39.790156 Longitude: -123.266403]]
* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:KGCN-001.png|thumb|left|Grand Canyon]]
[[Image:KGCN-002.png|thumb|right|Grand Canyon]]
These airports are in the vicinity of the Grand Canyon. From [[KGCN]] head north. From [[1Z1]] head south. From [[1G4]] head north (I think.) From AZ38 head north.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KGCN-003.png|thumb|left|Grand Canyon]]
[[Image:World-KGCN.png|thumb|right|Latitude: 35.952361 Longitude: -112.146972]]
* [[KGCN|KGCN - GRAND CANYON NATIONAL PARK]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KGCN.pdf chart]
* [[1Z1|1Z1 - GRAND CANYON BAR TEN AIRSTRIP]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1Z1.pdf chart]
* [[1G4|1G4 - GRAND CANYON WEST]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1G4.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KGCN-004.png|thumb|left|Grand Canyon]]

................

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KGCN
<div style="clear:both;"></div>

==Ranger Creek Airport==
[[Image:6WA8-002.png|thumb|left|landing 1]]
[[Image:6WA8-008.png|thumb|right|landing 2]]
Greenwater, WA. This airport is wedged into the bottom of a steep canyon. You definitely need to be on your toes to get in and out of here. I'd hate to think about what the wind would do to you in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-6WA8.png|thumb|right|Latitude: 47.01305555 Longitude: -121.534444451]]

* [[6WA8|6WA8 - Ranger Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/6W8A.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:6WA8-009.png|thumb|left|landing 3]]
* [[Piper PA-18 Super Cub|pa 18]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=6WA8 --aircraft=pa18
<div style="clear:both;"></div>

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=
==GRENOBLE Le-Versoud==

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( GRENOBLE Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://adf.ly/246619/http://adf.ly/246619/http://www.mediafire.com/?m3sna7bu2nrsec1
----

=Asia=
=Africa=
=Australia=
=Antarctica=

Places to fly

2011-09-18T09:43:11Z

OO ZVY: /* Europe */

[[FlightGear]] has accurate and realistic terrain. Here are some interesting places where you can do virtual sight seeing.

If you are starting with [[FGRun]] - the FlightGear launcher - you can enter the [[airport]] id and select the runway on the appropriate screen in the startup wizard.
If you are starting from the command line you can use the options: <tt>--airport=ABCD</tt> and <tt>--runway=12L</tt>.

Remember to give a look at the [[Suggested Airports]] page, where you can find a comprensive list of high quality airports in FlightGear.

'''Remove before flight!'''

Before you start flying into one of the suggested flights, you should add both the terrain and the Objects to you FlightGear installation; This is well explained on the [[Howto: Install scenery|installing scenery]] page.

p.s. charts are generated using FlightGear data only.

{{TOC limit|3}}

=North America=
==Round Valley Airport==
[[Image:O09-002.png|thumb|left|right after take off]]
[[Image:O09-003.png|thumb|right|Valley]]
Covalis, CA. The airport is at the West edge of a 7 mile across valley.<BR/>
The predominant wind is a cross wind. Take-offs to the west (if they use the full runway length) often have to fly between 2 small hills and over another valley while gaining altitude. Most pilots take off to the west.<BR/>
It is a paved runway and quite long. It was designated as an emergency recovery field during the Cold War and was used twice that I know of by military aircraft that could not take off again from the field.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:World-O09.png|thumb|right|Latitude: 39.790156 Longitude: -123.266403]]
* [[O09|O09 - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/O09.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
I have tried this trip using a p38, quite powerful airplane
* [[Lockheed-P38|P38]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=O09 --runway=28 --aircraft=p38
<div style="clear:both;"></div>

==Hell's Canyon==
[[Image:25U-001.png|thumb|left|right after take off]]
[[Image:25U-004.png|thumb|right|Valley]]
Hell's Canyon, Imnaha, OR. This airport is located just west of "Hell's Canyon National Park" which has the Snake River running through it.<br/>
Supposedly it's a 5500 foot drop from the top of the canyon to the river.<BR/>
The airport is located on the brink of this canyon.

See the remarks on the airport page (click on the airport id) ... DOWNDRAFTS, SHEER DROP IN TERRAIN, LIVESTOCK, etc. Don't go here on your first solo x-country. :-)
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:25U-005.png|thumb|left|Landing]]
[[Image:World-25U.png|thumb|right|Latitude: 45.427861 Longitude: -116.693889]]
* [[25U|25U - Round valley]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/25U.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:25U-006.png|thumb|left|Landing 2]]
I have tried this trip using a pilatus PC-9M, powerful airplane
* [[PC-9M|PC-9M]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=25U --aircraft=PC-9M
<div style="clear:both;"></div>

==Crater Lake National Park Tour==
[[Image:64s-003.png|thumb|left|Approaching the lake]]
[[Image:64s-002.png|thumb|right|Direction 40 degrees]]
Prospect, OR.<br/>

Take off and fly at a heading of about 40 degrees until you cross the first distinct ridge in front of you. (several minutes of flight in the navion ... just climb as fast as you can, it will be a close squeek to get over :-)<br/>

Once you clear the ridge and can see beyond it, turn right and fly a heading of about 70 degrees. You should see two shallow peaks off in the distance. Head right between these -- they are the two sides of the crater. As you get closer the shape of the crater will come into view. There's a lake there in real life, hopefully it will be there in flight gear too before long.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:64s-001.png|thumb|left|Leaving the 64S airfield]]
[[Image:World-64S.png|thumb|right|Latitude: 42.743183 Longitude: -122.488092]]
* [[64S|64S - Prospect State]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/64S.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:64s-004.png|thumb|left|Lake view 1]]
[[Image:64s-005.png|thumb|right|Lake view 2]]

* [[Ryan_Navion|Navion]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=64S --runway=02 --aircraft=navion
<div style="clear:both;"></div>

==Grand Canyon Tour==
[[Image:KGCN-001.png|thumb|left|Grand Canyon]]
[[Image:KGCN-002.png|thumb|right|Grand Canyon]]
These airports are in the vicinity of the Grand Canyon. From [[KGCN]] head north. From [[1Z1]] head south. From [[1G4]] head north (I think.) From AZ38 head north.
<div style="clear:both;"></div>

===Airports and coordinates===
[[Image:KGCN-003.png|thumb|left|Grand Canyon]]
[[Image:World-KGCN.png|thumb|right|Latitude: 35.952361 Longitude: -112.146972]]
* [[KGCN|KGCN - GRAND CANYON NATIONAL PARK]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KGCN.pdf chart]
* [[1Z1|1Z1 - GRAND CANYON BAR TEN AIRSTRIP]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1Z1.pdf chart]
* [[1G4|1G4 - GRAND CANYON WEST]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1G4.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KGCN-004.png|thumb|left|Grand Canyon]]

................

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KGCN
<div style="clear:both;"></div>

==Ranger Creek Airport==
[[Image:6WA8-002.png|thumb|left|landing 1]]
[[Image:6WA8-008.png|thumb|right|landing 2]]
Greenwater, WA. This airport is wedged into the bottom of a steep canyon. You definitely need to be on your toes to get in and out of here. I'd hate to think about what the wind would do to you in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-6WA8.png|thumb|right|Latitude: 47.01305555 Longitude: -121.534444451]]

* [[6WA8|6WA8 - Ranger Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/6W8A.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:6WA8-009.png|thumb|left|landing 3]]
* [[Piper PA-18 Super Cub|pa 18]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=6WA8 --aircraft=pa18
<div style="clear:both;"></div>

==Mount Rainier Tour==
[[Image:WA20-002.png|thumb|left|The mountain from far away]]
[[Image:WA20-006.png|thumb|right|external view]]
Eatonville, WA. Start out at Swanson Airport in Eatonville, WA. Take off and fly a heading of about 90 degrees. You will need to fly for 5-10 minutes before the mountain comes into view. Be patient if you don't see it right away, it will dwarf everything in it's vicinity.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-WA20.png|thumb|right|Latitude: 46.87588502 Longitude: -122.25733500]]

* [[WA20|WA20 - Swanson]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/WA20.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w130n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:WA20-007.png|thumb|left|external near view]]
[[Image:WA20-009.png|thumb|right|external near view]]
* [[mosquito]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=WA20 --aircraft=mosquito
<div style="clear:both;"></div>

==Death Valley Tour==
[[Image:L06-001.png|thumb|left|in the air]]
[[Image:Furnace-creek.jpg|thumb|left|real life view of Furnace Creek Airfield]]
[[Image:L06-002.png|thumb|right|in the air]]
Furnace Creek, CA. This starts you right in the middle of Death Valley which runs north & south. If you head south about 15 miles you'll hit the lowest point in the USA, 282 feet (86 meters) below sea level.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-L06.png|thumb|right|Latitude: 36.46451100 Longitude: -116.88139422]]
* [[L06|L06 - Furnace Creek]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/L06.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:L06-003.png|thumb|left|in the air]]
[[Image:L06-004.png|thumb|right|in the air]]
* [[rallye-MS893]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=L06 --aircraft=rallye-MS893
<div style="clear:both;"></div>

==Utah==
!!! Work in progress !!!<BR/>

Escalante Muni Airport, Escalante, UT. This airport is east and a bit north of Bryce Canyon National park. If you head mostly south and a bit east you'll eventually hit the Grand Canyon. It is sandwiched between the Dixie National forest to the north and the Grand Staircase-Escalante National Monument to the south. There should be interesting stuff to see no matter which direction you head.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-1L7.png|thumb|right|Latitude: 37.75054400 Longitude: -111.57578300]]
* [[1L7|1L7 - Escalante Muni]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/1L7.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=1L7 --aircraft=pa18
<div style="clear:both;"></div>

==Lake County Airport (CO)==
[[Image:KLXV-001.png|thumb|left|Adjust mixture !]]
[[Image:KLXV-002.png|thumb|right|The terrain will be covered by snow]]
Lake County Airport, Leadville, CO. This airport is at an elevation of 9927 making it a bit of a challenge to get into and out of with a standard C172.<BR/>
Make sure you lean out your engine before taking off and read up on density altitude before you try this one in real life.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:KLXV-003.png|thumb|left|The airport]]
[[Image:World-KLXV.png|thumb|right|Latitude: 39.22812500 Longitude: -106.31835600]]
* [[KLXV|KLXV - Lake Co]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KLXV.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w110n30.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KLXV-004.png|thumb|left|I like this panorama]]
[[Image:KLXV-005.png|thumb|right|The nearby lake]]
* [[Cessna C172P]]

<div style="clear:both;"></div>

===FlightGear launching===
[[Image:KLXV-006.png|thumb|left|Landing...]]
fgfs --airport=KLXV --aircraft=c172p
<div style="clear:both;"></div>

==Caribbean - Saint Martin and St. Kitts==
[[Image:TNCM-003.png|thumb|left|just after the take off]]
[[Image:TNCM-004.png|thumb|right|some nearby island]]
Pilots of the Caribbeans is an informal FlightGear community of users who fly around the small Caribbean islands, many of which have custom scenery and improved landclass data. (For details see [[Pilots of the Caribbean]])<BR/>

[[TNCM|Princess Juliana International Airport (TNCM)]] at the isle of Saint Martin, is one of the most popular airports in FlightGear. In large part due to the custom objects and land cover. However, St. Marten is only one of several detailed airports in the region - and, while the approach for TNCM is one of the most memorable in the whole world, the land cover for St. Kitts and Nevis makes it a lovely place to fly.

British Airways, US Airways and American Airlines, among others, all fly into St. Kitts' [[TKPK|Robert L. Bradshaw International Airport (TKPK)]] in real life.

Take off from TKPK in a [[Piper_J3_Cub|Piper Cub]] and make a northward, clockwise circle of the island. Start your descent on the east side of the island, and focus on the small hill which separates the north from the south. Start hugging the coast near the beach and look to the west - as soon as the railroad heads to the southwest, you're about ready to turn for final. Make your right hand turn for final and taxi to the terminal.

If you want to fully explore this whole country, take off in a Beaver, which has a little more speed, and fly a figure eight. Take off from TKPK and circle the airport to the north like in the Cub. Then instead of landing, perform a touch-and-go and turn left over the boat terminal and make for the west coast of Nevis. Enjoy the beauty of the south coast of St. Kitts before circling Nevis. Over Nevis, you have several options - cut your flight short and land at [[TKPN]] on the island of Nevis, complete the "figure eight" by heading back to TKPK, or check your fuel and head east across the Caribbean to Antigua (which does not have custom land cover).<BR/>
<BR/>
Check out the [[Pilots of the Caribbean]] page, for further informations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-TNCM.png|thumb|right|Latitude: 18.040953 Longitude: -63.108900]]

* [[TNCM|TNCM - Princess Juliana International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TNCM.pdf chart]
* [[TKPK|TKPK - Robert L. Bradshaw International Airport]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPK.pdf chart]
* [[TKPN|TKPN - Vance Winkworth Amory Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TKPN.pdf chart]
others interesting airports in the area:
* [[TFFF|TFFF - Le Lamentin]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFF.pdf chart]
* [[MDPP|MDPP - Gregorio Luperon Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/MDPP.pdf chart]
* [[TJSJ|TJSJ - Luis Munoz Marin Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TJSJ.pdf chart]
* [[FMEE|FMEE - St Denis Gillot]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/FMEE.pdf chart]
* [[TFFG|TFFG - Grand Case]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/TFFG.pdf chart]

required scenery tile:
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w070n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n10.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w080n20.tgz
* ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w090n20.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:TNCM-005.png|thumb|left|amazing]]
[[Image:TNCM-006.png|thumb|right|landing]]
* [[Piper_J3_Cub|Piper Cub]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=TKPK --aircraft=Cub
<div style="clear:both;"></div>

==Friedman Memorial Airport (Idaho)==
[[Image:KSUN-001.png|thumb|left|take off]]
[[Image:KSUN-002.png|thumb|right|nearby]]
Friedman Memorial Airport, Hailey, Idaho. This airport is nestled in a valley surrounded by significant terrain. It's one that shows up quite often in accident investigations.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:World-KSUN.png|thumb|right|Latitude: 43.51223900 Longitude: -114.30376100]]
* [[KSUN|KSUN - Friedman Mem]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/KSUN.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/w120n40.tgz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:KSUN-003.png|thumb|left|landing]]
[[Image:KSUN-004.png|thumb|right|landing]]
* [[FK9MK2]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=KSUN --aircraft=fk9mk2
<div style="clear:both;"></div>

=South America=
==Southern Tip of Chile==
[[Image:Scgz-001.png|thumb|left|right after take off]]
[[Image:Scgz-004.png|thumb|right|Some part of the scenery]]
Gary Carvell: Here is a suggestion for the FlightGear Places to Fly page. I don't have any particular routes, just fly around and enjoy the gorgeous scenery.<BR/>
These three airports are in the same region of the very southern tip of Argentina. This area is a scenic wonderland - a maze of islands, mountains, and ocean channels. Hours of entertainment.<BR/>
SCGZ - Puerto Williams Guardiamarina Zanartu Airport, Chile Located on the north coast of Isla Navarino facing the Beagle Channel. At 55 deg S. longitude, Puerto Williams is considered the southernmost town in the world.<BR/>
SAWH - Ushuaia Islas Malvinas Airport
SAWO - Ushuaia Est Aeronaval Airport
Ushuaia, on the south coast of Isla Grande de Tierra del Fuego, on the the Beagle Channel.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:Sawh-004.png|thumb|left|Approaching Ushumaia Malvinas Argentinas]]
[[Image:World-scgz.png|thumb|right|Latitude: -54.931072 Longitude: -67.626261]]

* [[SCGZ|SCGZ - Guardiamarina Zanartu]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SCGZ.pdf chart]
* [[SAWH|SAWH - Ushuaia Malvinas Argentinas]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWH.pdf chart]
* [[SAWO|SAWO - Ushuaia Est Aeronaval]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/SAWO.pdf chart]
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:Scgz-002.png|thumb|left|Just left the scgz airport]]
I personally like to fly this area in the [[Consolidated_Aircraft_PBY_Catalina|Catalina]], it's a great sightseeing plane with the advantage that you can take off and land just about anywhere.
* [[Consolidated_Aircraft_PBY_Catalina|Catalina]]
<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=SCGZ --aircraft=Catalina
<div style="clear:both;"></div>

=Middle East=
==Israel to Jordan over the Dead Sea==
[[Image:LLBS-001.png|thumb|left|take off]]
[[Image:LLBS-002.png|thumb|right|flat land]]
Dead Sea is the lowest water elevation on the Earth. Take off from the Beer-Sheva Teyman airport and head East-North-East. About half way there, after the southern Hebron mountains ridge, there'll be a sharp drop-off down to the Dead Sea --- the lowest exposed point on the Earth.<br/>
<br/>
It's really fun to descend and explore the beautiful coastline. In the real life, you wouldn't like to fly low over this water there of your own will --- while you don't need a life vest in the Dead Sea, the water is pretty caustic there for one's eyes. Once you're done marvelling the sights, continue on to the Queen Alia airport.
<div style="clear:both;"></div>
===Airports and coordinates===
[[Image:LLBS-006.png|thumb|left|landing in the dead sea, notice the altitude !]]
[[Image:OJAI-007.png|thumb|right|landing at Queen Alia Intl.]]
[[Image:World-LLBS.png|thumb|right|Latitude: 31.29037800 Longitude: 34.71922500]]
* [[LLBS|LLBS - Teyman]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/LLBS.pdf chart]
* [[OJAI|OJAI - Queen Alia Intl]] - [http://assistenza.larasrl.net/brisa/fgfs/suggested_flights/OJAI.pdf chart]

required scenery tile: ftp://ftp.sunsite.org.uk/sites/ftp.flightgear.org/flightgear-ftp/Scenery/e030n30.tar.gz
<div style="clear:both;"></div>

===Suggested aircraft===
[[Image:LLBS-003.png|thumb|left|approaching the dead sea]]
[[Image:LLBS-004.png|thumb|right|there is also a minor airport]]
* [[Albatross]]

<div style="clear:both;"></div>

===FlightGear launching===
fgfs --airport=LLBS --aircraft=Albatross
<div style="clear:both;"></div>

=Europe=

[[Image:LFLG.jpg|800px]]

France : '''LFLG''' ( GRENOBLE Le-Versoud ) airport : border of Alps
*P.A.F. home base [http://equipe-flightgear.forumactif.com/ link]
*Scenery : http://clemaez.fr/flightgear/flightgearfrance_05062011.tar.gz
*Texture : http://adf.ly/246619/http://adf.ly/246619/http://www.mediafire.com/?m3sna7bu2nrsec1
----

=Asia=
=Africa=
=Australia=
=Antarctica=

File:LFLG.jpg

2011-09-18T09:32:29Z

OO ZVY: