FlightGear wiki - User contributions [en]

Autopilot

2011-12-31T05:38:09Z

Gorilla: Undo revision 38603 by Reverse22 (talk) Link Spam

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

Blender

2011-12-31T05:36:54Z

Gorilla: Undo revision 38604 by Reverse22 (talk) Link spam!

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

Boeing 717

2011-12-31T05:36:43Z

Gorilla: Undo revision 38605 by Reverse22 (talk) Link Spam!

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

Boeing 727-230

2011-12-31T05:36:30Z

Gorilla: Undo revision 38606 by Reverse22 (talk) Link spam!

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

Boeing 737-100

2011-12-31T05:36:14Z

Gorilla: Undo revision 38607 by Reverse22 (talk) Link Spam!

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

Boeing 737-300

2011-12-31T05:36:03Z

Gorilla: Undo revision 38608 by Reverse22 (talk) Link Spam!

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

Boeing 737NG

2011-12-31T05:35:40Z

Gorilla: Undo revision 38609 by Reverse22 (talk) Link Spam!

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

New to FlightGear

2011-12-31T05:33:51Z

Gorilla: Undo revision 38615 by Reverse22 (talk) Link Spam

''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新手]]

Long Term Goals

2011-12-31T05:33:00Z

Gorilla: Undo revision 38614 by Reverse22 (talk) Link Spam!

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

FGFSPM

2011-12-31T05:31:59Z

Gorilla: Undo revision 38611 by Reverse22 (talk) Link spam!

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

Piper J3 Cub

2011-12-31T05:30:46Z

Gorilla: Undo revision 38616 by Reverse22 (talk) Link spam!

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

Pt/Aeronaves

2011-12-31T05:30:01Z

Gorilla: Undo revision 38618 by Reverse22 (talk) Link Spam!

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

Pt/Boeing 707-400

2011-12-31T05:28:04Z

Gorilla: Undo revision 38619 by Reverse22 (talk) Link Spam!

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

Pt/FlightGear

2011-12-31T05:27:47Z

Gorilla: Undo revision 38620 by Reverse22 (talk) Link Spam!

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

Pt/Página principal

2011-12-31T05:27:36Z

Gorilla: Undo revision 38621 by Reverse22 (talk) Link spam!

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

Pt/Portal:Desenvolvedor/Avião

2011-12-31T05:27:19Z

Gorilla: Undo revision 38622 by Reverse22 (talk) Link Spam!

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

Schleicher ASK 21

2011-12-31T05:27:06Z

Gorilla: Undo revision 38623 by Reverse22 (talk) Link Spam!

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

SketchUp to AC3D exporter

2011-12-31T05:23:46Z

Gorilla: Undo revision 38624 by Reverse22 (talk) Link Spam!

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

Suggested Prerecorded Flights

2011-12-31T05:22:00Z

Gorilla: Undo revision 38625 by Reverse22 (talk) Link Spam!

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

Zeppelin NT

2011-12-31T05:21:47Z

Gorilla: Undo revision 38626 by Reverse22 (talk) Link Spam!

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

FlightProSim

2011-12-31T05:20:59Z

Gorilla: Undo revision 38627 by Reverse22 (talk) Link Spam!

{{FlightGearVendors}}

[[Category:FlightGear vendors]]

Soaring

2011-12-31T05:20:32Z

Gorilla: Undo revision 38628 by Reverse22 (talk) Link Spam!

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

Lelystad Airport

2011-12-31T05:20:11Z

Gorilla: Undo revision 38629 by Reverse22 (talk) Link Spam

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

MBB Bo 105

2011-12-31T05:19:58Z

Gorilla: Undo revision 38630 by Reverse22 (talk) Link Spam

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

Messerschmitt Bf 109

2011-12-31T05:18:36Z

Gorilla: Undo revision 38631 by Reverse22 (talk) Link Spam!

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

Mikoyan-Gurevich MiG-15

2011-12-31T05:17:57Z

Gorilla: Undo revision 38632 by Reverse22 (talk) Link Spam

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

Moyes Dragonfly

2011-12-31T05:16:11Z

Gorilla: Undo revision 38634 by Reverse22 (talk) Link Spam

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

MPMap

2011-12-31T05:14:32Z

Gorilla: Undo revision 38633 by Reverse22 (talk) Link Spam

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

Talk:797

2011-12-25T21:02:44Z

Gorilla: /* Request for deletion */

= Article accuracy is being disputed =

I see no reason why this page is here as the plane doesn't exist on the drawing board.

