FlightGear wiki - User contributions [en]

Zh/Boeing 787-8 Dreamliner

2024-10-03T11:22:35Z

Dg-505: link to english version

{{BeingTranslated}}[[User:Gzhang|Gzhang]] ([[User talk:Gzhang|talk]]) 10:57, 3 October 2024 (UTC)

'''波音787-8 “梦想客机” '''项目的目标在于改进[[Boeing 787|旧版波音787]]上的系统与[[cockpit|驾驶舱]]。这个项目最初由Omega95和Redneck承担工作，对于原来的模型作了重大改进与重新开发，只有机模主体与涂装未经改动。有一个有意思的改变与关键特点是新的机模实现了基于[[JSBSim]]的新的[[Flight Dynamics Model|空气动力学模型]]。它在创建时使用了来自[https://www.lissys.uk/samp1/desmis.html the Piano tool]的大量数据。另外一些有趣的特点包括了一个很酷的“玻璃驾驶舱(即电化驾驶舱）” ，它有着十分详细的波音787的仪表，以及液压、气动、供暖、燃料系统和电传飞控等高级系统。

这个项目的开发最早可以追溯到在论坛上787-8的CDU开发，从这以后，它就变为了一项社区项目。它的成功来源于很多开发者和论坛用户的贡献。另一个关键特点是每当新发现、新方法出现，它们就会在论坛上持续下去，并且很快会有百科的How-to教程被写出，从而帮到其他开发者。

=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 must be downloaded separately.

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

Landing gear chocks are triangular prism shaped blocks that are placed in front of and behind the landing gears to prevent the aircraft from moving. These chocks 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 chocks.

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

See the <code>Aircraft/787-8/</code> directory in [[FGAddon]]. 

=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:Red Griffin ATC compatible aircraft]]
[[en:Boeing_787-8_Dreamliner]]

Boeing 787-8 Dreamliner

2024-10-03T11:20:28Z

Dg-505: link to translation

{{:{{PAGENAME}}/info}}
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 [https://www.lissys.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 must be downloaded separately.

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

Landing gear chocks are triangular prism shaped blocks that are placed in front of and behind the landing gears to prevent the aircraft from moving. These chocks 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 chocks.

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

See the <code>Aircraft/787-8/</code> directory in [[FGAddon]]. 

=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:Red Griffin ATC compatible aircraft]]
[[zh:Boeing_787-8_Dreamliner]]

Building using CMake - Windows

2024-10-03T10:33:12Z

Dg-505: /* Scripted Compilation */ https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/PH7PR84MB14883876038B3075C76B4C2CCC692@PH7PR84MB1488.NAMPRD84.PROD.OUTLOOK.COM/

{{Main article|Building FlightGear}}
This article is intended to give an overview of '''building FlightGear on modern Windows systems'''. It was created using Windows 11 and VS 2022. It ought to be transferable to earlier versions of the Windows OS and software.

As FlightGear is now 64-bit only, the guide only describes building on a 64-bit system.

