FlightGear wiki - User contributions [en]

List of developed airports

2012-05-19T04:20:45Z

Wagner Silva:

This page lists developed airports which are included in FlightGear if two conditions are fulfilled. Airports are listed here if
* at least one building or [[Signs|taxi signs]] have been placed
* the respective objects are represented in the [[FlightGear Scenery Database]].
Every improvement listed here can be downloaded using [[TerraSync]] and it will also be included in the next [[World Scenery]] release.

If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].

The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see
* the current airport layout with runways, taxiways and aprons
* red dots: static objects in the scenery database made especially for this airport
* dark red dots: shared models in the scenery database placed at this airport
* green dots: [[Signs|taxi signs]] placed at the airport

'''Note:''' You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.

== Airports ==

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Name !! style="background:#efefef" | Country !! style="background:#efefef" | Continent !! class="unsortable" style="background:#efefef" | Comment

|-
| EDDC || Dresden Airport || Germany || Europe || One building: hangar/terminal

|-
| [http://mapserver.flightgear.org/map/?lon=8.56293&lat=50.03795&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

|-
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown

|-
| [http://mapserver.flightgear.org/map/?lon=13.40379&lat=52.47502&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Tower and terminal

|-
| [http://mapserver.flightgear.org/map/?lon=11.78609&lat=48.35378&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [http://mapserver.flightgear.org/map/?lon=12.23603&lat=51.42262&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modeled with [[Signs]]

|-
| [http://mapserver.flightgear.org/map/?lon=13.28992&lat=52.55917&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars

|-
| [http://mapserver.flightgear.org/map/?lon=10.71706&lat=53.80496&zoom=15&layers=B000000TFFFFTFFFTTFFF EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]

|-
| [http://mapserver.flightgear.org/map/?lon=7.16278&lat=50.76767&zoom=15&layers=B000000TFFFFTFFFTTFFF EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modeled

|-
| EEKE || Kuressaare Airport || Estonia || Europe ||

|-
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe ||

|-
| EETU || Tartu Airport || Estonia || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=25.04487&lat=60.25318&zoom=15&layers=B000000TFFFFTFFFTTFFF EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=24.95253&lat=60.3206&zoom=14&layers=B000000TFFFFTFFFTTFFF EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=22.26281&lat=60.51412&zoom=14&layers=B000000TFFFFTFFFTFFFF EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled

|-
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility

|-
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe ||

|-
| EGGW || London Luton Airport || United Kingdom || Europe ||

|-
| EGKA || Shoreham Airport || United Kingdom || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=-0.19224&lat=51.14869&zoom=14&layers=B000000TFFFFTFFFTTFFF EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network

|-
| [http://mapserver.flightgear.org/map/?lon=-0.46095&lat=51.47139&zoom=14&layers=B000000TFFFFTFFFTTFFF EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

|-
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models

|-
| [http://mapserver.flightgear.org/map/?lon=1.28469&lat=52.67713&zoom=15&layers=B000000TFFFFTFFFTTFFF EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.

|-
| [http://mapserver.flightgear.org/map/?lon=4.75487&lat=52.31296&zoom=14&layers=B000000TFFFFTFFFTTFFF EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

|-
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=5.51885&lat=52.45717&zoom=15&layers=B000000TFFFFTFFFTTFFF EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

|-
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.

|-
| EIDW || [[Dublin Airport]] || Ireland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=6.11017&lat=62.56037&zoom=15&layers=B000000TFFFFTFFFTTFFF ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=6.10949&lat=61.83027&zoom=15&layers=B000000TFFFFTFFFTTFFF ENSD] || Sandane Airport || Norway || Europe ||

|-
| ENVA || Trondheim Værnes Airport || Norway || Europe ||

|-
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=-106.60912&lat=35.04021&zoom=14&layers=B000000TFFFFTFFFTTFFF KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=-84.42809&lat=33.63672&zoom=14&layers=B000000TFFFFTFFFTTFFF KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| KAUS || Austin-Bergstrom Airport, TX || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-76.66833&lat=39.17535&zoom=14&layers=B000000TFFFFTFFFTTFFF KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [http://mapserver.flightgear.org/map/?lon=-76.92254&lat=38.98062&zoom=15&layers=B000000TFFFFTFFFTTFFF KCGS] || College Park Airport, MD || USA || America ||

|-
| KDCA || Reagan National Airport, VA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-104.67318&lat=39.86166&zoom=13&layers=B000000TFFFFTFFFTTFFF KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

|-
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only

|-
| KFHR || Friday Harbor Airport, WA || USA || America ||

|-
| KIND || Indianapolis Airport, IN || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-90.07589&lat=32.31118&zoom=14&layers=B000000TFFFFTFFFTTFFF KJAN] || Jackson-Evers Airport, MS || USA || America ||

|-
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America ||

|-
| KLAS || Las Vegas McCarran Airport, NV || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-118.40809&lat=33.9425&zoom=14&layers=B000000TFFFFTFFFTTFFF KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

|-
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-109.4667&lat=47.04924&zoom=14&layers=B000000TFFFFTFFFTTFFF KLWT] || Lewistown Municipal Airport, MT || USA || America ||

|-
| KMCI || Kansas City Airport, MO || USA || America || Basic development only

|-
| KMTN || Martin State Airport, MD || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-117.69181&lat=35.68565&zoom=14&layers=B000000TFFFFTFFFTTFFF KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.04918&lat=37.4162&zoom=15&layers=B000000TFFFFTFFFTTFFF KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-122.22062&lat=37.7214&zoom=14&layers=B000000TFFFFTFFFTTFFF KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

|-
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-88.55704&lat=43.98436&zoom=14&layers=B000000TFFFFTFFFTTFFF KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-75.12398&lat=38.31045&zoom=14&layers=B000000TFFFFTFFFTTFFF KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.59751&lat=45.58871&zoom=14&layers=B000000TFFFFTFFFTTFFF KPDX] || Portland Airport, OR || USA || America ||

|-
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America ||

|-
| KRNO || Reno/Tahoe Airport, NV || USA || America ||

|-
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.3749&lat=37.61897&zoom=14&layers=B000000TFFFFTFFFTTFFF KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.

|-
| KSLC || Salt Lake City International Airport, UT || USA || America ||

|-
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America ||

|-
| LDSP || Split Airport || Croatia || Europe || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=2.35465&lat=49.04626&zoom=15&layers=B000000TFFFFTFFFTTFFF LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=2.56241&lat=49.00972&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=2.60632&lat=48.89629&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| LFPL || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPO || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPZ || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=-4.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| LFSB || Basel-Mulhouse || Switzerland || Europe ||

|-
| LILN || Venegono Airport || Italy || Europe || Developed airport

|-
| LILQ || Massa Cinquale Airport || Italy || Europe ||

|-
| LILV || Valbrembo Airport || Italy || Europe ||

|-
| LIMC || Milano-Malpensa Airport || Italy || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=9.70741&lat=45.66952&zoom=14&layers=B000000TFFFFTFFFTTFFF LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modelled

|-
| [http://mapserver.flightgear.org/map/?lon=9.27521&lat=45.44776&zoom=14&layers=B000000TFFFFTFFFTTFFF LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=7.36789&lat=45.73857&zoom=15&layers=B000000TFFFFTFFFTTFFF LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=11.34397&lat=47.26023&zoom=15&layers=B000000TFFFFTFFFTTFFF LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

|-
| LROP || Bucharest Otopeni || Romania || Europe ||

|-
| LSGS || Sion Airport || Switzerland || Europe || Basic development only

|-
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only

|-
| PANC || Ted Stevens Anchorage International Airport || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=136.80541&lat=34.85841&zoom=14&layers=B000000TFFFFFFFFTTFFF RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [http://mapserver.flightgear.org/map/?lon=139.78114&lat=35.5533&zoom=14&layers=B000000TFFFFTFFFTTFFF RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=126.45051&lat=37.46909&zoom=14&layers=B000000TFFFFTFFFTTFFF RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=121.01349&lat=14.51024&zoom=14&layers=B000000TFFFFTFFFTTFFF RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-
| TDPD || Melville Hall Airport || Dominica || America ||

|-
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America ||

|-
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America ||

|-
| TIST || Cyril E. King Airport || US Virgin Islands || America ||

|-
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America ||

|-
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America ||

|-
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain

|-
| TNCS || Junacho E. Yrausquin Airport || Saba || America || Fully modeled

|-
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-49.17201&lat=-25.53101&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBCT] || Afonso Pena International Airport || Brazil || South America || 3D Fully modeled - Download [http://www.grupofgbr.com.br/aeroportos#!__aeroportos Site Group FGBR]

|-
| [http://mapserver.flightgear.org/map/?lon=-46.65768&lat=-23.62558&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBSP] || Congonhas Airport || Brazil || South America || 3D Fully modeled - Download [http://www.grupofgbr.com.br/aeroportos#!__aeroportos Site Group FGBR]

|-
| [http://mapserver.flightgear.org/map/?lon=-46.46864&lat=-23.43351&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBGR] || Guarulhos International Airport || Brazil || South America || 3D Fully modeled - Download [http://www.grupofgbr.com.br/aeroportos#!__aeroportos Site Group FGBR]

|-
| [http://mapserver.flightgear.org/map/?lon=-48.54304&lat=-27.6685&zoom=15&layers=B0000000TFFFTFFFTFFFFFFF SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D Fully modeled - Download [http://www.grupofgbr.com.br/aeroportos#!__aeroportos Site Group FGBR]

|-
| VIDP || Indira Gandhi International Airport || India || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=-90.13769&lat=43.83872&zoom=15&layers=B000000TFFFFTFFFTTFFF 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-89.02545&lat=44.50485&zoom=15&layers=B000000TFFFFTFFFTTFFF 68C] || Iola Central County Airport, WI || USA || America ||

|}

{{Suggested}}

[[Category:List]]
[[Category:Airports]]

File:GRUPOFGBR.png

2012-05-07T04:55:30Z

Wagner Silva:

{{non-stable}}

{{infobox Aircraft
|image = GRUPOFGBR.png
|name = Group FGBR
|type = Development Group
|status = Active
|site = http://www.grupofgbr.com.br
}}

== Authors ==
Aurino das Neves = BR-NVS,
George Luiz = PR-GEO,
Michel Maia = michel,
Isaías V. Prestes = PR-PRE,
Rick Britto = BR-RIC,
Wagner Silva = BR-WAG.

Site:
[http://www.grupofgbr.com.br www.grupofgbr.com.br]

File:GRUPOFGBR.png

2012-05-07T04:29:03Z

Wagner Silva:

=={{int:filedesc}}==
{{Information
|description={{en|1=Group FGBr}}
|date=2012-05-07
|source={{own}}
|author=[[User:Wagner Silva|Wagner Silva]]
|permission=
|other_versions=
|other_fields=
}}

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

Pt/Boeing 777-200LR

2012-05-07T04:21:46Z

Wagner Silva:

{{non-stable}}
{{aero-stub}}

{{infobox Aircraft
|image = 777-200LR.png
|alt =
|name = Boeing 777-200LR
|type = Airliner
|fdm = YASim
|status = Alpha
|authors = Group FGBR - Brazil
|fgname = 777-200LR
|download = http://www.grupofgbr.com.br/avioes#!__avioes/vstc3=777
}}
O Boeing 777-200LR tornou-se a aeronave de maior alcance quando entrou em serviço em 2006. É capaz de voar 17,446 km em 18 horas. Pode ser equipado com 2 turbofans General Electric GE90-110B1, ou GE90-115B turbofans. Pode carregar 301 passageiros divididos em 3 classes e 330 passageiros em 2 classes.
O MTOW foi consideravelmente aumentado com a adição de três tanques auxiliares no compartimento de carga, novas asas, reforços estruturais e a adição de Wingtips.O 1º vôo foi realizado em 8 de março de 2005. O 777-200LR entrou em serviço em janeiro de 2006. A única aeronave fabricada com alcance superior ao LR, foi o KC-10.

The 777-200LR ("LR" for Longer Range), the C-market model, became the world's longest-range commercial airliner when it entered service in 2006. Boeing named this aircraft the Worldliner, highlighting its ability to connect almost any two airports in the world, although it is still subject to ETOPS restrictions. It holds the world record for the longest nonstop flight by a commercial airliner, and has a maximum range of 9,380 nautical miles (17,370 km). The −200LR was intended for ultra-long-haul routes such as Los Angeles to Singapore, or Dallas to Tokyo.

== 777-200LR FlightGear ==

Nesta versão (LR) "longer-range" vem com maior alcance, motores mais potentes GE90 by Prestes e wingles nas asas contém Cockpit 3D.
Vem com a textura do FlightGear Brasil feito pelo texturizador brasileiro Emerson.

O 777-200LR do Flightgear é uma produção brasileira da equipe do Grupo FGBR:

Aurino das Neves - BR-NVS

George Luis - PR-GEO

Hugo Michel Maia - Michel

Isaias Prestes - PR-PRE

Marcos

Wagner - BR-WAG

File:777-200LR.png

2012-05-07T04:05:14Z

Wagner Silva:

=={{int:filedesc}}==
{{Information
|description={{en|1=Boeing 777-200LR}}
|date=2012-05-07
|source={{own}}
|author=[[User:Wagner Silva|Wagner Silva]]
|permission=
|other_versions=
|other_fields=
}}

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

File:777-200LR.jpg

2012-05-07T04:01:41Z

Wagner Silva:

=={{int:filedesc}}==
{{Information
|description={{en|1=Boeing 777-200LR}}
|date=2012-05-07
|source=wingsoverkansas.com
|author=As imagens podem ter direitos autorais.
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{FAL}}

Embraer EMB-121 Xingu

2012-05-07T03:39:48Z

Wagner Silva:

{{non-stable}}

{{infobox Aircraft
|image = EMB-121.png
|name = Embraer EMB-121 Xingu
|type = Airliner
|livery = white
|authors = Bruno Reichert, Aurino Neves and Isaías V. Prestes
|fdm = JSBSim
|status-fdm = 2
|status-systems = 1
|status-cockpit = 3
|status-model = 4
|fgname = EMB-121
|download = http://www.grupofgbr.com.br/avioes#!__avioes
}}
The '''Embraer EMB 121 Xingu''' (pronounced "shingoo") is a twin-turboprop fixed-wing [[aircraft]] built by the Brazilian aircraft manufacturer, [[Embraer]]. The design of this plane is based on the EMB 110 Bandeirante, using its wing and engine design merged with an all-new fuselage. The EMB 121 first flew on 10 October 1976.

== Work in Progress ==
* Reliable electric system
* Liveries

== External links ==
* [http://www.centrohistoricoembraer.com.br/en/historia-aeronaves/emb-121-xingu.htm EMBRAER website for EMB-121 Xingu]
* [http://en.wikipedia.org/wiki/EMB-121_Xingu Wikipedia]

{{Embraer}}

[[Category:Airliners]]

Embraer 195

2012-05-07T03:36:34Z

Wagner Silva:

{{non-stable}}

{{infobox Aircraft
|image =Embraer195.png
|name =Embraer 195
|type =Airliner
|livery =Azul, FAB, JetBlue
|authors = Isaias V. Prestes, Group FGBR - Brazil
|fdm =JSBSim
|status =Under development
|fgname =Embraer-195
|download =http://www.grupofgbr.com.br/avioes#!__avioes
}}
The '''[[Embraer]] 195''' is a larger stretch of the E-170 model fitted with a new, larger wing and a new engine, the [[GE CF34-10E]], rated at 18,500 lb (82.30 kN). Being in the 100-seat range, it competes with smaller jets including the [[Bombardier]] [[CRJ-1000]], [[Boeing 717]]-200 and [[Boeing 737|737-600]] as well as the [[Airbus]] [[Airbus A318|A318]].

The first flight of the E-195 was in December 2004. European low cost carrier Flybe launched the E-195 with 14 orders and 12 options.

As the 190/195 family is of mainline [[aircraft]] size, many airlines will operate them as such, fitting them with a business class section and operating them themselves, instead of having them flown by a commuter airline partner. For example, Air Canada operates 45 [[Embraer 190|E-190]] aircraft fitted with 9 business-class and 84 economy-class seats as part of their primary fleet.

== Specifications ==
{| class="prettytable"
| '''Weights''' || '''STD & LR versions''' || '''AR version'''
|-
| '''Maximum Take Off Weight''' || STD 107,563lb 48,790kg || 115,279lb 52,290kg
|-
| || LR 111,972lb 50,790kg || ||
|-
| '''Maximum Landing Weight''' || 99,208lb 45,000kg || 100,971lb 45,800kg
|-
| '''Maximum Zero Fuel Weight''' || 93,696lb 42,500kg || 93,916lb 42,600kg
|-
| '''Basic Operating Weight''' || 63,603lb 28,850kg || 63,824lb 28,950kg
|-
| '''Maximum Payload''' || 30,093lb 13,650kg || 30,093lb 13,650kg
|-
| '''Maximum Fuel''' || 28,596lb 12,971kg || 28,596lb 12,971kg
|}

== External Links ==
* [http://www.embraercommercialjets.com.br/english/content/ejets/emb_195.asp Embraer 195 official webpage]
* [http://en.wikipedia.org/wiki/Embraer_195#E-190.2F195 Wikipedia (source)]

{{Embraer}}

[[Category:Airliners]]

Boeing 747-8

2012-05-07T03:32:30Z

Wagner Silva:

{{non-stable}}
{{aero-stub}}

{{infobox Aircraft
|image = 747-8i.jpg
|alt =
|name = Boeing 747-8i
|type = Airliner
|fdm = YASim
|status = Alpha
|authors = Group FGBR - Brazil
|fgname = 747-8i
|download = http://www.grupofgbr.com.br/avioes#!__avioes/vstc3=748/vstc2=748i
}}
The '''Boeing 747-8''' is a wide-body jet airliner developed by [[Boeing|Boeing Commercial Airplanes]]. Officially announced in 2005, the 747-8 is the fourth-generation [[Boeing 747]] version, with lengthened fuselage, redesigned wings and improved efficiency. The 747-8 is the largest 747 version, the largest commercial aircraft built in the United States, and the longest passenger aircraft in the world.

== Aircraft help ==
{{Main article|Boeing 747-400 Tutorial}}

{| class="prettytable"
!Key
!Function
|-
|Ctrl + b
|Speedbrakes
|-
|Delete
|Reverse thrusters
|-
|B
|Parking brake
|}
All buttons/switches in the cockpit can be controlled using the mouse. Most buttons exist of a toggle, where clicking it toggles it either on or off. Switches can be turned clockwise with the left mouse button and counter clockwise using the middle mouse button. Some buttons/switches have a cover on them, clicking it will either open or close it, so the button/switch can be pushed/turned.

Several panels are also available as 2D overlay panels. Clicking the hydraulics or electric overhead panels will open up a 2D variant. Useful when you'd like to keep an eye on the EICAS during startup! You can close the panel via Shift-P.

'''Important notice:''' as of FlightGear 2.6.0, the 744 has tiller steering, just like the real aircraft where the pedals only turn the nose wheel by a few degrees - to achieve optimal precision during takeoffs and landings. Use the tiller (747-400 > Tiller Steering) dialog to steer during taxiing.

* You can also connect a separate joystick axis to the tiller control - just like in the real aircraft, where there is a separate control wheel.
* Finally, you can also disable the separate tiller control and revert to the unrealistic behaviour of using pedals only to completely control the nose wheel (see 747-400 > Tiller Steering dialog).

=== Duo flight crew ===
Currently the pilot monitoring really cannot do anything else than monitoring. All switches and controls must be operated by the pilot flying.
* '''Pilot flying:''' launch the 747-400 as usual.
* '''Pilot monitoring:''' launch the 747-400-fo (First Officier) and position yourself somewhere close to the PF's positions. Now open the <tt>Boeing 747-400 > Select MP-pilot</tt> dialog and click the prefered PF's callsign.

=== Simplified procedures ===
==== Startup ====
# Press the continuous ignition switch on the overhead panel.
# Pull the start select switch for engine #4.
# Set the cutoff switch on the pedestal to RUN.
# Now repeat step 2 and 3 for engines #1, #2 and #3.

==== Takeoff ====
# Set flaps to 20, it will take a minute to extend, so you'd better do this during taxi.
# Smoothly apply full throttle.
# Push the stick slightly forward until atleast 80 kts.
# Around 160 kts, slowly pull the stick back to rotate. Rotate toward 15° pitch attitude.
# The plane should takeoff around 180 kts.
# Retract gear as soon as the aircraft is climbing with atleast 500 ft per minute.

==== Approach ====
# At 10000 ft MSL set the inboard landing light switches to ON.

==== Landing ====
# Set the flaps as directed by the flap extension schedule.
# At glideslope alive:
#* Gear down.
#* Set flaps to 20.
# At glideslope capture:
#* Set flaps to 25 or 30.

==== Landing roll ====
# Close all thrust levers.
# Set speedbrakes to UP.

==== Shutdown ====
# Set all fuel cutoff switches to OFF.
# Turn continuous ignition OFF.

{{boeing}}

[[Category:Airliners]]

Embraer EMB-120 Brasilia

2012-05-07T03:25:45Z

Wagner Silva:

{{non-stable}}

''This includes the following models: EMB-120, EMB-120ER''

{{infobox Aircraft
|image = EMB-120.png
|name = Embraer EMB-120 Brasilia
|type = Airliner
|livery = aluminum, white, RioSul, Interbrasil, United
|authors = Isaias V. Prestes and Aurino Neves
|fdm = YAsim
|status-fdm = 3
|status-systems = 1
|status-cockpit = 3
|status-model = 4
|fgname = EMB-120
|download = http://www.grupofgbr.com.br/avioes#!__avioes
}}
The '''Embraer EMB 120 ''Brasilia''''' is a twin-turboprop commuter airliner, produced by [[Embraer]] of Brazil. Originally called the Araguaia, the name was changed to Brasilia in 1979 at the official launching of the project. The design retained the T-tail and supercritical wing of the [[Embraer EMB-121 Xingu|EMB-121 Xingu]], but with the capacity for 30 seats. Originally designed to utilise the new 1500SHP Pratt & Whitney Canada PW115 Turboprop, this was later upgraded to the 1892 ESHP PW118.

== External links ==
* [http://http://www.centrohistoricoembraer.com.br/en/historia-aeronaves/emb-120-brasilia.htm EMBRAER website for EMB-120 Brasilia]
* [http://http://en.wikipedia.org/wiki/Embraer_EMB_120_Brasilia Wikipedia]

{{Embraer}}

[[Category:Airliners]]

User talk:Gijs

2012-04-22T05:21:54Z

Wagner Silva: /* Deleting of a user page? */

{{Archives|[[/Archive 2008-2011|2008-2011]]}}

== Idea: Suggested flights with stars ==

How 'bout this idea... Make a star rating system thingy for [[Suggested Flights]]? A template with 0 to 5 stars we could add to a flight so that users can rate the flight.
I dunno how to make it else I would... :)
[[User:PH-JBO|PH-JBO]] 19:38, 22 December 2011 (EST)
: We could use the rating system that is used for aircraft/airports, but that'll require each flight to be on a special page; which is quite a hassle IMO. Don't know of any other option right now...
: [[User:Gijs|Gijs]] 16:24, 23 December 2011 (EST)

== Renaming newly categorised files ==

I saw in [[Special:RecentChanges|recent changes]] that you have renamed many of the files that I have categorised, and I just want to say: {{thumbs up|13}} Thank you! --[[User:Johan G|Johan G]] 15:15, 14 February 2012 (EST)
: Not intentionally only files that you categorised (apparently you categorised ALL file :P), but files that had the basic fgfs-screen names, which is very very bad...
: I'd like to thank you for all the hard work you're doing on the wiki these days. Good to see some more activity!
: [[User:Gijs|Gijs]] 15:17, 14 February 2012 (EST)
:: I didn't really categorise ''all'' files (there's still about 1400 to go...), but thank you anyway. ;-) —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:07, 13 March 2012 (EDT)

== Template documentation ==

Just a heads up.

While having a bit less presence in the FlightGear community (probably a bit of recoil from straining myself, but also due to real life) for a while I drop in now and then for a peek on the Wiki.

Recently I noticed that one of my sup-pages ([http://wiki.flightgear.org/index.php?title=User:Johan_G/Wiki_improvement&oldid=40953 User:Johan G/Wiki improvement]) was a bit different, but noticed I'm the only one editing there. Checking the used templates gave the explanation. Specifically the <nowiki>{{</nowiki>[http://wiki.flightgear.org/index.php?title=Template:Tl&diff=42423&oldid=40924 tl]<nowiki>}}</nowiki> template. ;-)

When you add the <nowiki>{{</nowiki>[[Template:Informative template|informative template]]<nowiki>}}</nowiki>, make sure you leave the <code><nowiki><noinclude></nowiki></code> tag where it was. If you add empty lines and/or spaces, those will be added each time the the template is used with unwanted results. Remember that a space in the beginning of a line will put that remaining text on that line in a "code box". ;-)

''In this specific case the previous edit looked like this,''

<nowiki>{{[[Template:{{{1}}}|{{{1}}}]]}}<noinclude></nowiki>
...

''while the new edit looked like this (spaces represented by underscores),''

<nowiki>{{[[Template:{{{1}}}|{{{1}}}]]}}_</nowiki>
_
<nowiki><noinclude></nowiki>
...

''The result is that''
The template <nowiki>{{</nowiki>informative template<nowiki>}}</nowiki> is a template documenting templates.

''instead of being rendered like this,''

The template <nowiki>{{</nowiki>[[Template:Informative template|informative template]]<nowiki>}}</nowiki> is a template documenting templates.

''got rendered like this:''

The template <nowiki>{{</nowiki>[[Template:Informative template|informative template]]<nowiki>}}</nowiki>
is a template documenting templates

Otherwise I see that you are doing a wonderful job.{{thumbs up}} Just don't strain yourself, will you. :-)

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:49, 13 March 2012 (EDT)

== Unsigned template + Archive pages ==

I had been thinking of moving {{tl|unsigned2}} to {{tl|unsigned}} for a while, but not done it. Good idea to keep the redirection page.

On a totally different matter, when you get to the point when you consider your talk page is to long I hope that you do not delete parts of it, but instead move it to a archive in the form of a subpage, in case you or someone else want to have a look on it in the future.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:03, 19 March 2012 (EDT)

==Deleting of a user page?==
Hi Gijs, Through this message on behalf of the group fgbr denuciar (Unitedfreeworld) be using our name in a partnership to build the 747-8i does not exist.
We ask that meets our request and delete the Wiki page that is in putting the group fgbr as a partner working with (Unitedfreeworld).
Here is the page created for them: http://wiki.flightgear.org/Boeing_747-8i

Thank you for your attention.

The Group FGBr thanks.
My prefix is BR-WAG contact.

== Article considered for deletion ==
Hi Gijs, my page is also suggest for being deleted because aparently, someone want to make a page with all the VA which does already exist !
So, I ask you (or if you have good reason) not to delete my articles because it's really anoying to make everyday the same roll-back on the page.
Thx, [[User:Bastien.D|Bastien.D]] 20:00 01 April 2012 (EDT)

: Please see my message on your talk page: [[User talk:Bastien.D#Removing templates]]
: [[User:Gijs|Gijs]] 16:10, 1 April 2012 (EDT)

== Virtual airline template ==

{{thumbs up}} Thank you for the work on [http://wiki.flightgear.org/index.php?title=Template:Virtual_airline_summary&oldid=46998 Template:Virtual airline summary]! I could not have done it better for at least a couple of weeks. :-D —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:21, 9 April 2012 (EDT)

== Missing GPL logo image ==

I noticed that the image for the GLP v.2 logo at the bottom right of every page is missing, but I do not know for how long it has been missing. I do not know where I should point you to help you fix it, yet, but on the source for a downloaded page it is located as below (note the empty <code>src</code> attribute):

<syntaxhighlight lang="html4strict">

<div id="footer">
...
<img src="" alt="GNU GENERAL PUBLIC LICENSE Version 2, June 1991" width="88" height="31"/>
...
</div>

</syntaxhighlight>

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 05:18, 15 April 2012 (EDT)
: I think it's never been there actually. MediaWiki templates do not support the GPL (by default), so it failed to display an icon. But I've removed it now. Will adjust the copyright text slightly as well.
: Thanks! [[User:Gijs|Gijs]] 05:42, 15 April 2012 (EDT)

FlightGear Newsletter April 2012

2012-04-17T14:19:36Z

Wagner Silva: /* New aircraft */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===
New Embraer - 195, developed by the group FGBr.
version FG 2.4 / 2.6
Soon this site: www.grupofgbr.com.br
[[File:Embraer - 195 em desenvolvimento (2)..jpg]]
[[File:Embraer - 195 em desenvolvimento..jpg]]
[[File:Embraer - 195 em desenvolvimento (4)..jpg]]
[[File:Embraer - 195 em desenvolvimento (3)..jpg]]
Soon this site: www.grupofgbr.com.br

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

== Airport of the month ==
"Airport International Of Guarulhos (SBGR Sao Paulo)"

[[File:International_Airport_Of_Guarulhos.jpg]]
[[File:International Airport Of Guarulhos (1).jpg]]
[[File:International Airport Of Guarulhos (2).jpg]]

International Airport Of Guarulhos In Sao Paulo City Brasil
In the site: www.grupofgbr.com.br

== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

FlightGear Newsletter April 2012

2012-04-17T14:18:07Z

Wagner Silva: /* Airport of the month */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===
New Embraer - 195, developed by the group FGBr.
version FG 2.4 / 2.6
Soon this site: www.grupofgbr.com.br
[[File:Embraer - 195 em desenvolvimento (2)..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento (4)..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento (3)..jpg|thumb|Embraer - 195]]

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

== Airport of the month ==
"Airport International Of Guarulhos (SBGR Sao Paulo)"

[[File:International_Airport_Of_Guarulhos.jpg]]
[[File:International Airport Of Guarulhos (1).jpg]]
[[File:International Airport Of Guarulhos (2).jpg]]

International Airport Of Guarulhos In Sao Paulo City Brasil
In the site: www.grupofgbr.com.br

== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

FlightGear Newsletter April 2012

2012-04-17T14:12:09Z

Wagner Silva: /* Airport of the month */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===
New Embraer - 195, developed by the group FGBr.
version FG 2.4 / 2.6
Soon this site: www.grupofgbr.com.br
[[File:Embraer - 195 em desenvolvimento (2)..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento (4)..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento (3)..jpg|thumb|Embraer - 195]]

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

== Airport of the month ==
"Airport International Of Guarulhos (SBGR Sao Paulo)"

[[File:International Airport Of Guarulhos (1).jpg|thumb|New International Airport Of Guarulhos]]
[[File:International Airport Of Guarulhos (2).jpg|thumb|New International Airport Of Guarulhos]]

International Airport Of Guarulhos In Sao Paulo City Brasil
In the site: www.grupofgbr.com.br

== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

File:International Airport Of Guarulhos (1).jpg

2012-04-17T14:09:16Z

Wagner Silva:

=={{int:filedesc}}==
{{Information
|description={{en|1=International_Airport_Of_Guarulhos}}
|date=2012-04-17
|source={{own}}
|author=[[User:Wagner Silva|Wagner Silva]]
|permission=
|other_versions=
|other_fields=
}}

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

File:International Airport Of Guarulhos (2).jpg

2012-04-17T14:09:15Z

Wagner Silva:

File:International Airport Of Guarulhos.jpg

2012-04-17T14:02:52Z

Wagner Silva: In Sao Paulo City Brasil

In Sao Paulo City Brasil

FlightGear Newsletter April 2012

2012-04-17T13:59:03Z

Wagner Silva: /* New aircraft */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===
New Embraer - 195, developed by the group FGBr.
version FG 2.4 / 2.6
Soon this site: www.grupofgbr.com.br
[[File:Embraer - 195 em desenvolvimento (2)..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento (4)..jpg|thumb|Embraer - 195]][[File:Embraer - 195 em desenvolvimento (3)..jpg|thumb|Embraer - 195]]

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

== Airport of the month ==
== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

FlightGear Newsletter April 2012

2012-04-17T13:56:53Z

Wagner Silva: /* Aircraft of the month */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===
New Embraer - 195, developed by the group FGBr.
version FG 2.4 / 2.6
[[File:Embraer - 195 em desenvolvimento (2)..jpg|thumb|Adicionar legenda aqui]][[File:Embraer - 195 em desenvolvimento..jpg|thumb|Adicionar legenda aqui]][[File:Embraer - 195 em desenvolvimento (4)..jpg|thumb|Adicionar legenda aqui]][[File:Embraer - 195 em desenvolvimento (3)..jpg|thumb|Adicionar legenda aqui]]
Soon this site: www.grupofgbr.com.br

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

== Airport of the month ==
== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

FlightGear Newsletter April 2012

2012-04-17T13:54:54Z

Wagner Silva: /* New aircraft */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===
New Embraer - 195, developed by the group FGBr.
version FG 2.4 / 2.6
[[File:Embraer - 195 em desenvolvimento (2)..jpg|thumb|Adicionar legenda aqui]][[File:Embraer - 195 em desenvolvimento..jpg|thumb|Adicionar legenda aqui]][[File:Embraer - 195 em desenvolvimento (4)..jpg|thumb|Adicionar legenda aqui]][[File:Embraer - 195 em desenvolvimento (3)..jpg|thumb|Adicionar legenda aqui]]
Soon this site: www.grupofgbr.com.br

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

"'Airport International Of Guarulhos (SBGR Sao Paulo)"

[[http://img836.imageshack.us/img836/2581/46118228348625173396710.jpg]]
[[http://img821.imageshack.us/img821/9606/40211614604300884940910.jpg]]

[[http://img31.imageshack.us/img31/2633/40897514604304551607210.jpg]]

http://www.youtube.com/watch?v=md05laSb79g

International Airport Of Guarulhos In Sao Paulo City Brasil

[http://www.grupofgbr.com.br/galeria#!__aeroportos Download Link]

== Airport of the month ==
== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

FlightGear Newsletter April 2012

2012-04-17T13:48:23Z

Wagner Silva: /* New aircraft */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

New Embraer - 195, developed by the group FGBr.
version FG 2.4 / 2.6

[[File:Embraer - 195 em desenvolvimento (2)..jpg|thumb|Adicionar legenda aqui]]
[[File:Embraer - 195 em desenvolvimento..jpg|thumb|Adicionar legenda aqui]]
[[File:Embraer - 195 em desenvolvimento (4)..jpg|thumb|Adicionar legenda aqui]]
[[File:Embraer - 195 em desenvolvimento (3)..jpg|thumb|Adicionar legenda aqui]]

Soon this site: www.grupofgbr.com.br

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

"'Airport International Of Guarulhos (SBGR Sao Paulo)"

[[http://img836.imageshack.us/img836/2581/46118228348625173396710.jpg]]
[[http://img821.imageshack.us/img821/9606/40211614604300884940910.jpg]]

[[http://img31.imageshack.us/img31/2633/40897514604304551607210.jpg]]

http://www.youtube.com/watch?v=md05laSb79g

International Airport Of Guarulhos In Sao Paulo City Brasil

[http://www.grupofgbr.com.br/galeria#!__aeroportos Download Link]

== Airport of the month ==
== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

FlightGear Newsletter April 2012

2012-04-17T13:42:56Z

Wagner Silva: /* Aircraft of the month */

{{draft|newsletter}}

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

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

== Development news ==

=== Mailing list digest ===

(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)

=== Forum digest ===

=== Git digest ===

== Interview with a contributor (Sam Clancy) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]!''

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

* '''How long have you been involved in FlightGear?'''
Actively I've been involved with the FlightGear project since early January 2011. Simply because my old computer (which my family had had for about 5 or 6 years prior) couldn't run FlightGear. But after we upgraded... (insert evil laugh here)
* '''What is your forum nickname?'''
connect is my name.
* '''What are your major interests in FlightGear?'''
Flying, first of all. My life dream is to become a commercial airline pilot, hopefully somewhere in Europe. I've taken my very first steps towards this in real life, with my "TIF" or Training Introductory Flight, but I also believe my prior experience FlightGear, and of course my continued use of FlightGear gives me a much cheaper alternative, for the time being, to gain experience.
* '''Why is it that you are interested in flight simulation or aviation in general?'''
The fact that it took mankind literally thousands of years to figure out how to fly, in just a century we've gone from the Wright Flyer all the way to the Antonov An-225, the Airbus A380, the Boeing 747, the list is endless. I think the fact we got to the moon is pretty good to.
* '''What project are you working on right now?'''
I think you mean projects, in my case. I've actually got three on the go; all of which I am collaborating on (something I love with FlightGears community spirit). They are; the Airbus A350-900XWB in co-operation with Malik Guest (tehwarlock). The Jabiru J-170 (the aircraft I completed my "TIF" or Training Introductory Flight in) with Narendran Muraleedharan (Omega Pilot/Omega95) and Project Brisbane, perhaps the most ambitious, with Lachlan Bruce (spitfirebruce21), Drew Gibson (VH-TIT/FlightGearNZ) and Malik Guest (tehwarlock).
* '''What do you plan on doing in the future?'''
I actually don't know. I just hope I can develop my skills enough to contribute something really good to the FlightGear Project.'''
* '''Are you happy with the way the FlightGear project is going?
Overall; yes. Having come in the days of v2.0.0 and at one stage, using 0.9.0, it's blatantly obvious the progress that has been made in the year or so I've been actively involved in the community.
* '''On average, how much time do you spend working with/contributing to FlightGear?'''
A day? Hours. Note the plural form of the word. I don't have a number, as I'm frankly not pedantic enough to record, but I assume it'd scare me.
* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
Thorsten's Local/Advanced Weather; I use it everytime I fly. It's alot nicer visually then the "Global/Simple Weather" and I think it competes with FSX and REX.
* '''What do you enjoy most about developing for FlightGear?'''
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe.

'''[http://www.flightgear.org/contributors/ Read this and previous interviews at our website's archive].'''

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===
The Zivko Edge by Thorsten D was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling.

=== Liveries ===

== Scenery corner ==
=== Birds in FG ===
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. [[File:Sea_Gulls_2.png|thumb|]]

By attaching him, and variations of him, as sub-models to an invisible rotating base, You can have several seagulls circling above any model which has an .xml file.

There are 2 standard sub-model entries which can be added individually or together to an existing model’s .xml file. Each will add 4 Seagulls:
<model>
<path>Models/Fauna/SeaGull_Origin.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>15.0</z-m>
</offsets>
</model>
The above option is already available and the one below has been sent for inclusion in the model database, and should be available very soon.
<model>
<path>Models/Fauna/SeaGull_Origin_2.xml</path>
<offsets>
<x-m> 0.0</x-m>
<y-m> 0.0</y-m>
<z-m>20.0</z-m>
</offsets>
</model>

These entries can be altered to your own preference, or if you so wish you can alter the individual Seagull variations, which can be found in <tt>[[$FG_ROOT]]/Models/Fauna</tt>.

Who says we have to be serious all the time. Have fun. Enjoy.

VicMar

=== TerraGear ===
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official Terragear git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server.

== Aircraft of the month ==

"'Airport International Of Guarulhos (SBGR Sao Paulo)"

[[http://img836.imageshack.us/img836/2581/46118228348625173396710.jpg]]
[[http://img821.imageshack.us/img821/9606/40211614604300884940910.jpg]]

[[http://img31.imageshack.us/img31/2633/40897514604304551607210.jpg]]

http://www.youtube.com/watch?v=md05laSb79g

International Airport Of Guarulhos In Sao Paulo City Brasil

[http://www.grupofgbr.com.br/galeria#!__aeroportos Download Link]

== Airport of the month ==
== Screenshot of the month ==
FlightGear is going to simulate the effect of air pollution - with some air pollution, sunrise colors become a lot more spectacular, as demonstrated here by a DR-400 experiencing a sunrise flying close to Nice (France).

[[File:Dr400-nice.jpg|800px]]

== Suggested flights ==

=== Central Karakoram range ===
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high.

[[File:Karakoram1.jpg|300px|thumb|left|Circling Gasherbrum I]]

Take off from Skardu airport in Pakistan (OPSD). Skardu has a reasonably long (11,944 ft) runway at just 7,316 ft elevation, so you can take a jet, but for instance the Twin Otter is more stylish.

South of Skardu lies Deosai park, a famous high plateau, but we turn initially east. There's a chain of lakes which is the Indus river. After about five miles, the Shigar river merges with the Indus. Turn slightly left and follow the Shigar, then follow it into a long and broad lake-filled valley stretching into north-western direction.

Towards the end of the lake, a small tributary river, the Braldu, turns eastward out of the main valley. Follow the Braldu and start climbing (if you haven't done so yet). About 15 miles after turning into the Braldu river valley, two glacier-filled valleys stretch to the north - admire the view!

[[File:Karakoram2.jpg|300px|thumb|right|Heading back into Skardu, Nanga Parbat on the horizon]]

Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures!

A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem.

== Aircraft reviews ==

== Wiki updates ==
Throughout April, various aspects of the wiki have been changed or updated. The wiki software is now running the latest stable release, providing better security and usability. A side effect of this update is a bunch of new features.

Besides the update, several new extensions were installed.

Some of the most noticeable changes include:
* The '''upload wizard''' guides you through the process of uploading files. It provides an user interface to fill in the information template that we discussed in the previous newsletter edition. And should therefore help us archiving files in a way that they can be easily found back and used among the wiki and other places.
* Vector is the '''new default style''' of the wiki. It comes with a more advanced search box (moved to the top right of the page), showing suggestions of articles that you might be looking for.

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

== Community news ==
=== FlightGear on YouTube ===

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 04]]

File:Embraer - 195 em desenvolvimento (3)..jpg

2012-04-17T13:40:38Z

Wagner Silva:

=={{int:filedesc}}==
{{Information
|description={{pt|1=Este é o Embraer - 195, está sendo construindo pelo grupo FGBr.
Totalmente original.}}{{en|1=Embraer - 195, is being built by the group FGBr.
Totally original.}}
|date=2012-04-17
|source={{own}}
|author=[[User:Wagner Silva|Wagner Silva]]
|permission=
|other_versions=
|other_fields=
}}

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

File:Embraer - 195 em desenvolvimento (4)..jpg

2012-04-17T13:40:37Z

Wagner Silva:

File:Embraer - 195 em desenvolvimento (2)..jpg

2012-04-17T13:40:36Z

Wagner Silva:

File:Embraer - 195 em desenvolvimento..jpg

2012-04-17T13:39:18Z

Wagner Silva:

FlightGear Newsletter January 2012

2012-01-06T15:13:30Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
'''New airport of Congonhas - Brazil'''
Fully modeled from scratch. shortly in the '''www.grupofgbr.com.br'''[http://www.grupofgbr.com.br]
Stand by.

Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:12:23Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
'''New airport of Congonhas - Brazil'''
Fully modeled from scratch. shortly in the '''www.grupofgbr.com.br'''[http://www.grupofgbr.com.br]
Stand by.
[http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]
[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]
[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:11:04Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
'''New airport of Congonhas - Brazil'''
Fully modeled from scratch. shortly in the '''www.grupofgbr.com.br'''[www.grupofgbr.com.br]
Stand by.
[http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]
[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]
[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:09:17Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
'''New airport of Congonhas - Brazil'''
Fully modeled from scratch. shortly in the [http://www.grupofgbr.com.br]
Stand by.
[http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]
[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]
[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:07:38Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
'''New airport of Congonhas - Brazil'''
Fully modeled from scratch. shortly in the grupofgbr.com.br
Stand by.
[http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]
[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]
[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:05:59Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
'''New airport of Congonhas - Brazil'''
Fully modeled from scratch. shortly in the grupofgbr.com.br
Stand by.
[http:PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]
[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]]
[[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:04:22Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
New airport of Congonhas - Brazil
Fully modeled from scratch. shortly in the grupofgbr.com.br
Stand by.
[http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]
[[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]]
[[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:02:50Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
New airport of Congonhas - Brazil
Fully modeled from scratch. shortly in the grupofgbr.com.br
Stand by.
http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg
[[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]]
[[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T15:01:48Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
New airport of Congonhas - Brazil
Fully modeled from scratch. shortly in the grupofgbr.com.br
Stand by.
[[http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]]
[[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]]
[[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]]
Test New Airport of Congonhas (Grupo FGBR) Brazil
http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

FlightGear Newsletter January 2012

2012-01-06T14:59:58Z

Wagner Silva: /* Airport of the month */

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

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

== Development news ==

= Experiment: A new bounty system =

If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.
If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.
A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on here [[Bounty (Overview)]]

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* What is your forum nickname?

Hehe, guess once. ☺

* How long have you been involved in FlightGear?

Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* What are your major interests in FlightGear?
I like the open nature of the project and the possibility to contribute at various levels.

* What projects are you working on right now?
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* What do you plan on doing in the future?
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* Why is it that you are interested in flight simulation or aviation in general?
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* Are you happy with the way the FlightGear project is going?
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* What do you enjoy most about contributing to FlightGear?
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured our how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* Have you previously used other flight simulators or simulation software in general?
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* How does FlightGear compare in your opinion?
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* What was your first impression about FlightGear?
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* Do you think it is necessary to know how to program in order to contribute to FlightGear?
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* Have you ever used FlightGear professionally or for educational purposes?
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* What about FlightGear as a "game", do you think it can be used as such?
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* On average, how much time do you spend working with/contributing to FlightGear?
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* Which of the more recent FlightGear developments do you consider most interesting/appealing?
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* Is there some feature that you'd truly like to see in FlightGear one day?
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* What do you think could be done to attract even more new users and contributors to FlightGear?
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* Have you ever recommended FlightGear to other users, friends/family?
Not really, my friends and family aren’t really into flight simulation.

* Is there anything else you'd like to share with us?
Yeah, have a lot of fun, and if you can try to contribute something to the project.

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

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

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

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

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

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
The Netherlands have ca. 1800 windturbines at the moment. Since this month, 624 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. [http://www.w-i-n-d.nl A website] from the Dutch government has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
New airport of Congonhas - Brazil
Fully modeled from scratch. shortly in the grupofgbr.com.br
Stand by.
[[http://images.orkut.com/orkut/photos/PQAAAEDRVUTbnprQ2LaDEbwZUFwWX9apIASZ9uOvPGVInXZi_rc-B6wO3jChd52CqxcPO00gsaCgjDkPPKtLaFwVY74Am1T1UG3seeRLcCHamlDmnoG6LMmXWvhl.jpg]]
[[http://images.orkut.com/orkut/photos/OwAAAN8p1MNOFygUh--zrEpduKZieYVMwkjsT14rUpKL5my7hJ94jfExadrsuwdyLsECYeNher02iDCKBAxLOdNLK68Am1T1UK8e-cYk0WoLfRwRGxhntZfzRjpH.jpg]]
[[http://images.orkut.com/orkut/photos/PQAAAL_3Z_-jnpA7RWgEWrJ-jgMUzig3JxQpps1OXivf96oeMtMZPy6k5zGzBr6iiqiitKbm3sayiqs5WbisunrbdJsAm1T1UISdihQoi9G1fB0glVNNML3oZtja.jpg]]
Test New Airport of Congonhas (Grupo FGBR) Brazil
[[http://www.youtube.com/v/tUQCMTmQ-5Y?version=3&hl=pt_BR]]

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
* Day 10 - ?
* Day 11 - ?
* Day 12 - ?
|}

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

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

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

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

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]