<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.flightgear.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=De+profundis</id>
	<title>FlightGear wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.flightgear.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=De+profundis"/>
	<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/Special:Contributions/De_profundis"/>
	<updated>2026-04-15T11:08:54Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.6</generator>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=VFR_Tutorial&amp;diff=67481</id>
		<title>VFR Tutorial</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=VFR_Tutorial&amp;diff=67481"/>
		<updated>2014-02-08T15:51:53Z</updated>

		<summary type="html">&lt;p&gt;De profundis: De profundis moved page VFR Tutorial to Cross-CountryTutorial 2 - a VFR guide&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Cross-CountryTutorial 2 - a VFR guide]]&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=User:De_profundis/Cross-CountryTutorial_2_-_a_VFR_guide&amp;diff=67480</id>
		<title>User:De profundis/Cross-CountryTutorial 2 - a VFR guide</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=User:De_profundis/Cross-CountryTutorial_2_-_a_VFR_guide&amp;diff=67480"/>
		<updated>2014-02-08T15:51:53Z</updated>

		<summary type="html">&lt;p&gt;De profundis: De profundis moved page VFR Tutorial to Cross-CountryTutorial 2 - a VFR guide&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== VFR Tutorial ==&lt;br /&gt;
well this page is being worked at...&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=User:De_profundis/Cross-CountryTutorial_2_-_a_VFR_guide&amp;diff=67479</id>
		<title>User:De profundis/Cross-CountryTutorial 2 - a VFR guide</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=User:De_profundis/Cross-CountryTutorial_2_-_a_VFR_guide&amp;diff=67479"/>
		<updated>2014-02-08T15:49:28Z</updated>

		<summary type="html">&lt;p&gt;De profundis: Created page with &amp;quot; == VFR Tutorial == well this page is being worked at...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== VFR Tutorial ==&lt;br /&gt;
