FlightGear wiki - User contributions [en]

Moyes Dragonfly

2011-12-31T03:34:06Z

Reverse22:

{{infobox Aircraft
|image =Dragonfly-towing.jpg
|name =Moyes Dragonfly
|type =1-engine ultralight
|fdm =JSBSim
|status =production 1.0
|authors =Torsten Dreyer
|fgname = Dragonfly
}}

{|
|__TOC__
|}

== About the aircraft ==

This is a model of a Moyes Dragonfly, a microlight plane built by MOYES, Australia orignally designed by Robery Bailey of Florida. It is made of aluminium tubing, wing and empennage have a dracon skin. The pilot sits on the very front of the main tube with a breathtaking, undisturbed view.

The dragonfly has excellent slow flight characteristics and is suitable for towing of hang gliders.

The same basic design is also known as the Bailey Dragonfly, Bailey-Moyes Dragonfly, and has variants with considerable modifications and variations. The FGFS model is based on the design produced by Moyes.

<br clear="all" />

== Features ==
=== Basic flying ===
Basic flying features are quite simple and almost perfect as a starter for pilots. Takeoff and landing is simple and due to its slow flying speed, the Dragonfly is perfect for scenery exploration.
<br clear="all" />

=== Instrumentation ===
The airspeed indicator gauge can be configured to display either km/h, mph or kts by setting the property '''/instrumentation/airspeed-indicator/texture''' to either
* Airspeed-kmh.rgb
* Airspeed-mph.rgb
* Airspeed-kts.rgb
This can be done on startup as a command line switch or at runtime by setting the property with the [[Property browser]].

Example: Use airspeed indicator calibrated in KTS:
''fgfs --aircraft=Dragonfly --prop:/instrumentation/airspeed-indicator/texture=Airspeed-kts.rgb''

=== Banner towing ===
The FlightGear model of the Dragonfly supports banner towing. The banner to tow has to be picked up from the ground during the flight and can be released in flight before landing.

==== Configuration ====
Do use this feature, a small configuration file is needed telling FlightGear where the banners are on the ground. It is a small XML file placed in your FlightGear home directory (which is <tt>~/.fgfs</tt> on Linux and <tt>.../Users/.../AppData/Roaming/flightgear.org/</tt> on Windows) named <tt>groundbanner.xml</tt>. Create this file and paste the following content into it; it will tell FlightGear where to put the banner:
<syntaxhighlight lang="xml">
<PropertyList>
<groundbanner>
<path>Aircraft/Dragonfly/Models/GroundBanner.ac</path>
<lat type="double">37.6199</lat>
<lon type="double">-122.3735</lon>
<heading type="double">280</heading>
</groundbanner>
</PropertyList>
</syntaxhighlight>
This example places one banner at the runway intersection of [[KSFO]], left to 28R. There can be any number of <groundbanner> elements in the file, to place more of them.

You can verify that the banners were loaded on the output of your console window. For each configured and loaded groundbanner there is a message
GroundBanner created
[[File:Dragonfly-banner-onground.jpg|thumb|left|Banner on the ground]]
<br clear="all" />

==== Using ====
[[File:Dragonfly-banner-approach.jpg|thumb|left|Approaching the banner]]
[[File:Dragonfly-banner-gotcha.jpg|thumb|left|Banner picked]]
[[File:Dragonfly-banner-released.jpg|thumb|left|Banner released]]
<br clear="all" />
To pick up the banner from the ground, approach the rope between the two pylons at an altitude of less than 15ft agl. You have to be very close to the center of the rope to catch it.
When the pickup succeeded, a message is printed on the console window
banner-pickup
and you will notice a change in the flight-behaviour due to the increased drag caused by the banner on your tail. You can see the towed banner when looking back or changing the view.
you can release the banner by pressing the 'o' (lower case letter, not zero). You will notice a decrease of the drag and can see the banner falling down when looking at it.

== Issues ==
* aerodynamic coefficients are a very rough guess
* aerodynamics and movement of the banner is far from being realistic
* banners do not disappear from ground after pickup
* add a pilot when viewing from outside

=== Related lists ===
* [[Aircraft]]
* [[Table of models]]

