FlightGear wiki - User contributions [en]

Understanding Propeller Torque and P-Factor

2006-06-26T00:10:48Z

Sek: Adding link to AU groundschool, paraglider page

This is an attempt to answer the frequent question "Why is my aircraft turning left all the time?"

This occurs only in aircraft with propellers at the front of the aircraft. Three distinct phenomena cause the effect, all causing the aircraft to turn in the same direction. They are:

==Prop wash==
A propeller pushes air not just horizontally to the back, but more in a twisting helix around the fuselage (clockwise as seen from the cockpit). As the air whirls around the fuselage it pushes against the left side of the vertical tail, causing the plane to yaw to the left. The prop wash effect is at its greatest when the airflow is flowing more around the fuselage than along it, i.e., at high power and low airspeed, which is the situation when starting the takeoff run.

==Propeller Torque Effect==

Torque effect is the influence of engine torque on aircraft movement and control. It is generally exhibited as a left turning tendency in piston single engine propeller driven aircraft.

According to Newton's law, "for every action there is an equal and opposite reaction," such that the propeller, if turning clockwise (when viewed from the cockpit), imparts a tendency for the aircraft to rotate counterclockwise. Since most single engine aircraft have propellers rotating clockwise, they rotate to the left, pushing the left wing down.

Typically, the pilot is expected to counter this force through the control inputs. To counter the aircraft roll left, the pilot applies right aileron.

It is important to understand that torque is a movement about the roll axis. Aileron controls roll. Prop torque is not countered by moving the rudder or by setting rudder trim. It is countered by moving or trimming the aileron.

This correction induces adverse yaw, which is corrected by moving or trimming the rudder (right rudder).

On aircraft with contrarotating propellers (propellers that rotate in opposite directions) the torque from the two propellers cancel each other out, so that no compensation is needed.