well this page is being worked at...&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&amp;diff=67478</id>
		<title>FlightGear Newsletter February 2014</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&amp;diff=67478"/>
		<updated>2014-02-08T15:42:46Z</updated>

		<summary type="html">&lt;p&gt;De profundis: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{newsletter}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
{{Note|This newsletter is currently being written by our contributors, people like YOU:&lt;br /&gt;
&lt;br /&gt;
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.}}&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].&lt;br /&gt;
&lt;br /&gt;
=== Random Buildings ===&lt;br /&gt;
&lt;br /&gt;
=== Project Rembrandt ===&lt;br /&gt;
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].&lt;br /&gt;
&lt;br /&gt;
=== Canvas System ===&lt;br /&gt;
&lt;br /&gt;
The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&amp;amp;t=22014 FG Forum Topic]&lt;br /&gt;
&lt;br /&gt;
=== High Level Architecture ===&lt;br /&gt;
&lt;br /&gt;
=== Usability Improvements ===&lt;br /&gt;
&lt;br /&gt;
=== Getting involved as a programmer ===&lt;br /&gt;
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done.  Fundamentally we need more core devs.&lt;br /&gt;
&lt;br /&gt;
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].&lt;br /&gt;
&lt;br /&gt;
== Release ChangeLog ==&lt;br /&gt;
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.&lt;br /&gt;
&lt;br /&gt;
== Interview with a contributor (NAME) ==&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* How long have you been involved in FlightGear?&lt;br /&gt;
* What are your major interests in FlightGear?&lt;br /&gt;
* What project are you working on right now?&lt;br /&gt;
* What do you plan on doing in the future?&lt;br /&gt;
* Are you happy with the way the FlightGear project is going?&lt;br /&gt;
* What do you enjoy most about developing for FlightGear?&lt;br /&gt;
* Are there any &amp;quot;hidden features&amp;quot; you have worked on in FlightGear that new users may miss?&lt;br /&gt;
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?&lt;br /&gt;
&lt;br /&gt;
More questions are being collected here: [[Interview questions]].&lt;br /&gt;
&lt;br /&gt;
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX &lt;br /&gt;
&lt;br /&gt;
== Nasal for newbies ==&lt;br /&gt;
&lt;br /&gt;
== New software tools and projects ==&lt;br /&gt;
&lt;br /&gt;
== FlightGear addons and mods ==&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Updated aircraft ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== '''Sikorsky SH-60 Bravo Seahawk''' ====&lt;br /&gt;
'''James Cusick, (X7cusick8X)'''&lt;br /&gt;
&lt;br /&gt;
[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]&lt;br /&gt;
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]&lt;br /&gt;
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]&lt;br /&gt;
&lt;br /&gt;
The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast. &lt;br /&gt;
&lt;br /&gt;
Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk! &lt;br /&gt;
The updates include:&lt;br /&gt;
&lt;br /&gt;
Integrated Pushback&lt;br /&gt;
&lt;br /&gt;
Selectable payloads&lt;br /&gt;
&lt;br /&gt;
95% complete folding animation for carrier deck transit &lt;br /&gt;
&lt;br /&gt;
New Liveries &lt;br /&gt;
&lt;br /&gt;
FDM Fixes &lt;br /&gt;
&lt;br /&gt;
and more&lt;br /&gt;
&lt;br /&gt;
=== Liveries ===&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
=== Airports ===&lt;br /&gt;
&lt;br /&gt;
== Aircraft of the month ==&lt;br /&gt;
== Airport of the month ==&lt;br /&gt;
== Screenshot of the month ==&lt;br /&gt;
&lt;br /&gt;
== Suggested flights ==&lt;br /&gt;
== Aircraft reviews ==&lt;br /&gt;
&lt;br /&gt;
== Wiki updates ==&lt;br /&gt;
=== Translators required ===&lt;br /&gt;
{|&lt;br /&gt;
|[[File:en.gif]]&lt;br /&gt;
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:de.gif]]&lt;br /&gt;
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:nl.gif]]&lt;br /&gt;
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:es.gif]]&lt;br /&gt;
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.&lt;br /&gt;
&lt;br /&gt;
=== New tutorials and screencasts ===&lt;br /&gt;
&lt;br /&gt;
=== FlightGear  &amp;amp;diams; Cross-Country Tutorial II &amp;amp;diams; a  VFR  guide ===&lt;br /&gt;
[[File:Coverwiki2.jpg|250px|thumb|left]]&lt;br /&gt;
&amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt;It's almost been a year since the first release of Cross-Country Tutorial II.&amp;lt;br /&amp;gt;&lt;br /&gt;
Now with '''version three point zero''' the document is better than ever in many aspects.&amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt;&lt;br /&gt;
Go to the respective FG Forum thread: http://forum.flightgear.org/viewtopic.php?f=72&amp;amp;t=19600 where you can: &amp;lt;br /&amp;gt; &lt;br /&gt;
*download this tutorial &lt;br /&gt;
**find out more about it &lt;br /&gt;
***'''post your comments and suggestions'''&lt;br /&gt;
&amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt;coming up soon is the X-Country 2's own wiki page!&lt;br /&gt;
&amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt;&lt;br /&gt;
=== Forum news ===&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
=== Virtual airlines ===&lt;br /&gt;
=== FlightGear events ===&lt;br /&gt;
&lt;br /&gt;
== Useful links ==&lt;br /&gt;
== And finally ... ==&lt;br /&gt;
=== Contributing ===&lt;br /&gt;
One of the regular thoughts expressed on the FlightGear forums is &amp;quot;I'd like to contribute but I don't know how to program, and I don't have the time&amp;quot;. 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. &lt;br /&gt;
&lt;br /&gt;
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].&lt;br /&gt;
&lt;br /&gt;
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&amp;amp;t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].&lt;br /&gt;
&lt;br /&gt;
=== YASim looking for a new maintainer ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.&lt;br /&gt;
&lt;br /&gt;
Obviously this is chicken-and-egg, since no one can become expert enough in the  code to become a maintainer :)&lt;br /&gt;
&lt;br /&gt;
So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too, &lt;br /&gt;
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch. &lt;br /&gt;
Suggestions for that means in practice, are most welcome!&lt;br /&gt;
&lt;br /&gt;
Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.&amp;lt;ref&amp;gt;{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html &lt;br /&gt;
|title=YASim and documentation&lt;br /&gt;
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}&amp;lt;/ref&amp;gt;|James Turner}}&lt;br /&gt;
&lt;br /&gt;
{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer).  Just cc: me if you do, because my&lt;br /&gt;
latencies here are measured in weeks. &lt;br /&gt;
Bugs can always be fixed.  What YASim needs is a maintainer, not really expertise per se.  The latter comes from the former.&amp;lt;ref&amp;gt;{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html &lt;br /&gt;
|title=YASim and documentation&lt;br /&gt;
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}&amp;lt;/ref&amp;gt;|Andy Ross}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Call for volunteers ===&lt;br /&gt;
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support&lt;br /&gt;
&lt;br /&gt;
=== Did you know ===&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter]]&lt;br /&gt;
&amp;lt;!-- this needs to be changed after each release, so that newsletters show up in the proper category --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2.12]]&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&amp;diff=67477</id>
		<title>FlightGear Newsletter February 2014</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2014&amp;diff=67477"/>
		<updated>2014-02-08T15:39:26Z</updated>

		<summary type="html">&lt;p&gt;De profundis: /* New tutorials and screencasts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{newsletter}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
{{Note|This newsletter is currently being written by our contributors, people like YOU:&lt;br /&gt;
&lt;br /&gt;
We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.}}&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].&lt;br /&gt;
&lt;br /&gt;
=== Random Buildings ===&lt;br /&gt;
&lt;br /&gt;
=== Project Rembrandt ===&lt;br /&gt;
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].&lt;br /&gt;
&lt;br /&gt;
=== Canvas System ===&lt;br /&gt;
&lt;br /&gt;
The F-16CJ is being renovated to include the most realistic fighter HUDs yet. See the progress here:[[F-16CJ HUD Project Newsletter]]. It is also online the FG Forum here: [http://forum.flightgear.org/viewtopic.php?f=71&amp;amp;t=22014 FG Forum Topic]&lt;br /&gt;
&lt;br /&gt;
=== High Level Architecture ===&lt;br /&gt;
&lt;br /&gt;
=== Usability Improvements ===&lt;br /&gt;
&lt;br /&gt;
=== Getting involved as a programmer ===&lt;br /&gt;
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done.  Fundamentally we need more core devs.&lt;br /&gt;
&lt;br /&gt;
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].&lt;br /&gt;
&lt;br /&gt;
== Release ChangeLog ==&lt;br /&gt;
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.&lt;br /&gt;
&lt;br /&gt;
== Interview with a contributor (NAME) ==&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* How long have you been involved in FlightGear?&lt;br /&gt;
* What are your major interests in FlightGear?&lt;br /&gt;
* What project are you working on right now?&lt;br /&gt;
* What do you plan on doing in the future?&lt;br /&gt;
* Are you happy with the way the FlightGear project is going?&lt;br /&gt;
* What do you enjoy most about developing for FlightGear?&lt;br /&gt;
* Are there any &amp;quot;hidden features&amp;quot; you have worked on in FlightGear that new users may miss?&lt;br /&gt;
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?&lt;br /&gt;
&lt;br /&gt;
More questions are being collected here: [[Interview questions]].&lt;br /&gt;
&lt;br /&gt;
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX &lt;br /&gt;
&lt;br /&gt;
== Nasal for newbies ==&lt;br /&gt;
&lt;br /&gt;
== New software tools and projects ==&lt;br /&gt;
&lt;br /&gt;
== FlightGear addons and mods ==&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Updated aircraft ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== '''Sikorsky SH-60 Bravo Seahawk''' ====&lt;br /&gt;
'''James Cusick, (X7cusick8X)'''&lt;br /&gt;
&lt;br /&gt;
[[File:SH-60 Bravo.png|thumb|SH-60B Taking off from the USS Carl Vinson]]&lt;br /&gt;
[[File:SH-60 Landing.png|thumb|SH-60 Landing]]&lt;br /&gt;
[[File:SH-60 Rotor Wash.png|thumb|Rotor Wash]]&lt;br /&gt;
&lt;br /&gt;
The FG Seahawk is an incredibly easy to fly helicopter designed for naval conditions, with its integrated FCS and FDM landing on carrier decks is a blast. &lt;br /&gt;
&lt;br /&gt;
Recently i have take a break form FG but I am proud to announce the updated SH-60B Seahawk! &lt;br /&gt;
The updates include:&lt;br /&gt;
&lt;br /&gt;
Integrated Pushback&lt;br /&gt;
&lt;br /&gt;
Selectable payloads&lt;br /&gt;
&lt;br /&gt;
95% complete folding animation for carrier deck transit &lt;br /&gt;
&lt;br /&gt;
New Liveries &lt;br /&gt;
&lt;br /&gt;
FDM Fixes &lt;br /&gt;
&lt;br /&gt;
and more&lt;br /&gt;
&lt;br /&gt;
=== Liveries ===&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
=== Airports ===&lt;br /&gt;
&lt;br /&gt;
== Aircraft of the month ==&lt;br /&gt;
== Airport of the month ==&lt;br /&gt;
== Screenshot of the month ==&lt;br /&gt;
&lt;br /&gt;
== Suggested flights ==&lt;br /&gt;
== Aircraft reviews ==&lt;br /&gt;
&lt;br /&gt;
== Wiki updates ==&lt;br /&gt;
=== Translators required ===&lt;br /&gt;
{|&lt;br /&gt;
|[[File:en.gif]]&lt;br /&gt;
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:de.gif]]&lt;br /&gt;
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:nl.gif]]&lt;br /&gt;
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:es.gif]]&lt;br /&gt;
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
You can stay updated with FlightGear news, updates and tutorials by visiting and subscribing to [http://www.youtube.com/user/osjcag osjcag's] channel on YouTube.&lt;br /&gt;
&lt;br /&gt;
=== New tutorials and screencasts ===&lt;br /&gt;
&lt;br /&gt;
=== FlightGear  &amp;amp;diams; Cross-Country Tutorial II &amp;amp;diams; a  VFR  guide ===&lt;br /&gt;
[[File:Coverwiki2.jpg|250px|thumb|left]]&lt;br /&gt;
&amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt;It's almost been a year since the first release of Cross-Country Tutorial II.&amp;lt;br /&amp;gt;&lt;br /&gt;
Now with '''version three point zero''' the document is better than ever in many aspects.&amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt;&lt;br /&gt;
Go to the respective FG Forum thread: http://forum.flightgear.org/viewtopic.php?f=72&amp;amp;t=19600 where you can: &amp;lt;br /&amp;gt; &lt;br /&gt;
*download this tutorial &lt;br /&gt;
**find out more about it &lt;br /&gt;
***'''post your comments and suggestions'''&lt;br /&gt;
&amp;lt;br /&amp;gt; &amp;lt;br /&amp;gt;coming up soon is the X-Country 2's own wiki page!&lt;br /&gt;
&lt;br /&gt;
=== Forum news ===&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
=== Virtual airlines ===&lt;br /&gt;
=== FlightGear events ===&lt;br /&gt;
&lt;br /&gt;
== Useful links ==&lt;br /&gt;
== And finally ... ==&lt;br /&gt;
=== Contributing ===&lt;br /&gt;
One of the regular thoughts expressed on the FlightGear forums is &amp;quot;I'd like to contribute but I don't know how to program, and I don't have the time&amp;quot;. 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. &lt;br /&gt;
&lt;br /&gt;
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].&lt;br /&gt;
&lt;br /&gt;
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&amp;amp;t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].&lt;br /&gt;
&lt;br /&gt;
=== YASim looking for a new maintainer ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.&lt;br /&gt;
&lt;br /&gt;
Obviously this is chicken-and-egg, since no one can become expert enough in the  code to become a maintainer :)&lt;br /&gt;
&lt;br /&gt;
So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too, &lt;br /&gt;
if people are new to C++), and providing we have some assurance that a representative sample of yasim aircraft are unchanged or improved by the patch. &lt;br /&gt;
Suggestions for that means in practice, are most welcome!&lt;br /&gt;
&lt;br /&gt;
Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.&amp;lt;ref&amp;gt;{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html &lt;br /&gt;
|title=YASim and documentation&lt;br /&gt;
|author=James Turner |date= Fri, 05 Oct 2012 03:54:43 -0700}}&amp;lt;/ref&amp;gt;|James Turner}}&lt;br /&gt;
&lt;br /&gt;
{{cquote|I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer).  Just cc: me if you do, because my&lt;br /&gt;
latencies here are measured in weeks. &lt;br /&gt;
Bugs can always be fixed.  What YASim needs is a maintainer, not really expertise per se.  The latter comes from the former.&amp;lt;ref&amp;gt;{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html &lt;br /&gt;
|title=YASim and documentation&lt;br /&gt;
|author=Andy Ross |date= Fri, 05 Oct 2012 03:54:43 -0700}}&amp;lt;/ref&amp;gt;|Andy Ross}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Call for volunteers ===&lt;br /&gt;
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support&lt;br /&gt;
&lt;br /&gt;
=== Did you know ===&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter]]&lt;br /&gt;
&amp;lt;!-- this needs to be changed after each release, so that newsletters show up in the proper category --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2.12]]&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:Coverwiki2.jpg&amp;diff=67475</id>
		<title>File:Coverwiki2.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:Coverwiki2.jpg&amp;diff=67475"/>
		<updated>2014-02-08T15:04:50Z</updated>

		<summary type="html">&lt;p&gt;De profundis: De profundis uploaded a new version of &amp;amp;quot;File:Coverwiki2.jpg&amp;amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=the cover of &amp;quot;Cross Country Tutorial II&amp;quot;}}&lt;br /&gt;
|date=2013-04-04&lt;br /&gt;
|source={{own}}&lt;br /&gt;
|author=[[User:De profundis|De profundis]]&lt;br /&gt;
|permission=&lt;br /&gt;
|other_versions=&lt;br /&gt;
|other_fields=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{self|cc-by-sa-3.0}}&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=User:De_profundis&amp;diff=59433</id>
		<title>User:De profundis</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=User:De_profundis&amp;diff=59433"/>
		<updated>2013-04-10T11:24:45Z</updated>

		<summary type="html">&lt;p&gt;De profundis: a few things about be and my work (who wants to know anyway...?)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hello,&lt;br /&gt;
&lt;br /&gt;
I am Michalis from Rethymno Crete, Greece.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ever since I met this wonderful flying simulator, always wanted to do some work for FlightGear.&lt;br /&gt;
But my programming knowledge is close to zero...&lt;br /&gt;
&lt;br /&gt;
On the other hand, I enjoy learning about aviation, aquiring theoretical pilot knowledge and practicing what I learned in FlightGear.&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
So I combined all this to present the FG community with &amp;quot;[https://www.dropbox.com/s/j7cx4dqanc4iez4/VFR%20cross%20country%20II%20v121.pdf Cross-Country Tutorial II - a VFR guide]&amp;quot;&lt;br /&gt;
&lt;br /&gt;
They say it's going to be included in the official FG package and I'm very proud of it!&lt;br /&gt;
&lt;br /&gt;
dp&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2013&amp;diff=59372</id>
		<title>FlightGear Newsletter April 2013</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2013&amp;diff=59372"/>
		<updated>2013-04-04T12:12:18Z</updated>

		<summary type="html">&lt;p&gt;De profundis: /* Cross-Country Tutorial II - a VFR guide */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{newsletter}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
