FlightGear wiki - User contributions [en]

List of developed airports

2019-12-15T23:03:33Z

Anton: /* List of airports */ Fixed the Continent of CYYT

This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.

Airports can be listed here if these two conditions are fulfilled:
* At least one building or [[Signs|taxi signs]] have been placed
* Objects are represented in the [[FlightGear Scenery Database]].

Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.

A visual representation of the developed airports in FlightGear can be found at [http://www.iveze.nl/fgmap/ iveze.nl/fgmap/].

__TOC__

== For airport developers ==
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]].

== List of airports ==
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

{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment

|-
| CYGK || [[Kingston Norman Rogers]] || Canada || North America || Custom objects for all major buildings, including public terminal. (Buildings may not align with taxiways in default scenery, until it starts using the newest recommended airport data from X-Plane.)

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.

|-
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[AI Traffic]] and unique skyscrapers downtown

|-
| ED03 || Pohlheim Viehheide || Germany || Europe || Tower and buildings. Gliders often start from here.

|-
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects

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

|-
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects

|-
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

|-
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| EDDW || Bremen Airport || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFB || Reichelsheim Airport || Germany || Europe || Tower and buildings done

|-
| EDFE || Frankfurt Egelsbach || Germany || Europe || Tower,buildings,shared-models and incl. [[Signs]]

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

|-
| EDFO || Michelstadt Odenwald || Germany || Europe || Tower and buildings done

|-
| EDFQ || Allendorf-Eder || Germany || Europe || Tower and buildings done

|-
| EDGS || Siegerland Airport || Germany || Europe || Tower,buildings,shared-models and signs done

|-
| EDXW || [[Sylt Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 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]

|-
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled

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

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

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

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

|-
| EBBR || Brussels Airport || Belgium || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 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 ||

|-
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 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

|-
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

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

|-
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EGUL || RAF Lakenheath || United Kingdom || Europe || USAF military base, reasonably modeled.

|-
| EGUN || RAF Mildenhall || United Kingdom || Europe || USAF military base, reasonably modeled.

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

|-
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, busiest AI airport currently

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

|-
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

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

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

|-
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe ||

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

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

|-
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

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

|-
| KBOS || Boston Logan || USA || America || Fully modeled, plus unique buildings downtown

|-
| KFNT || Bishop Intl, MI || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lat=37.9858289&lon=-122.05529346000002&z=15 KCCR] || Buchanan Field Airport, Concord, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America ||

|-
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)

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

|-
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

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

|-
| KEQY || Charlotte-Monroe Executive Airport, NC || USA || America || Some buildings and aircraft using shared models

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

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

|-
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America ||

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

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

|-
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

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

|-
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America ||

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

|-
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.

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

|-
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

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

|-
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 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 ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 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 ||

|-
| [https://scenery.flightgear.org/map/?lat=33.80112251&lon=-118.34134126&z=15 KTOA] || Zamperini Field, Torrance, CA || USA || America || Fully modeled

|-
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully modelled

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

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

|-
| LEBB || Bilbao || Spain || Europe || Fully modeled

|-
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of terminal

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

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

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

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

|-
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| LIPA || [[Aviano Air Base]] || Italy || Europe || USAF military base, fitted with shared models.

|-
| LIPS || Aeroporto di Istrana || Italy || Europe || ItAF military base, fitted with shared models.

|-
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

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

|-
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery

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

|-
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-

| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings

|-

| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings

|-

| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America ||

|-
| 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 || Juancho E. Yrausquin Airport || Saba || America || Fully modeled

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

|-
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully modelled

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

|-
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, buildings, reference points and other POIs

|-
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || China || Asia || Terminals, control towers, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)

|-
| [https://scenery.flightgear.org/map/?lon=-52.7525&lat=47.618611&z=13 CYYT] || St. John's International Airport || Canada || North America || Convert from [https://gateway.x-plane.com/scenery/page/CYYT X-Plane Scenery Pack] that was released under the GNU General Public License.

|}

== Authors ==

Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ

Airports by D-ABBA:
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03

Airports by [[User:Laserman]]:
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ

== External links ==
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''

{{Suggested}}

[[Category:Lists]]
[[Category:Airports]]

List of developed airports

2019-12-15T23:02:06Z

Anton: Add the St. John's International Airport in the List of Airport section

This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.

Airports can be listed here if these two conditions are fulfilled:
* At least one building or [[Signs|taxi signs]] have been placed
* Objects are represented in the [[FlightGear Scenery Database]].

Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.

A visual representation of the developed airports in FlightGear can be found at [http://www.iveze.nl/fgmap/ iveze.nl/fgmap/].

__TOC__

== For airport developers ==
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]].

== List of airports ==
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

{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment

|-
| CYGK || [[Kingston Norman Rogers]] || Canada || North America || Custom objects for all major buildings, including public terminal. (Buildings may not align with taxiways in default scenery, until it starts using the newest recommended airport data from X-Plane.)

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.

|-
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[AI Traffic]] and unique skyscrapers downtown

|-
| ED03 || Pohlheim Viehheide || Germany || Europe || Tower and buildings. Gliders often start from here.

|-
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects

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

|-
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects

|-
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

|-
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| EDDW || Bremen Airport || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFB || Reichelsheim Airport || Germany || Europe || Tower and buildings done

|-
| EDFE || Frankfurt Egelsbach || Germany || Europe || Tower,buildings,shared-models and incl. [[Signs]]

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

|-
| EDFO || Michelstadt Odenwald || Germany || Europe || Tower and buildings done

|-
| EDFQ || Allendorf-Eder || Germany || Europe || Tower and buildings done

|-
| EDGS || Siegerland Airport || Germany || Europe || Tower,buildings,shared-models and signs done

|-
| EDXW || [[Sylt Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 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]

|-
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled

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

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

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

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

|-
| EBBR || Brussels Airport || Belgium || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 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 ||

|-
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 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

|-
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

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

|-
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EGUL || RAF Lakenheath || United Kingdom || Europe || USAF military base, reasonably modeled.

|-
| EGUN || RAF Mildenhall || United Kingdom || Europe || USAF military base, reasonably modeled.

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

|-
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, busiest AI airport currently

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

|-
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

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

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

|-
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe ||

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

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

|-
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

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

|-
| KBOS || Boston Logan || USA || America || Fully modeled, plus unique buildings downtown

|-
| KFNT || Bishop Intl, MI || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lat=37.9858289&lon=-122.05529346000002&z=15 KCCR] || Buchanan Field Airport, Concord, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America ||

|-
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)

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

|-
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

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

|-
| KEQY || Charlotte-Monroe Executive Airport, NC || USA || America || Some buildings and aircraft using shared models

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

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

|-
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America ||

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

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

|-
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

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

|-
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America ||

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

|-
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.

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

|-
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

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

|-
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 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 ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 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 ||

|-
| [https://scenery.flightgear.org/map/?lat=33.80112251&lon=-118.34134126&z=15 KTOA] || Zamperini Field, Torrance, CA || USA || America || Fully modeled

|-
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully modelled

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

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

|-
| LEBB || Bilbao || Spain || Europe || Fully modeled

|-
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of terminal

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

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

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

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

|-
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| LIPA || [[Aviano Air Base]] || Italy || Europe || USAF military base, fitted with shared models.

|-
| LIPS || Aeroporto di Istrana || Italy || Europe || ItAF military base, fitted with shared models.

|-
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

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

|-
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery

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

|-
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-

| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings

|-

| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings

|-

| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America ||

|-
| 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 || Juancho E. Yrausquin Airport || Saba || America || Fully modeled

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

|-
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully modelled

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

|-
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, buildings, reference points and other POIs

|-
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || China || Asia || Terminals, control towers, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)

|-
| [https://scenery.flightgear.org/map/?lon=-52.7525&lat=47.618611&z=13 CYYT] || St. John's International Airport || Canada || America || Convert from [https://gateway.x-plane.com/scenery/page/CYYT X-Plane Scenery Pack] that was released under the GNU General Public License.

|}

== Authors ==

Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ

Airports by D-ABBA:
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03

Airports by [[User:Laserman]]:
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ

== External links ==
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''

{{Suggested}}

[[Category:Lists]]
[[Category:Airports]]

Boeing 787-8 Dreamliner

2015-11-29T03:26:18Z

Anton: /* Downloading the 787-8 */

