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

== FlightGear events ==
== Development news ==

===Local Weather v0.85===
The [http://www.phy.duke.edu/~trenk/files/local_weather_fgfs2.0.0_v0.85.tgz version 0.85] (also on GIT) of the Local Weather package is out - with new cloud types and textures and most importantly a significant performance gain over previous versions. There is a new menu to allow the user at runtime to specify cloud visual ranges, so that the impact on framerate can be adjusted to the situation.

The increased performance means that 3d clouds on fast systems can be rendered out to 45 km, and high altitude 2d cloud sheets sometimes up to 80 km - vastly improving the visual impression of the sky from airliner altitudes.

In addition, some bugs in the wind modelling and long-range weather patterns have been ironed out - with Flightgear 2.0.0, the package performs good in tests.

In the works:

* better hard-coded support for e.g. terrain sampling
* a METAR interface to use real-time weather and wind data
* full dynamics of the life cycle of convective clouds as they drift over the terrain
* and as always - improvements to cloud placement algorithms and cloud textures

Stay tuned!

A small feature gallery:
<gallery>
Image:local_weather_0.85_01.jpg| Cumulus and Cirrocumulus clouds (Local Weather v0.85)
Image:local_weather_0.85_02.jpg| Cirrus and Cirrostratus clouds heralding a warmfront (Local Weather v0.85)
Image:local_weather_0.85_03.jpg| 45 km cloud visibility range (Local Weather v0.85)
Image:local_weather_0.85_04.jpg| Realistic cloud bottoms (Local Weather v0.85)
Image:local_weather_0.85_05.jpg| Cumulus and Altocumulus clouds (Local Weather v0.85)
Image:local_weather_0.85_06.jpg| Multiple 3d layered clouds (Local Weather v0.85)
</gallery>

===Water shader improvements===
[[File:Water shader Ju 52.jpg|300px|left|[[Junkers Ju 52]] flying over a lake in the French custom scenery.]]
Our all-time favourite shader-artist, Gral, picked up yet another project. This time it is something that covers over 70% of the entire scenery and is thus of great importance in a flight simulator: water. The new shader includes more realistic wave movements and much nicer sun "reflections". The extreme goal is to have real-time reflective water, which is still a long way to go, but with Gral's latest improvements we've at least made a step into the right direction. Transatlantic or Carribean flights have never been so exiting in FlightGear!

=== Weather supporting core code ===
[[File:new_weather_dialog.png|150px|right|The new weather dialog]]
The weather supporting core of FlightGear [http://gitorious.org/fg/flightgear/commit/5c6fe952598053fa63631fc0161d666f22a50f51 has been modified] during the last weeks to better support new weather models like the above mentioned Local Weather system. Data flow between environment systems is now defined in XML config files using well [[Autopilot Configuration Reference|known syntax and elements from the autopilot]]. Complex rules using predefined filters and arbitrary expressions can be defined without the need for C++ or Nasal coding.
Along with this patch comes a unified weather settings dialog, combining previous dialogs for weather conditions, scenario, clouds and precipitation. Further plans are to integrate a new real world data source [http://www.navlost.eu/nwxs/doc/desc/ NWX], providing METAR, aloft and temperature at altitude.

=== AI Objects ===
[[File:AIWingmenandAITanker.jpg|thumb|[ AIWingmen and AITanker]]

Some of the AI code has been revisited and tidied up, in a somewhat vain attempt to reduce the impact on frame rate. The facilities in Slaved Ballistic Objects, Wingmen, Ground Vehicles, and Escorts have been generalized. Now, any of these types can be subordinated, or parented, on any AI object which has a <name> tag. Thus, a wingman can be formated on a an AI Tanker, and can have a slaved droptank.

A Wingman can be formated on a Wingman to build larger formations.
[http://www.youtube.com/v/YaBghBIZZWI B29 12 Ship Formation]

With careful choice of options and locations frame rates can be kept at a reasonable level. Analysis has shown that the tall pole in the tent is the code which measures Altitude Above Ground Level. This is known to be code that is heavy on framerate and which is used extensively in the AI code. It might be possible to get a cheaper, simpler version of this function which would improve the impact on framerate. Hopefully, this will be the next stage of development.

== Nasal for newbies: OOP ==
OOP is all about creating "things" (i.e. a cloud) with "actions" (transform,draw,update) (or "messages").
Where a class (or hash in Nasal) is the "template" for a "thing" containing a number of member fields.
So the class only describes the "layout" or properties of objects that can be created. To actually use a class, it has to be "instantiated" which means creating an object using a specific "template class" (or even several different classes).

These member fields can be variables (e.g. lat, lon, alt) or functions (setAlt, setPos).
And the actual instance (cloud[n] in the property tree) of such a thing is then called an "object".
Functions that work with instance specific state are called "methods", they may refer to instance specific state using a "self reference" (me) in Nasal, that ensures that access to a field or method is using the right instance specific data.

In OOP, internal state is managed by wrapping everything in a class using accessor functions for modifying and getting internal values.
So internal state would in turn only be modified by an abstract interface: class "methods", instead of directly accessing class-internal fields.

This provides a way for managing access to a member variable (field), such an abstract interface is also useful for keeping logics private, and internal. For example, the name of a variable "altitude" can be easily changed internally to "altitude_ft", without having to rename all users of the class - simply because all other code will refer to the methods providing access to the field.

For example, instead of doing something like cloud.lat=10.22; cloud.lon=43.22; you would have a method accepting lat/lon variables: cloud.setPos(lat, lon);

That means that the actual variables containing the values for lat/lon are not exposed or used outside the actual object. This is called encapsulation and provides you with a way to manage state and ensure that internal state is valid at all times, because other code may only use the external interface.

This allows you for example to simply rename a class variable, without having to change any of the code that uses the object, because other code only uses class methods.

Another important thing in OOP is separation of concerns, i.e. you don't want to end up with huge bloated "super classes" that manage all sorts of different state, but instead use different classes where appropriate to split code into abstract "modules" with well defined responsibilities.

So, one of the very first steps to convert procedural code to OOP code would be to group your code into a number of logical "classes" (e.g. cloud, cloud field ).

Classes may be composed of other classes, i.e. a "cloud field" class would in turn contain "cloud" classes.
This is then called "composition".

Another way is inheritance, where a type may inherit properties (fields:variables and methods) from a "parent" class. Imagine it like taking a "template" for the class and then saying "make a new class using this template".

Inheritance has the added advantage of providing a means to customize class behavior without having to modify the actual class, because all member fields can be parametrized.

For example, a "cumulus" cloud class could be derived from the "cloud" class, just by parametrizing it (different cloud model, different texture, different transformations), without touching anything in the actual "cloud" class.

This is basically how OOP may be understood: things are classified according to "is a" or "has a" relationship.

Of course, one may still use objects like conventional variables for passing and returning parameters.

== New software tools ==
== FlightGear addons and mods ==
== In the hangar ==
===Livery hangar reaches 300===
Early September, the [http://liveries.flightgear.org/ FlightGear Livery Database] welcomed its [http://liveries.flightgear.org/liveries.php?id=301 300th livery]! It is a livery of the Polish Air Force's [[Lockheed C130]], created by Maciej Zgódka, one of the latest additions to the painters-team. In the same time, the database was upgraded with a couple of new "features":
* thumbnails of liveries pop up when you hover over a link.
* a contact page was added, to ease contacting the database maintainer.
* each livery has a "Report this livery" button, through which visitors can notify the maintainer of a broken download, incorrect or unknown author, licensing issues etc.

I would like to emphasize that lots of liveries are not yet assigned an author. Please check for yourself if there is any [http://liveries.flightgear.org/authors.php unknown-author-livery] of which you known/are the author. Lots of liveries are still in the need for a thumbnail, so those are welcome as well.
===BAe-146===
"Pilot Penguin" and "[[User:Nickyivyca|nickyivyca]]" have begun work on the BAe-146. Pilot Penguin will be doing mostly 3D work, and nick will be doing mostly FDM and systems work. [http://flightgear.org/forums/viewtopic.php?f=4&t=9494&start=15 See the forum thread for more info.]

== Scenery corner ==
===UK Football Stadiums===
[[File:Emiratesstadium.jpg|thumb|Emirates Stadium in Flightgear]]
Andyramone has completed and submitted three football stadiums to the scenery database. These include Carrow Road (Norwich), Emirates Stadium (Arsenal) and Stamford Bridge (Chelsea.) Portman Road (Ipswich) and White Hart Lane (Tottenham) are complete and will be submitted to the scenery database this month. The project will continue later this year with more London stadiums including Wembley on the to do list.

===Liverpool John Lennon Airport===
Andyramone has begun modeling Liverpool Airport (EGGP) in the UK. The terminal is complete and will be submitted to the database this month. Work has already begun on the control tower.

===KSFO Terminal 2===
San Fransisco International Terminal 2 has been fully remodelled by karla in Blender 2.49b using handmade textures in Gimp 2.46. New additions include: linking wings, antennae, railings, supports, ground floors interiors, ATC equipment, vigilant controller, architecture, light masts, night textures.

It has been released and is available from the Git database or directly from http://www.mediafire.com/file/ev447wrsqrfijlf/KSFO_T2.zip

The associated 942050.stg file has been changed slightly and it may also be downloaded for replacement in /Scenery/Objects/w130n30/w123n37/.

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

== Suggested flights ==
===Hawai'i===
[[Image:Maui03.jpg|thumb]]
Do you use [[TerraSync]]? If so, try a flight around Hawaii! Take off from PHNL in a light aircraft and head west until you hit Pearl Harbor; a right turn north will take you post the USS Arizona Memorial, and the Punchbowl Crater will be to your right. Or, fly east from PHNL past volcanic craters Diamond Head and Koko Head. If you follow the O'ahu coastline north from Koko Head, you can land at either old World War II airbase Bellows Field (now a wildlife reserve in real life) or at Keahole MCAS.

For a potentially more scenic route, fly east toward Molokai, and stay to the north (left) of the island. The northern part of Molokai features huge sea cliffs and a tiny airstrip on the Kalaupapa peninsula - the peninsula being the only respite from the cliffs. A former leper colony existed near the airstrip!

Also of interest are the volcanoes on Maui and the 'Big Island' of Hawai'i - flying VFR in a small plane from PHTO to PHKO over the plateau between Mauna Kea and Mauna Loa can be a challenge, as you have to take off from sea level, fly through a pass of 6500 feet, and then drop back down to sea level to land! The Hana coast of northern Maui is also a nice flight - a circumnavigation of Haleakala, starting and ending at PHOG, is quite a nice flight.

The islands will be available through the download center with the next major scenery release, but for now, fire up [[TerraSync]] and your favorite VFR aircraft and have a blast.

== Aircraft reviews ==

== Community news ==
=== FlightGear on youtube ===
* Ten students at NASA's LARSS (Langley Aerospace Research Summer Scholars), put together [http://www.youtube.com/watch?v=YmnFP-1UlSY an autonomous robotics lab], using mostly open source tools. One of which is a FlightGear Multiplayer Server.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

=== Forum news ===
=== Wiki updates ===
=== Multiplayer ===
=== Virtual airlines ===

== Useful links ==
== And finally ... ==
Next [http://www.fsweekend.com/ FSWeekend] event takes place November 6 & 7th 2010. Mark this date in your calendar and expect an outstanding presentation of FlightGear's features at [[Lelystad_Airport|Lelystad's airport]].

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2010 09]]

Howto:Animated jetways (Type 1)

2010-09-09T02:04:48Z

Nickyivyca: /* Usage */

[[File:777jetwaybeaf.jpg|thumb|right|300px|Before and after; jetways connecting to a [[Boeing 777-200]]]]

This article describes the animated jetway system by [[User:Skyop|Skyop]], how to use it, and how to implement it.

=Usage=

[[File:KLAS_jetways.png|thumb|right|300px|Movable jetway connected to a [[Boeing 737-300]] at Las Vegas McCarran International Airport (KLAS)]]

Currently, the following airports implement animated jetways in their scenery:

* Las Vegas McCarran International Airport (KLAS) ([[TerraSync]]-only)

'''Note that when TerraSyncing an airport, you have to tell [[FlightGear]] to load the new jetway models. To do this, set the <tt>/sim/paths/use-custom-scenery-data</tt> property to "true" in [[FGRun]]. Command-line users, use the <tt>--prop:/sim/paths/use-custom-scenery-data=true</tt> switch.'''

The following aircraft are animated-jetway capable:

* [[Boeing 737-300]] (separate download)
* [[Boeing 747-400]] (separate download)
* [[Boeing 777-200ER]] (separate download)
* [[Boeing 787|Boeing 787-8]] (Jetway #2 disabled, it goes through an engine)
* [[Bombardier CRJ-200LR]] (As part of official new release)
* [[Airbus A320]]

First determine if the jetway is clickable and is animated. To do this, press Ctrl-C. If the polygons of the jetway are outlined in yellow, then it is indeed animated.

Now align your airliner so that the nosegear is centered on the marking line and is directly over the "T" at the end of it. Click the jetway; if your aircraft does not include the required positioning information, you'll get a tooltip informing you that the jetway cannot be extended. Otherwise, the jetway should begin to position itself and eventually connect to your aircraft. Congratulations!

=Implementation=

==For aircraft developers==

To make your aircraft animated jetway-capable, you'll need to specify the following in your aircraft's -set.xml:

* The amount at which to extend the jetway (<tt>x-tra</tt>)
* The amount at which to lower/raise the jetway by rotating it along its Y axis (<tt>y-rot</tt>)
* The amount at which to rotate the jetway along its Z axis (<tt>z-rot</tt>)
* The amount at which to rotate the hood to extend it to the aircraft (<tt>hood-rot</tt>)

They should be added within the <tt><aircraft></tt> tag in the root of your XML file (but still within <tt><PropertyList></tt> of course!).

For instance, here's the jetway positioning information for the Boeing 737-300.

<aircraft>
<jetway-pos>
<x-tra>-1</x-tra>
<y-rot>-4</y-rot>
<z-rot>21</z-rot>
<hood-rot>5</hood-rot>
</jetway-pos>
</aircraft>

Here's the positioning information for the Boeing 777-200ER. Note the <tt><jetway2-pos></tt>, which describes positioning information for the second jetway.

<aircraft>
<jetway-pos>
<x-tra>-1</x-tra>
<y-rot>4</y-rot>
<z-rot>16</z-rot>
<hood-rot>2</hood-rot>
</jetway-pos>
<jetway2-pos>
<x-tra>2.5</x-tra>
<y-rot>5</y-rot>
<z-rot>46</z-rot>
<hood-rot>2</hood-rot>
</jetway2-pos>
</aircraft>

Last but certainly not least, the A380:

<aircraft>
<jetway-pos>
<x-tra>-2</x-tra>
<y-rot>2</y-rot>
<z-rot>18</z-rot>
<hood-rot>0</hood-rot>
</jetway-pos>
<jetway2-pos>
<x-tra>2.5</x-tra>
<y-rot>2.5</y-rot>
<z-rot>45</z-rot>
<hood-rot>0</hood-rot>
</jetway2-pos>
<jetway3-pos>
<x-tra>4</x-tra>
<y-rot>5</y-rot>
<z-rot>47</z-rot>
<hood-rot>3</hood-rot>
</jetway3-pos>
</aircraft>

The following will describe how to get these values. I will be using [[Blender]] for this purpose, but any 3D modeling program that can read [[AC3D]] files will suffice.

First, open up your 3D modeling suite and import one of the jetway models. They are located at <tt>(TerraSync directory)/Models/Airport</tt>, and are available through [[TerraSync]] or the [http://scenemodels.flightgear.org/modelbrowser.php?shared=7 Airport section of the FlightGear Scenery Database model directory] (look for "jetway-movable.xml," "jetway-movable-2.xml," or "jetway-movable-3.xml").

Now import your aircraft model (in this case, I am using [[User:Gijs|Gijs']] [[Boeing 747-400]]). Align it with the marking line as if you were piloting it.

[[File:Ajetway-air-tut1.png|800px]]

Now select the following objects: Tunnel2, Tunnel3, Rotunda2, Entrance, and Hood. Move them along their X axis until you think you have the correct length to extend the jetway. ''(Hint: You can always "retract" the jetway by moving these objects by a negative value!)''

[[File:Ajetway-air-tut2.png|800px]]

Now select the following objects: Tunnel1Rotunda, Tunnel1, Tunnel2, Tunnel3, Rotunda2, Entrance, and Hood. Rotate them along the Z axis with the center of axis being at 0,0,0 (X,Y,Z) until the jetway's movable rotunda is a couple meters or so away from the aircraft. In Blender, I could simply move my cursor to 0,0,0 and set the rotation pivot to cursor mode. The procedure will be different depending on what 3D modeling software you are using, of course. You may have to undo this step if you find that you extended the jetway too much or too little in the previous step.

[[File:Ajetway-air-tut3.png|800px]]

Once you are happy with the jetway's extension/rotation, use the amount you extended the jetway along its X axis as your <tt><x-tra></tt> value and the amount you rotated the jetway along its Z axis as your <tt><z-rot></tt> value.

In-game, the jetway's entrance will automatically rotate itself to compensate for the rest of the jetway's rotation, so there is no need to manipulate the entrance.

Now, undo all transformations you have done to the jetway until it is in the same state as it was when you imported it. Select the following objects: Tunnel1, Tunnel2, Rotunda2, Entrance, and Hood. Rotate them along the Y axis with the center of axis being at 1.5,0,4 until the entrance of the jetway aligns with the door of the aircraft vertically. Use the value you rotated the jetway at as your <tt><y-rot></tt> value ''(note: the values should be inverted, so if you rotated the jetway along its Y axis -2 degrees to get it 2 degrees up, you should use 2 instead of -2)''.

[[File:Ajetway-air-tut4.png|800px]]

Finally, we have one last value to fill in: <tt><hood-rot></tt>. It simply specifies how much the jetway's hood should extend itself by rotation. You can simply use some common sense here: obviously, this would be something along the lines of 0 for jumbo jets and 5 for a Boeing 737-like aircraft. Be careful not to set this value to something too high, otherwise the hood will appear to detach itself from the jetway!

Eventually, you should end up with an <tt><aircraft></tt> tree that resembles the examples above. Load up your aircraft in-game and taxi to an animated jetway. Click it, and hope everything works well!

[[File:Ajetway-air-tut5.jpg|800px]]

The procedure for utilizing a second or third jetway is essentially the same. The only difference is that some center of axis coordinates need to be changed (i.e., rotating the entire jetway by its Z axis from point 18,-5,0 instead of 0,0,0.

==For scenery developers==

[[File:Animatedjetway1.jpg|thumb|right|270px|A gate with one animated jetway; note the style, the details, and the level walking passage]]

Simply place a <tt>Models/Airport/jetway-movable.xml</tt> wherever you want- note that the origin of the jetway models are always at the terminal rotunda of the first jetway. You can download the movable jetway models through [[TerraSync]] or from [http://scenemodels.flightgear.org/modelbrowser.php?shared=7 the Airport section of the FlightGear Scenery Database model directory] (look for "jetway-movable.xml," "jetway-movable-2.xml," or "jetway-movable-3.xml").

==For scenery modelers==

The default animated jetway design is very common throughout the world, and found in practically all major United States airports. If you wish to create your own style though (i.e. glass jetways), then the simplest method would be to retexture one of the default animated jetways and copy the contents of its XML file (but change the <tt><path></tt>, of course).

You could create an entirely different jetway model, but you must keep the object names the same, and everything in the '''exact''' same location. Copy the contents of the XML file for one of the default animated jetways (but change the <tt><path></tt>, of course).

=External links=

* [http://tinypic.com/player.php?v=ajul44&s=4 Video showcasing the animation]
* [http://www.flightgear.org/forums/viewtopic.php?t=8728 Development thread]

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

2010-07-23T04:49:08Z

Nickyivyca: 787 Dreamliner current photo.

787 Dreamliner current photo.