''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. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and the changelog of the upcoming release.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].&lt;br /&gt;
&lt;br /&gt;
=== Advanced Weather ===&lt;br /&gt;
&lt;br /&gt;
Advanced Weather's cloud placement algorithms are currently receiving a major overhaul. In reality, many scattered cloud layers form rather complex patterns on the sky. One strategy is to simply take pictures of these and project them as 2d clouds layers into the scene, which looks fine from the ground, but fails from close-up. Advanced Weather has always preferred to model as 3d clouds whatever can be modelled in 3d. However, this means that the intricate patterns need to be created by a suitable algorithm.&lt;br /&gt;
&lt;br /&gt;
So far, the first generation of placement algorithms have utilized rather simple geometries like grid patterns and random clusters. While this is usually not a major issue from the ground, it is quite apparent from high altitude - here is an example of a cloud distribution based on multiple clusters:&lt;br /&gt;
&lt;br /&gt;
[[File:Clouddist old.jpg|300px|Old algorithm results from 80.000 ft]]&lt;br /&gt;
&lt;br /&gt;
Second generation placement algorithms are based on more intricate semi-random patterns. These distribute clouds just in a different way (i.e. the result does not require higher rendering performance) and the placement algorithms are not even significantly more expensive computationally (perhaps 10% - the advantage all comes from smarter design) - yet they work much better approximating real cloud distributions.&lt;br /&gt;
&lt;br /&gt;
Here are the results for the same weather situation from 'stick bundle' and 'domains' - two of the new placement methods:&lt;br /&gt;
&lt;br /&gt;
[[File:Clouddist new1.jpg|300px|New algorithm results from 80.000 ft]]&lt;br /&gt;
[[File:Clouddist new2.jpg|300px|New algorithm results from the ground]]&lt;br /&gt;
&lt;br /&gt;
Cloud distributions appear much more natural and appealing, especially from high altitude. Work is in progress to replace 1st generation by 2nd generation algorithms in both the online and offline weather models of Advanced Weather.&lt;br /&gt;
&lt;br /&gt;
=== Random Buildings ===&lt;br /&gt;
&amp;lt;!-- These are currently just a bunch of placeholders for the latest projects (as of 08/2012)  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Project Rembrandt ===&lt;br /&gt;
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].&lt;br /&gt;
&lt;br /&gt;
=== Canvas System ===&lt;br /&gt;
&amp;lt;!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== High Level Architecture ===&lt;br /&gt;
=== FlightGear an Android ===&lt;br /&gt;
&lt;br /&gt;
=== Usability Improvements ===&lt;br /&gt;
&lt;br /&gt;
=== Mailing list digest ===&lt;br /&gt;
&lt;br /&gt;
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)&lt;br /&gt;
&lt;br /&gt;
=== Forum digest ===&lt;br /&gt;
&lt;br /&gt;
=== Git digest ===&lt;br /&gt;
&lt;br /&gt;
=== Getting involved as a programmer ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Howto:Start core development]]&lt;br /&gt;
&lt;br /&gt;
== Release ChangeLog ==&lt;br /&gt;
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.&lt;br /&gt;
&lt;br /&gt;
== Interview with a contributor (NAME) ==&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* How long have you been involved in FlightGear?&lt;br /&gt;
* What are your major interests in FlightGear?&lt;br /&gt;
* What project are you working on right now?&lt;br /&gt;
* What do you plan on doing in the future?&lt;br /&gt;
* Are you happy with the way the FlightGear project is going?&lt;br /&gt;
* What do you enjoy most about developing for FlightGear?&lt;br /&gt;
* Are there any &amp;quot;hidden features&amp;quot; you have worked on in FlightGear that new users may miss?&lt;br /&gt;
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?&lt;br /&gt;
&lt;br /&gt;
More questions are being collected here: [[Interview questions]].&lt;br /&gt;
&lt;br /&gt;
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX &lt;br /&gt;
&lt;br /&gt;
== Snapshot releases ==&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;t=10488&amp;amp;p=144233&amp;amp;hilit=snapshot#p144233 at the forum].&lt;br /&gt;
&lt;br /&gt;
== Translators required ==&lt;br /&gt;
{|&lt;br /&gt;
|[[File:en.gif]]&lt;br /&gt;
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:de.gif]]&lt;br /&gt;
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:nl.gif]]&lt;br /&gt;
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:es.gif]]&lt;br /&gt;
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Nasal for newbies ==&lt;br /&gt;
&lt;br /&gt;
== New software tools and projects ==&lt;br /&gt;
&lt;br /&gt;
== FlightGear addons and mods ==&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Updated aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Liveries ===&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
=== Airports ===&lt;br /&gt;
&lt;br /&gt;
== Aircraft of the month ==&lt;br /&gt;
== Airport of the month ==&lt;br /&gt;
== Screenshot of the month ==&lt;br /&gt;
&lt;br /&gt;
== Suggested flights ==&lt;br /&gt;
== Aircraft reviews ==&lt;br /&gt;
&lt;br /&gt;
== Wiki updates ==&lt;br /&gt;
===New articles===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=new&lt;br /&gt;
  count=10&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
