<?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=Airbus330</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=Airbus330"/>
	<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/Special:Contributions/Airbus330"/>
	<updated>2026-04-19T06:17:28Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.6</generator>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76949</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76949"/>
		<updated>2014-10-04T02:55:53Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= A300F.png&lt;br /&gt;
|alt            = An A300F landing&lt;br /&gt;
|image2         = A300-600 Flightdeck.png&lt;br /&gt;
|alt2           = Flightdeck (originaly from the [[Airbus A300-600ST|A300-600ST]])&lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 1&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 3&lt;br /&gt;
|status-model	= 3&lt;br /&gt;
|fgname 	= A300-603, A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences and a two-crew (first ever), glass cockpit.&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, it is recommended to set your target vertical speed, altitude and speed while taxiing, these can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, this engages V/S mode and a basic &amp;quot;Wing leveler&amp;quot;.  &lt;br /&gt;
The HOLD button engages Heading mode and sets the the target heading to your current heading (so it is useless to preset a heading value).&lt;br /&gt;
Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending.&lt;br /&gt;
&lt;br /&gt;
Also note that V/S mode does not currently disengage when you reach your target altitude, so you need to watch that.&lt;br /&gt;
&lt;br /&gt;
Autothrust is pretty standard, the A/THR button toggles the function, and the knob sets target speed.&lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engage Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mode will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596 A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76766</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76766"/>
		<updated>2014-09-27T09:20:23Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: /* Autopilot help */ Updated AP helt&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= A300F.png&lt;br /&gt;
|alt            = An A300F landing&lt;br /&gt;
|image2         = A300-600 Flightdeck.png&lt;br /&gt;
|alt2           = Flightdeck (originaly from the [[Airbus A300-600ST|A300-600ST]])&lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 2&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 4&lt;br /&gt;
|status-model	= 4&lt;br /&gt;
|fgname 	= A300-603, A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences and a two-crew (first ever), glass cockpit.&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, it is recommended to set your target vertical speed, altitude and speed while taxiing, these can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, this engages V/S mode and a basic &amp;quot;Wing leveler&amp;quot;.  &lt;br /&gt;
The HOLD button engages Heading mode and sets the the target heading to your current heading (so it is useless to preset a heading value).&lt;br /&gt;
Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending.&lt;br /&gt;
&lt;br /&gt;
Also note that V/S mode does not currently disengage when you reach your target altitude, so you need to watch that.&lt;br /&gt;
&lt;br /&gt;
Autothrust is pretty standard, the A/THR button toggles the function, and the knob sets target speed.&lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engage Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mode will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596 A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_September_2014&amp;diff=76543</id>
		<title>FlightGear Newsletter September 2014</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_September_2014&amp;diff=76543"/>
		<updated>2014-09-18T23:06:28Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: /* In the Hangar */ Linked A300 title to page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Newsletter-header|September 2014}}&lt;br /&gt;