Further Reading: [http://www.aerospaceweb.org/question/dynamics/q0015a.shtml Propeller Torque Factor]

== P-Factor ==

P-factor is the term for asymmetric propeller loading, causes the airplane to yaw to the left when at high angles of attack.

The descending right side of the propeller (as seen from the rear) has a higher angle of attack than the upward-moving blade on the left side and provides more thrust. This occurs only when the propeller is not meeting the oncoming airflow head-on, for example when an aircraft is moving down the runway at a nose-high attitude (i.e. at a high angle of attack), as is the case with tail-draggers. Aircraft with tricycle landing gear maintain a level attitude on the takeoff run, so there is little P-factor during takeoff. In all cases, though, the effect is weaker than prop wash.

According to What You Need to Know About Aerodyanics... by Franklin Gutierrez.

== Gyroscopic Precession ==

This is the tedency of a spinning object to precess or move about its axis when disturbed by a force. The engine and propeller act as a big gyroscope. However, gyroscopic precession is likely to be minimal in a typical aircraft.

Gyroscopic precession is frequenly confused with p-factor.

One author maintains p-factor is caused by a combination of factors unrelated to gyroscopic precession http://home.earthlink.net/~x-plane/FAQ-Theory-PFactor.html

== External Links ==

* [http://www.auf.asn.au/groundschool/umodule11.html#tophenomena Engine effects and aerodynamic phenomena] Recreational Aviation Australia Ground School article on "prop wash," prop torque, gyro precession, p-factor and other similar factors affecting taildraggers.

* [http://www.americanparagliding.com/propellerforces.htm http://www.americanparagliding.com/propellerforces.htm] The forces of P-factor, gyro precession and asymmetric blade thrust act with particular intensity in powere parachute gliders (paragliders), as this article relates.

Nasal scripting language

2006-06-24T01:32:04Z

Sek:

Many applications today support scripting as a means of "gluing" the application together and enabling users to extend functionality of the application. For example, the 3d modeling application Blender implements most of its import and export filters as user contributed Python scripts, which are automatically integrated into the menu system. Many games are also integrating a scripting language to make it easier for modders to add features.

FlightGear has a scripting language called NASAL. You can find out more about it at the NASAL website.

http://www.plausible.org/nasal

Elements of the graphical user interface, aircraft instruments and performance can be scripted.

==NASAL Scripting for Flight Gear==

=== Listeners ===

A listener specifies a function to be executed when a specified property is written to. The value may or may not change, so the listener may execute "on change" if the property value changes, but also if it is rewritten with the same value. The listener executes whenever the property is written to.

A listener is attaches to a property. Listeners do not work with "tied" properties (most are in the FDM, but you can spot them by Ctrl-clicking "." in the property browser).

Listeners are useful when you need to monitor a value. They are most efficient when the value does not change frequently, but are generally more efficient and better than a timer.

Setting a listener:

setlistener( [Property], [Function] );

Note: The name of the function is never quoted in a listener.

monitor_course = func {
print("Monitoring course.");
}
setlistener("instrumentation/gps/wp/leg-course-deviation-deg", monitor_course);

Deleting a listener:

removelistener( [Function] );

removelistener(monitor_course);

Setting more than one listener on a given function:

kernel = func {
flaps = getprop(Controls, "flight/flaps");
if( flaps == 20 ) {
print("Flaps 20");
}
if( flaps == 40 ) {
print("Flaps 40");
}
if( flaps == 60 ) {
print("Flaps 60");
}
}
setlistener("/controls/flight/flaps", kernel);
setlistener("/controls/flight/flaps-serviceable", kernel);

Returning from a listener early:

monitor_course = func {
if( getprop(Internal, "power-good") == "off" ) {
return 0;
}
print("Monitoring course.");
}

Examples:

TODO

=== Tips ===
How to play sounds using NASAL script?

The same way one would do animations using Nasal;

Adjust properties in Nasal (they may be "private" properties in your own
subtree of the property list, say /tmp/<aircraft>) and let the sound
configuration file act on those properties.
(from flightgear-devel)

Nasal scripting language

2006-06-24T01:30:22Z

Sek: Adding multiple listeners to a function

Many applications today support scripting as a means of "gluing" the application together and enabling users to extend functionality of the application. For example, the 3d modeling application Blender implements most of its import and export filters as user contributed Python scripts, which are automatically integrated into the menu system. Many games are also integrating a scripting language to make it easier for modders to add features.

FlightGear has a scripting language called NASAL. You can find out more about it at the NASAL website.

http://www.plausible.org/nasal

Elements of the graphical user interface, aircraft instruments and performance can be scripted.

==NASAL Scripting for Flight Gear==

=== Listeners ===

A listener specifies a function to be executed when a specified property is written to. The value may or may not change, so the listener may execute "on change" if the property value changes, but also if it is rewritten with the same value. The listener executes whenever the property is written to.

A listener is attaches to a property. Listeners do not work with "tied" properties (most are in the FDM, but you can spot them by Ctrl-clicking "." in the property browser).

Setting a listener:

setlistener( [Property], [Function] );

Note: The name of the function is never quoted in a listener.

monitor_course = func {
print("Monitoring course.");
}
setlistener("instrumentation/gps/wp/leg-course-deviation-deg", monitor_course);

Deleting a listener:

removelistener( [Function] );

removelistener(monitor_course);

Setting more than one listener on a given function:

kernel = func {
flaps = getprop(Controls, "flight/flaps");
if( flaps == 20 ) {
print("Flaps 20");
}
if( flaps == 40 ) {
print("Flaps 40");
}
if( flaps == 60 ) {
print("Flaps 60");
}
}
setlistener("/controls/flight/flaps", kernel);
setlistener("/controls/flight/flaps-serviceable", kernel);

Returning from a listener early:

monitor_course = func {
if( getprop(Internal, "power-good") == "off" ) {
return 0;
}
print("Monitoring course.");
}

Examples:

TODO

=== Tips ===
How to play sounds using NASAL script?

The same way one would do animations using Nasal;

Adjust properties in Nasal (they may be "private" properties in your own
subtree of the property list, say /tmp/<aircraft>) and let the sound
configuration file act on those properties.
(from flightgear-devel)

Nasal scripting language

2006-06-23T23:57:11Z

Sek:

Many applications today support scripting as a means of "gluing" the application together and enabling users to extend functionality of the application. For example, the 3d modeling application Blender implements most of its import and export filters as user contributed Python scripts, which are automatically integrated into the menu system. Many games are also integrating a scripting language to make it easier for modders to add features.

FlightGear has a scripting language called NASAL. You can find out more about it at the NASAL website.

http://www.plausible.org/nasal

Elements of the graphical user interface, aircraft instruments and performance can be scripted.

==NASAL Scripting for Flight Gear==

=== Listeners ===

A listener specifies a function to be executed when a specified property is written to. The value may or may not change, so the listener may execute "on change" if the property value changes, but also if it is rewritten with the same value. The listener executes whenever the property is written to.

A listener is attaches to a property. Listeners do not work with "tied" properties (most are in the FDM, but you can spot them by Ctrl-clicking "." in the property browser).

Setting a listener:

monitor_course = func {
print("Monitoring course.");
}

setlistener("instrumentation/gps/wp/leg-course-deviation-deg", monitor_course);

Deleting a listener:

removelistener(monitor_course);

Returning from a listener early:

monitor_course = func {
if( getprop(Internal, "power-good") == "off" ) {
return 0;
}
print("Monitoring course.");
}

Examples:

TODO

=== Tips ===
How to play sounds using NASAL script?

The same way one would do animations using Nasal;

Adjust properties in Nasal (they may be "private" properties in your own
subtree of the property list, say /tmp/<aircraft>) and let the sound
configuration file act on those properties.
(from flightgear-devel)

Nasal scripting language

2006-06-23T23:56:12Z

Sek: Added listeners

Many applications today support scripting as a means of "gluing" the application together and enabling users to extend functionality of the application. For example, the 3d modeling application Blender implements most of its import and export filters as user contributed Python scripts, which are automatically integrated into the menu system. Many games are also integrating a scripting language to make it easier for modders to add features.

FlightGear has a scripting language called NASAL. You can find out more about it at the NASAL website.

http://www.plausible.org/nasal

Elements of the graphical user interface, aircraft instruments and performance can be scripted.

==NASAL Scripting for Flight Gear==

=== Listeners ===

== Listeners ==

A listener specifies a function to be executed when a specified property is written to. The value may or may not change, so the listener may execute "on change" if the property value changes, but also if it is rewritten with the same value. The listener executes whenever the property is written to.

A listener is attaches to a property. Listeners do not work with "tied" properties (most are in the FDM, but you can spot them by Ctrl-clicking "." in the property browser).

Setting a listener:

monitor_course = func {
print("Monitoring course.");
}

setlistener("instrumentation/gps/wp/leg-course-deviation-deg", monitor_course);

Deleting a listener:

removelistener(monitor_course);

Returning from a listener early:

monitor_course = func {
if( getprop(Internal, "power-good") == "off" ) {
return 0;
}
print("Monitoring course.");
}

Examples:

TODO

=== Tips ===
How to play sounds using NASAL script?

The same way one would do animations using Nasal;

Adjust properties in Nasal (they may be "private" properties in your own
subtree of the property list, say /tmp/<aircraft>) and let the sound
configuration file act on those properties.
(from flightgear-devel)

New to FlightGear

2006-06-19T18:19:51Z

Sek: Added common complaints, compass turning, vsi error, gyro drift

{|
|__TOC__
|}

== Getting Started ==

=== 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 you may choose the CVS version if you wish to work with a development version of FlightGear).

=== Getting Scenery ===

A limited set of scenery comes installed with FlightGear, which consists of the area surrounding KSFO.

In FlightGear, scenery is divided into two kinds of data: Objects and Terrain. 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 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://fgfsdb.stockill.org/ FlightGear Scenery Database].

Information beyond this brief overview is available in [[Installing Scenery]].

=== Getting Aircraft ===

To download additional Aircraft for FlightGear, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page, then choose [Aircraft Downloads http://www.flightgear.org/Downloads/aircraft/index.shtml].

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

/path/to/flight/gear/data/Aircraft

=== Starting FlightGear ===

Many users choose to start FlightGear from the command line ("console" or "shell" as it is known to Unix users).

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

=== Online Multiplayer Flying ===

See the [[Multiplayer Howto]]

=== 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 the 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 (why it is sometimes called a Directional Gyroscope), which 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, which are counter-intuitive. Pilots must learn to recognize these phenomena and compensate for the 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 vitural 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 an 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 a) do not specify an autopilot b) aircraft that 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 do I know what airports are avaialble? 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 VORs 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 FlightGear Online Map for multiplayers are both good resources as well as the FlightGear Community Flight Planner.

== Getting Help ==

=== Chat ===

The quickest way to get help with Flight Gear is to join in the chat room by IRC. You can get details on how to join the discussion at

http://www.flightgear.org/mail.html

and the current chat server is

Primary Site: Host = irc.flightgear.org, channel = #flightgear.

but check the flight gear site for the latest information.

=== Email Discussion Group ===

The documentation for Flight Gear is sketchy and undergoing constant change as new features are developed. This makes chat the best place to find answers to problems getting FlightGear to run.

=== Documents ===

The ways for _users_ to get help with FlightGear are:

* Documents bundled with the release package.
* FlightGear IRC channel.
* FlightGear users mailing list.

== 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 to 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 CVS version of FlightGear may choose to update their aircraft files through the CVS 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/

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 over time.

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 at:

http://www.flightgear.org/Docs/getstart/getstart.html

or download a PDF for viewing with Acrobar Reader or printing:

http://www.flightgear.org/Docs/getstart/getstart.pdf

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

== How you can help ==

'''[[Volunteer]]'''

=== Testing ===
* Build the latest CVS code or download snapshots (link)
* File Bug Reports

=== Support ===
* Help new users with downloading, compiling, installing and running FlightGear
* Provide Ideas & Suggestions

=== Development ===
* Writing documentation !! Everyone is welcome to contribute to "The Manual"; at least little experience in LaTeX makes the task easier. Please contact the authors of The Manual if you would like to add corrections or whole chapters.
* C/C++ Coding
* Aircraft development (3D modelling, textures, FDMs, scripting)

User:Sek

2006-06-17T18:30:36Z

Sek: ultralights

Steve Knoblock

Currenly working on:

* Modeling an ultralight aircraft, based loosely on the Boorabee (although plans exist, I could not obtain them after contacting the original designer...no answer by email).

* A model of the Digitrak digital autopilot for experimental aircraft.

Other interests:

* Would like to develop a comprehensive set of scenery to populate the Chesapeake Bay/DelMarVa region. Some of the favorite airports needing updating are: KSBY, KTGI, KOXB, KESN, Bay Bridge, Dover, Newcastle, Cambridge MD, Accomack County, St. Mary's, etc. also, FG really needs a good Chesapeake Bay Bridge model and a Chesapeake Bay-Bridge Tunnel model.

I tend to tool around the bay, these are my favorites. The direct flight back from KOXB or KSBY to KMTN has nice viusals in the evening. Another interesting flight is from Accomack Co. via the Cape Charles VOR to Norfolk.

* [http://www.airnav.com/airport/KSBY KSBY]
* [http://www.airnav.com/airport/KOXB KOXB]
* [http://www.airnav.com/airport/KMTN KMTN]
* [http://www.airnav.com/airport/KESN KESN]

Favorite Flights
* [http://www.airnav.com/airport/KSBY KSBY] to [http://www.airnav.com/airport/KMTN KMTN]
* [http://www.airnav.com/airport/KOXB KOXB] to [http://www.airnav.com/airport/KMTN KMTN]
* [http://www.airnav.com/airport/KSBY KSBY] to [http://www.airnav.com/airport/KILG KILG] to [http://www.airnav.com/airport/KPHL KPHL]
* [http://www.airnav.com/airport/EKN EKN] to [http://www.airnav.com/airport/HEF HEF]

Sometimes I fly out of Wallops instead of Accomack. Would be nice to collect some NASA planes there.

Flying back from Ocean City, MD or Salisbury, MD to Martin State just outside of Baltimore Washington International in the evening can be visually spectacular. Begin just before dusk and at Cessna cruise speed you should arrive as the sun is setting at your destionation. If you like watching the stars come out and the lights come on, start a little later.

The flight from Elkins east over the Appalachian mountains is challenging and scenic, especially with real weather. The airport is nestled in the Tygart Valley surrounded by mountains reaching over 4,000 feet. The airport sits on the valley floor at a little under 2,000 feet MSL near the town of Elkins, West Virginia. [Elkins-Randolph Co. Airport http://www.elkinsairport.com/] official website. According to the website, the airport was built in the 1930s and "being on one of the early airways crossing the country, Elkins has seen a wide range of navigation facilities, beginning with the lighting of fires at night to guide pilots. Later, Elkins became a site on the Airway Beacon System. (The last of which is still operating on Rich Mountain west of the airport.)"

Another interesting flight is navigating from Accomack Co. airport to Norfolk by way of the Cape Charles VOR station. The scenery can be very dramatic in evening and the weather changeable.

The Chesapeake watershed area offers a great variety of flying from the mountains to the seashore.

What I like about ultralight aircraft is how they recall the early days of aviation at the same time employing novel and advanced technologies. Instead of wire and wing cloth they are built of carbon fiber and titanium, offer leading edge avionics and autopilots not seen in many general aviation aircraft. I am fascinated by how the various parts of the aircraft mechanism are visible, instead of covered up with streamlined panels. They give the pilot a taste of flying in the early day. Relatively low and slow, the pilot gets a good view of the scenery passing by and depending on the aircraft, it may seem as if the aircraft is not there at all.

Self reference: --[[User:Sek|Sek]]

User:Sek

2006-06-12T01:09:32Z

Sek:

Template talk:Infobox aircraft

2006-06-12T01:09:12Z

Sek:

It would give more control over the infobox if we had the parser installed. http://meta.wikimedia.org/wiki/ParserFunctions#.23if: --[[User:Sek|Sek]]

Template talk:Infobox aircraft

2006-06-12T01:02:08Z

Sek:

It would give more control over the infobox if we had the parser installed. http://meta.wikimedia.org/wiki/ParserFunctions#.23if: --[[User Sek Sek]]

Template talk:Infobox aircraft

2006-06-12T01:01:52Z

Sek:

It would give more control over the infobox if we had the parser installed. http://meta.wikimedia.org/wiki/ParserFunctions#.23if: --[[User Sek Sek]

Es/Communicaciónes

2006-06-11T21:10:41Z

Sek: Adding Transponder

== CTAF/UNICOM ==

Aiports (in the United States) lacking a tower are sometimes served by a UNICOM radio. The UNICOM frequency gives pilots a common channel to communicate their intentions to other pilots in the vicinity of an uncontrolled airport.

It is generally required that pilots of aircraft having radio equipment permitting two-way communications should contact the Airport UNICOM to obtain advisory information and announce their intentions when within ten (10) miles of the Airport. Pilots are also encouraged to maintain a listening watch on the frequency when operating within a ten mile radius of the Airport. All departing aircraft shall announce on the UNICOM their intention and runway to be used for departure.

On intitial contact, pilots report altitude, aircraft type and identification, and location relative to the airport and state their intention, to land or overfly.

Pilots give a status report on downwind, base and final approach.

=== FlightGear UNICOM ===

FlightGear does not implement UNICOM in its current model of ATC radio. You may choose to use the IRC chat room to state intentions if it is not busy, to other Multiplayer aircraft. However, it is not necessary.

== Transponder ==

Wikipedia: [http://en.wikipedia.org/wiki/Transponder_code Transponder]

Template:Infobox aircraft

2006-06-11T20:15:26Z

Sek: gray background

{| class="infobox bordered" align="right" style="background: #eee;border: 1px solid #ccc;width: 25em; text-align: left; font-size: 95%;"
|+ style="font-size: larger;" | '''{{{name}}}'''
|-
|colspan="2" style="text-align:center;"| {{{image|}}}
|-
|colspan="2" style="border-bottom: 1px solid #aaa; text-align:center" |{{{caption|}}}
|-
!style="text-align:right;"|Type
|{{{type}}}
|-
!style="text-align:right;"|Author(s)
|{{{authors}}}
|-
!style="text-align:right;"|FDM
|{{{fdm|}}}
|-
!style="text-align:right;"|Status
|{{{status|}}}
|-
| colspan="2" style="font-size: smaller;" | {{{footnotes|}}}
|}
<noinclude>Comments go here.</noinclude>

Template:Infobox aircraft

2006-06-11T19:47:39Z

Sek: hacked alignment

{| class="infobox bordered" align="right" style="border: 1px solid #ccc;width: 25em; text-align: left; font-size: 95%;"
|+ style="font-size: larger;" | '''{{{name}}}'''
|-
!{{{image| |colspan="2" style="text-align:center;"| [[Image:{{{image}}}|thumb|300px]]}}}
|-
|colspan="2" style="border-bottom: 1px solid #aaa; text-align:center" |{{{caption| {{{caption}}} }}}
|-
|style="text-align:right;"|'''Type'''
|{{{type}}}
|-
|style="text-align:right;"|'''Author(s)'''
|{{{authors}}}
|-
|style="text-align:center;"|{{{fdm| |'''FDM'''|
{{{fdm}}} }}}
|-
|style="text-align:center;"|{{{status| |'''Status'''|
{{{status}}} }}}
|-
| colspan="2" style="font-size: smaller;" | {{{footnotes|}}}
|}
<noinclude>Comments go here.</noinclude>

Talk:New to FlightGear

2006-06-11T18:48:30Z

Sek:

I do not think New to FlightGear should become the main documentation for users, it should just be those things a newbie asks about or needs to know first to get up and running. Not a FAQ of every common question or the start of extensive user docs, it should point to further reading on the issues it touches. --[[User:Sek|Sek]]

Help:Contents

2006-06-11T18:41:45Z

Sek: shortcut: tables

Editing Help : http://en.wikipedia.org/wiki/Help:Editing

Shortcuts:
* [http://meta.wikimedia.org/wiki/Help:Table#Pipe_syntax_tutorial Making Tables]

Wiki Help or requests : hellosimon at gmail com

Realism

2006-06-06T04:20:38Z

Sek: Sources for FGSD object placement

How realistic is FlightGear aircraft and environment? How can I get the most realism out of the FlightGear environment?

== Aircraft ==

Todo: instruments

== Flight ==

Todo: qualities of flight models

== Environment ==

=== Extensive and Accurate World Scenery Data Base ===

* Over 20,000 real world airports included in the full scenery set.
* Correct runway markings and placement, correct runway and approach lighting.
* Taxiways available for many larger airports (even including the green center line lights when appropriate.)
* Sloping runways (runways change elevation like they usually do in real life.)
* Directional airport lighting that smoothly changes intensity as your relative view direction changes.
* World scenery fits on 3 DVD's. (I'm not sure that's a feature or a problem!) But it means we have pretty detailed coverage of the entire world.
* Accurate terrain worldwide, based on the most recently released SRTM terrain data.) 3 arc second resolution (about 90m post spacing) for North and South America, Europe, Asia, Africa, and Australia.
* Scenery includes all vmap0 lakes, rivers, roads, railroads, cities, towns, land cover, etc.
* Nice scenery night lighting with ground lighting concentrated in urban areas (based on real maps) and headlights visible on major highways. This allows for realistic night VFR flying with the ability to spot towns and cities and follow roads.
* Scenery tiles are paged (loaded/unloaded) in a separate thread to minimize the frame rate hit when you need to load new areas.

Real world tower registration data was used to locate towers in the United States. The data was sourced from the United States Federal Communications Comission tower registration database.

Thousands of objects have been added through the [FlightGear Scenery Database http://fgfsdb.stockill.org/].

* 2700+ obstructions added for France (not sure of the source for this obstruction data)

Todo: what are the sources for scenery database? The FAA obstructions data may have been used to populate the scenery database, but I am not sure.

== Weather ==

Todo: weather

FlightGear can periodically download weather (METAR) data. This information is used to influence the environment.

As of FG 0.9.10, for the current METAR station, FG models:

* Visibility for the rendered visual environment is set equal to the current METAR visibility. If the current METAR reports 10 statute mile visibility, the rendered visibility is 10 statute miles.

* If the METAR reports rain, FlightGear renders rain (precipitation).

* If METAR reports a thunderstorm, lightning is rendered and thunder produced through the audio system.

* FG appears to honor METAR dewpoint, "altimeter" or air pressure and reported sea level air pressure. It honors wing direction, speed and gust speed.

'''Notes'''

* Precipitation is modeled, but the graphics require improvement. Sufficient only to indicate rain.

* Lightning is present when a thunderstorm is near, the graphics are a fair representation, but also require improvement.

References

If you want to prove the relationship between FG and METAR, you can open the property browser. Monitor

/environment/metar/max-visibility-m == 9656m

and

/environment/visibility-m == 9656m

The values should be the same. When you press Z/z on the keyboard, you should see the second value change, showing this value controls the rendered visibility.

You can do the same for cloud layers. For example METAR code SCT 10 translates to coverage: scattered, elevation: 10039 and FG automatically sets thickness and transition for the layer.

== Visuals ==

Settings for maximum visual experience and rendering quality.

FlightGear command options:

--enable-horizon-effect
--enable-clouds-3d
--enable-specular-highlight (enabled by default)
--enable-real-weather-fetch
--shading-smooth (default)
--enable-skyblend (default)
--enable-textures (default)
--enable-real-weather-fetch

Sky Blend

This rendering option enables "fog" and haze in the distance. "sky and terrain look realistic"

Smooth Shading

Smooths shading.

Textures

Terrain texturing.

Volumetric (3D) Clouds

This renders clouds with three-dimensional realism.

Geometry/Resolution

This is the resolution the FlightGear window is rendered in. The higher the resolution, the greater the detail.

640x480 blocky and lacking in detail
800x600
1024x768
...
1600 x 1200 very fine detail
and up

Use anti-aliasing if you video card supports and your system can handle the extra load.

Real Weather (METAR)

This downloads current real world weather data into FlightGear from the nearest weather station (METAR report). The data is used to influence the environment. The cloud cover specified in the METAR report will be rendered.

Time

Set the current time for your location. If it's dark in San Francisco, it will be dark in the sim.

Yoke and Rudder Pedals

Rudder pedals add to realistic operation and make it much easier to accurately use the rudder over a twist stick. The yoke is less necessary, but can add to realism.

=== Accurate and Detailed Sky Model ===

FlightGear implements extremely accurate time of day modeling with correctly placed sun, moon, stars, and planets for the specified time and date. FlightGear can track the current computer clock time in order to correctly place the sun, moon, stars, etc. in their current and proper place relative to the earth. If it's dawn in Sydney right now, it's dawn in the sim right now when you locate yourself in virtual Sydney. The sun, moon, stars, and planets all follow their correct courses through the sky. This modeling also correctly takes into account seasonal effects so you have 24 hour days north of the arctic circle in the summer, etc. We also illuminate the correctly placed moon with the correctly placed sun to get the correct phase of the moon for the current time/date, just like in real life.

Frequently asked questions

2006-06-06T03:55:06Z

Sek: Adding MP

''' Feel free to make additions, changes, or corrections.'''

{|
|__TOC__
|}

== The FAQ ==
=== Where can I get the latest version of this FAQ? ===

http://flightgear.org/Docs/FlightGear-FAQ.html

=== Who do I contact if I have comments about this FAQ? ===

Add your comment to this FAQ's discussion page [[Talk:FAQ]]

=== How old is this document? ===

Click the History button in the menu on the left.

=== What other important documentation should I read? ===

* [http://flightgear.org/Docs/getstart/getstart.html Getting Started Guide]
* [[New to FlightGear]]
* Also see the FlightGear/docs-mini/ directory in the source distribution for various other helpful documents.

== Distribution ==

=== Where can I get FlightGear? ===

The official download page is http://flightgear.org/Downloads/. Source code is our primary form of distribution, but precompiled binaries are available for Windows and SGI IRIX.

Alternatively, FlightGear is packaged for Linux by SuSE, Debian (sid), and Mandrake (Cooker) and can be directly installed through those distributions.

=== What is the password for the FTP server? ===

The FTP server uses standard anonymous login procedures. Login with the username "anonymous" and use your email address as the password. Most FTP clients and web browsers will do this automatically for you.

=== Why won't the FTP server let me in with the right login info? ===

This generally means that the server is at it's capacity. You should receive a message saying such, but your FTP client may be hiding it from you. Your options are to keep trying until a slot opens up or try connecting to one of our FTP mirrors listed at http://flightgear.org/mirrors.html.

=== Where can I find the latest development source code? ===

The latest development code is available for everyone through our CVS repository. See http://flightgear.org/cvsResources/ for details.

Otherwise, you can get relatively up-to-date snapshots of the development tree at ftp://flightgear.sourceforge.net/pub/flightgear/Devel/Snapshots/.

=== What is SimGear, and why do I need it? ===

SimGear is a library of supporting code. SimGear is only needed if you plan on compiling FlightGear -- it is not needed to run precompiled binaries. For more information see http://www.simgear.org/.

=== Where can I fly and where do I get the scenery? ===

While the base package only comes with scenery for the San Francisco Bay area, you can currently fly just about anywhere in the world. See the "Additional Scenery" section of http://flightgear.org/Downloads/ for more information or go directly to our graphical downloader at http://flightgear.org/Downloads/world-scenery.html.

Also visit our "Places to Fly" section of the website (http://flightgear.org/Places/) for some help navigating to some awesome locations.

=== Where can I get different 3D models for my plane? ===

While we are working toward building our own 3D models, we have been given permission by several people to convert their models (which where originally intended for use with Microsoft Flight Simulator) to use with FlightGear.

=== How current is the data in FlightGear compared to the real world? ===

We use the same navaid and airport dataset that X-Plane uses. The current dataset can be found in the $FGROOT/Navaids/ and $FGROOT/Airports/ directories. If you have updates or corrections to the dataset, see http://flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html for instructions on contacting the database maintainer.

=== Where is the moving map? ===

A popular moving map display is avaliable under a separate project called Atlas. See http://atlas.sf.net/.

=== Why don't you charge money for this? ===

We could do that, since the initial download is about 25 megabytes. Especially for people who have to pay per-minute charges for internet access, buying a CD is a convenient and possibly cheaper option. Although we offer that service (see the website), we encourage other groups to redistribute it for their users, especially within an operating system distribution which makes installation even faster and easier for new users.

== Compiling ==

=== Why won't FlightGear compile? ===

Well, that depends. First make sure you are using the appropriate versions of FlightGear, SimGear, plib, zlib. If any of the packages are out of sync with the others, compilation may fail.

The FlightGear Downloads page (http://flightgear.org/Downloads/) should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Also ensure that you have some implementation of OpenGL with glut support with the appropriate header files. Linux users with nVidia cards should make sure you have the latest drivers from nVidia. Other Linux users make sure you have Mesa3D (http://mesa3d.org/) and your X server installed correctly. Windows users see http://www.x-plane.com/SYSREQ/v5ibm.html, and Mac users see http://www.x-plane.com/SYSREQ/v5mac.html.

If your problems persist, subscribe to our FlightGear-Users mailing list and let us know what problem you're having. See http://flightgear.org/mail.html for help with this.

=== I'm using RedHat 7, and ...? ===

Update your gcc packages. See http://redhat.com/errata/ to fix it and http://www.gnu.org/software/gcc/gcc-2.96.html for an explanation why.

== Configuring ==

=== How do I install new scenery? ===

The scenery archive files (ie. w100n30.tar.gz) should be untarred into the Scenery/Terrain directory in your $FG_ROOT.

=== How do I setup my joystick(s)? ===

FlightGear should come with a helpful program called `fgjs` that can help configure your joystick. Run `fgjs` and then copy the dot file it created into your home directory or add its contents to your existing rc file.

Also, see the README.Joystick file located in the FlightGear/docs-mini/ directory of the source distribution. This document is mirrored at http://rockfish.net/fg/README.Joystick.

=== What format should my personal .fgfsrc file be in? ===

Your .fgfsrc file should simply be a list of command-line options with one option per line. The file is not an XML file.

If you would rather use an XML configuration file, you can add something like the following in your .fgfsrc

<code> --config=/path/to/my/config.xml</code>

Almost every option corresponds to a property, so you can choose to use whichever method best suits your needs.

== Running ==

=== Why do I get an error loading libopenal.so.0? ===

With the default installation, libopenal.so.0 is installed into /usr/local/lib. You need to ensure that that path is listed in /etc/ld.so.conf, then run `ldconfig`as root.

=== Why do I get "ssgInit called without a valid OpenGL context"? ===

In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

Why do some other GL applications work though? Well, Steve Baker (Mr. PLIB) has explained this on the plib-users list (http://www.geocrawler.com/lists/3/SourceForge/1867/0/6470648/).

=== What happened to the panel, keyboard, etc? ===

The problem is almost certainly that your base package is out of sync with FlightGear. Many configurable parts of FlightGear are defined in XML files contained in the base package.

=== Why doesn't audio work properly under Irix? ===

FlightGear (as of June 2001) uses the Portable Libraries (PLIB) for playing audio. The audio queue implementation of PLIB is far from optimal (in fact it's just wrong). This seems to work on other platforms quite well, but Irix expects things to be programmed properly.

There has been discussion about using OpenAL (http://www.openal.org/) for the next release of both PLIB and FlightGear. Tests show that the OpenAL audio implementation does the job right, meaning that these audio problems should be gone by then. In the mean time it is best to disable audio on Irix completely (by adding --disable-sound either on the command line or to your $HOME/.fgfsrc file).

=== Why is FlightGear so slow? ===

FlightGear supports hardware acceleration, but it seems not to be activated. Make sure you have OpenGL libraries installed and configured properly and make sure you have the latest drivers for your video card.

Linux users: If you are an nVidia user, follow their directions on getting your card working. For most other users, make sure Mesa is installed property and ensure that you have the appropriate kernel device drivers for your card. Most people (and distributions) use modules for their video card device drivers; run `lsmod` as root to see what modules are loaded. You should also make sure that you are loading the appropriate modules in your XF86Config and that your video device section is correct. Now try running an OpenGL application (other than FlightGear) to see how it performs. You can try the gears demo from Mesa or something like Quake3.

=== Why is my SGI machine so slow? ===

First of all, one of the most common mistakes on SGI hardware is to forget to specify --fog-fastest. On most SGI machines the EXP2 shading model isn't hardware supported resulting in frame rates below 1 frame per second (fps).

FlightGear makes extensive use of the OpenGL z-buffer feature,which on most older SGI hardware is only supported in software. This means that the CPU has to do all the z-buffer calculations in addition to the other tasks FlightGear involves (flight dynamics, scenery tracking, pushing commands into the graphics queue, etc). The following features are software rendered on low-end SGI machines (like Indy and Indigo):

* stencil and accumulation buffer
* depth queuing and depth buffering
* fogging, lighting, clipping and transforms
* texturing

This means that running FlightGear with the following options may not even get the desired result:

<code> ./runfgfs --fog-disable --shading-flat --disable-skyblend --disable-textures --disable-clouds --disable-sound --disable-panel --enable-hud --disable-anti-alias-hud </code>

I could even imagine that adding --enable-wireframe doesn't work on these machines (I would be happy to be proven wrong though).

On a machine like O2 the following options give an acceptable result:
<code>./runfgfs --fog-fastest --disable-sound</code>

Since I don't have access to other SGI hardware I can't tell which options would be appropriate for your situation.

=== How do I see the frame rate? ===

There are two ways. One way is to hide the panel without the HUD showing. To hide the panel, use Shift+P; To make the HUD disappear, use H. The second way is to use the alternative HUD by Shift+I (Use I to switch back).
=== Stuck upside down after "crash"? ===

In his infinite wisdom the FlightGear Grand Master decided that planes were to valuable to allow them to be destroyed by novice pilots who seemed to crash a lot. The fact that nobody has bothered to model crashes may have something to do with it too. :-)

The result of this as you have noticed is that with a little practice an ingenuity you can trim the ship to fly inverted along the ground.

The quick answer is to hit Ctrl+U (with the default key bindings) to warp the plane up 1000ft.

For the stubborn people out there: The trick to learn is to roll back to normal (non inverted) do this by nursing the elevator to get to about 500 feet or so and use the ailerons to snap roll 180*. This is all good avionics except for the plane not destroying itself. Remember the controls work in reverse when you are inverted and keep that airspeed up!!!

=== Why does FlightGear die on startup saying "time zone reading failed"? ===

This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files.

== Hacking ==

=== What language is FlightGear written in? ===

Mostly C++ with some supporting C code that's primary contained within SimGear.

=== How do I design a flight dynamics model for a new aircraft? ===

To define an aircraft for FlightGear's primary FDM (JSBSIM), see http://jsbsim.sf.net/.

If you want a simpler FDM to work with, try your hand at YASim, an alternative FDM. For an guide on creating a YASim aircraft, look in the FlightGear base package for Aircraft-yasim/README.yasim.

=== How do I import planes from Microsoft Flight Simulator? ===

You can import the 3D model and textures, but the flight dynamics (the .AIR file) must be completely redone for FlightGear.

If you wish to import a model made with gmax, you will need to convert it to .MDL format using Microsoft's MakeMDL SDK which is available at http://zone.msn.com/flightsim/FS02DevDeskSDK08.asp.

=== How do I import BGL scenery from Microsoft Flight Simulator? ===

See http://chiangt.virtualave.net/BGL/bgl_index.html.

=== How do I design or modify a panel? ===

See the README.xmlpanel file located in the FlightGear/docs-mini/ directory of the source distribution. This document is mirrored at http://rockfish.net/fg/README.xmlpanel.

=== How do I place objects, like buildings, into FlightGear? ===

First, ensure that you have v0.7.7 or later, the scenery files where you plan to place the object, the actual model, and the longitude and latitude where you plan to place the object.

Now get the altitude for your point. If you don't want to calculate this yourself, start FlightGear at your location and take note of the altitude. Here's an example command:

fgfs --lat=45.50 --lon=-75.73 2>&1 | tee fgfs.log

The altitude is probably in feet, so divide the starting altitude by 3.28.

Search the output log file for the first occurrence of the string "Loading tile" and take note of the filename. In the above example, the output line looks like:

Loading tile /usr/local/Scenery/w080n40/w076n45/1712601

Copy a 3D model in a format that Plib understands to the same directory as the tile file. Edit the text file in that directory consisting of the tile name with the extension ".stg". The file will already exist if there is an airport on the tile; otherwise, you can create it from scratch. In our example, the filename is:

<code>/usr/local/Scenery/w080n40/w076n45/1712601.stg</code>

At the end of the file, add a new entry for your object, consisting of the word "OBJECT_STATIC" followed by the model name, the longitude in degrees, the latitude in degrees, the altitude in meters, and the heading in degrees. In our example the line looks like:

OBJECT_STATIC Towerax.ac -75.73 45.40 60 0

Save the changes to the .stg file, restart FlightGear, and enjoy.

NOTE: The above information was taken from the following mailing list post: http://www.geocrawler.com/archives/3/11854/2001/6/0/5991409/. See that page if this one doesn't make sense.

An alternative approach using PPE is described at http://mail.flightgear.org/pipermail/flightgear-devel/2001-December/002239.html by Norman Vine.

=== Where can I learn 3D programming and how do I get involved? ===

Contributing to the 2D panel doesn't require any coding at all, just a minimal knowledge of XML syntax (i.e. five minutes' worth) and good skills with drawing and/or paint programs. Every instrument on the current panel, with the partial exception of the magnetic compass, is defined entirely in XML with no custom C++ code. If you want to get started, take a look at John Check's excellent intro (http://rockfish.net/fg/README.xmlpanel).

Likewise, if you want to create a 3D cockpit for FlightGear, or to create buildings, external aircraft models, etc., your help is *desperately* needed. The only rule is to go easy on the triangles -- a model with 50,000 triangles probably won't be usable in FlightGear, and one with 5,000 triangles, only marginally. If you can design a nice 3D cockpit interior for a Cessna 172 (for example) in a 3D design program such as ac3D or ppe, we have coders who will be happy to add the support code in the C++.

If, on the other hand, you really want to get your hands dirty with C++ coding, you'll have to buy a good OpenGL book eventually. However, FlightGear uses a high-level library, plib, that hides most of the details of OpenGL. To get started with 3D C++ coding, you can take a look at the plib documentation and learn only as much OpenGL as you need, when you need it.

=== How do I add an airport? ===

You can add your airport to the $FGROOT/Airports/default.apt.gz file, but to get the airport to show up visually, you will have to rebuild the scenery around the airport. The format of the default.apt file is documented at http://flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html.

=== How do I generate my own scenery? ===

Yes, though it can be a difficult task. FlightGear's scenery generation is handled by a sister project, TerraGear. For more details, see http://terragear.org/.

== Flying ==

=== Where can I learn about instrument flying and navigation? ===

http://www.navfltsm.addr.com/ is a very good site for learning techniques for navigation.

Also see http://www.monmouth.com/~jsd/how/. This link is dead.

Please see [[Understanding Navigation]]

=== What is the difference between Aileron and Rudder? ===

There is a bit of info on aileron vs. rudder here: http://www.monmouth.com/~jsd/how/.

=== Is there support for multi-player flying? ===

Yes. Both the Windows and *nix versions of FlightGear are capable of multi-player flying on FlightGear servers.

Wiki: [http://wiki.flightgear.org/flightgear_wiki/index.php?title=Multiplayer_Howto Multiplayer_Howto]

A map showing players aircfart online in real time is available:
[http://pigeond.net/flightgear/fg_server_map.html FlightGear Online Server Map]

=== Is there support for any military scenarios like dog fighting or bomb dropping? ===

No, not at this time. Most of our developers are primarily interested and focused on civilian aviation. We aren't explicitly excluding these features -- we just haven't had anyone who seriously wanted to develop these areas.

== FlightGear v0.7.6 ==

=== Why do I get an error in viewer.cxx about `exit' being undeclared? ===

This error cropped up after the release of v0.7.6. To fix the problem, add "#include <stdlib.h>" to the top of viewer.cxx.

Frequently asked questions

2006-06-06T03:50:50Z

Sek: /* Where can I learn about instrument flying and navigation? */

''' Feel free to make additions, changes, or corrections.'''

{|
|__TOC__
|}

== The FAQ ==
=== Where can I get the latest version of this FAQ? ===

http://flightgear.org/Docs/FlightGear-FAQ.html

=== Who do I contact if I have comments about this FAQ? ===

Add your comment to this FAQ's discussion page [[Talk:FAQ]]

=== How old is this document? ===

Click the History button in the menu on the left.

=== What other important documentation should I read? ===

* [http://flightgear.org/Docs/getstart/getstart.html Getting Started Guide]
* [[New to FlightGear]]
* Also see the FlightGear/docs-mini/ directory in the source distribution for various other helpful documents.

== Distribution ==

=== Where can I get FlightGear? ===

The official download page is http://flightgear.org/Downloads/. Source code is our primary form of distribution, but precompiled binaries are available for Windows and SGI IRIX.

Alternatively, FlightGear is packaged for Linux by SuSE, Debian (sid), and Mandrake (Cooker) and can be directly installed through those distributions.

=== What is the password for the FTP server? ===

The FTP server uses standard anonymous login procedures. Login with the username "anonymous" and use your email address as the password. Most FTP clients and web browsers will do this automatically for you.

=== Why won't the FTP server let me in with the right login info? ===

This generally means that the server is at it's capacity. You should receive a message saying such, but your FTP client may be hiding it from you. Your options are to keep trying until a slot opens up or try connecting to one of our FTP mirrors listed at http://flightgear.org/mirrors.html.

=== Where can I find the latest development source code? ===

The latest development code is available for everyone through our CVS repository. See http://flightgear.org/cvsResources/ for details.

Otherwise, you can get relatively up-to-date snapshots of the development tree at ftp://flightgear.sourceforge.net/pub/flightgear/Devel/Snapshots/.

=== What is SimGear, and why do I need it? ===

SimGear is a library of supporting code. SimGear is only needed if you plan on compiling FlightGear -- it is not needed to run precompiled binaries. For more information see http://www.simgear.org/.

=== Where can I fly and where do I get the scenery? ===

While the base package only comes with scenery for the San Francisco Bay area, you can currently fly just about anywhere in the world. See the "Additional Scenery" section of http://flightgear.org/Downloads/ for more information or go directly to our graphical downloader at http://flightgear.org/Downloads/world-scenery.html.

Also visit our "Places to Fly" section of the website (http://flightgear.org/Places/) for some help navigating to some awesome locations.

=== Where can I get different 3D models for my plane? ===

While we are working toward building our own 3D models, we have been given permission by several people to convert their models (which where originally intended for use with Microsoft Flight Simulator) to use with FlightGear.

=== How current is the data in FlightGear compared to the real world? ===

We use the same navaid and airport dataset that X-Plane uses. The current dataset can be found in the $FGROOT/Navaids/ and $FGROOT/Airports/ directories. If you have updates or corrections to the dataset, see http://flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html for instructions on contacting the database maintainer.

=== Where is the moving map? ===

A popular moving map display is avaliable under a separate project called Atlas. See http://atlas.sf.net/.

=== Why don't you charge money for this? ===

We could do that, since the initial download is about 25 megabytes. Especially for people who have to pay per-minute charges for internet access, buying a CD is a convenient and possibly cheaper option. Although we offer that service (see the website), we encourage other groups to redistribute it for their users, especially within an operating system distribution which makes installation even faster and easier for new users.

== Compiling ==

=== Why won't FlightGear compile? ===

Well, that depends. First make sure you are using the appropriate versions of FlightGear, SimGear, plib, zlib. If any of the packages are out of sync with the others, compilation may fail.

The FlightGear Downloads page (http://flightgear.org/Downloads/) should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Also ensure that you have some implementation of OpenGL with glut support with the appropriate header files. Linux users with nVidia cards should make sure you have the latest drivers from nVidia. Other Linux users make sure you have Mesa3D (http://mesa3d.org/) and your X server installed correctly. Windows users see http://www.x-plane.com/SYSREQ/v5ibm.html, and Mac users see http://www.x-plane.com/SYSREQ/v5mac.html.

If your problems persist, subscribe to our FlightGear-Users mailing list and let us know what problem you're having. See http://flightgear.org/mail.html for help with this.

=== I'm using RedHat 7, and ...? ===

Update your gcc packages. See http://redhat.com/errata/ to fix it and http://www.gnu.org/software/gcc/gcc-2.96.html for an explanation why.

== Configuring ==

=== How do I install new scenery? ===

The scenery archive files (ie. w100n30.tar.gz) should be untarred into the Scenery/Terrain directory in your $FG_ROOT.

=== How do I setup my joystick(s)? ===

FlightGear should come with a helpful program called `fgjs` that can help configure your joystick. Run `fgjs` and then copy the dot file it created into your home directory or add its contents to your existing rc file.

Also, see the README.Joystick file located in the FlightGear/docs-mini/ directory of the source distribution. This document is mirrored at http://rockfish.net/fg/README.Joystick.

=== What format should my personal .fgfsrc file be in? ===

Your .fgfsrc file should simply be a list of command-line options with one option per line. The file is not an XML file.

If you would rather use an XML configuration file, you can add something like the following in your .fgfsrc

<code> --config=/path/to/my/config.xml</code>

Almost every option corresponds to a property, so you can choose to use whichever method best suits your needs.

== Running ==

=== Why do I get an error loading libopenal.so.0? ===

With the default installation, libopenal.so.0 is installed into /usr/local/lib. You need to ensure that that path is listed in /etc/ld.so.conf, then run `ldconfig`as root.

=== Why do I get "ssgInit called without a valid OpenGL context"? ===

In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

Why do some other GL applications work though? Well, Steve Baker (Mr. PLIB) has explained this on the plib-users list (http://www.geocrawler.com/lists/3/SourceForge/1867/0/6470648/).

=== What happened to the panel, keyboard, etc? ===

The problem is almost certainly that your base package is out of sync with FlightGear. Many configurable parts of FlightGear are defined in XML files contained in the base package.

=== Why doesn't audio work properly under Irix? ===

FlightGear (as of June 2001) uses the Portable Libraries (PLIB) for playing audio. The audio queue implementation of PLIB is far from optimal (in fact it's just wrong). This seems to work on other platforms quite well, but Irix expects things to be programmed properly.

There has been discussion about using OpenAL (http://www.openal.org/) for the next release of both PLIB and FlightGear. Tests show that the OpenAL audio implementation does the job right, meaning that these audio problems should be gone by then. In the mean time it is best to disable audio on Irix completely (by adding --disable-sound either on the command line or to your $HOME/.fgfsrc file).

=== Why is FlightGear so slow? ===

FlightGear supports hardware acceleration, but it seems not to be activated. Make sure you have OpenGL libraries installed and configured properly and make sure you have the latest drivers for your video card.

Linux users: If you are an nVidia user, follow their directions on getting your card working. For most other users, make sure Mesa is installed property and ensure that you have the appropriate kernel device drivers for your card. Most people (and distributions) use modules for their video card device drivers; run `lsmod` as root to see what modules are loaded. You should also make sure that you are loading the appropriate modules in your XF86Config and that your video device section is correct. Now try running an OpenGL application (other than FlightGear) to see how it performs. You can try the gears demo from Mesa or something like Quake3.

=== Why is my SGI machine so slow? ===

First of all, one of the most common mistakes on SGI hardware is to forget to specify --fog-fastest. On most SGI machines the EXP2 shading model isn't hardware supported resulting in frame rates below 1 frame per second (fps).

FlightGear makes extensive use of the OpenGL z-buffer feature,which on most older SGI hardware is only supported in software. This means that the CPU has to do all the z-buffer calculations in addition to the other tasks FlightGear involves (flight dynamics, scenery tracking, pushing commands into the graphics queue, etc). The following features are software rendered on low-end SGI machines (like Indy and Indigo):

* stencil and accumulation buffer
* depth queuing and depth buffering
* fogging, lighting, clipping and transforms
* texturing

This means that running FlightGear with the following options may not even get the desired result:

<code> ./runfgfs --fog-disable --shading-flat --disable-skyblend --disable-textures --disable-clouds --disable-sound --disable-panel --enable-hud --disable-anti-alias-hud </code>

I could even imagine that adding --enable-wireframe doesn't work on these machines (I would be happy to be proven wrong though).

On a machine like O2 the following options give an acceptable result:
<code>./runfgfs --fog-fastest --disable-sound</code>

Since I don't have access to other SGI hardware I can't tell which options would be appropriate for your situation.

=== How do I see the frame rate? ===

There are two ways. One way is to hide the panel without the HUD showing. To hide the panel, use Shift+P; To make the HUD disappear, use H. The second way is to use the alternative HUD by Shift+I (Use I to switch back).
=== Stuck upside down after "crash"? ===

In his infinite wisdom the FlightGear Grand Master decided that planes were to valuable to allow them to be destroyed by novice pilots who seemed to crash a lot. The fact that nobody has bothered to model crashes may have something to do with it too. :-)

The result of this as you have noticed is that with a little practice an ingenuity you can trim the ship to fly inverted along the ground.

The quick answer is to hit Ctrl+U (with the default key bindings) to warp the plane up 1000ft.

For the stubborn people out there: The trick to learn is to roll back to normal (non inverted) do this by nursing the elevator to get to about 500 feet or so and use the ailerons to snap roll 180*. This is all good avionics except for the plane not destroying itself. Remember the controls work in reverse when you are inverted and keep that airspeed up!!!

=== Why does FlightGear die on startup saying "time zone reading failed"? ===

This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files.

== Hacking ==

=== What language is FlightGear written in? ===

Mostly C++ with some supporting C code that's primary contained within SimGear.

=== How do I design a flight dynamics model for a new aircraft? ===

To define an aircraft for FlightGear's primary FDM (JSBSIM), see http://jsbsim.sf.net/.

If you want a simpler FDM to work with, try your hand at YASim, an alternative FDM. For an guide on creating a YASim aircraft, look in the FlightGear base package for Aircraft-yasim/README.yasim.

=== How do I import planes from Microsoft Flight Simulator? ===

You can import the 3D model and textures, but the flight dynamics (the .AIR file) must be completely redone for FlightGear.

If you wish to import a model made with gmax, you will need to convert it to .MDL format using Microsoft's MakeMDL SDK which is available at http://zone.msn.com/flightsim/FS02DevDeskSDK08.asp.

=== How do I import BGL scenery from Microsoft Flight Simulator? ===

See http://chiangt.virtualave.net/BGL/bgl_index.html.

=== How do I design or modify a panel? ===

See the README.xmlpanel file located in the FlightGear/docs-mini/ directory of the source distribution. This document is mirrored at http://rockfish.net/fg/README.xmlpanel.

=== How do I place objects, like buildings, into FlightGear? ===

First, ensure that you have v0.7.7 or later, the scenery files where you plan to place the object, the actual model, and the longitude and latitude where you plan to place the object.

Now get the altitude for your point. If you don't want to calculate this yourself, start FlightGear at your location and take note of the altitude. Here's an example command:

fgfs --lat=45.50 --lon=-75.73 2>&1 | tee fgfs.log

The altitude is probably in feet, so divide the starting altitude by 3.28.

Search the output log file for the first occurrence of the string "Loading tile" and take note of the filename. In the above example, the output line looks like:

Loading tile /usr/local/Scenery/w080n40/w076n45/1712601

Copy a 3D model in a format that Plib understands to the same directory as the tile file. Edit the text file in that directory consisting of the tile name with the extension ".stg". The file will already exist if there is an airport on the tile; otherwise, you can create it from scratch. In our example, the filename is:

<code>/usr/local/Scenery/w080n40/w076n45/1712601.stg</code>

At the end of the file, add a new entry for your object, consisting of the word "OBJECT_STATIC" followed by the model name, the longitude in degrees, the latitude in degrees, the altitude in meters, and the heading in degrees. In our example the line looks like:

OBJECT_STATIC Towerax.ac -75.73 45.40 60 0

Save the changes to the .stg file, restart FlightGear, and enjoy.

NOTE: The above information was taken from the following mailing list post: http://www.geocrawler.com/archives/3/11854/2001/6/0/5991409/. See that page if this one doesn't make sense.

An alternative approach using PPE is described at http://mail.flightgear.org/pipermail/flightgear-devel/2001-December/002239.html by Norman Vine.

=== Where can I learn 3D programming and how do I get involved? ===

Contributing to the 2D panel doesn't require any coding at all, just a minimal knowledge of XML syntax (i.e. five minutes' worth) and good skills with drawing and/or paint programs. Every instrument on the current panel, with the partial exception of the magnetic compass, is defined entirely in XML with no custom C++ code. If you want to get started, take a look at John Check's excellent intro (http://rockfish.net/fg/README.xmlpanel).

Likewise, if you want to create a 3D cockpit for FlightGear, or to create buildings, external aircraft models, etc., your help is *desperately* needed. The only rule is to go easy on the triangles -- a model with 50,000 triangles probably won't be usable in FlightGear, and one with 5,000 triangles, only marginally. If you can design a nice 3D cockpit interior for a Cessna 172 (for example) in a 3D design program such as ac3D or ppe, we have coders who will be happy to add the support code in the C++.

If, on the other hand, you really want to get your hands dirty with C++ coding, you'll have to buy a good OpenGL book eventually. However, FlightGear uses a high-level library, plib, that hides most of the details of OpenGL. To get started with 3D C++ coding, you can take a look at the plib documentation and learn only as much OpenGL as you need, when you need it.

=== How do I add an airport? ===

You can add your airport to the $FGROOT/Airports/default.apt.gz file, but to get the airport to show up visually, you will have to rebuild the scenery around the airport. The format of the default.apt file is documented at http://flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html.

=== How do I generate my own scenery? ===

Yes, though it can be a difficult task. FlightGear's scenery generation is handled by a sister project, TerraGear. For more details, see http://terragear.org/.

== Flying ==

=== Where can I learn about instrument flying and navigation? ===

http://www.navfltsm.addr.com/ is a very good site for learning techniques for navigation.

Also see http://www.monmouth.com/~jsd/how/. This link is dead.

Please see [[Understanding Navigation]]

=== What is the difference between Aileron and Rudder? ===

There is a bit of info on aileron vs. rudder here: http://www.monmouth.com/~jsd/how/.

=== Is there support for multi-player flying? ===

We have an initial stab at this that is incomplete and only seems to work under Linux. We'd love to find someone to pick up the slack here and develop this further. Specifically, plib now has some low level networking support for mult-player games. It would also be nice to develop support for the DIS protocol.

=== Is there support for any military scenarios like dog fighting or bomb dropping? ===

No, not at this time. Most of our developers are primarily interested and focused on civilian aviation. We aren't explicitly excluding these features -- we just haven't had anyone who seriously wanted to develop these areas.

== FlightGear v0.7.6 ==

=== Why do I get an error in viewer.cxx about `exit' being undeclared? ===

This error cropped up after the release of v0.7.6. To fix the problem, add "#include <stdlib.h>" to the top of viewer.cxx.

Realism

2006-06-05T02:40:30Z

Sek: Various realism recommendations

How realistic is FlightGear aircraft and environment? How can I get the most realism out of the FlightGear environment?

== Aircraft ==

Todo: instruments

== Flight ==

Todo: qualities of flight models

== Environment ==

=== Extensive and Accurate World Scenery Data Base ===

* Over 20,000 real world airports included in the full scenery set.
* Correct runway markings and placement, correct runway and approach lighting.
* Taxiways available for many larger airports (even including the green center line lights when appropriate.)
* Sloping runways (runways change elevation like they usually do in real life.)
* Directional airport lighting that smoothly changes intensity as your relative view direction changes.
* World scenery fits on 3 DVD's. (I'm not sure that's a feature or a problem!) But it means we have pretty detailed coverage of the entire world.
* Accurate terrain worldwide, based on the most recently released SRTM terrain data.) 3 arc second resolution (about 90m post spacing) for North and South America, Europe, Asia, Africa, and Australia.
* Scenery includes all vmap0 lakes, rivers, roads, railroads, cities, towns, land cover, etc.
* Nice scenery night lighting with ground lighting concentrated in urban areas (based on real maps) and headlights visible on major highways. This allows for realistic night VFR flying with the ability to spot towns and cities and follow roads.
* Scenery tiles are paged (loaded/unloaded) in a separate thread to minimize the frame rate hit when you need to load new areas.

== Weather ==

Todo: weather

FlightGear can periodically download weather (METAR) data. This information is used to influence the environment.

As of FG 0.9.10, for the current METAR station, FG models:

* Visibility for the rendered visual environment is set equal to the current METAR visibility. If the current METAR reports 10 statute mile visibility, the rendered visibility is 10 statute miles.

* If the METAR reports rain, FlightGear renders rain (precipitation).

* If METAR reports a thunderstorm, lightning is rendered and thunder produced through the audio system.

* FG appears to honor METAR dewpoint, "altimeter" or air pressure and reported sea level air pressure. It honors wing direction, speed and gust speed.

'''Notes'''

* Precipitation is modeled, but the graphics require improvement. Sufficient only to indicate rain.

* Lightning is present when a thunderstorm is near, the graphics are a fair representation, but also require improvement.

References

If you want to prove the relationship between FG and METAR, you can open the property browser. Monitor

/environment/metar/max-visibility-m == 9656m

and

/environment/visibility-m == 9656m

The values should be the same. When you press Z/z on the keyboard, you should see the second value change, showing this value controls the rendered visibility.

You can do the same for cloud layers. For example METAR code SCT 10 translates to coverage: scattered, elevation: 10039 and FG automatically sets thickness and transition for the layer.

== Visuals ==

Settings for maximum visual experience and rendering quality.

FlightGear command options:

--enable-horizon-effect
--enable-clouds-3d
--enable-specular-highlight (enabled by default)
--enable-real-weather-fetch
--shading-smooth (default)
--enable-skyblend (default)
--enable-textures (default)
--enable-real-weather-fetch

Sky Blend

This rendering option enables "fog" and haze in the distance. "sky and terrain look realistic"

Smooth Shading

Smooths shading.

Textures

Terrain texturing.

Volumetric (3D) Clouds

This renders clouds with three-dimensional realism.

Geometry/Resolution

This is the resolution the FlightGear window is rendered in. The higher the resolution, the greater the detail.

640x480 blocky and lacking in detail
800x600
1024x768
...
1600 x 1200 very fine detail
and up

Use anti-aliasing if you video card supports and your system can handle the extra load.

Real Weather (METAR)

This downloads current real world weather data into FlightGear from the nearest weather station (METAR report). The data is used to influence the environment. The cloud cover specified in the METAR report will be rendered.

Time

Set the current time for your location. If it's dark in San Francisco, it will be dark in the sim.

Yoke and Rudder Pedals

Rudder pedals add to realistic operation and make it much easier to accurately use the rudder over a twist stick. The yoke is less necessary, but can add to realism.

=== Accurate and Detailed Sky Model ===

FlightGear implements extremely accurate time of day modeling with correctly placed sun, moon, stars, and planets for the specified time and date. FlightGear can track the current computer clock time in order to correctly place the sun, moon, stars, etc. in their current and proper place relative to the earth. If it's dawn in Sydney right now, it's dawn in the sim right now when you locate yourself in virtual Sydney. The sun, moon, stars, and planets all follow their correct courses through the sky. This modeling also correctly takes into account seasonal effects so you have 24 hour days north of the arctic circle in the summer, etc. We also illuminate the correctly placed moon with the correctly placed sun to get the correct phase of the moon for the current time/date, just like in real life.

Troubleshooting problems

2006-06-05T02:15:26Z

Sek: adding usb joystick troubleshooting

Hi, you were probably referred to this page because you are having problems getting FlightGear to work for you. This page is dedicated to helping you address any issues you may face.

You need to realize that, in order for other people to be able to help you sorting out any FlightGear related problems, you need to provide certain information about your platform and the nature of the problem you are encountering. This is due to the fact that we don't have access to your machine and thus cannot see what you are (or were) doing, so you need to be our eyes and ears. Also, it is important that you try not to mix up different symptomps that may not necessarily be related with each other.

Even if some of the information we ask for is not always necessarily required in order to fix a particular issue, it can tremendously simplify and shorten the troubleshooting process, for example by allowing us to exclude certain problem sources. So, if at all possible please try to comply with our requests, if anything is unclear or you don't know how to obtain certain information please ask for clarification rather than ignoring a particular request.

'''In general, you should always try to provide the following information in your requests/reports:'''

'''Hardware Specs:'''

* CPU
* RAM
* SOUND CARD
* GRAPHICS CARD

'''Software Specs:'''

* OS (Version, Kernel, Servicepacks etc)
* any other software that may be running while FlightGear is running (i.e. antivirus tools)
* driver versions for relevant hardware (graphics, sound, input hardware)

'''Input Hardware:'''

* KEYBOARD (language/country encoding)
* MOUSE
* JOYSTICK
* YOKE
* PEDALS

'''FlightGear:'''

* version of FlightGear you are trying to get to work for you
* where you obtained it from
* in what format you obtained it (executables/binaries vs. source code)
* if you built it yourself, how you did do that (compiler,flags etc)
* how and where you installed FlightGear
* how you are starting FlightGear (GUI frontend vs. shell/console)
* startup parameters you use
* runtime settings you use
* any console messages (warnings and errors) you may see
* whether the same machine/OS has previously been used to run FlightGear successfully, if so what version of FlightGear
* if FlightGear works properly using the default settings

If you experience any problems during flight, please save the active flight and make the saved file available for further investigation (i.e. in order to post it to a forum or send it to a mailing list)

'''If you are facing scenery-related problems (i.e. no scenery visible), please also try to provide the following information:'''

* whether FlightGear's default airport KSFO (San Francisco) works for you or not
* whether you can see any scenery (i.e. runways) from the cockpit view
* whether you can see any scenery (i.e. runways) from non-cockpit views (i.e. outside view: using the v/V key to cycle through all views)
* what daytime settings you are using and whether changing this setting has any effect
* which tiles you downloaded, and from where-including the size of each file or its MD5 sum
* whether you are able to open the downloaded scenery tiles using an archiver such as WinZip, PowerZIP, IzArc
* which areas/airports specifically are causing trouble, and what you are (not) seeing (i.e. water?)
* how exactly you installed the scenery tiles, did you extract the scenery tiles properly?
* the location of your FlightGear base package (data) folder
* if you are using the FG_ROOT and FG_SCENERY variables, their contents
* the contents of the folder under $FG_ROOT/Terrain
* ICAO code and runway of airport, as well as your actual longitude/latitude retrieved from the property browser: /sim/position/longitude-deg & /sim/position/latitude-deg
* the value of /sim/rendering/draw-otw using the property browser (needs to be true)
* any screenshots depicting the problem

'''If you are facing problems related to your input hardware, please also try to provide the following information:'''

* the nature of your problem
* whether the symptoms appear to be in any way specific to the aircraft you are using
* what input hardware you are trying to use with FlightGear
* whether the corresponding hardware works under the same OS with other applications
* how the input hardware is connected to your machine
* if there is any other input hardware connected to your machine
* if the symptoms disappear when you disconnect either single components of your input hardware or all of it together

TODO: we need to evaluate the forum and mailing discussions of the last 2-3 months in order to determine which issues were the most frequently reported ones (i.e. FreeGLUT, RenderTexture,3D Clouds,non calibrated hardware etc), so that we can summarize these issues here, and possibly even directly provide solutions later on.

== Solutions ==

=== USB Joystick Fails to Work ===

FlightGear is designed to recognize automatically any USB joystick that it is aware of (has a configuration on file for it). Configuration for USB joysticks is located in the Inputs folder. For example:

Input/Saitek/X45.xml

The name reported by the joystick through the hardware of your system must match the name specified in the configuration file. If the stick identifies itself as

Saitek Saitek X45 Flight Control Stick

but the configuration file specifies

Saitek X45 USB Flight Stick

Flight Gear will fail to recognize it.

This happens with some frequency. It has been known for the same stick in a manufacturer's line to report different identifier strings. If you encounter a problem getting your usb stick to be recognized by FlightGear, it is helpful to first check to see

* a configuration file matching the name of your stick exists
* the configuration joystick name matches the name the stick actually reports to your computer

Realism

2006-06-05T02:07:32Z

Sek: /* Weather */

Realism

2006-06-05T01:55:35Z

Sek: /* Weather */

Realism

2006-06-05T01:39:24Z

Sek: /* Weather */

Realism

2006-06-05T01:38:14Z

Sek: /* Weather */

Realism

2006-06-05T01:36:02Z

Sek: adding METAR realims notes

Suggested Flights

2006-06-04T23:30:16Z

Sek: /* Chesapeake Bay-Bridge Tunnel Sightseeing */

== San Francisco ==

=== Half Moon Bay ===
Here's a suggested flight, after you do a cvs update on the base package to get the latest SF scenery. Start at Half Moon Bay, Runway 30, with 32km visibility:

'''fgfs --airport=KHAF --runway=30 --visibility=32000'''

Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to KSFO for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as Flight Gear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.

== Virginia Eastern Shore ==
===Chesapeake Bay-Bridge Tunnel Sightseeing===

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge (Note the bridge is not modeled by FlightGear...but I hope to work up one eventually). Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.

Suggested Flights

2006-06-04T23:26:53Z

Sek: Added KTGI to KORF flight.

== San Francisco ==

=== Half Moon Bay ===
Here's a suggested flight, after you do a cvs update on the base package to get the latest SF scenery. Start at Half Moon Bay, Runway 30, with 32km visibility:

'''fgfs --airport=KHAF --runway=30 --visibility=32000'''

Takeoff in the C172 and climb to 1000 feet, then continue north over the water, near the shoreline. Look out the right window frequently. Fly up the coast, overfly the Golden Gate Bridge, continue around the top of the peninsula past downtown SF, then fly on to KSFO for a landing. We now have lots to see.

If you cannot see the runway in the default 172, you must be flying too high or too slowly. You can start by practicing a bit with a good setup:

'''fgfs --offset-distance=1.5 --altitude=500 --vc=70'''

As soon as Flight Gear starts, cut the power to 1500 rpm and drop two notches of flap. Maintain 70 kt. Now, pick your landing spot (a bit down the runway) and try to hold it in the same spot on your windshield. If your landing spot starts moving down, you are too high, and should cut another 100 rpm; if it starts moving up, you are too low, and should add another 100 rpm. Adjust the nose to keep your speed at 70 kt all the way down until you're right above the numbers, then cut power to idle, drop the last notch of flaps, flare, and land.

== Virginia Eastern Shore ==
===Chesapeake Bay-Bridge Tunnel Sightseeing===

Take a short VFR trip from Tangier Island to view the famous Chesapeake Bay Bridge-Tunnel connecting Cape Charles to Cape Henry. Depart historic Tangier Island (KTGI) situated in the Chesapeake Bay and land at Norfolk International Airport (KORF), Norfolk, Virginia. The scenic character of the flight is enhanced by leaving the island at dusk. The flight is both scenic and challenging. Frequently, when flying with real weather, you will have a steady wind blowing across the bay. Starting out quiet Tangier and arriving at busy, glittering Norfolk International (KORF) gives the flight some contrast.

'''fgfs --airport=KTGI --runway=20 --timeofday=dusk'''

Before leaving Tangier: Set your altimeter to the prevailing barometric temperature. Set your communications radio to the Norfolk Intl. (KORF) ATIS frequency of 127.150 MHz to listen for weather reports in the destination area. Set your navigation radio to 112.20 MHz to pick up the Cape Charles (CCV) VOR. Set your heading bug to the runway heading, 200.

Takeoff straight, flying the runway heading. Climb to 2000ft and maintain.

Shortly, you should see the VOR assigned to NAV1 display receive a steady signal (the OFF flag will disappear). The DME should also settle down and display the distance to the Cape Charles VOR station. The flight to CCV will be about 26 nautical miles. As you fly, it will show your airspeed and time to arrival. It should take about ten minutes.

Turn the OBS knob until the VOR displays the TO flag and 190 degrees, the heading you should now turn to.

Fly south from Tangier, crossing an expanse of water, about ten miles until you see the Virginia Eastern Shore. You'll come upon the grass airstrip of Chance (VA89) a few minutes out from Tangier. Beyond are two flashing tower beacons. You may catch a glimpse of Weirwood/Kellam (W08) on the ocean shore, recognizable by two crossing dirt strips.

If you look carefully, you may see the little white building that is the Cape Charles VOR station. As you fly over VOR the flag will change from TO to FROM and the needle will deflect. Do not try to follow the needle. Wait until you are past the VOR. As you cross the VOR station, you should see a highway slanting across your path toward the south west. Turn to follow this highway. You'll come across a lone tower with beacon along the roadside. You'll see an access road stretching from the tower complex to the main road.

If the sky conditions permit, you may try your hand at wayfinding by following the road. If visiblity is poor, set the VOR to 180 degrees to parallel the road to the end of the peninsula. Or you can continue to fly outbound from the VOR on 190 by maintaining the same heading. The VOR needle should return to center with the FROM flag displaying. This will put you west of the bridge with a good view and the option to turn towards KORF near the initial approach fix. If you follow the highway you will need to overfly the airport, but if you stay on the 190 heading, you will be in a position to make a straight in landing.

As you fly down the peninsula you'll pass Cherrystone, Eagle's Nest, Scott and Bull Farm grass airstrips. Bull Farm is the last strip before the mouth of the Chesapeake. Just past Scott Farm you should see the first glimmer of the northern leg of the bridge. The grass strips can be very difficult to see.

As you reach the end of the peninsula, be careful to avoid the tower on Fisherman's Island at the north end of the north leg of the bridge. Next comes the north middle leg. Turn right a few degrees to follow the south middle leg. Watch as the deck plunges beneath the waves to allow ships to navigate the north and south channels.

As Cape Henry approaches, you'll see the Norfolk International airport to the right and the southern leg of the bridge touching the shore.

If you intend to land at KORF, you will want to start your approach soon. Otherwise, you may continue to follow the bridge to the end. Make the approach to KORF by contacting the tower for vectors. Or use the ILS.

This is a good flight to practice VOR flying on. It is a very straight flight path to the VOR requiring little adjustment and there are no other VORs in the area to confuse you.

Talk:Comper Swift

2006-06-03T03:15:44Z

Sek:

I have mixed feelings about identifying the author and talking in the first person in these manuals, but Andy's was so good, I didn't want to edit it as if it was written by a group. And based mine on his. I think we should have a page for the aircraft and one or more manuals linked from it. Maybe there will not be enough material for that and manual can go on the same page as the aircraft data. I suppose a POH has history and data on the aircraft. In that case, I would name the page for an aircraft by its name and place the POH under a heading. Then you can't bookmark it as cleanly. Also the name of this page is really wrong, I think it should be Comper Swift. --Sek

Talk:Comper Swift

2006-06-03T03:15:29Z

Sek:

File:Mergedisputed.gif

2006-06-03T02:59:06Z

Sek: Merge Disputed (from MediaWiki_

Merge Disputed (from MediaWiki_

File:Split-arrows.gif

2006-06-03T02:38:46Z

Sek: Split Arrows (from MediaWiki)

Split Arrows (from MediaWiki)

Template:Mergefrom

2006-06-03T02:30:19Z

Sek: css

<div class="messagebox merge" style="border: 1px #ccc solid; padding:12px;margin: 12px">[[Image:Mergefrom.gif|left]] It has been suggested that ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]'' be merged into this article or section.</div>
<includeonly>[[Category:Articles to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>
<noinclude>
Comments go here.
</noinclude>

Template:Merge

2006-06-03T02:29:47Z

Sek: css

<div class="messagebox merge" style="border: 1px #ccc solid; padding:12px;margin: 12px">[[Image:Merge-arrow.gif|left]] It has been suggested that this article or section be merged with ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''.</div>
<includeonly>[[Category:Articles to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>
<noinclude>
Comments go here.
</noinclude>

Template:Mergeto

2006-06-03T02:26:39Z

Sek: css

<div class="messagebox merge" style="border: 1px #ccc solid; padding:12px;margin: 12px">[[Image:Merge-arrow.gif|left]] It has been suggested that this article or section be merged into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. </div>
<includeonly>[[Category:Articles to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>
<noinclude>
Comments go here.
</noinclude>

Template:Mergeto

2006-06-03T02:25:50Z

Sek: adding css

<div class="messagebox merge" style="border: 1px #ccc solid">[[Image:Merge-arrow.gif|left]] It has been suggested that this article or section be merged into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. </div>
<includeonly>[[Category:Articles to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>
<noinclude>
Comments go here.
</noinclude>

Template:Mergeto

2006-06-03T02:21:57Z

Sek: commenting out discuss tags

<div class="messagebox merge">[[Image:Merge-arrow.gif|left]] It has been suggested that this article or section be merged into ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. </div>
<includeonly>[[Category:Articles to be merged|{{PAGENAME}} (into {{{1}}})]]</includeonly>
<noinclude>
Comments go here.
</noinclude>

File:Merge-arrows.gif

2006-06-03T01:54:12Z

Sek: Merge Arrows (from MediaWiki)

Merge Arrows (from MediaWiki)

File:Merge-arrow.gif

2006-06-03T01:52:34Z

Sek: Merge Arrow (from MediaWiki)

Merge Arrow (from MediaWiki)

File:Mergefrom.gif

2006-06-03T01:51:53Z

Sek: Merge From (from MediaWiki)

Merge From (from MediaWiki)

Martin Marietta X-24

2006-06-03T00:44:35Z

Sek:

Alias for x24b. x24b Alias for x24b-jsbsim. x24b-jsbsim USAF/NACA X-24B reentry testbed

== Development status/Issues/Todo ==
Outside:

* aircraft has no 3d model
* 3d Cockpit:
* 3d cockpit is not available General:
* Hud is not available

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Wright Flyer

2006-06-03T00:44:17Z

Sek:

== Development status/Issues/Todo ==
Outside:

* aircraft has no shadow

3d Cockpit:

General:

* propeller is not moving/turning when engine is running at low power
* engines can't be turned off

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Tupolev Tu-154 (YASim)

2006-06-03T00:43:55Z

Sek:

== Development status/Issues/Todo ==
Outside:

* there is a small bug on the right wing when lowering the flaps
* you can see inside the hull from behind when moving the rudder to the left or right
* cockpit and passenger windows are not transparent
* wings, wheels and engines are not textured - engine turbine does not rotate
* aircraft has no shadow - no aircraft light available
* aircraft has no wheel well area for the landing gears
* aircraft has no bay doors for the landing gears - no jet stream visible
* nozzle do not change shape when changing thrust (nor does the real one, so it's not a fault)
* there are no flaps when using reverse thrust

3d Cockpit:

* 3d cockpit is not available

General:

* no hud available

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Pilatus PC-7

2006-06-03T00:43:22Z

Sek:

was: t6texan2 Alias for t6texan2-jsbsim.
t6texan2-jsbsim T-6A Texan II

== Development Status/Issues/Todo ==
Outside:

* no pilot in cockpit visible
* aircraft has no shadow
* no aircraft light available
* 3d Cockpit: - no textures used -
* no pilor or instructor

General:

* engines can't be turned off
* engine sound does not change when accelerating. This is common for turboprop engine though.
* no hud available

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Space Shuttle (FG Space Program)

2006-06-03T00:43:00Z

Sek:

shuttle Alias for shuttle-jsbsim.

== Development status/Issues/Todo ==
Outside:

* - aircraft has no 3d model 3d

Cockpit:

* 3d cockpit is not available

General:

* no hud available
* Because the shuttle is a glider without engines after reentry the initial starting position should be somewhere at an altidude of over 80000 feet

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Sopwith Camel

2006-06-03T00:42:38Z

Sek:

Alias for sopwithCamel-v1-nl-uiuc sopwithCamel-v1-nl-uiuc

== Development status/Issues/Todo ==
The following points are all being worked on (at least the sensible ones)

Outside:

* propeller is not moving/turning when engine is running at low power
* cockpit does not fit very nice with the other flightgear airplanes (especially compared to the j3cub)
maybe it is a good thing to create a new one
* ailerons and pitch elevator are not animated

3d Cockpit:

* 3d cockpit is not available

General:

* engines can't be turned off
* no hud available -- Please be sensible!

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Soko J-22 Orao / IAR-93

2006-06-03T00:42:17Z

Sek:

== Development status/Issues/Todo ==
Outside:

* flaps are animated but flap sound can only be barely heard
* eninge turbine does not rotate or rotation is not visible
* no cockpit light at night visible
* aircraft has no shadow
* no aircraft light available
* no jetstream visible
* nozzle do not change shape when changing thrust
* there are no flaps when using reverse thrust

3d Cockpit:

* no cockpit light at night available
* no rudder/stick control in 3d cockpit available
* no ruder control pedals available
* no switches and leverls available
* no elevator trim control available
* no cockpit instruments available
* cockpit is not textured
* pilot is present but not animated

General:

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

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Schweizer 2-33

2006-06-03T00:41:31Z

Sek:

== Development status/Issues/Todo ==
Outside:

* when looking inside the cockpit there is an 3d error at the back seat
* flaps (what flaps? it has dive brakes and no flaps! --vassilii) are not animated
* rudder, ailerons and pitch elevator are not animated
* - no pilot/co-pilot in cockpit visible
* - aircraft is textured, but texture quality is poor and blocky (especially the text on the side)
* - aircraft has no shadow
* 3d Cockpit: - 3d cockpit is not available
* - ASI apparently borrowed from c172. V-speeds don't match sgs233. sgs233 has its ASI calibrated in MPH.

General:

* - no hud available
* - airplane does not crash, instead you can flight below the earth surface
* - initial starting postition shouldn't be over KSFO, because then every user will hear this noisy and disturbing warning sound because you're flighing over a runway (vassilii: I think the problem is rather that marker beacons shouldn't be received in the sgs as it has no electric stuff at all same with the radios)

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Piper Cherokee Warrior II

2006-06-03T00:40:57Z

Sek:

== Development status/Issues/Todo ==
Outside:
* - propeller is not visible (transparent) when rotating
* - when looking through the cockpit windows and on the instrument panel i can see the runway trough the instrument panel
* - flaps are moving in steps, they are not fluxional animated
* - no cockpit light at night visible
* - wings and wheels are not textured
* - aircraft has no shadow
* - no aircraft light available

3d Cockpit:

* no cockpit light at night available
* no rudder/stick control in 3d cockpit available
* no ruder control pedals available
* no switches and leverls available
* no elevator trim control available
* cockpit instruments are available but missing on the co-pilot side
* Usual Configuration in PA28s is left-side instrumentation only; radios not implemented yet
* cockpit instruments look flat, they don't have a 3d look
* cockpit is not textured
* no pilot or co pilot present
* cockpit window has no windscreen wipers;
** PA28s are not equipped with wipers.

General:

* aircraft is not set on the correct elevation when starting flightsgear, lowest part of the aircraft is approximately 0.40 m above the ground.

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

Piper J3 Cub

2006-06-03T00:40:32Z

Sek:

== Development status/Issues/Todo ==
Outside:

* pilot door is open and partly in the the wing rods
* does this airplane has flaps?
** Piper J3 Cubs do not have flaps.
* no pilot present in cockpit -
* no cockpit light at night visible
* aircraft has no shadow
* no aircraft light available

3d Cockpit:

* no cockpit light at night available
* no ruder control pedals available
* no switches and leverls available
* no elevator trim control available
* cockpit instruments (altimeter) can't be adjusted with the mouse
* cockpit is not textured
* no pilot present in cockpit

General:

* engine sound in cockpit does not differ from outside engine sound
* no hud available

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]