===New aircraft articles===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=new&lt;br /&gt;
  count=10&lt;br /&gt;
  categoryRoot=Aircraft&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
===Most popular newsletters===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=hot&lt;br /&gt;
  count=5&lt;br /&gt;
  categoryRoot=FlightGear Newsletter&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
&lt;br /&gt;
=== New tutorials and screencasts ===&lt;br /&gt;
==== Cross-Country Tutorial II - a VFR guide ====&lt;br /&gt;
&lt;br /&gt;
[[File:Coverwiki2.jpg|300px|the cover]]&lt;br /&gt;
&lt;br /&gt;
This is a new tutorial and guide for V.F.R. opperations.&amp;lt;br /&amp;gt;&lt;br /&gt;
Get the download link for the latest version from the [http://flightgear.org/forums/viewtopic.php?f=72&amp;amp;t=19600 forum post] under the &amp;quot;Documentation&amp;quot; tab.&lt;br /&gt;
&lt;br /&gt;
=== Forum news ===&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
=== Virtual airlines ===&lt;br /&gt;
=== FlightGear events ===&lt;br /&gt;
&lt;br /&gt;
== Useful links ==&lt;br /&gt;
== And finally ... ==&lt;br /&gt;
=== Contributing ===&lt;br /&gt;
One of the regular thoughts expressed on the FlightGear forums is &amp;quot;I'd like to contribute but I don't know how to program, and I don't have the time&amp;quot;. 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. &lt;br /&gt;
&lt;br /&gt;
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].&lt;br /&gt;
&lt;br /&gt;
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&amp;amp;t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].&lt;br /&gt;
&lt;br /&gt;
=== Call for volunteers ===&lt;br /&gt;
* The [[Flightgear On Android]] team is looking for testers&lt;br /&gt;
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support&lt;br /&gt;
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.&lt;br /&gt;
&lt;br /&gt;
=== Did you know ===&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter]]&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2013&amp;diff=59371</id>
		<title>FlightGear Newsletter April 2013</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2013&amp;diff=59371"/>
		<updated>2013-04-04T12:02:23Z</updated>

		<summary type="html">&lt;p&gt;De profundis: /* Cross-Country Tutorial II - a VFR guide */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{newsletter}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