&amp;lt;div style=&amp;quot;border-bottom:3px double #BBB;&amp;quot;&amp;gt;&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot; |&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; width=&amp;quot;33%&amp;quot; |&lt;br /&gt;
{{Newsletter-cover-item|FlightGear 3.2 released (this time for real!)}}&amp;lt;br/&amp;gt;&lt;br /&gt;
{{Newsletter-cover-item|DDS feedback needed}}&amp;lt;br/&amp;gt;&lt;br /&gt;
{{Newsletter-cover-item|Aircraft moved to SVN}}&amp;lt;br/&amp;gt;&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; width=&amp;quot;33%&amp;quot; |&lt;br /&gt;
{{Newsletter-cover-item|Performance issues}}&amp;lt;br/&amp;gt;&lt;br /&gt;
{{Newsletter-cover-item|The hidden Map}}&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; width=&amp;quot;33%&amp;quot; |&lt;br /&gt;
{{Newsletter-cover-item|Interview with a contributor}}&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== DDS feedback needed ==&lt;br /&gt;
&lt;br /&gt;
We are looking for feedback about possibly adopting DDS textures in FlightGear. There are several advantages in doing so:&lt;br /&gt;
&lt;br /&gt;
* DDS is a more compact format than png, hence the download size of the FG base package may be decreased&lt;br /&gt;
* Compressed DDS can be directly used by many graphics cards, reducing also GPU memory consumption&lt;br /&gt;
* DDS stores all texture resolution levels, i.e. no lower resolution levels have to be generated when the texture is used, hence it loads much faster into memory&lt;br /&gt;
* The resolution levels ('mipmaps') can be customized, allowing for some interesting effects at no performance cost&lt;br /&gt;
&lt;br /&gt;
Practically all commercial simulations use DDS for these reasons. &lt;br /&gt;
&lt;br /&gt;
However, the DDS compression algorithm is patented, which means that it is not readily available for open source graphics drivers used by most 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Continue reading at [[Switching default texture format to DDS]]...&lt;br /&gt;
&lt;br /&gt;
== Aircraft moved to SVN ==&lt;br /&gt;
Some months ago we decided to host our aircraft on an SVN repository in order to relieve &amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt;.&lt;br /&gt;
The &amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt; repo would be a mirror of the base package.&lt;br /&gt;
&lt;br /&gt;
We finally moved all our aircraft to '''the new SVN repo''': http://sourceforge.net/p/flightgear/fgaddon/&lt;br /&gt;
&lt;br /&gt;
This repository is named &amp;quot;FGAddon&amp;quot; because its content is not required to run FlightGear but provides a new feature (aircraft in this case); this is usually called an &amp;quot;addon&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Advantages ===&lt;br /&gt;
On the user side, the most important feature is to be able to checkout only desired aircraft, as you no longer need to download the 400+ aircraft at once.&lt;br /&gt;
&lt;br /&gt;
On the developer side, the most important interest is to have a base package (&amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt;) which is lighter to sync for new contributors and easier to keep up to date.&lt;br /&gt;
&lt;br /&gt;
=== A mini HowTo ===&lt;br /&gt;
* For Windows:  Install TortoiseSVN (http://tortoisesvn.net/) &lt;br /&gt;
* For Linux/Mac:  Install SVN&lt;br /&gt;
&lt;br /&gt;
Then to fetch an aircraft (in this example we pick up the [[Robin DR400 Dauphin|DR400 Dauphin]]):&lt;br /&gt;
 svn co https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/DR400-dauphin&lt;br /&gt;
&lt;br /&gt;
Then you can regularly fetch the latest updates with&lt;br /&gt;
 svn up&lt;br /&gt;
&lt;br /&gt;
If you are used to use Git, &amp;lt;code&amp;gt;svn co&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;svn up&amp;lt;/code&amp;gt; are similar to &amp;lt;code&amp;gt;git clone&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;git pull&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The aircraft will remain in the &amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt; Git repository for a few months, until everyone has transitioned to the SVN repositories.&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
For our aircraft developers who don't regularly read the mailing list (even though any aircraft developers should already be subscribed), please read this topic: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/DUB127-W168600DE27B42094E5263EC3C10%40phx.gbl/#msg3280971&lt;br /&gt;
&lt;br /&gt;
== Using Ada in FlightGear ==&lt;br /&gt;
[[File:FlightGear built using gnatmake.png|thumb|FlightGear built with optional support for Ada]]&lt;br /&gt;
&lt;br /&gt;
Recently, we've had an interesting discussion on the forum where some of FlightGear's threading issues were discussed, and a few contributors mentioned that Ada would have better tasking support than C++ because C++ support for tasking/multi-threading is generally considered fairly &amp;quot;low-level&amp;quot;. Other programming languages, like Ada, provide native support for multi-threading using built-in primitives like '''tasks''' and '''protected types'''.&lt;br /&gt;
&lt;br /&gt;
Meanwhile, a few contributors have teamed up to explore using Ada in FlightGear to make some experiments.&lt;br /&gt;
&lt;br /&gt;
We're hoping to document the steps required to extend our [[Developing using CMake|CMake build system]] to support optional modules implemented in Ada as discussed by onox, Flying toaster and Hooray on the forum, including support for mapping existing C++ classes to Ada (e.g. from OSG and/or OpenRTI).&lt;br /&gt;
&lt;br /&gt;
The main goal being here to leverage Ada's native tasking support for prototyping optional features that do not have to be running in the FlightGear main loop. &lt;br /&gt;
&lt;br /&gt;
We've already found some existing CMake modules that we can reuse: The [http://plplot.sourceforge.net/ PLPlot project] is implemented using C, C++ and Ada and provides a set of CMake modules that are scheduled to be merged into CMake soon.&lt;br /&gt;
&lt;br /&gt;
Hooray has copied those files into a branch of $FG_SRC and ended up with a working build environment that successfully links in Ada modules. For starters, we'll be playing with optionally allowing [[Howto:Add new fgcommands to FlightGear|fgcommands]] to be implemented in Ada, as well as new [[Howto:Create new subsystems|SGsubsystems]].&lt;br /&gt;
&lt;br /&gt;
Next, we'll be exploring how to add thin bindings using '''-fdump-ada-spec''' for existing SimGear/OpenRTI (HLA) headers and document the whole process on the wiki.&lt;br /&gt;
&lt;br /&gt;
Using -fdump-ada-specc to create bindings for SG/HLA classes to create standalone HLA federates in Ada would make FG pretty compelling for anybody doing this kind of thing professionally, because Ada simply happens to be widely used in the aviation industry, and it seems there are even bindings of complex stuff like OSG available.&lt;br /&gt;
&lt;br /&gt;
To learn more, please see [[Using Ada in FlightGear]]&lt;br /&gt;
&lt;br /&gt;
== Performance Issues ==&lt;br /&gt;
Several FlightGear users have pointed out inexplicable &amp;quot;slowness&amp;quot; that originally seemed related to the property rules subsystem - which is a subsystem that Torsten originally wrote/ported, so he investigated a little and managed to track this down to a pretty serious bug in the effects subsystem that may end up registering thousands of identical listeners, despite effects/shaders not even being in use necessarily. &lt;br /&gt;
&lt;br /&gt;
So the property rules code wasn't even the culprit but obviously it deals with properties, so easy to mis-identify as the troublemaker. &lt;br /&gt;
&lt;br /&gt;
As some of you may know from working with Nasal code: listeners are not in and of themselves expensive, but running identical listeners over and over again each frame is getting unnecessarily expensive quickly. This doesn't just apply to scripting space, but also to C++ space - here, it's the sheer performance offered by native C++ code that makes it much harder to identify such problems, because code that would bring the simulator down to its knees in Nasal may very well still be &amp;quot;fast enough&amp;quot; for most people with fast computers, despite being still very much &amp;quot;broken&amp;quot;, and plain wrong.&lt;br /&gt;
&lt;br /&gt;
As can be seen on the devel list, Torsten has been spending the last weeks troubleshooting the effects system, which isn't exactly straightforward because its original developer is not currently involved in FlightGear, and the code is pretty sophisticated and even multi-threaded (which means that parts of the code may be running concurrently on different CPUs) - however, Torsten did report pretty significant performance improvements recently - he's just pushed his work to a new branch so that other developers (and people building from source!) can have a look and test his changes and report feedback/issues - this will probably mean that it may take a few weeks until all the feedback has come in and implemented - but performance should be improved significantly by then - which also addresses the whole &amp;quot;when will 3.2 be released&amp;quot; question. Meanwhile, Stuart has joined Torsten to help with fixing the bug:&lt;br /&gt;
&lt;br /&gt;
{{FGCquote&lt;br /&gt;
  |Acutally, Stuart is working on this and has improved the UniformCache I started with. He has a much better insight in the Effect system than I do.&lt;br /&gt;
His work is much better than mine but still has some breakage for existing shaders, most prominent one is ALS.&lt;br /&gt;
We are still investigating whats going on there and I have to ask for just some more patience.&amp;lt;br/&amp;gt;&lt;br /&gt;
Torsten&lt;br /&gt;
  |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32846172/&lt;br /&gt;
     |title=&amp;lt;nowiki&amp;gt;Re: [Flightgear-devel] crash in SGPropertyNode::fireValueChanged&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
     |author=&amp;lt;nowiki&amp;gt;Torsten Dreyer&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
     |date=&amp;lt;nowiki&amp;gt;2014-09-18&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
   }}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Also, Hooray recently built fg on a dual-core netbook with Intel GMA graphics (1gb RAM) to see if/how well Canvas is supported there (some people reported white RTTs due to lack of FBO support) - it is true that doing this more regularly would probably help identify certain issues much earlier - it seems that a few contributors are still trying to spin up FG once in a while on their old computers - Thorsten repeatedly mentioned doing that for regression testing purposes when testing his own work. &lt;br /&gt;
&lt;br /&gt;
But FG would indeed be in a better shape if had some way to do this more often, possibly automatically on some kind of headless build/regression testing server - which kinda is what a few people have been working towards:&lt;br /&gt;
&lt;br /&gt;
* [[FlightGear Headless|Running FlightGear headless]] (i.e. without a window, used for subsystem performance testing)&lt;br /&gt;
&lt;br /&gt;
* [[Testing|Testing Performance]]&lt;br /&gt;
&lt;br /&gt;
Things like the recently discovered listener issue in the effects subsystem or massive memory leaks would stand less of a chance of going unnoticed if we had more people testing FG on old hardware - but it's a chicken/egg problem because you need to be pretty familiar with FG to make it work at all, so most people don't bother - and as a coder you tend to prefer writing code over testing obviously, so given the lack of feedback, FG is leaning more towards power users with the latest GPUs and 1+ gb of VRAM unfortunately - simply because that's where all the testing manpower typically is.&lt;br /&gt;
&lt;br /&gt;
People wanting to change that, need to roll up their sleeves and get involved, and PLEAE provide feedback.&lt;br /&gt;
&lt;br /&gt;
'''All''' testing on, and development for, such systems would benefit FG in the long term, because hardware support/compatibility would increase over time - which would also make it possible to target other architectures, i.e. gaming hardware, Rasberry Pi and so on: [[Howto:Optimizing FlightGear for mobile devices]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And here some initial observations based on running FlightGear on an underpowered Netbook with integrated Intel GMA graphics:&lt;br /&gt;
&lt;br /&gt;
* our existing GUI truly sucks: whenever a PUI dialog is opened, the frame rate is becoming single-digit&lt;br /&gt;
* once the dialog is closed, it will spike up to ~30 fps, with the Canvas/REPL window still shown (!)&lt;br /&gt;
* hiding the PUI menubar further helps increase frame rate and improve frame spacing&lt;br /&gt;
* hiding the menubar AND closing the REPL dialog, I am getting ~45-50 fps using the minimal startup profile, frame spacing is then roughly in the 60s&lt;br /&gt;
* the navcache is a huge resource hog for people on such systems - initializinig/rebuilding the cache is taking ages (10-20+ minutes here !)&lt;br /&gt;
* it would make sense to refactor the navcache and turn it into a library, so that we can prebuild the navcache - and either do so while packaging a release, or alternatively, during installation (plenty of time there!)&lt;br /&gt;
* in addition, threading would make sense probably, when the navcache was being rebuilt, the 2nd core was idling all the time while 1 core was at 100%&lt;br /&gt;
* Canvas/RTT (FBOs) actually work here (which is a good thing for FGPanel/FGCanvas usage)&lt;br /&gt;
* there are a bunch of default options that will &amp;quot;break&amp;quot; FG for users on such systems, including a number of options that will trigger OpenGL/OSG errors early on&lt;br /&gt;
&lt;br /&gt;
Hooray is hoping to do further testing, using the system monitor and the built-in profiler - keep in mind that this still is the code that contains some pretty severe performance bugs.&lt;br /&gt;
&lt;br /&gt;
If we had more people doing this kind of testing, we could definitely identify, and hopefully eliminate, quite a few performance issues that would not be noticeable on a typical developer's machine.&lt;br /&gt;
So this could be a worthwhile thing to do, and it would help FG in the long term - i.e. even benefit power users who have 2048 MB of VRAM and 8 cores/12 gb of RAM.&lt;br /&gt;
&lt;br /&gt;
The really interesting &amp;quot;benchmark&amp;quot; here is running osgviewer and fgviewer as comparison, because what FG is doing here isn't much different functionality-wise, and it's using the same technology stack (i.e. OSG), so should provide similar performance.&lt;br /&gt;
&lt;br /&gt;
Unofortunately, we generally don't have many people who do a lot of testing, troubleshooting - or even just provide feedback via the issue tracker - it is definitely true that the Canvas GUI is much faster here, despite containing a ton MORE Nasal code, and despite being MUCH more dynamic/flexible than our existing PUI dialogs.&lt;br /&gt;
&lt;br /&gt;
It would really be awesome to find a handful of people with access to old/slow hardware interested in testing and maybe troubleshooting things - while it would be great if those people knew how to build from source, and how to use git/gitorious, I don't think that's even necessary - we can definitely provide a lot of infrastructure and advice, but most of us don't typically have access to these kinds of computers. And while some of us admittedly aren't bothered by it, it is very true that FlightGear as a whole will benefit from teasing out certain bugs/issues, no matter if those are slowing things down due to CPU/GPU or RAM/VRAM utilization.&lt;br /&gt;
&lt;br /&gt;
But we really need more people willing to do this kind of testing and who can provide feedback regularly - and start yelling once something that previously worked, stops working or is becoming unnecessarily slow - there are a bunch of issues that should have never made it into the code, but which went unnoticed for months (or even years), because it's really only power users/contributors and developers who do this kind of testing, and as I am seeing right now, certain issues are pretty well &amp;quot;masked&amp;quot; on an 8-core, 10 gb, 2gb VRAM machine obviously ...&lt;br /&gt;
&lt;br /&gt;
We've been hoping to create some kind of &amp;quot;benchmark&amp;quot; for years - and this is one of those things that would truly help FlightGear in the long term, because we'd get quantifiable data over time, so that we can easily tell how a certain startup/run-time feature behaves in correlation with how it behaved previously, i.e. compared to updated dependencies (OpenAL, PLIB, OSG) - but also changes to the C++ code in SG/FG itself.&lt;br /&gt;
&lt;br /&gt;
People are generally quick to point at Nasal and its known GC issues, but are usually not experienced enough to look behind the scenes, and the amount of existing C++ code that is doing things in a slow fashion, code that's been lurking in the source tree for years more often than not. Creating some kind of simple benchmark would help all of us, no matter the kind of hardware we have: [[FlightGear_Benchmark]].&lt;br /&gt;
&lt;br /&gt;
If you're interested in getting involved with testing FlightGear and improving compatibility for older/slow systems, please get in touch with Hooray on the forum.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery mode=packed widths=230px heights=230px&amp;gt;&lt;br /&gt;
Fgfs 3.2 on a dual-core netbook.png|FlightGear 3.2/Canvas working on a dual-core Netbook with Intel GMA graphics showing the [[Interactive Nasal Console]] dialog&lt;br /&gt;
Comparing Native Canvas GUI Performance over PUI.png|A native [[Canvas]] window showing the new [[Aircraft Center]] dialog (good performance)&lt;br /&gt;
System-monitor-on-netbook.png|Screen shot showing a number of performance issues in a handful of FG subsystems, especially the PUI GUI&lt;br /&gt;
Pui slowness.png|The old PLIB/PUI GUI is shown here rendering a Canvas Widget with a [[MapStructure]] layer, a few users have reported that PUI is significantly slowing down the simulator&lt;br /&gt;
MapStructure self test over embedded PUI widget.png|And for comparison a native Canvas window also using the [[MapStructure]] framework,without going through PUI (better performance)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The hidden Map ==&lt;br /&gt;
[[File:FlightGear-Map-on-Android.png|right|400px]]&lt;br /&gt;
Did you know that FlightGear has an internal web server? And did you ever ask yourself the question, what does a flight simulator needs a web server for? A nice and impressive use case is a map application that has just been brought to the main menu. Click on &amp;quot;Equipment&amp;quot; and select &amp;quot;Map (opens in browser)&amp;quot;. Your web browser will pop up and show a map based on current web standards. It can display OpenStreetMap maps as a base layer as well as satelite image or roads from MapQuest. Overlays for current (real) weather like precipitation and isobares exist. The map can display FlightGear internal navigation data like airports, navaids etc. And it can display AI traffic and multiplayer aircraft, too.&lt;br /&gt;
Of course, it runs on any decent browser, but not only the one on your FlightGear computer. It is web-app-capable so you can install it to your mobile device (IOS and Android) to have a full screen map App on your tablet or phone displaying your current FlightGear status. All this at almost zero cost for the FlightGear main loop. All the rendering computations are done within your browser. The FlightGear webserver only provides the HTML and JavaScript files and transmits the internal properties over a websocket.&lt;br /&gt;
To enable the internal browser-based map, you need to enable the internal web server by adding &amp;lt;code&amp;gt;--httpd=8080&amp;lt;/code&amp;gt; to your command line.&lt;br /&gt;
Consult your mobile devices operation manual about how to add a web page as a full screen App.&lt;br /&gt;
&lt;br /&gt;
== Learning Canvas using Copy &amp;amp; Paste ==&lt;br /&gt;
Given that we still have aircraft developers who consider [[Canvas]] programming too 'inaccessible', we've started a dedicate wiki article for gathering useful Canvas snippets - early Canvas adopters are obviously invited to help grow this library of snippets over time to turn this into a useful repository for all people wanting to do Canvas development in some shape or form. For starters, here's a simple snippet creating a GUI dialog: &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Screenshot !! Code !! &lt;br /&gt;
|-&lt;br /&gt;
| [[File:Snippets-canvas-dialog.png|left|thumb|This is what the [[Nasal]]/[[Canvas]] snippet will look like once you pasted it into the [[Nasal Console]] and click &amp;quot;Execute&amp;quot;.]] || {{Note|This example uses so called method chaining, if you're not familiar with the concept, please see: [[Object_Oriented_Programming_with_Nasal#More_on_methods:_Chaining|Method Chaining]].}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;nasal&amp;quot; enclose=&amp;quot;div&amp;quot;&amp;gt;&lt;br /&gt;
# create a new window, dimensions are 320 x 160, using the dialog decoration (i.e. titlebar)&lt;br /&gt;
var window = canvas.Window.new([320,160],&amp;quot;dialog&amp;quot;);&lt;br /&gt;
&lt;br /&gt;
# adding a canvas to the new window and setting up background colors/transparency&lt;br /&gt;
var myCanvas = window.createCanvas().set(&amp;quot;background&amp;quot;, canvas.style.getColor(&amp;quot;bg_color&amp;quot;));&lt;br /&gt;
&lt;br /&gt;
# Using specific css colors would also be possible:&lt;br /&gt;
# myCanvas.set(&amp;quot;background&amp;quot;, &amp;quot;#ffaac0&amp;quot;);&lt;br /&gt;
&lt;br /&gt;
# creating the top-level/root group which will contain all other elements/group&lt;br /&gt;
var root = myCanvas.createGroup();&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
See: [[Canvas Snippets]]&lt;br /&gt;
== Dynamic Liveries via Canvas / Proof of Concept: Exhaust dirt==&lt;br /&gt;
''by [[User:Algernon|Algernon]] ([[User talk:Algernon|talk]]) 17:09, 17 September 2014 (UTC) ''&lt;br /&gt;
&lt;br /&gt;
To document the implementation on a FlightGear aircraft from the aircraft developer's point of view, I've chosen one of my pet projects, the Eurofighter EF2000 V2.0 which will be released in early 2015.&lt;br /&gt;
The intention is to use Canvas to allow multiple textures per livery, in this case those textures being the original livery paintwork and another, alpha-transparent texture consisting of dirt streaks specifically added to the livery paintwork to match with vents, seams and other sources of grimy build-ups. The intention is to allow dynamic management of the transparency of the dirt layer according to time and exposure to various elements, maintaining compatibility with the standard livery switching method and working similarly whether Rembrandt is enabled or not. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery mode=&amp;quot;packed&amp;quot;&amp;gt;&lt;br /&gt;
Two-layers.jpg|The two textures concerned, the ASG paintwork and the separate alpha transparency with dirt streaks&lt;br /&gt;
Dynamic-Textures-First-Try.jpg|A first (failed) attempt to put a canvas onto a model object in place of its texture.&lt;br /&gt;
Ef2000dyn1.jpg|The EF2000 showing a dynamically-changed texture on the fuselage - at the moment, the resolution appears to be wrong and the UV coordinates seem to be being ignored.&lt;br /&gt;
File:Ef2000dyn2.jpg|Changing the dialog window size to be the same size as the texture fixed the issue - note that the fuselage sections are free of dirt (except the APU exhaust smudge, which is a special case) where as the wings and tail have integral dirt in the texture.&lt;br /&gt;
File:Ef2000dyn3.jpg|A full-screen illustration using the updated Canvas code to make the canvas independent of the window, but with the window still displaying the canvas. Here, only the base &amp;quot;clean&amp;quot; paintwork texture is added to the fuselage element.&lt;br /&gt;
File:Ef2000dyn4.jpg|After creating a canvas with the base &amp;quot;clean&amp;quot; paintwork texture, another child is added containing the dirt layer transparency. The effect is seen both in the dialog window and on the airframe.&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To learn more, see [[Howto:Dynamic Liveries via Canvas]]&lt;br /&gt;
&lt;br /&gt;
== Interview with a contributor ==&lt;br /&gt;
&lt;br /&gt;
This month, the interview comes back. Hey everyone, I'm ZLSA. I've used FlightGear for a while now, but I only got into the development side recently.&lt;br /&gt;
&lt;br /&gt;
Um, I'm supposed to ask ''myself'' questions? Wait, nobody said I'd have to ask ''myself'' questions.&lt;br /&gt;
&lt;br /&gt;
'''What is your forum nickname, ZLSA?''' ZLSA.&lt;br /&gt;
&lt;br /&gt;
'''How long have you been involved with FlightGear?''' The first version I used was 1.9.1, I think. So circa 2008?&lt;br /&gt;
&lt;br /&gt;
'''What are your major interests in FlightGear?''' Well, I like 3d modeling and I'm rather good at it. Do you think I'm good at 3d modeling?&lt;br /&gt;
&lt;br /&gt;
'''I think you're pretty good at it.''' So my primary interest in FlightGear is modeling things; I modeled the [[Piper Archer CX]] exterior and interior. I also enjoy writing Nasal.&lt;br /&gt;
&lt;br /&gt;
'''What projects are you working on right now?''' Well I worked a bit on the Piper last night (just minor tweaks). Did you know that unless you use textures, the ambient color shown in FlightGear is always gray regardless of the exported ambient color? Makes cockpits look awful. Anyway, right now I'm working on a tee hangar. FlightGear doesn't seem to have any tee hangars.&lt;br /&gt;
&lt;br /&gt;
'''What do you plan on doing in the future?''' Finish the Piper and add more scenery objects. Having shaders on full with Rembrandt on doesn't help if the only buildings are 80-meter wide cubes.&lt;br /&gt;
&lt;br /&gt;
'''Why is it that you are interested in flight simulation or aviation in general?''' FlightGear sparked my interest in aviation when I first &amp;lt;s&amp;gt;played&amp;lt;/s&amp;gt; used it. I was just wondering what this &amp;lt;code&amp;gt;fgfs&amp;lt;/code&amp;gt; program was.&lt;br /&gt;
&lt;br /&gt;
'''Are you happy with the way the FlightGear project is going?''' In general, yes. It's come very far in the past few years. The biggest issue in my opinion is the scenery; I realize that at this point it's infeasible to redesign the scenery model to support dynamic subdivision and landclass transitions, but nothing breaks immersion more than flying over the desert until it suddenly turns into grass.&lt;br /&gt;
&lt;br /&gt;
'''What do you enjoy most about contributing to FlightGear?''' Seeing my creations used by other people.&lt;br /&gt;
&lt;br /&gt;
'''Are there any &amp;quot;hidden features&amp;quot; you have worked on in FlightGear that new users may miss?''' Nope, sorry.&lt;br /&gt;
&lt;br /&gt;
'''What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?''' Well I'll start this off with an example: when I first started making aircraft (it was an abysmally-modeled aircraft with horrible proportions that I stupidly released) I had no idea what I was doing. It took me several hours to figure out that the &amp;lt;nowiki&amp;gt;&amp;lt;PropertyList&amp;gt;&amp;lt;/nowiki&amp;gt; XML file was actually just the property tree in XML. That made things much easier for me. The same thing happened with Nasal when I realized that the name of the &amp;lt;nowiki&amp;gt;&amp;lt;file&amp;gt;&amp;lt;/nowiki&amp;gt; parent tag was just the Nasal &amp;quot;namespace&amp;quot;. So it might seem complicated, but once you play around with things for a bit, it will make sense.&lt;br /&gt;
&lt;br /&gt;
'''Have you previously used other flight simulators or simulation software in general?''' No.&lt;br /&gt;
&lt;br /&gt;
'''How does FlightGear compare in your opinion?''' If FSX and X-Plane were both free and open-source, I'd probably choose X-Plane because of the incredible graphics. But since they're both closed and paid products (and FSX is Windows-only while I use Linux), I would (and did) choose FlightGear over the other two major contenders.&lt;br /&gt;
&lt;br /&gt;
'''What was your first impression about FlightGear?''' How the heck do you pronounce ornithopter?&lt;br /&gt;
&lt;br /&gt;
'''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?''' It's free and open source. That attracts people, some of whom will contribute back. That is a huge benefit that's often overlooked.&lt;br /&gt;
&lt;br /&gt;
'''Do you think it is necessary to know how to program in order to contribute to FlightGear?''' Of course not. It would help, but it's definitely not needed. If every 3d artist reading this contributed a high-quality (but low-poly) model to the scenery database, it would make a huge difference. Similarly, placing objects with the UFO doesn't require any programming and makes a huge difference in the quality of a single FlightGear's airport.&lt;br /&gt;
&lt;br /&gt;
'''Have you ever used FlightGear professionally or for educational purposes?''' No and yes. While I haven't ever sat in any GA aircraft, FlightGear has helped me understand flight much better than reading and watching videos ever would.&lt;br /&gt;
&lt;br /&gt;
'''What about FlightGear as a &amp;quot;game&amp;quot;, do you think it can be used as such?''' Of course. It can also be used as a filler for your hard drive. It's whatever you want to use it for.&lt;br /&gt;
&lt;br /&gt;
'''On average, how much time do you spend working with/contributing to FlightGear?''' Probably in the hundreds of hours at this point.&lt;br /&gt;
&lt;br /&gt;
'''Which of the more recent FlightGear developments do you consider most interesting/appealing?''' Procedural textures. Rembrandt. Atmospheric light scattering/cloud shadows.&lt;br /&gt;
&lt;br /&gt;
'''Is there some feature that you'd truly like to see in FlightGear one day?''' Procedural terrain like in Outerra (not to add craters but to allow client-side scenery improvements while using the same dataset.)&lt;br /&gt;
&lt;br /&gt;
'''What do you think could be done to attract even more new users and contributors to FlightGear?''' Higher quality in general. Many users want a flight simulator that just works and looks good; currently, FlightGear is not suited to them.&lt;br /&gt;
&lt;br /&gt;
'''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?''' Back up your FlightGear data directory and play around with things.&lt;br /&gt;
&lt;br /&gt;
'''Have you ever recommended FlightGear to other users, friends/family?''' No, whenever I mention it they suddenly disappear...&lt;br /&gt;
&lt;br /&gt;
'''Is there anything else you'd like to share with us?''' No.&lt;br /&gt;
&lt;br /&gt;
'''Good day then, and thanks for agreeing to this interview.''' No problem.&lt;br /&gt;
&lt;br /&gt;
==In the Hangar==&lt;br /&gt;
&lt;br /&gt;
'''[[Airbus A300-600]]'''&lt;br /&gt;
&lt;br /&gt;
This Airbus A300-600 has been developed by Airbus330 and Toryx (Developer of the A310), using many parts of the A310. The Flightdeck was taken from the A300-600ST, but has the addition of a Cockpit Controllable Autopilot. It has a reasonably detailed exterior model, with accurate flap, speed brake, and spoiler position animations, tail surface animations and tyre smoke.  The interior now consists only of the cockpit, but that is fairly detailed except for the overhead panel. The version currently available for download from the forum or wiki has only the A300-603, but a version with the A300-600F will soon be released, (as soon as i make enough liveries).&lt;br /&gt;
Currently, the engines are always on, but i am now working on an autostart system, which will also be in the next release. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery mode=packed widths=230px heights=230px&amp;gt;&lt;br /&gt;
File:A300F.png|A300F-coming soon!&lt;br /&gt;
File:A300-600 Flightdeck.png|The &amp;quot;Office&amp;quot;&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_September_2014&amp;diff=76345</id>
		<title>FlightGear Newsletter September 2014</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_September_2014&amp;diff=76345"/>
		<updated>2014-09-16T10:36:27Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: Added an &amp;quot;In The Hangar&amp;quot; Section and the A300-600&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Newsletter-header|September 2014}}&lt;br /&gt;
