__NOTOC__
{{User
|name = José Roberto Silva
|location = Guarulhos, Greater São Paulo, Brazil
|callsign = PT-RSB
|favourite =[[Airbus A320]], [[Boeing 737]], [[Boeing 747-400]]
|website =[http://josesilvafgliveries.blogspot.com/]
}}

Languages: '''Brazilian Portuguese and English (level 3)'''

==Liveries==
===To Do===
'''Open for requests!'''

*BRA [[Boeing 737-300]] New Colors

===Done===
*BRA [[Boeing 737-300]] Old Colors
*TAM [[Boeing 767-300]]
*Qantas [[Boeing 767-300]]
*Gol [[Boeing 737-300]]
*Royal Brunei [[Boeing 767-300]] '''''(superseded by Patrick's version)'''''

==Wiki Articles==
'''Newsletters in general, Pt/Portals and...'''
===Translation to Portuguese===
====To Do====
*New to FlightGear - (Novo no FlightGear) - in progress as of 2010/07
*Flying the Helicopter - (Como voar de helicóptero) - in progress as of 2010/07
====Done====
*FlightGear - [[Pt/FlightGear|Translated version]]
*Installing Scenery - [[Pt/Instalando Cenário||Translated version]]

Talk:FlightGear Newsletter July 2010

2010-07-27T04:10:42Z

Rsbrflyer:

==Virtual Airline News Section?==

Good idea? Bad idea? What do you all think?--<span style="text-shadow: Palegreen -0.6em -0.6em -0.1em; class=texhtml">[[User Talk:Armchair Ace|<font color="ForestGreen" face="georgia"> Armchair Ace</font>]]</span> 11:20, 26 July 2010 (UTC)

''I bet it is going to start a flame war (again)... [[User:Rsbrflyer|Rsbrflyer]] 23:17, 26 July 2010 (UTC)''

I suppose you're right. Plan scrapped.--<span style="text-shadow: Palegreen -0.6em -0.6em -0.1em; class=texhtml">[[User Talk:Armchair Ace|<font color="ForestGreen" face="georgia"> Armchair Ace</font>]]</span> 01:31, 27 July 2010 (UTC)

''I really don't get why to flame for a virtual airline but, well...'' [[User:Rsbrflyer|Rsbrflyer]] 04:10, 27 July 2010 (UTC)

Talk:FlightGear Newsletter July 2010

2010-07-26T23:17:08Z

Rsbrflyer: /* Virtual Airline News Section? */

FlightGear Newsletter July 2010

2010-07-26T04:07:26Z

Rsbrflyer: more acft., typos correction, welcome section (feel free to remove =P)

{{newsletter}}
{{TOC_right}}

Welcome to the July edition of the FlightGear Newsletter! June has seen more scenery work than new or improved aircraft.

This month's newsletter marks a year since [[FlightGear Newsletter July 2009|the first issue]] was written!

==Newsletter history==

One year ago, in June 2009, [[FlightGear]]-head Curt proposed his newsletter-idea [http://www.flightgear.org/forums/viewtopic.php?f=6&t=5201 at the forum]. With multiple (failed) efforts in the past, those involved were extremely eager to get it up and going this time. Stuart was the one that wrote most of the first issue(s). At the time of the second issue, more people were involved and wrote a paragraph or two.

Today, the newsletter is written by a bunch of people, with different interests and relations to FlightGear. It provides an easy way to keep up-to-date with the ongoing developments; both in FlightGear itself and in the community around it.

We would like to use this opportunity to thank those that contributed over the past year. Thanks to their work, the newsletter still exists! In order to reach our next milestone, we would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone (with a wiki account, [[Special:UserLogin|click to register]]) can edit the newsletter and every contribution is welcome.

Now, all we can say is: enjoy this brand new edition!

==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 misconception 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.

Some ideas:

* writing articles for the [http://wiki.flightgear.org/index.php/Next_newsletter next issue of this newsletter]
* sending corrections/updates to the FlightGear Manual
* helping new users on the forums/IRC
* writing a wiki page
* organizing fly-outs

One of the easiest ways to help is to improve the scenery in your local area by placing buildings/structures using the UFO and submitting them to the [http://scenemodels.flightgear.org/contribute.php FlightGear Scenery Object Database]. It's easy, and best of all requires little time to have a real impact. Instructions on how to do this can be found in the wiki, article [[Placing 3D Objects with the UFO]].

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

==Reminder: Google Summer of Code 2011==

We would like to remind all readers that the FlightGear project is planning to participate in Google's Summer of Code 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.
Some easy ways for helping right now would be:

* suggest new project ideas (i.e. get in touch using the forums, mailing lists or the wiki)
* browse the forums or mailing list archives and look for suitable candidate projects
* help refine and improve existing project proposals
* help finalize the application template that we are preparing
* help us find suitable students who might be interested in participating in 2011
* help us find mentors
* summarize all related discussions, and document them here in the wiki

At the moment, we are collecting ideas for answering the various questions in the application: [http://flightgear.org/forums/viewtopic.php?f=38&t=8857 Why should FlightGear participate in GSoC?]

If you have any questions or other feedback related to GSoC, please use the forum to get in touch: [http://flightgear.org/forums/viewforum.php?f=38]

==Development news==

===A new forum for Google Summer of Code===
As some of you may already know, there is now an orchestrated effort going on to get FlightGear ready for becoming a mentoring organization in Google's Summer of Code 2011.

So far, all related information has been collected here in the wiki: [[GSoC]].
But to ease the planning and organization process, there has now been a new sub forum set up for talking about anything that is one way or another related to this effort.
The forum can be found at: http://flightgear.org/forums/viewforum.php?f=38

This should make it much easier for all community members to participate in all related discussions, without necessarily having to be subscribed to the mailing lists.

So if you have anything to contribute to this topic, please do make sure to check out this new forum.

You are for example also invited to make suggestions for new FlightGear related GSoC projects.

For the time being, one topic from the "New Features" sub forum has already been moved to this new forum, it is about a suggestion to procedurally populate the FlightGear scenery with dynamically created cities, for more details please check out [[AutoGen Scenery for FlightGear]].

===Local weather system update===

The local weather system is moving towards dynamical weather. Currently, an experimental version v0.73 is released which demonstrates the cloud drift in the wind (see more information [http://www.flightgear.org/forums/viewtopic.php?f=5&t=7358 here]). The upcoming release v0.8 which is currently in the final stages of being prepared will include

* Drift of clouds, thermals and other weather effects in the wind, enabling for example a realistic soaring experience in strong winds.

* Several available models for the wind field, including high-altitude wind patterns that gradually change along the aircraft route.

* A moderately complex model for the boundary layer, i.e. the region where the wind field interacts with terrain. The boundary layer thickness and wind speed reduction effect becomes tied to the roughness of the terrain - for example over open water, the layer will be much thinner than in mountains.

* Significantly more efficient tile management routines and some code cleanup, resulting in a better performance also in static mode.

The planned extensions beyond v0.8 include making the generation and decay of convective clouds and thermals a dynamical process, migrating to high-resolution cloud textures and shifting some low-level functionality to the C++ core for better performance.

Did you know?

The local weather package has an inbuilt METAR interface which generates weather based on a parsed METAR string. However, it can't be used with <i>--real-weather-fetch</i> because currently FlightGear automatically executes fetched and parsed METAR, thus preventing the local weather package from working. Some help from C++ programmers needed here!

===New mapping software===
Michael contributes new FlightGear mapping software to the community, written in the Ruby programming language: [http://rubyforge.org/projects/fgmap FGMap]. Basically it shows your current flight position on an [http://openstreetmap.org OpenStreetMap] map. It therefore has some similarity to [[Atlas]] and the online [[MPMap]]s. As with all projects, [http://rubyforge.org/tracker/?func=add&group_id=9572&atid=37032 feedback] is highly appreciated.

FGMap has many features, including:
* Show flight position on OpenStreetMap map in real-time
* Download new map tiles on-the-fly in the background
* Add shaded elevation layer to map for nice visual effect
* Display current speed and altitude
* Show position and frequency of all navigation aids on the map
* Create FlightGear route manager entries with a click of the mouse from navigation aids and waypoints
* Record and restore flight path
* Colorize path according to speed and altitude
* Display information about instantaneous speed and altitude for all points of the track
* Set waypoints on map

Downloads and more information are available at [http://rubyforge.org/projects/fgmap the project's website].

===Troubleshooting ''triangleintersect, QNaN'' etc.===

Last month, the infamous [http://wiki.flightgear.org/index.php/Howto:_Get_rid_of_common_errors#Warning:_Picked_up_TriangleIntersect QNaN errors] that may cause FlightGear to become [[Showstoppers|unresponsive]] have been linked to potential issues in the Nasal interpreter (and more generally Nasal code) by flug, for more details please see: [http://www.flightgear.org/forums/viewtopic.php?f=18&t=8483&p=83701 "Nasal source of Dreaded Triangle Error-source of many probs?"].
For the time being, you will want to look out for any Nasal code that contains unchecked divisions with unvalidated divisors.

==In the hangar==
===Airbus A320===
After a couple months of dormancy, [[Airbus A320|A320]] development has been picked up by ''skyop''. The aircraft has largely been updated for FlightGear 2.0.0, with [[thrust reversal]], [[pushback]], [[Howto: Add contrails|contrails]], and a few bugs fixed here and there. You can follow further A320 development at [http://www.flightgear.org/forums/viewtopic.php?f=4&t=5759 its forum thread].

===Bell P59 Airacomet and Bell 222 X===
''helijah'' created and pushed both P59 and Bell 222X onto Git. The Bell 222X FDM is still in development. More information and download at [http://helijah.free.fr/flightgear/hangar.htm ''helijah's'' Hangar].

===DeHavilland Canada DHC-7-150 Dash 7===
''Quadunit404'' has announced [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8805 intentions] to produce his first aircraft, the De Havilland Canada DHC-7-150 Dash 7, adding yet another member of the De Havilland Canada family to to FlightGear fleet after active development begins. Currently he is learning how to model using [[Blender]] and will be studying the FDMs of other turboprop regional airliners already in FlightGear to get an idea of how to write the [[FDM]].

===Lockheed Martin F-22 Raptor===
''simbabeat'' and ''jackmermod'' are working in improving the F-22 Raptor. The project is still at the modeling phase. For more information, see [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8960 the forum thread].

==BAE Hawk and T-45 Goshawk===
''Intel-Qube'' [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8960 is currently improving] the BAE Hawk and the T-45 Goshawk. The model is done, and to be done are the cockpit and other parts of the aircraft. Currently (until approximately the second week of August), the development is on hiatus.

===SpaceShipOne and White Knight===
''helijah'' made some changes to the SpaceShipOne model including the [[FDM]], adding fuselage reflection effect and separating the SpaceShipOne and White Knight objects. The next step is to improve the SpaceShipOne model by adding wheels and moving parts. After that he will try to separate the two aircraft when in flight.

==Livery database==
In the second week of July, the [http://liveries.flightgear.org livery database] welcomed its [http://liveries.flightgear.org/liveries.php?id=251 250th livery]: a glider club's livery for the [[Robin DR400]], created by top-painter Brett Harrison (Gooneybird). More liveries are welcome as always and can be [http://liveries.flightgear.org/contribute.php uploaded]!

==Scenery corner==
===Animated jetways===
[[File:Movable_Jetway.jpg|thumb|A Jetway connecting to a [[Boeing 737-300|737-300]].]]
''skyop'' and ''Gijs'' are currently working on animated jetways for FlightGear that can be activated with a click of the mouse. At the moment they are very primitive and only fit [[Boeing 737|737s]]. Planned features include automatic attachment to your airplane's door and even multiple jetways for wide-body airliners and [[Airbus A380|A380s]]. See [http://www.flightgear.org/forums/viewtopic.php?t=8728 this thread] for more information.

[[Image:Dubai_v0_vs_cs-osm.png|thumb|270px|Dubai, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Dublin scenery===
''eag1e'' created new terrain and buildings for Dublin airport (EIDW). For more details, see [http://flightgear.org/forums/viewtopic.php?f=5&t=8874 this link].

===Detailed terrain for Dubai===
As announced in an [[FlightGear Newsletter March 2010#Dubai is coming up|earlier edition]], Gijs has been (re)drawing the terrain of Dubai. The FlightGear scenery now includes:
* Palm Islands (islands in the shape of a palm)
* The World (islands together forming a world map)
* Detailed coastline and city boundaries
The area is represented in its form of 2008, due to the lack of more up-to-date imagery. Given Dubai's massive expansion speed, the scenery can be considered as out-of-date already. Nevertheless it is a great step forward in comparison to the previous terrain, as the image on the right proves.

This new terrain will be available with the upcoming scenery build. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].

[[Image:Qatar_v0_vs_cs-osm.png|thumb|270px|Qatar, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Detailed terrain for Qatar===
Believe it or not, but here is another Emirate that has been hand drawn! Fahim worked on the peninsula of Qatar, very close to Dubai. Seeing the image on the right, you might think detail/accuracy was lost (except for the urban areas), but I can tell you that the new terrain is far more accurate in all aspects.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver].

===Night flying at London Gatwick===
The new version of [[London Gatwick Airport]] (EGKK) is available and has improved textures and features. It claims to be one of the few ''(two?)'' major international airports in [[FlightGear]] suitable for night flying with full lighting textures on all buildings, hazard lights and approximately one hundred lighting masts. The tower even has lit instrumentation visible in the control room. Images are shown at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8363 the forum topic].

The taxiways at night are complex but made easier if the official charts are downloaded from [http://www.nats-uk.ead-it.com]. Many taxiway and runway signs have been included to help you on your way. Additional [[AI]] ground network and AI traffic have made this into a very busy airport and a single gate at each pier has been thoughtfully reserved so you can find a parking space when you land here (see the readme file for details).

In daytime the airport is fully modeled with detailed textures and even the roofs of buildings having accurate features. Stock model jetways, cargoes and ground vehicles have been added in quantity to give an authentic look to the airport. Large areas of open air car parks are distributed around the perimeter with novel layering of textures to enhance the 3D effect of the parked cars. Similarly, woods and trees have been added in surrounding areas to add more to the overall feel of the airport.

London Gatwick EGKK may be downloaded from [http://www.mediafire.com/?t2ml5ezmgwv MediaFire].

===Los Angeles International Airport===
[[Image:KLAX_newvsold.png|thumb|250px|New KLAX terminal 5 by Skyop vs. the old terminal 6 by MaverickAlex]]
''skyop'' has remodeled the terminals, roadways, and parking garages for KLAX Los Angeles International Airport. Improvements include more realistic textures, more accurate gates, and more accurate placement of buildings. The current Encounter building, control tower, and welcome pylons by MaverickAlex will be retained. See the development history at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8862 the project forum thread].

[[Image:Westfrisian_Islands.png|thumb|270px|Eastfrisian Islands, old vmap0 data (top) and the new custom scenery data (bottom).]]

===Improvement of Eastfrisian Islands, North Sea===

Mike ([[User:D-SKY1|D-SKY1]]) did his first steps in creating custom scenery. With great help from Fahim and Papillon81 he managed to improve Eastfrisian Islands ''Norderney, Baltrum, Langeoog and Wangerooge'', Northsea coast of Germany. With this improvement we close the gap between the enhanced dutch islands in the west and Helgoland in the east.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver]. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].
<br />
<br />
<br />
<br />
<br />

==Aircraft review==
'''This month: Bell P-59 Airacomet'''
[[Image:P59-1.jpg|thumb|270px|A P-59 buzzing the apron at KHND]]
The P-59 was the first American jet aircraft. It was developed by the Bell company in response to the USAAF's requirement for a jet fighter. Although the Airacomet never saw combat, it was used to train many USAAF pilots in flying jet aircraft.

As usual, Helijah has done a fantastic job with the 3D model of the aircraft, and GIT users can take full advantage of the new fuselage reflection effect which Helijah has added to this model. The canopy opens and closes, and the pilot's head moves around. Although these features may seem insignificant, they do add to the overall experience of flying this already beautiful aircraft.
[[Image:P59-2.jpg|thumb|left|270px|Flying over KHND]]
There are, however, some minor issues with the 3D model. The model has afterburners, while the real P-59 did not, and tracers fired from the guns of this aircraft do not behave like their real life counterparts. (The muzzle velocities of the guns have not been modelled correctly)

The 3D cockpit contains the standard six instruments, which is enough to fly with, and the autopilot works, too.
The FDM seems to be fairly accurate. For example, the Airacobra should, and will reach 46,200 feet, and it can achieve and sustain a climb rate of 3,200 feet per minute.

''Review by Armchair Ace''

==Nasal for newbies==
[[Nasal]] is the name of FlightGear's built in scripting language that allows people to easily create custom logics for adjusting and driving FlightGear internals without having to modify the C++ source code or recompile FlightGear.
To use Nasal you don't need to be a programmer, in fact Nasal is so simple that it can be used by people without any prior programming experience at all. Still Nasal is very powerful and flexible.

Nasal scripts can be used for doing many interesting things.
Some of the more recent examples being the bombable add-on, the local weather system or the seeking AI missiles, all of which are purely implemented as Nasal scripts.

You can see for yourself how easy it is to get started writing Nasal scripts:

Just create a new plain text file (using an editor like notepad on Windows) named "hello.nas" in the $FG_ROOT/Nasal directory, paste the following contents:

print("My first Nasal script !");

Watch the black shell window when starting FlightGear and you'll see the "My first Nasal script !" being printed to the console.
As you have surely noticed, all Nasal scripts in the $FG_ROOT/Nasal directory get loaded and run automatically during FlightGear startup.

The sample program just consists of one instruction, namely "print". Which is a function call to the built-in "print" function of the Nasal interpreter.
The print function can not only print strings, but also numbers or individual characters.

Function calls in Nasal always look like this:

name();

Where "name" would be the function's Nasal name, and then parentheses contain all parameters that you want to pass to the function. The expression is terminated using a semicolon.

To pass arguments to the function, you would simply add these in between the parentheses and separate them using a comma:

print(100, 200, 300);

==From the community==
===TransGear founder leaves===
Rob (MD-Terp), known by many as the founding father of the monthly [[TransGear]] events, [http://www.flightgear.org/forums/viewtopic.php?f=3&t=8809 announced] his "retirement" at the forum. With the first event being held just one month after the first edition of this newsletter, TransGear almost reached its first mileage. However, some former participants are discussing an option to continue organizing the event. More on that in a future edition.

We would like to thank Rob for all he has done, to wish him all the best, and deeply hope to see him return to the community one day.

==And finally...==

===Did you know?===

[[Category:FlightGear Newsletter|2010 06]]

FlightGear Newsletter July 2010

2010-07-23T14:37:54Z

Rsbrflyer: proofreading & shuffling

{{newsletter}}
{{TOC_right}}

This month's newsletter marks a year since [[FlightGear Newsletter July 2009|the first issue]] was written!

==Newsletter history==

One year ago, in June 2009, [[FlightGear]]-head Curt proposed his newsletter-idea [http://www.flightgear.org/forums/viewtopic.php?f=6&t=5201 at the forum]. With multiple (failed) efforts in the past, those involved were extremely eager to get it up and going this time. Stuart was the one that wrote most of the first issue(s). At the time of the second issue, more people were involved and wrote a paragraph or two.

Today, the newsletter is written by a bunch of people, with different interests and relations to FlightGear. It provides an easy way to keep up-to-date with the ongoing developments; both in FlightGear itself and in the community around it.

I would like to use this opportunity to thank those that contributed over the past year. Thanks to their work, the newsletter still exists! In order to reach our next mileage, 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, [[Special:UserLogin|free to register]]) can edit the newsletter and every contribution is welcome.

Now, all I can say is: enjoy this brand new edition!

==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 misconception 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.

Some ideas:

* writing articles for the [http://wiki.flightgear.org/index.php/Next_newsletter next issue of this newsletter]
* sending corrections/updates to the FlightGear Manual
* helping new users on the forums/IRC
* writing a wiki page
* organizing fly-outs

One of the easiest ways to help is to improve the scenery in your local area by placing buildings/structures using the UFO and submitting them to the [http://scenemodels.flightgear.org/contribute.php FlightGear Scenery Object Database]. It's easy, and best of all requires little time to have a real impact. Instructions on how to do this can be found in the wiki, article [[Placing 3D Objects with the UFO]].

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

==Reminder: Google Summer of Code 2011==

We would like to remind all readers that the FlightGear project is planning to participate in Google's Summer of Code 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.
Some easy ways for helping right now would be:

* suggest new project ideas (i.e. get in touch using the forums, mailing lists or the wiki)
* browse the forums or mailing list archives and look for suitable candidate projects
* help refine and improve existing project proposals
* help finalize the application template that we are preparing
* help us find suitable students who might be interested in participating in 2011
* help us find mentors
* summarize all related discussions, and document them here in the wiki

At the moment, we are collecting ideas for answering the various questions in the application: [http://flightgear.org/forums/viewtopic.php?f=38&t=8857 Why should FlightGear participate in GSoC?]

If you have any questions or other feedback related to GSoC, please use the forum to get in touch: [http://flightgear.org/forums/viewforum.php?f=38]

==Development news==

===A new forum for Google Summer of Code===
As some of you may already know, there is now an orchestrated effort going on to get FlightGear ready for becoming a mentoring organization in Google's Summer of Code 2011.

So far, all related information has been collected here in the wiki: [[GSoC]].
But to ease the planning and organization process, there has now been a new sub forum set up for talking about anything that is one way or another related to this effort.
The forum can be found at: http://flightgear.org/forums/viewforum.php?f=38

This should make it much easier for all community members to participate in all related discussions, without necessarily having to be subscribed to the mailing lists.

So if you have anything to contribute to this topic, please do make sure to check out this new forum.

You are for example also invited to make suggestions for new FlightGear related GSoC projects.

For the time being, one topic from the "New Features" sub forum has already been moved to this new forum, it is about a suggestion to procedurally populate the FlightGear scenery with dynamically created cities, for more details please check out [[AutoGen Scenery for FlightGear]].

===Local weather system update===

The local weather system is moving towards dynamical weather. Currently, an experimental version v0.73 is released which demonstrates the cloud drift in the wind (see more information [http://www.flightgear.org/forums/viewtopic.php?f=5&t=7358 here]). The upcoming release v0.8 which is currently in the final stages of being prepared will include

* Drift of clouds, thermals and other weather effects in the wind, enabling for example a realistic soaring experience in strong winds.

* Several available models for the wind field, including high-altitude wind patterns that gradually change along the aircraft route.

* A moderately complex model for the boundary layer, i.e. the region where the wind field interacts with terrain. The boundary layer thickness and wind speed reduction effect becomes tied to the roughness of the terrain - for example over open water, the layer will be much thinner than in mountains.

* Significantly more efficient tile management routines and some code cleanup, resulting in a better performance also in static mode.

The planned extensions beyond v0.8 include making the generation and decay of convective clouds and thermals a dynamical process, migrating to high-resolution cloud textures and shifting some low-level functionality to the C++ core for better performance.

Did you know?

The local weather package has an inbuilt METAR interface which generates weather based on a parsed METAR string. However, it can't be used with <i>--real-weather-fetch</i> because currently FlightGear automatically executes fetched and parsed METAR, thus preventing the local weather package from working. Some help from C++ programmers needed here!

===New mapping software===
Michael contributes new FlightGear mapping software to the community, written in the Ruby programming language: [http://rubyforge.org/projects/fgmap FGMap]. Basically it shows your current flight position on an [http://openstreetmap.org OpenStreetMap] map. It therefore has some similarity to [[Atlas]] and the online [[MPMap]]s. As with all projects, [http://rubyforge.org/tracker/?func=add&group_id=9572&atid=37032 feedback] is highly appreciated.

FGMap has many features, including:
* Show flight position on OpenStreetMap map in real-time
* Download new map tiles on-the-fly in the background
* Add shaded elevation layer to map for nice visual effect
* Display current speed and altitude
* Show position and frequency of all navigation aids on the map
* Create FlightGear route manager entries with a click of the mouse from navigation aids and waypoints
* Record and restore flight path
* Colorize path according to speed and altitude
* Display information about instantaneous speed and altitude for all points of the track
* Set waypoints on map

Downloads and more information are available at [http://rubyforge.org/projects/fgmap the project's website].

===Troubleshooting ''triangleintersect, QNaN'' etc.===

Last month, the infamous [http://wiki.flightgear.org/index.php/Howto:_Get_rid_of_common_errors#Warning:_Picked_up_TriangleIntersect QNaN errors] that may cause FlightGear to become [[Showstoppers|unresponsive]] have been linked to potential issues in the Nasal interpreter (and more generally Nasal code) by flug, for more details please see: [http://www.flightgear.org/forums/viewtopic.php?f=18&t=8483&p=83701 "Nasal source of Dreaded Triangle Error-source of many probs?"].
For the time being, you will want to look out for any Nasal code that contains unchecked divisions with unvalidated divisors.

==In the hangar==
===Bell P59 Airacomet and Bell 222 X===
''helijah'' created and pushed both P59 and Bell 222X onto Git. The Bell 222X FDM is still in development. More information and download at [http://helijah.free.fr/flightgear/hangar.htm ''helijah's'' Hangar].

===De Havilland Canada DHC-7-150 Dash 7===
''Quadunit404'' has announced [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8805 intentions] to produce his first aircraft, the De Havilland Canada DHC-7-150 Dash 7, adding yet another member of the De Havilland Canada family to to FlightGear fleet after active development begins. Currently he is learning how to model using [[Blender]] and will be studying the FDMs of other turboprop regional airliners already in FlightGear to get an idea of how to write the FDM.

===SpaceShipOne and White Knight===
''helijah'' has made some changes to the SpaceShipOne model including the [[FDM]], adding fuselage reflection effect and separating the SpaceShipOne and White Knight objects. The next step is to improve the SpaceShipOne model by adding wheels and moving parts. After that he will try to separate the two aircraft when in flight.

==Livery database==
In the second week of July, the [http://liveries.flightgear.org livery database] welcomed its [http://liveries.flightgear.org/liveries.php?id=251 250th livery]: a glider club's livery for the [[Robin DR400]], created by top-painter Brett Harrison (Gooneybird). More liveries are welcome as always and can be [http://liveries.flightgear.org/contribute.php uploaded]!

==Scenery corner==
===Animated jetways===
[[File:Movable_Jetway.jpg|thumb|A Jetway connecting to a [[Boeing 737-300|737-300]].]]
''skyop'' and ''Gijs'' are currently working on animated jetways for FlightGear that can be activated with a click of the mouse. At the moment they are very primitive and only fit [[Boeing 737|737s]]. Planned features include automatic attachment to your airplane's door and even multiple jetways for wide-body airliners and [[Airbus A380|A380s]]. See [http://www.flightgear.org/forums/viewtopic.php?t=8728 this thread] for more information.

[[Image:Dubai_v0_vs_cs-osm.png|thumb|270px|Dubai, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Dublin scenery===
''eag1e'' created new terrain and buildings for Dublin airport (EIDW). For more details, see [http://flightgear.org/forums/viewtopic.php?f=5&t=8874 this link].

===Detailed terrain for Dubai===
As announced in an [[FlightGear Newsletter March 2010#Dubai is coming up|earlier edition]], Gijs has been (re)drawing the terrain of Dubai. The FlightGear scenery now includes:
* Palm Islands (islands in the shape of a palm)
* The World (islands together forming a world map)
* Detailed coastline and city boundaries
The area is represented in its form of 2008, due to the lack of more up-to-date imagery. Given Dubai's massive expansion speed, the scenery can be considered as out-of-date already. Nevertheless it is a great step forward in comparison to the previous terrain, as the image on the right proves.

This new terrain will be available with the upcoming scenery build. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].

[[Image:Qatar_v0_vs_cs-osm.png|thumb|270px|Qatar, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Detailed terrain for Qatar===
Believe it or not, but here is another Emirate that has been hand drawn! Fahim worked on the peninsula of Qatar, very close to Dubai. Seeing the image on the right, you might think detail/accuracy was lost (except for the urban areas), but I can tell you that the new terrain is far more accurate in all aspects.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver].

===Night flying at London Gatwick===
The new version of [[London Gatwick Airport]] (EGKK) is available and has improved textures and features. It claims to be one of the few ''(two?)'' major international airports in [[FlightGear]] suitable for night flying with full lighting textures on all buildings, hazard lights and approximately one hundred lighting masts. The tower even has lit instrumentation visible in the control room. Images are shown at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8363 the forum topic].

The taxiways at night are complex but made easier if the official charts are downloaded from [http://www.nats-uk.ead-it.com]. Many taxiway and runway signs have been included to help you on your way. Additional [[AI]] ground network and AI traffic have made this into a very busy airport and a single gate at each pier has been thoughtfully reserved so you can find a parking space when you land here (see the readme file for details).

In daytime the airport is fully modeled with detailed textures and even the roofs of buildings having accurate features. Stock model jetways, cargoes and ground vehicles have been added in quantity to give an authentic look to the airport. Large areas of open air car parks are distributed around the perimeter with novel layering of textures to enhance the 3D effect of the parked cars. Similarly, woods and trees have been added in surrounding areas to add more to the overall feel of the airport.

London Gatwick EGKK may be downloaded from [http://www.mediafire.com/?t2ml5ezmgwv MediaFire].

===Los Angeles International Airport (KLAX)===
''skyop'' has been improving the Los Angeles airport terminals and [[AI traffic]] XML files. See the progress [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8862 at the forum].

[[Image:Westfrisian_Islands.png|thumb|270px|Westfrisian Islands, old vmap0 data (top) and the new custom scenery data (bottom).]]

===Improvement of Westfrisian Islands, North Sea===

Mike ([[User:D-SKY1|D-SKY1]]) did his first steps in creating custom scenery. With great help from Fahim and Papillon81 he managed to improve Westfrisian Islands ''Norderney, Baltrum, Langeoog and Wangerooge'', Northsea coast of Germany. With this improvement we close the gap between the enhanced dutch islands in the west and Helgoland in the east.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver]. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].
<br />
<br />
<br />
<br />
<br />

==Aircraft review==
'''This month: Bell P-59 Airacomet'''
[[Image:P59-1.jpg|thumb|270px|A P-59 buzzing the apron at KHND]]
The P-59 was the first American jet aircraft. Developed by the Bell company in response to the USAAF's requirement for a jet fighter. Although the Airacomet never saw combat, it was used to train many USAAF pilots in flying jet aircraft.

As usual, Helijah has done a fantastic job with the 3D model of the aircraft, and GIT users can take full advantage of the new fuselage reflection effect which Helijah has added to this model. The canopy opens and closes, and the pilot's head moves around. Although these features may seem insignificant, they do add to the overall experience of flying this already beautiful aircraft.
[[Image:P59-2.jpg|thumb|left|270px|Trying some aerobatics near KHND]]
There are, however, some minor issues with the 3D model. The model has afterburners, while the real P-59 did not, and tracers fired from the guns of this aircraft do not behave like their real life counterparts. (The muzzle velocities of the guns have not been modelled correctly)

The 3D cockpit contains the standard six instruments, which is enough to fly with, and the autopilot works, too.
The FDM seems to be fairly accurate, as the Airacobra should, and will reach 46,200 feet, and it can achieve and sustain a climb rate of 3,200 feet per minute.

==Nasal for newbies==
[[Nasal]] is the name of FlightGear's built in scripting language that allows people to easily create custom logics for adjusting and driving FlightGear internals without having to modify the C++ source code or recompile FlightGear.
To use Nasal you don't need to be a programmer, in fact Nasal is so simple that it can be used by people without any prior programming experience at all. Still Nasal is very powerful and flexible.

Nasal scripts can be used for doing many interesting things.
Some of the more recent examples being the bombable add-on, the local weather system or the seeking AI missiles, all of which are purely implemented as Nasal scripts.

You can see for yourself how easy it is to get started writing Nasal scripts:

Just create a new plain text file (using an editor like notepad on Windows) named "hello.nas" in the $FG_ROOT/Nasal directory, paste the following contents:

print("My first Nasal script !");

Watch the black shell window when starting FlightGear and you'll see the "My first Nasal script !" being printed to the console.
As you have surely noticed, all Nasal scripts in the $FG_ROOT/Nasal directory get loaded and run automatically during FlightGear startup.

The sample program just consists of one instruction, namely "print". Which is a function call to the built-in "print" function of the Nasal interpreter.
The print function can not only print strings, but also numbers or individual characters.

Function calls in Nasal always look like this:

name();

Where "name" would be the function's Nasal name, and then parentheses contain all parameters that you want to pass to the function. The expression is terminated using a semicolon.

To pass arguments to the function, you would simply add these in between the parentheses and separate them using a comma:

print(100, 200, 300);

==From the community==
===TransGear founder leaves===
Rob (MD-Terp), known by many as the founding father of the monthly [[TransGear]] events, [http://www.flightgear.org/forums/viewtopic.php?f=3&t=8809 announced] his "retirement" at the forum. With the first event being held just one month after the first edition of this newsletter, TransGear almost reached its first mileage. However, some former participants are discussing an option to continue organizing the event. More on that in a future edition.

We would like to thank Rob for all he has done, to wish him all the best, and deeply hope to see him return to the community one day.

==And finally...==

===Did you know?===

[[Category:FlightGear Newsletter|2010 06]]

FlightGear Newsletter July 2010

2010-07-17T03:23:57Z

Rsbrflyer: some news

{{newsletter}}
{{TOC_right}}

This month's newsletter marks a year since [[FlightGear Newsletter July 2009|the first issue]] was written!

'''<font size="4">Newsletter history</font>'''

One year ago, in June 2009, [[FlightGear]]-head Curt proposed his newsletter-idea [http://www.flightgear.org/forums/viewtopic.php?f=6&t=5201 at the forum]. With multiple (failed) efforts in the past, those involved were extremely eager to get it up and going this time. Stuart was the one that wrote most of the first issue(s). At the time of the second issue, more people were involved and wrote a paragraph or two.

Today, the newsletter is written by a bunch of people, with different interests and relations to FlightGear. It provides an easy way to keep up-to-date with the ongoing developments; both in FlightGear itself and in the community around it.

I would like to use this opportunity to thank those that contributed over the past year. Thanks to their work, the newsletter still exists! In order to reach our next mileage, 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, [[Special:UserLogin|free to register]]) can edit the newsletter and every contribution is welcome.

Now, all I can say is: enjoy this brand new edition!

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

Some ideas:

* writing articles for the [http://wiki.flightgear.org/index.php/Next_newsletter next issue of this newletter]
* sending corrections/updates to the FlightGear Manual
* helping new users on the forums/IRC
* writing a wiki page
* organising fly-outs

One of the easiest ways to help is to improve the scenery in your local area by placing buildings/structures using the UFO and submitting them to the [http://scenemodels.flightgear.org/contribute.php FlightGear Scenery Object Database]. It's easy, and best of all requires little time to have a real impact. Instructions on how to do this can be found in the wiki, [http://wiki.flightgear.org/index.php/Placing_3D_Objects_with_the_UFO Placing 3D Objects with the UFO].

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

==Reminder: Google Summer of Code 2011==

We would like to remind all readers that the FlightGear project is planning to participate in Google's Summer of Code 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.
Some easy ways for helping right now would be:

* suggest new project ideas (i.e. get in touch using the forums, mailing lists or the wiki)
* browse the forums or mailing list archives and look for suitable candidate projects
* help refine and improve existing project proposals
* help finalize the application template that we are preparing
* help us find suitable students who might be interested in participating in 2011
* help us find mentors
* summarize all related discussions, and document them here in the wiki

At the moment, we are collecting ideas for answering the various questions in the application: [http://flightgear.org/forums/viewtopic.php?f=38&t=8857 Why should FlightGear participate in GSoC?]

If you have any questions or other feedback related to GSoC, please use the forum to get in touch: http://flightgear.org/forums/viewforum.php?f=38

==Development news==

===A new forum for Google Summer of Code===
As some of you may already know, there is now an orchestrated effort going on to get FlightGear ready for becoming a mentoring organization in Google's Summer of Code 2011.

So far, all related information has been collected here in the wiki: [[GSoC]].
But to ease the planning and organization process, there has now been a new sub forum set up for talking about anything that is one way or another related to this effort.
The forum can be found at: http://flightgear.org/forums/viewforum.php?f=38

This should make it much easier for all community members to participate in all related discussions, without necessarily having to be subscribed to the mailing lists.

So if you have anything to contribute to this topic, please do make sure to check out this new forum.

You are for example also invited to make suggestions for new FlightGear related GSoC projects.

For the time being, one topic from the "New Features" sub forum has already been moved to this new forum, it is about a suggestion to procedurally populate the FlightGear scenery with dynamically created cities, for more details please check out [[AutoGen Scenery for FlightGear]].

===Local weather system update===
''Thorsten'' updated his local weather system to version 0.73. See more information [http://www.flightgear.org/forums/viewtopic.php?f=5&t=7358 here].

===New mapping software===
Michael contributes new FlightGear mapping software to the communitiy, written in the Ruby programming language: [http://rubyforge.org/projects/fgmap FGMap]. Basically it shows your current flight position on an [http://openstreetmap.org OpenStreetMap] map. It therefore has some similarity to [[Atlas]] and the online [[MPMap]]s. As with all projects, [http://rubyforge.org/tracker/?func=add&group_id=9572&atid=37032 feedback] is highly appreciated.

FGMap has many features, including:
* Show flight position on Openstreetmap map in real-time
* Download new map tiles on-the-fly in the background
* Add shaded elevation layer to map for nice visual effect
* Display current speed and altitude
* Show position and frequency of all navigation aids on the map
* Create FlightGear route manager entries with a click of the mouse from navigation aids and waypoints
* Record and restore flight path
* Colorize path according to speed and altitude
* Display information about instantaneous speed and altitude for all points of the track
* Set waypoints on map

Downloads and more information are available at [http://rubyforge.org/projects/fgmap the project's website].

===Troubleshooting ''triangleintersect, QNaN'' etc.===

Last month, the infamous [http://wiki.flightgear.org/index.php/Howto:_Get_rid_of_common_errors#Warning:_Picked_up_TriangleIntersect QNaN errors] that may cause FlightGear to become [[Showstoppers|unresponsive]] have been linked to potential issues in the Nasal interpreter (and more generally Nasal code) by flug, for more details please see: [http://www.flightgear.org/forums/viewtopic.php?f=18&t=8483&p=83701 "Nasal source of Dreaded Triangle Error-source of many probs?"].
For the time being, you will want to look out for any Nasal code that contains unchecked divisions with unvalidated divisors.

==Nasal for newbies==
[[Nasal]] is the name of FlightGear's built in scripting language that allows people to easily create custom logics for adjusting and driving FlightGear internals without having to modify the C++ source code or recompile FlightGear.
To use Nasal you don't need to be a programmer, in fact Nasal is so simple that it can be used by people without any prior programming experience at all. Still Nasal is very powerful and flexible.

Nasal scripts can be used for doing many interesting things.
Some of the more recent examples being the bombable addon, the local weather system or the seeking AI missiles, all of which are purely implemented as Nasal scripts.

You can see for yourself how easy it is to get started writing Nasal scripts:

Just create a new plain text file (using an editor like notepad on Windows) named "hello.nas" in the $FG_ROOT/Nasal directory, paste the following contents:

print("My first Nasal script !");

Watch the black shell window when starting FlightGear and you'll see the "My first Nasal script !" being printed to the console.
As you have surely noticed, all Nasal scripts in the $FG_ROOT/Nasal directory get loaded and run automatically during FlightGear startup.

The sample program just consists of one instruction, namely "print". Which is a function call to the built-in "print" function of the Nasal interpreter.
The print function can not only print strings, but also numbers or individual characters.

Function calls in Nasal always look like this:

name();

Where "name" would be the function's Nasal name, and then parentheses contain all parameters that you want to pass to the function. The expression is terminated using a semicolon.

To pass arguments to the function, you would simply add these in between the parentheses and separate them using a comma:

print(100, 200, 300);

==In the hangar==
===Bell P59 Airacomet and Bell 222 X===
''helijah'' created and pushed both P59 and Bell 222X onto Git. The Bell 222X FDM is still in development. More information and download at [http://helijah.free.fr/flightgear/hangar.htm ''helijah's'' Hangar].

===De Havilland Canada DHC-7-150 Dash 7===
''Quadunit404'' has announced [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8805 intentions] to produce his first aircraft, the De Havilland Canada DHC-7-150 Dash 7, adding yet another member of the De Havilland Canada family to to FlightGear fleet after active development begins. Currently he is learning how to model using [[Blender]] and will be studying the FDMs of other turboprop regional airliners already in FlightGear to get an idea of how to write the FDM.

===SpaceShipOne and White Knight===
''helijah'' has made some changes to the SpaceShipOne model including the [[FDM]], adding fuselage reflection effect and separating the SpaceShipOne and White Knight objects. The next step is to improve the SpaceShipOne model by adding wheels and moving parts. After that he will try to separate the two aircraft when in flight.

==Livery database==
In the second week of July, the [http://liveries.flightgear.org livery database] welcomed its [http://liveries.flightgear.org/liveries.php?id=251 250th livery]: a glider club's livery for the [[Robin DR400]], created by top-painter Brett Harrison (Gooneybird). More liveries are welcome as always and can be [http://liveries.flightgear.org/contribute.php uploaded]!

==Scenery corner==
===Animated jetways===
[[File:Movable_Jetway.jpg|thumb|A jetway connecting to a [[Boeing 737-300|737-300]].]]
''skyop'' and ''Gijs'' are currently working on animated jetways for FlightGear that can be activated with a click of the mouse. At the moment they are very primitive and only fit [[Boeing 737|737s]]. Planned features include automatic attachment to your airplane's door and even multiple jetways for wide-body airliners and [[Airbus A380|A380s]]. See [http://www.flightgear.org/forums/viewtopic.php?t=8728 this thread] for more information.

[[Image:Dubai_v0_vs_cs-osm.png|thumb|270px|Dubai, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Dublin scenery===
''eag1e'' created new terrain and buildings for Dublin airport (EIDW). For more details, see [http://flightgear.org/forums/viewtopic.php?f=5&t=8874 this link].

===Detailed terrain for Dubai===
As announced in an [[FlightGear Newsletter March 2010#Dubai is coming up|earlier edition]], Gijs has been (re)drawing the terrain of Dubai. The FlightGear scenery now includes:
* Palm Islands (islands in the shape of a palm)
* The World (islands together forming a worldmap)
* Detailed coastline and city boundaries
The area is represented in its form of 2008, due to the lack of more up-to-date imagery. Given Dubai's massive expansion speed, the scenery can be considered as out-of-date already. Nevertheless it is a great step forward in comparison to the previous terrain, as the image on the right proves.

This new terrain will be available with the upcoming scenery build. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].

[[Image:Qatar_v0_vs_cs-osm.png|thumb|270px|Qatar, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Detailed terrain for Qatar===
Believe it or not, but here is another Emirate that has been hand drawn! Fahim worked on the peninsula of Qatar, very close to Dubai. Seeing the image on the right, you might think detail/accuracy was lost (except for the urban areas), but I can tell you that the new terrain is far more accurate in all aspects.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver].

===Night flying at London Gatwick===
The new version of [[London Gatwick Airport]] (EGKK) is available and has improved textures and features. It claims to be one of the few ''(two?)'' major international airports in [[FlightGear]] suitable for night flying with full lighting textures on all buildings, hazard lights and approximately one hundred lighting masts. The tower even has lit instrumentation visible in the control room. Images are shown at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8363 the forum topic].

The taxiways at night are complex but made easier if the official charts are downloaded from [http://www.nats-uk.ead-it.com]. Many taxiway and runway signs have been included to help you on your way. Additional [[AI]] ground network and AI traffic have made this into a very busy airport and a single gate at each pier has been thoughtfully reserved so you can find a parking space when you land here (see the readme file for details).

In daytime the airport is fully modelled with detailed textures and even the roofs of buildings having accurate features. Stock model jetways, cargoes and ground vehicles have been added in quantity to give an authentic look to the airport. Large areas of open air car parks are distributed around the perimeter with novel layering of textures to enhance the 3D effect of the parked cars. Similarly, woods and trees have been added in surrounding areas to add more to the overall feel of the airport.

London Gatwick EGKK may be downloaded from [http://www.mediafire.com/?t2ml5ezmgwv MediaFire].

===Los Angeles International Airport (KLAX)===
''skyop'' has been improving the Los Angeles airport terminals and [[AI traffic]] XML files. See the progress [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8862 at the forum].

==Aircraft review==
'''This month: (name of aircraft here)'''

==From the community==
===TransGear founder leaves===
Rob (MD-Terp), known by many as the founding father of the monthly [[TransGear]] events, [http://www.flightgear.org/forums/viewtopic.php?f=3&t=8809 announced] his "retirement" at the forum. With the first event being held just one month after the first edition of this newsletter, TransGear almost reached its first mileage. However, some former participants are discussing an option to continue organizing the event. More on that in a future edition.

We would like to thank Rob for all he has done, to wish him all the best, and deeply hope to see him return to the community one day.

==And finally...==

===Did you know?===

[[Category:FlightGear Newsletter|2010 06]]

FlightGear Newsletter July 2010

2010-07-16T02:47:05Z

Rsbrflyer: /* Scenery corner */ dublin, some typos to be ironed on the whole news

{{newsletter}}
{{TOC_right}}

This month's newsletter marks a year since [[FlightGear Newsletter July 2009|the first issue]] was written!

'''<font size="4">Newsletter history</font>'''

One year ago, in June 2009, [[FlightGear]]-head Curt proposed his newsletter-idea [http://www.flightgear.org/forums/viewtopic.php?f=6&t=5201 at the forum]. With multiple (failed) efforts in the past, those involved were extremely eager to get it up and going this time. Stuart was the one that wrote most of the first issue(s). At the time of the second issue, more people were involved and wrote a paragraph or two.

Today, the newsletter is written by a bunch of people, with different interests and relations to FlightGear. It provides an easy way to keep up-to-date with the ongoing developments; both in FlightGear itself and in the community around it.

I would like to use this opportunity to thank those that contributed over the past year. Thanks to their work, the newsletter still exists! In order to reach our next mileage, 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, [[Special:UserLogin|free to register]]) can edit the newsletter and every contribution is welcome.

Now, all I can say is: enjoy this brand new edition!

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

Some ideas:

* writing articles for the [http://wiki.flightgear.org/index.php/Next_newsletter next issue of this newletter]
* sending corrections/updates to the FlightGear Manual
* helping new users on the forums/IRC
* writing a wiki page
* organising fly-outs

One of the easiest ways to help is to improve the scenery in your local area by placing buildings/structures using the UFO and submitting them to the [http://scenemodels.flightgear.org/contribute.php FlightGear Scenery Object Database]. It's easy, and best of all requires little time to have a real impact. Instructions on how to do this can be found in the wiki, [http://wiki.flightgear.org/index.php/Placing_3D_Objects_with_the_UFO Placing 3D Objects with the UFO].

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

==Development news==

===A new forum for Google's Summer of Code ===
As some of you may already know, there is now an orchestrated effort going on to get FlightGear ready for becoming a mentoring organization in Google's Summer of Code 2011.

So far, all related information has been collected here in the wiki: [[GSoC]].
But to ease the planning and organization process, there has now been a new sub forum set up for talking about anything that is one way or another related to this effort.
The forum can be found at: http://flightgear.org/forums/viewforum.php?f=38

This should make it much easier for all community members to participate in all related discussions, without necessarily having to be subscribed to the mailing lists.

So if you have anything to contribute to this topic, please do make sure to check out this new forum.

You are for example also invited to make suggestions for new FlightGear related GSoC projects.

For the time being, one topic from the "New Features" sub forum has already been moved to this new forum, it is about a suggestion to procedurally populate the FlightGear scenery with dynamically created cities, for more details please check out [[AutoGen Scenery for FlightGear]].

===New mapping software on the block===
Michael contributes new FlightGear mapping software to the communitiy, written in the Ruby programming language: [http://rubyforge.org/projects/fgmap FGMap]. Basically it shows your current flight position on an [http://openstreetmap.org OpenStreetMap] map. It therefore has some similarity to [[Atlas]] and the online [[MPMap]]s. As with all projects, [http://rubyforge.org/tracker/?func=add&group_id=9572&atid=37032 feedback] is highly appreciated.

FGMap has many features, including:
* Show flight position on Openstreetmap map in real-time
* Download new map tiles on-the-fly in the background
* Add shaded elevation layer to map for nice visual effect
* Display current speed and altitude
* Show position and frequency of all navigation aids on the map
* Create FlightGear route manager entries with a click of the mouse from navigation aids and waypoints
* Record and restore flight path
* Colorize path according to speed and altitude
* Display information about instantaneous speed and altitude for all points of the track
* Set waypoints on map

Downloads and more information are available at [http://rubyforge.org/projects/fgmap the project's website].

=== Troubleshooting triangleintersect, QNaN and friends ===

Last month, the infamous [http://wiki.flightgear.org/index.php/Howto:_Get_rid_of_common_errors#Warning:_Picked_up_TriangleIntersect QNaN errors] that may cause FlightGear to become [[Showstoppers|unresponsive]] have been linked to potential issues in the Nasal interpreter (and more generally Nasal code) by flug, for more details please see: [http://www.flightgear.org/forums/viewtopic.php?f=18&t=8483&p=83701 "Nasal source of Dreaded Triangle Error-source of many probs?"].
For the time being, you will want to look out for any Nasal code that contains unchecked divisions with unvalidated divisors.

==In the hangar==
===Bell P59 Airacomet and Bell 222 X===
''helijah'' created and pushed both P59 and Bell 222X onto Git. The Bell 222X FDM is still in development. More information and download at [http://helijah.free.fr/flightgear/hangar.htm ''helijah's'' Hangar].

===De Havilland Canada DHC-7-150 Dash 7===
''Quadunit404'' has announced [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8805 intentions] to produce his first aircraft, the De Havilland Canada DHC-7-150 Dash 7, adding yet another member of the De Havilland Canada family to to FlightGear fleet after active development begins. Currently he is learning how to model using [[Blender]] and will be studying the FDMs of other turboprop regional airliners already in FlightGear to get an idea of how to write the FDM.

===SpaceShipOne and White Knight===
''helijah'' has made some changes to the SpaceShipOne model including the [[FDM]], adding fuselage reflection effect and separating the SpaceShipOne and White Knight objects. The next step is to improve the SpaceShipOne model by adding wheels and moving parts. After that he will try to separate the two aircraft when in flight.

==Livery database==
In the second week of July, the [http://liveries.flightgear.org livery database] welcomed its [http://liveries.flightgear.org/liveries.php?id=251 250th livery]: a glider club's livery for the [[Robin DR400]], created by top-painter Brett Harrison (Gooneybird). More liveries are welcome as always and can be [http://liveries.flightgear.org/contribute.php uploaded]!

==Scenery corner==
===Animated jetways===
[[File:Movable_Jetway.jpg|thumb|A jetway connecting to a [[Boeing 737-300|737-300]].]]
''skyop'' and ''Gijs'' are currently working on animated jetways for FlightGear that can be activated with a click of the mouse. At the moment they are very primitive and only fit [[Boeing 737|737s]]. Planned features include automatic attachment to your airplane's door and even multiple jetways for wide-body airliners and [[Airbus A380|A380s]]. See [http://www.flightgear.org/forums/viewtopic.php?t=8728 this thread] for more information.

[[Image:Dubai_v0_vs_cs-osm.png|thumb|270px|Dubai, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Dublin scenery===
''eag1e'' created new terrain and buildings for Dublin airport (EIDW). For more details, see [http://flightgear.org/forums/viewtopic.php?f=5&t=8874 this link].

===Detailed terrain for Dubai===
As announced in an [[FlightGear Newsletter March 2010#Dubai is coming up|earlier edition]], Gijs has been (re)drawing the terrain of Dubai. The FlightGear scenery now includes:
* Palm Islands (islands in the shape of a palm)
* The World (islands together forming a worldmap)
* Detailed coastline and city boundaries
The area is represented in its form of 2008, due to the lack of more up-to-date imagery. Given Dubai's massive expansion speed, the scenery can be considered as out-of-date already. Nevertheless it is a great step forward in comparison to the previous terrain, as the image on the right proves.

This new terrain will be available with the upcoming scenery build. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].

[[Image:Qatar_v0_vs_cs-osm.png|thumb|270px|Qatar, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Detailed terrain for Qatar===
Believe it or not, but here is another Emirate that has been hand drawn! Fahim worked on the peninsula of Qatar, very close to Dubai. Seeing the image on the right, you might think detail/accuracy was lost (except for the urban areas), but I can tell you that the new terrain is far more accurate in all aspects.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver].

===Night flying at London Gatwick===
The new version of [[London Gatwick Airport]] (EGKK) is available and has improved textures and features. It claims to be one of the few ''(two?)'' major international airports in [[FlightGear]] suitable for night flying with full lighting textures on all buildings, hazard lights and approximately one hundred lighting masts. The tower even has lit instrumentation visible in the control room. Images are shown at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8363 the forum topic].

The taxiways at night are complex but made easier if the official charts are downloaded from [http://www.nats-uk.ead-it.com]. Many taxiway and runway signs have been included to help you on your way. Additional [[AI]] ground network and AI traffic have made this into a very busy airport and a single gate at each pier has been thoughtfully reserved so you can find a parking space when you land here (see the readme file for details).

In daytime the airport is fully modelled with detailed textures and even the roofs of buildings having accurate features. Stock model jetways, cargoes and ground vehicles have been added in quantity to give an authentic look to the airport. Large areas of open air car parks are distributed around the perimeter with novel layering of textures to enhance the 3D effect of the parked cars. Similarly, woods and trees have been added in surrounding areas to add more to the overall feel of the airport.

London Gatwick EGKK may be downloaded from [http://www.mediafire.com/?t2ml5ezmgwv MediaFire].

==Aircraft review==
'''This month: (name of aircraft here)'''

==From the community==
===TransGear founder leaves===
Rob (MD-Terp), known by many as the founding father of the monthly [[TransGear]] events, [http://www.flightgear.org/forums/viewtopic.php?f=3&t=8809 announced] his "retirement" at the forum. With the first event being held just one month after the first edition of this newsletter, TransGear almost reached its first mileage. However, some former participants are discussing an option to continue organizing the event. More on that in a future edition.

We would like to thank Rob for all he has done, to wish him all the best, and deeply hope to see him return to the community one day.

==And finally...==

===Did you know?===

[[Category:FlightGear Newsletter|2010 06]]

User:Rsbrflyer

2010-07-13T15:37:29Z

Rsbrflyer:

__NOTOC__
{{User
|name = José Roberto Silva
|location = Guarulhos, Greater São Paulo, Brazil
|callsign = PT-RSB
|favourite =[[Airbus A320]], [[Boeing 737]], [[Boeing 747-400]]
|website =[http://josesilvafgliveries.blogspot.com/]
}}

Languages: '''Brazilian Portuguese and English (level 3)'''

==Liveries==
===To Do===
'''Open for requests!'''

*VASP [[Boeing 737-300]]
*BRA [[Boeing 737-300]] Old Colors
*BRA [[Boeing 737-300]] New Colors

===Done===
*TAM [[Boeing 767-300]]
*Qantas [[Boeing 767-300]]
*Gol [[Boeing 737-300]]
*Royal Brunei [[Boeing 767-300]] '''''(superseded by Patrick's version)'''''

==Wiki Articles==
'''Newsletters in general, Pt/Portals and...'''
===Translation to Portuguese===
====To Do====
*New to FlightGear - (Novo no FlightGear) - in progress as of 2010/07
*Flying the Helicopter - (Como voar de helicóptero) - in progress as of 2010/07
====Done====
*FlightGear - [[Pt/FlightGear|Translated version]]
*Installing Scenery - [[Pt/Instalando Cenário||Translated version]]

User:Rsbrflyer

2010-07-13T15:18:08Z

Rsbrflyer: gol 737 livery done

__NOTOC__
{{User
|name = José Roberto Silva
|location = Guarulhos, Greater São Paulo, Brazil
|callsign = PT-RSB
|favourite =[[Airbus A320]], [[Boeing 737]], [[Boeing 747-400]]
|website =[http://josesilvafgliveries.blogspot.com/]
}}

Languages: '''Brazilian Portuguese and English (level 3)'''

==Liveries==
===To Do===
'''Open for requests!'''

===Done===
*TAM [[Boeing 767-300]]
*Qantas [[Boeing 767-300]]
*Gol [[Boeing 737-300]]
*Royal Brunei [[Boeing 767-300]] '''''(superseded by Patrick's version)'''''

==Wiki Articles==
'''Newsletters in general, Pt/Portals and...'''
===Translation to Portuguese===
====To Do====
*New to FlightGear - (Novo no FlightGear) - in progress as of 2010/07
*Flying the Helicopter - (Como voar de helicóptero) - in progress as of 2010/07
====Done====
*FlightGear - [[Pt/FlightGear|Translated version]]
*Installing Scenery - [[Pt/Instalando Cenário||Translated version]]

User:Rsbrflyer

2010-07-03T04:21:12Z

Rsbrflyer: hard to keep my page updated!

__NOTOC__
{{User
|name = José Roberto Silva
|location = Guarulhos, Greater São Paulo, Brazil
|callsign = PT-RSB
|favourite =[[Airbus A320]], [[Boeing 737]], [[Boeing 747-400]]
|website =[http://josesilvafgliveries.blogspot.com/]
}}

Languages: '''Brazilian Portuguese and English (level 3)'''

==Liveries==
===To Do===
'''Open for requests!'''
*Gol [[Boeing 737-300]] (new model)

===Done===
*TAM [[Boeing 767-300]]
*Qantas [[Boeing 767-300]]
*Royal Brunei [[Boeing 767-300]] '''''(superseded by Patrick's version)'''''

==Wiki Articles==
'''Newsletters in general, Pt/Portals and...'''
===Translation to Portuguese===
====To Do====
*New to FlightGear - (Novo no FlightGear) - in progress as of 2010/07
*Flying the Helicopter - (Como voar de helicóptero) - in progress as of 2010/07
====Done====
*FlightGear - [[Pt/FlightGear|Translated version]]
*Installing Scenery - [[Pt/Instalando Cenário||Translated version]]

Pt/Portal:Piloto

2010-07-03T04:16:50Z

Rsbrflyer: adding PT-BR again!

{{MenuDePortais}}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">O Portal de Pilotos</h2>
|-
|style="color:#000;"|
Este portal é destinado a usuários do [[FlightGear]] interessados em aprender mais sobre a aviação, voar em geral e os princípios do voo. Se você está apenas interessado(a) em realismo, por favor note que os artigos listados aqui podem ser mais técnicos do que o que você procura.
|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Recursos de Voo</h2>
|-
|style="color:#000;"|
* [[Pt/Aviônicos e instrumentos|Aviônicos e instrumentos]]
* [[Pt/Comunicações|Comunicações]]
* [[Pt/Como criar um plano de voo|Como criar um plano de voo]]
* [[Pt/Como conseguir cartas IFR|Como conseguir cartas IFR]]
* [[Pt/Definições de acrônimos|Definições de acrônimos]]
* [[Pt/Recursos para instrutores|Recursos para instrutores]]
* [[Pt/Lista de abeviações|Lista de abeviações]]
* [[Pt/Experiência real|Experiência real]]
* [[Pt/Recursos para certificação de pilotos nos EUA|Recursos para certificação de pilotos nos EUA]]
* [[Pt/Recursos de Tutoriais|Recursos de Tutoriais]]
* [[Pt/Entendendo Altitude|Entendendo Altitude]]
* [[Pt/Entendendo Navegação|Entendendo Navegação]]
* [[Pt/Entendendo torque e fator-P|Entendendo torque e fator-P]]
* [[Pt/Tempo e Clima|Tempo e Clima]]

===Links externos===
* [http://freechecklists.net/ Checklists] ''(em inglês)''
* [http://www.faa.gov/library/manuals/ Manuais da FAA] ''(em inglês)''
* [http://www.smartcockpit.com SmartCockpit.com] ''(em inglês)''
* [http://www.worldaerodata.com/ World Aeronautical Database] ''(em inglês)''

|-
|}

|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Helicópteros</h2>
|-
|style="color:#000;"|
Voar helicópteros é diferente de voar aviões de asa fixa em algumas maneiras. Por isso, habilidades diferentes e um entendimento diferente de aerodinâmica são necessários.

*[[Pt/Como voar de helicóptero|Como voar de helicóptero]], um manual do FlightGear sobre como voar helicópteros.

===Links externos===
* [http://www.faa.gov/library/manuals/aircraft/media/faa-h-8083-21.pdf The Rotorcraft Flying Handbook] ''(em inglês)''
* [http://www.dynamicflight.com/aerodynamics/ Helicopter Aerodynamics] ''(em inglês)''
* [http://en.wikipedia.org/wiki/Category:Helicopter_aerodynamics Aerodynamics on Wikipedia] ''(em inglês)''
|}
|}

__NOTOC__
__NOEDITSECTION__

[[es:Portal:Pilot]]
[[en:Portal:Pilot]]

Pt/Portal:Desenvolvedor/Modelagem 3D

2010-07-03T04:04:53Z

Rsbrflyer: adding PT-BR!

{{MenuDePortais}}

{|style="border-spacing:8px; margin:0px -8px; width:100%;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">O Portal da Modelagem 3D</h2>
|-
|style="color:#000;"|
Este portal se destina exclusivamente a tratar de modelagem 3D em geral, não se tratando especificamente da modelagem de uma aeronave ou cenário, mas sim como essas coisas funcionam no [[FlightGear]].
O objetivo é oferecer recursos relacionados com a modelagem 3D para o FlightGear. São recursos como tutoriais, cursos online, e-books, webcasts, etc.
Se você já sabe alguma coisa sobre modelagem 3D e está interessado na modelagem de um avião ou cenário especificamente, você deve olhar a página [[Pt/Portal:Desenvolvedor/Avião|Portal:Desenvolvedor/Avião]] ou [[Pt/Portal:Desenvolvedor/Cenário|Portal:Desenvolvedor/Cenário]].

|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Modelagem 3D</h2>
|-
|style="color:#000;"|
* [[Pt/Primeiros passos na modelagem 3D]]
* [[Pt/FAQ sobre modelagem]]
* [[Pt/Recursos para modelagem]]
* [[Copyright Inquiry|Direitos Autorais]] ''(em inglês)''
|-
|}

|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Tutoriais</h2>
|-
|style="color:#000;"|

* [http://www.linuxhaxor.net/2009/02/09/50-tutorials-to-get-you-started-with-gimp/ 50 tutorials to get started with gimp] (criação/edição de texturas) ''(em inglês)''.
* [http://www.linuxhaxor.net/2009/02/19/25-tutorials-to-get-you-started-with-blender/ 25 tutorials to get you started with blender] (modelagem 3d) ''(em inglês)''.
* [[Pt/Como iluminar faces|Como iluminar faces]]
* [[Pt/Como desenhar modelos 3D de aeronaves|Como desenhar modelos 3D de aeronaves]]
* [[Pt/Como Importar e Exportar modelos|Como Importar e Exportar modelos]]
* [[Pt/Como adicionar sombras usando Blender|Como adicionar sombras usando Blender]]
* [[Pt/Como modelar no SketchUp|Como modelar no SketchUp]]
* [[Pt/Texturas e Mapas de Texturas no SketchUp|Texturas e Mapas de Texturas no SketchUp]]
* [[Pt/Tutorial sobre Normais e Transparência|Tutorial sobre Normais e Transparência]]
* [[Pt/Algumas experiências com Blender e FlightGear|Algumas experiências com Blender e FlightGear]]
* [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro Livro em inglês sobre o Blender]
|}
|}

[[en:Portal:Developer/3D Modelers]]
[[es:Portal:Desarrolladores/3D Modeladores]]

Portal:Developer/3D Modelers/pt

2010-07-03T03:54:35Z

Rsbrflyer: Redirected page to Pt/Portal:Desenvolvedor/Modelagem 3D

#REDIRECT [[Pt/Portal:Desenvolvedor/Modelagem 3D]]

AI-traffic

2010-07-03T03:54:24Z

Rsbrflyer: Redirected page to Interactive traffic

#REDIRECT[[Interactive traffic]]

Pt/Portal:Desenvolvedorpara/Modelagem 3D

2010-07-03T03:53:48Z

Rsbrflyer: moved Pt/Portal:Desenvolvedorpara/Modelagem 3D to Pt/Portal:Desenvolvedor/Modelagem 3D

#REDIRECT [[Pt/Portal:Desenvolvedor/Modelagem 3D]]

Pt/Portal:Desenvolvedor/Modelagem 3D

2010-07-03T03:53:48Z

Rsbrflyer: moved Pt/Portal:Desenvolvedorpara/Modelagem 3D to Pt/Portal:Desenvolvedor/Modelagem 3D

{{PortalMenu}}

{|style="border-spacing:8px; margin:0px -8px; width:100%;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">O Portal da Modelagem 3D</h2>
|-
|style="color:#000;"|
Este portal se destina exclusivamente a tratar de modelagem 3D em geral, não se tratando especificamente da modelagem de uma aeronave ou cenário, mas sim como essas coisas funcionam no FlightGear.
O objetivo é oferecer recursos relacionado com a modelagem 3D para o FlightGear. São recursos como tutoriais, cursos online, ebooks, webcasts, etc.
Se você já sabe alguma coisa sobre modelagem 3D e está interessado na modelagem de um avião ou cenário especificamente, você deve olhar sim a página [[Portal:Developer/Aircraft]] ou [[Portal:Developer/Scenery]].

|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Modelagem 3D</h2>
|-
|style="color:#000;"|
* [[ Modeling - Getting Started ]]
* [[ Modeling - FAQ ]]
* [[ Modeling Resources ]]
* [http://wiki.flightgear.org/index.php/Copyright_Inquiry Copyright Inquiry]
|-
|}

|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Tutoriais</h2>
|-
|style="color:#000;"|

* [http://www.linuxhaxor.net/2009/02/09/50-tutorials-to-get-you-started-with-gimp/ 50 tutorials to get started with gimp] (criação/edição de texturas)
* [http://www.linuxhaxor.net/2009/02/19/25-tutorials-to-get-you-started-with-blender/ 25 tutorials to get you started with blender] (modelagem 3d)
* [[Howto: Illuminate faces|Illuminate faces]] (texturas durante a noite)
* [[ Howto: 3D Aircraft Models|3D Aircraft Models]] (howto)
* [[ Model Import and Export ]]
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender|Add smooth shadows in Blender]]
* [[ Modeling - SketchUp]]
* [[Textures & Texture Maps in SketchUp]]
* [[ Normals and Transparency Tutorial ]]
* [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro Blender3D Modeling]
* [[ Blender and FlightGear - some experiences]]
|}
|}

[[en:Portal:Developer/3D Modelers]]
[[es:Portal:Desarrolladores/3D Modeladores]]

FlightGear Newsletter July 2010

2010-07-02T15:35:43Z

Rsbrflyer: /* In the hangar */ more wikifying

FlightGear Newsletter July 2010

2010-07-02T15:33:37Z

Rsbrflyer: /* Scenery corner */ wikifying and making links shorter

User:Rsbrflyer

2010-07-02T03:30:38Z

Rsbrflyer:

__NOTOC__
{{User
|name = José Roberto Silva
|location = Guarulhos, Greater São Paulo, Brazil
|callsign = PT-RSB
|favourite =[[Airbus A320]], [[Boeing 737]], [[Boeing 747-400]]
|website =[http://josesilvafgliveries.blogspot.com/]
}}

Languages: '''Portuguese (BR) and English-3'''

==Liveries==
===To Do===
Open for requests!
*Gol [[Boeing 737-300]] (new model)

===Done===
*TAM [[Boeing 767-300]]
*Qantas [[Boeing 767-300]]
*''Royal Brunei [[Boeing 767-300]]'' '''''(superseded by Patrick's version)'''''

==Wiki Articles==
Newsletters in general and...
===Translation to Portuguese===
====To Do====
*New to FlightGear - in progress as of 2010/07
*Flying the Helicopter - in progress as of 2010/07
====Done====
*FlightGear
*Installing Scenery

User:Rsbrflyer

2010-07-02T03:29:19Z

Rsbrflyer: keeping my page up to date =P

__NOTOC__
{{User
|name = José Roberto Silva
|location = Guarulhos, Greater São Paulo, Brazil
|age = 23
|callsign = PT-RSB
|favourite =[[Airbus A320]], [[Boeing 737]], [[Boeing 747-400]]
|website =[http://josesilvafgliveries.blogspot.com/]
}}

Languages: '''Portuguese (BR) and English-3'''

==Liveries==
===To Do===
Open for requests!
*Gol [[Boeing 737-300]] (new model)

===Done===
*TAM [[Boeing 767-300]]
*Qantas [[Boeing 767-300]]
*''Royal Brunei [[Boeing 767-300]]'' '''''(superseded by Patrick's version)'''''

==Wiki Articles==
Newsletters in general and...
===Translation to Portuguese===
====To Do====
*New to FlightGear - in progress as of 2010/07
*Flying the Helicopter - in progress as of 2010/07
====Done====
*FlightGear
*Installing Scenery

FlightGear IRC channel

2010-07-01T04:00:37Z

Rsbrflyer: the irc problem :-(

The '''FlightGear IRC''' (Internet Relay Chat) '''channel''' is a chat room related to everything about [[FlightGear]]. It's mostly used by developers, but it is also a good place to ask for help if you are having a question.

To enter the IRC, you need an IRC client installed on your computer. For users of Mozilla browsers (like Firefox), the plugin [https://addons.mozilla.org/de/firefox/addon/16 ChatZilla] is surely a good option. You can also use [http://www.xchat.org/ XChat] (Linux and Windows), [http://www.pidgin.im/ Pidgin], [http://colloquy.info/ Colloquy] (for Mac), [http://www.mirc.com/ mIRC] or any other client.

==Official host==
{|
! style="background:#efefef; text-align: center" width="200px" | Host
! style="background:#efefef; text-align: center" | Comments
|-
| mpserver12.flightgear.org
| Being used now.
|}

The IRC chat has several channels, some of which are listed below.

{|
! style="background:#efefef; text-align: center" width="200px" |
! style="background:#efefef; text-align: center" | channel
|-
| Main channel
| #flightgear
|-
| [[Blender]]
| #flightgear-blender
|-
| [[FlightGear_Flight_Academy|Flight School]]
| #fg_school
|-
| IFR Navigation Squawk
| #airliners
|-
| Off topic chat
| #fg_cantene
|-
| Wiki
| #wiki
|-
| Forum
| #flightgear-forum
|}

==Other hosts==
{|
! style="background:#efefef; text-align: center" width="200px" |
! style="background:#efefef; text-align: center" | Host
! style="background:#efefef; text-align: center" | Channels
|-
| [[Flight Gear Flying Club]]
| uk1.connectedserver.com
| #FlyingClub
|-
| irc.freenode.net #flightgear
| Only for emergencies.
|}

==How to get in there with ChatZilla==
[[Image:IRC-ChatZilla.jpg|thumb|ChatZilla Client area]]
When using ChatZilla, go to your Mozilla/Firefox browser and enter [irc://mpserver12.flightgear.org irc://mpserver12.flightgear.org]. When ChatZilla has connected to the host, click "IRC" and "Join channel...". Pick the preferred channel.

To get directly to the main channel with ChatZilla, you can also enter [irc://mpserver12.flightgear.org/flightgear irc://mpserver12.flightgear.org/flightgear] in your browser.

==External links==
* [http://t0x.in/irccommands.html General IRC commands]

FlightGear Newsletter July 2010

2010-06-30T15:12:40Z

Rsbrflyer: how could I forget the category?

FlightGear Newsletter July 2010

2010-06-30T15:10:39Z

Rsbrflyer: preparing soil for the july newsletter

FlightGear Newsletter June 2010

2010-06-27T15:10:21Z

Rsbrflyer: helijah's c130 update

{{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.''

==Development news==
===SquawkGear: Bringing VATSIM to FlightGear!===
{{Main article|SquawkGear}}
SquawkGear is the much-awaited client that allows FlightGear users to connect to the largest and most realistic sim server in the world: [http://vatsim.net/ VATSIM]. VATSIM is simply a network that can, in theory, take any sim, although the current ones are X-Plane and Microsoft Flight Simulator. Using addons like SquawkBox for MSFS, pilots must adhere to strict rules about realism. A valid [[flight plan]] must always be submitted before takeoff, for instance. And pilots must contact [[Air Traffic Control]] before any actions.

SquawkGear brings this wonderful server to FlightGear. While installation is not as simple as that of VATSIM clients for MSFS, pilots are now able to connect to the VATSIM network and use chat and voice to communicate with other players and ATC. Since [[scenery]] is very different between sims, aircraft do not always appear where they are supposed to be; a MSFS user might see you hovering a few feet above the ground, for instance.

With its first release, SquawkGear is an excellent addon for pilots wishing to get on VATSIM without having to buy the payware sims. It is strongly recommended that you '''read all manuals''' before connecting to VATSIM; not only because installation is tricky, but also because there are certain rules to be followed on VATSIM. You will find that your [[KSFO]] on VATSIM is a thousand times more under control than your KSFO on one of the [[Howto: Multiplayer|mpservers]]!

''Special thanks to Ivan (Reed) for all of his work!''

===Bombable air combat add-on updated===
The [http://www.flightgear.org/forums/viewtopic.php?f=2&t=5742 Bombable air combat add-on to FlightGear] received a major update in June. Bombable now has these features:

* Dogfight against other FlightGear pilots over multiplayer with Sopwith Camel, SPAC VII, Fokker DR 1 Triplane, or A6M2 Zero
* Explode/burn when you crash
* Exceeding aircraft limitations (excess g-forces, overspeed) adds damage to your aircraft and finally leads to shutdown/crash
* Shootable/bombable moving AI tanks, jeeps, ships, and aircraft that catch fire, burn, explode, sink, crash, etc.
* AI scenarios that allow you to use FlightGear aircraft for air-to-ground, air-to-sea, and air-to-air combat missions against these targets

==In the hangar==
===Boeing 787 and CRJ-200===
''nickyivyca'' is currently working on the [[Boeing 787]]. He corrected the [[FDM]] and changed some details in the model.
More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8203 in the forums].

He has also been working in the [[CRJ-200]]:

''"The CRJ-200 and 787 were made with very similar systems and such. Neither had a 2.0 compatible AP. So, I found out what was wrong with the one for the 787 first, and made those changes to the CRJ here. Both worked. I also did some FDM improvements, like moving the engines to where they really are and adding gear smoke and contrails."'' - says he [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8329 in the forum thread].

===Cessna T-37===
''richter'' and ''snipey'' are working together in improving the Cessna T-37. Here is a list of items that have been improved/created:

'''Model:'''
* Completely remodeled canopy;
* Main gear wheel wells and covers.
'''Sound:'''
* Interior-exterior sound level difference.
'''Instruments:'''
* Basic flight instruments.

More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8354 at the forum].

===CH-47 Chinook===
''MOJO'' is tuning the CH-47. He spent some time adding external cosmetics which main purpose is to add more detail to the Chinook. He added antenna and aerials, domed windows, pitot tubes, winch, engine hub details and started with the internal cargo bay. He intends to be adding an animated refuel probe and will be including several liveries. His ultimate aim for the CH-47 Chinook is to attempt to get the model more defined and realistic.

===Cirrus Vision SF50===
''Zexe'' created a SF50 model. It is still at a very early stage. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8352 here].

===MiG-15bis===
''vitos'' improved the MiG-15bis model, and released it. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7486 here].

===MB-339 PAN===
The MB-339 PAN aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8604 was updated by ''Albert''] to work with [[FlightGear]] version 2.0.0.

===Curtiss P-40 Warhawk===
''jackmermod'' [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8621 is developing a P-40 model]. It is already complete, and to be done are the animations and textures. Development of the P-40 Warhawk is coming along very quick, although a full release date is unknown.

===X-29A===
''Intel-Qube'' [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8485 is currently revamping] the experimental X-29A aircraft. Here is a list of items that have been improved/created:

* A new, more realistic [[FDM]] is on the way;
* Landing gear has been redone and is now much more aesthetically pleasing;
* New exhaust will now dilate based on throttle as it should;
* The cockpit panel has been entirely rebuilt, is far more detailed, and will likely have interactive switches in the final release;
* The model is more ''"anatomically correct"''.

===Il-96-400/T===
The Il-96-400/T [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7439 has been updated] to version 3, with more accurate model and a better panel, among other little fixes.

===C-130 Hercules===
The [[C-130]] Hercules [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8629 is receiving some updates] from ''glazmax'' and ''helijah''. These updates include FDM and instruments fixes and improvements.

===San Antonio LPD17===
Browsing through the files, ''HHS'' [http://www.flightgear.org/forums/viewtopic.php?f=23&t=8351 found a rotorcraft carrier model] and made a scenario to run it, which is available on [[Git]].

==Scenery corner==
===Nighttime London Gatwick===
London Gatwick (EGKK) is being further improved and is in the second phase of development - night textures. All the buildings and features are currently being modified by ''karla'' to give suitable lighting and make London Gatwick even more attractive to FlightGear commercial fliers. Landing or taking off from Gatwick at night should add much to your enjoyment of the game - and most likely extend the hours you enter in your pilot's log.
Further improvements and many minor changes are also being made to the existing models and daytime textures.
The link shows an image of the part completed airport at night http://www.donlavelle.net/flightgear/flightgear19.html.

The new scenery will be released early in July.

===Dubai airport gets busy===
With the terrain updates that were discussed in the [[FlightGear Newsletter March 2010#Dubai is coming up|March edition]] still in our minds, we now have another feature for the area; taking it yet another step closer to a bussy and realistic representation of the real emirate!

After looking jealously at the greatly enhanced airport [[Amsterdam Airport Schiphol|Schiphol]] (EHAM) and the latest highlight Gatwick (EGKK) Mike ([[User:D-SKY1|D-SKY1]]) decided to create [[Interactive_Traffic|interactive traffic]] for [[Dubai International Airport]] (OMDB). Based on the existing airport layout in FlightGear the traffic pattern for taxiing between gates and runways has been created in [[TaxiDraw]] next to a timetable for runway usage.

Although no model work is done (yet) a big bunch of scheduled flights is now added to this important hub in the middle east. As Dubai is home port for Emirates Airlines (UAE) only Emirates flights are included. Within the next weeks more scheduled flights for AI traffic at Dubai will be added. During the process of creating AI traffic he tried to stay as close as possible to the real life timetable for Dubai International Airport querying several sources for double checking.

As Emirates Airlines (UAE) is one of the most important customers for the [[Airbus A380]] (UAE just ordered another 30 units of A380) the Emirates Airlines livery has been added to AI aircraft A380. Additionally some minor errors in several traffic files concerning changed [[ICAO]] codes for some airports have been removed.

All changes are available via [[Git]]. Enjoy the enhancements; and always follow [[SID]]s and [[STAR]]s to prevent collisions.

===Meadows Field and FGSignMaker===
''skyop'' released his improvements to the Meadows Field (KBFL) scenery. Read [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8466 this topic] for more information.

He is also writing [[FGSignMaker]], a tool to generate taxiway sign codes written in JavaScript. More information on taxiway signs can be found [[Signs|here]].

===Landcover additions===
Connecticut, Oshkosh (Wisconsin, USA) and the Toronto Harbor have been added to the [[FlightGear]] mapserver. They will be released to the public with the next scenery build, or alternatively the shapefiles can be downloaded and compiled by the user.

This is in addition to the other numerous improvements to the land cover which are pending with the next scenery release, which includes (but is not limited to) France; Madrid, Spain; London, England; Bonn, Germany; Western Washington, USA; Northwest Oregon, USA; Phoenix, Arizona, USA; Washington, DC, and Baltimore, Maryland, USA; Rhode Island; Hawaii; and Long Island, New York, USA.

Landcover development is ongoing.

===LFLJ and EDDF===
After one year of having released these sceneries (LFLJ/EDDF), ''papillon81'' returned to make changes (some of them big) at them.
More information: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=5238&st=0&sk=t&sd=a#p84745 EDDF], [http://www.flightgear.org/forums/viewtopic.php?f=5&t=1436&st=0&sk=t&sd=a&start=30#p84800 LFLJ].

==Multiplayer News==
===Atlas Virtual Airlines' leaders recognized!===
[[Atlas Virtual Airlines]], FlightGear's most populated airline, has been a hit success in its inaugural months since opening in mid-April. The airline, however, couldn't have made it without the guidance of its two current leaders: ''MaverickAlex'' (Alex Park) and ''SkyWlf77'' (Jason Sheperd). Besides sinking their own cash into the airline for site domain and software, these two founding members have sorted out many mis-judgements of Atlas and helped to form a strong and community-bonding airline. Jason, the vice-chairman and moderator, helped revamp AVA's standing on the forums and turned many former anti-Atlas-ers into supporting members, which has been very beneficial for the FlightGear multiplayer community. Thanks to him, members can now feel confident to join an airline that was, just months ago, in the midst of intense controversy. Sheperd has taken a strong stand against arguments and flame wars on the Forums, intent on preventing the locked-topics and arguing members that degraded the VA Community during the VA "Dark Ages". But now, Atlas has flourished into a friendship-filled and happy organization that members find enjoyment and fun in.

Meanwhile, Alex, the current chairman and administrator, independently designed an awesome and top-of-the-line VA website for Atlas pilots. He has also worked with nightmares of coding to get drawing-board ideas implemented. And on top of it all, Alex is finishing up his Bombardier Dash-8 400Q, designed especially for Atlas Express flights. This very nicely modeled aircraft will also be available to the public, underlining how Atlas Virtual Airlines is really benefiting all of FlightGear. Alex is the brains behind it all that makes Atlas so sophisticated. His partner, Jason, has the ideas and people-person skills that gives Atlas the openness and fun that attracts its 50-plus members. So, from all of Atlas and those who follow it, thank you, Jason and Alex!

BRIEFS: Atlas celebrated its 50th member this month, a landmark achievement for a VA that is still newborn!

==Aircraft Review==
'''This month: B-25 Mitchell'''

[[Image:B-25.jpg|thumb|270px|A B-25 in the air near KATL]]
The [[B-25]] served in almost every theater in World War II. From Europe to the Pacific, the Mitchell was there. One of the most famous missions accomplished by B-25s was the Doolittle Raid on Tokyo, when a group of 16 B-25s attacked the Japanese mainland, raising morale in the United States, and changing the priorities of the Imperial Japanese Navy, and possibly changing the direction of the war.

The flightgear model looks good on the outside. The author has done a lot of work on the textures, and this is improved even more by some excellent liveries made by Gooneybird that have been added to the B-25 base package by the author. The landing gear, engines and canopies are all carefully modeled, too.

The Cockpit is a little bit threadbare, with no chairs, two pilot figures, and the standard six instruments, which is more than enough to fly with. The only other issue I could come up with was the lack of weapons, but that is only an aesthetic problem. The B-25 handles nicely both on the ground and in the air. I can't talk about accuracy, however, as I have never flown in a B-25, so I don't know how it 'feels' in the air.

The Mitchell sounds great, too!

''Review by Armchair Ace''

==From the community==
===LinuxTAG===
Once again, a team of FlightGear enthusiasts operated a booth during the four days of this year's [http://www.linuxtag.org/ LinuxTAG], the most important place for Linux and open source software in Europe. Besides to it's main purpose of presenting FlightGear to a public audience, LinuxTag becomes more and more '''the''' place for a meeting of core FlightGear developers and users. A technical discussion between James, Alex and Matthias has the potential to become a ''FlightGear legend'' and will probably lead to a multithreaded processing within the simulator's core. Alex also held a public presentation about the integration of [http://www.linuxtag.org/2010/en/program/free-conference/all-events/details.html?talkid=329 "Android for pilots"] with fgfs. [http://www.linuxtag.org/2010/fileadmin/www.linuxtag.org/slides/Alex%20Perry%20-%20Android%20for%20Pilots%20-%20Integration%20with%20the%20FlightGear%20Flight%20Simulator.pdf]

An exciting first contact was initiated between FlightGear team members and a hardware vendor resulting in an idea to operate a shared presentation of powerful hardware running a powerful flight simulator at the next year's LinuxTAG - to proof the claim "where .com meets .org".

===FlightGear on YouTube===
* ''edubletooth'' captured a [http://www.youtube.com/watch?v=EeQUfnHLs_Q bunch of landings] at the airports with the world's most famous approach: [[Princess Juliana International Airport|Princess Juliana]] in the Netherlands Antilles. Make sure to bend when a 777-200 or maybe even a mighty [[Boeing 747|747]] is passing just meters over your head!
* [http://www.youtube.com/watch?v=nzCcqtkTUT8 This excellent video] proves that ''Howto'' Oscar (we already mentioned him last month) does more than creating howtos. Together with Don's extremely detailed simulation of Gatwick Airport (EGKK), Oscar's video angles make this an interesting and pleasant video to watch.

==And finally...==
===Your own Copilot===
How about having your own Copilot to help you fly your heavy metal? Imagine: You're at 3000 ft making a hand controlled descent to EGKK 26L in your [[Boeing 777-200|777-200ER]]: "flaps down"; check airspeed and altitude; you're now five miles out; "undercarriage down"; reduce speed a little more; "flaps down"; you seem to be slightly overspeed; "spoilers"; touch down "brakes" then "reverse thrust"; "flaps retract"; now take a look at the detailed scenery while taxiing to your stand; "view" and "zoom out".

Those using Windows can employ '''Shoot''' - a free user-editable voice command utility. This may be used concurrently with FlightGear to recognize spoken words or phrases and carry out keyboard actions - including sequential or Shift/Alt/Ctrl... keying. Unfortunately Linux users do not have access to such a powerful utility.

[http://clans.gameclubcentral.com/shoot Download Shoot 1.6.4] and install it on your PC. You also need the Microsoft Speech API (SAPI) which is also free; the link is given on the Shoot website. The free Microsoft .NET should also be installed using the Shoot link.

Shoot may be edited to obey verbal commands such as "start engines", "maximum thrust", "undercarriage up", "flaps retract", "trim nose down", "deploy spoilers", "reverse thrust", "view exterior" - or whatever you choose. Try it and add more immersion to your flying.

===Did you know?===

* ...that FlightGear is made of roughly 3,000,000 lines of code and would cost more than $42,000,000 if created from scratch? <small>(Metrics from [http://www.ohloh.net/p/flightgear/analyses/latest ohloh.net])</small>

* ...that in version 2.0, fellow pilots' chat messages could be ignored on [[multiplayer]] by checking the ignore box in the pilot list?
For upcoming releases, pilots' aircraft will also be able to be ignored. This is part of a strong offensive against "trolling" that disrupts MP flying.<br>

* ...that the USS Nimitz [[Howto: Carrier|aircraft carrier]] has deck elevators that can be lowered/raised to go below deck?
Toggle them up/down in your ATC Options menu under Carrier; Check-Apply raises them, unchecked-apply lowers them.

[[Category:FlightGear Newsletter|2010 06]]

FlightGear Newsletter June 2010

2010-06-27T03:15:22Z

Rsbrflyer: some more news and fixed typos.

{{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.''

==Development news==
===SquawkGear: Bringing VATSIM to FlightGear!===
{{Main article|SquawkGear}}
SquawkGear is the much-awaited client that allows FlightGear users to connect to the largest and most realistic sim server in the world: [http://vatsim.net/ VATSIM]. VATSIM is simply a network that can, in theory, take any sim, although the current ones are X-Plane and Microsoft Flight Simulator. Using addons like SquawkBox for MSFS, pilots must adhere to strict rules about realism. A valid [[flight plan]] must always be submitted before takeoff, for instance. And pilots must contact [[Air Traffic Control]] before any actions.

SquawkGear brings this wonderful server to FlightGear. While installation is not as simple as that of VATSIM clients for MSFS, pilots are now able to connect to the VATSIM network and use chat and voice to communicate with other players and ATC. Since [[scenery]] is very different between sims, aircraft do not always appear where they are supposed to be; a MSFS user might see you hovering a few feet above the ground, for instance.

With its first release, SquawkGear is an excellent addon for pilots wishing to get on VATSIM without having to buy the payware sims. It is strongly recommended that you '''read all manuals''' before connecting to VATSIM; not only because installation is tricky, but also because there are certain rules to be followed on VATSIM. You will find that your [[KSFO]] on VATSIM is a thousand times more under control than your KSFO on one of the [[Howto: Multiplayer|mpservers]]!

''Special thanks to Ivan (Reed) for all of his work!''

===Bombable air combat add-on updated===
The [http://www.flightgear.org/forums/viewtopic.php?f=2&t=5742 Bombable air combat add-on to FlightGear] received a major update in June. Bombable now has these features:

* Dogfight against other FlightGear pilots over multiplayer with Sopwith Camel, SPAC VII, Fokker DR 1 Triplane, or A6M2 Zero
* Explode/burn when you crash
* Exceeding aircraft limitations (excess g-forces, overspeed) adds damage to your aircraft and finally leads to shutdown/crash
* Shootable/bombable moving AI tanks, jeeps, ships, and aircraft that catch fire, burn, explode, sink, crash, etc.
* AI scenarios that allow you to use FlightGear aircraft for air-to-ground, air-to-sea, and air-to-air combat missions against these targets

==In the hangar==
===Boeing 787 and CRJ-200===
''nickyivyca'' is currently working on the [[Boeing 787]]. He corrected the [[FDM]] and changed some details in the model.
More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8203 in the forums].

He has also been working in the [[CRJ-200]]:

''"The CRJ-200 and 787 were made with very similar systems and such. Neither had a 2.0 compatible AP. So, I found out what was wrong with the one for the 787 first, and made those changes to the CRJ here. Both worked. I also did some FDM improvements, like moving the engines to where they really are and adding gear smoke and contrails."'' - says he [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8329 in the forum thread].

===Cessna T-37===
''richter'' and ''snipey'' are working together in improving the Cessna T-37. Here is a list of items that have been improved/created:

'''Model:'''
* Completely remodeled canopy;
* Main gear wheel wells and covers.
'''Sound:'''
* Interior-exterior sound level difference.
'''Instruments:'''
* Basic flight instruments.

More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8354 at the forum].

===CH-47 Chinook===
''MOJO'' is tuning the CH-47. He spent some time adding external cosmetics which main purpose is to add more detail to the Chinook. He added antenna and aerials, domed windows, pitot tubes, whinch, engine hub details and started with the internal cargo bay. He is going to be adding an animated refuel probe and will be doing some more liveries also, his main aim is to try and get the model more defined.

===Cirrus Vision SF50===
''Zexe'' created a SF50 model. It is still at a very early stage. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8352 here].

===MiG-15bis===
''vitos'' improved the MiG-15bis model, and released it. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7486 here].

===MB-339 PAN===
The MB-339 PAN aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8604 was updated by ''Albert''] to work with [[FlightGear]] version 2.0.0.

===Curtiss P-40 Warhawk===
''jackmermod'' [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8621 is developing a P-40 model]. It is already complete, and to be done are the animations and textures. Development is progressing fastly.

===X-29A===
''Intel-Qube'' [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8485 is currently revamping] the experimental X-29A aircraft. Here is a list of items that have been improved/created:

* A new, more realistic [[FDM]] is on the way;
* Landing gear has been redone and is now much more aesthetically pleasing;
* New exhaust will now dilate based on throttle as it should;
* The cockpit panel has been entirely rebuilt, is far more detailed, and will likely have interactive switches in the final release;
* The model is more ''"anatomically correct"''.

===Il-96-400/T===
The Il-96-400/T [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7439 has been updated] to version 3, with more accurate model and a better panel, among other little fixes.

===San Antonio LPD17===
Browsing through the files, ''HHS'' [http://www.flightgear.org/forums/viewtopic.php?f=23&t=8351 found a rotorcraft carrier model] and made a scenario to run it, which is available on [[Git]].

==Scenery corner==
===Nighttime London Gatwick===
London Gatwick (EGKK) is being further improved and is in the second phase of development - night textures. All the buildings and features are currently being modified by ''karla'' to give suitable lighting and make London Gatwick even more attractive to FlightGear commercial flyers. Landing or taking off from Gatwick at night should add much to your enjoyment of the game - and most likely extend the hours you enter in your pilot's log.
Further improvements and many minor changes are also being made to the existing models and daytime textures.
The link shows an image of the part completed airport at night http://www.donlavelle.net/flightgear/flightgear19.html.

The new scenery will be released early in July.

===Dubai airport gets busy===
With the terrain updates that were discussed in the [[FlightGear Newsletter March 2010#Dubai is coming up|March edition]] still in our minds, we now have another feature for the area; taking it yet another step closer to a bussy and realistic representation of the real emirate!

After looking jealously at the greatly enhanced airport [[Amsterdam Airport Schiphol|Schiphol]] (EHAM) and the latest highlight Gatwick (EGKK) Mike ([[User:D-SKY1|D-SKY1]]) decided to create [[Interactive_Traffic|interactive traffic]] for [[Dubai International Airport]] (OMDB). Based on the existing airport layout in FlightGear the traffic pattern for taxiing between gates and runways has been created in [[TaxiDraw]] next to a timetable for runway usage.

Although no modelwork is done (yet) a big bunch of scheduled flights is now added to this important hub in the middle east. As Dubai is home port for Emirates Airlines (UAE) only Emirates flights are included. Within the next weeks more scheduled flights for AI traffic at Dubai will be added. During the process of creating AI traffic he tried to stay as close as possible to the real life timetable for Dubai International Airport querying several sources for double checking.

As Emirates Airlines (UAE) is one of the most important customers for the [[Airbus A380]] (UAE just ordered another 30 units of A380) the Emirates Airlines livery has been added to AI aircrafts A380. Additionally some minor errors in several traffic files concerning changed [[ICAO]] codes for some airports have been removed.

All changes are available via [[Git]]. Enjoy the enhancements; and always follow [[SID]]s and [[STAR]]s to prevent collisions.

===Meadows Field and FGSignMaker===
''skyop'' released his improvements to the Meadows Field (KBFL) scenery. Read [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8466 this topic] for more information.

He is also writing [[FGSignMaker]], a tool to generate taxiway sign codes written in JavaScript. More information on taxiway signs can be found [[Signs|here]].

===Landcover additions===
Connecticut, Oshkosh (Wisconsin, USA) and the Toronto Harbor have been added to the [[FlightGear]] mapserver. They will be released to the public with the next scenery build, or alternatively the shapefiles can be downloaded and compiled by the user.

This is in addition to the other numerous improvements to the land cover which are pending with the next scenery release, which includes (but is not limited to) France; Madrid, Spain; London, England; Bonn, Germany; Western Washington, USA; Northwest Oregon, USA; Phoenix, Arizona, USA; Washington, DC, and Baltimore, Maryland, USA; Rhode Island; Hawaii; and Long Island, New York, USA.

Landcover development is ongoing.

===LFLJ and EDDF===
After one year of having released these sceneries (LFLJ/EDDF), ''papillon81'' returned to make changes (some of them big) at them.
More information: [http://www.flightgear.org/forums/viewtopic.php?f=5&t=5238&st=0&sk=t&sd=a#p84745 EDDF], [http://www.flightgear.org/forums/viewtopic.php?f=5&t=1436&st=0&sk=t&sd=a&start=30#p84800 LFLJ].

==Multiplayer News==
===Atlas Virtual Airlines' leaders recognised!===
[[Atlas Virtual Airlines]], FlightGear's most populated airline, has been a hit success in its inaugural months since opening in mid-April. The airline, however, couldn't have made it without the guidance of its two current leaders: ''MaverickAlex'' (Alex Park) and ''SkyWlf77'' (Jason Sheperd). Besides sinking their own cash into the airline for site domain and software, these two founding members have sorted out many mis-judgements of Atlas and helped to form a strong and community-bonding airline. Jason, the vice-chairman and moderator, helped revamp AVA's standing on the forums and turned many former anti-Atlas-ers into supporting members, which has been very beneficial for the FlightGear multiplayer community. Thanks to him, members can now feel confident to join an airline that was, just months ago, in the midst of intense controversy. Sheperd has taken a strong stand against arguments and flame wars on the Forums, intent on preventing the locked-topics and arguing members that degraded the VA Community during the VA "Dark Ages". But now, Atlas has flourised into a friendship-filled and happy organization that members find enjoyment and fun in.

Meanwhile, Alex, the current chairman and administrator, independently designed an awesome and top-of-the-line VA website for Atlas pilots. He has also worked with nightmares of coding to get drawing-board ideas implemented. And on top of it all, Alex is finishing up his Bombardier Dash-8 400Q, designed especially for Atlas Express flights. This very nicely modeled aircraft will also be available to the public, underlining how Atlas Virtual Airlines is really benefiting all of FlightGear. Alex is the brains behind it all that makes Atlas so sophisticated. His partner, Jason, has the ideas and people-person skills that gives Atlas the openess and fun that attracts its 50-plus members. So, from all of Atlas and those who follow it, thank you, Jason and Alex!

BRIEFS: Atlas celebrated its 50th member this month, a landmark achievement for a VA that is still newborn!

==Aircraft Review==
'''This month: B-25 Mitchell'''

[[Image:B-25.jpg|thumb|270px|A B-25 in the air near KATL]]
The [[B-25]] served in almost every theatre in World War II. From Europe to the Pacific, the Mitchell was there. One of the most famous missions accomplished by B-25s was the Doolittle Raid on Tokyo, when a group of 16 B-25s attacked the Japanese mainland, raising morale in the United States, and changing the priorities of the Imperial Japanese Navy, and possibly changing the direction of the war.

The flightgear model looks good on the outside. The author has done a lot of work on the textures, and this is improved even more by some excellent liveries made by Gooneybird that have been added to the B-25 base package by the author. The landing gear, engines and canopies are all carefully modelled, too.

The Cockpit is a little bit threadbare, with no chairs, two pilot figures, and the standard six instruments, which is more than enough to fly with. The only other issue I could come up with was the lack of weapons, but that is only an aesthetic problem. The B-25 handles nicely both on the ground and in the air. I can't talk about accuracy, however, as I have never flown in a B-25, so I don't know how it 'feels' in the air.

The Mitchell sounds great, too!

''Review by Armchair Ace''

==From the community==
===LinuxTAG===
Once again, a team of FlightGear enthusiasts operated a booth during the four days of this year's [http://www.linuxtag.org/ LinuxTAG], the most important place for Linux and open source software in Europe. Besides to it's main purpose of presenting FlightGear to a public audience, LinuxTag becomes more and more '''the''' place for a meeting of core FlightGear developers and users. A technical discussion between James, Alex and Matthias has the potential to become a ''FlightGear legend'' and will probably lead to a multithreaded processing within the simulator's core. Alex also held a public presentation about the integration of [http://www.linuxtag.org/2010/en/program/free-conference/all-events/details.html?talkid=329 "Android for pilots"] with fgfs. [http://www.linuxtag.org/2010/fileadmin/www.linuxtag.org/slides/Alex%20Perry%20-%20Android%20for%20Pilots%20-%20Integration%20with%20the%20FlightGear%20Flight%20Simulator.pdf]

An exciting first contact was initiated between FlightGear team members and a hardware vendor resulting in an idea to operate a shared presentation of powerful hardware running a powerful flight simulator at the next year's LinuxTAG - to proof the claim "where .com meets .org".

===FlightGear on YouTube===
* ''edubletooth'' captured a [http://www.youtube.com/watch?v=EeQUfnHLs_Q bunch of landings] at the airports with the world's most famous approach: [[Princess Juliana International Airport|Princess Juliana]] in the Netherlands Antilles. Make sure to bend when a 777-200 or maybe even a mighty [[Boeing 747|747]] is passing just meters over your head!
* [http://www.youtube.com/watch?v=nzCcqtkTUT8 This excellent video] proves that ''Howto'' Oscar (we already mentioned him last month) does more than creating howtos. Together with Don's extremely detailed simulation of Gatwick Airport (EGKK), Oscar's video angles make this an interesting and pleasant video to watch.

==And finally...==
===Your own Copilot===
How about having your own Copilot to help you fly your heavy metal? Imagine: You're at 3000 ft making a hand controlled descent to EGKK 26L in your [[Boeing 777-200|777-200ER]]: "flaps down"; check airspeed and altitude; you're now five miles out; "undercarriage down"; reduce speed a little more; "flaps down"; you seem to be slightly overspeed; "spoilers"; touch down "brakes" then "reverse thrust"; "flaps retract"; now take a look at the detailed scenery while taxying to your stand; "view" and "zoom out".

Those using Windows can employ '''Shoot''' - a free user-editable voice command utility. This may be used concurrently with FlightGear to recognize spoken words or phrases and carry out keyboard actions - including sequential or Shift/Alt/Ctrl... keying. Unfortunately Linux users do not have access to such a powerful utility.

[http://clans.gameclubcentral.com/shoot Download Shoot 1.6.4] and install it on your PC. You also need the Microsoft Speech API (SAPI) which is also free; the link is given on the Shoot website. The free Microsoft .NET should also be installed using the Shoot link.

Shoot may be edited to obey verbal commands such as "start engines", "maximum thrust", "undercarriage up", "flaps retract", "trim nose down", "deploy spoilers", "reverse thrust", "view exterior" - or whatever you choose. Try it and add more immersion to your flying.

===Did you know?===

* ...that FlightGear is made of roughly 3,000,000 lines of code and would cost more than $42,000,000 if created from scratch? <small>(Metrics from [http://www.ohloh.net/p/flightgear/analyses/latest ohloh.net])</small>

* ...that in version 2.0, fellow pilots' chat messages could be ignored on [[multiplayer]] by checking the ignore box in the pilot list?
For upcoming releases, pilots' aircraft will also be able to be ignored. This is part of a strong offensive against "trolling" that disrupts MP flying.<br>

* ...that the USS Nimitz [[Howto: Carrier|aircraft carrier]] has deck elevators that can be lowered/raised to go below deck?
Toggle them up/down in your ATC Options menu under Carrier; Check-Apply raises them, unchecked-apply lowers them.

[[Category:FlightGear Newsletter|2010 06]]

FGSignMaker

2010-06-27T03:06:39Z

Rsbrflyer: version 1.2.0

{{Infobox Software
| title = FGSignMaker
| logo =
| image = FGSignMaker_overview.png
| alt = Version 1.0.1
| developedby = skyop
| initialrelease = 0.5.0
| latestrelease = 1.2.0
| writtenin = (X)HTML/JavaScript
| os =
| platform = Cross-platform
| developmentstatus = Active (2010-)
| type =
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/forums/viewtopic.php?t=8596
}}
'''FGSignMaker''' is a (X)HTML/JavaScript-based (a.k.a. web-based) tool to generate [[Signs|taxiway sign]] codes for [[FlightGear]] licensed under the [[GNU General Public License]]. It can be used in conjunction with the [[UFO]] and your favorite plain text editor to add taxiway signs for FlightGear. The latest release available is version 1.0.1.

== Web browser compatibility ==
=== Known compatible browsers ===

FGSignMaker 1.0.1 is known to work well with the following web browsers:
* Internet Explorer 6 ('''not recommended''', due to JavaScript/CSS bugs and for just being a horrible browser in general)
* Internet Explorer 7
* Internet Explorer 8
* Mozilla Camino
* Mozilla Firefox 3.6
* Opera 9
* Safari

=== Most wanted ===
These browsers are "most wanted". If FGSignMaker works correctly under one of these browsers, please add them to the list above.
* Google Chrome

== Interface ==
=== Sign preview ===
[[File:FGSignMaker_signpreview.png|Sign preview]]

The sign preview, which updates automatically as you modify the sign code, gives you a rough (but fairly accurate) idea of how your sign will look when in FlightGear.

=== Sign code box ===
[[File:FGSignMaker_codebox.png|Sign code box]]

The sign code text box displays the actual code for the taxiway sign. You can insert glyphs here and type custom text. The "Select All" button selects all the text in this box and the "Clear" button deletes all the text ''without warning.''

=== Character counter and syntax checker ===
[[File:FGSignMaker_countersyntax.png|Character counter/syntax checker]]

The character counter (the "Character 15" in this screenshot) displays your cursor's position in the sign code box. It is mostly useful for debugging. The syntax checker is a basic, automatic tool that checks for misplaced braces ({ and }). It displays the position at which a misplaced brace was found.

=== Glyph inserter ===
[[File:FGSignMaker_glyphinserter.png|Glyph insertion tools]]

Last but certainly not least, the glyph inserter allows you to place predefined taxiway types and features. Currently it includes the four FAA-standard types implemented in FlightGear (L858-Y, L858-R, L858-L, L858-B), a line (vertical pipe |), and a no-entry sign.

== Placing taxiway signs ==
[[File:FGSignMaker_signfg-signmaker.png|250px|thumb|right|A taxiway sign in FlightGear (background) and in FGSignMaker (inset)]]
This tutorial explains how to add [[Signs|taxiway signs]] to FlightGear along with FGSignMaker. You are highly encouraged to add taxiway signs to your favorite airport, even if they are somewhat inaccurately placed.

=== Step 1: Launch FlightGear ===
[[File:FGSignMaker_tut1.png|400px|Step 1]]

First things first, we'll launch FlightGear in the [[UFO]] at the airport we will be working on (in this case [[KSFO]]). Here I will be using my fancy Linux terminal, but [[FlightGear Launch Control|FGRun]] will also suffice.

=== Step 2: Place taxiway sign(s) ===
[[File:FGSignMaker_tut2.png|830px|Step 2]]

With FlightGear loaded, fly the UFO to the location of the sign you want to place. Press the spacebar (or l-key) to bring up the model select dialog, choose <tt>[[$FGR_ROOT]]/Aircraft/ufo/Models/sign.ac</tt> and click where you want to place the new sign. Alt+Click the terrain to reposition the sign if need be. Press tab to bring up the adjustment dialog and use the heading slider and arrows to turn the sign. For more information on this process, see [[Howto: Place 3D objects with the UFO]].

=== Step 3: Build your sign in FGSignMaker ===
[[File:FGSignMaker_tut3.png|531px|Step 3]]

Now we create the actual taxiway sign code in FGSignMaker. In this case, a pilot looking at the sign would be on taxiway Delta, taxiway Charlie would be on the left, the end of runway 36L would be right in front, and the end of runway 18R would be on the right. To create this sign in FGSignMaker, we would:
# Click the L858-Y button
# Click the left arrow
# Type "C" into the sign code box
# Click the L858-L button
# Type "D" into the sign code box
# Click the L858-R button
# Type "36L-18R" into the sign code box
# Click the right arrow

=== Step 4: Add the sign into the *.stg file ===
Press the d-key to dump the export data to the command line or fgrun log window. You will see several lines similar to this example:

# w130n30/w123n37/942050.stg
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

------------------------------------------------------------------

As you add more signs and/or scenery objects, this output will grow. The latest object you placed is on the last line.

The most important piece of information we need right now is the *.stg file to edit. This is displayed in the comment (line with the hash # at the front).

# w130n30/w123n37/942050.stg

This tells us that the wanted *.stg file can be found at <tt>[[$FG_SCENERY]]/Objects/w130n30/w123n37/942050.stg</tt> - obviously, the path will vary depending on where you placed the sign.

Now open that *.stg file in your favorite plain text editor. Insert the desired OBJECT_SIGN line from the command line output from earlier, like so:

...
OBJECT_SIGN {@size=10,@material=RedSign}NO_CONTENTS_9072 -122.36162983 37.61539004 0.0118 0.0

Now replace the "{@size=10,@material=RedSign}NO_CONTENTS_[random number]" with the taxiway sign code you generated in step 3. Save the file.

=== Step 5: View your new sign(s) in FlightGear ===
[[File:FGSignMaker_signsinfg.png|300px|right|thumb|KBFL taxiway signs made with FGSignMaker]]
You won't immediately see your changes in FlightGear - you will have to restart the simulator. Once you do, you should be able to see the new taxiway signs.

== Submitting your work ==
If you are happy with your work, please submit it into the [[FlightGear Scenery Database]]. See [[FlightGear Scenery Database#Contributing_Positions|here]] for more details.

== To-do list ==

* Implement different sizes for signs
* Implement no-entry signs for the sign previewer
* Implement underscores, which are used in place of spaces

== External links ==
* [http://www.flightgear.org/forums/viewtopic.php?t=8596 Forum thread]
* [http://drop.io/cocu73e Download version 1.0.1]

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

FlightGear Newsletter June 2010

2010-06-24T15:27:27Z

Rsbrflyer: more news

{{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.''

==Development news==
===SquawkGear: Bringing VATSIM to FlightGear!===
{{Main article|SquawkGear}}
SquawkGear is the much-awaited client that allows FlightGear users to connect to the largest and most realistic sim server in the world: [http://vatsim.net/ VATSIM]. VATSIM is simply a network that can, in theory, take any sim, although the current ones are X-Plane and Microsoft Flight Simulator. Using addons like SquawkBox for MSFS, pilots must adhere to strict rules about realism. A valid [[flight plan]] must always be submitted before takeoff, for instance. And pilots must contact [[Air Traffic Control]] before any actions.

SquawkGear brings this wonderful server to FlightGear. While installation is not as simple as that of VATSIM clients for MSFS, pilots are now able to connect to the VATSIM network and use chat and voice to communicate with other players and ATC. Since [[scenery]] is very different between sims, aircraft do not always appear where they are supposed to be; a MSFS user might see you hovering a few feet above the ground, for instance.

With its first release, SquawkGear is an excellent addon for pilots wishing to get on VATSIM without having to buy the payware sims. It is strongly recommended that you '''read all manuals''' before connecting to VATSIM; not only because installation is tricky, but also because there are certain rules to be followed on VATSIM. You will find that your [[KSFO]] on VATSIM is a thousand times more under control than your KSFO on one of the [[Howto: Multiplayer|mpservers]]!

''Special thanks to Ivan (Reed) for all of his work!''

===Bombable air combat add-on updated===
The [http://www.flightgear.org/forums/viewtopic.php?f=2&t=5742 Bombable air combat add-on to FlightGear] received a major update in June. Bombable now has these features:

* Dogfight against other FlightGear pilots over multiplayer with Sopwith Camel, SPAC VII, Fokker DR 1 Triplane, or A6M2 Zero
* Explode/burn when you crash
* Exceeding aircraft limitations (excess g-forces, overspeed) adds damage to your aircraft and finally leads to shutdown/crash
* Shootable/bombable moving AI tanks, jeeps, ships, and aircraft that catch fire, burn, explode, sink, crash, etc.
* AI scenarios that allow you to use FlightGear aircraft for air-to-ground, air-to-sea, and air-to-air combat missions against these targets

==In the hangar==
===Boeing 787 and CRJ-200===
''nickyivyca'' is currently working on the [[Boeing 787]]. He corrected the [[FDM]] and changed some details in the model.
More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8203 in the forums].

He has also been working in the [[CRJ-200]]:

''"The CRJ-200 and 787 were made with very similar systems and such. Neither had a 2.0 compatible AP. So, I found out what was wrong with the one for the 787 first, and made those changes to the CRJ here. Both worked. I also did some FDM improvements, like moving the engines to where they really are and adding gear smoke and contrails."'' - says he [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8329 in the forum thread].

===Cessna T-37===
''richter'' and ''snipey'' are working together in improving the Cessna T-37. Here is a list of items that have been improved/created:

'''Model:'''
* Completely remodeled canopy;
* Main gear wheel wells and covers.
'''Sound:'''
* Interior-exterior sound level difference.
'''Instruments:'''
* Basic flight instruments.

More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8354 at the forum].

===CH-47 Chinook===
''MOJO'' is tuning the CH-47. He spent some time adding external cosmetics which main purpose is to add more detail to the Chinook. He added antenna and aerials, domed windows, pitot tubes, whinch, engine hub details and started with the internal cargo bay. He is going to be adding an animated refuel probe and will be doing some more liveries also, his main aim is to try and get the model more defined.

===Cirrus Vision SF50===
''Zexe'' created a SF50 model. It is still at a very early stage. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8352 here].

===MiG-15bis===
''vitos'' improved the MiG-15bis model, and released it. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7486 here].

===MB-339 PAN===
The MB-339 PAN aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8604 was updated by ''Albert''] to work with [[FlightGear]] version 2.0.0.

===Curtiss P-40 Warhawk===
''jackmermod'' [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8621 is developing a P-40 model]. It is already complete, and to be done are the animations and textures.

===X-29A===
''Intel-Qube'' [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8485 is currently revamping] the experimental X-29A aircraft. Here is a list of items that have been improved/created:

* A new, more realistic [[FDM]] is on the way;
* Landing gear has been redone and is now much more aesthetically pleasing;
* New exhaust will now dilate based on throttle as it should;
* The cockpit panel has been entirely rebuilt, is far more detailed, and will likely have interactive switches in the final release;
* The model is more ''"anatomically correct"''.

===Il-96-400/T===
The Il-96-400/T [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7439 has been updated] to version 3, with more accurate model and a better panel, among other little fixes.

===San Antonio LPD17===
Browsing through the files, ''HHS'' [http://www.flightgear.org/forums/viewtopic.php?f=23&t=8351 found a rotorcraft carrier model] and made a scenario to run it, which is available on [[Git]].

==Scenery corner==
===Nighttime London Gatwick===
London Gatwick (EGKK) is being further improved and is in the second phase of development - night textures. All the buildings and features are currently being modified by ''karla'' to give suitable lighting and make London Gatwick even more attractive to FlightGear commercial flyers. Landing or taking off from Gatwick at night should add much to your enjoyment of the game - and most likely extend the hours you enter in your pilot's log.
Further improvements and many minor changes are also being made to the existing models and daytime textures.
The link shows an image of the part completed airport at night http://www.donlavelle.net/flightgear/flightgear19.html.

The new scenery will be released early in July.

===Dubai airport gets busy===
With the terrain updates that were discussed in the [[FlightGear Newsletter March 2010#Dubai is coming up|March edition]] still in our minds, we now have another feature for the area; taking it yet another step closer to a bussy and realistic representation of the real emirate!

After looking jealously at the greatly enhanced airport [[Amsterdam Airport Schiphol|Schiphol]] (EHAM) and the latest highlight Gatwick (EGKK) Mike ([[User:D-SKY1|D-SKY1]]) decided to create [[Interactive_Traffic|interactive traffic]] for [[Dubai International Airport]] (OMDB). Based on the existing airport layout in FlightGear the traffic pattern for taxiing between gates and runways has been created in [[TaxiDraw]] next to a timetable for runway usage.

Although no modelwork is done (yet) a big bunch of scheduled flights is now added to this important hub in the middle east. As Dubai is home port for Emirates Airlines (UAE) only Emirates flights are included. Within the next weeks more scheduled flights for AI traffic at Dubai will be added. During the process of creating AI traffic he tried to stay as close as possible to the real life timetable for Dubai International Airport querying several sources for double checking.

As Emirates Airlines (UAE) is one of the most important customers for the [[Airbus A380]] (UAE just ordered another 30 units of A380) the Emirates Airlines livery has been added to AI aircrafts A380. Additionally some minor errors in several traffic files concerning changed [[ICAO]] codes for some airports have been removed.

All changes are available via [[Git]]. Enjoy the enhancements; and always follow [[SID]]s and [[STAR]]s to prevent collisions.

===Meadows Field and FGSignMaker===
''skyop'' released his improvements to the Meadows Field (KBFL) scenery. Read [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8466 this topic] for more information.

He is also writing [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8596 FGSignMaker], a tool to generate taxiway sign codes written in JavaScript. As of 2010-06-22, version 1.0.0 stable has been released. More information on taxiway signs can be found [[Signs|here]].

===Landcover additions===
Connecticut, Oshkosh (Wisconsin, USA) and the Toronto Harbor have been added to the FlightGear mapserver. They will be released to the public with the next scenery build, or alternatively the shapefiles can be downloaded and compiled by the user.

This is in addition to the other numerous improvements to the land cover which are pending with the next scenery release, which includes (but is not limited to) France; Madrid, Spain; London, England; Bonn, Germany; Western Washington, USA; Northwest Oregon, USA; Phoenix, Arizona, USA; Washington, DC, and Baltimore, Maryland, USA; Rhode Island; Hawaii; and Long Island, New York, USA.

Land cover development is ongoing.

==Multiplayer News==
===Atlas Virtual Airlines' leaders recognised!===
[[Atlas Virtual Airlines]], FlightGear's most populated airline, has been a hit success in its inaugural months since opening in mid-April. The airline, however, couldn't have made it without the guidance of its two current leaders: ''MaverickAlex'' (Alex Park) and ''SkyWlf77'' (Jason Sheperd). Besides sinking their own cash into the airline for site domain and software, these two founding members have sorted out many mis-judgements of Atlas and helped to form a strong and community-bonding airline. Jason, the vice-chairman and moderator, helped revamp AVA's standing on the forums and turned many former anti-Atlas-ers into supporting members, which has been very beneficial for the FlightGear multiplayer community. Thanks to him, members can now feel confident to join an airline that was, just months ago, in the midst of intense controversy. Sheperd has taken a strong stand against arguments and flame wars on the Forums, intent on preventing the locked-topics and arguing members that degraded the VA Community during the VA "Dark Ages". But now, Atlas has flourised into a friendship-filled and happy organization that members find enjoyment and fun in.

Meanwhile, Alex, the current chairman and administrator, independently designed an awesome and top-of-the-line VA website for Atlas pilots. He has also worked with nightmares of coding to get drawing-board ideas implemented. And on top of it all, Alex is finishing up his Bombardier Dash-8 400Q, designed especially for Atlas Express flights. This very nicely modeled aircraft will also be available to the public, underlining how Atlas Virtual Airlines is really benefiting all of FlightGear. Alex is the brains behind it all that makes Atlas so sophisticated. His partner, Jason, has the ideas and people-person skills that gives Atlas the openess and fun that attracts its 50-plus members. So, from all of Atlas and those who follow it, thank you, Jason and Alex!

BRIEFS: Atlas celebrated its 50th member this month, a landmark achievement for a VA that is still newborn!

==Aircraft Review==
'''This month: B-25 Mitchell'''

[[Image:B-25.jpg|thumb|270px|A B-25 in the air near KATL]]
The [[B-25]] served in almost every theatre in World War II. From Europe to the Pacific, the Mitchell was there. One of the most famous missions accomplished by B-25s was the Doolittle Raid on Tokyo, when a group of 16 B-25s attacked the Japanese mainland, raising morale in the United States, and changing the priorities of the Imperial Japanese Navy, and possibly changing the direction of the war.

The flightgear model looks good on the outside. The author has done a lot of work on the textures, and this is improved even more by some excellent liveries made by Gooneybird that have been added to the B-25 base package by the author. The landing gear, engines and canopies are all carefully modelled, too.

The Cockpit is a little bit threadbare, with no chairs, two pilot figures, and the standard six instruments, which is more than enough to fly with. The only other issue I could come up with was the lack of weapons, but that is only an aesthetic problem. The B-25 handles nicely both on the ground and in the air. I can't talk about accuracy, however, as I have never flown in a B-25, so I don't know how it 'feels' in the air.

The Mitchell sounds great, too!

''Review by Armchair Ace''

==From the community==
===LinuxTAG===
Once again, a team of FlightGear enthusiasts operated a booth during the four days of this year's [http://www.linuxtag.org/ LinuxTAG], the most important place for Linux and open source software in Europe. Besides to it's main purpose of presenting FlightGear to a public audience, LinuxTag becomes more and more '''the''' place for a meeting of core FlightGear developers and users. A technical discussion between James, Alex and Matthias has the potential to become a ''FlightGear legend'' and will probably lead to a multithreaded processing within the simulator's core. Alex also held a public presentation about the integration of [http://www.linuxtag.org/2010/en/program/free-conference/all-events/details.html?talkid=329 "Android for pilots"] with fgfs. [http://www.linuxtag.org/2010/fileadmin/www.linuxtag.org/slides/Alex%20Perry%20-%20Android%20for%20Pilots%20-%20Integration%20with%20the%20FlightGear%20Flight%20Simulator.pdf]

An exciting first contact was initiated between FlightGear team members and a hardware vendor resulting in an idea to operate a shared presentation of powerful hardware running a powerful flight simulator at the next year's LinuxTAG - to proof the claim "where .com meets .org".

===FlightGear on YouTube===
* ''edubletooth'' captured a [http://www.youtube.com/watch?v=EeQUfnHLs_Q bunch of landings] at the airports with the world's most famous approach: [[Princess Juliana International Airport|Princess Juliana]] in the Netherlands Antilles. Make sure to bend when a 777-200 or maybe even a mighty [[Boeing 747|747]] is passing just meters over your head!
* [http://www.youtube.com/watch?v=nzCcqtkTUT8 This excellent video] proves that ''Howto'' Oscar (we already mentioned him last month) does more than creating howtos. Together with Don's extremely detailed simulation of Gatwick Airport (EGKK), Oscar's video angles make this an interesting and pleasant video to watch.

==And finally...==
===Your own Copilot===
How about having your own Copilot to help you fly your heavy metal? Imagine: You're at 3000 ft making a hand controlled descent to EGKK 26L in your [[Boeing 777-200|777-200ER]]: "flaps down"; check airspeed and altitude; you're now five miles out; "undercarriage down"; reduce speed a little more; "flaps down"; you seem to be slightly overspeed; "spoilers"; touch down "brakes" then "reverse thrust"; "flaps retract"; now take a look at the detailed scenery while taxying to your stand; "view" and "zoom out".

Those using Windows can employ '''Shoot''' - a free user-editable voice command utility. This may be used concurrently with FlightGear to recognize spoken words or phrases and carry out keyboard actions - including sequential or Shift/Alt/Ctrl... keying. Unfortunately Linux users do not have access to such a powerful utility.

[http://clans.gameclubcentral.com/shoot Download Shoot 1.6.4] and install it on your PC. You also need the Microsoft Speech API (SAPI) which is also free; the link is given on the Shoot website. The free Microsoft .NET should also be installed using the Shoot link.

Shoot may be edited to obey verbal commands such as "start engines", "maximum thrust", "undercarriage up", "flaps retract", "trim nose down", "deploy spoilers", "reverse thrust", "view exterior" - or whatever you choose. Try it and add more immersion to your flying.

[[Category:FlightGear Newsletter|2010 06]]

===Did you know?===

* ...that in version 2.0, fellow pilots' chat messages could be ignored on [[multiplayer]] by checking the ignore box in the pilot list?
For upcoming releases, pilots' aircraft will also be able to be ignored. This is part of a strong offensive against "trolling" that disrupts MP flying.<br>

* ...that the USS Nimitz [[Howto: Carrier|aircraft carrier]] has deck elevators that can be lowered/raised to go below deck?
Toggle them up/down in your ATC Options menu under Carrier; Check-Apply raises them, unchecked-apply lowers them.

* ...that FlightGear is made of roughly 3,000,000 lines of code and would cost more than $42,000,000 if created from scratch? <small>(Metrics from [http://www.ohloh.net/p/flightgear/analyses/latest ohloh.net])</small>

FlightGear Newsletter June 2010

2010-06-22T17:29:08Z

Rsbrflyer: news, news, news!

{{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.''

==Development news==
===SquawkGear: Bringing VATSIM to FlightGear!===
{{Main article|SquawkGear}}
SquawkGear is the much-awaited client that allows FlightGear users to connect to the largest and most realistic sim server in the world: [http://vatsim.net/ VATSIM]. VATSIM is simply a network that can, in theory, take any sim, although the current ones are X-Plane and Microsoft Flight Simulator. Using addons like SquawkBox for MSFS, pilots must adhere to strict rules about realism. A valid [[flight plan]] must always be submitted before takeoff, for instance. And pilots must contact [[Air Traffic Control]] before any actions.

SquawkGear brings this wonderful server to FlightGear. While installation is not as simple as that of VATSIM clients for MSFS, pilots are now able to connect to the VATSIM network and use chat and voice to communicate with other players and ATC. Since [[scenery]] is very different between sims, aircraft do not always appear where they are supposed to be; a MSFS user might see you hovering a few feet above the ground, for instance.

With its first release, SquawkGear is an excellent addon for pilots wishing to get on VATSIM without having to buy the payware sims. It is strongly recommended that you '''read all manuals''' before connecting to VATSIM; not only because installation is tricky, but also because there are certain rules to be followed on VATSIM. You will find that your [[KSFO]] on VATSIM is a thousand times more under control than your KSFO on one of the [[Howto: Multiplayer|mpservers]]!

''Special thanks to Ivan (Reed) for all of his work!''

===Bombable air combat add-on updated===
The [http://www.flightgear.org/forums/viewtopic.php?f=2&t=5742 Bombable air combat add-on to FlightGear] received a major update in June. Bombable now has these features:

* Dogfight against other FlightGear pilots over multiplayer with Sopwith Camel, SPAC VII, Fokker DR 1 Triplane, or A6M2 Zero
* Explode/burn when you crash
* Exceeding aircraft limitations (excess g-forces, overspeed) adds damage to your aircraft and finally leads to shutdown/crash
* Shootable/bombable moving AI tanks, jeeps, ships, and aircraft that catch fire, burn, explode, sink, crash, etc.
* AI scenarios that allow you to use FlightGear aircraft for air-to-ground, air-to-sea, and air-to-air combat missions against these targets

==In the hangar==
===Boeing 787 and CRJ-200===
''nickyivyca'' is currently working on the [[Boeing 787]]. He corrected the [[FDM]] and changed some details in the model.
More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8203 in the forums].

He has also been working in the [[CRJ-200]]:

''"The CRJ-200 and 787 were made with very similar systems and such. Neither had a 2.0 compatible AP. So, I found out what was wrong with the one for the 787 first, and made those changes to the CRJ here. Both worked. I also did some FDM improvements, like moving the engines to where they really are and adding gear smoke and contrails."'' - says he [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8329 in the forum thread].

===Cessna T-37===
''richter'' and ''snipey'' are working together in improving the Cessna T-37. Items that have been improved/created:

'''Model:'''
* Completely remodeled canopy;
* Main gear wheel wells and covers.
'''Sound:'''
* Interior-exterior sound level difference.
'''Instruments:'''
* Basic flight instruments.

More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8354 at the forum].

===CH-47 Chinook===
''MOJO'' is tuning the CH-47. He spent some time adding external cosmetics which main purpose is to add more detail to the Chinook. He added antenna and aerials, domed windows, pitot tubes, whinch, engine hub details and started with the internal cargo bay. He is going to be adding an animated refuel probe and will be doing some more liveries also, his main aim is to try and get the model more defined.

===Cirrus Vision SF50===
''Zexe'' created a SF50 model. It is still at a very early stage. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8352 here].

===MiG-15bis===
''vitos'' improved the MiG-15bis model, and released it. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7486 here].

===MB-339 PAN===
The MB-339 PAN aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8604 was updated by ''Albert''] to work with [[FlightGear]] version 2.0.0.

===San Antonio LPD17===
Browsing through the files, ''HHS'' [http://www.flightgear.org/forums/viewtopic.php?f=23&t=8351 found a rotorcraft carrier model] and made a scenario to run it, which is available on [[Git]].

==Scenery corner==
===Nighttime London Gatwick===
London Gatwick (EGKK) is being further improved and is in the second phase of development - night textures. All the buildings and features are currently being modified by ''karla'' to give suitable lighting and make London Gatwick even more attractive to FlightGear commercial flyers. Landing or taking off from Gatwick at night should add much to your enjoyment of the game - and most likely extend the hours you enter in your pilot's log.
Further improvements and many minor changes are also being made to the existing models and daytime textures.
The link shows an image of the part completed airport at night http://www.donlavelle.net/flightgear/flightgear19.html.

The new scenery will be released early in July.

===Dubai airport gets busy===
With the terrain updates that were discussed in the [[FlightGear Newsletter March 2010#Dubai is coming up|March edition]] still in our minds, we now have another feature for the area; taking it yet another step closer to a bussy and realistic representation of the real emirate!

After looking jealously at the greatly enhanced airport [[Amsterdam Airport Schiphol|Schiphol]] (EHAM) and the latest highlight Gatwick (EGKK) Mike ([[User:D-SKY1|D-SKY1]]) decided to create [[Interactive_Traffic|interactive traffic]] for [[Dubai International Airport]] (OMDB). Based on the existing airport layout in FlightGear the traffic pattern for taxiing between gates and runways has been created in [[TaxiDraw]] next to a timetable for runway usage.

Although no modelwork is done (yet) a big bunch of scheduled flights is now added to this important hub in the middle east. As Dubai is home port for Emirates Airlines (UAE) only Emirates flights are included. Within the next weeks more scheduled flights for AI traffic at Dubai will be added. During the process of creating AI traffic he tried to stay as close as possible to the real life timetable for Dubai International Airport querying several sources for double checking.

As Emirates Airlines (UAE) is one of the most important customers for the [[Airbus A380]] (UAE just ordered another 30 units of A380) the Emirates Airlines livery has been added to AI aircrafts A380. Additionally some minor errors in several traffic files concerning changed [[ICAO]] codes for some airports have been removed.

All changes are available via [[Git]]. Enjoy the enhancements; and always follow [[SID]]s and [[STAR]]s to prevent collisions.

===Meadows Field and FGSignMaker===
''skyop'' released his improvements to the Meadows Field (KBFL) scenery. Read [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8466 this topic] for more information.

He is also writing [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8596 FGSignMaker], a tool to generate taxiway sign codes wrote in JavaScript. It is still in alpha version as of 2010-06-22, but should be soon released.

==Multiplayer News==
===Atlas Virtual Airlines' leaders recognised!===
[[Atlas Virtual Airlines]], FlightGear's most populated airline, has been a hit success in its inaugural months since opening in mid-April. The airline, however, couldn't have made it without the guidance of its two current leaders: ''MaverickAlex'' (Alex Park) and ''SkyWlf77'' (Jason Sheperd). Besides sinking their own cash into the airline for site domain and software, these two founding members have sorted out many mis-judgements of Atlas and helped to form a strong and community-bonding airline. Jason, the vice-chairman and moderator, helped revamp AVA's standing on the forums and turned many former anti-Atlas-ers into supporting members, which has been very beneficial for the FlightGear multiplayer community. Thanks to him, members can now feel confident to join an airline that was, just months ago, in the midst of intense controversy. Sheperd has taken a strong stand against arguments and flame wars on the Forums, intent on preventing the locked-topics and arguing members that degraded the VA Community during the VA "Dark Ages". But now, Atlas has flourised into a friendship-filled and happy organization that members find enjoyment and fun in.

Meanwhile, Alex, the current chairman and administrator, independently designed an awesome and top-of-the-line VA website for Atlas pilots. He has also worked with nightmares of coding to get drawing-board ideas implemented. And on top of it all, Alex is finishing up his Bombardier Dash-8 400Q, designed especially for Atlas Express flights. This very nicely modeled aircraft will also be available to the public, underlining how Atlas Virtual Airlines is really benefiting all of FlightGear. Alex is the brains behind it all that makes Atlas so sophisticated. His partner, Jason, has the ideas and people-person skills that gives Atlas the openess and fun that attracts its 50-plus members. So, from all of Atlas and those who follow it, thank you, Jason and Alex!

BRIEFS: Atlas celebrated its 50th member this month, a landmark achievement for a VA that is still newborn!

==Aircraft Review==
'''This month: B-25 Mitchell'''

[[Image:B-25.jpg|thumb|270px|A B-25 in the air near KATL]]
The [[B-25]] served in almost every theatre in World War II. From Europe to the Pacific, the Mitchell was there. One of the most famous missions accomplished by B-25s was the Doolittle Raid on Tokyo, when a group of 16 B-25s attacked the Japanese mainland, raising morale in the United States, and changing the priorities of the Imperial Japanese Navy, and possibly changing the direction of the war.

The flightgear model looks good on the outside. The author has done a lot of work on the textures, and this is improved even more by some excellent liveries made by Gooneybird that have been added to the B-25 base package by the author. The landing gear, engines and canopies are all carefully modelled, too.

The Cockpit is a little bit threadbare, with no chairs, two pilot figures, and the standard six instruments, which is more than enough to fly with. The only other issue I could come up with was the lack of weapons, but that is only an aesthetic problem. The B-25 handles nicely both on the ground and in the air. I can't talk about accuracy, however, as I have never flown in a B-25, so I don't know how it 'feels' in the air.

The Mitchell sounds great, too!

''Review by Armchair Ace''

==From the community==
===Linuxtag===

===FlightGear on YouTube===
* ''edubletooth'' captured a [http://www.youtube.com/watch?v=EeQUfnHLs_Q bunch of landings] at the airports with the world's most famous approach: [[Princess Juliana International Airport|Princess Juliana]] in the Netherlands Antilles. Make sure to bend when a 777-200 or maybe even a mighty [[Boeing 747|747]] is passing just meters over your head!
* [http://www.youtube.com/watch?v=nzCcqtkTUT8 This excellent video] proves that ''Howto'' Oscar (we already mentioned him last month) does more than creating howtos. Together with Don's extremely detailed simulation of Gatwick Airport (EGKK), Oscar's video angles make this an interesting and pleasant video to watch.

==And finally...==
===Your own Copilot===
How about having your own Copilot to help you fly your heavy metal? Imagine: You're at 3000 ft making a hand controlled descent to EGKK 26L in your [[Boeing 777-200|777-200ER]]: "flaps down"; check airspeed and altitude; you're now five miles out; "undercarriage down"; reduce speed a little more; "flaps down"; you seem to be slightly overspeed; "spoilers"; touch down "brakes" then "reverse thrust"; "flaps retract"; now take a look at the detailed scenery while taxying to your stand; "view" and "zoom out".

Those using Windows can employ '''Shoot''' - a free user-editable voice command utility. This may be used concurrently with FlightGear to recognize spoken words or phrases and carry out keyboard actions - including sequential or Shift/Alt/Ctrl... keying. Unfortunately Linux users do not have access to such a powerful utility.

[http://clans.gameclubcentral.com/shoot Download Shoot 1.6.4] and install it on your PC. You also need the Microsoft Speech API (SAPI) which is also free; the link is given on the Shoot website. The free Microsoft .NET should also be installed using the Shoot link.

Shoot may be edited to obey verbal commands such as "start engines", "maximum thrust", "undercarriage up", "flaps retract", "trim nose down", "deploy spoilers", "reverse thrust", "view exterior" - or whatever you choose. Try it and add more immersion to your flying.

[[Category:FlightGear Newsletter|2010 06]]

===Did you know?===

* ...that in version 2.0, fellow pilots' chat messages could be ignored on [[multiplayer]] by checking the ignore box in the pilot list?
For upcoming releases, pilots' aircraft will also be able to be ignored. This is part of a strong offensive against "trolling" that disrupts MP flying.<br>

* ...that the USS Nimitz [[Howto: Carrier|aircraft carrier]] has deck elevators that can be lowered/raised to go below deck?
Toggle them up/down in your ATC Options menu under Carrier; Check-Apply raises them, unchecked-apply lowers them.

Fgcom

2010-06-21T21:11:21Z

Rsbrflyer: Redirected page to FGCom

#REDIRECT[[FGCom]]

FlightGear Newsletter June 2010

2010-06-20T18:11:56Z

Rsbrflyer: some corrections

{{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.''

==Development news==
===SquawkGear: Bringing VATsim to FlightGear!===
{{Main article|SquawkGear}}
SquawkGear is the much-awaited client that allows FlightGear users to connect to the largest and most realistic sim server in the world: [http://vatsim.net/ VATsim]. VATsim is simply a network that can, in theory, take any sim, although the current ones are X-Plane and Microsoft Flight Simulator. Using addons like SquawkBox for MSFS, pilots must adhere to strict rules about realism. A valid [[flight plan]] must always be submitted before takeoff, for instance. And pilots must contact [[Air Traffic Control]] before any actions.

SquawkGear brings this wonderful server to FlightGear. While installation is not as simple as that of VATsim clients for MSFS, pilots are now able to connect to the VATsim network and use chat and voice to communicate with other players and ATC. Since [[scenery]] is very different between sims, aircraft do not always appear where they are supposed to be; a MSFS user might see you hovering a few feet above the ground, for instance.

With its first release, SquawkGear is an excellent addon for pilots wishing to get on VATsim without having to buy the payware sims. It is strongly recommended that you '''read all manuals''' before connecting to VATsim; not only because installation is tricky, but also because there are certain rules to be followed on VATsim. You will find that your [[KSFO]] on VATsim is a thousand times more under control than your KSFO on one of the [[Howto: Multiplayer|mpservers]]!

Special thanks to Ivan (Reed) for all of his work!

===Bombable air combat add-on updated===
The [http://www.flightgear.org/forums/viewtopic.php?f=2&t=5742 Bombable air combat add-on to FlightGear] received a major update in June. Bombable now has these features:

* Dogfight against other FlightGear pilots over multiplayer with Sopwith Camel, SPAC VII, Fokker DR 1 Triplane, or A6M2 Zero
* Explode/burn when you crash
* Exceeding aircraft limitations (excess g-forces, overspeed) adds damage to your aircraft and finally leads to shutdown/crash
* Shootable/bombable moving AI tanks, jeeps, ships, and aircraft that catch fire, burn, explode, sink, crash, etc.
* AI scenarios that allow you to use FlightGear aircraft for air-to-ground, air-to-sea, and air-to-air combat missions against these targets

==In the hangar==
===Boeing 787 and CRJ-200===
''nickyivyca'' is currently working on the [[Boeing 787]]. He corrected the [[FDM]] and changed some details in the model.
More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8203 in the forums].

He has also been working in the [[CRJ-200]]:

''"The CRJ-200 and 787 were made with very similar systems and such. Neither had a 2.0 compatible AP. So, I found out what was wrong with the one for the 787 first, and made those changes to the CRJ here. Both worked. I also did some FDM improvements, like moving the engines to where they really are and adding gear smoke and contrails."'' - says he [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8329 in the forum thread].

===Cessna T-37===
''richter'' and ''snipey'' are working together in improving the Cessna T-37. Items that have been improved/created:

'''Model:'''
* Completely remodeled canopy;
* Main gear wheel wells and covers.
'''Sound:'''
* Interior-exterior sound level difference.
'''Instruments:'''
* Basic flight instruments.

More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8354 at the forum].

===CH-47 Chinook===
''MOJO'' is tuning the CH-47. He spent some time adding external cosmetics which main purpose is to add more detail to the Chinook. He added antenna and aerials, domed windows, pitot tubes, whinch, engine hub details and started with the internal cargo bay. He is going to be adding an animated refuel probe and will be doing some more liveries also, his main aim is to try and get the model more defined.

===Cirrus Vision SF50===
''Zexe'' created a SF50 model. It is still at a very early stage. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8352 here].

===MiG-15bis===
''vitos'' improved the MiG-15bis model, and released it. More information [http://www.flightgear.org/forums/viewtopic.php?f=4&t=7486 here].

===San Antonio LPD17===
Browsing through the files, ''HHS'' [http://www.flightgear.org/forums/viewtopic.php?f=23&t=8351 found a rotorcraft carrier model] and made a scenario to run it, which is available on [[Git]].

==Scenery corner==
===Nighttime London Gatwick===
London Gatwick (EGKK) is being further improved and is in the second phase of development - night textures. All the buildings and features are currently being modified by ''karla'' to give suitable lighting and make London Gatwick even more attractive to FlightGear commercial flyers. Landing or taking off from Gatwick at night should add much to your enjoyment of the game - and most likely extend the hours you enter in your pilot's log.
Further improvements and many minor changes are also being made to the existing models and daytime textures.
The link shows an image of the part completed airport at night http://www.donlavelle.net/flightgear/flightgear19.html.

The new scenery will be released early in July.

===Dubai airport gets busy===
With the terrain updates that were discussed in the [[FlightGear Newsletter March 2010#Dubai is coming up|March edition]] still in our minds, we now have another feature for the area; taking it yet another step closer to a bussy and realistic representation of the real emirate!

After looking jealously at the greatly enhanced airport [[Amsterdam Airport Schiphol|Schiphol]] (EHAM) and the latest highlight Gatwick (EGKK) Mike ([[User:D-SKY1|D-SKY1]]) decided to create [[Interactive_Traffic|interactive traffic]] for [[Dubai International Airport]] (OMDB). Based on the existing airport layout in FlightGear the traffic pattern for taxiing between gates and runways has been created in [[TaxiDraw]] next to a timetable for runway usage.

Although no modelwork is done (yet) a big bunch of scheduled flights is now added to this important hub in the middle east. As Dubai is home port for Emirates Airlines (UAE) only Emirates flights are included. Within the next weeks more scheduled flights for AI traffic at Dubai will be added. During the process of creating AI traffic he tried to stay as close as possible to the real life timetable for Dubai International Airport querying several sources for double checking.

As Emirates Airlines (UAE) is one of the most important customers for the [[Airbus A380]] (UAE just ordered another 30 units of A380) the Emirates Airlines livery has been added to AI aircrafts A380. Additionally some minor errors in several traffic files concerning changed [[ICAO]] codes for some airports have been removed.

All changes are available via [[Git]]. Enjoy the enhancements; and always follow [[SID]]s and [[STAR]]s to prevent collisions ;)

==Multiplayer News==
===Atlas Virtual Airlines' leaders recognised!===
[[Atlas Virtual Airlines]], FlightGear's most populated airline, has been a hit success in its inaugural months since opening in mid-April. The airline, however, couldn't have made it without the guidance of its two current leaders: ''MaverickAlex'' (Alex Park) and ''SkyWlf77'' (Jason Sheperd). Besides sinking their own cash into the airline for site domain and software, these two founding members have sorted out many mis-judgements of Atlas and helped to form a strong and community-bonding airline. Jason, the vice-chairman and moderator, helped revamp AVA's standing on the forums and turned many former anti-Atlas-ers into supporting members, which has been very beneficial for the FlightGear multiplayer community. Thanks to him, members can now feel confident to join an airline that was, just months ago, in the midst of intense controversy. Sheperd has taken a strong stand against arguments and flame wars on the Forums, intent on preventing the locked-topics and arguing members that degraded the VA Community during the VA "Dark Ages". But now, Atlas has flourised into a friendship-filled and happy organization that members find enjoyment and fun in.

Meanwhile, Alex, the current chairman and administrator, independently designed an awesome and top-of-the-line VA website for Atlas pilots. He has also worked with nightmares of coding to get drawing-board ideas implemented. And on top of it all, Alex is finishing up his Bombardier Dash-8 400Q, designed especially for Atlas Express flights. This very nicely modeled aircraft will also be available to the public, underlining how Atlas Virtual Airlines is really benefiting all of FlightGear. Alex is the brains behind it all that makes Atlas so sophisticated. His partner, Jason, has the ideas and people-person skills that gives Atlas the openess and fun that attracts its 50-plus members. So, from all of Atlas and those who follow it, thank you, Jason and Alex!

BRIEFS: Atlas celebrated its 50th member this month, a landmark achievement for a VA that is still newborn!

==Aircraft Review==
'''This month: B-25 Mitchell'''

[[Image:B-25.jpg|thumb|270px|A B-25 in the air near KATL]]
The [[B-25]] served in almost every theatre in World War II. From Europe to the Pacific, the Mitchell was there. One of the most famous missions accomplished by B-25s was the Doolittle Raid on Tokyo, when a group of 16 B-25s attacked the Japanese mainland, raising morale in the United States, and changing the priorities of the Imperial Japanese Navy, and possibly changing the direction of the war.

The flightgear model looks good on the outside. The author has done a lot of work on the textures, and this is improved even more by some excellent liveries made by Gooneybird that have been added to the B-25 base package by the author. The landing gear, engines and canopies are all carefully modelled, too.

The Cockpit is a little bit threadbare, with no chairs, two pilot figures, and the standard six instruments, which is more than enough to fly with. The only other issue I could come up with was the lack of weapons, but that is only an aesthetic problem. The B-25 handles nicely both on the ground and in the air. I can't talk about accuracy, however, as I have never flown in a B-25, so I don't know how it 'feels' in the air.

The Mitchell sounds great, too!

''Review by Armchair Ace''

==From the community==
===Linuxtag===

===FlightGear on YouTube===
* ''edubletooth'' captured a [http://www.youtube.com/watch?v=EeQUfnHLs_Q bunch of landings] at the airports with the world's most famous approach: [[Princess Juliana International Airport|Princess Juliana]] in the Netherlands Antilles. Make sure to bend when a 777-200 or maybe even a mighty [[Boeing 747|747]] is passing just meters over your head!
* [http://www.youtube.com/watch?v=nzCcqtkTUT8 This excellent video] proves that ''Howto'' Oscar (we already mentioned him last month) does more than creating howtos. Together with Don's extremely detailed simulation of Gatwick Airport (EGKK), Oscar's video angles make this an interesting and pleasant video to watch.

==And finally...==
===Your own Copilot===
How about having your own Copilot to help you fly your heavy metal? Imagine: You're at 3000 ft making a hand controlled descent to EGKK 26L in your [[Boeing 777-200|777-200ER]]: "flaps down"; check airspeed and altitude; you're now five miles out; "undercarriage down"; reduce speed a little more; "flaps down"; you seem to be slightly overspeed; "spoilers"; touch down "brakes" then "reverse thrust"; "flaps retract"; now take a look at the detailed scenery while taxying to your stand; "view" and "zoom out".

Those using Windows can employ '''Shoot''' - a free user-editable voice command utility. This may be used concurrently with FlightGear to recognize spoken words or phrases and carry out keyboard actions - including sequential or Shift/Alt/Ctrl... keying. Unfortunately Linux users do not have access to such a powerful utility.

[http://clans.gameclubcentral.com/shoot Download Shoot 1.6.4] and install it on your PC. You also need the Microsoft Speech API (SAPI) which is also free; the link is given on the Shoot website. The free Microsoft .NET should also be installed using the Shoot link.

Shoot may be edited to obey verbal commands such as "start engines", "maximum thrust", "undercarriage up", "flaps retract", "trim nose down", "deploy spoilers", "reverse thrust", "view exterior" - or whatever you choose. Try it and add more immersion to your flying.

[[Category:FlightGear Newsletter|2010 06]]

===Did you know?===

* ...that in version 2.0, fellow pilots' chat messages could be ignored on [[multiplayer]] by checking the ignore box in the pilot list?
For upcoming releases, pilots' aircraft will also be able to be ignored. This is part of a strong offensive against "trolling" that disrupts MP flying.<br>

* ...that the USS Nimitz [[Howto: Carrier|aircraft carrier]] has deck elevators that can be lowered/raised to go below deck?
Toggle them up/down in your ATC Options menu under Carrier; Check-Apply raises them, unchecked-apply lowers them.

Pt/Página principal

2010-06-18T23:34:19Z

Rsbrflyer: fixing a template

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:100%; color:#000"|


{| style="width:100%; border:solid 0px; background:none;"
|style="width:100%; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Bem-vindo à Wiki do FlightGear!</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">nós temos [[Special:Statistics|{{NUMBEROFARTICLES}}]] artigos.</div>

[[file:de.gif|link=:de:Hauptseite]]
[[file:en.gif|link=:en:Main Page]]
[[file:es.gif|link=:es:Portada]]
[[file:fi.gif|link=:fi:Etusivu]]
[[file:fr.gif|link=:fr:Accueil]]
[[file:nl.gif|link=:nl:Hoofdpagina]]
[[file:pl.gif|link=:pl:Strona główna]]
[[file:pt.gif|link=:pt:Página principal]]
[[file:ru.gif|link=:ru:Заглавная страница]]
[[file:zh.gif|link=:zh:Main Page]]
|}


|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[Help:Tutorial|Editing]] '''·''' [[Help:Contents|Help]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|All pages]] '''·''' [[Special:Search|Search]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Simulador de Vôo FlightGear</h2>
|-
|style="color:#000;"|
[[Image:FGlogo.jpg|left]] '''[[Pt/FlightGear|FlightGear]] Flight Simulator''' é um simulador de vôo maduro, sofisticado e de código fonte aberto (open-source) criado e mantido completamente por voluntários. O código fonte completo desse projeto está disponível via [[Pt/Git|Git]], livremente licenciado sob a [[Pt/Licença Pública Geral GNU|Licença Pública Geral GNU]]. O FlightGear [[Pt/FlightGear|versão 2.0.0]] foi lançado em 25 de Fevereiro de 2010.

O objetivo do projeto [[Pt/FlightGear|FlightGear]] inclui a criação de um framework de simulador de voo para uso em pesquisas e/ou ambiente acadêmico, para o desenvolvimento e outro propósito envolvendo a simulação de voo, e também como uma aplicação para o usuário comum. O projeto pode ser expandido e melhorado por qualquer pessoa interessada em contribuir, seja para esse ou para os [[Pt/Projetos relacionados|projetos relacionados]] ([http://www.flightgear.org/links.html lista de projetos]).

O FlightGear é distribuido com um conjunto de documentação devidamente ilustrada - o destaque para ''"The Manual"'', que está disponível em [http://mapserver.flightgear.org/getstart.pdf PDF] e [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. A Wiki do FlightGear foi iniciada em 2006 e atualmente cobre uma vasta gama de tópicos relacionados ao FlightGear.

'''Escolha um dos (sub)portais:'''

{|style="background:none;"
|style="font-size:95%; padding-left:10px; padding-right:20px; margin:0px; vertical-align: top; text-align:left; white-space:nowrap; color:#000;"|
* [[Pt/Portal:Desenvolvedor|Desenvolvedor]]
** [[Pt/Portal:Desenvolvedor/Modelagem 3D|Modelagem 3D]]
** [[Pt/Portal:Desenvolvedor/Avião|Aeronaves]]
** [[Pt/Portal:Desenvolvedor/Cenário|Cenários]]
|style="font-size:95%; padding-left:20px; margin:0px; vertical-align: top; text-align: left; border-left: 2px solid #d9e2e2; white-space:nowrap; color:#000;"|
* [[Pt/Portal:Usuário|Usuário]]
* [[Pt/Portal:Piloto|Piloto]]
|}

===== '''Se você é um novato, dê uma olhada no [[Help:Contents|manual]] antes de criar ou editar um artigo!''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Iniciante</h2>
|-
|style="color:#000;"|
* [[FAQ ]]
* [[Pt/Como escapar dos erros comuns|Escapando dos erros comuns]]
* [[Pt/Como usar a função multiplayer|Multiplayer]]
* [[Pt/Novo no FlightGear|Novo no FlightGear]]
* [[Pt/Resolvendo Problemas|Problemas]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Utilizando o FlightGear</h2>
|-
|style="color:#000;"|
* [[Pt/Avião|Avião]]
* [[Pt/Voando de Helicóptero|Voando de Helicóptero]]
* [[Pt/Tabela de modelos|Tabela de modelos]]
'''[[Pt/Portal:Usuário|Mais e além...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Desenvolvendo o FlightGear</h2>
|-
|style="color:#000;"|
* [[Pt/Compilando o FlightGear|Compilando o FlightGear]]
* [[Pt/Compilando o Terragear no Ubuntu|Compilando o Terragear no Ubuntu]]
* [[Pt/Gerenciador de Pacotes do FlightGear|Gerenciador de Pacotes do FlightGear]]
'''[[Pt/Portal:Desenvolvedor|Mais e além...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Novidades</h2>
|-
|style="color:#000;"|
* [[FlightGear Newsletter {{MONTHNAME|{{LASTMONTHNAME}}}} {{CURRENTYEAR}}]] ([[:Category:FlightGear Newsletter|arquivo]])

* '''25 de Fevereiro de 2010:''' [[Pt/FlightGear|FlightGear 2.0.0]] lançado
* '''25 de Janeiro de 2009:''' [[Pt/FlightGear|FlightGear 1.9.1]] lançado
* '''22 de Dezembro de 2008:''' [[Pt/FlightGear|FlightGear 1.9.0]] lançado
* '''27 de Outubro de 2008:''' [[World Scenery 1.0.1]] lançado
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Imagem da Semana</h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Você sabia...</h2>
|-
|style="color:#000;"|
{{VocêSabiaMain}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Promoção</h2>
|-
|style="color:#000;"|
* [[Pt/Entrevistas sobre FlightGear|Entrevistas sobre FlightGear]]
* [[Pt/Vídeos sobre FlightGear|Vídeos sobre FlightGear]]

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[de:Hauptseite]]
[[es:Portada]]
[[fi:Etusivu]]
[[fr:Accueil]]
[[nl:Hoofdpagina]]
[[en:Main Page]]
[[pl:Strona główna]]
[[ru:Заглавная страница]]
[[zh:Main Page]]

Portal:Developer/Aircraft/pt

2010-06-18T23:25:49Z

Rsbrflyer: Redirected page to Pt/Portal:Desenvolvedor/Avião

#REDIRECT [[Pt/Portal:Desenvolvedor/Avião]]

Pt/Portal:Desenvolvedor/Avião

2010-06-18T23:25:13Z

Rsbrflyer:

{{Template:MenuDePortais}}

{|style="border-spacing:8px; margin:0px -8px; width:100%;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">O Portal do Desenvolvedor de Avião</h2>
|-
|style="color:#000;"|
Este portal se destina a desenvolvedores de [[Pt/Avião|aviões]] para o [[Pt/FlightGear|FlightGear]] e tem o objetivo de reunir artigos relacionados aos aviões. Veja o [[Pt/Portal:Desenvolvedor|portal do desenvolvedor]] para mais artigos sobre o desenvolvimento em geral.

|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"

! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Texturas</h2>
|-
|style="color:#000;"|
* [[Pt/Criar uma textura|Crie uma textura]]
* [[Pt/Texturas e Multiplayer|Texturas e Multiplayer]]
|}

{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FDM</h2>
|-
|style="color:#000;"|
* [[Pt/Como adicionar um reversor de empuxo|Adicionar reversor de empuxo]]
* [[Pt/Modelo de Voo| Modelo de Voo]]
* [[Pt/JSBSim Commander|JSBSim Commander]]
* [[Pt/JSBSim|JSBSim]] • [[Pt/UIUC|UIUC]] • [[Pt/YASim|YASim]]
|-
|}

{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Piloto automático</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.org/Docs/XMLAutopilot/ Customizing the XML Autopilot]
* [[Pt/Recursos para o ajuste do piloto automático|Recursos para o ajuste do piloto automático]]
|}

|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Geral</h2>
|-
|style="color:#000;"|
* [http://wiki.flightgear.org/index.php/Category:Aircraft_TODO Lista de Tarefas para os Aviões] (TODO-list)
* [[Pt/Recursos para informação sobre aviões|Recursos para informação sobre aviões]]
* [[Pt/Manuais de aviões|Manuais de aviões]]
* [[Pt/Recursos para o desenvolvimento de aviônicos|Recursos para o desenvolvimento de aviônicos]]
* [[Pt/Recursos para o desenvolvimento de sistemas do avião|Recursos para o desenvolvimento de sistemas do avião]]
|}

{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Scripts em Nasal</h2>
|-
|style="color:#000;"|
* [[Pt/A linguagem interpretada Nasal|A linguagem interpretada Nasal]]
* [[Pt/Escrevendo um simples script em Nasal|Escrevendo um simples script em Nasal]]
|}

|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Modelagem</h2>
|-
|style="color:#000;"|
* [[Pt/Modelos 3D de aviões|Modelos 3D de aviões]]
* [[Pt/Rotação do avião em torno do nariz|Rotação do avião em torno do nariz]]
* [[Pt/Como adicionar iluminação no avião|Como adicionar iluminação no avião]]
* [[Pt/Tutorial sobre Normais e Transparências|Tutorial sobre Normais e Transparências]]
* [[Pt/Como diminuir o número de faces|Como diminuir o número de faces]]
* [[Pt/Importação e exportação de modelo|Importação e exportação de modelo]]
* [[Pt/Iniciação à modelagem 3D|Iniciação à modelagem 3D]]
* [[:Category:Modeling|Categoria Modelagem]]
* [[Pt/Recursos para modelagem|Recursos para modelagem]]
* [[Copyright Inquiry|Direitos Autorais]] ''(em inglês)''

* [[Pt/AC3D|AC3D]] • [[Pt/Blender|Blender]] • [[Pt/SketchUp|SketchUp]] • [[Pt/Wings 3D|Wings 3D]]
|-
|}

|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Como...</h2>
|-
|style="color:#000;"|

* [[Pt/Como criar um avião|Criar um avião]]
* [[Pt/Como|Criar um helicoptero]]

* [[Pt/Como configurar visões no FlightGear|Configurar visões no FlightGear]]
* [[Pt/Como criar instrumentos para o painel|Criar instrumentos para o painel]]
* [[Pt/Como criar tutoriais interativos|Criar tutoriais interativos]]
* [[Pt/Como definir limites de velocidade|Definir limites de velocidade]]
* [[Pt/Como implementar asa flexível|Implementar asa flexível]]
* [[Pt/Como implementar o pushback|Implementar o pushback]]
* [[Pt/Visão do tipo caminhada‎|Visão do tipo caminhada‎]]
|}
|}

__NOTOC__
__NOEDITSECTION__

[[es:Portal:Desarrolladores/Aeronaves]]
[[en:Portal:Developer/Aircraft]]