''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. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and the changelog of the upcoming release.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].&lt;br /&gt;
&lt;br /&gt;
=== Advanced Weather ===&lt;br /&gt;
&lt;br /&gt;
Advanced Weather's cloud placement algorithms are currently receiving a major overhaul. In reality, many scattered cloud layers form rather complex patterns on the sky. One strategy is to simply take pictures of these and project them as 2d clouds layers into the scene, which looks fine from the ground, but fails from close-up. Advanced Weather has always preferred to model as 3d clouds whatever can be modelled in 3d. However, this means that the intricate patterns need to be created by a suitable algorithm.&lt;br /&gt;
&lt;br /&gt;
So far, the first generation of placement algorithms have utilized rather simple geometries like grid patterns and random clusters. While this is usually not a major issue from the ground, it is quite apparent from high altitude - here is an example of a cloud distribution based on multiple clusters:&lt;br /&gt;
&lt;br /&gt;
[[File:Clouddist old.jpg|300px|Old algorithm results from 80.000 ft]]&lt;br /&gt;
&lt;br /&gt;
Second generation placement algorithms are based on more intricate semi-random patterns. These distribute clouds just in a different way (i.e. the result does not require higher rendering performance) and the placement algorithms are not even significantly more expensive computationally (perhaps 10% - the advantage all comes from smarter design) - yet they work much better approximating real cloud distributions.&lt;br /&gt;
&lt;br /&gt;
Here are the results for the same weather situation from 'stick bundle' and 'domains' - two of the new placement methods:&lt;br /&gt;
&lt;br /&gt;
[[File:Clouddist new1.jpg|300px|New algorithm results from 80.000 ft]]&lt;br /&gt;
[[File:Clouddist new2.jpg|300px|New algorithm results from the ground]]&lt;br /&gt;
&lt;br /&gt;
Cloud distributions appear much more natural and appealing, especially from high altitude. Work is in progress to replace 1st generation by 2nd generation algorithms in both the online and offline weather models of Advanced Weather.&lt;br /&gt;
&lt;br /&gt;
=== Random Buildings ===&lt;br /&gt;
&amp;lt;!-- These are currently just a bunch of placeholders for the latest projects (as of 08/2012)  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Project Rembrandt ===&lt;br /&gt;
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].&lt;br /&gt;
&lt;br /&gt;
=== Canvas System ===&lt;br /&gt;
&amp;lt;!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== High Level Architecture ===&lt;br /&gt;
=== FlightGear an Android ===&lt;br /&gt;
&lt;br /&gt;
=== Usability Improvements ===&lt;br /&gt;
&lt;br /&gt;
=== Mailing list digest ===&lt;br /&gt;
&lt;br /&gt;
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)&lt;br /&gt;
&lt;br /&gt;
=== Forum digest ===&lt;br /&gt;
&lt;br /&gt;
=== Git digest ===&lt;br /&gt;
&lt;br /&gt;
=== Getting involved as a programmer ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Howto:Start core development]]&lt;br /&gt;
&lt;br /&gt;
== Release ChangeLog ==&lt;br /&gt;
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.&lt;br /&gt;
&lt;br /&gt;
== Interview with a contributor (NAME) ==&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* How long have you been involved in FlightGear?&lt;br /&gt;
* What are your major interests in FlightGear?&lt;br /&gt;
* What project are you working on right now?&lt;br /&gt;
* What do you plan on doing in the future?&lt;br /&gt;
* Are you happy with the way the FlightGear project is going?&lt;br /&gt;
* What do you enjoy most about developing for FlightGear?&lt;br /&gt;
* Are there any &amp;quot;hidden features&amp;quot; you have worked on in FlightGear that new users may miss?&lt;br /&gt;
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?&lt;br /&gt;
&lt;br /&gt;
More questions are being collected here: [[Interview questions]].&lt;br /&gt;
&lt;br /&gt;
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX &lt;br /&gt;
&lt;br /&gt;
== Snapshot releases ==&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;t=10488&amp;amp;p=144233&amp;amp;hilit=snapshot#p144233 at the forum].&lt;br /&gt;
&lt;br /&gt;
== Translators required ==&lt;br /&gt;
{|&lt;br /&gt;
|[[File:en.gif]]&lt;br /&gt;
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:de.gif]]&lt;br /&gt;
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:nl.gif]]&lt;br /&gt;
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:es.gif]]&lt;br /&gt;
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Nasal for newbies ==&lt;br /&gt;
&lt;br /&gt;
== New software tools and projects ==&lt;br /&gt;
&lt;br /&gt;
== FlightGear addons and mods ==&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Updated aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Liveries ===&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
=== Airports ===&lt;br /&gt;
&lt;br /&gt;
== Aircraft of the month ==&lt;br /&gt;
== Airport of the month ==&lt;br /&gt;
== Screenshot of the month ==&lt;br /&gt;
&lt;br /&gt;
== Suggested flights ==&lt;br /&gt;
== Aircraft reviews ==&lt;br /&gt;
&lt;br /&gt;
== Wiki updates ==&lt;br /&gt;
===New articles===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=new&lt;br /&gt;
  count=10&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