== External links ==
* [http://www.dragonfly-germany.de/ Dragonfly Germany]
* [http://www.moyesamerica.com/forms/DragonflyFlightManual.pdf Original Flight Manual (PDF)]
* http://www.flightgear.org/

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

MPMap

2011-12-31T03:33:37Z

Reverse22:

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

[[File:MP_Server.jpg|thumb|270px]]
'''MPMap''' is a utility that shows us where (other) pilots are on the world map. It's based on Google Maps, so you could use map or satellite view.

Currently there are two servers providing MPMap:
*[http://mpmap01.flightgear.org mpmap01]
*[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:Software]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Mikoyan-Gurevich MiG-15

2011-12-31T03:33:25Z

Reverse22:

{{infobox Aircraft
|name = MiG-15bis
|image = MiG-15bis-Interior.jpg
|type = subsonic jet fighter
|livery = USSR 60x standart
|fdm = JSBsim
|status = beta (v20102909)
|authors = Lee Elliott: initial 3d model,
Victor Slavutinsky : Everything else
|fgname = MiG-15bis
|download|
|download = http://users.flightgear.ru/vitos/MiG-15.zip
}}
The real [http://en.wikipedia.org/wiki/Mig-15 '''MiG-15bis'''] is the most produced aircraft of its type, and it made a great impact in its time. It must have been the most known Russian fighter in the West.

Aim of MiG-15bis FG project is to reproduce the real aircraft restrictions, habits, and features, exactly in that sequence.

Firstly, this mid-50's fighter doesn't have many switches, but without switching them correctly You would not even take off. If forgotten gears stuck or can even be teared apart on high speeds really than You get that here too. If You can overheat engine or cutoff it by low throttle then here is the same. But You can be sure that if You can flight that thing in simulation then You would flight real plane, at least if it is ready-to-go.

Secondly, it is a jet, but not a modern supersonic fighter with reheated engine. At subsonic speeds it starts to act oddly in reality as well as in simulation.

Thirdly, if You can extract gears of real MiG by emergency procedure that includes lever, handles, and valve, then same is here. Again, there aren't so many switches as in modern airliner. But every switch behaves as it does in reality.

Rest of what You need to know to fly this FG model is in included documentation. Read it carefully before takeoff.

Hope that it will lead You to know more about the real MiG-15.

And wish You good flight,

Victor Slavutinsky, vitosnet@mail.ru.

== Airplane of the Week/Month ==

The MiG-15bis was reviewed as 'Airplane of the Week/Month' on June 9, 2011 as follows:

<b>Model</b>

In my opinion, the MiG-15bis has one of the best 3d cockpits of all Flightgear aircraft. Not only are all gauges specially designed with cyrillic letters for this plane, but also details like the low throttle safer are done in full 3d beauty. In addition to the main panel, there are also two fully functional side panels in the cockpit.

[[File: Mig15bis-cockpit.jpg]]

The exterior model is not done quite with the same impressive level of detail, visible from the interior e.g. in the somewhat rough lines of the canopy, but also shows a lot of detail, e.g. surface bumps, nice animations for canopy, gear, flaps and brakes, or the glow and smoke of the running engine.

[[File: Mig15bis-model.jpg]]

The MiG-15bis is one of the planes where reading the (very detailed) manual is necessary even to start the engine - the startup procedure is fairly complicated. But it doesn't stop here - there are also procedures simulated for engine restart in mid-air, for emergency gear and for emergency flaps extraction.

In addition, the plane comes with a full set of functioning weapons and a photo-camera, so both 'real' and mock dogfighting is quite possible, and the two droptanks can be used for bombing practice if so desired.

<b>Flight characteristics</b>

The JSBSim FDM of the MiG-15bis is quite smooth, and all in all the plane is not difficult to fly. It is very agile and has a mild stall characteristics (I couldn't get it to do anything ugly with me). In high-g turns, it loses energy rapidly, illustrating nicely that the MiG-15bis is not really a match for more modern jet fighters such as the F-16, but its climb rate and velocity also demonstrate well why jet fighters quickly won the Korean skies.

What is perhaps most interesting about the MiG-15bis is that the model simulates quite a lot of restrictions - flaps and gear break when the airspeed is too high, the plane itself breaks for too high g-loads and the engine can overheat and shut off. The latter point actually spoils the fun taking off after having finally mastered the engine startup - if you climb out full throttle, you may need to look up on the mid-air engine restart procedure more quickly than you thought...

Also the gear load limits are fairly restrictive - it requires some work to bring the plane down in one piece, one can't simply smash it onto the runway. In difficult winds, that can be a real problem, but since the plane handles usually well, it's worth practicing.

<b>My personal wishlist</b>

A bit more tolerant gear would be nice... and some texture details on the canopy itself.

<b>Things to experience</b>

There's lots of details to experience. The MiG has an arrestor lever for the throttle to prevent it from moving on its own at high-g. That's not just for fun - the throttle does move on its own when the lever isn't used! Also, try flying into the transonic regime and experience how the flight dynamics changes.

== Downloads ==
* [http://users.flightgear.ru/vitos/MiG-15.zip MiG-15bis]
* [http://users.flightgear.ru/vitos/MiG-15_Skin.zip MiG-15bis livery .xcf source files ]

== External links ==
* [http://en.wikipedia.org/wiki/Mig-15 Wikipedia]
* [http://www.airwar.ru/enc/fighter/mig15bis.html Airwar.ru]

{{Mikoyan-Gurevich}}

[[Category:Aircraft]]
[[Category:Military aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Messerschmitt Bf 109

2011-12-31T03:33:03Z

Reverse22:

{{infobox Aircraft
|image =109-1.png
|name =Messerschmitt Bf 109 G14
|type = single piston fighter
|livery = Luftwaffe
|fdm = Yasim
|authors = Detlef Faber
|status = production
|download = http://www.flightgear.org/Downloads/aircraft-2.0.0/#bf109
}}
The '''Bf-109 G14''' was the standard Luftwaffe [[:Category:Military aircraft|Fighter]] at the Beginning of WW2 and stayed first line until the end. Pilots liked the handling, but the narrow landing gear caused a lot of accidents.

== Notes to Pilots ==
First some notes on the propeller adjust mechanism:

This is no constant speed unit! Propeller pitch advance is gouverned by a running line dependent on the engine rpm/manifold pressure relation. There is a lever beneath the throttle quadrant to switch between automatic/manual adjust. Manual is the rear rest of the switch and should be used for startup and taxi.

The actual amount of propeller pitch is displayed on the clock shaped Instrument on the right side of the panel. The range counts counter clockwise starting at 12.30 (full fine) to 8.30 (full course).

=== Start up ===
Ensure propeller adjust automatic is set to manual, and the pitch is set to 11.00. Set cutoff lever (right of throttle lever) to open, operate primer (left of seat) 5-6 times. Switch ignition (left side of the panel) to M1+2. Open throttle a bit and pull the starter Handle (beneath Mag-Switch). Be sure to open(offen) the radiator flaps (lever right beneath the panel).

=== Take Off ===
Flaps (the left wheel on the left side of the seat) down 10 degrees, Take off at 1.1 ata Manifold Pressure. When advancing the throttle past 75% propeller pitch adjustment will engage automatically. Lift Tailwheel at 150-180 km/h. Be prepared to use Aileron against Torque and Rudder to counteract Swing. Lift Off at 200-210 km/h.
Climb with 1.1 ata (Max Continous Power) 1.3 ata is limited to 30 min. 1.4 ata is limited to 5 min. Radiator flaps can be set to automatic.
[[File:109-6.png|270px|right|thumb|Cockpit View]]

=== Landing ===
Beware: While engine runs on low rpm (or beneath 0.9 ata manifold pressure), switch automatic propeller adjustment off (Ctrl-p) or else the propeller

pitch will run too course. Set propeller
pitch to 10.30. Lower Flaps and Gear under 300 km/h. Open radiator flaps. Approach Speed is 200 km/h. A curved Approach is recommended, because visibility on Final is bad. Speed at Treshold should be 175 km/h. Flare to Threepoint attitude before touchdown. After Touchdown use Rudder to keep the Aircraft straight.
Don't forget to release Tailwheel lock (lever on the left cockpitwall) before taxiing off the Runway.

[[File:109-5.png|270px|right|thumb|at altitude]]

== Features ==
* bump- and specmapped exteriour and interiour model
* 3D Cockpit with Engine Flight Instruments and clickable Controls
* engine failure simulation
* selectable Loadout
* livery selection
* logo Selection

[[Category:Aircraft]]
[[Category:Historical aircraft]]
[[Category:Military aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

MBB Bo 105

2011-12-31T03:32:48Z

Reverse22:

{{infobox Aircraft
|image =Bo105.jpg
|name =Bo 105
|type =Helicopter
|fdm = YASim
|status = production
|authors = Melchior Franz, Maik Justus (FDM)
|ratingfdm =5
|ratingexterior=4
|ratingcockpit=4
|ratingsounds =5
|fgname =bo105
}}
'''MBB Bo 105''' was a turbine powered [[helicopter]] introduced in the 1970s by Messerschmitt-Bölkow-Blohm also known as PAH-1. It was later produced by Eurocopter. In FlightGear it is included among the [[FlightGear 1.0 default aircraft|default]] [[aircraft]] and is one the more well developed and easier to fly helicopters for versions [[FlightGear 0.9.10|0.9.10]] and [[FlightGear 1.0|1.0]]. It has three selectable liveries that can be changed with Y key, included a military variant with armament that can be fired.

== Aircraft help ==
{| class="prettytable"
! Key
! Function
|-
| <nowiki>{/}</nowiki>
| Shutdown/Start turbines
|-
| d/D
| Select next/previous door
|-
| Ctrl-D
| Open/Close selected door
|-
| i
| Toggle ignition switch
|-
| m/M
| Shift engine balance to right/left engine
|-
| n/N
| Engine power adjustment up/down
|-
| r
| Apply rotor brake
|-
| R
| Toggle rotor brake
|-
| y/Y
| Switch to next/previous variant
|-
| Ctrl-Y
| Open material dialogs
|-
| ,
| Fire machine guns/missiles
|-
| Tab
| Open/Close Bo105 config dialog
|-
| Middle mouse button
| Adjust power lever
|}

== Nice textures for the interior ==
Horacio has made a very nice new texture for the interior of the Bo 105. Get them here: “[http://www.grafikavirtual.com/fgfs/?sec=aviones.php Versión de prueba del BO-105]”

[http://www.youtube.com/watch?v=0ASyBX1i4sM Here you can view a video] of the improved heli.

== Gallery ==
{{Gallery|
Sitting inside the Bo105 on the right side of the cockpit|Bo105 cockpit.jpg|
Bo105 at a heliplatform in the [[FlightGear NL]] scenery|FlightGearNL-9.jpg}}

== External links ==
* [http://www.fas.org/man/dod-101/sys/ac/row/bo105.htm FAS Bo 105 / PAH-1]
* [http://en.wikipedia.org/wiki/MBB_Bo_105 Wikipedia: Bo 105]

{{Eurocopter}}

[[Category:Aircraft]]
[[Category:Helicopters]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Lelystad Airport

2011-12-31T03:32:33Z

Reverse22:

{{stub}}
{{infobox Airport
|name = Lelystad Airport
|image =EHLE_tower.png
|iata =LEY
|icao =EHLE
|type =Public
|owner =Schiphol Group
|city = Lelystad, the Netherlands
|runway= 05/23
|length= 1300 m
|material= Concrete/Asphalt
|runway2= 05/23
|length2= 430 m
|material2= Grass
|website =http://www.lelystadairport.nl/
}}
'''Lelystad Airport''' is an airport near Lelystad, [[the Netherlands]]. It is the biggest general aviation airport in The Netherlands and is also home to a large aviation museum, the [[Aviodrome]] ([http://www.aviodrome.nl/ Aviodrome Website]), which hosts [[FSweekend|the largest Flight Simulator event]] in the world periodically. The museum's former KLM [[Boeing 747-200]] which they have on display is a prominent feature on the airport.

An expansion of the airport is planned in 2010 which would allow mainly budget airlines, holiday charters and regional airlines using aircraft such as the [[Boeing 737]] and the [[Airbus A320]] series to operate from Lelystad. The expansion would include a longer runway, 2100 meters long, and facilities to handle the bigger aircraft and approximately 2 million passengers.

== FlightGear scenery ==
Lelystad and surrounding area can be found on scenery tile e000n50/e005n52.

[[Category:Airports in the Netherlands]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Soaring

2011-12-31T03:32:21Z

Reverse22:

[[File:Aerotow2.jpg|thumb|270px|[[Bocian]] being towed by a [[Piper J3 Cub]].]]
'''Gliding''' or '''soaring''' is a recreational activity and competitive air sport in which pilots fly unpowered [[aircraft]] known as gliders or sailplanes using naturally occurring currents of rising air in the atmosphere to remain airborne.<ref>[http://en.wikipedia.org/wiki/Gliding Wikipedia]</ref>

== Gliders in FlightGear ==
[[FlightGear]] has several glider models and winch, AI aerotow or [[Doing aerotow over the net|MP aerotow]] launching methods (in addition to the normal "in-air start" method).

{{Gallery|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Dragonfly|Moyes Dragonfly]]|Dragonfly-towing.jpg|
[[Paraglider]]|Paraglider.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[ASW-20 sailplane|Schleicher ASW-20]]|Asw20.jpg|
[[Glaser-Dirks DG-101G|DG-101G]]|DG-101G_001.jpg|
[[Glaser-Dirks DG-300]]|DG-300.jpg|
[[ASK-13 sailplane|Schleicher ASK-13]]|Ask13.jpg|
[[SZD-9bis Bocian-1E|Bocian]]|Bocian.jpg
}}

=== Winch launches ===
Winch launches are currently available with the [[SZD-9bis Bocian-1E|Bocian]], the [[Schleicher ASK 21|ASK21]], the [[ASK-13 sailplane|ASK-13]] and the [[Glaser-Dirks_DG-101G|DG-101G]]. With the Bocian, it is possible to click in the scenery on a point where you would like to place a winch; with both, you can use Ctrl-w to place a winch directly in front of the glider. Press w to start the launch (in the ASK you need to hold it down) and, once at the top of the tow, release the cable with W.

=== Aerotows ===
For aerotows, two types are possible - AI or human pilot (via [[Howto: Multiplayer|multiplayer]]). To get an AI aerotow, select either the ASK, Bocian or DG-101G, choose KRHV as your airport and select the KRHV_towing_demo in the "Scenario" list box in [[FGRun]]. You should see a J3 Cub wobble its way towards you from a nearby taxiway, and pause close to your aircraft. Press control-o to hook on to it, and hold tight... the O key releases the cable.

For a multiplayer aerotow, you obviously need to arrange a tow with a human pilot - full instructions are available at [[doing aerotow over the net]].

The DG-101G implements a third type for aerotowing: a drag robot. To setup the drag robot press D. Then use the key sequenze as for AI aerotowing to attach to the drag robot. Then press d to start the robot.

Gliders that use the [[UIUC]] FDM are not (yet) capable of winch or aerotow launches. For such gliders it is necessary to start in the air.

=== Thermals and sinks ===
[[File:Pinzgauer.jpg|thumb|270px|[[Schleicher ASK 21]] gliding in the [[Pinzgauer Spaziergang]] thermals scenario]]
Thermals and sinks are modeled, but they must be defined individually in a thermal scenario file. To see how this is done it would be best to examine the file called <tt>[[$FG ROOT]]/AI/thermal_demo.xml</tt>, which sets up 11 thermals and 6 sinks around San Francisco Bay. To learn more about AI scenarios in general, see the related article called [[AI Systems]]. Note that the thermals and sinks exist independently of FlightGear's weather system, so it's possible to have cloud layers that don't match your thermal heights. To prevent this you may want to manually set the cloud layers to match your thermals. Thermal cap clouds are available since about one month ''after'' 0.9.10 was released. If you are using 0.9.10 or earlier you can make cap clouds work by a) fetching the cap cloud model from CVS, and b) adding a <z-m> offset to the cap cloud wrapper file to put the cloud at the right altitude.

=== Extra soaring locations ===
If you'd like to discover the Austrian alpine region, you might want to read [[Pinzgauer Spaziergang]].

The [[A local weather system | Local Weather]] package has (for Flightgear more recent than 2.0.0) the option to automatically generate thermals along with the convective clouds. Thermals and cap clouds optionally also evolve in time.

== Learn the theory ==
For those wishing to gain a more in-depth knowledge of correct glider operation, the [http://www.faa.gov/library/manuals/aircraft/glider_handbook/ FAA glider handbook] makes good reading.

== Related content ==
* [[Improving Glider Realism]]

<references/>

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

FlightProSim

2011-12-31T03:32:08Z

Reverse22:

{{FlightGearVendors}}

[[Category:FlightGear vendors]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Zeppelin NT

2011-12-31T03:31:58Z

Reverse22:

{{infobox Aircraft
|image =Zeppelin_NT.jpg
|name =Zeppelin Luftschifftechnik LZ N07
|type =Airship
|authors =Anders Gidenstam
|fdm =JSBSim
|status-fdm =2
|status-systems =3
|status-cockpit =3
|status-model =3
|fgname =ZLT-NT ZLT-NT-copilot
}}

== Important controls / keys ==

=== Aerodynamic flight controls ===

* Rudder (Aileron input is also transferred to the rudder since the real NT has a side stick.) At low speed the rudder is automatically augmented by a tail mounted side thruster controlled by the flight control system.
* Elevator (The elevator trim is seldom used see below for pitch trim.)

=== Engines and thrust vectoring ===

The Zeppelin NT has a non-standard set of engine controls. The engines' throttles are controlled by govenors - the throttle levers select the desired RPM.

'''Engine controls'''
* RPM select levers (PgUp/PgDown) - Increase/decrease selected engine RPM.
* Mixture levers (M/m) - Leaner/richer mixture.

'''Thrust vectoring'''
* Side engine swivel ([/]) - Swivel side engines up/down. 0 - 120 degrees.
* Aft engine swivel (G/g) - Swivel aft engine down/up. -90/0 degrees.
* Thrust levers (N/n) - Decrease/increase thrust (i.e. propeller blade angle).

The levers in the cockpit can also be controlled via the mouse pointer, either by clicking on a lever (left mouse button increases / middle mouse button decreases) or pointing at it and rotating the scroll wheel.

[[File:Zeppelin_NT_center_console.jpg|thumb|600px|center|The engine and propeller controls on the center console.]]

=== Gas and Envelope ===

* F/f - Open/close the gas valve.
* Q/q - Inflate/deflate fore ballonet.
* A/a - Inflate/deflate aft ballonet.

The fore and aft ballonets (air-filled bags inside the envelope) serve two purposes: (i) by inflating/deflating they maintain the pressure differential and volume of the envelope when the gas changes volume; and (ii) the trim of the airship can be changed by the relative inflation of the ballonets. While the required envelope pressure dictate the total volume of the ballonets the airship can be trimmed by having one ballonet more or less inflated than the other.

==== Envelop pressure management ====
When the airship rises the gas in the envelope expands and consequently the the total volume of the ballonets has to decrease or the envelope pressure will increase. There are pressure relief valves that automatically open when the pressure in the ballonet exceeds a set limit (which is lower than that of the gas relief valve to prevent gas being valved before both ballonets are empty) but the prudent airship pilot would rather use the manual ballonet valves than rely on the relief valves.

When the airship descends the increasing ambient pressure causes the gas in the envelope to contract and to maintain the envelope pressure above the ambient pressure total volume of the ballonets has to increase. The pilot has to set the ballonet controls for inflation. If the envelope pressure drops too low an alarm will sound. Monitor the gas pressure gauge!

==== Pitch trim ====
On the Zeppelin NT pitch trimming is done via the relative inflation of the fore/aft ballonets rather than with the elevator trim. Shifting air between the ballonets moves the center of gravity.

* To trim towards nose heavy - set the fore ballonet valve for inflation and/or the aft for deflation.
* To trim towards tail heavy - set the aft ballonet valve for inflation and/or the fore for deflation.

If the airship is above ''pressure height'', i.e. the altitude where the lifting gas occupies the entire volume of the envelope, the ballonets are empty and cannot be used for pitch trimming (and the simulated airship is likely to go badly out of trim). Ascending above pressure height also result in loss of lifting gas, beware of losing too much or you will be unable to maintain the envelope pressure when descending to the ground again.

'''Center of gravity range'''
Take off and Landing
Maximum Forward 1344.5 in
Maximum Aft 1374.0 in
In Flight
Maximum Forward 1315.0 in
Maximum Aft 1374.0 in

=== Ballast ===

The Zeppelin NT has no ballast approved for inflight adjustment. Use on ground only.

* w - Show current on-ground weight. Only works when on the ground.
* W - Weigh off to 700lbs heavy by adding/removing ballast. Takes about 10 seconds and is only applicable when on the ground.
* D/d - Drop ballast in 1%/0.1% decrements.

=== Ground crew / Mooring mast ===

* Y - Release mooring mast connection or wire.
* U - Attach mooring wire. Only possible when close to a mooring mast.
* y/u - Play out/winch in mooring wire.
* Alt + click on terrain - Place the mooring mast.

When landing to a stationary mast (which is the usual case in FlightGear), approach straight into the wind and land slightly short of the mast and taxi up to it under precision control. Use the rear thruster to keep the tail wheel in the air while taxing. The Zeppelin NT is very maneuverable and can land with great precision. The Road & Track Magazine wrote this about the real one "can ... almost land on a dime (Jim Dexter actually tried this, and missed by the length of a dollar bill)". Achieving that (or any) kind of precision is by no means easy, though.

The mooring mast is visible over the multiplayer network. It is also possible for other pilots using Zeppelin NT to dock with your mast.

[[File:Zeppelin_NT_landing.jpg|thumb|600px|center|Approaching the mooring mast for landing.]]

'''Note:''' The mooring force calculations are sensitive to long frame times (i.e. very low fps). In particular this can cause instability during FlightGear startup. One workaround is to pause the simulation immediately on startup and continue when scenery objects and multiplayers have been loaded. A better option is to reduce /sim/max-simtime-per-frame to a sane number, e.g. 0.1 meaning that each frame is at most 0.1 simulated seconds (so if your fps drops below 10 the simulation will run slower than real-time).
This can be done in preferences.xml by modifying the line
<max-simtime-per-frame>1.0</max-simtime-per-frame>
to
<max-simtime-per-frame>0.1</max-simtime-per-frame>

== Cockpit and instruments ==

[[File:Zeppelin_NT_cockpit.jpg|thumb|800px|center|The cockpit of the Zeppelin NT.]]

== Handling instructions ==

'''Disclaimer:''' These instructions are derived only from common sense together with certain data from the certificate of airworthiness and have no connection whatsoever to any instructions for the real Zeppelin NT.

=== At all times ===
* Maintain envelope pressure above 1.2 inH2O (300 Pa; 6.3 psf)

=== Engine start ===
* Mixture rich
* Low RPM (PgDn)
* Thrust levers set for propeller blade angle close to 0
* Magnetos set to both (} } })
* Run starter as required (s)

=== Pre-take off ===
* Weigh off (W)
* Make sure the center of gravity is within the take off range (See "Pitch trim" above and the aircraft help.)
* Swivel engines as needed (usually side engines to 80 - 90 degrees up and aft engine 90 degrees down)
* Thrust levers set for propeller blade angle close to 0
* Max RPM selected

=== Take off ===
* Raise the tail using the thrust lever for the aft engine
* Rotate around the mast using rudder until the nose points straight into the wind
* Increase thrust on the side engines
* Release from the mooring mast (Y)
* Control the aircraft's attitude and climb with the side and aft engine thrust levers
* Transit to forward flight by gradually swivel the side engines down
* Don't return the aft engine to 0 degrees too soon.

=== Cruise ===

* Mixture rich of peak EGT
* Thrust levers set to max thrust/blade angle
* Use engine RPM select for thrust control
* Pitch trim for level flight as needed by moving the center of gravity (within the legal limits) (See "Pitch trim" above and the aircraft help.) (It usually needs to move forward quite a bit)

=== Approach ===
* Make sure the center of gravity is within the landing range (See "Pitch trim" above and the aircraft help.)
* Mixture rich
* Max RPM selected
* Engine swivel as needed (usually side 90 degrees up, aft 90 degrees down)
* Use thrust levers for thrust control
* Approach the mast straight into the wind

=== Landing ===
* Land and hold just short of the mast
* Connect the mooring wire (U + u)
* Slowly taxi towards the mast assisted by the winch until contact is made.

== Multiplayer dual control ==

This aircraft is equipped for [[Dual control]] over the FlightGear multiplayer network.

To use this feature the pilot and copilot select each other in their Co/Pilot selection dialogs available from the "Zeppelin NT"->"MP-(Co)Pilot" menu.

Alternatively the pilot sets the property /sim/remote/pilot-callsign to the callsign of the prospective copilot. This property can be set in the property browser, on the [[command line]] or in fgrun. Command line example:
fgfs --aircraft=ZLT-NT --prop:/sim/remote/pilot-callsign="someone"

The copilot uses the copilot "aircraft" ZLT-NT-copilot and sets the property /sim/remote/pilot-callsign to the callsign of the pilot. Command line example:
fgfs --aircraft=ZLT-NT-copilot --prop:/sim/remote/pilot-callsign="anybody"

'''Note:'''

1. The Co/Pilot dialog is only available in FlightGear 2.0.0 or later and might still have some flaws. Switching between different copilots might sometimes cause problems.
It is usually enough if the copilot restarts her/his FlightGear instance or moves far away and then back using the location menu in these cases.

2. If the pilot sets /sim/remote/pilot-callsign at runtime the copilot should preferably join MP ''after'' the pilot set /sim/remote/pilot-callsign or things might not work correctly. This doesn't seem to be an issue in FlightGear 2.0.0 or later.

3. Using the ZLT-NT-copilot it is possible to hitch a ride with any ZLT-NT on MP. However, unless you are the pilot "approved" copilot you will only be an observer (and will not, if there is no approved copilot, receive the full aircraft state from the pilot).

== Known problems ==

* The mooring force calculations are sensitive to long frame times (i.e. very low fps), which can cause FlightGear to crash during startup or make the airship start in a bad state.
'''Workaround''': Try setting /sim/max-simtime-per-frame to 0.1 seconds or less. This can be done in preferences.xml by modifying the line
<max-simtime-per-frame>1.0</max-simtime-per-frame>
to
<max-simtime-per-frame>0.1</max-simtime-per-frame>

* The engines sometimes behave oddly, in particular in landing configuration (high RPM and varying blade angles). The engine sound is also too loud and a bit strange as well. Work in progress.

* (FlightGear 1.9.x) Unfortunately the pressure alarm will sound at startup since the envelope isn't initialized in a pressurized state. The ballonet inflation levers are preset to maximum inflation so the operating pressure is usually reached within 60 seconds.

* (FlightGear 1.9.x) Obsolete copies of mp_broadcast.nas (e.g. from the WildFire or Air racing add-ons) could cause problems. The up to date version now resides in <tt>$FG_ROOT/Nasal/mp_broadcast.nas</tt>. Remove the others - there should be no need for them.

== External links ==

* [http://www.gidenstam.org/FlightGear/Airships/ Download page with other lighter-than-air aircraft for FlightGear.] Requires the LTA support available in FlightGear 1.9.0 or later. '''Note: The most up to date version of the Zeppelin NT is available in FlightGear/git.'''

* User drivable Scania mast truck add-on for [http://www.gidenstam.org/FlightGear/Airships/Aircraft/ZLT-NT-mast-truck-addon_fgfs-2.0.0.tar.gz FlightGear 2.0.0] and [http://www.gidenstam.org/FlightGear/Airships/Aircraft/ZLT-NT-mast-truck-addon_fgfsGIT.tar.gz FlightGear/git.]

* [http://www.gidenstam.org/FlightGear/DualControl/ More on multiplayer dual control].

{{Aerostat}}

[[Category:Aircraft]]
[[Category:Airships]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Suggested Prerecorded Flights

2011-12-31T03:31:38Z

Reverse22:

'''Prerecorded flights''' provide for a great view of the capabilities of [[FlightGear]] without needing to know how to fly.

The command to playback flight data is

--generic=file,in,25,flight.out,playback,repeat --fdm=external

To record flight data use

--generic=file,out,25,flight.out,playback

Note that these are "extra" commands; you still need the basics ([[$FG_ROOT|--fg-root]], --aircraft etc.). In [[FGRun]], you can find these options under the Advanced button, on the last page.

Since the data is in text file, with a bit of trial and error you can effectively trim the flight down to parts that you like. In theory you can splice them together as well.

Feel free to included transcoded data from real-world telemetry as well. (RC UAVs, GPS flight logs, etc).

== Some recommendations ==

=== Wow! demos ===
In general, people *love* fast flights - so a nice jet or turboprop doing visually interesting things make great short demos.
For a list of airports with challenging real-life procedures and surroundings, you may want to check out [[Challenging Airports]].
For a list of well-populated scenery areas, check out [[Suggested Airports]] - there's also a list for [[Suggested Aircraft]].

=== Demonstrating something in particular ===

Longer, more visually uninteresting flights are also very useful to demonstrate something unusual or unique - like landing on an aircraft carrier. Keep in mind that only the aircraft is recorded, so the AI is not repeatable.

=== Trim the flight ===
It's no fun watching an aircraft sitting on the runway for two or three minutes before take off. Open up the file in your favourite editor and delete the extra flight data at the start and end.

If you don't have a convenient airport nearby to what you want to demonstrate, then be open to dropping some of the take off and approach.

== Sample precorded flights ==
{|
|'''Name'''
|'''Contributor'''
|'''Link'''
|'''Description'''
|'''Time'''
|'''Aircraft'''
|'''Extras'''
|-
|KSFO loop
|Jentron
|http://www.jentronics.com/fgfs/flight2.out.gz
|Take off from KSFO, fly over Bay Bridge, Alcatraz, Golden Gate Bridge, go vertical just after the Golden Gate, fly over San Francisco, past Oakland, land back at KSFO.
|10 minutes
|F4-E (or F18)
|-
| Storch
|Jentron
| http://www.jentronics.com/fgfs/fi-156-flight.out.gz
|
|20 Minutes
| Fi-156, Fi-156-de (new), or perhaps the dhc2W
|w120n40.tgz scenery set
|-
|Acrobatics above SFO buildings in Zlin 50 LX
|Unknown
|http://seb.marque.free.fr/fichiers/flightgear/z50lx.out.gz
|Take off from KSFO, straight to SFO, acrobatics, then play with Golden Gate, back to KSFO. Should be dead several times in this flight ;) Magical of simulation!. Use "S" for smoke, "u" to stop smoke. Better to use with --prop:/engines/engine/rpm=2500.
|15 minutes
|Zlin 50 LX (z50lx)
|}

{{Suggested}}

[[Category:List]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

SketchUp to AC3D exporter

2011-12-31T03:31:24Z

Reverse22:

{{Infobox Software
| title = SketchUp to AC3D exporter
| logo =
| image =
| alt =
| developedby = James Turner and others
| initialrelease = 0.1 (1 September 2008)
| latestrelease =
| writtenin = Ruby
| os =
| platform =
| developmentstatus = Active (2008-)
| type =
| license = [[GNU General Public License]]
| website =
}}
With the '''SketchUp to AC3D exporter''', developed by James Turner and improved by others, you are able to export [http://sketchup.google.com SketchUp] models to the [[File Formats#.2A.ac|.ac fileformat]]. The script works on both the free version aswell on the pro version.

== Installation ==
You can download the script at [[:File:ac3d_export.rb|this link]]. Place the .rb file into your <tt>SketchUp/Plugins</tt> folder. Now restart SketchUp and the script should be visible through the <tt>Plugins > Export to AC3D</tt> menu.

NOTE: on Google Sketchup 8, users are able to export as a .dae file, and AC3D is able to import .dae files- meaning no conversions are necessary if texturising in AC3D.

== A note about textures ==
The AC3D exporter is set to export textures to the PNG format by standard. That means that for FlightGear to be able to display your model correctly, you will have to provide your textures in the .png format.

So if you have a texture in a format other than PNG, you'll have to transform it into PNG. One free program capable of this conversion is ImageMagick. You can download it here:

* [http://www.imagemagick.org/script/binary-releases.php#windows Windows]
* [http://www.imagemagick.org/script/binary-releases.php#macosx Mac]

Also see: [[AC files: Basic changes to textures and colors#Textures|AC files: Textures]] and [[Textures & Texture Maps in SketchUp#Correct display of texture colors in the AC file|SketchUp: Correct display of texture colors in the AC file]].

== Development ==
The script is still in development at the moment. The current progress as of 12 September 2008 is:

'''Done:'''
* Geometry export
* Texture export

'''Known Issues:'''
* Texture scaling on the model may appear wrong, further testing required
* Material properties are guessed, so may appear different from Blender defaults. SketchUp has very limited material controls, so manual editing may be required.

'''To do:'''
* Conversion of lat- and longitude locations.

== Development Update July 2011 ==
SketchUp models which are completed using the existing
SketchUp to AC3D exporter are rendered in FlightGear with double sided faces.

Though there is nothing wrong with double sided faces, there is a considerable saving in FG processing if single faces can be used. This affects fps (frames per second) and is particularly noticeable when entering an area which is heavily inhabited with buildings/models.

It is possible to export SketchUp models with single faces by using a new version of the exporter (adapted by VicMar & i4dnf).

The new version is named ‘ac3dS_export.rb’ and is available for download from:
http://vicmar.weebly.com/downloads.html
The ‘ac3dS_export.rb’ file should be placed in the same folder/directory as the existing exporter. In the SketchUp ‘Plugins’ menu, it will appear as “Export to AC3D (Single_Faced)” and should appear with the existing exporter. Do NOT remove the existing exporter.

The new version is recommended for use with SketchUp models which do NOT have any see through textures. It is also not recommended if your model has apertures like open Hangar doors, which allow a view inside the building, as the opposite walls will be invisible.

There is a work around for models which have see-through textures, but it is a chore to do, so it is recommended you use the existing exporter for such models.
{{3d}}

[[Category:Modeling]]
[[Category:Scenery enhancement]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Schleicher ASK 21

2011-12-31T03:31:09Z

Reverse22:

{{infobox Aircraft
|image = Pinzgauer.jpg
|name = Schleicher ASK 21
|type = Glider
|livery =
|authors = Heiko Schulz<br/>AJ MacLeod
|fdm = YASim
|status = early-production
|fgname = ask21
}}<div style="padding-left:20px;">''Not to be confused with the [[Schleicher ASK 21 Mi]].''</div>

The '''Schleicher ASK 21''' is a modern glass-reinforced plastic two-seater [[:Category:Gliders|glider]] with a mid-set wing and a mass balanced [[T-Tail|T-tail]]. The ASK 21 is designed primarily for beginner instruction, but is also suitable for cross-country flying and aerobatic instruction.

The ASK 21 is a suggested [[aircraft]] for the [[Pinzgauer Spaziergang]].

== Aircraft help ==
{| class="prettytable"
|Ctrl + w
|Place Winch 1000m in front of aircraft
|-
|W
|Toggle winch hook
|-
|w
|Increase winch speed
|-
|Ctrl + o
|Find aircraft for aerotow
|-
|o
|Lock aerotow hook
|-
|O
|Open aerotow hook
|}

== Related content ==
* [[Howto: Do aerotow over the net]]
* [[Soaring]]

== External links ==
* [http://en.wikipedia.org/wiki/Schleicher_ASK_21 Wikipedia]

[[Category:Aircraft]]
[[Category:Gliders|ASK 21]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Pt/Portal:Desenvolvedor/Avião

2011-12-31T03:30:57Z

Reverse22:

{{Template:MenuDePortais}}

{|style="border-spacing:8px; margin:0px -8px; width:100%;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">O Portal do Desenvolvedor de Avião</h2>
|-
|style="color:#000;"|
Este portal se destina a desenvolvedores de [[Pt/Avião|aviões]] para o [[Pt/FlightGear|FlightGear]] e tem o objetivo de reunir artigos relacionados aos aviões. Veja o [[Pt/Portal:Desenvolvedor|portal do desenvolvedor]] para mais artigos sobre o desenvolvimento em geral.

|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"

! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Texturas</h2>
|-
|style="color:#000;"|
* [[Pt/Criar uma textura|Crie uma textura]]
* [[Pt/Texturas e Multiplayer|Texturas e Multiplayer]]
|}

{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FDM</h2>
|-
|style="color:#000;"|
* [[Pt/Como adicionar um reversor de empuxo|Adicionar reversor de empuxo]]
* [[Pt/Modelo de Voo|Modelo de Voo]]
* [[Pt/JSBSim Commander|JSBSim Commander]]
* [[Pt/JSBSim|JSBSim]] • [[Pt/UIUC|UIUC]] • [[Pt/YASim|YASim]]
|-
|}

{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Piloto automático</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.org/Docs/XMLAutopilot/ Customizing the XML Autopilot]
* [[Pt/Recursos para o ajuste do piloto automático|Recursos para o ajuste do piloto automático]]
|}

|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Geral</h2>
|-
|style="color:#000;"|
* [http://wiki.flightgear.org/index.php/Category:Aircraft_TODO Lista de Tarefas para os Aviões] (TODO-list)
* [[Pt/Recursos para informação sobre aviões|Recursos para informação sobre aviões]]
* [[Pt/Manuais de aviões|Manuais de aviões]]
* [[Pt/Recursos para o desenvolvimento de aviônicos|Recursos para o desenvolvimento de aviônicos]]
* [[Pt/Recursos para o desenvolvimento de sistemas do avião|Recursos para o desenvolvimento de sistemas do avião]]
|}

{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Scripts em Nasal</h2>
|-
|style="color:#000;"|
* [[Pt/A linguagem interpretada Nasal|A linguagem interpretada Nasal]]
* [[Pt/Escrevendo um simples script em Nasal|Escrevendo um simples script em Nasal]]
|}

|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Modelagem</h2>
|-
|style="color:#000;"|
* [[Pt/Modelos 3D de aviões|Modelos 3D de aviões]]
* [[Pt/Rotação do avião em torno do nariz|Rotação do avião em torno do nariz]]
* [[Pt/Como adicionar iluminação no avião|Como adicionar iluminação no avião]]
* [[Pt/Tutorial sobre Normais e Transparências|Tutorial sobre Normais e Transparências]]
* [[Pt/Como diminuir o número de faces|Como diminuir o número de faces]]
* [[Pt/Importação e exportação de modelo|Importação e exportação de modelo]]
* [[Pt/Iniciação à modelagem 3D|Iniciação à modelagem 3D]]
* [[:Category:Modeling|Categoria Modelagem]]
* [[Pt/Recursos para modelagem|Recursos para modelagem]]
* [[Copyright Inquiry|Direitos Autorais]] ''(em inglês)''

* [[Pt/AC3D|AC3D]] • [[Pt/Blender|Blender]] • [[Pt/SketchUp|SketchUp]] • [[Pt/Wings 3D|Wings 3D]]
|-
|}

|class="MainPageBG" style="width:25%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Como...</h2>
|-
|style="color:#000;"|

* [[Pt/Como criar um avião|Criar um avião]]
* [[Pt/Como|Criar um helicoptero]]

* [[Pt/Como configurar visões no FlightGear|Configurar visões no FlightGear]]
* [[Pt/Como criar instrumentos para o painel|Criar instrumentos para o painel]]
* [[Pt/Como criar tutoriais interativos|Criar tutoriais interativos]]
* [[Pt/Como definir limites de velocidade|Definir limites de velocidade]]
* [[Pt/Como implementar asa flexível|Implementar asa flexível]]
* [[Pt/Como implementar o pushback|Implementar o pushback]]
* [[Pt/Visão do tipo caminhada‎|Visão do tipo caminhada‎]]
|}
|}

__NOTOC__
__NOEDITSECTION__

[[es:Portal:Desarrolladores/Aeronaves]]
[[en:Portal:Developer/Aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Pt/Página principal

2011-12-31T03:30:41Z

Reverse22:

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:100%; color:#000"|


{| style="width:100%; border:solid 0px; background:none;"
|style="width:100%; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Bem-vindo à Wiki do FlightGear!</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">nós temos [[Special:Statistics|{{NUMBEROFARTICLES}}]] artigos.</div>

[[File:de.gif|link=:de:Hauptseite]]
[[File:en.gif|link=:en:Main Page]]
[[File:es.gif|link=:es:Portada]]
[[File:fi.gif|link=:fi:Etusivu]]
[[File:fr.gif|link=:fr:Accueil]]
[[File:nl.gif|link=:nl:Hoofdpagina]]
[[File:pl.gif|link=:pl:Strona główna]]
[[File:pt.gif|link=:pt:Página principal]]
[[File:ru.gif|link=:ru:Заглавная страница]]
[[File:zh.gif|link=:zh:Main Page]]
|}


|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[Help:Tutorial|Editing]] '''·''' [[Help:Contents|Help]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|All pages]] '''·''' [[Special:Search|Search]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Simulador de Vôo FlightGear</h2>
|-
|style="color:#000;"|
[[File:FGlogo.jpg|left]] '''[[Pt/FlightGear|FlightGear]] Flight Simulator''' é um simulador de vôo maduro, sofisticado e de código fonte aberto (open-source) criado e mantido completamente por voluntários. O código fonte completo desse projeto está disponível via [[Pt/Git|Git]], livremente licenciado sob a [[Pt/Licença Pública Geral GNU|Licença Pública Geral GNU]]. O FlightGear [[Pt/FlightGear|versão 2.0.0]] foi lançado em 25 de Fevereiro de 2010.

O objetivo do projeto [[Pt/FlightGear|FlightGear]] inclui a criação de um framework de simulador de voo para uso em pesquisas e/ou ambiente acadêmico, para o desenvolvimento e outro propósito envolvendo a simulação de voo, e também como uma aplicação para o usuário comum. O projeto pode ser expandido e melhorado por qualquer pessoa interessada em contribuir, seja para esse ou para os [[Pt/Projetos relacionados|projetos relacionados]] ([http://www.flightgear.org/links.html lista de projetos]).

O FlightGear é distribuido com um conjunto de documentação devidamente ilustrada - o destaque para ''"The Manual"'', que está disponível em [http://mapserver.flightgear.org/getstart.pdf PDF] e [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. A Wiki do FlightGear foi iniciada em 2006 e atualmente cobre uma vasta gama de tópicos relacionados ao FlightGear.

'''Escolha um dos (sub)portais:'''

{|style="background:none;"
|style="font-size:95%; padding-left:10px; padding-right:20px; margin:0px; vertical-align: top; text-align:left; white-space:nowrap; color:#000;"|
* [[Pt/Portal:Desenvolvedor|Desenvolvedor]]
** [[Pt/Portal:Desenvolvedor/Modelagem 3D|Modelagem 3D]]
** [[Pt/Portal:Desenvolvedor/Avião|Aeronaves]]
** [[Pt/Portal:Desenvolvedor/Cenário|Cenários]]
|style="font-size:95%; padding-left:20px; margin:0px; vertical-align: top; text-align: left; border-left: 2px solid #d9e2e2; white-space:nowrap; color:#000;"|
* [[Pt/Portal:Usuário|Usuário]]
* [[Pt/Portal:Piloto|Piloto]]
|}

===== '''Se você é um novato, dê uma olhada no [[Help:Contents|manual]] antes de criar ou editar um artigo!''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Iniciante</h2>
|-
|style="color:#000;"|
* [[FAQ]]
* [[Pt/Como escapar dos erros comuns|Escapando dos erros comuns]]
* [[Pt/Como usar a função multiplayer|Multiplayer]]
* [[Pt/Novo no FlightGear|Novo no FlightGear]]
* [[Pt/Resolvendo Problemas|Problemas]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Utilizando o FlightGear</h2>
|-
|style="color:#000;"|
* [[Pt/Avião|Avião]]
* [[Pt/Voando de Helicóptero|Voando de Helicóptero]]
* [[Pt/Tabela de modelos|Tabela de modelos]]
* [[Pt/Tutoriais de voos|Tutoriais de voos]]
'''[[Pt/Portal:Usuário|Mais e além...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Desenvolvendo o FlightGear</h2>
|-
|style="color:#000;"|
* [[Pt/Compilando o FlightGear|Compilando o FlightGear]]
* [[Pt/Compilando o Terragear no Ubuntu|Compilando o Terragear no Ubuntu]]
* [[Pt/Gerenciador de Pacotes do FlightGear|Gerenciador de Pacotes do FlightGear]]
'''[[Pt/Portal:Desenvolvedor|Mais e além...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Novidades</h2>
|-
|style="color:#000;"|
{{News}}
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Imagem da Semana</h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Você sabia...</h2>
|-
|style="color:#000;"|
{{VocêSabiaMain}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Promoção</h2>
|-
|style="color:#000;"|
* [[Pt/Entrevistas sobre FlightGear|Entrevistas sobre FlightGear]]
* [[Pt/Vídeos sobre FlightGear|Vídeos sobre FlightGear]]

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[en:Main Page]]
[[de:Hauptseite]]
[[es:Portada]]
[[fi:Etusivu]]
[[fr:Accueil]]
[[it:Pagina principale]]
[[nl:Hoofdpagina]]
[[pt:Página principal]]
[[pl:Strona główna]]
[[ru:Заглавная страница]]
[[zh:Main Page]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Pt/FlightGear

2011-12-31T03:30:14Z

Reverse22:

{{Infobox Software
| title = FlightGear
| logo = fglogosm.jpg
| image = FlightGear - 1903 Wright Flyer.jpg
| alt = [[Wright Flyer (UIUC)|Wright Flyer]] na versão 0.9.9
| developedby = Comunidade do FlightGear
| initialrelease = 17 de Julho de 1997
| latestrelease = 2.0.0
| writtenin = C++
| os = Windows, Linux, Mac OS X, FreeBSD, Solaris ou IRIX
| platform = Várias
| developmentstatus = Ativo (1996-)
| type = Simulador de voo
| license = [[GNU General Public License]]
| website = http://www.flightgear.org/
}}

[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] no FlightGear 1.0]]

'''O Simulador de Voo FlightGear''' (abreviado como '''FlightGear''' ou '''FGFS''') é um simulador de voo sofisticado, livre, completamente feito em código aberto, criado por voluntários. FlightGear é publicado sob os termos da [[GNU General Public License]]. A maior parte do FlightGear é escrita na linguagem de programação C++.

Versões cada vez mais detalhadas e realistas do FlightGear tem sido lançadas todo ano desde que o projeto foi lançado em 1996.

A última versão estável está disponível para download em [http://www.flightgear.org/Downloads/ http://www.flightgear.org/Downloads/], com compilações para vários sistemas operacionais incluindo o Microsoft Windows (32 e 64 bits), Mac OS X, Linux, IRIX, e Solaris.

== História ==
{{main article|FlightGear History}}

O desenvolvimento do FlightGear começou com uma proposta online em 1996, usando gráficos cutomizados em 3D. O desenvolvimento de uma versão em [[Pt/OpenGL|OpenGL]] foi iniciado por Curtis Olson em 1997. Muitas pessoas já contribuíram para o projeto desde sua concepção.

FlightGear incorporou outros recursos em código aberto ao invés de começar "do zero". Um deles é o modelo e voo LaRCsim da NASA e dados de elevação livres (SRTM). Os primeiros binários funcionando (.exe) saíram em 1997. Um grande desenvolvimento comunitário de novas versões resultou em versões progressivamente mais estáveis e avançadas. Por volta de 2001, o time estava lançando novas versões beta regularmente, e em torno de 2005, a maturidade do programa causou mais avaliações e aumentou a popularidade do FlightGear. Em 2007, o projeto saiu da fase beta com o lançamento da versão 1.0.0, dez anos após o lançamento inicial do FlightGear em 1997.

[[File:FG-A-10.jpg|thumb|270px|Cockpit 3D do [[A-10]] na versão 1.0.0 em 2008]]

Em 2008, a versão 1.9.0 do FlightGear foi lançada com a transição do sistema [[Pt/PLIB|PLIB]] para o sistema [[Pt/OpenSceneGraph|OSG]], o que causou a perda temporária de algumas funções como nuvens 3D e sombras. Porém, novas funções gráficas (como partículas) aumentaram o realismo gráfico do FlightGear.

== Software ==

O motor de simulação do FlightGear é chamado de [[Pt/SimGear|SimGear]]. É usado tanto para pesquisa acadêmica quanto para simulação de voo.

FlightGear é altamente customizável, possuindo desde [[:Category:Gliders|planador]]es até [[Pt/Helicóptero|helicópteros]], [[:Category:Airliners|jatos comerciais]] e [[Military aircraft|aviões militares]]. Esses modelos foram desenvolvidos por diversas pessoas.

As aeronaves do FlightGear utilizam um dos três modelos de voo: JSBSim, YAsim ou UIUC. Atualmente, apenas um motor de terreno é usado, TerraGear. Efeitos de clima incluem nuvens 3D, efeitos de luz, hora do dia, entre outros.

=== Modelos de voo ===
[[Pt/Modelos de Voo|Modelos de voo]] (FDM ou MDV) são como o voo é simulado no FlightGear. Toda aeronave precisa ser programada com um MDV para que o simulador saiba seu peso, velocidade de estol etc. UIUC e YAsim foram desenvolvidos especialmente para o FlightGear.

As primeiras versões utilizavam uma variante do MDV [[Pt/LaRCsim|LaRCsim]] da NASA, porém esse não era muito flexível, provocando a mudança para os MDVs atuais, mais flexíveis e realistas.

* [[Pt/JSBSim|JSBSim]] - o MDV padrão desde 2000.
* [[Pt/YASim|YASim]] - outro MDV utilizando outro tipo de cálculo. Apareceu pela primeira vez na versão 0.7.9 em 2002.
* [[Pt/UIUC|UIUC]] - mais um MDV, desenvolvido pelo UIUC Applied Aerodynamics Group na Universidade de Illinois em Urbana-Champaign, baseado no LaRCsim.
* FlightGear também pode usar MDVs externos (não incluídos por padrão), como o Matlab.
* Outros tipos de MDV para aeronaves específicas foram criados, como para dirigíveis e outras aeronaves mais leves que o ar.

=== Dependências ===
Ao contrário de softwares comerciais, tudo o que é feito no projeto sai em código-fonte C. Para transformá-lo em um programa utilizável, ele deve ser compilado para uma plataforma específica. As bibliotecas de software usadas para compilar o FlightGear têm mudado ao longo dos anos. A principal é a [[Pt/SimGear|SimGear]], que é a biblioteca usada para a simulação. [[Pt/TerraGear|TerraGear]] não é uma dependência, mas simplesmente um nome para o programa gerenciador de terreno padrão no FlightGear. O OpenAL é usado para som incluindo suporte à SDL (desde a versão 0.9.5). PLIB é usado para suporte de hardware e antigamente era usado para áudio, mas foi substituído pelo OpenAL. [[Pt/OpenGL|OpenGL]] é usado para suporte 3D e outro tipo de aceleração (como DirecX) não é suportada. O [[Pt/OpenSceneGraph|OpenSceneGraph]] é integrado ao FlightGear e serve para renderizar gráficos, em conjunto com o OpenGL. Por fim, Simple DirectMedia Layer é uma biblioteca de software que é usada para compilação. Algumas das dependências variam dependendo da plataforma para qua o código será compilado. Os usuários do FlightGear podem compilar o código por si próprios ou usar binários pré-compilados.

== Hardware ==
Os requisitos de hardware de que o FlightGear necessita são pequenos para máquinas que suportam o [[Pt/OpenGL|OpenGL]] e com aceleração de hardware 3D, com hardware da NVIDIA tendo o melhor suporte. As primeiras versões suportavam placas de vídeo 3dfx, porém isso foi cancelado porque os requerimentos de hardware aumentavam

[[File:Fgrun-page2.jpg|thumb|left|270px|O [[Pt/Assistente do FlightGear|Assistente do FlightGear]]]]
== Add-ons e customização ==
Há programas que estão integrados no FlightGear (dependências) e programas que se integrram como opcionais (add-ons). Alguns add-ons estão incluídos nos binários do FlightGear, dependendo do sistema operacional, como o [[Pt/Assistente do FlightGear|Assistente do FlightGear]], feitos pela comunidade. Porém, há add-ons independentes (não incluídas nos binários) mas que são hospedadas pelo FlightGear (como aeronaves).

Um software adicional (mas incluído) é a interface gráfica para iniciar o FlightGear. Por um tempo, no início, o FlightGear só podia ser iniciado através de uma [[Pt/Linha de comando|linha de comando]]. Porém, o controle gráfico de início do FlightGear foi incluído na versão 0.9.3 em 2003. ''[[Pt/KFreeFlight|KFreeFlight]]'' é um iniciador do FlightGear para KDE/Linux. o ''FGTools'' é um inciador alternativo para Windows. ''FGKicker'' é um iniciador baseado em GTK+.

Outros programas importantes incluem editores e projetos para terreno e cenário. ''[[Pt/Atlas|Atlas]]'' é um leitor de cartas e mapas para FlightGear.; ''[[Pt/Kelpie Flight Planner|Kelpie Flight Planner]]'' é um planejador de voo baseado em Java. ''[[Pt/FlightGear Scenery Designer|FlightGear Scenery Designer]]'' é um editor de cenário e terreno para FlightGear. O ''[[Pt/World Custom Scenery Project|World Custom Scenery Project]]'' é um projeto coordenando adições ao cenário como terreno detalhado e construções 3D. Por fim, ''[[Pt/TaxiDraw|TaxiDraw]]'' é um editor para pistas e pistas de táxi de um aeroporto.

=== Aeronaves ===

{{Main article|Table of models}}

O FlightGear começou com uma aeronave incluída do LaRCsim da NASA, um Navion, que foi trocado por um Cessna 172 em 2000. A criação e desenvolvimento do UIUC e JSBSim possibilitou o desenvolvimento de muito mais aeronaves, assim como o YASim, que então se tornou o MDV mais usado no FlightGear. Mais de 230 aeronaves estão disponíveis para o FlightGear 1.9.1, porém apenas poucas estão incluídas no instalador base do FlightGear.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300]] parado no cenário de [[EHAM]]]]

=== Cenário ===
{{Main article|Scenery}}
O [[Pt/Cenário|Cenário]] do FlightGear contém dados de elevação (SRTM) e dados de terreno do mundo todo. Objetos como terminais, moinhos e pontes estão na [[FlightGear Scenery Database|Base de Dados de Cenário]].

=== Rede e multi-display ===
Opções de rede possiblitam o contato entre vários usuários do FlightGear. Um protocolo de multiplayer está disponível para usar o FlightGear online com outros jogadores. Isso pode ser usado para voos em formação, linhas aéreas virtuais ou [[Pt/Simulação de Torre de Controle|Simulação de Torre de Controle]]. Outras funções incluem um mapa (MPMap) que possibilita usuários ver onde outros usuários estão.

Ver também: [[Pt/Tutorial de Multiplayer|Tutorial de Multiplayer]].

Também é possível sincronizar múltiplas instâncias do FlightGear para uso em diferentes monitores simultaneamente. Se todas essas instâncias estiverem sendo exectuadas com a mesma taxa de quadros (FPS), é possível ter boa sincronização entre displays.

== Código-fonte vs. binários ==

Ao contrário de muitos softwares comerciais, as datas de lançamento de versões correspondem ao lançamento do código-fonte, não o instalador executável. Para transformar o código em um programa utilizável, o mesmo deve ser compilado, o que necessita de bibliotecas específicas (ver a seção "Dependências"). Porém, como isto é uma tarefa difícil para a maioria dos usuários, outros contribuidores irão trabalhar para produzir arquivos pré-compilados (binários) para uma certa plataforma e sistema operacional. Estes arquivos variam em sua estabilidade, performance, dependências e o quão atualizadas estão em relação às outras.

Por exemplo, por volta de 2007 a última versão (experimental) era 0.9.11-pre1 e a versão 0.9.10 era a estável. Porém, os binários variam significativamente. Veja como estavam as versões após um ano do lançamento 0.9.10:

* Windows tinha um binário de 138 MB (v0.9.10) para Windows 98, 2000, ME e XP.

* Versões pré-compiladas para diferentes distribuições do Linux:
** Slackware (v0.9.10), Fedora Core 2,3 e 4 (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9).

* Solaris para processadores SPARC e x86:
** SPARC (v0.9.8), x86 (v0.9.9)

* Silicon Graphics IRIX (v0.9.9)

* Mac OS X:
** Mac OS 10.4 (v0.9.10)
** Mac OS 10.3 (v0.9.9)

* FreeBSD tinha um binário da versão 0.9.10

== Avaliações do FlightGear ==
{{Main article|FlightGear Reviews}}

== Ligações externas ==
{{Main article|Links}}
* [http://www.flightgear.org Website oficial]
* [http://fgfs.i-net.hu/ Website da comunidade]
* [http://www.caballerosaguila.shialeweb.com/ Website da comunidade em Espanhol]
* [http://gallery.flightgear.org.uk/ Screenshots dos desenvolvedores]

== Ver também ==
* [http://www.flightgear.org/proposal-3.0.1 Proposta original (em Inglês)] por David L. Murr (Revisão 3.0.1)
* [http://pt.wikipedia.org/wiki/FlightGear Artigo na Wikipédia]

[[de:FlightGear]]
[[es:FlightGear]]
[[nl:FlightGear]]
[[en:FlightGear]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Pt/Boeing 707-400

2011-12-31T03:30:00Z

Reverse22:

{{infobox Aircraft
|image = 707-400.png
|name =Boeing 707-400
|livery =Lufthansa, Varig PAX, Varig Cargo, Qantas
|type =Airliner
|fdm =JSBsim
|status =Development
|authors = Isaias V. Prestes, Innis Cunningham, Erik Hofman (FDM)
|fgname =707-400
|download =http://presteshangar.wikidot.com/boeing-707-400
}}
O Boeing 707 foi a primeira aeronave a jato, sem finalidade militar, a ser comercializada com sucesso. A sua introdução marca a chama Era do Jato. Devido ao seu sucesso, consolidou a Boeing como o maior fabricante de aeronaves a servir companhias aéreas no mundo. O nome do protótipo do 707 é chama Dash80.

== Desenvolvimento ==

* The initial standard model was the '''707-120''' with JT3C engines. Qantas ordered a shorter body version called the 707-138, which was a -120 that had six fuselage frames removed, three in front of the wings, three aft. The frames in the 707 were each 20 inches (500 mm) long, so this resulted in a net shortening of 10 ft (3 m) to 134 ft, 6 inches (41 m). Because the maximum takeoff weight remained the same 257,000 lbs (116 Tonne) as the -120, the 138 was able to fly the longer routes that Qantas needed.
* Braniff ordered the higher-thrust version with Pratt & Whitney JT4A engines, the 707-220.
* The final major derivative was the '''707-320''' which featured an extended-span wing and JT4A engines.
* The '''707-420''' was the same as the -320 but with '''Rolls-Royce Conway turbofan engines'''. British certification requirements relating to engine-out go-arounds also forced [[Boeing]] to increase the height of the tail fin on all 707 variants, as well as add a ventral fin, which was retrofitted on earlier -120 and -220 aircraft. These modifications also aided in the mitigation of dutch roll by providing more yaw stability.

[[File:707-400b.png|200px|thumb|left|The VARIG 707-400 PAX]]

== A Série -400 ==
A série -400 foi introduzida especificamente para atender um pedido da BOAC, ou seja, uma versão do 707 equipados com turbofans Rols-Royce Conway 508. Assim que iniciado o programa, a Lufthansa foi a primeira companhia aérea a realizar pedido e a Air India a primeira a receber um 400 em 18 de Fevereiro de 1960.

4 x Rolls Royce Conway (17150 lbf) turbofan engines Rolls-Royce Conway 508

== O 707-400 no Brasil ==

A Varig recebeu, a partir de 1960, 2 aeronaves Boeing 707-441, o PP-VJA e o PP-VJB. O PP-VJB acidentou-se em Lima, no Peru, em 1962, e a Varig o substituiu por outro 707-441, o PP-VJJ.
Os 707 da Varig faziam SNME além da linha para NY, que aliás, no começo tinha escala (ou mesmo início) em BSB, os 707-400 tb operavam a linha para LAX. Em 18 de novembro 1961 foi iniciada, também com o 707, a linha Rio de Janeiro - Los Angeles com escalas em Lima, Bogotá e México. Quando os 707 chegaram, o Galeão estava em obras para alongamento da pista. Por isso, os 707 faziam Brasilia, N.York,Brasilia. De Brasilia para o Galeão voavam os Caravelles. Quanto ao acidente em Lima, foi após a compra da Real, quando a Varig passou a voar para Los Angeles via Lima, extendendo depois até Tokio, após a chegada dos 320C. Recém inaugurada Capital do Brasil non stop para a Capital do Mundo via Boeing 707 Intercontinental, chique para a época!

[[File:707-400c.png|200px|thumb|right|Rolls-Royce Conway turbofan engines]]

== Ligações Externas ==

* [http://www.boeing.com/commercial/707family/ A família Boeing 707 na Boeing.com]
* [http://www.airlinercafe.com/page.php?id=72 Guia detalhado de todas variantes do 707/720 na airlinercafe.com]
* [http://www.airliners.net/aircraft-data/stats.main?id=87 Página do Boeing 707 na Airliners.net]

== Referência ==
* [http://en.wikipedia.org/wiki/Boeing_707 Wikipedia]

{{Boeing}}
[[en:Boeing 707-400]]

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:GPL model]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Pt/Aeronaves

2011-12-31T03:29:47Z

Reverse22:

Esta lista '''não está atualizada''' com todos aviões oficiais que se encontram sob a licença [[GNU General Public License|GPL]] para o FlightGear. Entretanto dá uma amostra visual dos tipos de aviões oficialmente disponíveis. Veja a [[Table of models|Tabela de modelos]] para uma listagem mais completa. Veja também os [[FlightGear hangars|hangares do FlightGear]] e hangares não oficiais (ou [[Helicopters|Helicópteros]], ou [[Vehicles|Veículos]] para mais exemplos e imagens)

Os exemplos listados aqui estão oficialmente disponíveis no projeto FlightGear e podem ser baixados em [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear.org Aircraft]. A instalação desses aviões geralmente requer um programa para descompactação (como o 7-Zip) e a instalação manual desses arquivos no diretório dos aviões do FlightGear ('pasta' se você usa Windows). [[FlightGear 1.0 default aircraft|Aqui uma lista dos aviões que já existem lá]].

As características, qualidade e compatibilidade dos aviões do FlightGear variam significativamente; pois o desenvolvimento desses aviões depende dos voluntários que trabalham em seu código - salvo alguns casos de projetos sob a guarda de universidades e governo americanos.

Lembre-se de que a lista é simplesmente uma amostra de alguns aviões e variações disponíveis para o FlightGear!

=== Aviões Civis Leves ===
O Cessna 172 é o avião padrão no FGFS.
{{Gallery|
[[Aerostar 700]]|Aerostar_700.jpg|
[[B&F FK9 Mark 2]]|FK9MK2.jpg|
[[Beechcraft Model 99]]|Beech99.jpg|
[[Cessna C172|Cessna 172P]] (1982)|Cessna_172P.jpg|
[[Piper Cherokee Warrior II|Piper Cherokee Warrior II (PA28-161)]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]] (1946) |Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II|Piper Seneca II (PA34-200T)]]|Piper_SenecaII.jpg|
[[Robin DR400]]|dr400.jpg|
[[Rallye-MS893E]]|Rallye-MS893.jpg
}}

=== Companhias Aéreas ===
Geralmente equipados com 2 até 4 motores turbofan e alguns dos mais complicados procedimentos de decolagem e aterragem (algo como múltiplos [[flaps]]). Além disso, aviônicos na vida real é voltada para aqueles com licenças de pilotos profissionais e certificações especiais. Entretanto, as possíveis simplificações do FG tornam essa tarefa muito mais fácil na simulação de voo.
{{Gallery|
[[Boeing 707]]|707.jpg|
[[Boeing 737]]|737-300.jpg|
[[Boeing 747-400]]|747-400.jpg|
[[Boeing 787]]|787.jpg|
[[Concorde]]|Concorde.jpg|
[[Fokker 50]]|Fokker50.jpg|
[[Tupolev 154]]|Tu154.jpg
}}

=== Helicópteros ===
{{Main article|Helicopter}}

Os helicópteros apresentam controles fundamentalmente diferente de aeronaves de asa fixa (ver ''[[Flying]] ''). O helicóptero moderno é geralmente equipado com 1 ou 2 motores de turbina, com um rotor principal com 2 até 6 lâminas.
{{Gallery|
[[Eurocopter Bo105|MBB Bo 105]]|FlightGearNL-9.jpg|
[[Eurocopter EC135|Eurocopter EC-135]]|Ec135.png|
[[CH-47 Chinook Helicopter|Boeing CH-47 Chinook]]|CH-47_Chinook.jpg|
[[Sikorsky S58|Sikorsky S-58]]|S58.jpg
}}

=== Gliders, Sailplanes, & Ultralights ===
Esses equipamentos quase sempre apresentam controles super simples, com mínimo avionicos. Voar de gliders ou sailplanes usando termais (ver [[Soaring]]) podem proporcionar uma experiência mais complicada. Ultraleves por outro lado estão entre os aviões mais simples no FG.
{{Gallery|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Dragonfly|Moyes Dragonfly]]|Dragonfly-towing.jpg|
[[Paraglider]]|Paraglider.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[ASW-20 sailplane|Schleicher ASW-20]]|Asw20.jpg|
[[Glaser-Dirks DG-300]]|DG-300.jpg
}}

=== Warbirds ===
FG inclui um vasto leque de lendários aviões militares. Complexidade e realismo são características marcantes do nível de desenvolvimento no trabalho de um específico avião desse tipo.
{{Gallery|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[P-51D Mustang]]|P51d-mustang.png|
[[Nakajima Ki-84‎]]|ki-84.jpg|
[[Saab J 35Ã– Draken|Saab J35Ö Draken]]|Saab_J35.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Supermarine Spitfire]]|Spitfire.jpg
}}

=== Aviões para Porta-aviões ===
O FG suporta aterrissagens e decolagem a partir de porta-aviões (2 está disponíveis no FG 1.0.0).
{{Gallery|
[[Douglas A-4 Skyhawk]]|Douglas_A4.jpg|
[[Grumman A-6E|Grumman A-6E Intruder]]|A-6E.jpg|
[[Blackburn Buccaneer]]|Buccaneer.jpg|
[[Grumman F-14 Tomcat]]|F-14.jpg|
[[Hawker Seahawk|Hawker Seahawk FGA6]]|Hawker_Seahawk.jpg
}}

=== Aviões militares da OTAN ===
O FG tem uma grande variedade de aviões militares, aposentados ou modernos, disponíveis. O grande destaque fica por conta da possibilidade de reabastecimento ar-ar com o venerável KC-135 e ''ordnance release'' de A-10.
{{Gallery|
[[Fairchild A-10]]|A-10.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[Boeing E-3 Sentry]]|E-3B.jpg|
[[F-15C Eagle]]|F-15C.jpg|
[[F-80C Shooting Star]]|F-80C.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[Hawker Hunter]]|Hawker_Hunter.png|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg
}}

=== Históricos ===
Alguns antigos avões, dos desconhecidos aos famosos, estão disponíveis com o mais variado nível de qualidade.
{{Gallery|
[[Couzinet 70]]|Couzinet70.jpg|
[[De Havilland D.H. 91 Albatross]]|dh91.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Lockheed 1049|Lockheed Constellation]]|Lockheed_1049.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg
}}

=== Miscelânia ===
Aviões experimentais, barcos voadores e de propósito específico.
{{Gallery|
[[Boeing 314]]|314.jpg|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[de Havilland Canada DHC-3 Otter]]|DHC-3.jpg|
[[GDT Hornet (autogyro)]]|Hornet.jpg|
[[Bell Boeing V22 Osprey|Bell V-22 Osprey]]|V22Osprey.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg
}}

=== Dirigíveis (Disponíveis a partir da versão 1.9.0) ===

Estas aeronaves se valem de um gás mais leve que o ar para se tornarem flutuantes. Além dos métodos de controle das aeronaves típicas, como elevator, leme e aceleração do motor, tornam-se opções lastro e controle de volume de gás e pressão.
{{Gallery|
[[Zeppelin NT]]|Zeppelin_NT.jpg|
[[ZF Navy free balloon]]|ZF_Navy_free_balloon.jpg|
[[Submarine Scout]]|Submarine_Scout.jpg
}}

=== Ficção Científica ===
Modelos alternativos proporcionam uma simulação de realidade diversa, mas pode também ser úteis para a exploração de um cenário.
{{Gallery|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Bluebird]]|bluebird_hovercraft.jpg
}}

== Relacionados ==
* Veja [http://scenemodels.flightgear.org/ Base de Dados de Objetos para Cenário FGFS ], para mais modelos de [[Scenery]]
* [[Howto: Multiplayer]], [[Installing Scenery|Instalando Cenários]], e [[Flying the Helicopter|Voando com um Helicóptero]].
[[en:Aircraft]]
[[es:Avión]]
[[fr:Avions]]

[[Category:List]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Property tree

2011-12-31T03:29:07Z

Reverse22:

{{PropertyTree}}The so called '''Property Tree''' in [[FlightGear]] is generally considered FlightGear's central nervous system and one of FlightGear's greatest assets!

This is because the Property Tree system provides access to low level run time state variables via a very intuitive tree-like hierarchy. This allows FlightGear's behavior to be easily controlled and manipulated at run time.

The FlightGear Property Tree is the common denominator for crucial run time state and also the interface to these internal state variables.

The concepts and mechanisms behind the "Property Tree" may not be immediately obvious to FlightGear beginners. This page is meant to help new users familiarize themselves with the FlightGear property tree.

To make it easier to manipulate the tree, start FlightGear with the following command line
fgfs --httpd=5480
Then after a few moments open in a new window - [http://localhost:5480 http://localhost:5480]

== Introduction ==
When a simulation is running, all the variables such as position, speed, flaps, cabin lights, et all are calculated and manipulated through a property tree.

The "virtual" tree that runs the simulation appears much like a directory/file structure. eg:
<pre>
/sim/aircraft = A333

/position/
/position/longitude-deg = '-122.3576677' (double)
/position/latitude-deg = '37.61372424' (double)
/position/altitude-ft = '28.24418581' (double)
/position/altitude-agl-ft = '22.47049626' (double)

/controls/seat/eject/initiate
/controls/electric/APU-generator
</pre>
Some of these variables are "calculated" within the sim, whilst others can be manipulated. Writing a variable is as easy as
/* Its my turn to play the sim */
set('/controls/seat/eject/initiate', 1)

The values can also be set from the httpd interface.

What makes FG powerful is that a new aircraft can easily be designed with its unique set of properties that somehow affect the simulation. The Aircraft model has an xml file of properties within the property tree.

This is why the property tree is not consistent with fixed variables, they are created dynamically, to represent a propeller plane vs Jumbo or even a "Caspian Sea Monster".

The property tree is read, written, accessed and manipulated in a variety of ways, such as
* internal compiled code within FG - the c/c++ code
* [[Nasal]] scripts - this is javascript like scripting with read/write to the property tree. This is the way most aircraft are implemented.
* sockets that are either in/out/bi - this allows send/recieve to the FG sim via sockets
* telnet interface - query and fly the plane on the command line (see [[Telnet usage]])
* html interface - fly the plane with a browser or an PDA
For example, multiplayer mode is accomplished by exchanging sets of variables from the tree (height, position, speed, etc).

== Flight Dynamics Model (FDM) ==
FlightGear uses a few [[Flight Dynamics Models]], such as
* [[JSBSim]]
* [[YASim]]
These flight dynamics models present themselves differently in the tree, using different variables, in different places. That is what an aircraft can be designed around.

[[Category:Nasal]]
[[Category:XML]]
[[Category:Property Tree]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Piper J3 Cub

2011-12-31T03:28:53Z

Reverse22:

{{infobox Aircraft
|image =Piper_j3cub.jpg
|name =Piper J-3 Cub
|type =Civilian aircraft
|fdm = [[YASim]]
|status =
|authors = <ul><li> David Megginson (3D, FDM)
<li> Jim Wilson (Instruments)
<li> Don Lavelle (3D remodel, instrument mods, pilot mods, effects, livery)</ul>
}}
The '''Piper J-3 Cub''' is a small, simple, light [[aircraft]] that was built between 1937 and 1947 by [[:Category:Piper|Piper Aircraft]]. With tandem (fore and aft) seating, it was intended for flight training but became one of the most popular and best-known light aircraft of all time. The Cub's simplicity, affordability and popularity invokes comparisons to the Ford Model T automobile.

The aircraft's standard yellow paint has come to be known as “Cub Yellow” or "Lock Haven Yellow".

== Aircraft help ==
=== Controls ===
{| class="prettytable"
!Key
!Function
|-
|d
|Open/Close Door
|-
|s
|Start engine
|-
|Ctrl-o
|Start/Stop aerotowing
|}

=== Manual ===
This section originally contained material which was suspected of not complying with the GPL and was removed.

The original Cub manual may be found by searching for "how to fly a Piper Cub" on the net. This link should also work - http://www.paragonair.com/N/70497/FLY_A_CUB.pdf

=== Pilot Check List ===
# chocks on
# check fuel quantity
# check controls movements
# switch fuel on
# check magneto off
# swing prop
# switch magneto to both
# swing prop
# chocks away
# check oil pressure
# check door close
# S-taxi to runway
# check all clear
# throttle to 1400 rpm
# check tachometer
# ease throttle forward
# at 100 feet ease tail up
# stick to neutral
# stick back pressure to 10 feet altitude
# stick neutral again
# climb
# fly
# prepare to land
# ease throttle back
# check carb heater
# glide to runway
# clear engine with throttle
# at 15 feet back pressure
# at 2 feet stick all way back
# no need to brake
# S-taxi
# switch magneto off

=== Aerotowing ===
The J3Cub is capable of [[Howto: Do aerotow over the net|aerotowing over multiplayer]] by the glider pilot pressing Ctrl-o while behind the Cub.

== Development status/Issues/Todo ==
The aircraft was fully remodelled in April 2010 and made available as the Cub. The original low resolution model is still available as the Piper J3 Cub in FGFS version 1.9.1 and older.

'''3D Cockpit:'''
* no switches and levers available
* altimeter can't be adjusted with the mouse

'''General:'''
* engine sound in cockpit differs only slightly from outside engine sound

'''Non-bugs:'''
* pilot door is open and partly in the the wing rods - this is accurate, and how the J3 can be flown
* does this airplane have flaps? - no
* no electrical system, therefore no cockpit, instrument, or aircraft lights - but there is an engine start to make it easy
* no HUD

{{Piper}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Civilian aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

New to FlightGear

2011-12-31T03:28:39Z

Reverse22:

''Note some parts of this article have not been updated for 2008''

== Getting started ==
=== Hardware requirements ===
For FlightGear to run smoothly, it requires a video card with OpenGL drivers. OpenGL 2.0 or higher is required for FlightGear 2.0 and later. Most modern PCs support OpenGL, but if you are having trouble with slow frame-rates, see [[Hardware Recommendations]] for more information.

FlightGear is known to have graphics problems and slow framerates with most laptops. Since laptops are smaller, the graphics card(s) on them are usually lower-end. See [[Notebooks known to run FlightGear]] for some reviews of several laptop systems.

=== Getting FlightGear ===
You may download the latest files from [http://www.flightgear.org/Downloads/ FlightGear Downloads] page. Choose the source or binary files appropriate for your particular system. Or, depending on level technical expertise you may choose the [[Git]] version if you wish to work with a development version of FlightGear. The Git version typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to acquire and install. In general, the development version is not advised to the average user. You may also order Flightgear on a set of DVDs, availible on [http://www.flightgear.org/dvd/]

=== Installing on Windows ===
After installing FlightGear on Windows a dialog box appears to define file locations.

The first line asks for FlightGear Executable. Use the browse button to navigate to the location of fgfs.exe (in the default setup that is <tt>C:\Program Files\FlightGear\bin\win32\fgfs.exe</tt>).

The second line asks for [[$FG ROOT|FlightGear Root]]. Use the browse button to navigate to the <tt>data/</tt> directory or enter the location of the 'data' directory (in the defualt setup that is <tt>C:\Program Files\FlightGear\data</tt>). This will populate the scenery box as well.

Once you have defined these default settings, continue the installation as explained below.

=== Installing on Mac OS X ===
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. 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 http://macflightgear.sourceforge.net/home/documents/users-guide/ for more details.

If you want to launch flightgear using command-line, launch <tt>/Applications/Utilities/Terminal.app</tt> and type the following.

cd /Applications/FlightGear.app/Contents/Resources
./fgfs --options.....

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:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=$FG_ROOT/Scenery

After launching the GUI launcher, you will have the alias to [[$FG ROOT]] at $HOME/Documents/Flightgear/<version> so you can browse the data folder using Finder.

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 installing new aircraft.

=== Configuring OpenGL ===
FlightGear runs best with current [[OpenGL]] video drivers. If you are having trouble running FlightGear smoothly, see [[Configuring OpenGL]] for more information.

=== Getting scenery ===
{{Main article|Howto: Install scenery}}
A limited set of [[scenery]] comes installed with FlightGear, which consists of the area surrounding [[San Francisco International Airport]] (KSFO).

In FlightGear, scenery is divided into two kinds of data:
* '''Objects''' are the buildings, bridges and radio towers, etc. that represent three-dimensional structures.
* '''Terrain''' represents the contours, elevations and type of ground you fly/taxi over.

All object data goes in an Objects/ directory and all terrain data goes in a Terrain/ directory. The location of the scenery and its sub-directories depends on your particular installation.

To download objects and terrain for FlightGear, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page. On this page follow the link to download scenery from the map. Choose a block from the map where you will by flying. Once the package has downloaded, extract into your FlightGear scenery directory.

The scenery packages available from the FlightGear website contain both Objects and Terrain for the locations.

You may obtain additional and more up to date scenery Objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database].

Information beyond this brief overview is available in [[Installing Scenery]] and [[Downloading New Flightgear Scenery for Windows XP]]

=== Getting aircraft ===
{{Main article|Howto: Install aircraft}}
To download additional [[aircraft]] for FlightGear individually, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page, then choose [Aircraft Downloads http://flightgear.org/Downloads/aircraft-2.0.0/].

Once the aircraft package has downloaded, decompress and extract the archived files onto your computer. You may extract to a temporary directory and move them, or extract directly into the Aircraft directory in FlightGear. This is typically <tt>[[$FG ROOT]]/data/Aircraft</tt>.

=== Starting FlightGear ===
Many users choose to start FlightGear from the command line ("console" or "shell" as it is known to Unix users). Alternatively some use graphical interfaces such as [[FlightGear Launch Control|Fgrun]] (FlightGear Launch Control).

To start FlightGear type on the command line:

fgfs

and hit enter. This will start FlightGear.

If FlightGear fails to start, it is likely the compiled FlightGear binary software is not in your path. If you know Unix, you may add the location of the binary to your path and try starting again. Otherwise, you may find the location of the 'fgfs' binary and enter an absolute path to it like

/usr/games/fgfs

The location depends on your particular system and choices you made during compile and installation.

It is important to understand when not using a graphical interface to start FlightGear, your interaction will be entirely from the command line. To see available aircraft, you specify an option on the command line. To specify an aircraft, an airport, multiplayer server, etc. you add an option to the command line when starting FlightGear. Please consult the list of [[Command Line Parameters]]. The parameters are also useful to those starting FlightGear from [[FlightGear Launch Control]] graphical interface, as it allows you to specify parameters.

=== Displaying available aircraft ===
From the command line:

fgfs --show-aircraft

displays a list of available (installed) aircraft.

=== Choosing an aircraft ===
From the command line:

fgfs --aircraft=foo

where foo is the name of the folder the aircraft files live in. See also [[Command Line Parameters]].

=== Online multiplayer flying ===
{{Main article|Howto: Multiplayer}}

=== Using the Keyboard and Mouse ===
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. Other adjustments may be made with the keyboard.

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. A chart displaying what each key does will display.

To use the mouse to fly the aircraft, right click and move the mouse to direct the aircraft, right click again to look around, click again to return to normal.

=== First time in the cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the 'virtual cockpit?' Not all FlightGear aircraft come with an interior, including a virtual cockpit. (Due to FlightGear being used by various research projects, some aircraft may not even come with an exterior model. Remember, FlightGear is very flexible.) A 2D panel may display over the 3d cockpit if one exists. You may turn this off using the View menu. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected.

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. Use the Zoom keys to zoom in on an instrument. The 'x' and Shift-X keys control eyepoint zoom in the Cockpit View. Use the joystick hat (or other controller assigned to this function) to pan the eyepoint to the instrument you wish to read. Then zoom in.

Alternate Method: Click the right mouse button until you get a cursor with two arrows (like this <=>). You can now move your view around the cockpit. Press 'x' and Shift-X to zoom in and out.

'''Note:''' Some functions, such as starter or magneto, may be difficult to use or lack "hotspots" to control with your mouse. Especially when flying an aircraft model that is still undergoing development. In this case, look for equivalent controls on a 2D panel or resort to the keyboard. The keyboard controls always work according to the assignments listed on the Help Menu (unless reassigned by an aircraft or configuration). Go to the main window menu, click Help, then click Basic Keys or Common Aircraft Keys.

One of the first steps I take on entering an unfamiliar cockpit is to press Ctrl-C to highlight all the "hotspots" on the 3d cockpit instrument panel. This enables you to easily see where to place the mouse to operate an instrument's controls, buttons, knobs, etc.

Many aircraft offer a help menu specific to that aircraft on the Aircraft Help menu (go to Help, then Aircraft Help.

== Making your first flight ==
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 increased realism FlightGear provides. In a certain other flight simulator, some settings are turned down to make the aircraft easier to fly. This reduces effects such as propeller torque and p-factor, which may be the cause of the tendency to turn to the left (to figure out which effect, you may read more in [[Understanding Propeller Torque and P-Factor]]).

Despite marketing slogans to the contrary, some flight simulators are aimed at a casual game player market, and ship with their "realism" turned down. The realism is always turned up in FlightGear.

FlightGear offers a great deal of realism, which may be confusing to first time pilots.

* "Left Turning Syndrome" for the previously mentioned reasons.
* 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.
* The Vertical Speed Indicator is also subject to error.
* The Horizontal Situation Indicator is driven by a gyroscope (that is why it's sometimes called a Directional Gyroscope), which is subject to a phenomenon called gyro drift. For a number of reasons, the gyro will drift from its current heading and must be periodically (about every 15 minutes) calibrated to agree with the magnetic compass heading.

Many forces act on an aircraft in flight as well as on the instruments and systems 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.

=== Flying using navigational aids and the autopilot ===
To make this very clear for new users: 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. '''For aircraft that provide their own autopilot in the cockpit, you must 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 (generally).

FlightGear, as of version 0.9.9, comes with a "built-in" autopilot. The Autopilot dialog accessible from the FlightGear toolbar in the main FlightGear window does not work with all aircraft. It only works with aircraft that either
* do not specify an autopilot
* use the default autopilot. When an aircraft does not specify an autopilot, the default is used.

For aircraft that supply their own autopilot, you must use the autopilot controls in the 2D or virtual cockpit. The Cessna comes with a KAP140 autopilot in its virtual cockpit. You cannot use the Autopilot dialog with this aircraft. It has no effect. You must use the autopilot device in the panel.

For help with navigation see [[Understanding Navigation]]

=== Airports and navigation aids ===
When you first start FlightGear, whether from the command line or the graphical interface, you may wonder how to determine what airports are available. FGRun 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. Short of finding an actual sectional map for the area you wish to fly, what can you do?

[http://maps.google.com Google Maps] and the [[MPMap|FlightGear Online Map for multiplayers]] are both good resources as well as the FlightGear [http://fgfs.i-net.hu/modules/fgplanner/ Community Flight Planner].

== Getting help ==
Besides this wiki, there are more places that can be visited to obtain information or request help:
* Documents bundled with the release package.
* [http://flightgear.org/forums FlightGear Forum]
* [[FlightGear IRC channel]], the quickest way to get help.
* [[Malinglists|FlightGear users mailing list]], biggest chance to get in contact with developers.

== Getting more detailed information ==
This page is designed to give the user the essential things they need to know about using FG for the first time.

You now know enough to get started with FlightGear. To learn more, you may wish to start at the main page of this wiki and read the more detailed Getting Started section, or Using FlightGear section or study the Flying Resources to learn more about flight instruments and how to navigate and fly your aircraft.

Also, note that those using the Git version of FlightGear may choose to update their aircraft files through the Git system.

The following are some issues raised by new users of FlightGear. More detailed troubleshooting and answers can be found in [[Troubleshooting Problems]] and the [[FAQ]].

=== I do not want to compile FlightGear, what can I do? ===
[http://www.flightgear.org/Downloads/ Our website] offers precompiled binaries for download and install on a variety of systems. Current platforms are Windows, Linux, Solaris, SGI, Mac OSX and FreeBSD. These are offered as a convienence and availablility may vary at times.

Note: FlightGear is highly configurable through editable [[XML]] files. You are free, and encouraged to, make changes to aircraft flight models and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. The flight model is not defined in a binary file. It is easy to modify (given enough knowledge). Although the install is binary, most of FlightGear's system is open to configuration through XML files and [[NASAL scripting]].

=== Does FlightGear come with a printed manual? ===
You are invited to read "[[The Manual]]" online as [http://www.flightgear.org/Docs/getstart/getstart.html HTML]
or download a [http://mapserver.flightgear.org/getstart.pdf PDF] for viewing with Acrobar Reader or printing.

"The Manual" is not always up to date with recent developments but provides a good start for beginners.

== How you can help ==
{{Main article|Volunteer}}

=== Testing ===
* [[Building Flightgear|Build]] the latest Git code or download snapshots (link)
* [http://flightgear-bugs.googlecode.com File bug reports]

=== Debugging & Profiling ===
* Running FlightGear via valgrind to track down memory leaks

=== Support ===
* Help new users with downloading, compiling, installing and running FlightGear (http://www.flightgear.org/forums or on IRC)
* Provide Ideas & Suggestions, see: [[Feature Requests / Proposals / Ideas]]
* Help clean up this wiki
* Help provide new contents for missing wiki pages

=== Development ===
* Writing documentation! Everyone is welcome to contribute to "The Manual"; having at least a little experience with LaTeX makes the task easier. Please contact the authors of The Manual if you would like to add corrections or whole chapters, you may also simply use this wiki to contribute fixes, modifications and new contents.
* C/C++ Coding:
** provide source code cleanups (i.e. help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
** provide bug fixes [[Bugs]]
** provide enhanced features [[Feature Requests / Proposals / Ideas]]
** provide new features
** get involved in any of the other FlightGear-affiliated projects
* Aircraft development (3D modelling, textures, FDMs, scripting)
* Scenery development

[[de:Neu bei FlightGear]]
[[Nl:Nieuw bij FlightGear]]
[[es:Nuevo para FlightGear]]
[[fr:Nouveau sur flightgear]]
[[zh:FlightGear新手]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Long Term Goals

2011-12-31T03:28:25Z

Reverse22:

'''Note:''' this is not an official collection of goals, rather it is simply assembled from various mailing list discussions and thus reflects mainly personal goals of individual contributors, rather than the official set of goals of the FlightGear project as a whole. However, given that FlightGear is being developed by these very contributors, this should be a fairly representative list of long term goals.

= General =
* multi platform flight simulator: support as many platforms as possible
* provide an open framework for educational and scientific projects
* uncomplicated installation/deinstallation
* stable flight simulation platform
* framework for research related efforts (i.e. proof of concept avionics)
* provide a compelling and free alternative to commercial flight simulator products
* highly available (i.e. provide binaries for all supported platforms)
* provide fully interactive tutorials and courses

= Development & Contributions =
* encourage contributions and community involvement
* non-obfuscated architecture: expose all internals to users via public, well-documented interfaces
* framework-centric development philosophy and -model

= Realism =
* worldwide scenery coverage - available, look for "World Scenery"
* appropriate realism
* wide support for all sorts of aircraft (airplanes, helicopters, unpowered flight)
* realistic avionics modeling
* realistic weather modeling
* realistic IFR simulator
* realistic VFR simulator
* procedure trainer
* realistic visual and aural effects where appropriate
* realistic and complete systems modeling, including failure modeling

= Features =
* multiplayer support Mutiplayer
** Multiple players has been implemented.
** Multiple pilots/passengers per plane is currently in development
* support for multi-core architectures (SMP)
* support for networked distribution
* strive for eligibility for FAA PCATD/FTD certification
* provide support for use with virtual ATC facilities
* provide support for AI Traffic to populate the virtual world with aircraft

= Graphics =
* provide support for multiple output windows per instance
* multi-head/monitor support - for multiple screens per instance
* multi-accelerator support - for multiple 3D cards per running instance

= Hardware =
* support lower-end hardware
* support a wide range of input hardware (joysticks, yokes, pedals)
* support various makes of 3D accelerator cards

= Performance =
* appropriate startup and runtime performance
* provide playable framerates (>=20fps) in 1024x768 on older systems

= Footprint =
* appropriate download size
* appropriate memory footprint, resource consumption
* minimum amount of external dependencies
* reasonable build times

= Technical =
* conveniently extensible, even for non-programmers
* highly configurable and customizable
* fully runtime configurable [http://www.mail-archive.com/flightgear-devel@flightgear.org/msg09560.html]
* backwards compatible

== Code Base ==
* support as many C++ compilers and -versions as possible
* provide current project files for as many compilers/IDEs as possible
* modular design and architecture
* comprehensible source code
* tight code base
* quality code base
* well documented and commented

...

[[Category:Contributing]]
[[Category:Conventions & Guidelines]]
[[Category:List]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Livery

2011-12-31T03:28:13Z

Reverse22:

[[File:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]
On this page we describe how you make use of a script to get a '''livery selection dialog''' for an [[aircraft]] or [[vehicle]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

== A note to those who wish to make a livery ==
If your livery is likely to be edited by other users, consider making a paintkit in addition to your livery.

A paintkit is where you create a blank livery which shows only constructional elements like bolts, rivets, windows, doors and panels. This is done so any other users looking to create their own livery can make a realistic looking livery with these construction elements, without having to redraw them or trying to avoid painting over them. This makes the process of creating a livery a more fun and less stressful task.

Paintkits are usually provided within the aircraft's <tt>Models/</tt> directory and/or at [http://liveries.flightgear.org/paintkits.php the livery database].

== Files to edit ==
There are a few files we need to make (or edit), namely:
* <tt>...-set.xml</tt>
* <tt>Models/....xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/.../Models/Liveries</tt>.

=== Models/Liveries ===
For every livery we need to make a file. Let's say we got a KLM livery, we then need to make a file called <tt>KLM.xml</tt> in our <tt>Models/Liveries</tt> directory. When a particular livery is selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.
<syntaxhighlight>
<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<747-texture>Liveries/KLM.png</747-texture>
</livery>
</model>
</sim>
</PropertyList>
</syntaxhighlight>

In the example above, the texture files are also stored in the <tt>Models/Liveries/</tt> directory of the aircraft; the texture path is relative to the model's xml in which it is used.

=== Models/....xml ===
The first part is related to the nasal script. <tt>("Aircraft/747/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:
<syntaxhighlight>
<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/747/Models/Liveries");
</load>

<unload>
livery_update.stop();
</unload>
</nasal>
</syntaxhighlight>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of 3D modelling software like [[Blender]] or [[AC3D]]. The <tt><texture>Liveries/KLM.png</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''
<syntaxhighlight>
<animation>
<type>material</type>
<object-name>Fuselage</object-name>
<object-name>Hstab</object-name>
<object-name>Vstab</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>747-texture</texture-prop>
<texture>Liveries/KLM.png</texture>
</animation>
</syntaxhighlight>

=== Nasal/liveries.nas ===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/.../Models/Liveries");

=== ...-set.xml ===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!
<syntaxhighlight>
<model>
<path>Aircraft/.../models/....xml</path>
<livery>
<file type="string"/>
</livery>
</model>
</syntaxhighlight>

If you want the default livery to be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the appropriate livery.
<syntaxhighlight>
<file type="string">KLM</file>
</syntaxhighlight>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<syntaxhighlight>
<menubar>
<default>
<menu n="100">
<label>...</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>
</syntaxhighlight>

== Multiple texture files per livery ==
Some models use multiple textures file (e.g. separate files for fuselage and wings). Every texture needs it own property. You can add as many textures as you like.

=== Nasal/liveries.nas ===
This is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

=== Models/Liveries ===
Instead of just one texture we have to deal with multiple ones now.
<syntaxhighlight>
<?xml version="1.0"?>

<PropertyList>
<sim>
<model>
<livery>
<name type="string">KLM Royal Dutch Airlines</name>
<texture-fuselage>KLM-Livery-fuselage.png</texture-fuselage>
<texture-wings>KLM-Livery-wings.png</texture-wings>
</livery>
</model>
</sim>
</PropertyList>
</syntaxhighlight>
=== Models/....xml ===
<syntaxhighlight>
<animation>
<type>material</type>
<object-name>hull</object-name>
<object-name>nosecone</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-fuselage</texture-prop>
<texture>KLM-Livery-fuselage.png</texture>
</animation>

<animation>
<type>material</type>
<object-name>left-flap</object-name>
<object-name>left-aileron</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture-wings</texture-prop>
<texture>KLM-Livery-wings.png</texture>
</animation>
</syntaxhighlight>
Note that the texture-prop in both animations are different. They should match the tags around the textures in your <tt>Models/Liveries/</tt> files.

=== ...-set.xml ===
Is the same as "ordinary" aircraft with just one texture. You will find the content of this file earlier in this article.

== Performance Improvements ==
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

== Testing ==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

== Sharing your liveries ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Menubar]]
[[Category:Modeling]]

[[es:Livery_over_MP]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

GNU General Public License

2011-12-31T03:27:58Z

Reverse22:

The [http://www.gnu.org/copyleft/gpl.html '''GNU General Public Licence'''] ('''GNU GPL''' or simply '''GPL''') is a widely used free software licence, originally written by Richard Stallman for the GNU project. The GPL is the most popular and well-known example of the type of strong copyleft licence that requires derived works to be available under the same copyleft. Under this philosophy, the GPL is said to grant the recipients of a computer program the rights of the free software definition and uses copyleft to ensure the freedoms are preserved, even when the work is changed or added to. This is in distinction to permissive free software licences, of which the BSD licences are the standard examples.

The GNU Lesser General Public Licence (LGPL) is a modified, more permissive, version of the GPL, originally intended for some software libraries. There is also a GNU Free Documentation Licence, which was originally intended for use with documentation for GNU software, but has also been adopted for other uses, such as the Wikipedia project.

The Affero General Public Licence (GNU AGPL) is a similar licence with a focus on networking server software. The GNU AGPL is similar to the GNU General Public Licence, except that it additionally covers the use of the software over a computer network, requiring that the complete source code be made available to any network user of the AGPLed work, for example a web application. The Free Software Foundation recommends that this licence is considered for any software that will commonly be run over the network.

== FlightGear and GPL ==
FlightGear is released under the GNU GPL, which means that everyone may edit, change, or use models, source and textures freely. Most planes and scenery are also released under GPL.

== Related content ==
* [[Copyright Inquiry]]
[[es:Licencia General Pública GNU]]

[[Category:GPL]]
[[Category:License]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

FGFSPM

2011-12-31T03:27:45Z

Reverse22:

[[File:fgfspm.jpg|thumb|200px]]
'''FlightGear Package Manager''' ('''FGFSPM''') allows for installation and update (and will allow for uninstallation) of all kinds of [[FlightGear]]-related resources (including [[scenery]] tiles and updates to global objects and shared models, and even FlightGear's binaries). The latest version is .2 alpha, released in October 2008.

The program is developed in [[Java]] and requires [[Java]] version 1.6 (or later).

The Package Manager is based on the idea of packages, which are described by an [[XML]] document. The person who wants to provide a new resource, must simply pack the data in a ZIP file and create an XML document (a ''package descriptor'') to describe it. When the ZIP file and the XML document are published on the internet, users will simply have to type the XML document's URL inside the program to get the content installed and all its dependencies satisfied.

Updates also get simpler using the Package Manager, as users will simply have to ask the program to check for updates and it will automatically scan the list of installed packages looking for new versions of each on the net.

== Usage ==
The current version (a preliminary alpha release) of this program can be found at https://sourceforge.net/projects/fgfspm/
=== Installation ===
# Unzip the file somewhere on your computer.
# Launch <tt>dist/fgfspm.jar</tt>.
# You will be asked to set the FlightGear root. This must be your <tt>FlightGear/data</tt> directory.
=== Downloading new packages ===
# Launch the package manager and go to <tt>Packages > Install new package</tt>.
# Fill in the URL of the package descriptor file, mark URL, and click OK to install.
#* The statuswindow seems to be down at the moment, so don't quit if you think nothing happens.
=== Updating packages ===
# Launch the package manager and go to <tt>Packages > Update selected</tt> if you just want to update a single package, or <tt>Packages > Update everything</tt> if you like to update all packages in once.
#* In order for the update feature to work, you must have installed the package from an XML descriptor on the Internet. If the XML file you used was stored on your local machine, you'll have to act as if you wanted to install a new package in order to update it.

== Related content ==
* [[Simplifying Aircraft Deployment]] (RFC)
* [[Suggested Software]]
[[pt:Gestor de Paquetes de FlightGear]]

[[Category:Software]]
[[Category:Java]]
[[Category:GPL]]
[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 747-400

2011-12-31T03:24:52Z

Reverse22:

{{infobox Aircraft
|image = 747-400_KLM.png
|alt = KLM 744 flying over the Netherlands
|name = Boeing 747-400
|type = Airliner
|liverydbid = 1
|fdm = JSBSim
|status-fdm = 3
|status-systems = 3
|status-cockpit = 3
|status-model = 3
|authors = <ul><li>Gijs de Rooy<li>Ivan Ngeow (2D panels, hyd and elec systems)<li>Jentron (FDM support)<li>Syd Adams (PFD/ND displays)<li>Alexander Barrett (sounds)<li>Markus Bulik (autopilot)</ul>
|fgname = 747-400<br>747-400-fo
}}
[[File:747-400.jpg|thumb|270px|Exterior view of a KLM 747-400.]]
[[File:747-400_SIA_climbing_out_EGKK.png|thumb|270px|Singapore Airlines climbing out of [[London Gatwick Airport|Gatwick]].]]
[[File:747-400 pushback eham.jpg|thumb|270px|A KLM Boeing 747-400 ready for [[Howto: Implement pushback|pushback]] at [[Amsterdam Airport Schiphol]].]]The '''Boeing 747-400''', is the most recent version of the [[Boeing 747]] in service; and the best selling and most advanced model of the 747 family.

The 747-400 is being replaced by the [[Boeing 747-8i]], expected to enter service in 2012.

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

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

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

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

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

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

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

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

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

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

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

== Frequently asked questions ==
'''Why are the thrust reversers not working?'''
:Make sure throttle is at idle when engaging the thrust reversers. This is a safety feature from the real aircraft.

'''My yoke is obstructing the view on a display.'''
:Click the yoke to hide it. You can get it back via the <tt>747-400 > Show/hide yokes</tt> menu.

'''Why does my aircraft climb when I set flaps for landing?'''
:Flaps are not meant to slow your aircraft down. Slow down before you extend the next level of flaps.

'''My wings dissapeared?'''
'''My gear does not listen to the gear handle.'''
:FlightGear's 744 has a (basic) failure system.
:* When you're pulling an excessive amount of G's, the wings will snap off (and you'll loose all lift).
:* Landing gear will get stuck at its current position if it is lowered above V<sub>LE</sub> (maximum speed at which it is safe to fly with the landing gear extended).
:You can fix your aircraft via the <tt>747-400 > Repair</tt> menu.

[[File:747-400_cockpit.jpg|thumb|270px|3D cockpit of the Boeing 747-400 (under development)]]

== Development status/Issues/Todo ==
The latest version is always available at through [[Git]]. The author would happily receive your comments.

* FDM refinements; create a [[DATCOM]] model.

'''Outside:'''
* Details like pivot tubes and air inlets.
* Main gear textures.

'''Inside:'''
* Passenger cabin.

'''Flightdeck:'''
* Maintenance overhead panel.
* More (realistic) textures. All current textures are temporarily.
* More instruments and knobs/switches.

'''DualControl'''
* Splitting panels and instruments between both pilots, so you can simulate a real flightdeck crew of two.

== Related content ==
* [[Boeing 747-400 Tutorial]]

{{Boeing}}

[[nl:Boeing 747-400]]

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 737NG

2011-12-31T03:24:35Z

Reverse22:

{{non-stable}}

{{infobox Aircraft
|image =737-700.jpg
|alt =Boeing 737-700 in a brazilian airport
|name =Boeing 737-700
|type =Airliner
|livery =Gol, Varig
|authors =George Luiz, Isaias V. Prestes, Michel Maia
|fdm =JSBSim
|status =Alpha
|fgname =737-700
|download = http://www.4shared.com/file/143411275/54de1ad1/737-700_11.html
}}[[File:737-700ares.jpg|thumb|270px|Ares colors to 737-700]]The '''Boeing 737-700''' was the first of Next Generation series when launch customer Southwest Airlines ordered the variant in November 1993. The variant was based on the 737-300 and entered service in 1998. It replaced the [[Boeing 737-300|737-300]] in Boeing's lineup, and its direct competitor is the A319. It typically seats 132 passengers in a two class cabin or 149 in all economy configuration.

The 737-700C is a convertible version where the seats can be removed from the aircraft to carry cargo. There is a large door on the left side of the aircraft. The US Navy was the launch customer for the 737-700C.

Boeing launched the 737-700ER on 31 January 2006. All Nippon Airways is the launch customer, with the first one delivered on February 16, 2007. The 737-700ER is a mainline passenger version of the BBJ1 and 737-700IGW. It combines the 737-700 fuselage with the wings and landing gear of a 737-800. It will offer a range of 5,510 nautical miles (10,205 kilometers), with seating for 126 passengers in a traditional 2-class configuration. A competitor to this model would be the A319LR. The 700ER has the longest range for a 737.

At the end of July 2008, Delta Air Lines took delivery of the first of 10 -700 model aircraft fitted with Messier-Bugatti's carbon brakes.

All Nippon Airways, Japan’s second-biggest carrier, is to pioneer the model in Asia with a daily service between Tokyo and Mumbai. ANA’s service, believed to be the first all-business class route connecting to a developing country, was to start in September 2007 and use a Boeing 737-700ER outfitted with 36 seats and an extra fuel tank.

The C-40A Clipper is a 737-700C used by the U.S. Navy as a replacement for the C-9B Skytrain II. The C-40B and C-40C are used by the US Air Force for transport of Generals and other senior leaders. The Boeing 737 AEW&C is a 737-700IGW roughly similar to the 737-700ER. This is an Airborne Early Warning and Control (AEW&C) version of the 737NG. Australia is the first customer (as Project Wedgetail), followed by Turkey and South Korea.

= Development status/Issues/Todo =
== Inside ==

== Outside ==

== FDM ==

= Changelog =

{|
! Version
! Data
! Notes
! Download
|-
| 1.1
| 05/10/2009
| new cfm 56-7 XML and liveries.
| [http://www.4shared.com/file/143411275/54de1ad1/737-700_11.html 737-700_v1.1]
|-
| 4.3
| 30/10/2009
| new liveries.
| [http://www.4shared.com/file/144755877/8e96839c/737-300_43.html 737-300 v4.3]
|-
|}

= Reference =
* [http://en.wikipedia.org/wiki/Boeing_737 Wikipedia Boeing 737]

= External links =
* [http://en.wikipedia.org/wiki/Boeing_737 Wikipedia Boeing 737 article]
* [http://www.b737.org.uk The Boeing 737 technical site]

= Related content =
* [[Table of models]]

== Related lists ==
* [[Aircraft]]
* [[Aircraft Todo]]

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:GPL model]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 737-300

2011-12-31T03:24:20Z

Reverse22:

{{infobox Aircraft
|image =737-300.jpg
|alt =Boeing 737-300 in KLM livery
|name =Boeing 737
|type =Airliner
|livery =KLM, LH Retro 1986, AirFrance, MAERSK
|authors =David Culp, Innis Cunningham, Heiko Schulz, Brett Harrison, Emmanuel Barranger
|fdm =JSBSim
|status =Development
|fgname =737-300
|download =http://www.flightgear.org/Downloads/aircraft-2.0.0/#737-300
}}
The prototype of the '''Boeing 737-300''' rolled out of the Renton plant on 17 January 1984, and first flew on 24 February 1984. After it received its flight certification on 14 November 1984, USAir received the first aircraft on 28 November. A very popular aircraft, Boeing received 252 orders for it in 1985, and over 1000 throughout its production. The 300 series remained in production until 1999 when the last aircraft was delivered to Air New Zealand on December 17, 1999.

=== Liveries ===
The 737-300 1.9.1 was FlightGears' most repainted airplane. But the aircraft was refined in many ways, so the liveries from 1.9.1 don't fit anymore to 737-300 for 2.0.0.
So thanks to Brett Harrison, we have now two paintkits. One for Gimp: [http://www.mediafire.com/?yhm4uvzzmjm]and one for Inkscape:[http://www.mediafire.com/?keu2mizyvwj].
Already included are AirFrance, Lufthansa Retro and KLM. Maersk Air and many, many more soon to come will be available on the [http://liveries.flightgear.org/ official FlightGear's liveries page]!

== Features in 2.0.0 ==
* new built fuselage based on free datas from Boeing and free available scale drawings matching now the real dimensions and proportions
* wings done by Innis Cunningham scaled and textured
* vstab done by Innis Cunningham scaled and textured
* better texture mapping and paintkit
* contrails done with particles based on a script by Zan
* new wheels done by helijah
* added thrust reserver by Bertrand Coconnier
* using generic tyre smoke
* added pushback
* added some more contactpoints to the fdm
* start of an 3d-cockpit
* fdm refined: pointmasses and locations based on a real 733 Balance and Trim sheet
* autopilot stable now in all altitudes, every weight and on glideslope until approx. 25-0ft

As the aircraft is still in developement, following issues will be started to sort out this year:
== Development status/Issues/Todo (FGFS 2.0.0) ==
'''Outside:'''
* wings need still some refinement and UVmapping
* wheel well area still missing

'''3d Cockpit:'''
* 3d-mainpanel added- needs still a lot of work like adding all instruments, and make them all work correctly (!)

'''Interior'''
* better interior needed

'''General:'''
* engine sound in cockpit does not differ from outside engine sound
* engines can't be turned off

== External links ==
* [http://en.wikipedia.org/wiki/Boeing_737 Wikipedia Boeing 737 article]
* [http://www.b737.org.uk The Boeing 737 technical site]

== Related content ==
* [[Table of models]]
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:GPL model]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 737-100

2011-12-31T03:24:07Z

Reverse22:

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

{{infobox Aircraft
|image =737-100_outside.jpg
|alt =737-100 in Lufthansa colors
|name =Boeing 737-100
|type =Airliner
|livery = Air FLorida, Air France, Alitalia, Aloha Airlines, America West Airlines, Boeing N73700, Canadian Airlines, Continental Airlines, Continental Airlines (old), Lufthansa (default), KLM, Kuwait Airways, NASA, Qatar Airways, Singapore Airlines, Swiss Air
|authors =Emmanuel Baranger
|fdm =YASim
|status =Alpha
|fgname =737-100
|download =
}}

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 727-230

2011-12-31T03:23:57Z

Reverse22:

{{infobox Aircraft
|image =727-230.2.jpeg
|alt =Boeing 727-230 in LH livery
|name =Boeing 727-230
|type =Airliner
|livery =Lufthansa,
|authors =Heiko Schulz, Emmanuel Barranger
|fdm =YASim
|status =Alpha
|fgname =727-230
|download =
}}The '''Boeing 727''' is a mid-size, narrow-body, three-engine, T-tailed commercial jet [[:Category:Airliners|airliner]]. The first [[:Category:Boeing|Boeing]] 727 flew in 1963 and for over a decade it was the most produced commercial jet airliner in the world. When production ended in 1984, a total of 1,831 aircraft had been produced.

The model for [[FlightGear]] is currently alpha, but will have some nice eye candies like [[Howto: Implement generic tyre smoke|tyre smoke]], contrails, engine smoke, [[Howto: Implement pushback|pushback]], hopefully a good [[Cockpit|3d-flightdeck]], a good [[autopilot]] usuable from cockpit and a as near-as-possible-realistic [[FDM]]. As it is OpenSource all developers and users are invited to improve this aircraft to make it realistic as possible.

Last Version 0.2 from 10/18/2009

== Development status/Issues/Todo ==
'''Outside:'''
* wings not yet completed (fairings missing, flaps and slat animation could be better)
* stair missing
* animating passenger doors not yet
* completing texture mapping not yet
* livery-over-mp not yet
* lighting
* has tyre smoke
* has now pushback feature

'''3d Cockpit:'''
* mainpanel in the work, first added instruments

'''General:'''
* well, it is Alpha! ;-)

== External links ==
* [http://en.wikipedia.org/wiki/Boeing_727 Wikipedia Boeing 727 Article]
* [http://www.boeing.com/commercial/727family/ Boeing Homepage about the 727]
* [http://rbogash.com/727history.html page about the 727-prototype]
* [http://www.boeing-727.com/ unofficial site about the 727]

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 717

2011-12-31T03:23:45Z

Reverse22:

{{infobox Aircraft
|image =717-200.jpg
|alt =The Boeing 717 in the AirTran Airways livery
|name =Boeing 717
|type =Regional Airliner
|livery =AirTran Airways
|authors =Malik Guest, Skyop, Gary Neely
|fdm =JSBsim
|status =Development
|fgname =717-200
|download =http://flightgear.org/forums/viewtopic.php?f=4&t=6145&start=555#p119978
}}
[[File:717-cockpit.jpg|thumb|270px|The 3d cockpit, looking downward at the instruments]]
[[File:717-cockpit-overhead.jpg|thumb|270px|The 3d cockpit, looking upward at the overhead panel]]
[[File:717-mfd.jpg|thumb|270px|The 717's mult-function display, showing the selected [[VOR]]s, [[Multiplayer|multiplayer traffic]] in the area, and the next waypoint entered in the [[Route Manager]]]]
The '''Boeing 717''' is a twin-engine, single-aisle jet [[:Category:Airliners|airliner]], developed for the 100-seat market. The airliner was designed and marketed by [[:Category:McDonnell Douglas|McDonnell Douglas]] as the MD-95, a third-generation derivative of the DC-9.

The first order was placed in October 1995; however, McDonnell Douglas and Boeing merged in 1997 prior to production. The first planes entered service in 1999 as the Boeing 717. Production ceased in May 2006 after 156 units were produced. This plane is currently under production in flightgear with an expected release sometime halfway through 2010.

== Aircraft help ==
The knobs on the [[autopilot]] control panel can be adjusted by clicking the sides to increase and middle-clicking to decrease. You can also use the scroll wheel if your mouse includes one. Click the face on the front of a knob to perform its function.

=== Key commands ===
{| class="wikitable"
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Delete
| style="border: 0.125em solid black; padding: 0.25em;" | activate reverse thrust
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-b
| style="border: 0.125em solid black; padding: 0.25em;" | cycle speedbrake setting
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Tab
| style="border: 0.125em solid black; padding: 0.25em;" | cycle autobrake setting
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-z
| style="border: 0.125em solid black; padding: 0.25em;" | toggle autopilot Master Arm switch
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-y
| style="border: 0.125em solid black; padding: 0.25em;" | toggle autopilot Mach speed hold
|-
! style="border: 0.125em solid black; padding: 0.25em;" | Ctrl-o
| style="border: 0.125em solid black; padding: 0.25em;" | toggle autothrottle TO/GA set
|}

You can find a full list of autopilot key commands in the documentation included with [[FlightGear]].

=== Startup procedures===
1. APU master switch START. <br />
2. (Wait some seconds...) APU master switch RUN.<br />
3. APU electric generator ON.<br />
4. Engine 1 and engine 2 starters ON.<br />
5. Engine 1 and engine 2 cutoff switches RUN.<br />
6. Engine 1 and engine 2 electric generators ON. APU electric generator OFF.<br />
7. APU master switch OFF.

== Development status ==

=== Completed ===
* Animations
* Custom instruments
* Autobrake/speedbrake systems
* Autostart system
* APU system
* [[Livery over MP|Livery select]]
* [[Howto: Implement generic tyre smoke|Tire smoke]]
* [[Howto: Add contrails|Contrails]]
* [[Howto: Implement pushback|Pushback]]
* Engine fire system
* [[Howto: Animated jetways|Animated jetway]] definition

=== To-do ===
* FDM tweaking (as always)

== External Links ==
* [http://www.boeing.com/commercial/717 Official website]
* [http://flightgear.org/forums/viewtopic.php?f=4&t=6145&st=0&sk=t&sd=a Boeing 717 FlightGear Forum Topic]

== Reference ==
* [http://en.wikipedia.org/wiki/Boeing_717 Wikipedia]

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Blender

2011-12-31T03:23:15Z

Reverse22:

'''Blender''' is a open source 3D content creation suite available for all major operating systems under the [[GNU General Public License]] and available for free. <sup>[http://www.blender.org/]</sup> Many [[FlightGear]] developers use Blender, and there are a lot of articles on the FlightGear Wiki about using it.

'''Note:''' in order to import/export FlightGear's most common 3D format (AC3D, .ac) you must use Blender version 2.49b or older.

== Related content ==
=== Blender related articles ===
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender]]
* [[Blender Ground Signs Tutorial]]
* Aircraft modeling tutorial (flightgear-specific)
** by Helijah: Breguet Br-761 "Deux ponts"
*** [http://helijah.free.fr/flightgear/Creation/Creation-fr.htm In French]
*** [http://helijah.free.fr/flightgear/Creation/Creation-en.htm In English]
* Aircraft modeling tutorial (non-flightgear-specific)
** by Kevin Jongen: [http://www.websitetoolbox.com/tool/post/felixdk/vpost?id=2283400 Nieuport 11] and [http://www.military-meshes.com/forums/showthread.php?t=2232 additional discussion]
** by Samo: [http://forums.cgsociety.org/showthread.php?f=91&t=252648&highlight=blender+aircraft Policarpov I-15 Chato]
** by Witold Jaworski: [http://airplanes3d.net/wm-000_e.xml E-book "Virtual Modeling" ] on P-40B. With over 3600 pictures and 1112 pages. Currently only in Polish (no English). But you can try machine translation plus the use of many pictures :-)

=== Also related to modeling and Blender ===
* [[GMax2AC]]
* [[Howto: Illuminate faces|Illuminate faces]]
* [[Howto: Make a helicopter|Make a helicopter]]
* [[Model Import and Export]]
* [[Modeling - FAQ]]
* [[Modeling - Getting Started]]
* [[Modeling - SketchUp]]
* [[Normals and Transparency Tutorial]]
* [[SketchUp to AC3D exporter]]

== External links ==
* [http://www.blender.org/ Official website]
* [http://wiki.blender.org/index.php/Main_Page Official wiki]
* [http://www.blender.org/download/get-blender/ Get Blender]

{{3d}}

[[Category:Modeling]]
[[Category:Software]]
[[Category:GPL]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Autopilot

2011-12-31T03:23:01Z

Reverse22:

[[File:Autopilot.jpg|thumb|270px|The autopilot setting dialog of FlightGear.]]

An '''autopilot''' ('''AP''') is a mechanical, electrical, or hydraulic system used to guide a vehicle without assistance from a human being. Most people understand an autopilot to refer specifically to [[aircraft]], but self-steering gear for ships, boats, space craft and missiles is often also called by this term.

The autopilot of an aircraft is sometimes referred to as "George".

== Autopilot in FlightGear ==
We have a generic one and custom ones written for a certain aircraft, which are supposed to simulate particular autopilot types/models for a specific aircraft.

The generic one can be used for aircraft which don't have a custom autopilot implementation, and seems to work reasonably well on most aircraft using [[JSBSim]]. You can enable it with the "Autopilot Settings" which you can open using the F11-key or in the menu bar using the "Autopilot" item.

In real life, aircraft have specifically-programmed/customized autopilot system to cater for individual aircraft characteristics.
To a certain extent, Flightgear has the possibility to simulate this as well.

So it is possible to write a custom <tt>autopilot.xml</tt> to override the generic autopilot implementation.
This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both.
Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot/aircraft-specific features (for examples, see the b1900d or Citation Bravo in Git/HEAD). [[File:Custom-autopilot-dialog.png|thumb|300px|A custom autopilot dialog]]

Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots).
For example, the [[Piper PA34-200T Seneca II|Seneca II]] and the [[Piper PA-24 Comanche|Piper Comanche]] autopilots can be only used from the virtual cockpit using custom panel hotspots. This is in fact increasingly the case, as new emulations of autopilot systems are implemented using the built-in scripting language [[Nasal scripting language|Nasal]] which provides for much more flexible system design and functionality, compared to the relatively static way of describing autopilot systems and their relevant and modes using only the [[XML]]-configurable autopilot system. In fact, to properly emulate more complex autoflight systems that provide support for more abstract flight modes, using a combination of XML-configurable PID controllers and Nasal is likely to be the most promising approach.

In general, it can be considered to be more complex to provide proper cockpit panel implementations than wiring up the autopilot properties to the standard autopilot GUI dialog, so if an aircraft's autopilot doesn't seem to work properly using cockpit panel hotspots, you may want to try using the standard GUI dialog instead.

Also, please note that not all aircraft/autopilot combinations provide full support for all features offered by the standard autopilot dialog. This may be due to an aircraft's completion status, but also due to technical limitations in certain aircraft/autopilot, so that only certain modes are provided.
This may also apply to aircraft panels, that are seemingly offering functionality that may not yet be implemented.

In addition, JSBSim also features support for a standalone autopilot implementation, that works without any dependency to FlightGear/Nasal.

For further information about programing autopilots in FlightGear look at [[Autopilot Tuning Resources]] and http://www.flightgear.org/Docs/XMLAutopilot/.

== Autopilot Settings ==
The AP Settings dialog can be found at '''Autopilot > Autopilot Settings'''.

=== Heading control ===
* '''Wings Level''': enable this to keep your plane horizontal- usually used at Go-Arounds.
* '''Heading Bug:''' located on the compass rose of your instrument panel is a movable heading bug, the purple triangles that are pointing at your runways heading (283 for KSFO default). This bug is moved around the rose by setting the Heading Bug. The heading bug can be used several ways. When hand flying the aircraft turn the bug to your desired heading. This way you will have a constant visual reminder. If [[ATC|Air Traffic Control]] gives you a new heading move the heading bug to the new heading and you have your visual reminder.
* '''True Heading:''' your true heading as shown on the compass (of the [[Head-up display|HUD]]) and [[Multiplayer Howto|MP Map]].
* '''NAV1 CDI Course:''' used for VOR-by VOR flying like in old days and used with [[ILS]].

=== Velocity control ===
* '''Speed with Throttle:''' speed will be regulated to the selected speed by controlling throttle.
* '''Speed with Pitch:''' your plane will be pushed down or up to reach the selected speed. This can not be used during takeoff, landing or low altitude flights. Doing so could cause a crash.
=== Pitch/Altitude control ===
* '''Vertical Speed:''' set the speed of vertical climb. Usually used as "feet per minute"
* '''Pitch Hold:''' pitch degrees of your plane. Use a negative number to lower your nose.
* '''AoA Hold:''' The Ange of Attack describes the angle of the wings compared to the direction of the circumfluent air. The lift of the wing depends on the AoA. A too high AoA will cause the aircraft to stall.
* '''Altitude Hold:''' the desired altitude of your plane in feet (FL1=100 ft, FL25=2500 ft etc.).
* '''AGL Hold:''' The Altitude about Ground Level. Usually the altitude is given about sea level.
* '''NAV1 Glideslope:''' The vertical slope which led the aircraft from the interception point down to Runway level-used only with [[ILS]].

=== FlightDirector Mode ===
The flight director computes and displays the proper pitch and bank angles required in order for the aircraft to follow a selected path. A simple example: the aircraft is in level flight on a heading of 045 degree and at an altitude of 15000 feet maintaining a speed of 260 kts, the FD bars are thus centered. Then the flight director is set to a new heading of 090 degrees and a new altitude of 20000 feet. The aircraft must thus turn to the right and climb. This is done by rolling to the right and pulling up. The roll bar will deflect to the right and the pitch bar will deflect upwards. The pilot will then pull back on the control column while rolling the aircraft to the right. Once he reaches the proper pitch and bank angle the FD bars will again center and remain centered until it is time to roll back to wings level (when the heading starts to approach 090). When the aircraft approaches 20000 feet the pitch bar will deflect downwards thus commanding the pilot to reduce pitch in order to level off at the new altitude.

The FD is generally used in direct connection with the Autopilot. Where the FD commands the AP to put the aircraft in the attitude necessary to follow a trajectory. The FD/AP combination is typically used in autopilot coupled low instrument approaches, (below 200 feet agl) or CAT II and CAT III ILS instrument approaches.

The exact form of the flight director's display varies with the instrument type either crosshair or command bars.

== Route manager ==
The Route Manager in FlightGear is something like a very simple FMC- Flight Management Control/Computer.
In FGFS you can input a list of waypoints like NAVAIDS, Fixes and Airports, which the aircraft flies along. You can also add the altitude which the aircraft should have at a certain waypoint. So it is possible to let the aircraft fly along a certain route.

At the moment, it is not possible to add velocities or other constraints.

{{main article | Route Manager}}

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Howto:Multiplayer

2011-12-31T03:22:42Z

Reverse22:

With the '''multiplayer''' function of [[FlightGear]] you are able to see other pilots and vice-versa. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate]] drops during loading of aircraft models. Especially heavy models can cause severe lag. Therefore, it is suggested to fly in locations other than [[KSFO]], where there are fewer pilots flying around.

== Servers ==
'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you, has the lowest latency (ping time) or is the least busy.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Location
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracked]
! style="background:#efefef" |Maintainer
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Comments
|-
|mpserver01.flightgear.org
|Germany
|Yes
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Yes
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|UK
|Yes
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Yes
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|No
|Anders Gidenstam
|AndersG
|AndersG
|Offline from 2011-06-20 and until further notice.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Yes
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Yes
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, mostly short pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|Yes
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Yes
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Yes
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|No
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Yes
|Charles Ingels
|charles
|cbz-026
|
|}

Use [http://mpmap01.flightgear.org/mpstatus/ this], [http://mpmap02.flightgear.org/mpstatus/ this] or [http://flightgear.mxchange.org/mpstatus/ this] link to check if the MP servers are online. Locations of the servers are also available at [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps].

If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Map ===
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at [http://mpmap01.flightgear.org mpmap01] and/or [http://mpmap02.flightgear.org mpmap02]. You will also find this useful to check that you are successfully connecting to the server.

== Multiple connections per computer ==
It is possible to run multiple FlightGear instances on a single computer and connect them all to the multiplayer network. However, this requires some extras to keep in mind:
* both instances use the same out-port.
* one instance uses in port=5001, the other port 5002.
* and of course should both instances have unique callsigns.

== Using the Windows launcher / FGRun ==
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
# Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|FGRun]].
# On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft. Enter the callsign of your choice (check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether it is already in use or not. Do not pick a callsign that is already used!), enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes.
# Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). Once FlightGear has started, you will notice chat messages that say "Hello" indicating pilots that are online and then as they join (you can change this message by editing the <tt><chat type="string">Hello</chat></tt> line in <tt>[[$FG ROOT]]/preferences.xml</tt>). You may wish to use a different server (i.e. "Hostname" entry).

For more advanced settings, the <tt>Advanced > Network</tt> tab can be opened. You are able to remove the in or out lines only through this method for example.

== Using fgfs from the command line ==
First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,5000
--callsign=anything

where 5000 is the port number the server is listening on (which is 5000 for the official servers).

If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:

--multiplay=in,10,your.ip.address,portnumber

where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

''If you are using fgrun, please note that fgrun expects you to enter a valid (non-loopback, i.e. not 127.0.0.1) IP address or hostname for the local network interface.''

Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

=== Now, going more slowly for those who are completely lost... ===
Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

== Related content ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
[[de:Howto: Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

[[Category:Howto|Multiplayer]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Howto:Improve framerates

2011-12-31T03:22:24Z

Reverse22:

Anything below about 15 frames per second (fps) is close to unusable, or at least, will not be enjoyable. Additionally, the more the framerate decreases, the more other features of the simulation will suffer. The current [[FlightGear]] software architecture is such that long rendering times (slow framerates) may prevent other parts of the flight simulator, such as the autopilot, from having sufficient CPU time to respond correctly in the context of the simulation.

FlightGear's framerate is influenced by various factors, including:

* [[scenery]] complexity (terrain, clouds, trees, particles, random 3D objects, multiplayer/AI traffic, animated jetways)
* [[cockpit]] complexity (2D vs. 3D)
* environmental options (eg. visibility, precipitation)
* [[FDM]] update interval
* AI scenarios
* [[aircraft]] speed (scenery paging)
* rendering options
* debugging level

You can disable most features that often adversely affect framerate. Here is a collection of settings that you may change to improve your framerate. Please note that some of these will only take effect if they're specified at startup and cannot be changed after the simulation has started.

== Hints for users ==
=== Shaders ===
As of FlightGear 2.0.0, a growing number of [[shaders]] is being implemented into FlightGear. While these do make your flights visually appealing, they tend to have quite an impact on most computers. Luckily you can easily disable shaders in the <tt>View > Rendering Options</tt> dialog. As of FlightGear 2.6.0 an advanced shader options dialog is available, in which you can adjust every single shader's setting.

It requires some testing to find out what settings are best for your computer, but it's defenitely worth spending some time on!

=== Other windows/programs ===
Don't run FlightGear while also running another application, except if you need it. The two programs are competing for the CPU's proccessing power. As a basic rule, try to minimize the amount of programs open, so FlightGear can have the biggest portion of the CPU Times. Graphics-intensive programs also drain the GPU/graphics card, so you may be able to add a few frames.

=== AI traffic ===
[[Interactive Traffic|AI-traffic]] is computer controlled traffic, which includes traffic over the [[Howto: Multiplayer|MP network]]. By turning off this function you're not able to see other aircraft.

Most stuttering, or lag, in FlightGear is caused by AI traffic. Especially heavy models need quite some time to load, eg the [[Grumman F-14 Tomcat|F-14]] or the [[Rockwell B-1B Lancer|B-1B]]. Every time a new aircraft enters your local area, your computer has to load the model for that particular aircraft. The time required to read the data from the drive creates a stutter, or lag, which can range from a minor annoyance to a crash. The busier the place you fly, the more lag you'll get; eg flying around KSFO will generate more lag than a flight near EGLL, since there is more traffic near KSFO.

Turning off just the computer-generated aircraft (leaving the MP traffic visible), can be done by adding a command to your commandline:
--prop:/sim/traffic-manager/enabled=0
Or via [[FGRun]] through Advanced > Properties, add a new property with <tt>/sim/traffic-manager/enabled=0</tt>

=== Operating system specific ===
Many newer Linux distributions, like openSUSE 11.2, come with KDE4 as a desktop environment. While it allows some fancy desktop effects, it is known to consume enough computing power from the CPU and the graphics card to slow FlightGear down by 10 frames per second or even more. Choosing another window manager from the login screen, like xfce results in higher FlightGear performance. Setting "Compositing" to "off" in KDE4 might also help.

=== Debugging/log level ===
The more FlightGear has to write out to the log, the more framerates will be sacrificed. On normal usage, one is best of with the highest log level, which is ''alert''. In FGRun this can be set via <tt>Advanced > Debugging</tt>, on a commandline you'll use <tt>--log-level=alert</tt> (or simply remove an existing --log-level command, as alert is the default).

=== Optimus Technology ===
Most notebooks that run Windows 7 have the so called [http://www.nvidia.com/object/optimus_technology.html Optimus Technology] (NVidia) or Hybrid Graphics technology (ATI) onboard. This is meant to increase battery life, by automatically switching of the powerfull graphics card when it's not needed. However, FlightGear needs it all the time, even if Optimus says it doesn't! This miscommunication results in low framerates (because your computer will run Flightgear on the weak onboard processor).

To make use of the powerful graphics card, perform the following steps:
# Go to the NVidia control panel. Probably located in the Windows Control Panel.
# Open the 3D Settings tab. Now there's two options you can take:
#* On the "General settings tab", set "Prefered graphics processor" to NVidia. The NVidia card will now be used for all software. This can decrease battery life significantly.
#* On the "Programm settings" tab, locate <tt>fgfs.exe</tt> (eg. <tt>C:/Program Files/FlightGear/bin/win32/fgfs.exe</tt>) and assign the NVidia card to it. From now on the NVidia card will be used for FlightGear.

== Hints for developers ==
=== 3D models ===
Contrary to what many people believe, the impact of high vertex-count models on framerate is fairly minimal. In addition, for graphics hardware built after 2004 and intended for games (example: Nvidia GeForce 6 series), textures are close to, or completely, free. Today (in 2010), the major graphics bottleneck is between the CPU and the GPU. The goal in optimizing models is to store as much as possible on the GPU and reduce the number of rendering commands sent to the GPU. For graphic artists, the key things to remember are:

* Reduce the number of different textures used on a model to a minimum. It's better to use a few (or one!) big textures than many little ones.
* Avoid mixing textured and untextured geometry in the same model. Build the coloring into the texture map instead.
* Within your modeling tool, try work with large meshes instead of groups of small meshes - but please don't mistake this as a request for grouping multiple, distinct buildings into a single AC3D file. I know that this can result in a very unpleasant workflow; we are working on optimizations in FlightGear that will combine mesh parts automatically.
* Textures containing alpha cause various problems. In order to be rendered correctly, translucent geometry must be sorted by distance on the CPU. Furthermore, geometry is sorted on a course level (basically by mesh), so you may see various artifacts. If you have some transparent parts of a model, you should violate the first rule above and assign those parts to their own texture.
* Don't assign an RGBA texture to a model that is completely opaque!

== External links ==
[http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_15286 Optimizing file size, performance and streaming of 3D content]

[[Category:Howto|Improve framerates]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Howto:Carrier

2011-12-31T03:22:10Z

Reverse22:

Over the years, [[FlightGear]] has been equipped with a vast amount of [[aircraft carrier]]s that allow pilots to simulate the entire range of carrier operations, from catapult takeoffs, to "controlled crashes".

==Features==
[[File:Carrier3.jpg|thumb|300px|The Nimitz carrier in the San Fransisco bay]]

* Start FG with your chosen aircraft placed on the aircraft carrier "Nimitz" or "Eisenhower"
* Engage the launchbar in the steam catapult
* Have the carrier set course into the prevailing wind direction and attempt to get wind speed over the deck at a suitable value for launch
* Launch from the deck when ready
* Set the TACAN receiver in the aircraft to Nimitz's channel (029Y) and have the heading and range to the carrier displayed on the cockpit instruments
* Land on the deck and be halted by the arrestor cables
* Taxi onto the deck elevators, operate them and park on the hangar deck (0.9.10 and later)

== Start at a carrier ==
Note that several FlightGear aircraft are carrier capable, but the [[Hawker Seahawk|Seahawk]] is possibly the easiest to fly to begin with. You can start FlightGear with the command line or a GUI.

=== From commandline ===
To position your [[aircraft]] on the carrier at startup, use the following [[Command Line Parameters|command line options]] beside your normal options ([[$FG_ROOT|fg-root]] etc.). Note the upper-case "N" in Nimitz and the fact that the scenario comes in front of carrier! You can copy-paste this (the slash will make it look like one line):
--ai-scenario=nimitz_demo \
--carrier=Nimitz \
--aircraft=seahawk \

Please note the uppercase N in <tt>--carrier=Nimitz</tt>.

The following (optional) start positions are available:
--parkpos=cat-1
--parkpos=cat-2
--parkpos=cat-3
--parkpos=cat-4
--parkpos=park-1

=== Mac OS X launcher ===
If you are using the OSX launcher to run FlightGear, you should find a text entry box in the gui that allows you to specify command line options, add the above mentioned commands there.

=== Windows launcher ===
As of FlightGear 1.0.0 there comes a special box for the carriers on the airport selection page of the wizard. Type <tt>Nimitz</tt> in the carrier box and select <tt>nimitz_demo</tt> in the scenario list on the next page.

== Takeoff ==
[[File:Carrier1.jpg|thumb|300px|The [[Hawker Seahawk|Seahawk]] aircraft ready for takeoff]]
Once FlightGear has started, you should ensure that the parking brakes are off, ease the plane a little way down the catapult pressing L to engage the launchbar (hold for several seconds until given "Engaged" feedback; this might be best done from an external view initially.) You should notice the aircraft being pulled into alignment with the catapult and see the strops appear and hold down the aircraft. This will only happen if your aircraft is close enough to the correct spot on the catapult; as a rough guide, for the default parking position the seahawk's nose should be rougly level with the deck observation bubble.

To get the carrier into as good a position as possible for launch, select the <tt>AI > Carrier Controls</tt> menu, then check the "Turn to launch course" box.

You should now notice the carrier begin to pick up speed and turn into the wind, and naturally the deck may tilt somewhat as it turns. You should wait for this maneuver to finish and the deck to return to level before moving on to the next stage.
[[Image:Carrier6.jpg|thumb|300px|'''1:''' The takeoff part of the carrier with the catapults
'''2:''' The land part of the carrier with the wires]]
Being engaged to the catapult, you should spool up the engines to full power, ensure the brakes are off and that all flight controls are in a suitable position for launch. When ready, press C to release the catapult. Your aircraft will be hurled forward off the deck, and you should be able to raise the undercarriage and climb slowly away, being careful to avoid stalling.

== Locating the carrier ==
Actually finding the carrier in a vast expanse of open water can be very difficult, especially if visibility is poor. To assist with this task, the carriers are equipped with [[TACAN]], which allows a suitably-equipped aircraft (Seahawk at present) to obtain a range and bearing to the carrier.

First, you must set the appropriate TACAN channel, 029Y in this case, in the radios dialogue (Ctrl-R or choose <tt>Equipment > Radio Settings</tt> from the menu). You should, if within range, notice the [[DME]] instrument show your distance from the carrier, and the [[ADF]] instrument (next to the DME in the seahawk) should indicate a bearing to the carrier. Turn to the indicated heading and you should see the DME dial indicate you're closing in on the carrier.

{|
! Carrier || Scenario || TACAN
|-
| Nimitz || nimitz_demo || 029Y
|-
| Eisenhower || nimitz_demo || 030Y
|-
| Clemenceau || clemenceau_demo || 026Y
|-
| Foch || foch_demo || 026X
|-
| Akagi || akagi || N/A
|}

== Landing ==
This is the most difficult part of the operation, as in real life. You might well find Andy Ross' [[A-4F Skyhawk Operations Manual]] useful here.

Basically, though, you should use the TACAN to locate the carrier, and line up with the rear of the deck. As this part of the deck is at an angle to the course of the vessel, you may need to correct your alignment often. Ensure that the aircraft is in the correct configuration for approach (the <tt>Help > Aircraft Help</tt> menu should contain useful data for your aircraft) and that the gear and the arrestor hook are down.

[[File:Carrier5.jpg|thumb|300px|The Fresnel Lens Optical landing System]]
As you approach you should see, on the left hand side of the deck, a set of brightly coloured lights - called the Fresnel Lens Optical landing System (FLOLS). This indicates your position on the landing glideslope. You will see a horizontal row of green lights, and when approximately on the glideslope, an orange light ( known in some circles as 'the meatball') approximately in line with the green lights. When approaching correctly, the meatball appears in line with the green lights. If you are high it is above, and when low it is below. If you are very low the meatball turns red. If you fly to keep the meatball aligned you should catch number 3 wire.

=== Touchdown ===
Carrier landings are often described as "controlled crashes" and you shouldn't waste your time attempting to flare and place the aircraft gently on the deck like you would with a conventional landing - ensuring that you catch the wires is the main thing.

Immediately your wheels touch the deck, you should open the throttles to full power, in case you have missed the wires and need to go around again; the wires will hold the aircraft if you have caught them, even at full power.

If you wish, you can then (with 0.9.10 and later) raise the elevators from the carrier menu, taxi onto one of the elevators, lower it (uncheck the box on the menu and don't worry, they are VERY slow...) and taxi off into the hangar.

Don't be discouraged if you don't succeed at first with carrier landings - it's not an easy maneouver to master. If after a little practice you find the Seahawk too easy, you could move on to the Seafire for more of a challenge!

== Related content ==
* [[Carrier over MP]] to find out how you could control the carrier and/or use the carrier over the multiplayer network.

[[de:Flugzeugträger]]

[[Category:Howto|Carrier]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Help:Contents

2011-12-31T03:21:53Z

Reverse22:

* [[Help:Your first article]] read this first.
* [[Help:Tutorial]] how to formate your articles.
* [[Help:Template]] how to create, edit and use templates.
* [[Help:Translate]] translation can be done by everyone!

* [http://en.wikipedia.org/wiki/Help:Editing Help:Editing] editing help (Wikipedia)
* [http://meta.wikimedia.org/wiki/Help:Table#Pipe_syntax_tutorial Making Tables] (Wikimedia)

'''Wiki Help or requests : hellosimon at gmail com'''

[[Category:Help]]

[[de:Help:Inhalt]]
[[fr:Help:Aide]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Grumman A-6E

2011-12-31T03:21:43Z

Reverse22:

{{infobox Aircraft
|image =A-6E.jpg
|caption = The "Intruder"
|name =Grumman A-6E Intruder
|type =Attack aircraft
|authors =Alexis Bory
|fdm =YASim
|status =Beta
|fgname =A-6E
}}

The Grumman A-6 Intruder is available for FlightGear, and is capable of air-to-air refueling and landing on the carrier in that version. It features a high-quality 3D cockpit, avionics, and exterior model.

The FG model is modeled with [[Tactical Air Navigation]]

== About the aircraft ==
The '''A-6 Intruder''' is an American twin jet-engine, mid-wing attack aircraft built by Grumman Aerospace. In service between 1963 and 1997, the Intruder was designed as an all-weather replacement for the piston-engined A-1 Skyraider medium attack aircraft. A specialized electronic warfare derivative, the EA-6B Prowler, remains in service as of May 2008. As the A-6 was slated for retirement, its precision strike mission was taken over by the now retired F-14 Tomcat equipped with LANTIRN, which has subsequently passed on the role to the F/A-18E/F Super Hornet.

An A-6E Intruder is on display at the [[National Air and Space Museum]].

== Aircraft help ==
{| class="prettytable"
!Key
!Function
|-
|c
|Canopy open/close command
|-
|C
|Catapult launch command
|-
|k/j
|Air Brakes open/close
|-
|L
|Carrier Launch-bar engage
|-
|o/O
|Hook up/down
|-
|f/F
|Wing Fold up/down
|}

== Operating Instructions ==

=== Landing ===

==== Carrier Landing pattern ====
[[File:A-6E-carrier-landing-pattern-ng.png]]

== Development status/Issues/Todo ==
'''Outside:'''
* Fix the relatively massive "hiccup" in elevator

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

== External links ==
* [http://en.wikipedia.org/wiki/A-6_Intruder Wikipedia's article on the A-6 Intruder]
* [http://croo.murgl.org/fgfs/A-6E/A-6E-A-6E-20071101.tgz Download the development version of the A-6E (11/01/2007)]
* [http://www.youtube.com/watch?v=EKELqBGVsqw A-6 flight - Dynamic water effect in FlightGear] ([http://www.youtube.com/watch?v=EKELqBGVsqw&hd=1 720p]) - August 18, 2009

{{Grumman}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Hardware recommendations

2011-12-31T03:21:23Z

Reverse22:

{{out of date}}

These '''hardware recommendations''' are based on informal user experience, be sure to consult other sources before making serious decisions regarding computer hardware.

You may also want to check out the following article on building your own FlightGear box based on decommissioned and refurbished server: [[Howto: Build a cheap FlightGear box]].

== Recommended Hardware for FlightGear 1.9.x ==
* A 3D video card, with support for [[OpenGL]] 1.2 or better (OpenGL 2.0 is preferred) and at least 128-256 MB video RAM. Flightgear requires a hardware accelerated 3D video card with OpenGL drivers to run at reasonable frame-rates. Most modern PCs have hardware accelerated 3D cards. If your FlightGear video is not running smoothly, see [[Configuring OpenGL]]. See [[Supported Video Cards]]) for a list of video cards known to work with FlightGear. Note that cards with working shader support will enable FlightGear to run with more visual effects.
* At least 512-1024 MB '''free''' RAM (and more is better). FlightGear uses more than 500 MB of RAM by default. If less free RAM is available, FlightGear would be slowed down significantly due to OS swapping
* A 1-2 GHZ CPU (multi-core processors have benefits for some FlightGear components such as the tile loader)
* 500 MB HD space for a minimum installation, 3 GB if you want to compile it yourself, plus up to 8 GB for optional world-wide scenery
* A 3 button mouse or 2 button mouse with scroll wheel
* An optional sound card, Soundblaster compatible, preferably with EAX support
* An optional [[joystick]]/yoke and/or pedals - Gameport or USB (HID compatible), see [[Supported Peripherals]] for a list of input hardware known to work with FlightGear.

== Notebooks ==
If you are interested in running FlightGear on a notebook, you may also want to check out [[Notebooks known to run FlightGear]].

== Incompatible Hardware ==
A list of video cards that may not properly run FlightGear can be found at [[Problematic Video Cards]].

== Related content ==
* [[Supported Video Cards]]
* [[Supported Peripherals]]
* [[3D Video Introduction]]
* [[Configuring OpenGL]]
* [[Troubleshooting Problems]]

[[pl:Wymagania systemowe‎]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Custom France scenery

2011-12-31T03:21:10Z

Reverse22:

Custom scenery is available for continental France. It was developed using a variety of free data sources.
[[File:Alps-custom-france-scenery.jpg|thumb|500px|Flying over the Alps using the custom France scenery.]]

== Distribution ==

'''The first release of this custom scenery covering all of continental France is available from [http://www.mguillaud.net/fg/custom-scenery-france-v1.tgz] (warning: 781 MB file).'''

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:
* landcover information from the CORINE program (Source : European Union, SOeS, CORINE Land Cover, 2006 - [http://www.ifen.fr/index.php?id=88]). See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures,
* landmass updated according to CORINE data,
* digital elevation data from Jonathan de Ferranti for the alpine area [http://www.viewfinderpanoramas.org/dem3.html],
* fitting of the elevation data with 20m accuracy ("terrafit.py -e 20"),
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].

Please see the forums [http://www.flightgear.org/forums/viewtopic.php?f=5&t=5631&sid=4d3e3507c3ef5fe2d2dbb7bd138ef8ea] for feedback and information about work in progress.

== Suggested flights ==

* Take-off from Grenoble le Versoud (LFLG). Head south following the general direction of the Alps. Bearing left (East) will take you into high alpine territory, while towards the West lie the plains of the Rhône valley. Once you reach the Mediterranean coast, follow it to land in Marseilles (LFML), Nice (LFMN), or another smaller airport serving the French Riviera.

[[fr:Décor personnalisé de la France]]

[[Category:Scenery]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Control surfaces

2011-12-31T03:20:57Z

Reverse22:

Aircraft flight control surfaces allow a pilot to adjust and control the aircraft's flight attitude.

Development of an effective set of flight controls was a critical advance in the development of the aircraft. Early efforts at fixed-wing aircraft design succeeded in generating sufficient lift to get the aircraft off the ground, but once aloft, the aircraft proved uncontrollable, often with disastrous results. The development of effective flight controls is what allowed stable flight.
== Ailerons ==
[[File:Ailerons.jpg|thumb|300px|Ailerons (red) on the wings of a [[Cessna C172]]]]'''Ailerons''' are hinged control surfaces attached to the trailing edge of the wing of a fixed-wing aircraft. The ailerons are used to control the aircraft in roll. The two ailerons are typically interconnected so that one goes down when the other goes up: the downgoing aileron increases the lift on its wing while the upgoing aileron reduces the lift on the other wing, producing a rolling moment about the aircraft's longitudinal axis. The word aileron is French for "little wing."
== Wingtip Devices ==
[[File:Wingtip_device.jpg|thumb|300px|A wingtip device (red) on the wing of a [[Boeing 747]]]]'''Wingtip device'''s, sometimes know as winglets, are usually intended to improve the efficiency of fixed-wing [[aircraft]]. There are several types of devices, and though they function in different manners, the intended aerodynamic effect is to modify the aircraft's wake in some beneficial manner. Wingtip devices can also improve aircraft handling characteristics. From a marketing standpoint, they are also valued for their aesthetic appeal, and aircraft have been equipped with them for cosmetic reasons as well.
== Elevators ==
[[File:Elevator.jpg|thumb|300px|Elevators on the tail of a [[Boeing 777-200]]]]'''Elevator'''s are control surfaces, usually at the rear of an aircraft, which control the aircraft's orientation by changing the pitch of the aircraft, and so also the angle of attack of the wing. An increased wing angle of attack will cause a greater lift to be produced by the profile of the wing, and a slowing of the aircraft. A decreased angle of attack will produce an increase in speed (a dive). The elevators may be the only pitch control surface present (and are then called a stabilator), or may be hinged to a fixed or adjustable surface called a stabilizer.
== Flaps ==
[[File:Flaps.jpg|thumb|300px|Flaps (red) on the wings of a [[Cessna C172]]]]'''Flaps''' are hinged surfaces on the trailing edge of the wings of a fixed-wing aircraft. As flaps are extended the stalling speed of the aircraft is reduced. Flaps are also used on the leading edge of the wings of some high-speed jet aircraft, where they may be called slats.

Flaps reduce the stalling speed by increasing the camber of the wing and thereby increasing the maximum lift coefficient. Some trailing edge flaps also increase the area of the wing and, for any given aircraft weight, this reduces the stalling speed. The Fowler flap is an example of one which increases the area of the wing.
== Rudder ==
[[File:Rudder.jpg|thumb|300px|Rudder (red) on the tail of a [[Cessna C172]]]]On an aircraft, the '''rudder''' is called a "control surface" along with the rudder-like elevator (attached to horizontal tail structure) and [[aileron]]s (attached to the wings) that control [[pitch]] and [[roll]]. The rudder is usually attached to the fin (or vertical stabilizer) which allows the pilot to control yaw in the vertical axis, i.e. change the horizontal direction in which the nose is pointing. The rudder's direction is manipulated with the movement of foot pedals by the pilot.

[[Category:Aircraft controls]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Category:Airports

2011-12-31T03:20:35Z

Reverse22:

This page lists all airports for which a [[FlightGear]] wiki page exists, regardless of whether buildings have been placed at these airports in FlightGear or not. For airports with buildings in FlightGear, '''see the list of [[Developed Airports]]'''.

[[Category:Places]]
[[Category:Scenery]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Category:Airbus

2011-12-31T03:20:25Z

Reverse22:

'''Airbus SAS''' is an [[:Category:Aircraft manufacturer|aircraft manufacturing]] subsidiary of EADS, a European aerospace company. Based in Toulouse, France, and with significant activity across Europe, the company produces around half of the world's jet airliners.

Airbus began as a consortium of aerospace manufacturers. Consolidation of European defence and aerospace companies around the turn of the century allowed the establishment of a simplified joint stock company in 2001, owned by EADS (80%) and BAE Systems (20%). After a protracted sales process BAE sold its shareholding to EADS on 13 October 2006.

Airbus employs around 57,000 people at sixteen sites in four European Union countries: Germany, France, the United Kingdom, and Spain. Final assembly production is at Toulouse (France), Hamburg (Germany), Seville (Spain) and, since 1999, Tianjin (China). Airbus has subsidiaries in the United States, Japan and China.

The company is known for producing and marketing the first commercially viable fly by wire [[:Category:Airliners|airliner]].

[[Category:Aircraft manufacturer]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 777

2011-12-31T03:20:14Z

Reverse22:

[[File:777-200.jpg|thumb|270px|[[Boeing 777-200]] in British Airways livery]]
[[File:COA777.jpg|thumb|270px|[[Boeing 777-200]] in Continental livery]]

The '''Boeing 777''' is a long-range, wide-body twin-engine airliner built by Boeing Commercial Airplanes. The world's largest twinjet and commonly referred to as the "Triple Seven", it can carry between 283 and 368 passengers in a three-class configuration and has a range from 5,235 to 9,450 [[nautical mile]]s (9,695 to 17,500 km). Distinguishing features of the 777 include the six wheels on each main landing gear, its circular fuselage cross section, the largest diameter turbofan engines of any aircraft, the pronounced "neck" aft of the flight deck, and the blade-like tail cone.

As of May 2008, 56 customers have placed orders for 1,080 777s. Direct market competitors to the 777 are the [[Airbus A330-300]], [[Airbus A340|A340]], and some variants of the [[Airbus A350|A350 XWB]], which is currently under development. The 777 may eventually be replaced by a new product family, the [[Boeing Y3]], which would draw upon technologies from the [[Boeing 787|787]].

You can see a guide on how to fly this plane on [[User:Vaeronic|Vaeron's wikipage]]. For version 2.0, see [[Boeing 777 Tutorial: Version 2.0.|ChocBoy's tutorial]]

== Variants ==
* [[Boeing 777-200]]
* [[Boeing 777-300]]

== External links ==
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ]

{{Boeing}}

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 747

2011-12-31T03:20:01Z

Reverse22:

[[File:747-400.jpg|thumb|270px|A [[Boeing 747-400]] in KLM livery.]]
[[File:747.jpg|thumb|270px|A [[Boeing 747-100]] in PIA livery.]]
The '''Boeing 747''', sometimes nicknamed the "'''Jumbo Jet'''", is among the world's most recognizable aircraft, and was the first wide-body commercial airliner ever produced. Manufactured by Boeing's Commercial Airplane unit in the United States, the original version of the 747 was two and a half times the size of the [[Boeing 707]], one of the common large commercial aircraft of the 1960s. The aircraft's wingspan is actually longer than the length of the Wright Brothers' first flight. First flown commercially in 1970, it held the passenger capacity record for 37 years, until it was surpassed by the [[Airbus A380]].

The four-engine 747 uses a double deck configuration for part of its length. It is available in passenger, freighter and other versions. The 747's hump created by the upper deck allows for a front cargo door on freighter versions, and serves as additional seating in most versions. The [[Boeing 747-400|747-400]], the latest version in service, is among the fastest airliners in service with a high-subsonic cruise speed of Mach 0.85 (567 mph or 913 km/h). It has an intercontinental range of 7,260 [[nautical mile]]s (8,350 mi or 13,450 km). The 747-400 passenger version can accommodate 416 passengers in a typical three-class layout or 524 passengers in a typical two-class layout.

The 747 was expected to become obsolete after 400 were sold because of the development of supersonic airliners, but it has outlived many of its critics' expectations, and production passed the 1,000 mark in 1993. As of March 2008, 1,400 aircraft had been built, with 122 more in various configurations on order. The latest version of the aircraft, the 747-8, is scheduled to enter service in 2009.

== Variants ==
* [[Boeing 747-100]]
* [[Boeing 747-200]]
* [[Boeing 747-400]]
* [[Boeing 747-8i]]

== External links ==
* [http://www.boeing.com/commercial/747family/index.html Boeing 747 product page]

{{Boeing}}

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Boeing 707

2011-12-31T03:19:39Z

Reverse22:

[[File:707.jpg|thumb|270px|The -338 variant]]
[[File:707-400.png|thumb|270px|707-400 RR Conway turbofan]]
The '''Boeing 707''' is a four-engine commercial passenger jet [[:Category:Airliners|airliner]] developed by [[:Category:Boeing|Boeing]] in the early 1950s. Its name is most commonly spoken as "Seven Oh Seven". Boeing delivered a total of 1010 Boeing 707s, which dominated passenger air transport in the 1960s and remained common through the 1970s. Boeing also offered a smaller, faster version of the [[aircraft]] that was marketed as the Boeing 720.

Although it was not the first commercial jet in service, the 707 was among the first to be commercially successful, and is generally credited as ushering in the Jet Age. It established Boeing as one of the largest makers of passenger aircraft, and led to the later series of aircraft with "7x7" designations.

== Variants ==
Currently there are two variants available in [[FlightGear]]:
* [[Boeing 707-338]]
* [[Boeing 707-400]]

== Reference ==
* [http://en.wikipedia.org/wiki/Boeing_707 Wikipedia]

{{Boeing}}
[[Pt:Boeing 707]]

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Bluebird

2011-12-31T03:19:25Z

Reverse22:

{{infobox Aircraft
|image = bluebird6-splash2-640.jpg
|name = Bluebird
|type = UFO
|fdm =
|status-fdm = 0
|status-systems = 3
|status-cockpit = 4
|status-model = 4
|authors = Stewart Andreason
|fgname = bluebird, bluebird-09, bluebird-osg
|download = http://www.flightgear.org/Downloads/aircraft-2.4.0/#bluebird
}}
The '''Bluebird''' is a futuristic hovercraft for [[FlightGear]]. Some of it's features:
* Stable hover platform
* Walk around inside and outside
* Jump out the rear hatch like a skydiver
* Digital cockpit: GPS, english and metric
* Inside variable lighting

== External links ==
Newest version is always at:
* [http://seahorseCorral.org/flightgear_aircraft.html "Stewart's SEA-horse Aircraft Hanger"]

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

ATC-aircraft

2011-12-31T03:19:11Z

Reverse22:

{{ATC-navbar}}
{{infobox Aircraft
|image =ATC-aircraft.jpg
|alt =Tower view with ATC1
|name =ATC-aircraft
|type =Air traffic control
|authors =Syd Adams, Csaba Halasz
|status =Under development
|fgname =ATC, ATC2
|download =http://flightgear.org/Downloads/aircraft-2.0.0/#ATC
}}
The '''ATC-"aircraft"''' is the [[FlightGear]] interface for the [[Air traffic control|Air Traffic Control]]. This means that any player can log on as ATC and control the traffic for any airport of their choice. Only users with FlightGear version 1.9 or higher are able to control the airspace.

Currently two version of ATC-aircraft are available.

== Aircraft help ==
{| class="prettytable"
!Key
!Function
|-
|Ctrl-F
|Font selector
|-
|P
|Toggle radarscreen
|-
|Ctrl-T
|Toggle visual target tracking
|}

* To move to a new airport, use the <tt>Location > Tower Position</tt> [[menubar|menu]].
* To adjust view position, modify <tt>/sim/tower</tt> properties in the [[property browser]].

== Todo/Bugs ==
* The radar screen is oversized on some screen sizes. It should be automatically resized for any window size.
* The screen showing the ATC view is very small when viewed with radar. The radar screen should be resized by the user if possible.
* There are some bugs when using normal [[Howto: Multiplayer#Multiplayer Chat|MP Chat]]. You can't then use it again (FG has to be restarted to fix the bug) and you have to use the ATC Chat box at the bottom.
*Please add how to shift targets on the Radar screen in ATC2 so as to move from target 0 to 1, etc in a multi-aircraft environment.

== See also ==
* [[Howto: Be a controller]]
* [[ATC Tutorial]]

[[Category:Aircraft]]
[[Category:Air Traffic Control]]

[[de:ATC-Instanz]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Altitude

2011-12-31T03:19:00Z

Reverse22:

In aviation the height the aircraft is flying in is called the altitude. It is expressed in feet. The international foot is defined as exactly 0.3048 metres. In aircrafts the altitude is measured with the [[altimeter]]. The basis of the altimeter is the same as a aneroid barometer, an airtight drum that will change shape depending on the pressure of the surrounding air. The higher the aircraft the larger the drum. The altimeter is very sensitive and the air pressure caused by the weather has great influence on it.

In contrast to [[altimeter|altimeters]], ground radar is perfect for measuring directly the altitude above the ground without being influenced by the weather. It is used for ground warning systems.

In communication with [[ATC]] two types of altitude are being used:
#lower airspace: [[#True altitude|true altitude]] (normally just called altitude)
#upper airspace: [[#Flight level|flight level]] (FL)

==Indicated altitude==
*The [[altimeter]] reading.
The altimeter can be set to '''three''' possible references
#to [[#QNH|QNH]], resulting in the indicated altitude "matching" the [[#True altitude|true altitude]] (see below).
#to the Standard pressure (29.92" Hg or 1013.25 hPa) making the altimeter show the [[#Pressure altitude|pressure altitude]]. This configuration should only be used in high altitudes.
#to the [[#Height|height]] above the airfield. While on the runway the indicated altitude would read zero. Near the airfield the indicated altitude would be the [[#Absolute altitude|absolute altitude]] ([[above ground level]]).

What you have to use depends on the local [[flight rules]].

===QNH===
[http://en.wikipedia.org/wiki/QNH QNH] is a brevity code for "atmospheric pressure at sea-level". It is needed when starting or landing an aircraft, when it is important to have the [[#Indicated altitude|indicated altitude]] as accurate as possible.

The code QNH is used in:
*the pilots request for the "atmospheric pressure at sea-level". In their reply [[ATC]] will repeat QNH followed with the pressure.
*automatic weather reports via [[ATIS]].

If there is neither [[ATIS]] nor [[ATC]] available you can find the QNH value in Environment=>Global Weather.

If QNH is not available but the [[#Elevation|elevation]] of the departing airfield is known, set the [[altimeter]] to it instead. The resulting QNH is the correct one. It is also possible to use QNH from a nearby airfield.

To use a barometer (i.e. your [[altimeter]]) as a tool to measure the altitude, it must be corrected for weather influences. For this task, every airfield is equipped with an accurate barometer. By combining this value with the [[#True altitude|true altitude]] of the airfield, they can calculate the barometric pressure at [[Mean Sea Level]], the QNH. It will transmit the QNH via [[ATC]] and [[ATIS]] and with that piece of information the altimeter in the aircraft can be corrected for weather influences and will display an altitude close to the [[#True altitude|true altitude]] of the aircraft. This way the [[#Indicated altitude|indicated altitude]] will be quite accurate for a ''certain area around the airfield'' as long as the ''weather remains stable''. While on the airfield the altimeter would show the altitude of the airfield.

It is vital to set the altimeter to QNH when using a height map, so that the [[#Indicated altitude|indicated altitude]] can be compared to the [[#Elevation|elevations]] on the map, which is of special importance during the approach to an airfield. There have been dramatic accidents where pilots were flying using [[#Pressure altitude|pressure altitude]] during descend instead of the [[#True altitude|true altitude]], making the height map of the area almost useless. In bad visibility mountains have not been noticed and the ground was higher as expected.

==Pressure altitude==
*Pressure altitude is the '''barometric pressure expressed in feet''' (this means your expensive piece of equipment has been reduced to a barometer).
*The altimeter shows pressure altitude, if it is set to the '''standard pressure''': 29.92" Hg = 1013.25 hPa.

This has the big advantage, that ''all aircrafts are using the same altimeter settings'', so the ''same [[#Indicated altitude|indicated altitude]]'' in ''different planes'' in the ''same area'' is the ''same [[#True altitude|true altitude]]''.

The problem with pressure altitude is that changing weather makes the air pressure vary. So you never know exactly which [[#True altitude|true altitude]] you are flying on. This makes pressure altitude very dangerous to use at low altitudes!

As all planes in the same area experience the same effect they will still fly at the same altitude relative to each other.

===Flight level===
*[[#Pressure altitude|Pressure altitude]] divided by 100 is referred to as the flight level.
It is used above the transition altitude (18,000 feet (5,500 m) in the US, but may be as low as 3,000 feet (910 m) in other jurisdictions if they do not have higher mountains). When the [[altimeter]] reads 18,000 ft on the standard pressure setting the aircraft is said to be at "Flight level 180" or FL180.

To assure vertical separation [[IFR]] pilots are required to use the altimeter. It is not allowed to use the height measured by GPS systems.

==Density altitude==
*Altitude in terms of the density of the air.

This is the only kind of altitude, that is not used for determining the position of the aircraft. Instead it is an important factor for the power your aircraft/helicopter is able to develop in the current situation.

High temperatures cause the air to be less dense. Low air density causes less drag (friction), less lift, less engine performance (the rotorblades have less effect and the engine receives less oxygen). But less friction also enables you to fly faster and more efficient, as less energy is lost for the friction.

Low temperatures cause the air te be more dense. So you have more drag, lift and engine performance (rotorblades have more effect, engine recieves more oxygen) for the price of being slower and burning more fuel as more energy is needed to overpower the friction.

In FlightGear the density of the air is simulated by making a helicopter stick to the ground on a warm day or by making it impossible for the heavy loaded Antonov to depart from Mexico City. The density altitude is calculated from the barometric pressure and the temperature. The higher the temperature, the lower the density, the higher the density altitude (in reference with the [[#True altitude|true altitude]]). ([http://en.wikipedia.org/wiki/Density_altitude wikipedia])

==General Definitions==
===Height===
The height of something is the '''vertical distance to a certain point'''.

===True altitude===
The true altitude is the '''[[#Height|height]] above the mean sea level''' ([[AMSL]]).

After setting the [[altimeter]] to [[#QNH|QNH]] the [[#Indicated altitude|indicated altitude]] is close to the true altitude.

===Absolute altitude===
The absolute altitude is the [[#Height|height]] '''relative to the ground directly below''' ([[AGL]]: above ground level).

Ground radar and ground warning systems display the absolute altitude. If the [[altimeter]] is set to display zero while being on the airfield, the [[#Indicated altitude|indicated altitude]] will be the absolute altitude as long as the [[#Elevation|elevation]] of the terrain below does not change.

In FlightGear there is a "system" altitude, that altitude is [[AMSL]]. Some will refer to this altitude as [[#Absolute altitude|absolute altitude]], which is theoretically incorrect.

===Elevation===
The [[#True altitude|true altitude]] of positions on the ground is referred to as the elevation. In aviation these positions normally are runways or mountain peaks.

It is vital to know the elevation of a runway before descending towards it. The best sources for elevation data are:
*[[Atlas]] provides an accurate height map. One needs to interpret the colours on the map to know the elevation. For [[IFR]] and flight planning Atlas is not suited.
*[[MPMap]] is an on-line tool for FlightGear that provides accurate information about runways including the elevation.
*[[Airport Diagram Generator]] will create a PDF file, an accurate map of the airfield. It includes the elevation.
*Websites that are used for real flight planning. A few problems, the Real runway is not always 100% the same as the FlightGear runway, not all FlightGear runways can be found on those websites (The FlightGear database is more complete).
It is very unfortunate that [[Kelpie]] doesn't provide this information.

==Additional information==

*QFE: Atmospheric pressure at the airport, can be used to show [[#Absolute altitude]].
*QNE: Elevation of the airfield above [[AMSL]].
*QFF: Atmospheric pressure calculated towards [[AMSL]] under Standard conditions, this code is not used.
*ISA-1: International Standard Atmosphere: Atmospheric model of various layers of the earth atmosphere. Each layer has a temperature, pressure, viscosity and density. It is based on an average model of the earth atmosphere. Publication ISO 2533:1975. There is a US model that is synchronised with this standard but is reaching higher.
*ISA-2: ICAO Standard Atmosphere: Same as ISA-1 but reaching higher and with slightly different values. In aviation this is the standard to use. Publication Doc 7488-CD.
*Attitude: Most often the Pitch of an aircraft, the angle of the nose in reference to the ground, but there are other definitions.
*Ascend = climb = go higher.
*Descend: go lower.

==External links==
*http://en.wikipedia.org/wiki/Altitude
*http://en.wikipedia.org/wiki/Pressure_altitude
*http://en.wikipedia.org/wiki/Flight_level
*http://en.wikipedia.org/wiki/QNH
*http://www.altitude.nu/

{{Understanding}}

[[Category:Aviation]]
[[de:Flughöhe]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Aircraft carrier

2011-12-31T03:18:41Z

Reverse22:

[[File:Carrier3.jpg|thumb|300px|The Nimitz carrier in the San Fransisco bay]]
An '''aircraft carrier''' is a warship designed with a primary mission of deploying and recovering [[aircraft]], acting as a seagoing airbase. Aircraft carriers thus allow a naval force to project air power great distances without having to depend on local bases for staging aircraft operations. Most modern day aircraft carriers are nuclear powered, and thus not dependent upon fuel. Modern carriers can operate for as much as 20 years without having to refuel.

== Carriers in FlightGear ==
FlightGear currently includes four modern aircraft carriers:

* USS Dwight D. Eisenhower
* USS Nimitz
* USS Carl Vinson and the Vinson Battle Group
* Clemenceau

== Related content ==
* [[Howto: Carrier]] teaches how to land on and takeoff from a carrier.
* [[Carrier over MP]] for carrier control over a multiplay network.
[[es:Portaaviones]]
[[nl:Vliegdekschip]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]

Airbus A320 family

2011-12-31T03:16:45Z

Reverse22:

''This includes the following models: A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231, A320-family''

{{infobox Aircraft
|image =A320-family.jpg
|name =Airbus A320 Family
|type =Narrow-body Commercial Airliner(s)
|livery =Nearly every livery in [http://liveries.flightgear.org/aircraft.php?id=8 the database]
|fdm =JSBSim
|status =Alpha
|authors =Ampere K. Hardraade, Skyop
|fgname =A318-111, A319-111, A319-131, A320-111, A320-211, A320-231, A321-211, A321-231
|download =http://flightgear.org/forums/viewtopic.php?t=9032&p=115034#p115034
|development =http://gitorious.org/airbus-aircraft/a320
}}
[[File:A320-cockpit.jpg|thumb|300px|The 3d [[cockpit]] of the A320 family, currently under development]]

The '''Airbus A320 Family''' is a series of narrow-body commercial passenger jets manufactured by [[Airbus|Airbus Industries]]. Designed for short to medium hauls, the aircraft pioneer fly-by-wire technology and regularly compete with the [[Boeing 737|Boeing 737 series]]. The series includes the Airbus A318, the A319, the A320, and the A321. The [[Airbus A320E|"A320 Enhanced" program]] aims to further improve the A320 family with longer range and better fuel economy.

== Variants ==
* <tt>A318-111</tt>: Airbus A318-111 with CFM56 engines
* <tt>A319-111</tt>: Airbus A319-111 with CFM56 engines
* <tt>A319-131</tt>: Airbus A319-131 with IAE V2500 engines
* <tt>A320-111</tt>: Airbus A320-111 with CFM56 engines
* <tt>A320-211</tt>: Airbus A320-211 with CFM56 engines
* <tt>A230-231</tt>: Airbus A320-231 with IAE V2500 engines
* <tt>A321-211</tt>: Airbus A321-211 with CFM56 engines
* <tt>A321-231</tt>: Airbus A321-231 with IAE V2500 engines

== Startup procedures ==
''This applies to all the A320 models''<br />

1. Start the APU. APU starter ON and APU master switch ON.<br />
2. APU electric generator ON.<br />
3. Engine start knob START.<br />
4. (Wait a couple seconds...) Engine cutoff switches RUN.<br />
5. Engine 1 and engine 2 electric generators ON. APU electric generator OFF.<br />
6. APU starter and master switch off. Engine start knob OFF.

== Development status ==

=== Completed ===
* Base model(s)
* Animations
* Instruments
* 3d [[cockpit]]
* Autobrake/speedbrake systems '''[Git-only]'''
* Autopilot system '''[Git-only]'''
* [[Livery over MP|Livery select]]
* [[Howto: Implement generic tyre smoke|Tire smoke]]
* [[Howto: Add contrails|Contrails]]
* [[Howto: Implement pushback|Pushback]]
* Engine fire system
* [[Howto: Animated jetways|Animated jetway]] definitions

=== To-do ===
* Fly-by-wire system
* Animate slats

== Related content ==
* [[Aircraft]]
* [[Aircraft Todo]]
* [[Airbus A319]] (in development separately)
* [[Airbus A321]] (in development separately)

= External links =
* [http://www.flightgear.org/forums/viewtopic.php?t=9032 Development thread]
* [http://gitorious.org/airbus-aircraft/a320 A320-family at Gitorious]
* [http://gitorious.org/airbus-aircraft/a320/archive-tarball/master Download the latest version of A320-family]
* [http://www.airbus.com/en/aircraftfamilies/a320/ Airbus A320 Family official homepage]

{{Airbus}}

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

[http://www.prlog.org/11289974-phone-number-lookup-verizon-phone-number-reverse-lookup-to-get-information-you-need-quickly.html phone number lookup]

[http://thetvtopc.com/Reverse_Cell_Phone_Lookup_Number reverse cell phone lookup]