&amp;lt;div style=&amp;quot;border-bottom:3px double #BBB;&amp;quot;&amp;gt;&lt;br /&gt;
{| width=&amp;quot;100%&amp;quot; |&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; width=&amp;quot;33%&amp;quot; |&lt;br /&gt;
{{Newsletter-cover-item|FlightGear 3.2 released (this time for real!)}}&amp;lt;br/&amp;gt;&lt;br /&gt;
{{Newsletter-cover-item|DDS feedback needed}}&amp;lt;br/&amp;gt;&lt;br /&gt;
{{Newsletter-cover-item|Aircraft moved to SVN}}&amp;lt;br/&amp;gt;&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; width=&amp;quot;33%&amp;quot; |&lt;br /&gt;
{{Newsletter-cover-item|Performance issues}}&amp;lt;br/&amp;gt;&lt;br /&gt;
{{Newsletter-cover-item|The hidden Map}}&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; width=&amp;quot;33%&amp;quot; |&lt;br /&gt;
{{Newsletter-cover-item|Interview with a contributor}}&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== DDS feedback needed ==&lt;br /&gt;
&lt;br /&gt;
We are looking for feedback about possibly adopting DDS textures in FlightGear. There are several advantages in doing so:&lt;br /&gt;
&lt;br /&gt;
* DDS is a more compact format than png, hence the download size of the FG base package may be decreased&lt;br /&gt;
* Compressed DDS can be directly used by many graphics cards, reducing also GPU memory consumption&lt;br /&gt;
* DDS stores all texture resolution levels, i.e. no lower resolution levels have to be generated when the texture is used, hence it loads much faster into memory&lt;br /&gt;
* The resolution levels ('mipmaps') can be customized, allowing for some interesting effects at no performance cost&lt;br /&gt;
&lt;br /&gt;
Practically all commercial simulations use DDS for these reasons. &lt;br /&gt;
&lt;br /&gt;
However, the DDS compression algorithm is patented, which means that it is not readily available for open source graphics drivers used by most 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Continue reading at [[Switching default texture format to DDS]]...&lt;br /&gt;
&lt;br /&gt;
== Aircraft moved to SVN ==&lt;br /&gt;
Some months ago we decided to host our aircraft on an SVN repository in order to relieve &amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt;.&lt;br /&gt;
The &amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt; repo would be a mirror of the base package.&lt;br /&gt;
&lt;br /&gt;
We finally moved all our aircraft to '''the new SVN repo''': http://sourceforge.net/p/flightgear/fgaddon/&lt;br /&gt;
&lt;br /&gt;
This repository is named &amp;quot;FGAddon&amp;quot; because its content is not required to run FlightGear but provides a new feature (aircraft in this case); this is usually called an &amp;quot;addon&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Advantages ===&lt;br /&gt;
On the user side, the most important feature is to be able to checkout only desired aircraft, as you no longer need to download the 400+ aircraft at once.&lt;br /&gt;
&lt;br /&gt;
On the developer side, the most important interest is to have a base package (&amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt;) which is lighter to sync for new contributors and easier to keep up to date.&lt;br /&gt;
&lt;br /&gt;
=== A mini HowTo ===&lt;br /&gt;
* For Windows:  Install TortoiseSVN (http://tortoisesvn.net/) &lt;br /&gt;
* For Linux/Mac:  Install SVN&lt;br /&gt;
&lt;br /&gt;
Then to fetch an aircraft (in this example we pick up the [[Robin DR400 Dauphin|DR400 Dauphin]]):&lt;br /&gt;
 svn co https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/DR400-dauphin&lt;br /&gt;
&lt;br /&gt;
Then you can regularly fetch the latest updates with&lt;br /&gt;
 svn up&lt;br /&gt;
&lt;br /&gt;
If you are used to use Git, &amp;lt;code&amp;gt;svn co&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;svn up&amp;lt;/code&amp;gt; are similar to &amp;lt;code&amp;gt;git clone&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;git pull&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The aircraft will remain in the &amp;lt;code&amp;gt;fgdata&amp;lt;/code&amp;gt; Git repository for a few months, until everyone has transitioned to the SVN repositories.&lt;br /&gt;
&lt;br /&gt;
=== Background ===&lt;br /&gt;
For our aircraft developers who don't regularly read the mailing list (even though any aircraft developers should already be subscribed), please read this topic: https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/DUB127-W168600DE27B42094E5263EC3C10%40phx.gbl/#msg3280971&lt;br /&gt;
&lt;br /&gt;
== Performance Issues ==&lt;br /&gt;
Several FlightGear users have pointed out inexplicable &amp;quot;slowness&amp;quot; that originally seemed related to the property rules subsystem - which is a subsystem that Torsten originally wrote/ported, so he investigated a little and managed to track this down to a pretty serious bug in the effects subsystem that may end up registering thousands of identical listeners, despite effects/shaders not even being in use necessarily. &lt;br /&gt;
&lt;br /&gt;
So the property rules code wasn't even the culprit but obviously it deals with properties, so easy to mis-identify as the troublemaker. &lt;br /&gt;
&lt;br /&gt;
As some of you may know from working with Nasal code: listeners are not in and of themselves expensive, but running identical listeners over and over again each frame is getting unnecessarily expensive quickly. This doesn't just apply to scripting space, but also to C++ space - here, it's the sheer performance offered by native C++ code that makes it much harder to identify such problems, because code that would bring the simulator down to its knees in Nasal may very well still be &amp;quot;fast enough&amp;quot; for most people with fast computers, despite being still very much &amp;quot;broken&amp;quot;, and plain wrong.&lt;br /&gt;
&lt;br /&gt;
As can be seen on the devel list, Torsten has been spending the last weeks troubleshooting the effects system, which isn't exactly straightforward because its original developer is not currently involved in FlightGear, and the code is pretty sophisticated and even multi-threaded (which means that parts of the code may be running concurrently on different CPUs) - however, Torsten did report pretty significant performance improvements recently - he's just pushed his work to a new branch so that other developers (and people building from source!) can have a look and test his changes and report feedback/issues - this will probably mean that it may take a few weeks until all the feedback has come in and implemented - but performance should be improved significantly by then - which also addresses the whole &amp;quot;when will 3.2 be released&amp;quot; question.&lt;br /&gt;
&lt;br /&gt;
Also, Hooray recently built fg on a dual-core netbook with Intel GMA graphics (1gb RAM) to see if/how well Canvas is supported there (some people reported white RTTs due to lack of FBO support) - it is true that doing this more regularly would probably help identify certain issues much earlier - it seems that a few contributors are still trying to spin up FG once in a while on their old computers - Thorsten repeatedly mentioned doing that for regression testing purposes when testing his own work. &lt;br /&gt;
&lt;br /&gt;
But FG would indeed be in a better shape if had some way to do this more often, possibly automatically on some kind of headless build/regression testing server - which kinda is what a few people have been working towards:&lt;br /&gt;
&lt;br /&gt;
* [[FlightGear Headless|Running FlightGear headless]] (i.e. without a window, used for subsystem performance testing)&lt;br /&gt;
&lt;br /&gt;
* [[Testing|Testing Performance]]&lt;br /&gt;
&lt;br /&gt;
Things like the recently discovered listener issue in the effects subsystem or massive memory leaks would stand less of a chance of going unnoticed if we had more people testing FG on old hardware - but it's a chicken/egg problem because you need to be pretty familiar with FG to make it work at all, so most people don't bother - and as a coder you tend to prefer writing code over testing obviously, so given the lack of feedback, FG is leaning more towards power users with the latest GPUs and 1+ gb of VRAM unfortunately - simply because that's where all the testing manpower typically is.&lt;br /&gt;
&lt;br /&gt;
People wanting to change that, need to roll up their sleeves and get involved, and PLEAE provide feedback.&lt;br /&gt;
&lt;br /&gt;
'''All''' testing on, and development for, such systems would benefit FG in the long term, because hardware support/compatibility would increase over time - which would also make it possible to target other architectures, i.e. gaming hardware, Rasberry Pi and so on: [[Howto:Optimizing FlightGear for mobile devices]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
And here some initial observations based on running FlightGear on an underpowered Netbook with integrated Intel GMA graphics:&lt;br /&gt;
&lt;br /&gt;
* our existing GUI truly sucks: whenever a PUI dialog is opened, the frame rate is becoming single-digit&lt;br /&gt;
* once the dialog is closed, it will spike up to ~30 fps, with the Canvas/REPL window still shown (!)&lt;br /&gt;
* hiding the PUI menubar further helps increase frame rate and improve frame spacing&lt;br /&gt;
* hiding the menubar AND closing the REPL dialog, I am getting ~45-50 fps using the minimal startup profile, frame spacing is then roughly in the 60s&lt;br /&gt;
* the navcache is a huge resource hog for people on such systems - initializinig/rebuilding the cache is taking ages (10-20+ minutes here !)&lt;br /&gt;
* it would make sense to refactor the navcache and turn it into a library, so that we can prebuild the navcache - and either do so while packaging a release, or alternatively, during installation (plenty of time there!)&lt;br /&gt;
* in addition, threading would make sense probably, when the navcache was being rebuilt, the 2nd core was idling all the time while 1 core was at 100%&lt;br /&gt;
* Canvas/RTT (FBOs) actually work here (which is a good thing for FGPanel/FGCanvas usage)&lt;br /&gt;
* there are a bunch of default options that will &amp;quot;break&amp;quot; FG for users on such systems, including a number of options that will trigger OpenGL/OSG errors early on&lt;br /&gt;
&lt;br /&gt;
Hooray is hoping to do further testing, using the system monitor and the built-in profiler - keep in mind that this still is the code that contains some pretty severe performance bugs.&lt;br /&gt;
&lt;br /&gt;
If we had more people doing this kind of testing, we could definitely identify, and hopefully eliminate, quite a few performance issues that would not be noticeable on a typical developer's machine.&lt;br /&gt;
So this could be a worthwhile thing to do, and it would help FG in the long term - i.e. even benefit power users who have 2048 MB of VRAM and 8 cores/12 gb of RAM.&lt;br /&gt;
&lt;br /&gt;
The really interesting &amp;quot;benchmark&amp;quot; here is running osgviewer and fgviewer as comparison, because what FG is doing here isn't much different functionality-wise, and it's using the same technology stack (i.e. OSG), so should provide similar performance.&lt;br /&gt;
&lt;br /&gt;
Unofortunately, we generally don't have many people who do a lot of testing, troubleshooting - or even just provide feedback via the issue tracker - it is definitely true that the Canvas GUI is much faster here, despite containing a ton MORE Nasal code, and despite being MUCH more dynamic/flexible than our existing PUI dialogs.&lt;br /&gt;
&lt;br /&gt;
It would really be awesome to find a handful of people with access to old/slow hardware interested in testing and maybe troubleshooting things - while it would be great if those people knew how to build from source, and how to use git/gitorious, I don't think that's even necessary - we can definitely provide a lot of infrastructure and advice, but most of us don't typically have access to these kinds of computers. And while some of us admittedly aren't bothered by it, it is very true that FlightGear as a whole will benefit from teasing out certain bugs/issues, no matter if those are slowing things down due to CPU/GPU or RAM/VRAM utilization.&lt;br /&gt;
&lt;br /&gt;
But we really need more people willing to do this kind of testing and who can provide feedback regularly - and start yelling once something that previously worked, stops working or is becoming unnecessarily slow - there are a bunch of issues that should have never made it into the code, but which went unnoticed for months (or even years), because it's really only power users/contributors and developers who do this kind of testing, and as I am seeing right now, certain issues are pretty well &amp;quot;masked&amp;quot; on an 8-core, 10 gb, 2gb VRAM machine obviously ...&lt;br /&gt;
&lt;br /&gt;
We've been hoping to create some kind of &amp;quot;benchmark&amp;quot; for years - and this is one of those things that would truly help FlightGear in the long term, because we'd get quantifiable data over time, so that we can easily tell how a certain startup/run-time feature behaves in correlation with how it behaved previously, i.e. compared to updated dependencies (OpenAL, PLIB, OSG) - but also changes to the C++ code in SG/FG itself.&lt;br /&gt;
&lt;br /&gt;
People are generally quick to point at Nasal and its known GC issues, but are usually not experienced enough to look behind the scenes, and the amount of existing C++ code that is doing things in a slow fashion, code that's been lurking in the source tree for years more often than not. Creating some kind of simple benchmark would help all of us, no matter the kind of hardware we have: [[FlightGear_Benchmark]].&lt;br /&gt;
&lt;br /&gt;
If you're interested in getting involved with testing FlightGear and improving compatibility for older/slow systems, please get in touch with Hooray on the forum.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery mode=packed widths=230px heights=230px&amp;gt;&lt;br /&gt;
Fgfs 3.2 on a dual-core netbook.png|FlightGear 3.2/Canvas working on a dual-core Netbook with Intel GMA graphics showing the [[Interactive Nasal Console]] dialog&lt;br /&gt;
Comparing Native Canvas GUI Performance over PUI.png|A native [[Canvas]] window showing the new [[Aircraft Center]] dialog (good performance)&lt;br /&gt;
System-monitor-on-netbook.png|Screen shot showing a number of performance issues in a handful of FG subsystems, especially the PUI GUI&lt;br /&gt;
Pui slowness.png|The old PLIB/PUI GUI is shown here rendering a Canvas Widget with a [[MapStructure]] layer, a few users have reported that PUI is significantly slowing down the simulator&lt;br /&gt;
MapStructure self test over embedded PUI widget.png|And for comparison a native Canvas window also using the [[MapStructure]] framework,without going through PUI (better performance)&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The hidden Map ==&lt;br /&gt;
[[File:FlightGear-Map-on-Android.png|right|400px]]&lt;br /&gt;
Did you know that FlightGear has an internal web server? And did you ever ask yourself the question, what does a flight simulator needs a web server for? A nice and impressive use case is a map application that has just been brought to the main menu. Click on &amp;quot;Equipment&amp;quot; and select &amp;quot;Map (opens in browser)&amp;quot;. Your web browser will pop up and show a map based on current web standards. It can display OpenStreetMap maps as a base layer as well as satelite image or roads from MapQuest. Overlays for current (real) weather like precipitation and isobares exist. The map can display FlightGear internal navigation data like airports, navaids etc. And it can display AI traffic and multiplayer aircraft, too.&lt;br /&gt;
Of course, it runs on any decent browser, but not only the one on your FlightGear computer. It is web-app-capable so you can install it to your mobile device (IOS and Android) to have a full screen map App on your tablet or phone displaying your current FlightGear status. All this at almost zero cost for the FlightGear main loop. All the rendering computations are done within your browser. The FlightGear webserver only provides the HTML and JavaScript files and transmits the internal properties over a websocket.&lt;br /&gt;
To enable the internal browser-based map, you need to enable the internal web server by adding &amp;lt;code&amp;gt;--httpd=8080&amp;lt;/code&amp;gt; to your command line.&lt;br /&gt;
Consult your mobile devices operation manual about how to add a web page as a full screen App.&lt;br /&gt;
&lt;br /&gt;
== Interview with a contributor ==&lt;br /&gt;
&lt;br /&gt;
This month, the interview comes back. Hey everyone, I'm ZLSA. I've used FlightGear for a while now, but I only got into the development side recently.&lt;br /&gt;
&lt;br /&gt;
Um, I'm supposed to ask ''myself'' questions? Wait, nobody said I'd have to ask ''myself'' questions.&lt;br /&gt;
&lt;br /&gt;
'''What is your forum nickname, ZLSA?''' ZLSA.&lt;br /&gt;
&lt;br /&gt;
'''How long have you been involved with FlightGear?''' The first version I used was 1.9.1, I think. So circa 2008?&lt;br /&gt;
&lt;br /&gt;
'''What are your major interests in FlightGear?''' Well, I like 3d modeling and I'm rather good at it. Do you think I'm good at 3d modeling?&lt;br /&gt;
&lt;br /&gt;
'''I think you're pretty good at it.''' So my primary interest in FlightGear is modeling things; I modeled the [[Piper Archer CX]] exterior and interior. I also enjoy writing Nasal.&lt;br /&gt;
&lt;br /&gt;
'''What projects are you working on right now?''' Well I worked a bit on the Piper last night (just minor tweaks). Did you know that unless you use textures, the ambient color shown in FlightGear is always gray regardless of the exported ambient color? Makes cockpits look awful. Anyway, right now I'm working on a tee hangar. FlightGear doesn't seem to have any tee hangars.&lt;br /&gt;
&lt;br /&gt;
'''What do you plan on doing in the future?''' Finish the Piper and add more scenery objects. Having shaders on full with Rembrandt on doesn't help if the only buildings are 80-meter wide cubes.&lt;br /&gt;
&lt;br /&gt;
'''Why is it that you are interested in flight simulation or aviation in general?''' FlightGear sparked my interest in aviation when I first &amp;lt;s&amp;gt;played&amp;lt;/s&amp;gt; used it. I was just wondering what this &amp;lt;code&amp;gt;fgfs&amp;lt;/code&amp;gt; program was.&lt;br /&gt;
&lt;br /&gt;
'''Are you happy with the way the FlightGear project is going?''' In general, yes. It's come very far in the past few years. The biggest issue in my opinion is the scenery; I realize that at this point it's infeasible to redesign the scenery model to support dynamic subdivision and landclass transitions, but nothing breaks immersion more than flying over the desert until it suddenly turns into grass.&lt;br /&gt;
&lt;br /&gt;
'''What do you enjoy most about contributing to FlightGear?''' Seeing my creations used by other people.&lt;br /&gt;
&lt;br /&gt;
'''Are there any &amp;quot;hidden features&amp;quot; you have worked on in FlightGear that new users may miss?''' Nope, sorry.&lt;br /&gt;
&lt;br /&gt;
'''What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?''' Well I'll start this off with an example: when I first started making aircraft (it was an abysmally-modeled aircraft with horrible proportions that I stupidly released) I had no idea what I was doing. It took me several hours to figure out that the &amp;lt;nowiki&amp;gt;&amp;lt;PropertyList&amp;gt;&amp;lt;/nowiki&amp;gt; XML file was actually just the property tree in XML. That made things much easier for me. The same thing happened with Nasal when I realized that the name of the &amp;lt;nowiki&amp;gt;&amp;lt;file&amp;gt;&amp;lt;/nowiki&amp;gt; parent tag was just the Nasal &amp;quot;namespace&amp;quot;. So it might seem complicated, but once you play around with things for a bit, it will make sense.&lt;br /&gt;
&lt;br /&gt;
'''Have you previously used other flight simulators or simulation software in general?''' No.&lt;br /&gt;
&lt;br /&gt;
'''How does FlightGear compare in your opinion?''' If FSX and X-Plane were both free and open-source, I'd probably choose X-Plane because of the incredible graphics. But since they're both closed and paid products (and FSX is Windows-only while I use Linux), I would (and did) choose FlightGear over the other two major contenders.&lt;br /&gt;
&lt;br /&gt;
'''What was your first impression about FlightGear?''' How the heck do you pronounce ornithopter?&lt;br /&gt;
&lt;br /&gt;
'''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?''' It's free and open source. That attracts people, some of whom will contribute back. That is a huge benefit that's often overlooked.&lt;br /&gt;
&lt;br /&gt;
'''Do you think it is necessary to know how to program in order to contribute to FlightGear?''' Of course not. It would help, but it's definitely not needed. If every 3d artist reading this contributed a high-quality (but low-poly) model to the scenery database, it would make a huge difference. Similarly, placing objects with the UFO doesn't require any programming and makes a huge difference in the quality of a single FlightGear's airport.&lt;br /&gt;
&lt;br /&gt;
'''Have you ever used FlightGear professionally or for educational purposes?''' No and yes. While I haven't ever sat in any GA aircraft, FlightGear has helped me understand flight much better than reading and watching videos ever would.&lt;br /&gt;
&lt;br /&gt;
'''What about FlightGear as a &amp;quot;game&amp;quot;, do you think it can be used as such?''' Of course. It can also be used as a filler for your hard drive. It's whatever you want to use it for.&lt;br /&gt;
&lt;br /&gt;
'''On average, how much time do you spend working with/contributing to FlightGear?''' Probably in the hundreds of hours at this point.&lt;br /&gt;
&lt;br /&gt;
'''Which of the more recent FlightGear developments do you consider most interesting/appealing?''' Procedural textures. Rembrandt. Atmospheric light scattering/cloud shadows.&lt;br /&gt;
&lt;br /&gt;
'''Is there some feature that you'd truly like to see in FlightGear one day?''' Procedural terrain like in Outerra (not to add craters but to allow client-side scenery improvements while using the same dataset.)&lt;br /&gt;
&lt;br /&gt;
'''What do you think could be done to attract even more new users and contributors to FlightGear?''' Higher quality in general. Many users want a flight simulator that just works and looks good; currently, FlightGear is not suited to them.&lt;br /&gt;
&lt;br /&gt;
'''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?''' Back up your FlightGear data directory and play around with things.&lt;br /&gt;
&lt;br /&gt;
'''Have you ever recommended FlightGear to other users, friends/family?''' No, whenever I mention it they suddenly disappear...&lt;br /&gt;
&lt;br /&gt;
'''Is there anything else you'd like to share with us?''' No.&lt;br /&gt;
&lt;br /&gt;
'''Good day then, and thanks for agreeing to this interview.''' No problem.&lt;br /&gt;
&lt;br /&gt;
==In the Hangar==&lt;br /&gt;
&lt;br /&gt;
'''Airbus A300-600'''&lt;br /&gt;
&lt;br /&gt;
This Airbus A300-600 has been developed by Airbus330 and Toryx (Developer of the A310), using many parts of the A310. The Flightdeck was taken from the A300-600ST, but has the addition of a Cockpit Controllable Autopilot. It has a reasonably detailed exterior model, with accurate flap, speed brake, and spoiler position animations, tail surface animations and tyre smoke.  The interior now consists only of the cockpit, but that is fairly detailed except for the overhead panel. The version currently available for download from the forum or wiki has only the A300-603, but a version with the A300-600F will soon be released, (as soon as i make enough liveries).&lt;br /&gt;
Currently, the engines are always on, but i am now working on an autostart system, which will also be in the next release. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery mode=packed widths=230px heights=230px&amp;gt;&lt;br /&gt;
File:A300F.png|A300F-coming soon!&lt;br /&gt;
File:A300-600 Flightdeck.png|The &amp;quot;Office&amp;quot;&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airliner_development_status&amp;diff=76343</id>
		<title>Airliner development status</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airliner_development_status&amp;diff=76343"/>
		<updated>2014-09-16T10:26:52Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: /* Airbus A300 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.&lt;br /&gt;
&lt;br /&gt;
= Airbus Industries =&lt;br /&gt;
== Airbus A300 ==&lt;br /&gt;
* Airbus A300-B2 - {{alds|stalled}}&lt;br /&gt;
* Airbus A300-B4 - {{alds|stalled}}&lt;br /&gt;
* [[Airbus A300-600]] - {{alds|active}}&lt;br /&gt;
* [[Airbus A300-600ST]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A310 ==&lt;br /&gt;
* Airbus A310-200 - {{alds|not started}}&lt;br /&gt;
* [[Airbus A310-300]] - {{alds|active}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A320 ==&lt;br /&gt;
* [[A320-family]]&lt;br /&gt;
** Airbus A318-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A318-200 - {{alds|stable}}&lt;br /&gt;
** Airbus A319-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A319-200 - {{alds|stable}}&lt;br /&gt;
** Airbus A320-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A320-200 - {{alds|stable}}&lt;br /&gt;
** Airbus A321-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A321-200 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
* [[Airbus A320neo|A320neo]]&lt;br /&gt;
** Airbus A319neo - {{alds|active}}&lt;br /&gt;
** Airbus A320neo - {{alds|active}}&lt;br /&gt;
** Airbus A321neo - {{alds|active}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A330 ==&lt;br /&gt;
* [[Airbus A330-200]] - {{alds|stable}}&lt;br /&gt;
* Airbus A330-200F - {{alds|not started}}&lt;br /&gt;
* [[Airbus A330-300]] - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A340 ==&lt;br /&gt;
* Airbus A340 - {{alds|not started}}&lt;br /&gt;
* [[Airbus A340|Airbus A340-300]] - {{alds|stalled}}&lt;br /&gt;
* [[Airbus A340|Airbus A340-500]] - {{alds|active}}&lt;br /&gt;
* [[Airbus A340-600]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A350 ==&lt;br /&gt;
* Airbus A350-800 -{{alds|not started}}&lt;br /&gt;
* Airbus A350-900 - {{alds|stable}}&lt;br /&gt;
* Airbus A350-1000 -{{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A380 ==&lt;br /&gt;
* [[Airbus A380|Airbus A380-800]] - {{alds|active}}&lt;br /&gt;
* Airbus A380-900 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Avions Transportation Regional =&lt;br /&gt;
== ATR-42 ==&lt;br /&gt;
* ATR-42-200 - {{alds|not started}}&lt;br /&gt;
* ATR-42-300 - {{alds|not started}}&lt;br /&gt;
* ATR-42-500 - {{alds|stalled}}&lt;br /&gt;
* ATR-42-600 - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
== ATR-72 ==&lt;br /&gt;
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}&lt;br /&gt;
* ATR-72-600 - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
= Boeing Commercial Airplanes =&lt;br /&gt;
== Boeing 707 ==&lt;br /&gt;
* [[Boeing 707]]&lt;br /&gt;
** Boeing 707-100 - {{alds|not started}}&lt;br /&gt;
** Boeing 707-200 - {{alds|not started}}&lt;br /&gt;
** Boeing 707-300 - {{alds|abandoned}}&lt;br /&gt;
* Boeing 720 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 717 ==&lt;br /&gt;
* [[Boeing 717|Boeing 717-200]] - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 727 ==&lt;br /&gt;
* Boeing 727-100 - {{alds|not started}}&lt;br /&gt;
* Boeing 727-200 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 737 ==&lt;br /&gt;
* Boeing 737-100 - {{alds|abandoned}}&lt;br /&gt;
* Boeing 737-200 - {{alds|abandoned}}&lt;br /&gt;
* [[Boeing 737-300]] - {{alds|stalled}}&lt;br /&gt;
* [[Boeing 737-400]] - {{alds|stalled}}&lt;br /&gt;
* [[Boeing 737-500]] - {{alds|stalled}}&lt;br /&gt;
* Boeing 737NG models - {{alds|active}} by [[user:zakalawe]]&lt;br /&gt;
* [[Boeing 737-7 MAX]] - {{alds|not started}}&lt;br /&gt;
* [[Boeing 737-8 MAX]] - {{alds|not started}}&lt;br /&gt;
* [[Boeing 737-9 MAX]] - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 747 ==&lt;br /&gt;
* [[Boeing 747-100]] - {{alds|abandoned}}&lt;br /&gt;
* [[Boeing 747-200]] - {{alds|abandoned}}&lt;br /&gt;
* Boeing 747-300 - {{alds|not started}}&lt;br /&gt;
* [[Boeing 747-400]] - {{alds|stable}}&lt;br /&gt;
* [[Boeing 747-8 Dreamlifter|Boeing 747-8]] - {{alds|stalled}}&lt;br /&gt;
* [[Boeing 747-8i]] - {{alds|active}}&lt;br /&gt;
* Boeing 747SP - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 757 ==&lt;br /&gt;
* [[Boeing 757-200]] - {{alds|stalled}}&lt;br /&gt;
* Boeing 757-300 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 767 ==&lt;br /&gt;
* Boeing 767-200 - {{alds|not started}}&lt;br /&gt;
* [[Boeing 767-300]] - {{alds|abandoned}}&lt;br /&gt;
* [[Boeing 767-300F]] - {{alds|active}}&lt;br /&gt;
* Boeing 767-400 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 777 ==&lt;br /&gt;
* [[Boeing 777-200]] - {{alds|stable}}&lt;br /&gt;
* [[Boeing 777-300]] - {{alds|abandoned}}&lt;br /&gt;
* Boeing 777-8X - {{alds|not started}}&lt;br /&gt;
* Boeing 777-9X - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 787 ==&lt;br /&gt;
* [[Boeing 787-8]] - {{alds|stable}}&lt;br /&gt;
* Boeing 787-9 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Bombardier Aerospace =&lt;br /&gt;
== Dash 7 ==&lt;br /&gt;
* Dash 7-100 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Dash 8 ==&lt;br /&gt;
* Dash 8-300 - {{alds|abandoned}}&lt;br /&gt;
* Dash 8-Q400 - {{alds|active}}&lt;br /&gt;
&lt;br /&gt;
== Canadair Regional Jets ==&lt;br /&gt;
* [[CRJ-200|CRJ200]] - {{alds|active}}&lt;br /&gt;
* CRJ700 - {{alds|stable}}&lt;br /&gt;
* [[CRJ-900|CRJ900]] - {{alds|stable}}&lt;br /&gt;
* CRJ1000 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== CSeries ==&lt;br /&gt;
* CS100 - {{alds|stalled}}&lt;br /&gt;
* CS300 - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
= Douglas Aircraft Company =&lt;br /&gt;
== DC-1 ==&lt;br /&gt;
* DC-1 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-2 ==&lt;br /&gt;
* DC-2 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== DC-3 ==&lt;br /&gt;
* DC-3 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== DC-4 ==&lt;br /&gt;
* DC-4 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-5 ==&lt;br /&gt;
* DC-5 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-6 ==&lt;br /&gt;
* DC-6 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== DC-7 ==&lt;br /&gt;
* DC-1 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-8 ==&lt;br /&gt;
* DC-8-10 - {{alds|not started}}&lt;br /&gt;
* DC-8-20 - {{alds|not started}}&lt;br /&gt;
* DC-8-30 - {{alds|not started}}&lt;br /&gt;
* DC-8-40 - {{alds|not started}}&lt;br /&gt;
* DC-8-50 - {{alds|not started}}&lt;br /&gt;
* DC-8-60 - {{alds|stable}}&lt;br /&gt;
* DC-8-70 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== DC-9 ==&lt;br /&gt;
* DC-9-10 - {{alds|not started}}&lt;br /&gt;
* DC-9-20 - {{alds|not started}}&lt;br /&gt;
* DC-9-30 - {{alds|stable}}&lt;br /&gt;
* DC-9-40 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-10 ==&lt;br /&gt;
* DC-10-10 - {{alds|not started}}&lt;br /&gt;
* DC-10-20 - {{alds|not started}}&lt;br /&gt;
* DC-10-30 - {{alds|abandoned}}&lt;br /&gt;
* DC-10-40 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Embraer Manufacturers =&lt;br /&gt;
== Embraer 120 Series ==&lt;br /&gt;
* EMB120 - {{alds|not started}}&lt;br /&gt;
* EMB125 - {{alds|not started}}&lt;br /&gt;
* EMB140 - {{alds|not started}}&lt;br /&gt;
* EMB145 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Embraer E-jet Series ==&lt;br /&gt;
* ERJ170 - {{alds|stable}}&lt;br /&gt;
* ERJ175 - {{alds|stable}}&lt;br /&gt;
* ERJ190 - {{alds|stable}}&lt;br /&gt;
* ERJ195 - {{alds|stable}}&lt;br /&gt;
* Legacy - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Fokker Aero-structures =&lt;br /&gt;
== Fokker F27 ==&lt;br /&gt;
* Fokker F27 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 50 ==&lt;br /&gt;
* [[Fokker 50]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 60 ==&lt;br /&gt;
* Fokker 60 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 70 ==&lt;br /&gt;
* [[Fokker 70]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 100 ==&lt;br /&gt;
* [[Fokker 100]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
= Lockheed Corporation =&lt;br /&gt;
== Lockheed 1049H ==&lt;br /&gt;
* L1049H  - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== Lockheed L1011 ==&lt;br /&gt;
* L1011-1 - {{alds|not started}}&lt;br /&gt;
* L1011-100 - {{alds|not started}}&lt;br /&gt;
* L1011-200 - {{alds|not started}}&lt;br /&gt;
* L1011-500 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
= McDonnell Douglas =&lt;br /&gt;
== MD-11 ==&lt;br /&gt;
* [[MD-11]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== MD-80 ==&lt;br /&gt;
* MD-81 - {{alds|stable}}&lt;br /&gt;
* MD-82 - {{alds|not started}}&lt;br /&gt;
* MD-83 - {{alds|not started}}&lt;br /&gt;
* MD-87 - {{alds|not started}}&lt;br /&gt;
* MD-88 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== MD-90 ==&lt;br /&gt;
* MD-90 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Aircraft enhancement]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76341</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76341"/>
		<updated>2014-09-16T01:21:56Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= A300F.png&lt;br /&gt;
|alt            = An A300F landing&lt;br /&gt;
|image2         = A300-600 Flightdeck.png&lt;br /&gt;
|alt2           = Flightdeck (originaly from the [[Airbus A300-600ST|A300-600ST]])&lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 2&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 4&lt;br /&gt;
|status-model	= 4&lt;br /&gt;
|fgname 	= A300-603, A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences and a two-crew (first ever), glass cockpit.&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, first set your values, (Speed, Heading, etc.) These can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, and then arm which ever mode you want. Recommended modes are V/S (engaged by clicking the V/S knob or the LVL/CH button) and Heading (engaged with the HDG button). Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending. &lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engaged Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mode will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596 A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=User_talk:Johan_G&amp;diff=76340</id>
		<title>User talk:Johan G</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=User_talk:Johan_G&amp;diff=76340"/>
		<updated>2014-09-15T22:24:59Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==A300-600==&lt;br /&gt;
&lt;br /&gt;
Hi thanks for doing that to my A300-600 page, it looks a lot more professional. I tried changing the name as well but couldn't figure out how :-) [[User:Airbus330|Airbus330]] ([[User talk:Airbus330|talk]]) 22:24, 15 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Swedish ==&lt;br /&gt;
Hi Johan,&lt;br /&gt;
&lt;br /&gt;
thanks for starting translating articles to Swedish! Unfortunately, the wiki admin has to &amp;quot;add&amp;quot; this language to the system (therefore adding [[sv:Article]] does not work as of now). I've immediately asked him to do so, but it might take a while. In the meantime you can continue translating articles, it's just the linking that doesn't work.&lt;br /&gt;
&lt;br /&gt;
Cheers,&lt;br /&gt;
[[User:Gijs|Gijs]] 08:36, 3 July 2011 (EDT)&lt;br /&gt;
&lt;br /&gt;
:Ah, that explains why the language link doesn't seem to work. Thank you! I sent him a mail as well. Well, at least I can continue (in a slow pace). [[User:Johan G|Johan G]] 08:43, 3 July 2011 (EDT)&lt;br /&gt;
&lt;br /&gt;
== Don't be a stranger. ==&lt;br /&gt;
Jag hoppas att du kommer tillbaka snart. {{Unsigned2|11:45, 11 October 2011|PH-JBO}}&lt;br /&gt;
&lt;br /&gt;
:Thank you for hoping for my return. Den som väntar på något gott... ''In other words, I'm back.'' [[User:Johan G|Johan G]] 09:59, 5 December 2011 (EST)&lt;br /&gt;
::Du är inte ensam. Välkommen tillbaka! [[User:PH-JBO|PH-JBO]] 07:28, 6 December 2011 (EST)&lt;br /&gt;
&lt;br /&gt;
== Test ==&lt;br /&gt;
A short thest to see if a new section added with the &amp;quot;+&amp;quot; tab is appended to the bottom of the page. [[User:Johan G|Johan G]] 07:32, 9 February 2012 (EST)&lt;br /&gt;
&lt;br /&gt;
== Discussing new main page/portals ==&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;br /&gt;
would be nice if you could come on [[IRC]] this week. I'd like to discuss the new main page/portals that I've been working on ;)&lt;br /&gt;
You'll find me in [irc://#wiki@irc.flightgear.org #wiki@irc.flightgear.org]&lt;br /&gt;
&lt;br /&gt;
Cheers,&lt;br /&gt;
[[User:Gijs|Gijs]] 12:27, 19 March 2012 (EDT)&lt;br /&gt;
&lt;br /&gt;
: Hi, I should be in #wiki now as Johan_G.  This will bee interesting.  I have not used IRC before, and last time I watched it over someones shoulder was in &amp;lt;s&amp;gt;1999&amp;lt;/s&amp;gt; 1998!&lt;br /&gt;
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:52, 19 March 2012 (EDT)&lt;br /&gt;
&lt;br /&gt;
== Infobox aircraft changes ==&lt;br /&gt;
I thought, I'd better get in touch with the only wikimedia template guru that I know :-) I just added a handful of meta categories (inspired by [http://forum.flightgear.org/viewtopic.php?f=25&amp;amp;t=21431#p195109]), and now want to extend the infobox accordingly, including images for each supported features, see: http://wiki.flightgear.org/Template_talk:Infobox_aircraft Any ideas/preference how to implement this best? Images will probably be contributed by Michat. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:33, 30 November 2013 (UTC)&lt;br /&gt;
&lt;br /&gt;
:It is low on my to-do list, but see my answer at [[Template talk:Infobox aircraft]].&lt;br /&gt;
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:08, 1 December 2013 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Yes/no template ==&lt;br /&gt;
&lt;br /&gt;
Hi Johan,&lt;br /&gt;
&lt;br /&gt;
the yes/no template doesn't seem to work well on [[Photoscenery]], everything says &amp;quot;yes&amp;quot; now. Another issue is that the 1m/pixel text is no longer centered, as if it only applies to &amp;quot;texture materials&amp;quot;, while it's supposed to cover &amp;quot;3D model&amp;quot; as well. And to be honest, I prefer the more pronounced colours that we had before... I'm all in for a yes/no template though, don't get me wrong ;-)&lt;br /&gt;
&lt;br /&gt;
Cheers,&lt;br /&gt;
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:43, 2 March 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
: Oops. I was updating the templates to be able to handle adding xhtml attributes and one the edits accidentally had &amp;quot;Yes instead of &amp;quot;No&amp;quot;.  Should already work as expected by now.&lt;br /&gt;
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:51, 2 March 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
: Made the colours quite a bit stronger, but black text should still be readable in the cells.&lt;br /&gt;
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:20, 2 March 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Thanks for appreciating ==&lt;br /&gt;
Hi, thanks for appreciating [[Howto:Convert objects with ModelConverterX]]. I recently posted a howto on [http://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=22851 georeferencing OSM in WED], let me know if that could be added somewhere in the wiki, I'd be glad to, but I'm not sure if it's useful outside of Italy.--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 22:38, 26 April 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
:You are very welcome. :-)&lt;br /&gt;
:About the howto, it could probably fit really well as an article on the wiki.  My only concern there is using Google to check the taxiways.  I am not sure or not that it is relevant, but Google's terms of use do not allow derivative works.  Licenses can be a problem sometimes, and I am completely ignorant when it comes to Italian legislation on intellectual property, but I assume that most sources are copyrighted more or less automatically, but that there might be a few sources with less restrictive licenses.&lt;br /&gt;
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:30, 27 April 2014 (UTC)&lt;br /&gt;
:: I see. Well, in Italy (see elgaton's answer) we're allowed to trace over some nice aerial images in OSM, but that's all, so we have to go through OSM and its limitations (i.e. no Bezier). I can substitute that part with just a warning to check by other means what angles should be rounded, or suggest to make rounded corners stand out in OSM with more points. However blurry is the border with Google, I guess it could be considered as &amp;quot;getting the coordinates&amp;quot;* of rounded corners (*I've read it's considered ok here).&lt;br /&gt;
::It jumps to my mind that Bing has allowed use of its aerial images for OSM tracing - worldwide. They have a good detail but are not very precise, yet that's something a mapper can fix. I guess this changes the usefulness of the howto :D Let me know if there's a particular page/category where I can put this. --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:43, 28 April 2014 (UTC)&lt;br /&gt;
:::The juridical stuff can be a problematic at times. ;-)&lt;br /&gt;
:::A fitting category would be [[:Category:Scenery enhancement]] I think.&lt;br /&gt;
:::(On a side note that category page have turned into an article over time, which looks messy and wont turn up in a regular wiki search using the search box.)&lt;br /&gt;
:::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:03, 28 April 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
== A FlightGear help category ==&lt;br /&gt;
&lt;br /&gt;
Today [[Unexpected Crashes with Scenery ver.2]] was added to [[:Category:Help]]. There's lack indeed of a FlightGear help category (into FlightGear of course). That sounds like a good name (place), but I won't add it until I know your opinion.&lt;br /&gt;
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:49, 10 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
: Ah, thanks for asking.  There is indeed lack of a FlightGear help category, but I'll get to that.  The help category seem to only have contained pages in the help namespace, i.e. articles with help about using the wiki (i think that category page even states that).&lt;br /&gt;
&lt;br /&gt;
: As for the FlightGear help pages, I have actually never really figured out if there originally was some kind of thought through structure there or if the whole thing was a bit haphazard turned into ad hoc.  I.e. I have never really grasped how to use them in an intuitive way (for both me, other editors and the readers).  There is a lot of categories that slightly overlap or are slightly vague, which does not help when trying to find articles or even categories.  I think a lot of that mess should be discussed on the [[FlightGear wiki:Village pump|village pump]].&lt;br /&gt;
&lt;br /&gt;
: In addition there are lots of annoying little technicalities, like that the search box auto-complete function is case sensitive and that some editors are very much into Camel Case Titles, something for example Wikipedia is recommending their editors to avoid.  Speaking of that, the wiki could need a style guide, but that would take some extra maintenance to enforce.&lt;br /&gt;
&lt;br /&gt;
: To be honest have been secretly wishing that you might be into trying to figure out a better structure and better category names, specially for the FlightGear related stuff.  I have thought about it and figured that I would wish it would be better... but doesn't feel up to it.  I spent most of my categorisation efforts on templates and images, unless pages was uncategorised.&lt;br /&gt;
&lt;br /&gt;
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:30, 10 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
:: Heh, and you picked your &amp;quot;dupe&amp;quot; very wisely. Your last phrase in parentheses, in the above topic, is the main reason for me being here. I'll definitely try that when I get more confidence. However there's a lot of automatable stuff, some of which should be done before to ease that part. Some I pointed out in the [[User talk:Bigstones/Essay:A plan for a reorganization of the wiki#Bot proposal (request?)|other discussion]], one is that of recategorizing other languages, one is fixing camel case (like for spaces with Howto). Much more might come out.&lt;br /&gt;
:: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 00:49, 11 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
:: edit -- see [[FlightGear wiki:Village pump#Category:Support]] --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:48, 11 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
::: Good move. The more eyes, the better. :-) &lt;br /&gt;
:::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 21:10, 11 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Updated compile guide ==&lt;br /&gt;
&lt;br /&gt;
[[User:Daemonburrito/Building FlightGear - Linux]]&lt;br /&gt;
&lt;br /&gt;
Hello, Johan. As promised, a completely reworked compile guide. It makes a nice, clean, and safe environment. And it ''works''!&lt;br /&gt;
&lt;br /&gt;
But it is a pretty big change to drop in there, so I'm leaving it on my user page for comments for a bit. Let me know what you think. [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 17:06, 10 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
: I am not really the right person to review it, except for copy editing (i.e. style/wiki markup) if that would be needed.  In this case I think it might be better to mention it on the forum.  I have very little experience with Linux, and on top of that it was quite some time ago (Red hat Linux, kernel 2.2 etc. on a ''way'' to weak box).&lt;br /&gt;
&lt;br /&gt;
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:40, 10 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
:: Will do. Thanks! [[User:Daemonburrito|Daemonburrito]] ([[User talk:Daemonburrito|talk]]) 23:04, 10 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
== On reorganization of [[:Category:Troubleshooting]] ==&lt;br /&gt;
&lt;br /&gt;
Hi Johan, I hope I was not too messy yesterday. I'm sure I never broke a link, and neither lost any information (a huge amount was duplicated), although I also rewrote some parts. Actually, 2-3 redirects are still around only because I couldn't edit some Japanese/Chinese pages. The two deletions you postponed:&lt;br /&gt;
* [[Howto:Improve framerates]] - I didn't delete the content just to save one edit, but I did actually already move everything.&lt;br /&gt;
* [[Intel GMA cards]] - I've found that page by chance, and it wasn't referenced anywhere. The information it contains is already in the same place where I moved the forum ref.&lt;br /&gt;
I hope this can help for a future review. Also, in case you want to review my future plans, I wrote them in my user page.&lt;br /&gt;
&lt;br /&gt;
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 10:43, 18 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
:: I think I may have been messier.  In retrospect I might should have left the redirects for those that by habit look for those article titles when troubleshooting.  Also a lot of posts on the forum point to those.  I will probably restore those and try point them towards suitable pages.&lt;br /&gt;
&lt;br /&gt;
:: That said, I think you have done a great job separating the information aimed at developers from the one aimed at users.  It kind of makes me wonder why no one thought of that before.&lt;br /&gt;
&lt;br /&gt;
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 23:59, 18 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
::: Let me know if I can help with redirects...&lt;br /&gt;
::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 19:54, 19 May 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
== DDS article moved ... ==&lt;br /&gt;
&lt;br /&gt;
Not sure if you have been followin the discussion on the devel list or if I misunderstood something, but I don't think it's necessarily specific to just terrain textures ? Anyway, please keep the redirect either way because Thorsten already posted a link using the old name. So while the current name is definitely better, we should probably ensure that all links keep on working, while the website/forum can be updated, the devel archives cannot ... --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 23:28, 4 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
: Ah, my misunderstanding.  Terrain textures was specifically mentioned in one of the sections/quotes so I thought it was about that specifically.  I will move it to [[Switching default texture format to DDS]] instead.&lt;br /&gt;
&lt;br /&gt;
: As for keeping the redirect, I am more cautious about deleting them due to some to eager deletions I have done in the past...&lt;br /&gt;
&lt;br /&gt;
: Thanks for the heads up.&lt;br /&gt;
&lt;br /&gt;
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 23:40, 4 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
== Improvements and cleaning of Wiki pages ==&lt;br /&gt;
Hi Johan_G! You seem to be very popular and loved. I'm here to thank you for your work on cleaning the article about the Mulhouse airport. I really like how it's cleaner and the templates, you seem to be good at it. I really don't have that much of an idea. Also cool that you're an admin. I may not be very popular and appear irregularly, but I do my best to help the wiki (also notice the problems I have with Flightgear in my User page, you may pass by and leave a message, it's so empty :'( ). I guess that's all for now&lt;br /&gt;
&lt;br /&gt;
[[User:Thefan|Thefan630]] ([[User talk:Thefan|talk]]) 10:00, 10 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
: As for the Mulhouse airport article, you are very welcome.  Thanks also for the kind words.&lt;br /&gt;
&lt;br /&gt;
: Making articles easier to read is one of my longterm goals on the wiki, but I am usually spending most of my time on improving stuff that would help other do the work, in essence structure and documentation on how to use the wiki.  Have a look at the [[:Category:Help|help pages]] and the [[:Category:Templates|templates]] and their documentation, though there is still a lot of undocumented templates, including some important ones.  The [[:Category:Wiki style guides|style guides]] are still in their infancy (and at the moment I feel the article style guide is a bit convoluted, but it can be improved).&lt;br /&gt;
&lt;br /&gt;
: The templates I added, and most of the so called ''messagebox templates'' can be found at [[Help:Gallery of messagebox templates]].  Links to them can be found on [[Help:Templates]].  However, the quick way to find links to templates is by looking at the bottom of a page you are editing.  Just click the text &amp;quot;Templates used on this page:&amp;quot; and you will see a list of links to the templates (and hopefully their documentation).&lt;br /&gt;
&lt;br /&gt;
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:13, 10 September 2014 (UTC)&lt;br /&gt;
&lt;br /&gt;
:: When you have time, please take a look at the new entry at [[Talk:EuroAirport Basel-Mulhouse-Freiburg]]&lt;br /&gt;
&lt;br /&gt;
:: [[User:Thefan|Thefan630]] ([[User talk:Thefan|talk]]) 12:27, 10 September 2014 (UTC)&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76286</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76286"/>
		<updated>2014-09-15T08:35:23Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= [[File:A300F.png|thumb|A300F landing]]&lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 2&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 4&lt;br /&gt;
|status-model	= 4&lt;br /&gt;
|fgname 	= A300-603, A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences and a two-crew (first ever), glass cockpit.&lt;br /&gt;
&lt;br /&gt;
[[File:A300-600 Flightdeck.png|thumb|A300-Flightdeck, taken and modified from the A300-600ST]]&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, first set your values, (Speed, Heading, etc.) These can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, and then arm which ever mode you want. Recommended modes are V/S (engaged by clicking the V/S knob or the LVL/CH button) and Heading (engaged with the HDG button). Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending. &lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engaged Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mode will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596 A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Template:Airbus&amp;diff=76285</id>
		<title>Template:Airbus</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Template:Airbus&amp;diff=76285"/>
		<updated>2014-09-15T08:34:29Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Navbox&lt;br /&gt;
| name  = Airbus&lt;br /&gt;
| title = [[Airbus]]&lt;br /&gt;
| listclass = hlist&lt;br /&gt;
&lt;br /&gt;
| list1  = &lt;br /&gt;
* [[Airbus A300|A300]] ([[Airbus A300-600ST|-600ST]])&lt;br /&gt;
* [[A300-600|A300-600]]&lt;br /&gt;
* [[Airbus A310|A310]]&lt;br /&gt;
* [[Airbus A319|A319]]&lt;br /&gt;
* [[Airbus A320 Family|A320 series (318, 319, 320, and 321)]]&lt;br /&gt;
* [[Airbus A320neo|Airbus A320neo family]]&lt;br /&gt;
* [[Airbus A320E|A320E]]&lt;br /&gt;
* [[Airbus A321|A321]]&lt;br /&gt;
* [[Airbus A330|A330]]&lt;br /&gt;
* [[Airbus A340|A340]] ([[Airbus A340-600|-600|]][[Airbus A340-600HGW|-600HGW]])&lt;br /&gt;
* [[Airbus A350|A350]]&lt;br /&gt;
* [[Airbus A380|A380]]&lt;br /&gt;
}}&amp;lt;includeonly&amp;gt;{{main other| [[Category:Airbus]] }}&amp;lt;/includeonly&amp;gt;&amp;lt;noinclude&amp;gt;&lt;br /&gt;
{{Informative template|1=&lt;br /&gt;
__NOTOC__&lt;br /&gt;
== Goal ==&lt;br /&gt;
This navigation template links together Airbus aircraft.&lt;br /&gt;
&lt;br /&gt;
Adding this template to a page in the article namespace will automatically add [[:Category:Airbus]] to that page.&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
Put this line before the categories and the language links at the bottom of the article.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;{{Airbus}}&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Navigation templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76284</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76284"/>
		<updated>2014-09-15T07:37:40Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= [[File:A300F.png|thumb|A300F landing]]&lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 2&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 4&lt;br /&gt;
|status-model	= 4&lt;br /&gt;
|fgname 	= A300-603, A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences and a two-crew (first ever), glass cockpit.&lt;br /&gt;
&lt;br /&gt;
[[File:A300-600 Flightdeck.png|thumb|A300-Flightdeck, taken from the A300-600ST]]&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, first set your values, (Speed, Heading, etc.) These can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, and then arm which ever mode you want. Recommended modes are V/S (engaged by clicking the V/S knob or the LVL/CH button) and Heading (engaged with the HDG button). Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending. &lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engaged Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mode will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596 A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:A300F.png&amp;diff=76283</id>
		<title>File:A300F.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:A300F.png&amp;diff=76283"/>
		<updated>2014-09-15T07:36:14Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: User created page with UploadWizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=A300F landing}}&lt;br /&gt;
|date=2014-09-15 17:34:25&lt;br /&gt;
|source={{own}}&lt;br /&gt;
|author=[[User:Airbus330|Airbus330]]&lt;br /&gt;
|permission=&lt;br /&gt;
|other_versions=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{self|cc-by-sa-3.0}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Airbus]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:A300-600_Flightdeck.png&amp;diff=76282</id>
		<title>File:A300-600 Flightdeck.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:A300-600_Flightdeck.png&amp;diff=76282"/>
		<updated>2014-09-15T07:36:03Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: User created page with UploadWizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=A300-Flightdeck, taken from the A300-600ST}}&lt;br /&gt;
|date=2014-09-15 17:34:22&lt;br /&gt;
|source={{own}}&lt;br /&gt;
|author=[[User:Airbus330|Airbus330]]&lt;br /&gt;
|permission=&lt;br /&gt;
|other_versions=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{self|cc-by-sa-3.0}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Airbus]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76278</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76278"/>
		<updated>2014-09-15T05:14:43Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= &lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 2&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 4&lt;br /&gt;
|status-model	= 4&lt;br /&gt;
|fgname 	= A300-603, A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences and a two-crew (first ever), glass cockpit.&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, first set your values, (Speed, Heading, etc.) These can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, and then arm which ever mode you want. Recommended modes are V/S (engaged by clicking the V/S knob or the LVL/CH button) and Heading (engaged with the HDG button). Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending. &lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engaged Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mode will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596 A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76219</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76219"/>
		<updated>2014-09-14T07:51:51Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= &lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 2&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 4&lt;br /&gt;
|status-model	= 4&lt;br /&gt;
|fgname 	= A300-603, A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences and a two-crew (first ever), glass cockpit.&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, first set you values, (Speed, Heading, etc.) These can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, and then arm which ever mode you want. Recommended modes are V/S (engaged by clicking the V/S knob or the LVL/CH button) and Heading (engaged with the HDG button). Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending. &lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engaged Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mode will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596 A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76218</id>
		<title>Airbus A300-600</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A300-600&amp;diff=76218"/>
		<updated>2014-09-14T06:37:10Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: Created page with &amp;quot;{{infobox Aircraft |image 		=  |name 		= Airbus A300-600 |type 		= Airliner |livery 	= Air Transat, PIA |authors 	= Airbus330, Toryx, Pierre Duval |fdm 		= JSBsim |status-fdm...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image 		= &lt;br /&gt;
|name 		= Airbus A300-600&lt;br /&gt;
|type 		= Airliner&lt;br /&gt;
|livery 	= Air Transat, PIA&lt;br /&gt;
|authors 	= Airbus330, Toryx, Pierre Duval&lt;br /&gt;
|fdm 		= JSBsim&lt;br /&gt;
|status-fdm	= 2&lt;br /&gt;
|status-systems	= 1&lt;br /&gt;
|status-cockpit	= 4&lt;br /&gt;
|status-model	= 4&lt;br /&gt;
|fgname 	= A300-603&lt;br /&gt;
|fgmane   =A300-600F&lt;br /&gt;
|download = https://drive.google.com/file/d/0Bxn-0nSiqGxvd3BZczFJMXA4ZE0/edit?usp=sharing&lt;br /&gt;
}}'''This aircraft is in develoment by Airbus330'''&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A300-600''' is a medium- to long-range twin-engine widebody jet [[airliner]]. Entering Service in 1983, it was a significant upgrade of the A300B, the first aircraft created by [[Airbus]], the consortium of European aerospace companies, which is now amalgamated into one company, Airbus Group. The A300-600 has the same fuselage as the original [[A300]], the first twin-engined widebody airliner, but uses A310 tail section and engines. Other differences include using wingtip fences.&lt;br /&gt;
&lt;br /&gt;
== Autopilot help ==&lt;br /&gt;
To use the Autopilot, first set you values, (speed, Heading, etc.) These can be set using the knobs on the glare shield, or by using the dialog box. After takeoff turn on the AP master switch, and then arm which ever mode you want. Recommended modes are V/S (engaged by clicking the V/S knob or the LVL/CH button) and Heading (engaged with the HDG button). Note that if the LVL/CH light is on V/S mode is not necessarily engaged, it also comes on when ever the AP is climbing or Descending. &lt;br /&gt;
&lt;br /&gt;
The landing system is a little different in the A300, what would normally be LOC mode is called V/L. Pressing V/L will engaged Nav1 Localizer hold and the LAND button engages Glideslope hold. Also note that LAND mod will not climb so engaging LAND mode while still under the G/S is safe :)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [http://http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=23596/ A300-600 development progress can be viewed here]&lt;br /&gt;
* [http://en.wikipedia.org/wiki/Airbus_A300 Airbus A300 Wikipedia article]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=User:Airbus330&amp;diff=76217</id>
		<title>User:Airbus330</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=User:Airbus330&amp;diff=76217"/>
		<updated>2014-09-14T06:04:22Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: Created page with &amp;quot;Hi This is Airbus330, Developer of the A300-600&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi This is Airbus330, Developer of the A300-600&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airliner_development_status&amp;diff=74307</id>
		<title>Airliner development status</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airliner_development_status&amp;diff=74307"/>
		<updated>2014-07-28T11:40:59Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: Showed development of A300-600&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.&lt;br /&gt;
&lt;br /&gt;
= Airbus Industries =&lt;br /&gt;
== Airbus A300 ==&lt;br /&gt;
* Airbus A300-B2 - {{alds|stalled}}&lt;br /&gt;
* Airbus A300-B4 - {{alds|stalled}}&lt;br /&gt;
* Airbus A300-600 - {{alds|active}}&lt;br /&gt;
* [[Airbus A300-600ST]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A310 ==&lt;br /&gt;
* Airbus A310-200 - {{alds|not started}}&lt;br /&gt;
* [[Airbus A310-300]] - {{alds|active}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A320 ==&lt;br /&gt;
* [[A320-family]]&lt;br /&gt;
** Airbus A318-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A318-200 - {{alds|stable}}&lt;br /&gt;
** Airbus A319-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A319-200 - {{alds|stable}}&lt;br /&gt;
** Airbus A320-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A320-200 - {{alds|stable}}&lt;br /&gt;
** Airbus A321-100 - {{alds|stable}}&lt;br /&gt;
** Airbus A321-200 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
* [[Airbus A320neo|A320neo]]&lt;br /&gt;
** Airbus A319neo - {{alds|active}}&lt;br /&gt;
** Airbus A320neo - {{alds|active}}&lt;br /&gt;
** Airbus A321neo - {{alds|active}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A330 ==&lt;br /&gt;
* [[Airbus A330-200]] - {{alds|stable}}&lt;br /&gt;
* Airbus A330-200F - {{alds|not started}}&lt;br /&gt;
* [[Airbus A330-300]] - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A340 ==&lt;br /&gt;
* Airbus A340 - {{alds|not started}}&lt;br /&gt;
* [[Airbus A340|Airbus A340-300]] - {{alds|stalled}}&lt;br /&gt;
* [[Airbus A340|Airbus A340-500]] - {{alds|active}}&lt;br /&gt;
* [[Airbus A340-600]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A350 ==&lt;br /&gt;
* Airbus A350-800 -{{alds|not started}}&lt;br /&gt;
* Airbus A350-900 - {{alds|stable}}&lt;br /&gt;
* Airbus A350-1000 -{{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Airbus A380 ==&lt;br /&gt;
* [[Airbus A380|Airbus A380-800]] - {{alds|active}}&lt;br /&gt;
* Airbus A380-900 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Avions Transportation Regional =&lt;br /&gt;
== ATR-42 ==&lt;br /&gt;
* ATR-42-200 - {{alds|not started}}&lt;br /&gt;
* ATR-42-300 - {{alds|not started}}&lt;br /&gt;
* ATR-42-500 - {{alds|stalled}}&lt;br /&gt;
* ATR-42-600 - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
== ATR-72 ==&lt;br /&gt;
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}&lt;br /&gt;
* ATR-72-600 - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
= Boeing Commercial Airplanes =&lt;br /&gt;
== Boeing 707 ==&lt;br /&gt;
* [[Boeing 707]]&lt;br /&gt;
** Boeing 707-100 - {{alds|not started}}&lt;br /&gt;
** Boeing 707-200 - {{alds|not started}}&lt;br /&gt;
** Boeing 707-300 - {{alds|abandoned}}&lt;br /&gt;
* Boeing 720 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 717 ==&lt;br /&gt;
* [[Boeing 717|Boeing 717-200]] - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 727 ==&lt;br /&gt;
* Boeing 727-100 - {{alds|not started}}&lt;br /&gt;
* Boeing 727-200 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 737 ==&lt;br /&gt;
* Boeing 737-100 - {{alds|abandoned}}&lt;br /&gt;
* Boeing 737-200 - {{alds|abandoned}}&lt;br /&gt;
* [[Boeing 737-300]] - {{alds|stalled}}&lt;br /&gt;
* [[Boeing 737-400]] - {{alds|stalled}}&lt;br /&gt;
* [[Boeing 737-500]] - {{alds|stalled}}&lt;br /&gt;
* Boeing 737NG models - {{alds|active}} by [[user:zakalawe]]&lt;br /&gt;
* [[Boeing 737-7 MAX]] - {{alds|not started}}&lt;br /&gt;
* [[Boeing 737-8 MAX]] - {{alds|not started}}&lt;br /&gt;
* [[Boeing 737-9 MAX]] - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 747 ==&lt;br /&gt;
* [[Boeing 747-100]] - {{alds|abandoned}}&lt;br /&gt;
* [[Boeing 747-200]] - {{alds|abandoned}}&lt;br /&gt;
* Boeing 747-300 - {{alds|not started}}&lt;br /&gt;
* [[Boeing 747-400]] - {{alds|stable}}&lt;br /&gt;
* [[Boeing 747-8 Dreamlifter|Boeing 747-8]] - {{alds|stalled}}&lt;br /&gt;
* [[Boeing 747-8i]] - {{alds|active}}&lt;br /&gt;
* Boeing 747SP - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 757 ==&lt;br /&gt;
* [[Boeing 757-200]] - {{alds|stalled}}&lt;br /&gt;
* Boeing 757-300 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 767 ==&lt;br /&gt;
* Boeing 767-200 - {{alds|not started}}&lt;br /&gt;
* [[Boeing 767-300]] - {{alds|abandoned}}&lt;br /&gt;
* [[Boeing 767-300F]] - {{alds|active}}&lt;br /&gt;
* Boeing 767-400 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 777 ==&lt;br /&gt;
* [[Boeing 777-200]] - {{alds|stable}}&lt;br /&gt;
* [[Boeing 777-300]] - {{alds|abandoned}}&lt;br /&gt;
* Boeing 777-8X - {{alds|not started}}&lt;br /&gt;
* Boeing 777-9X - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Boeing 787 ==&lt;br /&gt;
* [[Boeing 787-8]] - {{alds|stable}}&lt;br /&gt;
* Boeing 787-9 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Bombardier Aerospace =&lt;br /&gt;
== Dash 7 ==&lt;br /&gt;
* Dash 7-100 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Dash 8 ==&lt;br /&gt;
* Dash 8-300 - {{alds|abandoned}}&lt;br /&gt;
* Dash 8-Q400 - {{alds|active}}&lt;br /&gt;
&lt;br /&gt;
== Canadair Regional Jets ==&lt;br /&gt;
* [[CRJ-200|CRJ200]] - {{alds|active}}&lt;br /&gt;
* CRJ700 - {{alds|stable}}&lt;br /&gt;
* [[CRJ-900|CRJ900]] - {{alds|stable}}&lt;br /&gt;
* CRJ1000 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== CSeries ==&lt;br /&gt;
* CS100 - {{alds|stalled}}&lt;br /&gt;
* CS300 - {{alds|stalled}}&lt;br /&gt;
&lt;br /&gt;
= Douglas Aircraft Company =&lt;br /&gt;
== DC-1 ==&lt;br /&gt;
* DC-1 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-2 ==&lt;br /&gt;
* DC-2 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== DC-3 ==&lt;br /&gt;
* DC-3 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== DC-4 ==&lt;br /&gt;
* DC-4 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-5 ==&lt;br /&gt;
* DC-5 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-6 ==&lt;br /&gt;
* DC-6 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== DC-7 ==&lt;br /&gt;
* DC-1 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-8 ==&lt;br /&gt;
* DC-8-10 - {{alds|not started}}&lt;br /&gt;
* DC-8-20 - {{alds|not started}}&lt;br /&gt;
* DC-8-30 - {{alds|not started}}&lt;br /&gt;
* DC-8-40 - {{alds|not started}}&lt;br /&gt;
* DC-8-50 - {{alds|not started}}&lt;br /&gt;
* DC-8-60 - {{alds|stable}}&lt;br /&gt;
* DC-8-70 - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== DC-9 ==&lt;br /&gt;
* DC-9-10 - {{alds|not started}}&lt;br /&gt;
* DC-9-20 - {{alds|not started}}&lt;br /&gt;
* DC-9-30 - {{alds|stable}}&lt;br /&gt;
* DC-9-40 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== DC-10 ==&lt;br /&gt;
* DC-10-10 - {{alds|not started}}&lt;br /&gt;
* DC-10-20 - {{alds|not started}}&lt;br /&gt;
* DC-10-30 - {{alds|abandoned}}&lt;br /&gt;
* DC-10-40 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Embraer Manufacturers =&lt;br /&gt;
== Embraer 120 Series ==&lt;br /&gt;
* EMB120 - {{alds|not started}}&lt;br /&gt;
* EMB125 - {{alds|not started}}&lt;br /&gt;
* EMB140 - {{alds|not started}}&lt;br /&gt;
* EMB145 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Embraer E-jet Series ==&lt;br /&gt;
* ERJ170 - {{alds|stable}}&lt;br /&gt;
* ERJ175 - {{alds|stable}}&lt;br /&gt;
* ERJ190 - {{alds|stable}}&lt;br /&gt;
* ERJ195 - {{alds|stable}}&lt;br /&gt;
* Legacy - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
= Fokker Aero-structures =&lt;br /&gt;
== Fokker F27 ==&lt;br /&gt;
* Fokker F27 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 50 ==&lt;br /&gt;
* [[Fokker 50]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 60 ==&lt;br /&gt;
* Fokker 60 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 70 ==&lt;br /&gt;
* [[Fokker 70]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== Fokker 100 ==&lt;br /&gt;
* [[Fokker 100]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
= Lockheed Corporation =&lt;br /&gt;
== Lockheed 1049H ==&lt;br /&gt;
* L1049H  - {{alds|stable}}&lt;br /&gt;
&lt;br /&gt;
== Lockheed L1011 ==&lt;br /&gt;
* L1011-1 - {{alds|not started}}&lt;br /&gt;
* L1011-100 - {{alds|not started}}&lt;br /&gt;
* L1011-200 - {{alds|not started}}&lt;br /&gt;
* L1011-500 - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
= McDonnell Douglas =&lt;br /&gt;
== MD-11 ==&lt;br /&gt;
* [[MD-11]] - {{alds|abandoned}}&lt;br /&gt;
&lt;br /&gt;
== MD-80 ==&lt;br /&gt;
* MD-81 - {{alds|stable}}&lt;br /&gt;
* MD-82 - {{alds|not started}}&lt;br /&gt;
* MD-83 - {{alds|not started}}&lt;br /&gt;
* MD-87 - {{alds|not started}}&lt;br /&gt;
* MD-88 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
== MD-90 ==&lt;br /&gt;
* MD-90 - {{alds|not started}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Aircraft enhancement]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Airbus_A330-300_Series&amp;diff=71259</id>
		<title>Airbus A330-300 Series</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Airbus_A330-300_Series&amp;diff=71259"/>
		<updated>2014-05-14T22:45:48Z</updated>

		<summary type="html">&lt;p&gt;Airbus330: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{infobox Aircraft&lt;br /&gt;
|image       = A333-splash.png&lt;br /&gt;
|name        = Airbus A330-300 Series&lt;br /&gt;
|type        = Wide-body Airliner&lt;br /&gt;
|fdm         = JSBSim&lt;br /&gt;
|status      = Git Development Version&lt;br /&gt;
|authors     = Narendran M, Chris M, Zhuang T, Geir M, Kyle D, A330-200 Developers&lt;br /&gt;
|fgname      = A330-303, A330-323, A330-343&lt;br /&gt;
|download    = https://gitorious.org/fg-airbus-a333/airbus-a330-300-main/archive-tarball/master&lt;br /&gt;
|development = https://gitorious.org/fg-airbus-a333/airbus-a330-300-main&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This aircraft package is now rembrandt compatible! (Simply checkout the rembrandt branch from the git repository to get it)&lt;br /&gt;
&lt;br /&gt;
The '''Airbus A330-300 series''' project consists of the '''Airbus A330-303''' (A330-300 with ''General Electric CF6-80E1 Engines''), '''Airbus A330-323''' (A330-300 with ''Pratt and Whitney PW4000 Engines'') and the '''Airbus A330-343''' (A330-300 with ''Rolls Royce Trent 772B-60 Engines''). The project uses theOmegaHangar's new [[Airbus A320neo|Airbus A320/30/40]] cockpit and systems and new Airbus A330-300 models. The A330-300 series aircraft have been converted from the same developers' Airbus A330-200 series aircraft. The following changes have been made:&lt;br /&gt;
&lt;br /&gt;
* Fuselage Length Increased (6 fuselage sectional frames in front of the wings and 4 behind)&lt;br /&gt;
* Rudder Height Decreased (to be precise, by 0.59 meters)&lt;br /&gt;
* Textures Re-mapped and new paintkits created (to accommodate to the extended models)&lt;br /&gt;
* Animations fixed (nose and tail, due to extensions)&lt;br /&gt;
* Minor FDM Changes made (CoG, Weights, Fuel, Contact Points, Metrics (VStab Area and HTail Arm))&lt;br /&gt;
* New Liveries (see below)&lt;br /&gt;
&lt;br /&gt;
Feel free to start a discussion in [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=16438 the forum topic] if you'd like to contribute to the project.&lt;br /&gt;
&lt;br /&gt;
==Airbus Systems==&lt;br /&gt;
&lt;br /&gt;
===Airbus Fly-By-Wire===&lt;br /&gt;
The Airbus fly-by-wire (adapted from the Airbus A320neo fly-by-wire) is a system which continuously takes in the pilot's stick input, uses them as Pitch/Roll-Rate commands, and calculates the required surface deflection to achieve the commanded rate. The fly-by-wire also provides flight envelope protection and the soft/hard bank feature.&lt;br /&gt;
&lt;br /&gt;
====Pitch/Roll-Rate and G-Force Command====&lt;br /&gt;
For the Roll Axis, the stick all the way to the left commands a negative 30 degrees roll rate and all the way to the right commands a positive 30 degrees roll rate.&lt;br /&gt;
&lt;br /&gt;
As for the Pitch Axis, the commands are divided according to the airspeed of the aircraft. If the Airspeed is under 210 knots, pitch-rate is used and over 210 knots, g-force is used. Under 210 knots, pulling the stick all the way to the back commands a 30 degrees pitch rate and pushing it all the way forward commands a negative 30 degrees pitch rate. Over 210 knots, pulling the stick all the way to the back commands a 2.75G acceleration and pushing it all the way forward commands a -0.75G acceleration. &lt;br /&gt;
&lt;br /&gt;
====Flight Envelope Protection====&lt;br /&gt;
For the Roll Axis, having the stick less than half way deflected either side, you get what's called a ''soft bank''. With a soft bank, the aircraft can't exceed 33 degrees of bank to either side. If the stick is deflected more than half way, you get a hard bank and the aircraft can be banked up till 67 degrees to either side.&lt;br /&gt;
&lt;br /&gt;
For the Pitch Axis, the aircraft will maintain itself between a pitch of 30 degrees nose up and 15 degrees nose down.&lt;br /&gt;
&lt;br /&gt;
=== Hydraulics System ===&lt;br /&gt;
The Airbus A320, A330 and [[Airbus A340|A340]] series have similar hydraulic systems. There are three hydraulic systems on the aircraft, each having it's own reservoir- the '''GREEN''' system, the '''YELLOW''' system and the '''BLUE''' system.&lt;br /&gt;
&lt;br /&gt;
The Green system is powered by the Left Engine's Hydraulic Pump, the yellow by the Right Engine's Hydraulic Pump and the Blue System with an Electric Pump. During normal operation, each hydraulic system should have their hydraulic pressure between 2500 and 3000 PSI. (Pounds per Square Inch) The engine systems control the surfaces, stabilizers, flaps/slats and landing gears while the electric pump system connect to only the surfaces and stabilizers. In case a system fails, an alternate system can be used. The yellow system also has an electric pump which can be used to power the hydraulics using external power when the aircraft is on the ground.&lt;br /&gt;
&lt;br /&gt;
The Yellow and Green Hydraulic systems have a power transfer unit which is used to transfer hydraulic pressure between the pumps in case there is a 500 PSI difference between the pressures in the green and yellow systems.&lt;br /&gt;
&lt;br /&gt;
All hydraulic controls (including the PTU) can be controlled form the Hydraulics section on the Overhead Panel.&lt;br /&gt;
&lt;br /&gt;
'''MORE SYSTEMS INFORMATION COMING SOON'''&lt;br /&gt;
&lt;br /&gt;
== Example Flight(s) ==&lt;br /&gt;
&lt;br /&gt;
=== Custom Emirates Flight from Frankfurt to Munich ===&lt;br /&gt;
&lt;br /&gt;
This flight was requested by Detlef N. (MIA0283), and video tutorials were recorded for different sections of the flight. The videos can be viewed below or in the ''FlightGear Airbus'' YouTube channel. Thank you for watching!&lt;br /&gt;
&lt;br /&gt;
''NOTE that these tutorials have been meant for the Airbus A330-200 series aircraft but are applicable to the A320neo and A330-300 series too. This is because of the shared flightdeck and systems on board most A3XX aircraft.''&lt;br /&gt;
&lt;br /&gt;
==== Flight Planning ====&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|R66q_10dwKw|480|auto|Part 1: Flight Planning}}&lt;br /&gt;
&lt;br /&gt;
==== Manual Start-up ====&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|8TI14RJDn2k|480|auto|Part 2: Manual Start-up}}&lt;br /&gt;
&lt;br /&gt;
==== Take-off and Climb ====&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|IpkdhebC4-o|480|auto|Part 3: Take-off and Climb}}&lt;br /&gt;
&lt;br /&gt;
''NOTE: Cruise skipped due to the fact that it may be '''boring'''''...&lt;br /&gt;
&lt;br /&gt;
==== Descent and Autoland ====&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|NeX3samzrqU|480|auto|Part 4: Descent and Autoland}}&lt;br /&gt;
&lt;br /&gt;
== Liveries ==&lt;br /&gt;
The Airbus A330-300 series have liveries for each variant (303, 323 an 343) and are managed by Chris M (muffinman). Please let us know if you're creating a livery by changing the status on the livery below so that duplicates are avoided.&lt;br /&gt;
&lt;br /&gt;
=== Airbus A330-303 Liveries ===&lt;br /&gt;
'''''All liveries complete!'''''&lt;br /&gt;
{|&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; |&lt;br /&gt;
* KLM - '''COMPLETE'''&lt;br /&gt;
* Qantas - '''COMPLETE'''&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; |&lt;br /&gt;
* Qatar - '''COMPLETE'''&lt;br /&gt;
* XL Airways - '''COMPLETE'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Airbus A330-323 Liveries ===&lt;br /&gt;
'''''All liveries complete!'''''&lt;br /&gt;
{|&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; |&lt;br /&gt;
* Air Caraibes - '''COMPLETE'''&lt;br /&gt;
* Asiana Airlines - '''COMPLETE'''&lt;br /&gt;
* Czech Airlines - '''COMPLETE'''&lt;br /&gt;
* Delta Air Lines - '''COMPLETE'''&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; |&lt;br /&gt;
* Korean Air - '''COMPLETE'''&lt;br /&gt;
* Malaysia ('''one'''world) - '''COMPLETE'''&lt;br /&gt;
* Thai Airways International - '''COMPLETE'''&lt;br /&gt;
* US Airways - '''COMPLETE'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Airbus A330-343 Liveries ===&lt;br /&gt;
{|&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; |&lt;br /&gt;
* Aeroflot (SkyTeam) - '''COMPLETE'''&lt;br /&gt;
* AirAsia X&lt;br /&gt;
* Air Canada - '''COMPLETE'''&lt;br /&gt;
* Air Canada (Star Alliance) - '''COMPLETE'''&lt;br /&gt;
* Air China - '''COMPLETE'''&lt;br /&gt;
* Air Transat (Previous Livery) - '''COMPLETE'''&lt;br /&gt;
* Cathay Pacific - '''COMPLETE'''&lt;br /&gt;
* Cathay Pacific ('''one'''world) - '''COMPLETE'''&lt;br /&gt;
* Cebu Pacific Air&lt;br /&gt;
* China Eastern - '''COMPLETE'''&lt;br /&gt;
* China Southern - '''COMPLETE'''&lt;br /&gt;
* Corsair International&lt;br /&gt;
* Dragonair - '''COMPLETE'''&lt;br /&gt;
* Edelweiss Air - '''COMPLETE'''&lt;br /&gt;
* EgyptAir&lt;br /&gt;
* Etihad&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; |&lt;br /&gt;
* Hainan&lt;br /&gt;
* Hong Kong Airlines&lt;br /&gt;
* Lufthansa - '''COMPLETE'''&lt;br /&gt;
* Oman Air&lt;br /&gt;
* Saudi Arabian Airlines&lt;br /&gt;
* SAS - '''COMPLETE'''&lt;br /&gt;
* SAS (Star Alliance) - '''COMPLETE'''&lt;br /&gt;
* Sichuan Airlines&lt;br /&gt;
* Singapore Airlines - '''COMPLETE'''&lt;br /&gt;
* Swiss International Air Lines - '''COMPLETE'''&lt;br /&gt;
* Thai Airways International - '''COMPLETE'''&lt;br /&gt;
* Thomas Cook Airlines Scandinavia - '''COMPLETE'''&lt;br /&gt;
* Transasia Airways - '''COMPLETE'''&lt;br /&gt;
* Turkish Airlines - '''COMPLETE'''&lt;br /&gt;
* Virgin Atlantic - '''COMPLETE'''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Default Flight Database==&lt;br /&gt;
&lt;br /&gt;
The Airbus A330-300 series do NOT have an airline's flight database. It's open for users to add their own routes. Nevertheless, a few Singapore Airlines A330-300 routes might be added to the default database in the near future.&lt;br /&gt;
&lt;br /&gt;
== External link ==&lt;br /&gt;
* [http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=16438 Development topic]&lt;br /&gt;
&lt;br /&gt;
{{Airbus}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Airliners]]&lt;/div&gt;</summary>
		<author><name>Airbus330</name></author>
	</entry>
</feed>