===New aircraft articles===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=new&lt;br /&gt;
  count=10&lt;br /&gt;
  categoryRoot=Aircraft&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
===Most popular newsletters===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=hot&lt;br /&gt;
  count=5&lt;br /&gt;
  categoryRoot=FlightGear Newsletter&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
&lt;br /&gt;
=== New tutorials and screencasts ===&lt;br /&gt;
==== Cross-Country Tutorial II - a VFR guide ====&lt;br /&gt;
&lt;br /&gt;
[[File:Coverwiki2.jpg|thumb|the cover]]&lt;br /&gt;
&lt;br /&gt;
This is a new tutorial and guide for V.F.R. opperations.&amp;lt;br /&amp;gt;&lt;br /&gt;
Get the download link for the latest version from the [http://flightgear.org/forums/viewtopic.php?f=72&amp;amp;t=19600 forum post] under the &amp;quot;Documentation&amp;quot; tab:&lt;br /&gt;
&lt;br /&gt;
=== Forum news ===&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
=== Virtual airlines ===&lt;br /&gt;
=== FlightGear events ===&lt;br /&gt;
&lt;br /&gt;
== Useful links ==&lt;br /&gt;
== And finally ... ==&lt;br /&gt;
=== Contributing ===&lt;br /&gt;
One of the regular thoughts expressed on the FlightGear forums is &amp;quot;I'd like to contribute but I don't know how to program, and I don't have the time&amp;quot;. 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. &lt;br /&gt;
&lt;br /&gt;
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].&lt;br /&gt;
&lt;br /&gt;
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&amp;amp;t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].&lt;br /&gt;
&lt;br /&gt;
=== Call for volunteers ===&lt;br /&gt;
* The [[Flightgear On Android]] team is looking for testers&lt;br /&gt;
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support&lt;br /&gt;
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.&lt;br /&gt;
&lt;br /&gt;
=== Did you know ===&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter]]&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:Coverwiki2.jpg&amp;diff=59370</id>
		<title>File:Coverwiki2.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:Coverwiki2.jpg&amp;diff=59370"/>
		<updated>2013-04-04T12:00:38Z</updated>

		<summary type="html">&lt;p&gt;De profundis: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=the cover of &amp;quot;Cross Country Tutorial II&amp;quot;}}&lt;br /&gt;
