https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=RChandra&feedformat=atomFlightGear wiki - User contributions [en]2024-03-28T12:42:11ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=Phi&diff=120477Phi2019-09-22T14:01:56Z<p>RChandra: /* Phi */ cp ed</p>
<hr />
<div>[[File:Early-Phi-screen shot.PNG|thumb|right|Early Phi screenshot]]<br />
<br />
== Phi ==<br />
<br />
'''Phi''' is an HTML5/JavaScript/CSS based multi-platform user interface and instructor station. The implementation uses some state-of-the-art JavaScript libraries, most notably jQuery, knockoutjs and requirejs (files included for offline usage). Phi is capable of being run on any device that has a Web browser or Web apps like Apple's iPad without the browser decorations. See [[Phi#Usage | Usage]] section below for further details.<br />
<br />
== Background ==<br />
<small>''Direct quotes from '''Torsten'''. Original '''Phi''' developer''</small><br />
<br />
While working on the new radio/atis implementation, I rediscovered the internal httpd (aka web-server) to browse the property tree. It's much easier to have multiple browser windows open and point to various locations in the property tree than to reopen the internal property browser and navigate to the locations after each sim restart. After a while, I got disappointed by the functionality, look, and feel of the http property-browser. So I had a look at the code to see if it could be improved. I quickly realized, that the implementation was simple but not scale-able. I looked for alternatives already available on the GPL market. I found Mongoose as a well maintained, feature rich and yet simple implementation of a web server and started to embed that into FlightGear.<br />
<ref>[http://sourceforge.net/p/flightgear/mailman/message/32068663/ Initial motivation]</ref><br />
<br />
'''''FI''''' = Flight Instructor (you sure know that), or FlightGear Interface. In Deutsch (my native language) the spoken '''''FI''''' sounds like the Greek letter Phi. And I like the uppercase letter of Phi for it's symmetry. It's vertical bar reminds me of the projector screen in a simulator, watched from both sides: the trainer and the trainee. For the less philosophical meanings of Phi, check out {{wikipedia|Phi}} and pick the one that suits best ;-)<br />
<ref>[http://sourceforge.net/p/flightgear/mailman/message/33347855/ Why Phi?]</ref><br />
<br />
== Usage ==<br />
==== Qt5 Launcher ====<br />
{{Main article|Integrated Qt5 Launcher}}<br />
To use Phi you need to start the internal httpd server before FlightGear is started. The easiest way to do this is using the built-in Qt5 launcher and add the following line to '''Settings > Additional options'''.<br />
<br />
<br />
[[File:Phi launcher option.PNG|300px|Qt5 launcher option for Phi]]<br />
<br />
==== FFGo ====<br />
{{Main article|FFGo}}<br />
Add the --httpd command switch somewhere in the config file. <br />
<br />
<br />
[[File:FFGo launcher.PNG|300px|FFGo launcher]]<br />
<br />
==== Console ====<br />
run fgfs with the command line switch --httpd Example.<br />
fgfs --httpd=8080<br />
<br />
<br />
Once FlightGear is up and running we can access the Phi user interface from the main menu in FlightGear. '''Select Equipment > Map (opens in browser)''' or launch a web browser and enter the URL <br />
http://localhost:8080<br />
<br />
== Phi UI Features ==<br />
Phi is at foremost a multi-platform user interface that has two-way data binding with FlightGear via the internal HTTP web server. This allows Phi to be a fully functional user interface that can directly control FlightGear. The following list is a set of features that are currently implemented and working.<br />
=== Aircraft ===<br />
This is where you will find all things related to the currently selected aircraft in-sim, if available. <br />
*'''Help''' - Displays the aircraft help file '''Help > Aircraft Help'''<br />
*'''Mass & Balance''' - Displays aircraft specific fuel and payload options '''Equipment > Fuel and Payload'''<br />
*'''Checklist''' - Displays aircraft checklist '''Help > '''<br />
*'''Failures''' - <br />
*'''Panel''' - <br />
*'''Select''' - ''Known bug in FG for windows versions 7+, assume this feature to not work anytime soon even if you see a list of planes to install''<br />
=== Environment===<br />
*'''Date & Time''' - Change in-sim time of day and current date<br />
*'''Weather''' - <br />
*'''Position''' - Interface where you can search for airports via ICAO codes and then select a runway/parking spot to load into FlightGear '''Location > Select Airport'''<br />
=== Map ===<br />
Loads an OpenStreetMap as the background and updates your current position around the world in real time while you fly. Allows one to not only track current flight, but the ability to drag the plane icon around the map which will instantly update FlightGear with the new lon. and lat. coordinate position. <br />
=== Tools===<br />
Things that make for a more realistic experience. Not exactly needed to fly a plane, but these tools will add to the realism.<br />
*'''Holding Pattern''' - A tool to help one understand how to enter the holding pattern. Enter in the Heading and Inbound Track and the diagram will show you visually the Holding pattern.<br />
*'''Wind Calculator''' - <br />
*'''Vertical Navigation (VNAV)''' - ''from my understanding not anytime soon, needs FG integration first''<br />
*'''Stopwatch''' - Self-explanatory<br />
=== Simulator ===<br />
*'''Screenshot''' - Set the time between screen updates. See [[Phi#Screen Shots]]<br />
*'''Properties''' - In-sim property tree, two-way data binding, good for debugging!<br />
*'''Config''' - In-sim config settings<br />
**'''AI''' - Enable/Disable AI<br />
**'''Multi-Player''' - Enter callsign and select which server to connect to on the multi-player network.<br />
*'''Reset''' - Reset the FlightGear Sim<br />
*'''Exit''' - Quit<br />
<br />
=== Property Plotter ===<br />
You find the property plotter here: <br />
* start fgfs with --httpd=8080 (or any other port) <br />
* open browser at http://yourfgmachine-or-localhost:8080/ <br />
* click Tab "Simulator" <br />
* Select button "Properties" <br />
* Navigate the property tree to the property of interest <br />
* click the little image symbol just left of the properties value <br />
* you have your plot The code lives in $FGDATA/data/Phi/topics/Simulator/Properties.[js|html] <br />
<br />
You need some background knowledge of http://knockoutjs.com/ (HTML data binding) and http://www.flotcharts.org/ (Chart drawing) Let Torsten know if you need some more information <ref>{{cite web<br />
|url = https://sourceforge.net/p/flightgear/mailman/message/35591702/ <br />
|title = <nowiki> Re: [Flightgear-devel] fgplot / currently active canvas developers? </nowiki> <br />
|author = <nowiki> Torsten Dreyer </nowiki> <br />
|date = Jan 8th, 2017 <br />
|added = Jan 8th, 2017 <br />
|script_version = 0.40 <br />
}}</ref><br />
<br />
== Screen Shots ==<br />
You can access the new screenshot handler after starting FlightGear per instructions here [[Phi#Usage|Usage]] <br />
http://localhost:8080/screenshot<br />
<br />
It understands some request parameters:<br />
<br />
*'''type:''' either png or jpg (guess what this does)<br />
<br />
*'''window:''' the name of the window to capture (for those with multi screen setups)<br />
<br />
*'''stream:''' provide mjpeg stream<br />
<br />
===Examples:===<br />
==== Single screenshot ====<br />
send png instead of jpg (jpg is default)<br />
http://localhost:8080/screenshot?type=png<br />
send a png screenshot from the window named "WindowA" as defined under <br />
rendering/camera-group/window/name in your screen configuration.<br />
http://localhost:8080/screenshot?type=png&window=WindowA<br />
use default jpg encoding<br />
http://localhost:8080/screenshot?window=WindowA<br />
==== Motion-jpeg ====<br />
Send a motion-jpeg encoded video stream.<br />
http://localhost:8080/screenshot?window=WindowA&stream=y<br />
Can be used by ffmpeg to directly encode various video formats.<br />
ffplay -f mjpeg http://localhost:8080/screenshot/stream=y<br />
<br />
Compression level for PNG is hardcoded to 9 (highest) and JPEG_QUALITY hardcoded to 80. These seem to be a good balance of performance vs. quality<br />
<br />
== Web-based EFIS ==<br />
The web-based EFIS is created from a scale-able vector graphics (svg), is animated by JavaScript and driven by properties from FlightGear over websockets. The same svg files that are used for the FlightGear internal canvas based instruments can also be used for the browser based display, so both instruments (that of the 3d model and that in your browser) look 100% alike. Web-socket properties are exchanged at frame rate making animations as smooth as they can get. Because it uses SVG, instruments are always rendered at the highest available resolution of the device without scaling artifacts.<br />
<ref name="HelloFGP2.0">[http://sourceforge.net/p/flightgear/mailman/message/32840486/ Goodbye fgPanel, Hello fgPanel 2.0]</ref><br />
<br />
The most exciting part is, the web based instrument runs on any modern platform without the need to install any spooky software. It also runs flawless on my Android phone and tablet and of course in a standard browser (Firefox and Chrome tested). On mobile OSes, you can add it to your home screen, making this a full-screen web-app to get rid of the browser navigation and toolbar (like shown in the screenshot). There is not much required on the FlightGear side - recent 2016.1.1 has all it needs. Workload for FlightGear is negligible, for the current EFIS, on page load a few hundred kilobytes of static files are transmitted and once fully loaded, 10 (ten!) properties are observed and transmitted on change. All the rendering takes place on the web browser's device.<br />
<ref name="HelloFGP2.0"></ref><br />
<br />
Probably, a video is more descriptive, here is a shot of an earlier (incomplete) version:<br />
<br />
{{#ev:youtube|sYM7uiWIprc}}<br />
<br />
You can see a FlightGear instance on the top right of the big monitor and Firefox on the left showing the EFIS. Both run on the same computer. Below the monitor are an old iPod touch (left) and a Nexus 7 (right), both running the EFIS as a web-app in full screen mode connected over WLAN. The EFIS in the FlightGear window is based on Canvas/Nasal. The other EFISes are 100% Nasal free, just HTML/SVG/CSS/JavaScript<ref>[http://sourceforge.net/p/flightgear/mailman/message/32840980/ Video reference]</ref><br />
<br />
=== Making Web-Panel instruments ===<br />
{{Note| This section should be considered unfinished. If you have something to add, please do so}}<br />
I use Inkscape to draw the SVGs. The objects to animate are selected by their id attribute, so you should set a reasonable name for those. To get proper scaling of the SVGs, you need to set the viewBox: width, <br/><br />
height, and preserveAspectRation of the <svg> tag element. It should be also possible to draw SVG's on the fly e.g. from svg.js and animate this as well. Not much has been on this front.<br />
<ref name="HelloFGP2.0"></ref><br />
<br />
==== Examples ====<br />
Here you can find code examples that have been added to the Phi project<br />
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/<br />
The Horizon example is a fat free, stripped down basic idea of a web based instrument for Phi.<br />
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.html<br />
https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Phi/examples/horizon.js<br />
<br />
== Future Development ==<br />
{{Note|Nothing concrete}}<br />
*improve the aircraft specific plugin system to allow special widgets and pages for aircraft (thinking of the shuttle here)<br />
*make layout and theme configurable<br />
*keep settings persistent between sessions<br />
*write a tile renderer to create map tiles from scenery<br />
*better support for touch events<br />
*together with ThorstenR: UI to configure a 3d weather model<br />
<br />
== References ==<br />
{{Appendix}}<br />
<br />
[[Category:Cockpit building]]<br />
[[Category:GUI]]</div>RChandrahttps://wiki.flightgear.org/w/index.php?title=FlightGear_logos&diff=107559FlightGear logos2017-04-02T14:06:34Z<p>RChandra: /* 3D logotype */ cp editing</p>
<hr />
<div>Feel free to add your FlightGear logo(s) here.<br />
<br />
== Official logo ==<br />
=== 2011 - Present ===<br />
[[File:FlightGear logo.png]]<br />
<br />
; Author: {{usr|Gijs|Gijs de Rooy}}, based on original icon.<br />
; License: GNU GPL v2<br />
{{inote|There is also an {{fgdata file|Docs/img/FlightGear_logo.svg|t=SVG version}} of this logo (added by {{fgdata commit|ef898e}}).}}<br />
<br />
=== 2000 - 2011 ===<br />
[[File:Fglogosm.jpg]]<br />
<br />
; Author: Michael Smith <ref>{{Cite web<br />
|url = http://flightgear.org/thanks.shtml<br />
|title = http://flightgear.org/thanks.shtml<br />
}}</ref><br />
; Source: http://www.flightgear.org/ ([http://www.flightgear.org/legacy.shtml legacy])<br />
<br />
=== Until 2000 ===<br />
[[File:Fglogosm_old1.jpg]]<br />
<br />
; Author: Unknown, uploaded by {{usr|Gijs}}<br />
; Source: http://www.flightgear.org/ ([http://web.archive.org/web/19981212014011/http://flightgear.org/ archive])<br />
<br />
== A-10 Logo ==<br />
<br />
[[File:Wiki_logo.png]]<br />
<br />
* Author: Wes Summers<br />
* License: http://creativecommons.org/licenses/by-sa/3.0/<br />
* Source: [[Media:A-10_logo.pdf| Illustrator PDF]]<br />
<br />
== New Test Logo ==<br />
[[File:Flightgear-logov2.png]]<br />
<br />
* Author: BBCTV (Japanese Flightgear User)<br />
* License: Copyright Flightgear<br />
* Source: Made with Adobe Illustrator<br />
<br />
== Set of logos for Wiki ==<br />
<br />
[[File:Fg_trails_lc.png]] [[File:Fg_wings_large.png]] [[File:Fg_wings_up.png]] [[File:Fg_trails_large.png]]<br />
<br />
* Author: Wes Summers<br />
* License: http://creativecommons.org/licenses/by/3.0/<br />
<br />
== 3D logotype ==<br />
[[File:FG happy new year 2.png]]<br />
<br />
* Author: Roman Alvarez<br />
* Source: made with Cinema 4D and GIMP<br />
<br />
== Badge Logo ==<br />
<br />
[[File:Fglogo1.png]] [[File:Fglogowiki.png]][[File:Fglogoforum.png]]<br />
<br />
* Author: Michat<br />
* License: OFFGU. Only for FG (Flightgear) users. FlightGear users only.<br />
<br />
== FG Eagles Haunting Logo Motive ==<br />
<br />
[[File:FGMotive.png|left|FG Eagles Haunting logo motive]]{{-}}<br />
<br />
* FG Eagles Haunting logo motive<br/><br />
<br />
== The F of FlightGear ==<br />
<br />
<br />
[[File:Fglogo3baja.png|150px|The Flightgear's F (dont search the X just try the F)72spi - Also available in 300dpi high quality for printing purposes]]{{-}}<br />
<br />
* The F of FlightGear is also available in high resolution for printing. [http://wiki.flightgear.org/File:Fglogo3alta.png Get Badged as FGSuperHero Now]<br/><br />
<br />
== FGType Logo Motive Spread the word * ==<br />
[[File:Fglogo2baja.png|150px|FGType with a Waterman "Stylo" to Inkscape adventure]]{{-}}<br />
<br />
* FG is the Free and Open Flight Simulator<br />
* FGType with a Waterman "inkLeak Stylo" to Inkscape adventure to the conquer of the FontForge<br />
* Author: Michat de La Fontaine<br />
* License: OFFGU. Only for FG (Flightgear) users. FlightGear users only.<br />
<br/><br />
<br />
== FGsprite ==<br />
<br />
[[File:Fglogothesprite.png|FGSprite]]<br />
<br />
* Author: Michat<br />
<br />
== Equiped and Ready logos ==<br />
<br />
[[Image:Tutorialready.png|link=Tutorials]]<br />
[[Image:Checklistready.png|link=Aircraft Checklists]]<br />
[[Image:Routemanagerready.png|link=Route Manager]]<br />
[[Image:Airrefuelingready.png|link=Howto:Aerial refueling]]<br />
[[Image:Rembrandtready.png|link=Rembrandt]]<br />
[[Image:Spacetripready.png|link=Category:Spaceflight]]<br />
[[Image:Tooltipready.png|link=Tooltips]]<br />
<br />
* Author:Michat<br />
* ''"Tooltip Ready"'' graphics derived from and added by mhab<br />
* License: OFFGU. Only for FG (Flightgear) users. FlightGear users only.<br />
<br />
== Alternative ready logos == <br />
[[Image:Airrefuel-ready.png|link=Howto:Aerial refueling]]<br />
[[Image:Bombable-ready.png|link=Bombable]]<br />
[[Image:Canvas-ready.png|link=Canvas]]<br />
[[Image:Checklist-ready.png|link=Aircraft Checklists]]<br />
[[Image:Dualcontrol-ready.png|link=Dual Control]]<br />
[[Image:Rembrandt-ready.png|link=Rembrandt]]<br />
[[Image:Space-ready.png|link=Category:Spaceflight]]<br />
[[Image:Tutorial-ready.png|link=Tutorials]]<br />
<br />
* Author: {{usr|Bugman}} (Space-ready.png), {{usr|Red Leader}} (all the others)<br />
* License: '''[http://creativecommons.org/licenses/by-sa/4.0/deed.en CC-BY-SA-4.0]''' (Space-ready.png), '''[http://creativecommons.org/licenses/by-sa/3.0/deed.en CC-BY-SA-3.0]''' (all the others)<br />
<br />
== Desktop Backgrounds ==<br />
<br />
[[File:FGBGBG.png|left|300px|1024x768 Mulberry + FG Fosfo bug]]<br />
[[File:Fgorangefeather.png|300px|1024x768 FG Feather Orange]]<br />
[[File:Fgbg.png|300px|1024x768 BLUE Super Relax Recommended]]<br />
[[File:1024x768softuserblack2.png|300px|Desktop Background]]<br />
<br />
<br />
[[File:1024x768softuserblack3.png|300px|Desktop Background]]<br />
[[File:1024x768softuserblack4.png|300px|Desktop Background]]<br />
[[File:1024x768softuserblack5.png|300px|Desktop Background]]<br />
[[File:1024x768softuserblack6.png|300px|Desktop Background]]<br />
<br />
[[File:Lakeofconstance2.png|300px|Lake of Constance FG B-707 Background]]<br />
<br />
== FG Stripes ==<br />
[[File:172P 01.jpg|300px|FG Stripes]]<br />
[[File:172P 02.jpg|300px|FG Stripes]]<br />
[[File:172P 03.jpg|300px|FG Stripes]]<br />
<br />
[[File:172P 04.jpg|300px|FG Stripes]]<br />
[[File:172P 05.jpg|300px|FG Stripes]]<br />
[[File:172P 06.jpg|300px|FG Stripes]]<br />
<br />
[[File:172P 07.jpg|300px|FG Stripes]]<br />
[[File:172P 08.jpg|300px|FG Stripes]]<br />
[[File:172P 09.jpg|300px|FG Stripes]]<br />
<br />
[[File:172P 10.jpg|300px|FG Stripes]]<br />
[[File:172P 11.jpg|300px|FG Stripes]]<br />
<br />
<br />
[[Category:FlightGear]]<br />
<br />
{{Appendix}}</div>RChandrahttps://wiki.flightgear.org/w/index.php?title=Weather_reports&diff=107278Weather reports2017-03-05T17:30:15Z<p>RChandra: /* Explanation */ occurence (spelling)</p>
<hr />
<div>In aviation it is very important to be able to exchange weather information rapidly and unambiguously. To solve this problem, some standards have been defined by international organizations to exchange codified '''weather reports'''.<br />
<br />
== METAR ==<br />
A METAR is a codified observation message indicating an airfield weather conditions observed at a given time. There are different ways of messaging weather reports, but in [[FlightGear]] METAR is used. The data is retrieved from [http://weather.noaa.gov/weather/metar.shtml NOAA]. Such a message is established every hour.<br />
<br />
The METAR-message can be found and set in the dialog ''Environment > [[Weather]] Conditions''. To have the actual weather (or playing with [[ATC]]) you need to enable the Real weather fetch in the [[FlightGear Wizard]], or set the Weather conditions to ''Live data'' in the very same dialog.<br />
<br />
=== Explanation ===<br />
'''Example:''' <br />
{| class="wikitable" <br />
|2008/03/15 12:24 || KSFO || 151224Z || 05012KT || 10SM || SN || BKN050 || 02/M08 || A3016 || RMK AO2 SLP228 || T00221083<br />
|- <br />
|1 || 2 || 3 || 4 || 5 || 6 || 7 || 8 || 9 || 10 || 11<br />
|}<br />
<br />
# Date<br />
# ICAO Identifier (4-letter)<br />
# Issuance Time DDHHMMz (UTC) <br />
#* COR (CCD in Canada) if correction to observation<br />
# Wind<br />
#* First 3 digits: True Wind direction or average if variable (VRB).<br />
#** Note: If the wind direction varies 60° or more, the direction will be indicated with a V (e.g. 180V250)<br />
#* Next 2 digits: Mean speed and units<br />
#** KT=knots, KMH=kilometers/hour, MPS=meters/second<br />
#* G (gust) as needed – 2 or 3 digit maximum speed<br />
#* Calm will be indicated by 00000KT<br />
#* Example: 18012G22KT 150V240<br />
# Horizontal Visibility<br />
#* Prevailing Visibility (PV)<br />
#** Statue miles (SM) and fractions (US & Canada only) or,<br />
#** 4 digit minimum visibility in meters, and, <br />
#** Lowest value and direction, as required (shown as a remark)<br />
#* Runway Visual Range (RVR)<br />
#** R: Runway Designator, L/R/C as needed, “/”<br />
#** P/M: Plus/Minus (US only)<br />
#** 4 digit value (feet/meters)<br />
#** V (variability) with tendency U/D/N (up/down/no change)<br />
#** Example: R18R/1200FTV/U<br />
# Present Weather (Constructed sequentially):<br />
#* Intensity<br />
#* Descriptor<br />
#* Precipitation (Dominant type is listed first if more than one type reported)<br />
#* Obscuration<br />
#* Other<br />
# Sky Cover<br />
#* Cloud Description<br />
#** Amount in eights (octas)<br />
#** SKC=Sky Clear (clear below 12,000 for ASOS/AWOS)<br />
#** NSC=No significant clouds<br />
#** FEW=Few (1/8 to 2/8 sky cover)<br />
#** SCT=Scattered (3/8 to 4/8 sky cover)<br />
#** BKN=Broken (5/8 to 7/8 sky cover)<br />
#** OVC=Overcast (8/8 sky cover)<br />
# Temperature/Dewpoint (whole °C) (preceded by M=minus)<br />
#* First 2 digits = temperature<br />
#* Second 2 digits = dewpoint<br />
# Altimeter setting (QNH) and indicator (A=InHg, Q=hPa)<br />
# Supplementary Information<br />
#* RE = Recent weather followed by weather codes<br />
#* WS = Windshear, followed by:<br />
#** TKOF/LDG (takeoff/landing)<br />
#** RWY (2 digits runway identifier and designator L/R/C)<br />
#* RMK = Remark<br />
#** SLP = Sea Level Pressure<br />
#** T00221083 (Expanded temp/dewpoint) <br />
#** 1st, 5th digits: 0=plus, 1=minus<br />
#** 2nd-4th digits: temp (decimal missing) (02.2)<br />
#** 6th-8th digits: dewpoint (decimal missing) (-8.3)<br />
# Trend Forecast (2 hours from time of observation) (Not used in US)<br />
#* PROB and 2 digits (30 or 40) = probability 30% or 40%<br />
#* Used to indicate the probability of occurence of alternate element(s) or temporary fluctuations<br />
#* Change Indicator<br />
#** BECMG = Becoming (used where changes are expected to reach or pass through specified values<br />
#** TEMPO = Temporary (fluctuations of less than one hour duration<br />
#** NOSIG = No significant change<br />
#* Forecast Wind (same as item 4)<br />
#* Forecast Visibility (as item 5) (9999 indicates 10Kilometers vis or greater)<br />
#* Forecast Weather (as item 6)<br />
#* Forecast Cloud (as item 7)<br />
<br />
== TAF ==<br />
In meteorology and aviation, TAF is a format for reporting weather forecast information, particularly as it relates to aviation. "TAF" is an acronym of Terminal Aerodrome Forecast or, in some countries, Terminal Area Forecast. Generally, TAF's can apply to a 9- or 12-hour forecast; some TAFs cover an 18- or 24-hour period; and as of November 5,2008, TAFs for some major airports cover 30 hours periods. The date/time group reflects the new 30 hour period in Coordinated Universal Time (UTC), as always.<br />
<br />
== See also ==<br />
* [[Weather]]<br />
<br />
== External Links ==<br />
* [http://aviationweather.gov/static/help/taf-decode.php Decoding a TAF]<br />
<br />
[[Category:Weather]]<br />
<br />
[[es:METAR]]</div>RChandrahttps://wiki.flightgear.org/w/index.php?title=Cessna_172P&diff=107235Cessna 172P2017-03-01T01:55:07Z<p>RChandra: /* Landing */ touchdown -> touch down</p>
<hr />
<div>{{:{{PAGENAME}}/info}}<br />
The '''Cessna 172P ''Skyhawk''''' is a four-seat, single-engine, high-wing fixed-wing [[aircraft]]. First flown in 1955 and still in production, more Cessna 172s have been built than any other aircraft.<br />
<br />
A C172 has been the default aircraft in [[FlightGear]] since 2000, when it replaced the [[Navion]]. It has had a long development and includes a wide variety of simulation features. In 2015, it went through a complete refresh, including engine options, various tire sizes and floats, as well as a complete cockpit texture makeover. This new detailed version of the plane has become the default aircraft since [[Changelog_3.6|FlightGear 3.6]].<br />
<br />
== Features ==<br />
<br />
The new C172p has a much better 3D model and is now fully textured (including the interior). All the switches in the cockpit are clickable. It also has an improved FDM, more complex procedures and new realistic checklists, new sound effects, and damage modelling. The aircraft can get damaged if mishandled (e.g. gear collapse after a hard landing).<br />
<br />
[[File:C172p-bodensee-panorama.jpg|center|800px]]<br />
<br />
The aircraft currently has five variants, all available from the aircraft menu:<br />
* regular wheels<br />
* 26" bush tires<br />
* 31" bush tires<br />
* pontoons<br />
* amphibian<br />
* snow skis<br />
<br />
Also, from the same menu, the user can select two different engines:<br />
* 160 HP<br />
* 180 HP (recommended when using pontoons, amphibian and skis variants)<br />
<br />
The aircraft now can get damaged from collisions, crashes, hard landings or overload while in-flight, and the modelling includes wheel collapse, wings breaking, etc. The damage can be turned off in the aircraft menu, which also contains an option for repairing the aircraft.<br />
<br />
The windows now can get foggy or frosty, depending on the combination of interior and exterior temperatures. The pilot must then use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. Alternatively, it's possible to disable the effect in the "Aircraft Options" in the "Cessna 172P" menu. This effect depends on the new ALS effects found in 3.5 and above, and will also have the side effect of producing grey windows in versions prior to 3.5.<br />
<br />
The FDM has also been modified. The aircraft may enter into a spin in case of an asymmetric stall (a particularly dangerous situation when turning to final, in which case the aircraft is at low speed and low height). The FDM has also been tweaked to include hydrodynamics effects while taking off or landing on water, as well as adding a new 180 HP engine.<br />
<br />
There are several liveries available, some of which have higher resolution than others, which are marked as HD in the liveries menu. Each of the HD liveries also has unique cockpit and interior textures.<br />
<br />
The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].<br />
<br />
Also, if the user has enabled ALS (Atmospheric light scattering) in the Rendering Options, then it's possible to activate the flashlight by clicking on the "Cessna 172P" menu and selecting "Flashlight". Select it once for the white flashlight, select it again for a red one and select it one more time to turn it off.<br />
<br />
The aircraft can now go through a pre-flight: wheel chocks, tie-downs and the pitot tube cover can now be added or removed, oil management and fuel contamination by water have been implemented (both of which are not activated by default, but are available in the Aircraft Options dialog).<br />
<br />
Carburettor icing is also modelled. Accumulating carburettor ice will result in loss of power. Applying carb heat will help to melt it. If the engine starts to cough when carb heat is applied, it means that ice has indeed been accumulated in the carburettor and now is being melt. To reduce the cough during the melting process, one can lean the mixture. <br />
<br />
As of version 2016.3, static objects can be toggled in the Ground Equipment dialog. These include cones under the wings, a fuel truck, a ground power unit and ladders. The ground power can be used to recharge the battery and the fuel truck can be used to refuelling the tanks. The walker can climb the ladder by walking towards it, which makes it easy to access the fuel tank cap in order to refill it.<br />
<br />
[[File:c172p-ALS-flashlight2.jpg|500px|center|Cessna 172P's flashlight in the cockpit]]<br />
<br />
== Handling The Aircraft ==<br />
<br />
=== Pre-Flight Inspection ===<br />
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]<br />
It's recommended to use any exterior view or activate the walker for these procedures.<br />
* Fuel quantity: add by clicking on the fuel tank caps above each wing (you can add a ladder in the Ground Equipment dialog and climb it with the walker as well)<br />
* Left wing: remove tie-down<br />
* Left wing: remove pitot tube cover<br />
* Left wing: check for fuel contamination by clicking under the wing and take a fuel sample. If the sample is light blue, the fuel is not contaminated and can be returned to the tank. If the sample is transparent or partially transparent, you must discard it and take new samples until they are completely light blue<br />
* Tail: remove tie-down<br />
* Right wing: remove tie-down<br />
* Right wing: check for fuel contamination<br />
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.<br />
* Nose: remove wheel chocks<br />
<br />
=== Engine Start (manual and complex startup) ===<br />
* Priming: prime the engine at least 3 times<br />
* Mixture: Rich (red lever all the way in)<br />
* Throttle: Open 1/8 (black lever at 20%)<br />
* Parking Brake: Applied ({{Key press|Shift|B}})<br />
* Prop Area: Clear<br />
* Master switch: ON (both)<br />
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)<br />
* Ignition: Start ({{Key press|S}})<br />
<br />
=== Engine Start (automatically with Autostart) ===<br />
* Click on the menu "Cessna C172P" and select "Autostart" in order to start the plane. Please note that the Autostart attempts to start the engine with the mixture full rich, so if you are taking off from a very high altitude airport you may need to manually start the plane.<br />
<br />
=== Takeoff ===<br />
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]<br />
* no flaps<br />
* full throttle<br />
* rotate at 55 KIAS<br />
<br />
=== Climbout ===<br />
* no flaps<br />
* full throttle<br />
* 75 KIAS<br />
<br />
=== Cruise ===<br />
* throttle 65%<br />
* mixture rich of peak<br />
* speed around 100 knots<br />
<br />
=== Landing ===<br />
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touch down]]<br />
* full flaps<br />
* 60 KIAS<br />
<br />
=== Airspeeds ===<br />
: ''See also [[Aircraft speed#V speeds]]''<br />
<br />
The information in this section is based on external resources.<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref><br />
<br />
{| class="wikitable"<br />
! Airspeed !! CAS<br />
|-<br />
| Stall speed, landing configuration, V<sub>S<sub>0</sub></sub> || 33 kt<br />
|-<br />
| Stall speed, clean, V<sub>S<sub>1</sub></sub> || 44 kt<br />
|-<br />
| Rotation speed, V<sub>R</sub> || 55 kt<br />
|-<br />
| Best angle of climb speed, V<sub>X</sub> || 59 kt<br />
|-<br />
| Best rate of climb speed, V<sub>Y</sub> || 76 kt<br />
|-<br />
| Maximum flap extended speed, V<sub>FE</sub> || 85 kt<br />
|-<br />
| rowspan="2" valign="top" | Maneuvering speed, V<sub>A</sub> || 96 kt (floatplane)<br />
|-<br />
| 99 kt (landplane)<br />
|-<br />
| Maximum structural cruising speed, V<sub>NO</sub> || 127 kt<br />
|-<br />
| Never exceed speed, V<sub>NE</sub> || 158 kt<br />
|}<br />
<br />
== FAQ ==<br />
<br />
Here are some of the frequently asked questions about this aircraft:<br />
<br />
<br />
'''Q:''' I am experiencing grey windows, what is happening?<br />
<br />
'''A:''' If you experience grey windows, you do not have the correct FlightGear version. This aircraft requires 3.5 or above.<br />
<br />
<br />
'''Q:''' Why does the aircraft keep turning left?<br />
<br />
'''A:''' Please see [[understanding Propeller Torque and P-Factor]]. If using the amphibian model on a solid runway, note that at the taxiing is done by differential braking (the rudder becomes more and more effective as the plane gains speed).<br />
<br />
<br />
'''Q:''' Why will the engine not start?<br />
<br />
'''A:''' You can start the engine automatically by clicking on the menu "Cessna C172P" and selecting "Autostart". For a manual start, please follow the checklists available by clicking on the menu "Help" followed by "Aircraft Checklists". As seen above, the engine must by "primed" before starting. If oil management is activated, you must have enough oil for the engine to work (more than 5.0 quarts). If fuel contamination is activated, the fuel must be light blue in order for the engine to properly work. You must also make sure that the battery is charged enough (you can check and recharge it in the Aircraft Options dialog).<br />
<br />
<br />
'''Q:''' Why does the Autostart fail to start the engine?<br />
<br />
'''A:''' That's probably because you are attempting to take off from a very high altitude airport. Autostart always tries to start the engine with the mixture full rich, and if it fails to do that properly then you must manually start the engine after properly leaning the mixture.<br />
<br />
<br />
'''Q:''' Why does the engine die immediately after startup?<br />
<br />
'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.<br />
<br />
<br />
'''Q:''' Why can't I start the sim with the engine running?<br />
<br />
'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".<br />
<br />
<br />
'''Q:''' Why I keep running out of battery?<br />
<br />
'''A:''' Just like in the real airplane, it's always a bad idea to keep the battery switch on for a long time while the engine is not running, as the battery will run out of charge. When the engine is running, the alternator will make sure that the battery is always recharging. If you run out of battery charge, go to the Aircraft Options dialog and recharge it.<br />
<br />
<br />
'''Q:''' Why the aircraft doesn't move?<br />
<br />
'''A:''' The aircraft won't move if you have the parking brakes set, or if either of the wing tie-downs, the tail tie-down or wheel chocks are in place (if the option "allow securing aircraft" is enabled in the aircraft menu).<br />
<br />
<br />
'''Q:''' Why the airspeed indicator doesn't work?<br />
<br />
'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.<br />
<br />
<br />
'''Q:''' How can I switch to the bush tires/pontoons/amphibian?<br />
<br />
'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.<br />
<br />
<br />
'''Q:''' How can I switch to the 180 HP engine?<br />
<br />
'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.<br />
<br />
<br />
'''Q:''' Why can't I take off from the water without crashing the plane?<br />
<br />
'''A:''' Taking off and landing on water can be quite tricky. Try applying a little bit of back pressure on the yoke while accelerating to 55 KIAS. It's also recommended to use the 180 HP engine instead of the default 160 HP, as the extra weight of the pontoons make it really hard to climb with the default engine.<br />
<br />
<br />
'''Q:''' Why is the simulator lagging so much?<br />
<br />
'''A:''' As with any complex 3D model, this new version of the c172p is a bit more demanding on the computers than the older one. If you are having troubles with performance, try using non-HD liveries which use textures with lower resolutions, as well as other solutions that can improve performance (disabling certain graphical options in the Rendering Options, lowering the resolution of FlightGear, etc.).<br />
<br />
Some tricks that help to increase fps is by disabling all GUI windows, including the menu bar and the orange fps counters at the bottom of the screen. You can display an alternative fps counter in the top left corner via the "Debug" menu and then selecting "Cycle On-Screen Statistics". Make sure to hide the menu bar by pressing F10 to see the counter.<br />
<br />
A second trick is to simply disable the rendering of all clouds if you don't mind. Start FlightGear with "--prop:/sim/rendering/draw-mask/clouds=0".<br />
<br />
If you notice heavy slowdowns when flying over certain scenery and you see FlightGear generating many "Warning:: Picked up error in TriangleIntersect" messages in the terminal or log file, you can disable this by starting FlightGear with "--prop:/sim/rendering/osg-notify-level=fatal".<br />
<br />
<br />
'''Q:''' Why are the windows getting foggy/frosty?<br />
<br />
'''A:''' If the dew point of the cabin air temperature is higher than the surface temperature of the windshield, the windows will get either foggy or frosty. Use the Cabin Heat and Cabin Air levers (on the right of the flaps) to control it. The dew point rises with the temperature in the cabin, and it rises faster than the windshield temperature can adjust, resulting in temporary fog. If the air is very humid, the dew point is going to be very close to the cabin temperature, which makes it likely that it will be higher than the windshield temperature. Extra passengers will create a more humid atmosphere in the cabin. Try to increase air flow using the Cabin Air lever or overhead air vents in order to decrease the humidity or temperature. Alternatively, disable the effect by going to the menu "Cessna 172P", selecting "Aircraft Options" and disable the option "Enable frost and fog".<br />
<br />
<br />
'''Q:''' How do I increase the cabin air temperature?<br />
<br />
'''A:''' Increase the cabin air temperature by opening the Cabin Heat lever. In order to actually get a heated air flow, you need a medium or high EGT (Exhaust Gas Temperature -- the instrument between the yoke and the ADF instrument), and airspeed and/or sufficient propeller RPM.<br />
<br />
<br />
'''Q:''' How can I click on a switch which is being covered by the yoke?<br />
<br />
'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".<br />
<br />
<br />
'''Q:''' Why my engine seems to be losing power?<br />
<br />
'''A:''' Assuming that you have the mixture correctly leaned according to your altitude and atmospheric pressure, then another possibility is that you are accumulating carburettor ice which results in loss of power. Apply carb heat and the ice should slowly melt. Notice that if the engine starts to cough when you apply carb heat, it means that ice is being melt and is a sign that icing was indeed your problem. To reduce the cough during the melting process, lean the mixture.<br />
<br />
== Development status/Issues/TODO ==<br />
<br />
This aircraft is undergoing a constant development, which can be followed on its [https://github.com/Juanvvc/c172p-detailed repository], where a [https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements] can also be found.<br />
<br />
== Gallery ==<br />
<br />
<gallery mode="packed"><br />
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil<br />
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)<br />
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit<br />
c172p-floats.jpg|Float variant in San Francisco<br />
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy<br />
c172p-landing.jpg|On final at Aosta Airport (LIMW)<br />
c172p-cockpit3.jpg|The fully textured interiors of the new c172p<br />
c172p-night.jpg|A night flight, showing the instrument illumination<br />
c172p-particles.jpg|Taking off on water, showing the particle system<br />
c172p-plane1.jpg|Above Serra do Mar in Brazil<br />
c172p-plane2.jpg|Flying at sunset<br />
c172p-winter.jpg|European winter<br />
c172p-damage.jpg|Gear collapse due to heavy landing<br />
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows<br />
c172p-taubate.jpg|Flying above Taubate, Brazil<br />
<br />
</gallery><br />
<br />
== External links ==<br />
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]<br />
* [http://www.atlasaviation.com/checklists/cessna-172/cessna_172_checklist.htm Cessna 172 checklists at AtlasAviation.com]<br />
<br />
{{Appendix}}<br />
<br />
{{Cessna}}<br />
<br />
[[Category:Aircraft with a cockpit-only autopilot]]<br />
<br />
[[de:Cessna 172P]]<br />
[[es:Cessna 172P]]<br />
[[fr:Cessna 172P]]<br />
[[zh:Cessna 172P]]</div>RChandrahttps://wiki.flightgear.org/w/index.php?title=New_to_FlightGear&diff=107069New to FlightGear2017-02-24T03:22:46Z<p>RChandra: /* How you can help */ fix ideas/suggestions randomcaps</p>
<hr />
<div>'''Welcome to [[FlightGear]]!''' Here we'll try to get you up in the virtual air in the shortest time possible. We'll also introduce you to some of the features of this flight simulator and also a few information on its community.<br />
<br />
== Installation and setup ==<br />
=== Hardware requirements ===<br />
For FlightGear to run smoothly, it requires a video card with OpenGL drivers 2.0 or higher. This is usually not a problem, but take a look at [[Hardware Recommendations]] to have a better idea.<br />
<br />
Many laptops are known to have issues with FlightGear, as the graphics card(s) on them are usually lower-end. See [[notebooks known to run FlightGear]] for reviews of several laptop systems.<br />
<br />
=== Getting FlightGear ===<br />
You may download the latest files from [http://www.flightgear.org/download/ FlightGear Downloads] page. Choose the source or binary files appropriate for your particular system. Most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <tt>fgfs</tt> or <tt>flightgear</tt>.)<br />
<br />
Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you're willing to do some testing there's a nightly build for Windows or Mac available for download at the [[FlightGear Build Server]],and a daily-updated Ubuntu PPA. If you are using a Git version controlled copy of FlightGear, you may choose to synchronise your aircraft using the version controlled [[FGAddon|FGAddon aircraft development repository]].<br />
<br />
You may also order FlightGear on a set of DVDs, available on the [http://www.flightgear.org/dvd/ FlightGear main site].<br />
<br />
=== Installing on Windows ===<br />
After you downloaded the installer, Run it and follow its instructions to install FlightGear.<br />
<br />
Take care to temporarily disable your antivirus during installation. FlightGear is thought by some antiviruses to have a virus.<br />
<br />
<br />
With the Windows installer, you may choose where to install FlightGear. The FGROOT directory would be [your chosen directory]/data .<br />
<br />
=== Installing on Mac OS X ===<br />
Installing [[FlightGear Mac OS X|FlightGear on Mac OS X]] is very simple. Just drag and drop the FlightGear icon to the <tt>/Applications</tt> folder. That's it. <br />
<br />
The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select an aircraft and and airport by clicking the "Gear" buttons at the right of the names. Pressing "Start flight" will launch the simulator. You can configure more options using the GUI launcher. see the [http://macflightgear.sourceforge.net/home/documents/users-guide/ Users Guide] for more details.<br />
<br />
If you'd like to launch FlightGear using command-line, launch <tt>/Applications/Utilities/Terminal.app</tt> and type the following.<br />
<br />
cd /Applications/FlightGear.app/Contents/Resources<br />
./fgfs --options..... <br />
<br />
The [[$FG ROOT]] and [[$FG SCENERY]] are not set on Mac OS X. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:<br />
<br />
FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data<br />
FG_SCENERY=[[$FG_ROOT]]/Scenery<br />
<br />
After launching the GUI launcher, you will have the alias to [[$FG ROOT]] at <tt>$HOME/Documents/Flightgear/<version></tt> so you can browse the data folder using Finder.<br />
<br />
Note: Once you have installed FlightGear, mac users can locate their [[$FG_ROOT]] folder by opening their applications folder in Finder, right clicking on FlightGear, and clicking "Show Package Contents". This will take you inside the FlightGear folder. You are now able to access all files including Data/Aircraft for [[Howto: Install aircraft#Macintosh OS X|installing new aircraft]].<br />
<br />
=== Configuring OpenGL ===<br />
FlightGear runs best with current [[OpenGL]] video drivers. If you are having trouble running FlightGear, see [[Graphics drivers configuration]] for more information.<br />
<br />
=== Getting scenery ===<br />
A limited set of [[scenery]] comes installed with FlightGear, which consists of the area surrounding [[San Francisco International Airport]] (KSFO).<br />
<br />
In FlightGear, scenery is generally stored in you [[$FG_ROOT]] directory, and is divided into three kinds of data:<br />
* '''Airports''' holds airport data, like runway usage and parking spots.<br />
* '''Objects''' and '''Models''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.<br />
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.<br />
<br />
The current way of "installing" new scenery is enabling [[TerraSync]], which will automatically download and update any place you visit - even on the fly! However, some might have problems with that, so you can also manually download and install new scenery parts, either official, the [[World Scenery]], or custom.<br />
<br />
The official, although outdated, scenery is available at [http://www.flightgear.org/download/scenery/ the scenery download section] of the FlightGear website, and can be installed following [[Howto: Install scenery]]. You may obtain additional and more up to date scenery objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database]. '''This is recommended for users with weak internet connections or weak computers!'''<br />
<br />
Custom Scenery is available in many places. For example, in our forums ([http://forum.flightgear.org forum.flightgear.org]) or on repositories. An internet search should be able to find them.<br />
<br />
=== Getting aircraft ===<br />
Additional [[aircraft]] can be downloaded and installed through the launcher. Alternatively, you can go to the FlightGear website and navigate to the [http://www.flightgear.org/download/ download page], then choose the aircraft download link that fits your FlightGear version. For the installation, see [[Howto: Install aircraft]].<br />
<br />
== Running FlightGear ==<br />
=== Starting FlightGear ===<br />
The easiest way to start FlightGear is a graphical interface like [[FlightGear Qt launcher]]. This is a frontend to the command line version.<br />
<br />
Many users choose however to start FlightGear directly from the command line. The executable name is <tt>fgfs</tt> and can be run without options. If it's "not found", it is likely not in your [https://en.wikipedia.org/wiki/PATH_(variable) path]. The location depends on your particular system and choices you made during compile and installation. There is a list of [[Command Line Parameters]] which must be used to change many options, like the aircraft you want. The most important:<br />
<br />
fgfs --show-aircraft # displays a list of installed aircraft<br />
fgfs --aircraft=c172p # start FG with the aircraft "c172p" (from the list)<br />
<br />
=== Using the keyboard and/or mouse ===<br />
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard for flying, yet even a cheap joystick would improve the experience so much.<br />
<br />
To get help with keyboard commands, with FlightGear running, go to the ''Help'' menu, look under ''Basic Keys'' (for simulator related commands) and ''Common Aircraft Keys'' (for commands universal to all aircraft) and ''Aircraft Help'' (for key commands specific to your aircraft).<br />
<br />
Coming from an other simulator? Check [[key commands compared to other simulators]] for an overview of the difference between the key commands of that sim and FlightGear and the [[Flightgear dialogs and menubar]].<br />
<br />
To use the mouse to fly the aircraft, press tab (the cursor should change to a cross) and move the mouse to direct the aircraft. Tab again to look around (cursor should show a two sided arrow), and tab again to return to normal mode, used to click stuff in the cockpit. In some aircraft, such as the [[A320neo]] and [[A330-200]]/[[A330-300|300]] this unfortunately will not work, so you will have to use right click to look around and mouse mode is disabled. Fortunately, those planes are airliners, which are really stable and easy to fly with the keyboard.<br />
<br />
=== First time in the cockpit ===<br />
Finding your way around the cockpit can be daunting the first time.<br />
<br />
Where is the "virtual cockpit?" Not all FlightGear aircraft come with an interior actually, some research projects may not even come with an exterior model. A 2D panel may display over the 3D cockpit if one exists. You may turn this off using the ''View'' menu or {{key press|Shift|V}}. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected ({{key press|Ctrl|V}}).<br />
<br />
You may find it difficult to read some of the displays, dials and gauges on the instrument panel. You can use the ''view'' mode of the mouse (right click until you get a cursor shaped like a double arrow) to pan and the mousewheel to zoom, or pan with the joystick hat and zoom with {{key press|X}} and {{key press|Shift|X}}.<br />
<br />
One of the first steps that many take on entering an unfamiliar cockpit is to press {{key press|Ctrl|C}} to highlight all the "hotspots", that is instrument's controls, buttons, knobs, etc. Many aircraft also offer a specific help menu.<br />
<br />
Some functions, such as starter or magneto, may be difficult to use or simply lack clickable "hotspots", especially in aircraft models which are in development. In most cases you can go for the equivalent controls on a 2D panel or resort to the keyboard. The keyboard always work according to the assignments listed on the ''Help'' menu, but sometimes these are reassigned by an aircraft or configuration. Again, remember to check all the help dialogs.<br />
<br />
=== Starting the engine ===<br />
You're eager to fly, but the engine's off. Well, turning on the engines is not always easy. Some aircraft have an ''autostart'' entry in their custom menu, but here's a general procedure that should work in many cases.<br />
<br />
In general to start the engine on a piston-engine type aircraft, you need:<br />
# Fuel: some aircraft start the simulation with no fuel. You can add it in ''Equipment > Fuel and Payload''.<br />
# Correct mixture: this is generally ''rich'', so push the red knob all the way in, or use the key {{key press|m}} to enrich ({{key press|Shift|m}} leans.)<br />
# Magnetos set on ''both'': turn the key or press {{key press|&#125;}} ''three times'' to move through ''R'', ''L'', ''both''.<br />
# Throttle: some engines start better with a little gas.<br />
# Run the starter: click the "start" position of the key on the panel, or press {{key press|s}}. Hold the starter for sufficient time, even 10 seconds.<br />
<br />
Starting all engines in a multi-engine aircraft is similar to the single engine--except you must follow the same start sequence for each and every engine. Flightgear provides a convenient way to do this for all engines at once: press {{key press|~}} and all the procedure above will work for all the engines. Note though that the default 2-D panel is connected to ''only one engine'' and the {{key press|~}} trick might not work. Also, give some gas to be sure that all the engines are on.<br />
<br />
These instructions may not work for jet aircraft, helicopters, or other types of aircraft with complex start procedures. Check the instructions in the aircraft help menu (Press {{key press|?}}) and/or at [[Aircraft|the aircraft's wiki]]. In general to start the engine on a jet engine type aircraft, you need to:<br />
# Set cutoff ON <br />
# Engage the starter<br />
# Once the engines spools up to approximately 5% N1, set cutoff OFF<br />
# Disengage the starter once the engine has reached operational speed<br />
<br />
=== Online multiplayer flying ===<br />
FlightGear has some multiplayer servers that will let you fly in more lively skies, see [[Howto: Multiplayer]]. There are also [[OpenRadar]] and [[ATC-pie]], standalone programs that will let you be an [[Air traffic control|air traffic controller]].<br />
<br />
There's also a [[MPMap|multiplayer map]] that lets you see who's online right now,and even what navaids are nearby.<br />
<br />
== Making your first flight ==<br />
=== Realism ===<br />
One of the most frequent questions novice pilots ask about any flight sim, but more so to FlightGear, is "why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the [[Understanding Propeller Torque and P-Factor|propeller torque and p-factor]].<br />
<br />
In certain other flight simulators, despite marketing slogans to the contrary, some settings are turned down to make the aircraft easier to fly. This reduces effects such as the above. The realism is always turned up in FlightGear.<br />
<br />
Here are some of the FlightGear realism points, which may be confusing to first time pilots:<br />
* "Left turning syndrome" for the previously mentioned reasons.<br />
* Compass turning error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction ([https://en.wikipedia.org/wiki/Aircraft_compass_turns more on this].)<br />
* The Vertical Speed Indicator (VSI) is also subject to error.<br />
* The Horizontal Situation Indicator (HSI) is driven by a gyroscope (that is why it's sometimes called a Directional Gyroscope), which is subject to ''gyro drift'': the indicator will drift from its current heading and must be periodically (every ~15 minutes) calibrated to agree with the magnetic compass heading.<br />
*You cannot just cancel a turn or climb by centring the yoke or stick. You must turn or push the stick the other way to get to level and level flight. But even then, the plane will not mantain its altitude or heading by itself- a common mistake is trying to find a hands off yoke position. While with trims one could leave the plane for a couple of seconds, one must use autopilot or constantly adjust the yokes.<br />
<br />
Many forces act on an aircraft in flight as well as on the [[avionics and instruments]] used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. ''FlightGear models instrument errors that exist in the real world''.<br />
<br />
=== Airports and navigation aids ===<br />
When you first start FlightGear, whether from the command line or the graphical interface, you may wonder how to determine what airports are available. The launcher displays a list of airports, but you will not see details such as tower or [[ILS]] frequencies. You will not find a map showing [[VOR]]s and their frequencies. What can you do? See [[Getting aeronautical charts]].<br />
<br />
In-sim, there is a map you can use in ''Equipment > Map'', which will allow you to see navigation data and the position of airports and aids. For more help with navigation see [[Understanding Navigation]].<br />
<br />
=== Flying using the autopilot ===<br />
Some aircraft require you to use the [[autopilot]] available from the ''Autopilot'' menu, which is the original FlightGear autopilot. This is a ''generic'' autopilot and as such, many aircraft come with their own ''specific'' autopilot, frequently a model of the real life one.<br />
<br />
For aircraft that provide their own autopilot, you should use the autopilot controls available in the virtual cockpit. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot in some aircraft, including the Airbuses and the [[Cessna 172P|C172P]].<br />
<br />
The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You cannot use the ''Autopilot'' dialog from the menu with this aircraft. You must use the autopilot device in the panel.<br />
<br />
== The FlightGear community ==<br />
=== Getting help ===<br />
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:User|User portal]] of this wiki, there are other pages you may want to read:<br />
* [[Troubleshooting problems]] to help you with the most common issues;<br />
* [[Frequently asked questions]];<br />
...and communication channels that can be used to obtain information or request help:<br />
* The [[FlightGear Manual]], a ''must read'' for beginners;<br />
* [https://forum.flightgear.org FlightGear Forum] and its subforums;<br />
* [[FlightGear IRC channel]], the quickest way to get help;<br />
* [[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;<br />
* Documents bundled with the release package.<br />
<br />
=== Customizing FlightGear without compiling it ===<br />
[http://www.flightgear.org/download/ Our website] offers precompiled binaries for download and install on Windows and Mac OSX, while most Linux distros provide a packaged version in their repositories.<br />
<br />
Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].<br />
<br />
=== How you can help ===<br />
{{Main article|Volunteer}}<br />
FlightGear is an opensource, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the forum and everything else. Volunteers, i.e. ''people that do things'', are fundamental to this project: without them, it wouldn't make a single step forward. So it is essential that contributors have fun in what they do.<br />
<br />
If you really plan to contribute to this project, you should take a look at some articles that will give you some hints:<br />
* [[Howto:Understand the FlightGear development process]]<br />
* [[Implementing new features for FlightGear]]<br />
* [[How the FlightGear project works]]<br />
<br />
There are never enough people contributing, and the fields where their help would be appreciated are many:<br />
;Testing :<br />
* [[Building Flightgear|Build]] the latest Git code or download snapshots from the [[FlightGear Build Server]]<br />
* [https://sourceforge.net/p/flightgear/codetickets/ File bug reports]<br />
* Running FlightGear via valgrind to track down memory leaks<br />
<br />
;Support :<br />
* Help new users with downloading, compiling, installing and running FlightGear (https://forum.flightgear.org or on IRC)<br />
* Provide ideas & suggestions, see: [[Feature Requests / Proposals / Ideas]]<br />
* Help clean up this wiki<br />
* Help provide new contents for missing wiki pages<br />
<br />
;Development :<br />
* C/C++ Coding:<br />
** provide source code cleanups (i.e. help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)<br />
** provide bug fixes [[Bugs]] or new features <br />
** get involved in any of the other FlightGear-affiliated projects <br />
* Aircraft development (3D modelling, textures, FDMs, scripting)<br />
* Scenery development (terrain, model, weather)<br />
<br />
[[Category:FlightGear]]<br />
<br />
[[de:Neu bei FlightGear]]<br />
[[es:Nuevo para FlightGear]]<br />
[[fr:Nouveau sur flightgear]]<br />
[[it:Nuovo per FlightGear]]<br />
[[ja:FlightGear入門]]<br />
[[nl:Nieuw bij FlightGear]]<br />
[[pt:Novo no FlightGear]]<br />
[[zh:FlightGear新手]]<br />
[[th:New to FlightGear]]</div>RChandrahttps://wiki.flightgear.org/w/index.php?title=Bendix/King_KAP140_Autopilot&diff=107068Bendix/King KAP140 Autopilot2017-02-24T03:12:35Z<p>RChandra: /* External link */ fixed dead link to Bendix Pilot's Guide to a more current one</p>
<hr />
<div>The '''''Bendix/King KAP 140''''' '''Two Axis/Altitude Preselect Autopilot System''' is the [[autopilot]] of the default [[Cessna 172]], controlling the [[elevator]] and [[aileron]]s.<br />
<br />
== Quick Guide ==<br />
[[File:KAP140.jpg|KAP140 Two Axis with Preselect Altitude]]<br />
<br />
# To activate the autopilot in wings level (ROL) and vertical speed (VS) modes press the AP button. The autopilot will try to keep the wings level by keeping the turn rate at zero. The autopilot will also try to maintain the vertical speed at activation. Use the UP and DN buttons to set the desired vertical speed.<br />
# With the autopilot active you can use the HDG button to toggle between wings level (ROL) and heading select (HDG) modes. In heading select mode the autopilot will try to maintain the heading selected by the heading bug on the directional gyro.<br />
# Use NAV button to toggle between navigation mode (NAV) and wings level (ROL) mode. NAV mode is flying to NAV1 or GPS. That is one of the Heading modes in KAP140 that direction when heading bug OBS operated. Please be careful.<br />
# Toggle other mode and approach (APR) mode when APR button pushed and following marker beacon, VOR, GPS and [[ILS]] (localizer and glide slope) for automatic approach. This mode is recommended for instrument approach.<br />
# The REV button enables the back course mode having the autopilot flying away from the runway. This mode is like APR mode except that the direction is away from the localizer (LOC) and that glide slope (GS) is not used.<br />
# Use the ALT button to toggle between vertical speed (VS) and altitude hold (ALT) modes. In altitude hold mode the UP and DN buttons change the altitude by 20 feet per press.<br />
# The ARM button enables altitude preselect by the rotary knob using procedure below, pushing it again disables altitude preselect.<br />
## Input the current atmospheric pressure using the BARO button and rotary knob<br />
## Check that the display is showing altitude and set your desired altitude, using the rotary knob. <br />
## Set your desired vertical speed using UP and DN button.<br />
## Press the ARM button that is enable ARM mode.<br />
# The BARO button sets the atmospheric pressure. When the BARO button is pushed, enter desired atmospheric pressure using the rotary dial/knob.<br />
# Press the AP button to deactivate the autopilot. The horizontal and vertical modes can not be activated independently.<br />
<br />
Please read the Pilot's Guide for complete instructions on the use of the KAP140 Autopilot system.<br />
<br />
== Related pages ==<br />
* [[Joystick Autopilot Bindings]] Snippets for joystick.xml file that allow control of most of the autopilot functions using the joystick.<br />
== External link ==<br />
* [https://bendixking.com/HWL/media/Pilot-Guides/006-18034-0000_3.pdf Bendix/King KAP 140 Pilot's Guide download link] (PDF, 7.1 MB), Honywell, rev. 3, Sep 2005.<br />
<br />
[[Category:Aircraft instruments]]<br />
<br />
[[es:Piloto automático Bendix/King KAP140]]</div>RChandra