<blockquote>Boeing is not planning to build a 1,000 passenger commercial airplane dubbed the "797," based on the blended wing body (BWB) concept or any other futuristic concept. It's certainly not in our commercial market forecast, which goes out for 20 years. We think the commercial airplane market favors point-to-point routes, and we're developing the 787 as the perfect match to help meet that demand. [http://www.snopes.com/photos/airplane/boeing797.asp Boeing denial of 797]</blockquote>
-[[User:Gorilla|Gorilla]] 09:37, 25 December 2011 (EST)

Talk:Aviation Week

2011-12-25T20:50:05Z

Gorilla: Created page with "= Request for Deletion = I fail to see why the main article is here. If it was fleshed out, it would be reproducing what should be in wikipedia. - ~~~~"

= Request for Deletion =

I fail to see why the main article is here. If it was fleshed out, it would be reproducing what should be in wikipedia. - [[User:Gorilla|Gorilla]] 15:50, 25 December 2011 (EST)

Talk:797

2011-12-25T14:39:06Z

Gorilla: /* Request for deletion */

= Request for deletion =

I see no reason why this page is here as the plane doesn't exist on the drawing board. [http://www.snopes.com/photos/airplane/boeing797.asp Boeing denial of 797] nor doing anything with the Blended Wing Body concept. -[[User:Gorilla|Gorilla]] 09:37, 25 December 2011 (EST)

Talk:797

2011-12-25T14:37:13Z

Gorilla: Request for deletion

= Request for deletion =

I see no reason why this page is here as the plane doesn't exist on the drawing board. [http://www.snopes.com/photos/airplane/boeing797.asp|Boeing denial of 797] nor doing anything with the Blended Wing Body concept. -[[User:Gorilla|Gorilla]] 09:37, 25 December 2011 (EST)

Talk:7-Zip

2011-12-25T14:13:33Z

Gorilla: /* Deletion request */

= Deletion request =
I'd like to nominate this page for deletion as there is little more than we can add that can not be found on [http://wikipedia.org/wiki/Main_Page Wikipedia] See [http://en.wikipedia.org/wiki/7-zip] for details. It could make more sense to add a extra line or two to the linked page [[Suggested software]] to cover the home page for 7-Zip. [[User:Gorilla|Gorilla]] 08:48, 25 December 2011 (EST)

Talk:7-Zip

2011-12-25T13:48:24Z

Gorilla: Added details to request the deletion of main article.

= Deletion request =
I'd like to nominate this page for deletion as there is little more than we can add that can not be found on [http://wikipedia.org/wiki/Main_Page Wikipedia] See [http://en.wikipedia.org/wiki/7-zip] for details. It could make more sense to add a extra line or two to the linked page [[Suggested_software]] to cover the home page for 7-Zip. [[User:Gorilla|Gorilla]] 08:48, 25 December 2011 (EST)

Fairchild Republic A-10 Thunderbolt II

2011-12-25T13:35:14Z

Gorilla: /* HUD */

{{infobox Aircraft
|image = A-10.jpg
|caption = The "Warthog"
|name = A-10 Thunderbolt II
|type = Military aircraft
|authors = Lee Elliott, Alexis Bory
|fdm = YASim
|status-fdm = 4
|status-systems = 5
|status-cockpit = 4
|status-model = 4
|fgname = A-10
|download =
}}
The [[FlightGear]] '''Fairchild A-10 Thunderbolt II''' (aka '''Warthog''') offers a wide variety of features and controls. Special features include the ability to simulate ordnance use, and a detailed 3D textured cockpit. Many of the A-10's flight systems are modeled as well, such as support for [[Tactical Air Navigation]] (TACAN).

== About the aircraft ==
"This is Fairchild-Republic A-10, also named Warthog. It's a U.S. single-seat, twin-engine, very robust jet aircraft designed for ground attack."

== User's Manual ==
In the current version, the aircraft simulation begins with the aircraft powered down.

The electrical power systems and the [[APU]]'s operation are simulated to a large extent. [[Howto: Air-Air Refueling|Air to air refueling]] is also implemented.

The navigation instruments are [[TACAN]], [[ILS]] and also a [[VHF]] so you can have homing on a [[VOR]] station.

Several external loads are available and the [[HUD]] provides a [[CCIP]] (Continuous Computed Impact Point).

=== Electrical power with APU starting procedure ===
[[File:A-10-electrical-power-control-panel.jpg|thumb|Electrical control panel]]
At FlightGear startup, both electrical power and [[APU]] are shut down and there is no external power supplied.

Everything is asleep...

You, might see, early on, some needles spinning back on the engines gauges panel and the [[VSI]]... this is only a software initialization artifact.

So, look at the right console, there is a panel with 6 switches, that's the Main Electrical Control Panel. Hit Ctrl-c and you will have a view of where to click...

Let's connect the battery: switch on the battery switch. A few indicators should light up, but not all of them. Now with the battery connected you can start the [[APU]].

The [[APU]] start/stop switch is located near the throttle on the left console. Switch it on. Now check the [[APU]]'s tachometer and EGT on the engine gauge panel.

If the [[APU]] has started successfuly you should see the EGT (Exhaust Gas Temperature) rapidly climb to 800/900 °C and then stabilize when the RPMs reach 60%.

[[File:A-10-throttle-engine-start.jpg|thumb|Throttle, engines operation and APU panel]]

Now the [[APU]] has sufficient RPMs to provide electrical power through its generator. So let's turn on the [[APU]] generator. This one is on the main electrical control panel, upper left corner of the electrical control panel, right console again.

With the [[APU]] generator powered up most of the instruments receive electrical power and now the [[AOA]] indexer lights up and the [[HSI]] (the compass) and ADI (artificial horizon) look much better.

At 85% RPM the [[APU]] supplies enough bleed air to start the engines.

[[File:engine-gauges.jpg|thumb|APU running, Engines gauges at stop.]]

=== Engines starting procedure ===
Now that we have minimum electrical power and bleed air supplied by the APU, starting the engines is straight forward.

Just click on one of the throttle rails (Ctrl-c to see them), the throttle will move from stop to idle and the engine start. Wait for the starting cycle light to turn off, turn on the corresponding generator and repeat with the second engine.

Now the complete electrical circuit is powered and you can stop the APU to save some fuel. It wont be useful anymore. (This could change with future development of engines failures...)

=== Fuel System ===
FlightGear A-10 starts with all internal tanks full.

2 wing tanks (left and right), 2 fuselage tanks: left main (aft) linked to left system and right main (forward) linked to right system, up to 3 external tanks (2 wings and 1 fuselage).

Normally the left wing and left main tanks feed the left engine and the APU. The right wing and right main tanks feed the right engine. The two feed lines can be interconnected by opening the cross feed valve ('''E''' switch).

The wing boost pumps ('''G''' switch) supply the respective engines until the wing tanks are empty, then the wing boost pumps automatically shut off. The main boost pumps then supply the respective engines with the remainder fuel in main tanks.

In case of a wing tank boost pump failure, the wing tank fuel will gravity feed its respective main tank if the main tank fuel level is below 600 lbs. Check valves prevent reverse fuel flow from the main tanks to the wing tanks.

In case of a main tank boost pump failure, the affected engine will suction-feed from the affected tank for all power setting up to an altitude of nearly 10,000 feet.

Unequal fuel level between left (aft) main and right (forward) main tank (imbalance superior 750 lbs) will cause a longitudinal CG shift that may exceed allowable limits. In this case, opening the valve "tank gate" create a link between the two main tanks.

Fuel from the external tanks is transfered to the wing or main tanks by pressure from the bleed air system. Wing tanks can be topped when the fuel level is below 1590 lbs.
Main tanks can be topped when the fuel level is below 3034 lbs.
The cycling is repeated until fuel is depleted from the external wing tanks first, and external fuselage tank secondly.

For negative G flight, collector tanks will supply the engine with sufficient fuel for 10 seconds operation at MAX power.

With fully loaded fuel tanks and a full load of armament, the A-10 is heavy--about 50,000 pounds. At this weight the plane is quite difficult to fly. Symptoms you would notice are difficult to take off, difficulty gaining altitude, difficult to manoeuvre without triggering stall warnings or actual stalls.

To avoid these problems, if you choose to equip the plane with full armament you may wish to fill the tanks only half full or so--the plane becomes much easier to fly and half fuel is still enough for a reasonably long flight.

[[File:A-10-fuel-control-doc.jpg|thumb|Fuel Control panel.]]

The '''Fuel Control panel''' is located on the forward part of left console. 1 lever, 4 push buttons and 8 switches are functional.

: ('''A''') Fill Disable buttons, left and right wings tanks. Here fill disabled (button up showing red stripe). Refuel disabled for the wings tanks.

: ('''B''') Fill Disable buttons, left and right main tanks (practically forward and aft fuselage tanks). Here fill enabled (button down hiding red stripe). Refuel enabled for the main tanks.

: ('''C''') Refuel Receiver Door lever.

: ('''D''') External Tanks switches, Wings and Fuselage. Set to OFF to un-pressurize external tanks

: ('''E''') Cross Feed switch, allow any operating boost pump to feed both engines.

: ('''F''') Tank Gate switch, open a valve linking the left (aft) and right (forward) main fuel tanks.

: ('''G''') Boost Pumps (Wing)

: ('''H''') Boost Pumps (Main)

=== HUD ===
[[File:A-10-hud-control-panel.jpg|thumb|HUD Control panel]]

The Head Up Display is turned off by default at aircraft startup. To turn it on electrical power on at least one of the three generator is needed as it isn't wired to the battery.

The '''HUD Control panel''' is located on the upper left corner of the main instrument panel. Three knobs are functional.

: ('''A''') Mode Selector Switch: OFF, TEST (standard display), NAV (standard display), CCIP (standard display + Countinuous Computed Impact Point), CCRP (standard display), EXP (standard display), STBY (standard display). Actually you will mostly use NAV and CCIP as other modes are not modeled yet. See later in Weapons System about reticles use.

: ('''B''') INTEN knob: Adjust the HUD luminosity.

: ('''C''') DEPR knob: Changes the vertical position of the primary aiming reticle in the HUD, There is a digital index in the HUD showing its position, range from -1.00 to 1.00 followed by the letter "D".

'''HUD Symbology:'''

[[File:A-10-hud-symbology.jpg|thumb|HUD Symbology]]

: ('''D''') Pitch ladder.

: ('''E''') Indicated Air Speed, Kts.

: ('''F''') Primary Aiming Reticle.

: ('''G''') Horizon Line

: ('''H''') Primary Aiming Reticle Digital index.

: ('''I''') Magnetic Heading Tape.

: ('''J''') Indicated Altitude in feet (ASL).

: ('''K''') Radar Altitude in feet (AGL) followed by letter "R".

: ('''I''') Aircraft Pitch in degrees, boxed.

: ('''M''') Total Velocity Vector indicator.

: ('''N''') Pointer showing the rudders deflection.

=== Weapons system ===
[[File:A-10-arm-1.jpg|thumb|Armament panel]]
Be sure to have energy before trying to use the armament panel. The gun's rounds counter ('''A''') should be lighted in blue and the HUD should be active.

There is actually 2 AIM-9, the GAU9 gatling gun, and MK85 250 pound bombs.

First of all push up the Master Switch to ARM ('''B''').

For the gun, push up the Gun Rate Switch to HI (right of the rounds counter). You should have on the left side of the main panel a red light indicating 'Gun Ready'. Press key 'e' on the keyboard to fire the gun.

For AIM-9, turn ('''C''') the AIM-9 Mode Knob to SEL (click on the right side of the knob). Now a big circle appears on the HUD symbology, that the searching aera of the AIM-9. Now select Pylon #11, you should ear the seeker sound. This sound is audible only when an AIM-9 is available, selected and searching. Press key ',' to fire the AIM-9.

(In Flightgear, the key ',' is usaly used for left brake, in the A-10 a nasal script intercepts the binding for weapons release, this is not a definitive solution).

You can also choose to fly without the AIM-9s ans the ECM pod, press Tab or Ctrl-I on the keyboard to display the config menu.

== External links ==
* [http://croo.murgl.org/fgfs/AG-demo/index.html A-10 Ground bombing demo--tanks on a bombing range in Nevada]
* [http://croo.murgl.org/fgfs/index.html Info from original developers]
* [http://brenthugh.com/flightgear/Sun_Valley_Tank_Invasion1.zip Several ground bombing scenarios suitable for the A-10, involving moving and static tank formations, explodable M1 Abrams tanks, etc.]

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
* [[FlightGear 1.0 default aircraft]]
[[Fr:Fairchild A-10]]]

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

AI Systems

2011-12-25T13:31:58Z

Gorilla:

{{Out of date}}

[[FlightGear]] has a number of more or less independently operating systems for simulating semi- intelligent interaction with the environment, so called '''AI Systems'''. Because there often times exists some confusion regarding to which system does what, one should take notice of the differences between them: The major distinction is that between an older ATC/AI system, and a newer AIModels system. The AIModels system can, in turn, be controlled in at least three different ways; directly, using a script, through the multiplayer system, and through a subsystem known as the traffic manager.

* To enable/disable the AI traffic system:
** use <tt>--enable-ai-traffic</tt> / <tt>--disable-ai-traffic</tt> for FlightGear >= 2.2.0
** ( use <tt>--prop:/sim/ai-traffic/enabled=[1|0]</tt> for FlightGear 2.0.0 and older )
* To enable/disable the AIModels system: use <tt>--prop:/sim/ai/enabled=[1|0]</tt>

== ATC/AI ==
'''The ATC/AI system was removed with FlightGear 2.2.0. It was replaced by a new module, see [[Interactive Traffic]]'''

The [[Air traffic control|Air Traffic Control]] system simulates interaction between the user and a number of AI controlled cessna and piper aircraft. This system can be controlled using the GUI from within FlightGear. The ATC/AI system is no longer maintained and marked for deprecation. Recent reports have indicated that the ATC/AI system may be causing numerical computation problems in some cases, resulting in a flurry of NaN warning messages on the FlightGear console. If you experience this, you might consider shutting down the ATC/AI system

For airports with a tower frequency, if that frequency is tuned in to your radio, you may contact ATC.

To obtain the tower frequencies for an airport within range of ATC, go to the ATC/AI menu, choose Frequencies to display the dialog. If there are any airports within 40nm range, a button with the airport designation will appear. Click see the frequencies. Tune the tower frequency in on the COM1 radio and then hit the single quote key to open the ATC window.

Points:
* Untowered airports are not supported in any way by ATC.
* You must be within 40 nautical miles of an ATC facility (towered airport with tower frequencies) to contact ATC.

== AI Models ==
Starting with FlightGear version 0.9.4 you can place AI objects in the "FlightGear world". In version 0.9.4 the AI objects can be defined in the preferences.xml file, or in an airplane's *-set.xml file. In later versions they are defined in a "scenario file" only. The types of AI objects you can have are airplanes, ships, thunderstorms, thermals/sinks, static and ballistic objects. AI objects have some things in common: The have a location in the "FlightGear world", they can have an associated exterior 3D model, and they can move according to an internal [[Flight Dynamics Model|FDM]] (flight dynamics model). As of now, these objects are created at simulator start-up by adding some XML code to a scenario file. The scenario file must be in the data/AI directory. You select which scenario files you want to use by naming it in the preferences.xml file. The preferences.xml file has an entry that looks like this (FlightGear versions newer than 0.9.4, including Git):

<ai>
<enabled type="bool">true</enabled>
<scenario>aircraft_demo</scenario>
</ai>

The above bit of XML enables the AI system and selects a scenario file called aircraft_demo.xml.

''Notes:
* XML tags are ''case-sensitive''.
* Introducing certain characters into the XML file, even as part of a comment, will cause the file to choke. These include &, <, and --.''

The scenario file contains one entry for each AI object. The entry specifies what kind of object to create, what its initial conditions will be, and optionally (for aircraft and ships) a flight plan. The entry for a sailboat could look like this:

<entry>
<type>ship</type>
<model>models/geometry/sailboat.xml</model>
<speed-ktas type="double">12.0</speed-ktas>
<altitude-ft type="double">0.0</altitude-ft>
<longitude type="double">-122.33333</longitude>
<latitude type="double">37.61667</latitude>
<heading type="double">20.0</heading>
</entry>

Most of the parameters are self-explanitory. The "type" of object can be one of "aircraft", "ship", "carrier", "thunderstorm", "thermal", "ballistic" or "static". The rest of the items give the AI object a model, a starting location, and a starting speed and direction. You use the <MODEL> item to give the object any valid exterior model. You can even make the ship look like an airplane if you want! Note that the speed of the AI object is true airspeed, and since AI aircraft and ships don't feel wind or current then this also the ground speed. The "ship" type can also have a <RUDDER> value specified, which will cause the ship to move in a circle (HINT: use small values, five degrees or less, and right rudder is positive). Here is an example of how to create an aircraft AI object:


<entry>
<type>aircraft</type>
<class>light</class>
<model>Aircraft/a4/Models/a4-blue.xml</model>
<speed-ktas type="double">320.0</speed-ktas>
<altitude-ft type="double">7000.0</altitude-ft>
<longitude type="double">-122.6</longitude>
<latitude type="double">37.9</latitude>
<heading type="double">210.0</heading>
<bank type="double">-15.0</bank>
</entry>

It looks much the same as the ship AI code. There are two differences, the <class> item and the <bank> item. If the class is set to "tanker" the airplane will allow you to refuel if you can get close behind it. The bank is of course similar to the ship's rudder. In the above example the A-4 will be orbiting to the left at 15 degrees of bank. You can also create a ship or airplane with a flight plan. In this case the object will follow the flight plan, and then delete itself when it reaches the end. The flight plans are kept in data/Data/AI/FlightPlans. To create an airplane with a flightplan do this:

<entry>
<type>aircraft</type>
<class>jet-transport</class>
<model>Aircraft/737/Models/737.xml</model>
<flightplan>ksfo_ils28l.xml</flightplan>
</entry>

To make a thunderstorm, use this:


<entry>
<type>storm</type>
<model>Models/Geometry/thunderstorm.xml</model>
<speed-ktas type="double">20.0</speed-ktas>
<altitude-ft type="double">4000.0</altitude-ft>
<latitude type="double">37.3917</latitude>
<longitude type="double">-122.2817</longitude>
<heading type="double">90</heading>
</entry>

There's not much to it. No, they don't turn :) To create a thermal, use this:

<entry>
<type>thermal</type>
<latitude type="double">37.61633</latitude>
<longitude type="double">-122.38334</longitude>
<strength-fps type="double">8.33</strength-fps>
<diameter-ft type="double">4000</diameter-ft>
<height-msl>6000</height-msl>
<model>Models/Geometry/thermalcap.xml</model>
</entry>

The AI thermals don't move, they are invisible, and they don't "lean" downwind. The <strength-fps> defines the maximum vertical velocity of the airmass at the center of the thermal. The strength decreases to zero at the thermal's edge. A
model can be assigned to the thermal, and usually this will be a small cloud to mark the thermal's location. To create a sink, just give a "thermal" a negative strength, and give it a null model. Please see the demo scenario (thermal_demo.xml) for examples.

A ballistic AI object starts with an initial azimuth, elevation and speed, then follows a ballistic path from there (with air resistance and wind included). Try this:

<entry>
<type>ballistic</type>
<model>Models/Geometry/rocket.xml</model>
<speed-fps type="double">500.0</speed-fps>
<altitude-ft type="double">50.0</altitude-ft>
<longitude type="double">-122.39</longitude>
<latitude type="double">37.62</latitude>
<heading type="double">200.0</heading>
<azimuth type="double">70.0</azimuth>
<elevation type="double">45.0</elevation>
</entry>

Note that the speed is now in feet per second.

The AI storm objects can be displayed on weather radar. See the Aircraft/Instruments/wxradar.xml file for details. The AI aircraft objects can be displayed on radar. See the Aircraft/Instruments/radar.xml file for details.

You can make your own AI scenario file, called say my_scenario.xml, and cut/paste entries from the other scenario files to build an AI scenario as complicated as you like.

The following how-to shows you how to animate a tail-dragger airplane so that its pitch attitude looks proper for the AI aircraft's airpeed. This is not needed for aircraft with tricycle landing gear.

=== Using Interpolation Tables ===
Interpolation tables are very handy for effecting animations that are non-linear in relation to the property they are referenced to.

They save the use of factors, offsets and min/max values.

For example; relating flap extension to airspeed of an AI model. Typically an aircraft will extend flaps on final approach to control Indicated Airspeed (IAS) and stall speed to affect a low speed controlled landing. Upon touchdown the extra lift efficiency introduced by the flaps is no longer required or desirable, hence the flaps will be retracted ASAP after touch down.

This is relatively simple in a sim aircraft as the /surface-positions/flap-pos-norm property is a normalised indicator of the flap setting chosen by the pilot.

AI aircraft have no pilots to control flaps nor does the flight plan <flaps-down>true/false</flaps-down> parameter effect the /AI property tree parameter, a relationship to the IAS is the next best choice.

To effect this relationship (IAS/flap-position) using factors/offsets and min/max would be quite difficult and non-intuitive. Using interpolation tables allows the following scenario to be setup very easily and intuitively:

: '''C172P'''
{| border="1"
|-
| Max
| 123 KIAS
|-
| Cruise
| 90 KIAS
|-
| Stall (no flaps)
| 50 KIAS
|-
| Flaps
| 0, 10, 20, 30 deg.
|-
| Approach
| 90 KIAS
|-
| 10° flaps
| 90 KIAS
|-
| 20° flaps
| 70 KIAS
|-
| 30° flaps
| 60 KIAS
|-
| Flare & touch down
| 50 KIAS
|-
| Brake
| 45 KIAS
|-
| Retract flaps
| 45 KIAS
|}

'''Table IAS/flap extension'''
{| border="2"
|+
| IAS (kt) || Flaps
|-
| 90
| 0
|-
| 70 - 89
| 10
|-
| 60-69
| 20
|-
| 45-59
| 30
|-
| < 45
| 0
|}

When the pilot extends the flaps "one notch" they will extend to "10°" etc. In the property tree, these 4 steps will typically be normalised to 0.00, 0.33, 0.66, 1.00. This will differ from aircraft to aircraft. If the aircraft does not have equal extensions for each "notch" of flaps, the values observed may be; 0.00, 0.10, 0.30, 0.66, 1.00. Modeling this non-linear extension using "factor, offset, min/max" would be extremely difficult if not impossible. Modeling it using interpolation tables is very easy, as you shall see.

For sim animations, the actual physical rotation of the control surface in the real world needs to be researched; this may reveal a linear or non-linear relationship between "nominal flap extension indicator" and physical rotation of the surface. That is, "10 degrees of flap" might only involve rotating the flap surface 5 degrees around its axis in the wing structure. In our 0,10,20,30 scenarios, assuming a linear relationship, 30 degrees of flap would result in the flap being rotated 15 degrees around its wing axis. Therefore the normalised /surface-positions/flap-pos-norm property would have a factor of 15 applied to the rotate animation

The way to change a linear relationship that uses "factor, offset, min/max" in the sim animation to a interpolation table in the AI animation is best understood by examining how "factor, offset, min/max" approach works:

# Take normalised value of the flaps (0=retracted, 1=extended)
# Apply the factor.
# Apply the offset
# Apply the min/max values

e.g.
factor=60
offset= -30
min=-10
max+10

these figures are nonsense but are used to illustrate a point:

flaps retracted(0°) = 0 x 60 = 0, (offset=-30) = -30, (min= -10) = -10
flaps extended(10°) = 0.33 x 60 = 20, (offset=-30) = -10, (min= -10) = -10
flaps extended(20°) = 0.66 x 60 = 40, (offset=-30) = 10, (min= -10/max=10) = 10
flaps extended(30°) = 1.00 x 60 = 60, (offset=-30) = 30, (max=10) = 10

more realistically, offset and min max are not used for flaps, only a factor.

say 27°, this represents the maximum rotation of the 3-D component in the model around its defined axis.

flaps retracted(0°) = 0 x 27 = 0
flaps extended(10°) = 0.33 x 27 = 9
flaps extended(20°) = 0.66 x 27 = 18
flaps extended(30°) = 1.00 x 27 = 27

from this it can be seen that the 3-D object will be rotated 0°, 9°, 18° & 27° to represent the 0°, 10°, 20° & 30° deployment of the flaps.

Relating this back to the speeds above:

{| border="1"
|+
| IAS (kt)
| <rotate> value
|-
| 0
| 0
|-
| 44
| 0
|-
| 45
| 27
|-
| 59
| 27
|-
| 60
| 18
|-
| 69
| 18
|-
| 70
| 9
|-
| 89
| 9
|-
| 90
| 0
|-
| 100
| 0
|}

this gives a stepped effect, where the movement is limited to 1knt of airspeed. That is the 3-D object will linearly move from 9° to 18° while the aircraft looses speed from 70 knots to 69 knots. This behaviour will make the need for an upper and lower limit of a stepped value obvious.

a simplified table of:

{| border="1"
|+
| IAS (kt)
| <rotate> value
|-
| 0
| 0
|-
| 45
| 27
|-
| 60
| 18
|-
| 70
| 9
|-
| 90
| 9
|-
| 100
| 0
|}

will cause the flaps to start extending at the rate of 1/45 x 27 degrees per knot of airspeed gained until 45 knots when the rate of change will adjust to the new gradient. This is not how flaps behave, but can be used to good effect with "tail dragger" animations where at a certain IAS the tail starts rising, maybe at an increasing rate, until flying attitude is reached when it stops rising any further. The tail rising is not a stepped function of IAS.

Now we have the basic ideas behind interpolation tables, the question is how are they implemented…answer;…easy ….an example of the stepped flaps animation above

<interpolation>
<entry><ind>0.000></ind><dep>0.000</dep></entry>
<entry><ind>44.00></ind><dep>0.000</dep></entry>
<entry><ind>45.00></ind><dep>27.00</dep></entry>
<entry><ind>59.00></ind><dep>27.00</dep></entry>
<entry><ind>59.00></ind><dep>27.00</dep></entry>
<entry><ind>60.00></ind><dep>18.00</dep></entry>
<entry><ind>69.00></ind><dep>18.00</dep></entry>
<entry><ind>70.00></ind><dep>9.000</dep></entry>
<entry><ind>89.00></ind><dep>9.000</dep></entry>
<entry><ind>90.00></ind><dep>0.000</dep></entry>
<entry><ind>100.0></ind><dep>0.000</dep></entry>
</interpolation>

Here endth Interpolation tables 101
:-Dene

=== Submodels ===
Submodels are AI ballistic objects that emanate from, fall from, or launch from the user aircraft. They are presently used to model smoke, contrails, flares, tracers, bombs, drop tanks and flight path markers.

Submodels are controlled by the submodel manager. The manager reads a submodel configuration file at the start of the sim session. This configuration file is written by the aircraft author and defines all the submodels for that particular aircraft.

As an example examine the submodels file in the Aircraft/737-300 directory. This file creates two submodels which will become the airplane's left and right engine contrails. Each contrail needs its own submodel definition because the contrails begin at different locations. Each contrail consists of a train of individual "puff" models that are released in rapid succession as long as the "trigger" property is true. We ensure an unlimited supply of puffs by setting the "count" parameter to -1. The individual puffs, being AIBallistic objects, will follow their own ballistic paths once released. In this case we have used the "bouyancy" parameter to negate gravity in the ballistic path. The puffs have been given a life span of eight seconds. At cruising speed the [[Boeing 737|737]] will thus have about 400 puffs behind it at any moment.

* [http://wiki.flightgear.org/images/0/0f/Submodels.txt This annotated submodels.xml file] gives a good idea about how to create submodel files, what parameters are available and how to use them, and also the type of research needed to make sure the information and models are accurate historically.

=== Multiplayer controlled traffic ===
{{Main article|Howto: Multiplayer}}
FlightGear's multiplayer system also makes use of the AIModels subsystem.

=== Traffic Manager controlled traffic ===
{{Main article|Interactive Traffic}}
Traffic Manager controlled input to the AIModels subsystem is also known as [[Interactive traffic|Interactive Traffic]].

[[Category:FlightGear feature]]

=== AI Scenarios ===
{{Main article|AI Scenarios}}

Fairchild Republic A-10 Thunderbolt II

2011-12-25T12:55:34Z

Gorilla: /* Fuel System */

{{infobox Aircraft
|image = A-10.jpg
|caption = The "Warthog"
|name = A-10 Thunderbolt II
|type = Military aircraft
|authors = Lee Elliott, Alexis Bory
|fdm = YASim
|status-fdm = 4
|status-systems = 5
|status-cockpit = 4
|status-model = 4
|fgname = A-10
|download =
}}
The [[FlightGear]] '''Fairchild A-10 Thunderbolt II''' (aka '''Warthog''') offers a wide variety of features and controls. Special features include the ability to simulate ordnance use, and a detailed 3D textured cockpit. Many of the A-10's flight systems are modeled as well, such as support for [[Tactical Air Navigation]] (TACAN).

== About the aircraft ==
"This is Fairchild-Republic A-10, also named Warthog. It's a U.S. single-seat, twin-engine, very robust jet aircraft designed for ground attack."

== User's Manual ==
In the current version, the aircraft simulation begins with the aircraft powered down.

The electrical power systems and the [[APU]]'s operation are simulated to a large extent. [[Howto: Air-Air Refueling|Air to air refueling]] is also implemented.

The navigation instruments are [[TACAN]], [[ILS]] and also a [[VHF]] so you can have homing on a [[VOR]] station.

Several external loads are available and the [[HUD]] provides a [[CCIP]] (Continuous Computed Impact Point).

=== Electrical power with APU starting procedure ===
[[File:A-10-electrical-power-control-panel.jpg|thumb|Electrical control panel]]
At FlightGear startup, both electrical power and [[APU]] are shut down and there is no external power supplied.

Everything is asleep...

You, might see, early on, some needles spinning back on the engines gauges panel and the [[VSI]]... this is only a software initialization artifact.

So, look at the right console, there is a panel with 6 switches, that's the Main Electrical Control Panel. Hit Ctrl-c and you will have a view of where to click...

Let's connect the battery: switch on the battery switch. A few indicators should light up, but not all of them. Now with the battery connected you can start the [[APU]].

The [[APU]] start/stop switch is located near the throttle on the left console. Switch it on. Now check the [[APU]]'s tachometer and EGT on the engine gauge panel.

If the [[APU]] has started successfuly you should see the EGT (Exhaust Gas Temperature) rapidly climb to 800/900 °C and then stabilize when the RPMs reach 60%.

[[File:A-10-throttle-engine-start.jpg|thumb|Throttle, engines operation and APU panel]]

Now the [[APU]] has sufficient RPMs to provide electrical power through its generator. So let's turn on the [[APU]] generator. This one is on the main electrical control panel, upper left corner of the electrical control panel, right console again.

With the [[APU]] generator powered up most of the instruments receive electrical power and now the [[AOA]] indexer lights up and the [[HSI]] (the compass) and ADI (artificial horizon) look much better.

At 85% RPM the [[APU]] supplies enough bleed air to start the engines.

[[File:engine-gauges.jpg|thumb|APU running, Engines gauges at stop.]]

=== Engines starting procedure ===
Now that we have minimum electrical power and bleed air supplied by the APU, starting the engines is straight forward.

Just click on one of the throttle rails (Ctrl-c to see them), the throttle will move from stop to idle and the engine start. Wait for the starting cycle light to turn off, turn on the corresponding generator and repeat with the second engine.

Now the complete electrical circuit is powered and you can stop the APU to save some fuel. It wont be useful anymore. (This could change with future development of engines failures...)

=== Fuel System ===
FlightGear A-10 starts with all internal tanks full.

2 wing tanks (left and right), 2 fuselage tanks: left main (aft) linked to left system and right main (forward) linked to right system, up to 3 external tanks (2 wings and 1 fuselage).

Normally the left wing and left main tanks feed the left engine and the APU. The right wing and right main tanks feed the right engine. The two feed lines can be interconnected by opening the cross feed valve ('''E''' switch).

The wing boost pumps ('''G''' switch) supply the respective engines until the wing tanks are empty, then the wing boost pumps automatically shut off. The main boost pumps then supply the respective engines with the remainder fuel in main tanks.

In case of a wing tank boost pump failure, the wing tank fuel will gravity feed its respective main tank if the main tank fuel level is below 600 lbs. Check valves prevent reverse fuel flow from the main tanks to the wing tanks.

In case of a main tank boost pump failure, the affected engine will suction-feed from the affected tank for all power setting up to an altitude of nearly 10,000 feet.

Unequal fuel level between left (aft) main and right (forward) main tank (imbalance superior 750 lbs) will cause a longitudinal CG shift that may exceed allowable limits. In this case, opening the valve "tank gate" create a link between the two main tanks.

Fuel from the external tanks is transfered to the wing or main tanks by pressure from the bleed air system. Wing tanks can be topped when the fuel level is below 1590 lbs.
Main tanks can be topped when the fuel level is below 3034 lbs.
The cycling is repeated until fuel is depleted from the external wing tanks first, and external fuselage tank secondly.

For negative G flight, collector tanks will supply the engine with sufficient fuel for 10 seconds operation at MAX power.

With fully loaded fuel tanks and a full load of armament, the A-10 is heavy--about 50,000 pounds. At this weight the plane is quite difficult to fly. Symptoms you would notice are difficult to take off, difficulty gaining altitude, difficult to manoeuvre without triggering stall warnings or actual stalls.

To avoid these problems, if you choose to equip the plane with full armament you may wish to fill the tanks only half full or so--the plane becomes much easier to fly and half fuel is still enough for a reasonably long flight.

[[File:A-10-fuel-control-doc.jpg|thumb|Fuel Control panel.]]

The '''Fuel Control panel''' is located on the forward part of left console. 1 lever, 4 push buttons and 8 switches are functional.

: ('''A''') Fill Disable buttons, left and right wings tanks. Here fill disabled (button up showing red stripe). Refuel disabled for the wings tanks.

: ('''B''') Fill Disable buttons, left and right main tanks (practically forward and aft fuselage tanks). Here fill enabled (button down hiding red stripe). Refuel enabled for the main tanks.

: ('''C''') Refuel Receiver Door lever.

: ('''D''') External Tanks switches, Wings and Fuselage. Set to OFF to un-pressurize external tanks

: ('''E''') Cross Feed switch, allow any operating boost pump to feed both engines.

: ('''F''') Tank Gate switch, open a valve linking the left (aft) and right (forward) main fuel tanks.

: ('''G''') Boost Pumps (Wing)

: ('''H''') Boost Pumps (Main)

=== HUD ===
[[File:A-10-hud-control-panel.jpg|thumb|HUD Control panel]]

The Head Up Display is turned off by default at aircraft startup. To turn it on electrical power on at least one of the three generator is needed as it isn't wired to the battery.

The '''HUD Control panel''' is located on the upper left corner of the main instrument panel. Three knobs are functional.

('''A''') Mode Selector Switch: OFF, TEST (standard display), NAV (standard display), CCIP (standard display + Countinuous Computed Impact Point), CCRP (standard display), EXP (standard display), STBY (standard display). Actually you will mostly use NAV and CCIP as other modes are not modeled yet. See later in Weapons System about reticles use.

('''B''') INTEN knob: Adjust the HUD luminosity.

('''C''') DEPR knob: Changes the vertical position of the primary aiming reticle in the HUD, There is a digital index in the HUD showing its position, range from -1.00 to 1.00 followed by the letter "D".

'''HUD Symbology:'''

[[File:A-10-hud-symbology.jpg|thumb|HUD Symbology]]

('''D''') Pitch ladder.

('''E''') Indicated Air Speed, Kts.

('''F''') Primary Aiming Reticle.

('''G''') Horizon Line

('''H''') Primary Aiming Reticle Digital index.

('''I''') Magnetic Heading Tape.

('''J''') Indicated Altitude in feet (ASL).

('''K''') Radar Altitude in feet (AGL) followed by letter "R".

('''I''') Aircraft Pitch in degrees, boxed.

('''M''') Total Velocity Vector indicator.

('''N''') Pointer showing the rudders deflection.

=== Weapons system ===
[[File:A-10-arm-1.jpg|thumb|Armament panel]]
Be sure to have energy before trying to use the armament panel. The gun's rounds counter ('''A''') should be lighted in blue and the HUD should be active.

There is actually 2 AIM-9, the GAU9 gatling gun, and MK85 250 pound bombs.

First of all push up the Master Switch to ARM ('''B''').

For the gun, push up the Gun Rate Switch to HI (right of the rounds counter). You should have on the left side of the main panel a red light indicating 'Gun Ready'. Press key 'e' on the keyboard to fire the gun.

For AIM-9, turn ('''C''') the AIM-9 Mode Knob to SEL (click on the right side of the knob). Now a big circle appears on the HUD symbology, that the searching aera of the AIM-9. Now select Pylon #11, you should ear the seeker sound. This sound is audible only when an AIM-9 is available, selected and searching. Press key ',' to fire the AIM-9.

(In Flightgear, the key ',' is usaly used for left brake, in the A-10 a nasal script intercepts the binding for weapons release, this is not a definitive solution).

You can also choose to fly without the AIM-9s ans the ECM pod, press Tab or Ctrl-I on the keyboard to display the config menu.

== External links ==
* [http://croo.murgl.org/fgfs/AG-demo/index.html A-10 Ground bombing demo--tanks on a bombing range in Nevada]
* [http://croo.murgl.org/fgfs/index.html Info from original developers]
* [http://brenthugh.com/flightgear/Sun_Valley_Tank_Invasion1.zip Several ground bombing scenarios suitable for the A-10, involving moving and static tank formations, explodable M1 Abrams tanks, etc.]

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
* [[FlightGear 1.0 default aircraft]]
[[Fr:Fairchild A-10]]]

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

Howto:Set up a FGCom server

2011-12-25T12:11:10Z

Gorilla: Rejigged the top part of the page for readibility

__TOC__

= Introduction =

This page is for installing FGCom '''Server '''. If you want to have voice communications within FlightGear, you are probably wanting to install the [[FGCom|client]].

This document is to assist in setting up hot spares as potential failover for the new server and for replacing that server if/when that becomes necessary. It is not expected that this will be a widely used document, nonetheless, the information contained is no less valuable for that.

= Install Asterisk =
You need an instance of Asterisk on the server, you can either install Asterisk via a package manager (if you're using CentOS/RHEL) or via the source code if you're on a different distro. For easiness (and because I can) I chose to do it via the package manager.
We used CentOS (this works for RedHat too) and the instructions for installing it on CentOS/RHEL are as follows:

== CentOS/RHEL ==

=== Setting up the Package Manager ===

In the ''''/etc/yum.repos.d'''' folder create the following files:

centos-asterisk.repo:
[asterisk-tested]
name=CentOS-$releasever - Asterisk - Tested
baseurl=http://packages.asterisk.org/centos/$releasever/tested/$basearch/
enabled=0
gpgcheck=0
#gpgkey=http://packages.asterisk.org/RPM-GPG-KEY-Digium

[asterisk-current]
name=CentOS-$releasever - Asterisk - Current
baseurl=http://packages.asterisk.org/centos/$releasever/current/$basearch/
enabled=1
gpgcheck=0
#gpgkey=http://packages.asterisk.org/RPM-GPG-KEY-Digium

centos-digium.repo:
[digium-tested]
name=CentOS-$releasever - Digium - Tested
baseurl=http://packages.digium.com/centos/$releasever/tested/$basearch/
enabled=0
gpgcheck=0
#gpgkey=http://packages.digium.com/RPM-GPG-KEY-Digium

[digium-current]
name=CentOS-$releasever - Digium - Current
baseurl=http://packages.digium.com/centos/$releasever/current/$basearch/
enabled=1
gpgcheck=0
#gpgkey=http://packages.digium.com/RPM-GPG-KEY-Digium

=== Installing the Packages ===

[root@localhost~]# yum install asterisk16 asterisk16-configs asterisk16-voicemail dahdi-linux dahdi-tools libpri

You will then see something like this:
=========================================================================================
Package Arch Version Size
=========================================================================================
Installing:
asterisk16 i386 1.6.0.15-1_centos5 4.0 k
Installing for dependencies:
asterisk-sounds-core-en-gsm noarch 1.4.15-1_centos5 1.7 M
asterisk16-core i386 1.6.0.15-1_centos5 11 M
asterisk16-dahdi i386 1.6.0.15-1_centos5 837 k
asterisk16-doc i386 1.6.0.15-1_centos5 10 k
asterisk16-voicemail i386 1.6.0.15-1_centos5 264 k
dahdi-firmware noarch 2.0.1-1_centos5 1.9 k
dahdi-firmware-oct6114-064 noarch 1.05.01-1_centos5 165 k
dahdi-firmware-oct6114-128 noarch 1.05.01-1_centos5 166 k
dahdi-firmware-tc400m noarch MR6.12-1_centos5 1.7 M
dahdi-linux i386 2.2.0.2-1_centos5 3.3 k
kernel i686 2.6.18-164.el5 16 M
kmod-dahdi-linux i686 2.2.0.2-1_centos5.2.6.18_164.el5 3.4 M
kmod-dahdi-linux-fwload-vpmadt032 i686 2.2.0.2-1_centos5.2.6.18_164.el5 124 k
libpri i386 1.4.10.1-1_centos5 103 k
libss7 i386 1.0.2-1_centos5 63 k
yum-kmod noarch 1.1.16-13.el5.centos 17 k

Transaction Summary
========================================================================================
Install 17 Package(s)
Update 0 Package(s)
Remove 0 Package(s)

Total download size: 35 M
Is this ok [y/N]:

Press ''''y'''' and press ''''Enter''''

Downloading Packages:
(1/17): dahdi-firmware-2.0.1-1_centos5.noarch.rpm | 1.9 kB 00:00
(2/17): dahdi-linux-2.2.0.2-1_centos5.i386.rpm | 3.3 kB 00:00
(3/17): asterisk16-1.6.0.15-1_centos5.i386.rpm | 4.0 kB 00:00
(4/17): asterisk16-doc-1.6.0.15-1_centos5.i386.rpm | 10 kB 00:00
(5/17): yum-kmod-1.1.16-13.el5.centos.noarch.rpm | 17 kB 00:00
(6/17): libss7-1.0.2-1_centos5.i386.rpm | 63 kB 00:00
(7/17): libpri-1.4.10.1-1_centos5.i386.rpm | 103 kB 00:00
(8/17): kmod-dahdi-linux-fwload-vpmadt032-2.2.0.2-1_centos5.2.6.18_164.el5.i686.rpm | 124 kB 00:00
(9/17): dahdi-firmware-oct6114-064-1.05.01-1_centos5.noarch.rpm | 165 kB 00:00
(10/17): dahdi-firmware-oct6114-128-1.05.01-1_centos5.noarch.rpm | 166 kB 00:00
(11/17): asterisk16-voicemail-1.6.0.15-1_centos5.i386.rpm | 264 kB 00:01
(12/17): asterisk16-dahdi-1.6.0.15-1_centos5.i386.rpm | 837 kB 00:04
(13/17): dahdi-firmware-tc400m-MR6.12-1_centos5.noarch.rpm | 1.7 MB 00:08
(14/17): asterisk-sounds-core-en-gsm-1.4.15-1_centos5.noarch.rpm | 1.7 MB 00:08
(15/17): kmod-dahdi-linux-2.2.0.2-1_centos5.2.6.18_164.el5.i686.rpm | 3.4 MB 00:17
(16/17): asterisk16-core-1.6.0.15-1_centos5.i386.rpm | 11 MB 00:57
(17/17): kernel-2.6.18-164.el5.i686.rpm | 16 MB 00:23
-------------------------------------------------------------------------------------
Total 283 kB/s | 35 MB
02:06
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID e8562897
Importing GPG key 0xE8562897 "CentOS-5 Key (CentOS 5 Official Signing Key) " from
/etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
Is this ok [y/N]:

Press ''''y'''' and ''''Enter'''' again

Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : kernel [ 1/17]
Installing : asterisk16-core [ 2/17]
Installing : kmod-dahdi-linux [ 3/17]
Installing : asterisk16-doc [ 4/17]
Installing : kmod-dahdi-linux-fwload-vpmadt032 [ 5/17]
Installing : asterisk-sounds-core-en-gsm [ 6/17]
Installing : dahdi-firmware-oct6114-064 [ 7/17]
Installing : yum-kmod [ 8/17]
Installing : dahdi-firmware-tc400m [ 9/17]
Installing : dahdi-firmware-oct6114-128 [10/17]
Installing : asterisk16-voicemail [11/17]
Installing : libss7 [12/17]
Installing : libpri [13/17]
Installing : dahdi-firmware [14/17]
Installing : dahdi-linux [15/17]
Installing : asterisk16-dahdi [16/17]
Installing : asterisk16 [17/17]

Installed: asterisk16.i386 0:1.6.0.15-1_centos5
Dependency Installed: asterisk16-core.i386 0:1.6.0.15-1_centos5 ...
Complete!
[root@localhost yum.repos.d]#

When you are met with the screen above with the words ''''Complete!'''' on it then you are ready to move on to Part 2: Configuration Files

== Debian/Ubuntu ==
This about covers it:

apt-get install asterisk

== Install from Source ==

=== Downloading the Source ===
Downloading necessary packages: LIBPRI, DAHDI, AND Asterisk

cd /usr/src
wget http://www.asterisk.org/downloads/asterisk/releases/asterisk-1.6.2-current.tar.gz
wget http://downloads.asterisk.org/pub/telephony/libpri/releases/libpri-1.4.11.3.tar.gz
wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/releases/dahdi-linux-complete-2.3.0.1+2.3.0.tar.gz

=== Installing Libpri ===

tar -xvzf libpri-1.4.11.3.tar.gz
cd libpri-1.4.11.3
make
make install

=== Installing DAHDI ===

cd /usr/src
tar -xvzf dahdi-linux-complete-2.3.0.1+2.3.0.tar.gz
cd dahdi-linux-complete-2.3.0.1+2.3.0
make
make install
make config

=== Installing Asterisk ===

cd /usr/src
tar -xvzf asterisk-1.6.2-current.tar.gz
cd asterisk-1.6.2.11/
make clean
./configure
make
make install
make samples
make config

= Configuration Files =

Regardless of what OS you are running Asterisk on and regardless of what method of installation you used to install it, there are 2 main configuration files that we need to work with and one file we need to generate and include:

=== extensions.conf ===
If you are using an existing Asterisk server then add the following lines to the [default] context:
#include "fgcom.inc"
include => fgcom
Or if you are using a new Asterisk install remove everything from ''''extensions.conf'''' and put in:
[general]
static=yes
writeprotect=yes
;
[default]
#include "fgcom.inc"
include => fgcom

=== iax.conf ===
[general]
bandwith=low
disallow=lpc10
jitterbuffer=yes
forcejitterbuffer=no
tos=lowdelay
autokill=30000
codecpriority=host
disallow=all
allow=gsm
allow=ilbc
allow=g726
language=en
maxauthreq=30
context=fgcom
minregexpire=30
maxregexpire=10800
maxexpirey=10800
defaultexpirey=10800
;
[guest]
type=user
username=guest
secret=guest
context=fgcom
qualify=yes
callerid=Guest IAX User
host=dynamic
requirecalltoken=no
;

=== fgcom.inc ===
This is a special file generated using a script. It should be placed in the Asterisk config directory (/etc/asterisk/ normally).

Generation details to follow

FGCom (before 3.0)

2011-12-25T11:58:40Z

Gorilla: Added links to sourceforge respository

{{cleanup}}

{{Infobox Software
| title = FGCom
| logo =
| image =
| alt =
| developedby = Holger Wirtz, Martin Spott, Csaba Halasz
| initialrelease =
| latestrelease =
| writtenin =
| os =
| platform =
| developmentstatus = Active (2007-)
| type =
| license = [[GNU General Public License]]
| website = http://sourceforge.net/projects/fgcom/
}}
'''FGCom''' is an addon for [[FlightGear]]. With FGCom (and the infrastructure behind it), FlightGear now has a realtime voice communication system which enriches the FlightGear capabilities, especially for [[Howto: Multiplayer|multiplayer]] events, like:

* Flying in groups, see the [http://www.flightgear.org/forums/viewforum.php?f=10 multiplayer events forum]
** Invite friends to a guided sightseeing tour in your most beloved area or do “Fly In's”
** Do military training like [[Howto: Air-Air Refueling|“Air-Air-Refuelling”]], “Dog fights”, “Escort flights”, etc.
* Offering additional services at an airport like [[Air traffic control|ATC]], [[Vehicle|snowplows, pushbacks]], [[FlightGear Race|racing-events]] etc.
* Have a [[Dual control|real time flighttraining]] (e.g. pilot in Hongkong, teacher in Sydney), do [[Soaring|Glider-towing]], ask for on-line support during flight or just ask somebody flying a plane of interest about specifics.
* Or just sit in a cockpit in Germany while sightseeing San Francisco in a [[Cessna C172|C172]], voice-chat with a Texan in a plane I dreamed of as a boy ([[Lockheed Constellation|Super Constellation]]) and both getting information from a New Zealand guy (it shall be a wonderful island – but do real people live there? He said: Yes!!).
* And much more!

You can even use it in models without radios - just use the standard FlightGear [[menu]] (<tt>Equipment > Radio Settings</tt>).

In the future FGCom surely will extend further and surely will get a “Speech to Text” capability in order to also integrate the text-based automated ATC-routines inside FlightGear.

== The Client installation ==
=== Prequisites ===
==== Hardware Requirements ====
If you are satisfied with the operation and responsetimes of your current FlightGear installation, then you should see no significant difference after adding the FGCom. If your FlightGear installation runs already a little marginal, then you might experience some delays when many new airplane-models etc. must be loaded. This may happen when starting up at a busy airport. You can monitor/verify such a "short-time overload" in the FlightGear command-window.

For details see the [http://www.flightgear.org/hardwarereq.html common hardware and driver requirements].

Of course you will also need a connection to the internet for this real-time, worldwide voice communication.

==== Software requirements ====
{| border="1"
|align="center" width="90px" |'''FlightGear''' ||The basic [[FlightGear]] Flight Simulation installation. This must be installed prior to installing FGCom ''(except if installing the Linux "Git complete" version which can install FGCom and FlightGear concurrently)''.
|-
|align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of FGFS. As the name says, it enables communication of several players via a chat-function (until now per keyboard - now also with this vocal interface: FGCom).
|}

==== Nice to have ====
{| border="1"
|align="center" width="90px" | '''FGrun'''||This [[FlightGear Launch Control]] (also known as FG Wizard), is a graphical front end to start the FGFS. This makes it very easy to startup the FGFS with all it's possible options. In some newer distributions this is already part of the basic FGFS installation package
|-
|align="center" |'''MPMap'''||[[MPMap]] is a pure browser application based on Google Maps, so it does not need any installation, except a Web-Browser. With MPMap you can watch all Multiuser-planes worldwide on a road-map, satellite picture or a composite of both. It includes most of the airports, navigational aids, and current weather information. So it can be used for preflight planning, without having the FGFS started or even installed. But it needs a constant connection to the internet - on the other hand you can do your preflight planning anywhere where there is a PC, connected to the internet.
|-
|align="center" |'''Runwayfinder'''||[http://www.runwayfinder.com This standalone Browser-Application] does present a fantastic Fight-Planning tool, showing similar aspects like the "MPMap" but adds an Aeronatical map. It does not link to FGFS, MPMap or Multiplayer -- and covers only the domestic USA.
|-
|align="center" |'''Atlas'''||[[Atlas]] displays the current position of your airplane on an landscape type of map together with navigational information. It derives its data direct out of the installed FGFS databases. So you do not need any connections to the internet.
|-
|align="center" |'''Festival'''||[http://www.flightgear.org/Docs/getstart/getstartch5.html#x10-1080005.7 Festival] is a TTS (Text To Speech) system that can convert all in the FGFS displayed written text (ATC, Chat, etc.) into speech and put it on your loudspeakers.
|}

=== Installing FGCom ===
==== Install on Linux ====
For Linux-Systems there are three ways to install:

# '''Downloading from the “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).'''
#* '''Advantage:''' This is the easiest way and ensures that maintenance and services for this package and all concurrencies to it are provided automatically for a reasonable time-frame.
#* '''Disadvantage:''' The availability of those packages is usually very late and most Distributors do not cover all FGFS-features. To our knowledge none of the Distributors has an FGCom package available as of March 2009.
#* '''Installation:''' Follow the usual procedures of your distributer on how to install additional packages.
# '''Installing a “Git complete”'''
#* '''Advantage:''' It is the very easiest form of installation and installs in one step all prerequisite/companion modules (FGFS, FGrun, FGcom, PLIB, OSG, Simgear, AT). Also it can be added and removed from the system without disturbing the rest of the system (Libraries, Menus, Structures, etc.). It was tested on several Ubuntu and Debian systems.
#* '''Disadvantage:''' No automated maintenance available. The handling is a little different from the standard Menu-driven practice.
#* '''Installation:''' [[Scripted Compilation on Linux Debian/Ubuntu]]
# '''Compiling it locally:'''
#* '''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.
#* '''Disadvantage:''' No automated maintenance available. Also the user should have some basic knowledge of his system and its devices.
#* '''Installation:''' [http://code.google.com/p/fgcomgui/wiki/Linux_Installation instructions]

Then continue with testing on [[FGCOM Testing]].

==== Install on Mac ====

'''MacFlightGear 1.9.1/2.0.0'''<br />
You can download the "MacFlightGear"-Application from the [http://www.flightgear.org/Downloads/binary.shtml#mac FlightGear download-center]. The current version 2.0.0 of the code does contain the FGCom and works for OSX >= 10.5. (with OSX versions < 10.5 you will end up with a generic "bus error" message).

==== Install on Windows ====
Please use the Windows installation description, available through [[FGCOM for Windows]].

=== Testing ===
During testing we will test/adjust:
# the basic FGCom functions without FlightGear
# FGCom together with FlightGear
# the microphone and loudspeaker system

For these tests please refer to [[FGCOM Testing]].

=== Functional test & user briefing ===
Experiences pointed out, that the cooperation between FGCom and FlightGear works more reliable, if FlightGear is started first. So we will start with setting up a flight-test-environment:

==== Start FlightGear ====
We suggest to use [[FGRun]] to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for FGCom-operation:

If you don't have an icon available to start FGrun, then start FlightGear manually:

# Start a [[Command line|command-window]]
# Change into the directory in which FGFS was installed
# Execute the following command or something similar
{|
! style="background:#efefef" | Linux
|fgrun
|-
! style="background:#efefef" | Linux Git:
|cd ~/fgfs<br />sh ./run_fgrun.sh
|-
! style="background:#efefef" | Windows
|C:<br />cd 'C:\Program Files\Flightgear\win32'<br />fgrun.exe
|}

Wait for the program window to start and then define:

# Start by '''choosing an airplane'''. For this first try we suggest the [[Cessna C172]]P, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]].<br />→ Click "Next".
# As '''starting place''' please define the [[airport]] KPAO (Palo Alto) runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br />→ Click "Next".[[File:FGrun_base.jpg|thumb|Basic & multiplayer options]]
# Define the '''Multiplayer options:''' (see [[Howto: Multiplayer]] for details).
#* “AI models” must be activated in order to see all traffic
#* “Multiplayer” must be activated
#* type “'''mpserverXX.flightgear.org'''” into the field “Hostname:”, replace “XX” with the server number nearest you - select it in http://pigeond.net/flightgear/mpstatus/. Actually it does not matter which server you take (as long as it is online and not as overcrowded as mpserver02) - you might try which server gives you the best response-times.
#* Insert your “Callsign:” (max. 7 characters)
#* define the “in” and “out” ports both with the standard “5000”
#* With "Load/Save as" you may build up yourself a library of settings for different airports.<br />→ Click "Advanced".[[File:FGrun_IP.jpg|thumb|Advanced: Initial Position]]
# In the “'''Advanced Options'''” check the following sections (click/select them in the left column):
#* General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
#* Features: “AI Traffic” should be activated already
#* Initial Position: You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''
#** ''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.[[File:MPmap.jpg|thumb|[[MPMap]]]]
# Open the '''[http://mpmap01.flightgear.org MPMap]'''
#* if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
#* click on “nav”
#* disable all options except “apt code”
#* type “KPAO” into the filed “Navaids lookup”
#* hit ENTER or click onto the reading-glass symbol
#* click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”
#* now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”
#* then zoom into the airport
#* set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen
#* type those long/lat values into the field below and also the wanted heading of the plane while parking[[File:FGrun_net.jpg|thumb|Advanced: Network]]
# '''Network:''' Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.
#* WARNING: When saving these settings and reloading them again, FGRun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".
#* If you need to '''define the unique IP-Address''', open a [[Command line|command-window]] and type

{|
! style="background:#efefef" | OS
! style="background:#efefef" | to type
! style="background:#efefef" | cap.
! style="background:#efefef" | returned values
|-
! style="background:#efefef" | Linux
|ifconfig
|eth0
|Link encap:Ethernet HWaddr 00:1d:92:80:a6:ab<br />inet addr:'''192.168.178.23''' Bcast:192.168.178.255 Mask:255.255.255.0
|-
! style="background:#efefef" | Windows
|ipconfig /all
|et
|Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF
<br />DHCP aktiviert. . . . . . . . . . : Ja
<br />Autokonfiguration aktiviert . . . : Ja
<br />IP-Adresse. . . . . . . . . . . . : '''192.168.178.20'''
<br />Subnetzmaske. . . . . . . . . . . : 255.255.255.0
<br />IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
|}
#* '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!![[File:FGrun_IO.jpg|thumb|Advanced: Input/Output]]
# '''Input/Output:'''
#* You do need a "generic" line as shown, because '''this defines the interface between FlightGear and FGCom'''.
#** To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown.
#** Editing an existing line: Start by clicking onto the existing one, then change as required.
#** Deleting an existing line: Click onto the line to be deleted, then hit "Delete"
# '''Avionics:''' let us define:
{|
! style="background:#efefef" | Nav1:
| 114.10
| San Jose VOR
|-
! style="background:#efefef" | Nav2:
| 115.80
| SF VOR
|-
! style="background:#efefef" | ADF:
| 379
| Brijj, beacon at SF
|}
#* And activate DME to Nav1
#* There is no field to input COM-radios, but remember them for setting them later manually:
{|
! style="background:#efefef" | Com1
| 118.60
| Paolo Alto
|-
! style="background:#efefef" | Com2
| 120.50
| San Francisco
|}

# '''Properties:'''
#* Here you can define any presetting for any values in the FGFS. See e.g.: <tt>File > Browse Internal Properties</tt> in the FlightGear [[menu]].[[File:FGrun_prop.jpg|thumb|Advanced: Properties]]
#* I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
#** Input a new line: Just hit “New” and type your string.
#** Edit a line: Be sure first to click onto an existing item and then edit this “Property”
#** Delete a line: Click onto the line to be deleted then hit "Delete"
# Hit “OK” → “Run” and watch FlightGear starting. If screen-place allows you may want to pull the shown "FGFS Report-Window" to the side and watch how busy your PC is while loading the other multi-player models.

==== Start FGCom ====
Open a [[Command line|command-window]] and change into the directory in which FGCom was installed (probably the same as FlightGear) and start FGCom. Do not use any other options than the server address “-Sfgcom.flightgear.org.uk”:
{|
! style="background:#efefef" |Linux
|fgcom -Sfgcom.flightgear.org.uk
|"-Sfgcom..." with capital "S"
|-
! style="background:#efefef" |Linux Git
| cd ~/fgfs<br />sh ./run_fgcom.sh
| for this “Git complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
! style="background:#efefef" |Windows
|cd 'C:\Program Files\Flightgear\win32'<br />fgcom.exe -Sfgcom.flightgear.org.uk
|"-Sfgcom..." with capital "S"
|}
For the following test position this command-window somewhere, where you can monitor it throughout the test.

The first response should be:
/fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 206M
Using iaxclient library Version SVN 206M

Successfully parsed command-line options.
Reading list of airports...done.
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
If your printout up to that line is different go back to chapter [[FGCOM#Test the basic function|Test the basic function]]

{|
|+
|-
|width="300"| ||
|-
|1) If, due to a prior flight, COM1 was set to anything else but 118.600 (e.g. to 119.650) you will see the following 2 lines added to the initialization of the FGCom-window: ||
|-
|
Selected frequency: 119.650
Call rejected by remote
|
Instead of “119.650” there will be shown the last used frequency. In this case the source of the nearest ATC-Freq. 119.650 is more than 50km away from your actual position of the airplane, so FGCom rejects a connection to it. If the last frequency used would have been within 50 km you get an indication very similar to the next item.
|-
|2) Switch COM1 to 118.60 (needed at Palo Alto):
|-
|
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
|This last line will be repeated according the to time span you defined in the “Input/Output” command “--generic=socket,in,'''10''',,5500,tcp”, you may change that value later according to your preferences.
|-
|<br />3) Press your PTT (PushToTalk on space-bar and joystick, as available):
|-
|
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.
|-
|<br />Now lets set/verify the other Radios:
* COM2 = 120.50 San Francisco
* NAV1 = 114.10 San Jose
* NAV2 = 115.80 San Francisco
4) Pressing Upper+Space will switch to the next radio: '''NAV1'''
|-
|
Radio-Select: NAV1
Selected frequency: 114.100
Hanging up call 0
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|Compare this to the NAV2 indication 2 steps later: something is wrong – and it wasn't your fault: Although this NAV is valid (see ...FGFS/data/Airports/apt.dat.gz), it is missing in the FGCom listing .../FGCom/positions.txt. I encountered this problem several times, as well for Airports as also for VOR's. If this happens with your most beloved airport you can add those missing data with a text-editor. But before changing be sure to save the original data somewhere - just in case!
|-
|<br />5) Pressing Upper+Space once more switches to '''COM2'''
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km)
[LISTEN] mute mic, unmute speaker
Call 0 accepted
Call 0 answered
|That looks OK: San Francisco is about 29 km away<br /><br />watch the “km” instead of miles!<br />'''10 km''' = '''6.2137 mi'''
|-
|<br />6) Pressing Upper+Space once more switches to '''NAV2'''
|-
|
Radio-Select: NAV2
Selected frequency: 115.800
Hanging up call 0
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|And Yes: The SF VOR is just a little closer than the airport(center)
|-
|<br />7) Pressing Upper+Space once more brings back '''COM1''':
|-
|
Radio-Select: COM1
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|-
|<br />8) Lets us start and continue flying in the direction about 130°:
|-
|
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km)
|notice that you first come closer (to the center of the airport) and after that getting away
|-
|<br />9) Let's switch to '''COM2''' (San Francisco) and watch:
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km)
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km)
..
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km)
Hanging up call 0
Radio-Select: NAV2
Selected frequency: 115.800
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|That means: at about 50KM we are getting out of range and thus the on COM2 active SF getts terminated. Notice that also the inactive NAV2 gets terminated, because it exceeded the allowable range at about the same time!
|}
10) You could turn now and watch the opposite: At about the same distance those two will become active again (automatically, if you did not change the settings).

If you got here without any (technical) problems your FGCom is fully functional. Have fun when using it.

=== Using FGCom ===
There are basically three types of FGCom-usage:
* '''Normal usage at airports:''' i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through the "'" (UpperCase#) and/or the Chat-Menus). In addition you then can talk to anybody in a radius of about 50 km (about 30 miles) around the airport, may that be friends, a maintained FGCOM-ATC/Twr-Operator, airport utilities, etc.. Be aware that as of April 2009 only very few planes are using the FGCOM for ATC-purposes - thus you should always use the ATC-Chat "keyboard"-procedures to announce arrivals/departures/taxiing etc. in addition. (We hope that may change in some future!)
* The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - and not yet "overcrowded!). Also when traveling you might want to listen on the 122.75 for others who want to contact you (or reverse). When there is much "talk" on the 122.75 you might just arrange with your partner to switch to 123.45 - and return to 122.75 afterward. As of April 2009 the 122.75 is already operational for this application, the 123.45 will follow soon. You may try from time to time if this limitations still exist.
* Finally you can manipulate the frequency-tables (positions.txt in your FGFS/FGCOM local directory) and '''define an own frequency for special events'''. e.g. a Flight-School at one airport with maybe multiple student-groups. Of course those are local manipulations on your own PC, which you have to agree on with your (planned to be) partners in advance.

=== Supplemantery Information ===
==== Tips and Tricks ====
===== Airport missing in FGCom: =====
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line
KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
You can add extra lines for any locations you want. e.g.: (watch the separation comas)
apt-code = DUMY (a "dummy" or your favorite, but missing, airport code)
KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz”
or just take one of which you are sure that you do not need it in the FGFS-reality
(notice that several Airports (far apart) use same frequencies!
long/lat = take out of the Mpmap (or Google Map)
type = whatever
name = whatever
''(of course those definition are only known to your own PC and last only until the next data update!)''

===== Editing FGCOM-Data-Files =====
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
* For windows you can use "WordPad"
* For Linux the "gedit" works fine

===== Copying-Printing this WIKI-Page''' =====
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:

* to copy:
** select in the Browser-Menu: "File" --> "Save Page as.. "
* to print:
** go to the [http://wiki.flightgear.org/index.php?title=FGCOM&printable=yes printable version].
** Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"
** before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages!
** If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer

===== Joystick compatibility between Operating Systems: =====
{{Main article|Joystick}}

You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"):
<axis> (instead of the usual <axis n=”3”> )
<desc>Mixture</desc>
<number>
<unix>3</unix>
<mac>5</mac>
<windows>5</windows>
</number>
<binding>
<command>nasal</command>
<script>controls.mixtureAxis()</script>
</binding>
</axis>

===== Assign PTT to joystick =====
If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)
<button n="x">
<desc>PTT - Push To Talk</desc>
<binding>
<command>nasal</command>
<script>controls.ptt(1)</script>
</binding>
<mod-up>
<binding>
<command>nasal</command>
<script>controls.ptt(0)</script>
</binding>
</mod-up>
</button>

==== Helpful internet adresses ====
'''World-Time:'''
* [http://www.timeanddate.com/worldclock/custom.html?sort=1 standard deviations]
* [http://www.timezoneconverter.com/cgi-bin/tzc.tzc direct conversions]

Especially for multiplayer events you should define all times in the internationally used GMT (Greenwich Meantime). Just pick up your deviation from GMT and memorize it. If everybody does it, we could avoid a lot of misunderstandings.

* '''Decimal to Degree''' http://www.hbnweb.de/mathematik/grad-dezimal.html <br />
*: Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it.<br /><br />
* '''Miles, km, feet, etc. etc. ...''': http://www.convertunits.com/
*: If like to avoid troubles (like NASA lost a satellite because of it) just look it up.

'''Ports needed'''

In case of problems over the internet you might check that the the following ports are allowed:
1314 TCP if the Festival-Server is used for Text/Sound
2005 UDP Vcp-Stream
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer (VPN Sftw.)
5001 UDP Enable HTTP-server
5002 UDP Enable property server
5003 UDP Enable Screen-Shot services
5004 UDP (may be used as a spare)
5505 UDP Terra Sync
16661 UDP FGCom listening to FGFS, usually “local host” only
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).

==== Commandline Parameters ====
fgcom --help
returns the following useful info
fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 163M
Using iaxclient library Version SVN 163M

OPTION DESCRIPTION

-d, -debug, --debug= show debugging information
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')
-s, -fgserver, --fgserver= network device to connect to (default: 'localhost')
-p, -port, --port= where we should listen to FG (default: '16661')
-a, -airport, --airport= airport-id (ICAO) for ATC-mode
-f, -frequency, --frequency= frequency for ATC-mode
-U, -user, --user= username for VoIP account (default: 'guest')
-P, -password, --password= password for VoIP account (default: 'guest')
-i, -mic, --mic= mic input level (0.0 - 1.0)
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)
-b, -mic-boost, --mic-boost= enable mic boost
-l, -list-audio, --list-audio= list audio devices
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')