|date=2013-04-04&lt;br /&gt;
|source={{own}}&lt;br /&gt;
|author=[[User:De profundis|De profundis]]&lt;br /&gt;
|permission=&lt;br /&gt;
|other_versions=&lt;br /&gt;
|other_fields=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{self|cc-by-sa-3.0}}&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2013&amp;diff=59369</id>
		<title>FlightGear Newsletter April 2013</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2013&amp;diff=59369"/>
		<updated>2013-04-04T11:42:25Z</updated>

		<summary type="html">&lt;p&gt;De profundis: /* New tutorials and screencasts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{newsletter}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
''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. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and the changelog of the upcoming release.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].&lt;br /&gt;
&lt;br /&gt;
=== Advanced Weather ===&lt;br /&gt;
&lt;br /&gt;
Advanced Weather's cloud placement algorithms are currently receiving a major overhaul. In reality, many scattered cloud layers form rather complex patterns on the sky. One strategy is to simply take pictures of these and project them as 2d clouds layers into the scene, which looks fine from the ground, but fails from close-up. Advanced Weather has always preferred to model as 3d clouds whatever can be modelled in 3d. However, this means that the intricate patterns need to be created by a suitable algorithm.&lt;br /&gt;
&lt;br /&gt;
So far, the first generation of placement algorithms have utilized rather simple geometries like grid patterns and random clusters. While this is usually not a major issue from the ground, it is quite apparent from high altitude - here is an example of a cloud distribution based on multiple clusters:&lt;br /&gt;
&lt;br /&gt;
[[File:Clouddist old.jpg|300px|Old algorithm results from 80.000 ft]]&lt;br /&gt;
&lt;br /&gt;
Second generation placement algorithms are based on more intricate semi-random patterns. These distribute clouds just in a different way (i.e. the result does not require higher rendering performance) and the placement algorithms are not even significantly more expensive computationally (perhaps 10% - the advantage all comes from smarter design) - yet they work much better approximating real cloud distributions.&lt;br /&gt;
&lt;br /&gt;
Here are the results for the same weather situation from 'stick bundle' and 'domains' - two of the new placement methods:&lt;br /&gt;
&lt;br /&gt;
[[File:Clouddist new1.jpg|300px|New algorithm results from 80.000 ft]]&lt;br /&gt;
[[File:Clouddist new2.jpg|300px|New algorithm results from the ground]]&lt;br /&gt;
&lt;br /&gt;
Cloud distributions appear much more natural and appealing, especially from high altitude. Work is in progress to replace 1st generation by 2nd generation algorithms in both the online and offline weather models of Advanced Weather.&lt;br /&gt;
&lt;br /&gt;
=== Random Buildings ===&lt;br /&gt;
&amp;lt;!-- These are currently just a bunch of placeholders for the latest projects (as of 08/2012)  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Project Rembrandt ===&lt;br /&gt;
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].&lt;br /&gt;
&lt;br /&gt;
=== Canvas System ===&lt;br /&gt;
&amp;lt;!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== High Level Architecture ===&lt;br /&gt;
=== FlightGear an Android ===&lt;br /&gt;
&lt;br /&gt;
=== Usability Improvements ===&lt;br /&gt;
&lt;br /&gt;
=== Mailing list digest ===&lt;br /&gt;
&lt;br /&gt;
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)&lt;br /&gt;
&lt;br /&gt;
=== Forum digest ===&lt;br /&gt;
&lt;br /&gt;
=== Git digest ===&lt;br /&gt;
&lt;br /&gt;
=== Getting involved as a programmer ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Howto:Start core development]]&lt;br /&gt;
&lt;br /&gt;
== Release ChangeLog ==&lt;br /&gt;
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.&lt;br /&gt;
&lt;br /&gt;
== Interview with a contributor (NAME) ==&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* How long have you been involved in FlightGear?&lt;br /&gt;
* What are your major interests in FlightGear?&lt;br /&gt;
* What project are you working on right now?&lt;br /&gt;
* What do you plan on doing in the future?&lt;br /&gt;
* Are you happy with the way the FlightGear project is going?&lt;br /&gt;
* What do you enjoy most about developing for FlightGear?&lt;br /&gt;
* Are there any &amp;quot;hidden features&amp;quot; you have worked on in FlightGear that new users may miss?&lt;br /&gt;
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?&lt;br /&gt;
&lt;br /&gt;
More questions are being collected here: [[Interview questions]].&lt;br /&gt;
&lt;br /&gt;
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX &lt;br /&gt;
&lt;br /&gt;
== Snapshot releases ==&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;t=10488&amp;amp;p=144233&amp;amp;hilit=snapshot#p144233 at the forum].&lt;br /&gt;
&lt;br /&gt;
== Translators required ==&lt;br /&gt;
{|&lt;br /&gt;
|[[File:en.gif]]&lt;br /&gt;
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:de.gif]]&lt;br /&gt;
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
|[[File:nl.gif]]&lt;br /&gt;
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
|[[File:es.gif]]&lt;br /&gt;
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Nasal for newbies ==&lt;br /&gt;
&lt;br /&gt;
== New software tools and projects ==&lt;br /&gt;
&lt;br /&gt;
== FlightGear addons and mods ==&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&lt;br /&gt;
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&amp;amp;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.&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Updated aircraft ===&lt;br /&gt;
&lt;br /&gt;
=== Liveries ===&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
=== Airports ===&lt;br /&gt;
&lt;br /&gt;
== Aircraft of the month ==&lt;br /&gt;
== Airport of the month ==&lt;br /&gt;
== Screenshot of the month ==&lt;br /&gt;
&lt;br /&gt;
== Suggested flights ==&lt;br /&gt;
== Aircraft reviews ==&lt;br /&gt;
&lt;br /&gt;
== Wiki updates ==&lt;br /&gt;
===New articles===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=new&lt;br /&gt;
  count=10&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
===New aircraft articles===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=new&lt;br /&gt;
  count=10&lt;br /&gt;
  categoryRoot=Aircraft&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
===Most popular newsletters===&lt;br /&gt;
&amp;lt;DynamicArticleList&amp;gt;&lt;br /&gt;
  type=hot&lt;br /&gt;
  count=5&lt;br /&gt;
  categoryRoot=FlightGear Newsletter&lt;br /&gt;
&amp;lt;/DynamicArticleList&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
&lt;br /&gt;
=== New tutorials and screencasts ===&lt;br /&gt;
==== Cross-Country Tutorial II - a VFR guide ====&lt;br /&gt;
&lt;br /&gt;
This is a new tutorial and guide for V.F.R. opperations.&amp;lt;br /&amp;gt;&lt;br /&gt;
Get the download link for the latest version from the [http://flightgear.org/forums/viewtopic.php?f=72&amp;amp;t=19600 forum post] under the &amp;quot;Documentation&amp;quot; tab:&lt;br /&gt;
&lt;br /&gt;
=== Forum news ===&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
=== Virtual airlines ===&lt;br /&gt;
=== FlightGear events ===&lt;br /&gt;
&lt;br /&gt;
== Useful links ==&lt;br /&gt;
== And finally ... ==&lt;br /&gt;
=== Contributing ===&lt;br /&gt;
One of the regular thoughts expressed on the FlightGear forums is &amp;quot;I'd like to contribute but I don't know how to program, and I don't have the time&amp;quot;. 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. &lt;br /&gt;
&lt;br /&gt;
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].&lt;br /&gt;
&lt;br /&gt;
To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&amp;amp;t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].&lt;br /&gt;
&lt;br /&gt;
=== Call for volunteers ===&lt;br /&gt;
* The [[Flightgear On Android]] team is looking for testers&lt;br /&gt;
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support&lt;br /&gt;
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.&lt;br /&gt;
&lt;br /&gt;
=== Did you know ===&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter]]&lt;/div&gt;</summary>
		<author><name>De profundis</name></author>
	</entry>
</feed>