{{infobox Aircraft
|ready = aircraftmonth
|image = Boeing-787-8-splash.png
|name = Boeing 787-8 Dreamliner
|type = Airliner
|livery = Default: BOE, ANA, MIA ; The UVMap has not changed, so the old 787-8's liveries can also be used.
|liverydbid = 11
|fdm = JSBSim
|status = In Development
|authors = Omega95, Redneck, Awexome, Bicyus, ScottH1, Hooray, Zan, NickyIvyCA, Jentron, Thorsten, OT-666, Tikibar and Joshua Wilson (See Authors.txt for more info)
|fgname = 787-8
|status-fdm = 4
|status-systems = 5
|status-cockpit = 4
|status-model = 4
|download = http://wiki.flightgear.org/Boeing_787-8_Dreamliner#Downloading_the_787-8
|development = http://forum.flightgear.org/viewtopic.php?f=4&t=15333
}}
The '''Boeing 787-8 Dreamliner''' project was aimed at improving the systems and [[cockpit]] of the [[Boeing 787|old Boeing 787]]. Initially undertaken by Omega95 and Redneck, the project led to a major overhaul and redevelopment of the predecessor model, with only the main aircraft model and liveries yet to be modified. An interesting change and key feature of the new model is the impementation of a new [[Flight Dynamics Model]] based on the [[JSBSim]]. This was created using much data from [http://www.lissys.demon.co.uk/samp1/desmis.html -- the Piano tool]. Other interesting new features include the development of a 'cool' glass cockpit with highly detailed Boeing 787-8 instruments; and many advanced systems such as the Hydraulics, Pneumatics, Heating, Fuel System and Fly-By-Wire functionality.

The first trace of the project on the forum was from the development of the Boeing 787-8's CDU and since then, it has turned into a community project. A lot of developers and forum users have contributed to make this successful. Another key feature is that whenever findings or innovations have been made, they have gone on to the forum and soon, a lot of wiki HowTo tutorials have been created so that these may help other developers too.

=Innovations=

==New Control Display Unit==
[[File:Omega95-cdu-boeing-787-8.jpeg|300px|thumb|Boeing 787-8 Dreamliner Control Display Unit]]

A new [[Control Display Unit]] (CDU) specifically built for the Boeing 787-8 replaces the generic Boeing CDU and lets you control many of the configurations and settings on the aircraft like VNAV Cruise Settings, the flight plan (with VNAV altitudes,jump to, activate and remove features), Fly-By-Wire Configuration, Departure/Arrival Settings, Electronic Flight Bag (EFB) input etc.

The forum topic for the Boeing 787-8 CDU development can be found in [http://forum.flightgear.org/viewtopic.php?f=18&t=15082 this forum topic].

'''Functions Accessible through the Control Display Unit:'''
*Electronic Flight Bag Input
*Fly-by-wire Configuration
*Vertical Navigation Configuration
*Flight(plan) Management Computer
*Automatic Hold Configuration
*Set Terminal Procedures
*Flight Logging System
*Take-off and Approach Reference Speeds (keeps calculation according to weight)

==Vertical Situation Display==

[[File:Omega95-vsd-instrument.jpeg|300px|thumb|Boeing 787-8 Vertical Situation Display]]

A Vertical Situation Display [http://hoeprr.home.xs4all.nl/DreamHC/Download/B737_VSD_Briefing.pdf] is an instrument, part of the Navigational Display (on the MFDs) that show the aircraft's Vertical Navigation Altitudes, Vertical Profile and projects the terrain in front of you. In the Boeing 787-8, it shows approaching terrain for up to 50 miles and also color codes the terrain regions on the basis of danger (red - increase altitude immediately; orange/yellow - advisory; white - safe). The view the Vertical Situation Display, go to the NAV page on any of the MFDs. Note that the VSD is not available on the full-screen ND (NAV page on 2 adjacent MFDs). The VSD is uses a series of Nasal and XML files (which some core developers make like to call 'Hacks') to get functionality of hard coded instruments.

The forum topic for the Vertical Situation Display Development can be found here. [http://forum.flightgear.org/viewtopic.php?f=30&t=15200]
Hooray is also working on a Wiki HowTo on implementing the VSD in nasal. [[Howto: Implement a Vertical Situation Display in Nasal]]

==New Navigation Display==

The Boeing 787-8 features a new Navigation Display (ND) which features the ability to plot the waypoints and connect them, like in the real ND. [[User:zakalawe]] has been working on a hard coded version of such a display but as we didn't get it at the time, we designed this instrument completely with nasal and XML interactions. Another feature on the Boeing 787-8 is the ability to show a larger Navigation display when both pages are set to NAV on the co-pilot's side MFDs. The larger full screen MFD shows more waypoints and the range can be adjusted between 1 nautical mile and 250 nautical miles. It also shows the airport diagram of the nearest airport positioned and rotated in the right configuration and can be seen better when the range is less than 10 nautical miles.

Another feature of the Boeing 787-8's Navigation Display is a very functional TCAS (Traffic Alert and Collision Avoidance System) which has also been designed completely in Nasal and XML and does not require wxradar to work.

==Electronic Flight Bag==
Please also see [[Canvas EFB Framework]]

[[File:Omega95-efb-787.jpeg|300px|thumb|Boeing 787-8 Dreamliner Electronic Flight Bag]]

The Electronic Flight Bag (EFB) as the name says is like an electronic database of handy documents and charts. The Electronic Flight Bag on board the Boeing 787-8 can calculate the required amount of fuel for your flight, show any airport's (you can search using the EFB INPUT page on the CDU) information, like elevation, metar and runway information like heading, length, ILS frequency), connect to Virtual Star Alliance's Automatic PIREP System for more functionality, connect to Redneck's FGFSCopilot for logging, show the GPS settings (your position on the world map, course and true headings to your next way-point and distance to your next waypoint. It also has realistic checklists for every phase of the flight, and an operating manual explaining basic maneuvers. You can also "INSTALL" airport diagrams and charts into the '/787-8/EFB-DB' folder which allows you to view them on the CDU (searchable using the EFB INPUT page on the CDU).

===Quick Guide to install and view airport Diagrams===

> Download diagrams from any source, convert them to *.jpg format and rename them '<icao>.jpg'. Then, place them in the EFB-DB folder. Then, use the 'EFB INPUT' page on the CDU to enter the airport ICAO and it displays the diagram on the EFB.

===Quick Guide to install and view SIDs, STARs and IAPs===

* Download the chart you need from any source (I use http://www.airnav.com for US charts and http://www.opennav.com for others), and convert the chart to *.jpg format. (if it's pdf, a good idea is to open it in full view and take a screenshot :wink: )
* If the airport and chart type folder doesn't yet exist inside the EFB-DB/Charts folder, create them like (for example I want to install the 25L-ILS IAP chart for KLAX) /EFB-DB/Charts/KLAX/IAP/
* Now, rename your *.jpg file to the chart name (eg. 25L-ILS.jpg) and place it inside the '/EFB-DB/Charts/KLAX/IAP/' folder.
* Now, open the /EFB-DB/ChartsList.xml file and add in your chart data (use the older charts' data for the format)
* Start up the 787, go to the 'Airport Charts' page on the EFB, go to the 'EFB INPUT' page on the CDU and
** Enter the Airport ICAO and press on the button next to 'Airport ICAO (Enter)' label (or the space under it on the touch-screen CDU)
** Click on the button next to the 'Chart Type (Select)' label to cycle through SID, STAR and IAP
** Click on the button next to the 'Chart ID (select)' label to cycle through available charts.
** Now, hit the 'DISPLAY >' button on the CDU and look at the EFB to see your chart.

Note that for some charts, the orientation may be land-scape and not portrait. But to overcome that, I've put a 'ROTATE' option on the EFB which rotates the chart when you click it.

''The Above has been taken from the forum topic.''

===''Third-Party'' EFB Software===

The Electronic Flight Bag is also meant to provide and interface third-party and/or operating airline softwares. These are not present in the Flight Management Computer by default but we're working on a couple of ''softwares'' for the EFB. This is not ''unrealistic'' because this is one of the main purposes of the Electronic Flight Bag. Here're the ''softwares'' we're working on for the EFB.

====FGFSCopilot Logger====

The [[FGFSCopilot]] is a java program that can do almost everything required from taking off till landing the plane at your destination. The Boeing 787-8 has an FGFSCopilot Log page in the EFB which shows it's connection status and every log message the FGFSCopilot sends to FlightGear.

====VNAV Automatic Altitudes Generator====

The VNAV AutoGen is a third party software on the EFB that automatically calculates ideal vnav altitudes for the active route. To use it, simply create/load a flightplan, copy it to the active route, go to the VNAV Altitudes Gen page on the EFB and click on ''AUTOGEN >''. That would generate altitudes for you which're displayed on the EFB. You can scroll through the waypoints using ''SCROLL UP >'' and ''SCROLL DOWN >''. Finally, if you're happy with the automatically generated altitudes, click on ''COPY TO RTE >'' to move them to the active route.

==Fly-By-Wire System==

The Boeing 787-8 Dreamliner is FlightGear's first Airliner to feature a complete Fly-by-wire system. The idea behind this fly-by-wire is to get it the pilot's controls (/fdm/jsbsim/fcs/x-cmd-norm : where x can be aileron, rudder or elevator) and work with it and give out another output property (/fdm/jsbsim/fcs/x-fbw-output) which is read by the FDM and control surface animators. The throttles don't have a chain such as the other surfaces so that the pilot can easily override the fly-by-wire (one of Boeing's "philosophies"). At this stage, the fly-by-wire can protect the aircraft from extreme bank angles (flight envelope protection- roll) where the bank angle limit can be set by the pilot in the CDU's 'FBW CONFIG' page, protect the aircraft from extreme alpha angles (flight envelope protection- alpha), calculate the throttle required and set it accordingly to maintain profile on turns, reduce throttle to stay under limits and finally auto-stabilize the plane and maintain the current profile when the yoke is brought back to the center. The Fly-by-wire also dampens the control to prevent any sudden motion. Fly-by-wire can be toggled from the CDU's 'FBW CONFIG' page.

NOTE : To be able to activate alpha-protection, roll-protection and auto-stabilizer, you need to be atleast higher than 3500 feet. This is so that the fly-by-wire doesn't interrupt your approach.

We've also created a tutorial which shows how you can implement the fly-by-wire we wrote for your aircraft : [[Howto: Implement a Fly-By-Wire System for Airliners]]

==Automatic Vertical Navigation==

I've seen a lot of wiki pages on aircraft autopilot and always noticed that next to 'VNAV -' the author writes either he doesn't know what it is, or it doesn't do anything or he hasn't tested it yet. Well, for a change, here I'm telling you what the VNAV does.

We have designed the autopilot route manager in the CDU to be able to accept VNAV altitudes for each (or whichever you want) waypoint. On the Dialog Route Manager, enter your waypoint in the format 'WP@ALT' for example, 'KSFO@9000'. So let's say you have different altitudes according to your SID/STAR/IAP till cruise altitude and then different altitudes for your waypoints when you land. Let's assume your flight plan to be:
DEP, WP1@3500, WP2@10000, WP3@18000, WP4@26000, WP5, WP6, WP7, WP8, WP9, WP10, WP11@20000, WP12@12000, WP13@8500, WP14@4000, DEST

You doesn't have to enter altitudes for WP5 to WP10 because you'll start cruising at WP5 (say you want to cruise FL360 aka. 36000 ft) and stay at 36000 ft till WP10. That means WP11 will be your 'End Cruise' Waypoint, where you aim at when you're out of the cruise.

To set cruise settings, go to the CDU's 'VNAV' page and enter cruise altitude in the respective area. Then enter your cruise start altitude (in this case, WP5) and cruise end altitude (in this case, WP11) in their respective places (there're labels).

Once you're ready, finish other checklists, take off and turn on 'LNAV' and 'VNAV' on the Autopilot. The VNAV is designed to automatically calculate the required/ideal climb/descent rate to get to your waypoint just in time. Out of all the tests we've conducted, the VNAV is VERY accurate at the moment.

==Flight-plan Management System==

[[File:787-8-fpm.jpeg|300px|thumb|Boeing 787-8 Flightplan Manager]]

In the Feb 25th, 2012 git commit, a new flight-plan management system has been written for the Flight Management Computer(s). The new system, like the real one lets you put in 2 flight-plans (with altitudes), and an alternate airport. You can do everything that you can to the route manager on these 2 flightplans. Boeing likes to call them '''Primary Flightplan''' and '''Secondary Flightplan'''. Once you enter your primary and/or secondary flight-plan, the respective flight-plan's status will show ''READY'' on the flight-plan management page. Then, a new option, ''COPY TO RTE'' will appear under the respective flight-plan and on clicking that, that plan will be moved to the active route. To make any changes to the route, you can either make them to the flight-plan and copy them to the route again or simply work with the active route by clicking on the '''ACTIVE ROUTE''' option in the Flight-plan Management page. An alternate airport is recommended to be entered in the CDU so that in case there's a problem during flight, the plane can be automatically be diverted (by the FMC) without you having to do anything other than pressing the ''DIVERT'' option on the Flight-plan management page. Note that using the ''DIVERT'' button to divert to your alternate airport clears your active route and sets the aircraft on a direct flight to the Alternate Airport.

==Automatic Holding Pattern==

[[File:Boeing-787-8-auto-hold.jpeg|300px|thumb|Boeing 787-8 Automatic Holding as seen in the FlightGear Tracker]]

The Boeing 787-8 now features an automatic holding pattern system where you enter the hold fix/navaid, hold radial and hold leg time and the aircraft automatically, flies in a holding pattern there. (as described in real Instrument Flight Rules Rating Course (IFR) textbooks) This feature is still being developed at the moment and is not perfected, but it still does the basic thing for you.

We have tested this feature from KIAH (George Bush Intercontinental Airport, Houston) holding at the VOR, LOA (LEONA VORTAC, about 70 miles north-west of KIAH) at a hold radial of 0, and hold leg time 120 seconds. We've been able to hold and re-trace the hold path every lap, but we get a strange shape due to the pid-controller. We're still working on it.

==Traffic Alert and Collision Avoidance System==

[[File:787-8-TCAS.jpeg|300px|thumb|Boeing 787-8 Dreamliner TCAS]]

The Boeing 787-8 Dreamliner (as of February 21st, 2012 on GIT) features a brand new TCAS (Traffic Alert and Collision Avoidance System) which has a capability of showing 30 Multiplayer aircraft and 20 AI Aircraft on it! Now, you won't have to complain about not seeing all aircraft on VATSIM ;) We're still working on increasing it's capability to 50 each multi-player and AI.

The TCAS has 3 different symbols for each aircraft and 4 different color codes. Each aircrafts' callsign, altitude and true airspeed will also be written next to the sprite.

*The '''Diamond Shaped''' Aircraft sprite shows that the aircraft is ''flying level''.
*The '''Box with Up Arrow''' shows that the aircraft is ''climbing''.
*The '''Box with Down Arrow''' shows that the aircraft is ''descending''.

*A '''Cyan or Blue''' Colored Sprite shows that the aircraft is at a safe distance.
*A '''Yellow''' Colored sprite shows that you need to be aware of traffic nearby.
*A '''Orange''' Colored sprite shows that you need to either change altitude or course, consult ATC. It is an advisory.
*A '''Red''' Colored sprite shows that you are in danger and immediately need to follow the TCAS instructions.

The TCAS is configured to sound voice alerts according to the situation. The TCAS voice alerts needs to be followed over the ATC's instruction if they contradict. The TCAS will alert you if you are in danger of collision with MP or AI Aircraft.

''NOTE: The TCAS voice alerts have been confirmed working on FlightGear git (2.7, as of February 19th, 2012) but don't seem to work in FlightGear 2.4.''

==Terrain Map and Weather Radar==

[[File:787-8-terrain-map.jpeg|300px|thumb|Boeing 787-8 Dreamliner Terrain Map]]

The Boeing 787-8 Dreamliner (git version as of February 21st, 2012) features a terrain radar which creates a terrain map on the MFD when the Navigational Display is set to TERR mode (you can change the mode from the buttons on both sides of the Mode Control Panel). Click on WXR to view the WXRadar (Collins WXR-2100), TERR to view the Terrain Map and CLR to clear the ND. The weather radar is still under development and a working version is not available, but the terrain map uses a 'get little and interpolate' method to create smooth terrain mapping.

==World Map and Flight Path Plotter==

[[File:787-8-wmap.jpeg|300px|thumb|Boeing 787-8 Satellite Imaging]]

Another option to put on the ND is the world map. It's not exactly a terrain map, but rather like satellite imaging. The plane is shown (it's zoomed in) on the map and the plane's path is marked with fading red dots. You can get your ND to show the satellite maps by pressing the WMAP button on the ND mode panel. Note that you can have any 1 of WXR, TERR or WMAP on and to remove them, press the 'CLR' button.

==Airline Flight Management Computer==

[[File:787-8-fmc.jpeg|300px|thumb|Boeing 787-8 Flight Management Computer - FLIGHT INFO]]

The Boeing 787-8 Dreamliner is an Airliner and we can't leave out some of the key features airline manufacturers put in their aircraft. There're 2 major sections in the Flight Management Computer (it's a part of the CDU) - the ROUTE and DEP/ARR. Both pages are accessed from the CDU(s). The Route is directly connected to the Route Manager and doesn't do anything 'special', but the DEP/ARR page lets you work with preset routes, SIDs, STARs, IAPs etc. You can enter the flight number (this is meant for virtual airlines: By default, Merlion's Boeing 787-8 Routes are included in the Database but I'll make a tutorial on how other airlines can put in their data) and be able to search for the flight information. If the airline has specified a Route and/or VNAV Altitudes and Configuration, you can load up those preset routes and altitudes by pressing the 'SET ROUTE >' menu. If a preset route doesn't exist, the FMS will generate a route automatically. A pilot does not have to worry about preset/generated routes. Another feature in the FMC is Scott Hamilton's LevelD-767 NAVDATA Parser, which gets SID/STAR/IAP Data and automatically puts them in the right place in the route manager for you to be able to fly them. This data can be managed from the PROCEDURES option in the DEP/ARR page.

''A much more detailed tutorial of how to use preset routes and automatically set terminal procedures is available in the wiki sub-page: [[Boeing 787-8 Dreamliner: Flightplan and Procedures Tutorial]]''

''We'll also be creating a video tutorial (Dreamliner Tutorial #6) on the Flight Management Computer.''

===FMS Navigational and Terminal Procedures Data===

The Boeing 787-8 Dreamliner and the Airbus A380 (being developed by Scott Hamilton) uses Scott's Level-D 767 NAVDATA Parser to get Navigational Data and Terminal Procedures into the aircraft's Flight Management Computer (Flight Management System on the A380). The FMS Data can be downloaded as an extractable '''*.exe''' file from http://www.filestube.com/source.html?token=f6f36bf2e8d20ecb03ea but we also have FMS Data files for individual airports on Git with the Boeing 787-8 Project. Download specific Airport NavData XML files from the source tree of the ''git://gitorious.org/fg-boeing-787-8/fms-data.git'' repository. You can also download master as a '''*.tar.gz''' from https://gitorious.org/fg-boeing-787-8.

By default, the 787-8 contains navigational data for the following airport - WSSS, YBBN, KLAX, KJFK, EGKK for testing purposes and as the Flight Management Computer Tutorial is a flight from KLAX to KJFK.

== Work on the C++ front ==
The capabilities provided by this aircraft touch many parts of FlightGear, that will benefit from modifications to the C++ code, this is an attempt at documenting useful C++ work. Most of this should probably be posted to the issue tracker, too.

===Camera/Video Surveillance Instrument===

The Aircraft doesn't 'yet' have a camera/video surveillance instrument but the team is working on it. We are creating a Wiki [[Howto: Use a Camera View in an Instrument]] while working on it so our progress can help other aircraft developers. The basic idea is the render the camera view to texture and get flightgear to display it on the instrument. As this instrument includes work in C++, it will NOT be available in FlightGear 2.4.0 or 2.6.0, and not even git at the moment.

=== Creating a 2D drawing API ===
Also see [[Howto: Create a 2D drawing API for FlightGear]].

=== Increasing the range of geodinfo() ===

Fix geodinfo() so that it may provide access to tiles not yet loaded, i.e. tiles that are not "visible" (which is the limiting factor currently). This will also be useful for the local weather system and probably a number of related scripts.

{{cquote|The tile manager is capable of satisfying multiple requests. Anyone can give it a position, range and a timeout. It will then try to load all tiles in the range specified. And it will stop loading them after the timeout - unless you have updated the request with a new timeout. So you could tell it every 5 seconds that you're interested in a certain area around the aircraft, and use a timeout of 5,01 seconds. A matter of memory and loading speed though.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33348.html |title=Future Weather System |last=Brehm |first=Thorsten |work=FlightGear-devel mailinglist |date 1 August 2011}}</ref>|Thorsten Brehm}}

=Glass Cockpit=

[[File:Omega95-cockpit.jpeg|300px|thumb|Boeing 787-8 Glass Cockpit]]

The Boeing 787-8 Dreamliner has a very complete and realistic modern glass cockpit based of the real Boeing 787-8 cockpit. Almost all of the instruments (excl. Weather radar which is currently coming up, and the voice comm.) are functional and work like the real thing. Multiple views have been created (like the OHP, CDU, EFB, Full Cockpit Views) so that pilots can easily work on different parts without looking away and adjusting view position.

That's all I can say about the cockpit now... You better test it out to judge it.

=Systems Overview=

==Electrical System==

The Boeing 787-8 Dreamliner uses a modified version of Syd Adam's Jet Electrical System. Backup Generators have been added, a Ram Air Turbine Generator has been implemented and the APU loop has been modified. There are 5 major power sources available are:
* Engine Generators (L1 and R1 are main generators and L2 and R2 are backup)
* Battery
* Primary and Secondary External Power
* APU Generators (Auxiliary Power Unit must be started and running for the APU Generators to provide power)
* Ram Air Turbine (used in case of dual engine failures to provide just enough power for Central Hydraulic Systems (C1 and C2) and Instruments.

To Understand the Electrical System better, take a look at the 'ELEC' page on any of the MFDs on board.

==Hydraulic System==

The Hydraulic System on-board is very advanced and does the job it's supposed to do.
There are 3 basic Hydraulic Systems - Left Engine Hydraulics, Right Engine Hydraulics and Central Electrical Hydraulics. Both Left and Right Engine Hydraulic Systems are pressurized by Engine pumps which require the engines to be running. These pumps pressurize the L and R systems that are connected to the flaps, spoilers, brakes and landing gears. Therefore, you need atleast 1 of the 2 Engine pumps to be running to be able to use these. But, the landing gear has an 'alternate gravity drop system' which you can use to get your gear down in case of a hydraulic failure.
The Central System has 2 electric pumps that control pressure to the hydraulic system that controls the ailerons, rudder and elevators. Only 1 of the 2 pumps have to be turned on at a time, and the other can be used as backup in case of a failure. The hydraulic pumps can overheat and fault if not adequately cooled, refer to the 'Pneumatics and Air Conditioning System' for more information on this.

To Understand the Hydraulic System better, take a look at the 'HYD' page on any of the MFDs on board.

==Pneumatic System==

The Boeing 787-8's pneumatic and Air-conditioning system controls bleed and flow of air through packs (and trim) which are then used to cool the equipment on board. The pneumatic system is pretty simple, you have 2 packs, 2 trim air controls, a gasper, and engines and APU bleed. The 787's systems automatically control bleed according to what is required and available, but you'll have to control the trim and packs. Equipment Cooling is an option on the Pneumatics panel which passes cool air into the hydraulic and fuel pumps to prevent them from overheating. When a pump overheats, you get a warning and if you do not either turn it off or switch on equipment cooling, the pump can fault. The 'PNEU' page on the MFDs show you more information on equipment temperatures and Pneumatic settings.

==Fuel Control System==

The Fuel Control System let's you control the 7 fuel pumps on board the 787-8 Dreamliner (2 Left Tank Pumps, 2 Central Tank Pumps, 2 Right Tank Pumps and a Crossfeed pump). The left tank and central tank pumps pump fuel from these tanks to the left engine, while the right tank and central tank pumps pump fuel from these tanks to the right engine. In case of a fuel imbalance, you can turn on the crossfeed pumps to transfer fuel from the tank with excess fuel to the one with low fuel.

===Fuel Jettison===

The Aircraft has a complete fuel jettison system where you can select which wing nozzle to jettison from, arm jettison and use a knob to define the dump rate. If the Left Nozzle is activated and Fuel Jettison is armed, you dump fuel from the left and central tanks, and the same for the right nozzle. Note that the 787 will NOT let you dump fuel if you have less than a critical value.

==Heating System==

[[File:Omega95-window-heating.jpeg|300px|thumb|Ice starts building up on the windows if temperature is sub-zero and window heating is turned off.]]

The Heating System on board controls 4 different heating equipment. First of all, let's get into "natural icing".

===Natural Icing at certain Conditions===

If your TAT (Total Air Temperature) value is under 10, your wings, engines and wind shield can start picking up ice. Window Ice simply forms on the window and obstructs your view out of the cockpit. Whereas, wing ice actually affects your lift and drag in the FDM! As for engine ice, if you have extremely high amounts of ice, the engines can fault and you might have to cool and then restart them.

Note that Engine surges are NOT due to ice build up. If you get an engine surge while flying, you might either be flying over Vne, or in extreme weather conditions with N1 above safe limit in those conditions.

===The Aircraft's way of Taking care of Ice===

The '''Window Heating''' switches on the overhead panel enables a heater to start melting the ice on the windshield letting you see outside clearly.

The '''Anti-Ice''' knobs (2 engine knobs and a wing anti-ice knob) let you control the heating equipment on the respective areas.

The 'HEAT' page on the MFD should have more information on the Heating Systems.

==Gear System==

The Boeing 787-8 dreamliner has 3 retractable gear units, the nose gear has 2 tires, and the main landing gears have 4 each in a square layout. The gear system manages gear compression and failures (stuck, tires burst and break off) on the basis of airspeed, wow and compression.

The gears system can be monitored from the 'GEAR' page on the MFD(s).

==Ground Service Controls==

[[File:787-ground.jpeg|300px|thumb|Boeing 787-8 Ground Service Controls]]

[[File:787-ground_1.jpeg|300px|thumb|Boeing 787-8 Ground Services (Right)]]

[[File:787-ground_2.jpeg|300px|thumb|Boeing 787-8 Ground Services (Left)]]

===Fuel Truck===

The fuel truck (MENU: Boeing 787-8 > Fuel Truck Controls) can be enabled/disabled and connected/disconnected from the aircraft's fuel value under the wing. You can enter an amount of fuel in the request fuel quantity input and ask the truck to re-fuel the aircraft to that quantity. You can also ask it to drain the fuel tanks.

===De-icing Truck===

The de-icing truck along with the other ground services can be controls from the ''Ground Services Controls'' menu (MENU: Boeing 787-8 > Ground Services Controls). The de-icing truck can be enabled/disabled and you can also de-icing the aircraft. The de-icing process includes the truck animations and actually de-icing the aircraft!

===External Power Box===

The External Power box is a stand-alone generator that provides external power to the aircraft. When enabled, it is connected to the external power socked under the aircraft's left wing. Note that this needs to be enabled so that you get external power. When you start FlightGear, the external power will be enabled by default.

===Landing Gear Chokes===

Landing Gear chokes are triangular prism shaped blocks that're placed in front of and behind the landing gears to prevent the aircraft from moving. These chokes will also prevent the aircraft from moving in FlightGear and are enabled by default on start up. Note that to get the aircraft moving, you need to remove the parking brakes and chokes.

===Catering Truck===

The catering truck can be enabled/disabled and toggled. The ''Toggle Catering'' option is to lift/lower the catering box and connect to the the R1 Door. It doesn't do anything else.

===Baggage Ramp and Trailers===

These're just models and don't do anything at the moment.

==System Failure Simulation==

[[File:787-failures.jpeg|300px|thumb|Boeing 787-8 Failure Simulator]]

The aircraft has a built-in failure simulation dialog where you can get different systems to fail in different ways. The failure simulation dialog can do the following:
* Flame-out any of the engines
* Fail any of the engines
* Set any of the engines on fire
* Burst any of the Wheel Tyres
* Have a gear unit ''break-off''
* Stuck a gear unit in it's current position
* Fail individual hydraulic systems
* Overheat any of the hydraulic or fuel pumps
* Fault any of the hydraulic or fuel pumps

Other general failures like Electrical, Static etc. have not been implemented in this dialog as they can already be controlled with FlightGear's Generic System Failures dialog.

''NOTE: When you flame-out an engine, it can be restarted, but not in the case of a failure. Faults just means that the pump is too hot to function, but it can be restarted when cooled.''

'''IMPORTANT!'''
*In case of an engine surge, (this cannot be toggled by user as it requires certain weather conditions and N1 to occur) immediately reduce throttle and get the N1 under 65%. If you're flying too fast, try to slow down and avoidance extreme weather (heavy rain and snow) would be a nice idea if you want to prevent surges.
*In case of an engine fire, pull the respective engine's fire extinguisher lever (it's right behind the throttle quadrant) and cutoff fuel to that engine. If the fire persists and you don't extinguish it, the engine may face an explosion and severe damage will be inflicted, leaving that engine unusable (basically, you can't restart it)

=Virtual Copilot=

Johan G posted in the Boeing 787-8 Dreamliner Forum Topic:
''I really see why there could be a real need to have a copilot along when "flying in" the aircraft during pilot conversion.''

Basically, the systems are very complex that it might be difficult for just 1 person to control the plane and manage the systems. As an immediate solution, the virtual copilot can announce ref. speeds, control flap lever, control gear lever, control heating and pneumatics, set altimeter setting and engage thrust reverser's and spoilers on touchdown. You can select exactly what you want ''him'' to do in the Virtual Copilot Settings Dialog.

On the other hand, we're working on a new advanced dual control system which allows the copilot to completely control the aircraft and see all instruments over multiplayer.

=Downloading the 787-8=

The Boeing 787-8 Dreamliner is hosted in GIT and has been made into different kinds of releases so that users can download it according to what they need. In the Boeing 787-8's Git Project page [https://github.com/omega95-aircraft/fg-boeing-787-8], you can find 3 different Repositories:

==fg-boeing-787-8-main==

This is the main Aircraft repository on GitHub. It includes the bleeding edge version (''master'' branch), and different types of releases of the latest stable version (''stable_d'', ''stable_e'', and ''stable_f'' branches).

===master ''Bleeding Edge''===

The '''master''' branch on the fg-boeing-787-8-main repository contains the latest development version of the Aircraft. This contains everything that's there in the
authors' aircraft folder from when a commiter last pushed his changes.

'''Download master as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/master
 
'''Download master as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/master</del>

===stable_d ''Default Database''===

The '''stable_d''' branch (''d'' for ''default database'') contains the latest stable release with the selected airport diagrams, charts and FMC navigation data. This is recommended for everyone but you can get the other releases according to your needs too.

'''Download stable_d as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/stable_d
 
'''Download stable_d as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_d</del>

===stable_e ''Empty Database''===

The '''stable_e''' branch (''e'' for ''empty database'') contains the latest stable release of just the basic aircraft, including models, nasal, systems etc. but the EFB and FMC databases are empty. This is recommended for those with slow internet connections. If you get a better connection later, you can download the whole database only from the ''fg-boeing-787-8-data'' repository.

'''Download stable_e as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/stable_e
 
'''Download stable_e as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_e</del>

===stable_f ''Full Database''===

The '''stable_f''' branch (''f'' for ''full database'') contains the latest stable release of the aircraft, default diagrams and charts and the complete FMC Datbase. This release especially features FMC navigation data for 3808 airports (all we have so far)! It's recommended only if you have a very good internet connection. (WARNING! 280+ MB)

'''Download stable_f as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/stable_f
 
'''Download stable_f as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_f</del>

==fg-boeing-787-8-data==

The Data Repository contains all the available EFB and FMC Database files. All these files are also included in the ''stable_f'' releases, so if you have a ''stable_f'' release, you don't need to worry about this.

'''Download master as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-data/archive-tarball/master

==fg-boeing-787-8-devel==

If you're interested in helping develop this aircraft and join the team, you can download the files in this repository. These are not required for the running of the aircraft but include some files like wxradar files, dual control files etc.

'''Download master as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-devel/archive-tarball/master

==Cloning and Pulling==

Cloning and Pulling the 787-8 repositories are the same like every other git repository, including FlightGear. Once you clone/pull, you can select the branch you want using ''git checkout <master/stable_d/stable_e/stable_f>''

More information on using git is available at [[FlightGear And Git]].

=Aircraft of the month!=

{{#ev:youtube|WlzEoCsJvz4|480|center}}

Thanks to Oscar [http://www.youtube.com/user/osjcag] for the amazing ''Aircraft of the Month Review Video'' for the Boeing 787-8 Dreamliner.

=Boeing 787-8 Wiki Sub-Pages=

* [[Boeing 787-8 Dreamliner: Operating Manual and Checklists]]
* [[Boeing 787-8 Dreamliner: Video Tutorials]]
* [[Boeing 787-8 Dreamliner: Control Display Unit Reference Manual]]
* [[Boeing 787-8 Dreamliner: Flightplan and Procedures Tutorial]]

=Aircraft Status and ToDo List=

==Flight Dynamics Model: 4==

* The Boeing 787-8 has a JSBSim FDM matching a lot of results from http://www.lissys.demon.co.uk/samp1/desmis.html
* We don't have more detailed test results. so we can't test everything yet. Once we get that, we need to tune the FDM further.

==Aircraft Systems: 5==

* The Aircraft has very advanced systems imitating realistic systems from the real 787.
* Random/Checkable Failures purposely haven't been implemented as random is never realistic. But Engine failures, ice etc. occur in the appropriate conditions.
* The 787-8 has very advanced instruments, flight management computer, hydraulic, electric, pneumatic, heating, fuel etc. systems.

==Cockpit and Instruments: 4==

* The cockpit is very detailed and most buttons are there and functional.
* The instrument displays are very advanced and functional, the ND could be replaced by a hard coded version though.
* A Camera View instrument is supposed to be there but isn't, but we're working on a hard coded camera view instrument.
* The aircraft uses textures extracted from pictures and ambient occlusions created with blender.
* The complete cockpit has been light-mapped and looks very good at night too.

==Model: 4==

* The model is still from the old 787-8, there's the basic model without a cabin, rods aren't yet complete either.
* The landing gears have been re-done and look a lot better now, but the model has a much better scope of improvement.
* The Model Rating has been taken right out of the old Boeing 787-8

=Related content=
There are plenty of tutorials and code snippets that were specifically created for this project, this is a list of all things related:

{{Appendix|all|
* {{Cite web|url=http://www.bristol.ac.uk/aerospace/msc/avadi/units/projects/ub2009f/group7/7878summarysheet.pdf |title=787-8 Summary Sheet |date=21 January 2009 |publisher=Department of Aerospace Engineering, University of Bristol }}
* {{Cite web|url=http://www.wpafb.af.mil/shared/media/document/AFD-090121-023.pdf |title=The Boeing 787 Aircraft |work=Air Force HSI |publisher=Wright-Patterson Air Force Base }}
* {{Cite web|url=http://www.boeing.com/commercial/aeromagazine/articles/qtr_4_07/AERO_Q407.pdf |title=AERO Quarterly |date=2007 |publisher=Boeing}}
----
{{references}}

'''Weather radar (wxradar)'''
* {{Cite web|url=http://www.smartcockpit.com/data/pdfs/flightops/aircraft/Collins_WXR-2100_Operator%27s_Guide.pdf |title=Collins WXR-2100 MultiScan™ Radar Fully Automatic Weather Radar |date=2003 |publisher=Rockwell Collins }}
* {{Cite web|url=http://www.ll.mit.edu/publications/journal/pdf/vol12_no2/12_2weatherradar.pdf |title=Weather Radar Development and Application Programs |last=Evans |first=James E. |coauthors=Weber, Mark E. |date=2000 |work=Lincoln Laboratory Journal}}
}}

[[File:787-8-cockpit-panorama.jpeg|800px|Panoramic View of the 787-8 Dreamliner Cockpit]]
{{boeing}}

[[Category:Airliners]]

Boeing 787-8 Dreamliner

2015-11-29T03:19:55Z

Anton: /* fg-boeing-787-8-main: Updated repository */

{{infobox Aircraft
|ready = aircraftmonth
|image = Boeing-787-8-splash.png
|name = Boeing 787-8 Dreamliner
|type = Airliner
|livery = Default: BOE, ANA, MIA ; The UVMap has not changed, so the old 787-8's liveries can also be used.
|liverydbid = 11
|fdm = JSBSim
|status = In Development
|authors = Omega95, Redneck, Awexome, Bicyus, ScottH1, Hooray, Zan, NickyIvyCA, Jentron, Thorsten, OT-666, Tikibar and Joshua Wilson (See Authors.txt for more info)
|fgname = 787-8
|status-fdm = 4
|status-systems = 5
|status-cockpit = 4
|status-model = 4
|download = http://wiki.flightgear.org/Boeing_787-8_Dreamliner#Downloading_the_787-8
|development = http://forum.flightgear.org/viewtopic.php?f=4&t=15333
}}
The '''Boeing 787-8 Dreamliner''' project was aimed at improving the systems and [[cockpit]] of the [[Boeing 787|old Boeing 787]]. Initially undertaken by Omega95 and Redneck, the project led to a major overhaul and redevelopment of the predecessor model, with only the main aircraft model and liveries yet to be modified. An interesting change and key feature of the new model is the impementation of a new [[Flight Dynamics Model]] based on the [[JSBSim]]. This was created using much data from [http://www.lissys.demon.co.uk/samp1/desmis.html -- the Piano tool]. Other interesting new features include the development of a 'cool' glass cockpit with highly detailed Boeing 787-8 instruments; and many advanced systems such as the Hydraulics, Pneumatics, Heating, Fuel System and Fly-By-Wire functionality.

The first trace of the project on the forum was from the development of the Boeing 787-8's CDU and since then, it has turned into a community project. A lot of developers and forum users have contributed to make this successful. Another key feature is that whenever findings or innovations have been made, they have gone on to the forum and soon, a lot of wiki HowTo tutorials have been created so that these may help other developers too.

=Innovations=

==New Control Display Unit==
[[File:Omega95-cdu-boeing-787-8.jpeg|300px|thumb|Boeing 787-8 Dreamliner Control Display Unit]]

A new [[Control Display Unit]] (CDU) specifically built for the Boeing 787-8 replaces the generic Boeing CDU and lets you control many of the configurations and settings on the aircraft like VNAV Cruise Settings, the flight plan (with VNAV altitudes,jump to, activate and remove features), Fly-By-Wire Configuration, Departure/Arrival Settings, Electronic Flight Bag (EFB) input etc.

The forum topic for the Boeing 787-8 CDU development can be found in [http://forum.flightgear.org/viewtopic.php?f=18&t=15082 this forum topic].

'''Functions Accessible through the Control Display Unit:'''
*Electronic Flight Bag Input
*Fly-by-wire Configuration
*Vertical Navigation Configuration
*Flight(plan) Management Computer
*Automatic Hold Configuration
*Set Terminal Procedures
*Flight Logging System
*Take-off and Approach Reference Speeds (keeps calculation according to weight)

==Vertical Situation Display==

[[File:Omega95-vsd-instrument.jpeg|300px|thumb|Boeing 787-8 Vertical Situation Display]]

A Vertical Situation Display [http://hoeprr.home.xs4all.nl/DreamHC/Download/B737_VSD_Briefing.pdf] is an instrument, part of the Navigational Display (on the MFDs) that show the aircraft's Vertical Navigation Altitudes, Vertical Profile and projects the terrain in front of you. In the Boeing 787-8, it shows approaching terrain for up to 50 miles and also color codes the terrain regions on the basis of danger (red - increase altitude immediately; orange/yellow - advisory; white - safe). The view the Vertical Situation Display, go to the NAV page on any of the MFDs. Note that the VSD is not available on the full-screen ND (NAV page on 2 adjacent MFDs). The VSD is uses a series of Nasal and XML files (which some core developers make like to call 'Hacks') to get functionality of hard coded instruments.

The forum topic for the Vertical Situation Display Development can be found here. [http://forum.flightgear.org/viewtopic.php?f=30&t=15200]
Hooray is also working on a Wiki HowTo on implementing the VSD in nasal. [[Howto: Implement a Vertical Situation Display in Nasal]]

==New Navigation Display==

The Boeing 787-8 features a new Navigation Display (ND) which features the ability to plot the waypoints and connect them, like in the real ND. [[User:zakalawe]] has been working on a hard coded version of such a display but as we didn't get it at the time, we designed this instrument completely with nasal and XML interactions. Another feature on the Boeing 787-8 is the ability to show a larger Navigation display when both pages are set to NAV on the co-pilot's side MFDs. The larger full screen MFD shows more waypoints and the range can be adjusted between 1 nautical mile and 250 nautical miles. It also shows the airport diagram of the nearest airport positioned and rotated in the right configuration and can be seen better when the range is less than 10 nautical miles.

Another feature of the Boeing 787-8's Navigation Display is a very functional TCAS (Traffic Alert and Collision Avoidance System) which has also been designed completely in Nasal and XML and does not require wxradar to work.

==Electronic Flight Bag==
Please also see [[Canvas EFB Framework]]

[[File:Omega95-efb-787.jpeg|300px|thumb|Boeing 787-8 Dreamliner Electronic Flight Bag]]

The Electronic Flight Bag (EFB) as the name says is like an electronic database of handy documents and charts. The Electronic Flight Bag on board the Boeing 787-8 can calculate the required amount of fuel for your flight, show any airport's (you can search using the EFB INPUT page on the CDU) information, like elevation, metar and runway information like heading, length, ILS frequency), connect to Virtual Star Alliance's Automatic PIREP System for more functionality, connect to Redneck's FGFSCopilot for logging, show the GPS settings (your position on the world map, course and true headings to your next way-point and distance to your next waypoint. It also has realistic checklists for every phase of the flight, and an operating manual explaining basic maneuvers. You can also "INSTALL" airport diagrams and charts into the '/787-8/EFB-DB' folder which allows you to view them on the CDU (searchable using the EFB INPUT page on the CDU).

===Quick Guide to install and view airport Diagrams===

> Download diagrams from any source, convert them to *.jpg format and rename them '<icao>.jpg'. Then, place them in the EFB-DB folder. Then, use the 'EFB INPUT' page on the CDU to enter the airport ICAO and it displays the diagram on the EFB.

===Quick Guide to install and view SIDs, STARs and IAPs===

* Download the chart you need from any source (I use http://www.airnav.com for US charts and http://www.opennav.com for others), and convert the chart to *.jpg format. (if it's pdf, a good idea is to open it in full view and take a screenshot :wink: )
* If the airport and chart type folder doesn't yet exist inside the EFB-DB/Charts folder, create them like (for example I want to install the 25L-ILS IAP chart for KLAX) /EFB-DB/Charts/KLAX/IAP/
* Now, rename your *.jpg file to the chart name (eg. 25L-ILS.jpg) and place it inside the '/EFB-DB/Charts/KLAX/IAP/' folder.
* Now, open the /EFB-DB/ChartsList.xml file and add in your chart data (use the older charts' data for the format)
* Start up the 787, go to the 'Airport Charts' page on the EFB, go to the 'EFB INPUT' page on the CDU and
** Enter the Airport ICAO and press on the button next to 'Airport ICAO (Enter)' label (or the space under it on the touch-screen CDU)
** Click on the button next to the 'Chart Type (Select)' label to cycle through SID, STAR and IAP
** Click on the button next to the 'Chart ID (select)' label to cycle through available charts.
** Now, hit the 'DISPLAY >' button on the CDU and look at the EFB to see your chart.

Note that for some charts, the orientation may be land-scape and not portrait. But to overcome that, I've put a 'ROTATE' option on the EFB which rotates the chart when you click it.

''The Above has been taken from the forum topic.''

===''Third-Party'' EFB Software===

The Electronic Flight Bag is also meant to provide and interface third-party and/or operating airline softwares. These are not present in the Flight Management Computer by default but we're working on a couple of ''softwares'' for the EFB. This is not ''unrealistic'' because this is one of the main purposes of the Electronic Flight Bag. Here're the ''softwares'' we're working on for the EFB.

====FGFSCopilot Logger====

The [[FGFSCopilot]] is a java program that can do almost everything required from taking off till landing the plane at your destination. The Boeing 787-8 has an FGFSCopilot Log page in the EFB which shows it's connection status and every log message the FGFSCopilot sends to FlightGear.

====VNAV Automatic Altitudes Generator====

The VNAV AutoGen is a third party software on the EFB that automatically calculates ideal vnav altitudes for the active route. To use it, simply create/load a flightplan, copy it to the active route, go to the VNAV Altitudes Gen page on the EFB and click on ''AUTOGEN >''. That would generate altitudes for you which're displayed on the EFB. You can scroll through the waypoints using ''SCROLL UP >'' and ''SCROLL DOWN >''. Finally, if you're happy with the automatically generated altitudes, click on ''COPY TO RTE >'' to move them to the active route.

==Fly-By-Wire System==

The Boeing 787-8 Dreamliner is FlightGear's first Airliner to feature a complete Fly-by-wire system. The idea behind this fly-by-wire is to get it the pilot's controls (/fdm/jsbsim/fcs/x-cmd-norm : where x can be aileron, rudder or elevator) and work with it and give out another output property (/fdm/jsbsim/fcs/x-fbw-output) which is read by the FDM and control surface animators. The throttles don't have a chain such as the other surfaces so that the pilot can easily override the fly-by-wire (one of Boeing's "philosophies"). At this stage, the fly-by-wire can protect the aircraft from extreme bank angles (flight envelope protection- roll) where the bank angle limit can be set by the pilot in the CDU's 'FBW CONFIG' page, protect the aircraft from extreme alpha angles (flight envelope protection- alpha), calculate the throttle required and set it accordingly to maintain profile on turns, reduce throttle to stay under limits and finally auto-stabilize the plane and maintain the current profile when the yoke is brought back to the center. The Fly-by-wire also dampens the control to prevent any sudden motion. Fly-by-wire can be toggled from the CDU's 'FBW CONFIG' page.

NOTE : To be able to activate alpha-protection, roll-protection and auto-stabilizer, you need to be atleast higher than 3500 feet. This is so that the fly-by-wire doesn't interrupt your approach.

We've also created a tutorial which shows how you can implement the fly-by-wire we wrote for your aircraft : [[Howto: Implement a Fly-By-Wire System for Airliners]]

==Automatic Vertical Navigation==

I've seen a lot of wiki pages on aircraft autopilot and always noticed that next to 'VNAV -' the author writes either he doesn't know what it is, or it doesn't do anything or he hasn't tested it yet. Well, for a change, here I'm telling you what the VNAV does.

We have designed the autopilot route manager in the CDU to be able to accept VNAV altitudes for each (or whichever you want) waypoint. On the Dialog Route Manager, enter your waypoint in the format 'WP@ALT' for example, 'KSFO@9000'. So let's say you have different altitudes according to your SID/STAR/IAP till cruise altitude and then different altitudes for your waypoints when you land. Let's assume your flight plan to be:
DEP, WP1@3500, WP2@10000, WP3@18000, WP4@26000, WP5, WP6, WP7, WP8, WP9, WP10, WP11@20000, WP12@12000, WP13@8500, WP14@4000, DEST

You doesn't have to enter altitudes for WP5 to WP10 because you'll start cruising at WP5 (say you want to cruise FL360 aka. 36000 ft) and stay at 36000 ft till WP10. That means WP11 will be your 'End Cruise' Waypoint, where you aim at when you're out of the cruise.

To set cruise settings, go to the CDU's 'VNAV' page and enter cruise altitude in the respective area. Then enter your cruise start altitude (in this case, WP5) and cruise end altitude (in this case, WP11) in their respective places (there're labels).

Once you're ready, finish other checklists, take off and turn on 'LNAV' and 'VNAV' on the Autopilot. The VNAV is designed to automatically calculate the required/ideal climb/descent rate to get to your waypoint just in time. Out of all the tests we've conducted, the VNAV is VERY accurate at the moment.

==Flight-plan Management System==

[[File:787-8-fpm.jpeg|300px|thumb|Boeing 787-8 Flightplan Manager]]

In the Feb 25th, 2012 git commit, a new flight-plan management system has been written for the Flight Management Computer(s). The new system, like the real one lets you put in 2 flight-plans (with altitudes), and an alternate airport. You can do everything that you can to the route manager on these 2 flightplans. Boeing likes to call them '''Primary Flightplan''' and '''Secondary Flightplan'''. Once you enter your primary and/or secondary flight-plan, the respective flight-plan's status will show ''READY'' on the flight-plan management page. Then, a new option, ''COPY TO RTE'' will appear under the respective flight-plan and on clicking that, that plan will be moved to the active route. To make any changes to the route, you can either make them to the flight-plan and copy them to the route again or simply work with the active route by clicking on the '''ACTIVE ROUTE''' option in the Flight-plan Management page. An alternate airport is recommended to be entered in the CDU so that in case there's a problem during flight, the plane can be automatically be diverted (by the FMC) without you having to do anything other than pressing the ''DIVERT'' option on the Flight-plan management page. Note that using the ''DIVERT'' button to divert to your alternate airport clears your active route and sets the aircraft on a direct flight to the Alternate Airport.

==Automatic Holding Pattern==

[[File:Boeing-787-8-auto-hold.jpeg|300px|thumb|Boeing 787-8 Automatic Holding as seen in the FlightGear Tracker]]

The Boeing 787-8 now features an automatic holding pattern system where you enter the hold fix/navaid, hold radial and hold leg time and the aircraft automatically, flies in a holding pattern there. (as described in real Instrument Flight Rules Rating Course (IFR) textbooks) This feature is still being developed at the moment and is not perfected, but it still does the basic thing for you.

We have tested this feature from KIAH (George Bush Intercontinental Airport, Houston) holding at the VOR, LOA (LEONA VORTAC, about 70 miles north-west of KIAH) at a hold radial of 0, and hold leg time 120 seconds. We've been able to hold and re-trace the hold path every lap, but we get a strange shape due to the pid-controller. We're still working on it.

==Traffic Alert and Collision Avoidance System==

[[File:787-8-TCAS.jpeg|300px|thumb|Boeing 787-8 Dreamliner TCAS]]

The Boeing 787-8 Dreamliner (as of February 21st, 2012 on GIT) features a brand new TCAS (Traffic Alert and Collision Avoidance System) which has a capability of showing 30 Multiplayer aircraft and 20 AI Aircraft on it! Now, you won't have to complain about not seeing all aircraft on VATSIM ;) We're still working on increasing it's capability to 50 each multi-player and AI.

The TCAS has 3 different symbols for each aircraft and 4 different color codes. Each aircrafts' callsign, altitude and true airspeed will also be written next to the sprite.

*The '''Diamond Shaped''' Aircraft sprite shows that the aircraft is ''flying level''.
*The '''Box with Up Arrow''' shows that the aircraft is ''climbing''.
*The '''Box with Down Arrow''' shows that the aircraft is ''descending''.

*A '''Cyan or Blue''' Colored Sprite shows that the aircraft is at a safe distance.
*A '''Yellow''' Colored sprite shows that you need to be aware of traffic nearby.
*A '''Orange''' Colored sprite shows that you need to either change altitude or course, consult ATC. It is an advisory.
*A '''Red''' Colored sprite shows that you are in danger and immediately need to follow the TCAS instructions.

The TCAS is configured to sound voice alerts according to the situation. The TCAS voice alerts needs to be followed over the ATC's instruction if they contradict. The TCAS will alert you if you are in danger of collision with MP or AI Aircraft.

''NOTE: The TCAS voice alerts have been confirmed working on FlightGear git (2.7, as of February 19th, 2012) but don't seem to work in FlightGear 2.4.''

==Terrain Map and Weather Radar==

[[File:787-8-terrain-map.jpeg|300px|thumb|Boeing 787-8 Dreamliner Terrain Map]]

The Boeing 787-8 Dreamliner (git version as of February 21st, 2012) features a terrain radar which creates a terrain map on the MFD when the Navigational Display is set to TERR mode (you can change the mode from the buttons on both sides of the Mode Control Panel). Click on WXR to view the WXRadar (Collins WXR-2100), TERR to view the Terrain Map and CLR to clear the ND. The weather radar is still under development and a working version is not available, but the terrain map uses a 'get little and interpolate' method to create smooth terrain mapping.

==World Map and Flight Path Plotter==

[[File:787-8-wmap.jpeg|300px|thumb|Boeing 787-8 Satellite Imaging]]

Another option to put on the ND is the world map. It's not exactly a terrain map, but rather like satellite imaging. The plane is shown (it's zoomed in) on the map and the plane's path is marked with fading red dots. You can get your ND to show the satellite maps by pressing the WMAP button on the ND mode panel. Note that you can have any 1 of WXR, TERR or WMAP on and to remove them, press the 'CLR' button.

==Airline Flight Management Computer==

[[File:787-8-fmc.jpeg|300px|thumb|Boeing 787-8 Flight Management Computer - FLIGHT INFO]]

The Boeing 787-8 Dreamliner is an Airliner and we can't leave out some of the key features airline manufacturers put in their aircraft. There're 2 major sections in the Flight Management Computer (it's a part of the CDU) - the ROUTE and DEP/ARR. Both pages are accessed from the CDU(s). The Route is directly connected to the Route Manager and doesn't do anything 'special', but the DEP/ARR page lets you work with preset routes, SIDs, STARs, IAPs etc. You can enter the flight number (this is meant for virtual airlines: By default, Merlion's Boeing 787-8 Routes are included in the Database but I'll make a tutorial on how other airlines can put in their data) and be able to search for the flight information. If the airline has specified a Route and/or VNAV Altitudes and Configuration, you can load up those preset routes and altitudes by pressing the 'SET ROUTE >' menu. If a preset route doesn't exist, the FMS will generate a route automatically. A pilot does not have to worry about preset/generated routes. Another feature in the FMC is Scott Hamilton's LevelD-767 NAVDATA Parser, which gets SID/STAR/IAP Data and automatically puts them in the right place in the route manager for you to be able to fly them. This data can be managed from the PROCEDURES option in the DEP/ARR page.

''A much more detailed tutorial of how to use preset routes and automatically set terminal procedures is available in the wiki sub-page: [[Boeing 787-8 Dreamliner: Flightplan and Procedures Tutorial]]''

''We'll also be creating a video tutorial (Dreamliner Tutorial #6) on the Flight Management Computer.''

===FMS Navigational and Terminal Procedures Data===

The Boeing 787-8 Dreamliner and the Airbus A380 (being developed by Scott Hamilton) uses Scott's Level-D 767 NAVDATA Parser to get Navigational Data and Terminal Procedures into the aircraft's Flight Management Computer (Flight Management System on the A380). The FMS Data can be downloaded as an extractable '''*.exe''' file from http://www.filestube.com/source.html?token=f6f36bf2e8d20ecb03ea but we also have FMS Data files for individual airports on Git with the Boeing 787-8 Project. Download specific Airport NavData XML files from the source tree of the ''git://gitorious.org/fg-boeing-787-8/fms-data.git'' repository. You can also download master as a '''*.tar.gz''' from https://gitorious.org/fg-boeing-787-8.

By default, the 787-8 contains navigational data for the following airport - WSSS, YBBN, KLAX, KJFK, EGKK for testing purposes and as the Flight Management Computer Tutorial is a flight from KLAX to KJFK.

== Work on the C++ front ==
The capabilities provided by this aircraft touch many parts of FlightGear, that will benefit from modifications to the C++ code, this is an attempt at documenting useful C++ work. Most of this should probably be posted to the issue tracker, too.

===Camera/Video Surveillance Instrument===

The Aircraft doesn't 'yet' have a camera/video surveillance instrument but the team is working on it. We are creating a Wiki [[Howto: Use a Camera View in an Instrument]] while working on it so our progress can help other aircraft developers. The basic idea is the render the camera view to texture and get flightgear to display it on the instrument. As this instrument includes work in C++, it will NOT be available in FlightGear 2.4.0 or 2.6.0, and not even git at the moment.

=== Creating a 2D drawing API ===
Also see [[Howto: Create a 2D drawing API for FlightGear]].

=== Increasing the range of geodinfo() ===

Fix geodinfo() so that it may provide access to tiles not yet loaded, i.e. tiles that are not "visible" (which is the limiting factor currently). This will also be useful for the local weather system and probably a number of related scripts.

{{cquote|The tile manager is capable of satisfying multiple requests. Anyone can give it a position, range and a timeout. It will then try to load all tiles in the range specified. And it will stop loading them after the timeout - unless you have updated the request with a new timeout. So you could tell it every 5 seconds that you're interested in a certain area around the aircraft, and use a timeout of 5,01 seconds. A matter of memory and loading speed though.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33348.html |title=Future Weather System |last=Brehm |first=Thorsten |work=FlightGear-devel mailinglist |date 1 August 2011}}</ref>|Thorsten Brehm}}

=Glass Cockpit=

[[File:Omega95-cockpit.jpeg|300px|thumb|Boeing 787-8 Glass Cockpit]]

The Boeing 787-8 Dreamliner has a very complete and realistic modern glass cockpit based of the real Boeing 787-8 cockpit. Almost all of the instruments (excl. Weather radar which is currently coming up, and the voice comm.) are functional and work like the real thing. Multiple views have been created (like the OHP, CDU, EFB, Full Cockpit Views) so that pilots can easily work on different parts without looking away and adjusting view position.

That's all I can say about the cockpit now... You better test it out to judge it.

=Systems Overview=

==Electrical System==

The Boeing 787-8 Dreamliner uses a modified version of Syd Adam's Jet Electrical System. Backup Generators have been added, a Ram Air Turbine Generator has been implemented and the APU loop has been modified. There are 5 major power sources available are:
* Engine Generators (L1 and R1 are main generators and L2 and R2 are backup)
* Battery
* Primary and Secondary External Power
* APU Generators (Auxiliary Power Unit must be started and running for the APU Generators to provide power)
* Ram Air Turbine (used in case of dual engine failures to provide just enough power for Central Hydraulic Systems (C1 and C2) and Instruments.

To Understand the Electrical System better, take a look at the 'ELEC' page on any of the MFDs on board.

==Hydraulic System==

The Hydraulic System on-board is very advanced and does the job it's supposed to do.
There are 3 basic Hydraulic Systems - Left Engine Hydraulics, Right Engine Hydraulics and Central Electrical Hydraulics. Both Left and Right Engine Hydraulic Systems are pressurized by Engine pumps which require the engines to be running. These pumps pressurize the L and R systems that are connected to the flaps, spoilers, brakes and landing gears. Therefore, you need atleast 1 of the 2 Engine pumps to be running to be able to use these. But, the landing gear has an 'alternate gravity drop system' which you can use to get your gear down in case of a hydraulic failure.
The Central System has 2 electric pumps that control pressure to the hydraulic system that controls the ailerons, rudder and elevators. Only 1 of the 2 pumps have to be turned on at a time, and the other can be used as backup in case of a failure. The hydraulic pumps can overheat and fault if not adequately cooled, refer to the 'Pneumatics and Air Conditioning System' for more information on this.

To Understand the Hydraulic System better, take a look at the 'HYD' page on any of the MFDs on board.

==Pneumatic System==

The Boeing 787-8's pneumatic and Air-conditioning system controls bleed and flow of air through packs (and trim) which are then used to cool the equipment on board. The pneumatic system is pretty simple, you have 2 packs, 2 trim air controls, a gasper, and engines and APU bleed. The 787's systems automatically control bleed according to what is required and available, but you'll have to control the trim and packs. Equipment Cooling is an option on the Pneumatics panel which passes cool air into the hydraulic and fuel pumps to prevent them from overheating. When a pump overheats, you get a warning and if you do not either turn it off or switch on equipment cooling, the pump can fault. The 'PNEU' page on the MFDs show you more information on equipment temperatures and Pneumatic settings.

==Fuel Control System==

The Fuel Control System let's you control the 7 fuel pumps on board the 787-8 Dreamliner (2 Left Tank Pumps, 2 Central Tank Pumps, 2 Right Tank Pumps and a Crossfeed pump). The left tank and central tank pumps pump fuel from these tanks to the left engine, while the right tank and central tank pumps pump fuel from these tanks to the right engine. In case of a fuel imbalance, you can turn on the crossfeed pumps to transfer fuel from the tank with excess fuel to the one with low fuel.

===Fuel Jettison===

The Aircraft has a complete fuel jettison system where you can select which wing nozzle to jettison from, arm jettison and use a knob to define the dump rate. If the Left Nozzle is activated and Fuel Jettison is armed, you dump fuel from the left and central tanks, and the same for the right nozzle. Note that the 787 will NOT let you dump fuel if you have less than a critical value.

==Heating System==

[[File:Omega95-window-heating.jpeg|300px|thumb|Ice starts building up on the windows if temperature is sub-zero and window heating is turned off.]]

The Heating System on board controls 4 different heating equipment. First of all, let's get into "natural icing".

===Natural Icing at certain Conditions===

If your TAT (Total Air Temperature) value is under 10, your wings, engines and wind shield can start picking up ice. Window Ice simply forms on the window and obstructs your view out of the cockpit. Whereas, wing ice actually affects your lift and drag in the FDM! As for engine ice, if you have extremely high amounts of ice, the engines can fault and you might have to cool and then restart them.

Note that Engine surges are NOT due to ice build up. If you get an engine surge while flying, you might either be flying over Vne, or in extreme weather conditions with N1 above safe limit in those conditions.

===The Aircraft's way of Taking care of Ice===

The '''Window Heating''' switches on the overhead panel enables a heater to start melting the ice on the windshield letting you see outside clearly.

The '''Anti-Ice''' knobs (2 engine knobs and a wing anti-ice knob) let you control the heating equipment on the respective areas.

The 'HEAT' page on the MFD should have more information on the Heating Systems.

==Gear System==

The Boeing 787-8 dreamliner has 3 retractable gear units, the nose gear has 2 tires, and the main landing gears have 4 each in a square layout. The gear system manages gear compression and failures (stuck, tires burst and break off) on the basis of airspeed, wow and compression.

The gears system can be monitored from the 'GEAR' page on the MFD(s).

==Ground Service Controls==

[[File:787-ground.jpeg|300px|thumb|Boeing 787-8 Ground Service Controls]]

[[File:787-ground_1.jpeg|300px|thumb|Boeing 787-8 Ground Services (Right)]]

[[File:787-ground_2.jpeg|300px|thumb|Boeing 787-8 Ground Services (Left)]]

===Fuel Truck===

The fuel truck (MENU: Boeing 787-8 > Fuel Truck Controls) can be enabled/disabled and connected/disconnected from the aircraft's fuel value under the wing. You can enter an amount of fuel in the request fuel quantity input and ask the truck to re-fuel the aircraft to that quantity. You can also ask it to drain the fuel tanks.

===De-icing Truck===

The de-icing truck along with the other ground services can be controls from the ''Ground Services Controls'' menu (MENU: Boeing 787-8 > Ground Services Controls). The de-icing truck can be enabled/disabled and you can also de-icing the aircraft. The de-icing process includes the truck animations and actually de-icing the aircraft!

===External Power Box===

The External Power box is a stand-alone generator that provides external power to the aircraft. When enabled, it is connected to the external power socked under the aircraft's left wing. Note that this needs to be enabled so that you get external power. When you start FlightGear, the external power will be enabled by default.

===Landing Gear Chokes===

Landing Gear chokes are triangular prism shaped blocks that're placed in front of and behind the landing gears to prevent the aircraft from moving. These chokes will also prevent the aircraft from moving in FlightGear and are enabled by default on start up. Note that to get the aircraft moving, you need to remove the parking brakes and chokes.

===Catering Truck===

The catering truck can be enabled/disabled and toggled. The ''Toggle Catering'' option is to lift/lower the catering box and connect to the the R1 Door. It doesn't do anything else.

===Baggage Ramp and Trailers===

These're just models and don't do anything at the moment.

==System Failure Simulation==

[[File:787-failures.jpeg|300px|thumb|Boeing 787-8 Failure Simulator]]

The aircraft has a built-in failure simulation dialog where you can get different systems to fail in different ways. The failure simulation dialog can do the following:
* Flame-out any of the engines
* Fail any of the engines
* Set any of the engines on fire
* Burst any of the Wheel Tyres
* Have a gear unit ''break-off''
* Stuck a gear unit in it's current position
* Fail individual hydraulic systems
* Overheat any of the hydraulic or fuel pumps
* Fault any of the hydraulic or fuel pumps

Other general failures like Electrical, Static etc. have not been implemented in this dialog as they can already be controlled with FlightGear's Generic System Failures dialog.

''NOTE: When you flame-out an engine, it can be restarted, but not in the case of a failure. Faults just means that the pump is too hot to function, but it can be restarted when cooled.''

'''IMPORTANT!'''
*In case of an engine surge, (this cannot be toggled by user as it requires certain weather conditions and N1 to occur) immediately reduce throttle and get the N1 under 65%. If you're flying too fast, try to slow down and avoidance extreme weather (heavy rain and snow) would be a nice idea if you want to prevent surges.
*In case of an engine fire, pull the respective engine's fire extinguisher lever (it's right behind the throttle quadrant) and cutoff fuel to that engine. If the fire persists and you don't extinguish it, the engine may face an explosion and severe damage will be inflicted, leaving that engine unusable (basically, you can't restart it)

=Virtual Copilot=

Johan G posted in the Boeing 787-8 Dreamliner Forum Topic:
''I really see why there could be a real need to have a copilot along when "flying in" the aircraft during pilot conversion.''

Basically, the systems are very complex that it might be difficult for just 1 person to control the plane and manage the systems. As an immediate solution, the virtual copilot can announce ref. speeds, control flap lever, control gear lever, control heating and pneumatics, set altimeter setting and engage thrust reverser's and spoilers on touchdown. You can select exactly what you want ''him'' to do in the Virtual Copilot Settings Dialog.

On the other hand, we're working on a new advanced dual control system which allows the copilot to completely control the aircraft and see all instruments over multiplayer.

=Downloading the 787-8=

The Boeing 787-8 Dreamliner is hosted in GIT and has been made into different kinds of releases so that users can download it according to what they need. In the Boeing 787-8's Git Project page [https://gitorious.org/fg-boeing-787-8], you can find 3 different Repositories:

==fg-boeing-787-8-main==

This is the main Aircraft repository on GitHub. It includes the bleeding edge version (''master'' branch), and different types of releases of the latest stable version (''stable_d'', ''stable_e'', and ''stable_f'' branches).

===master ''Bleeding Edge''===

The '''master''' branch on the fg-boeing-787-8-main repository contains the latest development version of the Aircraft. This contains everything that's there in the
authors' aircraft folder from when a commiter last pushed his changes.

'''Download master as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/master
 
'''Download master as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/master</del>

===stable_d ''Default Database''===

The '''stable_d''' branch (''d'' for ''default database'') contains the latest stable release with the selected airport diagrams, charts and FMC navigation data. This is recommended for everyone but you can get the other releases according to your needs too.

'''Download stable_d as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/stable_d
 
'''Download stable_d as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_d</del>

===stable_e ''Empty Database''===

The '''stable_e''' branch (''e'' for ''empty database'') contains the latest stable release of just the basic aircraft, including models, nasal, systems etc. but the EFB and FMC databases are empty. This is recommended for those with slow internet connections. If you get a better connection later, you can download the whole database only from the ''fg-boeing-787-8-data'' repository.

'''Download stable_e as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/stable_e
 
'''Download stable_e as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_e</del>

===stable_f ''Full Database''===

The '''stable_f''' branch (''f'' for ''full database'') contains the latest stable release of the aircraft, default diagrams and charts and the complete FMC Datbase. This release especially features FMC navigation data for 3808 airports (all we have so far)! It's recommended only if you have a very good internet connection. (WARNING! 280+ MB)

'''Download stable_f as zip''' : https://github.com/omega95-aircraft/fg-boeing-787-8/tree/stable_f
 
'''Download stable_f as tarball''' : <del>https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-main/archive-tarball/stable_f</del>

==fg-boeing-787-8-data==

The Data Repository contains all the available EFB and FMC Database files. All these files are also included in the ''stable_f'' releases, so if you have a ''stable_f'' release, you don't need to worry about this.

'''Download master as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-data/archive-tarball/master

==fg-boeing-787-8-devel==

If you're interested in helping develop this aircraft and join the team, you can download the files in this repository. These are not required for the running of the aircraft but include some files like wxradar files, dual control files etc.

'''Download master as tarball''' : https://gitorious.org/fg-boeing-787-8/fg-boeing-787-8-devel/archive-tarball/master

==Cloning and Pulling==

Cloning and Pulling the 787-8 repositories are the same like every other git repository, including FlightGear. Once you clone/pull, you can select the branch you want using ''git checkout <master/stable_d/stable_e/stable_f>''

More information on using git is available at [[FlightGear And Git]].

=Aircraft of the month!=

{{#ev:youtube|WlzEoCsJvz4|480|center}}

Thanks to Oscar [http://www.youtube.com/user/osjcag] for the amazing ''Aircraft of the Month Review Video'' for the Boeing 787-8 Dreamliner.

=Boeing 787-8 Wiki Sub-Pages=

* [[Boeing 787-8 Dreamliner: Operating Manual and Checklists]]
* [[Boeing 787-8 Dreamliner: Video Tutorials]]
* [[Boeing 787-8 Dreamliner: Control Display Unit Reference Manual]]
* [[Boeing 787-8 Dreamliner: Flightplan and Procedures Tutorial]]

=Aircraft Status and ToDo List=

==Flight Dynamics Model: 4==

* The Boeing 787-8 has a JSBSim FDM matching a lot of results from http://www.lissys.demon.co.uk/samp1/desmis.html
* We don't have more detailed test results. so we can't test everything yet. Once we get that, we need to tune the FDM further.

==Aircraft Systems: 5==

* The Aircraft has very advanced systems imitating realistic systems from the real 787.
* Random/Checkable Failures purposely haven't been implemented as random is never realistic. But Engine failures, ice etc. occur in the appropriate conditions.
* The 787-8 has very advanced instruments, flight management computer, hydraulic, electric, pneumatic, heating, fuel etc. systems.

==Cockpit and Instruments: 4==

* The cockpit is very detailed and most buttons are there and functional.
* The instrument displays are very advanced and functional, the ND could be replaced by a hard coded version though.
* A Camera View instrument is supposed to be there but isn't, but we're working on a hard coded camera view instrument.
* The aircraft uses textures extracted from pictures and ambient occlusions created with blender.
* The complete cockpit has been light-mapped and looks very good at night too.

==Model: 4==

* The model is still from the old 787-8, there's the basic model without a cabin, rods aren't yet complete either.
* The landing gears have been re-done and look a lot better now, but the model has a much better scope of improvement.
* The Model Rating has been taken right out of the old Boeing 787-8

=Related content=
There are plenty of tutorials and code snippets that were specifically created for this project, this is a list of all things related:

{{Appendix|all|
* {{Cite web|url=http://www.bristol.ac.uk/aerospace/msc/avadi/units/projects/ub2009f/group7/7878summarysheet.pdf |title=787-8 Summary Sheet |date=21 January 2009 |publisher=Department of Aerospace Engineering, University of Bristol }}
* {{Cite web|url=http://www.wpafb.af.mil/shared/media/document/AFD-090121-023.pdf |title=The Boeing 787 Aircraft |work=Air Force HSI |publisher=Wright-Patterson Air Force Base }}
* {{Cite web|url=http://www.boeing.com/commercial/aeromagazine/articles/qtr_4_07/AERO_Q407.pdf |title=AERO Quarterly |date=2007 |publisher=Boeing}}
----
{{references}}

'''Weather radar (wxradar)'''
* {{Cite web|url=http://www.smartcockpit.com/data/pdfs/flightops/aircraft/Collins_WXR-2100_Operator%27s_Guide.pdf |title=Collins WXR-2100 MultiScan™ Radar Fully Automatic Weather Radar |date=2003 |publisher=Rockwell Collins }}
* {{Cite web|url=http://www.ll.mit.edu/publications/journal/pdf/vol12_no2/12_2weatherradar.pdf |title=Weather Radar Development and Application Programs |last=Evans |first=James E. |coauthors=Weber, Mark E. |date=2000 |work=Lincoln Laboratory Journal}}
}}

[[File:787-8-cockpit-panorama.jpeg|800px|Panoramic View of the 787-8 Dreamliner Cockpit]]
{{boeing}}

[[Category:Airliners]]

Property Tree/Native Protocol Slaving

2014-01-18T02:15:09Z

Anton: /* Success ! */

{{Template:PropertyTree}}

FlightGear can also be configured to dump UDP or TCP data packets out over the network at a high speed. Other copies of FG can be configured to read these packets and use that data (and disable the internal FDM calculations.)

In this case, depending on your command line options, FG can be configured to be a telnet server, an http server, a "dynamics" master/server, or a "dynamics" slave/client, and possibly some combination of all of those simultaneously depending on the context and what you are trying to accomplish.

There is an --native-ctrls= command line option to send a set of flight control related properties. It works just like the --native-fdm option,
just remember to use a different port number.

For past projects, I've used the --props= option to accept property configuration changes (things like weather effects and time of day.) You
can use this interface to read/write individual properties. I setup a separate gui that was configured to know the ip addresses of all the slaves
so it could update them appropriately when I wanted to make a change. For the time of day, this presupposes that all the computer clocks are pretty
closely in sync ... then you can send the same time offset to them (in seconds) so they all can display the same time of day effects.

There is no synchronization in the native-fdm and native-ctrls protocols used for multiple displays. The master instance just transmit to the slaves, who process the data when and in the order it is received. This ought to work without problems in a local network.

native_ctrls is what gets sent to a remote fdm (i.e. the control positions) and native_fdm is what gets sent back to flightgear (i.e. the fdm data.) There's no reason you can't send both in your application if you need to.

The FDM defines the control surface position (deflection) so that data is passed to FlightGear in the native_fdm structure.

I will not claim that the existing FG interfaces cover every possible case. They have been designed to try to serve existing needs with some sort of logical consistency.

If you have a specific need that doesn't easily fall within the existing interface structure, it's not all that hard to add your own custom interface. There are several examples (i.e. native_ctrls, native_fdm, native_gui, etc.) which you can copy and modify to suit your needs. If the new interface is of general interest or if you make a persuasive argument, we could probably add it to the FG code base.

I'd take a look at net_fdm.h and native_fdm.c. The data structure received by FlightGear can easily be modified to include whichever parameters you'd like to control from your Matlab sim. You just need to add code to set the appropriate FlightGear properties.

It doesn't make sense to modify the current version of FlightGear because different people have different requirements. For instance, if you allow both control positions and surface deflections to be sent, how does the fdm know which one to use? Furthermore, the native_fdm is designed to control actual rotation rates and velocities, so control positions don't factor into this. It seems like you'd like a little bit of each, which to me means a custom modification.

We have discussed a more flexible (xml configurable) udp binary interface, but no work has commenced on that front.

It might not be a good idea to throttle the frame rate to the data rate - FG will only check for input (at most) once per frame and that could easily fall out of sync with the producer in this case (if data arrives too late in some frames). If FG consumes all pending data it finds that could explain the jerks. Can you try throttling to 2x the data rate?

==Asymmetric View Frustrums ==
Supporting mutliple displays are well supported in FlightGear. There is a document called README.IO that touches on this. You may also want to check out [http://www.inkdrop.net/dave/multimon.pdf]. If you need more help, just ask.

You can set up your view parameters for each instance individually, e.g.:
<pre>
--fov=35
--prop:/sim/view/config/heading-offset-deg=42
--prop:/sim/view/config/pitch-offset-deg=3
</pre>

You can adjust these properties in real time if you need to, but typically you set these once for a particular monitor configuration and you simply send over the position and orientation to the slave machines and everything happens automatically. The configurable numbers are offsets from straight ahead.

If you need to model your view point changing relative to your monitors (head tracker?) and need to fiddle with your frustums and view direction offsets in real time, then that's a bit more difficult. I'm not aware of anyone doing this, but it shouldn't be all that much additional effort to add support for this sort of thing.

I should point out that we also have some capabilities for configuring asymmetric view frustums if you need that. We use a higher level mechanism (that meshed well with what we already had in place) so you specify a larger screen and then specify the horizontal and vertical subsections of that larger display that will be shown on a particular monitor. This probably doesn't cover all asymmetric view frustum needs, but it does let you do a lot in a way that people can conceptually get their head around (rather than using obscure l, r, t, b, n, f numbers that takes an opengl guru to derive.)

For my specific need I wanted 3 monitors side by side in a straight line, and I wanted the projection plane to also be a straight line. So referencing your link, Example 1 is what we originally could do, but is not what I wanted. I wanted to do something similar to Example .... errr ... I guess there isn't an example on that page of what I wanted to do. Kind of like Example 5 I guess except with the "red" line (plane of projection) extending straight across. The center view frustum would be symmetic and the sides would be asymmetric. I realize this isn't "correct" but I need a compromise to build a display system that look "reasonable" from a large variety of perspectives at the same time.

So anyway, here's my approach. Let's say I wanted 3 monitors, each covering 30 degrees FOV.

* I added an --aspect-ratio-multipler=x.xx option. FG automatically calculates aspect ratio based on X, Y screen resolution. This option scales the Y FOV.
* I created a super wide display with something like --fov=90 --aspect-ratio-multiplier=0.33333
* I added some options to select a portion of this wide screen to draw onto the individual monitor:

<pre>
--prop:/sim/current-view/frustum-left-pct=0.00000
--prop:/sim/current-view/frustum-right-pct=0.333333
</pre>

This gives me the leftmost 1/3 of my wide (--fov=90) screen. And the aspect ratio multiplier option allows me to get the desired vertical field of view.
Well, technically, my scheme still requires a separate running copy of FG and a separate video card for each monitor. I've had the best results doing this from 3 different machines, but I've heard stories of others having reasonable results with running multiple copies of FG on a single machine. At the moment FG doesn't have direct support for opening up multiple windows to drive multiple displays from a single instance of FG.

There really isn't any extra performance hit though for asymmetric view frustums. The frustum is trimmed down before the cull and draw phase.

I should say though that most people will just want to point their displays perpendicular to the viewer and use a more standard/straightforward symetric view frustums. I had to do asymmetric view frustums for a particular project with specialized needs. We ended up with a combination of compromises that I wasn't entirely happy about. We were trying to achieve a middle of the road solution that wasn't perfect anywhere, but wasn't horrible anywhere either.

== Syncing multiple instances ==

For anyone trying to sync multiple copies of flightgear and get silky smooth frame rates, or anyone trying to get silky smooth frame rates in a single copy of FG the following is some important information I learned the hard way...

If you want smooth rendering, you need to do a couple things. First, make sure that your copy of FG can render a sustained consistant frame rate. One *good* option is to sync to the vertical refresh signal on your monitor. With linux/nvidia there is an environemental variable you need to set to activate this feature (see readme that comes with the driver.) For other cards or platforms, there may be some different mechanism. Secondly, there is a tool that FG gives you to throttle frame rates to a maximum value. Set the property /sim/frame-rate-throttle to some value that is a multiple of your monitor's refresh rate, but is fast enough for your machine to keep up with consistently. From the command line or your ~/.fgfsrc you could do this:

--prop:/sim/frame-rate-throttle-hz=30

Just to convince yourself this is working, you might want to try something like:

--prop:/sim/frame-rate-throttle-hz=5

This will limit your maximum frame rate to the specified hertz (if your machine can go that fast.) The internal FG mechanism to do this is a simple busy/wait loop so you don't gain any CPU cycles with this, but you do get pretty accurate timing.

Getting the rendering speed consistent is one side of the coin. The other is that you need to feed the data input stream at the same consistent rate. This can be hard to control if you are communicating over the network.

Consider this: here in the USA our monitors really like to run at 60 hz (or 72 or 75.) I usually run them at 60hz because that's easier to keep up with for FG rendering. For one particular example, I was stepping FG down to 30hz. I was trying to feed FG from another application running on the same machine. This was a really low cpu-usage process so I was using timer interrupts to wakeup every 33ms and send the data over the network. I was about to congratulate myself on my own cleverness, but I was continually nagged by much choppier rendering than I thought I should be seeing. Something wasn't right. It just so happened that someone had an oscilliscope they could connect in to one of the interfaces and see exactly how fast my data feeding program was running ... I was shocked that it was doing 25hz (or one data output every 40ms even though my timer was set to wake up every 33ms.) A 25hz input stream combined with a 30hz renderer just can't provide jitter free video output, in fact it's pretty horrible.

Upon further investigation I discovered that the underlying linux CPU scheduler runs at 100hz (20ms cpu scheduler interrupt rate.) This is hard coded into the kernel and at one time represented a good balance between not burning too much CPU with excessive context switching, yet switching processes often enough so that they didn't become too unresponsive.

Apparently the linux timer interrupt system only checks for a timer interrupt during a context switch (or every 20ms.) So I requested a 33ms wakeup ... after the first 20ms context switch, the timer hadn't expired yet, and the system wouldn't check again for another 20ms ... so I was getting 40ms interrupt times when I asked for 33ms... Actually you get 40ms interrupts if you ask for anything > 20ms or <= 40ms. Frustrating! I actually tried playing with the system cpu scheduler rate and recompiling my kernel and never got the results I was hoping for.

This message is starting to get a little long and tedious, but my point here is that for smooth frame rates: (1) you need to draw the scene at a consistant rate (and I mean a consistant frame rate, not a variable rate faster than movie frame rates, but that's another tedious discussion for another time.) And (2) you need to feed your position/orientation updates at that exact same rate (and my example was to show why that's not always easy.) :-)

What I ended up doing on the Linux platform was to keep the two applications running on the same machine, but communicate between them using a named pipe. Each application blocks waiting for input from the other side of the pipe, so you aren't held hostage to your OS's CPU scheduling/timing interrupt voodoo. FG acts in sort of a "master" or "commander" roll. The other application which feeds the data waits for a request and immediate responds with the result. This way FG runs essentially at full speed and isn't hindered by blocking on the other application's output (because even though it does block, it get's a reply back immediately to unblock it.) The other application blocks on FG's output which means it sit's idle (not burning any CPU) until a request/command comes in on the pipe. Of course you have to make sure your communication is all sequenced perfectly or you risk a dead lock scenario.

Hopefully this message doesn't read too much like a computer science operating systems class, but any similarities you do see are intentional. :-)

Windows doesn't have a real concept of "pipes" in it's underlying kernel, especially "real time" pipes which can't be faked with a temporary file, so shared memory is another solution for getting two applications to talk to each other. I'm sure that's where the "sharemem.dll" comes into play.

Also it should be noted that if you can run your monitors/projectors at 60hz refresh rate, and then sync FG to the vertical refresh signal, and if your hardware is fast enough to sustain at least 60hz, then you can have extremely smooth displays. If you are able to send the NetFDM packets at exactly 60hz to all your display channels, you can have remarkably good syncronization between channels, and very smooth animation over all. But the key is to have *everything* running at a solid consistant frame rate. If you can't do 60hz, we have a mechanism to artificially throttle the frame rate to something lower, like 30hz or 20hz. Sometimes a slower consistant frame rate produces much smoother results than a faster, but varying frame rate.

if you're really seeking for a 'clean' solution there are more topics to add. For instance you have to synchronize the yoke positions because you are likely to have a setup where the co-pilot's yoke is visible in the right-window view. Neither protocol will handle this. You might see AI aircraft taking off at the local airfield, an aircraft carrier or whatever else which lack synchronization as well, no matter which protocol you use.

Distributing the AI stuff over the general/official MultiPlayer server might not be such a nice thing to do, so it might make more sense so
synchronize the slave views locally. This still lacks synchronization of AI objects but at least you don't annoy other people which are using
the MP server.

Having the MP protocol extended to handle the needs of local synchronization might be the solution of choice, because apparently it puts less load onto the master machine than the 'native' protocol and it is platform independent - and while everybody is waiting for a chance to implement new features inside the MP protocol, 'they' might add a viewer-only mode as well

In my application with one cockpit computer and 3 out-the-window computers, I already am using the FGNetFDM and FGNetCtrls structures to pass data between these 4 machines. Flight dynamics, cockpit controls, control surface animations, etc. are already synced. That is taken care of.

Now I want to fly this system of computers in the multiplayer world. An invisible player option (view only) for each of my visual channels would
be a quick and dirty solution to my problem. I realize it wouldn't be perfect and there could be synchronization issues with the MP aircraft
locations when passing between displays, but I can live with that for now.

AI aircraft is an entirely different issue. I just turn all that off on this system because precisely as you point out, the AI stuff operates
independently in each display and that is not helpful. There are a lot of things we could discuss with AI aircraft, but I don't want to
distract everyone from my main request, a viewer only mode for the Multiplayer system.

<pre>
//*** example to slave one copy of fgfs to another ***

// This instructs the first instance of fgfs to send UDP packets in the native format to a machine called seattle.com on port 5500.
fgfs1: --native=socket,out,30,seattle.com,5500,udp

// The second instance of fgfs will accept UDP packets (from anywhere) on port 5500.
// Note the additional --fdm=external option which tells the second instance of fgfs to not run the normal flight model,
// but instead set the FDM values based on an external source (the network in this case.)
fgfs2: --native=socket,in,30,toulouse.net,5500,udp --fdm=external
</pre>

== Slaving Controls (Joystick) ==
--native-ctrls transmits many variables concerned with flight control positions, cockpit switches, radio settings, sim status (paused?), etc. See net_ctrls.hxx

Look at the Network subdirectory for all the various options and the mini-docs for a howto. the necessary socket code is built into flightgear
and envoked as " --native-ctrls=socket,in,32,,5700,tcp " where:
* 32 is the data rate (packets/sec)
* 5700 is the socket address used by the slave and server
* tcp is the IP protocol (you can use udp, but packert deliver is not guaranteed)

== Slaving Dynamics (FDM) ==
There is a sample implementation that shows how to do this in the sourcecode under FlightGear/examples/netfdm.

== Example: Syncing custom properties (animations etc) using a generic protocol ==

For the full thread, see [http://forum.flightgear.org/viewtopic.php?f=36&t=19858].

(Required background reading: $FG_ROOT/Docs/README.IO and $FG_ROOT/Docs/README.generic)
=== Multi-Instance Setup ===
* I was under the impression that using only one computer and multiple displays with FlightGear would be too taxing on the computer and graphics hardware. I've done multiple screens with GEFS (Google Earth Flight Simulator) and got some pretty slow frame rates doing it. Multiple computers with FGFS though is *so* much smoother most of the time. Much, much better.
* After much trial and error, I've succeeded in setting up slave computers for displaying different camera views, and it's pretty freaking awesome. I'd like to do some fine tuning now and hope I can find some help here on the forum.
* I've pretty much been working with just one aircraft in getting the multi-computer thing going. The way I implemented it was to add a new view to the Aircrane aircraft on each computer - slave left view, master view, slave right view.
=== Syncing Shadows ===
* The first thing I'd like to tackle is - how to not have inappropriate shadows - in the slave displays. The aircraft can be well above the ground and yet cast *in the air* the shadow it would cast if it were on the ground. And possibly related to that, the props/rotors/etc. are frozen and don't move at all. Is there anything that can be done about this? I'm using native-fdm and native-ctrls between the computers but know next-to-nothing about the capabilities of the other options/protocols. I had some success with native-gui (I think it was), but so far, the fdm and ctrls combo works best for me.
* One more thing I noticed today was that while the attitude may change, there doesn't seem to be a corresponding change in the shadow. It always looks like it would look if the aircraft were parked on the ground
* sounds to me like you are using a combination of I/O protocols that isn't suitable to synchronize aircraft properties to update the slave instances.
* This is an aircraft-specific issue, due to the limitations of the protocols that's used - basically, the aircraft uses animations and properties that are not synchronized with other instances. So that animations from the main/master instance are not properly propagated to the slaves.
=== The Problem ===
* The way you described your setup, you are running multiple instances of FG, which are connected in a master/slave fashion - which basically means that important properties need to be replicated/copied over to the slaves instances. These are properties like position, orientation, view, velocities etc - each FG instance will then individually compute a corresponding view. The frame/image itself will never be copied to the other instances - just the variables.
* So are there additional protocols I should/could be using maybe? Is sending just the master computer's camera views - without its fdm etc. - something that's possible, or does that require too much work from the master's graphics card and defeat the whole purpose of using multiple computers?
* Meanwhile, I'm thinking the wierd shadows are only a symptom, and the props/rotors not moving is another sympton. It's as though the aircraft models in the slave computers get no instruction to be anything but parked on the ground with the engines off. You see (at least I see) the changes in attitude as you fly, but that's it. Nothing else ever changes...
* the animation properties don't seem to be properly synchronized - you'll need to handle that explicitly using another sync protocol, the FDM/input protocols don't transmit animation properties - they just transmit the "fundamental" properties. Basically, your slaved instance knows nothing about the properties that it needs to get from the master instance.
=== Using a custom protocol to sync properties ===
* Also, you can easily come up with your own custom protocols by editing/creating XML files [[Generic Protocol]]
* it looks like generic protocol might be the way I want to go, but how do I determine which properties need to be included and which ones don't? Or am I asking the wrong question?
* You could try to run a single master instance and check the values of the properties via the property browser. That should give you an idea of working values, even without understanding all the XML/animation magic.
* We've been discussing weird shadows, and propellers not spinning and such, but my focus is primarily on the shadow problem. I can put up with animations of flight control surfaces not working in the 'at aircraft' views, because I'd probably only use those views occasionally. However, in views from the pilot's perspective, pitching down and banking can cause extremely distracting dark shadows to come into view that darken huge chunks of real estate below. The size of the shadow is constant, regardless of altitude; it's the shadow that would be cast on the ground when the aircraft is on the ground. I nearly jump out of my seat sometimes when they suddenly appear during a dive etc.
* Well I've started thinking it might simply be a matter of *altitude updating* of the aircraft's shadow casting properties that's not being received by the slave instances via the native-fdm protocol. The 'shadowcasters' of the slaves, so to speak, always think the aircraft is on the ground. If this is the case, I would imagine that somewhere in the properties browsers of the master and the slaves I would see the values of certain altitude properties being updated in the master and remaining constant in the slaves?
=== Finding relevant properties ===
* So if any following this thread think I'm on the right track here, could you offer some suggestions as to what properties I might look at or what altitude related keywords in the xml files and properties browser might be worth taking a look at? I've done some searching on "agl" (above ground level, I assume)and "elev*" and "shadow*," but haven't come across anything yet that looks all that promising. Of course looks can be deceiving, so any insights at all would be greatly appreciated.
* if this is "stock" FG in non-Rembrandt mode, the shadows are unlikely to be actually computed - they are just a "hack" added by modelers, in the form of semi-transparent 3D models usually.
* In the master computer's view, the same shadows I've been talking about *change* as altitude changes. It's the ground shadow you see with all aircraft. The higher the aircraft goes, the smaller the shadow on the ground appears to the pilot. In the slave views, the shadow doesn't change at all with change in altitude. The shadow is always the same size to the pilot; it's always the size it is when the aircraft is on the ground. What I need to know (I think) is what properties effect that change in the master's views that are missing in the slave instances. Would it matter whether or not that change is caused by a hack or whether or not it's a hack that gets changed? Couldn't such a change be transmitted via the generic protocol nevertheless?
* Regarding the shadows: that'd depend on the animations that are used there - so, you'll want to check out the animations on the master, see how they work exactly, and then provide the correponding data (=properties) by sync'ing them from the master to the slaves. Given your progress, that should be all do-able now, you just need to find the animations and check what properties are used. A fair deal of stuff can be learned just by using the property browser or the Nasal console and playing around with various properties, and changing them at runtime - no slaves needed for that, just to make sense of how the animations and properties hang together.
* Actually, the shadow is 95% generic/standard across aircraft, and only has two rotates (/orientation/pitch and /orientation/yaw) and a translate (/position/altitude-agl or /position/gear-agl-ft) and sometimes one more for the rotors (I forget the property, but it's under /rotors/main and it's absolute position in degrees). I think it will work, but it's odd that the shadow is not showing up (I wonder if it is possibly below-ground?).
* I meant to say was that it was the /position/gear-agl-ft property I wanted to try, because when I inspected that property in the slave with the internal properties browser, it showed a value of ' ' (blank), whereas the same property on the master did show a value.
* I'm trying to set up generic protocol communication between a master and slave computer.
=== The generic protocol ===
* I created an xml protocol file with an output block for the master and opened a generic protocol output.
* A protocol file can contain either or both of <input> and <output> definition blocks.
* Well, I think I'm on the right track. First of all, I took the protocol file with the output block for the master and copied it to the slave computer and simply changed both output tags to input tags.
* Then I created the input generic protocol on the slave and gave her a shot. Well, lo and behold, the shadows are gone, although not as I had hoped. I was thinking I would still see *appropriate* ground shadows, but it turned out there are now no shadows at all...which is a far cry better than it was before. I can definitely live with this, but if anyone can think of any tweaks to get the appropriate shadows back, that would be way cool.
* In the protocol files I used, I wasn't sure what value to put in for the 'format' tag, so I edited it out. I didn't know how to find out what it should be. Wouldn't it be great if the correct value for that would bring back the appropriate shadows?
* Someone with more expertise could probably look at the value for the /position/gear-agl-ft property in the properties browser and determine by the number that's displayed what the format is, but I'm not in possession of that knowledge at the moment.
* I'm making progress. I have shadows behaving pretty well and am starting to get rotors moving, but the rotors are behaving badly. They spin in the slave when they're stationary in the master. They start looking like they're robo-spider-legs, drawing in and out and in and up and in and down, all with quick jerky moves and blurring going on. It's wild!
=== Format tags ===
* Well I've not put in many format tags at all, and I'm wondering if that can matter. The values of a property in the slave property browser can be radically different from the values of the same property in the master's property browser. Is there a way to find out which format tags to use for properties on the tree?
* Generally, I think you will be wanting to use %f. Read up on printf formatting flags: %d is an integer and %f a float/double. I think that all properties will almost certainly be doubles.
* I use "type" tags to declare property values as double, float, etc. When you, for instance, declare a type to be float, what does formatting as %f do? I know you can dictate how many decimal places there should be on either side of the decimal point with something like %xx.xf, but what does %f default to? It's the number of places on either side of the decimal point that I was wondering what would be best.
* I guess I'll go ahead and experiment with it while I wait for any reply you might be able to offer. I don't think I'd do too much damage doing that...
* the type attribute tells the property tree how to store a value internally, using the most appropriate data type saves memory and reduces conversion overhead (bool, int, float, double, string). Using the printf-style format strings in a generic protocol XML file, merely tells the I/O system how to encode/decode a property - so that it can be saved/transmitted and restored properly. Using the wrong type and/or format string in a binary protocol, would cause wrong data to be transmitted/processed by FG. Basically, each type specifier tells FG how long each data type is in memory (bits-wise). For example, a boolean value is just 0 or 1 - so it only requires a single bit. A byte, on the other hand, requires 8 bits - and an integer (int) 4 bytes (32 bit). So telling FG that something is a bit, will cause the data to be truncated to just a bit - which is what the format specifiers are all about: you can affect the re-interpretation of values from the property tree. In addition, there's the concept of signed-ness, i.e. numbers being positive or negative, or numbers having a mantissa - these affect how the values are stored in memory, and accordingly, the receiver must know how a value was encoded, to transform it back to what you want it to be.
=== Success ! ===
* Well I'll be! I added %f formatting to everything, and now everything appears to be working almost perfectly. The shadows are appropriate and the main rotor on the slave appears to be behaving exactly like the one on the master. This is awesome. The only difference I can see is that the animated main rotor shadow appears to have fewer blades on the slave, but if I never find out why and fix it, it will barely matter. I'm completely stoked! All I basically have left to do is put in pretty much the same code for the tail rotor that I did for the main rotor.

<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<PropertyList>
<generic>
<output>
<line_separator>newline</line_separator>
<var_separator>,</var_separator>

<chunk>
<node>/position/gear-agl-ft</node>
<type>float</type>
<format>%1.9f</format>
</chunk>


<chunk>
<node>/rotors/main/blade/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[1]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[1]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[1]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[2]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[2]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[2]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[3]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[3]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[3]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[4]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[4]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[4]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[5]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[5]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[5]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>



<chunk>
<node>/rotors/main/cone-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone1-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone2-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone3-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone4-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/roll-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/rpm</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/stall</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/stall-filtered</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/torque</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/yaw-deg</node>
<type>float</type>
<format>%f</format>
</chunk>
</output>

<input>
<line_separator>newline</line_separator>
<var_separator>,</var_separator>

<chunk>
<node>/position/gear-agl-ft</node>
<type>float</type>
<format>%1.9f</format>
</chunk>


<chunk>
<node>/rotors/main/blade/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[1]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[1]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[1]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[2]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[2]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[2]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[3]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[3]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[3]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[4]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[4]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[4]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[5]/flap-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[5]/incidence-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/blade[5]/position-deg</node>
<type>float</type>
<format>%f</format>
</chunk>



<chunk>
<node>/rotors/main/cone-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone1-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone2-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone3-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/cone4-deg</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/roll-deg</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/rpm</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/stall</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/stall-filtered</node>
<type>double</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/torque</node>
<type>float</type>
<format>%f</format>
</chunk>

<chunk>
<node>/rotors/main/yaw-deg</node>
<type>float</type>
<format>%f</format>
</chunk>
</input>
</generic>
</PropertyList>
</syntaxhighlight>

== Examples ==
For setting up slaved visual channels, here are some of the options I have used:

<pre>
--enable-game-mode (--enable-fullscreen depending on glut vs. sdl)
--prop:/sim/menubar/visibility=false
--prop:/sim/ai/enabled=false (prevents the ai ATC text at the top of the screen.) --prop:/sim/ai-traffic/enabled=false (prevents strange planes from flying across a single view)
--prop:/sim/rendering/bump-mapping=false
--fov=35
--prop:/sim/view/config/heading-offset-deg=-35
--prop:/sim/view/config/pitch-offset-deg=3
--native-fdm=socket,in,60,,5505,udp
--native-ctrls=socket,in,60,,5506,udp
--fdm=null
</pre>

== Time Syncing ==
You can set /sim/time/cur-time-override to override the current time. If you do so, you also have to do this continously to keep the time up-to-date. The
value to feed into this property is the return value of the posix time() function. Unfortunately there is no output property for this values. The other input property for setting time is /sim/time/warp to set the offset to the system's clock.

Also see:
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33861.html
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38274.html
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38675.html
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40068.html

== Troubleshooting ==
Check the hardwired version number in the packet. That will get incremented when the structure changes. It's also there if you want to get crazy and build a system that can read the packet version and decode it differently for different versions. I suspect there probably was a change

Howto:Adding a canvas to a GUI dialog

2014-01-12T03:49:13Z

Anton:

{{Template:Canvas Navigation}}

'''Note: This tutorial describes features only available in FlightGear >= 2.8 ! (also note that the Canvas/PUI support described here will eventually be phased out, once PUI is finally retired, probably some time after the 3.0 release)'''

Using the combination of Nasal scripting, GUI dialogs and embedded canvas regions for 2D rendering, you can create standalone "FlightGear applications" in the form of self-contained dialogs that you can easily share with fellow FlightGear users. This can for example be used to create a plotting application like [[FGPlot]], which would look to FlightGear like a conventional dialog.

To create a new canvas dialog, you can just open an existing dialog from $FG_ROOT/gui/dialogs (e.e.g copy a simple dialog like the exit/about dialog), and then customize it according to your needs - i.e. by naming it "fgplot.xml", remove any stuff that you don't need, then add a new canvas widget to the dialog, like this:

<syntaxhighlight lang="xml">
<canvas>
<name>fgplot</name>
<valign>fill</valign>
<halign>fill</halign>
<stretch>true</stretch>
<pref-width>600</pref-width>
<pref-height>400</pref-height>
<nasal>

<load>
<![CDATA[

# you can add your canvas-specific code here
var my_canvas = canvas.get( cmdarg() ); # this will get a handle to the parent canvas :

print("Hello world from the embedded canvas section!\n");

]]>
</load>
</nasal>
</canvas>
</syntaxhighlight>
You can then use Nasal to animate your canvas and draw graphics etc.

== FGPlot ==
Here's a complete fgplot.xml example for $FG_ROOT/gui/dialogs, open it through the Nasal console, by running '''gui.showDialog("fgplot");'''

[[File:Fgplot-canvas.png|400px|Stub]]

'''(Note: As of 07/2013, FGPlot has significantly progressed since the early days of the prototype - see the [[FGPlot]] article for details and screen shots)'''

<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<PropertyList>
<name>fgplot</name>
<modal>false</modal>
<layout>vbox</layout>

<text>
<label>FGPlot</label>
</text>

<group>
<layout>hbox</layout>
<halign>fill</halign>
<default-padding>10</default-padding>
<empty><stretch>true</stretch></empty>

<empty><stretch>true</stretch></empty>

<canvas>
<name>fgplot</name>
<valign>fill</valign>
<halign>fill</halign>
<stretch>true</stretch>
<pref-width>600</pref-width>
<pref-height>400</pref-height>
<nasal>

<load>
<![CDATA[
# you can add your canvas-specific code here
var my_canvas = canvas.get( cmdarg() ); # this will get a handle to the parent canvas:

var root = my_canvas.createGroup();
var text = root.createChild("text")
.setText("Hello world from FGPlot v. 0.1 !")
.setTranslation(10, 30)
.setAlignment("left-top")
.setFontSize(20)
.setFont("LiberationFonts/LiberationSans-Regular.ttf")
.set("max-width", 380)
.setColor(1,0,0);

var graph = root.createChild("group");

var x_axis = graph.createChild("path", "x-axis")
.moveTo(10, 150)
.lineTo(380, 150)
.setColor(1,0,0)
.setStrokeLineWidth(3);

var y_axis = graph.createChild("path", "y-axis")
.moveTo(10, 30)
.lineTo(10, 250)
.setColor(1,0,0)
.setStrokeLineWidth(3);

var plot = graph.createChild("path", "data")
.setStrokeLineWidth(2)
.setColor(0,0,1)
.moveTo(10,150); # origin

var samples = [ # absolute coordinates
[50, 150], [100,140], [200,110], [270, 55]
];

foreach(var set; samples) {
plot.lineTo( set[0], set[1] );
}
]]>
</load>
</nasal>
</canvas>

<button>
<legend>Exit</legend>
<equal>true</equal>
<key>Esc</key>
<binding>
<command>dialog-close</command>
</binding>
</button>

<empty><stretch>true</stretch></empty>
</group>
</PropertyList>

</syntaxhighlight>

Next, you can use a timer to plot properties like '''/position/altitude-ft''' or '''/velocities/groundspeed-kt'''.

Bombable

2013-02-12T21:40:06Z

Anton: /* Bombable video */

[[File:Bombable4 4 600.png|thumb|Bombable 4.4]]
[[File:camel-through-wing.jpg|thumb|[[Sopwith Camel]]]]
[[File:spad-vs-camel.jpg|thumb]]
[[File:warthog-down-on-bay-bridge.jpg|thumb|[[A-10 Warthog]]]]

'''Bombable''' is an add-on to [[FlightGear]] that adds bombs, weapons, damage, fire, and explosion effects to FlightGear that work with the main [[aircraft]], [[scenery]], AI aircraft and other AI objects and multiplayer aircraft objects.

==Bombable features==
* [[Multiplayer]] dogfighting.
* AI dogfighting and bombing scenarios, using most any FlightGear aircraft that can shoot weapons or drop bombs, against planes, ships, and vehicles that dodge, turn, attack, shoot at you, and generally act like fighter pilots would
* Shootable/bombable moving tanks, [[jeep]]s, ships, and aircraft that catch fire, burn, explode, sink, crash, etc. These work with most any FlightGear aircraft that can fire weapons.
* AI scenarios that allow you to use FlightGear aircraft for air-to-ground, air-to-sea, and air-to-air combat missions against these targets
* Explode/burn when you crash
* Exceeding [[Howto: Define limits|aircraft limitations]] (excess g-forces, overspeed) adds damage to your aircraft and finally leads to shutdown/crash

==Downloading and using in FlightGear==
* [http://www.flightgear.org/forums/viewtopic.php?f=6&t=5742&p=43772 Download Bombable on the Flightgear Forums thread for Bombable]
* Instructions for installing and using Bombable are included in the Docs directory of the download file.

==List of Bombable Aircrafts==
[[Sopwith Camel]], SPAD VII, [[Fokker Dr.I]] Triplane, [[A6M2 Zero]], F6F Hellcat, [[Fairchild Republic A-10 Thunderbolt II|A-10 Warthog]], [[UFO]], and other included aircraft such the [[Polikarpov I16]].

==How to ading Bombable to a FlightGear aircraft==
* [[Howto: Adding Bombable to FlightGear Aircraft]]

==Related articles==
* [[Howto: Dogfighting over Multiplayer with Bombable]]
* [[Dicta Boelcke]] rules for dogfighting by the WWI aces
* [[Bombable_Development_Roadmap]]
==Bombable video==
{{#ev:youtube|LL7bdHrR8uI|auto|This is an embedded video!}}

==Readme==
http://wiki.flightgear.org/Bombable_Readme

==History==
FlightGear seems to have most all the pieces under the hood to make an excellent platform for simulating historical military aircraft, dogfighting and fighter plane tactics with aircraft of different eras, and bombing runs and other tactics from various historical eras, and other aircraft simulations that could depend on FlightGear's realistic, underlying flight models.

Some aircraft have implemented limited weapons, armament, and explosions. The A-10 Warthog was released, including an AI scenario for the A-10 to bomb M-1 tanks, which then exploded realistically.

The Bombable add-on was designed to put all the available FlightGear elements together as a proof of concept to see if FlightGear can be a realistic simulator for aircraft that include weapons and armament, working with AI aircraft and over Multiplayer, including:

* Realistic impact detection and damage assessment
* Damage tracking over AI and Multiplayer and communication of impacts and damage levels over Multiplayer
* AI aircraft, vehicles, and ships that can evade, attack, and generally act realistically
* Explosions, fires, and so on, upon damage and crash

Bombable was developed with the idea that in a realistic flight simulator environment, the rules and techniques of dogfighting and aerial warfare--like the World War I [[Dicta Boelcke]], by Oswald Boelcke, one of the first great aces of the war--would naturally develop and naturally play out.

==Status==
As of October 2011 (Bombable 4.4) the status is:
* Damage impact detection is the most advanced element in Bombable. It is greatly improved over FG's native impact detection system, and the framework is in place for further refinements or as a model for FG to implement more refined impact detection internally.

* Damage tracking and communication over Multiplayer works well in a very lightweight with a very low data rate. However, only a general damage percentage is tracked and communicated. Damage to different locations or systems is not simulated.

* AI aircraft behavior is controlled by a Nasal script that modifies FlightGear's AI system. This is Bombable's weakest point--in many ways the Nasal script is simply fighting the underlying AI code for control of the AI aircraft. Creating more realistic/intelligent AI fighter aircraft will require greater integration with FlightGear's AI systems.

* AI aircraft weapons systems are simulated through a probabilistic approach. And shown visually via FlightGear's Particle System. At this time it appears that creating and tracking AI weapon projectiles via FlightGear's submodel system, which simulates submodel dynamics and impacts precisely, is technically difficult and would have a drastic negative impact on the FlightGear framerate. Bombable follows the more promising of simulating AI weapon fire using FlightGear's particle system, which allows for visual display of numerous moving particles with little to no effect on the framerate and calculating weapons hits mathematically in a simple way that has minimal impact on framerate.

* AI AIRCRAFT MOVE VERTICALLY--AND DO LOOPS: AI aircraft now move much more realistically in the vertical direction. They do loops, dive, and all the rest. Their behavior (climb rates, dive rates, and so on) matches those of the corresponding FG aircraft. This makes for a much more realistic 3-D dogfighting experience in FlightGear.

* Proof of concept for explosions, fires, weapons damage animations, and crash animations is in place. All these elements could be refined for greater realism.

* REALISTIC ROLL RATES FOR AI AIRCRAFT: Roll rates are one the most important factors determining the effectiveness of fighter aircraft-- aircraft that can roll faster can turn faster. Now the roll rate for AI aircraft in scenarios can be customized, and bugs in the roll & turn routines for AI aircraft have been fixed.

* SIGNIFICANT PERFORMANCE IMPROVEMENTS: Bombable now makes much less of an impact on your framerate, and much less stuttering & slowdown at key points, like when numerous machine gun rounds are impacting.

* RELOCATE ANY SCENARIO TO YOUR LOCATION: Have an AI scenario based in San Francisco, but want to fly in London? No problem, just hit a button in the Bombable menu and your scenario comes to you, wherever you are. Damage levels for AI aircraft and objects are re-set. It's like loading a new scenario without having to re-start FlightGear.

* RE-SPAWN AI AIRCRAFT & OBJECTS: After you have shot down (or been shot down by!) AI aircraft or objects in scenarios, you can instantly re-spawn them and try again. (Available in the Bombable menu.)

The last two are kind of game changers--it's like being able to re-start/re-load a scenario instantly without having to re-start FG.

==Versions==

===Version 4.4===

Version 4.4 is a complete revamping of Bombable into more of a complete, cohesive system for Multiplayer and AI dogfighting and bombing. The accuracy of all the basic functions has been improved and made more realistic, and a number of new "Bombable- compatible" aircraft have been included, from WWI fighters to modern-day jet fighters.

* WEAPON HIT DETECTION GREATLY IMPROVED: Complete re-vamped system for detecting your weapon hits on AI or Multiplayeraircraft. It is no longer limited by FG's built-in, large "damage cylinder". It now extends the weapon's flight path within that cylinder to determine precisely how close the weapon hit on your target--allowing muchbetter modeling of hits, damage, and results.

* DAMAGE ANALYSIS SYSTEM GREATLY IMPROVED: In addition, the damage analysis system has been updated to calculate and use the momentum of weapons as the basis for determing damage of weapon hits. This has proven to be far more realistic and gives much better results thanthe previous ad-hoc method.

* GREATLY IMPROVED DAMAGE IMPACT ANIMATIONS: Previous versions of Bombable relied on FG's built-in impact animations. The result was that FG often showed the damage impact explosion when the projectile had actually made a clean miss of the aircraft. In Bombable 4.4, this problem is solved, with impact explosions being shown exactly where Bombable calculates they happen, and only when Bombable detects an actual hit with damage. So you have much tigher correspondence between what you see and whatdamage is recorded.

* The impact animations work for all types of small and large caliber guns and bombs. The system uses FG's excellent particle system to draw the gun and bomb impacts with almost not impact on framerate, and far less jerkiness than FG's usual submodel method. As a bonus, the new animations look much, much better as well, and the visual of the impact matches the actual damage of the impact quite well--that is, the visual size of a bomb explosion closely matches the actual damage area of the bomb; small caliber weapons hits show as smallerimpacts that large caliber weapons, etc.

* YOUR OWN WEAPONS CAN DAMAGE YOU: Drop a bomb on your own aircraft or too
near it? You'll see the results--damage to your aircraft. This makes bombing
runs far more realistic--if you get too close to the bomb impact, you'll feel
the results.

* IMPACT VISUALS, SMOKE, AND FIRE SHOWN ON SCENERY: If you drop a bomb on a
scenery or a building, you see an explosion and a long-lasting fire--
just as you do when you bomb a jeep, tank, or airplane. Previously, the
bombs, guns, rockets, and other armament only had an effect on AI and MP
aircraft, tanks, ships, and so on. Now armament hits affect almost everything
in the FlightGear world.

* RE-SPAWN AI AIRCRAFT: After you have shot down (or been shot down by!)
AI aircraft in scenarios, you can instantly re-spawn them and try again.
(Available in the Bombable menu.)

* BOMBABLE FOKKER DR.1 FIXED: Fixed/update the Fokker Dr.1 aircraft. It is now the same aircraft as distributed in FG 2.4.0 but with added historically accurate guns and an aircraft help file.

* BOMBABLE GRUMMAN F6F HELLCAT ADDED: Added a new Bombable-compatible aircraft, the Grumman F6F Hellcat. This makes a great foil to the A6M2 Zero, as they fought against each other in WWII. (As always, mucho thanks must go to the authors of the F6F aircraft--all I've done is update the weaponry to be historically accurate and add a thin veneer of tweaks to make the aircraft completely compatible with Bombable. All credit for aircraft design, systems, FDM, and everything else goes to the original authors, in this case EmanuelBaranger and others.)

* NEW SCENARIOs: New scenario to show off the F6F, one to show offthe Bombable UFO, and one to help with testing:

**BOMB-LakeTahoeWWIIB17BombersWithF6FCover.xml
**BOMB-MarinCountyUFOInvasion.xml
**BOMB-Kansas-City-Bombable-Testbed.xml

* BOMBABLE A-10 WARTHOG ADDED: The A-10 is the best plane to fly several scenarios and including it in the package means that it can be used to fly multiplayer bombable as well. It has several tweaks making it easier to use with the Bombable package and also improves an annoying bug where the A-10 slows FG's framerate massively after a few re-init/re-locates. (Again, all credit to the A-10 original authors--all I have done is adda few Bombable tweaks and specifics.)

* BOMBABLE UFO ADDED: This is mostly for testing; keys 1-9, 0, q, and w fire different weapons. A working AI version is included--so you can have dueling Bombable UFOs over Multiplayer or try the UFO dogfighting scenario (surprisingly fun!). Also a testbed scenario is included, and using the UFO with the BOMB-Kansas-City-Bombable-Testbed.xml scenario is the easiest way to test most Bombable functions, aircraft, and AI aircraft. (Based on FG's stock UFO, but with Bombable capabilitiesadded.)

* BOMB DAMAGE: Reconfigured damage impact of bombs; the bombs now act--lookand create damage--far closer to real data.

* NEW MENU: Re-vamped Bombable menu with new/streamlined/more sensible options.

* RESET DAMAGE: In the new Bombable menu you can reset damage for main aircraft and AI aircraft and objects.

* BOMBABLE SCENARIOS RENAMED: Renamed all scenarios that come with the package with prefix "BOMB-". This should make it easier to find the scenarios and also update or remove them when necessary.

* SMALLER SMOKE/FIRE OPTION: A small fire option, used where appropriate, so that fires/explosions/damage don't always look sooverly huge.

* UNUSABLE AIRCRAFT REMOVED: Removed unused/unusable aircraft from the distribution. Some of these are perfectly fine for general flying, but weapons or other features don't work well with Bombable, and having them listed in the menus when they didn't really work made forconfusion.

* SCENARIO FIXES: Some scenarios were not loading properly for some people in ver. 4.3. This might be because of inconsistencies in the case of some file and directory names. I worked on resolving thisissue, but please let me know if it is still happening.

* SCENARIOS RENAMED: Renamed all scenarios to start with "BOMB-". This should help us keep straight which scenarios work with Bombable and also troubleshoot and track down & fix problems with scenarios.

* AI WEAPONS IMPROVED: AI weapons now malfunction when the AI aircraft, vehicle, or ship is damaged.

* MISC. UPDATES: Updated included AI aircraft and scenarios to fit with the new impact detection system.

* FOR BOMBABLE AIRCRAFT DESIGNERS: If you have designed aircraft to use with Bombable, you should look at the sample AI aircraft provided to see updates to the Bombable dimensions, vulnerabilities, and weapons sections. You will need to re-tool your aircraft slightly, but when finished the results will be much better.

* BUG FIXES: Various small bug fixed and improvements, fixed a lot of the programs with scenarios, AI Aircraft, directories.

See the To Do file (many of which have now been done) for many more changes, updates, and improvements.

===Version 4.3===
------------------------

* Multiplayer dogfighting is now working in FG 2.4.0. (It broke sometime in the FG 2.X.X. series.) Use one of the MP-dogfighting- enabled planes included in the packet (Sopwith Camel-Bombable/Yasim, SPAD VII-Bombable, or FKDR1-Bombable/JSB, or A6M2-Bombable/YASim--use the versions marked as Guns/Bombable, not the default FG installs) and make sure your opponent does the same--you will both be able to shoot and damage each other, see damage reports, etc.

* Weapons on AI aircraft--which will shoot at you as you attack them--can now be placed in different locations and aimed indifferent directions.

In combat, they will shoot you if that location/direction is lined up with you. The AI B-17 Bomber included in the package will shoot at you from the rear; the M-1 tank will shoot towards the front at about a 45 degree angle, Jeep will shoot forwards and upwards,Ferries will shoot forward or backwards, etc.

The result is a far more realistic experience. Shooting bombers used to be like shooting fish in a barrel--now between the bombers shooting at you and the fighter planes coming in from high cover, you're lucky to score a few small hits and get out of therealive . . .

* The AI Weapons system was generally improved and weapon strength, direction, size, location, and effectiveness can be specified in the XML file for each AI aircraft type. (If you're creating your own Bombable-enable aircraft, just add weapons specs in the WEAPONSsection of AI aircraft; see enclosed AI/Aircraft files for examples.)

* Generally tweaked AI aircraft, attack & weapons routines, and AI scenarios for a better, more realistic experience. In particular,try:

** MarinCountyWWIIBombersWithCover.xml (fly A6M2-Bombable/YASim)
** MarinCountyCamelInvasion1-Simple.xml (fly Sopwith Camel-Bombable/YASim)

* Again worked on the problem of getting AI aircraft to climb and dive more realistically instead of sedately. The AI aircraft are farmore realistic/active in the vertical direction now.

* Bombable no longer overwrites existing aircraft or anything else in FG's installation. It will add new aircraft and a few other Bombable-specific files. All new/added aircraft have the suffix -Bombable. Bombable will overwrite-replace things from its ownprevious installation, but no other files.

Generally when flying Bombable's AI scenarios or flying over multiplayer with another person using Bombable, your best experience will be to use one of the aircraft provided (and identifiable by the -Bombable extension) or another aircraftspecifically set up to use Bombable's capabilities.

===Version 4.2===
------------------------
* Made numerous changes/updates/improvements related to getting Bombable working with FG 2.4.0.

* Found the FG 2.4.0 "reinit" problem in both M-1 and Jeep in AI/Aircraft & fixed

* Reconfigured the damage calculations for light weapons in the test_impact function. Result may be that it is harder/takes more hits than before to damage aircraft or objects. If it is too hard you can select both "Easy Mode" and "Super Easy Mode" together to make it quite a bit easier to both hit targets and create damage. This still needs some refinement but it is setting the groundworkfor a better, more consistent way of dealing with damage.

* Small refinements in display, damage reports, etc.

* FG 2.4.0 is doing this crazy thing where it reinitializes AI objects in scenario repeatedly and also (sometimes!) slips in non-AI objects like joystick inputs for initialization as AI/scenario objects. This results in massive slowdowns and other bizarre behavior. So I've set up checks to disallow repeated re-inits of AI objects and only allow AI and Multiplayer objects (as opposed joystick input devices, etc) to initialize themselves with Bombable. The ultimate solution here is a FG code fix, but in the meanwhilesome of the worst effects might be mitigated.

===Version 4.0===
------------------------
This is a beta release that works with Flightgear 2.4.0. Some AI aircraft characteristics have changed in FG 2.4.0 so there are someproblems and different behavior in the AI aircraft.

* Removed the "reinit" command in bombable.nas that made FG 2.4.0 croak.

* Removed the mp_broadcast.nas file that is no longer necessary with FG 2.4.0 (and in fact the old version included with Bombable made FG2.4.0 choke).

* FG 2.4.0 doesn't make the weight or mass of the armament available on impact (previous versions}}} did!), so a kludgy work-around wascreated.

* Numerous other tweaks and bug fixes.

===Version 3.0p===
------------------------
This is a bit of an alpha release and has not been as thoroughly
tested with all scenarios as previous releases.

AI AIRCRAFT ARE MORE MOBILE VERTICALLY: AI Aircraft dodge and chase
you more vertically, diving and climbing.

VARIOUS BUGFIXES

===Version 3.0o===
------------------------
AI AIRCRAFT SHOOT AT AND DAMAGE YOU: When in an AI dogfight, if you
let the AI aircraft get into position they have a chance to shoot at
and possibly damage you. This is working best with WWI AI Aircraft
(Camel, SPAD, Fokker) as in the Marin County Camel Invasion
scenarios, but it will also work with the Zero and Warthog scenarios.

MOSTLY FIXED MENU/OPTIONS SAVE/RESTORE BUG: Some of the options
still don't save/restore correctly, but most do now.

NUMEROUS OTHER BUGFIXES/SMALL IMPROVEMENTS

===Version 3.0n===
------------------------
AI AIRCRAFT DODGE AND 'ATTACK' REALISTICALLY: AI dogfights just
became 10X as realistic, as fighter planes will turn and attack,
just as fighter planes did in WWI and WWII. Try the Marin County
Camel Invasion and Marin County Zero Invasion scenarios for a taste
of how this works. (No weapons for AI aircraft yet--maybe in the
future.)

NEW SCENARIO--B-17 BOMBERS WITH FIGHTER COVER: Fly out of Marin
Ranch and attack a squadron of 6 B-17 Bombers. As you do so, the
fighter squadrons descend and swarm you. They don't fire at you
(yet! fodder for future versions!) but they turn aggressively
towards you, evade your shots, etc., just as real fighters would.

DAMAGED AI AIRCRAFT CRASH MORE REALISTICALLY

GREATLY IMPROVED, MORE REALISTIC DAMAGE ANALYSIS: Damage assessment
for guns is a lot more realistic, giving greater damage when you hit
closer to the center of the object and allowing for the possibility
that even small arms might strike a vital or explosive point,
causing catastrophic damage. For instance, you can now damage the
Nimitz or Eisenhower*--though it's still tough to sink.

MORE REALISTIC FIRE STARTING: One of the chief causes of combat
aircraft damage is the fires that even small caliber weapons can
cause--and fires are even more likely with heavier ammo that
includes incendiary (high explosive) materials. Bombable now models
that any hit may start a fire, and heavier rounds are more likely to
start files. Fires progressively damage the aircraft and eventually
bring it down. Beware that fires sometimes go out before completely
disabling the aircraft--so monitor the enemy aircraft to make sure
they do not recover and escape.

MORE REALISTIC AIRCRAFT SMOKE STARTING: Similar to fire starting,
each damaging hit has the possibility to cause damage that causes
the aircraft to emit a trail of smoke. The bigger/closer the hit,
the more likely to cause this damage.

BOMBABLE PREFERENCES/SETTINGS SAVED AND RESTORED AT STARTUP

FIXED EXCESSIVE DAMAGE REPORT PROBLEM: Aircraft would continually
report damage even after objects received 100% damage--now fixed.

NUMEROUS SMALL BUGFIXES

* Note: You can bomb the Nimitz/Eisenhower carriers if you have the
bombable carriers add-on:
http://www.flightgear.org/forums/viewtopic.php?f=2&t=7082

===Version 3.0m===
------------------------
Positive and negative G-force limits are now settable separately
(most aircraft have different limits for positive vs negative G, so
this adds some realism)

Bugfixes on damage & damage report

Every hit now registers via on-screen popup (vs previous behavior of
only showing damage when it increased past multiples of 5%)

Bugfixes on g-force damage that caused extraneous very high g forces
to cause random damage

Bugfixes in multiplayer communication, fixed problems when MP is
disabled or doesn't exist

Bugfix on bombable multiplayer unload (runtime error "listenerids")
and improvement to unload routines

Fixed Easy/Super Easy Mode malfunction (Super Easy Mode never
engaged; new default mode is Easy Mode which should give same
performance as previous default mode)

Tuned damage/vulnerabilities on ferries (San Francisco Ferry
Invasion scenario)

===Version 3.0L===
------------------------
OVERSPEED DETECTION/DAMAGE

G-FORCE AND OVERSPEED DETECTION OPTIONAL - Switches in the Bombable
menu to turn it off; turned off by default except for planes
included in Bombable package.

VULNERABILITIES FRAMEWORK FOR PRIMARY AIRCRAFT - allows max
acceleration, max speed parameters to be set individually per
aircraft (main aircraft) and then damage from
overspeed/overacceleration is accrued when those limits are exceeded.

BLACKOUT/REDOUT TUNABLE PER AIRCRAFT - allows blackout & redout
values to be set per aircraft--for instance to reflect that WWI
aircraft had no pressure suits or special high-G training. This will
help level the playing field and create uniformity in MP dogfighting
with similar aircraft.

G-FORCE AND OVERSPEED LIMITS AND DAMAGE AMOUNTS TUNED - for the four
aircraft included in the Bombable package (A6M2 Zero, Sopwith Camel,
SPAD VII, Fokker DR1) the g-force damage & overspeed damage
parameters have been individually tuned and are fairly realistic.

FIRES ONLY FOR APPROPRIATE DAMAGE - Overspeed & overacceleration
(g-force) damage doesn't start a fire, though it will still rack up
100% damage and shut you down.

BUGFIXES - a large number of bugfixes

===Version 3.0k===
* '''Excessive G-force damages your aircraft:''' Excessive g-force now adds damage to your airframe and can even make you crash. To avoid damaging your aircraft due to excessive g-force, always fly with blackout/redout turned on and avoid pulling g-forces much beyond those that make you blackout or redout.
* '''Zeros over marin county scenario:''' Marin County Zero Invasion scenario added.

===Version 3.0j (private release)===
* '''Burn/smoke on crash:''' Aircraft now catch fire, burn, and instantly go to 100% damage when they crash. This is broadcast via MP so others will see you burn when you crash.
* '''A5mw zero for dogfighting:''' A6M2 ready for MP dogfighting included in release.
* '''A6M2 Zero:''' Added historically accurate guns and cannons (fire with e and E) to A6M2 Zero.
* '''Bombable A62M Zero:''' Included Bombable version of the AI A6M2 Zero from Hellcat's Carrier Bombable project, but also made a few tweaks/improvements to he AI A6M2 for improved realism. See http://www.4shared.com/file/235605076/6101800f/carrier_bombable.html
* '''Dogfighting:''' Greatly improved dogfighting/multiplayer communication of damages
* '''Bugfix DR 1:''' Added keyboard firing switch to Fokker DR 1 (use the 'e' key to fire the weapons).
* '''Bugfixes:''' Many other miscellaneous bug fixes and improvements.

===Version 3.0i===
* '''Reset resets damage:''' In dogfighting, resetting or using the Location menu to change your location resets your damage to 0% and broadcasts that to others flying with you via multiplayer
* '''FlightGear 2.0 compatible:''' Tested and works with FG 2.0 as well as FG 1.9 and CVS versions between 1.9 and 2.0
* '''Bugfixes:''' Various small bugfixes

===Versions 3.0 through 3.0h===
* '''Bombable/shootable:''' Code to make objects, AI aircraft, MP aircraft bombable and shootable.
* '''Moving AI bombable/shootable objects:''' Code to allow AI aircraft, naval vessels, and surface vehicles to move (sort of) realistically and act as bombable/moving aerial targets.
* '''Scenarios:''' Bombing and dogfighting scenarios using these AI aircraft.
* '''Multiplayer dogfighting:''' Code to allow multiplayer (MP) communication of damage to aircraft, allowing multiplayer dogfighting
* '''Aircraft enhancements--weapons and dogfighting:''' Three WWI era aircraft enhanced with historically accurate weapons systems and prepared for MP dogfighting (Sopwith Camel, Fokker DR1, SPAD-VII)
* '''Contrails and smoke:''' MP aircraft capable of dogfighting, and some other MP and AI aircraft automatically have contrails and engine smoke trails. This makes it possible to locate the aircraft when doing MP dogfighting and generally adds to the realism.

== External links ==
[http://www.flightgear.org/forums/viewtopic.php?f=6&t=5742&p=43772 Download Bombable, Bombable forum thread]

[[Category:Bombable]]
[[Category:Bombable aircraft]]
[[Category:Combat related]]
[[Category:FlightGear add-ons]]
[[Category:Software]]

Airbus A380

2012-12-17T22:31:46Z

Anton: /* Front Panel */

{{infobox Aircraft
|image = A380 in flight.png
|name = Airbus A380
|type = Airliner
|livery = Airbus, Singapore, Qantas
|liverydbid = 5
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton
|fdm = JSBSim
|status-fdm = 4
|status-systems = 4
|status-cockpit = 4
|status-model = 4
|fgname = A380
|download =
|development = http://gitorious.org/airbus-aircraft/a380
}}
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.

The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest freight aircraft, with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).

== Aircraft help ==

An [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.

=== Startup ===
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)
# Start APU by clicking Master SW on the overhead
# Optionally enter flight plan on MFD
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]
# click on strobe and beacon lighting
# Switch Engine Start to IGN/START on overhead
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal
# you can turn off the APU by clicking the APU Master Sw.

=== Takeoff ===
# release parking brake
# Flaps to position 2 (0-4)
# Push throttle to around 50% N1 and wait to stabilise
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent
# Get Vr speed (~165 kts) and rotate
# pitch up to around 10deg and maintain 210kts
# Gear up
# AP1 enabled, push HDG to managed mode if flight plan entered
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down
# Before THR ACCEL retract flaps fully

=== Airbus Flight Guidance ===
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from;
# the flight plan as entered on the MFD
# the current phase of flight
# the performance characteristics as entered on the MFD
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]

=== Flight Management System ===
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.

If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.

== Development status/Issues/Todo ==
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].

=== Complete ===
* basic model
** fuselage
** wings (with wing flex)
** vertical and horizontal stabilisers
** flaps and slats
** engines, pylons and wing-tips
* FDM
* autopilot tuning
* engine, wind, seat-belt chime sounds
* pushback
* gear retraction and doors
* fuel tanks
* cargo, crew and passenger point mass
* CL, FLEX and TOGA thrust detents and A/THR
* majority of FMS
* SID/STAR parser
* Flight Guidance Computer
* simple electrical system
* door system, just needs objects to animate!
* animated jetway positions
* auto changeover level
* Environment Control System (cabin pressurisation)
* auto-tuned VOR on NAV2
* anti-ice and air packs take bleed air
* Rembrandt lighting for;
** cockpit lighting
** cockpit panel lighting
** wing lighting
** landing lights
** tail logo lighting
** cabin lighting

==== Glareshield ====
* altitude selected mode
* heading selected mode
* speed selected mode
* vertical managed mode
** SRS
** CLB
** OP CLB
** CRZ
** DES
** OP DES
* lateral managed mode
** NAV
** LOC
* speed managed mode
** CLB
** CRZ
** DES
* localizer and approach
* Flight Director, AP 1 and AP 2
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS
* ND nearby airports display switch on EFIS
* ND traffic display switch on EFIS
* airspeed AP control on FCU selectable between knots or mach value
* altitude selectable between 100ft and 1000ft
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)

==== Front Panel ====
* FMA on PFD (active and some armed lateral, vertical and thrust)
* indicated speed ribbon on PFD
* localizer and Glide scope indicators on PFD
* E/WD
* updated Nav Display
** ARC mode
** ROSE mode
** aerodrome moving map with 'ZOOM' scale in PLAN mode
** nearby airports on ND^
** multi-player and AI traffic on ND
** VOR/ADF left-hand and right-hand display
* E/WD checklists
* gear lever and indicators

==== Overhead ====
* apu start
* engine IGN
* strobe, beacon, nav lights, landing, nose
* seat-belt and no-smoking switches
* electrical panel
* air panel
* anti-ice panel

==== Pedestal ====
* Flaps lever
* MFD keyboard and number pad
* ECAM/SD page select
* System Display (ECAM/SD) (many pages)
** permanent data zone
** doors
** cruise
** engines
** apu
** fuel
** electrical AC
** electrical DC
* engine master switches
* MFD (several pages)
** active init
** active departure and SID
** active arrival and STAR
** T.O. Performance
** CRZ Performance
** Active Flight Plan

=== To Do ===
* window and door cut-outs (to work with door system and lighting)
* animate parking brake and <del>speed brake</del>
* cabin interior
* <del>tune LOC and G/S</del>
* flap/slat position on PFD
* <del>livery refresh</del>
* <del>landing</del>, wing, tail and cabin lighting
* <del>landing, wing, tail lighting switches</del>
* engine start sounds^
* complete PFD and EFIS selection switches
* <del>complete ND EFIS selection switches</del>^
* <del>complete ND display modes</del>
** PLAN
** LS^
** VOR^
** <del>MAP</del>
* add standard procedure check-lists to EWD
* complete remaining ECAM pages (skeleton pages already in-place)
** <del>DOOR</del>
** <del>APU</del>
** <del>ENGINE</del>
** COND
** WHEEL
** PRESSURE
** BLEED
** <del>ELEC AC</del>
** <del>ELEC DC</del>
** <del>FUEL</del>
** HYDRAULIC
* complete remaining MFD pages (too numerous to list)
* <del>animation for air/cond overhead panel</del>
* <del>animation for elec overhead panel</del>
* complete fuel overhead panel
* radio panels on pedestal
* <del>gear lever and indicators</del>
* thrust levers
* auto-brake selector
* standby instruments
* <del>calculation of V speeds as part of FMS</del>
* air systems; <del>cabin pressure</del> and temperature
* <del>complete DC and AC electrical system</del>
* <del>replace digit textures with text animation</del>
* fix up scaling of texture sizes^

^ = in recent Git development repository

== External links ==
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]

{{Airbus}}

[[Category:Airliners]]
[[Category:Quadjets]]
[[Category:Cargo aircraft]]

Airbus A380

2012-12-17T22:29:28Z

Anton: /* Front Panel */

{{infobox Aircraft
|image = A380 in flight.png
|name = Airbus A380
|type = Airliner
|livery = Airbus, Singapore, Qantas
|liverydbid = 5
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton
|fdm = JSBSim
|status-fdm = 4
|status-systems = 4
|status-cockpit = 4
|status-model = 4
|fgname = A380
|download =
|development = http://gitorious.org/airbus-aircraft/a380
}}
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.

The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest freight aircraft, with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).

== Aircraft help ==

An [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.

=== Startup ===
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)
# Start APU by clicking Master SW on the overhead
# Optionally enter flight plan on MFD
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]
# click on strobe and beacon lighting
# Switch Engine Start to IGN/START on overhead
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal
# you can turn off the APU by clicking the APU Master Sw.

=== Takeoff ===
# release parking brake
# Flaps to position 2 (0-4)
# Push throttle to around 50% N1 and wait to stabilise
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent
# Get Vr speed (~165 kts) and rotate
# pitch up to around 10deg and maintain 210kts
# Gear up
# AP1 enabled, push HDG to managed mode if flight plan entered
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down
# Before THR ACCEL retract flaps fully

=== Airbus Flight Guidance ===
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from;
# the flight plan as entered on the MFD
# the current phase of flight
# the performance characteristics as entered on the MFD
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]

=== Flight Management System ===
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.

If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.

== Development status/Issues/Todo ==
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].

=== Complete ===
* basic model
** fuselage
** wings (with wing flex)
** vertical and horizontal stabilisers
** flaps and slats
** engines, pylons and wing-tips
* FDM
* autopilot tuning
* engine, wind, seat-belt chime sounds
* pushback
* gear retraction and doors
* fuel tanks
* cargo, crew and passenger point mass
* CL, FLEX and TOGA thrust detents and A/THR
* majority of FMS
* SID/STAR parser
* Flight Guidance Computer
* simple electrical system
* door system, just needs objects to animate!
* animated jetway positions
* auto changeover level
* Environment Control System (cabin pressurisation)
* auto-tuned VOR on NAV2
* anti-ice and air packs take bleed air
* Rembrandt lighting for;
** cockpit lighting
** cockpit panel lighting
** wing lighting
** landing lights
** tail logo lighting
** cabin lighting

==== Glareshield ====
* altitude selected mode
* heading selected mode
* speed selected mode
* vertical managed mode
** SRS
** CLB
** OP CLB
** CRZ
** DES
** OP DES
* lateral managed mode
** NAV
** LOC
* speed managed mode
** CLB
** CRZ
** DES
* localizer and approach
* Flight Director, AP 1 and AP 2
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS
* ND nearby airports display switch on EFIS
* ND traffic display switch on EFIS
* airspeed AP control on FCU selectable between knots or mach value
* altitude selectable between 100ft and 1000ft
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)

==== Front Panel ====
* FMA on PFD (active and some armed lateral, vertical and thrust)
* indicated speed ribbon on PFD
* localizer and Glidescope indicators on PFD
* E/WD
* updated Nav Display
** ARC mode
** ROSE mode
** aerodrome moving map with 'ZOOM' scale in PLAN mode
** nearby airports on ND^
** multi-player and AI traffic on ND
** VOR/ADF left-hand and right-hand display
* E/WD checklists
* gear lever and indicators

==== Overhead ====
* apu start
* engine IGN
* strobe, beacon, nav lights, landing, nose
* seat-belt and no-smoking switches
* electrical panel
* air panel
* anti-ice panel

==== Pedestal ====
* Flaps lever
* MFD keyboard and number pad
* ECAM/SD page select
* System Display (ECAM/SD) (many pages)
** permanent data zone
** doors
** cruise
** engines
** apu
** fuel
** electrical AC
** electrical DC
* engine master switches
* MFD (several pages)
** active init
** active departure and SID
** active arrival and STAR
** T.O. Performance
** CRZ Performance
** Active Flight Plan

=== To Do ===
* window and door cut-outs (to work with door system and lighting)
* animate parking brake and <del>speed brake</del>
* cabin interior
* <del>tune LOC and G/S</del>
* flap/slat position on PFD
* <del>livery refresh</del>
* <del>landing</del>, wing, tail and cabin lighting
* <del>landing, wing, tail lighting switches</del>
* engine start sounds^
* complete PFD and EFIS selection switches
* <del>complete ND EFIS selection switches</del>^
* <del>complete ND display modes</del>
** PLAN
** LS^
** VOR^
** <del>MAP</del>
* add standard procedure check-lists to EWD
* complete remaining ECAM pages (skeleton pages already in-place)
** <del>DOOR</del>
** <del>APU</del>
** <del>ENGINE</del>
** COND
** WHEEL
** PRESSURE
** BLEED
** <del>ELEC AC</del>
** <del>ELEC DC</del>
** <del>FUEL</del>
** HYDRAULIC
* complete remaining MFD pages (too numerous to list)
* <del>animation for air/cond overhead panel</del>
* <del>animation for elec overhead panel</del>
* complete fuel overhead panel
* radio panels on pedestal
* <del>gear lever and indicators</del>
* thrust levers
* auto-brake selector
* standby instruments
* <del>calculation of V speeds as part of FMS</del>
* air systems; <del>cabin pressure</del> and temperature
* <del>complete DC and AC electrical system</del>
* <del>replace digit textures with text animation</del>
* fix up scaling of texture sizes^

^ = in recent Git development repository

== External links ==
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]

{{Airbus}}

[[Category:Airliners]]
[[Category:Quadjets]]
[[Category:Cargo aircraft]]

Airbus A380

2012-12-17T22:25:51Z

Anton: /* Glareshield */

{{infobox Aircraft
|image = A380 in flight.png
|name = Airbus A380
|type = Airliner
|livery = Airbus, Singapore, Qantas
|liverydbid = 5
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton
|fdm = JSBSim
|status-fdm = 4
|status-systems = 4
|status-cockpit = 4
|status-model = 4
|fgname = A380
|download =
|development = http://gitorious.org/airbus-aircraft/a380
}}
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.

The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest freight aircraft, with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).

== Aircraft help ==

An [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.

=== Startup ===
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)
# Start APU by clicking Master SW on the overhead
# Optionally enter flight plan on MFD
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]
# click on strobe and beacon lighting
# Switch Engine Start to IGN/START on overhead
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal
# you can turn off the APU by clicking the APU Master Sw.

=== Takeoff ===
# release parking brake
# Flaps to position 2 (0-4)
# Push throttle to around 50% N1 and wait to stabilise
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent
# Get Vr speed (~165 kts) and rotate
# pitch up to around 10deg and maintain 210kts
# Gear up
# AP1 enabled, push HDG to managed mode if flight plan entered
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down
# Before THR ACCEL retract flaps fully

=== Airbus Flight Guidance ===
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from;
# the flight plan as entered on the MFD
# the current phase of flight
# the performance characteristics as entered on the MFD
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]

=== Flight Management System ===
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.

If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.

== Development status/Issues/Todo ==
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].

=== Complete ===
* basic model
** fuselage
** wings (with wing flex)
** vertical and horizontal stabilisers
** flaps and slats
** engines, pylons and wing-tips
* FDM
* autopilot tuning
* engine, wind, seat-belt chime sounds
* pushback
* gear retraction and doors
* fuel tanks
* cargo, crew and passenger point mass
* CL, FLEX and TOGA thrust detents and A/THR
* majority of FMS
* SID/STAR parser
* Flight Guidance Computer
* simple electrical system
* door system, just needs objects to animate!
* animated jetway positions
* auto changeover level
* Environment Control System (cabin pressurisation)
* auto-tuned VOR on NAV2
* anti-ice and air packs take bleed air
* Rembrandt lighting for;
** cockpit lighting
** cockpit panel lighting
** wing lighting
** landing lights
** tail logo lighting
** cabin lighting

==== Glareshield ====
* altitude selected mode
* heading selected mode
* speed selected mode
* vertical managed mode
** SRS
** CLB
** OP CLB
** CRZ
** DES
** OP DES
* lateral managed mode
** NAV
** LOC
* speed managed mode
** CLB
** CRZ
** DES
* localizer and approach
* Flight Director, AP 1 and AP 2
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS
* ND nearby airports display switch on EFIS
* ND traffic display switch on EFIS
* airspeed AP control on FCU selectable between knots or mach value
* altitude selectable between 100ft and 1000ft
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)

==== Front Panel ====
* FMA on PFD (active and some armed lateral, vertical and thrust)
* indicated speed ribbon on PFD
* localiser and Glidescope indicators on PFD
* E/WD
* updated Nav Display
** ARC mode
** ROSE mode
** aerodrome moving map with 'ZOOM' scale in PLAN mode
** nearby airports on ND^
** multi-player and AI traffic on ND
** VOR/ADF left-hand and right-hand display
* E/WD checklists
* gear lever and indicators

==== Overhead ====
* apu start
* engine IGN
* strobe, beacon, nav lights, landing, nose
* seat-belt and no-smoking switches
* electrical panel
* air panel
* anti-ice panel

==== Pedestal ====
* Flaps lever
* MFD keyboard and number pad
* ECAM/SD page select
* System Display (ECAM/SD) (many pages)
** permanent data zone
** doors
** cruise
** engines
** apu
** fuel
** electrical AC
** electrical DC
* engine master switches
* MFD (several pages)
** active init
** active departure and SID
** active arrival and STAR
** T.O. Performance
** CRZ Performance
** Active Flight Plan

=== To Do ===
* window and door cut-outs (to work with door system and lighting)
* animate parking brake and <del>speed brake</del>
* cabin interior
* <del>tune LOC and G/S</del>
* flap/slat position on PFD
* <del>livery refresh</del>
* <del>landing</del>, wing, tail and cabin lighting
* <del>landing, wing, tail lighting switches</del>
* engine start sounds^
* complete PFD and EFIS selection switches
* <del>complete ND EFIS selection switches</del>^
* <del>complete ND display modes</del>
** PLAN
** LS^
** VOR^
** <del>MAP</del>
* add standard procedure check-lists to EWD
* complete remaining ECAM pages (skeleton pages already in-place)
** <del>DOOR</del>
** <del>APU</del>
** <del>ENGINE</del>
** COND
** WHEEL
** PRESSURE
** BLEED
** <del>ELEC AC</del>
** <del>ELEC DC</del>
** <del>FUEL</del>
** HYDRAULIC
* complete remaining MFD pages (too numerous to list)
* <del>animation for air/cond overhead panel</del>
* <del>animation for elec overhead panel</del>
* complete fuel overhead panel
* radio panels on pedestal
* <del>gear lever and indicators</del>
* thrust levers
* auto-brake selector
* standby instruments
* <del>calculation of V speeds as part of FMS</del>
* air systems; <del>cabin pressure</del> and temperature
* <del>complete DC and AC electrical system</del>
* <del>replace digit textures with text animation</del>
* fix up scaling of texture sizes^

^ = in recent Git development repository

== External links ==
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]

{{Airbus}}

[[Category:Airliners]]
[[Category:Quadjets]]
[[Category:Cargo aircraft]]

Airbus A380

2012-12-17T22:24:38Z

Anton: /* Glareshield */

{{infobox Aircraft
|image = A380 in flight.png
|name = Airbus A380
|type = Airliner
|livery = Airbus, Singapore, Qantas
|liverydbid = 5
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton
|fdm = JSBSim
|status-fdm = 4
|status-systems = 4
|status-cockpit = 4
|status-model = 4
|fgname = A380
|download =
|development = http://gitorious.org/airbus-aircraft/a380
}}
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.

The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest freight aircraft, with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,200 kilometres (8,200 nm), sufficient to fly from New York to Hong Kong for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).

== Aircraft help ==

An [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.

=== Startup ===
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)
# Start APU by clicking Master SW on the overhead
# Optionally enter flight plan on MFD
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]
# click on strobe and beacon lighting
# Switch Engine Start to IGN/START on overhead
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal
# you can turn off the APU by clicking the APU Master Sw.

=== Takeoff ===
# release parking brake
# Flaps to position 2 (0-4)
# Push throttle to around 50% N1 and wait to stabilise
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent
# Get Vr speed (~165 kts) and rotate
# pitch up to around 10deg and maintain 210kts
# Gear up
# AP1 enabled, push HDG to managed mode if flight plan entered
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down
# Before THR ACCEL retract flaps fully

=== Airbus Flight Guidance ===
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from;
# the flight plan as entered on the MFD
# the current phase of flight
# the performance characteristics as entered on the MFD
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]

=== Flight Management System ===
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: $FG_ROOT/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.

If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.

== Development status/Issues/Todo ==
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].

=== Complete ===
* basic model
** fuselage
** wings (with wing flex)
** vertical and horizontal stabilisers
** flaps and slats
** engines, pylons and wing-tips
* FDM
* autopilot tuning
* engine, wind, seat-belt chime sounds
* pushback
* gear retraction and doors
* fuel tanks
* cargo, crew and passenger point mass
* CL, FLEX and TOGA thrust detents and A/THR
* majority of FMS
* SID/STAR parser
* Flight Guidance Computer
* simple electrical system
* door system, just needs objects to animate!
* animated jetway positions
* auto changeover level
* Environment Control System (cabin pressurisation)
* auto-tuned VOR on NAV2
* anti-ice and air packs take bleed air
* Rembrandt lighting for;
** cockpit lighting
** cockpit panel lighting
** wing lighting
** landing lights
** tail logo lighting
** cabin lighting

==== Glareshield ====
* altitude selected mode
* heading selected mode
* speed selected mode
* vertical managed mode
** SRS
** CLB
** OP CLB
** CRZ
** DES
** OP DES
* lateral managed mode
** NAV
** LOC
* speed managed mode
** CLB
** CRZ
** DES
* localizer and approach
* FlightDirector, AP 1 and AP 2
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS
* ND nearby airports display switch on EFIS
* ND traffic display switch on EFIS
* airspeed AP control on FCU selectable between knots or mach value
* altitude selectable between 100ft and 1000ft
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)

==== Front Panel ====
* FMA on PFD (active and some armed lateral, vertical and thrust)
* indicated speed ribbon on PFD
* localiser and Glidescope indicators on PFD
* E/WD
* updated Nav Display
** ARC mode
** ROSE mode
** aerodrome moving map with 'ZOOM' scale in PLAN mode
** nearby airports on ND^
** multi-player and AI traffic on ND
** VOR/ADF left-hand and right-hand display
* E/WD checklists
* gear lever and indicators

==== Overhead ====
* apu start
* engine IGN
* strobe, beacon, nav lights, landing, nose
* seat-belt and no-smoking switches
* electrical panel
* air panel
* anti-ice panel

==== Pedestal ====
* Flaps lever
* MFD keyboard and number pad
* ECAM/SD page select
* System Display (ECAM/SD) (many pages)
** permanent data zone
** doors
** cruise
** engines
** apu
** fuel
** electrical AC
** electrical DC
* engine master switches
* MFD (several pages)
** active init
** active departure and SID
** active arrival and STAR
** T.O. Performance
** CRZ Performance
** Active Flight Plan

=== To Do ===
* window and door cut-outs (to work with door system and lighting)
* animate parking brake and <del>speed brake</del>
* cabin interior
* <del>tune LOC and G/S</del>
* flap/slat position on PFD
* <del>livery refresh</del>
* <del>landing</del>, wing, tail and cabin lighting
* <del>landing, wing, tail lighting switches</del>
* engine start sounds^
* complete PFD and EFIS selection switches
* <del>complete ND EFIS selection switches</del>^
* <del>complete ND display modes</del>
** PLAN
** LS^
** VOR^
** <del>MAP</del>
* add standard procedure check-lists to EWD
* complete remaining ECAM pages (skeleton pages already in-place)
** <del>DOOR</del>
** <del>APU</del>
** <del>ENGINE</del>
** COND
** WHEEL
** PRESSURE
** BLEED
** <del>ELEC AC</del>
** <del>ELEC DC</del>
** <del>FUEL</del>
** HYDRAULIC
* complete remaining MFD pages (too numerous to list)
* <del>animation for air/cond overhead panel</del>
* <del>animation for elec overhead panel</del>
* complete fuel overhead panel
* radio panels on pedestal
* <del>gear lever and indicators</del>
* thrust levers
* auto-brake selector
* standby instruments
* <del>calculation of V speeds as part of FMS</del>
* air systems; <del>cabin pressure</del> and temperature
* <del>complete DC and AC electrical system</del>
* <del>replace digit textures with text animation</del>
* fix up scaling of texture sizes^

^ = in recent Git development repository

== External links ==
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]

{{Airbus}}

[[Category:Airliners]]
[[Category:Quadjets]]
[[Category:Cargo aircraft]]

Boeing B-52

2012-12-13T23:14:53Z

Anton: /* Aircraft help */

{{infobox Aircraft
|image = B-52F.jpg
|alt =Boeing B-52F
|name = B-52 Stratofortress
|type = Military aircraft
|fdm = YASim
|status = beta
|authors = Lee Elliott
|fgname = B-52F
|download=http://flightgear.org/Downloads/aircraft/index.shtml#B-52F
}}
The '''Boeing B-52 Stratofortress''' is a long-range, subsonic, jet-powered, strategic bomber operated by the United States Air Force (USAF) since 1955.

== Variants ==
Currently only one variant is modeled in [[FlightGear]]:
* '''B-52F''', the aircraft was given J57-P-43W engines with a larger capacity water injection system and new alternators. The aircraft had a problem with fuel leaks, which were eventually solved by service modifications Blue Band, Hard Shell, and QuickClip.

== Aircraft help ==
{| class="prettytable"
!Key
!Function
|-
|Ctrl-z
|Steer right
|-
|Ctrl-\
|Steer left
|-
|K
|Toggle trajectory markers on & off
|-
|U
|Update the drop-view location
|}

* Approach AoA 1.0 deg
* Flaps have only two settings: extended or retracted
* Flap cycle time 60 seconds

=== AP Altitude Mode Controller ===
The altitude mode controller appears as a strip reading

[[File:AP_mode_B52.jpg]]

The meaning of the different modes are:
* AH = Altitude Hold
* TF = Terrain Following
* TO = Automatic Take-Off
* IL = Automatic Instrument Landing
* MC = Mach Climb

==== AH Mode ====
The AH (Altitude Hold) function is intended to hold the aircraft at the altitude set in /autopilot/settings/target-altitude-ft. When engaged, the set altitude can be changed by using the standard FG keystrokes.

==== TF Mode ====
The TF (Terrain Following) function is intended to hold the aircraft at a constant distance above ground level (agl). The separation distance is set in /autopilot/settings/target-agl-ft. It is not currently possible to change this setting from either of the panels - it must be changed via the property browser.

It should also be noted that FG does not currently provide a look-ahead function that could be used for a proper terrain following system so the current terrain following function works by simply checking the agl directly below the a/c. This means that the TF function can only react after the separation has increased or decreased and will not stop you from flying into steep sided ground elevations i.e. cliffs.

==== TO Mode ====
The TO (automatic take-off) mode will attempt to perform a take-off in the direction that the a/c is pointing - there's no way that I know of
to actually track the runway.

You need to be on the ground and with the flaps fully extended before this mode will function.

Once the a/c has achieved 260 kias it will switch to altitude-hold and true heading-hold.

==== IL Mode ====
The IL (automatic instrument landing) mode will attempt to get the a/c on the nav1 ILS heading & then follow it, configure the a/c for landing and get it on to the glideslope, follow the glide-slope down and perform a landing. Both the front and rear landing gear will be correctly aligned for any cross-winds but you will need to steer the front gear as the rear gear are aligned with the fuselage during the roll-out.

The engines and elevator, however, will remain under the control of the auto-landing script until touchdown.

The auto-landing script limits the max descent-rate on the glideslope so you will need to ensure that you're not too high/too close when trying this mode.

It is, of course, not very reliable, but gives some idea of what needs to be done at various phases of landing i.e. getting the speed down and
coping with the huge trim changes required when the flaps are extended.

==== MC Mode ====
The MC (Mach Climb Mode) function is designed to command the highest climb rate that can be sustained for a given mach setting and is only enabled when mach-hold-by-throttle is selected on the AP Speed Controller. This function has some limitations, one being that it works best when the aircraft is travelling below the set mach number and is accelerating to achieve it. If the aircraft is already travelling at the set mach number the climb rate is likely to be very low and it may be necessary to temporarily reduce speed, and then increase it again (using the AP Speed Controller) or force a climb by pulling back on the stick.

* Click on AP Mode to turn off all A/P locks.
* The 2D VFR panel is just a place-holder for the radio instruments - use the 2D mini-panel to control the aircraft (Shift-s).
* Set the Altitude hold and TF/AGL settings via the autopilot menu. If an AP Mode is grayed out it is not available
* Use the yaw display to align the landing main gear in cross-wind landings - the rear gear will center itself once the speed is below the transition speed for normal steering.
* To use Mach-Climb mode click on the light blue M in the speed instrument to select mach-hold mode, set the required mach you want to maintain, select MC and then either turn off speed locks (Ctrl-s) and set the throttles manually or select KIAS hold (yellow K) and set a high speed - this will force the throttles to 100%.

== Development status/Issues/Todo ==
'''Outside:'''
* flaps are animated, but the shape of the wing does not change when flaps are extended. This means we have 2 flaps. One that is animated and another one that is not animated
* cockpit windows are transparent, but you can see the runway instead of the cockpit when looking through them from the outside
* turbines do not rotate
* no aircraft light available
* aircraft has no wheel well area for the landing gears
* no jetstream visible
* nozzle do not change shape when changing thrust
* there are no flaps when using reverse thrust - weapons bay door can't be opened

'''3d Cockpit:'''
* 3d cockpit is not available

'''General:'''
* no engine sound when running at lowest engine power
* aircraft is not set on the correct elevation when starting flightsgear. Lowest part of the aircraft is approximately 0.40 m below the ground
* when you take off,you must close your flaps or you will not be able to fly higher

== External links ==
* [http://en.wikipedia.org/wiki/B-52 Wikipedia article]

{{Boeing}}

[[Category:Bomber aircraft]]

Howto:Understand console output

2012-12-06T00:48:24Z

Anton: /* Unknown Chunk: ***UNKNOWN*** (0xA08A) */

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

== Errors with known solutions ==
=== Aircraft uses deprecated node egt_degf. Please upgrade to egt-degf ===
The aircraft should be updated to make use of the renamed egt-degf property but it will still work as expected. You could contact the aircraft's author but he/she is probably already aware of this.

=== Airports/.... ... Done ===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG SCENERY]]/Airports</tt> directory.

=== Bad operation output detected in configuration file ===
[[JSBSim]] reports that a <output> tag is incorrectly placed in the aircraft's FDM. When used in a <fcs_function>, it should be outside the innter <function> tags, so like:
<syntaxhighlight>
<fcs_function name="Flap Cmd Deg">
<function>
<product>
<property>fcs/flap-cmd-norm</property>
<value>30</value>
</product>
</function>
<output>fcs/flap-cmd-deg1</output>
</fcs_function>
</syntaxhighlight>

=== Base package check failed ... Found version ... at: ... Please upgrade to version: ===
When using [[Git]], the data must match the binary or compilation. You cannot use data from a different date than the binary's release date.

=== Base package check failed ... Found version [none] at: ... Please upgrade to version: ===
FlightGear was unable to find the [[$FG ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.

=== Cannot find specified aircraft ===
Shows up when you use an incorrect aircraft name in the --aircraft=... command. Check the correct name by running --show-aircraft, or by looking at the aircraft's -set.xml file (eg. <tt>--aircraft=737-300</tt> for <tt>737-300-set.xml</tt>).

=== condition: comparison without property[1] or value ===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

=== Could not find at least one of the following objects for animation: ===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. Also in the .xml file make sure that there are not spaces at the beginning or end of the object name. If you are not the aircraft's author you can safely ignore such warnings.

=== creating 3D noise texture... DONE ===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

=== Error: bind() failed in make_server_socket() ===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

=== Error Building Technique: findAttr: could not find attribute bool ===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

=== Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed ===
Your computer is not connected with the internet, while a certain enabled feature (eg. multiplayer) does require an internet connection.

=== Error: RenderTexture requires the following unsupported OpenGL extensions... ===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

=== Failed to find .... in apt.dat.gz ===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher. Note that you might need to enable a scenario in combination with a --carrier= command.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

=== Failed to open file ... ===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

=== Fatal error: illegal character after . or .. ===
Some .xml file contains a fault. Possible solutions:
* To refer to a top-level property in the tree, <tt>../</tt> should be used instead of <tt>.../</tt>

=== Fatal error: mismatched tag ... ===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

=== Fatal error: name must begin with alpha or '_' ===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

=== Failed to tie property fcs/ to object methods ===
This [[JSBSim]] error comes up when there are unnamed components (eg. switches) in the FDM of an aircraft. Components must have unique names, from which properties will be created. As long as you are not overwriting an existing property, the <tt>name="..."</tt> can be used to output the components result to a property.

=== Fatal error: unclosed token ===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.

=== FGMultiplayerMgr::Open - Failed to bind receive socket ===
This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

=== FGMultiplayMgr::MP_ProcessData: No such file or directory ===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

=== FGMultiplayMgr - No receiver port, Multiplayermode disabled ===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

=== FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting ===
FlightGear found a reference in the [[FDM]] to a non-existing property.

=== FGPropertyManager::GetNode() No node found for ... The property ... is undefined. ===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

=== Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed ===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG ROOT]]/Timezone/time.tab</tt> with it.

=== Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model ===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

=== freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance ===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

=== Gate ... doesn't seem to have routes associated with it ===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

=== glLinkProgram "" Failed ===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

=== loading scenario '...' ===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

=== Model not found: ... ===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

=== Nasal runtime error: nil used in numeric context ===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG ROOT]]/Nasal/</tt> script.

=== Near camera not rendering ===
[[File:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

=== No render bin name specified in render bin section ===
Update [[SimGear]] (or binary) and your data directory.

=== No render bin number specified in render bin section ===
Update [[SimGear]] (or binary) and your data directory.

=== ... not a valid win32 application ===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

=== OBJECT_SIGN: unexpected } in sign contents ===
One of the OBJECT_SIGN lines in the .stg file (of the tile that was loaded when this error showed up) contains a fault. Note that <tt>}</tt> must be preceded by a <tt>{</tt> character.

=== OBJECT_SIGN: unsupported glyph `.' ===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

=== OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source. ===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[Git]] version or solve the problem yourself and let someone commit the patch.

=== OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data. ===
Disabling sound is a temporarily solution for this problem.

=== osgDB ac3d reader: could not find texture... ===
See [[#Failed to open file ...|Failed to open file ...]]

=== osgDB ac3d reader: detected surface with less than 3 vertices! ===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

=== Program's vertex attrib binding ..., usrAttr... ===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

=== QNAN ===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

=== Scaling image... ===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

=== ssgInit called without a valid OpenGL context ===
In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

=== The system cannot find the file specified ===
* If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again. '''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.
* Make sure you did set the right executable (<tt>fgfs.exe</tt>) on the first page of the [[FlightGear Launch Control]].

=== Time zone reading failed ===
This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files

=== Traffic manager could not find airport ===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

=== Unable to choose requested pixel format ===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

=== Unable to find airport details for .... in FGTower::Init() ===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG ROOT]]/ATC/default.tower</tt> and <tt>[[$FG ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

=== Unable to open aircraft directory ===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description ===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

=== Unknown exception to the main loop. Aborting... Possible cause: No such file or directory ===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear Launch Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

=== Unknown exception in main loop. Aborting... Possible cause: Not enough space ===
See [[Howto: Improve framerates#Optimus Technology]].

When your computer does not have the Optimus Technolog (NVidia) or Hybrid Graphics technology (ATI), you are likely to be unable to run FlightGear. Integrated graphics cards are very weak; too weak for FlightGear. You can try to switch of some of the eye-candy though, but even then the same error may appear...
It may be useful to check the latest drivers for your graphic card.
•If you have a Nvidia GPU, then visit http://wiki.flightgear.org/Howto:Improve_framerates#nVidia.
•For '''ATI line''' of video cards, look at this site: http://www.amd.com/us/products/technologies/amd-catalyst/pages/catalyst.aspx .You should find a file named "Catalyst control center", which allow you to modify the behaviour of your GPU with flightgear. I mean the Antialiasing control, the triple buffering, etc.
=== WARNING: Couldn't convert texture... ===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

=== Warning: Could not find plugin to read objects from file ... ===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

=== Warning: Picked up TriangleIntersect ===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

=== Warning: TangentSpaceGenerator: unknown primitive mode 9 ===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

=== YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations ===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

=== YASim SOLUTION FAILURE: Zero length fuselage ===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

=== YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! ===
Make sure the [[JSBSim]] [[FDM]] of the aircraft has a <code><fdm_config version="2.0"</code> tag.

== Errors without known solutions ==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

=== Aircraft propulsion element has problems in file ... ===

=== AL Error (fx): Invalid Value at pitch and gain ===
The sound effect's pitch (high or low) and gain (volume multiplication factor) values are not valid.

=== AL Error (sound manager): Invalid Operation at update ===

=== AL Error (sound manager): Invalid Value at buffer add data No such buffer! ===

=== Failed to execute command nasal ===
Has something to do with the [[Nasal]] scripting language used by FlightGear.

=== Failed to tie (or untie while closing) property ... to object methods ===
A JSBSim error.

=== FGMultiplayMgr::MP_ProcessData - message from ... has invalid length! ===

=== FGMultiplayMgr::MP_ProcessData: Result too large ===

===GPS: malformed route, index=1===

=== Mesa 7.3 implementation error: bad texture level in r300UploadSubImage ===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

=== Nasal runtime error: stack overflow ===

=== No image file for texture, using white ===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

=== No path in /sim/sound/path ===
You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

=== OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos ===

Has something to do with OpenAL not understanding where the sound comes from.

=== OpenAL error (AL_ILLEGAL_COMMAND): set_volume ===

Has something to do with OpenAL not understanding the sound volume.

=== PT_vs_hpt: ran out of layers ===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

=== Tried to initialize a non-existent engine! ===
The developer of the aircraft did not code the engine properly.

'''Developers:''' Check that the engine.xml file, FDM.xml, and -set.xml is coded properly.

=== Unknown Chunk: ***UNKNOWN*** (0xA08A) ===
I use Autodesk 3ds Max (.3ds) occurs when the 3D data model.

Solution converts the file format AC3D.

=== Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,) ===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

=== Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus ===
It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

=== WARNING: PUI: Too many live puInterfaces open at once! ===
Appears when printing large outputs (very) frequently on the screen.

=== Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements ===
[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

[[Category:Howto|Console output]]

Howto:Understand console output

2012-12-06T00:44:44Z

Anton: /* Unknown Chunk: ***UNKNOWN*** (0xA08A) */

This document lists '''[[FlightGear]] errors''', how to get rid of them and other '''console output'''. If FlightGear quits but does not give you any error, try increasing the [[FlightGear Launch Control#Debugging|Log Level]].

Errors can appear in various locations, but the most common one is the console (a black window), which pops up when you run fgfs.exe.

== Errors with known solutions ==
=== Aircraft uses deprecated node egt_degf. Please upgrade to egt-degf ===
The aircraft should be updated to make use of the renamed egt-degf property but it will still work as expected. You could contact the aircraft's author but he/she is probably already aware of this.

=== Airports/.... ... Done ===
This is not an error. The message lets us know that [[TerraSync]] is updating the <tt>[[$FG SCENERY]]/Airports</tt> directory.

=== Bad operation output detected in configuration file ===
[[JSBSim]] reports that a <output> tag is incorrectly placed in the aircraft's FDM. When used in a <fcs_function>, it should be outside the innter <function> tags, so like:
<syntaxhighlight>
<fcs_function name="Flap Cmd Deg">
<function>
<product>
<property>fcs/flap-cmd-norm</property>
<value>30</value>
</product>
</function>
<output>fcs/flap-cmd-deg1</output>
</fcs_function>
</syntaxhighlight>

=== Base package check failed ... Found version ... at: ... Please upgrade to version: ===
When using [[Git]], the data must match the binary or compilation. You cannot use data from a different date than the binary's release date.

=== Base package check failed ... Found version [none] at: ... Please upgrade to version: ===
FlightGear was unable to find the [[$FG ROOT]] directory. Set it using the <tt>--fg-root=</tt> commandline option.

=== Cannot find specified aircraft ===
Shows up when you use an incorrect aircraft name in the --aircraft=... command. Check the correct name by running --show-aircraft, or by looking at the aircraft's -set.xml file (eg. <tt>--aircraft=737-300</tt> for <tt>737-300-set.xml</tt>).

=== condition: comparison without property[1] or value ===
A condition (like <tt><less-than></tt> or <tt><equals></tt>) exists, without either:
* a property to check
* a value to check the property against

=== Could not find at least one of the following objects for animation: ===
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. Also in the .xml file make sure that there are not spaces at the beginning or end of the object name. If you are not the aircraft's author you can safely ignore such warnings.

=== creating 3D noise texture... DONE ===
Tells you that a new noise texture is created. It is not an error and can be ignored.

===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified====
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem.

=== Error: bind() failed in make_server_socket() ===
When using [[Howto: Multiplayer|multiplayer]] or socket input, this usually means you specified an invalid ip address or the port is in use. Note: for multiplayer, you don't need to use the ''--multiplay=in,...'' option at all, FlightGear (since version 1.0) figures out the proper setting automatically. Only use when you know what you are doing.

=== Error Building Technique: findAttr: could not find attribute bool ===
Make sure that your data and source (or binary) match. They must be from the same date, to provide the best performance.

=== Error: connect() failed in make_client_socket() SG_IO_OUT socket creation failed ===
Your computer is not connected with the internet, while a certain enabled feature (eg. multiplayer) does require an internet connection.

=== Error: RenderTexture requires the following unsupported OpenGL extensions... ===
Your graphics card doesn't support some graphics feature that FG requires. Update your drivers, change the BPP value and/or try disabling some of the visual goodies like [[3D Clouds]].

=== Failed to find .... in apt.dat.gz ===
You need to edit ATC/default.tower and ATC/default.atis. You can open these files with any text editor. Either remove or fix the entries containing your airports ICAO code (like KSFO).

===Failed to locate aircraft carrier = ...===
FlightGear is unable to find a [[Aircraft carrier|carrier]] under the set name. Check your commandline (<tt>--carrier=...</tt>) or the [[FlightGear Launch Control#Page Three - Airport Selection|airport page]] of the launcher. Note that you might need to enable a scenario in combination with a --carrier= command.

'''Hint:''' Make sure your park position and carrier name is correct. See the [[Howto: Carrier|wiki's carrier page]] for details.

=== Failed to open file ... ===
Check if the file exists on your system. If the missing file is a scenery object; be sure you have the latest [http://scenemodels.flightgear.org/download/SharedModels.tgz Shared Models] from the [[FlightGear Scenery Database]].

=== Fatal error: illegal character after . or .. ===
Some .xml file contains a fault. Possible solutions:
* To refer to a top-level property in the tree, <tt>../</tt> should be used instead of <tt>.../</tt>

=== Fatal error: mismatched tag ... ===
In some .xml file, an opening tag (like <tt><sim></tt>) does not match its closing tag (like <tt></sim></tt>). This error is hard to track down, best method is to comment (place code between <nowiki></nowiki>) most of the aircraft. Then uncomment code one by one, until the error appears again.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a tag is mis-matched and which tag is mis-matched. You'll probably know there's a problem if IE displays an error message.

=== Fatal error: name must begin with alpha or '_' ===
This error comes up when a property should be formed of which the name does not start with a letter of the alphabet or _. If this error only happens with certain planes, contact their authors.

=== Failed to tie property fcs/ to object methods ===
This [[JSBSim]] error comes up when there are unnamed components (eg. switches) in the FDM of an aircraft. Components must have unique names, from which properties will be created. As long as you are not overwriting an existing property, the <tt>name="..."</tt> can be used to output the components result to a property.

=== Fatal error: unclosed token ===
A token (<nowiki></nowiki>) has been started, but not closes. Add <nowiki>--></nowiki> at the correct line.

'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.

=== FGMultiplayerMgr::Open - Failed to bind receive socket ===
This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.

=== FGMultiplayMgr::MP_ProcessData: No such file or directory ===
This is telling you that there's someone online on the multiplayerserver, using a plane that you do not have installed on your own system. In order to remove the error (and see the other plane) you have to install the plane that the other pilot is using.

=== FGMultiplayMgr - No receiver port, Multiplayermode disabled ===
FlightGear [[Howto: Multiplayer|multiplayer]] has not been set.

=== FGPropertyManager::GetNode() No node found for ... In component: ... unknown property ... referenced. Aborting ===
FlightGear found a reference in the [[FDM]] to a non-existing property.

=== FGPropertyManager::GetNode() No node found for ... The property ... is undefined. ===
FlightGear found a reference in the [[FDM]] to a non-existing property. Keep in mind that JSBSim reads the FDM from top to bottom. Properties should always be created before they are needed somewhere.

=== Fgtzfile_read(): : Invalid argument Fatal error: Timezone reading failed ===
This one is caused by wrong line ending in a timezone file. Solution might be to download the Timezone/time.tab file manually from [http://gitorious.org/fg/fgdata/blobs/raw/master/Timezone/zone.tab Gitorious] (Right mouseclick > Save target as) and overwrite the file in <tt>[[$FG ROOT]]/Timezone/time.tab</tt> with it.

=== Found unexpected subsystem: system exiting. JSBSim failed to load aircraft and/or engine model ===
You are probably trying to run an aircraft on a out-of-date version of FlightGear. The planes on the official download page are intended to be used with the latest version of FlightGear. Usage on any older systems may not work.

=== freeglut (fgfs): Unable to create direct context rendering for window 'FlightGear' This may hurt performance ===
This reports that you do not have proper hardware accelerated 3D (direct rendering) configured.

=== Gate ... doesn't seem to have routes associated with it ===
A startup location in the [[Interactive Traffic#Ground networks|groundnetwork]] is not (properly) connected to a taxi route. Contact the airport author, or import the network to [[TaxiDraw]] and run the Verify network command to find the corrupted gate.

=== glLinkProgram "" Failed ===
Update your drivers; they have to support atleast OpenGL 2.0 for FlightGear 2.0 and later.

=== loading scenario '...' ===
This is not an error. It shows that an [[AI Systems#AI Models|AI scenario]] is loaded.

=== Model not found: ... ===
This one tells you that FlightGear was unable to find a certain file. The nice thing is that it also tells you excactly what file.

# Check if the file really does not exist at your computer.
# Try to locate the file in which the missing file is referenced. This is likely to be <tt>-set.xml</tt> in the root directory of the loaded [[aircraft]]. Between the <model> tags, the base model file is referenced. This file references to all other models that are displayed with the aircraft.
# Contact the aircraft author with a detailed bug-report, in which you state the excact location of the missing file and (if you found it) the file in which it is referenced.

=== Nasal runtime error: nil used in numeric context ===
This error is [[Nasal]] triggered by a Nasal file (the console should show what file (and line) and from where it was referenced). The Nasal script tried to do something with a [[Property Tree|property]] with an empty value. A solution is to fill the property before the Nasal is loaded. This can be done by setting the property in an [[aircraft]]'s <tt>-set.xml</tt> file or by adding a [[Nasal scripting language#Listeners and Signals|listener]] to the script.

[[Howto: Contact the developers|Contact the developers]] if this error is shown for a <tt>[[$FG ROOT]]/Nasal/</tt> script.

=== Near camera not rendering ===
[[File:Near_camera_off.png|500px]]

If you screen looks like the image above; make sure you have at least [[OSG]] version 2.7.6.

=== No render bin name specified in render bin section ===
Update [[SimGear]] (or binary) and your data directory.

=== No render bin number specified in render bin section ===
Update [[SimGear]] (or binary) and your data directory.

=== ... not a valid win32 application ===
This Windows error could have various reasons to pop up. Usually, the file that is causing troubles is mentioned. Re-installing this file might solve the problem.

=== OBJECT_SIGN: unexpected } in sign contents ===
One of the OBJECT_SIGN lines in the .stg file (of the tile that was loaded when this error showed up) contains a fault. Note that <tt>}</tt> must be preceded by a <tt>{</tt> character.

=== OBJECT_SIGN: unsupported glyph `.' ===
Check the OBJECT_SIGN lines in the .stg file of the tile that was loaded when this error showed up.

=== OpenAL error <AL_INVALID_VALUE>: bind source <alGenSources> Failed to generate audio source. ===
This error is probably displayed because of some misdirected audio settings in the [[aircraft]]s setup. Check the -sound.xml file of the aircraft and see if all files refered to really exist. If not, try to contact the author of the plane, so he can fix the problem in the [[Git]] version or solve the problem yourself and let someone commit the patch.

=== OpenAL error (AL_INVALID_VALUE): constructor (alBufferData) Fatal error: Failed to buffer data. ===
Disabling sound is a temporarily solution for this problem.

=== osgDB ac3d reader: could not find texture... ===
See [[#Failed to open file ...|Failed to open file ...]]

=== osgDB ac3d reader: detected surface with less than 3 vertices! ===
In one of the loaded models a non-existing surface is found. This can be a single line (sometimes used to simulate thin wires) or a fault in the model.

=== Program's vertex attrib binding ..., usrAttr... ===
Tells you that an effect binded certain attributes to a [[Shaders|shader]].

=== QNAN ===
(Q)NAN stands for (Quiet) Not A Number, produced by 0/0 or other floating point break downs. There can be various causes for this:
* Using a "flap start" value of 0 in the [[YASim]] [[FDM]]. Use some small value like 0.001 instead.

=== Scaling image... ===
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures.

=== ssgInit called without a valid OpenGL context ===
In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

=== The system cannot find the file specified ===
* If you are running Windows Vista; start by looking in <tt>C:\Users\Owner\AppData\Local\VirtualStore</tt> and seeing if you have a folder called FlightGear in there. If you do, cut-and-paste (merge) that one with <tt>C:\Program Files\Flightgear</tt> and try to launch FlightGear again. '''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible.
* Make sure you did set the right executable (<tt>fgfs.exe</tt>) on the first page of the [[FlightGear Launch Control]].

=== Time zone reading failed ===
This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files

=== Traffic manager could not find airport ===
There is either an airport missing from apt.dat, or there is a wrong ICAO code in a [[Interactive Traffic#Building Traffic Files|traffic file]]. An airport missing from apt.dat could be due to a recent opening.

=== Unable to choose requested pixel format ===
Error should be solved as of version 1.9. If not, try changing your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] and/or resolution.

=== Unable to find airport details for .... in FGTower::Init() ===
This error can be surpressed by disabling [[Interactive Traffic|AI Traffic]], via the AI/ATC [[menu]].

The error appears when an airport in <tt>[[$FG ROOT]]/Airports/apt.dat.gz</tt> cannot be found in <tt>[[$FG ROOT]]/ATC/default.tower</tt> and <tt>[[$FG ROOT]]/ATC/default.atis</tt>. Renaming the airports in the apt.dat.gz file ór in both default ATC files will fix the problem.

=== Unable to open aircraft directory ===
The [[aircraft]] that you are trying to run most likely relies on another aircraft, which you did not install (yet). The error shows what aircraft, so go download that one!
=== Unexpected tag '...' found in YASim aircraft description ===
FlightGear found a non-existing tag in the [[FDM]] of the aircraft you are trying to launch. If you have not changed the original aircraft, contact the aircraft author. Else, check the FDM througly for mistakes.

Also, make sure you didn't force a FDM to be loaded.
* '''Commandline:''' <tt>--fdm=...</tt> should be left out.
* '''[[FGRun]]:''' <tt>Advanced > Flight Model</tt> should be set to jsb (which will leave the whole command out of the commandline, so you can use this setting with any FDM).

=== Unknown ... aircraft: ... defaulting to C172 ===
FlightGear is unable to load the forced [[FDM]] (set through <tt>--fdm=...</tt> or via <tt>Advanced > Flight Model</tt> in [[FGRun]]) for this aircraft. FlightGear automatically picks the right FDM for each aircraft, so there is no need to set it manually, unless you know what you are doing. In the Flight Model dialog of FGRun, set the FDM to <tt>jsb</tt>; that is the "auto setting".

=== Unknown exception to the main loop. Aborting... Possible cause: No such file or directory ===
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear Launch Control#Debugging|log level]] to debug and repeating excactly what you did when the error came up, might provide some more information on what FlightGear was doing when the error occurred.
* Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work.
* Changing the resolution to a smaller one might work as well.

=== Unknown exception in main loop. Aborting... Possible cause: Not enough space ===
See [[Howto: Improve framerates#Optimus Technology]].

When your computer does not have the Optimus Technolog (NVidia) or Hybrid Graphics technology (ATI), you are likely to be unable to run FlightGear. Integrated graphics cards are very weak; too weak for FlightGear. You can try to switch of some of the eye-candy though, but even then the same error may appear...
It may be useful to check the latest drivers for your graphic card.
•If you have a Nvidia GPU, then visit http://wiki.flightgear.org/Howto:Improve_framerates#nVidia.
•For '''ATI line''' of video cards, look at this site: http://www.amd.com/us/products/technologies/amd-catalyst/pages/catalyst.aspx .You should find a file named "Catalyst control center", which allow you to modify the behaviour of your GPU with flightgear. I mean the Antialiasing control, the triple buffering, etc.
=== WARNING: Couldn't convert texture... ===
You are trying to run an aircraft not compatible with your FlightGear version. Most of the time, this error appears when you fly an aircraft, textured with .png files on versions older than 1.9. Convert the textures manually to .rgb or upgrade your FlightGear version.

=== Warning: Could not find plugin to read objects from file ... ===
A library is missing from your computer. Therefore, certain fileformats cannot be read. Try to reinstall/update [[OSG]], as the libraries used by FlightGear should be part of the standard package.

=== Warning: Picked up TriangleIntersect ===
Reduce your [[FlightGear Launch Control#Debugging|Log Level]] to alert. Or [[Showstoppers|send the fgfs output to /dev/null (unix systems) or 2>nul (Windows)]]. The errors might still be shown, but do not affect the sim anymore.

=== Warning: TangentSpaceGenerator: unknown primitive mode 9 ===
This is an [[OSG]] error, showing up when an effect needs tangent vectors, but polygons are not support. The error itself can be ignored, altough some [[shaders]] may look wrong. Shader developers should try to minimise the use of polygons and use triangles and quads instead.

=== YASim SOLUTION FAILURE: Solution failed to converge after 10000 iterations ===
Some control in the [[YASim]] [[FDM]] is too weak, according to YASim, to control the aircraft. An effectiveness tag will be required in the FDM to solve this error.

=== YASim SOLUTION FAILURE: Zero length fuselage ===
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.

=== YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! ===
Make sure the [[JSBSim]] [[FDM]] of the aircraft has a <code><fdm_config version="2.0"</code> tag.

== Errors without known solutions ==
Please take a look at the upcoming errors and see if you know a solution to get rid of them. Your additions are greatly appreciated!

=== Aircraft propulsion element has problems in file ... ===

=== AL Error (fx): Invalid Value at pitch and gain ===
The sound effect's pitch (high or low) and gain (volume multiplication factor) values are not valid.

=== AL Error (sound manager): Invalid Operation at update ===

=== AL Error (sound manager): Invalid Value at buffer add data No such buffer! ===

=== Failed to execute command nasal ===
Has something to do with the [[Nasal]] scripting language used by FlightGear.

=== Failed to tie (or untie while closing) property ... to object methods ===
A JSBSim error.

=== FGMultiplayMgr::MP_ProcessData - message from ... has invalid length! ===

=== FGMultiplayMgr::MP_ProcessData: Result too large ===

===GPS: malformed route, index=1===

=== Mesa 7.3 implementation error: bad texture level in r300UploadSubImage ===
http://www.flightgear.org/forums/viewtopic.php?f=2&t=6706&start=0&st=0&sk=t&sd=a

=== Nasal runtime error: stack overflow ===

=== No image file for texture, using white ===
A [[Shaders|shader]] error, possibly you (or the developer) have/has not specified a texture for a surface while modeling the aircraft model in AC3D, Blender, Wings...

=== No path in /sim/sound/path ===
You (or the developer) have/has not specified a proper sound file in the aircraft's -set.xml file.

=== OpenAL error (AL_ILLEGAL_COMMAND): set_source_pos ===

Has something to do with OpenAL not understanding where the sound comes from.

=== OpenAL error (AL_ILLEGAL_COMMAND): set_volume ===

Has something to do with OpenAL not understanding the sound volume.

=== PT_vs_hpt: ran out of layers ===
This is issued from the atmosphere implementation in FlightGear's environment system. A comment in the code says: "''should never get here''". Please provide input when this happens: excessive altitudes? Negative altitudes?

=== Tried to initialize a non-existent engine! ===
The developer of the aircraft did not code the engine properly.

'''Developers:''' Check that the engine.xml file, FDM.xml, and -set.xml is coded properly.

=== Unknown Chunk: ***UNKNOWN*** (0xA08A) ===
I use Autodesk 3ds Max (.3ds) occurs when the 3D data model.
Solution converts the file format AC3D.

=== Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,) ===
This warning is generated from OSG. Set your environment variable
OSG_NOTIFY_LEVEL=FATAL

=== Warning: GraphicsWindowWin32::grabFocus() - Failed grabbing the focus ===
It seems that this happens when you have another window open and you are "focusing" (the window is active) on it. FlightGear will try to grab itself infront of the other window.

=== WARNING: PUI: Too many live puInterfaces open at once! ===
Appears when printing large outputs (very) frequently on the screen.

=== Warning: State::drawQuads(0, 154400) too large handle in remapping to ushort glDrawElements ===
[[fr:Howto: Débarrassez-vous des erreurs les plus fréquentes]]

[[Category:Howto|Console output]]