== Required software ==
* [https://cmake.org/download/ CMake for Windows]. Download and install the Windows Win64-x64 Installer.
* [https://visualstudio.microsoft.com/downloads/ Microsoft Visual Studio 2022] (MSVC). The Community version is free. There is no need for the premium versions; none of their features are required to build FlightGear. The C++ compiler will not be installed by default. You either choose this component during installation or after installation by starting MSVC and trying to create a new C++ project. The one to download is "Desktop Development with C++". Make sure to have the latest version of the Windows SDK for your Windows version and the C++ Compiler checked. As of 12/19/2023, the latest version of the compiler is "MSVC v143 - VS 2022 C++ x64/86 build tools".
* [https://www.qt.io/download-open-source/ Qt5] for the [[Integrated Qt5 Launcher]]. Download the online installer, and choose the version matching your toolchain of Visual Studio e.g. "Qt 5.15.2 --> MSVC 2019 64-bit". Any version past 5.9 will be fine; latest 5.x recommended. '''Do NOT use Qt6'''. Enable the "Archive" filter to show 5.x options. Leave the default Developer and Designer Tools selection - these are needed for coding and compiling. Otherwise, here is [https://www.qt.io/offline-installers Offline Qt Downloads] for the optional offline-installer versions of Qt.
* [https://git-scm.com/download/win Git] to keep your build up to date. It also simplifies downloads of components. Optional, but can't recommend it enough!

== Obtaining source ==
{{Main article|FlightGear and Git}}
Throughout this article it is assumed that you have set up git clones of the various source repositories (FlightGear, SimGear, data...).
Using an organized directory (see below) will help significantly.

The commands to run are:

{{code|git clone https://git.code.sf.net/p/flightgear/simgear simgear}}

{{code|git clone https://git.code.sf.net/p/flightgear/flightgear flightgear}}

{{code|git clone https://git.code.sf.net/p/flightgear/fgdata fgdata}}

{{code|git clone https://git.code.sf.net/p/flightgear/windows-3rd-party windows-3rd-party}}

{{code|git clone https://gitlab.com/flightgear/openscenegraph.git osg}}

{{caution| Cloning fgdata from SourceForge often fails. Therefore, we suggest you use a GitLab mirror repository. Instead of

{{code|git clone https://git.code.sf.net/p/flightgear/fgdata fgdata}}

call:

{{code|git clone https://gitlab.com/flightgear/fgdata.git fgdata}}

and after downloaded all data:

<syntaxhighlight lang="bash">
cd fgdata
git checkout next
git remote set-url origin https://git.code.sf.net/p/flightgear/fgdata
git pull
</syntaxhighlight>
}}

After downloading these, I would suggest assembling a folder structure as below:

== Directory Tree ==
On Windows, assumptions on the directory structure are made to automate the discovery of dependencies. This recommended directory structure is described below. The components can be downloaded from the links above. If you do not use the recommended structure you will need to enter paths by hand and some parts may not input correctly.

Caveat -- spaces in the directory names will cause errors. It is best to make sure there are no spaces in the path anywhere.

<tt>
: FlightGearBuild / </tt> (Main root directory) <tt>
:: fgdata / </tt> (FlightGear data files) <tt>
:: flightgear / </tt> (FlightGear sources) <tt>
:: install / </tt> (Directory where you will install the built binaries to) <tt>
::: launch.bat / </tt> (launch script if desired, see below) <tt>
:: osg / </tt> (OSG sources) <tt>
:: simgear / </tt> (SimGear sources) <tt>
:: windows-3rd-party /
:: build.bat / </tt> (build script, see below) <tt>
:: update.bat / </tt> (update script, see below)

== Building ==
=== Scripted Compilation ===
This script will allow you to build OpenSceneGraph, SimGear and FlightGear automatically.

{{collapsible script
| type = Windows batch file
| title = The <code>build.bat</code> script for configuring and compiling OSG, SG, and FG
| lang = batch
| script =
SET PATH=%PATH%;%ProgramFiles%\CMake\bin
SET QT5SDK64=C:\Qt\5.15.2\msvc2019_64
SET CMAKE_TOOLCHAIN="Visual Studio 17 2022"
SET ROOT_DIR=C:\path\to\FlightGearBuild

md osg-build
md simgear-build
md flightgear-build

cd %ROOT_DIR%\osg-build

cmake %ROOT_DIR%\osg -G %CMAKE_TOOLCHAIN% -A x64 ^
-DACTUAL_3RDPARTY_DIR=%ROOT_DIR%\windows-3rd-party/msvc140/3rdParty.x64 ^
-DCMAKE_RELWITHDEBINFO_POSTFIX:STRING= ^
-DOSG_USE_UTF8_FILENAME:BOOL=ON ^
-DWIN32_USE_MP:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config RelWithDebInfo --target INSTALL

cd %ROOT_DIR%\simgear-build
cmake %ROOT_DIR%\simgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install
cmake --build . --config RelWithDebInfo --target INSTALL

cd %ROOT_DIR%\flightgear-build
cmake %ROOT_DIR%\flightgear -G %CMAKE_TOOLCHAIN% -A x64 ^
-DCMAKE_INSTALL_PREFIX:PATH=%ROOT_DIR%\install ^
-DCMAKE_PREFIX_PATH=%QT5SDK64% ^
-DOSG_FSTREAM_EXPORT_FIXED:BOOL=ON

cmake --build . --config RelWithDebInfo --target INSTALL

pause
| show = 1
}}

{{tip | 10/2024: When using VS2022 make sure your osg has this fix applied: https://gitlab.com/flightgear/openscenegraph/-/commit/31082758036c12738467a7210a17604275a79517<ref>https://sourceforge.net/p/flightgear/mailman/message/58821522/</ref>

Some folks encountered the following problem when building flightgear:
<syntaxhighlight>
CMake Error at CMakeLists.txt:283 (find_package):
By not providing "FindBoost.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Boost", but
CMake did not find one.

Could not find a package configuration file provided by "Boost" with any of
the following names:

BoostConfig.cmake
boost-config.cmake

Add the installation prefix of "Boost" to CMAKE_PREFIX_PATH or set
"Boost_DIR" to a directory containing one of the above files. If "Boost"
provides a separate development package or SDK, be sure it has been
installed.
</syntaxhighlight>
This could be solved by doing the following in the top-level <code>CMakeLists.txt</code> of [https://sourceforge.net/p/flightgear/simgear/ci/next/tree/CMakeLists.txt#l16 simgear] and [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/CMakeLists.txt#l26 flightgear]:

In each file search for the line
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 NEW)
</syntaxhighlight>
(it should be near the top of each file) and change from <code>NEW</code> to <code>OLD</code> like this<ref>https://sourceforge.net/p/flightgear/mailman/message/58815368/</ref>:
<syntaxhighlight lang='CMake'>
cmake_policy(SET CMP0167 OLD)
</syntaxhighlight>

In addition there are reports that a linking error occurs when building flightgear:
<syntaxhighlight>
pui.lib(puValue.obj) : error LNK2019: unresolved external symbol __imp_strncat referenced in function "protected: void__cdecl puValue::copy_stringval(char const *)" (?copy_stringval@puValue@@IEAAXPEBD@Z) [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
F:\git\flightgear-build\src\Main\RelWithDebInfo\fgfs.exe : fatal error LNK1120: 1 unresolved externals [F:\git\flightgear-build\src\Main\fgfs.vcxproj]
</syntaxhighlight>
A workaround could be by changing the build type from <code>RelWithDebInfo</code> to <code>Release</code> when building osg, simgear and flightgear<ref>https://sourceforge.net/p/flightgear/mailman/message/58824438/</ref>:

In the <code>build.bat</code> change all three occurrences of
<syntaxhighlight lang='batch'>
cmake --build . --config RelWithDebInfo --target INSTALL
</syntaxhighlight>
to
<syntaxhighlight lang='batch'>
cmake --build . --config Release --target INSTALL
</syntaxhighlight>
}}

Before starting to use the script, you need to edit the top few lines of the script. You will have to:

1. Set the path to your CMake installation.

2. Ensure that the path to your QT SDK is correct for your version of MSVC.

3. Ensure your toolchain version matches, e.g. "Visual Studio 16 2019" for MSVC 2019 or "Visual Studio 15 2017" for MSVC 2017.

4. Set ROOT_DIR to the FlightGearBuild folder you created (the above directory structure)

==== Post-compilation: Launching FlightGear ====
'''In the debugger:'''
Open flightgear-build/FlightGear.sln. You can then perform all your development / debugging directly in VS. You normally only need to run build.bat again, if you update SimGear or OSG.

To launch FlightGear from Visual Studio, you can follow the following steps:
The first time only:
# Make sure you set your build type to RelWithDebInfo in the top bar.
# To start with the launcher, click on the small black arrow beside Local Windows Debugger to open 'fgfs debug properties'. Switch to debugging; add {{code|--launcher}} to the 'Command Arguments'. Click Apply and then OK.
# Press the green arrow (Local Windows Debugger) to start up FlightGear.
# The first time you'll have to choose where FGDATA is -- to do this, select the 'fgdata' directory you cloned at the start.

Thereafter, simply press the green arrow directly each time you want to start. If there are any local changes, it will recompile; alternatively it will start up directly. It will take a little longer to start as it loads symbols; however you also have the benefit that any segfaults will be caught allowing you to report them!

'''As a standard .exe:'''
NB these instructions overall are intended for setting up for development; there's a slightly more convoluted process for setting up for just plain flying (e.g. taking advantage of new features for aircraft development).

Essentially, Visual Studio doesn't copy in the DLLs into the /bin/ folder. It's also not ideal to manually copy in the DLLs as it can cause all sorts of issues. However, without the DLLs FlightGear won't work; therefore, you need to set the PATH so it knows where to look for them.
This launch script should work, put into your /install/bin/ folder:
{{collapsible script
| type = Windows batch file
| title = The <code>launch.bat</code> script for launching flightgear
| lang = batch
| script =
SET PATH=C:\path\to\FlightGearBuild\install\bin;C:\path\to\FlightGearBuild\windows-3rd-party\msvc140\3rdParty.x64\bin;C:\Qt\5.15.2\msvc2019_64\bin;%PATH%
fgfs.exe --launcher
| show = 1
}}

Adjust the "path\to" references to suit your own personal installation, as well as the QT5 path.

=== Updating ===
To update FlightGear, in general, just run ''git pull'' on the source directories and then re-run the build.bat script -- it will update what it needs to, relatively quickly.

{{collapsible script
| type = Windows batch file
| title = The <code>update.bat</code> script for updating repositories
| lang = batch
| script =
SET ROOT_DIR=C:\path\to\FlightGearBuild

cd %ROOT_DIR%\osg
git pull

cd %ROOT_DIR%\fgdata
git pull

cd %ROOT_DIR%\flightgear
git pull

cd %ROOT_DIR%\simgear
git pull

cd %ROOT_DIR%\windows-3rd-party
git pull

pause
| show = 1
}}

=== Changing the Configuration ===
When the SimGear/FlightGear version numbers change, or you change configuration options (e.g. toggling Compositor, changing OSG versions, changing Qt versions) you do have to re-configure in CMake. To do this, it's usually safest to delete the simgear-build and flightgear-build folders and re-run the build.bat script, to ensure the build is clean. There is no need to delete osg-build unless changing OSG version.

In case of problems, most of the time deleting the simgear-build and flightgear-build folders and re-running the build.bat script will be sufficient.

{{building}}
[[fr:compiler flightear avec CMake - Windows]]
[[Category:Windows specific]]
[[Category:Hackathon Materials]]

Aircraft checklists

2024-08-27T14:25:59Z

Dg-505: /* Reloading checklists */ Add 'reinit-gui' to 'reload_checklist' function to update the checklist dialog window

{{infobox subsystem
|image =Aircraft Checklists dialog.jpg
|name = Generic Aircraft Checklists
|started= 03/2010
|description = Centralized checklist management
|status = Under active development as of 05/2015
|maintainers = {{usr|Stuart}}
|developers = * {{usr|Stuart}}
* {{usr|Sanhozay}}
|changelog = * {{Git File History|project=flightgear|sub-project=fgdata|path=/Nasal/checklist.nas}}
* {{Git File History|project=flightgear|sub-project=fgdata|path=/gui/dialogs/checklist.xml}}
* {{Git File History|project=flightgear|sub-project=fgdata|path=/Aircraft/Generic/autochecklist.nas}}
}}

{{Startup}}
{{Checklists}}

As of version 2.9, [[FlightGear]] can display '''aircraft checklists''' in a standardized way, under Help > Aircraft Checklists.

== Adding checklists ==
To learn more about creating custom checklists, see {{readme file|checklists}} and the [[Cessna 172P]] as the reference implementation. Increasingly, the [[tutorials]] system is also extended such that it may make use of aircraft checklists.

Checklists are situated under <tt>/sim/checklists</tt>. As the checklists may be quite long, it is recommended that they are put in a separate file using the following entry in the <tt>-set.xml</tt> file of the aircraft:

<syntaxhighlight lang="xml">
<checklists include="c172-checklists.xml"/>
</syntaxhighlight>

Each individual checklist is created under a <checklist> XML tag, with the following sub-properties:

* <code><title></code> The name of the checklist
* <code><page></code> One or more pages from the checklist, containing one or more of the following:
** <code><item></code> A checklist item, containing
*** <code><name></code> The item name, to appear on the left hand side of the checklist
*** <code><value></code> One or more values, to appear on the right hand side of the checklist. Second and and subsequent <value> tags are displayed underneath each other. It is recommended that the <value> tags are kept short, to minimize the size of the displayed checklist.
*** <code><condition></code> An optional [[Howto:Animate models#Conditions|condition node]] that evaluates when the checklist item is complete. Incomplete checklist items are shown in yellow, while completed items are shown in green (NOTE: When more than one condition has to be met, the use of <and></and> is mandatory to make this work).
*** <code><marker></code> An optional marker node that is used to display a circle around a control when the user clicks a "?" button next to the item. This contains <x-m>, <y-m>, <z-m> and <scale> sub-elements and uses the [[Tutorials#Marker|tutorial marker]]. Note that this requires the marker model to be included in the aircraft model, as explained in the aforementioned article.
*** <code><binding></code> Zero or more XML bindings that are used by the simulator to execute the checklist item if the user clicks on a ">" button next to the item.

For simple checklists the <page> element can be omitted and <item> entries placed directly under the <checklist>.

The following example shows a simple checklists XML file:

<syntaxhighlight lang="xml">
<PropertyList>
<checklist>
<title>After Landing</title>
<item>
<name>Carburetor Heat</name>
<value>COLD</value>
<condition>
<equals>
<property>/controls/anti-ice/engine[0]/carb-heat</property>
<value>0</value>
</equals>
</condition>
<marker>
<x-m>-0.3225</x-m>
<y-m>-0.0850</y-m>
<z-m>-0.2117</z-m>
<scale>2.0500</scale>
</marker>
<binding>
<command>property-assign</command>
<value>0</value>
</binding>
</item>
<item>
<name>Wing Flaps</name>
<value>UP</value>
</item>
</checklist>
<checklist>
<title>Getting hamburger</title>
<page>
<item>
...
</item>
</page>
</checklist>
</PropertyList>
</syntaxhighlight>

See the Cessna 172P for an example of how this all fits together.

=== Bindings ===
[[File:C172p-checklist-via-pui.png|thumb|FlightGear [[Aircraft Checklists]] [[PUI]] dialog]]
One or more [[Bindings|binding elements]] can be added to a checklist item. Conceptually, these are the actions that the user should execute to complete the item. The checklist GUI displays items with such <binding> elements with an additional [>] button. Clicking on the button executes the bindings, allowing the user to watch as the computer/co-pilot/instructor executes the checklist item.

The <binding> element is exactly as you would expect - so property-assign, nasal etc. works.

The plan is to extend this function so that checklists with one or more items containing a <binding> element can have an (optional) button
to execute the entire checklist.

=== Grouping Checklists ===

Checklists can optionally be grouped together under a <group> node in the property tree, with each group given a descriptive name. For example:

<group>
<name>Emergency</name>
<checklist>...
<checklist>...
</group>
<group>
<name>Ground</name>
<checklist>...
<checklist>...
</group>

This is supported within the Checklist dialog, and also by the FG1000.

== Automatic Tutorial Generation ==
By default, checklists are automatically converted into [[Tutorials|tutorials]]. However, if your aircraft has custom tutorials, or it is not appropriate to have a tutorial for a particular checklist, you can disable this by setting <code><auto-tutorial>false</auto-tutorial></code> within the <code><checklist></code> or <code><group></code>. You can set <code>/sim/checklists/auto-tutorials=false</code> to disable generating any tutorials at all.

== Reloading checklists ==
Cut and paste this little code snippet in the [[Nasal Console]] and excecute it:

<syntaxhighlight lang="nasal">
var reload_checklist = func(filename) {
props.globals.getNode("/sim/checklists").remove(); # Delete the entire checklist node from the property tree. Otherwise, parts that are deleted in the xml file won't be removed from the property tree.
var checklist_path=sprintf("%s/%s",getprop("/sim/aircraft-dir"),filename);
var data = io.read_properties(checklist_path,"/sim/checklists");
fgcommand("reinit", props.Node.new({"subsystem": "gui"})); # Reload the GUI to update the checklist dialog window
}

reload_checklist(filename: "777-200-checklists.xml");
</syntaxhighlight>

Change the filename to the name of the file you are editing. Make sure to monitor the startup window and/or the [[Nasal Console]] loglist widget for any XML related warnings (e.g. parsing errors).

== Automated checklist execution ==

As of version 3.5, [[FlightGear]] can automate the execution of various sequences of aircraft checklists using the <tt>autochecklist.nas</tt> script in <tt>$FGDATA/Aircraft/Generic</tt>. The advantage of this approach is that the checklist files become the source of checklists, tutorials and autostart; if the checklists change, so does the autostart (see {{Wikipedia|Don't repeat yourself}}).

The <tt>autochecklist.nas</tt> script can be used to create an autostart menu but is not restricted to autostart; any checklist sequence can be run from any piece of Nasal code.

Automated checklists may not work for more complex aircraft startup sequences, but they are so easy to set up that it's worth trying alongside the development of the aircraft startup process. If it works, great! If it doesn't, you haven't wasted your time because you have at least made a start on your checklists.

=== Background ===

The <tt>autochecklist.nas</tt> script relies on the aircraft having a set of checklists that have complete sets of [[Bindings|bindings]] to take the aircraft from one state to another. For autostart, for example, you need to be able to start the aircraft solely by pressing the binding buttons on the right side of the checklist.

Using the script is a simple three step process involving a few lines of XML and as little as one line of [[Nasal]] code:

# Add the script to your aircraft
# Define one or more named checklist sequences
# Call the script to execute a checklist sequence

For example, you could define a sequence called "startup" that runs the sequence of checklists: "Before Starting Engines" and "Start Engines". Calling the <tt>autochecklist.nas</tt> script from a menu item binding with "startup" as the argument creates an autostart menu.

When you invoke the <tt>autochecklist</tt> script, it executes the checklists defined in the named sequence in the order that they are listed. Starting with the first item in the first checklist, it checks the {{readme file|conditions}} associated with the checklist item. If false, it runs the binding. It then moves onto the next item and checks if the condition from the previous item has been satisfied. If it is still false, it waits for a number of seconds -- maybe the binding was interpolated or the condition is waiting for something to start, e.g. APU spooling up. Once the condition from the previous item is satisfied, it looks at the condition on the current item and runs the binding if the condition is false. Execution continues like this until all checklist items have their bindings satisfied.

In some cases, e.g. checks on maximum takeoff weight, bindings will never cause the condition to be satisfied. To cover these cases, the script will consider the checklist to have failed if the condition associated with a checklist item does not become true within a timeout period. In these cases, the pilot needs to review the checklist manually and work out why the aircraft will not start. Once the condition has been corrected, e.g. they removed some fuel or payload to get below MTOW, the checklists can be executed again and should be successful. Because the script checks the condition of each item before running the binding, the automated execution is re-entrant; it just picks up where it left off and does only what needs to be done.

=== Add the script ===

Add <tt>autochecklist.nas</tt> to the aircraft's <tt>-set.xml</tt> file (or equivalent):

<syntaxhighlight lang="xml">
<nasal>
...
<autochecklist>
<file>Aircraft/Generic/autochecklist.nas</file>
</autochecklist>
</nasal>
</syntaxhighlight>

=== Define checklist sequences ===

In the aircraft's <tt>-set.xml</tt> file, create one or more named checklist sequences that specify ordered lists of checklists to execute. The names can be anything you like as long as they are valid XML tags. The names are never displayed within the simulator.

For example, to run checklists with indexes 0 and 1 for startup and checklist 9 for shutdown:

<syntaxhighlight lang="xml">
<sim>
<checklists>
<checklist include="Checklists/before-starting-engines.xml"/>
<checklist include="Checklists/start-engines.xml"/>

<checklist include="Checklists/parking.xml"/>
<startup>
<index n="0">0</index> 
<index n="1">1</index> 
</startup>
<shutdown>
<index n="0">9</index> 
</shutdown>
</checklists>
</sim>
</syntaxhighlight>

=== Execute the checklist sequence ===

For the typical usage of autostart, add a Nasal binding as a menu item and execute the named checklist sequence:

<syntaxhighlight lang="xml">
<item>
<label>Autostart</label>
<binding>
<command>nasal</command>
<script>autochecklist.complete_checklists("startup");</script>
</binding>
</item>
</syntaxhighlight>

Obviously, additional logic can be included in the binding if you want the autostart menu to toggle between autostart and shutdown.

==== Fine tuning checklist bindings ====

Sometimes, a checklist binding will do something like display a dialog, e.g. fuel and payload dialog. It would be irritating to the pilot if these things happened during automated execution. These bindings can make use of the <code>sim/checklists/auto/active</code> property, which will be <tt>true</tt> when the checklist binding is being run by the autochecklist script and <tt>false</tt> otherwise.

<syntaxhighlight lang="xml">
<binding>
<command>nasal</command>
<script>
var auto = getprop("sim/checklists/auto/active");
if (!auto) gui.showWeightDialog();
</script>
</binding>
</syntaxhighlight>

==== Expedited checklists ====

For in-air start sequences in some aircraft, you can pass zero as the second argument of the <tt>complete_checklists</tt> function to expedite the sequence. All items in the checklist sequence will be executed without waiting for previous items to complete. Note that this means the checklist sequence is never considered to have failed.

<syntaxhighlight lang="nasal">
if (!getprop("gear/gear/wow")) {
autochecklist.complete_checklists(sequence: "in-air-start", wait: 0);
} else {
autochecklist.complete_checklists("ground-start");
}
</syntaxhighlight>

Clearly the checklist sequence used for in-air start should be different from a ground start and should put the aircraft into a flying state, e.g. gear up, flaps up. Bindings can use the property <code>sim/checklists/auto/expedited</code> to check if the execution is expedited, i.e. there is no wait between items. Note that the expedited flag does not in itself indicate whether a binding is being run as part of an automated checklist. You may need to test both the <code>sim/checklists/auto/active</code> and <code>sim/checklists/auto/expedited</code> properties, e.g.

<syntaxhighlight lang="nasal">
var auto = getprop("sim/checklists/auto/active");
var expedited = getprop("sim/checklists/auto/expedited");

if (auto and expedited) {
...
}
</syntaxhighlight>

=== Customizing execution (optional) ===

The behavior of the <tt>autochecklist.nas</tt> script can be customized by setting properties, either in the aircraft's <tt>-set.xml</tt> file or at runtime. Configuration is under the <tt>sim/checklists/auto</tt> node.

<syntaxhighlight lang="xml">
<sim>
<checklists>
...
<auto>
<startup-message>Running checklists, please wait ...</startup-message>
<completed-message>Checklists complete.</completed-message>
<timeout-message>Some checks failed.</timeout-message>
<timeout-sec>10</timeout-sec>
<wait-sec>3</wait-sec>
</auto>
</checklists>
</sim>
</syntaxhighlight>

* <code>startup-message</code> message displayed prior to automated checklist execution
* <code>completed-message</code> message displayed on successful completion of the checklist
* <code>timeout-message</code> message displayed if checklist execution times out waiting for a checklist condition to be satisfied
* <code>timeout-sec</code> if the previous condition is not satisfied within this timeout, the automated execution fails
* <code>wait-sec</code> time to wait before re-checking the status of the previous item if its condition is false after running the binding (effectively a polling interval).

Messages are displayed as copilot announcements (by setting <tt>sim/messages/copilot</tt>). They can be set empty if messages are not required. Note that messages are never displayed for expedited starts.

Care should be taken with the timeout value. This is the timeout for a single item waiting for the previous condition to be satisfied, not the overall timeout for the checklist sequence. If the timeout is set to a large value and conditions cannot be satisfied, the pilot will have to wait a long time for the failure message to appear.

=== Other features and ideas ===

Automated checklist execution is not restricted to autostart and shutdown. If you have an "After Landing" checklist that switches landing lights off, raises flaps and turns taxi lights on, for example, you could assign that to a keyboard shortcut. Rollout and taxi is a busy time on some aircraft and it's often not easy to find the switches and controls necessary to complete this kind of checklist.

To use the <tt>autochecklist.nas</tt> script, pilots need <tt>FGDATA</tt> v3.5 or greater, otherwise the script will not be available. The availability of automated checklists can be tested by checking whether the <tt>sim/checklists/auto</tt> node is nil and a suitable indication given to the pilot if it is nil.

For an example of using automated checklists, refer to the [[Lockheed Constellation]], for which the script was originally written.

== Development ==
the docs for this particular feature are to be found in {{readme file|checklists}}.
This is also where you can read that the c172p is considered the reference implementation.
The system itself is located in {{fgdata source|path=gui/dialogs/checklist.xml|line=18|pre=$FG_ROOT|post=(embedded Nasal)}}, but -at least for now- that should not matter to you - unless you want to extend the system to add support for new features (in which case, you'll also want to check out $FG_ROOT/Nasal/checklist.nas).
Whatever is added to the Nasal code should never be aircraft-specific - aircraft specific stuff needs to be expressed via your own XML files - if something is missing, just extend the Nasal file, or ask for help so that we can post some pointers/snippets.
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=218209#p218209
| title = <nowiki>Re: </nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Sep 11th, 2014
| added = Sep 11th, 2014
| script_version = 0.25
}}
</ref>

it would be a good idea to localie any custom Nasal blocks, and instead introduce custom fgcommands using the addcommand() API - basically the reason being that there could be an aircraft-specific API using fgcommands for starting engines, instead of having aircraft-specific "Nasal blobs" in each checklist file. A while ago, this was actually discussed on the devel list, too. In other words, an "fgcommand" (implemented in Nasal) would help better isolate checklists from aircraft specifics.
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=241259#p241259
| title = <nowiki>Re: Automated Checklist Execution</nowiki>
| author = <nowiki>Hooray</nowiki>
| date = May 1st, 2015
| added = May 1st, 2015
| script_version = 0.25
}}
</ref>

== Checklist Generation Language ==

Forum user sanhozay has created a custom language called [https://github.com/sanhozay/CLGen CLGen] for generating checklists.

The main benefits to be gained from using CLGen are:

* More compact Nasal-like syntax that is easier to work with than XML
* Re-use of item definitions means source code is around 20-25% of the equivalent hand-written XML
* PDF and Graphviz DOT views of the checklists to aid prototyping
* Type checking and code generation means less debugging of checklists in Flightgear

Creating checklists with CLGen can be as simple as:

<pre>
checklist("Startup") {
check("Parking Brake", "ON");
check("Navigation Lights", "ON");
check("Beacon", "OFF");
}</pre>

CLGen supports conditions expressed in Nasal-like syntax, bindings, fgcommands, markers and automated inclusion of copyright headers. It is also possible, with some restrictions, to reverse-engineer existing checklists into CLGen source format and to generate PDF and Graphviz DOT representations of existing checklists.

[[File:CLGen DOT File.png|500px|Example of an image created from CLGen's DOT file output.]]
[[File:CLGen PDF Output.png|300px|Example of a PDF file created from CLGen.]]

CLGen is written in Java and runs on Mac OS, Linux and Windows platforms with a Java 8 runtime.

For more information, including a step-by-step Wiki tutorial, visit the [https://github.com/sanhozay/CLGen CLGen project on Github]

== References ==
<references/>

== Related content ==
=== Forum topics ===
* {{forum link|t=37992|title=The future of checklists}} (September 2020)
* {{forum link|t=32180|title=Checklist Generation DSL}} (May 2017) - CLGen Release Announcement

=== Development mailing list ===
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38325.html Aircraft Checklists] (mailing list)
* [https://sourceforge.net/p/flightgear/mailman/message/33904555/ Automated Checklist Execution] (mailing list)

[[Category:Aircraft enhancement]]

Aircraft checklists

2024-08-27T10:51:49Z

Dg-505: /* Reloading checklists */ Before reloading the checklist.xml: Delete the entire checklist node from the property tree. Otherwise, parts that are deleted in the xml file won't be removed from the property tree.

{{infobox subsystem
|image =Aircraft Checklists dialog.jpg
|name = Generic Aircraft Checklists
|started= 03/2010
|description = Centralized checklist management
|status = Under active development as of 05/2015
|maintainers = {{usr|Stuart}}
|developers = * {{usr|Stuart}}
* {{usr|Sanhozay}}
|changelog = * {{Git File History|project=flightgear|sub-project=fgdata|path=/Nasal/checklist.nas}}
* {{Git File History|project=flightgear|sub-project=fgdata|path=/gui/dialogs/checklist.xml}}
* {{Git File History|project=flightgear|sub-project=fgdata|path=/Aircraft/Generic/autochecklist.nas}}
}}

{{Startup}}
{{Checklists}}

As of version 2.9, [[FlightGear]] can display '''aircraft checklists''' in a standardized way, under Help > Aircraft Checklists.

== Adding checklists ==
To learn more about creating custom checklists, see {{readme file|checklists}} and the [[Cessna 172P]] as the reference implementation. Increasingly, the [[tutorials]] system is also extended such that it may make use of aircraft checklists.

Checklists are situated under <tt>/sim/checklists</tt>. As the checklists may be quite long, it is recommended that they are put in a separate file using the following entry in the <tt>-set.xml</tt> file of the aircraft:

<syntaxhighlight lang="xml">
<checklists include="c172-checklists.xml"/>
</syntaxhighlight>

Each individual checklist is created under a <checklist> XML tag, with the following sub-properties:

* <code><title></code> The name of the checklist
* <code><page></code> One or more pages from the checklist, containing one or more of the following:
** <code><item></code> A checklist item, containing
*** <code><name></code> The item name, to appear on the left hand side of the checklist
*** <code><value></code> One or more values, to appear on the right hand side of the checklist. Second and and subsequent <value> tags are displayed underneath each other. It is recommended that the <value> tags are kept short, to minimize the size of the displayed checklist.
*** <code><condition></code> An optional [[Howto:Animate models#Conditions|condition node]] that evaluates when the checklist item is complete. Incomplete checklist items are shown in yellow, while completed items are shown in green (NOTE: When more than one condition has to be met, the use of <and></and> is mandatory to make this work).
*** <code><marker></code> An optional marker node that is used to display a circle around a control when the user clicks a "?" button next to the item. This contains <x-m>, <y-m>, <z-m> and <scale> sub-elements and uses the [[Tutorials#Marker|tutorial marker]]. Note that this requires the marker model to be included in the aircraft model, as explained in the aforementioned article.
*** <code><binding></code> Zero or more XML bindings that are used by the simulator to execute the checklist item if the user clicks on a ">" button next to the item.

For simple checklists the <page> element can be omitted and <item> entries placed directly under the <checklist>.

The following example shows a simple checklists XML file:

<syntaxhighlight lang="xml">
<PropertyList>
<checklist>
<title>After Landing</title>
<item>
<name>Carburetor Heat</name>
<value>COLD</value>
<condition>
<equals>
<property>/controls/anti-ice/engine[0]/carb-heat</property>
<value>0</value>
</equals>
</condition>
<marker>
<x-m>-0.3225</x-m>
<y-m>-0.0850</y-m>
<z-m>-0.2117</z-m>
<scale>2.0500</scale>
</marker>
<binding>
<command>property-assign</command>
<value>0</value>
</binding>
</item>
<item>
<name>Wing Flaps</name>
<value>UP</value>
</item>
</checklist>
<checklist>
<title>Getting hamburger</title>
<page>
<item>
...
</item>
</page>
</checklist>
</PropertyList>
</syntaxhighlight>

See the Cessna 172P for an example of how this all fits together.

=== Bindings ===
[[File:C172p-checklist-via-pui.png|thumb|FlightGear [[Aircraft Checklists]] [[PUI]] dialog]]
One or more [[Bindings|binding elements]] can be added to a checklist item. Conceptually, these are the actions that the user should execute to complete the item. The checklist GUI displays items with such <binding> elements with an additional [>] button. Clicking on the button executes the bindings, allowing the user to watch as the computer/co-pilot/instructor executes the checklist item.

The <binding> element is exactly as you would expect - so property-assign, nasal etc. works.

The plan is to extend this function so that checklists with one or more items containing a <binding> element can have an (optional) button
to execute the entire checklist.

=== Grouping Checklists ===

Checklists can optionally be grouped together under a <group> node in the property tree, with each group given a descriptive name. For example:

<group>
<name>Emergency</name>
<checklist>...
<checklist>...
</group>
<group>
<name>Ground</name>
<checklist>...
<checklist>...
</group>

This is supported within the Checklist dialog, and also by the FG1000.

== Automatic Tutorial Generation ==
By default, checklists are automatically converted into [[Tutorials|tutorials]]. However, if your aircraft has custom tutorials, or it is not appropriate to have a tutorial for a particular checklist, you can disable this by setting <code><auto-tutorial>false</auto-tutorial></code> within the <code><checklist></code> or <code><group></code>. You can set <code>/sim/checklists/auto-tutorials=false</code> to disable generating any tutorials at all.

== Reloading checklists ==
Cut and paste this little code snippet in the [[Nasal Console]] and excecute it:

<syntaxhighlight lang="nasal">
var reload_checklist = func(filename) {
props.globals.getNode("/sim/checklists").remove(); # Delete the entire checklist node from the property tree. Otherwise, parts that are deleted in the xml file won't be removed from the property tree.
var checklist_path=sprintf("%s/%s",getprop("/sim/aircraft-dir"),filename);
var data = io.read_properties(checklist_path,"/sim/checklists");
}

reload_checklist(filename: "777-200-checklists.xml");
</syntaxhighlight>

Change the filename to the name of the file you are editing. Make sure to monitor the startup window and/or the [[Nasal Console]] loglist widget for any XML related warnings (e.g. parsing errors).

After that you should call <code>Menubar -> Debug -> Reload GUI</code> to make sure the checklist dialog window gets updated (or call the <code>reinit-gui</code>-function via nasal, if you know how to do this).

== Automated checklist execution ==

As of version 3.5, [[FlightGear]] can automate the execution of various sequences of aircraft checklists using the <tt>autochecklist.nas</tt> script in <tt>$FGDATA/Aircraft/Generic</tt>. The advantage of this approach is that the checklist files become the source of checklists, tutorials and autostart; if the checklists change, so does the autostart (see {{Wikipedia|Don't repeat yourself}}).

The <tt>autochecklist.nas</tt> script can be used to create an autostart menu but is not restricted to autostart; any checklist sequence can be run from any piece of Nasal code.

Automated checklists may not work for more complex aircraft startup sequences, but they are so easy to set up that it's worth trying alongside the development of the aircraft startup process. If it works, great! If it doesn't, you haven't wasted your time because you have at least made a start on your checklists.

=== Background ===

The <tt>autochecklist.nas</tt> script relies on the aircraft having a set of checklists that have complete sets of [[Bindings|bindings]] to take the aircraft from one state to another. For autostart, for example, you need to be able to start the aircraft solely by pressing the binding buttons on the right side of the checklist.

Using the script is a simple three step process involving a few lines of XML and as little as one line of [[Nasal]] code:

# Add the script to your aircraft
# Define one or more named checklist sequences
# Call the script to execute a checklist sequence

For example, you could define a sequence called "startup" that runs the sequence of checklists: "Before Starting Engines" and "Start Engines". Calling the <tt>autochecklist.nas</tt> script from a menu item binding with "startup" as the argument creates an autostart menu.

When you invoke the <tt>autochecklist</tt> script, it executes the checklists defined in the named sequence in the order that they are listed. Starting with the first item in the first checklist, it checks the {{readme file|conditions}} associated with the checklist item. If false, it runs the binding. It then moves onto the next item and checks if the condition from the previous item has been satisfied. If it is still false, it waits for a number of seconds -- maybe the binding was interpolated or the condition is waiting for something to start, e.g. APU spooling up. Once the condition from the previous item is satisfied, it looks at the condition on the current item and runs the binding if the condition is false. Execution continues like this until all checklist items have their bindings satisfied.

In some cases, e.g. checks on maximum takeoff weight, bindings will never cause the condition to be satisfied. To cover these cases, the script will consider the checklist to have failed if the condition associated with a checklist item does not become true within a timeout period. In these cases, the pilot needs to review the checklist manually and work out why the aircraft will not start. Once the condition has been corrected, e.g. they removed some fuel or payload to get below MTOW, the checklists can be executed again and should be successful. Because the script checks the condition of each item before running the binding, the automated execution is re-entrant; it just picks up where it left off and does only what needs to be done.

=== Add the script ===

Add <tt>autochecklist.nas</tt> to the aircraft's <tt>-set.xml</tt> file (or equivalent):

<syntaxhighlight lang="xml">
<nasal>
...
<autochecklist>
<file>Aircraft/Generic/autochecklist.nas</file>
</autochecklist>
</nasal>
</syntaxhighlight>

=== Define checklist sequences ===

In the aircraft's <tt>-set.xml</tt> file, create one or more named checklist sequences that specify ordered lists of checklists to execute. The names can be anything you like as long as they are valid XML tags. The names are never displayed within the simulator.

For example, to run checklists with indexes 0 and 1 for startup and checklist 9 for shutdown:

<syntaxhighlight lang="xml">
<sim>
<checklists>
<checklist include="Checklists/before-starting-engines.xml"/>
<checklist include="Checklists/start-engines.xml"/>

<checklist include="Checklists/parking.xml"/>
<startup>
<index n="0">0</index> 
<index n="1">1</index> 
</startup>
<shutdown>
<index n="0">9</index> 
</shutdown>
</checklists>
</sim>
</syntaxhighlight>

=== Execute the checklist sequence ===

For the typical usage of autostart, add a Nasal binding as a menu item and execute the named checklist sequence:

<syntaxhighlight lang="xml">
<item>
<label>Autostart</label>
<binding>
<command>nasal</command>
<script>autochecklist.complete_checklists("startup");</script>
</binding>
</item>
</syntaxhighlight>

Obviously, additional logic can be included in the binding if you want the autostart menu to toggle between autostart and shutdown.

==== Fine tuning checklist bindings ====

Sometimes, a checklist binding will do something like display a dialog, e.g. fuel and payload dialog. It would be irritating to the pilot if these things happened during automated execution. These bindings can make use of the <code>sim/checklists/auto/active</code> property, which will be <tt>true</tt> when the checklist binding is being run by the autochecklist script and <tt>false</tt> otherwise.

<syntaxhighlight lang="xml">
<binding>
<command>nasal</command>
<script>
var auto = getprop("sim/checklists/auto/active");
if (!auto) gui.showWeightDialog();
</script>
</binding>
</syntaxhighlight>

==== Expedited checklists ====

For in-air start sequences in some aircraft, you can pass zero as the second argument of the <tt>complete_checklists</tt> function to expedite the sequence. All items in the checklist sequence will be executed without waiting for previous items to complete. Note that this means the checklist sequence is never considered to have failed.

<syntaxhighlight lang="nasal">
if (!getprop("gear/gear/wow")) {
autochecklist.complete_checklists(sequence: "in-air-start", wait: 0);
} else {
autochecklist.complete_checklists("ground-start");
}
</syntaxhighlight>

Clearly the checklist sequence used for in-air start should be different from a ground start and should put the aircraft into a flying state, e.g. gear up, flaps up. Bindings can use the property <code>sim/checklists/auto/expedited</code> to check if the execution is expedited, i.e. there is no wait between items. Note that the expedited flag does not in itself indicate whether a binding is being run as part of an automated checklist. You may need to test both the <code>sim/checklists/auto/active</code> and <code>sim/checklists/auto/expedited</code> properties, e.g.

<syntaxhighlight lang="nasal">
var auto = getprop("sim/checklists/auto/active");
var expedited = getprop("sim/checklists/auto/expedited");

if (auto and expedited) {
...
}
</syntaxhighlight>

=== Customizing execution (optional) ===

The behavior of the <tt>autochecklist.nas</tt> script can be customized by setting properties, either in the aircraft's <tt>-set.xml</tt> file or at runtime. Configuration is under the <tt>sim/checklists/auto</tt> node.

<syntaxhighlight lang="xml">
<sim>
<checklists>
...
<auto>
<startup-message>Running checklists, please wait ...</startup-message>
<completed-message>Checklists complete.</completed-message>
<timeout-message>Some checks failed.</timeout-message>
<timeout-sec>10</timeout-sec>
<wait-sec>3</wait-sec>
</auto>
</checklists>
</sim>
</syntaxhighlight>

* <code>startup-message</code> message displayed prior to automated checklist execution
* <code>completed-message</code> message displayed on successful completion of the checklist
* <code>timeout-message</code> message displayed if checklist execution times out waiting for a checklist condition to be satisfied
* <code>timeout-sec</code> if the previous condition is not satisfied within this timeout, the automated execution fails
* <code>wait-sec</code> time to wait before re-checking the status of the previous item if its condition is false after running the binding (effectively a polling interval).

Messages are displayed as copilot announcements (by setting <tt>sim/messages/copilot</tt>). They can be set empty if messages are not required. Note that messages are never displayed for expedited starts.

Care should be taken with the timeout value. This is the timeout for a single item waiting for the previous condition to be satisfied, not the overall timeout for the checklist sequence. If the timeout is set to a large value and conditions cannot be satisfied, the pilot will have to wait a long time for the failure message to appear.

=== Other features and ideas ===

Automated checklist execution is not restricted to autostart and shutdown. If you have an "After Landing" checklist that switches landing lights off, raises flaps and turns taxi lights on, for example, you could assign that to a keyboard shortcut. Rollout and taxi is a busy time on some aircraft and it's often not easy to find the switches and controls necessary to complete this kind of checklist.

To use the <tt>autochecklist.nas</tt> script, pilots need <tt>FGDATA</tt> v3.5 or greater, otherwise the script will not be available. The availability of automated checklists can be tested by checking whether the <tt>sim/checklists/auto</tt> node is nil and a suitable indication given to the pilot if it is nil.

For an example of using automated checklists, refer to the [[Lockheed Constellation]], for which the script was originally written.

== Development ==
the docs for this particular feature are to be found in {{readme file|checklists}}.
This is also where you can read that the c172p is considered the reference implementation.
The system itself is located in {{fgdata source|path=gui/dialogs/checklist.xml|line=18|pre=$FG_ROOT|post=(embedded Nasal)}}, but -at least for now- that should not matter to you - unless you want to extend the system to add support for new features (in which case, you'll also want to check out $FG_ROOT/Nasal/checklist.nas).
Whatever is added to the Nasal code should never be aircraft-specific - aircraft specific stuff needs to be expressed via your own XML files - if something is missing, just extend the Nasal file, or ask for help so that we can post some pointers/snippets.
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=218209#p218209
| title = <nowiki>Re: </nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Sep 11th, 2014
| added = Sep 11th, 2014
| script_version = 0.25
}}
</ref>

it would be a good idea to localie any custom Nasal blocks, and instead introduce custom fgcommands using the addcommand() API - basically the reason being that there could be an aircraft-specific API using fgcommands for starting engines, instead of having aircraft-specific "Nasal blobs" in each checklist file. A while ago, this was actually discussed on the devel list, too. In other words, an "fgcommand" (implemented in Nasal) would help better isolate checklists from aircraft specifics.
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=241259#p241259
| title = <nowiki>Re: Automated Checklist Execution</nowiki>
| author = <nowiki>Hooray</nowiki>
| date = May 1st, 2015
| added = May 1st, 2015
| script_version = 0.25
}}
</ref>

== Checklist Generation Language ==

Forum user sanhozay has created a custom language called [https://github.com/sanhozay/CLGen CLGen] for generating checklists.

The main benefits to be gained from using CLGen are:

* More compact Nasal-like syntax that is easier to work with than XML
* Re-use of item definitions means source code is around 20-25% of the equivalent hand-written XML
* PDF and Graphviz DOT views of the checklists to aid prototyping
* Type checking and code generation means less debugging of checklists in Flightgear

Creating checklists with CLGen can be as simple as:

<pre>
checklist("Startup") {
check("Parking Brake", "ON");
check("Navigation Lights", "ON");
check("Beacon", "OFF");
}</pre>

CLGen supports conditions expressed in Nasal-like syntax, bindings, fgcommands, markers and automated inclusion of copyright headers. It is also possible, with some restrictions, to reverse-engineer existing checklists into CLGen source format and to generate PDF and Graphviz DOT representations of existing checklists.

[[File:CLGen DOT File.png|500px|Example of an image created from CLGen's DOT file output.]]
[[File:CLGen PDF Output.png|300px|Example of a PDF file created from CLGen.]]

CLGen is written in Java and runs on Mac OS, Linux and Windows platforms with a Java 8 runtime.

For more information, including a step-by-step Wiki tutorial, visit the [https://github.com/sanhozay/CLGen CLGen project on Github]

== References ==
<references/>

== Related content ==
=== Forum topics ===
* {{forum link|t=37992|title=The future of checklists}} (September 2020)
* {{forum link|t=32180|title=Checklist Generation DSL}} (May 2017) - CLGen Release Announcement

=== Development mailing list ===
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38325.html Aircraft Checklists] (mailing list)
* [https://sourceforge.net/p/flightgear/mailman/message/33904555/ Automated Checklist Execution] (mailing list)

[[Category:Aircraft enhancement]]

User:Dg-505

2023-02-13T01:53:05Z

Dg-505: Add my SOTM candidate for 2023-01

{{User
|name = dg-505 (Jonathan)
|location = Leverkusen, Germany
|age = 19
|interests = Gliding, model planes, FlightGear
|favourite =
* [[DHC-6 Twin Otter]]
* [http://zaretto.com/f-14b F-14B JSBSim]
* [[Boeing_707-420|Boeing 707]]
* [[Douglas_DC-3-C-47|Douglas Dc-3/C-47]]
* [[Glaser-Dirks_DG-101G|DG-101]]
* [[Cessna_337G_Skymaster|Cessna 337 Skymaster]]
}}
== My FlightGear history ==
The first time I downloaded FlightGear was, at least I think, in 2010, when 2.0.0 was the latest version. I flew around a bit, but because of my very very low end laptop, it was not a very nice experience. I stopped using FlightGear fo a couple of years. Then in late 2013 I re-discovered FlightGear with 2.12 as the latest release. I started wondering, how such a Flight Simulator can be freeware and open source. After reading many articles on the [http://forum.flightgear.org/ Forum] and the Wiki, I wanted to contibute something to this wonderful project. So my first small contributions were some objects in the [http://scenemodels.flightgear.org/ FlightGear scenery Database].
My main interests in FlightGear are currently improving the region around EDFL with some 3D models, and helping a bit contribute to the DHC-6 Twin Otter.
I just started learning XML and it's a slow learning progress, because before FlightGear I didn't have ''any'' experiences in writing any kind of code.
As I also haven't written a single line of nasal, I am more a 3D modeler; I think this is my better area of contribution.

Currently I'm working together with other users on the Twin Otter.

== Aircraft ==
DHC-6 Twin Otter ([[De_Havilland_Canada_DHC-6_Twin_Otter|wiki page]], [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 forum])

== Gallery ==
<gallery widths="250" heights="250" mode="packed">
File:Seconds Before Touchdown.jpg
</gallery>

== External links ==
* [http://forum.flightgear-de.net German FlightGear forum]

File:Seconds Before Touchdown.jpg

2023-02-13T01:45:28Z

Dg-505: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=[[Grumman F-14 Tomcat]] on final approach to Carrier USS Truman (CVN-75)}}
{{de|1=[[Grumman F-14 Tomcat]] im Endanflug auf den Flugzeugträger USS Truman (CVN-75)}}
|date=2023-02-13 02:33:00
|source={{own}}
|author=[[User:Dg-505|Dg-505]]
|permission=
|other versions=
}}

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

[[Category:Grumman F-14 Tomcat screenshots]]
[[Category:USS Harry S. Truman (CVN-75) screenshots]]

HDR

2021-12-26T12:38:23Z

Dg-505: redirect "HDR" to https://wiki.flightgear.org/HDR_Pipeline

#redirect[[HDR Pipeline]]

FlightGear Newsletter March 2021

2021-03-07T15:38:58Z

Dg-505: /* In the hangar */ Twin Otter update

{{User:Skybike/Template:Newsletter-header-translate|2021-03}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== Initial stab at Data Distribution Services Support ===

Erik added the first stab at supporting CycloneDDS ('''Data Distribution
Service''') support in next: https://github.com/eclipse-cyclonedds/cyclonedds

'''Data Distribution Services''' are used in IoT applications and has a number
of advantages over normal socket support:

* Auto configuring within a LAN.
* Auto connecting and disconnecting.
* Platform and computer language agnostic:
** Use the .idl files in FlightGear/src/networking/DDS to create the structures for your favorite language.
* Instead to a one-on-one connection you get a one-to-many connection.

What does this mean?

You now can connect to FlightGear from Java and Python and get the same
data as in C and C++
* Use you Rasbery Pi to display some cockpit instruments.
* Controlling the main system from a cell-phone<ref>https://sourceforge.net/p/flightgear/mailman/message/37233914/</ref>

Learn more at [[Data Distribution Services Support]]






== In the hangar ==



=== Updated aircraft ===

==== DHC-6 Twin Otter ====
Simworld 2020 added a few features to the COM/NAV systems:<ref>[https://forum.flightgear.org/viewtopic.php?f=14&t=38835 Forum thread]</ref>

* A second ADF receiver
* Pilot's RMI now listens to the 1st ADF reciever, Copilot's RMI listens to the 2nd ADF receiver.
* We now have a KMA 20 audio panel, where you can control the audio output of the NAV/COM systems.
* The COM radios now feature Spacebar PTT support.
* Addition of a NAV1/GPS slave to the panel
* The copilot's panel now has it's own CDI instruments for the NAV1 and NAV2 receivers.

The [[FGAddon]] hangar has been updated with revision [https://sourceforge.net/p/flightgear/fgaddon/5629/ 5629].





== Scenery corner ==
















== Help wanted ==
{{Help wanted}}

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2021 03]]

FlightGear Newsletter February 2020

2020-02-24T13:40:18Z

Dg-505: /* Screenshot of the Month */ link to SOTM subforum

{{User:Skybike/Template:Newsletter-header-translate|2020-02}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== Improvements to the Wingflex Shader ===
With the merge of [https://sourceforge.net/p/flightgear/fgdata/merge-requests/167/ Merge Request 167] and [https://sourceforge.net/p/flightgear/fgdata/merge-requests/168/ Merge Request 168], the wingflex shader, previously purely applicable for organic wingflex as in the [[Dragon]] is now able to simulate wingflex for "normal" wings, without the need to cut the wings into pieces as before. As using this shader will break rotation animations having a y-component, e.g. the rotation of an aileron, these can now be performed in the shader themselves. See the [[Wingflex Shader|corresponding wiki article]] for more information.




== In the hangar ==






=== Updated aircraft ===
[[File:Twin Otter over Sognefjord.jpg|thumb|300px|The Twin Otter over Norway]]
==== DHC-6 Twin Otter ====
Tim Dicus (SurferTim) added a variant with upgraded engines to the [[Twin Otter]]. By default, the DHC-6-300 series is equipped with Pratt & Whitney PT6A-27 turboprop engines with 620 HP of shaft power. However now it is possible to fly the Twin Otter with even more powerful engines. The new variant includes PT6A-34 engines, which provide a maximum of 750 HP of shaft power.

He also made some improvements regarding the autopilot, nav instruments, seaplane variant and ground equipment.





== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the important development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Scenery corner ==














== Community news ==







=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [http://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
Flightgear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flightsims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==

=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====


If you want to participate in the screenshot contest , you can submit your candidate to {{forum link|title=this|f=88|t= }}. Be sure to see the first post for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}

[[Category:Changes after 2019.1]]
[[Category:FlightGear Newsletter|2020 02]]

[[de:FlightGear Newsletter {{#time: F Y | 2020-02 | de }}]]

FlightGear Newsletter February 2020

2020-02-24T13:39:00Z

Dg-505: /* In the hangar */ Updated Twin Otter by Tim Dicus

{{User:Skybike/Template:Newsletter-header-translate|2020-02}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== Improvements to the Wingflex Shader ===
With the merge of [https://sourceforge.net/p/flightgear/fgdata/merge-requests/167/ Merge Request 167] and [https://sourceforge.net/p/flightgear/fgdata/merge-requests/168/ Merge Request 168], the wingflex shader, previously purely applicable for organic wingflex as in the [[Dragon]] is now able to simulate wingflex for "normal" wings, without the need to cut the wings into pieces as before. As using this shader will break rotation animations having a y-component, e.g. the rotation of an aileron, these can now be performed in the shader themselves. See the [[Wingflex Shader|corresponding wiki article]] for more information.




== In the hangar ==






=== Updated aircraft ===
[[File:Twin Otter over Sognefjord.jpg|thumb|300px|The Twin Otter over Norway]]
==== DHC-6 Twin Otter ====
Tim Dicus (SurferTim) added a variant with upgraded engines to the [[Twin Otter]]. By default, the DHC-6-300 series is equipped with Pratt & Whitney PT6A-27 turboprop engines with 620 HP of shaft power. However now it is possible to fly the Twin Otter with even more powerful engines. The new variant includes PT6A-34 engines, which provide a maximum of 750 HP of shaft power.

He also made some improvements regarding the autopilot, nav instruments, seaplane variant and ground equipment.





== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the important development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Scenery corner ==














== Community news ==







=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [http://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
Flightgear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flightsims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==

=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====


If you want to participate in the screenshot contest , you can submit your candidate to {{forum link|title=this|f=19|t= }}. Be sure to see the first post for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}

[[Category:Changes after 2019.1]]
[[Category:FlightGear Newsletter|2020 02]]

[[de:FlightGear Newsletter {{#time: F Y | 2020-02 | de }}]]

Changelog 2018.1

2018-02-11T10:51:11Z

Dg-505: /* Significant Aircraft Updates */ Note about Twin Otter update

{{changelogs|prev=2017.3|next=2017.5}}
{{-}}
{{draft|changelog|This changelog is currently being written for the FlightGear v2018.1 release. Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.}}

The FlightGear development team is delighted to announce the v2018.1 "Honolulu" release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multiplayer environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2018.1 for free from [http://www.flightgear.org/ FlightGear.org].

FlightGear - Fly Free!

== Useability ==
* Improved control for aircraft carriers

== Graphics ==
* Improved "Classic theme" with better fonts and colours
* Canvas MapStructure support for SlippyMaps, including VFRCharts, STAMEN,
* Various improvements to the Launcher
* Atmospheric Light Scattering renderer: extra volumetric vegetation layers for denser undergrowth

== Scenery ==
* active Volcanos, including Kilauea, Stromboli, Etna,
* New Hawaii regional texture definitions
* several scenic waterfalls in the Hawaii area
* new and unique vegetation textures for several parts of the world

== Significant Aircraft Updates ==
* A new glider: Rolladen-Schneider LS4
* [[Space Shuttle]] improvements
* Cessna 182S
* Amelia - an animated and hard-working co-pilot for the Alouette III capable of taking off and landing
* Citation II
* F-14 - various changes including improved carrier operations
* Robinson R44 helicopter
* Major [[DHC-6 Twin Otter]] update: JSBSim variant added (starus: experimental), more realistic fuel system in JSBSim, significantly more detailed simulation of the electrical system including various DC and AC buses, circuit breakers and bus tie relay. Please help improve the JSBSim FDM: Test the behaviour and share your experiences in the [https://forum.flightgear.org/viewtopic.php?f=4&t=21965 FlightGear Forum], or even better, directly improve the FDM in [[FGAddon]]!

== Other ==
* CH Products Throttle Quadrant supported out-of-the-box. Thanks to CH Products for providing a sample quadrant.
* Improved support for add-ons<ref name="addons-note">See [https://sourceforge.net/p/flightgear/mailman/message/36222728/ this message] and [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.add-ons $FG_ROOT/Docs/README.add-ons] if you wrote an add-on for FlightGear 2017.3.</ref>
* Support NMEA traffic alerts (e.g. flarm) to allow FG to feed AI/MP traffic to Nav/moving map clients such as xcsoar, skydemon, skymap
* Improvements to YASIM, including multiple wing sections, support for whole-stabilizer trim, better information from CLI tools
* More realistic carrier landings with improvements to the JSBSim arrestor wire behaviour.

== Footnotes ==
<references/>

[[Category:Changes after 2017.3]]

Howto:Use multiple screens under linux

2017-12-01T12:32:40Z

Dg-505:

This Howto explains how to get FlightGear running over multiple screens on Linux.
Like so often on Linux, there are multiple ways to get something working.
This is just a way, that worked for me.

== Using i3 window manager ==

* First of all, you have to install the [http://i3wm.org i3 window manager] using your package manager (or, at your choice, from source).
* When running i3 for the first time, you'll be asked if you want it to create a config file for you and what key (Alt or Win) you want to use as mod key. Confirm the creation of the config file. (In this Howto I assume, that the Win key is used as mod key)
* Edit the config file, usually located in '~/.config/i3/config', with the text editor of your choice.
* Add following line: 'bindsym $mod+Shift+f fullscreen toggle global' (You can use any other combination as well as long as it doesn't already exists.)
* Now reload the config (easiest way to do so is to log out and in again).
* Now it's time to start FlightGear using the terminal (Win+Enter) or the dmenu (Win+d). When it has started, press Win+Shift+f and here you go.

If it happens that the screens are in the wrong order, use the following steps to fix.
* Open a terminal and run 'xrandr' to list all your outputs. Outputs with resolution information are connected.
* Now you have to set the relative position of the screens with 'xrandr --output <output> --left-of <output>' and 'xrandr --output <output> --right-of <output>'. Here you have to play a bit around since every system is different (The changes are not permanent so you just have to log out and in again to reset).
* When you have figured out, which command (or with more than two screens, commands) work for you, add the following line to the i3 config file: 'exec <your command>' (multiple times when you needed more than one command). This way it doesn't change anything to your usually used window manager.

Feel free to add your way.

[[Category:Howto]]

De Havilland Canada DHC-6 Twin Otter

2017-11-19T12:10:45Z

Dg-505: /* TODO list/future plans */

{{lowercase title}}{{:{{PAGENAME}}/info}}
The '''de Havilland Canada DHC-6 Twin Otter''', sometimes affectionately called the '''''Twotter''''', is a 20-passenger STOL (Short Takeoff and Landing) utility aircraft. It has often been called the most successful aircraft program in Canada's history. The Twin Otter is a high-wing twin-engine turboprop aircraft with a non-retractable tricycle gear, a non-pressurised cabin and two constant-speed props. In FlightGear, there are three versions available: Wheels, Floats (amphibious) and skis.

== About the original ==
The DHC-6 Twin Otter is the further development version of the [[DHC-3]] Otter of the same manufacturer. The development of the Twin Otter began in 1964, it's first flight was on May 20, 1965<ref>{{wikipedia|De Havilland Canada DHC-6 Twin Otter#Design and development}}</ref>. To keep the STOL abilities of the Otter, the DHC-6 got two powerful {{wikipedia|Pratt & Whitney Canada PT6}} turboprop engines with 410 kW produced by each turbine in the first version, the DHC-6-100.

In 1968, the Twin Otter was developed to a new version, the -200 series, which had improved STOL performance.

One year later, in 1969, the DHC-6-300 series was introduced, with more powerful engines, the PT6A-27 with 460 kW. Until today, the -300 Series is with 614 built aircraft the most successful variant of the Twin Otter. 1988 the production of the DHC-6-300 ended.

After 18 years of not-producing the Twin Otter Viking Air acquired the production rights from Bombadier Aerospace, and started producing a new series, the DHC-6-400, whose first flight was on October 01, 2008. The DHC-6-400 is equipped with modern state-of-the-art avionics and even more powerful PTA6-34 engines also from Pratt and Whitney. Until summer 2014, there were built 55 aircraft of the -400 series.

The aircraft's powerful engines, it's STOL abilities, and it's spacious cabin make the DHC-6 a popular aircraft for skydiving and well-suited as a bush plane for inacessible and remote terrain in many developing countries.

The FlightGear version is the DHC-6-300 Series.

== Handling the aircraft ==
=== Preflight inspection ===
To make it as real as possible it is highly recommended to use the walker for the preflight inspection
* Nose:
** Remove the covers of both pitot tubes. Otherwise the airspeed indicator won't show anything. (The pitot tubes are approximately at eye level in front of the left and right cockpit doors)
** Check the nose gear (wheel, damper, taxi lamp) for damage and tire pressure
* Left wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the left tie-down
** Check the wing, landing light, aileron and flaps for damage
* Left main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Tail:
** Remove the rear tie-down
** Check the empennage for damage
* Right main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Right wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the right tiedown.
** Check the wing, landing light, aileron and flaps for damage

=== Engine startup process ===
[[File:DHC-6 Twin Otter center panel.jpg|thumb|400px|The center panel of the Twin Otter with engine instruments and radio stack]]
[[File:DHC-6 Twin Otter Overhead Panel.jpg|thumb|400px|The overhead panel of the Twin Otter]]
The Twin Otter is a quite complex aircraft, so starting up the engines isn't something that can be done in two or three steps.
# Ensure that the parking brake is set, the throttle levers are in idle position, propeller levers are on feather position and fuel condition levers are in cutoff position
# Switch on the battery master and select BATTERY as power source (Captain's overhead panel)
# Switch on the cabin lights and the instrument lighting
# Check that the voltage is above 18 V; normally it's around 24 V (above the radio sack)
# Make sure that there is enough fuel in the tanks for the flight you've planned
# Switch on the "FASTEN SEATBELT" and the "NO SMOKING" sign
# Switch on the beacon (center overhead panel)
# If you do not start up on asphalt, you must switch on the intake deflectors. Otherwise the engines can get damaged
# Engage both boost pumps (at the bottom of the center panel, below the engine instruments)
# If the outside temperature is below 0°C you must switch on the Pitot Heat and the Prop De-ice
# Switch the IND selector to BAT (above the radio stack)
# Check that no one's about to walk into the left propeller
# Engage the stater switch left and watch GG RPM rising (lowest engine instrument on the center panel)
# When GG RPM exceeds 12 % push the left condition lever full forward to supply the engine with fuel
# When the PROP RPM rises stable repeat the steps 12 - 14 for the right engine
# When also the right propeller increases it's RPM stable you can switch off the starter
# Push both propeller levers full forward
# Switch on the navigation lights (POSN LT)
# Switch on both generators
# Select R GEN on the IND selector
# Switch on the window heating (First officers overhead panel)
# Compare the indication of the heading indicator with the magnetic compass: If they don't coincide you have to synchronize them by adjusting the heading offset of the heading indicator
# Set the radios to the required frequencies and the altimeter to QNH/airport elevation

{{note|The startup procedure described above is slightly simplified. When following the in-sim checklists you have to execute 4 checklists with over 50 items.}}

=== Take off ===
* Flaps 10-20° depending on runway length
* Landing lights on
* Release the parking brake
* Engage Autofeather to automatically feather the prop if an engine fails
* Give full throttle. Some engine limit warnings will appear, but for a short time you may exceed the limits.
* Rotate at aprox. 80-95 kts

=== Climb ===
* Reduce power to fall below the engine limits
* Flaps up
* Landing lights off
* Airspeed around 110-120 kts
* Intake deflectors and Autofeather off

=== Cruise ===
* Airspeed 150-165 kts
* If outside temperature falls below 0°C switch on the Pitot Heat and the Prop De-ice
* Engine instruments within limits
* Keep an eye on the fuel quantity

=== Landing ===
* Set Flaps step by step
* Airspeed below 108 kts when Flaps extended
* Landing lights on
* Condition and propeller levers full forward
* If not landing on asphalt, activate the intake deflector
* Verify that the parking brake is off
* Touchdown with 60-70 kts
* After touchdown apply reverse thrust

=== Airspeeds ===

{| class="wikitable"
! Airspeed !! IAS
|-
| Stall speed, landing config (VS0) || 58 kts
|-
| Stall speed, cruise config (VS1) || 80 kts
|-
| Rotation speed (VR) || 80-95 kts
|-
| Maximum flap extended speed (VFE) || 108 kts
|-
| Cruise speed (VC) || 150-165 kts
|-
| Maneuvering speed (VA) || 130 kts
|-
| Never exceed speed (VNE) || 170 kts
|}

== Systems overview<ref>[http://www.cram.com/flashcards/twin-otter-dhc6-300-1980260 Twin Otter flashcards on cram.com]</ref><ref>[http://www.aerosoft2.de/downloads/twotter/Manual-Twin-Otter-Extended-Vol2-Systems.pdf Systems manual of Aerosoft's Twin Otter Extended]</ref> ==
The Twin Otter is equipped with several [[Aircraft systems|systems]] which operate the aircraft's components:
* Electrical: Operates i. a. hydraulic pump, boost pumps, engine gauges, turn coordinator, lighting, auto-feather
* Fuel: Supplies engines with fuel from two fuel tanks
* Hydraulic: Operates flaps, nose wheel steering, and wheel brakes
* [[FGproperties/Systems/Pitot|Pitot]]: Supplies airspeed indicators with dynamic pressure
* Pneumatic/Bleed Air: Operates heating and de-icing system and intake deflectors
* [[FGproperties/Systems/static|Static]]: Supplies airspeed indicators, altimeters and vertical speed indicators with static pressure
* [[Aircraft systems#Vacuum|Vacuum]]: Drives gyros for artifical horizon and directional gyro/heading indicator

Please note that as of July 2016 not all of these systems are implemented!

=== Electrical system ===
[[File:Twin Otter electrical system scheme.jpg|thumb|400px|The electrical system of the Twin Otter in a schematic representation]]
The electrical system is fed by an 40 ampere-hour battery and two engine-driven generators (which operate as starter-motors when starting the engine). It is primarily a 28 volt, direct current (DC) system, but some components need alternating current (AC) to work.

There exist seven buses which provide electrical power to several components:
# Left 28V DC bus: Is driven by left engine's generator. It feeds the DC voltmeter, hydraulic pump, prop auto-feather system, fire detection system, primary boost pumps (forward and rear), "R GEN FAIL" caution light
# Right 28V DC bus: Is driven by right engine's generator. It feeds the propeller overspeed governor, crossfeed fuel valve, secondary boost pumps (forward and rear), "L GEN FAIL" caution light
# Aux battery bus: Uses a auxiliary 3.6 ampere-hour battery to support the starter motors when starting the engines.
# Main battery bus: Is controlled by the Master Battery switch. When switched off, only the interior lights are provided with power. When MASTER is selected, it connects the electrical system to generators or battery or external power, depending on the EXTERNAL/BATTERY selector switch position.
# Battery/External Power bus: Is controlled by the EXTERNAL/BATTERY selector switch. When EXTERNAL is selected, it isolates the battery and connects the external power unit to the left and right bus. BATTERY will connect the battery to the left and right bus when generators are not running or the generator voltage is lower than the battery voltage. If the generator voltage is highter than the battery voltage it connects the left and right bus to the respective generator. When swithced off, the whole electrical system gets disconnected.
# 26V AC bus: Torque presure, fuel flow, and oil pressure gauges,
# 115V AC bus: Fuel quantity gauges, vacuum pumps for gyros (artifical horizon and directional gyro

The two AC buses are fed from one of the two static inverters. The No.1 inverter receives power from the Left 28V DC bus (and hence from the left generator), and the No.2 inverter receives power from the right 28V DC bus (and hence from the right generator). The inverters are selected alternatively by the inverter switch located on the overhead panel.

{{caution|Please note that the above chart isn't 100% correct. E.g. the "DC Master" is connected only to the Left 28V DC Bus, not to the right. Or that the battery is connected to the Main Battery Bus even if the External/Battery selector is switched off. Maybe I'll correct these errors someday, but please don't hesitate to do it if you want.}}

=== Fuel system ===
The Twin Otter's fuel systems consists of two fuel tanks, two primary fuel boost pumps, two secondary boost pumps, a crossfeed valve, gauges for fuel quantity and fuel flow, and a few caution lights.

The fuel tanks are located beneath the cabin floor and arranged in tandem. While the forward tank has a capacity of 1235 lbs the rear tank can contain up to 1341 lbs of fuel. With the engines mounted significantly above the fuel tanks the engines cannot bes supplied with fuel by gravity and hence the system has to rely completely on the fuel pumps. In normal operation (i.e. when the fuel tank selector is set to NORM) the foward tank feeds the right engine and the rear tank feeds the left engine.

However when the tank selector is set to BOTH ON FWD or BOTH ON AFT the boost pumps on the non-selected tank are deactivated and both boost pumps on the selected tank are activated which overwrites the boost pump switches.

The cross-feed valve is powered by the right DC bus, i.e. to work properly it needs either the battery connected or the right generator to be online.

If the primary boost pump fails, the secondary boost pump will automatically activate and the BOOST PUMP 1 FWD/AFT PRESSURE will light up. However the secondary boost pumps can be activated manually through the STANDBY BOOST PUMP EMER switches.

The FUEL LOW LEVEL caution lights will illuminate when the forward tank contains less than 75 lbs resp. the rear tank contains less than 110 lbs of fuel.

For the Twin Otter we have a refuelling system whereby you can easily refuel your Twin Otter or drain the tanks. To activate the fuel system, click on one of the fuel caps located on the left side of the fuselage or go to "Menu" -> "DHC-6" -> "Options" -> "Ground Services" -> "Fuel Truck controls".

=== Hydraulic system ===
The Twin Otter has a quite simple hydraulic system which is mostly fully automated. Hydraulic pressure is provided by an electrical pump which gets it's power from the left electrical bus. Only a few components are operated hydraulically: Nose wheel steering, wheel brakes, and flaps.

If the hydraulic system fails or is inactive, you can still move the flap lever or the nose wheel steering bar, but it won't have any effect on the nose wheel or flap setting.

The only manual control is a mechanic hand pump whih can be used as a backup in case of an failure of the electric pump. The hand pump is stowed behind the copilot's seat.

=== Pneumatic/Bleed air system ===
The very simple pneumatic system of the Twin Otter is only used to provide hot air for the heating and the de-icing system.

Two switches labeled "BLEED AIR" on the overhead panel control the bleed air valve on the left (resp. right) engine.

To get the pitot heat and the prop de-icing working, you have to switch on the bleed air switches.

The intake deflectors are also extended pneumatically, but they don't need the bleed air switch to be activated. Instead they need GG RPM (also called "N2", or "Ng") to be higher than 80 percent.

=== Pitot system ===
A working pitot system is very essential for safe flight, although it is connected to only one instrument: The airspeed indicator (ASI). But if the ASI fails you have no opportunity to know your airspeed and you end up very likely in a stall or even a crash.

The Twin Otter has two indepentently working pitot systems. The left pitot system feeds the pilot's ASI and the right pitot system feeds the copilot's ASI with dynamic pressure.

The two pitot tubes are located on the side of the fuselage in front of the pilot's (resp. copilot's) door. Make sure you removed the pitot tube covers from the pitot tubes prior to the flight or your ASI won't indicate your airspeed but act similar to an altimeter as in this case only static pressure is provided.

If you notice some odd behaviour of the ASI in flight (e.g. accelerating in climb and decelerating in descent) this is a strong indication of a iced pitot tube. Switch on the pitot heat to prevent icing.

=== Static system ===
There are three instruments that work with static pressure: Airspeed indicator (ASI), altimeter (ALT), and vertical speed indicator (VSI). The Twin Otter has a total of four static ports which are located in front of the cockpit doors, two on each side. As they are not pointing into the airstream they are not in danger of icing.

Now what happens in case of an failure of the pitot and/or the static system?

{| class="wikitable"
|-
!Instrument
!Static failure
!Pitot failure
!Both failure
|-
!VSI
|fixed at 0
|normal indication
|fixed at 0
|-
!ALT
|fixed at current value
|normal indication
|fixed at current value
|-
!ASI
|Ascent: indicates too slow
Descent: indicates too fast
|Ascent: Indicates too fast
Descent: Indicates too slow
|fixed at current value
|}

=== Vacuum system ===
Each engine has a vacuum pump that drives the gyros for the attidude indicators and the directional gyros.

The vacuum pump is powered by the gas generator (GG) of the respective engine.

== Keyboard shortcuts ==
[[File:Twin Otter flashlight.jpg|thumb|500px|Twin Otter showing the ALS flashlight]]
{| class="keytable"
!Key
!Function
|-
|{{Key press|Del}}
|Toggle thrust reversers for selected engine(s). Only with throttles in idle position
|-
|{{Key press|c}}
|Show/hide cockpit
|-
|{{Key press|!}}
|Select left engine
|-
|{{Key press|@}}
|Select right engine
|-
|{{Key press|~}}
|Select both engines
|-
|{{Key press|n}}/{{Key press|N}}
|Increase/decrease propeller pitch on selected engine(s)
|-
|{{Key press|j}}/{{Key press|J}}
|Increase/decrease left fuel condition
|-
|{{Key press|k}}/{{Key press|K}}
|Increase/decrease right fuel condition
|-
|{{Key press|l}}
|Toggle pitot heat on/off
|-
|{{Key press|L}}
|Toggle prop deice on/off
|-
|{{Key press|m}}
|Toggle intake deflectors on/off
|-
|{{Key press|f}}
|Toggle [[ALS technical notes#ALS flashlight|flashlight]] (only if [[ALS]] activated)
|-
|{{Key press|y}}
|Show/hide yokes
|-
|{{Key press|Y}}
|Show/hide pilots
|-
|{{Key press|F5}}
|Aileron trim left
|-
|{{Key press|F6}}
|Aileron trim right
|-
|{{Key press|F7}}
|Rudder trim left
|-
|{{Key press|F8}}
|Rudder trim right
|-
|{{Key press|F11}}
|Autopilot controls
|-
|{{Key press|F12}}
|Radio Stack
|-
|{{Key press|q}}
|Adjust nose wheel left
|-
|{{Key press|Ctrl|w}}
|Center nose wheel
|-
|{{Key press|e}}
|Adjust nose wheel right
|-
|{{Key press|w}}/{{Key press|a}}/{{Key press|s}}/{{Key press|d}}
|Move walker forward/backward/left/right. Only in Walk View or Walker Orbit View
|}

== Development ==
After some time of silence, in early 2014 the Twin Otter got under active development again. Until today (Jan. 2015), the visuals (mainly the interior, thanks to Patten and the FlightGear PAF team) and the electrical systems reached many improvements. For example, lanbo64 implemented a startup procedure which comes quite close to the reality.

In addition, dg-505 created an extensive tutorial system, which makes it easy to learn the standard operating procedures, and a number of checklists, which are taken from real Twin Otter Checklists. Richard Harrison is currently working on an [[ALS_technical_notes#Interior_shading|interior shadow cubemap]].

Currently, the Twin Otter is still under active [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 development]. If You are interested in helping to make the Twin Otter even better, You are welcome to join!

{{note|Since December 2015 the development of the Twin Otter has moved away from GitHub and over to the official FlightGear [[FGAddon]] hangar!

If you want to contribute to the Twin Otter it would be advantageous (but not mandatory!) if you have at least basic knowledge about version control. See [[FGAddon]] for details.

You also should get into contact with {{usr|Dg-505}} or {{usr|Bugman}}.
}}

== Review ==
{{review}}

'''Note that this review is about the actual version (January 2015), so some things may change in the future.'''

=== The appearance ===
The Twin Otter has a accurately modelled 3D model. It has some details like the nose gear, the hinges for the ailerons/flaps, or the pitot tubes. All control surfaces are animated (ailerons, flaps, elevator, rudder) and the amphibious version has a retractable gear with two nicely modelled floats. The doors are animated and open/close by clicking on it. In the basic version there are some liveries included, which look partly really good. Many more liveries are available in the [http://liveries.flightgear.org/aircraft.php?id=57 FlightGear Livery Database].

About the interior I have to say that both the cockpit and the cabin are quite accurate. Both have photo-realistic texturing, which is, at least from my point of view, very important for good optics. The interior gives some attention to detail: For example, the cabin has a extinguisher and a seatbelt/no smoking sign. Same thing in the cockpit: The Twin Otter has a very detailed cockpit with almost every instrument working and most switches animated and functional. In my view, the cockpit textures deserve a special mention. As said, it is photo-realistic textured and some of these textures look slightly worn, which gives the appearance of a pretty old, frequently used aircraft. Hats off to the designer(s), this looks really good and realistic.

Another nice function: If you want to know which instrument is which, you can press {{key press|Ctrl|C}} to find out. Then you see also the clickable hotspots in the cockpit.

''' My personal wishlist concerning the appearance:'''
* A bit more detail of the skis
* A bit more detail of the props
* Some additional details like antennas, etc.
* Animation and implementation of the missing switches

=== Flying the Twin Otter ===
Starting the engines of the Twin Otter can be done in two different ways: First, using the Autostart button, which is absolutely '''NOT''' recommended because it's extremely unrealistic! The second way is by using the checklists/tutorials, which guide you step by step through the procedures. If you aren't familiar with this aircraft and want it realistic, it could take some time to get the engines running.

Due to the powerful engines and the STOL skills, the twin otter flies after only a short time of accelerating on the runway. During the climb, the Twin Otter can prove her excellent climb rate: Near sea level a climb rate more than 1500 fpm is also with full fuel tanks and pax absolutely no problem.

In the air the Twin Otter is quite easy to handle. The reactions to the joystick inputs are direct but not too sensitive. As I haven't flown the Twin Otter in reality, so I can't say precisely how realistic the FDM is. But taking the size, the powerful engines, and the relatively small control surfaces into account, it seems to me, that the creator of the FDM has done a good job, and it comes fairly close to the reality.

The FlightGear Twin Otter is also equipped with an autopilot, which is self-explaining and easy to use, but in general I fly manually, because the aircraft is easy to handle.

Landing the Twin Otter is as easy as the rest of the flight. Just pull the throttles back, slow down, line up in front of the runway, and descent. It's worth mentioning that the flaps work very good, so if you need to descent fast for any reason, you can put full flaps, and descent at -2000 fpm without gaining too much speed.

If you only have a very short runway for landing, thrust reverse might be a useful tool. Right after touch down press the {{key press|Del}} key and apply full throttle. Your Twin Otter will quickly slow down, and is healthier for the brakes if you use reverse thrust.

=== Try this ===
If you want have a challenge, try to fly a long-range IFR route in bad weather without using the autopilot. Because all navigation instruments are operated from the cockpit, radio navigation is simulated realistically. Before the flight you can search for the VOR frequencies, and simply navigate from VOR to VOR using the NAV-Display and the DME.

Or try try flying in the mountains, where the high climb rate and the maneuverability is essential, especially if the weather is bad.

== Changelog ==
This is intended to give a brief overview over the update history. No guarantee of completeness.
=== Update 07.2015 ===
[[File:Twin Otter - new interior effects.jpg|thumb|500px|New glass effects in the Twin Otter]]
Some new interior effects have been added by lanbo64 and dg-505:
* Rain effect
* Fog on windows
* Frost
* Glass reflections
* Interior shadows
* Flashlight

=== Update 12.2015 ===
[[File:Twin Otter refuelling in LXGB.jpg|thumb|500px|Twin Otter secured and being refueled at Gibraltar Intl]]
In December 2015 the Twin Otter received a major update.
The major changes are:
* Addition of components to securing the aircraft
** Covers for the Pitot tubes
** Wheel chocks
** Covers for the engine intakes and exhausts
** Tie-downs
* Some cockpit elements added/updated
** A radar altimeter added (taken from the [[Cessna 550 Citation II|Citation]] and slightly modified)
** Removed the ADF display and replaced it with a Turn Coordinator (taken from the [[Boeing 707-420|707]] and slightly modified)
** Replaced the [[Avionics_and_instruments#Attitude_Indicator|Artifical Horizon]] with a more realistic one
** A Emergency Locator Transmitter added (taken from the [[Cessna 337G Skymaster|Cessna Skymaster]] and slightly modified)
** Added a switch to mute the fire alarm
** and other, minor improvements
* Some work on the sound
** Rain sound when outside the aircraft
** Sound for rain on the windshield
** Thunder sounds
* The skis have now significantly more detailed 3D-objects
* Added a sophisticated [[FGPanel|2D-Panel]] containing all the major instruments of the Twin Otter (that was tons of work!)
* New splash screens
* Added shadows for ALS and the default rendering system
* Added support for DFaber's [[Walk view|walker]]
* Ground services: Added an advanced fuel truck system
* Added custom dialog windows for the radio stack and the autopilot
* Added a custom flight recorder which reads many of the DHC6-specific properties
* Updated the Autostart/Shutdown functions and the [[Tutorials|tutorials]]/[[Aircraft Checklists|checklists]] to match with the updates
* and many more further improvements, updates and bugfixes...
[[File:Twin Otter cockpit - 29 June 2016.jpg|thumb|500px|Cockpit status from 29 June 2016]]

=== Update 06.2016 ===
* Pilot 3D Models. Show/hide them with {{key press|Shift|Y}}.
* Major systems and instrumentation update
** Left pitot and static system for pilot's instruments
** Right pitot and static system for copilot's instruments
** Two independent altimeters for pilot and copilot
** Second KI206 VOR indicator vor better capability of IFR and radio navigation
* Hydraulic system
** Gauge for hydraulic pressure
** Pressure depends on voltage output
* Smooth animation of all switches
* Animation and implementation of the nose wheel steering lever.
{{-}}

=== Update 11.2017 ===
After a lot of work and a long pause the Twin Otter now has a JSBSim variant!
* JSBSim FDM with data by Erik Hofmann from [http://jsbsim.cvs.sourceforge.net/viewvc/jsbsim/JSBSim/aircraft/DHC6/ jsbsim.cvs.sourceforge.net] and [[Aeromatic]]
* Realistic fuel system implementation in JSBSim
* Electrical system update:
** Main Battery bus, always connected to electrical system
** Battery/External Power bus, operate starter motors and switches between battery and external power
** Left 28 V DC bus, recieves power from Battery/External power bus or left generator, proviedes power to No.1 static inverter
** Right 28 V DC bus, recieves power from right generator, provides power to No.2 static inverter
** 26V AC Bus, recieves power from No.1 or No.2 static inverter
** 115 V AC Bus, recieves power from No.1 or No.2 static inverter
** Bus tie switch: When "NORMAL" power gets distributed between left and right 28 V DC bus, i.e. left bus feeds right bus when right generator is offline and right bus feeds left bus when left generator and battery and external power are offline. When "OPEN" Left bus only feeds left bus and right bus only feeds right bus, i.e. there is no power distribution.
** Circuit breakers are now included in the electrical system. So every consumer (e.g. Boost pumps, lights, Radios, Hydraulic oil pump, stall warning, caution lights, wipers, et al) has influence on the power consumption and can be deactivated individually by deactivating the respective C/B.
* Pneumatic system:
** Bleed air pressure is directly dependent on turbine RPM
** Intake deflectors need at least 50 psi to extend. Intake deflector switch must be held to "Extend" for at least 4 seconds.
* ...

== TODO list/future plans ==
In the forum thread about the development of the Twin Otter we've collected some ideas what will be done in the near future (or not so near, who knows...)
{{note|This is the status from January 4th, 2016}}
* Alternative DME, because the current one has some issues with the visibility of the digits<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271314 Forum development topic]</ref> {{done}}
* Ventilator models for the pilots<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271340 Forum development topic]</ref>{{not done}}
* Electrical system: More detailed simulation of the various buses, external power, Bus Tie, circuit breakers<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271426 Forum development topic]</ref> {{done}} (nov. 2017)
* Animation and implementation of Nose wheel steering bar and trim tabs<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref> {{done}} (29 June 2016)
* Proper animation of the Oil temperature gauges and propeller spin<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271462 Forum development topic]</ref>
* Maybe tweaking the FDM to better reaction to aileron input<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271414 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271420 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271431 Forum development topic]</ref>
* Toggleable Pilot models {{done}} (5 June 2016)
* Add support for [[Dual Control]] {{not done}}
* Add a version with a [[JSBSim]] FDM {{done}} (Nov. 2017)
* Variable interior: Different cockpit layouts (e.g. with a glass cockpit), different cabin layouts (e.g. cargo or combined passenger-cargo), multiple colour styles {{not done}}
* Add a control lock {{not done}}
* Additional baggage compartment in the long nose {{not done}}
* Add more, and enhance the securing and ground equipment (e.g. safety cones, include tiedowns in the FDM (like the Cessna 182) {{not done}}
* Generally, make the 3D model more detailed, more high poly {{not done}}

== Specifications ==
* Never exceed speed: 170 knots (195 mph , 314 km/h)
* Maximum speed: 170 knots (195 mph, 314 km/h)
* Cruise speed: 150-160 knots (173-184 mph, 278-296 km/h)
* Stall speed: 58 knots (VSO, gross weight, landing configuration)
* Stall speed: 80 knots (VS1, cruise configuration)
* Range: 920 nautical miles (1,050 mi, 1,690 km)
* Service ceiling: 25,000 ft (7,620 m)
* MTOW: 12,500 lbs (5,670 kg)
* Rate of climb: 1,600 ft/min (8.1 m/s)

== Gallery ==
<gallery mode="packed">
Twin_otter_rembrandt.png|Showing the Rembrandt landing light
Twin_otter_clouds.png|Flying IFR
Twin_otter_fog.png|Over the alps
Twin_otter_sunrise.png|Still over the alps
DHC-6 Twin Otter Cockpit.jpg|View from the Copilot
DHC-6 Twin Otter @ LOWI - Cockpit.jpg|Entering the Twin Otter in LOWI
DHC-6 Twin Otter.jpg|Over the Grand Canyon
DHC-6_Twin_Otter_@_Matterhorn.png|Circuiting the Matterhorn
Twin_Otter_winter.jpg|Zero altitude flying
De_Havilland_Canada_DHC-6_Twin_Otter_@_TNCM.jpg|Leaving Saint Marteen Island
DHC-6_flight.jpg|Flying over the woods
DHC-6_cabin.jpg|The cabin
De Havilland Canada DHC-6 Twin Otter @ Golden Gate Bridge.jpg|Landing at the Golden Gate bridge
Cockpit of the Twin Otter.jpg|Over the Grand Canyon at Sunset
Twin Otter over Lake Of Constance.jpg|Flying at the Lake of Constance
Twin Otter over Sognefjord.jpg|In Norway over the Sognefjord
Twin Otter Landing @ TNCS.jpg|Landing in heavy thunderstorms
Twin Otter @ BIMS (Iceland).jpg|Discovering small airfields in Iceland
Twin Otter by Adam Swift (Mig29pilot).jpg|Exploring the Scottish Highlands (by Adam Swift)
DHC-6 Twin Otter in steep climb.jpg|Steep climb in Swiss Alps
</gallery>

== Videos ==
{{#ev:youtube|2sPIYeXyi2o|Long range flight and polar navigation (by ''' lanbo64 ''')}}
{{#ev:youtube|MeWQgOOX49o|DHC-6 flight from LFLR to LFLS (by ''' Patten ''')}}

== Thanks to ==
* Syd Adams
* Christian Thiriot (PATTEN)
* Bo Lan (lanbo64)
* Jonathan Schellhase (dg-505)
* Clément de l'Hamaide (f-jjth)
* PAF Team
* Zdenal
* Erik
* abassign
* primtala2
* CaptB
* Adam Swift (Mig29pilot)
* tauchergreg
* Sebastian (rollershutter)
* Thorsten Renk
* The [[Cessna 172]] development team
* The whole FlightGear community

If you have contributed something to this aircraft but don't find your name on this list, feel free to contact me on the [https://forum.flightgear.org/ucp.php?i=pm&mode=compose&u=16519 FlightGear Forum], the [[User talk:Dg-505|FlightGear Wiki]], send an Email to <code>dg-505@web.de</code>, or just edit this page by yourself.

== External links ==
* {{Wikipedia|De Havilland Canada DHC-6 Twin Otter|noicon=1}} (Wikipedia)
* [http://www.blm.gov/style/medialib/blm/nifc/av.Par.70826.File.tmp/SOPA_otter.pdf Standard Operating Procedures (pdf)]
* [http://www.vikingair.com/viking-aircraft/dhc-6-twin-otter Official website]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 Development thread] (FlightGear Forum)

== References ==
{{Appendix}}

{{de Havilland Canada}}

[[Category:Aircraft with a cockpit-only autopilot]]

[[de:de Havilland Canada DHC-6 Twin Otter]]
[[fr:de Havilland Canada DHC-6 Twin Otter]]

De Havilland Canada DHC-6 Twin Otter/info

2017-11-18T23:46:13Z

Dg-505:

<noinclude>{{lowercase title}}</noinclude><includeonly>{{infobox aircraft
| name = de Havilland Canada DHC-6 Twin Otter
| hangar = fgaddon
| aircraft = dhc6
| image = Dhc6-splash1.jpg
| alt = {{LangSwitch
| de = Die DHC-6 Twin Otter im Flug
| en = The DHC-6 Twin Otter in flight
| fr = Le DHC-6 Twin Otter en vol
}}
| image2 = Twin Otter - interior shadows.jpg
| alt2 = {{LangSwitch
| de = Cockpit des Twin Otter mit Innenbeschattung
| en = Cockpit of the Twin Otter with interior shading
| fr = Cockpit du Twin Otter avec un ombrage intérieur
}}
| type = Civil utility aircraft/Military utility aircraft/STOL aircraft/Floatplane
| config = High wing aircraft/Monoplane aircraft/Fixed gear aircraft/Tricycle landing gear aircraft
| propulsion = Turboprop aircraft/Twin-engine aircraft
| manufacturer = de Havilland Canada
| authors = Syd Adams (Initial model)/Christian Thiriot (3D, Textures)/Bo Lan (Nasal, FDM, Systems)/Jonathan Schellhase (3D, Nasal, Systems, Sound, misc)/others (see below)
| devel-team = {{LangSwitch
| de = DHC-6 Twin Otter Entwicklungsteam
| en = DHC-6 Twin Otter team
| fr = L'équipe du DHC-6 Twin Otter
}}
| fdm = YASim, JSBSim
| fgname = dhc6/dhc6F/dhc6S
| status-fdm = 4
| status-systems = 4
| status-cockpit = 5
| status-model = 5
| ready = checklist/tutorials/rembrandt
| liverydbid = 57
| forumtid = 21965
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[de Havilland Canada DHC-6 Twin Otter]].
[[Category:Aircraft infobox documentation]]
</noinclude>

De Havilland Canada DHC-6 Twin Otter

2017-11-18T23:44:53Z

Dg-505: Update 11.2017

{{lowercase title}}{{:{{PAGENAME}}/info}}
The '''de Havilland Canada DHC-6 Twin Otter''', sometimes affectionately called the '''''Twotter''''', is a 20-passenger STOL (Short Takeoff and Landing) utility aircraft. It has often been called the most successful aircraft program in Canada's history. The Twin Otter is a high-wing twin-engine turboprop aircraft with a non-retractable tricycle gear, a non-pressurised cabin and two constant-speed props. In FlightGear, there are three versions available: Wheels, Floats (amphibious) and skis.

== About the original ==
The DHC-6 Twin Otter is the further development version of the [[DHC-3]] Otter of the same manufacturer. The development of the Twin Otter began in 1964, it's first flight was on May 20, 1965<ref>{{wikipedia|De Havilland Canada DHC-6 Twin Otter#Design and development}}</ref>. To keep the STOL abilities of the Otter, the DHC-6 got two powerful {{wikipedia|Pratt & Whitney Canada PT6}} turboprop engines with 410 kW produced by each turbine in the first version, the DHC-6-100.

In 1968, the Twin Otter was developed to a new version, the -200 series, which had improved STOL performance.

One year later, in 1969, the DHC-6-300 series was introduced, with more powerful engines, the PT6A-27 with 460 kW. Until today, the -300 Series is with 614 built aircraft the most successful variant of the Twin Otter. 1988 the production of the DHC-6-300 ended.

After 18 years of not-producing the Twin Otter Viking Air acquired the production rights from Bombadier Aerospace, and started producing a new series, the DHC-6-400, whose first flight was on October 01, 2008. The DHC-6-400 is equipped with modern state-of-the-art avionics and even more powerful PTA6-34 engines also from Pratt and Whitney. Until summer 2014, there were built 55 aircraft of the -400 series.

The aircraft's powerful engines, it's STOL abilities, and it's spacious cabin make the DHC-6 a popular aircraft for skydiving and well-suited as a bush plane for inacessible and remote terrain in many developing countries.

The FlightGear version is the DHC-6-300 Series.

== Handling the aircraft ==
=== Preflight inspection ===
To make it as real as possible it is highly recommended to use the walker for the preflight inspection
* Nose:
** Remove the covers of both pitot tubes. Otherwise the airspeed indicator won't show anything. (The pitot tubes are approximately at eye level in front of the left and right cockpit doors)
** Check the nose gear (wheel, damper, taxi lamp) for damage and tire pressure
* Left wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the left tie-down
** Check the wing, landing light, aileron and flaps for damage
* Left main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Tail:
** Remove the rear tie-down
** Check the empennage for damage
* Right main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Right wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the right tiedown.
** Check the wing, landing light, aileron and flaps for damage

=== Engine startup process ===
[[File:DHC-6 Twin Otter center panel.jpg|thumb|400px|The center panel of the Twin Otter with engine instruments and radio stack]]
[[File:DHC-6 Twin Otter Overhead Panel.jpg|thumb|400px|The overhead panel of the Twin Otter]]
The Twin Otter is a quite complex aircraft, so starting up the engines isn't something that can be done in two or three steps.
# Ensure that the parking brake is set, the throttle levers are in idle position, propeller levers are on feather position and fuel condition levers are in cutoff position
# Switch on the battery master and select BATTERY as power source (Captain's overhead panel)
# Switch on the cabin lights and the instrument lighting
# Check that the voltage is above 18 V; normally it's around 24 V (above the radio sack)
# Make sure that there is enough fuel in the tanks for the flight you've planned
# Switch on the "FASTEN SEATBELT" and the "NO SMOKING" sign
# Switch on the beacon (center overhead panel)
# If you do not start up on asphalt, you must switch on the intake deflectors. Otherwise the engines can get damaged
# Engage both boost pumps (at the bottom of the center panel, below the engine instruments)
# If the outside temperature is below 0°C you must switch on the Pitot Heat and the Prop De-ice
# Switch the IND selector to BAT (above the radio stack)
# Check that no one's about to walk into the left propeller
# Engage the stater switch left and watch GG RPM rising (lowest engine instrument on the center panel)
# When GG RPM exceeds 12 % push the left condition lever full forward to supply the engine with fuel
# When the PROP RPM rises stable repeat the steps 12 - 14 for the right engine
# When also the right propeller increases it's RPM stable you can switch off the starter
# Push both propeller levers full forward
# Switch on the navigation lights (POSN LT)
# Switch on both generators
# Select R GEN on the IND selector
# Switch on the window heating (First officers overhead panel)
# Compare the indication of the heading indicator with the magnetic compass: If they don't coincide you have to synchronize them by adjusting the heading offset of the heading indicator
# Set the radios to the required frequencies and the altimeter to QNH/airport elevation

{{note|The startup procedure described above is slightly simplified. When following the in-sim checklists you have to execute 4 checklists with over 50 items.}}

=== Take off ===
* Flaps 10-20° depending on runway length
* Landing lights on
* Release the parking brake
* Engage Autofeather to automatically feather the prop if an engine fails
* Give full throttle. Some engine limit warnings will appear, but for a short time you may exceed the limits.
* Rotate at aprox. 80-95 kts

=== Climb ===
* Reduce power to fall below the engine limits
* Flaps up
* Landing lights off
* Airspeed around 110-120 kts
* Intake deflectors and Autofeather off

=== Cruise ===
* Airspeed 150-165 kts
* If outside temperature falls below 0°C switch on the Pitot Heat and the Prop De-ice
* Engine instruments within limits
* Keep an eye on the fuel quantity

=== Landing ===
* Set Flaps step by step
* Airspeed below 108 kts when Flaps extended
* Landing lights on
* Condition and propeller levers full forward
* If not landing on asphalt, activate the intake deflector
* Verify that the parking brake is off
* Touchdown with 60-70 kts
* After touchdown apply reverse thrust

=== Airspeeds ===

{| class="wikitable"
! Airspeed !! IAS
|-
| Stall speed, landing config (VS0) || 58 kts
|-
| Stall speed, cruise config (VS1) || 80 kts
|-
| Rotation speed (VR) || 80-95 kts
|-
| Maximum flap extended speed (VFE) || 108 kts
|-
| Cruise speed (VC) || 150-165 kts
|-
| Maneuvering speed (VA) || 130 kts
|-
| Never exceed speed (VNE) || 170 kts
|}

== Systems overview<ref>[http://www.cram.com/flashcards/twin-otter-dhc6-300-1980260 Twin Otter flashcards on cram.com]</ref><ref>[http://www.aerosoft2.de/downloads/twotter/Manual-Twin-Otter-Extended-Vol2-Systems.pdf Systems manual of Aerosoft's Twin Otter Extended]</ref> ==
The Twin Otter is equipped with several [[Aircraft systems|systems]] which operate the aircraft's components:
* Electrical: Operates i. a. hydraulic pump, boost pumps, engine gauges, turn coordinator, lighting, auto-feather
* Fuel: Supplies engines with fuel from two fuel tanks
* Hydraulic: Operates flaps, nose wheel steering, and wheel brakes
* [[FGproperties/Systems/Pitot|Pitot]]: Supplies airspeed indicators with dynamic pressure
* Pneumatic/Bleed Air: Operates heating and de-icing system and intake deflectors
* [[FGproperties/Systems/static|Static]]: Supplies airspeed indicators, altimeters and vertical speed indicators with static pressure
* [[Aircraft systems#Vacuum|Vacuum]]: Drives gyros for artifical horizon and directional gyro/heading indicator

Please note that as of July 2016 not all of these systems are implemented!

=== Electrical system ===
[[File:Twin Otter electrical system scheme.jpg|thumb|400px|The electrical system of the Twin Otter in a schematic representation]]
The electrical system is fed by an 40 ampere-hour battery and two engine-driven generators (which operate as starter-motors when starting the engine). It is primarily a 28 volt, direct current (DC) system, but some components need alternating current (AC) to work.

There exist seven buses which provide electrical power to several components:
# Left 28V DC bus: Is driven by left engine's generator. It feeds the DC voltmeter, hydraulic pump, prop auto-feather system, fire detection system, primary boost pumps (forward and rear), "R GEN FAIL" caution light
# Right 28V DC bus: Is driven by right engine's generator. It feeds the propeller overspeed governor, crossfeed fuel valve, secondary boost pumps (forward and rear), "L GEN FAIL" caution light
# Aux battery bus: Uses a auxiliary 3.6 ampere-hour battery to support the starter motors when starting the engines.
# Main battery bus: Is controlled by the Master Battery switch. When switched off, only the interior lights are provided with power. When MASTER is selected, it connects the electrical system to generators or battery or external power, depending on the EXTERNAL/BATTERY selector switch position.
# Battery/External Power bus: Is controlled by the EXTERNAL/BATTERY selector switch. When EXTERNAL is selected, it isolates the battery and connects the external power unit to the left and right bus. BATTERY will connect the battery to the left and right bus when generators are not running or the generator voltage is lower than the battery voltage. If the generator voltage is highter than the battery voltage it connects the left and right bus to the respective generator. When swithced off, the whole electrical system gets disconnected.
# 26V AC bus: Torque presure, fuel flow, and oil pressure gauges,
# 115V AC bus: Fuel quantity gauges, vacuum pumps for gyros (artifical horizon and directional gyro

The two AC buses are fed from one of the two static inverters. The No.1 inverter receives power from the Left 28V DC bus (and hence from the left generator), and the No.2 inverter receives power from the right 28V DC bus (and hence from the right generator). The inverters are selected alternatively by the inverter switch located on the overhead panel.

{{caution|Please note that the above chart isn't 100% correct. E.g. the "DC Master" is connected only to the Left 28V DC Bus, not to the right. Or that the battery is connected to the Main Battery Bus even if the External/Battery selector is switched off. Maybe I'll correct these errors someday, but please don't hesitate to do it if you want.}}

=== Fuel system ===
The Twin Otter's fuel systems consists of two fuel tanks, two primary fuel boost pumps, two secondary boost pumps, a crossfeed valve, gauges for fuel quantity and fuel flow, and a few caution lights.

The fuel tanks are located beneath the cabin floor and arranged in tandem. While the forward tank has a capacity of 1235 lbs the rear tank can contain up to 1341 lbs of fuel. With the engines mounted significantly above the fuel tanks the engines cannot bes supplied with fuel by gravity and hence the system has to rely completely on the fuel pumps. In normal operation (i.e. when the fuel tank selector is set to NORM) the foward tank feeds the right engine and the rear tank feeds the left engine.

However when the tank selector is set to BOTH ON FWD or BOTH ON AFT the boost pumps on the non-selected tank are deactivated and both boost pumps on the selected tank are activated which overwrites the boost pump switches.

The cross-feed valve is powered by the right DC bus, i.e. to work properly it needs either the battery connected or the right generator to be online.

If the primary boost pump fails, the secondary boost pump will automatically activate and the BOOST PUMP 1 FWD/AFT PRESSURE will light up. However the secondary boost pumps can be activated manually through the STANDBY BOOST PUMP EMER switches.

The FUEL LOW LEVEL caution lights will illuminate when the forward tank contains less than 75 lbs resp. the rear tank contains less than 110 lbs of fuel.

For the Twin Otter we have a refuelling system whereby you can easily refuel your Twin Otter or drain the tanks. To activate the fuel system, click on one of the fuel caps located on the left side of the fuselage or go to "Menu" -> "DHC-6" -> "Options" -> "Ground Services" -> "Fuel Truck controls".

=== Hydraulic system ===
The Twin Otter has a quite simple hydraulic system which is mostly fully automated. Hydraulic pressure is provided by an electrical pump which gets it's power from the left electrical bus. Only a few components are operated hydraulically: Nose wheel steering, wheel brakes, and flaps.

If the hydraulic system fails or is inactive, you can still move the flap lever or the nose wheel steering bar, but it won't have any effect on the nose wheel or flap setting.

The only manual control is a mechanic hand pump whih can be used as a backup in case of an failure of the electric pump. The hand pump is stowed behind the copilot's seat.

=== Pneumatic/Bleed air system ===
The very simple pneumatic system of the Twin Otter is only used to provide hot air for the heating and the de-icing system.

Two switches labeled "BLEED AIR" on the overhead panel control the bleed air valve on the left (resp. right) engine.

To get the pitot heat and the prop de-icing working, you have to switch on the bleed air switches.

The intake deflectors are also extended pneumatically, but they don't need the bleed air switch to be activated. Instead they need GG RPM (also called "N2", or "Ng") to be higher than 80 percent.

=== Pitot system ===
A working pitot system is very essential for safe flight, although it is connected to only one instrument: The airspeed indicator (ASI). But if the ASI fails you have no opportunity to know your airspeed and you end up very likely in a stall or even a crash.

The Twin Otter has two indepentently working pitot systems. The left pitot system feeds the pilot's ASI and the right pitot system feeds the copilot's ASI with dynamic pressure.

The two pitot tubes are located on the side of the fuselage in front of the pilot's (resp. copilot's) door. Make sure you removed the pitot tube covers from the pitot tubes prior to the flight or your ASI won't indicate your airspeed but act similar to an altimeter as in this case only static pressure is provided.

If you notice some odd behaviour of the ASI in flight (e.g. accelerating in climb and decelerating in descent) this is a strong indication of a iced pitot tube. Switch on the pitot heat to prevent icing.

=== Static system ===
There are three instruments that work with static pressure: Airspeed indicator (ASI), altimeter (ALT), and vertical speed indicator (VSI). The Twin Otter has a total of four static ports which are located in front of the cockpit doors, two on each side. As they are not pointing into the airstream they are not in danger of icing.

Now what happens in case of an failure of the pitot and/or the static system?

{| class="wikitable"
|-
!Instrument
!Static failure
!Pitot failure
!Both failure
|-
!VSI
|fixed at 0
|normal indication
|fixed at 0
|-
!ALT
|fixed at current value
|normal indication
|fixed at current value
|-
!ASI
|Ascent: indicates too slow
Descent: indicates too fast
|Ascent: Indicates too fast
Descent: Indicates too slow
|fixed at current value
|}

=== Vacuum system ===
Each engine has a vacuum pump that drives the gyros for the attidude indicators and the directional gyros.

The vacuum pump is powered by the gas generator (GG) of the respective engine.

== Keyboard shortcuts ==
[[File:Twin Otter flashlight.jpg|thumb|500px|Twin Otter showing the ALS flashlight]]
{| class="keytable"
!Key
!Function
|-
|{{Key press|Del}}
|Toggle thrust reversers for selected engine(s). Only with throttles in idle position
|-
|{{Key press|c}}
|Show/hide cockpit
|-
|{{Key press|!}}
|Select left engine
|-
|{{Key press|@}}
|Select right engine
|-
|{{Key press|~}}
|Select both engines
|-
|{{Key press|n}}/{{Key press|N}}
|Increase/decrease propeller pitch on selected engine(s)
|-
|{{Key press|j}}/{{Key press|J}}
|Increase/decrease left fuel condition
|-
|{{Key press|k}}/{{Key press|K}}
|Increase/decrease right fuel condition
|-
|{{Key press|l}}
|Toggle pitot heat on/off
|-
|{{Key press|L}}
|Toggle prop deice on/off
|-
|{{Key press|m}}
|Toggle intake deflectors on/off
|-
|{{Key press|f}}
|Toggle [[ALS technical notes#ALS flashlight|flashlight]] (only if [[ALS]] activated)
|-
|{{Key press|y}}
|Show/hide yokes
|-
|{{Key press|Y}}
|Show/hide pilots
|-
|{{Key press|F5}}
|Aileron trim left
|-
|{{Key press|F6}}
|Aileron trim right
|-
|{{Key press|F7}}
|Rudder trim left
|-
|{{Key press|F8}}
|Rudder trim right
|-
|{{Key press|F11}}
|Autopilot controls
|-
|{{Key press|F12}}
|Radio Stack
|-
|{{Key press|q}}
|Adjust nose wheel left
|-
|{{Key press|Ctrl|w}}
|Center nose wheel
|-
|{{Key press|e}}
|Adjust nose wheel right
|-
|{{Key press|w}}/{{Key press|a}}/{{Key press|s}}/{{Key press|d}}
|Move walker forward/backward/left/right. Only in Walk View or Walker Orbit View
|}

== Development ==
After some time of silence, in early 2014 the Twin Otter got under active development again. Until today (Jan. 2015), the visuals (mainly the interior, thanks to Patten and the FlightGear PAF team) and the electrical systems reached many improvements. For example, lanbo64 implemented a startup procedure which comes quite close to the reality.

In addition, dg-505 created an extensive tutorial system, which makes it easy to learn the standard operating procedures, and a number of checklists, which are taken from real Twin Otter Checklists. Richard Harrison is currently working on an [[ALS_technical_notes#Interior_shading|interior shadow cubemap]].

Currently, the Twin Otter is still under active [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 development]. If You are interested in helping to make the Twin Otter even better, You are welcome to join!

{{note|Since December 2015 the development of the Twin Otter has moved away from GitHub and over to the official FlightGear [[FGAddon]] hangar!

If you want to contribute to the Twin Otter it would be advantageous (but not mandatory!) if you have at least basic knowledge about version control. See [[FGAddon]] for details.

You also should get into contact with {{usr|Dg-505}} or {{usr|Bugman}}.
}}

== Review ==
{{review}}

'''Note that this review is about the actual version (January 2015), so some things may change in the future.'''

=== The appearance ===
The Twin Otter has a accurately modelled 3D model. It has some details like the nose gear, the hinges for the ailerons/flaps, or the pitot tubes. All control surfaces are animated (ailerons, flaps, elevator, rudder) and the amphibious version has a retractable gear with two nicely modelled floats. The doors are animated and open/close by clicking on it. In the basic version there are some liveries included, which look partly really good. Many more liveries are available in the [http://liveries.flightgear.org/aircraft.php?id=57 FlightGear Livery Database].

About the interior I have to say that both the cockpit and the cabin are quite accurate. Both have photo-realistic texturing, which is, at least from my point of view, very important for good optics. The interior gives some attention to detail: For example, the cabin has a extinguisher and a seatbelt/no smoking sign. Same thing in the cockpit: The Twin Otter has a very detailed cockpit with almost every instrument working and most switches animated and functional. In my view, the cockpit textures deserve a special mention. As said, it is photo-realistic textured and some of these textures look slightly worn, which gives the appearance of a pretty old, frequently used aircraft. Hats off to the designer(s), this looks really good and realistic.

Another nice function: If you want to know which instrument is which, you can press {{key press|Ctrl|C}} to find out. Then you see also the clickable hotspots in the cockpit.

''' My personal wishlist concerning the appearance:'''
* A bit more detail of the skis
* A bit more detail of the props
* Some additional details like antennas, etc.
* Animation and implementation of the missing switches

=== Flying the Twin Otter ===
Starting the engines of the Twin Otter can be done in two different ways: First, using the Autostart button, which is absolutely '''NOT''' recommended because it's extremely unrealistic! The second way is by using the checklists/tutorials, which guide you step by step through the procedures. If you aren't familiar with this aircraft and want it realistic, it could take some time to get the engines running.

Due to the powerful engines and the STOL skills, the twin otter flies after only a short time of accelerating on the runway. During the climb, the Twin Otter can prove her excellent climb rate: Near sea level a climb rate more than 1500 fpm is also with full fuel tanks and pax absolutely no problem.

In the air the Twin Otter is quite easy to handle. The reactions to the joystick inputs are direct but not too sensitive. As I haven't flown the Twin Otter in reality, so I can't say precisely how realistic the FDM is. But taking the size, the powerful engines, and the relatively small control surfaces into account, it seems to me, that the creator of the FDM has done a good job, and it comes fairly close to the reality.

The FlightGear Twin Otter is also equipped with an autopilot, which is self-explaining and easy to use, but in general I fly manually, because the aircraft is easy to handle.

Landing the Twin Otter is as easy as the rest of the flight. Just pull the throttles back, slow down, line up in front of the runway, and descent. It's worth mentioning that the flaps work very good, so if you need to descent fast for any reason, you can put full flaps, and descent at -2000 fpm without gaining too much speed.

If you only have a very short runway for landing, thrust reverse might be a useful tool. Right after touch down press the {{key press|Del}} key and apply full throttle. Your Twin Otter will quickly slow down, and is healthier for the brakes if you use reverse thrust.

=== Try this ===
If you want have a challenge, try to fly a long-range IFR route in bad weather without using the autopilot. Because all navigation instruments are operated from the cockpit, radio navigation is simulated realistically. Before the flight you can search for the VOR frequencies, and simply navigate from VOR to VOR using the NAV-Display and the DME.

Or try try flying in the mountains, where the high climb rate and the maneuverability is essential, especially if the weather is bad.

== Changelog ==
This is intended to give a brief overview over the update history. No guarantee of completeness.
=== Update 07.2015 ===
[[File:Twin Otter - new interior effects.jpg|thumb|500px|New glass effects in the Twin Otter]]
Some new interior effects have been added by lanbo64 and dg-505:
* Rain effect
* Fog on windows
* Frost
* Glass reflections
* Interior shadows
* Flashlight

=== Update 12.2015 ===
[[File:Twin Otter refuelling in LXGB.jpg|thumb|500px|Twin Otter secured and being refueled at Gibraltar Intl]]
In December 2015 the Twin Otter received a major update.
The major changes are:
* Addition of components to securing the aircraft
** Covers for the Pitot tubes
** Wheel chocks
** Covers for the engine intakes and exhausts
** Tie-downs
* Some cockpit elements added/updated
** A radar altimeter added (taken from the [[Cessna 550 Citation II|Citation]] and slightly modified)
** Removed the ADF display and replaced it with a Turn Coordinator (taken from the [[Boeing 707-420|707]] and slightly modified)
** Replaced the [[Avionics_and_instruments#Attitude_Indicator|Artifical Horizon]] with a more realistic one
** A Emergency Locator Transmitter added (taken from the [[Cessna 337G Skymaster|Cessna Skymaster]] and slightly modified)
** Added a switch to mute the fire alarm
** and other, minor improvements
* Some work on the sound
** Rain sound when outside the aircraft
** Sound for rain on the windshield
** Thunder sounds
* The skis have now significantly more detailed 3D-objects
* Added a sophisticated [[FGPanel|2D-Panel]] containing all the major instruments of the Twin Otter (that was tons of work!)
* New splash screens
* Added shadows for ALS and the default rendering system
* Added support for DFaber's [[Walk view|walker]]
* Ground services: Added an advanced fuel truck system
* Added custom dialog windows for the radio stack and the autopilot
* Added a custom flight recorder which reads many of the DHC6-specific properties
* Updated the Autostart/Shutdown functions and the [[Tutorials|tutorials]]/[[Aircraft Checklists|checklists]] to match with the updates
* and many more further improvements, updates and bugfixes...
[[File:Twin Otter cockpit - 29 June 2016.jpg|thumb|500px|Cockpit status from 29 June 2016]]

=== Update 06.2016 ===
* Pilot 3D Models. Show/hide them with {{key press|Shift|Y}}.
* Major systems and instrumentation update
** Left pitot and static system for pilot's instruments
** Right pitot and static system for copilot's instruments
** Two independent altimeters for pilot and copilot
** Second KI206 VOR indicator vor better capability of IFR and radio navigation
* Hydraulic system
** Gauge for hydraulic pressure
** Pressure depends on voltage output
* Smooth animation of all switches
* Animation and implementation of the nose wheel steering lever.
{{-}}

=== Update 11.2017 ===
After a lot of work and a long pause the Twin Otter now has a JSBSim variant!
* JSBSim FDM with data by Erik Hofmann from [http://jsbsim.cvs.sourceforge.net/viewvc/jsbsim/JSBSim/aircraft/DHC6/ jsbsim.cvs.sourceforge.net] and [[Aeromatic]]
* Realistic fuel system implementation in JSBSim
* Electrical system update:
** Main Battery bus, always connected to electrical system
** Battery/External Power bus, operate starter motors and switches between battery and external power
** Left 28 V DC bus, recieves power from Battery/External power bus or left generator, proviedes power to No.1 static inverter
** Right 28 V DC bus, recieves power from right generator, provides power to No.2 static inverter
** 26V AC Bus, recieves power from No.1 or No.2 static inverter
** 115 V AC Bus, recieves power from No.1 or No.2 static inverter
** Bus tie switch: When "NORMAL" power gets distributed between left and right 28 V DC bus, i.e. left bus feeds right bus when right generator is offline and right bus feeds left bus when left generator and battery and external power are offline. When "OPEN" Left bus only feeds left bus and right bus only feeds right bus, i.e. there is no power distribution.
** Circuit breakers are now included in the electrical system. So every consumer (e.g. Boost pumps, lights, Radios, Hydraulic oil pump, stall warning, caution lights, wipers, et al) has influence on the power consumption and can be deactivated individually by deactivating the respective C/B.
* Pneumatic system:
** Bleed air pressure is directly dependent on turbine RPM
** Intake deflectors need at least 50 psi to extend. Intake deflector switch must be held to "Extend" for at least 4 seconds.
* ...

== TODO list/future plans ==
In the forum thread about the development of the Twin Otter we've collected some ideas what will be done in the near future (or not so near, who knows...)
{{note|This is the status from January 4th, 2016}}
* Alternative DME, because the current one has some issues with the visibility of the digits<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271314 Forum development topic]</ref> {{done}}
* Ventilator models for the pilots<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271340 Forum development topic]</ref>{{not done}}
* Electrical system: More detailed simulation of the various buses, external power, Bus Tie, circuit breakers<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271426 Forum development topic]</ref> {{progressbar|30}}{{pending}}
* Animation and implementation of Nose wheel steering bar and trim tabs<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref> {{done}} (29 June 2016)
* Proper animation of the Oil temperature gauges and propeller spin<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271462 Forum development topic]</ref>
* Maybe tweaking the FDM to better reaction to aileron input<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271414 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271420 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271431 Forum development topic]</ref>
* Toggleable Pilot models {{done}} (5 June 2016)
* Add support for [[Dual Control]] {{not done}}
* Add a version with a [[JSBSim]] FDM {{pending}}
* Variable interior: Different cockpit layouts (e.g. with a glass cockpit), different cabin layouts (e.g. cargo or combined passenger-cargo), multiple colour styles {{not done}}
* Add a control lock {{not done}}
* Additional baggage compartment in the long nose {{not done}}
* Add more, and enhance the securing and ground equipment (e.g. safety cones, include tiedowns in the FDM (like the Cessna 182) {{not done}}
* Generally, make the 3D model more detailed, more high poly {{not done}}

== Specifications ==
* Never exceed speed: 170 knots (195 mph , 314 km/h)
* Maximum speed: 170 knots (195 mph, 314 km/h)
* Cruise speed: 150-160 knots (173-184 mph, 278-296 km/h)
* Stall speed: 58 knots (VSO, gross weight, landing configuration)
* Stall speed: 80 knots (VS1, cruise configuration)
* Range: 920 nautical miles (1,050 mi, 1,690 km)
* Service ceiling: 25,000 ft (7,620 m)
* MTOW: 12,500 lbs (5,670 kg)
* Rate of climb: 1,600 ft/min (8.1 m/s)

== Gallery ==
<gallery mode="packed">
Twin_otter_rembrandt.png|Showing the Rembrandt landing light
Twin_otter_clouds.png|Flying IFR
Twin_otter_fog.png|Over the alps
Twin_otter_sunrise.png|Still over the alps
DHC-6 Twin Otter Cockpit.jpg|View from the Copilot
DHC-6 Twin Otter @ LOWI - Cockpit.jpg|Entering the Twin Otter in LOWI
DHC-6 Twin Otter.jpg|Over the Grand Canyon
DHC-6_Twin_Otter_@_Matterhorn.png|Circuiting the Matterhorn
Twin_Otter_winter.jpg|Zero altitude flying
De_Havilland_Canada_DHC-6_Twin_Otter_@_TNCM.jpg|Leaving Saint Marteen Island
DHC-6_flight.jpg|Flying over the woods
DHC-6_cabin.jpg|The cabin
De Havilland Canada DHC-6 Twin Otter @ Golden Gate Bridge.jpg|Landing at the Golden Gate bridge
Cockpit of the Twin Otter.jpg|Over the Grand Canyon at Sunset
Twin Otter over Lake Of Constance.jpg|Flying at the Lake of Constance
Twin Otter over Sognefjord.jpg|In Norway over the Sognefjord
Twin Otter Landing @ TNCS.jpg|Landing in heavy thunderstorms
Twin Otter @ BIMS (Iceland).jpg|Discovering small airfields in Iceland
Twin Otter by Adam Swift (Mig29pilot).jpg|Exploring the Scottish Highlands (by Adam Swift)
DHC-6 Twin Otter in steep climb.jpg|Steep climb in Swiss Alps
</gallery>

== Videos ==
{{#ev:youtube|2sPIYeXyi2o|Long range flight and polar navigation (by ''' lanbo64 ''')}}
{{#ev:youtube|MeWQgOOX49o|DHC-6 flight from LFLR to LFLS (by ''' Patten ''')}}

== Thanks to ==
* Syd Adams
* Christian Thiriot (PATTEN)
* Bo Lan (lanbo64)
* Jonathan Schellhase (dg-505)
* Clément de l'Hamaide (f-jjth)
* PAF Team
* Zdenal
* Erik
* abassign
* primtala2
* CaptB
* Adam Swift (Mig29pilot)
* tauchergreg
* Sebastian (rollershutter)
* Thorsten Renk
* The [[Cessna 172]] development team
* The whole FlightGear community

If you have contributed something to this aircraft but don't find your name on this list, feel free to contact me on the [https://forum.flightgear.org/ucp.php?i=pm&mode=compose&u=16519 FlightGear Forum], the [[User talk:Dg-505|FlightGear Wiki]], send an Email to <code>dg-505@web.de</code>, or just edit this page by yourself.

== External links ==
* {{Wikipedia|De Havilland Canada DHC-6 Twin Otter|noicon=1}} (Wikipedia)
* [http://www.blm.gov/style/medialib/blm/nifc/av.Par.70826.File.tmp/SOPA_otter.pdf Standard Operating Procedures (pdf)]
* [http://www.vikingair.com/viking-aircraft/dhc-6-twin-otter Official website]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 Development thread] (FlightGear Forum)

== References ==
{{Appendix}}

{{de Havilland Canada}}

[[Category:Aircraft with a cockpit-only autopilot]]

[[de:de Havilland Canada DHC-6 Twin Otter]]
[[fr:de Havilland Canada DHC-6 Twin Otter]]

FlightGear Newsletter November 2017

2017-11-18T23:02:40Z

Dg-505: /* In the hangar */ DHC-6 Twin Otter update

{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community.}} 

{{Newsletter-header|November 2017}} 
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-item|FSweekend 2017}} 
{{Newsletter-cover-header|Development news}} 
{{Newsletter-cover-item|G1000-style avionics}} 
{{Newsletter-cover-header|In the hangar}} 
{{Newsletter-cover-item|IDG update}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>

== FSweekend 2017 ==
During [[FSweekend]] 2017, team FlightGear had the privilege to give a number of presentations in a big theatre at the [[Aviodrome]] aerospace museum in Lelystad, the Netherlands. One of the presentations covered the launch, engine failure and subsequent return to launch site of a [[Space Shuttle]]. Part of the presentation was recorded and can be seen below.

{{#ev:youtube|eorJBus1qDk}}

== Development news ==

=== G1000-style avionics ===
Here is a little update of the G1000 emulation. Stuart has now got the key [[MapStructure]] layers in place, though they are not styled correctly for the '''G1000''' yet and Stuart would like to replace some of them (airspace in particular) with vector data, and started on the MFD architecture. For prototyping he hacked together a [[PUI]] dialog box, which speeds up development massively as it reloads all the Nasal code each time it's opened.

There's a screenshot of it here: [[File:Fg1000_mfd.jpg|thumb|right]]

There's also a wiki page of the current status here: http://wiki.flightgear.org/FG1000 Next steps are to get the MFD architecture in place - this will probably require some changes to Richard's generic [[Canvas MFD Framework|MFD]] to support buttons that don't change the MFD pages better. Stuart has not yet pushed this to fgdata - he'll wait until he's happy with the overall architectures so that there is a solid base for anyone else interested in helping out.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/36103513/
|title = <nowiki> [Flightgear-devel] FG1000 update </nowiki>
|author = <nowiki> Stuart Buchanan </nowiki>
|date = Nov 4th, 2017
|added = Nov 4th, 2017
|script_version = 0.40
}}</ref>

If you are interested in helping with any of this, and familiar with Inkscape, GIMP or maybe even Blender it would be great if you could get in touch via the [https://forum.flightgear.org/viewtopic.php?f=71&t=32764 FG1000 topic on the forum] to see if we can come up with the artwork resembling a G1000-style device, possibly even a 3D model for aircraft developers. Having the artwork in place for creating a simple "skin" would also mean that we could get rid of the [[PUI]] dialog and instead use a native Canvas GUI window showing an appropriate raster image with bindings for each button/dial via [[Canvas Event Handling]].

== In the hangar ==
=== IDG update ===
The it0uchpods Development Group have continued to work on the IDG-A32X / A33X / MD-11X Professional series aircraft.
==== MD-11X ====
The MD-11X was publicly released on October 29th. It includes a complex pneumatic and electrical system, as well as an advanced autopilot / autoland system. While not as complete as the Airbii, this aircraft is ready to fly, and may be downloaded from [https://github.com/it0uchpods/IDG-MD-11X GitHub].
==== IDG-A32X ====
The IDG-A32X continues to be improved with a new and improved cockpit 3D model by our newest member, TH-555 (Thorsten H). Legoboyvdlp (Jonathan R.) continues to work on the ECAM, with an electrical SD page underway, while it0uchpods (Joshua D.) has created a new (WIP) PFD, which may be accessed from the Utilities > Test Canvas menu. Wecsje (Charlie S.) is currently working on the paintkits, which will be increased to 4096 * 4096 to allow HD liveries. Recent improvements include a fix to the speedbrake logic, double-flashing strobe lights, shadows in the cockpit by kikossousan (Mehdi K.) and a new sound for the CFM LEAP engines. The aircraft's roll characteristics has been retuned to have a more realistic flight behaviour in DIRECT ROLL mode (ALTN / DIRECT laws).

==== IDG-A33X ====
Work also continues on the IDG-A33X, albeit at a slower pace. The A32X cockpit and shadows by kikossousan have been added pending modifications to the cockpit to a (very similar) A330 cockpit. The drag of the flaps and slats has been increased to a more realistic value, while the fly by wire, FADEC, FMGC, and Canvas screens have all been bugfixed and improved. The aircraft's roll characteristics has been retuned, just like the IDG-A33X

==== Event ====
On November 4th, 2017, the IDG-A32X turned one year old, and we are very proud with what we have accomplished in that time, and we assure you that there is much more to come!

To celebrate this, we plan to have a group flight from München (EDDM) to Hamburg Finkerwerder (EDHI), and then onwards to Frankfurt Main (EDDF). EDHI (Hamburg Finkenwerder) is where one of the Airbus factories is located, and is an airport and seaport combined due to the Elbe river. Most of the A320ceo/neo production line is located there, and there is some nice scenery in FlightGear.

'''Date:''' Saturday 18th November 2017 
'''Time:''' meetup at 17:30UTC, departure at 18:15UTC. ETA on ending time: TBD 
'''Location:''' initial meetup at EDDM, for spawn positions see the forum 
'''Aircraft:''' IDG-A32X (or IDG-A33X), NO others allowed! 
 
Read more at [https://forum.flightgear.org/viewtopic.php?f=10&t=33217 the forum]!

=== DHC-6 Twin Otter update ===
The [[Twin Otter]] now has a [[JSBSim]] variant!

With FDM data provided by Erik Hofmann from [http://jsbsim.cvs.sourceforge.net/viewvc/jsbsim/JSBSim/aircraft/DHC6/ jsbsim.cvs.sourceforge.net] and [[Aeromatic]] I created a JSBSim FDM for the Twin Otter. Because of my lack of knowledge this FDM flies not very realistic/plausible and should be considered experimental!

I see this as a starting point for future tuning of the JSBSim FDM variant. My long term goal is to abandon the [[Yasim]] variants of the DHC-6 as soon as the JSBSim FDM reaches a better state than the Yasim FDM because in JSBSim you can do much more fancy stuff.

There has also been an update to the various systems of the Twin Otter: We now simulate various electrical buses: Left DC bus which gets powered from Battery or External Power Unit or Left generator, Right DC Bus which gets powered from Right Generator, 26 V and 115 V AC Bus which get powered from one of the static inverters. The bus tie switch has been implemented that connects the left and right DC bus. Also the circuit breakers which have been added and animated in a previous update are now integrated in the electrical system.

The lighting of the instruments is now controlled individually by three knobs at the overhead panel like in the real thing.

All engine instruments that need electrical power to work are passed through a filter so that they behave correctly in case that the power gets lost.

In addition to this there is now a simple implementation of a pneumatic/bleed air system which provides a realistic behaviour of the intake deflectors.

You can recieve the update via SVN/[[FGAddon]] or via the catalog system once it has been updated.

== Scenery corner ==

== Community news ==

== Contributing ==

=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

FlightGear's Screenshot of the Month November 2017 is ''Approaching Sint Maarten'' by tonghuix
[[File:SOTM-Nov17.jpg|900px|center|Approaching Sint Maarten]]



{{Appendix}}

[[Category:FlightGear Newsletter|2017 11]]
[[Category:Changes after 2017.3]]

[[de:FlightGear Newsletter {{#time: F Y | 2017-11 | de }}]]

FlightGear Newsletter May 2017

2017-06-08T19:11:54Z

Dg-505: /* Screenshot of the Month */

File:Bo 105 over Sint Marteen.png

2017-06-08T19:11:13Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=An MBB Bo 105 at a sightseeing tour over Sint Marteen island}} {{de|1=Eine MBB Bo105 auf einem Rundflug über der Insel St. Martin}}
|date=2017-05-10
|source=http://i.imgur.com/ve0u4He.png
|author=Icecode GL
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshots of helicopters]]
[[Category:Screenshots of cockpits]]
[[Category:Screenshots of scenery]]
[[Category:Screenshot of the month|2017 05]]

File:Bo 105 over Sint Marteen.png

2017-06-08T19:08:06Z

Dg-505: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=An MBB Bo 105 at a sightseeing tour over Sint Marteen island}}{{de|1=Eine MBB Bo105 auf einem Rundflug über der Insel St. Martin}}
|date=2017-05-10
|source=http://i.imgur.com/ve0u4He.png
|author=Icecode GL
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshots of helicopters]]
[[Category:Screenshots of cockpits]]
[[Category:Screenshots of scenery]]
[[Category:Screenshot of the month]]

File:777 over Malaga.jpg

2017-05-18T16:41:24Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=Cockpit of a Boeing 777 in flight over Malaga, Spain}} {{de|1=Cockpit einer Boeing 777 im Flug über Malaga, Spanien}}
|date=2017-04-07
|source=http://i.imgur.com/hZhyHx5.jpg
|author=Icecode GL
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Boeing 777 cockpit screenshots]]
[[Category:Screenshots of scenery in Europe]]
[[Category:Screenshot of the month|2017 04]]

FlightGear Newsletter April 2017

2017-05-18T16:39:26Z

Dg-505: /* Screenshot of the Month */

{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter March 2017]].}} 

{{Newsletter-header|April 2017}} 
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
{{Newsletter-cover-header|In the hangar}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>

== Development news ==

'''MapGear is out!'''

MapGear.py is a mapping tool for FlightGear that saves the flight path as an animated .GIF.

The aim is to create a nice map projection/animation for any log file submitted. For this to happen a
good degree of numerical tunning is required so the more feedback the project has from users the better.
Feedback would be greatly appreciated!

So far, the program seems to be stable enough so it is worth of publishing here in the FlightGear Newsletter.

It consists of a small python script and a few Geo information data files taken from NaturalEarth.

Stay tuned via the announcement page:
https://forum.flightgear.org/viewtopic.php?f=6&t=31741

Screenshot:
[img]http://i.imgur.com/cUuza9l.gif[/img]

Licensed under the GPLv2+

== In the hangar ==
=== Updates to the Citation II ===
During March 2017 the [[Cessna_550_Citation_II|Citation II]] has received a number of updates:
==== Citation II config dialog ====
One of the more prominent ones is the new Citation config dialog. It allows for settings, such as, what group of items you want to be stored throughout sessions. Also, for convenience, it provides some shortcuts to most used dialogs and a button to reset all circuit-breakers at once.

Check it out in sim via <code>menu -> Citation II -> Citation II config</code>.

==== tutorials ====
Also 2 [[Tutorials|tutorials]] have been added in the [[Boeing_707-420|707]] style - with markers, view zoom and explicit messages. See the Citation II config dialog or menu -> help -> tutorials.

==== state overlays ====
It is now possible to start the Citation II in some assorted [[State_Overlay_System|states]]. You could start FG on a parking space and add <code>--state=parking</code> to startup the Citation cold and dark. This would be a good place to start the startup tutorial from the config dialog.

Or you could start on the runway and add <code>--state=take-off</code> to your launcher. All you need to do is throttle up and go! Or take the tutorial "take-off" from the config dialog, which will guide you savely to cruise altitude, according to official checklists.

All possible states are:
* '''parking''' ( cold and dark, all systems off) (same as without --state=$state )
* '''taxi''' ( engines and all systems running - ready to taxi )
* '''take-off''' ( flaps and AP set - just throttle up and go )
* '''cruise''' ( flying at FL360 on AP )
* '''approach''' ( !experimental! )
For details see: [[Cessna_550_Citation_II#will_be_released_with_2017.2|Citation II]]

==== new splash screen system ====
James has added a new splash screen scheme, as well as a new preview feature for the [[FlightGear_Qt_launcher|QT launcher]]. The Citation II now complies with that scheme and provides a new logo and some brand-new splash screens.

=== Updates to the ERCO Ercoupe ===
[[File:Ercoupe-cockpit.jpg|thumb|right|The improved ERCO Ercoupe cockpit]]
After the discussion in the mailing list about possibly adding the Ercoupe as a second default aircraft for the novice users the Ercoupe has had a considerable upgrade:
* The FDM has been improved
* Reflection effects are added to the fuselage
* Reflection and shadow effects are added to the cockpit
* Cockpit panel and instruments have been improved
* Textures have been improved
* A number of new liveries were added
* Functional navigation lights were added

== Scenery corner ==

== Community news ==

== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].

|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====
FlightGear's Screenshot of the Month May 2016 is ''Early Morning Coffee'' by {{usr|Icecode|Icecode GL}}
[[File:777 over Malaga.jpg|900px|center|Early Morning Coffee]]

If you want to participate in the screenshot contest of May 2017, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=32163 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=32163#p310086 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of May 2017.

[[Category:FlightGear Newsletter|2017 04]]
[[Category:Changes after 2017.1]]

File:777 over Malaga.jpg

2017-05-18T16:36:46Z

Dg-505: Dg-505 uploaded a new version of File:777 over Malaga.jpg

=={{int:filedesc}}==
{{Information
|description={{en|1=Cockpit of a Boeing 777 in flight over Malaga, Spain}}{{de|1=Cockpit einer Boeing 777 im Flug über Malaga, Spanien}}
|date=2017-04-07
|source=http://i.imgur.com/hZhyHx5.jpg
|author=Icecode GL
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Boeing 777 cockpit screenshots]]
[[Category:Screenshots of scenery in Europe]]
[[Category:Screenshot of the month]]

File:777 over Malaga.jpg

2017-05-18T16:34:53Z

Dg-505: User created page with UploadWizard

Talk:FlightGear Newsletter March 2017

2017-04-05T12:04:20Z

Dg-505: SOTM March 2017

== SOTM March 2017 ==
Hi Admins,
can you please add the SOTM of March to this Newsletter?

<syntaxhighlight>
FlightGear's Screenshot of March 2017 is ''Sea of clouds'' by {{usr|Thorsten}}
[[File:DHC-6 in Alaska.jpg|900px|center|Sea of clouds]]

If you want to participate in the screenshot contest of April, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=31985 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=31985#p308198 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of May.
</syntaxhighlight>

Thank you

[[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 08:04, 5 April 2017 (EDT)

File:DHC-6 in Alaska.jpg

2017-04-05T12:00:37Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=A DHC-6 Twin Otter is exploring the mountainous landscape of southern Alaska east of Palmer (PAAQ)}} 
{{de|1=Eine DHC-6 Twin Otter im Flug über die bergige Landschaft des südlichen Alaska östlich von Palmer (PAAQ)}}
|date=2017-03-09
|source=http://www.science-and-fiction.org/FG/pics/dhc603.jpg
|author=Thorsten Renk
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month|2017 03]]
[[Category:De Havilland Canada DHC-6 Twin Otter cockpit screenshots]]
[[Category:Screenshots of scenery in the United States of America]]

File:DHC-6 in Alaska.jpg

2017-04-05T12:00:10Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=A DHC-6 Twin Otter is exploring the mountainous landscape of southern Alaska east of Palmer (PAAQ)}} 
{{de|1=Eine DHC-6 Twin Otter im Flug über die bergige Landschaft des südlichen Alaska östlich von Palmer (PAAQ)}}
|date=2017-03-09
|source=http://www.science-and-fiction.org/FG/pics/dhc603.jpg
|author=Thorsten Renk
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month]]
[[Category:De Havilland Canada DHC-6 Twin Otter cockpit screenshots]]
[[Category:Screenshots of scenery in the United States of America]]

File:DHC-6 in Alaska.jpg

2017-04-05T11:53:11Z

Dg-505:

File:Cap-10 in Basque Country.jpg

2017-04-05T11:52:29Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=A Mudry Cap-10 is doing some aerobatics in the Basque Country}} 
{{de|1=Eine Mudry Cap-10 beim Kunstflug über dem Baskenland}}
|date=2017-02-05
|source=http://i63.tinypic.com/29ncjk9.jpg
|author=xcvb
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshots of aerobatic aircraft]]
[[Category:Screenshots of scenery in Europe]]
[[Category:Screenshot of the month|2017 02]]

File:DHC-6 in Alaska.jpg

2017-04-05T11:49:28Z

Dg-505: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=A DHC-6 Twin Otter is exploring the mountainous landscape of southern Alaska east of Palmer (PAAQ)}}{{de|1=Eine DHC-6 Twin Otter im Flug über die bergige Landschaft des südlichen Alaska östlich von Palmer (PAAQ)}}
|date=2017-03-09
|source=http://www.science-and-fiction.org/FG/pics/dhc603.jpg
|author=Thorsten Renk
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month]]
[[Category:De Havilland Canada DHC-6 Twin Otter cockpit screenshots]]
[[Category:Screenshots of scenery in the United States of America]]

FlightGear Newsletter February 2017

2017-03-04T09:56:00Z

Dg-505: /* Screenshot of the Month */ nextmonth

{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter January 2017]].}}

{{Newsletter-header|February 2017}}
<div style="border-bottom: 3px double #BBB">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
{{Newsletter-cover-header|In the hangar}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>
== Development news ==
=== FlightGear v2017.1 released ===
The FlightGear development team is delighted to announce the v2017.1 "Bergen" release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include: Accurate buildings from OpenStreetMap, voice synthesis of tutorial instructions, improved rendering of Earth from orbit, and a more realistic blackout/redout system.

=== Bombable Add-on: Update 4.6 now available - Full Compatibility with FG 2016.x.x ===
The [[Bombable]] add-on--which converts FlightGear into full fledged combat flight simulator, with realistic weapons, dogfighting, bombing, and strafing--either with AI opponents or via multiplayer, has been updated to version 4.6.

The new version of Bombable brings full compatibility with FlightGear through 2016.4.4.

Download the Bombable add-on, or find out more, on the [[Bombable|Bombable wiki page]]

[[File:Bombable-Camel-vs-Camel.png|framed|center|The Bombable Add-On features aircraft from World War I through modern times]]

== In the hangar ==

=== JSBSim Sopwith Camel Updated to Ver. 2.0alpha ===
Flug's JSBSim Sopwith Camel has undergone major revisions and the 2.0alpha version of the aircraft has been released.

[http://forum.flightgear.org/viewtopic.php?f=4&t=19584&start=45#p305653 More information and download the JSBSim Camel here]

[[File:real-sopwith-camel-1917-vs-flightgear-2017.png|framed|center|Real Sopwith Camel 1917 vs FlightGear JSBSim Camel 2017]]

==== Major features of the new release: ====
* '''Greatly updated/refined flight dynamics model''', even more closely adhering to the historically reported behavior of the aircraft
* '''Crashes modeled''' - parts break, dust, explosions, etc.
[[File:JSBSim-camel-bad-crash.jpg|framed|right|JSBSim Camel: Bad Crash]]
* '''Completely new sound design''' - hear when you are rolling, landing gear makes contact, wind buffeting etc
* '''Ground interactions''' - tail drag, wheels, wingtip, etc dragging surface kicks up dust
* '''Water landings''' - you can successfully ditch in water, kicks up spray & other effects
* '''Friction effects and bumps''' - you can land or take off on almost any suitable land, but you will notice increased drag from e.g. tall grass, bumps, and you might break a landing gear if you're not careful. Use ''''n' key to nudge the aircraft''' if you get stuck in a hole or ditch.
* '''New Inspect Aircraft View''' - based on Walk View, this allows you to easily get various views near the aircraft

[http://www.youtube.com/watch?v=QOXPFoV-JTI View a video demo of an early version of some of these features.]

==== Things to try in your new JSBSim Camel: ====
* '''Crash landing'''
[[File:JSBSim-camel-ground-effects.jpg|300px|thumbnail|right|JSBSim Camel Ground Contact Effects]]
* '''Hard landing'''
* '''Over-g/overspeed'''
* '''Inverted flight'''
* '''Land in a random field''', try to take off again (use 'n' as needed for nudges, and '''menu Camel/Repair''' as needed--because you WILL need it).
* '''Water landing''' - try both a controlled ditch and hard landing
* '''Scrape a wing''' on takeoff or landing
* '''Nose over''' on takeoff or landing (menu Camel/Repair afterwards . . . )
* '''Take off, land and do touch-and-go landings''' while viewing from external view (Model View or Inspect Aircraft View)
* '''How fast can you do a level 360 degree turn''' left or right? Real Camel pilots could do it 8-10 seconds level flight to level flight.
* '''Spins and recovery''' - try powered stall and unpowered stall in level flight; pulling into a stall at 45, 60, and 90 degree bank angles, etc. How about a stall from inverted flight? Can you figure out how to enter a flat inverted spin from inverted flight--as reported by WWI Camel pilots?
* Take offs and landings in '''calm weather, headwind, crosswind, tailwind'''. Can you successfully take off and land in a strong crosswind, for example?
* Take offs and landings in calm weather, headwind, crosswind, tailwind. Can you successfully take off and land in a strong crosswind, for example?
* '''Loops, barrel rolls, split-s turns, wingovers, hammerheads,''' other typical acrobatic and fighter maneuvers. What happens if you pull the stick back moderately or hard at the top of a loop?
[[File:JSBSim-camel-nosing-over2.jpg|framed|left|JSBSIM Camel: Nosing Over]]
* Install the '''[http://wiki.flightgear.org/Bombable Bombable] add-on and dogfight''' other Camels, Spads, Fokkers, etc.
* Or '''dogfight via multiplayer''' with [http://wiki.flightgear.org/Bombable Bombable]

Note that the JSBSim version of the Camel included in the pack is the primary emphasis of this release. The JSBSim FDM and effects mentioned above are the point of the release. The aircraft model is identical to the FG Camel, so you won't see anything new there! And the release also includes a YASim version of the Camel that is Bombable compatible but doesn't include any other special effects or FDM development of the type outlined above.

In short, to see fly the *JSBSim Camel*. In the FG aircraft menu, look for *Sopwith Camel 1F.1 (JSBSim, Historically Accurate FDM & Weapons, Bombable-compatible, ver 2.0)*.

Version 2.0alpha is a pre-release and may be refined further (based on user feedback) before the final release. However, the release is fully functional and generally well tested.

[http://forum.flightgear.org/viewtopic.php?f=4&t=19584&start=45#p305653 More information and download the JSBSim Camel here]
[[File:JSBSim-camel-tumbling2.jpg|728x576px|framed|center|JSBSim Camel: Tumbling to a stop]]

== Scenery corner ==
== Community News ==
== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====
FlightGear's Screenshot of the Month February 2017 is ''Having some fun in the Basque Country'' by xcvb!
[[File:Cap-10 in Basque Country.jpg|900px|center|TITLE]]

If you want to participate in the screenshot contest of March 2017, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=31783 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=31783#p306280 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of March.

[[Category:FlightGear Newsletter|2017 02]]
[[Category:Changes after 2017.1]]
[[de:FlightGear Newsletter Februar 2017]]

FlightGear Newsletter February 2017

2017-03-04T08:39:09Z

Dg-505: /* Screenshot of the Month */

{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter January 2017]].}}

{{Newsletter-header|February 2017}}
<div style="border-bottom: 3px double #BBB">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
{{Newsletter-cover-header|In the hangar}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>
== Development news ==
=== FlightGear v2017.1 released ===
The FlightGear development team is delighted to announce the v2017.1 "Bergen" release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include: Accurate buildings from OpenStreetMap, voice synthesis of tutorial instructions, improved rendering of Earth from orbit, and a more realistic blackout/redout system.

=== Bombable Add-on: Update 4.6 now available - Full Compatibility with FG 2016.x.x ===
The [[Bombable]] add-on--which converts FlightGear into full fledged combat flight simulator, with realistic weapons, dogfighting, bombing, and strafing--either with AI opponents or via multiplayer, has been updated to version 4.6.

The new version of Bombable brings full compatibility with FlightGear through 2016.4.4.

Download the Bombable add-on, or find out more, on the [[Bombable|Bombable wiki page]]

[[File:Bombable-Camel-vs-Camel.png|framed|center|The Bombable Add-On features aircraft from World War I through modern times]]

== In the hangar ==

=== JSBSim Sopwith Camel Updated to Ver. 2.0alpha ===
Flug's JSBSim Sopwith Camel has undergone major revisions and the 2.0alpha version of the aircraft has been released.

[http://forum.flightgear.org/viewtopic.php?f=4&t=19584&start=45#p305653 More information and download the JSBSim Camel here]

[[File:real-sopwith-camel-1917-vs-flightgear-2017.png|framed|center|Real Sopwith Camel 1917 vs FlightGear JSBSim Camel 2017]]

==== Major features of the new release: ====
* '''Greatly updated/refined flight dynamics model''', even more closely adhering to the historically reported behavior of the aircraft
* '''Crashes modeled''' - parts break, dust, explosions, etc.
[[File:JSBSim-camel-bad-crash.jpg|framed|right|JSBSim Camel: Bad Crash]]
* '''Completely new sound design''' - hear when you are rolling, landing gear makes contact, wind buffeting etc
* '''Ground interactions''' - tail drag, wheels, wingtip, etc dragging surface kicks up dust
* '''Water landings''' - you can successfully ditch in water, kicks up spray & other effects
* '''Friction effects and bumps''' - you can land or take off on almost any suitable land, but you will notice increased drag from e.g. tall grass, bumps, and you might break a landing gear if you're not careful. Use ''''n' key to nudge the aircraft''' if you get stuck in a hole or ditch.
* '''New Inspect Aircraft View''' - based on Walk View, this allows you to easily get various views near the aircraft

[http://www.youtube.com/watch?v=QOXPFoV-JTI View a video demo of an early version of some of these features.]

==== Things to try in your new JSBSim Camel: ====
* '''Crash landing'''
[[File:JSBSim-camel-ground-effects.jpg|300px|thumbnail|right|JSBSim Camel Ground Contact Effects]]
* '''Hard landing'''
* '''Over-g/overspeed'''
* '''Inverted flight'''
* '''Land in a random field''', try to take off again (use 'n' as needed for nudges, and '''menu Camel/Repair''' as needed--because you WILL need it).
* '''Water landing''' - try both a controlled ditch and hard landing
* '''Scrape a wing''' on takeoff or landing
* '''Nose over''' on takeoff or landing (menu Camel/Repair afterwards . . . )
* '''Take off, land and do touch-and-go landings''' while viewing from external view (Model View or Inspect Aircraft View)
* '''How fast can you do a level 360 degree turn''' left or right? Real Camel pilots could do it 8-10 seconds level flight to level flight.
* '''Spins and recovery''' - try powered stall and unpowered stall in level flight; pulling into a stall at 45, 60, and 90 degree bank angles, etc. How about a stall from inverted flight? Can you figure out how to enter a flat inverted spin from inverted flight--as reported by WWI Camel pilots?
* Take offs and landings in '''calm weather, headwind, crosswind, tailwind'''. Can you successfully take off and land in a strong crosswind, for example?
* Take offs and landings in calm weather, headwind, crosswind, tailwind. Can you successfully take off and land in a strong crosswind, for example?
* '''Loops, barrel rolls, split-s turns, wingovers, hammerheads,''' other typical acrobatic and fighter maneuvers. What happens if you pull the stick back moderately or hard at the top of a loop?
[[File:JSBSim-camel-nosing-over2.jpg|framed|left|JSBSIM Camel: Nosing Over]]
* Install the '''[http://wiki.flightgear.org/Bombable Bombable] add-on and dogfight''' other Camels, Spads, Fokkers, etc.
* Or '''dogfight via multiplayer''' with [http://wiki.flightgear.org/Bombable Bombable]

Note that the JSBSim version of the Camel included in the pack is the primary emphasis of this release. The JSBSim FDM and effects mentioned above are the point of the release. The aircraft model is identical to the FG Camel, so you won't see anything new there! And the release also includes a YASim version of the Camel that is Bombable compatible but doesn't include any other special effects or FDM development of the type outlined above.

In short, to see fly the *JSBSim Camel*. In the FG aircraft menu, look for *Sopwith Camel 1F.1 (JSBSim, Historically Accurate FDM & Weapons, Bombable-compatible, ver 2.0)*.

Version 2.0alpha is a pre-release and may be refined further (based on user feedback) before the final release. However, the release is fully functional and generally well tested.

[http://forum.flightgear.org/viewtopic.php?f=4&t=19584&start=45#p305653 More information and download the JSBSim Camel here]
[[File:JSBSim-camel-tumbling2.jpg|728x576px|framed|center|JSBSim Camel: Tumbling to a stop]]

== Scenery corner ==
== Community News ==
== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====
FlightGear's Screenshot of the Month February 2017 is ''Having some fun in the Basque Country'' by xcvb!
[[File:Cap-10 in Basque Country.jpg|900px|center|TITLE]]

[[Category:FlightGear Newsletter|2017 02]]
[[Category:Changes after 2017.1]]
[[de:FlightGear Newsletter Februar 2017]]

File:Cap-10 in Basque Country.jpg

2017-03-04T08:38:59Z

Dg-505:

File:Cap-10 in Basque Country.jpg

2017-03-04T08:34:16Z

Dg-505: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=A Mudry Cap-10 is doing some aerobatics in the Basque Country}}{{de|1=Eine Mudry Cap-10 beim Kunstflug über dem Baskenland}}
|date=2017-02-05
|source=http://i63.tinypic.com/29ncjk9.jpg
|author=xcvb
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshots of aerobatic aircraft]]
[[Category:Screenshots of scenery in Europe]]
[[Category:Screenshot of the month]]

Checklists

2017-02-14T19:12:24Z

Dg-505: Redirected page to Aircraft Checklists

#redirect[[Aircraft Checklists]]

File:ASK-21 over Grand Canon.jpg

2017-02-02T20:54:00Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=A Schleicher ASK 21 is soaring above the Grand Canon.}} {{de|1=Eine Schleicher ASK 21 im Segelflug über dem Grand Canon.}}
|date=2017-01-02
|source=http://i.imgur.com/v1NRylX.jpg
|author=D-ECHO
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month|2017 01]]
[[Category:Screenshots of sailplanes]]
[[Category:Schleicher]]
[[Category:Screenshots of scenery in the United States of America]]

FlightGear Newsletter January 2017

2017-02-02T20:52:03Z

Dg-505: /* Screenshot of the Month */

File:ASK-21 over Grand Canon.jpg

2017-02-02T20:50:46Z

Dg-505: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=A Schleicher ASK 21 is soaring above the Grand Canon.}}{{de|1=Eine Schleicher ASK 21 im Segelflug über dem Grand Canon.}}
|date=2017-01-02
|source=http://i.imgur.com/v1NRylX.jpg
|author=D-ECHO
|permission=
|other versions=
}}

=={{int:license-header}}==
{{cc-by-sa-4.0}}

[[Category:Screenshot of the month]]
[[Category:Screenshots of sailplanes]]
[[Category:Schleicher]]
[[Category:Screenshots of scenery in the United States of America]]

FlightGear Newsletter January 2017

2017-01-31T18:19:44Z

Dg-505: Screenshot of the year

De/FlightGear Newsletter Dezember 2016

2017-01-08T19:32:10Z

Dg-505: Translate

{{draft|Dieser Newsletter|Sobald die englische Version fertig ist, kann sie hier hinein übersetzt werden. Wenn Du Texte verfassen, Videos aufnehmen oder oder über etwas berichten willst, was die FlightGear Community interessieren könnte, ist dies immer im [[Next newsletter|nächsten englischen Newsletter]] willkommen. Der neuste fertige Newsletter in deutsch ist der [[De/FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]]}}
{{De/Newsletter-header|2016-12}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Neuigkeiten in der Entwicklung}} 
[[#Bremsschirm-Effekt in ALS|Bremsschirm-Effekt in ALS]] 
[[#ALS Model Shader für glänzende Oberflächen|ALS Model Shader für glänzende Oberflächen]] 
{{Newsletter-cover-header|Im Hangar}} 
[[#Aérospatiale/Westland Gazelle|Aérospatiale/Westland Gazelle]] 
[[#Bobcat Volanti|Bobcat Volanti]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Szenerie-Abteilung}} 
{{Newsletter-cover-header|Community News}} 
[[#Artikel auf FlightSim.com|Artikel auf FlightSim.com]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Mitarbeiten}} 
[[#Übersetzer gesucht|Übersetzer gesucht]] 
[[#FlightGear Logos|FlightGear Logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot des Monats|Screenshot des Monats]]
|}</div>

== Neuigkeiten in der Entwicklung ==
=== Bremsschirm-Effekt in ALS ===
Das Spektrum der [[ALS]]-Effekte wurde erweitert um eine Animation für Bremsfallschirme. Der Effekt simuliert die Verformung eines runden Bremsschirms unter Belastung. Der Schirm ändert Form und Verhalten in Abhängigkeit des Widerstands, den er verursacht, und er kann sogar plausibel aussehende Bewegungen ausführen, wenn er abgeworfen wird.

[[File:Chute seq01.jpg|400px|Animation zum Abwerfen des Schirms]] [[File:Chute seq03.jpg|400px|Animation zum Abwerfen des Schirms]]

[[ALS technical notes#Chute animation effect|Erfahre mehr] auf der entsprechenden Wiki-Seite.

=== ALS Model Shader für glänzende Oberflächen ===
Der Model Shader hat einige Schwierigkeiten damit, bei Verwendung von Umgebungs-Reflexionen Farben zu erhalten. Genauer gesagt kann ein weißer glänzender Rumpf grau erscheinen, wenn Reflexionen hinzugefügt werden. Die neue Option "grain merge" ermöglicht es, die Farben der Oberfläche deutlich besser zu erhalten (rechts).

[[File:Reflect model default.jpg|400px|Verwischung von Farben in einer Reflexion]]
[[File:Reflect grain merge.jpg|400px|"Grain Merge"-Effekt in einer Reflexion]]

Des Weiteren wurde der Reflexions-Effekt um eine konfigurierbare Fresnel-Verbesserung für kleine Winkel erweitert.

[[ALS technical notes#Glossy surfaces|Erfahre mehr] auf der entsprechenden Wiki-Seite.

== Im Hangar ==
=== Aérospatiale/Westland Gazelle ===
Das FGUK team ist hocherfreut, die erste Veröffentlichung ihrer Gazelle für FlightGear ankündigen zu können. Enthalten ist nicht nur ein Modell der Westland, sondern auch die Aerospitale, deren Unterschiede modelliert wurden. Dies ist ein echter Genuss für jeden, der an diesen fantastischen Helikoptern interessiert ist.

[http://www.fguk.eu/index.php/hangar/download/13-rotary-wing/252-aerospatiale-westland-gazelle DOWNLOAD hier: FGUK Download Hangar - Gazelle]

'''Preview video:'''

https://youtu.be/aog0ZqMbDlc

[[File:Gazellev1.jpg|thumb|Flight Gear Gazelle V1.0]]

'''Release notes:

'''V1.0'''
* Ausführliche Überarbeitung des FDMs um ein realistischeres Flugverhalten der Gazelle zu erreichen.
* Texturen im Cockpit überarbeitet
* Beide Versionen haben realistische Fluginstrumente. Die Westland basiert auf der Version der British Armend Forces.
* Lichtschalter sitzen nun auf dem Main Panel. Der Schalter für den Landescheinwerfer ist auf dem Collective-Hebel platziert.
* Collective, Steuerknüppel, Pedale, Rotorbremse und Leistungshebel sind alle animiert.
* Manueller Startup bzw. Shutdown möglich (siehe Hilfemenü).
* Beide unterstützen Multiplayer-Passagier, sodass Du einen Freund mit auf den Flug nehmen kannst.
* Alle Kabinentüren sind animiert (Klick zum öffnen/schließen).
* Update für die Sounds.
* Verschiedene Konfigurationen möglich. Westland hat eine militärische Ausstattung, die Aerospitale hat Zwiebeln.
17 lakierungen sind für beide Versionen verfügbar.

Im "Gazelle"-Menü gibt es ein Browser-basiertes Hilfemenü.

Mehr Fotos auf der [https://www.facebook.com/FlightGearUK/ Flight Gear UK Facebookseite]

=== Bobcat Volanti ===
[[Bobcat Volanti]] wurde veröffentlicht. Dies ist ein fiktionaler Helikopter basierend auf dem '''Bobcat''' aus GTA.

[[File:Bobcat Volanti.jpg|400px|Bobcat Volanti]]

== Szenerie-Abteilung ==

== Community News ==
=== Artikel auf FlightSim.com ===
{{usr|Thorsten}} veröffentlichte einen [http://www.flightsim.com/vbfs/content.php?16990-FlightGear-s-Atmospheric-Light-Scattering-Rendering-Framework sehr interesannten Artikel] auf [http://www.flightsim.com FlightSim.com], wo er einige Features von [[Atmospheric light scattering]] beschreibt: Zum Beispiel, Dunst, Sonnenphänomene, Nordlichter und einige Effekte für Flugzeuge. Dieser Artikel zeigt auch einige wunderschöne Screenshots die bisher sonst nirgendwo zu sehen sind.

== Mitarbeiten ==
=== Übersetzer gesucht ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, start at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help: Traduzir|Help: Traduzir]].
|}

=== FlightGear Logos ===
Solltest Du graphische Elemente für deine FlightGear Website (Hangar, YouTube-Kanal, o.ä.) suchen, wirf doch einen Blick auf die [[FlightGear logos|FlightGear Logos]]. Und falls Du eine künstlerische Ader hast, fühl Dich frei, eigene Designs zu erstellen und hier hochzuladen.

=== Screenshots ===
Das FlightGear-Projekt benötigt ständig Screenshots, welche neue Features seit dem letzten Release zeigen. Diese sollten von hoher Qualität sein, besonders von inhaltlicher und technischer Seite. Dafür wird empfohlen, die besten Graphikfilter zu nutzen ([[:de:Antialiasing|Antialiasing]], Texturenschärfung, etc.). Näheres unter [[:de:Howto:Gute Screenshots machen|Howto:Gute Screenshots machen]].

Kandidaten für den besten Screenshot im Januar 2017 können in [https://forum.flightgear.org/viewtopic.php?f=19&t=31368 diesem] Forum Thread eingereicht werden. Beachte auch die Teilnahmeregeln im [https://forum.flightgear.org/viewtopic.php?f=19&t=31368#p302478 ersten Post]. Aus Gründen der Zweckmäßigkeit werden am 25. Januar oder wenn 15 Kandidaten eingereicht wurden, alle Einträge in einem separaten Thread zusammengefasst, wo auch das Voting stattfinden wird. Selbst wenn Du keinen Screenshot beiträgst, bist Du natürlich eingeladen, dabei auch deine Stimme(n) mit abzugeben. Am Ende des Monats, nach Abschluss des Votings, wird der beste Screenshot im FlightGear Newsletter Februar 2017 präsentiert.

==== Screenshot des Monats ====
FlightGear's Screenshot des Monats Dezember 2016 ist ''Morning patrol over Koblenz, November 1944'' von {{usr|Dg-505|Jonathan S.}}
[[File:P-51D over Koblenz.jpg|900px|center|Morning patrol over Koblenz, November 1944]]

[[Category:De/FlightGear Newsletter|2016 12]]
[[Category:Changes after 2016.4]]

[[en:FlightGear Newsletter December 2016]]

FlightGear Newsletter December 2016

2017-01-08T18:51:04Z

Dg-505: /* Screenshot of the Month */ SOTM for January 17

{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter November 2016]].}}

{{Newsletter-header|December 2016}}
<div style="border-bottom: 3px double #BBB">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
[[#ALS chute animation effect|ALS chute animation effect]] 
[[#ALS model shader options for glossy surfaces|ALS model shader options for glossy surfaces]] 
{{Newsletter-cover-header|In the hangar}} 
[[#Aérospatiale / Westland Gazelle|Aérospatiale / Westland Gazelle]] 
[[#Bobcat Volanti|Bobcat Volanti]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
[[#Article on FlightSim.com|Article on FlightSim.com]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>

== Development news ==
=== ALS chute animation effect ===
The ALS effect suite has been expanded by an animation effect for parachutes. The effect simulates the deformation of a round parachute under stresses. The chute changes form and behavior depending on how much drag it supplies, and can even be made to go through a plausible series of motions when jettisoned.

[[File:Chute seq01.jpg|400px|Drag chute separation sequence 1]] [[File:Chute seq03.jpg|400px|Drag chute separation sequence 2]]

[[ALS technical notes#Chute animation effect|Read more]] on the ALS effect wiki page.

=== ALS model shader options for glossy surfaces ===
The model shader has some issues with preserving the colors when using environment reflections. In particular, a white glossy fuselage might appear grey when adding reflections (left). Using the new 'grain merge' option, the color can be preserved much better (right).

[[File:Reflect model default.jpg|400px|Effect of color mixing in a reflection]]
[[File:Reflect grain merge.jpg|400px|Effect of grain merge in reflection]]

In addition, the reflection has been augmented by a small-angle configurable Fresnel enhancement.

[[ALS technical notes#Glossy surfaces|Read more]] on the ALS effect wiki page.

== In the hangar ==
=== Aérospatiale/Westland Gazelle ===
The FGUK Development team are absolutely ecstatic to be able to announce the release of our Gazelle for FlightGear. Encompassing not only the Westland but also the Aerosptiale models with the differences modelled between them this is a real delight for anyone with an interest in these fantastic helicopters.

[http://www.fguk.eu/index.php/hangar/download/13-rotary-wing/252-aerospatiale-westland-gazelle DOWNLOAD HERE: FGUK Download Hangar - Gazelle]

'''Preview video:-'''

https://youtu.be/aog0ZqMbDlc

[[File:Gazellev1.jpg|thumb|Flight Gear Gazelle V1.0]]

''''RELEASE NOTES:-''''

'''V1.0'''

*Extensive FDM rework to provide a more realistic Gazelle flight performance.
*Cockpit textures reworked.
*Both versions have realistic flight instruments. Westland version is based on the British Armed forces version.
*Light switches now located on the Main panel. landing light switch is located on the Collective.
*Collective, Cyclic, Pedals, Rotor brake and Engine power lever all animated.
*Manual start / shut down possible ( see help file ).
*Both support Multiplayer passenger modes so you can take your friends for a flight.
*All cabin doors are animated ( Click to open / close )
*Updated sound pack.
*Configuration options. Westland has the Military kit option, the Aérospatiale has Onions ( try the onions ! )

17 Liveries available between both versions

Browser based Help file available in the "Gazelle" menu option in sim.

More photos on the [https://www.facebook.com/FlightGearUK/ Flight Gear UK Facebook Page]

=== Bobcat Volanti ===
[[Bobcat Volanti]] has been released. It is a fictional helicopter and body is based off GTA Vice City '''Bobcat'''.

[[File:Bobcat Volanti.jpg|400px|Bobcat Volanti]]

== Scenery corner ==

== Community news ==
=== Article on FlightSim.com ===
{{usr|Thorsten}} published a very [http://www.flightsim.com/vbfs/content.php?16990-FlightGear-s-Atmospheric-Light-Scattering-Rendering-Framework interesting article] on [http://www.flightsim.com FlightSim.com] where he describes some features of [[Atmospheric light scattering]] like among others haze, sun phenomena, sunrise, aurora borealis and some aircraft effects. This article also shows some very beautiful screenshots which have been never published anywhere else.

== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====
FlightGear's Screenshot of the Month December 2016 is ''Morning patrol over Coblenz, November 1944'' by {{usr|Dg-505|Jonathan S.}}
[[File:P-51D over Koblenz.jpg|900px|center|Morning patrol over Coblenz, November 1944]]

If you want to participate in the screenshot contest of January 2017, you can submit your candidate to [https://forum.flightgear.org/viewtopic.php?f=19&t=31368 this] forum topic. Be sure to see the [https://forum.flightgear.org/viewtopic.php?f=19&t=31368#p302478 first post] for participation rules. For purposes of convenience and organization, after all the entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there. Once the voting has finished, the best screenshot will be presented in the Newsletter edition of January 2017.

[[Category:FlightGear Newsletter|2016 12]]
[[Category:Changes after 2016.4]]

[[de:FlightGear Newsletter Dezember 2016]]

System dependent instruments

2017-01-02T12:17:06Z

Dg-505: /* Electrical */

The tables below shows the properties that the different {{flightgear source|path=src/Instrumentation|text=standard instrument implementations}} are dependent on.

== Electrical ==

{| class="wikitable"
! Source file !! Instrument !! Property!! Comment
|-
|heading_indicator_dg || Directional Gyro (DG) || /systems/electrical/outputs/DG || drives gyro, > 0.02 to work
|-
| dme || Distance measuring equipment (DME) || /systems/electrical/outputs/dme || any non zero works
|-
| kr_87 || King KR 87 Digital ADF || /systems/electrical/outputs/adf || > 1 to work
|-
| turn_indicator || Turn Indicator || /systems/electrical/outputs/turn-coordinator[n]<ref>https://sourceforge.net/p/flightgear/flightgear/ci/2b9de5ceaa2e59b0a042ac1eea77e97ef2b6b5d3/</ref> || drives gyro, > 0.24 to work
|-
| mrg || master reference gyro || /systems/electrical/outputs/MRG || drives gyro, > 0.5 to work
|-
| gps || GPS || /systems/electrical/outputs/gps || any non zero works
|-
| kt_70 || Transponder || /systems/electrical/outputs/transponder || >1 to work
|-
| adf || ADF ||/systems/electrical/outputs/adf || needs to be >8 to work
|-
| mk_viii || Honeywell MK VIII EGPWS || /systems/electrical/outputs/mk[n] || >=15 to work
|-
| heading_indicator_fg || Flux-gate compass || /systems/electrical/outputs/DG || drives gyro, > 0.02 to work
|-
| transponder || Transponder || /systems/electrical/outputs/transponder || needs to be >8 to work
|-
| tacan || TACAN || systems/electrical/outputs/tacan || any non zero
|-
| navradio || Navigation radios (eg. kx165) || /systems/electrical/outputs/nav[n] || > 1 to work
|-
| marker_beacon || Marker beacon indicator ||/systems/electrical/outputs/nav[0] || > 1 to work
|}

{{Appendix}}

== Vacuum ==
{| class="wikitable"
! Source file !! Instrument !! Property !! Comment
|-
| heading_indicator || Heading indicator || /systems/vacuum/suction-inhg || drives gyro > 0.1 to work
|-
| attitude_indicator || Attitude indicator || /systems/vacuum/suction-inhg" || drives gyro > 0.1 to work
|}

== Static ==
{| class="wikitable"
! Source file !! Instrument !! Property !! Comment
|-
| altimeter || Altimeter || /systems/static/pressure-inhg || tau default 0.1
|-
| vertical_speed_indicator || VSI || /systems/static/pressure-inhg ||
|-
| airspeed_indicator || Airspeed indicator || /systems/static/pressure-inhg ||
|}

== Pitot ==
{| class="wikitable"
! Source file !! Instrument !! Property !! Comment
|-
| airspeed_indicator || Airspeed indicator || /systems/pitot/total-pressure-inhg ||
|}

[[Category:Core development]]

FlightGear Newsletter December 2016

2017-01-01T15:21:30Z

Dg-505: /* Screenshot of the Month */

{{draft|newsletter|Please feel free to add content that you think will be of interest to the FlightGear community. You can read the latest newsletter at [[FlightGear Newsletter November 2016]].}}

{{Newsletter-header|December 2016}}
<div style="border-bottom: 3px double #BBB">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Development news}} 
[[#ALS chute animation effect|ALS chute animation effect]] 
[[#ALS model shader options for glossy surfaces|ALS model shader options for glossy surfaces]] 
{{Newsletter-cover-header|In the hangar}} 
[[#Aérospatiale / Westland Gazelle|Aérospatiale / Westland Gazelle]] 
[[#Bobcat Volanti|Bobcat Volanti]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery Corner}} 
{{Newsletter-cover-header|Community News}} 
[[#Article on FlightSim.com|Article on FlightSim.com]] 
| valign="top" width="33%" |
{{Newsletter-cover-header|Contributing}} 
[[#Translators required|Translators required]] 
[[#FlightGear logos|FlightGear logos]] 
[[#Screenshots|Screenshots]] 
[[#Screenshot of the Month|Screenshot of the Month]]
|}</div>

== Development news ==

=== ALS chute animation effect ===

The ALS effect suite has been expanded by an animation effect for parachutes. The effect simulates the deformation of a round parachute under stresses. The chute changes form and behavior dependent on how much drag it supplies, and can even be made to go through a plausible series of motions when jettisoned.

[[File:Chute seq01.jpg|400px|Drag chute separation sequence 1]] [[File:Chute seq03.jpg|400px|Drag chute separation sequence 2]]

[[ ALS_technical_notes#Chute_animation_effect | Read more...]] on the ALS effect wiki page.

=== ALS model shader options for glossy surfaces ===

The model shader has some issues with preserving the colors when using environment reflections. In particular, a white glossy fuselage might appear grey when adding reflections (left). Using the new 'grain merge' option, the color can be preserved much better (right).

[[File:Reflect model default.jpg|400px|Effect of color mixing in a reflection]]
[[File:Reflect grain merge.jpg|400px|Effect of grain merge in reflection]]

In addition, the reflection has been augmented by a small-angle configurable Fresnel enhancement.

[[ ALS_technical_notes#Glossy_surfaces | Read more...]] on the ALS effect wiki page.

== In the hangar ==

=== Aérospatiale / Westland Gazelle ===
The FGUK Development team are absolutely ecstatic to be able to announce the release of our Gazelle for FlightGear. Encompassing not only the Westland but also the Aerosptiale models with the differences modelled between them this is a real delight for anyone with an interest in these fantastic helicopters.

[http://www.fguk.eu/index.php/hangar/download/13-rotary-wing/252-aerospatiale-westland-gazelle DOWNLOAD HERE: FGUK Download Hangar - Gazelle]

'''Preview video:-'''

https://youtu.be/aog0ZqMbDlc

[[File:Gazellev1.jpg|thumb|Flight Gear Gazelle V1.0]]

''''RELEASE NOTES:-''''

'''V1.0'''

*Extensive FDM rework to provide a more realistic Gazelle flight performance.
*Cockpit textures reworked.
*Both versions have realistic flight instruments. Westland version is based on the British Armed forces version.
*Light switches now located on the Main panel. landing light switch is located on the Collective.
*Collective, Cyclic, Pedals, Rotor brake and Engine power lever all animated.
*Manual start / shut down possible ( see help file ).
*Both support Multiplayer passenger modes so you can take your friends for a flight.
*All cabin doors are animated ( Click to open / close )
*Updated sound pack.
*Configuration options. Westland has the Military kit option, the Aérospatiale has Onions ( try the onions ! )

17 Liveries available between both versions

Browser based Help file available in the "Gazelle" menu option in sim.

More photos on the [https://www.facebook.com/FlightGearUK/ Flight Gear UK Facebook Page]

=== Bobcat Volanti ===
[[Bobcat Volanti]] has been released. It is a fictional helicopter and body is based off GTA Vice City '''Bobcat'''.

[[File:Bobcat Volanti.jpg|400px|Bobcat Volanti]]

== Scenery corner ==

== Community news ==
=== Article on FlightSim.com ===
{{usr|Thorsten}} published a very [http://www.flightsim.com/vbfs/content.php?16990-FlightGear-s-Atmospheric-Light-Scattering-Rendering-Framework interesting article] on [http://www.flightsim.com FlightSim.com] where he describes some features of [[Atmospheric light scattering]] like among others haze, sun phenomena, sunrise, aurora borealis and some aircraft effects. This article also shows some very beautiful screenshots which have been never published anywhere else.

== Contributing ==
=== Translators required ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====
FlightGear's Screenshot of the Month December 2016 is ''Morning patrol over Coblenz, November 1944'' by {{usr|Dg-505|Jonathan S.}}
[[File:P-51D over Koblenz.jpg|900px|center|Morning patrol over Coblenz, November 1944]]

 

[[Category:FlightGear Newsletter|2016 12]]
[[Category:Changes after 2016.4]]

[[de:FlightGear Newsletter Dezember 2016]]

File:P-51D over Koblenz.jpg

2017-01-01T15:20:35Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=A North American P-51D Mustang is flying over Koblenz with the river Mosel in background}} 
{{de|1=Eine North American P51D Mustang im Flug über Koblenz mit der Mosel im Hintergrund}}
|date=2016-11-19
|source={{own}}
|author=[[User:Dg-505|Jonathan S. (Dg-505)]]
|permission=
|other versions=
}}

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

[[Category:Screenshot of the month|2016-12]]
[[Category:North American P-51 Mustang screenshots]]
[[Category:Screenshots of scenery in Europe]]
[[Category:Screenshots of weather]]

File:P-51D over Koblenz.jpg

2017-01-01T15:18:17Z

Dg-505: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=A North American P-51D Mustang is flying over Koblenz with the river Mosel in background}}{{de|1=Eine North American P51D Mustang im Flug über Koblenz mit der Mosel im Hintergrund}}
|date=2016-11-19
|source={{own}}
|author=[[User:Dg-505|Jonathan S. (Dg-505)]]
|permission=
|other versions=
}}

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

[[Category:Screenshot of the month]]
[[Category:North American P-51 Mustang screenshots]]
[[Category:Screenshots of scenery in Europe]]
[[Category:Screenshots of weather]]

File:Twin Otter electrical system scheme.jpg

2016-12-06T19:32:19Z

Dg-505:

=={{int:filedesc}}==
{{Information
|description={{en|1=Schematic represetntation of the electrical system of the DHC-6 Twin Otter (no warranty of correctness and/or completeness!) Update Dec 6, 2016: Please note that this chart isn't 100% correct. E.g. the "DC Master" is connected only to the Left 28V DC Bus, not to the right. Or that the battery is connected to the Main Battery Bus even if the External/Battery selector is switched off. Maybe I'll correct these errors someday, but please don't hesitate to do it if you want.}} {{de|1=Schematische Darstellung des elektrischen Systems in der DHC-6 Twin Otter (ohne Garantie auf Korrektheit und/oder Vollständigkeit!)}}
|date=2016-07-15
|source={{own}}
|author=[[User:Dg-505|Jonathan S. (Dg-505)]]
|permission=
|other versions=
}}

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

[[Category:Diagrams]]

De Havilland Canada DHC-6 Twin Otter

2016-12-06T19:29:46Z

Dg-505: /* Electrical system */ small note about some mistakes in the diagram

{{lowercase title}}{{:{{PAGENAME}}/info}}
The '''de Havilland Canada DHC-6 Twin Otter''', sometimes affectionately called the '''''Twotter''''', is a 20-passenger STOL (Short Takeoff and Landing) utility aircraft. It has often been called the most successful aircraft program in Canada's history. The Twin Otter is a high-wing twin-engine turboprop aircraft with a non-retractable tricycle gear, a non-pressurised cabin and two constant-speed props. In FlightGear, there are three versions available: Wheels, Floats (amphibious) and skis.

== About the original ==
The DHC-6 Twin Otter is the further development version of the [[DHC-3]] Otter of the same manufacturer. The development of the Twin Otter began in 1964, it's first flight was on May 20, 1965<ref>{{wikipedia|De Havilland Canada DHC-6 Twin Otter#Design and development}}</ref>. To keep the STOL abilities of the Otter, the DHC-6 got two powerful {{wikipedia|Pratt & Whitney Canada PT6}} turboprop engines with 410 kW produced by each turbine in the first version, the DHC-6-100.

In 1968, the Twin Otter was developed to a new version, the -200 series, which had improved STOL performance.

One year later, in 1969, the DHC-6-300 series was introduced, with more powerful engines, the PT6A-27 with 460 kW. Until today, the -300 Series is with 614 built aircraft the most successful variant of the Twin Otter. 1988 the production of the DHC-6-300 ended.

After 18 years of not-producing the Twin Otter Viking Air acquired the production rights from Bombadier Aerospace, and started producing a new series, the DHC-6-400, whose first flight was on October 01, 2008. The DHC-6-400 is equipped with modern state-of-the-art avionics and even more powerful PTA6-34 engines also from Pratt and Whitney. Until summer 2014, there were built 55 aircraft of the -400 series.

The aircraft's powerful engines, it's STOL abilities, and it's spacious cabin make the DHC-6 a popular aircraft for skydiving and well-suited as a bush plane for inacessible and remote terrain in many developing countries.

The FlightGear version is the DHC-6-300 Series.

== Handling the aircraft ==
=== Preflight inspection ===
To make it as real as possible it is highly recommended to use the walker for the preflight inspection
* Nose:
** Remove the covers of both pitot tubes. Otherwise the airspeed indicator won't show anything. (The pitot tubes are approximately at eye level in front of the left and right cockpit doors)
** Check the nose gear (wheel, damper, taxi lamp) for damage and tire pressure
* Left wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the left tie-down
** Check the wing, landing light, aileron and flaps for damage
* Left main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Tail:
** Remove the rear tie-down
** Check the empennage for damage
* Right main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Right wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the right tiedown.
** Check the wing, landing light, aileron and flaps for damage

=== Engine startup process ===
[[File:DHC-6 Twin Otter center panel.jpg|thumb|400px|The center panel of the Twin Otter with engine instruments and radio stack]]
[[File:DHC-6 Twin Otter Overhead Panel.jpg|thumb|400px|The overhead panel of the Twin Otter]]
The Twin Otter is a quite complex aircraft, so starting up the engines isn't something that can be done in two or three steps.
# Ensure that the parking brake is set, the throttle levers are in idle position, propeller levers are on feather position and fuel condition levers are in cutoff position
# Switch on the battery master and select BATTERY as power source (Captain's overhead panel)
# Switch on the cabin lights and the instrument lighting
# Check that the voltage is above 18 V; normally it's around 24 V (above the radio sack)
# Make sure that there is enough fuel in the tanks for the flight you've planned
# Switch on the "FASTEN SEATBELT" and the "NO SMOKING" sign
# Switch on the beacon (center overhead panel)
# If you do not start up on asphalt, you must switch on the intake deflectors. Otherwise the engines can get damaged
# Engage both boost pumps (at the bottom of the center panel, below the engine instruments)
# If the outside temperature is below 0°C you must switch on the Pitot Heat and the Prop De-ice
# Switch the IND selector to BAT (above the radio stack)
# Check that no one's about to walk into the left propeller
# Engage the stater switch left and watch GG RPM rising (lowest engine instrument on the center panel)
# When GG RPM exceeds 12 % push the left condition lever full forward to supply the engine with fuel
# When the PROP RPM rises stable repeat the steps 12 - 14 for the right engine
# When also the right propeller increases it's RPM stable you can switch off the starter
# Push both propeller levers full forward
# Switch on the navigation lights (POSN LT)
# Switch on both generators
# Select R GEN on the IND selector
# Switch on the window heating (First officers overhead panel)
# Compare the indication of the heading indicator with the magnetic compass: If they don't coincide you have to synchronize them by adjusting the heading offset of the heading indicator
# Set the radios to the required frequencies and the altimeter to QNH/airport elevation

{{note|The startup procedure described above is slightly simplified. When following the in-sim checklists you have to execute 4 checklists with over 50 items.}}

=== Take off ===
* Flaps 10-20° depending on runway length
* Landing lights on
* Release the parking brake
* Engage Autofeather to automatically feather the prop if an engine fails
* Give full throttle. Some engine limit warnings will appear, but for a short time you may exceed the limits.
* Rotate at aprox. 80-95 kts

=== Climb ===
* Reduce power to fall below the engine limits
* Flaps up
* Landing lights off
* Airspeed around 110-120 kts
* Intake deflectors and Autofeather off

=== Cruise ===
* Airspeed 150-165 kts
* If outside temperature falls below 0°C switch on the Pitot Heat and the Prop De-ice
* Engine instruments within limits
* Keep an eye on the fuel quantity

=== Landing ===
* Set Flaps step by step
* Airspeed below 108 kts when Flaps extended
* Landing lights on
* Condition and propeller levers full forward
* If not landing on asphalt, activate the intake deflector
* Verify that the parking brake is off
* Touchdown with 60-70 kts
* After touchdown apply reverse thrust

=== Airspeeds ===

{| class="wikitable"
! Airspeed !! IAS
|-
| Stall speed, landing config (VS0) || 58 kts
|-
| Stall speed, cruise config (VS1) || 80 kts
|-
| Rotation speed (VR) || 80-95 kts
|-
| Maximum flap extended speed (VFE) || 108 kts
|-
| Cruise speed (VC) || 150-165 kts
|-
| Maneuvering speed (VA) || 130 kts
|-
| Never exceed speed (VNE) || 170 kts
|}

== Systems overview<ref>[http://www.cram.com/flashcards/twin-otter-dhc6-300-1980260 Twin Otter flashcards on cram.com]</ref><ref>[http://www.aerosoft2.de/downloads/twotter/Manual-Twin-Otter-Extended-Vol2-Systems.pdf Systems manual of Aerosoft's Twin Otter Extended]</ref> ==
The Twin Otter is equipped with several [[Aircraft systems|systems]] which operate the aircraft's components:
* Electrical: Operates i. a. hydraulic pump, boost pumps, engine gauges, turn coordinator, lighting, auto-feather
* Fuel: Supplies engines with fuel from two fuel tanks
* Hydraulic: Operates flaps, nose wheel steering, and wheel brakes
* [[FGproperties/Systems/Pitot|Pitot]]: Supplies airspeed indicators with dynamic pressure
* Pneumatic/Bleed Air: Operates heating and de-icing system and intake deflectors
* [[FGproperties/Systems/static|Static]]: Supplies airspeed indicators, altimeters and vertical speed indicators with static pressure
* [[Aircraft systems#Vacuum|Vacuum]]: Drives gyros for artifical horizon and directional gyro/heading indicator

Please note that as of July 2016 not all of these systems are implemented!

=== Electrical system ===
[[File:Twin Otter electrical system scheme.jpg|thumb|400px|The electrical system of the Twin Otter in a schematic representation]]
The electrical system is fed by an 40 ampere-hour battery and two engine-driven generators (which operate as starter-motors when starting the engine). It is primarily a 28 volt, direct current (DC) system, but some components need alternating current (AC) to work.

There exist seven buses which provide electrical power to several components:
# Left 28V DC bus: Is driven by left engine's generator. It feeds the DC voltmeter, hydraulic pump, prop auto-feather system, fire detection system, primary boost pumps (forward and rear), "R GEN FAIL" caution light
# Right 28V DC bus: Is driven by right engine's generator. It feeds the propeller overspeed governor, crossfeed fuel valve, secondary boost pumps (forward and rear), "L GEN FAIL" caution light
# Aux battery bus: Uses a auxiliary 3.6 ampere-hour battery to support the starter motors when starting the engines.
# Main battery bus: Is controlled by the Master Battery switch. When switched off, only the interior lights are provided with power. When MASTER is selected, it connects the electrical system to generators or battery or external power, depending on the EXTERNAL/BATTERY selector switch position.
# Battery/External Power bus: Is controlled by the EXTERNAL/BATTERY selector switch. When EXTERNAL is selected, it isolates the battery and connects the external power unit to the left and right bus. BATTERY will connect the battery to the left and right bus when generators are not running or the generator voltage is lower than the battery voltage. If the generator voltage is highter than the battery voltage it connects the left and right bus to the respective generator. When swithced off, the whole electrical system gets disconnected.
# 26V AC bus: Torque presure, fuel flow, and oil pressure gauges,
# 115V AC bus: Fuel quantity gauges, vacuum pumps for gyros (artifical horizon and directional gyro

The two AC buses are fed from one of the two static inverters. The No.1 inverter receives power from the Left 28V DC bus (and hence from the left generator), and the No.2 inverter receives power from the right 28V DC bus (and hence from the right generator). The inverters are selected alternatively by the inverter switch located on the overhead panel.

{{caution|Please note that the above chart isn't 100% correct. E.g. the "DC Master" is connected only to the Left 28V DC Bus, not to the right. Or that the battery is connected to the Main Battery Bus even if the External/Battery selector is switched off. Maybe I'll correct these errors someday, but please don't hesitate to do it if you want.}}

=== Fuel system ===
The Twin Otter's fuel systems consists of two fuel tanks, two primary fuel boost pumps, two secondary boost pumps, a crossfeed valve, gauges for fuel quantity and fuel flow, and a few caution lights.

The fuel tanks are located beneath the cabin floor and arranged in tandem. While the forward tank has a capacity of 1235 lbs the rear tank can contain up to 1341 lbs of fuel. With the engines mounted significantly above the fuel tanks the engines cannot bes supplied with fuel by gravity and hence the system has to rely completely on the fuel pumps. In normal operation (i.e. when the fuel tank selector is set to NORM) the foward tank feeds the right engine and the rear tank feeds the left engine.

However when the tank selector is set to BOTH ON FWD or BOTH ON AFT the boost pumps on the non-selected tank are deactivated and both boost pumps on the selected tank are activated which overwrites the boost pump switches.

The cross-feed valve is powered by the right DC bus, i.e. to work properly it needs either the battery connected or the right generator to be online.

If the primary boost pump fails, the secondary boost pump will automatically activate and the BOOST PUMP 1 FWD/AFT PRESSURE will light up. However the secondary boost pumps can be activated manually through the STANDBY BOOST PUMP EMER switches.

The FUEL LOW LEVEL caution lights will illuminate when the forward tank contains less than 75 lbs resp. the rear tank contains less than 110 lbs of fuel.

For the Twin Otter we have a refuelling system whereby you can easily refuel your Twin Otter or drain the tanks. To activate the fuel system, click on one of the fuel caps located on the left side of the fuselage or go to "Menu" -> "DHC-6" -> "Options" -> "Ground Services" -> "Fuel Truck controls".

=== Hydraulic system ===
The Twin Otter has a quite simple hydraulic system which is mostly fully automated. Hydraulic pressure is provided by an electrical pump which gets it's power from the left electrical bus. Only a few components are operated hydraulically: Nose wheel steering, wheel brakes, and flaps.

If the hydraulic system fails or is inactive, you can still move the flap lever or the nose wheel steering bar, but it won't have any effect on the nose wheel or flap setting.

The only manual control is a mechanic hand pump whih can be used as a backup in case of an failure of the electric pump. The hand pump is stowed behind the copilot's seat.

=== Pneumatic/Bleed air system ===
The very simple pneumatic system of the Twin Otter is only used to provide hot air for the heating and the de-icing system.

Two switches labeled "BLEED AIR" on the overhead panel control the bleed air valve on the left (resp. right) engine.

To get the pitot heat and the prop de-icing working, you have to switch on the bleed air switches.

The intake deflectors are also extended pneumatically, but they don't need the bleed air switch to be activated. Instead they need GG RPM (also called "N2", or "Ng") to be higher than 80 percent.

=== Pitot system ===
A working pitot system is very essential for safe flight, although it is connected to only one instrument: The airspeed indicator (ASI). But if the ASI fails you have no opportunity to know your airspeed and you end up very likely in a stall or even a crash.

The Twin Otter has two indepentently working pitot systems. The left pitot system feeds the pilot's ASI and the right pitot system feeds the copilot's ASI with dynamic pressure.

The two pitot tubes are located on the side of the fuselage in front of the pilot's (resp. copilot's) door. Make sure you removed the pitot tube covers from the pitot tubes prior to the flight or your ASI won't indicate your airspeed but act similar to an altimeter as in this case only static pressure is provided.

If you notice some odd behaviour of the ASI in flight (e.g. accelerating in climb and decelerating in descent) this is a strong indication of a iced pitot tube. Switch on the pitot heat to prevent icing.

=== Static system ===
There are three instruments that work with static pressure: Airspeed indicator (ASI), altimeter (ALT), and vertical speed indicator (VSI). The Twin Otter has a total of four static ports which are located in front of the cockpit doors, two on each side. As they are not pointing into the airstream they are not in danger of icing.

Now what happens in case of an failure of the pitot and/or the static system?

{| class="wikitable"
|-
!Instrument
!Static failure
!Pitot failure
!Both failure
|-
!VSI
|fixed at 0
|normal indication
|fixed at 0
|-
!ALT
|fixed at current value
|normal indication
|fixed at current value
|-
!ASI
|Ascent: indicates too slow
Descent: indicates too fast
|Ascent: Indicates too fast
Descent: Indicates too slow
|fixed at current value
|}

=== Vacuum system ===
Each engine has a vacuum pump that drives the gyros for the attidude indicators and the directional gyros.

The vacuum pump is powered by the gas generator (GG) of the respective engine.

== Keyboard shortcuts ==
[[File:Twin Otter flashlight.jpg|thumb|500px|Twin Otter showing the ALS flashlight]]
{| class="keytable"
!Key
!Function
|-
|{{Key press|Del}}
|Toggle thrust reversers for selected engine(s). Only with throttles in idle position
|-
|{{Key press|c}}
|Show/hide cockpit
|-
|{{Key press|!}}
|Select left engine
|-
|{{Key press|@}}
|Select right engine
|-
|{{Key press|~}}
|Select both engines
|-
|{{Key press|n}}/{{Key press|N}}
|Increase/decrease propeller pitch on selected engine(s)
|-
|{{Key press|j}}/{{Key press|J}}
|Increase/decrease left fuel condition
|-
|{{Key press|k}}/{{Key press|K}}
|Increase/decrease right fuel condition
|-
|{{Key press|l}}
|Toggle pitot heat on/off
|-
|{{Key press|L}}
|Toggle prop deice on/off
|-
|{{Key press|m}}
|Toggle intake deflectors on/off
|-
|{{Key press|f}}
|Toggle [[ALS technical notes#ALS flashlight|flashlight]] (only if [[ALS]] activated)
|-
|{{Key press|y}}
|Show/hide yokes
|-
|{{Key press|Y}}
|Show/hide pilots
|-
|{{Key press|F5}}
|Aileron trim left
|-
|{{Key press|F6}}
|Aileron trim right
|-
|{{Key press|F7}}
|Rudder trim left
|-
|{{Key press|F8}}
|Rudder trim right
|-
|{{Key press|F11}}
|Autopilot controls
|-
|{{Key press|F12}}
|Radio Stack
|-
|{{Key press|q}}
|Adjust nose wheel left
|-
|{{Key press|Ctrl|w}}
|Center nose wheel
|-
|{{Key press|e}}
|Adjust nose wheel right
|-
|{{Key press|w}}/{{Key press|a}}/{{Key press|s}}/{{Key press|d}}
|Move walker forward/backward/left/right. Only in Walk View or Walker Orbit View
|}

== Development ==
After some time of silence, in early 2014 the Twin Otter got under active development again. Until today (Jan. 2015), the visuals (mainly the interior, thanks to Patten and the FlightGear PAF team) and the electrical systems reached many improvements. For example, lanbo64 implemented a startup procedure which comes quite close to the reality.

In addition, dg-505 created an extensive tutorial system, which makes it easy to learn the standard operating procedures, and a number of checklists, which are taken from real Twin Otter Checklists. Richard Harrison is currently working on an [[ALS_technical_notes#Interior_shading|interior shadow cubemap]].

Currently, the Twin Otter is still under active [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 development]. If You are interested in helping to make the Twin Otter even better, You are welcome to join!

{{note|Since December 2015 the development of the Twin Otter has moved away from GitHub and over to the official FlightGear [[FGAddon]] hangar!

If you want to contribute to the Twin Otter it would be advantageous (but not mandatory!) if you have at least basic knowledge about version control. See [[FGAddon]] for details.

You also should get into contact with {{usr|Dg-505}} or {{usr|Bugman}}.
}}

== Review ==
{{review}}

'''Note that this review is about the actual version (January 2015), so some things may change in the future.'''

=== The appearance ===
The Twin Otter has a accurately modelled 3D model. It has some details like the nose gear, the hinges for the ailerons/flaps, or the pitot tubes. All control surfaces are animated (ailerons, flaps, elevator, rudder) and the amphibious version has a retractable gear with two nicely modelled floats. The doors are animated and open/close by clicking on it. In the basic version there are some liveries included, which look partly really good. Many more liveries are available in the [http://liveries.flightgear.org/aircraft.php?id=57 FlightGear Livery Database].

About the interior I have to say that both the cockpit and the cabin are quite accurate. Both have photo-realistic texturing, which is, at least from my point of view, very important for good optics. The interior gives some attention to detail: For example, the cabin has a extinguisher and a seatbelt/no smoking sign. Same thing in the cockpit: The Twin Otter has a very detailed cockpit with almost every instrument working and most switches animated and functional. In my view, the cockpit textures deserve a special mention. As said, it is photo-realistic textured and some of these textures look slightly worn, which gives the appearance of a pretty old, frequently used aircraft. Hats off to the designer(s), this looks really good and realistic.

Another nice function: If you want to know which instrument is which, you can press {{key press|Ctrl|C}} to find out. Then you see also the clickable hotspots in the cockpit.

''' My personal wishlist concerning the appearance:'''
* A bit more detail of the skis
* A bit more detail of the props
* Some additional details like antennas, etc.
* Animation and implementation of the missing switches

=== Flying the Twin Otter ===
Starting the engines of the Twin Otter can be done in two different ways: First, using the Autostart button, which is absolutely '''NOT''' recommended because it's extremely unrealistic! The second way is by using the checklists/tutorials, which guide you step by step through the procedures. If you aren't familiar with this aircraft and want it realistic, it could take some time to get the engines running.

Due to the powerful engines and the STOL skills, the twin otter flies after only a short time of accelerating on the runway. During the climb, the Twin Otter can prove her excellent climb rate: Near sea level a climb rate more than 1500 fpm is also with full fuel tanks and pax absolutely no problem.

In the air the Twin Otter is quite easy to handle. The reactions to the joystick inputs are direct but not too sensitive. As I haven't flown the Twin Otter in reality, so I can't say precisely how realistic the FDM is. But taking the size, the powerful engines, and the relatively small control surfaces into account, it seems to me, that the creator of the FDM has done a good job, and it comes fairly close to the reality.

The FlightGear Twin Otter is also equipped with an autopilot, which is self-explaining and easy to use, but in general I fly manually, because the aircraft is easy to handle.

Landing the Twin Otter is as easy as the rest of the flight. Just pull the throttles back, slow down, line up in front of the runway, and descent. It's worth mentioning that the flaps work very good, so if you need to descent fast for any reason, you can put full flaps, and descent at -2000 fpm without gaining too much speed.

If you only have a very short runway for landing, thrust reverse might be a useful tool. Right after touch down press the {{key press|Del}} key and apply full throttle. Your Twin Otter will quickly slow down, and is healthier for the brakes if you use reverse thrust.

=== Try this ===
If you want have a challenge, try to fly a long-range IFR route in bad weather without using the autopilot. Because all navigation instruments are operated from the cockpit, radio navigation is simulated realistically. Before the flight you can search for the VOR frequencies, and simply navigate from VOR to VOR using the NAV-Display and the DME.

Or try try flying in the mountains, where the high climb rate and the maneuverability is essential, especially if the weather is bad.

== Update 07.2015 ==
[[File:Twin Otter - new interior effects.jpg|thumb|500px|New glass effects in the Twin Otter]]
Some new interior effects have been added by lanbo64 and dg-505:
* Rain effect
* Fog on windows
* Frost
* Glass reflections
* Interior shadows
* Flashlight

== Update 12.2015 ==
[[File:Twin Otter refuelling in LXGB.jpg|thumb|500px|Twin Otter secured and being refueled at Gibraltar Intl]]
In December 2015 the Twin Otter received a major update.
The major changes are:
* Addition of components to securing the aircraft
** Covers for the Pitot tubes
** Wheel chocks
** Covers for the engine intakes and exhausts
** Tie-downs
* Some cockpit elements added/updated
** A radar altimeter added (taken from the [[Cessna 550 Citation II|Citation]] and slightly modified)
** Removed the ADF display and replaced it with a Turn Coordinator (taken from the [[Boeing 707-420|707]] and slightly modified)
** Replaced the [[Avionics_and_instruments#Attitude_Indicator|Artifical Horizon]] with a more realistic one
** A Emergency Locator Transmitter added (taken from the [[Cessna 337G Skymaster|Cessna Skymaster]] and slightly modified)
** Added a switch to mute the fire alarm
** and other, minor improvements
* Some work on the sound
** Rain sound when outside the aircraft
** Sound for rain on the windshield
** Thunder sounds
* The skis have now significantly more detailed 3D-objects
* Added a sophisticated [[FGPanel|2D-Panel]] containing all the major instruments of the Twin Otter (that was tons of work!)
* New splash screens
* Added shadows for ALS and the default rendering system
* Added support for DFaber's [[Walk view|walker]]
* Ground services: Added an advanced fuel truck system
* Added custom dialog windows for the radio stack and the autopilot
* Added a custom flight recorder which reads many of the DHC6-specific properties
* Updated the Autostart/Shutdown functions and the [[Tutorials|tutorials]]/[[Aircraft Checklists|checklists]] to match with the updates
* and many more further improvements, updates and bugfixes...
[[File:Twin Otter cockpit - 29 June 2016.jpg|thumb|500px|Cockpit status from 29 June 2016]]

== Update 06.2016 ==
* Pilot 3D Models. Show/hide them with {{key press|Shift|Y}}.
* Major systems and instrumentation update
** Left pitot and static system for pilot's instruments
** Right pitot and static system for copilot's instruments
** Two independent altimeters for pilot and copilot
** Second KI206 VOR indicator vor better capability of IFR and radio navigation
* Hydraulic system
** Gauge for hydraulic pressure
** Pressure depends on voltage output
* Smooth animation of all switches
* Animation and implementation of the nose wheel steering lever.
{{-}}
== TODO list/future plans ==
In the forum thread about the development of the Twin Otter we've collected some ideas what will be done in the near future (or not so near, who knows...)
{{note|This is the status from January 4th, 2016}}
* Alternative DME, because the current one has some issues with the visibility of the digits<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271314 Forum development topic]</ref> {{done}}
* Ventilator models for the pilots<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271340 Forum development topic]</ref>{{not done}}
* Electrical system: More detailed simulation of the various buses, external power, Bus Tie, circuit breakers<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271426 Forum development topic]</ref> {{progressbar|30}}{{pending}}
* Animation and implementation of Nose wheel steering bar and trim tabs<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref> {{done}} (29 June 2016)
* Proper animation of the Oil temperature gauges and propeller spin<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271462 Forum development topic]</ref>
* Maybe tweaking the FDM to better reaction to aileron input<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271414 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271420 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271431 Forum development topic]</ref>
* Toggleable Pilot models {{done}} (5 June 2016)
* Add support for [[Dual Control]] {{not done}}
* Add a version with a [[JSBSim]] FDM {{pending}}
* Variable interior: Different cockpit layouts (e.g. with a glass cockpit), different cabin layouts (e.g. cargo or combined passenger-cargo), multiple colour styles {{not done}}
* Add a control lock {{not done}}
* Additional baggage compartment in the long nose {{not done}}
* Add more, and enhance the securing and ground equipment (e.g. safety cones, include tiedowns in the FDM (like the Cessna 182) {{not done}}
* Generally, make the 3D model more detailed, more high poly {{not done}}

== Specifications ==
* Never exceed speed: 170 knots (195 mph , 314 km/h)
* Maximum speed: 170 knots (195 mph, 314 km/h)
* Cruise speed: 150-160 knots (173-184 mph, 278-296 km/h)
* Stall speed: 58 knots (VSO, gross weight, landing configuration)
* Stall speed: 80 knots (VS1, cruise configuration)
* Range: 920 nautical miles (1,050 mi, 1,690 km)
* Service ceiling: 25,000 ft (7,620 m)
* MTOW: 12,500 lbs (5,670 kg)
* Rate of climb: 1,600 ft/min (8.1 m/s)

== Gallery ==
<gallery mode="packed">
Twin_otter_rembrandt.png|Showing the Rembrandt landing light
Twin_otter_clouds.png|Flying IFR
Twin_otter_fog.png|Over the alps
Twin_otter_sunrise.png|Still over the alps
DHC-6 Twin Otter Cockpit.jpg|View from the Copilot
DHC-6 Twin Otter @ LOWI - Cockpit.jpg|Entering the Twin Otter in LOWI
DHC-6 Twin Otter.jpg|Over the Grand Canyon
DHC-6_Twin_Otter_@_Matterhorn.png|Circuiting the Matterhorn
Twin_Otter_winter.jpg|Zero altitude flying
De_Havilland_Canada_DHC-6_Twin_Otter_@_TNCM.jpg|Leaving Saint Marteen Island
DHC-6_flight.jpg|Flying over the woods
DHC-6_cabin.jpg|The cabin
De Havilland Canada DHC-6 Twin Otter @ Golden Gate Bridge.jpg|Landing at the Golden Gate bridge
Cockpit of the Twin Otter.jpg|Over the Grand Canyon at Sunset
Twin Otter over Lake Of Constance.jpg|Flying at the Lake of Constance
Twin Otter over Sognefjord.jpg|In Norway over the Sognefjord
Twin Otter Landing @ TNCS.jpg|Landing in heavy thunderstorms
Twin Otter @ BIMS (Iceland).jpg|Discovering small airfields in Iceland
Twin Otter by Adam Swift (Mig29pilot).jpg|Exploring the Scottish Highlands (by Adam Swift)
DHC-6 Twin Otter in steep climb.jpg|Steep climb in Swiss Alps
</gallery>

== Videos ==
{{#ev:youtube|2sPIYeXyi2o|Long range flight and polar navigation (by ''' lanbo64 ''')}}
{{#ev:youtube|MeWQgOOX49o|DHC-6 flight from LFLR to LFLS (by ''' Patten ''')}}

== Thanks to ==
* Syd Adams
* Christian Thiriot (PATTEN)
* Bo Lan (lanbo64)
* Jonathan Schellhase (dg-505)
* Clément de l'Hamaide (f-jjth)
* PAF Team
* Zdenal
* Erik
* abassign
* primtala2
* CaptB
* Adam Swift (Mig29pilot)
* tauchergreg
* Sebastian (rollershutter)
* Thorsten Renk
* The [[Cessna 172]] development team
* The whole FlightGear community

If you have contributed something to this aircraft but don't find your name on this list, feel free to contact me on the [https://forum.flightgear.org/ucp.php?i=pm&mode=compose&u=16519 FlightGear Forum], the [[User talk:Dg-505|FlightGear Wiki]], send an Email to <code>dg-505@web.de</code>, or just edit this page by yourself.

== External links ==
* {{Wikipedia|De Havilland Canada DHC-6 Twin Otter|noicon=1}} (Wikipedia)
* [http://www.blm.gov/style/medialib/blm/nifc/av.Par.70826.File.tmp/SOPA_otter.pdf Standard Operating Procedures (pdf)]
* [http://www.vikingair.com/viking-aircraft/dhc-6-twin-otter Official website]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 Development thread] (FlightGear Forum)

== References ==
{{Appendix}}

{{de Havilland Canada}}

[[Category:Aircraft with a cockpit-only autopilot]]

[[de:de Havilland Canada DHC-6 Twin Otter]]
[[fr:de Havilland Canada DHC-6 Twin Otter]]

JSBSim Engines

2016-12-05T18:54:07Z

Dg-505: /* Starting the engine */

[[JSBSim]] provides a framework for aerodynamics. This page will attempt to explain how to create engines for the JSBSim framework. Engines also require [[JSBSim Thrusters|thrusters]].

== FGPiston ==
Piston engine model. You enter values based on commonly available data and this model creates reasonable output values.
=== Configuration File Format ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<piston_engine name="{string}">
<minmp unit="{INHG | PA | ATM}"> {number} </minmp>
<maxmp unit="{INHG | PA | ATM}"> {number} </maxmp>
<displacement unit="{IN3 | LTR | CC}"> {number} </displacement>
<bore unit="{IN | M}"> {number} </bore> 
<stroke unit="{IN | M}"> {number} </stroke>
<cylinders> {number} </cylinders>
<cylinder-head-mass unit="{KG | LBS}"> {number} </cylinder-head-mass>
<compression-ratio> {number} </compression-ratio>
<sparkfaildrop> {number} </sparkfaildrop>
<maxhp unit="{HP | WATTS}"> {number} </maxhp>
<cycles> {number} </cycles>
<idlerpm> {number} </idlerpm>
<maxrpm> {number} </maxrpm>
<numboostspeeds> {number} </numboostspeeds>
<boostoverride> {0 | 1} </boostoverride>
<boostmanual> {0 | 1} </boostmanual>
<ratedboost1 unit="{INHG | PA | ATM}"> {number} </ratedboost1>
<ratedpower1 unit="{HP | WATTS}"> {number} </ratedpower1>
<ratedrpm1> {number} </ratedrpm1>
<ratedaltitude1 unit="{FT | M}"> {number} </ratedaltitude1>
(repeat for speeds 2 and 3)
<takeoffboost unit="{INHG | PA | ATM}"> {number} </takeoffboost>

<bsfc unit="{LBS/HP*HR | KG/KW*HR}"> {number} </bsfc>
<volumetric-efficiency> {number} </volumetric-efficiency>
<air-intake-impedance-factor> {number} </air-intake-impedance-factor>
<ram-air-factor> {number} </ram-air-factor>
<cooling-factor> {number} </cooling-factor>

<starter-torque> {number} </starter-torque>
<starter-rpm> {number} </starter-rpm>
<static-friction unit="{HP | WATTS}"> {number} </static-friction>
<man-press-lag> {number} </man-press-lag>
<boost-loss-factor> {number} </boost-loss-factor>
</piston_engine>
</syntaxhighlight>

=== Parameter definitions ===
{| class="prettytable"
|minmp
|this value is the nominal idle manifold pressure at sea-level without boost. Along with idlerpm, it determines the throttle response slope.
|-
|maxmp
|this value is the nomial maximum manifold pressure at sea-level without boost. Along with maxrpm it determines the resistance of the aircraft's intake system. See air-intake-impedance-factor
|-
|displacement
|this value is used to determine mass air and fuel flow which impacts engine power and cooling.
|-
|bore
|cylinder bore is currently unused.
|-
|stroke
|piston stroke is used to determine the mean piston speed. A longer stroke results in an engine that does not work as well at higher speeds.
|-
|cylinders
|number of cylinders scales the cylinder head mass.
|-
|cylinder-head-mass
|the nominal mass of a cylinder head. A larger value slows changes in engine temperature
|-
|compression-ratio
|the compression ratio affects the change in volumetric efficiency with altitude.
|-
|sparkfaildrop
|this is the percentage drop in horsepower for single magneto operation.
|-
|maxhp
|this value is the nominal power the engine creates at maxrpm. It will determine bsfc if that tag is not input. It also determines the starter motor power.
|-
|static-friction
|this value is the power required to turn an engine that is not running. Used to control and slow a windmilling propeller.
|-
|cycles
|Designate a 2 or 4 stroke engine. Currently only the 4 stroke engine is supported.
|-
|idlerpm
|this value affects the throttle fall off and the engine stops running if it is slowed below 80% of this value. The engine starts running when it reaches 80% of this value.
|-
|maxrpm
|this value is used to calculate air-box resistance and BSFC. It also affects oil pressure among other things.
|-
|maxthrottle
|Deprecated / unused
|-
|minthrottle
|Deprecated / unused
|-
|numboostspeed
| zero (or not present) for a naturally-aspirated engine, either 1, 2 or 3 for a boosted engine. This corresponds to the number of supercharger speeds. Merlin XII had 1 speed, Merlin 61 had 2, a late Griffon engine apparently had 3. No known engine more than 3, although some German engines apparently had a continuously variable-speed supercharger.
|-
|boostoverride
|unused
|-
|boost-loss-factor (fgfs 2.8)
|boost-loss-factor - zero (or not present) for 'free' supercharging. A value entered will be used as a multiplier to the power required to compress the input air. Typical value should be 1.15 to 1.20.
|-
|boostmanual
|whether a multispeed supercharger will manually or automatically shift boost speeds. On manual shifting the boost speeds is accomplished by controlling propulsion/engine/boostspeed
|-
|takeoffboost
|boost in psi above sea level ambient.
|-
|ratedboost[123]
|the absolute rated boost above sea level ambient (14.7 PSI, 29.92 inHg) for a given boost speed, in psi
|-
|ratedpower[123]
|required by the parser but ignored
|-
|ratedrpm[123]
|The rpm at which rated boost is developed
|-
|ratedaltitude[123]
|The altitude up to which rated boost can be maintained. Up to this altitude the boost is maintained constant for a given throttle position by the BCV or wastegate. Beyond this altitude the manifold pressure must drop, since the supercharger is now at maximum unregulated output. The actual pressure multiplier of the supercharger system is calculated at initialisation from this value.
|-
|bsfc (Advanced)
|Indicated Specific Fuel Consumption. The power produced per unit of fuel. Higher numbers give worse fuel economy. This number may need to be lowered slightly from actual BSFC numbers because some internal engine losses are modeled separately.
|-
|volumetric-efficiency (Advanced)
|the nominal volumetric efficiency of the engine. Boosted engines require values above 1.
|-
|air-intake-impedance-factor (Advanced)
|this number is the pressure drop across the intake system. Increasing it reduces available manifold pressure.
|-
|ram-air-factor (Advanced)
|this number creates a pressure increase with an increase in dynamic pressure (aircraft speed).
|-
|cooling-factor (Advanced)
|this number models how efficient the aircraft cooling system is.
|-
|starter-torque (fgfs 2.8)
|A value specifying the zero RPM torque in lb*ft the starter motor provides. Current default value is 40% of the maximum horsepower value.
|-
|starter-rpm (fgfs 2.8)
| A value specifying the maximum RPM the unloaded starter motor can achieve. Loads placed on the engine by the propeller and throttle will further limit RPM achieved in practice. The actual RPM needs to be more than idlerpm * 0.8 for the engine to start running.
|-
|static-friction (fgfs 2.8)
|this value is the power required to turn an engine that is not running. Used to control and slow a windmilling propeller. Choose a small percentage of maxhp. It can also be adjusted at run-time to simulate accessory or other non-thruster engine load.
|-
|man-press-lag (fgfs 2.8)
|Delay in seconds for manifold pressure changes to take effect after the throttle is moved or the RPM changes. Default is 1 second.
|-
|}

=== Notes ===
* Intake & Throttle
** The intake is modeled by <ram-air-factor>,<minmp>, <maxmp>, and <air-intake-impedance-factor>.
** <ram-air-factor> is the efficiency of the air scoop intake. 0 turns ram air off. Default is 1. This value is exposed on the property tree so it may be altered at runtime to simulate alternate air, etc. The value can be calculated by (ambient pressure)/(desired pressure)-1 where desired pressure is full throttle at rated RPM.
** <maxmp> is the maximum manifold pressure achievable. It is used for determining <BSFC> and <air-intake-impedance-factor> if a values are not supplied for those items.
** <minmp> is used along with <idlerpm> to determine the slope of the throttle response
** <air-intake-impedance-factor> is the fixed impedance in the air intake system. It is determined by <maxmp> if not supplied. This value is exposed on the property tree so it may be altered at runtime to simulate intake icing, alternate air, etc.
* Boost
** <boostmanual> whether a multispeed supercharger will manually or automatically shift boost speeds. On manual shifting the boost speeds is accomplished by controlling propulsion/engine/boostspeed
** <takeoffboost> - Many aircraft had an extra boost setting beyond rated boost, but not totally uncontrolled as in the already mentioned boost-control-cutout, typically attained by pushing the throttle past a mechanical 'gate' preventing its inadvertant use. This was typically used for takeoff, and emergency situations, generally for not more than five minutes. This is a change in the boost control setting, not the actual supercharger speed, and so would only give extra power below the rated altitude. When TAKEOFFBOOST is specified in the config file (and is above RATEDBOOST1), then the throttle position is interpreted as:
*** 0 to 0.98 : idle manifold pressure to rated boost (where attainable)
*** 0.99, 1.0 : takeoff boost (where attainable).
*** A typical takeoff boost for an earlyish Merlin was about 12psi, compared with a rated boost of 9psi.
*** It is quite possible that other boost control settings could have been used on some aircraft, or that takeoff/extra boost could have activated by other means than pushing the throttle full forward through a gate, but this will suffice for now.
** <ratedboost[123]> - the absolute rated boost above sea level ambient (14.7 PSI, 29.92 inHg) for a given boost speed, in psi. Eg the Merlin XII had a rated boost of 9psi, giving approximately 39inHg manifold pressure up to the rated altitude.
*** Note that <maxmp> is still the non-boosted max manifold pressure even for boosted engines - effectively this is simply a measure of the pressure drop through the fully open throttle.
** <ratedaltitude[123]> - The altitude up to which rated boost can be maintained. Up to this altitude the boost is maintained constant for a given throttle position by the BCV or wastegate. Beyond this altitude the manifold pressure must drop, since the supercharger is now at maximum unregulated output. The actual pressure multiplier of the supercharger system is calculated at initialisation from this value.
** <ratedpower[123]> - The power developed at rated boost at rated altitude at rated rpm.
** <ratedrpm[123]> - The rpm at which rated power is developed.
* Power production
** <sparkfaildrop> is the amount of power you get for single magneto operation, try a value of 0.8 or so.
** <volumetric-efficiency> controls how much air goes through the engine at a given RPM. Values below 1 for unboosted engines and values over 1 for boosted engines. This value is exposed on the property tree so it may be altered at runtime.
** <bsfc> is the amount of power the engine produces per unit of fuel consumed. Use it to tune the power produced. This value is exposed on the property tree so it may be altered at runtime.
* Cooling
** <cylinder-head-mass> controls how fast the engine heats up and cools off. So if you have a '5-minute' limit on a power setting you can adjust this value so the engine just starts to overheat at the end of the given time frame.
** <cooling-factor> controls how much 'air' flows over the engine to cool it. Raising the value makes the engine run cooler. This value is exposed on the property tree so it may be altered at runtime to simulate cowl flaps, for example.
* Tuning
** Using a constant speed load, set the engine model to full throttle and rated RPM.
** Set <ram-air-factor> to zero.
** Adjust <air-intake-impedance-factor> to achieve the proper static full throttle manifold pressure.
** Increase airspeed to cruise and adjust <ram-air-factor> to achieve the proper dynamic full throttle manifold pressure.
** Adjust <volumetric-efficiency> first to achieve desired fuel flow rate, leaning engine as required.
** Adjust <bsfc> to achieve desired power.
** Some piston engines will have power curves that will need to be altered from default depending on operating conditions. For example engines with multi-speed superchargers will produce less horse power on high speed at the same manifold pressure compared to low speed. Functions can be setup to alter <volumetric-efficiency> and <bsfc> at run time to get the power and fuel consumption curves correct by using different values for high and low supercharger speeds.

== FGTurbine ==
The jet turbine engine

=== Configuration File Format ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<turbine_engine name="{string}">
<milthrust unit="{LBS | N}"> {number} </milthrust>
<maxthrust unit="{LBS | N}"> {number} </maxthrust>
<bypassratio> {number} </bypassratio>
<bleed> {number} </bleed>
<tsfc> {number} </tsfc>
<atsfc> {number} </atsfc>
<idlen1> {number} </idlen1>
<idlen2> {number} </idlen2>
<n1spinup> {number} </n1spinup>
<n2spinup> {number} </n2spinup>
<maxn1> {number} </maxn1>
<maxn2> {number} </maxn2>
<augmented> {0 | 1} </augmented>
<augmethod> {0 | 1 | 2} </augmethod>
<injected> {0 | 1} </injected>
<injection-time> {number} </injection-time>
<function name="IdleThrust"> </function>
<function name="MilThrust"> </function>
<function name="AugThrust"> </function>
<function name="Injection"> </function>
</turbine_engine>
</syntaxhighlight>

=== Parameter definitions ===
{| class="prettytable"
|milthrust
|Maximum thrust, static, at sea level.
|-
|maxthrust
|Afterburning thrust, static, at sea level.
|-
|bypassratio
|Ratio of bypass air flow to core air flow.
|-
|bleed
|Thrust reduction factor due to losses (0.0 to 1.0).
|-
|tsfc
|Thrust-specific fuel consumption at cruise, lbm/hr/lbf
|-
|atsfc
|Afterburning TSFC, lbm/hr/lbf
|-
|idlen1
|Fan rotor rpm (% of max) at idle
|-
|idlen2
|Core rotor rpm (% of max) at idle
|-
|n1spinup
|Fan rotor rpm starter acceleration (default 1.0)
|-
|n2spinup
|Core rotor rpm starter acceleration (default 3.0)
|-
|maxn1
|Fan rotor rpm (% of max) at full throttle
|-
|maxn2
|Core rotor rpm (% of max) at full throttle
|-
|augmented
|0 = afterburner not installed 1 = afterburner installed
|-
|augmethod
|0 = afterburner activated by property /engines/engine[n]/augmentation 1 = afterburner activated by pushing throttle above 99% position 2 = throttle range is expanded in the FCS, and values above 1.0 are afterburner range
|-
|injected
|0 = Water injection not installed 1 = Water injection installed
|-
|injection-time
|Time, in seconds, of water injection duration
|-
|function
|Two functions, IdleThrust and MilThrust must always be defined. AugThrust is required for afterburning (reheated) engines. Injection is for water injected engines. These functions return a multiplier that is applied to the supplied static thrust values. In aeromatic configurations these functions are tables based on sonic velocity and air density
|}

=== Notes ===
*Bypass ratio is used only to estimate engine acceleration time. The effect of bypass ratio on engine efficiency is already included in the TSFC value. Feel free to set this parameter (even for turbojets) to whatever value gives a desired spool-up rate. Default value is 0.
*The bleed factor is multiplied by thrust to give a resulting thrust after losses. This can represent losses due to bleed, or any other cause. Default value is 0. A common value would be 0.04.
*Nozzle position, for variable area exhaust nozzles, is provided for users needing to drive a nozzle gauge or animate a virtual nozzle.
*This model can only be used with the "direct" thruster. See the file: /engine/direct.xml
*TSFC=fuel consumption per hour/thrust
*There is a Java program here to calculate thrust vs airspeed and altitude. http://adg.stanford.edu/aa241/propulsion/engmodel.html

== FGTurboprop ==
The turboprop engine

=== Configuration File Format ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<milthrust unit="{LBS | N}"> {number} </milthrust>
<idlen1> {number} </idlen1>
<idlen2> {number} </idlen2>
<maxn1> {number} </maxn1>
<maxn2> {number} </maxn2>

<betarangeend> {number} </betarangeend>
<reversemaxpower> {number} </reversemaxpower>
<maxpower> {number} </maxpower>
<psfc> {number} </psfc>
<n1idle_max_delay> {number} </n1idle_max_delay>
<maxstartingtime> {number} </maxstartingtime>
<startern1> {number} </startern1>
<ielumaxtorque> {number} </ielumaxtorque>
<itt_delay> {number} </itt_delay>

<table name="EnginePowerVC">
<description> Engine power, function of airspeed and pressure </description>
<independentVar lookup="row">atmosphere/P-sl-psf</independentVar>
<independentVar lookup="column">velocities/ve-kts</independentVar>
<tableData>
0 50 100 150 200 250
503 0.357 0.380 0.400 0.425 0.457 0.486
1048 0.586 0.589 0.600 0.621 0.650 0.686
1328 0.707 0.721 0.731 0.757 0.786 0.821
1496 0.779 0.786 0.808 0.821 0.857 0.900
1684 0.850 0.857 0.874 0.900 0.943 0.979
1896 0.914 0.929 0.946 0.971 1 1.057
2135 1 1.011 1.029 1.043 1.083 1.150
2213 1.029 1.043 1.057 1.079 1.114 1.171
</tableData>
</table>

<table name="EnginePowerRPM_N1" type="internal">
<description> Engine Power, function of RPM and N1 </description>
<tableData>
0 5 60 86 94 95 96 97 98 99 100 101
0 0 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5
800 0 0.5 35 200 350 380 420 460 500 530 580 620
1200 0 0.5 30 230 400 430 470 505 550 590 640 680
1600 0 0.5 5 240 440 475 510 550 595 630 680 720
2000 0 0.1 0.1 225 450 495 525 565 610 650 700 745
2200 0 0.1 0.1 205 440 480 515 560 605 645 695 743
</tableData>
</table>

<table name="ITT_N1" type="internal">
<description> Inter-Turbine Temperature ITT [deg C] depending on N1 and engine run (0=off / 1=running) </description>
<tableData>
0 1
{n1 value} {number} {number}
...
{n1 value} {number} {number}
</tableData>
</table>

<table name="CombustionEfficiency_N1" type="internal">
<tableData>
{n1 value} {number}
...
{n1 value} {number}
</tableData>
</table>

</syntaxhighlight>

=== Parameter definitions ===
{| class="prettytable"
|milthrust
|[LBS]
|-
|idlen1
|[%]
|-
|maxn1
|[%]
|-
|betarangeend[%]
| if ThrottleCmd < betarangeend/100.0 then engine power=idle, propeller pitch is controled by ThrottleCmd (between MINPITCH and REVERSEPITCH). if ThrottleCmd > betarangeend/100.0 then engine power increases up to max reverse power reversemaxpower [%] max engine power in reverse mode
|-
|maxpower
| [HP]
|-
|psfc
| power specific fuel consumption [pph/HP] for N1=100%
|-
|n1idle_max_delay
|[-] time constant for N1 change
|-
|maxstartenginetime [sec]
| after this time the automatic starting cycle is interrupted when the engine doesn't start (0=automatic starting not present)
|-
|startern1
|[%] when starting starter spin up engine to this spin
|-
|ielumaxtorque [lb.ft]
|if torque>ielumaxtorque limiters decrease the throttle (ielu = Integrated Electronic Limiter Unit)
|-
|itt_delay
|[-] time constant for ITT change (ITT = Inter Turbine Temperature)
|-
|}

=== Starting the engine ===
In a [[YASim]] aircraft you need to simulate the spool-up of the engine in a [[Nasal]] script. For an example see lines 498-529 of [{{fgaddon aircraft url|b1900d|Nasal/systems.nas|l=498}} systems.nas] from the [[B1900d]].

JSBSim however spools the engine up automatically when certain conditions are met. According to my experience the process is the following:

# The [[property]] <code>/engines/engine[~n~]/cutoff</code> has to be true.
# Set the property <code>/controls/electric/engine[~n~]generator</code> to true.
# Set the property <code>/controls/engines/engine[~n~]/starter</code> to true as well.
# As result, <code>/engines/engine[~n~]/starter</code> and <code>/engines/engine[~n~]/starting</code> will be set to true and <code>/engines/engine[~n~]/n1</code> will increase which means that the engine is spooling up. In JSBSim <code>n1</code> represents the rotation speed of the turbine shaft which is significantly higher than the propeller speed.
# <code>/engines/engine[~n~]/n1</code> stabilizes at a specific value which is defined in <code><startern1></code> in the engine definition file of the FDM (see the table above or as an example the [{{fgaddon aircraft url|b1900d|Engines/PT6A67D.xml|l=11}} engine file] of the B1900d).
# When <code>/engines/engine[~n~]/n1</code> rises above 15 (at least I think), you can set <code>/engines/engine[~n~]/cutoff</code> to false which simulates that the engine now gets supplied with fuel.
# This sets <code>/engines/engine[~n~]/starting</code> to false and <code>/engines/engine[~n~]/cranking</code> to true.
# Now you may set <code>/engines/engine[~n~]/starter</code> to false without interrupting the starting process.
# <code>/engines/engine[~n~]/n1</code> will increase further until it stabilizes at the value which is defined in <code>idlen1</code> in the [{{fgaddon aircraft url|b1900d|Engines/PT6A67D.xml|l=5}} engine definition file].
# Finally <code>/engines/engine[~n~]/cranking</code> will be set to false and <code>/engines/engine[~n~]/running</code> to true which means that the engine is now running.

Pleas note that the above described process is only an assumption based on my experiences with trying to create a JSBSim FDM for the [[Twin Otter]] which is equipped with turboprop engines, and unfortunately I cannot guarantee the correctness. If something is wrong here feel free to correct it.
: [[User:Dg-505|Dg-505]] ([[User talk:Dg-505|talk]]) 13:53, 5 December 2016 (EST)

== FGRocket ==
The rocket engine
=== Configuration File Format ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<rocket_engine name="{string}">
<isp> {number} </isp>
<builduptime> {number} </builduptime>
<maxthrottle> {number} </maxthrottle>
<minthrottle> {number} </minthrottle>
<slfuelflowmax> {number} </slfuelflowmax>
<sloxiflowmax> {number} </sloxiflowmax>
<variation>
<thrust> {number} </thrust>
<total_isp> {number} </total_isp>
</variation>
<thrust_table name="propulsion/thrust_prop_remain" type="internal">
<tableData>
{number} {number}
...
{number} {number}
</tableData>
</thrust_table>
</rocket_engine>
</syntaxhighlight>

== FGElectric ==
Simple thrust producer. You enter the max power as <power unit="WATTS"> and the engine model produces throttle_setting*power watts of output.
* Enter the max power as <power unit="WATTS"> and the engine model produces throttle_setting*power watts of output.
=== Configuration File Format ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<electric_engine name="{string}">
<power unit="{HP | WATTS}"> {number} </power>
</electric_engine>
</syntaxhighlight>

=== Notes ===
FGElectric models an electric motor based on the configuration file <power> parameter. The throttle controls motor output linearly from zero to <power>. This power value (converted internally to horsepower) is then used by FGPropeller to apply torque to the propeller. At present there is no battery model available, so this motor does not consume any energy. There is no internal friction.

== Sources ==
* http://jsbsim.sourceforge.net/JSBSim/classJSBSim_1_1FGPiston.html
* http://jsbsim.sourceforge.net/JSBSim/classJSBSim_1_1FGTurbine.html
* http://jsbsim.sourceforge.net/JSBSim/classJSBSim_1_1FGTurboProp.html

{{JSBSim}}

De Havilland Canada DHC-6 Twin Otter

2016-12-04T16:40:51Z

Dg-505: /* TODO list/future plans */

{{lowercase title}}{{:{{PAGENAME}}/info}}
The '''de Havilland Canada DHC-6 Twin Otter''', sometimes affectionately called the '''''Twotter''''', is a 20-passenger STOL (Short Takeoff and Landing) utility aircraft. It has often been called the most successful aircraft program in Canada's history. The Twin Otter is a high-wing twin-engine turboprop aircraft with a non-retractable tricycle gear, a non-pressurised cabin and two constant-speed props. In FlightGear, there are three versions available: Wheels, Floats (amphibious) and skis.

== About the original ==
The DHC-6 Twin Otter is the further development version of the [[DHC-3]] Otter of the same manufacturer. The development of the Twin Otter began in 1964, it's first flight was on May 20, 1965<ref>{{wikipedia|De Havilland Canada DHC-6 Twin Otter#Design and development}}</ref>. To keep the STOL abilities of the Otter, the DHC-6 got two powerful {{wikipedia|Pratt & Whitney Canada PT6}} turboprop engines with 410 kW produced by each turbine in the first version, the DHC-6-100.

In 1968, the Twin Otter was developed to a new version, the -200 series, which had improved STOL performance.

One year later, in 1969, the DHC-6-300 series was introduced, with more powerful engines, the PT6A-27 with 460 kW. Until today, the -300 Series is with 614 built aircraft the most successful variant of the Twin Otter. 1988 the production of the DHC-6-300 ended.

After 18 years of not-producing the Twin Otter Viking Air acquired the production rights from Bombadier Aerospace, and started producing a new series, the DHC-6-400, whose first flight was on October 01, 2008. The DHC-6-400 is equipped with modern state-of-the-art avionics and even more powerful PTA6-34 engines also from Pratt and Whitney. Until summer 2014, there were built 55 aircraft of the -400 series.

The aircraft's powerful engines, it's STOL abilities, and it's spacious cabin make the DHC-6 a popular aircraft for skydiving and well-suited as a bush plane for inacessible and remote terrain in many developing countries.

The FlightGear version is the DHC-6-300 Series.

== Handling the aircraft ==
=== Preflight inspection ===
To make it as real as possible it is highly recommended to use the walker for the preflight inspection
* Nose:
** Remove the covers of both pitot tubes. Otherwise the airspeed indicator won't show anything. (The pitot tubes are approximately at eye level in front of the left and right cockpit doors)
** Check the nose gear (wheel, damper, taxi lamp) for damage and tire pressure
* Left wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the left tie-down
** Check the wing, landing light, aileron and flaps for damage
* Left main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Tail:
** Remove the rear tie-down
** Check the empennage for damage
* Right main gear:
** Remove the wheel chocks
** Check the gear for damage and tire pressure
* Right wing:
** Remove the engine cover, or you won't be able to start the engines
** Remove the right tiedown.
** Check the wing, landing light, aileron and flaps for damage

=== Engine startup process ===
[[File:DHC-6 Twin Otter center panel.jpg|thumb|400px|The center panel of the Twin Otter with engine instruments and radio stack]]
[[File:DHC-6 Twin Otter Overhead Panel.jpg|thumb|400px|The overhead panel of the Twin Otter]]
The Twin Otter is a quite complex aircraft, so starting up the engines isn't something that can be done in two or three steps.
# Ensure that the parking brake is set, the throttle levers are in idle position, propeller levers are on feather position and fuel condition levers are in cutoff position
# Switch on the battery master and select BATTERY as power source (Captain's overhead panel)
# Switch on the cabin lights and the instrument lighting
# Check that the voltage is above 18 V; normally it's around 24 V (above the radio sack)
# Make sure that there is enough fuel in the tanks for the flight you've planned
# Switch on the "FASTEN SEATBELT" and the "NO SMOKING" sign
# Switch on the beacon (center overhead panel)
# If you do not start up on asphalt, you must switch on the intake deflectors. Otherwise the engines can get damaged
# Engage both boost pumps (at the bottom of the center panel, below the engine instruments)
# If the outside temperature is below 0°C you must switch on the Pitot Heat and the Prop De-ice
# Switch the IND selector to BAT (above the radio stack)
# Check that no one's about to walk into the left propeller
# Engage the stater switch left and watch GG RPM rising (lowest engine instrument on the center panel)
# When GG RPM exceeds 12 % push the left condition lever full forward to supply the engine with fuel
# When the PROP RPM rises stable repeat the steps 12 - 14 for the right engine
# When also the right propeller increases it's RPM stable you can switch off the starter
# Push both propeller levers full forward
# Switch on the navigation lights (POSN LT)
# Switch on both generators
# Select R GEN on the IND selector
# Switch on the window heating (First officers overhead panel)
# Compare the indication of the heading indicator with the magnetic compass: If they don't coincide you have to synchronize them by adjusting the heading offset of the heading indicator
# Set the radios to the required frequencies and the altimeter to QNH/airport elevation

{{note|The startup procedure described above is slightly simplified. When following the in-sim checklists you have to execute 4 checklists with over 50 items.}}

=== Take off ===
* Flaps 10-20° depending on runway length
* Landing lights on
* Release the parking brake
* Engage Autofeather to automatically feather the prop if an engine fails
* Give full throttle. Some engine limit warnings will appear, but for a short time you may exceed the limits.
* Rotate at aprox. 80-95 kts

=== Climb ===
* Reduce power to fall below the engine limits
* Flaps up
* Landing lights off
* Airspeed around 110-120 kts
* Intake deflectors and Autofeather off

=== Cruise ===
* Airspeed 150-165 kts
* If outside temperature falls below 0°C switch on the Pitot Heat and the Prop De-ice
* Engine instruments within limits
* Keep an eye on the fuel quantity

=== Landing ===
* Set Flaps step by step
* Airspeed below 108 kts when Flaps extended
* Landing lights on
* Condition and propeller levers full forward
* If not landing on asphalt, activate the intake deflector
* Verify that the parking brake is off
* Touchdown with 60-70 kts
* After touchdown apply reverse thrust

=== Airspeeds ===

{| class="wikitable"
! Airspeed !! IAS
|-
| Stall speed, landing config (VS0) || 58 kts
|-
| Stall speed, cruise config (VS1) || 80 kts
|-
| Rotation speed (VR) || 80-95 kts
|-
| Maximum flap extended speed (VFE) || 108 kts
|-
| Cruise speed (VC) || 150-165 kts
|-
| Maneuvering speed (VA) || 130 kts
|-
| Never exceed speed (VNE) || 170 kts
|}

== Systems overview<ref>[http://www.cram.com/flashcards/twin-otter-dhc6-300-1980260 Twin Otter flashcards on cram.com]</ref><ref>[http://www.aerosoft2.de/downloads/twotter/Manual-Twin-Otter-Extended-Vol2-Systems.pdf Systems manual of Aerosoft's Twin Otter Extended]</ref> ==
The Twin Otter is equipped with several [[Aircraft systems|systems]] which operate the aircraft's components:
* Electrical: Operates i. a. hydraulic pump, boost pumps, engine gauges, turn coordinator, lighting, auto-feather
* Fuel: Supplies engines with fuel from two fuel tanks
* Hydraulic: Operates flaps, nose wheel steering, and wheel brakes
* [[FGproperties/Systems/Pitot|Pitot]]: Supplies airspeed indicators with dynamic pressure
* Pneumatic/Bleed Air: Operates heating and de-icing system and intake deflectors
* [[FGproperties/Systems/static|Static]]: Supplies airspeed indicators, altimeters and vertical speed indicators with static pressure
* [[Aircraft systems#Vacuum|Vacuum]]: Drives gyros for artifical horizon and directional gyro/heading indicator

Please note that as of July 2016 not all of these systems are implemented!

=== Electrical system ===
[[File:Twin Otter electrical system scheme.jpg|thumb|400px|The electrical system of the Twin Otter in a schematic representation]]
The electrical system is fed by an 40 ampere-hour battery and two engine-driven generators (which operate as starter-motors when starting the engine). It is primarily a 28 volt, direct current (DC) system, but some components need alternating current (AC) to work.

There exist seven buses which provide electrical power to several components:
# Left 28V DC bus: Is driven by left engine's generator. It feeds the DC voltmeter, hydraulic pump, prop auto-feather system, fire detection system, primary boost pumps (forward and rear), "R GEN FAIL" caution light
# Right 28V DC bus: Is driven by right engine's generator. It feeds the propeller overspeed governor, crossfeed fuel valve, secondary boost pumps (forward and rear), "L GEN FAIL" caution light
# Aux battery bus: Uses a auxiliary 3.6 ampere-hour battery to support the starter motors when starting the engines.
# Main battery bus: Is controlled by the Master Battery switch. When switched off, only the interior lights are provided with power. When MASTER is selected, it connects the electrical system to generators or battery or external power, depending on the EXTERNAL/BATTERY selector switch position.
# Battery/External Power bus: Is controlled by the EXTERNAL/BATTERY selector switch. When EXTERNAL is selected, it isolates the battery and connects the external power unit to the left and right bus. BATTERY will connect the battery to the left and right bus when generators are not running or the generator voltage is lower than the battery voltage. If the generator voltage is highter than the battery voltage it connects the left and right bus to the respective generator. When swithced off, the whole electrical system gets disconnected.
# 26V AC bus: Torque presure, fuel flow, and oil pressure gauges,
# 115V AC bus: Fuel quantity gauges, vacuum pumps for gyros (artifical horizon and directional gyro

The two AC buses are fed from one of the two static inverters. The No.1 inverter receives power from the Left 28V DC bus (and hence from the left generator), and the No.2 inverter receives power from the right 28V DC bus (and hence from the right generator). The inverters are selected alternatively by the inverter switch located on the overhead panel.

=== Fuel system ===
The Twin Otter's fuel systems consists of two fuel tanks, two primary fuel boost pumps, two secondary boost pumps, a crossfeed valve, gauges for fuel quantity and fuel flow, and a few caution lights.

The fuel tanks are located beneath the cabin floor and arranged in tandem. While the forward tank has a capacity of 1235 lbs the rear tank can contain up to 1341 lbs of fuel. With the engines mounted significantly above the fuel tanks the engines cannot bes supplied with fuel by gravity and hence the system has to rely completely on the fuel pumps. In normal operation (i.e. when the fuel tank selector is set to NORM) the foward tank feeds the right engine and the rear tank feeds the left engine.

However when the tank selector is set to BOTH ON FWD or BOTH ON AFT the boost pumps on the non-selected tank are deactivated and both boost pumps on the selected tank are activated which overwrites the boost pump switches.

The cross-feed valve is powered by the right DC bus, i.e. to work properly it needs either the battery connected or the right generator to be online.

If the primary boost pump fails, the secondary boost pump will automatically activate and the BOOST PUMP 1 FWD/AFT PRESSURE will light up. However the secondary boost pumps can be activated manually through the STANDBY BOOST PUMP EMER switches.

The FUEL LOW LEVEL caution lights will illuminate when the forward tank contains less than 75 lbs resp. the rear tank contains less than 110 lbs of fuel.

For the Twin Otter we have a refuelling system whereby you can easily refuel your Twin Otter or drain the tanks. To activate the fuel system, click on one of the fuel caps located on the left side of the fuselage or go to "Menu" -> "DHC-6" -> "Options" -> "Ground Services" -> "Fuel Truck controls".

=== Hydraulic system ===
The Twin Otter has a quite simple hydraulic system which is mostly fully automated. Hydraulic pressure is provided by an electrical pump which gets it's power from the left electrical bus. Only a few components are operated hydraulically: Nose wheel steering, wheel brakes, and flaps.

If the hydraulic system fails or is inactive, you can still move the flap lever or the nose wheel steering bar, but it won't have any effect on the nose wheel or flap setting.

The only manual control is a mechanic hand pump whih can be used as a backup in case of an failure of the electric pump. The hand pump is stowed behind the copilot's seat.

=== Pneumatic/Bleed air system ===
The very simple pneumatic system of the Twin Otter is only used to provide hot air for the heating and the de-icing system.

Two switches labeled "BLEED AIR" on the overhead panel control the bleed air valve on the left (resp. right) engine.

To get the pitot heat and the prop de-icing working, you have to switch on the bleed air switches.

The intake deflectors are also extended pneumatically, but they don't need the bleed air switch to be activated. Instead they need GG RPM (also called "N2", or "Ng") to be higher than 80 percent.

=== Pitot system ===
A working pitot system is very essential for safe flight, although it is connected to only one instrument: The airspeed indicator (ASI). But if the ASI fails you have no opportunity to know your airspeed and you end up very likely in a stall or even a crash.

The Twin Otter has two indepentently working pitot systems. The left pitot system feeds the pilot's ASI and the right pitot system feeds the copilot's ASI with dynamic pressure.

The two pitot tubes are located on the side of the fuselage in front of the pilot's (resp. copilot's) door. Make sure you removed the pitot tube covers from the pitot tubes prior to the flight or your ASI won't indicate your airspeed but act similar to an altimeter as in this case only static pressure is provided.

If you notice some odd behaviour of the ASI in flight (e.g. accelerating in climb and decelerating in descent) this is a strong indication of a iced pitot tube. Switch on the pitot heat to prevent icing.

=== Static system ===
There are three instruments that work with static pressure: Airspeed indicator (ASI), altimeter (ALT), and vertical speed indicator (VSI). The Twin Otter has a total of four static ports which are located in front of the cockpit doors, two on each side. As they are not pointing into the airstream they are not in danger of icing.

Now what happens in case of an failure of the pitot and/or the static system?

{| class="wikitable"
|-
!Instrument
!Static failure
!Pitot failure
!Both failure
|-
!VSI
|fixed at 0
|normal indication
|fixed at 0
|-
!ALT
|fixed at current value
|normal indication
|fixed at current value
|-
!ASI
|Ascent: indicates too slow
Descent: indicates too fast
|Ascent: Indicates too fast
Descent: Indicates too slow
|fixed at current value
|}

=== Vacuum system ===
Each engine has a vacuum pump that drives the gyros for the attidude indicators and the directional gyros.

The vacuum pump is powered by the gas generator (GG) of the respective engine.

== Keyboard shortcuts ==
[[File:Twin Otter flashlight.jpg|thumb|500px|Twin Otter showing the ALS flashlight]]
{| class="keytable"
!Key
!Function
|-
|{{Key press|Del}}
|Toggle thrust reversers for selected engine(s). Only with throttles in idle position
|-
|{{Key press|c}}
|Show/hide cockpit
|-
|{{Key press|!}}
|Select left engine
|-
|{{Key press|@}}
|Select right engine
|-
|{{Key press|~}}
|Select both engines
|-
|{{Key press|n}}/{{Key press|N}}
|Increase/decrease propeller pitch on selected engine(s)
|-
|{{Key press|j}}/{{Key press|J}}
|Increase/decrease left fuel condition
|-
|{{Key press|k}}/{{Key press|K}}
|Increase/decrease right fuel condition
|-
|{{Key press|l}}
|Toggle pitot heat on/off
|-
|{{Key press|L}}
|Toggle prop deice on/off
|-
|{{Key press|m}}
|Toggle intake deflectors on/off
|-
|{{Key press|f}}
|Toggle [[ALS technical notes#ALS flashlight|flashlight]] (only if [[ALS]] activated)
|-
|{{Key press|y}}
|Show/hide yokes
|-
|{{Key press|Y}}
|Show/hide pilots
|-
|{{Key press|F5}}
|Aileron trim left
|-
|{{Key press|F6}}
|Aileron trim right
|-
|{{Key press|F7}}
|Rudder trim left
|-
|{{Key press|F8}}
|Rudder trim right
|-
|{{Key press|F11}}
|Autopilot controls
|-
|{{Key press|F12}}
|Radio Stack
|-
|{{Key press|q}}
|Adjust nose wheel left
|-
|{{Key press|Ctrl|w}}
|Center nose wheel
|-
|{{Key press|e}}
|Adjust nose wheel right
|-
|{{Key press|w}}/{{Key press|a}}/{{Key press|s}}/{{Key press|d}}
|Move walker forward/backward/left/right. Only in Walk View or Walker Orbit View
|}

== Development ==
After some time of silence, in early 2014 the Twin Otter got under active development again. Until today (Jan. 2015), the visuals (mainly the interior, thanks to Patten and the FlightGear PAF team) and the electrical systems reached many improvements. For example, lanbo64 implemented a startup procedure which comes quite close to the reality.

In addition, dg-505 created an extensive tutorial system, which makes it easy to learn the standard operating procedures, and a number of checklists, which are taken from real Twin Otter Checklists. Richard Harrison is currently working on an [[ALS_technical_notes#Interior_shading|interior shadow cubemap]].

Currently, the Twin Otter is still under active [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 development]. If You are interested in helping to make the Twin Otter even better, You are welcome to join!

{{note|Since December 2015 the development of the Twin Otter has moved away from GitHub and over to the official FlightGear [[FGAddon]] hangar!

If you want to contribute to the Twin Otter it would be advantageous (but not mandatory!) if you have at least basic knowledge about version control. See [[FGAddon]] for details.

You also should get into contact with {{usr|Dg-505}} or {{usr|Bugman}}.
}}

== Review ==
{{review}}

'''Note that this review is about the actual version (January 2015), so some things may change in the future.'''

=== The appearance ===
The Twin Otter has a accurately modelled 3D model. It has some details like the nose gear, the hinges for the ailerons/flaps, or the pitot tubes. All control surfaces are animated (ailerons, flaps, elevator, rudder) and the amphibious version has a retractable gear with two nicely modelled floats. The doors are animated and open/close by clicking on it. In the basic version there are some liveries included, which look partly really good. Many more liveries are available in the [http://liveries.flightgear.org/aircraft.php?id=57 FlightGear Livery Database].

About the interior I have to say that both the cockpit and the cabin are quite accurate. Both have photo-realistic texturing, which is, at least from my point of view, very important for good optics. The interior gives some attention to detail: For example, the cabin has a extinguisher and a seatbelt/no smoking sign. Same thing in the cockpit: The Twin Otter has a very detailed cockpit with almost every instrument working and most switches animated and functional. In my view, the cockpit textures deserve a special mention. As said, it is photo-realistic textured and some of these textures look slightly worn, which gives the appearance of a pretty old, frequently used aircraft. Hats off to the designer(s), this looks really good and realistic.

Another nice function: If you want to know which instrument is which, you can press {{key press|Ctrl|C}} to find out. Then you see also the clickable hotspots in the cockpit.

''' My personal wishlist concerning the appearance:'''
* A bit more detail of the skis
* A bit more detail of the props
* Some additional details like antennas, etc.
* Animation and implementation of the missing switches

=== Flying the Twin Otter ===
Starting the engines of the Twin Otter can be done in two different ways: First, using the Autostart button, which is absolutely '''NOT''' recommended because it's extremely unrealistic! The second way is by using the checklists/tutorials, which guide you step by step through the procedures. If you aren't familiar with this aircraft and want it realistic, it could take some time to get the engines running.

Due to the powerful engines and the STOL skills, the twin otter flies after only a short time of accelerating on the runway. During the climb, the Twin Otter can prove her excellent climb rate: Near sea level a climb rate more than 1500 fpm is also with full fuel tanks and pax absolutely no problem.

In the air the Twin Otter is quite easy to handle. The reactions to the joystick inputs are direct but not too sensitive. As I haven't flown the Twin Otter in reality, so I can't say precisely how realistic the FDM is. But taking the size, the powerful engines, and the relatively small control surfaces into account, it seems to me, that the creator of the FDM has done a good job, and it comes fairly close to the reality.

The FlightGear Twin Otter is also equipped with an autopilot, which is self-explaining and easy to use, but in general I fly manually, because the aircraft is easy to handle.

Landing the Twin Otter is as easy as the rest of the flight. Just pull the throttles back, slow down, line up in front of the runway, and descent. It's worth mentioning that the flaps work very good, so if you need to descent fast for any reason, you can put full flaps, and descent at -2000 fpm without gaining too much speed.

If you only have a very short runway for landing, thrust reverse might be a useful tool. Right after touch down press the {{key press|Del}} key and apply full throttle. Your Twin Otter will quickly slow down, and is healthier for the brakes if you use reverse thrust.

=== Try this ===
If you want have a challenge, try to fly a long-range IFR route in bad weather without using the autopilot. Because all navigation instruments are operated from the cockpit, radio navigation is simulated realistically. Before the flight you can search for the VOR frequencies, and simply navigate from VOR to VOR using the NAV-Display and the DME.

Or try try flying in the mountains, where the high climb rate and the maneuverability is essential, especially if the weather is bad.

== Update 07.2015 ==
[[File:Twin Otter - new interior effects.jpg|thumb|500px|New glass effects in the Twin Otter]]
Some new interior effects have been added by lanbo64 and dg-505:
* Rain effect
* Fog on windows
* Frost
* Glass reflections
* Interior shadows
* Flashlight

== Update 12.2015 ==
[[File:Twin Otter refuelling in LXGB.jpg|thumb|500px|Twin Otter secured and being refueled at Gibraltar Intl]]
In December 2015 the Twin Otter received a major update.
The major changes are:
* Addition of components to securing the aircraft
** Covers for the Pitot tubes
** Wheel chocks
** Covers for the engine intakes and exhausts
** Tie-downs
* Some cockpit elements added/updated
** A radar altimeter added (taken from the [[Cessna 550 Citation II|Citation]] and slightly modified)
** Removed the ADF display and replaced it with a Turn Coordinator (taken from the [[Boeing 707-420|707]] and slightly modified)
** Replaced the [[Avionics_and_instruments#Attitude_Indicator|Artifical Horizon]] with a more realistic one
** A Emergency Locator Transmitter added (taken from the [[Cessna 337G Skymaster|Cessna Skymaster]] and slightly modified)
** Added a switch to mute the fire alarm
** and other, minor improvements
* Some work on the sound
** Rain sound when outside the aircraft
** Sound for rain on the windshield
** Thunder sounds
* The skis have now significantly more detailed 3D-objects
* Added a sophisticated [[FGPanel|2D-Panel]] containing all the major instruments of the Twin Otter (that was tons of work!)
* New splash screens
* Added shadows for ALS and the default rendering system
* Added support for DFaber's [[Walk view|walker]]
* Ground services: Added an advanced fuel truck system
* Added custom dialog windows for the radio stack and the autopilot
* Added a custom flight recorder which reads many of the DHC6-specific properties
* Updated the Autostart/Shutdown functions and the [[Tutorials|tutorials]]/[[Aircraft Checklists|checklists]] to match with the updates
* and many more further improvements, updates and bugfixes...
[[File:Twin Otter cockpit - 29 June 2016.jpg|thumb|500px|Cockpit status from 29 June 2016]]

== Update 06.2016 ==
* Pilot 3D Models. Show/hide them with {{key press|Shift|Y}}.
* Major systems and instrumentation update
** Left pitot and static system for pilot's instruments
** Right pitot and static system for copilot's instruments
** Two independent altimeters for pilot and copilot
** Second KI206 VOR indicator vor better capability of IFR and radio navigation
* Hydraulic system
** Gauge for hydraulic pressure
** Pressure depends on voltage output
* Smooth animation of all switches
* Animation and implementation of the nose wheel steering lever.
{{-}}
== TODO list/future plans ==
In the forum thread about the development of the Twin Otter we've collected some ideas what will be done in the near future (or not so near, who knows...)
{{note|This is the status from January 4th, 2016}}
* Alternative DME, because the current one has some issues with the visibility of the digits<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271314 Forum development topic]</ref> {{done}}
* Ventilator models for the pilots<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271340 Forum development topic]</ref>{{not done}}
* Electrical system: More detailed simulation of the various buses, external power, Bus Tie, circuit breakers<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271426 Forum development topic]</ref> {{progressbar|30}}{{pending}}
* Animation and implementation of Nose wheel steering bar and trim tabs<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=510#p271354 Forum development topic]</ref> {{done}} (29 June 2016)
* Proper animation of the Oil temperature gauges and propeller spin<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271462 Forum development topic]</ref>
* Maybe tweaking the FDM to better reaction to aileron input<ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271414 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271420 Forum development topic]</ref><ref>[http://forum.flightgear.org/viewtopic.php?f=4&t=21965&start=525#p271431 Forum development topic]</ref>
* Toggleable Pilot models {{done}} (5 June 2016)
* Add support for [[Dual Control]] {{not done}}
* Add a version with a [[JSBSim]] FDM {{pending}}
* Variable interior: Different cockpit layouts (e.g. with a glass cockpit), different cabin layouts (e.g. cargo or combined passenger-cargo), multiple colour styles {{not done}}
* Add a control lock {{not done}}
* Additional baggage compartment in the long nose {{not done}}
* Add more, and enhance the securing and ground equipment (e.g. safety cones, include tiedowns in the FDM (like the Cessna 182) {{not done}}
* Generally, make the 3D model more detailed, more high poly {{not done}}

== Specifications ==
* Never exceed speed: 170 knots (195 mph , 314 km/h)
* Maximum speed: 170 knots (195 mph, 314 km/h)
* Cruise speed: 150-160 knots (173-184 mph, 278-296 km/h)
* Stall speed: 58 knots (VSO, gross weight, landing configuration)
* Stall speed: 80 knots (VS1, cruise configuration)
* Range: 920 nautical miles (1,050 mi, 1,690 km)
* Service ceiling: 25,000 ft (7,620 m)
* MTOW: 12,500 lbs (5,670 kg)
* Rate of climb: 1,600 ft/min (8.1 m/s)

== Gallery ==
<gallery mode="packed">
Twin_otter_rembrandt.png|Showing the Rembrandt landing light
Twin_otter_clouds.png|Flying IFR
Twin_otter_fog.png|Over the alps
Twin_otter_sunrise.png|Still over the alps
DHC-6 Twin Otter Cockpit.jpg|View from the Copilot
DHC-6 Twin Otter @ LOWI - Cockpit.jpg|Entering the Twin Otter in LOWI
DHC-6 Twin Otter.jpg|Over the Grand Canyon
DHC-6_Twin_Otter_@_Matterhorn.png|Circuiting the Matterhorn
Twin_Otter_winter.jpg|Zero altitude flying
De_Havilland_Canada_DHC-6_Twin_Otter_@_TNCM.jpg|Leaving Saint Marteen Island
DHC-6_flight.jpg|Flying over the woods
DHC-6_cabin.jpg|The cabin
De Havilland Canada DHC-6 Twin Otter @ Golden Gate Bridge.jpg|Landing at the Golden Gate bridge
Cockpit of the Twin Otter.jpg|Over the Grand Canyon at Sunset
Twin Otter over Lake Of Constance.jpg|Flying at the Lake of Constance
Twin Otter over Sognefjord.jpg|In Norway over the Sognefjord
Twin Otter Landing @ TNCS.jpg|Landing in heavy thunderstorms
Twin Otter @ BIMS (Iceland).jpg|Discovering small airfields in Iceland
Twin Otter by Adam Swift (Mig29pilot).jpg|Exploring the Scottish Highlands (by Adam Swift)
DHC-6 Twin Otter in steep climb.jpg|Steep climb in Swiss Alps
</gallery>

== Videos ==
{{#ev:youtube|2sPIYeXyi2o|Long range flight and polar navigation (by ''' lanbo64 ''')}}
{{#ev:youtube|MeWQgOOX49o|DHC-6 flight from LFLR to LFLS (by ''' Patten ''')}}

== Thanks to ==
* Syd Adams
* Christian Thiriot (PATTEN)
* Bo Lan (lanbo64)
* Jonathan Schellhase (dg-505)
* Clément de l'Hamaide (f-jjth)
* PAF Team
* Zdenal
* Erik
* abassign
* primtala2
* CaptB
* Adam Swift (Mig29pilot)
* tauchergreg
* Sebastian (rollershutter)
* Thorsten Renk
* The [[Cessna 172]] development team
* The whole FlightGear community

If you have contributed something to this aircraft but don't find your name on this list, feel free to contact me on the [https://forum.flightgear.org/ucp.php?i=pm&mode=compose&u=16519 FlightGear Forum], the [[User talk:Dg-505|FlightGear Wiki]], send an Email to <code>dg-505@web.de</code>, or just edit this page by yourself.

== External links ==
* {{Wikipedia|De Havilland Canada DHC-6 Twin Otter|noicon=1}} (Wikipedia)
* [http://www.blm.gov/style/medialib/blm/nifc/av.Par.70826.File.tmp/SOPA_otter.pdf Standard Operating Procedures (pdf)]
* [http://www.vikingair.com/viking-aircraft/dhc-6-twin-otter Official website]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=21965 Development thread] (FlightGear Forum)

== References ==
{{Appendix}}

{{de Havilland Canada}}

[[Category:Aircraft with a cockpit-only autopilot]]

[[de:de Havilland Canada DHC-6 Twin Otter]]
[[fr:de Havilland Canada DHC-6 Twin Otter]]

FlightGear Newsletter December 2016

2016-12-03T08:36:41Z

Dg-505: