FlightGear wiki - User contributions [en]

MPMap

2017-08-14T23:22:24Z

Condab: Removed 'mpmap01'

:''See [[Howto:Multiplayer]] for how to set-up multiplay.''

[[File:MP_Server.jpg|thumb|270px|A satelite view of the area around [[San Francisco International Airport]].]]
'''MPMap''' is an utility that shows [[aircraft]], flying in the [[FlightGear]] world, on a world map. Besides that it also provides access to navigation data such as [[ILS]] frequencies, runway numbers and fixes. As it makes use of Google Maps, one can choose between map or satellite view.

Currently there is one server providing MPMap:
*[http://mpmap02.flightgear.org mpmap02]

== Using the map ==
* You can minimize this menu dock by clicking on the title (where the "FGMap - server name - pilots: n" is). Click on it again to bring up this menu again.
* The icon at the top right hand corner of the menu box gives you a permanent link to current view of the map, which includes the current zoom level, map type, and pilots that map is following.

[[File:MP_Map_Pilots.jpg|thumb|270px]]
[[File:MP_Map_NAV.jpg|thumb|270px]]
=== Pilots ===
* You can pan to a pilot by clicking on the callsign/name.
* You can "follow" and track a pilot by ticking the checkbox of a pilot. This means that pilot will always be visible on the map. You can follow more than one pilot, and the map will pan and zoom automatically.
* You can filter the pilot list by entering a Part of the Callsign or Aircraft.

=== NAV ===
* You can search for navaids by string using the lookup input field. You could start the lookup by pressing Enter or clicking on the [[File:Mpmap_nav_search.gif|caption]] button after typing in the lookup string.
* Lookup results are shown in the lower part of the menu. You can view and pan to the navaid by clicking on each navaid result.
* You can search for all navaids visible in the current map view by clicking on the [[File:Mpmap_nav_inview.gif|caption]] button.
* For all the lookups, you can select the type of navaids to search for using the six checkboxes below the lookup input field.
* Both the string lookup and current map view lookup has a maximum number for returning navaids.
* You can toggle each type of shown navaid on or off by using the five checkboxes on the bottom right of the menu.
* You can clear all the navaids added from lookups by clicking on the [[File:Mpmap_nav_trash.gif|caption]] button.

[[File:MP_Map_Server.jpg|thumb|270px]]
=== Server ===
* You can select which server the map will be showing from the server dropdown list.
* You can toggle updating of the map using the checkbox provided.
* You can change how often the map will update using the textbox provided.

[[File:MP_Map_Settings.jpg|thumb|270px]]
=== Settings ===
* You can choose how the pilot label will be shown on the map. Currently there are 4 modes:
** off - labels are always off.
** always - labels will be shown for all pilots at any time.
** follow always - labels will only be shown for pilots which are selected for "follow" in the pilot tab.
** mouse over only - labels will only be shown when you move your mouse over the icon of a pilot.
* You can choose how the icon is displayed for each pilot on the map. Currently there are 3 modes:
** normal - a normal red aircraft icon.
** photo - a photographic icon, not available for all aircraft.
** dot - a simple red dot, similiar to a ATC radar.
* You can turn on or off the trails of pilots with the "Pilot trails" checkbox.
* You can turn on or off the "Zoom/Pan to all pilots" mode with the corresponding checkbox. When this mode is enabled, all pilots will be "followed" automatically at all time. That also means any new pilots joining will be followed automatically too.
* You can turn on debug mode of the map with the "Debug" checkbox. When it is turned on a debug tab will be added, showing debugging messages of the map.

== Startup parameters ==
You can specify certain startup parameters for the map. Parameters are passed using standard URL query string. Key and value pairs are appended to the URL like:

[http://mpmap02.flightgear.org/?key1=value1&key2=value2 http://mpmap02.flightgear.org/?key1=value1&key2=value2]

Currently valid keys and values are:
* '''fg_server''' - FG server to use at startup.
** '''server name:''' the name of the server which would be shown in the server selection dropdown list.
** '''server host:''' the host of the server, this could be the host name or the IP address of the server.
** '''admin port:''' the admin port number of the server, this is usually the port you use for FlightGear --multiplay '''plus one'''.
** '''example:''' fg_server=os-devel,postrobot.de,5003
* '''ll''' - Latitude and Longitude (in that order) at startup.
** '''example:''' ll=37.613545,-122.357237
* '''z''' - map zoom level, range 0 - 17, being 0 is the highest zoom level.
** '''example:''' z=0
* '''t''' - map type, m for map, s for satellite, h for hybrid.
** '''example:''' t=s
* '''follow''' - Follow the pilot at startup given its callsign. Multiple follow is allowed.
** '''example:''' follow=pigeon&follow=ampere
* '''pilot_label''' - Set the startup pilot label mode. Valid values are off, always, follows, and mouseover. See the help of the settings tab more info.
** '''example:''' pilot_label=off
* '''icon_mode''' - Set the startup pilot aircraft icon mode. Valid values are normal, photo, and dot. See the help of the settings tab more info.
** '''example:''' icon_mode=dot
* '''menu''' - menu tab to display at startup.
** '''example:''' menu=nav
* '''nomapcontrol''' - Hide Google Map zoom and map mode controls.
* '''nomenu''' - Hide the menu, completely.
* '''menuminimized''' - Have the menu minimized on startup.
* '''update_interval''' - Set the startup map update interval, in seconds.
** '''example:''' update_interval=10

== Related content ==
* [[FlightGear Tracker]]
* [[FlightGear Multiplayer Server]]

[[Category:Multiplayer]]
[[Category:Software]]
[[fr:MPMap]]

OculusImplementation

2017-08-14T22:41:24Z

Condab: 'Flightgear' & 'flightgear' -> 'FlightGear'

{{Stub}}
This Page sums up the Efforts made / to make, to add Oculus Rift VR Helm Support to FlightGear documenting the whole effort and what you've got so far, which will also help others to get started with this much more easily
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=234192#p234192
| title = <nowiki>Re: </nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Mar 6th, 2015
| added = Mar 6th, 2015
| script_version = 0.25
}}
</ref>

The main Forum Thread is [http://forum.flightgear.org/viewtopic.php?f=6&t=22640 Oculus Rift Implementation]

There are (at least) two approaches:
* integrate the Oculus Rift SDK into the C++ Code (Advantages are: easy Setup (i.e. Direct to Rift Mode), Execution speed
* deal separately with Headtracker and Display Integration (Advantages are: flexible setup i.e. headtracker on different Workstation, streaming to different Displays, Multiplatform Widows, Linux, evtl MAC)

direct c++ Integration has been started by [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=15936 Gouranga] and [http://forum.flightgear.org/memberlist.php?mode=viewprofile&u=510 Gijs]

Separate Headtracker tests are succesfull using
* a self written tool by [http://forum.flightgear.org/viewtopic.php?f=6&t=22640&start=15#p216006 ludomotico]
* a universal headtracker [https://github.com/opentrack/opentrack opentrack]
 
== Motivation ==
Getting the position and orientation data from the VR goggles to FlightGear and getting it to control the view through e.g. view.nas should be fully possible.
In fact some related work has been done in the field of head tracking, in essence using some input from either hardware or software to control view movements. There is also functionality for stereoscopic viewing built in into FlightGear. (Click on the following links to search the forum for posts about [http://www.flightgear.org/forums/search.php?st=0&sk=t&sd=d&sr=posts&keywords=head+tracking head tracking] and [http://www.flightgear.org/forums/search.php?st=0&sk=t&sd=d&sr=posts&keywords=stereoscopic stereoscopic viewing].)

What I really would like to see though is being able to use the Oculus Rift. They are expensive, but not compared to many other VR goggles, and... they are in some ways more innovative than an order of magnitude more expensive VR goggles. <ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=181325#p181325
| title = <nowiki>Re: Virtual goggles</nowiki>
| author = <nowiki>Johan G</nowiki>
| date = Apr 14th, 2013
| added = Apr 14th, 2013
| script_version = 0.25
}}
</ref>

== Status ==
The latest news on this seem to be in these two topics. In essence not much seem to be happening at the moment.<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=241805#p241805
| title = <nowiki>Re: Virtual goggles</nowiki>
| author = <nowiki>Johan G</nowiki>
| date = May 6th, 2015
| added = May 6th, 2015
| script_version = 0.25
}}
</ref>

* [http://forum.flightgear.org/viewtopic.php?f=42&t=25156 Free aircraft helicopter simulator Flightgear vs Oculus Rift] Jan 2015
* [http://forum.flightgear.org/viewtopic.php?f=6&t=22640 Oculus Rift Support] Apr 2014-Mar 2015

successfully support oculus but still not stable. [http://imgur.com/mV6AoKg http://imgur.com/mV6AoKg]<ref>{{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=265725#p265725
| title = <nowiki>Re: </nowiki>
| author = <nowiki>nicole_yaoyao</nowiki>
| date = Nov 24th, 2015
| added = Nov 24th, 2015
| script_version = 0.25
}}
</ref>

{{FGCquote
|1= summary of my advances: [http://forum.flightgear.org/viewtopic.php?f=6&t=22640&start=15#p216006 viewtopic.php?f=6&t=22640&start=15#p216006]
- There is no problem with the headtracking. There are several ways to connect the headtrack to FlightGear, and any of them should work. My way was using an intermediate program to read the position from the oculus and send it to FlightGear using the telnet server. It worked awesomely.
- The 3D effect is another thing. In my opinion, it should be an effect provided by OpenSceneGraph and not FlightGear, as the other stereoscopic effects are. The integration must be done outside the FlightGear community. There are several efforts to integrate OpenSceneGraph and the Oculus. If one of them is successful (I have not checked lately), FlightGear must just switch it on and use it. Currently, you can use the Oculus with the split-screen option (in View->Stereoscopic) and configure 0 as eye separation. You won't perceive any depth, but the aircraft and scenery will be shown perfectly. Well, not perfectly, it will be deformed at the borders.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=241809#p241809
| title = <nowiki>Re: Virtual goggles</nowiki>
| author = <nowiki>ludomotico</nowiki>
| date = May 6th, 2015
| added = May 6th, 2015
| script_version = 0.25
}}
}}

* Using Oculus Rift DK2 and Oculus SDK 0.3 on Linux. FlightGear fully updated to current GIT. OpenSceneGraph 3.2.0
* Image: using stereoscopic mode, fullscreen, eyes distance=0. Obviously, the 3D effect is lost but the immersion is not. I'm still researching how applying the barrel distortion the Oculus needs to create the 3D effect, but my bet is still on an OpenSceneGraph plugin without any modification in FlightGear or SimGear (apart from the switch in the stereoscopic menu to activate this mode) I'll wait for the 0.4 version of the Oculus SDK for Linux.
* tracking position: you'll find below a standalone program that tracks the position of the headset and moves the view accordingly. This assumes FligthGear is running with a telnet server in port 9000. It seems the heading needs some reset if you put the headset on the table, so '''do not put the headset on the table''' while running the tracker :D I'm guessing and not really sure, but I think v0.3 of the SDK uses internal accelerometers to track the position and does not use the external camera for synchroniation. I think the external camera is only supported from v0.4 of the SDK. I have only tested this program in Linux.

To build the position tracker, you have to download and build the Oculus SDK (v0.3 at the time of writing this, 0.4 version is not yet available for Linux) and change the paths of the Oculus SDK in the Makefile. Then, "make demo1" and run "demo1" with the Oculus and FligthGear activated.
[https://dl.dropboxusercontent.com/u/13130748/oculus.zip https://dl.dropboxusercontent.com/u/13130748/oculus.zip]
This is only a test, it is not optimized and full of debug messages and it uses some classes for Sockets with no clear license. Do not assume it is GPL because it is not!
Apart from the lacking of the 3D effect, flying with this needs some minutes to get used to. Once you get the idea, the feeling of complete immersion and being able to move your head to see the environment is awesome! The resolution is not the best and the pixels are very evident, but I'm still not sure if I'm using the max resolution the Oculus supports
<ref>{{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=216006#p216006
| title = <nowiki>Re: </nowiki>
| author = <nowiki>ludomotico</nowiki>
| date = Aug 4th, 2014
| added = Aug 4th, 2014
| script_version = 0.25
}}
</ref>

== USB/HID Support ==
For a summary, refer to: [[USB HID Support]]
Here's a list of postings/threads covering the status of Saitek USB/HID device support in FG:

* [http://forum.flightgear.org/viewtopic.php?p=74623#p74623 Saitek Radio panel]
* [http://forum.flightgear.org/viewtopic.php?p=201170#p201170 USB Interface development]
* [http://forum.flightgear.org/viewtopic.php?p=185021#p185021 Oculus Rift Development]
* [http://forum.flightgear.org/viewtopic.php?p=192242#p192242 force vibration]

Note that there's also a dedicated ticket/feature request (see the tracker at: [http://sourceforge.net/p/flightgear/codetickets/619/ #619 HID abstraction layer for Nasal] )
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=242121#p242121
| title = <nowiki>Re: Support for Saitek Hardware </nowiki>
| author = <nowiki>Hooray</nowiki>
| date = May 8th, 2015
| added = May 8th, 2015
| script_version = 0.25
}}</ref>

== Alternatives ==
There is an alternative to Oculus Rift that have some interesting aspects in regard to flight simulators: CastAR
It is a very different setup from what most of you have seen before. For starters it is based on using retroreflective materials ("reflex sheets") and a projector built into the glasses. For head tracking the glasses also have a camera that tracks IR diodes.<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=250213#p250213
| title = <nowiki>Re: Virtual goggles</nowiki>
| author = <nowiki>Johan G</nowiki>
| date = Jul 7th, 2015
| added = Jul 7th, 2015
| script_version = 0.25
}}
</ref>

== Opentrack ==
where to get opentrack...use this link... [https://github.com/opentrack/opentrack https://github.com/opentrack/opentrack] on the page that it opens you'll have to scroll down to the readme section and select the binary releases link to download the program.

You can create different profile within opentrack...they're self explanitory.
FlightGear has to also be set in stereoscopic side by side mode....this is kinda hard to do...so I set up a shortcut key in my video driver to swap screens...that way I can switch screens back and forth while FlightGear is running. The file menus at the top are not visible inside the oculus, s this saves huge headaches.
Keep the tread alive! There will be more people interested in the subject as it becomes more prevalent...Maybe somebody who knows how to program the barrel shader into OSG so the view doesn't skew when you rotate your head side to side...(this will make you very queey)<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=234182#p234182
| title = <nowiki>Re: </nowiki>
| author = <nowiki>water_raptor</nowiki>
| date = Mar 5th, 2015
| added = Mar 5th, 2015
| script_version = 0.25
}}
</ref>

* is multi platform (windows, linux),
* can read the Oculus Rift Tracker as Input (in different sdk versions)
* and comes with a headtracker.xml Protocol for generic input in FlightGear.
 
Display Integration could be done by the FlightGear/OSG Stereosopic side by side Support,
but lacks the special 'Barrel distortion' transformation needed for each eye. 
Successful tests here use the Stereoscopic side by side Mode, with eye distance=0, but still barrel distortion.
 
this could of be either
* coded in C++ into the render pipline without SDK need as a shader
or
* done as a shader in the FG shader system without C++ code?
 
Gijs has begun work on the [[Shader_requests#Lens_distortion_shader_for_Oculus_Rift|Lens distortion shader]]
 

== Open Questions ==
* is it possible (or feasable) to integrate a shader into the action system, i.e. Action Display with Rembrand active
:Answer is YES, with rembrand active, there is already a distortion shader in place, which could be used or adapted (without code changes)
* would that be before the Side by Side step in the rendering pipeline as a single eye distortion, or afterwards as a side by side distortion shader
:Answer is, that the stereoscopic OSG Side by Side option is NOT available with rembrand
* so is it possible to have side by side views done with rembrand AND have the barrel distortion shader in place for each eye view
:(''mmartin'')should be, will investigate

== Related ==
* [https://github.com/opentrack/opentrack opentrack]
* [https://github.com/bjornblissing/osgoculusviewer osgoculusviewer]
* [https://github.com/ChrisDenham/osgopenvrviewer osgopenvrviewer]
* [https://github.com/dghost/glslRiftDistort OpenGL Barrel Distortion Shader for the Oculus Rift]

Cessna 172P

2017-07-28T13:17:04Z

Condab: Added four user-created images to gallery.

{{:{{PAGENAME}}/info}}
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.

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

== Features ==

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

[[File:C172p-bodensee-panorama.jpg|center|800px]]

The aircraft currently has five variants, all available from the aircraft menu:
* regular wheels
* 26" bush tires
* 36" bush tires
* pontoons
* amphibian
* snow skis

Also, from the same menu, the user can select two different engines:
* 160 HP
* 180 HP (recommended when using pontoons, amphibian and skis variants)

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.

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.

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.

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.

The aircraft has a simulation of the [[Bendix/King KAP140 Autopilot]].

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.

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

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.

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.

[[File:c172p-ALS-flashlight2.jpg|500px|center|Cessna 172P's flashlight in the cockpit]]

== Handling The Aircraft ==

=== Pre-Flight Inspection ===
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]
It's recommended to use any exterior view or activate the walker for these procedures.
* 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)
* Left wing: remove tie-down
* Left wing: remove pitot tube cover
* 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
* Tail: remove tie-down
* Right wing: remove tie-down
* Right wing: check for fuel contamination
* Nose: check for oil quantity by clicking on the oil door in the nose. Critical oil level for either engine is 5.0 quarts.
* Nose: remove wheel chocks

=== Engine Start (manual and complex startup) ===
* Priming: prime the engine at least 3 times
* Mixture: Rich (red lever all the way in)
* Throttle: Open 1/8 (black lever at 20%)
* Parking Brake: Applied ({{Key press|Shift|B}})
* Prop Area: Clear
* Master switch: ON (both)
* Magnetos: Both (Press {{Key press|<nowiki>}</nowiki>}} three times)
* Ignition: Start ({{Key press|S}})

=== Engine Start (automatically with Autostart) ===
* 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.

=== Takeoff ===
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]
* no flaps
* full throttle
* rotate at 55 KIAS

=== Climbout ===
* no flaps
* full throttle
* 75 KIAS

=== Cruise ===
* throttle 65%
* mixture rich of peak
* speed around 100 knots

=== Landing ===
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touch down]]
* full flaps
* 60 KIAS

=== Airspeeds ===
: ''See also [[Aircraft speed#V speeds]]''

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>

{| class="wikitable"
! Airspeed !! CAS
|-
| Stall speed, landing configuration, VS0 || 33 kt
|-
| Stall speed, clean, VS1 || 44 kt
|-
| Rotation speed, VR || 55 kt
|-
| Best angle of climb speed, VX || 59 kt
|-
| Best rate of climb speed, VY || 76 kt
|-
| Maximum flap extended speed, VFE || 85 kt
|-
| rowspan="2" valign="top" | Maneuvering speed, VA || 96 kt (floatplane)
|-
| 99 kt (landplane)
|-
| Maximum structural cruising speed, VNO || 127 kt
|-
| Never exceed speed, VNE || 158 kt
|}

== FAQ ==

Here are some of the frequently asked questions about this aircraft:

'''Q:''' I am experiencing grey windows, what is happening?

'''A:''' If you experience grey windows, you do not have the correct FlightGear version. This aircraft requires 3.5 or above.

'''Q:''' Why does the aircraft keep turning left?

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

'''Q:''' Why will the engine not start?

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

'''Q:''' Why does the Autostart fail to start the engine?

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

'''Q:''' Why does the engine die immediately after startup?

'''A:''' Probably because the throttle is being incremented too fast after startup as the engine needs a few seconds to stabilize itself.

'''Q:''' Why can't I start the sim with the engine running?

'''A:''' You can! Go to the menu "Cessna C172P", select "Aircraft Options" and tick the option "Start with engine running".

'''Q:''' Why I keep running out of battery?

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

'''Q:''' Why the aircraft doesn't move?

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

'''Q:''' Why the airspeed indicator doesn't work?

'''A:''' If the option "allow securing aircraft" is enabled in the aircraft menu, then very likely you forgot to remove the pitot tube cover.

'''Q:''' How can I switch to the bush tires/pontoons/amphibian?

'''A:''' By clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the other landing gear options.

'''Q:''' How can I switch to the 180 HP engine?

'''A:''' This is also done by clicking in menu "Cessna 172P", selecting "Aircraft Options" and then selecting the engine power option.

'''Q:''' Why can't I take off from the water without crashing the plane?

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

'''Q:''' Why is the simulator lagging so much?

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

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.

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

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

'''Q:''' Why are the windows getting foggy/frosty?

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

'''Q:''' How do I increase the cabin air temperature?

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

'''Q:''' How can I click on a switch which is being covered by the yoke?

'''A:''' You can hide the yokes by clicking on them or by going to the menu "Cessna 172P", selecting "Hide/Show Yokes".

'''Q:''' Why my engine seems to be losing power?

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

== Development status/Issues/TODO ==

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.

== Gallery ==

<gallery mode="packed">
c172p-plane5.jpg|Cessna 172P above Chapada Diamantina in Brazil
c172p-plane4.jpg|Taking off from Compiegne Margny (LFAD)
c172p-cockpit2.jpg|About to land, showing the new ALS shadow effects in the cockpit
c172p-floats.jpg|Float variant in San Francisco
c172p-plane3.jpg|Cessna 172P at high altitude flying over Lago di Garda in Italy
c172p-landing.jpg|On final at Aosta Airport (LIMW)
c172p-cockpit3.jpg|The fully textured interiors of the new c172p
c172p-night.jpg|A night flight, showing the instrument illumination
c172p-particles.jpg|Taking off on water, showing the particle system
c172p-plane1.jpg|Above Serra do Mar in Brazil
c172p-plane2.jpg|Flying at sunset
c172p-winter.jpg|European winter
c172p-damage.jpg|Gear collapse due to heavy landing
c172p-frost.jpg|If the conditions are just right, frost or fog will appear in the windows
c172p-taubate.jpg|Flying above Taubate, Brazil
c172p-equipment.jpg|All equipment; external power unit, fuel tank, ladder, wing safety cones, wheel chocks, pitot tube cover & tie-downs
c172p-bush.jpg|Cessna 172P with 36" bush tires
c172p-parked.jpg|N35799 livery parked at Camden Airport (YSCN)
c172p-cover.jpg|Cessna 172P with pitot tube cover and nose wheel chock placed

</gallery>

== External links ==
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]
* [http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf Cessna 172 checklist at aerodynamicaviation.com]

{{Appendix}}

{{Cessna}}

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

[[de:Cessna 172P]]
[[es:Cessna 172P]]
[[fr:Cessna 172P]]
[[nl:Cessna 172P]]
[[zh:Cessna 172P]]

File:C172p-cover.jpg

2017-07-28T12:59:32Z

Condab: Condab uploaded a new version of File:C172p-cover.jpg

=={{int:filedesc}}==
{{Information
|description={{en|1=Cessna 172P parked with pitot tube cover placed}}
|date=2017-04-04
|source={{own}}
|author=[[User:Condab|Connor Dabron]]
|permission=
|other versions=
}}

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

[[Category:Cessna 172 screenshots]]
[[Category:High wing aircraft]]
[[Category:Light aircraft]]

File:C172p-equipment.jpg

2017-07-28T12:50:22Z

Condab: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=New Ground Equipment options, including external power unit & fuel tank}}
|date=2017-07-27
|source={{own}}
|author=[[User:Condab|Connor Dabron]]
|permission=
|other versions=
}}

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

[[Category:Cessna 172 screenshots]]
[[Category:High wing aircraft]]
[[Category:Light aircraft]]

File:C172p-bush.jpg

2017-07-28T12:32:10Z

Condab: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Cessna 172P with 36" bush tires}}
|date=2017-07-27
|source={{own}}
|author=[[User:Condab|Connor Dabron]]
|permission=
|other versions=
}}

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

[[Category:Cessna 172 screenshots]]
[[Category:High wing aircraft]]
[[Category:Light aircraft]]

File:C172p-parked.jpg

2017-07-27T11:51:10Z

Condab: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=N35799 livery parked at Camden Airport (YSCN)}}
|date=2017-04-03
|source={{own}}
|author=[[User:Condab|Connor Dabron]]
|permission=
|other versions=
}}

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

[[Category:Cessna 172 screenshots]]
[[Category:High wing aircraft]]
[[Category:Light aircraft]]

File:C172p-cover.jpg

2017-07-27T11:37:17Z

Condab: Condab uploaded a new version of File:C172p-cover.jpg

File:C172p-cover.jpg

2017-07-27T11:33:20Z

Condab: Condab uploaded a new version of File:C172p-cover.jpg

File:C172p-cover.jpg

2017-07-27T11:20:46Z

Condab: User created page with UploadWizard

Changelog 2017.1

2017-06-27T02:01:26Z

Condab: Improved punctuation consistency

{{changelogs|prev=2016.4|next=2017.2}}
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.

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 v2017.1 for free from [http://www.flightgear.org/ FlightGear.org]

FlightGear - Fly Free!

== Major enhancements in this release ==
=== Core ===
* Support for additional layers of scenery, initially for use by OpenStreetMap buildings.
* <tt>''preferences.xml''</tt> has been renamed to <tt>''defaults.xml''</tt> ({{fgdata commit|0565ea}}).

=== Aircraft Modeling ===
* More realistic blackout/redout system based on studies for military training simulations ({{fgdata commit|52e559}}).
* Improved AI models for a number of aircraft, and AI schedules for an increasing number of airlines.

=== Atmospheric Light Scattering ===
* New shaders for drag chute animation, allowing to render flexing and deformation under stress.
* New "grain merge" and Fresnel option for environment reflections on the aircraft fuselage.
Learn more in the [[FlightGear Newsletter December 2016|Newsletter]].

=== Environment Rendering ===
* For rendering views from orbit, Earthview 2.0 is now available, with support for normal maps, better upper atmosphere edge, cloud relief shader, improved dawn zone, horizon estimation and improved resource management.

=== Performance ===
* Canvas performance has been improved.
* Support for {{abbr|SIMD|single instruction, multiple data}} operations added, improving performance on some architectures.
* AI performance has been improved.

=== Usability ===
* Bergen Airport, Flesland (ENBR) in Norway is the default airport for this release.
* Tutorial instructions are now played through the built-in voice synthesis system, making them easier to follow.

=== Scenery ===
* Accurate buildings generated through OpenStreetMap are now available via [[TerraSync]]. Buildings for the UK, Switzerland and large parts of Scandinavia are available already, with more to be generated in the future.
* Improved scenery and terrain for the Azores.

=== Canvas System ===
* [[Canvas]] performance has been improved.
* [[FGQCanvas|Remote canvas]] is now available.

=== Highlighted new and improved aircraft ===
* [[Piper J-3 Cub]]
* [[Saab 37 Viggen]]
* [[Schleicher ASK 21]]
* [[General Dynamics F-16 Fighting Falcon]]

=== Bug fixes ===
* Various bug fixes that cause crashes in multiplayer.

* See [https://sourceforge.net/p/flightgear/codetickets/search/?q=status%3AFixed+AND+created_date%3A%5B2016-11-17T18%3A27%3A17Z+TO+2017-02-22T18%3A48%3A48Z%5D our bugtracker] for a list, albeit incomplete, of the bugs fixed in this release.

==== Changes in 2017.1.2 ====
* Change Windows multi-app launch detection from a .pid file to a named mutex.
* <code>--console</code> now works in the launcher.

==== Changes in 2017.1.3 ====
* A bug in handling log messages was fixed.
* Route Manager crash was fixed.
* Correct runway selection depending on weather provided with <code>--metar</code> has been added.
* Fixes to launcher issues.
* Fixed a weather bug.
* Fixed a bug with handling of integer factors in the generic protocol.
* Option <code>--log-file</code> was renamed to <code>--log-dir</code>
* Restore display of live metar data in the weather dialog.

[[Category:FlightGear changelogs]]
[[Category:New Versioning Scheme]]

Changelog 2017.2

2017-06-27T01:21:59Z

Condab: Improved punctuation and capitalization consistency

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



== Major enhancements in this release ==
=== Core ===

=== Aircraft Modeling ===
* Added support to allow a geometry object (a line segment with two vertices) that is used to define both the centre and the axis for an animation. This will work with rotate, translate and the knob animations.

=== YASim ===
* The YASim code is under heavy development and will continue to get improvements in the future.

=== Multiplayer ===
* Optional new protocol that improves efficiency (35% reduction in bandwidth). Older clients (pre 2017.1) will only see basic aircraft motion when new protocol selected.
* New debugging options; local loopback, transmitted packet size, packet dump.
* Extra generic properties; float[20..39], short[0..79], bool[0..90].
* Connect dialog will use configured ports rather than always using 5000,5000.

=== Atmospheric Light Scattering ===

* G-force effect with greyout and tunnel vision.
* HUD effect simulating more realistically the appearance of light projected onto glass.
* Improved Aurora shader.

=== Environment Rendering ===
* Added a normalmap to the Earthview clouds and landscape.
* Added a lightmap to Earthview at night, including thunderstorm visuals.
* Earthview atmosphere Rayleigh scattering added.

=== Performance ===

=== Misc/Uncategorized ===
* A '''new, modern splash screen''' together with start-up tips.
* The launcher's design '''is reworked'''.

=== Usability ===
* '''Improved aircraft discovery''': Search tags and large screenshots in the launcher.

=== Internationalization ===

=== Scenery ===
* Enhancements for the integration of [[Osm2city.py|osm2city]] generated sceneries:
** Textures and effects are now part of [[FGData]] and therefore do not need to be distributed separately.
** Traffic shader visualising cars on streets based on street type, time of day etc.
** Shader for lit streets.
* Custom sceneries can add and correct fixes and navaids.
** This is the logical extension to what was already possible for airports using the NavData/apt folder inside a scenery folder.
** FlightGear now looks for *.dat and *.dat.gz files in NavData/fix and NavData/nav in addition to NavData/apt (optional subfolders of each scenery folder).
** See [https://sourceforge.net/p/flightgear/mailman/message/35716882/ this message] for details.

=== Canvas System ===
* Additional APIs to update text elements more performance-friendly.

=== Nasal Scripting ===
* <code>get_cart_ground_intersection()</code> and <code>aircraftToCart()</code> {{flightgear commit|b80b9a|t=added}}.

=== Documentation ===

=== Highlighted new and improved aircraft ===
* [[Space Shuttle]] milestone 8 with complete 3d cockpit.
* [[Saab 35 Draken|Saab Draken]]
* [[Dassault Mirage 2000-5|Mirage 2000]]
* [[Saab 37 Viggen|Saab Viggen]]
* [[Ercoupe 415-C|Ercoupe]] with completely re-worked 3d model and effects.
* [[Lockheed Constellation]] with new dual-control protocol for a pilot and a flight engineer.
* Improvements to many AI aircraft.

=== Other ===
Parameter <code>--log-file</code> renamed to <code>--log-dir</code> ({{flightgear commit|dab685}}).

=== Bug fixes ===
* See [https://sourceforge.net/p/flightgear/codetickets/search/?q=status%3AFixed+AND+created_date%3A%5B2017-02-22T18%3A48%3A48Z+TO+*%5D our bugtracker] for a list, albeit incomplete, of the bugs fixed in this release.

[[Category:FlightGear changelogs]]
[[Category:New Versioning Scheme]]