Available codecs:
u - ulaw (default and best codec because the mixing is based onto ulaw)
a - alaw
g - gsm
s - speex
7 - G.723

Mode 1: client for COM1 of flightgear:
$ fgcom
- connects fgcom to fgfs at localhost:16661
$ fgcom -sother.host.tld -p23456
- connects fgcom to fgfs at other.host.tld:23456

Mode 2: client for an ATC at <airport> on <frequency>:
$ fgcom -aKSFO -f120.500
- sets up fgcom for an ATC radio at KSFO 120.500 MHz

Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!

Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''

== Server installation ==
{{Main article|Howto: Set up a FGCom server}}

== External links ==
* [http://sourceforge.net/projects/fgcom/ fgcom(SourceForge-Project)] Subversion is [http://fgcom.svn.sourceforge.net/ available here]. If you haven't used Subversion before, you might find it easier to fetch a [http://fgcom.svn.sourceforge.net/viewvc/fgcom/?view=tar archive] instead.
* latest source available here (?): http://code.google.com/p/fgcomgui/

=== Deprecated or broken links ===
* [http://squonk.abacab.org/dokuwiki/fgcom Old Official website]
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]

== Status ==
* '''March, 2009:'''
Adding User-Information for installing, using, maintaining FGCOM on different platforms.

* '''18 November, 2008:'''
Latest SVN (rev 163) has the compile problems fixed. Also we have a '''new server: fgcom.flightgear.org.uk'''. User accounts not required (ie. do '''not''' use -U or -P)
* '''31 October, 2008:'''

The latest SVN release at this time is the '''r149''' which does not compile due to a constant that is not defined (STL_STRING). Such constant appears at line 57 in the file ''src/fgcom_init.cpp'' which is:
''#include STL_STRING''

I guess that such constant must point to the STL library include file but I am not sure.
I revert to the '''r148''' SVN version which successfully compiles.

Command to get such version is: ''svn co -r148 svn://svn.dfn.de:/fgcom/trunk fgcom-r148''

* '''19 June, 2008:''' Currently the server is <u>down</u> due to hardware problems. It is unknown when the service comes back because he currently has no time to fix the problems.

* '''22 November 2007:''' Due to heavy development at this time there may be some differences between the information on the web pages and the installation. Please follow the discussions on the FlightGear development list!

== Related content ==
* [[FlightGear related projects]]
* [[FGComGui]]

[[Category:Software]]

FlightGear Newsletter April 2011

2011-04-19T14:53:21Z

Gorilla: Misconception is one word!

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== Atmospheric scattering shader ===
Zan has been working very hard on an experimental atmospheric scattering [[shader]]. The shaders makes use of [http://sponeil.net/ Sean O'Neil's algorithm]. Altough there are some issues with the shader, it looks like it will have a promising future!

==== Doctor Who Fans ====
[[Image:TARDIS.png|thumb|Doctor Who TARDIS]]
Vinura has started work on developing a [http://en.wikipedia.org/wiki/TARDIS#The_Doctor.27s_TARDIS Doctor Who TARDIS] for FlightGear. The exterior model is almost complete in SketchUp.

== Nasal for newbies ==
== New software tools and projects ==

== FlightGear addons and mods ==
== In the hangar ==
=== New instruments ===
The [[Boeing 777-200ER]]'s chronometer has been moved to the generic instruments directory (<tt>Aircraft/Instruments-3d/chronometer</tt>). This allows aircraft developers to easily implement this clock in their aircraft. All related Nasal code was included in the model xml file, so there's really just one file to be linked to! Some aircraft already make use of this clock, including the [[Boeing 747-400]] and [[Boeing 757-200|757-200]].

There are several advantages in moving instruments to the generic directoy, some of which are:
* Easy to be re-used in other aircraft, all you need to do is link to (and position) the model and on some instruments link to a Nasal file.
* If someone extents the functionality of a generic instrument, it will be automatically extended in all the aircraft that use it.

=== New aircraft ===
=== Updated aircraft ===
=== Liveries ===
[[Image:Fgfs-screen-072.png|thumb|Airbus A320]]
[[Image:Fgfs-screen-089.png|thumb|Boeing 767]]
Some [http://liveries.flightgear.org/airlines.php?id=231 SriLankan Airlines] liveries have been made by Vinura for the Boeing 767 and Airbus A320.

== Scenery corner ==

=== New scenery ===
New third-party scenery for the USA's Pacific Northwest (Seattle and Portland, OR) and Rio de Janeiro is now available for download at http://www.stattosoftware.com/flightgear

=== New Buildings ===
Once again, there are new Eastern Asian buildings !

* Saigon Center - Ho Chi Minh City - Vietnam
* Mode Gakuen Coccoon Tower - Tokyo - Japan
* Trade Tower - Seoul - South Korea
* Koryo Hotel - Pyongyang - North Korea
* The Center - Hong Kong - China
* Central Plaza - Hong Kong - China

=== Airports ===
The generic Concourse C at KDEN was recently replaced with a much better, realistic working model featuring animated jetways. Please enjoy.

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==
SriLankan Airlines livery on an Airbus A320 taken at dusk.

[[File:Fgfs-screen-085.png|600px]]

== Suggested flights ==
Departing from Brisbane International Airport and heading towards Sydney International Airport at a heading of about 203, you will come across some beautiful scenery.
<gallery>
Image:Fgfs-screen-020.png
Image:Fgfs-screen-016.png
Image:Fgfs-screen-012.png
</gallery>

== Aircraft reviews ==

=== '''''The Good old Cessna Citation X''''' ===
I hope to do a monthly review of a specific aircraft. I can't guarantee that I will get to do it every month though because I do have other stuff to attend to.

The [[Cessna Citation X]] is by far one of my favourite little planes! Its reaction time is quite quick. The rudder control is very responsive, even the slightest move of your rudder pedals or the mouse and the aircraft's rudder moves. It accelerates quite fast down the runway, building up momentum and then, you lift your joystick up slightly and the nose lifts up just like you want it to.

Regarding the animations, they are extraordinary. They function quite well like for example the flaps, spoilers or the landing gear. The cockpit is quite well designed and has a lot of instruments, just like a real Citation would.

It has a tutorial system built in for people wanting to fly one. '''''This was the first jet plane that I could actually land properly in.''''' It also has several nice camera views, including views from the passenger seats.

<gallery>
Image:Cessna Citation X Cockpit.png
Image:Cessna Citation X Passenger View 1.png
Image:Cessna Citation X Passenger View 2.png
Image:Cessna Citation X - Screenshot 2.png
</gallery>

'''Recommendation:'''

I would recommend this plane to people who have already flown planes like the [[Cessna C172P]] or the [[Piper J3 Cub]] and want to progress into Jet aviation. This is a GREAT little starter plane to get you going.

This has to be one of the best planes that I have ever used in FlightGear!

Thanks for reading! :D

'''''Review By: Vinura'''''

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on youtube ===

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===
==== FlyingClub Mayday 1 ====
The FGFC '''"Mayday 1: Manitoba Rescue"''' operation was held April 2nd, 2011 at CYAV, Winnipeg/St.Andrews, with seven pilots participating. The scenario stated two of Manitoba's major rivers were flooding, and people were stranded along both, so STOL and helicopter pilots were mustered at CYAV, received assignments from ATC, planned their flights, and notified ATC when they were ready to proceed. A total of twenty missions were assigned, sixteen of which were successfully completed in the space of three hours.

The scenario was based around the idea that pilots should have basic skills in addition to merely flying with an autopilot, and was designed to test both their actual flying ability by not having airports at their destinations, and providing no actual navigational data beyond a map or two. They were required to map their routes in territory unknown to them, then fly those routes in their chosen aircraft, land, report in, then return to CYAV to complete a "cycle." Points were awarded for cycle completion, and points deducted for aircraft crashes. FG Seg faults were not penalized.

Comments back about the operation from pilots have so far been positive. Watch the [http://www.flightgear.org/forums/viewforum.php?f=10&sid=381d9860a9183d143cd2fa8aee16099d Multiplayer Forums] for the next one; there will be one, but at this writing, it has not yet been decided.

* [[FlightGear Flying Club]]
* [http://flightgearfans.wordpress.com/about/ FGFC WordPress Site ]
* [http://www.flightgear.org/forums/viewtopic.php?f=10&t=11551 Mayday 1 Forum Pages]

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common misconception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
*...that you can fly backwards in a UFO? While holding the brake button down on your joystick or keyboard, increase engine throttle and you should start to fly backwards. A video is to be seen at [http://www.youtube.com/watch?v=F7U1bsO7g-EYouTube]

[[Category:FlightGear Newsletter|2011 04]]

FGCOM Testing

2010-09-19T02:41:27Z

Gorilla: /* Error: "TYPO" (mistyped command or option) or Network-problem: */

This "FGCOM_Testing" is intended to support FGCOM-users in debugging their FGCOM-System directly after installation, but also for those who want to verify the basic functionality or want to readjust the audio-system. It covers the following 4 areas in more detail:
#Testing of the standalone FGCOM Installation
#Testing the FGCOM together with the FlighGear Simulator
#Adjusting the Microphone and Speaker volumes</ol>
#In the [[#Appendix|Appendix]] you will find supporting informations

Of course the prerequisite for the following is that you have already installed the FGCOM (see the [[FGCOM|FGCOM-main-page]]) !
<br><br>

== '''The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"''' ==

Prior to executing the following [[Command line|command]] open a command-window and change into the directory, into which the FGCom was installed. This path will then be shown shown in the command window, followed by a "$"-sign. Enter the following "fgcom"-command with the required/wanted options:

<pre>fgcom -Sfgcom.flightgear.org.uk -f910</pre>

: ''fgcom''
:: the command ''(in case you installed by using the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|download_and_compile.sh script]] for LINUX-Systems you have to replace the command "fgcom" with "sh ./run_fgcom.sh". Then the complete command would be: "'''sh ./run_fgcom.sh -f910'''")''
: ''-Sfgcom.flightgear.org.uk''
:: the central server for FGCOM
: ''-f910''
:: the only available frequency for echo-tests
: optional
:: In case your audiosystem is rather weak, you may try the options:
:: ''-i and/or -o'': i=input(microphone) o=output(Speaker), both values between 0.0 and 1.0 (e.g.: -i0.9)

You do not need any Login-Passwords and/or User-Names !!!

For a detailed description of all available options see [[FGCOM#Commandline Parameters|Commandline Parameters]] - in the following we will only show the minimal required options:
<pre>That should give you the following return:
fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 163M
Using iaxclient library Version SVN 163M

Successfully parsed commandline options.
Reading list of airports...done.
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
Call 0 accepted
Call 0 answered
</pre>

Speak into your microphone and your words should be echoed back with a short delay. e.g. say "one" - and you should notice that the "one" is returned '''after''' you finished speaking it.
<br>'''If that was OK'''
*type <nowiki>ctrl-C</nowiki> to exit this Quick-Test command-window
*and continue with the next chapter: [[#Test the FGCOM together with the FlighGear Simulator|Test the FGCOM together with the FlighGear Simulator]].
<br>'''In case of trouble''' check the following most probable errors:

<br>
===Error: FGCOM does not start because of OpenAL-version:===
If you see a message from the Operating-System similar to the following Windows message:
"The procedure entry point alcCaptureSamples could not be located in the dynamic link libary Open AL32.dll."
Then download and install the latest OpenAL software from: http://connect.creativelabs.com/openal/Downloads/Forms/AllItems.aspx
: for windows: '''alinst.zip'''
: for Linux: '''openal-soft-1.10.622'''
: for OSX: '''OpenALInstaller'''
''Be aware that the versions and also the names of the modules may change -- so please always check also the description of the module at the right side on that http-page!''

<br>
===Error: Incorrect Home-Directory specified for FGCOM:===

typical for '''Windows'''-Systems:
<pre>
C:\Users\localuser>cd \Programme\Fxx
The System cannot find the given path.

C:\Users\emmerich>fgcom.exe -Sfgcom.flightgear.org.uk -f910
The command "fgcom.exe" is either mistyped or could not be found.
</pre>

typical for '''Linux'''-Systems:
<pre>
/home/emmerich/Desktop/Link to fgcom: line 1: cd: /home/emmerich/fgf: No such file or directory
sh: Can't open run_fgcom.sh
</pre>

*The system is right: I gave it (for testing) a wrong directory!
*You better correct yours prior to retrying!

===Error: "TYPO" (mistyped command or option) or Network-problem:===
<pre>
./fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 223M
Using iaxclient library Version SVN 223M

Successfully parsed command-line options.
Reading list of airports...done.
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
</pre>
after some time there may appear:

<pre>
''' Call 0 timed out.'''
'''Timeout for a non-existent session. Dropping'''

</pre>
or
<pre>
'''Call 0 accepted'''
'''Call 0 answered'''
'''The service is unavailable. Please wait until fgcom Version 3 is online. Thank you.'''
</pre>
most likely you may have

*defined a wrong Frequency to use or you may have forgotten to define one. You '''must define the option -f910'''
*forgotten a "-"sign in front of an option
*typed a small "-sfgcom..." instead the capital "-Sfgcom..."
*mistyped the Server-Name or defined a wrong FGCOM-Server
*or you may have created your own unique "typo" (lol).
*or it may indicate a '''Network-Problem''':
**Check your network by using some other application (e.g. your file browser to look up an usually not used http-address - if you use a recently used address the answer might be out of your locally saved copies - even so the network is not connected! (e.g. use "http://mainz.de/" to test)
*If you use a firewall (what you should - out of general safety reasons!) make sure the ports below are enabled for your PC.

<pre>
2005 UDP Vcp-Stream
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer (VPN Sftw.)
16661 UDP FGCom listening to FGFS, usually on localhost only
</pre>

===Error: "Phone-book" and/or "positions" cannot be found and/or are corrupted:===
<pre>
./fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 223M
Using iaxclient library Version SVN 223M

Successfully parsed commandline options.
'''Reading list of airports...Cannot open /home/emmerich/fgfs/install/fgcom/fgcom/positions.txt'''
'''fopen: No such file or directory'''
'''Stopping service.'''
(etc)
</pre>
*check the directory in which the FGCOM is installed for the files "phonebook.txt" and "positions.txt". These are normal text-files in which you can add missing informations with a standard editor, for Windows you should use the "WordPad" (not the "Editor"). Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added.

===Error: The Sound-Card is not fully compatible:===
<pre>
./fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 223M
Using iaxclient library Version SVN 223M

'''AL lib: alsa.c:564: set access failed: Invalid argument'''
Successfully parsed commandline options.
Reading list of airports...done.
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
Call 0 accepted
Call 0 answered
</pre>
*Continue checking/adjusting:
**If everything else works out OK forget this problem (but be aware: The Audio might not function perfectly!)
**otherwise check the Internet for new drivers for your sound-card or other fixes.

<br>

== Test the FGCOM together with the FlighGear Simulator ==

In the forgoing chapter you checked the FGCOM as a standalone application. Now we will test whether the '''FGFS''' (FlighGear Flight-Simulator) itself and the FGCOM work together, inclusive the PTT-button (PushToTalk, usually the space-bar) and the internal connections via the assigned ports.
<br>
For this test
<ol><li>start the FGFS with any plane at any airport you like
<li>start the FGCOM (usually it does not matter which one starts first - but in case of trouble you should try to start in this sequence!)</li>

<li>click in the FGFS menu-bar onto "Equipment" --> "Radio Settings"
*into the field "COM1" enter the frequency "910.00" then click "Apply" (and "OK" if you want to close the Pop-up.)
* '''Ensure the FGFS is the active window''': if something does not work out as expected click with the mouse somewhere into the Main-FGFS-window (that will activate the window) and then retry the last action(s)!!!

<li>if the FGCom Command-window initiates, but does not respond to any COMM-Frequency setting:
: This indicates a pure Port/Interface problem between the FGCOM and the FGFS.
:: Try to enforce (the usually predefined) port as option. i.e. add the option “-p16661” to the FGCom Start-Command
:: check the FGrun extended Options → Input/output “generic=socket..”: The port there must be the same as for the FGCom, i.e. 16661 (if it was not intentionally changed by you)
:You may try to change the interface-port to e.g. UPD 5004. In this case you have to watch 3 places:
::add the option “-p5004” to the FGCom start-command
::also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004 '''or''' add the option "--generic=socket,out,10,localhost,5004,udp,fgcom" to your FGFS start-command.
::and you may have to tell your Firewall to allow port UDP 5004
:anyhow make sure all these 3 places contain the same Port-number !!!

<br>
<li>Push the PTT ''(normally the Space-Bar (if you reassigned the PTT to another key - use that one!))'' and speak into your microphone:
"your words should be echoed back with a short delay. e.g. say "one" - and you should notice that the "one" is returned after you finished speaking it.
::'''if you heard''' that echo:
::keeping the PTT pressed for about 3 sec and watch for a possible start of "funny noises".
:::if those occur continue with chapter [[#Adjust the Microphone and Speaker volumes|Adjust the Microphone and Speaker volumes]]
:::otherwise switch your COM1 back to the frequency wanted --> continue with the next numbered item.
::'''if you did not hear''' the echoed return
:::Test your PTT: Watch the FGCOM messages in the FGCOM-Window:
:::When pushing the PTT they should switch between ''[SPEAK] unmute mic'' followed by ''[LISTEN] mute mic''
:::If they did not switch you probably use an airplane model that has reassigned the Space-bar to another function:
:: Otherwise check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line ''<key n="32">'' then this plane is intentionally using "key 32" (Space) for something other than the PTT. Known planes that do that as of Feb. 2009 are: an2, bluebird-base, ogel, OV10.., seafireIIc, spitfireIIa, ufo. There could be others.

<br><br>

== Adjust the Microphone and Speaker volumes ==

Finally we will adjust the Microphone and Loudspeaker volumes to an optimum, as well for yourself as also for your fellow players.
<br>''(You could perform this test also with the "f910-test" in chapter 1, but with the test-setup in chapter 2 it becomes more realistic!)''

# Start your FGFS and FGCOM as described in the forgoing chapter(s), the COM1 must be switched to 910.00 and be the active one.
# Talk into your Microphone and verify the delayed feedback. If this does not function as described before, repeat the forgoing chapters.
# While talking into the microphone adjust your loudspeaker so that your echoed voice is understandable, but not any louder than required.
# Now '''adjust your microphone''' volume from 0 to full. Somewhere in between you will find a spot at which the returned echo-volume will not increase according to the microphone-volume changes. Leave the volume just a little below that point.
# After the microphone is set, '''adjust the loudspeaker''' volume to a level you prefer.
# Finally verify both settings by keeping the PTT pressed for about 10 seconds without talking and/or feeding any other sounds into the microphone.
#*listen for "funny noises" building up over time (hard to describe: some "unverified whoosh" and maybe additional even some sound like "air in a water-pipe" - actually: Whenever you hear anything --> it is no good!!!.
#*Mostly these "build up sounds with time" are due to an active microphone booster. Try to keep that booster to an absolute minimum (even better try to switch it off completely if not really needed!) while instead increasing the microphone volume
#* but also a rather high adjusted speaker-volume may cause such "funny noises" - try reducing the loudspeaker volume if you cannot solve the problem by adjusting the microphone and/or booster.
#*then you might readjust as described in the forgoing items.
#Now you are ready to talk to others, e.g. set your COM1 to the desired frequency and let your co-players praise you for that "absolute brilliant voice you have"!
<br />

By the way: You do not have to wait for the next MP-event to check this real life: When flying next time, look into your pilots-list (FGFS-menu-bar --> Network --> Pilot List) and try to contact one of those pilots (or pilotesses) listed there via MPchat (FGFS-menu-bar --> network --> Chat) - via this chat you then can define what frequency to use - to be sure you tune to the same. In general all of those having FGCOM operational will gladly help you testing! You may have to look in [[MPMap|MPmap]] first to find where there are some people - because you need a distance less than 100 nm to get into contact via MPchat.

PLEASE: While "on Air" in MP keep the PTT pressed only while actually talking - and never longer than about 20 sec. After some time you will be timed out anyhow - but even before that drastic cutoff you might give your co-players a chance to reply/say something!
<br><br>

== Appendix ==

=== Tips and Tricks ===
====Typical Problems====
<ol><li>Microphone not plugged or Mute-Key activated: It sounds stupid – but most technical problems are due to such “cannot bee”s – please: Always spend the 2 sec. to check this first! Also some Microphones do have an own "Mute-Key", which sometimes is not obviously to see - check your handbook if your Mic has such a switch.
</li><br><li>Plug/Jack connections are often the cause for trouble: Try to re-seat your plugs and (if possible) try to use another jack (after cleaning the plug!).
</li><br><li>Multiple Microphones and/or Loudspeakers plugged to your PC: Be aware that most PC's do have Jack-mechanisms that prevent more than one input and/or output per PC. Try using only one (at best the major one - mostly at the back of the PC)
</li><br><li>If you changed your Mic/Loudspeaker setup or did plug them into anther jack, it is advisable to restart your PC – just to make sure the system knows what you did! (For Windows-Systems this is usually not necessary - but: It cannot hurt to reassure!)
*If you use USB-headsets you might first try to get FGCOM running with standard Input/output devices – and go back to USB after that. If nothing else it helps to narrow down into the trouble-area!
</li><br><li>Check that none of your Sound-system Inputs/Outputs are set to “Mute”:
*For basic systems you might use a '''right''' mouse-click onto the loudspeaker-symbol in the upper or lower position of you screen.
**For WIndows-Systems: If that symbol is not there:
***'''for Vista''': Left mouse-click onto “Start”, type “SndVol.exe” into the line just above the Start-button
***'''for XP:''' Left mouse-click onto “Start” then on “Run”, type “SndVol32.exe” into the appearing input-field.
*For some “highly sophisticated (and expensive)” sound-cards you might need to use their unique descriptions.
*FGCOM does not require a “better” sound-card like e.g. for Music or so – it is all Telephone/TCP-IP talking only – (except some people I know like to play country-music while pushing the PTT – that sounds nice - but still is not really high fidelity!)
</li><br><li>Always make sure that you can record and playback something you talk into the microphone with your basic system tools, completely independent of the FlightGear and/or the “OpenAL”. (See your handbooks for testing your unique system and/or the chapter [[#Where to find the volume controls|Where to find the volume controls]])
</li><br><li>If the connection is noisy or poor quality:
*First retest your sound-setup as described [[#Adjust the Microphone and Speaker volumes|above]]
*try routing your Mic/Speaker cables away from electro-smog (Fans, AC/DC modules, motors, lamps, etc.)
*even placing your sound-card into another plug-position may help
*a (digital) USB-headset may help avoiding noise and feedback problems
*if stereomix is enabled on your sound-card - try to disable it
</li><br><li>Most PC's are set up that you need to keep your PTT (PushToTalk) button pushed as long as you talk. But there are also sound-cards which open for talk with the first push/release and close it with the second push/release. Test your system how it works (may be while trying to record something or while testing according to the [[Adjust the Microphone and Speaker volumes|above]]).
</li><br><li>If the FGFS sound-volume does not match your FGCOM-volume:
*After starting the FGFS click onto “File” in the FGFS menu-bar, then onto “Sound Configuration”: Adjust the upper slide-control to a proper volume. Be aware that this setting will get lost when you exit via “X” - always exit via “File” → “Exit/Quit”.
*To the opposite you may adjust the volume of your FGCOM by changing the “-o” and/or “-i” options to values between 0 and 1 (see the [[#The Initial test of the standalone FGCOM Installation --> the so called "-f910 Test"|FGOM command at the beginning of this wiki-page]]).
</li><br><li>It is known that the AirToAir frequency 123.45 does not yet work - reason unknown and fix-date unknown. (This affects all Operating Systems!)
</li><br><li>Did you know? If no Tower-frequency is in range, you also can use the VOR-frequencies - just put them into your COM1 or COM2.
</li></ol><br>
Try to keep in mind: FGCOM is proven to work! So if there are problems look also for surrounding PC-features like unique hardware, software, etc.
<br><br>

====High Quality Sound-Cards====
Especially “high quality” sound-cards may get you into trouble, because e.g.:
*they may monitor how long the microphone was not used and switch it off after some timespan (without you noticing it)
*during reboot or restart they may initiate with values out of a special profile instead of reusing the “last used” values
*or they may set some slide controls to “0” (especially microphone sliders)
*some do switch the microphone only after pushing '''and''' releasing the space-bar – while we want to change the microphone-status only while the space-bar is pushed down! (This may not affect a PTT asigned to a joystick)<br>
So know your standard settings and check if they have changed (without your written permission!)
<br><br>
====Special for Linux (.alsoftrc)====
(ref [[Linux software audio mixing with FlightGear]]) <br>
check your Home-directory (“~/”) for a file "'''.alsoftrc'''"
(remember that the “show hidden files” must be enabled!)
*if ".alsoftrc" does not exist
**Check if there is a (old version) ".openalrc"
***if yes: Check if you really use the old OpenAL library and not the newer OpenAL-soft library. If still have the old you put something like this in ".openalrc":
(define devices '(alsa))
(define alsa-out-device "plug:dmix")
**if not, create a new ".alsoftrc" file and insert something like the following into it:
format = AL_FORMAT_STEREO16
cf_level = 1
drivers = alsa
[alsa] # ALSA backend stuff
device = plug:dmix
capture = plug:dsnoop
The system wide OpenAL-soft configuration file may be /etc/openal/alsoft.conf or similar. It usually contains comments describing all possible configuration options.
<br><br>
====USB-Headsets-Problems with Linux (Ubuntu)====
The following is based/verified on Ubuntu, but should be similar on other distributions:
*If Recording is ok '''and''' the f910-Test looks alright in the window, '''but''' there is no delayed response:
**type "cat /proc/asound/modules" into the command window, e.g.:
$ cat /proc/asound/modules
0 snd_usb_audio
1 snd_hda_intel
**If that displays multiple devices (as shown in the above list, which is the result '''after''' doing the following!), then the USB-Headset should be in the "0" position. If this is not the case, notice the name of your USB-device and edit it. e.g.:
"sudo gedit /etc/modprobe.d/alsa-base.conf"
**add as last line into that file, e.g.:
options snd_usb_audio index=0
<br>
====Festival====
*If you use '''Festival''' (the Text/Speech AddOn)
**and
*** it works OK when running alone
*** but runs int error "can't open /dev/dsp" when running with FGFS (and/or other applications)
** then add a TextFile ".festivalrc" into your home-directory, containing:
(Parameter.set 'Audio_Command "aplay -q -c 1 -t raw -f s16 -r $SR $FILE")
(Parameter.set 'Audio_Method 'Audio_Command)
</ol><br><br>
=== Where to find the volume controls ===
Please be aware that FGCOM is used on many very different PC's, Notebooks, etc. under very different Operating-Systems and with very different Sound-Cards. So the following basic concepts may not fit your actual system 100%. In addition you may have to check your actual System and/or unique Sound-Card manuals!
<ol>

'''<li>Define the audio-devices to use:'''
{| border="1"
|+
|width=300 align="center"|'''for Linux:'''
|width=300 align="center"|'''for Windows:'''
|width=300 align="center"|'''for MAC:'''
|-
|width=300|Enter [[Command line|command]]: ''gnome-sound-properties''
[[image:FGCOM-U-Prefs.jpg|thumb|center|250px|test devices]]
For each task you can open a selection-menu (on the right the downward arrow) in order to select the wanted device. I suggest to first try setting all to "Autodetect". Then click onto the green "Test"-button. If you need to make changes, reboot the PC after each change!
|width=300|<br>Click right onto the audio-icon → Preferences → Audio-tab:
[[image:FGCOM-W-Audio.jpg|thumb|center|250px|set devices]]
See the two Tabs (in the picture) '''Audio''' and '''Stimme''' (voice), you need to change in both!
|width=300|Open with Menu --> System-preferences:
[[image:FGCOM-OVol.jpg|thumb|center|250px|set devices]]
Switch between "Output" and "Input" and select the wanted device('s) in the field "Chose a device...".
|}
If you did change these device-settings, it is a good idea to reboot the PC and retest the settings prior to continue.
<br><br>

'''<li>Adjust volumes and switch boosters''' (for the first loudspeaker-adjustments you should switch off the Mic.!)
{| border="1"
|-
|width=300|Click right on Audio-Icon → Open Vol. Ctrl:
[[image:FGCOM-UVolCtrl.jpg|thumb|center|250px|Volume Control]]
The amount of the slider-controls vary depending on the capabilities of the sound-card or the usage of USB-headsets.

The “booster” is available under “Switches” (you may have to activate it first under "Preferences").
|width=300|Click right on the Audio-Icon → Volume-Ctrl. (or type command: sndvol32)
[[image:FGCOM-W-VolCtrl.jpg|thumb|center|250px|set devices]]
In this example the card overrides the std. Microsoft “Mic.” with “Rear Pink In”. Be aware of such changes caused by usually “high expense” devices!
The “booster” is available under options.
|width=300|Use the above shown window to adjust.
|}
<br><br>

'''<li>Verify the basic Mic/Loudspeaker functionality:'''
<br>Use the volume-control-panels to enable the microphone for this test. Then:
{| border="1"
|-
|width=300|Open the recorder with the [[Command line|command]]: ''gnome-sound-recorder''
[[image:FGCOM-U-sndctrl.jpg|thumb|center|250px|Recording-test]]
*Record
*Stop
*Play
|width|Open the Recorder with [[Command line|command]]: ''sndrec32''
[[image:FGCOM-W-sndrec.jpg|thumb|center|250px|Recording-test]]
*Start recording (click red point)
*talk some words into the mic
*stop (rectangel)
*spool back ( < < )
*listen (>)
|width=300|There is no basic recording program available with OSX.
|}
[[de:FGCOM_Testing]]

Scripted Compilation on Linux Debian/Ubuntu

2010-07-13T16:16:08Z

Gorilla: /* Download */

==Description==
The following script takes care of downloading and compiling Flightgear from the git repositories with just one command execution for both 32-bit and 64-bit Debian based systems (Debian, Ubuntu). Pre-existing installed version (if any) of Flightgear are not touched at all since the script builds and installs everything under the directory in which it is launched.

Necessary packages are installed via the apt-get system while libraries not included in the repositories are downloaded and compiled on the fly (i.e. [[Plib]], [[Simgear]] and [[OSG]]).

===List of compiled programs===
The script is able to download and compile:
* Flightgear (And all the data needed to use it)
* [[Fgrun]]
* [[FGCOM]]
* [[Atlas]]
* [[Terrasync]]

==Download==
You can download the script here: [[http://brisa.homelinux.net/fgfs/download_and_compile.sh download_and_compile.sh]] [[http://wiki.flightgear.org/images/b/b7/Download_and_compile.sh Wiki Backup]]

The script is hosted on a home server, so if the electricity goes down or internet connection fails, you will be not able to download it directly.

If all else fails, join the [[FlightGear IRC channel]] and ask for the download_and_compile.sh script. Someone there will be likely to provide it to you.

==Instructions==
To run download_and_compile.sh, just save it in a directory called for example: ~/fg_tools
then execute it (no need to execute it as root).

Here is for example a sequence of commands to get the script and launch it in a new folder.
<pre>
mkdir ~/fgfs
cd ~/fgfs
wget http://brisa.homelinux.net/fgfs/download_and_compile.sh
chmod 755 download_and_compile.sh
sh download_and_compile.sh
</pre>
Once all will be finished, you will sucessfully get all the programs installed in the ~/fgfs directory.

===Launching FlightGear===
To run your new git installation of Flightgear you have to launch the ''run_fgfs.sh'' command under the same folder, for example:
<pre>
cd ~/fgfs
sh run_fgfs.sh
</pre>

===Launching Fgrun===
For many users it's more comfortable having Flightgear launched by the graphical utiliy Fgrun which is installed as well in the same folder. You have to launch the ''run_fgrun.sh'' command, for example:
<pre>
cd ~/fgfs
sh run_fgrun.sh
</pre>

===Launching FGCOM===
FGCOM is the system used by flightgear to simulate radio communications between users. Launch it using the ''run_fgcom.sh'' command:
<pre>
cd ~/fgfs
sh run_fgcom.sh -cs
</pre>

===Launching Atlas===
Atlas provides a map for Flightgear, use it launching: ''run_atlas.sh''
<pre>
cd ~/fgfs
sh run_fgatlas.sh
</pre>

===Launching Terrasync===
Your Flightgear compilation comes with the Terrasync program too, so if you want to use it:
<pre>
cd ~/fgfs
sh run_terrasync.sh -p 5500 -d /folder/with/sceneries
</pre>
Where: ''/folder/with/sceneries'' is the folder containing the sceneries data.

Then launch fgfs with the '''--fg-scenery=/folder/with/sceneries --atlas=socket,out,5,localhost,5500,udp''' option

==Troubleshooting==

===Compilation errors===
Here we are, no fear, if you wish to use programs from the cvs/svn/git repositories, you might face compilation errors that will prevent you to have a working copy of one or more of the programs provided by this script. What can be the causes that prevent us from a successful compiling? As far as I know those:
# Software developers introduce a new functionality with a new piece of code that prevents the compilation under your architecture, this can happen working with cvs/svn/git sources.
# The program refuses to compile because of a divergence in the libraries it depends. For example Flightgear might not compile because OSG has been modified, while OSG itself compiles fine, FG won't.
# One or more repositories are down and you can't get the library you need. (Both from cvs/svn/git or apt-get)

There is a simple solution to the above errors: wait and relaunch the script after some time (hours or days), if (and generally happens) software developers repair or synchronize their code with the newly updated libraries, your Flightgear will compile fine as if the previous error never took place.

Sometimes it happens that the script fails to compile only fgrun,fgcom or atlas, if you then see the run_fgfs.sh file it means that Flightgear installation was successful and you can safely run it.

==Options==
The script by default (without any option) will only compile Flightgear and Fgrun. To make it compile all, you need to launch the script with the ''ALL'' parameter. i.e.:
<pre>
sh download_and_compile.sh ALL
</pre>

===Compiling only one program===
If you wish to recompile only one of the programs you can launch the script with one of the following parameters:
* PLIB (to compile and install only plib)
* OSG (to compile and install only OpenSceneGraph)
* SIMGEAR (to compile and install only Simgear)
* FGFS (to compile and install only FlightGear)
* DATA (to download / update only data files for FlightGear)
* FGRUN (to compile and install only Fgrun)
* FGCOM (to compile and install only Fgcom)
* ATLAS (to compile and install only Atlas)

===Fast updating===
There is a second parameter ''UPDATE'' that allows you to just update your installation. i.e.:
This will only update FGFS
<pre>
sh download_and_compile.sh FGFS UPDATE
</pre>

===Advanced options===
* Skip download of packages using '''-p n''' option
* Skip compilation of programs using '''-c n''' option
* Skip retrieving software updates using '''-d n''' option
* Skip reconfigure (make clean) using '''-r n''' option

For example, if you a developer and wish to fast recompile and reinstall only modification for FlightGear do this:
<pre>
sh download_and_compile.sh -p n -d n -r n FGFS
</pre>

this will only recompile modifications and reinstall them.

==Disk usage==
Having both compiled program, source codes and data from git requires some hard disk space: It will take you something like 3GB of space.
If you don't have a fast machine, it will require you also some hours of compilation time.

Scripted Compilation on Linux Debian/Ubuntu

2010-07-13T16:15:03Z

Gorilla: /* Download */

==Description==
The following script takes care of downloading and compiling Flightgear from the git repositories with just one command execution for both 32-bit and 64-bit Debian based systems (Debian, Ubuntu). Pre-existing installed version (if any) of Flightgear are not touched at all since the script builds and installs everything under the directory in which it is launched.

Necessary packages are installed via the apt-get system while libraries not included in the repositories are downloaded and compiled on the fly (i.e. [[Plib]], [[Simgear]] and [[OSG]]).

===List of compiled programs===
The script is able to download and compile:
* Flightgear (And all the data needed to use it)
* [[Fgrun]]
* [[FGCOM]]
* [[Atlas]]
* [[Terrasync]]

==Download==
You can download the script here: [[http://brisa.homelinux.net/fgfs/download_and_compile.sh download_and_compile.sh]] [[http://wiki.flightgear.org/images/b/b7/Download_and_compile.sh Wiki Backup]]

The script is hosted on a home server, so if the electricity goes down or internet connection fails, you will be not able to download it directly.

If all else fails, join the [[FlightGear IRC channel]] and ask for the download_and_compile.sh script. Someone there will be likely to provide it to you.

[[http://wiki.flightgear.org/images/b/b7/Download_and_compile.sh]]

==Instructions==
To run download_and_compile.sh, just save it in a directory called for example: ~/fg_tools
then execute it (no need to execute it as root).

Here is for example a sequence of commands to get the script and launch it in a new folder.
<pre>
mkdir ~/fgfs
cd ~/fgfs
wget http://brisa.homelinux.net/fgfs/download_and_compile.sh
chmod 755 download_and_compile.sh
sh download_and_compile.sh
</pre>
Once all will be finished, you will sucessfully get all the programs installed in the ~/fgfs directory.

===Launching FlightGear===
To run your new git installation of Flightgear you have to launch the ''run_fgfs.sh'' command under the same folder, for example:
<pre>
cd ~/fgfs
sh run_fgfs.sh
</pre>

===Launching Fgrun===
For many users it's more comfortable having Flightgear launched by the graphical utiliy Fgrun which is installed as well in the same folder. You have to launch the ''run_fgrun.sh'' command, for example:
<pre>
cd ~/fgfs
sh run_fgrun.sh
</pre>

===Launching FGCOM===
FGCOM is the system used by flightgear to simulate radio communications between users. Launch it using the ''run_fgcom.sh'' command:
<pre>
cd ~/fgfs
sh run_fgcom.sh -cs
</pre>

===Launching Atlas===
Atlas provides a map for Flightgear, use it launching: ''run_atlas.sh''
<pre>
cd ~/fgfs
sh run_fgatlas.sh
</pre>

===Launching Terrasync===
Your Flightgear compilation comes with the Terrasync program too, so if you want to use it:
<pre>
cd ~/fgfs
sh run_terrasync.sh -p 5500 -d /folder/with/sceneries
</pre>
Where: ''/folder/with/sceneries'' is the folder containing the sceneries data.

Then launch fgfs with the '''--fg-scenery=/folder/with/sceneries --atlas=socket,out,5,localhost,5500,udp''' option

==Troubleshooting==

===Compilation errors===
Here we are, no fear, if you wish to use programs from the cvs/svn/git repositories, you might face compilation errors that will prevent you to have a working copy of one or more of the programs provided by this script. What can be the causes that prevent us from a successful compiling? As far as I know those:
# Software developers introduce a new functionality with a new piece of code that prevents the compilation under your architecture, this can happen working with cvs/svn/git sources.
# The program refuses to compile because of a divergence in the libraries it depends. For example Flightgear might not compile because OSG has been modified, while OSG itself compiles fine, FG won't.
# One or more repositories are down and you can't get the library you need. (Both from cvs/svn/git or apt-get)

There is a simple solution to the above errors: wait and relaunch the script after some time (hours or days), if (and generally happens) software developers repair or synchronize their code with the newly updated libraries, your Flightgear will compile fine as if the previous error never took place.

Sometimes it happens that the script fails to compile only fgrun,fgcom or atlas, if you then see the run_fgfs.sh file it means that Flightgear installation was successful and you can safely run it.

==Options==
The script by default (without any option) will only compile Flightgear and Fgrun. To make it compile all, you need to launch the script with the ''ALL'' parameter. i.e.:
<pre>
sh download_and_compile.sh ALL
</pre>

===Compiling only one program===
If you wish to recompile only one of the programs you can launch the script with one of the following parameters:
* PLIB (to compile and install only plib)
* OSG (to compile and install only OpenSceneGraph)
* SIMGEAR (to compile and install only Simgear)
* FGFS (to compile and install only FlightGear)
* DATA (to download / update only data files for FlightGear)
* FGRUN (to compile and install only Fgrun)
* FGCOM (to compile and install only Fgcom)
* ATLAS (to compile and install only Atlas)

===Fast updating===
There is a second parameter ''UPDATE'' that allows you to just update your installation. i.e.:
This will only update FGFS
<pre>
sh download_and_compile.sh FGFS UPDATE
</pre>

===Advanced options===
* Skip download of packages using '''-p n''' option
* Skip compilation of programs using '''-c n''' option
* Skip retrieving software updates using '''-d n''' option
* Skip reconfigure (make clean) using '''-r n''' option

For example, if you a developer and wish to fast recompile and reinstall only modification for FlightGear do this:
<pre>
sh download_and_compile.sh -p n -d n -r n FGFS
</pre>

this will only recompile modifications and reinstall them.

==Disk usage==
Having both compiled program, source codes and data from git requires some hard disk space: It will take you something like 3GB of space.
If you don't have a fast machine, it will require you also some hours of compilation time.

File:Download and compile.sh

2010-07-13T16:13:12Z

Gorilla:

FlightGear Newsletter July 2010

2010-07-12T14:22:16Z

Gorilla: Fixed a spelling error

{{newsletter}}
{{TOC_right}}

This month's newsletter marks a year since [[FlightGear Newsletter July 2009|the first issue]] was written!

'''<font size="4">Newsletter history</font>'''

One year ago, in June 2009, [[FlightGear]]-head Curt proposed his newsletter-idea [http://www.flightgear.org/forums/viewtopic.php?f=6&t=5201 at the forum]. With multiple (failed) efforts in the past, those involved were extremely agger to get it up and going this time. Stuart was the one that wrote most of the first issue(s). At the time of the second issue, more people were involved and wrote a paragraph or two.

Today, the newsletter is written by a bunch of people, with different interests and relations to FlightGear. It provides an easy way to keep up-to-date with the ongoing developments; both in FlightGear itself and in the community around it.

I would like to use this opportunity to thank those that contributed over the past year. Thanks to their work, the newsletter still exists! In order to reach our next mileage, we would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone (with a wiki account, [Special:UserLogin|free to register]) can edit the newsletter and every contribution is welcome.

Now, all I can say is: enjoy this brand new edition!

==Development news==
===New mapping software on the block===
Michael contributes new FlightGear mapping software to the communitiy, written in the Ruby programming language: [http://rubyforge.org/projects/fgmap FGMap]. Basically it shows your current flight position on an [http://openstreetmap.org OpenStreetMap] map. It therefore has some similarity to [[Atlas]] and the online [[MPMap]]s. As with all projects, [http://rubyforge.org/tracker/?func=add&group_id=9572&atid=37032 feedback] is highly appreciated.

FGMap has many features, including:
* Show flight position on Openstreetmap map in real-time
* Download new map tiles on-the-fly in the background
* Add shaded elevation layer to map for nice visual effect
* Display current speed and altitude
* Show position and frequency of all navigation aids on the map
* Create FlightGear route manager entries with a click of the mouse from navigation aids and waypoints
* Record and restore flight path
* Colorize path according to speed and altitude
* Display information about instantaneous speed and altitude for all points of the track
* Set waypoints on map

Downloads and more information are available at [http://rubyforge.org/projects/fgmap the project's website].

==In the hangar==
===Bell P59 Airacomet and Bell 222 X===
''helijah'' created and pushed both P59 and Bell 222X onto Git. The Bell 222X FDM is still in development. More information and download at [http://helijah.free.fr/flightgear/hangar.htm ''helijah's'' Hangar].

===De Havilland Canada DHC-7-150 Dash 7===
''Quadunit404'' has announced [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8805 intentions] to produce his first aircraft, the De Havilland Canada DHC-7-150 Dash 7, adding yet another member of the De Havilland Canada family to to FlightGear fleet after active development begins. Currently he is learning how to model using [[Blender]] and will be studying the FDMs of other turboprop regional airliners already in FlightGear to get an idea of how to write the FDM.

===SpaceShipOne and White Knight===
''helijah'' has made some changes to the SpaceShipOne model including the [[FDM]], adding fuselage reflection effect and separating the SpaceShipOne and White Knight objects. The next step is to improve the SpaceShipOne model by adding wheels and moving parts. After that he will try to separate the two aircraft when in flight.

==Livery database==
In the second week of July, the [http://liveries.flightgear.org livery database] welcomed its [http://liveries.flightgear.org/liveries.php?id=251 250th livery]: a glider club's livery for the [[Robin DR400]], created by top-painter Brett Harrison (Gooneybird). More liveries are welcome as always and can be [http://liveries.flightgear.org/contribute.php uploaded]!

==Scenery corner==
===Animated jetways===
[[File:Movable_Jetway.jpg|thumb|A jetway connecting to a [[Boeing 737-300|737-300]].]]
''skyop'' and ''Gijs'' are currently working on animated jetways for FlightGear that can be activated with a click of the mouse. At the moment they are very primitive and only fit [[Boeing 737|737s]]. Planned features include automatic attachment to your airplane's door and even multiple jetways for wide-body airliners and [[Airbus A380|A380s]]. See [http://www.flightgear.org/forums/viewtopic.php?t=8728 this thread] for more information.

===Detailed terrain for Dubai===
[[Image:Dubai_v0_vs_cs.png|thumb|270px|Dubai, with vmap0 data (left) and custom scenery data.]]
As announced in an [[FlightGear Newsletter March 2010#Dubai is coming up|earlier edition]], Gijs has been (re)drawing the terrain of Dubai. The FlightGear scenery now includes:
* Palm Islands (islands in the shape of a palm)
* The World (islands together forming a worldmap)
* Detailed coastline and city boundaries
The area is represented in its form of 2008, due to the lack of more up-to-date imagery. Given Dubai's massiv expansion speed, the scenery can be considered as out-of-date already. Nevertheless it is a great step forward compares to the previous terrain, as the image on the right proofs.

This new terrain will be available with the upcoming scenery build. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].

===Night flying at London Gatwick===
The new version of [[London Gatwick Airport]] (EGKK) is available and has improved textures and features. It claims to be one of the few ''(two?)'' major international airports in [[FlightGear]] suitable for night flying with full lighting textures on all buildings, hazard lights and approximately one hundred lighting masts. The tower even has lit instrumentation visible in the control room. Images are shown at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8363 the forum topic].

The taxiways at night are complex but made easier if the official charts are downloaded from [http://www.nats-uk.ead-it.com]. Many taxiway and runway signs have been included to help you on your way. Additional [[AI]] ground network and AI traffic have made this into a very busy airport and a single gate at each pier has been thoughtfully reserved so you can find a parking space when you land here (see the readme file for details).

In daytime the airport is fully modelled with detailed textures and even the roofs of buildings having accurate features. Stock model jetways, cargoes and ground vehicles have been added in quantity to give an authentic look to the airport. Large areas of open air car parks are distributed around the perimeter with novel layering of textures to enhance the 3D effect of the parked cars. Similarly, woods and trees have been added in surrounding areas to add more to the overall feel of the airport.

London Gatwick EGKK may be downloaded from [http://www.mediafire.com/?t2ml5ezmgwv MediaFire].

==Aircraft review==
'''This month: (name of aircraft here)'''

==From the community==
===TransGear founder leaves===
Rob (MD-Terp), known by many as the founding father of the monthly [[TransGear]] events, [http://www.flightgear.org/forums/viewtopic.php?f=3&t=8809 announced] his "retirement" at the forum. With the first event being held just one month after the first edition of this newsletter, TransGear almost reached its first mileage. However, some former participants stepped up to continue organising such events and maybey even Rob will return. More on that in a future edition.

We would like to thank Rob for all he has done, wish him all the best and deeply hope to see him return to the community one day.

==And finally...==

===Did you know?===

[[Category:FlightGear Newsletter|2010 06]]

Using TerraGear

2010-07-12T14:02:33Z

Gorilla: /* Obtaining TerraGear */

[[Image:Terragearprocesschart.png|thumb|TerraGear Process Flow Chart]]
The [[TerraGear]] software project supports [[FlightGear]] by creating the files used by FlightGear to represent the elevation and texture of the earth, including airports, cities, fields, forests, rivers, roads and so on. The TerraGear software reads data files containing ground elevation, airport locations and layouts, geographical land-cover data, and more, and produces the scenery files used by FlightGear to represent the terrain of the world.

For simplicity and convenience, most FlightGear users simply download the plug-and-play scenery files from the FlightGear scenery server, or use [[TerraSync]] to automatically download scenery as needed. But there is a variety of reasons you might want to use TerraGear to produce your own terrain files, rather than downloading the standard FlightGear scenery.

For instance, if you use [[TaxiDraw]] to modify/improve information about an [[:Category:Airports|airport]]'s taxiway/apron layout, you might wish to see how that modified airport would look in the scenery before deciding you're happy with the results. Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher-resultion vector data (vmap1, Tiger, osm) to get better roads/streams. For all these reasons, learning how to use TerraGear is a good idea.

==Obtaining TerraGear==
You can either build TerraGear yourself, or download a pre-compiled binary. The later is the easiest and advised for starters.

* '''Option 1 - Download TerraGear pre-compiled (recommended for beginners) on Windows'''
*# Download the latest TerraGear-cs-Win..-....zip file (check what bits version you run!) from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/.
*# Create or choose a directory to hold the TerraGear tools.
*# Unzip the package into a sub-directory named <tt>Terragear/</tt> in the base directory.

* '''Option 2 - Compile TerraGear from source code''' as explained in [[Building TerraGear|this article]].

''Note:'' You might need default_priorities.txt from the mapserver [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob_plain;f=src/BuildTiles/Clipper/default_priorities.txt;h=4bb644a265ffc978a4303aad79169ace7ec1f043;hb=61ac48f3e56941b82aeb35960252c6ec4b7388d4 Git respository] See this forum thread for details: [http://www.flightgear.org/forums/viewtopic.php?f=5&p=77950]

==Using TerraGear==
First, choose the boundaries for the area of scenery you want to build, in terms of latitude and longitude. The smaller the area of scenery you generate, the smaller the amount of data you will need, and the less CPU time it will take. For example, if you are just interested in generating a new airport layout at 12.3W 34.4N, then simply generating the scenery between 12W 34N and 13W 35N would be sufficient.

Write down the bounding box (minimum and maximum longitude and latitude) for the scenery you want to generate. Remember that West and South are negative - i.e. 4W 10S would be -4, -10. Try not to get mixed up, otherwise you'll end up generating scenery or airports on the other side of the planet!

You'll be dealing with multiple different types of data in various formats. Create a new directory for your scenery work. Within that directory, create the following sub-directories:

* '''data/''' - for raw and pre-processed data (eg elevation files)
* '''output/''' - for the scenery files you will create
* '''work/''' - for data that has been processed (eg by shape-decode) and is ready to be munged into scenery

===Obtaining and processing data===
Terragear uses three different kinds of information to generate scenery:

# The elevation of the land (provided by SRTM)
# The location and layout of airports (provided by apt.dat or a custom .dat)
# Whether a given lat/lon is sea, land, city, forest, town, road, railway (provided by VMAP0, CORINE etc. or custom shapefiles)

This article describes how obtain and process each of these types of data in order, and bring it together for use by FlightGear. The order of these steps is important. For example, the airport data step needs the elevation data to determine the elevation of the airports and thus you should start with preparing elevation data.

'''<u>Please note:</u> for inclusion in the official FlightGear scenery, all data <u>must</u> come from [[GNU GPL]] compatible sources!'''

====Elevation data====
The best elevation data currently available is from the Shuttle Radar Topography Mission (SRTM). There are two types of SRTM data:
* Highly accurate 1-arcsecond resolution data, known as SRTM-1, for the USA
* Less accurate 3-arcsecond data, known as SRTM-3, for the rest of the world.
From now on, we'll assume you are using SRTM-3 data. Unless otherwise noted, the process for SRTM-1 is identical.

You can download the appropriate data from http://dds.cr.usgs.gov/srtm/version2_1/. You want all .hgt.zip files covering your region of interest. Depending on the size of your scenery, there may be quite a few. Download them to <tt>data/SRTM-30/</tt> in your base directory. (The reason why the directories are called SRTM-30 is because genapts will look for a few known, hardcoded directories in it's working directory. SRTM-30 is one of them and this is the least confusing in that list.)

Now we've got the data, we need to convert it into something of use to TerraGear. First, you need to unzip each of the .hgt files. After that, open the commandline (Windows: <tt>Start > Run > cmd.exe</tt>) and change into the base directory (<tt>cd .../.../TerraGear</tt>).
* '''NOTE:''' If you want to create a batch-file, replace <tt>%f</tt> with <tt>%%f</tt>, see [http://technet.microsoft.com/en-us/library/bb490909.aspx]
* '''NOTE:''' For SRTM-1 data, replace the <tt>3</tt> by a <tt>1</tt> in the first argument to hgtchop

Then type this:
for %f in (./data/SRTM-30/*.hgt) do ./Terragear/hgtchop.exe 3 %f ./work/SRTM-30

For Linux:
for i in $PWD/data/SRTM-3/*.hgt; do hgtchop 3 $i $PWD/work/SRTM-30; done

Now you will get a lot of .arr.gz files in your work/SRTM-3/ directory. We need to convert these to the .fit.gz format. Run the commandline again with
* '''NOTE:''' the space and dot at the and are important!

./Terragear/terrafit.exe .

====Airport data====
Now we've got elevation data, we can generate our airports. First, create a <tt>data/airports/</tt> directory and copy in your apt.dat file. This may be direct from your FlightGear data package (though you'll need to unzip it), or it may be one that you've modified with [[TaxiDraw]].

The command to create airports is "genapts". Run it without any arguments to see the various command-line options.

If it is simply run with a specified apt.dat and work directory, it will generate airport layouts for every airport in the file, which can take a long time.

If you are just creating a single airport and you know the ICAO ID (e.g. [[KSFO]], EGPH, EG32), use is as follows from your root scenery directory (i.e. the directory above your data, work and output directories). If you use an apt.dat file with one single airport in it you should omit the "--airport" parameter.

genapts --input=data/airports/apt.dat --work=./work --airport=<AIRPORT_ID>

If you are generating a larger set of scenery, then you can specify the minimum and maximum longitude and latitude.

Genapts will create two sub-directories in your work directory:
* AirportArea/
* AirportObj/

These contain the definitions of the airport layout and any objects present (e.g. windsocks).

====Landuse data====
The final piece of data we need to generate is the landuse data. In general, this is taken from the VMAP0 dataset as shapefiles from the scenery database mapserver, but other sources can also be used.

The landuse data can be split into a number of different types:

* '''Landmass''' separates the land from the sea. It is used as a mask for all other data. The most commonly used is the VMAP0 Landmass, but GSHHS can also be used.
* '''Land use data:''' defines whether a piece of land is forest, urban, sand, lava, glacier etc. These are usually VMAP0 data, defined as polygons.
* '''Line data:''' includes railroads, streams, roads. Typically VMAP0, but also Open Street Map for roads.
* '''Point data:''' is currently only used for defining towns.

By far the easiest way to get this data is to download shapefiles from the wonderful [http://mapserver.flightgear.org MapServer]. The MapServer lets you download the shapefiles for any selected scenery area. Click on the "Download Shapefiles" link (or go direct: http://mapserver.flightgear.org/download.psp). Enter in the bounding box of the scenery you want to generate, select the type of shapefile data you want, and click download. For basic scenery, get everything listed under VMap0 (with prefix v0_).

Download each shapefile into a <tt>data/shapefiles/</tt> directory.

You can load these shapefiles into a GIS editor such as [[QGIS]] or GRASS to view and edit. This is a good idea to verify you have the correct files! Later on, you can experiment with replacing various shapefiles with other versions (GSHHS for coastline, OSM for roads etc.).

The next step is to decode the shape-files into TerraGear format using the '''ogr-decode''' command.

There are three important command-line arguments for ogr-decode:
* the destination directory for the decoded data
* the location of the shapefile's directory
* the material type

Each shape-file corresponds with one of the material types defined in the materials.xml files. The mapping is pretty obvious. For example, v0_mixedcroppasturecover maps to MixedCropPastureCover. Note that the material types are case-sensitive, so it is a good idea to refer to the <tt>[[$FG_ROOT]]/materials.xml</tt> file to hand so you can check. The exception is v0_landmass, which MUST be mapped onto the type Default.

Additionally, there are a number of optional arguments, to indicate the width of line data (for roads, streams, railways), how large to make point data (for towns) and how long the longest straight line is allowed to be.

For example, to decode the v0_landmass shapefile, you use the following command:

ogr-decode --max-segment 500 --area-type Default work/Landmass data/shapefiles/v0_landmass

To create streams of width 10 metres

ogr-decode --max-segment 500 --line-width 10 --area-type Stream work/Stream data/shapefiles/v0_stream

To generate some towns about 1km across

ogr-decode --point-width 500 --area-type Town work/Town data/shapefiles/v0_town

Run this command for each shapefile in the set.

==Generating scenery==
You will now have a work directory looking something like this:

AirportArea SRTM-30
AirportObj Stream
Bog IrrCropPastureCover Town
Lake Urban Landmass
Railroad DryCropPastureCover Road
EvergreenBroadCover Marsh Sand
MixedCropPastureCover ScrubCover
GrassCover MixedForestCover Shared

Now we can actually generate the scenery. This is done by the fgfs-construct command. Run the command with "--help" to get usage information.

We need to define:
* the work (--work-dir) and output (--output-dir) directories
* the center of the scenery we want to generate (--lat, --lon)
* the radius (--xdist, --ydist) from which to generate
* All the work directories to include in the scenery.

For example:
fgfs-construct --work-dir=./work --output-dir=./output --lon=55 --lat=60 --xdist=3 --ydist=3 \
AirportArea SRTM-30 AirportObj Stream Bog IrrCropPastureCover Town Lake Urban Landmass Railroad \
DryCropPastureCover Road EvergreenBroadCover Marsh Sand MixedCropPastureCover ScrubCover GrassCover \
MixedForestCover

When this finishes, the output directory will contain a scenery sub-tree.

Point to it by setting either [[$FG_SCENERY]] or by using the --fg-scenery command-line option to fgfs, and give your new scenery a try!

==Troubleshooting==
Below is a list of common problems and solutions. If in doubt - Google it. Many problems (particularly when compiling TerraGear) have been hit before:

* Crashes in genapts. Sometimes genapts will crash when dealing with a particular airport. In that case, try running it again with the --start-id argument to start at the airport it failed on, and the --nudge argument which tries to nudge the calculations in the right direction.
* fgfs-construct Killed. The fgfs-construct process may kill itself if it is using too many system resources. Increasing the values for setrlimit in src/BuildTiles/Main/main.cxx is the best solution.
* Airports appear in the bottom of holes, or there are spaces between the airports and the scenery. This typically happens when genapts is unable to find the correct elevation data, or the elevation data changed between running genapts and shape-decode. Try generating a single airport in your scenery area using genapts, and look at the output. In particular, make sure there is a work/SRTM-30 directory.
* Only the airports appear in the scenery. There are three typical causes for this:
** You didn't download the correct shapefiles for the area.
** You haven't run shape-decode on the v0_landmass shapefile as Default
** You didn't include the correct directories in fgfs-construct.
* Generate scenery includes data removed from the shapefiles. If you are editing shapefiles, you need to delete the appropriate work subdirectory before running shape-decode. Otherwise your changes will be in addition to those already present.
* All the scenery is flat and at sea-level. Typically this is because you didn't include any elevation data in your fgfs-construct command. Make sure there's a STRM-30 directory included in the command-line.
* All terrain copies the material of a certain shapefile. You have probably forgotten to put each of the downloaded shapefiles in a seperate directory inside the Data/shapefiles directory.

{{Terra}}

[[Category:Scenery enhancement]]

Bombardier CRJ-200 (Old)

2010-07-05T01:44:51Z

Gorilla: Added details about the broken link and an alternative.

{{infobox Aircraft
|image =CRJ-200.jpg
|caption =United Airline Boeing 737-300
|name =Bombardier CRJ-200
|type =Airliner
|livery =
|authors =Joshua Wilson
|fdm =YASim
|status =Development
|fgname =CRJ-200
|download =http://www.flightgear.org/Downloads/aircraft/#CRJ-200 Borken Link
}}
The '''Bombardier CRJ100''' and '''CRJ200''' are a family of regional [[:Category:Airliners|airliner]] manufactured by [[:Category:Bombardier Aerospace|Bombardier]], and based on the Canadair Challenger business jet.

The CRJ200 is identical to the 100 model except for more efficient engines.

Pinnacle Airlines had operated some with 44 seats with closets in the forward areas of the passenger cabin though these were converted to 50 seat airplanes. These modifications were designed to allow operations under their major airline contract "scope clause" which restricts major airlines' connection carriers from operating equipment carrying 50 or more passengers to guard against usurpation of Air Line Pilots Association & Allied Pilots Association pilots' union contract. Similarly, Comair's fleet of 40-seat CRJ200s were sold at a discounted price to discourage Comair from purchasing the less expensive and smaller Embraer 135.

As of August 2006 a total of 938 CRJ100 and CRJ200 aircraft (all variants) are in airline service, with 8 further firm orders. Major operators include Comair (143), Pinnacle Airlines (132), SkyWest Airlines (136), Atlantic Southeast Airlines (110), Air Wisconsin (70),, ALMA de Mexico (22), Air Canada Jazz (58), Mesa Airlines (60), Lufthansa CityLine (26), Air Nostrum (35, Plus 7 orders), PSA Airlines (35) and Republic Airways Holdings (24). Some 19 other airlines also operate smaller fleets of the type.[1]

==Broken Link details==

As this CRJ-200 is not included in the official Flightgear project, the download link is broken. See the [[Bombardier_CRJ-200LR]] for an alternative.

== Development status/Issues/Todo ==
'''Outside:'''
* no lighting

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

{{bombardier}}

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

FlightGear Git

2010-06-23T12:46:38Z

Gorilla: Added details aboout creating an initial clone of the source from the project's gitorious repository.

In May 2010, after a hardware failure on the CVS servers, the [[FlightGear]] project changed version control system from [[CVS]] to '''Git'''. The Git repositories are located at [http://gitorious.org/fg Gitorious] and at the [http://mapserver.flightgear.org/git/?p=fgdata;a=summary Mapserver].

Due to the recent switch, we are currently doing our best on providing manuals for obtaining FlightGear through Git. The following articles are work in progress as of June 1st:
* '''Mac OS X:''' [[FlightGear Git on Mac OS X]]
* '''Windows:''' [[FlightGear Git on Windows]]

== Motivation ==
Much has been written on the advantages of Git over CVS. For us, some advantages are:
* Much better support for branches and merging branches. This is especially important for creating bug-fix releases for major releases while still allowing work on the next major release to continue. It is also very nice for a developer's personal workflow.
* Easier path for contributors to submit changes and developers to integrate them;
* Much better support for everyday tasks like searching the project history for changes, viewing changes, bisecting the project history to find the original source of a bug.

Also, as noted before, the CVS servers had a hardware failure on May 2010, speeding up FlightGear's change to Git.

== Repositories ==
For historical reasons there continue to be separate repositories for Simgear and Flightgear. There are 3 interesting branches in the repositories. Listed in order from least stable to most:
* <tt>next</tt> The current tip of new development. This branch should always compile and run, but various things could be broken.
* <tt>master</tt> The tip of stable, tested new features. If we were to make a new release today, we would start from the tip of this branch. New features that have been "cooking" in the <tt>next</tt> branch for a few days or weeks will be merged here.
* <tt>maint</tt> Bug fixes for the most recently released Flightgear. When a release is made from <tt>master</tt>, this branch is reset to it.

This arrangement follows the scheme used by the Git maintainers.
[http://www.kernel.org/pub/software/scm/git/docs/howto/maintain-git.txt This description] is very technical; you will surely have achieved git-fu if completely understand it. However, the idea of maintaining several branches of different stability is common in collaborative software projects.

==Quick checkout==

Brief notes:

# Check on gitorious for valid projects: http://gitorious.org/fg
# Cloning Simgear
# Cloning FlightGear
# Cloning FGData

By default you will be checking out the next branch of SimGear and FlightGear. This is probably what you want if you want to assist with reporting bugs and the like before they are release as a proper release version.

===Cloning SimGear===
<pre>
$ git clone git://gitorious.org/fg/simgear.git
Initialized empty Git repository in /home/gpatterson/project/flightgear/compiles/simgear/.git/
remote: Counting objects: 19784, done.
remote: Compressing objects: 100% (5896/5896), done.
remote: Total 19784 (delta 15095), reused 17731 (delta 13610)
Receiving objects: 100% (19784/19784), 6.85 MiB | 88 KiB/s, done.
Resolving deltas: 100% (15095/15095), done.
</pre>

===Cloning SimGear===
<pre>
$ git clone git://gitorious.org/fg/flightgear.git
Initialized empty Git repository in /home/gpatterson/project/flightgear/compiles/flightgear/.git/
remote: Counting objects: 72119, done.
remote: Compressing objects: 100% (17140/17140), done.
remote: Total 72119 (delta 57619), reused 68255 (delta 54756)
Receiving objects: 100% (72119/72119), 19.56 MiB | 111 KiB/s, done.
Resolving deltas: 100% (57619/57619), done.
</pre>

===Cloning FGData===
(To be done)

==External links==
=== Git tutorials and resources ===
* Git [http://git-scm.com/documentation documentation and tutorials]
* Git as a [http://tomayko.com/topics/git way of life].
* [http://wiki.github.com/bogolisk/egg Egg], a cool Git emacs mode.
* A guide to [http://nathanj.github.com/gitguide/ using Git on Windows]
* [http://kylecordes.com/2008/04/30/git-windows-go/ Git on Windows Go!] (Setting up msysgit on Windows)
* [http://gitcasts.com/posts/git-on-windows Git on Windows (webcast)]
* [http://sourceforge.net/projects/qgit qgit - interactive git repository viewer and frontend]
* Additional [[Resources WRT running git on Win32]]

FlightGear Git

2010-06-23T12:37:57Z

Gorilla: Added Quick checkout header

In May 2010, after a hardware failure on the CVS servers, the [[FlightGear]] project changed version control system from [[CVS]] to '''Git'''. The Git repositories are located at [http://gitorious.org/fg Gitorious] and at the [http://mapserver.flightgear.org/git/?p=fgdata;a=summary Mapserver].

Due to the recent switch, we are currently doing our best on providing manuals for obtaining FlightGear through Git. The following articles are work in progress as of June 1st:
* '''Mac OS X:''' [[FlightGear Git on Mac OS X]]
* '''Windows:''' [[FlightGear Git on Windows]]

== Motivation ==
Much has been written on the advantages of Git over CVS. For us, some advantages are:
* Much better support for branches and merging branches. This is especially important for creating bug-fix releases for major releases while still allowing work on the next major release to continue. It is also very nice for a developer's personal workflow.
* Easier path for contributors to submit changes and developers to integrate them;
* Much better support for everyday tasks like searching the project history for changes, viewing changes, bisecting the project history to find the original source of a bug.

Also, as noted before, the CVS servers had a hardware failure on May 2010, speeding up FlightGear's change to Git.

== Repositories ==
For historical reasons there continue to be separate repositories for Simgear and Flightgear. There are 3 interesting branches in the repositories. Listed in order from least stable to most:
* <tt>next</tt> The current tip of new development. This branch should always compile and run, but various things could be broken.
* <tt>master</tt> The tip of stable, tested new features. If we were to make a new release today, we would start from the tip of this branch. New features that have been "cooking" in the <tt>next</tt> branch for a few days or weeks will be merged here.
* <tt>maint</tt> Bug fixes for the most recently released Flightgear. When a release is made from <tt>master</tt>, this branch is reset to it.

This arrangement follows the scheme used by the Git maintainers.
[http://www.kernel.org/pub/software/scm/git/docs/howto/maintain-git.txt This description] is very technical; you will surely have achieved git-fu if completely understand it. However, the idea of maintaining several branches of different stability is common in collaborative software projects.

==External links==
=== Git tutorials and resources ===
* Git [http://git-scm.com/documentation documentation and tutorials]
* Git as a [http://tomayko.com/topics/git way of life].
* [http://wiki.github.com/bogolisk/egg Egg], a cool Git emacs mode.
* A guide to [http://nathanj.github.com/gitguide/ using Git on Windows]
* [http://kylecordes.com/2008/04/30/git-windows-go/ Git on Windows Go!] (Setting up msysgit on Windows)
* [http://gitcasts.com/posts/git-on-windows Git on Windows (webcast)]
* [http://sourceforge.net/projects/qgit qgit - interactive git repository viewer and frontend]
* Additional [[Resources WRT running git on Win32]]

==Quick checkout==

Talk:Island Virtual Airways

2010-06-20T14:18:17Z

Gorilla: /* Merger into AVA */

We need a link to the IVA liveries. Where are they?

David [[User:D-79|D-79]] 13:03, 15 July 2009 (EDT)

The liveries are on the IVA website. I wouldn't care putting a link to the livery page on here but I would rather not put direct links on here to each of them. They are at http://islandva.org/index.php?option=com_content&view=article&id=47&Itemid=53

Michael [[User:mdsmith2| MDSmith2]] 19:57, 15 July 2009 (Zulu)

: Hey Michael, thanks, I just added that.
: David [[User:D-79|D-79]] 16:37, 15 July 2009 (EDT)

== Merger into AVA ==

There was some discussion on the forums concerning the merging of this VA into AVA. But we never recieved any word from any IVA members. Does anyone know IVA's stance concerning the merger? --[[User:Armchair Ace|Armchair Ace]] 09:00, 25 April 2010 (UTC)

: I believe that IslandVA as a group didn't form a concensus on whether to merge or not. --[[User:Gorilla|Gorilla]] 14:18, 20 June 2010 (UTC)